MGC-25/50/100 MGC+50/100 - Polycom
MGC-25/50/100 MGC+50/100 - Polycom
MGC-25/50/100 MGC+50/100 - Polycom
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
Limitations<br />
Detailed Description - General<br />
“Start only when the chairperson connects” option is implemented, participants in all<br />
conferences will be placed on hold until a chairperson joins one of the conferences. If the<br />
“Terminate conference after the chairperson exits” option is implemented, all conferences<br />
will be terminated when there is no longer a chairperson connected to a conference.<br />
Terminating a Cascading Conference<br />
The system will terminate a slave conference when it no longer has any live participants,<br />
and will terminate the master conference when it no longer has any live participants itself<br />
and has no slave conferences with live participants.<br />
Monitoring Auto Cascaded Conference Links<br />
The links between Auto Cascaded conferences can be monitored in both the <strong>MGC</strong> Manager<br />
and the <strong>MGC</strong> WebCommander. The important links to monitor are the dial-out link<br />
participants.<br />
Figure 1-1 shows an example of monitoring an Auto Cascaded conference in the <strong>MGC</strong><br />
Manager.<br />
Figure 1-1: Monitoring an Auto Cascade conference<br />
The Link Participant Names<br />
The dial-out link participant name will be as follows:<br />
LinkTo[ConferenceType(Master/Slave)]_[Target MCU IP]_<br />
[Primary or Secondary connection (0/1)_[Link Number (01..99)]<br />
For example, the master conference link to slave3 may be called:<br />
LinkToSlave_11.11.11.11_0_03<br />
Dial-in link participants will have a visual name of the following format after they are<br />
moved from the Entry Queue to the conference:<br />
LinkTo[ConferenceType(Master/Slave)]_[Link Number (01..99)]<br />
For example, the dial-in link from a slave conference may have the visual name:<br />
LinkToMaster_01<br />
• In Continuous Presence conferences, the layout must be set to full screen.<br />
• The <strong>MGC</strong> Manager and WebCommander monitoring is per MCU. There is no GUI to<br />
display cascaded conferences across multiple MCUs as one conference.<br />
• The following chairperson actions are implemented per MCU: Voting, Question and<br />
Answers, Replay Roll Call, Change password and Operator assistance.<br />
• For H.263 4CIF and H.264 Continuous Presence conferences, the link will be defined<br />
as H.263 CIF.<br />
• The Auto Cascade feature does not work with H.239/People + Content.<br />
33