MCUs

MCU Management

 

 

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 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.

The following table describes the fields in the list (the View Details command lets you see this information in a more readable form for the selected MCU).

Table 6-1Information in the MCU list

 

Column

Description

 

 

 

 

 

 

Connection and service status and capabilities:

 

 

Connected

Disconnected

 

 

Connected securely (encrypted connection)

 

 

In service

Out of service

 

 

Busied out

Not licensed

 

 

Supports conference recording

 

 

Doesn’t support conference recording

 

 

Supports shared number dialing IVR service

 

 

Functions as a gateway

 

 

Supports SVC conferences

 

 

(see “SVC Conferencing Support” on page 4)

 

 

Warning

 

 

 

Hover over an icon to see the associated status message.

 

 

 

 

 

Name

The name of the MCU.

 

 

 

 

 

 

Model

The type of MCU.

 

 

 

 

 

Version

The version of software on the MCU.

 

 

 

 

Polycom, Inc.

 

133

Page 145
Image 145
Polycom 3725-76302-001LI manual Column Description, See SVC Conferencing Support on