Filter
Top Products
MCU Management
Polycom, Inc. 125
Note: MCUs and ISDN Gateway Selection
MCU pools and pool orders are not used to select an ISDN gateway for simplified gateway dialing.
See ISDN Gateway Selection Process on page 139.
When a Polycom RealPresence Collaboration Server or RMX MCU is functioning as an ISDN
gateway, each call through the gateway consumes two ports, one for the ISDN side and one for the
H.323 side. The ports used for gateway calls aren’t available for conferences, so gateway operations
may significantly reduce the available conferencing resources.
Note: MCU Support
The Polycom RealPresence DMA system supports the use of Cisco Codian 4200, 4500, and MSE
8000 series MCUs as part of the Conference Manager’s conferencing resource pool, but their Media
Port Reservation feature is not supported. This feature must be set to Disabled on Cisco Codian
MCUs in order to use them as part of the Conference Manager’s conferencing resource pool.
The Polycom RealPresence DMA system supports the use of Polycom MGC MCUs, but not as part of
the Conference Manager’s conferencing resource pool. They can register with the Call Server as
standalone MCUs (dialed by IP or prefix) and/or ISDN gateways. Their model designation is Polycom
MGC gateway, even if being used as standalone MCUs.
Note: MCU Connections
In order to efficiently manage multiple calls as quickly as possible, the Polycom RealPresence DMA
system uses multiple connections per MCU. By default, a RealPresence Collaboration Server or RMX
MCU allows up to 20 connections per user. We recommend not reducing this setting (the
MAX_NUMBER_OF_MANAGEMENT_SESSIONS_PER_USER system flag). If you have a
RealPresence DMA supercluster with three Conference Manager clusters and a busy conferencing
environment, we recommend increasing this value to 30.
Note: Bandwidth Management Requires MCU Registration
For H.323 calls to a conference room (virtual meeting room, or VMR), the RealPresence DMA system
can only do bandwidth management if the MCU is registered with it (in a supercluster, registered with
any cluster). If the MCU is unregistered or 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 RealPresence Collaboration Server or RMX
MCU to register with the RealPresence 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 RealPresence DMA system to assign an alternate gatekeeper to an MCU,
the MCU must be in a territory that has a backup RealPresence DMA system assigned to it.