Hi Mark, <div><br></div><div>Try the global command <em style="font-weight:bold;font-style:normal;color:rgb(0,0,0);font-family:arial,sans-serif;font-size:small;font-variant:normal;letter-spacing:normal;line-height:16px;text-align:left;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255)">advertised_address</em><span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:16px;text-align:left;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);display:inline!important;float:none">="</span><span style="font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant:normal;letter-spacing:normal;line-height:16px;text-align:left;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);display:inline!important;float:none"><font class="Apple-style-span" color="#000000"><b>domain</b></font></span><span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:16px;text-align:left;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);display:inline!important;float:none">.org" or the external IP address. It should fix the problem with record routing.</span></div>
<div class="gmail_extra"><br clear="all"><div><div>Flavio E. Goncalves</div><div><br></div></div>
<br><br><div class="gmail_quote">2013/1/4 Mark Currie <span dir="ltr"><<a href="mailto:mark@ziliant.com" target="_blank">mark@ziliant.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div lang="EN-ZA" link="blue" vlink="purple"><div><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Thanks for the advice Flavio.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Currently I am actually pretty close with my NAT’ed OpenSIPS and NAT’ed clients. I am assuming this is because I have a simple NAT scenario with full-cone NATs.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">I get as far as making a call, but when I pick-up the call only one side gets RTP through. I traced the problem to the fact that a local address is being put in the “Record Route” section of an ACK response.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">I would like to try to get this more controllable scenario working first before I launch into new complexity with RTP proxies etc. I think that I just need to know how to get the fix_nat_sip() and fix_nat_contact() to work. Any pointers with that?<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Regards<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Mark<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt"><div><div style="border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0cm 0cm 0cm"><p class="MsoNormal"><b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> <a href="mailto:users-bounces@lists.opensips.org" target="_blank">users-bounces@lists.opensips.org</a> [mailto:<a href="mailto:users-bounces@lists.opensips.org" target="_blank">users-bounces@lists.opensips.org</a>] <b>On Behalf Of </b>Flavio Goncalves<br>
<b>Sent:</b> 03 January 2013 12:27<br><b>To:</b> OpenSIPS users mailling list<br><b>Subject:</b> Re: [OpenSIPS-Users] NAT issues on client and server<u></u><u></u></span></p></div></div><div><div class="h5"><p class="MsoNormal">
<u></u> <u></u></p><p class="MsoNormal">Hi Mark, <u></u><u></u></p><div><p class="MsoNormal"><u></u> <u></u></p></div><div><p class="MsoNormal">There is no simple way to traverse NAT. Unless all your routers use a non symmetric NAT, you will have to use rtpproxy or mediaproxy (you can check this with a stun client). OpenSIPS behind NAT make things even more complicated. So I suggest that you follow an example with rtpproxy or media proxy and also use the OpenSIPS in a valid IP address. The setup you are trying to do with OpenSIPS behind NAT is possible, but it is even more complex. <u></u><u></u></p>
</div><div><p class="MsoNormal"><br clear="all"><u></u><u></u></p><div><div><p class="MsoNormal">Flavio E. Goncalves<u></u><u></u></p></div><div><p class="MsoNormal"> <u></u><u></u></p></div></div><p class="MsoNormal" style="margin-bottom:12.0pt">
<u></u> <u></u></p><div><p class="MsoNormal">2013/1/3 Mark Currie <<a href="mailto:mark@ziliant.com" target="_blank">mark@ziliant.com</a>><u></u><u></u></p><p class="MsoNormal">Hi,<br><br>I have a very simple setup for a closed network of users (all NAT'ed) with<br>
one OpenSIPS server (also NAT'ed).<br><br>I have managed to solve my first problem with registration by following<br>previous posts and using fix_nat_register(), but I am still having problems<br>with NAT issues during a call. I know that I probably need to use<br>
fix_nat_contact() and fix_nat_sip() but I can't figure out how to use these<br>properly through the documentation.<br><br>I have tried to search for examples of opensips.cfg that suit my scenario<br>but all the ones I found are complicated with proxies etc. Can someone point<br>
me to simple example of opensips.cfg that takes care of NAT?<br><br>Regards<br>Mark Currie<br><br><br>_______________________________________________<br>Users mailing list<br><a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><u></u><u></u></p></div><p class="MsoNormal"><u></u> <u></u></p></div></div></div>
</div></div></div><br>_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
<br></blockquote></div><br></div>