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.

<strong>Polycom</strong> <strong>RMX</strong> 1500/<strong>2000</strong>/4000 Administrator’s <strong>Guide</strong><br />

For example, if company B wants to set up federation with company A and receive and send<br />

SIP calls that will be handled by the <strong>Polycom</strong> SIP signaling domain in company A, you need<br />

to add the FQDN of the company A Office Communications Server domain as well as the<br />

SIP signaling domain of company A to the list of Internal SIP Server domains supported by<br />

the company B Office Communications Server environment.<br />

For more information, see the Microsoft documentation and the Visual Communications<br />

Deployment Administration <strong>Guide</strong>.<br />

Configuring the Office Communications Server for <strong>RMX</strong> Systems<br />

To be able to work with the Office Communications Server, the <strong>RMX</strong> unit must be<br />

configured as a Trusted Host in the OCS. This is done by defining the IP address of the<br />

signaling host of each <strong>RMX</strong> unit as Trusted Host.<br />

Meeting Rooms are usually not registered to the OCS, and Static Routes are used instead.<br />

Setting Static Routes in the OCS enables SIP entities / UAs to connect to conferences<br />

without explicit registration of conferences with the OCS.<br />

Routing is performed by the OCS based on the comparison between the received URI and<br />

the provisioned static route pattern. If a match is found, the request is forwarded to the next<br />

hop according to the defined hop’s address.<br />

This is the recommended working method. It alleviates the need to create a user account in<br />

the OCS for each Meeting Room and Entry Queue. This also allows users to join ongoing<br />

conferences hosted on the MCU without registering all these conferences with OCS.<br />

Entry Queues can also be for Ad-hoc conferencing enabling Office Communicator clients to<br />

dial to the Entry Queue and create a new ongoing conference using DTMF codes to enter the<br />

target conference ID. In such a case, other OC users will have to use that ID to join the newly<br />

created conference.<br />

Setting the Trusted Host for <strong>RMX</strong> in the Office Communications Server<br />

To set the <strong>RMX</strong> as trusted in OCS:<br />

1 Open the OCS Management application.<br />

2 Expand the Enterprise Pools list.<br />

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

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

Saved successfully!

Ooh no, something went wrong!