Appendix H-Setting the MCU for Integration Into Microsoft Environment
Polycom, Inc. H-13
• Establishing a Voice Route to the MCU “Voice” Gateway - The Voice Route to the MCU
(or DMA) must be configured in the OCS infrastructure.
• Configure Office Communicator Users for Enterprise Voice.
MCU side:
The following tasks are detailed in "Configuring the RMX 1500/2000/4000 for Microsoft
Integration” on page H-36.
1 Modify the Management Network Service to include the DNS server and set the
Transport Type to TLS.
2 Create the security certificate (using one of the two available methods)
3 Define a SIP Network Service in the MCU and install the TLS certificate.
4 Modify and add the required system flags in the MCU System Configuration.
5 Optional. Defining additional Entry Queues and Meeting Rooms in the MCU
environment. For details see "Meeting Rooms” on page 6-1 and "Entry Queues” on
page 7-1.
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
MCU™ Systems Integration with Microsoft Office Communications Server 2007 Deployment
Guide.
Optional. Removing the MCU from the Host Authorization List
If you have defined the MCU as Trusted Host to enable dialing using the Static Routes and
you want to use numerical dialing in addition or instead of SIP URI dialing, you need to
remove the current definition of the MCU and redefine it as a voice gateway.
To remove the definition of the MCU as trusted host from the Front End Properties:
1 In the OCS application, display the Front End Properties (right-click the Front End and
select Properties).
2 Click the Host Authorization tab.
If the MCU was previously defined as a Trusted Host for matching URI dialing method, this definition
must be removed before configuring the MCU as a voice gateway. It will be defined as trusted host
as part of the voice gateway configuration. For more details, see Optional. Removing the MCU from
the Host Authorization List.