•If none of the conferences has a chairperson, then the conference that is running on the MCU which is highest in the MCUs table in the Web Server Manager will be assigned as the master conference.
•If there is more than one conference with a chairperson, then the conference with a chairperson that is running on the MCU which is highest in the MCUs table in the Web Server Manager will be assigned as the master conference.
If chairperson activation is disabled, then the conference that is running on the MCU which is highest in the MCUs table in the Web Server Manager will be assigned as the master conference.
Chairperson Activation
If chairperson activation is enabled in the Auto Cascade configuration in the MGC Web Server Manager, then the cascaded conference can implement the “Start when the chairperson connects”, and “Terminate conference after the chairperson exits” features, provided these options are selected in the individual conferences.
Starting the Conference to be Cascaded
If the “Start only when the chairperson connects” option is implemented, participants in all conferences will be placed on hold until a chairperson joins one of the conferences.
Terminating a Cascading Conference
If the “Terminate conference after the chairperson exits” option is implemented, all conferences will be terminated when there is no longer a chairperson connected to a conference. In addition, the system will terminate a slave conference when it no longer has any live participants, and will terminate the master conference when no participants are connected and no slave conferences with connected participants are still connected to it.
Implementation of Chairperson DTMF features
The following chairperson DTMF actions are implemented across the MCUs:
•Mute all but me
•Terminate the conference
•Place the conference on hold
•Lock and unlock the conference
•Secure the conference and release a secured conference
