HomeProducts & ServiceCalling FeaturesCost ComparisonsInternational RatesWhat is VoIPSign Up Online
Contact us
                800.594.3670

Unlock Those Telephone Company Handcuffs

From: Cory Andrews  Published on July 29, 2008 at 10:01 am

   Can you explain how to set SIP ports on modern popular hardware phones such as the medium priced (or are they entry level these days) Sipura/Linksys/Cisco line? Why would you not use 5060? If you have several phones behind NAT on the same LAN, is there a logical way to set these? How does the other endpoint see this?

   Part of the problem with NAT is that there are several competing mechanisms for negotiating it, and the industry cannot seem to get behind a single, unified methodology. Until this happens, dealing with NAT will likely continue to be a pain in the butt.

STUN, ICE and TURN are three examples of solutions to issues inherent with SIP + NAT. STUN is not 100% reliable depending on the type of NAT you are dealing with. ICE builds upon STUN by allowing the device to use a range of ports and STUN techniques. However, ICE is not well supported. Media relay solutions like TURN can cause latency/QoS issues with VoIP, and are generally difficult to scale.

If you are behind NAT, you can set up port forwarding on your router/firewall to allow VoIP traffic to pass through. For SIP, use ports 5060 to 5070. For RTP audio, use port 8766 to 35000.

When configuring Linksys devices behind NAT, there are a few things you want to be particular about. In the configuration UI, make sure you have the following options set:

STUN Enable: yes
STUN Server: STUN.xten.com
NAT Mapping Enable: yes

Double check the NAT Keep Alive Interval setting on your phone and make sure it is set to a low value, ideally around 10-15 seconds.