Setting Up Your System
91
the ICE approach to NAT traversal.
Manual NAT (Static NAT)
Manual NAT helps IP connections traverse NAT gateways without the third-party network server
(STUN/TURN server). If manual NAT feature is enabled, the configured public IP address and
port can be carried in the SIP requests or RTP packets, in which the other party obtains the
phone’s public address. It is useful to reduce the cost of the company’s network deployment.
STUN (Simple Traversal of UDP over NATs)
STUN is a network protocol, used in NAT traversal for applications of real-time voice, video,
messaging, and other interactive IP communications. The STUN protocol allows entities behind
a NAT to first discover the presence of a NAT and the type of NAT (for more information on the
NAT types, refer to NAT Types on page 90) and to obtain the mapped (public) IP address and
port number that the NAT has allocated for the UDP connections to remote parties. The
protocol requires assistance from a third-party network server (STUN server) usually located on
public Internet. The IP phone can be configured to act as a STUN client, to send exploratory
STUN messages to the STUN server. The STUN server uses those messages to determine the
public IP address and port used, and then informs the client.
Capturing packets after you enable the STUN feature, you can find that the IP phone sends
Binding Request to the STUN server, and then mapped IP address and port is placed in the
Binding Response: Binding Success Response MAPPED-ADDRESS: 59.61.92.59:19232.
STUN does not work if the NAT device is symmetric. This may be a drawback in many situations
as most enterprise-class firewalls are symmetric.
To Next Page
Loading...
Need help?
General
