<div dir="ltr">@Mitan,<div><br></div><div style>"most of the time" is not really correct. It depends on our decisions. Here I want to support peer 2 peer call when both UA does not in symmetric NAT, to reduce task for the rtpproxy :)</div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Mar 4, 2013 at 5:43 PM, Mitan Lopez <span dir="ltr"><<a href="mailto:mitan23@aol.com" target="_blank">mitan23@aol.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<font color="black" face="arial">So RTP proxy servers are used most of the time in Internet to communicate between 2 UA's? (in this case why bother to check all those lines in kamailio cfg?)
<div><span class="HOEnZb"><font color="#888888"><br>
<div style="clear:both">Mitan Lopez<br>
<a href="mailto:mitan23@aol.com" target="_blank">mitan23@aol.com</a><br>
</div></font></span><div><div class="h5">
<br>
<br>
<div style="font-size:10pt;font-family:arial,helvetica">-----Original Message-----<br>
From: Alex Balashov <<a href="mailto:abalashov@evaristesys.com" target="_blank">abalashov@evaristesys.com</a>><br>
To: sr-users <<a href="mailto:sr-users@lists.sip-router.org" target="_blank">sr-users@lists.sip-router.org</a>><br>
Sent: Mon, Mar 4, 2013 11:30 am<br>
Subject: Re: [SR-Users] Cannot hear voice with symmetric NAT and STUN<br>
<br>
<div style="font-size:12px;font-family:Tahoma,Verdana,Arial,Sans-Serif;margin:0px">
<pre style="font-size:9pt"><tt>On 03/04/2013 02:55 AM, Khoa Pham wrote:
> @Alex: thanks for reply
>
> In this IPv4 world, most devices are in NAT, and it only matters if they
> are symmetric NAT or not.
>
> So if 1 client is behind symmetric NAT, I want to use rtpproxy,
> otherwise, I do not.
> According to what I read from kamailio cfg, Kamailio only knows if
> client is NATed or not, it doesnot know the NAT type
That's correct.
The only way you can infer whether a client is symmetric is through its
insertion of the 'rport' parameter into the Via header. However,
symmetric clients are not required to insert it; it is only so that a
client can request symmetric behaviour from a server. AS RFC 3581 says:
A client, compliant to this specification (clients include UACs and
proxies), MAY include an "rport" parameter in the top Via header
field value of requests it generates.
Certainly, there's nothing saying it must do so.
However, almost all UAs out there are symmetric these days. It's got to
be over 95%+. Have you run into one that isn't?
-- Alex
--
Alex Balashov - Principal
Evariste Systems LLC
235 E Ponce de Leon Ave
Suite 106
Decatur, GA 30030
United States
Tel: +1-678-954-0670
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>
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
<a href="mailto:sr-users@lists.sip-router.org" target="_blank">sr-users@lists.sip-router.org</a>
<a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users" target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a>
</tt></pre>
</div>
</div>
</div></div></div>
</font><br>_______________________________________________<br>
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list<br>
<a href="mailto:sr-users@lists.sip-router.org">sr-users@lists.sip-router.org</a><br>
<a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users" target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a><br>
<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>