19.08.2013 Views

RMX 2000 Administrator's Guide Version 7.6.1 - Polycom

RMX 2000 Administrator's Guide Version 7.6.1 - Polycom

RMX 2000 Administrator's Guide Version 7.6.1 - Polycom

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Interactive Connectivity Establishment (ICE)<br />

Appendix H-Setting the <strong>RMX</strong> for Integration Into Microsoft Environment<br />

Interactive Connectivity Establishment (ICE) provides a structure/protocol to unify the<br />

various NAT Traversal techniques that are used to cross firewalls.<br />

It enables SIP based endpoints to connect while traversing a variety of firewalls that may<br />

exist between the calling endpoint (local) and the MCU or called endpoint (remote). It is the<br />

only way for remote Microsoft Office Communicator/Lync users to call into the enterprise<br />

without a VPN.<br />

ICE <strong>Guide</strong>lines<br />

• ICE is available in MPM+ Card Configuration Mode (<strong>Version</strong> 7.0 and later) and MPMx<br />

Card Configuration Mode (<strong>Version</strong> 7.1 and later).<br />

• <strong>RMX</strong> ICE implementation complies with Microsoft ICE implementation.<br />

• ICE is available only in IPv4 environment.<br />

• ICE can be implemented in an environment that includes a STUN server and a Relay<br />

server (for example, Microsoft AV Edge server).<br />

• The firewall must be UDP enabled.<br />

• The <strong>RMX</strong> must have a unique account in the Active Directory and must be registered<br />

with the Office Communications/Lync server.<br />

• ICE is supported only within a single IP Network Service per <strong>RMX</strong> and not in Multiple<br />

Networks configuration.<br />

• Ensure that the <strong>RMX</strong> system SIP signaling domain has been allowed on the Lync Server<br />

edge server to which you are federating (if your deployment does not include a DMA<br />

system).<br />

• Content sharing (BFCP protocol) is not supported in ICE environment.<br />

Connecting to the <strong>RMX</strong> in ICE Environment<br />

The dialing methods that can be used by an endpoint to connect to another endpoint<br />

depends on the ICE environment: Local, Remote or Federation.<br />

Figure 9 ICE Environment<br />

Local connection - a connection between the <strong>RMX</strong> and endpoints that reside within the same<br />

organization. For example, an endpoint in Zone A calls the <strong>RMX</strong> in Zone A.<br />

Branch Office - a connection between an endpoint that is behind a firewall and the <strong>RMX</strong> that<br />

reside in the same zone. The user in the Branch Office can also place and receive calls from<br />

other enterprises and remote users. For example, Enterprise A also contains a branch office,<br />

which in this example is a <strong>Polycom</strong> HDX user who is behind more than one firewall.<br />

<strong>Polycom</strong>, Inc. H-3

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!