MGC-25/50/100 MGC+50/100 - Polycom

More documents

Recommendations

Info

MGC Release Notes - Version 7.5 32 Defining Auto Cascading Entry Queues To eliminate IVR prompts when Auto Cascade links are created, you must set up Auto Cascade Entry Queues on each MCU. 1. In the Entry Queue Properties dialog box, select the Cascade check box. 2. Enter a value in the Numeric ID field. The Numeric ID must be identical in the Auto Cascading Entry Queues of all the MCUs. 3. Leave the Ad Hoc check box cleared. 4. Proceed to configure the Entry Queue as for any other Entry Queue. Implementation of Chairperson DTMF features The following chairperson DTMF actions are implemented across the MCUs: • Mute all but me and unmute • Terminate the conference • Place the conference on hold and release the conference from being placed on hold • Lock and unlock the conference • Secure the conference and release a secured conference • Wait for the Chairperson Chairperson Conference Activation If chairperson activation is enabled in the Auto Cascade configuration in the MGC WebCommander Server Manager, then the cascaded conference may implement the “Start only when the chairperson connects”, and “Terminate conference after the chairperson exits” features, provided these options are selected in the individual conferences. If the
Limitations Detailed Description - General “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. 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. Terminating a Cascading Conference The system will terminate a slave conference when it no longer has any live participants, and will terminate the master conference when it no longer has any live participants itself and has no slave conferences with live participants. Monitoring Auto Cascaded Conference Links The links between Auto Cascaded conferences can be monitored in both the MGC Manager and the MGC WebCommander. The important links to monitor are the dial-out link participants. Figure 1-1 shows an example of monitoring an Auto Cascaded conference in the MGC Manager. Figure 1-1: Monitoring an Auto Cascade conference The Link Participant Names The dial-out link participant name will be as follows: LinkTo[ConferenceType(Master/Slave)]_[Target MCU IP]_ [Primary or Secondary connection (0/1)_[Link Number (01..99)] For example, the master conference link to slave3 may be called: LinkToSlave_11.11.11.11_0_03 Dial-in link participants will have a visual name of the following format after they are moved from the Entry Queue to the conference: LinkTo[ConferenceType(Master/Slave)]_[Link Number (01..99)] For example, the dial-in link from a slave conference may have the visual name: LinkToMaster_01 • In Continuous Presence conferences, the layout must be set to full screen. • The MGC Manager and WebCommander monitoring is per MCU. There is no GUI to display cascaded conferences across multiple MCUs as one conference. • The following chairperson actions are implemented per MCU: Voting, Question and Answers, Replay Roll Call, Change password and Operator assistance. • For H.263 4CIF and H.264 Continuous Presence conferences, the link will be defined as H.263 CIF. • The Auto Cascade feature does not work with H.239/People + Content. 33
Page 1 and 2: MGC-25/50/100 MGC+50/100 Release No
Page 3 and 4: Table of Contents Version 7.5 - New
Page 5 and 6: Version 7.5 - New Features List The
Page 7 and 8: Table 1: New Features List (Continu
Page 9 and 10: Version 7.5 Upgrade Package Content
Page 11 and 12: # Board Type Prior to Installation
Page 13 and 14: Table 1: Version 7.5 Interoperabili
Page 15 and 16: Dongle Upgrade Dongle Information T
Page 17 and 18: Software Upgrade Procedure MGC-25
Page 19 and 20: 6. Click Download. Save the new don
Page 21 and 22: Software Upgrade Procedure Upgradin
Page 23 and 24: Installing the MGC Manager Software
Page 25 and 26: Detailed Description - Video Detail
Page 27 and 28: Detailed Description - General Netw
Page 29 and 30: Secure Socket Layer (SSL) Detailed
Page 31 and 32: 9. Paste the certificate’s text i
Page 33 and 34: Detailed Description - General —
Page 35: Ad Hoc Auto Cascade Detailed Descri
Page 39 and 40: HTTP File Transfer Mode Detailed De
Page 41 and 42: Direct IP Dial-in Detailed Descript
Page 43 and 44: Detailed Description - General —
Page 45 and 46: Detailed Description - General MGC+
Page 47 and 48: Corrections, Pending Issues and Lim
Page 49 and 50: Table 4: Corrections between Versio
Page 51 and 52: Corrections between Versions V.7.0
Page 53 and 54: Version 7.5 Pending Issues Table 6:
Page 55 and 56: Table 6: Pending Issues (Continued)
Page 57 and 58: Table 6: Pending Issues (Continued)
Page 59 and 60: Table 7: System Limitations (Contin
Page 69 and 70: Appendix A - Falcon Diagnostic Tool
Page 71 and 72: Table 8: Diagnostic Tests Card Unit
Page 73 and 74: Table 8: Diagnostic Tests Card Unit
Page 77 and 78: Setting the Log Files Path Appendix
Page 79 and 80: Running Diagnostic Tests Appendix A
Page 83 and 84: Test Results Appendix A - Falcon Di
Page 85 and 86: Appendix - Adding an MCU to the Net
Page 87 and 88:
Log File Report Examples Appendix A
Page 89 and 90:
Appendix A - Falcon Diagnostic Tool
Page 91 and 92:
Page 93 and 94:
show all

MGC-25/50/100 MGC+50/100 - Polycom

Create successful ePaper yourself

Delete template?

Save as template?