Generally, you need to enable the remote NAT traversal feature when at least one of these conditions is true:
1- Your sipXecs has a private IP address and is deployed behind a NAT; AND/OR 2- At least one phone is deployed behind a remote NAT (e.g. home user, remote branch office, ...) The remote NAT traversal can help overcome the NATs found in the conditions enumerated above. It can be configured by following the 6 steps described in http://sipx-wiki.calivia.com/index.php/Configuring_remote_workers_cheats heet > -----Original Message----- > From: sipx-users-boun...@list.sipfoundry.org > [mailto:sipx-users-boun...@list.sipfoundry.org] On Behalf Of > Burden, Mike > Sent: Tuesday, December 08, 2009 8:32 AM > To: Todd Hodgen; sipx-users@list.sipfoundry.org > Subject: Re: [sipx-users] How to set up a non-NAT'd sipXecs > IP PBXwithoutgiving public addresses to the phones > > Getting from a host on a public IP to a host on a private IP > does not necessarily require NAT, just a static route. > > The sipXecs server could be at a public IP on a DMZ, and the > phones could be on a subnet with private addresses attached > to that DMZ via a router. > NAT may or may not be enabled at that router. > > > +----------+ > | Internet | > +----------+ > | > Firewall > | > +---DMZ----+ > | sipXecs | Public IP Address > +----------+ > | > Router (If the phones don't require Internet access, then > NAT is not required here) > | > +-Phone Subnet-+ > | Phones | Private IP Addresses > +--------------+ > > > > Mike Burden > Lynk Systems, Inc > e-mail: m...@lynk.com > Phone: 616-532-4985 > > > > > > > > > -----Original Message----- > From: Todd Hodgen [mailto:thod...@verizon.net] > Sent: Monday, December 07, 2009 4:35 PM > To: Burden, Mike; sipx-users@list.sipfoundry.org > Subject: RE: [sipx-users] How to set up a non-NAT'd sipXecs > IP PBX withoutgiving public addresses to the phones > > If the Server is on a Public Address, and the phones are on > NAT addresses, how would they get to server without going > through a router to get onto the same network as the server? > That is where your Nat will come in - traversing the router. > Seems the Server would need to know they are NAT, as > it will be NAT coming to the server. > > > > -----Original Message----- > From: sipx-users-boun...@list.sipfoundry.org > [mailto:sipx-users-boun...@list.sipfoundry.org] On Behalf Of > Burden, Mike > Sent: Monday, December 07, 2009 1:25 PM > To: sipx-users@list.sipfoundry.org > Subject: [sipx-users] How to set up a non-NAT'd sipXecs IP > PBX without giving public addresses to the phones > > I asked this once before, but maybe not in precise terms... > > Given that sipXecs cannot be dual-homed, if the sipXecs > server is given a public IP address, does it create issues to > have the phones behind NAT? > > If so, then do the phones need non-NAT access to the ITSP, or > just non-NAT access to the sipXecs server? > > > Mike Burden > Lynk Systems, Inc > e-mail: m...@lynk.com > Phone: 616-532-4985 > > _______________________________________________ > sipx-users mailing list sipx-users@list.sipfoundry.org List > Archive: http://list.sipfoundry.org/archive/sipx-users > Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users > sipXecs IP PBX -- http://www.sipfoundry.org/ > > _______________________________________________ > sipx-users mailing list sipx-users@list.sipfoundry.org List > Archive: http://list.sipfoundry.org/archive/sipx-users > Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users > sipXecs IP PBX -- http://www.sipfoundry.org/ > _______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/
