Mcu Resource Management By Realpresence Resource Manager Xma), Polycom Cma And Polycom Dma - Polycom RealPresence 4000 Administrator's Manual

MCU Resource Management by RealPresence Resource Manager (XMA),
Polycom CMA and Polycom DMA
When the RealPresence Resource Manager (XMA), Polycom CMA and Polycom DMA are
part of the solution, following a request by the RealPresence Resource Manager (XMA),
Polycom CMA or Polycom DMA, the MCU will send updates on resource usage to both
CMA and DMA, with each application updating its own resource usage for the MCU. This
provides better management of the RMX resources by the RealPresence Resource Manager
(XMA), Polycom CMA and Polycom DMA.
Guidelines
•
•
•
•
•
•
•
Port Usage Threshold
The RMX can be set to alert the administrator to potential port capacity shortages. A
capacity usage threshold can be set as a percentage of the total number of licensed ports in
the system.
When the threshold is exceeded, a System Alert is generated.
The default port capacity usage threshold is 80%.
The administrator can monitor the MCU's port capacity usage via the Port Gauges in the
Status Bar of the RMX Web Client.
Polycom, Inc.
Resource usage updates from RMX to the CMA and DMA are supported only with
RMXs with MPM+ or MPMx cards.
Both Flexible Resource Capacity™ and Fixed Resource Capacity™ modes are supported
with DMA.
Only Flexible Resource Capacity™ mode is supported with CMA.
Following requests sent by CMA and DMA, the RMX will send the number of occupied
resources for a conference or total for the MCU, according the Resource Capacity Mode
used by the system.
— In Flexible Resource Capacity Mode, CMA/DMA receive information about how many
Video (CIF) and Audio resources are occupied per conference or MCU according the
request type sent by the CMA and DMA.
In Fixed Resource Capacity™ Mode, DMA receives information about the number of
—
occupied resources per resource type (Audio Only, CIF, SD, HD 720p, HD 1080p)
and per conference or MCU according the request type sent by the DMA.
Occupied resources are resources that are connected to ongoing conferences.
Disconnected endpoints in an ongoing conference are not counted as occupied
resources.
An ongoing conference that does not include participants and the Send Content to Legacy
Endpoints option is disabled does not occupy resources. If the Send Content to Legacy
Endpoints option is enabled, the conference occupies one SD resource.
The RMX is unaware of the resource usage split between the CMA and DMA.
Chapter 21-RMX Administration and Utilities
21-23