Polycom 7000 User Manual

Page of 437
 
Polycom RealPresence DMA System Initial Configuration Summary
Polycom, Inc. 
33
 
Obtain and install a security certificate from a trusted certificate authority. See 
 and 
Configure as needed various login policy settings (see 
) and optionally, a 
management access whitelist (see 
). 
Document your current configuration for comparison in the future. We recommend saving screen 
captures of all the configuration pages. 
Manually create a backup, download it, and store it in a safe place. See 
Set Up MCUs
Make sure your MCUs are configured to accept encrypted (HTTPS) management connections (required for 
maximum or high security mode). 
Make sure that each MCU is in a site belonging to a territory for which the Polycom RealPresence DMA 
system is responsible. If you’re deploying a supercluster (see 
 and 
), make sure that each territory has a primary and backup 
cluster assigned to it. If the primary cluster becomes unavailable, the MCUs registered to it can re-register 
to the backup. 
If you’re deploying a supercluster, verify that you’ve enabled the hosting of conference rooms in the right 
territories and assigned clusters to those territories. See 
Standalone MCUs can register themselves to the Polycom RealPresence DMA system’s Call Server. To 
make an MCU available as a conferencing resource, either add it to the appropriate Polycom RealPresence 
DMA cluster’s Conference Manager manually or, if it’s already registered with the Call Server, edit its entry 
to enable it for conference rooms and provide the additional configuration information required. See 
You must organize MCUs configured as conferencing resources into one or more MCU pools (logical 
groupings of media servers). Then, you can define one or more MCU pool orders that specify the order of 
preference in which MCU pools are used. 
Note: MCUs and RealPresence DMA system interaction
The Polycom RealPresence DMA system can interact with MCUs, or media servers, in either or both 
of the following two ways: 
MCUs may be made available to system’s Conference Manager to manage for multi-point 
conferencing (hosting virtual meeting rooms, or VMRs). 
MCUs may be registered with the system’s Call Server as standalone MCUs and/or gateways. 
This configuration summary assumes you want to do both.