September 2007
8. A CTI event comes in indicating the stop of the call in step #2. Only
Unify 2 hears the event and processes it. Unify 2 updates its state tables.
9. Unify 2 sends the StopRecord event to the Recorder.
10.The Recorder responds with a Stopped message. Only Unify 2 hears the
stopped message because Unify 1 is still down. Unify 2 updates its state
tables.
11.Unify 1 and the Hot Fail Over Application come back online.
12.The Hot Fail Over Application keeps Unify 2 as the primary Unify until
it encounters a problem.
System Infrastructure Guide
Configuring Primary Recorder Components
125