Filter
Top Products
Appendix H-Setting the RMX for Integration Into Microsoft OCS Environment
H-2
For a detailed description of the configuration of the Polycom
conferencing entities for the integration in Microsoft Office
Communications Server 2007 see Polycom® HDX and RMX™ Systems
Integration with Microsoft Office Communications Server 2007 Deployment
Guide.
Configuring the OCS for RMX 2000/4000
Setting the Trusted Host and Static Route for RMX in the
OCS
To be able to work with the OCS, the RMX unit must be configured as a
Trusted Host in the OCS. This is done by defining the IP address of the
signaling host of each RMX unit as Trusted Host.
Meeting Rooms are usually not registered to the OCS, and Static Routes
are used instead. Setting Static Routes in the OCS enables SIP entities /
UAs to connect to conferences without explicit registration of conferences
with the OCS.
Routing is performed by the OCS based on the comparison between the
received URI and the provisioned static route pattern. If a match is found,
the request is forwarded to the next hop according to the defined hop’s
address.
This is the recommended working method. It alleviates the need to create
a user account in the OCS for each Meeting Room and Entry Queue. This
also allows users to join ongoing conferences hosted on the MCU without
registering all these conferences with OCS.
Entry Queues can also be for Ad-hoc conferencing enabling Office
Communicator clients to dial to the Entry Queue and create a new
ongoing conference using DTMF codes to enter the target conference ID.
In such a case, other OC users will have to use that ID to join the newly
created conference.
To set the RMX as trusted and define Static Routes in OCS:
1 Open the OCS Management application.