Hello Lawrence,<br><br>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 ...<br>
<br>Thanks,<br><br>Michel<br><br><div class="gmail_quote">On Mon, Apr 22, 2013 at 7:05 PM, Lawrence Conroy <span dir="ltr"><<a href="mailto:lconroy@insensate.co.uk" target="_blank">lconroy@insensate.co.uk</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi There,<br>
have you looked at <<a href="http://www.ietf.org/rfc/rfc3263.txt" target="_blank">http://www.ietf.org/rfc/rfc3263.txt</a>>, and in particular section 5 on page 11?<br>
<br>
IIUC, you're asking for an SRV lookup when the server sends a 100 trying back towards the UAC.<br>
<br>
For the terminally lazy, here's the second paragraph of 3263 section 5:<br>
A server, according to RFC 3261 [1], will send a response on the<br>
connection it arrived on (in the case of reliable transport<br>
protocols), and for unreliable transport protocols, to the source<br>
address of the request, and the port in the Via header field. The<br>
procedures here are invoked when a server attempts to send to that<br>
location and that response fails (the specific conditions are<br>
detailed in RFC 3261). "Fails" is defined as any closure of the<br>
transport connection the request came in on before the response can<br>
be sent, or communication of a fatal error from the transport layer.<br>
<br>
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.<br>
If it did have an explicit port value, then I'd kinda guess that that's where it would be sent.<br>
<br>
i.e., it looks to me like fS is performing as the SIP standard requires.<br>
<br>
all the best,<br>
Lawrence<br>
<div><div class="h5"><br>
On 22 Apr 2013, at 16:30, Michel Brabants wrote:<br>
> 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).<br>
> Michel<br>
><br>
> On Mon, Apr 22, 2013 at 5:28 PM, Michel Brabants<br>
> <<a href="mailto:michel.brabants@gmail.com">michel.brabants@gmail.com</a>>wrote:<br>
>> Hello,<br>
>><br>
>> one more question. While performing tests, I noticed that freeswitch<br>
>> didn't respond to the port that is specified in the srv-record, which is in<br>
>> the contact-address. This is when it receives an incoming invite in one of<br>
>> the defined gateways in freeswitch. The srv-record has 5062 in it, but<br>
>> freeswitch doesn't seem to try to resolve the srv-record.<br>
>><br>
>> Kind regards,<br>
>><br>
>> Michel<br>
<br>
<br>
</div></div>_________________________________________________________________________<br>
Professional FreeSWITCH Consulting Services:<br>
<a href="mailto:consulting@freeswitch.org">consulting@freeswitch.org</a><br>
<a href="http://www.freeswitchsolutions.com" target="_blank">http://www.freeswitchsolutions.com</a><br>
<br>
FreeSWITCH-powered IP PBX: The CudaTel Communication Server<br>
<a href="http://www.cudatel.com" target="_blank">http://www.cudatel.com</a><br>
<br>
Official FreeSWITCH Sites<br>
<a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
<a href="http://wiki.freeswitch.org" target="_blank">http://wiki.freeswitch.org</a><br>
<a href="http://www.cluecon.com" target="_blank">http://www.cluecon.com</a><br>
<br>
FreeSWITCH-users mailing list<br>
<a href="mailto:FreeSWITCH-users@lists.freeswitch.org">FreeSWITCH-users@lists.freeswitch.org</a><br>
<a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a><br>
UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-users</a><br>
<a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
</blockquote></div><br>