Integrating The Rmx Into The Microsoft Office Communications Server Environment; Setting The Matched Uri Dialing Method - Polycom RMX 1500 Administrator's Manual

Integrating the RMX into the Microsoft Office Communications
Server Environment
When the RMX is integrated into the Office Communications Server environment, calls to
conferences running on the RMX can be routed using Matched URI dialing and/or
Numerical dialing.
Both routing methods (numerical dialing and Matched URI dialing) can be enabled
simultaneously in the Office Communications Server and the RMX system or you can
enable one of these methods, depending on your environment requirements.
In both methods, the RMX configuration is the same.

Setting the Matched URI Dialing Method

To enable the Matched URI dialing method the following tasks have to be completed:
Office Communications Server side:
1
2
RMX side:
The following tasks are detailed in "Configuring the RMX 1500/2000/4000 for Microsoft
Integration" on page H-34.
3
4
5
6
7
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.
Polycom, Inc.
Set the Static Route & Trusted Host for RMX in the Office Communications Server.
Optional if Load Balancer Server is present. Set the Static Route & Trusted Host for
RMX in the Load Balancer server.
Modify the Management Network Service to include the DNS server and set the
Transport Type to TLS.
Create the security certificate (using one of the two available methods)
Define a SIP Network Service in the RMX and install the TLS certificate.
Modify and add the required system flags in the RMX System Configuration.
Optional. Defining additional Entry Queues and Meeting Rooms in the RMX
environment. For more information see "Defining a New Entry Queue" on page 5-3 and
"Creating a New Meeting Room" on page 4-4.
Appendix H-Setting the RMX for Integration Into Microsoft Environment
H-5