Table Of Contents

Tasks Required When Failover or Failback Occurs

Notifying Subscribers of the Active Server and the URLs to Use for Accessing Cisco Unity Web Applications

Preparing for Manual or Scheduled Failback (Integrations Through PIMG/TIMG Units Only)

Standby Redundancy: Failing Over to the Secondary Server

T1 Integrations Through Voice Cards: Enabling the Phone System to Send Calls to the Active Server After Failover or Failback Occurs

Tasks Required When Failover or Failback Occurs

---

This chapter contains the following sections:

•Notifying Subscribers of the Active Server and the URLs to Use for Accessing Cisco Unity Web Applications

•Preparing for Manual or Scheduled Failback (Integrations Through PIMG/TIMG Units Only)

•Standby Redundancy: Failing Over to the Secondary Server

•T1 Integrations Through Voice Cards: Enabling the Phone System to Send Calls to the Active Server After Failover or Failback Occurs

Notifying Subscribers of the Active Server and the URLs to Use for Accessing Cisco Unity Web Applications

Notify subscribers when failover or failback occurs, and give them the correct URLs to use for accessing the following Cisco Unity web applications on the active server:

•Cisco Unity Administrator

•Status Monitor

•Cisco Personal Communications Assistant (Subscribers use the Cisco PCA to access the Cisco Unity Assistant.)

---

Note When subscribers access the Cisco Unity Administrator on the inactive server, they will not be allowed to save changes. When subscribers access the Cisco PCA on the inactive server, any changes they make in the Cisco Unity Assistant can be saved, but the changes are not replicated on the active server.

---

Preparing for Manual or Scheduled Failback (Integrations Through PIMG/TIMG Units Only)

When Cisco Unity is integrated with a phone system through PIMG/TIMG units and you want failback to occur (the secondary server is currently active), do the following procedure before the secondary server fails back to the primary server.

To Disable Failover Initiation When Calls Are Unanswered on the Primary Server

---

Step 1 On the secondary server, on the Windows Start menu, click Programs > Cisco Unity > Failover Monitor.

Step 2 Click Configure.

Step 3 Uncheck the Force Failover If Call Arrives on Inactive Secondary check box.

Step 4 Click OK.

---

Approximately 10 seconds after the primary server becomes active and failback occurs, do the following procedure.

To Enable Failover Initiation When Calls Are Unanswered on the Primary Server

---

Step 1 On the secondary server, on the Windows Start menu, click Programs > Cisco Unity > Failover Monitor.

Step 2 Click Configure.

Step 3 Check the Force Failover If Call Arrives on Inactive Secondary check box.

Step 4 Click OK.

---

Standby Redundancy: Failing Over to the Secondary Server

When standby redundancy is configured, automatic failover and failback are disabled. When the primary server stops taking calls, you must manually initiate failover to the secondary (standby) server.

To Manually Initiate Failover to the Secondary Server

---

Step 1 On the secondary server, on the Windows Start menu, click Programs > Cisco Unity > Failover Monitor.

Step 2 Click Failover.

Step 3 Click OK to confirm that you want to fail over to the secondary server.

Step 4 See the following sections to do the applicable tasks:

•"Notifying Subscribers of the Active Server and the URLs to Use for Accessing Cisco Unity Web Applications" section

•"T1 Integrations Through Voice Cards: Enabling the Phone System to Send Calls to the Active Server After Failover or Failback Occurs" section

---

T1 Integrations Through Voice Cards: Enabling the Phone System to Send Calls to the Active Server After Failover or Failback Occurs

When Cisco Unity and the phone system use a T1 line and voice cards for voice connections, the phone system cannot send calls to the secondary server when failover occurs. Similarly, after the secondary server is active and receiving calls and failback occurs, the phone system cannot send calls to the primary server.

This section contains two procedures. After failover occurs, do the first procedure, "To Enable the Phone System to Send Calls to the Secondary Server After Failover Occurs (Voice Card Integrations)," to enable the phone system to send calls over a T1 line to the secondary server. (Alternatively, you can disconnect the T1 line that connects the primary server and the phone system.)

After failback occurs, do the second procedure, "To Enable the Phone System to Send Calls to the Primary Server After Failback Occurs (Voice Card Integrations)," to enable the phone system to send calls over a T1 line to the primary server. (Alternatively, you can reconnect the T1 line that connects the primary server and the phone system.)

To Enable the Phone System to Send Calls to the Secondary Server After Failover Occurs (Voice Card Integrations)

---

Step 1 On the primary server, exit the Cisco Unity software. For more information, see the "Exiting and Starting the Cisco Unity Software and Server" section on page A-1.

Step 2 On the Windows Start menu, click Programs > Dialogic System Software > Dialogic Configuration Manager-DCM.

Step 3 On the Service menu, click Stop Service. A second Dialogic Configuration Manager window appears.

Step 4 When the message "Success: Dialogic service stopped" appears, click Close.

---

To Enable the Phone System to Send Calls to the Primary Server After Failback Occurs (Voice Card Integrations)

---

Step 1 On the primary server, on the Windows Start menu, click Programs > Dialogic System Software > Dialogic Configuration Manager-DCM.

Step 2 On the Service menu, click Start Service. A second Dialogic Configuration Manager window appears.

Step 3 When the message "Success: Dialogic service started" appears, click Close.

Step 4 Start the Cisco Unity software. For more information, see the "Starting the Cisco Unity Software" section on page A-3.

---