On Thu, Apr 21, 2011 at 5:42 AM, Alexandru Oniciuc < alexandru.onic...@trivenet.it> wrote:
> Dear * users, > > > > in your opinion, when using a * as a public server, is good practice > enabling nat=yes in sip.conf for all the peers? > > Can anyone imagine a scenario when enabling this parameter (even for peers > that don’t require it) can cause problems? > > > > Regards and thanks in advance, > > Alex > > > > 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. I use nat=yes all the time and it works just fine. http://www.mail-archive.com/asterisk-users@lists.digium.com/msg213941.html Nobody actually answered the question about the bad side, they just argued about the SIP RFC. Many others agreed to make it default behavior and that setting nat=yes gives a an extra degree of security. RFCs are great and all, but in the real world, phones just need to work. Thanks, Steve Totaro
-- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
