Avaya scopia elite 6000 series Installation Manual page 17

Planning a Centralized or Distributed Topology (Cascading) for MCU
Figure 3: Distributed MCU deployment cascading meetings for reduced WAN bandwidth
The bandwidth used by a cascaded link is equivalent to only a single client connection in each
direction: upload and download. The bandwidth value is determined by the MCU meeting type (or
service), which is invoked when choosing a dial prefix for the meeting. You define the maximum
bandwidth for each meeting type in the MCU. For more information on defining meeting types, see
®
Administrator Guide for Scopia Elite 6000 Series MCU.
Users do not need to choose a specific MCU. The powerful functionality of virtual rooms enables
®
you to dial the same number anywhere in the world, while the Scopia Solution infrastructure
transparently directs you to the correct meeting on the correct MCU.
The maximum supported number of participants in a single videoconference is 500 for both the
centralized and distributed MCU deployment.
Users do not need to manually enable cascading when creating meetings. This is performed
®
transparently by Avaya Scopia Management using sophisticated cascading algorithms.
When an endpoint initiates a meeting on an MCU, that MCU becomes the master MCU. Other
MCUs which participate in the meeting are designated as slave MCUs. There are a number of
factors that might influence when the system automatically chooses to cascade to a different MCU.
For example, to avoid reaching the maximum bandwidth threshold, the system would attempt
cascading with a different MCU, a slave MCU. Endpoints would then join the videoconference from
the slave MCU. Only one level of cascading is supported: all slave MCU conferences must cascade
to the same master MCU conference. Administrators can also customize the priority given to
®
cascading in a distributed topology, as explained in Administrator Guide for Avaya Scopia
Management .
®
February 2016 Avaya Scopia Elite 6000 Series MCU Installation Guide 17
Comments on this document? infodev@avaya.com