> I'm trying to test the remote worker feature of the latest build. > > However, when the remote phone register with SipX it looks > like it is not detected as a NAT device from the registration > line "transport=udp;x-sipX-nonat"
This indicates that the phone does not appear to be behind a remote NAT from the point of view of sipXecs. There are usually two explanations for this: 1- the phone truly isn't behind a remote NAT from the POV of sipXecs -or- 2- the phone is indeed behind a remote NAT but has STUN enabled so that it appears as a phone with a public IP address. The recommendation when using the sipXecs-resident NAT traversal is to disable any STUN/TURN/ICE on remote phones and disable SIP ALGs in remote NATs/Firewalls. > > Now, the phone has nat enabled and has the public ip address > of itself in the registration. So it does register and audio > comes from the Sipx box. But no audio from the phone goes to > sipx. It's trying to send media to the sipx server internal address. So that likely points to a configuration error. Please verify the following: 1- Under System->Internet Calling: verify that the Intranet domains and Intranet Subnets accurately describe the private network that sipXecs is a part of. 2- Under System->Internet Calling->NAT Traversal, make sure that the Public IP Address and External Address are set to the WAN-facing IP address of the NAT/Firewall fronting the private network that sipXecs is in. 3- Make sure to open pinholes and port forwarding rules on the NAT/Firewall to route TCP/UDP port 5060 to sipXecs. Do the same for UDP ports 3000 to 30500 which are used for media traffic. Let me know if that improves things for you. > _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
