> > Yes I observed x-sipx-nonat of remote worker in the contact > of registration menu. Let me check the settings of STUN/ICE > of remote worker. Do I also need to turn off STUN/ICE of > called party as well ?
The remote NAT traversal feature is a complete end-to-end one and does not require any outside assistance from STUN/ICE or SIP ALGs. In fact, in the case of SIP ALGs, 9 times out of 10, their implementation is not fully standards compliant and breaks the interop between the remote phone and sipXecs. As a result, using things like STUN/ICE and SIP ALGs on top of the sipXecs NAT traversal feature usually breaks things. So, the morale of the story is that if you choose to rely on sipXecs solving your NAT traversal issues, please disable any other NAT traversal features in your deployment. > > -----Original Message----- > From: Robert Joly [mailto:[email protected]] > Sent: Monday, July 20, 2009 10:27 PM > To: jun,wen; [email protected] > Subject: RE: [sipx-users] Remote worker cannot call to second > intranet subnets > > Ok, next thing to check then is whether or not there is some > SIP-aware equipment at the remote worker site. The simplest > way to tell is to check the registration of the remote user under > Diagnostics->Registrations. If you see a X-sipX-nonat in the contact, > this indicates that the phone or remote firewall is trying to > do NAT compensation - turn off STUN/ICE at the remote worker > phone and disable SIP ALGs in the remote firewall. > > If instead you see X-sipX-privcontact then the problem is > something else and I'll need a snapshot of your system with > sipXproxy logging turned all the way up to 'DEBUG' to put my > finger on it. > > > -----Original Message----- > > From: jun,wen [mailto:[email protected]] > > Sent: Monday, July 20, 2009 10:20 AM > > To: Joly, Robert (CAR:9D30); [email protected] > > Subject: RE: [sipx-users] Remote worker cannot call to > second intranet > > subnets > > > > Yes all of my three intranet subnets, 192.168.2.0/24, > > 192.168.8.0/24 and 192.168.10.0/24, were already set in the > "Intranet > > Calling". > > > > -----Original Message----- > > From: Robert Joly [mailto:[email protected]] > > Sent: Monday, July 20, 2009 9:57 PM > > To: jun,wen; [email protected] > > Subject: RE: [sipx-users] Remote worker cannot call to > second intranet > > subnets > > > > Please make sure that your 192.168.8.0/24 and > 192.168.10.0/24 appear > > in your intranet subnet list under System->Intranet > Calling. The rule > > of thumb here is that the Intranet Subnets section should > contain all > > the subnets that describe your intranet. > > > > > > > > Hi, I have three intranet subnets by a central site with > sipx server > > > (192.168.2.0/24 ) and two of branch sites (192.168.8.0/24 and > > > 192.168.10.0/24) with VPN tunnel interconnections of > hub-and-spoke. > > > > > > The sip phones inside these three intranet subnets can > make call to > > > each other without problem, and the remote worker also can > > make call > > > to the sip phone inside the subnet of sipx server. > > > > > > Whereas, when the remote worker calls to the sip phone inside the > > > second/third intranets, the called party rings but has > only one-way > > > audio from remote work to called party. > > > > > > Is there anything related to the sipXbridge settings ? > > > > > > Regards, > > > > > > Jun > > > > > > _______________________________________________ > > > 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/ > > > > > > > > > _______________________________________________ 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/
