Interactive Connectivity Establishment (Ice) - Polycom RealPresence 4000 Administrator's Manual

Polycom® RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator's Guide

Interactive Connectivity Establishment (ICE)

Interactive Connectivity Establishment (ICE) provides a structure/protocol to unify the
various NAT Traversal techniques that are used to cross firewalls.
It enables SIP based endpoints to connect while traversing a variety of firewalls that may
exist between the calling endpoint (local) and the MCU or called endpoint (remote). It is the
only way for remote Microsoft Office Communicator/Lync users to call into the enterprise
without a VPN.
ICE Guidelines
•
•
•
•
When ICE over UDP is blocked in the firewall UDP port, the ICE connection through the TCP
protocol is automatically used instead of UDP for fallback.
•
•
•
•
Connecting to the RMX in ICE Environment
The dialing methods that can be used by an endpoint to connect to another endpoint
depends on the ICE environment: Local, Remote or Federation.
Figure H-2
Local connection - a connection between the RMX and endpoints that reside within the same
organization. For example, an endpoint in Zone A calls the RMX in Zone A.
Branch Office - a connection between an endpoint that is behind a firewall and the RMX that
reside in the same zone. The user in the Branch Office can also place and receive calls from
other enterprises and remote users. For example, Enterprise A also contains a branch office,
which in this example is a Polycom HDX user who is behind more than one firewall.
H-4
Collaboration Server ICE implementation complies with Microsoft ICE
implementation.
ICE is available only in IPv4 environment.
ICE can be implemented in an environment that includes a STUN server and a Relay
server (for example, Microsoft AV Edge server).
The firewall must be UDP enabled.
The RMX must have a unique account in the Active Directory and must be registered
with the Office Communications/Lync server.
From Version 7.8, ICE is supported with RMX Multiple Networks.
Ensure that the RMX system SIP signaling domain has been allowed on the Lync Server
edge server to which you are federating (if your deployment does not include a DMA
system).
Content sharing (BFCP protocol) is not supported in ICE environment.
ICE Environment
Polycom, Inc.