Configuring The Office Communications Server For Rmx Systems - Polycom RMX 1500 Administrator's Manual

Appendix H-Setting the RMX for Integration Into Microsoft Environment
H-8
For a detailed description of the configuration of the Polycom
conferencing components for the integration in Microsoft Office
Communications Server 2007 see Polycom® HDX and RMX™ Systems
Integration with Microsoft Office Communications Server 2007 Deployment
Guide.
In ICE environment, to enable the Matched URI dialing in the federated
environment to be able to connect to the RMX SIP signaling domain, you
must also configure the Office Communications Server. When federating
an Office Communications Server edge server with another Office
Communications Server environment, you need to include the FQDN of
the Office Communications Server edge server as well as the SIP signaling
domain for federated environment. The SIP signaling domain is the
FQDN of the Polycom DMA system or a Polycom RMX system (when
your deployment does not include a DMA system).
For example, if company B wants to set up federation with company A
and receive and send SIP calls that will be handled by the Polycom SIP
signaling domain in company A, you need to add the FQDN of the
company A Office Communications Server domain as well as the SIP
signaling domain of company A to the list of Internal SIP Server domains
supported by the company B Office Communications Server
environment.
For more information, see the Microsoft documentation and the Visual
Communications Deployment Administration Guide.
Configuring the Office Communications Server for
RMX Systems
To be able to work with the Office Communications Server, 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.