Installation and Configuration Guide for Visual Voicemail Release 8.5

Cluster of Publisher and Subscriber Cisco Unity Connection Servers in an Active-Active Configuration with One Cisco Unified Communications Manager Server

To configure Visual Voicemail on a system where publisher and subscriber Cisco Unity Connection servers are integrated in an active-active configuration with one Cisco Unified Communications Manager server, you must do the following:

• Create a unique Visual Voicemail pilot number for each Cisco Unity Connection server in the cluster. Each pilot number must use the correct set of voicemail ports that corresponds to the particular Cisco Unity Connection server.

The set of voicemail ports for a server is contained in a line group. A hunt list refers to the line group, and a hunt pilot refers to the hunt list. Therefore the hunt pilot for a particular server must use a line group which has the correct ports for that server.

• Create a line group for each Cisco Unity Connection server in the cluster. The directory numbers that are listed for the ports for the publisher server must be added to the line group for the publisher server. Similarly, the directory numbers that are listed for the ports for the subscriber server must be added to the line group for the subscriber server.

For more information about how to create a line group, see Creating a Line Group or Route Group (Cisco Unity Connection Clusters Only).

• Create a hunt list for each Cisco Unity Connection server in the cluster. You must add the line group for the publisher server to the hunt list for the publisher server. Similarly, you must add the line group for the subscriber server to the hunt list for the subscriber server.

For more information about how to create a hunt list, see Creating a Hunt List or Route List (Cisco Unity Connection Clusters Only).

• Configure the Cisco Unity Connection settings for the web service on both the publisher and subscriber Cisco Unity Connection servers.

When you configure the voicemail web service, enter the appropriate pilot number for each Cisco Unity Connection server in the Pilot Number for TRAP Connections field. This setting has different values on the publisher server and subscriber server, because you created a different pilot number for each server.

• Configure two reverse TRAP rules on the Cisco Unity Connection publisher server, as follows:

– In the first rule, set the Dialed Number field of the routing condition to the Visual Voicemail pilot number for the publisher server.

– In the second rule, set the Dialed Number field of the routing condition to the Visual Voicemail pilot number for the subscriber server.

You do not need to do this configuration on the subscriber server because the rules are replicated to the subscriber server.

• Create one Visual Voicemail service on the Cisco Unified Communications Manager server. Use the cluster DNS alias as the hostname in the following fields:

– Service URL of the service

– Default Value of the voicemail_server parameter

The term cluster DNS alias refers to two Cisco Unity Connection servers that work together as a cluster, that is, both servers actively accept calls and web service requests from Visual Voicemail.

When you use the cluster DNS alias for the voicemail_server parameter, the Visual Voicemail application uses the Cisco Unity Connection servers in a round robin order. When a user signs in to the Visual Voicemail application, the Cisco Unity Connection server that is used automatically provides the hostname of the partner server to the Visual Voicemail application. The partner hostname is cached locally by the Visual Voicemail application and is used in failover scenarios when the original server is not available.

If you want to configure security for Visual Voicemail, you must do the following:

• Add the use_secure_https_connection parameter to the Visual Voicemail service on the Cisco Unified Communications Manager server.
• Obtain a certificate for Visual Voicemail on each Cisco Unity Connection server.
• Add the certificates for each Cisco Unity Connection server to Cisco Unified Communications Manager and to the phones.

For more information about clusters of publisher and subscriber Cisco Unity Connection servers in an active-active configuration, navigate to the Design Guide for Cisco Unity Connection from the following URL:

http://www.cisco.com/en/US/products/ps6509/tsd_products_support_design.html

For more information about using a Cisco Unity Connection cluster, as well as information on how a Connection cluster works, navigate to the Cluster Configuration and Administration Guide for Cisco Unity Connection from the following URL:

http://www.cisco.com/en/US/products/ps6509/prod_maintenance_guides_list.html

Balancing Web Service Requests Between Servers in an Active-Active Configuration

To balance web service requests equally between two Cisco Unity Connection servers, use DNS aliasing. To do this, you must add two DNS Host(A) records as follows:

• Host Name = unityCxnCluster IP Address : IP address of primary server
• Host Name = unityCxnCluster IP Address : IP address of secondary server

If you add these two records, DNS queries for the cluster DNS alias unityCxnCluster resolve alternately between the two IP addresses.

For more information about balancing web service requests between servers in an active-active configuration, navigate to the Design Guide for Cisco Unity Connection from the following URL:

http://www.cisco.com/en/US/products/ps6509/tsd_products_support_design.html

Related Topics

• How to Create a Line Group and Hunt List or Route Group and Route List (Cisco Unity Connection Clusters Only)
• Configuring Voicemail Web Service on Cisco Unity Connection
• Configuring a Reverse TRAP Rule on Cisco Unity Connection
• How to Add the Visual Voicemail Service in Cisco Unified Communications Manager
• Adding the Security Service Parameter to the Visual Voicemail Service
• Adding the Certificate to Cisco Unified Communications Manager and IP Phones
• Uploading Certificates to Cisco Unified Communications Manager

Configuration of Multiple Cisco Unity Connection Clusters Integrated with One Cisco Unified Communications Manager Server

To configure Visual Voicemail on a system where multiple Cisco Unity Connection clusters are integrated with one Cisco Unified Communications Manager server, you must do the following:

• Create a unique Visual Voicemail pilot number for each Cisco Unity Connection server. Each pilot number must use the correct set of voicemail ports for the particular Cisco Unity Connection server.
• Configure the Cisco Unity Connection settings for the web service on both the publisher and subscriber Cisco Unity Connection servers in each cluster.

When you configure the voicemail web service, enter the appropriate pilot number for each Cisco Unity Connection server in the Pilot Number for TRAP Connections field. This setting has different values on each Cisco Unity Connection server, because you created a different pilot number for each server.

• Configure the reverse TRAP rule on each Cisco Unity Connection server. Use the same Visual Voicemail pilot number in the Dialed Number field on each server.
• Create one Visual Voicemail service on the Cisco Unified Communications Manager server for each cluster. For each Cisco Unified Communications Manager server, use the cluster DNS alias as the hostname of that server in the following fields:

– Service URL of the service

– Default Value of the voicemail_server parameter

Each service must have the same value in the Service Name field, because this value must match the value in the.jad file. Cisco Unified Communications Manager allows you to create multiple services with the same name. You can use the Service Description field to distinguish between the services.

When you use the cluster DNS alias for the voicemail_server parameter, the Visual Voicemail application uses the Cisco Unity Connection servers in that cluster in a round robin order. When a user signs in to the Visual Voicemail application, the Cisco Unity Connection server that is used automatically provides the hostname of the partner server to the Visual Voicemail application. The partner hostname is cached locally by the Visual Voicemail application and is used in failover scenarios when the original server is not available.

If you want to configure security for Visual Voicemail, you must do the following:

• Add the use_secure_https_connection parameter to each Visual Voicemail service on the Cisco Unified Communications Manager server.
• Obtain a certificate for Visual Voicemail on each Cisco Unity Connection server.
• Add the certificates for each Cisco Unity Connection server to Cisco Unified Communications Manager and to the phones.