I think that the solution is using force_tcp_alias. This would solve the problem for the incoming bye, as ser would<br>
search for an already open tcp connection to alice (let's hope is still there). The phone of alice needs not know/support<br>
connection reuse draft (ser does).<br>
This solved a similar problem i used to have, as you pointed me. Now i do a force_tcp_alias for all mesages going<br>
through the config file ... probably not optimal, but my config file is faaar from optimal :)<br>
<br>
Regards<br>
<br>
Cesc<br><br><div><span class="gmail_quote">On 10/15/05, <b class="gmail_sendername">Alexander Ph. Lintenhofer</b> &lt;<a href="mailto:lintenhofer@aon.at">lintenhofer@aon.at</a>&gt; wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi everybody,<br><br>A short question:<br><br><a href="mailto:alice@atlanta.com">alice@atlanta.com</a> is behind NAT. She uses TCP to connect her UAC to<br><a href="http://sip.atlanta.com">sip.atlanta.com</a> in the public network.
<br>Inviting <a href="mailto:bob@biloxi.com">bob@biloxi.com</a> suceeds. But Bob can't terminate the call. His<br>BYE is not routed back, because fix_nated_contact() does only work with<br>UDP. And Bob builds the R-URI with the Infos of Alice's contact header.
<br><br>The route is as follows:<br><a href="mailto:alice@atlanta.com">alice@atlanta.com</a> [<a href="http://172.16.0.4">172.16.0.4</a>] -&gt; <a href="http://natbox.atlanta.com">natbox.atlanta.com</a> [<a href="http://172.16.0.1">
172.16.0.1</a> |<br><a href="http://192.168.0.13">192.168.0.13</a>] -&gt; <a href="http://sip.atlanta.com">sip.atlanta.com</a> [<a href="http://192.168.0.14">192.168.0.14</a>] -&gt; <a href="http://sip.biloxi.com">sip.biloxi.com
</a><br>[<a href="http://192.168.1.14">192.168.1.14</a>] -&gt; <a href="mailto:bob@biloxi.com">bob@biloxi.com</a> [<a href="http://192.168.1.1">192.168.1.1</a>]<br><br>Possible solutions:<br>- force_tcp_alias() -&gt; but reading the draft
<br>draft-ietf-sip-connect-reuse-04.txt yields that this must be supported<br>by the components - so doesn't the snom360 of Alice<br>- commenting some lines in nathelper.c and activate it for TCP -&gt; this<br>works pretty fine and the BYE finds its way from Bob through the NAT-Box
<br>to Alice. But this is a dirty solution.<br><br>So does anybody has a similar problem? My config works fine with UDP but<br>switching to TCP makes life hard...<br>I attached the traces Bob received, his last BYE is finally dropped by
<br><a href="http://sip.atlanta.com">sip.atlanta.com</a>, because the network-address <a href="http://172.16.0.4">172.16.0.4</a> can't be found!<br><br>Thank you for your help!<br>regards, Philipp<br><br>=========================================================================
<br><br>Received from tcp:<a href="http://192.168.1.14:5060">192.168.1.14:5060</a> at 15/10/2005 19:18:32:250 (1751 bytes):<br><br>INVITE sip:bob@192.168.1.1:2063;transport=tcp;line=wxqurd1s SIP/2.0<br>Record-Route: &lt;sip:
<a href="http://192.168.1.14">192.168.1.14</a>;transport=tcp;r2=on;ftag=5s8qncdbso;lr=on&gt;<br>Record-Route:<br>&lt;sip:<a href="http://192.168.1.14:5061">192.168.1.14:5061</a>;transport=tls;r2=on;ftag=5s8qncdbso;lr=on&gt;
<br>Record-Route:<br>&lt;sip:<a href="http://192.168.0.14:5061">192.168.0.14:5061</a>;transport=tls;r2=on;ftag=5s8qncdbso;lr=on&gt;<br>Record-Route: &lt;sip:<a href="http://192.168.0.14">192.168.0.14</a>;transport=tcp;r2=on;ftag=5s8qncdbso;lr=on&gt;
<br>Via: SIP/2.0/TCP <a href="http://192.168.1.14">192.168.1.14</a>;branch=z9hG4bKcad9.057cd815.0;i=d<br>Via: SIP/2.0/TLS <a href="http://192.168.0.14:5061">192.168.0.14:5061</a>;branch=z9hG4bKcad9.685be3c3.0;i=1<br>Via: SIP/2.0/TCP
<br><a href="http://172.16.0.4:2327">172.16.0.4:2327</a>;received=<a href="http://192.168.0.13">192.168.0.13</a>;branch=z9hG4bK-y79imu6dlqxs;rport=2327<br>From: &quot;Alice&quot; &lt;<a href="mailto:sip:alice@atlanta.com">
sip:alice@atlanta.com</a>&gt;;tag=5s8qncdbso<br>To: &lt;<a href="mailto:sip:bob@biloxi.com">sip:bob@biloxi.com</a>&gt;<br>Call-ID: 3c2675cac832-ce5ge5sxlx2q@snom360<br>CSeq: 1 INVITE<br>Max-Forwards: 68<br>Contact: &lt;sip:alice@172.16.0.4
:2327;transport=tcp;line=fyyuh6tl&gt;<br>P-Key-Flags: resolution=&quot;31x13&quot;, keys=&quot;4&quot;<br>User-Agent: snom360/4.3<br>Accept: application/sdp<br>Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, SUBSCRIBE,
<br>PRACK, MESSAGE, INFO<br>Allow-Events: talk, hold, refer<br>Supported: timer, 100rel, replaces, callerid<br>Session-Expires: 3600<br>Content-Type: application/sdp<br>Content-Length: 507<br>P-hint: outbound<br>P-hint: forced TLS relay
<br>P-hint: usrloc applied<br><br>Sent to tcp:<a href="http://192.168.1.14:5060">192.168.1.14:5060</a> at 15/10/2005 19:18:32:270 (929 bytes):<br><br>SIP/2.0 180 Ringing<br>Via: SIP/2.0/TCP <a href="http://192.168.1.14">192.168.1.14
</a>;branch=z9hG4bKcad9.057cd815.0;i=d<br>Via: SIP/2.0/TLS <a href="http://192.168.0.14:5061">192.168.0.14:5061</a>;branch=z9hG4bKcad9.685be3c3.0;i=1<br>Via: SIP/2.0/TCP<br><a href="http://172.16.0.4:2327">172.16.0.4:2327
</a>;received=<a href="http://192.168.0.13">192.168.0.13</a>;branch=z9hG4bK-y79imu6dlqxs;rport=2327<br>Record-Route: &lt;sip:<a href="http://192.168.1.14">192.168.1.14</a>;transport=tcp;r2=on;ftag=5s8qncdbso;lr=on&gt;<br>
Record-Route:<br>&lt;sip:<a href="http://192.168.1.14:5061">192.168.1.14:5061</a>;transport=tls;r2=on;ftag=5s8qncdbso;lr=on&gt;<br>Record-Route:<br>&lt;sip:<a href="http://192.168.0.14:5061">192.168.0.14:5061</a>;transport=tls;r2=on;ftag=5s8qncdbso;lr=on&gt;
<br>Record-Route: &lt;sip:<a href="http://192.168.0.14">192.168.0.14</a>;transport=tcp;r2=on;ftag=5s8qncdbso;lr=on&gt;<br>From: &quot;Alice&quot; &lt;<a href="mailto:sip:alice@atlanta.com">sip:alice@atlanta.com</a>&gt;;tag=5s8qncdbso
<br>To: &lt;<a href="mailto:sip:bob@biloxi.com">sip:bob@biloxi.com</a>&gt;;tag=fxdufnc4xz<br>Call-ID: 3c2675cac832-ce5ge5sxlx2q@snom360<br>CSeq: 1 INVITE<br>Contact: &lt;sip:bob@192.168.1.1:2063;transport=tcp;line=wxqurd1s&gt;
<br>Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, SUBSCRIBE,<br>PRACK, MESSAGE, INFO<br>Allow-Events: talk, hold, refer<br>Content-Length: 0<br><br>Sent to tcp:<a href="http://192.168.1.14:5060">192.168.1.14:5060
</a> at 15/10/2005 19:18:33:390 (1377 bytes):<br><br>SIP/2.0 200 Ok<br>Via: SIP/2.0/TCP <a href="http://192.168.1.14">192.168.1.14</a>;branch=z9hG4bKcad9.057cd815.0;i=d<br>Via: SIP/2.0/TLS <a href="http://192.168.0.14:5061">
192.168.0.14:5061</a>;branch=z9hG4bKcad9.685be3c3.0;i=1<br>Via: SIP/2.0/TCP<br><a href="http://172.16.0.4:2327">172.16.0.4:2327</a>;received=<a href="http://192.168.0.13">192.168.0.13</a>;branch=z9hG4bK-y79imu6dlqxs;rport=2327
<br>Record-Route: &lt;sip:<a href="http://192.168.1.14">192.168.1.14</a>;transport=tcp;r2=on;ftag=5s8qncdbso;lr=on&gt;<br>Record-Route:<br>&lt;sip:<a href="http://192.168.1.14:5061">192.168.1.14:5061</a>;transport=tls;r2=on;ftag=5s8qncdbso;lr=on&gt;
<br>Record-Route:<br>&lt;sip:<a href="http://192.168.0.14:5061">192.168.0.14:5061</a>;transport=tls;r2=on;ftag=5s8qncdbso;lr=on&gt;<br>Record-Route: &lt;sip:<a href="http://192.168.0.14">192.168.0.14</a>;transport=tcp;r2=on;ftag=5s8qncdbso;lr=on&gt;
<br>From: &quot;Alice&quot; &lt;<a href="mailto:sip:alice@atlanta.com">sip:alice@atlanta.com</a>&gt;;tag=5s8qncdbso<br>To: &lt;<a href="mailto:sip:bob@biloxi.com">sip:bob@biloxi.com</a>&gt;;tag=fxdufnc4xz<br>Call-ID: 3c2675cac832-ce5ge5sxlx2q@snom360
<br>CSeq: 1 INVITE<br>Contact: &lt;sip:bob@192.168.1.1:2063;transport=tcp;line=wxqurd1s&gt;<br>Require: timer<br>Session-Expires: 3600;refresher=uac<br>User-Agent: snom360/4.3<br>Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, SUBSCRIBE,
<br>PRACK, MESSAGE, INFO<br>Allow-Events: talk, hold, refer<br>Supported: timer, 100rel, replaces, callerid<br>Content-Type: application/sdp<br>Content-Length: 296<br><br>ACK sip:bob@192.168.1.1:2063;transport=tcp;line=wxqurd1s SIP/2.0
<br>Record-Route: &lt;sip:<a href="http://192.168.1.14">192.168.1.14</a>;transport=tcp;r2=on;ftag=5s8qncdbso;lr=on&gt;<br>Record-Route:<br>&lt;sip:<a href="http://192.168.1.14:5061">192.168.1.14:5061</a>;transport=tls;r2=on;ftag=5s8qncdbso;lr=on&gt;
<br>Record-Route:<br>&lt;sip:<a href="http://192.168.0.14:5061">192.168.0.14:5061</a>;transport=tls;r2=on;ftag=5s8qncdbso;lr=on&gt;<br>Record-Route: &lt;sip:<a href="http://192.168.0.14">192.168.0.14</a>;transport=tcp;r2=on;ftag=5s8qncdbso;lr=on&gt;
<br>Via: SIP/2.0/TCP <a href="http://192.168.1.14">192.168.1.14</a>;branch=0;i=d<br>Via: SIP/2.0/TLS <a href="http://192.168.0.14:5061">192.168.0.14:5061</a>;branch=0;i=1<br>Via: SIP/2.0/TCP<br><a href="http://172.16.0.4:2327">
172.16.0.4:2327</a>;received=<a href="http://192.168.0.13">192.168.0.13</a>;branch=z9hG4bK-o9f1lglhf4pk;rport=2327<br>From: &quot;Alice&quot; &lt;<a href="mailto:sip:alice@atlanta.com">sip:alice@atlanta.com</a>&gt;;tag=5s8qncdbso
<br>To: &lt;<a href="mailto:sip:bob@biloxi.com">sip:bob@biloxi.com</a>&gt;;tag=fxdufnc4xz<br>Call-ID: 3c2675cac832-ce5ge5sxlx2q@snom360<br>CSeq: 1 ACK<br>Max-Forwards: 68<br>Contact: &lt;sip:alice@172.16.0.4:2327;transport=tcp;line=fyyuh6tl&gt;
<br>Content-Length: 0<br>P-hint: rr-enforced<br>P-hint: rr-enforced<br><br>Sent to tcp:<a href="http://192.168.1.14:5060">192.168.1.14:5060</a> at 15/10/2005 19:18:34:480 (703 bytes):<br><br>BYE sip:alice@172.16.0.4:2327;transport=tcp;line=fyyuh6tl SIP/2.0
<br>Via: SIP/2.0/TCP <a href="http://192.168.1.1:2063">192.168.1.1:2063</a>;branch=z9hG4bK-gu03sll9uumm;rport<br>Route: &lt;sip:<a href="http://192.168.1.14">192.168.1.14</a>;transport=tcp;r2=on;ftag=5s8qncdbso;lr=on&gt;<br>
Route: &lt;sip:<a href="http://192.168.1.14:5061">192.168.1.14:5061</a>;transport=tls;r2=on;ftag=5s8qncdbso;lr=on&gt;<br>Route: &lt;sip:<a href="http://192.168.0.14:5061">192.168.0.14:5061</a>;transport=tls;r2=on;ftag=5s8qncdbso;lr=on&gt;
<br>Route: &lt;sip:<a href="http://192.168.0.14">192.168.0.14</a>;transport=tcp;r2=on;ftag=5s8qncdbso;lr=on&gt;<br>From: &lt;<a href="mailto:sip:bob@biloxi.com">sip:bob@biloxi.com</a>&gt;;tag=fxdufnc4xz<br>To: &quot;Alice&quot; &lt;
<a href="mailto:sip:alice@atlanta.com">sip:alice@atlanta.com</a>&gt;;tag=5s8qncdbso<br>Call-ID: 3c2675cac832-ce5ge5sxlx2q@snom360<br>CSeq: 1 BYE<br>Max-Forwards: 70<br>Contact: &lt;sip:bob@192.168.1.1:2063;transport=tcp;line=wxqurd1s&gt;
<br>User-Agent: snom360/4.3<br>Content-Length: 0<br><br>_______________________________________________<br>Serusers mailing list<br><a href="mailto:Serusers@iptel.org">Serusers@iptel.org</a><br><a href="http://mail.iptel.org/mailman/listinfo/serusers">
http://mail.iptel.org/mailman/listinfo/serusers</a><br></blockquote></div><br>