<table cellspacing="0" cellpadding="0" border="0" ><tr><td valign="top" style="font: inherit;">Hi,<br><br>When NAT = YES, Asterisk server will extract IP from the network layer. <br> <br>When Nat = No, the Asterisk server will respond to the IP in the SIP header. Am I right?<br><br>May be such type of options can be helpful for SIP application developers.<br><br>Can't think of a scenario but If it is set to be YES for all peers, what will happen is that the<span style="font-weight: bold;"> response </span>to all the SIP request will be routed to the IP in the network layer. IP's in the SIP header will be ignored, should not create a problem.<br> <br><br>Regards<br><br>--- On <b>Sun, 4/24/11, Steve Totaro <i><stotaro@asteriskhelpdesk.com></i></b> wrote:<br><blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"><br>From: Steve Totaro <stotaro@asteriskhelpdesk.com><br>Subject: Re:
[asterisk-users] Nat=yes<br>To: "Asterisk Users Mailing List - Non-Commercial Discussion" <asterisk-users@lists.digium.com><br>Date: Sunday, April 24, 2011, 2:13 PM<br><br><div id="yiv1727955616"><br><br><div class="yiv1727955616gmail_quote">On Thu, Apr 21, 2011 at 5:42 AM, Alexandru Oniciuc <span dir="ltr"><<a rel="nofollow" ymailto="mailto:Alexandru.Oniciuc@trivenet.it" target="_blank" href="/mc/compose?to=Alexandru.Oniciuc@trivenet.it">Alexandru.Oniciuc@trivenet.it</a>></span> wrote:<br><blockquote class="yiv1727955616gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div lang="IT"><div><p class="yiv1727955616MsoNormal"><span lang="EN-US">Dear * users,</span></p><p class="yiv1727955616MsoNormal"><span lang="EN-US"> </span></p><p class="yiv1727955616MsoNormal"><span lang="EN-US">in your opinion, when using a * as a public server, is good practice enabling nat=yes in sip.conf for all the peers?</span></p>
<p class="yiv1727955616MsoNormal"><span lang="EN-US">Can anyone imagine a scenario when enabling this parameter (even for peers that don’t require it) can cause problems?</span></p><p class="yiv1727955616MsoNormal"><span lang="EN-US"> </span></p><p class="yiv1727955616MsoNormal">
<span lang="EN-US">Regards and thanks in advance,</span></p><p class="yiv1727955616MsoNormal"><span lang="EN-US">Alex</span></p><p class="yiv1727955616MsoNormal"><span lang="EN-US"> </span></p></div></div><br></blockquote><div><br>I asked this same exact question several years ago. There are many replies with different takes. I would skim through Alex's posts, there is really nothing worth reading except it will break the SIP RFC handed down by the internets themselves.<br>
<br>I use nat=yes all the time and it works just fine.<br><br><a rel="nofollow" target="_blank" href="http://www.mail-archive.com/asterisk-users@lists.digium.com/msg213941.html">http://www.mail-archive.com/asterisk-users@lists.digium.com/msg213941.html</a><br>
<br>Nobody actually answered the question about the bad side, they just argued about the SIP RFC.<br><br>Many others agreed to make it default behavior and that setting nat=yes gives a an extra degree of security.<br><br>
RFCs are great and all, but in the real world, phones just need to work.<br><br>Thanks,<br>Steve Totaro<br> <br></div></div>
</div><br>-----Inline Attachment Follows-----<br><br><div class="plainMail">--<br>_____________________________________________________________________<br>-- Bandwidth and Colocation Provided by <a href="http://www.api-digital.com" target="_blank">http://www.api-digital.com</a> --<br>New to Asterisk? Join us for a live introductory webinar every Thurs:<br> <a href="http://www.asterisk.org/hello" target="_blank">http://www.asterisk.org/hello</a><br><br>asterisk-users mailing list<br>To UNSUBSCRIBE or update options visit:<br> <a href="http://lists.digium.com/mailman/listinfo/asterisk-users" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-users</a></div></blockquote></td></tr></table>