Deployment Guide

Avaya Video Conferencing Manager Deployment Guide 69
Using Cascading MCUs
Use cascading MCUs to connect calls between two groups of participants. Each groups' communication is
channeled through one MCU, and the MCUs pass the bundled communication between each other, greatly
reducing the bandwidth needed for the groups to communicate with each other.
Consider the following example: Eight participants on a network in Japan want to conference with a group
of seven participants on a network in Europe. You schedule the 15 participants in a conference along with
two MCUs, one that serves the users in Japan, and one that serves the users in Europe. You then drag
one of the MCUs (which becomes subservient) and drop it onto the icon for the other (which becomes the
master). For this example to work, the MCUs need to know to which participants to connect. You do this by
giving the devices affinity to an MCU.
NOTE If you created a PIN to use for the call when adding one or more MCUs, the
same PIN is used for all cascaded MCUs.
Assign MCU affinity to a device from the Devices page or the Device details page of a device. Refer to
MCU Affinity.
NOTE If you integrated a third party scheduling application, users cannot schedule a
cascading MCU call from that application.
Use cascading MCUs in calls scheduled from third party scheduling applications by editing the call details
from the Events page in Avaya Video Conferencing Manager. If you update a call scheduled from a third
party scheduling application by adding cascading MCUs from the Events page, Avaya Video Conferencing
Manager sends an email to the meeting organizer describing the changes, provided you allow sending
email notifications to meeting organizers. For more information about allowing email notifications to be
sent to meeting organizers, refer to Mail Integration Settings.