Filter
Top Products
Network Settings
4-32 41-001343-02 REV04 – 05.2014
Interactive Connectivity Establishment (ICE) Support
The phones now support the Interactive Connectivity Establishment (ICE) Protocol. ICE makes use of the Session Traver-
sal Utilities for NAT (STUN) protocol and its extension, Traversal Using Relay NAT (TURN).
In an ICE environment, two agent endpoints (or two phones communicating at different locations) are able to communi-
cate via the SIP Protocol by exchanging Session Description Protocol (SDP) messages. At the beginning of the ICE proc-
ess, the agents are ignorant of their own topologies. In particular, they might or might not be behind a NAT (or multiple
tiers of NATs).
ICE allows the agents to discover enough information about their topologies to potentially find one or more paths by
which they can communicate.
The ICE Protocol is automatically enabled if both STUN and TURN servers are configured in the network. The following
occurs when ICE is used on the phone:
• The TURN address/port is always used as the preferred media address in initial INVITES.
• Media is sent through the TURN server prior to the completion of the ICE connectivity check.
• A Re-INVITE is used to adjust media (if required) after the ICE connectivity check is complete.
• When ICE is enabled, call hold is performed via the send only attribute instead of changing the media address to
0.0.0.0.
• The ICE Protocol supports the RTCP SDP attribute (RFC 3605)
STUN and TURN can be enabled using the Aastra Web UI or the configuration files. This automatically enables ICE.
5. In the “TURN Server” field, enter the IP address and/or qualified domain name of the TURN server in your network. You can enter up to 2 val-
ues separated by a comma. The first value is the primary and the second value is the backup. For example:
10.50.103.12, turnbackup.aastra.com.
The TURN configuration is only used for media (RTP traffic) that goes through the server - not for signaling. (For signaling, you need to enable
Rport if the NAT device does not recognized SIP).
The TURN configuration applies globally to each phone.
If you configure both STUN and TURN on the phone, it discovers what type of NAT device is between the phone and the public network. If
the NAT device is full cone, restricted cone, or port restricted cone, the phone uses STUN. If the NAT device is symmetric, the phone uses
TURN. If you configure TURN only, the phone uses TURN with the NAT discovery process. TURN is compatible with all types of NAT devices
but can be costly since all traffic goes through a media relay (which can be slow, can exchange more messages, and requires the TURN server
to allocate bandwidth for calls).
Note:
The NAT IP configuration parameter takes precedence over the STUN and TURN parameters.
6. In the “TURN Port” field, enter the port number of the TURN server. You can enter up to 2 values separated by a comma. The first value is the
primary and the second value is the backup. For example:
3479,3480
Default is 3479. Range of values are 0 to 65535.
7. (Optional) In the “TURN User ID” field, enter the username that a user must enter when accessing an account on the TURN server. For exam-
ple, 0412919146.
Valid values are up to 63 alphanumeric characters.
8. (Optional) In the “TURN Password” field, enter the password that a user must enter when accessing an account on the TURN server. For
example, 42447208233b8b8b8a234.
Valid values are up to 63 alphanumeric characters.
9. Click Save Settings to save your changes.
Aastra Web UI