DMA OperationsGuide Set Up MCUs
30 Polycom, Inc.
Make sure that each MCU is in a site belonging to a territory for which the
Polycom DMA system is responsible. If you’re deploying a supercluster (see
“Configure the Call Server and Optionally Create a Supercluster” on page28
and “About Superclustering” on page227), 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 “Configure the Call Server and Optionally Create a
Supercluster” on page 28.
Standalone MCUs can register themselves to the Polycom DMA system’s Call
Server. To make an MCU available as a conferencing resource, either add it to
the appropriate Polycom 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 “MCU Management” on page131.
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.
Every conference room (VMR) is associated with an MCU pool order. The
pool(s) to which an MCU belongs, and the pool order(s) to which a pool
belongs, are used to determine which MCU is used to host a conference. See
“MCU Pools” on page 152 and “MCU Pool Orders” on page156 for
information about how to use pools and pool orders, as well as the rules that
the system uses to choose an MCU for a user.
The Polycom DMA system uses conference templates to define the
conferencing experience associated with a conference room or enterprise
group. You can create standalone templates (recommended), setting the
conferencing parameters directly in the Polycom DMA system, or link
templates to RMX conference profiles (see “Conference Templates” on
page1 95).
Note
If you have a Polycom RealPresence Resource Manager system that’s going to use
the DMA system API to schedule conferences on the DMA system’s conferencing
resources (MCU pools), you must create MCU pools and pool orders specifically for
the use of the RealPresence Resource Manager system. The pool orders should be
named in such a way that:
•They appear at the top of the pool order list presented in the RealPresence
Resource Manager system.
•Users of that system will understand that they should choose one of those pool
orders.
If the RealPresence Resource Manager system is also going to be used to directly
schedule conferences on MCUs, those MCUs should not be part of the
conferencing resources (MCU pools) available to the DMA system.