Filter
Top Products
DMA Operations Guide MCUs
120 Polycom, Inc.
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 137 and “MCU Pool Orders” on page 141.
Note
If you have a Polycom RealPresence Resource Manager system that uses 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 directly schedule
conferences on MCUs that it manages, those MCUs should not be part of the
conferencing resources (MCU pools) available to the DMA system.
Note
MCU pools and pool orders are not used to select an ISDN gateway for simplified
gateway dialing. See “ISDN Gateway Selection Process” on page 133.
Note
For H.323 calls to a conference room (virtual meeting room, or VMR), the Polycom
DMA system can only do bandwidth management if the MCU hosting the
conference room is registered with it (in a supercluster, with any cluster). If the MCU
is unregistered, or is registered to another gatekeeper (not part of the supercluster),
the bandwidth for the call is not counted for bandwidth management, site statistics,
or the network usage report.
In a SIP signaling environment, in order for a Polycom RMX MCU to register with
the Polycom DMA system’s Call Server, two system flags on the MCU must be set
properly:
• Set the MS_ENVIRONMENT flag to NO.
• Make sure the SIP_REGISTER_ONLY_ONCE flag is set to NO or not present.
In order for the Polycom DMA system to assign an alternate gatekeeper to an MCU,
that MCU must be in a site that belongs to a territory which has a backup Polycom
DMA system assigned to it.