<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix"><tt>Hi George,<br>
<br>
NAT traversal is not only about pinging, but also about
mangling/correcting the SIP traffic (from private IPs
perspective) and ensuring the RTP flow.<br>
<br>
So you need to be sure that all 3 points are addressed.<br>
<br>
TCP versus UDP - there is only a difference at IP transport
level...like datagram versus connection, and their implications
at NAT level (being able to reach the device behind the nat).
Otherwise it;s the same.<br>
<br>
For UDP, can you see what fails ? the registration? reaching the
UAC ? <br>
<br>
Regards,<br>
</tt>
<pre class="moz-signature" cols="72">Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
<a class="moz-txt-link-freetext" href="http://www.opensips-solutions.com">http://www.opensips-solutions.com</a></pre>
On 14.10.2014 18:37, george wu wrote:<br>
</div>
<blockquote
cite="mid:9f50cdb.2658d.1490f4e26ee.Coremail.aihuawu2012@163.com"
type="cite">
<div
style="line-height:1.7;color:#000000;font-size:14px;font-family:Arial">
<div>My experience is for two uac (linphone) behind a firewall,<br>
tcp/tls will always work.<br>
udp will never work.<br>
<br>
for both tcp/udp, my uac will send keep alive every 10
seconds.<br>
I don't understand what makes those difference.<br>
Can any one share your experience?<br>
<br>
George Wu<br>
<br>
<br>
</div>
</div>
<br>
<br>
<span title="neteasefooter"><span id="netease_mail_footer"></span></span><br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a>
<a class="moz-txt-link-freetext" href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a>
</pre>
</blockquote>
<br>
</body>
</html>