
© 2017 Avaya Inc. All rights reserved
Release Notes for Avaya Scopia® XT Series What’s New | 10
This new features applies to all XT Series endpoints, including Scopia XT7100, XT5000, XT4300,
XT Executive 240, and XT5000 for IP Office. Furthermore, it works both for the MCU option (only
hardware terminals) and for the SMB option (mixed hardware terminals, PC clients, and mobile
clients). No further license is needed, apart the MCU or SMB. Customers already owning a SMB or
MCU option on their XT units will obtain access to this feature just upgrading to v9.1.
By technical point of view, the technique used is called “MCU cascading”and involves dialing from
one MCU conference to another MCU conference. Each called MCU is seen as an additional
participant on the local MCU conference. This technique limits the experience available to
participants because they can only see a part of the participants on one or another MCU.
The cascade occurs between a single master MCU and one or more slave MCUs, all supporting
cascading. Endpoints can be connected to either the master or slave MCUs. These “MCU to MCU”
connections use up a port on each slave MCU and one port per slave on the master MCU.
During a cascaded conference usually the video from the active speaker (participant who is
talking, or the last who talked) on a slave MCU is sent to the master MCU. On the master MCU,
the video from all slave MCUs and the directly attached endpoints are mixed in accordance with
the conference layout (usually a continuous presence layout).
This view is then sent back to each slave MCU, which then forwards this to its endpoints by re-
encoding it according to the capabilities of the connected endpoints.
If not configured, Master/Slave determination when a call is placed between two MCUs is random,
and does not depend on the direction of the call. As the Master/Slaves determination changes the
visualization of the meeting, sometimes it is better to configure the MCUs in advance.
For instance, if you need participants at rooms A, B and C to be always seen by everyone, while
others rooms can be seen only if they have questions, you can configure XT at room A as Master
MCU, connect B and C directly to MCU A and connect all other participants to other XTs (slaves),
connected to A.
To force an XT to be a master MCU, browse to:
[GUI] CONFIGURE>ADVANCED>CALLS>PREFERENCES>MCU>
[WEB]ADMINISTRATOR SETTINGS>ADVANCED>CALLS>PREFERENCES>MCU>
Important
When using XT endpoints as Master or Slave MCU, the following limitations apply:
oAll participants at Slave (S) and Master (M) nodes can see the same
Continuous Presence video (CP). This requires two encoders on each
Slave MCU, one to propagate received CP to Slave’s eps and one to send
Slaves contribution for CP to Master. Slave shows locally/sends to all its
connection except Master the CP from Master