Filter
Top Products
4-9
When one MCU is down (for example, power shortage), the gatekeeper will
identify that one MCU (A) is unavailable and will automatically forward the
calls to the second MCU (B). The participants are connected to the
conference that was copied from MCU A with the same name.
When the first MCU (A) is up and running again, the gatekeeper will connect
the participants to conferences running on MCU A. If a conference with the
same ID is now running on both MCUs (for example, if MCU A recovered
quickly, participants that connected later were connected to MCU A), the
system will automatically cascade both conferences (using the Auto Cascade
feature) to create one conference. This will eliminate the need to disconnect
and reconnect participants to a single conference.
If the origin conference is terminated on one MCU its backup conference will
be automatically terminated on the second MCU.
In the same way, if ISDN PBX is configured to route calls from one MCU to
another according to MCU availability, the same behavior will occur.
Redundancy Guidelines
• ISDN and IP Network Services must have the same configuration (for
example, MCU Prefix in gatekeeper, dial-in numbers range, etc.) on both
MCUs.
• Conference Profiles, Entry Queue and IVR Services must be identical on
both MCUs.
• Entry Queues must be identical on both MCUs.
• The following conference parameters are copied from the source MCU
to the target MCU (backup):
— Conference duration
— Passwords (chairperson and conference entry)
— User Defined fields
— Billing Code
— Lecture Mode parameters
— Layout and Auto Layout
The Central Server Service is disabled in Secure Mode.