> Are there any special phone settings for a remote polycom > handset to register appropriately? I say this because I see > the registration showing the remote public ip address from > the ISP but not announcing itself as being being NAT. Is this correct?
This indicates that some device is trying to do NAT compensation for SIP before the packet arrives at the sipXecs. In almost 100% of the cases, NAT compensation is not done completely and some scenarios will fail. Therefore it is strongly recommended to turn off all NAT compensation for SIP in the network and let sipXecs do all the work. Check the following: 1- Make sure you have STUN disabled on your Polycom phone 2- If the router in front of your phone has a SIP ALG, turn it off. BTW, NetGear calls this feature 'SPI' or stateful packet inspection 3- If the router in front of your sipXecs has a SIP ALG, turn it off. 4- If none of the above apply, it may be that your ISP has equipment that is trying to do NAT compensation. I believe I have seen this once with an ISP in the UK that also offered SIP services. Seems like their SBC's touched the SIP packets even though that person was not subscribed to the SIP service. _______________________________________________ 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/
