Hi There, have you looked at <http://www.ietf.org/rfc/rfc3263.txt>, and in particular section 5 on page 11? IIUC, you're asking for an SRV lookup when the server sends a 100 trying back towards the UAC. For the terminally lazy, here's the second paragraph of 3263 section 5: A server, according to RFC 3261 [1], will send a response on the connection it arrived on (in the case of reliable transport protocols), and for unreliable transport protocols, to the source address of the request, and the port in the Via header field. The procedures here are invoked when a server attempts to send to that location and that response fails (the specific conditions are detailed in RFC 3261). "Fails" is defined as any closure of the transport connection the request came in on before the response can be sent, or communication of a fatal error from the transport layer. I'm assuming that the via in your INVITE did not include a port, so the UAS should send it back to the default port, according to 3263. If it did have an explicit port value, then I'd kinda guess that that's where it would be sent. i.e., it looks to me like fS is performing as the SIP standard requires. all the best, Lawrence On 22 Apr 2013, at 16:30, Michel Brabants wrote:

I'm taling here about the trying that freeswitch sends in response to the invite. It goes to the wrong port (5060 instead of 5062). Michel

On Mon, Apr 22, 2013 at 5:28 PM, Michel Brabants <michel.brabants@gmail.com>wrote:

...

Hello,

one more question. While performing tests, I noticed that freeswitch didn't respond to the port that is specified in the srv-record, which is in the contact-address. This is when it receives an incoming invite in one of the defined gateways in freeswitch. The srv-record has 5062 in it, but freeswitch doesn't seem to try to resolve the srv-record.

Kind regards,

Michel

I wasn't aware that SRV Records were required for responses to a request. -- Brian West brian@freeswitch.org FreeSWITCH Solutions, LLC PO BOX PO BOX 2531 Brookfield, WI 53008-2531 Twitter: @FreeSWITCH_Wire T: +1.918.420.9266 | F: +1.918.420.9267 | M: +1.918.424.WEST iNUM: +883 5100 1420 9266 ISN: 410*543 On Apr 22, 2013, at 12:47 PM, Michel Brabants <michel.brabants@gmail.com> wrote:

Hello Lawrence,

thanks for the quick response. I'll have a further look, but this makes srv-records almost useless in my case. I'll probably use the option to send always back to the receiver-ports. There is no way for me that the rport-field to the via-header and normally it would be obtainable from the srv-record if it was used ...

Thanks,

Michel