MCU Management
Polycom, Inc. 148
MCU has IVR service required by user’s conference template.
MCU has recording capability required by user’s conference template.
If there are multiple MCUs that are equally capable, select the least used, as determined by the
following formula:
port_availability = (free_video_ports / total_video_ports) + (0.0001 *
free_audio_ports / total_audio_ports)
mixer_availability = (total_video_ports - 2 * active_dma_conferences) /
total_video_ports + 0.0001 * (total_audio_ports - 2 * active_dma_conferences) /
total_audio_ports
availability = min (port_availability, mixer_availability)
4 If no MCUs in the selected MCU pool have capacity, select the next MCU pool in the pool order and
return to step 3.
5 If no MCUs are available in any of the MCU pools in the pool order:
If fallback is enabled, select the best MCU available to the Polycom RealPresence DMA system,
based on the system’s capability algorithm.
If fallback is not enabled, reject the call.
See also:
MCU Pool Orders on page 145
MCU Pool Order Procedures on page 150
MCU Availability and Reliability Tracking
In order to minimize the number of failed calls, the Polycom RealPresence DMA system employs
mechanisms for detecting and handling MCU availability and reliability issues:
● If it can’t reach an MCU’s management interface, the RealPresence DMA system won’t route calls to
that MCU.
● If an MCU reports zero capacity via its management interface, the RealPresence DMA system won’t
route calls to that MCU.
Note: Certain Conference Options Affect MCU Selection
• On the Admin > Conference Manager > Conference Settings page, when the MCU Selection
field is set to Prefer MCU in first caller's site, the system will match the MCU chosen for the call
with the site that the first caller’s endpoint belongs to.
• On the Admin > Conference Manager > Conference Templates page, under the Add/Edit
Conference template > RMX General Settings dialog, the Cascade for Size option enables
conferences using this template to span Polycom MCUs to achieve conference sizes larger than a
single MCU can accommodate.
If Cascade for Size is enabled and the MCU Selection field is set to Prefer MCU in first caller's
site, the rules for Cascade for size take precedence over the rules for Prefer MCU in first caller's
site during MCU selection. This is because if a conference starts on an MCU with insufficient ports
reserved for Cascade for size, then that conference will never cascade.