<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">2013/3/26 Michael Collins <span dir="ltr"><<a href="mailto:msc@freeswitch.org" target="_blank">msc@freeswitch.org</a>></span><br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
showed specifically has "transport=tls</blockquote></div><br><br><span id="result_box" class="" lang="en"><span class="">I wrote in the</span> </span><span id="result_box" class="" lang="en">mailing list <span class=""> </span></span><span id="result_box" class="" lang="en"><span class="">Bogan </span> <span class="">response:<br>
<br></span></span><br><pre>Hi Alexsandr,
Well, the problem is more complex a bit. I see you configured OpenSIPs
to add PATH header to REGISTER before sending it to FS. The address in
PATH has UDP transport, so FS (if supports PATH) should send the calls
back to OpenSIPS by using the address from PATH (with UDP). The contact
in register has TLS transport (and you fwd it to FS as it is), but it
should not be used directly by FS because of the presence and priority
of PATH hdr.
So, my only explanation is that FS does not support / not configured to
handle PATH, so that it uses the address from contact, which is TLS.
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
<a href="http://www.opensips-solutions.com">http://www.opensips-solutions.com</a></pre><span id="result_box" class="" lang="en"><span class=""><br></span></span></div></div>