Configuring Cisco Visual Voicemail on the Cisco Unified Communications System
This chapter contains the procedures for configuring Cisco Visual Voicemail on the Cisco Unified Communications System. It includes tasks that need to be performed on Cisco Unified Communications Manager server(s) and on the voicemail server(s), which could be either Cisco Unity Connection or Cisco Unity.
Enabling Web Access on Phones
Revised October 08, 2012
For Visual Voicemail to function correctly on 7900 series Phones, the phones must have web access enabled. However, for Visual Voicemail 7.x MIDlet, if web access is not enabled for 7900 series phones the user will need to enter the Directory Number as it will not be updated automatically.To enable web access on the phones in your system, you can use the following Cisco Unified Communications Manager windows:
- Device Configuration window
- Common Phone Profile window
- Enterprise Phone Configuration window
Note It is not necessary to enable "Phone Web Access" for using Visual VoiceMail feature. Phone Web Access is required only if you need to access phone logs.
For more information about these windows, see the Cisco Unified Communications Manager Administration Guide at http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_maintenance_guides_list.html.
For more information about web access, see the Cisco Unified Communications Manager Security Guide at the same URL.
How to Create a Line Group and Hunt List or Route Group and Route List (Cisco Unity Connection Clusters Only)
Creating a Line Group or Route Group (Cisco Unity Connection Clusters Only)
If you are configuring Visual Voicemail in a cluster of publisher and subscriber Cisco Unity Connection servers in an active-active configuration, you must have a line group or route group for each Cisco Unity Connection server. (Line groups are necessary if Cisco Unified Communications Manager and Connection are configured to work together in a SCCP integration. Route groups are necessary if Cisco Unified Communications Manager and Connection are configured to work together in a SIP integration.)
For SCCP integrations, 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.
To view a list of ports and associated directory numbers, select Advanced Features > Voice Mail > Cisco Voice Mail Port in Cisco Unified Communications Manager Administration.
For SIP integrations, the devices that are listed for the SIP trunks for the publisher server must be added to the route group for the publisher server. Similarly, the devices that are listed for the SIP trunks for the subscriber server must be added to the route group for the subscriber server.
To view a list of SIP trunks and associated devices, select Device > Trunk in Cisco Unified Communications Manager Administration.
For more information about how to create a line group or route group, see the Cisco Unified Communications Manager Administration Guide at the following URL:
http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_maintenance_guides_list.html
Creating a Hunt List or Route List (Cisco Unity Connection Clusters Only)
If you are configuring Visual Voicemail in a cluster of publisher and subscriber Cisco Unity Connection servers in an active-active configuration, you must have a unique hunt list or route list configured for each Cisco Unity Connection server. (Hunt lists are necessary if Cisco Unified Communications Manager and Connection are configured to work together in a SCCP integration. Route lists are necessary if Cisco Unified Communications Manager and Connection are configured to work together in a SIP integration.)
These hunt lists and route lists should be configured differently than the hunt lists and route lists you have configured for the audio voicemail service.
For SCCP integrations, 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. Do not add the line group for the subscriber server to the hunt list of the publisher server. And do not add the line group of the publisher to the hunt list of the subscriber server.
For SIP integrations, you must add the route group for the publisher server to the route list for the publisher server. Similarly, you must add the route group for the subscriber server to the route list for the subscriber server. Do not add the route group for the subscriber server to the route list of the publisher server. And do not add the route group of the publisher to the route list of the subscriber server.
For more information about how to create a hunt list or route list, see the Cisco Unified Communications Manager Administration Guide at the following URL:
http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_maintenance_guides_list.html
Creating a Voicemail Pilot Number for Visual Voicemail
When users start Visual Voicemail, it automatically uses a port to open a line and establishes a reverse TRAP connection to the voicemail server. On the Cisco Unified Communications Manager server, you must create a voicemail pilot number for the reverse TRAP connection to be successful. This is in addition to the voicemail pilot that you may already have configured for the audio voicemail service.
Procedure
Step 1 In Cisco Unified Communications Manager Administration, select Advanced Features > Voice Mail > Voice Mail Pilot.
Step 2 Select Add New.
Step 3 Enter a directory number for the voicemail pilot for Visual Voicemail in the Voice Mail Pilot Number field.
Step 4 Select the same calling search space that you use for the audio voicemail system from the Calling Search Space list box.
Step 5 (Optional) Enter a description in the Description field, for example, enter Visual Voicemail Reverse TRAP Pilot.
Step 6 Select Save.
Creating a Hunt Pilot or Route Pattern for the Visual Voicemail Pilot Number
When users start Visual Voicemail, it automatically uses a port to open a line and establishes a reverse TRAP connection to the voicemail server. On the Cisco Unified Communications Manager server, you must create a hunt pilot or route pattern for the reverse TRAP connection to be successful. This is in addition to the hunt pilot or route pattern that you may already have configured for the audio voicemail service.
A hunt pilot is necessary if Cisco Unified Communications Manager and Connection are configured to work together in a SCCP integration. A route pattern is necessary if Cisco Unified Communications Manager and Connection are configured to work together in a SIP integration.
See the applicable section:
Creating a Hunt Pilot for the Visual Voicemail Pilot Number
A hunt pilot is necessary if Cisco Unified Communications Manager and Connection are configured to work together in a SCCP integration. A hunt pilot is a string of digits and a set of associated digit manipulations that route calls to a hunt list.
For more information about hunt pilots, see the Cisco Unified Communications Manager Administration Guide at the following URL:
http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_maintenance_guides_list.html
Procedure
Step 1 In Cisco Unified Communications Manager Administration, select Call Routing > Route/Hunt > Hunt Pilot.
Step 2 Select Add New.
Step 3 Enter the number of the Visual Voicemail pilot number in the Hunt Pilot field.
Step 4 (Optional) Enter a description in the Description field, for example, enter Visual Voicemail Reverse TRAP Hunt Pilot.
Step 5 Cisco Unity Connection clusters only: In the Hunt List list box, select the same hunt list that is associated with the applicable Connection server.
All other voicemail configurations: In the Hunt List list box, select the same hunt list that is associated with the audio voicemail service.
Step 6 Select Save.
Step 7 Call the Visual Voicemail pilot number. If you hear prompts from the voicemail system, you have successfully created the Visual Voicemail pilot number and hunt pilot.
Creating a Route Pattern for the Visual Voicemail Pilot Number
A route pattern is necessary if Cisco Unified Communications Manager and Connection are configured to work together in a SIP integration. A route pattern is a string of digits and a set of associated digit manipulations that route calls to a route list.
For more information about route patterns, see the Cisco Unified Communications Manager System Guide at the following URL:
http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_maintenance_guides_list.html
Procedure
Step 1 In Cisco Unified Communications Manager Administration, select Call Routing > Route/Hunt > Route Pattern.
Step 2 Select Add New.
Step 3 Enter the number of the Visual Voicemail pilot number in the Route Pattern field.
Step 4 (Optional) Enter a description in the Description field, for example, enter Visual Voicemail Reverse TRAP Route Pattern.
Step 5 Cisco Unity Connection clusters only: In the Gateway/Route List list box, select the route list that is associated with the applicable Connection server.
All other voicemail configurations: In the Gateway/Route List list box, select the route list for the audio voicemail service.
Step 6 Select Save.
Step 7 Call the Visual Voicemail pilot number. If you hear prompts from the voicemail system, you have successfully created the Visual Voicemail pilot number and route pattern.
Configuring Voicemail Web Service on Cisco Unity Connection
When you install Cisco Unity Connection, the voicemail web service is automatically installed. You must configure several voicemail web service settings in Cisco Unity Connection.
Procedure
Step 1 In Cisco Unity Connection Administration, select System Settings > Advanced > Connection Administration.
Step 2 Enter values for the following Voice Mail Web Service settings:
|
|
Applications Can Cache the Cisco Unity Connection Password |
Select this option to enable Visual Voicemail to cache the extension and numeric password of users. This is required if you want to enable users to use the sign-in option Keep me signed in. |
Pilot Number for Voice Mail |
Enter the directory number of the audio voicemail service. |
Session Timeout (in Seconds) |
Ensure that this value is set to 300. |
Pilot Number for TRAP Connections |
Enter the Visual Voicemail reverse TRAP pilot number. |
Step 3 Select Save.
Configuring a Reverse TRAP Rule on Cisco Unity Connection
Procedure
Step 1 Select Call Management > Call Routing > Direct Routing Rules in Cisco Unity Connection Administration.
Step 2 Select Add New.
Step 3 Enter a name for the rule in the Display Name field. For example, enter Visual Voicemail Reverse TRAP Rule.
Step 4 Select Save to save the name.
Step 5 Follow these steps to create a routing rule condition:
a. Select Add New in the Routing Rule Conditions section.
b. Select the Dialed Number option.
c. Select Equals from the list box of condition operators.
d. Enter the number of the Visual Voicemail pilot number in the value field.
e. Select Save to save the condition.
Step 6 From the Edit menu, select Edit Direct Routing Rule.
Step 7 In Send Caller To section, select the Conversation option select Reverse TRAP from the list box.
Step 8 Select Save to save the rule.
Step 9 To test that the revers TRAP rule, call the Visual Voicemail pilot number. If you hear five or six seconds of silence followed by termination of the call, you have successfully created the reverse TRAP rule.
Configuring a Message Indicator Count on Cisco Unity Connection
Procedure
Step 1 In Cisco Unity Connection Administration, select Telephony Integrations > Phone System.
Step 2 Search for the phone system in the Phone Systems window.
Step 3 Select the applicable phone system.
Step 4 Check Send Message Counts.
Step 5 Select Save.
Balancing Web Service Requests Between Connection Servers (Cisco Unity Connection Clusters Only)
To balance web service requests equally between two Cisco Unity Connection servers in an active-active cluster configuration, 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.
How to Add the Visual Voicemail Service in Cisco Unified Communications Manager
Service Parameters for Visual Voicemail
To update a Visual Voicemail service parameter, you must delete the Visual Voicemail service then recreate the service. Therefore, it is best to decide which service parameters you want to use before you create the Visual Voicemail service.
You can use the following parameters with the Visual Voicemail service:
|
|
call_connect_delay |
Specifies in milliseconds the delay that Visual Voicemail allows for a call to be automatically answered and connected to the voicemail server. This call is then used to play or record a message. The default value is 1000, but this value might need to be adjusted if there is significant network latency between the IP Phones running Visual Voicemail and the voicemail server. If this value is not large enough, then calls created by Visual Voicemail to play or record messages might be disconnected after five or six seconds. |
log_level |
Specifies the degree of detail that you want to appear for the phones that subscribe to the Visual Voicemail service. You can enter the following values: info, error, debug. Default value: info. |
tui_key_mappings_file_url |
(Optional) Specifies the HTTP location of the key mappings file. For more information about this parameter, see the “Configuring Key Mappings in Visual Voicemail” chapter. |
tui_key_mappings_file_version |
(Optional) Specifies the version number of the key mappings file. For more information about this parameter, see the “Configuring Key Mappings in Visual Voicemail” chapter. |
use_secure_https_connection |
(Optional) Specifies whether to implement security in the Visual Voicemail service, that is whether to use HTTPS instead of HTTP to transmit voice messages. Set the value of this parameter to 1 to implement security in the Visual Voicemail service. For more information about security, see the “Configuring Security for Cisco Visual Voicemail” chapter. |
voicemail_server |
Specifies the hostname of the voicemail server. |
Related Topics
Adding the Visual Voicemail Service
Procedure
Step 1 In Cisco Unified Communications Manager Administration, select Device > Device Settings > Phone Services.
Step 2 Select Add New.
Step 3 Enter information in the IP Phone Services Configuration window, as follows:
|
|
Service Name |
Enter VisualVoicemail Note that there is no space between “Visual” and “Voice” in the service name. |
ASCII Service Name |
Enter a name for the service in ASCII characters. This name is displayed on a phone if the phone cannot display Unicode characters. |
Service URL |
Enter the following URL: http://<voicemail server info> /midlets/VisualVoicemail/VisualVoicemail.jad where <voicemail server info> is the IP address or host name or DNS alias of voice mail server. |
Service Category |
Select Java MIDlet. |
Service Type |
Select Messages to associate the service with the Messages button on the phone. |
Service Vendor |
Enter Cisco |
Service Version |
Leave this field blank. |
Enable |
Select this to enable the service. |
Enterprise Subscription |
Do not select this. This method of installing the Visual Voicemail service on phones is suitable for only the most simple phone systems. |
Step 4 Select Save.
Step 5 Select New Parameter to add a parameter to the service.
|
|
Parameter Name |
Enter the following text in this field: voicemail_server |
Parameter Display Name |
Enter a name for the parameter. This name is used in the Cisco Unified Communications Manager user interface. For example, enter Voicemail server. |
Default Value |
Cisco Unity Connection only: If you have a Cisco Unity Connection cluster, enter the cluster DNS alias. Otherwise, enter the hostname of the Cisco Unity Connection server. Cisco Unity only: Enter the hostname of the primary server. This value is displayed to administrators when they subscribe phones to this service. When a user signs in to Visual Voicemail, the hostname of any partner server that is available is cached by the Visual Voicemail MIDlet for use during failover. For this reason, only one hostname is needed for this parameter. |
Parameter Description |
Enter a description. For example, enter Hostname of voicemail server. |
Parameter is Required |
Select this option. |
Parameter is a Password |
Do not select this option. |
For more information about service administration, see Cisco Unified Communications Manager System Guide and Cisco Unified Communications Manager Administration Guide at the following URL:
http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_maintenance_guides_list.html
Step 6 Select Save.
Step 7 Select Add New to add another parameter to the service.
|
|
Parameter Name |
Enter the following text in this field: call_connect_delay |
Parameter Display Name |
Enter a name for the parameter. For example, enter Call Connect Delay. |
Default Value |
Enter 1000. |
Parameter Description |
Enter a description. For example, enter Default call connect delay. |
Parameter is Required |
Select this option. |
Parameter is a Password |
Do not select this option. |
Step 8 Select Save.
Step 9 Select Add New to add another parameter to the service.
|
|
Parameter Name |
Enter the following text in this field: log_level |
Parameter Display Name |
Enter a name for the parameter. For example, enter Log Level. |
Default Value |
Enter the following text in this field: info |
Parameter Description |
Enter a description. For example, enter Level of logging. |
Parameter is Required |
Select this option. |
Parameter is a Password |
Do not select this option. |
Step 10 Select Save And Close.