<br><br><div class="gmail_quote">On Sun, Apr 24, 2011 at 5:55 AM, Muhammad Ali <span dir="ltr"><<a href="mailto:ali_i31@yahoo.com">ali_i31@yahoo.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<table border="0" cellpadding="0" cellspacing="0"><tbody><tr><td style="font: inherit;" valign="top">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><<a href="mailto:stotaro@asteriskhelpdesk.com" target="_blank">stotaro@asteriskhelpdesk.com</a>></i></b> wrote:<br><br></td></tr></tbody></table></blockquote>
</div><br>I am unsure of what you are saying. <br><br>All I know is that setting nat=yes has never failed me when nat=no has and we are talking countless phones and installs. <br><br>In the OSI reference model, the "Network" is layer 3, IP.<br>
<br>Call it Network, layer 3, or IP, it is the same.<br><br>nat=yes breaks the RFC due to NAT but it gets people talking. My customers don't really care for things that don't work. <br><br>Thanks,<br>Steve Totaro<br>