Filter
Top Products
MCU Management
Polycom, Inc. 130
The following table describes the fields in the dialog box.
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: 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 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: Resource Usage Reporting
The RealPresence DMA system reports port numbers based on resource usage for CIF calls. Version
8.1 and later Polycom MCUs report port numbers based on resource usage for HD720p30 calls. In
general, 3 CIF = 1 HD720p30, but it varies depending on bridge/card type and other factors.
See your Polycom RealPresence Collaboration Server or RMX system documentation for more
detailed information about resource usage.
Field Description
External MCU
Name Name for the MCU (up to 32 characters; must not include any of the following:
, " ; ? : = *).
Type Lists the types of MCUs the system supports. Must be set to the correct MCU
type in order for the RealPresence DMA system to be able to connect to it.
For an MGC MCU, this must be set to Polycom MGC gateway, even if it’s
being used as a standalone MCU.
Management IP address Host name or IP address for logging into the MCU (to use it as a conferencing
resource).
Note: Polycom MCUs don't include their management IP address in the
Subject Alternate Name (SAN) field of the CSR (Certificate Signing Request),
so their certificates identify them only by the Common Name (CN). Therefore
if Skip certificate validation for server connecting is off (see Security
Settings on page 50), the MCU's management interface must be identified by
the name specified in the CN field (usually the FQDN), not by IP address.