<div dir="ltr">@Alex:<div><br></div><div style>Many router out there are using Full cone NAT. </div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Mar 5, 2013 at 7:08 PM, Alex Balashov <span dir="ltr"><<a href="mailto:abalashov@evaristesys.com" target="_blank">abalashov@evaristesys.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On 03/05/2013 07:04 AM, Khoa Pham wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
When client use STUN, it can detect the NAT type. When client<br>
register, it contains x-NAT (0:unknown, 1: full cone, ..., 6:<br>
symmetric), which will be helpful for the server to detect NAT type.<br>
</blockquote>
<br></div>
Again, where are you finding these nonsymmetric clients? The amount of non-symmetrical SIP and RTP implementations out there in the wild at this point is negligible.<br>
<br>
-- <br>
Alex Balashov - Principal<br>
Evariste Systems LLC<br>
235 E Ponce de Leon Ave<br>
Suite 106<br>
Decatur, GA 30030<br>
United States<br>
Tel: +1-678-954-0670<br>
Web: <a href="http://www.evaristesys.com/" target="_blank">http://www.evaristesys.com/</a>, <a href="http://www.alexbalashov.com/" target="_blank">http://www.alexbalashov.com/</a><br>
<br>
______________________________<u></u>_________________<br>
sr-dev mailing list<br>
<a href="mailto:sr-dev@lists.sip-router.org" target="_blank">sr-dev@lists.sip-router.org</a><br>
<a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev" target="_blank">http://lists.sip-router.org/<u></u>cgi-bin/mailman/listinfo/sr-<u></u>dev</a><br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><span style="color:rgb(0,0,0)">Khoa Pham</span><br style="color:rgb(0,0,0)"><span style="color:rgb(0,0,0)">HCMC University of Science</span><br style="color:rgb(0,0,0)">
<span style="color:rgb(0,0,0)">Faculty of Information Technology</span><br>
</div>