Table of Contents
Advertisement
September 2007
Hot Fail Over Application
This software component is a small executable program used to monitor the
activity of two Unify Servers and enable a secondary Unify to control the
Recorders should the primary Unify fail. The Hot Fail Over Application is
typically deployed on one of the two Unify servers. Because of this, the
Unify Script must interpret loss of communication with the Hot Fail Over
Application as a sign that it should be in control.
Unify troubleshooting
Several scenarios exist for Unify failure. For example, Unify can fail and the
Hot Fail Over application is still functional. Alternatively, both Unify and
the Hot Fail Over application can fail at the same time, in which case Hot
Fail Over on the secondary server would take over. The following scenarios
are identified and described:
Secondary Unify Takes Over
Hot Fail Over application works from the secondary Unify
CTI Event Arrives Before Secondary Unify is Promoted
Unify with Hot Fail Over Application crashes
Secondary Unify takes over
These steps describe events that occur when the primary Unify fails, the Hot
Fail Over application senses this, and promotes the secondary Unify to take
over.
1. Unify 1 is the primary (controlling) Unify and Unify 2 is the secondary
(backup) Unify. Both are running correctly.
2. A CTI event comes in indicating a start of a call. Both Unify 1 and Unify
2 process the event and update their state tables.
3. Only Unify 1 actually sends the Start Record command to the Recorder.
4. Both Unify 1 and Unify 2 hear the Recorder respond to the Start Record
command with the Started message and update their state tables.
System Infrastructure Guide
Configuring Primary Recorder Components
121
Advertisement
Table of Contents
