Cisco Unified Communications Manager SCCP Integration Guide for Cisco Unity Release 5.0 - Integrating a Secondary Server for Cisco Unity Failover with a Cisco Unified Communications Manager Integration [Cisco Unity]

Table Of Contents

Integrating a Secondary Server for Cisco Unity Failover with a Cisco Unified Communications Manager Integration

Requirements

Integration Descriptions

Setting Up the Secondary Server for Failover

Integrating a Secondary Server for Cisco Unity Failover with a Cisco Unified Communications Manager 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 Cisco Unity installation guide 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 Descriptions

•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 Cisco Unity installation guide and earlier in this integration guide.

•A license that enables failover.

Integration Descriptions

The phone system communicates with both the primary and secondary servers through the LAN or WAN. Figure 12-1 shows the required connections.

Figure 12-1 Connections Between Cisco Unified Communications Manager and the Cisco Unity Servers

Setting Up the Secondary Server for Failover

Before proceeding, confirm that the name of the voice mail server and voice mail ports that serve the secondary server are different from the name of the voice mail server and voice mail ports that serve the primary server. Otherwise, the failover will not function correctly.

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 Cisco Unity installation guide.

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, except for the CUCM/CCM Device Name Prefix setting.

Caution The CUCM/CCM Device Name Prefix setting for the secondary server must be different from the CUCM/CCM Device Name Prefix setting for the primary server. Otherwise, the secondary server cannot function correctly.

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.

Step 18 Click Save.

Step 19 Exit UTIM.

If you do not want to set up Cisco Unified CM authentication and encryption of voice messaging ports, skip the next procedure. You have completed integrating the secondary server.

If you want to set up Cisco Unified CM authentication and encryption of voice messaging ports on the secondary server, continue to the next procedure.

Caution The CUCM/CCM Cluster Security Mode settings on the secondary server must match the CUCM/CCM Cluster Security Mode settings on the primary server. Otherwise, Cisco Unified CM authentication and encryption will fail.

To Enable Cisco Unified Communications Manager Authentication and Encryption for Voice Messaging Ports on the Secondary Server

Step 1 If UTIM is not already open, on the secondary server, on the Windows Start menu, click Programs > Cisco Unity > Manage Integrations. UTIM appears.

Step 2 In the left pane, double-click Cisco Unity Server. The existing integrations appear.

Step 3 Click the Cisco Unified CM integration.

Step 4 In the right pane, click the cluster for the integration.

Step 5 Click the Servers tab.

Step 6 In the CUCM/CCM Cluster Security Mode field, click the applicable setting.

Caution The CUCM/CCM Cluster Security Mode setting for Cisco Unity voice messaging ports must match the security mode setting for the Cisco Unified CM ports. Otherwise, Cisco Unified CM authentication and encryption will fail.

Table 12-1 CUCM/CCM Cluster Security Mode

Setting

Effect

Non-secure

The integrity and privacy of call-signaling messages will not be ensured because call-signaling messages will be sent as clear (unencrypted) text and will be connected to Cisco Unified CM through a non-authenticated port rather than an authenticated TLS port.

In addition, the media stream will not be encrypted.

Authenticated

The integrity of call-signaling messages will be ensured because they will be connected to Cisco Unified CM through an authenticated TLS port. However, the privacy of call-signaling messages will not be ensured because they will be sent as clear (unencrypted) text.

In addition, the media stream will not be encrypted.

Encrypted

The integrity and privacy of call-signaling messages will be ensured because they will be connected to Cisco Unified CM through an authenticated TLS port, and the call-signaling messages will be encrypted.

In addition, the media stream can be encrypted.

Step 7 If you clicked the Non-secure setting, click Save and skip the remaining steps in this procedure.

If you clicked the Authenticated or the Encrypted settings, the Security tab and the Add TFTP Server dialog box appear. In the Add TFTP Server dialog box, in the IP Address or Host Name field, enter the IP address (or DNS name) of the primary TFTP server for the Cisco Unified CM cluster and click OK.

Step 8 If there are more TFTP servers that Cisco Unity will use to download the Cisco Unified CM certificates, click Add. The Add TFTP Server dialog box appears.

Step 9 In the IP Address or Host Name field, enter the IP address (or DNS name) of the secondary TFTP server for the Cisco Unified CM cluster, and click OK.

Step 10 Repeat Step 8 and Step 9 for each remaining TFTP server in the Cisco Unified CM cluster.

Step 11 Repeat Step 4 through Step 10 for each remaining cluster in the Cisco Unified CM integration.

On the Security tab, you can press the buttons described in Table 12-2 to add, modify, delete, or verify the TFTP servers that you are connecting to from the Cisco Unity server.

Table 12-2 Buttons for Managing the TFTP Servers

Button

Action

Add

Displays the Add TFTP Server dialog box to add another TFTP server.

Modify

Displays the Modify TFTP Server dialog box so that you can modify the settings of the selected TFTP server.

Delete

Deletes the selected TFTP server.

Step 12 Click Save.

Cisco Unity creates the voice messaging port device certificates, exports the Cisco Unity server root certificate, and displays the Export Cisco Unity Root Certificate dialog box.

Step 13 Note the file name of the exported Cisco Unity server root certificate and click OK.

Step 14 Copy the Cisco Unity server root certificate to all Cisco Unified CM servers in all clusters by doing the applicable steps:

•Recommended—by using a floppy disk. Continue with Step 15.

•For secure networks—by using a network share. Skip to Step 16.

Caution The Cisco Unity system clock must be synchronized with the Cisco Unified CM system clock for Cisco Unified CM authentication to function immediately. Otherwise, Cisco Unified CM will not let the Cisco Unity voice messaging ports register until the Cisco Unified CM system clock has passed the time stamp in the Cisco Unity device certificates.

Step 15 If you are using a floppy disk to copy the Cisco Unity server root certificate, do the following substeps:

a. Insert an empty floppy disk in the floppy drive of the Cisco Unity server.

b. Browse to the CommServer\SkinnyCerts directory.

c. Copy the Cisco Unity server root certificate file that you noted in Step 13 to the floppy disk.

d. Remove the floppy disk from the Cisco Unity server.

e. Insert the floppy disk in the floppy drive of a Cisco Unified CM server.

f. Copy the Cisco Unity server root certificate file on the floppy disk to the C:\Program Files\Cisco\Certificates directory of the Cisco Unified CM server.

g. Restart the Cisco CallManager service on the Cisco Unified CM server.

h. Repeat Step 15 e. through Step 15 g. on all remaining Cisco Unified CM servers in the cluster.

i. Repeat Step 15 e. through Step 15 h. to copy the Cisco Unity server root certificate to all Cisco Unified CM servers in all remaining Cisco Unified CM clusters.

j. For security, delete the Cisco Unity server root certificate file on the floppy disk.

k. On the Cisco Unity server, in UTIM, in the left pane, click the first cluster.

l. Click the Servers tab.

m. Click Verify Servers to confirm the connection to the Cisco Unified CM servers.

If the test is not successful, a dialog box appears that displays the location of the security logs, which provide troubleshooting steps. After troubleshooting, test the connection again.

n. Repeat Step 15 k. through Step 15 m. on all remaining clusters.

o. On the Tools menu, click Restart Cisco Unity to restart the Cisco Unity services.

p. Exit UTIM.

Step 16 If you are using a secure network share to copy the Cisco Unity server root certificate, do the following substeps:

a. On the Cisco Unity server, browse to the CommServer\SkinnyCerts directory.

b. Select Cisco Unity server root certificate file that you noted in Step 13, and press Ctrl-C.

c. Open a network share to a Cisco Unified CM server and log on.

d. Browse to the C:\Program Files\Cisco\Certificates directory on the Cisco Unified CM server.

e. Press Ctrl-V to paste the Cisco Unity server root certificate file.

f. Restart the Cisco CallManager service on the Cisco Unified CM server.

g. Repeat Step 16 c. through Step 16 f. on all remaining Cisco Unified CM servers in the cluster.

h. Repeat Step 16 c. through Step 16 g. to copy the Cisco Unity server root certificate to all Cisco Unified CM servers in all remaining Cisco Unified CM clusters.

i. For security, disconnect the network share.

j. In UTIM, in the left pane, click the first cluster.

k. Click the Servers tab.

l. Click Verify Servers to confirm the connection to the Cisco Unified CM servers.

If the test is not successful, a dialog box appears that displays the location of the security logs, which provide troubleshooting steps. After troubleshooting, test the connection again.

m. Repeat Step 16 j. through Step 16 l. on all remaining clusters.

n. On the Tools menu, click Restart Cisco Unity to restart the Cisco Unity services.

o. Exit UTIM.