Installation and Configuration Guide for Visual Voicemail Release 8.5
Overview of Mandatory Tasks for Configuring Cisco Visual Voicemail on a Cisco Unified Communications System
Downloads: This chapterpdf (PDF - 146.0KB) The complete bookPDF (PDF - 2.21MB) | Feedback

Overview of Mandatory Tasks for Configuring Cisco Visual Voicemail on a Cisco Unified Communications System

Table Of Contents

Overview of Mandatory Tasks for Configuring Cisco Visual Voicemail on a Cisco Unified Communications System

Task List for Configuring with a Single Cisco Unity Connection Server or Networked Connection Servers.

Task List for Configuring Visual Voicemail for a Cisco Unity Connection Cluster or Networked Connection Clusters

Task List for Configuring Visual Voicemail with a Single Cisco Unity Server or Networked Cisco Unity Servers

Task List for Configuring Visual Voicemail with a Cisco Unity Failover Pair or Networked Cisco Unity Failover Pairs


Overview of Mandatory Tasks for Configuring Cisco Visual Voicemail on a Cisco Unified Communications System


This chapter contains four task lists. Use the applicable task list, depending on whether you are configuring Cisco Visual Voicemail to integrate with Cisco Unity or Cisco Unity Connection and whether you have a single voicemail server or multiple voicemail servers in a cluster or network:

Cisco Unity Connection

Task List for Configuring with a Single Cisco Unity Connection Server or Networked Connection Servers.

Task List for Configuring Visual Voicemail for a Cisco Unity Connection Cluster or Networked Connection Clusters

Cisco Unity

Task List for Configuring Visual Voicemail with a Single Cisco Unity Server or Networked Cisco Unity Servers

Task List for Configuring Visual Voicemail with a Cisco Unity Failover Pair or Networked Cisco Unity Failover Pairs

Task List for Configuring with a Single Cisco Unity Connection Server or Networked Connection Servers.

Revised January 6, 2011

This task list applies to a Cisco Unified Communications system that contains either one Cisco Unity Connection server or multiple Connection servers networked together. If your Unified Communications system contains a Cisco Unity Connection cluster or multiple Connection clusters networked together, see the "Task List for Configuring Visual Voicemail for a Cisco Unity Connection Cluster or Networked Connection Clusters" section.


Note This task list assumes that the Cisco Unity Connection server(s) and the Cisco Unified CM server(s) are already configured and integrated correctly, and are functioning.


1. Ensure that you have read and understood all of the information in Considerations Before You Configure Visual Voicemail.

2. Confirm that the Unified Communications system meets all of the necessary system requirements and the correct versions of all the required software, as listed in the release notes at the following URL:

http://www.cisco.com/en/US/products/ps9829/prod_release_notes_list.html

3. Enable web access on Cisco IP phone. See the "Enabling Web Access on Phones" section.

4. To allow Visual Voicemail to establish reverse TRAP connections to the voicemail server, create a voicemail pilot number and either a hunt pilot or a route pattern on the Cisco Unified Communications Manager server.

Perform the following subtasks:

a. Create a voicemail pilot number. See the "Creating a Voicemail Pilot Number for Visual Voicemail" section.

If you have multiple Cisco Unity Connection servers networked together, create a unique Visual Voicemail pilot number for each Connection server.

b. Create either a hunt pilot or route pattern. See the "Creating a Hunt Pilot or Route Pattern for the Visual Voicemail Pilot Number" section.

If you have multiple Cisco Unified Communications Manager servers in a cluster environment, create the Visual Voicemail pilot number and hunt pilot or route pattern on each Cisco Unified CM server. You must use the same directory number for the pilot number or route pattern on each Cisco Unified CM server.

5. Configure voicemail web service on the voicemail server. See the "Configuring Voicemail Web Service on Cisco Unity Connection" section.

If you have multiple Cisco Unity Connection servers networked together, enter the appropriate Visual Voicemail pilot number for each Connection server in the Voice Mail Web Service: Pilot Number for TRAP Connections field. This setting has different values on each Connection server, because you created a different Visual Voicemail pilot number for each server.

6. Configure a reverse TRAP rule on the voicemail server. See the "Configuring a Reverse TRAP Rule on Cisco Unity Connection" section.

If you have multiple Cisco Unity Connection servers networked together, configure a reverse TRAP rule on each Connection server. Use the appropriate Visual Voicemail pilot number in the Dialed Number field on each server.

7. Configure message indicator counts. See the "Configuring a Message Indicator Count on Cisco Unity Connection" section.

If you have multiple Cisco Unity Connection servers networked together, configure message indicator counts on each server in the network.

8. Add the Visual Voicemail service on the Cisco Unified Communications Manager server. See the "How to Add the Visual Voicemail Service in Cisco Unified Communications Manager" section.

If you have multiple Cisco Unity Connection servers networked together, create a Visual Voicemail service for each Connection server in the network.

If you have multiple Cisco Unified Communications Manager servers in a cluster environment, repeat this step on each Cisco Unified CM server.

9. Optional: Configure security for Visual Voicemail. See the "Configuring Security for Cisco Visual Voicemail" chapter.

If you have multiple Cisco Unity Connection servers networked together, download the tomcat certificate from each of the Connection servers and add all of the certificates to the Cisco Unified CM server and to the IP phones.

If you have multiple Cisco Unified Communications Manager servers in a cluster environment, you must add the tomcat security certificate to each Cisco Unified CM server in the cluster.

10. Install Visual Voicemail on the phones. See the "Installing Cisco Visual Voicemail on Phones" chapter.

11. Optional: Customize the keypad mapping file that defines which keys perform which actions when users press numbers on the phone keypad. See the "Configuring Key Mappings in Visual Voicemail" chapter.

12. Provide information about Visual Voicemail to users. See the "Information to Provide to Users" chapter.

Task List for Configuring Visual Voicemail for a Cisco Unity Connection Cluster or Networked Connection Clusters

Revised January 6, 2011

This task list applies to a Cisco Unified Communications system that contains a Cisco Unity Connection cluster or multiple Connection clusters networked together. If your Unified Communications system contains either one Cisco Unity Connection server or multiple Connection servers networked together, see the "Task List for Configuring with a Single Cisco Unity Connection Server or Networked Connection Servers." section.


Note This task list assumes that the Cisco Unity Connection cluster(s) and the Cisco Unified CM server(s) are already configured and integrated correctly, and are functioning.


1. Ensure that you have read and understood all of the information in Considerations Before You Configure Visual Voicemail.

2. Confirm that the Unified Communications system meets all of the necessary system requirements and the correct versions of all the required software, as listed in the release notes at the following URL:

http://www.cisco.com/en/US/products/ps9829/prod_release_notes_list.html

3. Enable web access on Cisco IP phone. See the "Enabling Web Access on Phones" section.

4. To allow Visual Voicemail to establish reverse TRAP connections to the voicemail servers, create Visual Voicemail pilot numbers and either hunt pilots or route patterns on the Cisco Unified Communications Manager server. Also, create either line groups and hunt lists or route groups and route lists for each server in the cluster.

Perform the following subtasks:

a. Confirm that there is a line group or route group for each Cisco Unity Connection server in the cluster. See the"Creating a Line Group or Route Group (Cisco Unity Connection Clusters Only)" section.

b. Create a hunt list or route list for each Cisco Unity Connection server in the cluster. See "Creating a Hunt List or Route List (Cisco Unity Connection Clusters Only)" section.

c. To allow Visual Voicemail to establish reverse TRAP connections to the voicemail servers, create a unique Visual Voicemail pilot number for each Cisco Unity Connection server in the cluster. See the "Creating a Voicemail Pilot Number for Visual Voicemail" section.

If you have multiple Cisco Unified Communications Manager servers in a cluster environment, create the Visual Voicemail pilot numbers on each Cisco Unified CM server. You must use the same directory numbers for the pilot numbers on each Cisco Unified CM server.

d. Create a hunt pilot or route pattern for each Visual Voicemail pilot number. See the "Creating a Hunt Pilot or Route Pattern for the Visual Voicemail Pilot Number" section.

Each hunt pilot or route pattern must use the correct set of voicemail ports that corresponds to the particular Cisco Unity Connection server.

If you have multiple Cisco Unified Communications Manager servers in a cluster environment, create the Visual Voicemail hunt pilots or route patterns on each Cisco Unified Communications Manager server.

5. On the Cisco Unity Connection servers, configure the voicemail web service settings.

You must enter the appropriate reverse TRAP pilot number for each Cisco Unity Connection server in the Voice Mail Web Service: Pilot Number for TRAP Connections field. This setting has different values on the publisher server and subscriber server, because you created a different Visual Voicemail pilot number for each server.

The value you enter in the Voice Mail Web Service: Pilot Number for Voice Mail will be the same on the publisher and subscriber because this is the pilot number for the audio voicemail service.

See the "Configuring Voicemail Web Service on Cisco Unity Connection" section.

6. Configure two reverse TRAP rules on the Connection publisher server as follows:

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

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

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

See the "Configuring a Reverse TRAP Rule on Cisco Unity Connection" section.

If you have multiple Cisco Unity Connection clusters networked together, create two reverse TRAP rules on each publisher server in the network.

7. Configure message indicator counts. See the "Configuring a Message Indicator Count on Cisco Unity Connection" section.

If you have multiple Cisco Unity Connection clusters networked together, configure message indicator counts on each publisher server in the network.

8. Configure a DNS alias to balance web service requests equally between the primary and secondary Connection servers. See the "Balancing Web Service Requests Between Connection Servers (Cisco Unity Connection Clusters Only)" section.

If you have multiple Cisco Unity Connection clusters networked together, configure a DNS alias for each Connection cluster so that web service requests are balanced between the primary and secondary servers of each cluster.

9. Create one Visual Voicemail service on the Cisco Unified CM 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 scenarios when the original server is not available.

See the "How to Add the Visual Voicemail Service in Cisco Unified Communications Manager" section.

If you have multiple Cisco Unity Connection clusters networked together, create one Visual Voicemail service for each Connection cluster in the network.

If you have multiple Cisco Unified Communications Manager servers in a cluster environment, repeat this step on each Cisco Unified CM server.

10. Optional: Configure security for Visual Voicemail. You must download the tomcat certificate from both Connection servers and add both certificates to the Cisco Unified CM server and to the IP phones. See the "Configuring Security for Cisco Visual Voicemail" chapter.

If you have multiple Cisco Unity Connection clusters networked together, you must download the tomcat certificate every Connection server and add all of the certificates to the Cisco Unified CM server and to the IP phones.

If you have multiple Cisco Unified Communications Manager servers in a cluster environment, add the tomcat certificates to each Cisco Unified CM server in the cluster.

11. Install Visual Voicemail on the phones. See the "Installing Cisco Visual Voicemail on Phones" chapter.

12. (Optional) Customize the keypad mapping file that defines which keys perform which actions when users press numbers on the phone keypad. See the "Configuring Key Mappings in Visual Voicemail" chapter.

13. Provide information about Visual Voicemail to users, as listed in "Information to Provide to Users".

Task List for Configuring Visual Voicemail with a Single Cisco Unity Server or Networked Cisco Unity Servers

Revised January 6, 2011

This task list applies to a Cisco Unified Communications system that contains either one Cisco Unity Connection server or multiple Cisco Unity servers networked together. If your Unified Communications system contains a Cisco Unity failover pair or multiple Cisco Unity failover pairs networked together, see the "Task List for Configuring Visual Voicemail with a Cisco Unity Failover Pair or Networked Cisco Unity Failover Pairs" section.


Note This task list assumes that the Cisco Unity server and the Cisco Unified CM server(s) are already configured and integrated correctly, and are functioning.


1. Ensure that you have read and understood all of the information in Considerations Before You Configure Visual Voicemail.

2. Confirm that the Unified Communications system meets all of the necessary system requirements and the correct versions of all the required software, as listed in the release notes at the following URL:

http://www.cisco.com/en/US/products/ps9829/prod_release_notes_list.html

3. Enable web access on Cisco IP phone. See the "Enabling Web Access on Phones" section.

4. To allow Visual Voicemail to establish reverse TRAP connections to the voicemail server, create a voicemail pilot number and either a hunt pilot or a route pattern on the Cisco Unified Communications Manager server.

Perform the following subtasks:

a. Create a voicemail pilot number. See the "Creating a Voicemail Pilot Number for Visual Voicemail" section.

If you have multiple Cisco Unity servers networked together, create a unique Visual Voicemail pilot number for each Cisco Unity server.

b. Create either a hunt pilot or route pattern. See the "Creating a Hunt Pilot or Route Pattern for the Visual Voicemail Pilot Number" section.

If you have multiple Cisco Unity servers networked together, create either a hunt pilot or route pattern for each Visual Voicemail pilot number. Each hunt pilot or route pattern must use the correct set of voicemail ports that corresponds to the particular Cisco Unity server.

If you have multiple Cisco Unified Communications Manager servers in a cluster environment, create the Visual Voicemail pilot number and either hunt pilot or route pattern on each Cisco Unified CM server. You must use the same directory numbers for the pilot numbers or route patterns on each Cisco Unified CM server.

5. Configure voicemail web service on the voicemail server. See the "Configuring Voicemail Web Service on Cisco Unity 8.0 and later" section.

If you have multiple Cisco Unity servers networked together, any changes you make to the voicemail web service settings must be repeated on each Cisco Unity server in the network.

6. Configure a reverse TRAP rule on the Cisco Unity voicemail server. See the "Configuring a Reverse TRAP Rule on Cisco Unity" section.

If you have multiple Cisco Unity servers networked together, configure a reverse TRAP rule on each of the Cisco Unity servers. Use the appropriate Visual Voicemail pilot number for each server in the Dialed Number (DNIS) field.

7. Configure message indicator counts. See the "Configuring a Message Indicator Count on Cisco Unity" section.

8. Add the Visual Voicemail service on the Cisco Unified Communications Manager server. See the "How to Add the Visual Voicemail Service in Cisco Unified Communications Manager" section.

If you have multiple Cisco Unity servers networked together, create a Visual Voicemail service for each Cisco Unity server. For each Cisco Unity server, use 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 VisualVoicemail in the Service Name field. Cisco Unified CM allows you to create multiple services with the same name. You can use the Service Description field to distinguish between the services.

If you have multiple Cisco Unified Communications Manager servers in a cluster environment, repeat this step on each Cisco Unified CM server.

9. Optional: Configure security for Visual Voicemail. See the "Configuring Security for Cisco Visual Voicemail" chapter.

If you have multiple Cisco Unity servers networked together, obtain a certificate for Visual Voicemail on each Cisco Unity server and add all of the certificates to the Cisco Unified CM server and to the IP phones.

If you have multiple Cisco Unified Communications Manager servers in a cluster environment, you must add the certificates for the Cisco Unity server to each Cisco Unified CM server in the cluster.

10. Install Visual Voicemail on the phones. See the "Installing Cisco Visual Voicemail on Phones" chapter.

11. Optional: Customize the keypad mapping file that defines which keys perform which actions when users press numbers on the phone keypad. See the "Configuring Key Mappings in Visual Voicemail" chapter.

12. Provide information about Visual Voicemail to users. See the "Information to Provide to Users" chapter.

Task List for Configuring Visual Voicemail with a Cisco Unity Failover Pair or Networked Cisco Unity Failover Pairs

Revised January 6, 2011

This task list applies to a Cisco Unified Communications system that contains either one pair of Cisco Unity servers configured in a failover configuration or multiple Cisco Unity failover pairs networked together. If your Unified Communications system contains either one single Cisco Unity Connection server or multiple Cisco Unity servers networked together, see the "Task List for Configuring Visual Voicemail with a Single Cisco Unity Server or Networked Cisco Unity Servers" section.


Note This task list assumes that the Cisco Unity servers and the Cisco Unified CM server(s) are already configured and integrated correctly, and are functioning.


1. Ensure that you have read and understood all of the information in Considerations Before You Configure Visual Voicemail.

2. Confirm that the Unified Communications system meets all of the necessary system requirements and the correct versions of all the required software, as listed in the release notes at the following URL:

http://www.cisco.com/en/US/products/ps9829/prod_release_notes_list.html

3. Enable web access on Cisco IP phone. See the "Enabling Web Access on Phones" section.

4. To allow Visual Voicemail to establish reverse TRAP connections to the voicemail server, create one voicemail pilot number and either a hunt pilot or a route pattern on the Cisco Unified Communications Manager server.

Perform the following subtasks:

a. Create a Visual Voicemail voicemail pilot number. See the "Creating a Voicemail Pilot Number for Visual Voicemail" section.

If you have multiple Cisco Unity failover pairs networked together, create a unique Visual Voicemail pilot number for each Cisco Unity failover pair.

If you have multiple Cisco Unified Communications Manager servers in a cluster environment, create the Visual Voicemail pilot numbers on each Cisco Unified CM server. You must use the same directory numbers for the pilot numbers on each Cisco Unified CM server.

b. Create either a hunt pilot or route pattern for the Visual Voicemail pilot number. See the "Creating a Hunt Pilot or Route Pattern for the Visual Voicemail Pilot Number" section.

If you have multiple Cisco Unity failover pairs networked together, create a unique hunt pilot or route pattern for each Cisco Unity failover pair. Each hunt pilot or route pattern must use the correct set of voicemail ports that corresponds to the particular Cisco Unity failover pair.

If you have multiple Cisco Unified Communications Manager servers in a cluster environment, create the Visual Voicemail hunt pilots or route patterns on each Cisco Unified Communications Manager server.

5. Configure voicemail web service on both the primary and secondary servers. See the "Configuring Voicemail Web Service on Cisco Unity 8.0 and later" section.

If you have multiple Cisco Unity failover pairs networked together, any changes you make to the voicemail web service settings must be repeated on each Cisco Unity server in the network.

6. Configure a reverse TRAP rule on both the primary server and the secondary server. Use the same Visual Voicemail pilot number in the Dialed Number (DNIS) field for both servers. See the "Configuring a Reverse TRAP Rule on Cisco Unity" section.

If you have multiple Cisco Unity failover pairs networked together, configure a reverse TRAP rule on each of the Cisco Unity servers, including all the primary and secondary servers. For each primary and secondary pair, use the same Visual Voicemail pilot number in the Dialed Number (DNIS) field for both servers.

7. Configure message indicator counts. See the "Configuring a Message Indicator Count on Cisco Unity" section.

8. Add the Visual Voicemail service on the Cisco Unified Communications Manager server. Create only one Visual Voicemail service on the Cisco Unified Communications Manager server. Enter the hostname of the primary Cisco Unity server in the following fields:

Service URL of the service

Default Value of the voicemail_server parameter

When a user signs in to Visual Voicemail, the primary server automatically provides the hostname of the secondary server to the application. The hostname of the secondary server is cached locally by the application and is used in failover scenarios when the primary server is not available.

See the "How to Add the Visual Voicemail Service in Cisco Unified Communications Manager" section.

If you have multiple Cisco Unity failover pairs networked together, create one Visual Voicemail service for each Cisco Unity failover pair. Each service must have VisualVoicemail in the Service Name field. Cisco Unified CM allows you to create multiple services with the same name. You can use the Service Description field to distinguish between the services.

If you have multiple Cisco Unified Communications Manager servers in a cluster environment, repeat this step on each Cisco Unified CM server.

9. Optional: Configure security for Visual Voicemail. Obtain a certificate for both the primary and secondary Cisco Unity servers and add both certificates to the Cisco Unified CM server and to the IP phones. See the "Configuring Security for Cisco Visual Voicemail" chapter.

If you have multiple Cisco Unity failover pairs networked together, obtain a certificate for Visual Voicemail on each Cisco Unity server, including all primary and secondary servers. Add all of the certificates to the Cisco Unified CM server and to the IP phones.

If you have multiple Cisco Unified Communications Manager servers in a cluster environment, you must add the certificates for both the Cisco Unity servers to each Cisco Unified CM server in the cluster.

10. Install Visual Voicemail on the phones. See the "Installing Cisco Visual Voicemail on Phones" chapter.

11. Optional: Customize the keypad mapping file that defines which keys perform which actions when users press numbers on the phone keypad. See the "Configuring Key Mappings in Visual Voicemail" chapter.

12. Provide information about Visual Voicemail to users. See the "Information to Provide to Users" chapter.