A cascaded conference is a single conference occurring over more than one Cisco TelePresence MCU. These MCUs may be located at different locations. The cascade occurs between a single master MCU and one or more slave MCUs. Endpoints can be connected to either the master or slave MCUs. Each slave communicates with the master over a H.323 connection. These connections use up a port on each slave MCU and one port per slave on the master MCU.
During a cascaded conference the video from the active speaker 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 according to the conference layout. This view is then sent back to each slave MCU, which then forwards this to its endpoints. Each of these endpoints receives a separately encoded copy of the stream based on their capabilities.
You can create a cascaded conference in three ways, using the:
Setting up MCU 1
Setting up MCU 2
The steps below set up a gateway so that the MCUs can communicate directly and then bring MCU1 into the conference. (The gateway only needs to be set up once and will be used every time this conference occurs).
Setting up the conference
To set up the conference on MCU1:
Starting the conference
As soon as the conference on MCU1 starts, it calls any pre-configured endpoints including the MCU2 conference 333. This means it calls directly into the conference 333 on the MCU2 cascading the MCUs together. Endpoints connected to conference 333 on both MCUs participate in the same conference.
To cascade a conference across two Cisco TelePresence MCUs using the Management API (rather than the web interface or Cisco TelePresence Director):
During the conference the master MCU sends a CP layout to the slave, while the slave sends a 1x1 voice-switched layout back. All participants on the slave MCU view the layout sent from the master, with one of the panes always showing the loudest participant on the slave.
To create a cascaded conference using Cisco TelePresence Conference Director:
The conference is created. When it is active, the Cascaded Conference icon on the slave MCUs shows that it is a cascaded conference.
|April 13th, 2011||TAA_KB_43|