On 2/9/2012 7:43 AM, Tony Graziano wrote: > If your firewall is configured correctly, why would NAT be set to YES. > Normally it would be set to NO if sipXbridge is in use and advertising > a public IP address (behind NAT). It has always been suggested to have > the provider DISABLE or TURN OFF NAT when using sipxbridge. In the > instances where it does not work for someone, I have always found the > outbound NAT type and/or STATIC port nat were not set properly before > creating the NAT entries, creating a dependency on NAT=YES at the > ITSP. This could potentially lead to the alarms? I never have them, so > I'm just saying... I hear you, and technically you are correct. I have tried everything. In my experience there was a case where 2 separate accounts/locations could not register. The accounts had worked perfectly for months. Nothing changed. After much testing and tweaking, simply switching to NAT=yes made the accounts come back up. IMO something had changed at voip.ms. Anyway it works. And I am sure it works both ways, I just lean to setting it to Yes now.
-- Regards -------------------------------------- Gerald Drouillard Technology Architect Drouillard& Associates, Inc. http://www.Drouillard.biz _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
