Table Of Contents

Integrating a Secondary Server for Cisco Unity Failover with a TIMG Integration

Requirements

Integration Description

Serial Integration with TIMG Units

In-Band Integration with TIMG Units

Setting Up the Secondary Server for Failover

Integrating a Secondary Server for Cisco Unity Failover with a TIMG Integration

---

The Cisco Unity failover feature enables a secondary server to provide voice messaging services when the primary server becomes inactive. For information on installing a secondary server for failover, see the applicable Installation Guide for Cisco Unity at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_installation_guides_list.html.

For information on Cisco Unity failover, see the applicable Failover Configuration and Administration Guide for Cisco Unity at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_feature_guides_list.html.

This chapter provides information for integrating the secondary Cisco Unity server. See the following sections:

•Requirements

•Integration Description

•Setting Up the Secondary Server for Failover

Requirements

The following components are required to integrate a secondary server:

•One secondary server for each primary server installed and ready for the integration, as described in the applicable Installation Guide for Cisco Unity and earlier in this integration guide.

•A license that enables failover.

Integration Description

See the applicable description for the integration type that your system uses:

•Serial Integration with TIMG Units

•In-Band Integration with TIMG Units

Serial Integration with TIMG Units

The phone system sends call information and MWI requests through the data link, which consists of an RS-232 serial cable between the phone system and the master TIMG unit. Voice connections are sent through the T1 digital lines (DS1 or "dry T1" digital lines only) between the phone system and the TIMG units. The TIMG units communicate with the primary and secondary servers through the LAN or WAN by using Session Initialization Protocol (SIP). Figure 7-1 shows the required connections for a serial integration by using TIMG units.

Figure 7-1 Connections for a Serial Integration with Cisco Unity Failover by Using TIMG Units

In-Band Integration with TIMG Units

The phone system sends call information, MWI requests, and voice connections in-band (through the T1 digital lines—DS1 or "dry T1" digital lines only) to the TIMG units. The TIMG units communicate with the primary and secondary servers through the LAN or WAN by using Session Initiation Protocol (SIP). Figure 7-2 shows the required connections for an in-band integration by using TIMG units.

Figure 7-2 Connections for an In-Band Integration with Cisco Unity Failover by Using TIMG Units

Setting Up the Secondary Server for Failover

Do the following procedure to integrate the secondary server.

To Set Up the Secondary Server for Failover

---

Step 1 Install a secondary server with the same configuration as the primary server. For installation instructions, see the applicable Installation Guide for Cisco Unity.

Step 2 On the Windows Start menu of the secondary server, click Programs > Cisco Unity > Manage Integrations. The UTIM window appears.

Step 3 On the Integration menu of the UTIM window, click New. The Telephony Integration Setup Wizard appears.

Step 4 Enter the settings to match the integration settings on the primary server.

---

Note We recommend not reassigning any unassigned subscribers and call handlers to the new integration, if you are prompted by the wizard. Failover replication will automatically assign the correct integration.

---

Step 5 At the prompt to restart the Cisco Unity services, click Yes.

---

Note When restarting the Cisco Unity services, use the UTIM prompt instead of the Cisco Unity icon in the Windows taskbar. The taskbar icon does not restart all of the Cisco Unity services.

---

Step 6 After Cisco Unity restarts, on the Windows Start menu of the Cisco Unity server, click Programs > Cisco Unity > Manage Integrations. UTIM appears.

Step 7 In the left pane of the UTIM window, click the phone system integration that you created in Step 3.

Step 8 In the right pane, click Properties.

Step 9 On the Integration tab, compare the setting of the Integration ID field for the secondary server to the setting of the Integration ID field for the primary server.

Step 10 If the integration IDs of the phone system on the primary and secondary server are the same, skip to Step 16.

If the integration IDs of the phone system on the primary and secondary servers are different, on the secondary server, click Modify Integration ID.

Step 11 When cautioned that subscribers associated with the current Integration ID setting will not be automatically associated with the new Integration ID setting, click OK.

Step 12 In the Modify Integration ID dialog box, in the Enter New Integration ID field, enter the Integration ID setting for the phone system on the primary server and click OK.

Step 13 Click Save.

Step 14 At the prompt to restart the Cisco Unity services, click Yes.

Step 15 In the left pane, click the phone system integration that you created in Step 3.

Step 16 In the right pane, click the Ports tab.

Step 17 Enter the port settings to match the port settings on the primary server.

---

Caution In programming the phone system, do not send calls to voice messaging ports in Cisco Unity that cannot answer calls (voice messaging ports that are not set to Answer Calls). For example, if a voice messaging port is set only to Message Notification, do not send calls to it.

---

Step 18 Click Save.

Step 19 Repeat Step 16 through Step 18 for each remaining TIMG unit in the phone system integration.

Step 20 Exit UTIM.

---