Robert, Why this last reset of the ATA made a difference I do not yet know - but as of now it is working as we would expect.
Thank you for your time and help. -Max On Mon, Feb 22, 2010 at 1:15 PM, Robert Joly <[email protected]> wrote: >> Here's the registration for a Phone and the ATA. I'm going to >> peak in the Linksys configuration for SIP configuration. >> >> sip:[email protected] <sip:[email protected];x-sipX-nonat> 2214 > > So, this device (presumably the phone) , if a remote device, has some kind of > STUN or ALG in the picture. > >> sip:[email protected] >> <sip:[email protected]:15060;x-sipX-privcontact=192.168.15.101> >> 771 > > This device, presumably the ATA, does not have STUN or ALG, so it should be > capable of receiving incoming calls. If that is not the case, could you > please send me a network capture of the problem? > > You can initiate a network capture but from the shell of your sipXecs box > with the following command: tcpdump -n -nn -s 0 -i any -w net.cap > > While you have tcpdump running, reboot your ATA and once fully up, try to > call it. Once this is done Press ctrl-c to stop tcpdump and e-mail me > directly net.cap along with a brief description of your observations. > > > > >> >> Thanks, >> Max >> >> On Mon, Feb 22, 2010 at 1:05 PM, Robert Joly <[email protected]> wrote: >> >> 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/
