hello, <br><br>im just wondering if it is possible to make FS re-use the existing TLS connection established on UA registratioin for incoming calls to UA?<br><br><br>as an example... i have extensions 1002 (uses TLS) and 1009 (uses SIP/UDP). Both extensions are registered to the same FS. I can place calls from 1002 everywhere but 1002 cannot get any calls.<br>
<br><a href="http://pastebin.freeswitch.org/19575">http://pastebin.freeswitch.org/19575</a><br><br><br><br>recv 394 bytes from tls/[109.227.38.121]:<span style="background-color:rgb(255,255,0)">60591 </span>at 18:16:03.019253:<br>
------------------------------------------------------------------------<br> REGISTER sip:85.114.35.241 SIP/2.0<br> Via: SIP/2.0/TLS <span style="background-color:rgb(255,255,0)"><a href="http://109.227.38.121:5061">109.227.38.121:5061</a></span>;rport;branch=z9hG4bK419550279<br>
From: <<a href="mailto:sip%3A1002@85.114.35.241">sip:1002@85.114.35.241</a>>;tag=376877386<br> To: <<a href="mailto:sip%3A1002@85.114.35.241">sip:1002@85.114.35.241</a>><br> Call-ID: 665211288<br> CSeq: 1 REGISTER<br>
Contact: <sip:1002@<span style="background-color:rgb(255,255,0)"><a href="http://109.227.38.121:5061">109.227.38.121:5061</a></span>;transport=tls;line=d85e74961f65cc6><br> Max-Forwards: 70<br> User-Agent: Linphone/3.4.0 (eXosip2/unknown)<br>
Expires: 2000<br> Content-Length: 0<br> <br> ------------------------------------------------------------------------<br><br>I know this register message is broken... good for TCP/UDP but bad for TLS :=)<br><br><br>
anyhow, extension 1002 establishes a TLS flow <a href="http://109.227.38.121:60591">109.227.38.121:60591</a> <> <a href="http://85.114.35.241:5061">85.114.35.241:5061</a><br>of course you know what happens when 1009 calls 1002, since 1002 advertized address:port in contact header different than the source port of the existing flow, FS tries to establish a new transport towards the UA and it fails. :=)<br>
<br>So is there any way we can force FS to re-use the existing flow and send subsequent request messages via existing connection rather than trying to establish a new one that is going to fail miserably?<br><br><br>The more i write this e-mail, the more i realize its a UA problem... don't advertize something you cannot get a call on... but anyhow... needed to ask that question :=)<br>
<br><br>so, how do we fix this ?<br>is the implementation of RFC5626 on client side the answer for that... does FS support this rfc at all ?<br>the other solution should be to tie contact port to transport port but that's a hack..<br>
<br>any good advice in how to fix the UA behavior so it can send and receive calls via TLS connections?<br><br><br>regards,<br>Tihomir.<br><br><br><br><br><br><br><br>