> Robert, > > I removed the STUN configuration from the ATA and reset the device. > The behavior is the same.
What about the Linksys router, any SIP ALG lurking in there? Can you go in sipXconfig under diagnostics->Registrations and tell me what the registration contact looks like for your ATA? Basically, if you see a 'sipx-nonat' in there, a SIP ALG in the router or a STUN client in you ATA is at work. > > -Max > > On Mon, Feb 22, 2010 at 12:36 PM, Robert Joly <[email protected]> wrote: > >> Hello, > >> > >> I have a sipx server running on a statically assigned public ip > >> address. I need to support far end NAT for remote users > (ATAs behind > >> a home firewall). I have a Grandstream HT 286 that we are > >> experimenting with. Initially I connected the ATA to our > office DHCP > >> network, autoconfigured the device from the config server > (tftp) and > >> everything works fine. Moving the ATA behind a linksys router and > >> receiving a DHCP assigned NAT'd address the device can > still connect > >> to tftp, register with sipx, make outbound calls to the PSTN and > >> internal extensions, but cannot receive calls from internal > >> extensions. > >> > >> Servers -> <server> -> NAT -> Use STUN System -> Internet > Calling -> > >> NAT Traversal -> Enable NAT Traversal > >> > >> <phone> -> SIP -> STUN Server -> "stun01.sipphone.com" > > > > The recommendation is to disable any NAT traversal technologies in > > routers and endpoints including STUN and SIP ALGs. Please > be sure to > > disable such things in your ATA and Linksys and retry. > > > _______________________________________________ sipx-users mailing list [email protected] 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/
