Chapter 4 - Options Settings
•The following conference parameters are NOT copied:
—Remarks and Remarks History
—Lecturer Name (as the backup conference does not include participants)
—Video Forcing (as the backup conference does not include participants)
•If a new conference is started or scheduled on one MCU, and the MCU failed before the conference was backed up on the second MCU, this conference will not be backed up.
•Defined participants are not copied between MCUs and they must be added manually to the backup conferences.
•If the conference is cascaded, it cannot be monitored as one conference.
•If the parameters of one conference are updated, they will be automatically updated also in the backup conference.
•The CDR files are separate on each MCU. A backup conference is identified by its prefix and when activated it will contain participants.
When MCU Redundancy is enabled, do not enter data in the field “User Defined 3” as it is reserved for the Central Server Service internal use.
MCU Redundancy Configuration
1.Click
The Login window is displayed.
2.Enter your User Name and Password and click OK. MGC Web Server Manager window opens.
3.If required, add new MCUs to the list.
4.On the Options menu, click Redundancy Configuration.
The system displays a list of paired MCUs currently defined in the Web Server Manager.
