Home | Skip to Content | Skip to Search | Skip to Navigation | Skip to Footer |
Worldwide [change] |Register |About Cisco
Guest

Hierarchical Navigation

Cisco Unity Connection

Cisco Unified CallManager 4.3 Integration Guide for Cisco Unity Connection 1.1

Downloads

Table Of Contents

Cisco Unified CallManager 4.3 Integration Guide for Cisco Unity Connection 1.1

Integration Tasks

Task List to Create the Integration

Task List to Change the Number of Voice Messaging Ports

Task List to Add a Cisco Unified CallManager Express Server to a Cisco Unified CallManager Phone System Integration

Requirements

Integration Description

Call Information

Integration Functionality

Integrations with Multiple Phone Systems

Planning How the Voice Messaging Ports Will Be Used by Cisco Unity Connection

Programming the Cisco Unified CallManager Phone System

Creating a New Integration with the Cisco Unified CallManager Phone System

Setting Up Cisco Unified CallManager Authentication and Encryption with Cisco Unity Connection

Testing the Integration

(Multiple Integrations Only) Adding New User Templates

Changing the Number of Voice Messaging Ports

Adding a Cisco Unified CallManager Express Server to a Cisco Unified CallManager Phone System Integration


Appendix: Cisco Unified CallManager Authentication and Encryption of Cisco Unity Connection Voice Messaging Ports

Cisco Unified CallManager Security Features

Functional Overview

Security Mode Settings in Cisco Unity Connection


Appendix: Documentation and Technical Assistance

Conventions

Obtaining Documentation, Obtaining Support, and Security Guidelines


Cisco Unified CallManager 4.3 Integration Guide for Cisco Unity Connection 1.1

Published May 14, 2007

This document provides instructions for integrating the Cisco Unified CallManager phone system with Cisco Unity Connection.

Note If you are configuring MWI relay across trunks in a distributed phone system, you must refer to the Cisco Unified CallManager documentation for requirements and instructions. Configuring MWI relay across trunks does not involve Cisco Unity Connection settings.

Integration Tasks

Before doing the following tasks to integrate Cisco Unity Connection with the Cisco Unified CallManager phone system, confirm that the Cisco Unity Connection server is ready for the integration by completing the applicable tasks in the Cisco Unity Connection Installation Guide.

The following task lists describe the process for creating and changing integrations.

Task List to Create the Integration

Use the following task list to set up a new integration with the Cisco Unified CallManager phone system. If you are installing a new Cisco Unity Connection server by using the Cisco Unity Connection Installation Guide, you may have already completed some of the following tasks.

1. Review the system and equipment requirements to confirm that all phone system and Cisco Unity Connection server requirements have been met. See the "Requirements" section.

2. Plan how the voice messaging ports will be used by Cisco Unity Connection. See the "Planning How the Voice Messaging Ports Will Be Used by Cisco Unity Connection" section.

3. Program Cisco Unified CallManager. See the "Programming the Cisco Unified CallManager Phone System" section.

4. Create the integration. See the "Creating a New Integration with the Cisco Unified CallManager Phone System" section.

Note An additional Cisco Unified CallManager cluster can be added by creating a new phone system integration through the Phone System Integration Wizard. Each Cisco Unified CallManager cluster is a separate phone system integration.

5. Test the integration. See the "Testing the Integration" section.

6. If this integration is a second or subsequent integration, add the applicable new user templates for the new phone system. See the (Multiple Integrations Only) Adding New User Templates.

Task List to Change the Number of Voice Messaging Ports

Use the following task list to change the number of voice messaging ports for an integration after it has been created.

1. Change the number of voice messaging ports in Cisco Unified CallManager Administration and in Cisco Unity Connection Administration. See the "Changing the Number of Voice Messaging Ports" section.

Task List to Add a Cisco Unified CallManager Express Server to a Cisco Unified CallManager Phone System Integration

Use the following task list to add a Cisco Unified CallManager Express server to a Cisco Unified CallManager cluster.

1. Confirm that the Cisco Unified CallManager Express server meets the requirements for integrating with Cisco Unity Connection. Refer to the applicable Cisco Unified CallManager Express integration guide at http://www.cisco.com/en/US/products/ps6509/products_installation_and_configuration_guides_list.html.

2. Add the Cisco Unified CallManager Express server to a new port group in the Cisco Unified CallManager phone system integration. See "Adding a Cisco Unified CallManager Express Server to a Cisco Unified CallManager Phone System Integration" section.

Requirements

The Cisco Unified CallManager integration supports configurations of the following components:

Phone System

•A Cisco IP telephony applications server consisting of Cisco Unified CallManager 4.2(x), running on a Cisco Media Convergence Server (MCS) or customer-provided server meeting approved Cisco configuration standards.

•IP phones for the Cisco Unified CallManager extensions.

•A LAN connection in each location where you will plug an IP phone into the network.

•For multiple Cisco Unified CallManager clusters, the capability for users to dial an extension on another Cisco Unified CallManager cluster without having to dial a trunk access code or prefix.

Cisco Unity Connection Server

•The applicable version of Cisco Unity Connection. For details on compatible versions of Cisco Unity Connection, refer to the Compatibility Matrix: Cisco Unity Connection, the Cisco Unity-CM TSP, Cisco Unified CallManager, and Cisco Unified CallManager Express at http://www.cisco.com/en/US/products/ps6509/products_device_support_tables_list.html.

•Cisco Unity Connection installed and ready for the integration, as described in the Cisco Unity Connection Installation Guide at http://www.cisco.com/en/US/products/ps6509/prod_installation_guides_list.html.

•The applicable Cisco Unity-CM TSP, installed. For details on compatible versions of the TSP, refer to the Compatibility Matrix: Cisco Unity Connection, the Cisco Unity-CM TSP, Cisco Unified CallManager, and Cisco Unified CallManager Express at http://www.cisco.com/en/US/products/ps6509/products_device_support_tables_list.html.

•A license that enables the appropriate number of voice messaging ports.

Integration Description

The Cisco Unified CallManager integration uses the LAN to connect Cisco Unity Connection and the phone system. The gateway provides connections to the PSTN. Figure 1 shows the connections.

Figure 1 Connections Between the Phone System and Cisco Unity Connection

Call Information

The phone system sends the following information with forwarded calls:

•The extension of the called party

•The extension of the calling party (for internal calls) or the phone number of the calling party (if it is an external call and the system uses caller ID)

•The reason for the forward (the extension is busy, does not answer, or is set to forward all calls)

Cisco Unity Connection uses this information to answer the call appropriately. For example, a call forwarded to Cisco Unity Connection is answered with the personal greeting of the user. If the phone system routes the call to Cisco Unity Connection without this information, Cisco Unity Connection answers with the opening greeting.

Integration Functionality

The Cisco Unified CallManager integration with Cisco Unity Connection provides the following features:

•Call forward to personal greeting

•Call forward to busy greeting

•Caller ID

•Easy message access (a user can retrieve messages without entering an ID; Cisco Unity Connection identifies a user based on the extension from which the call originated; a password may be required)

•Identified subscriber messaging (Cisco Unity Connection automatically identifies a user who leaves a message during a forwarded internal call, based on the extension from which the call originated)

•Message waiting indication (MWI)

The functionality of this integration may be affected by the issues described below.

Use of Cisco Unified Survivable Remote Site Telephony (SRST) Router

When a Cisco Unified Survivable Remote Site Telephony (SRST) router is part of the network and the Cisco Unified SRST router takes over call processing functions from Cisco Unified CallManager (for example, because the WAN link is down), phones at a branch office can continue to function. In this situation, however, the integration features have the following limitations:

•Call forward to busy greeting—When the Cisco Unified SRST router uses FXO/FXS connections to the PSTN and a call is forwarded from a branch office to Cisco Unity Connection, the busy greeting cannot play.

•Call forward to internal greeting—When the Cisco Unified SRST router uses FXO/FXS connections to the PSTN and a call is forwarded from a branch office to Cisco Unity Connection, the internal greeting cannot play. Because the PSTN provides the calling number of the FXO line, the caller is not identified as a user.

•Call transfers—Because an access code is needed to reach the PSTN, call transfers from Cisco Unity Connection to a branch office will fail.

•Identified user messaging—When the Cisco Unified SRST router uses FXO/FXS connections to the PSTN and a user at a branch office leaves a message or forwards a call, the user is not identified. The caller appears as an unidentified caller.

•Message waiting indication—MWIs are not updated on branch office phones, so MWIs will not correctly reflect when new messages arrive or when all messages have been listened to. We recommend resynchronizing MWIs after the WAN link is reestablished.

•Routing rules—When the Cisco Unified SRST router uses FXO/FXS connections to the PSTN and a call arrives from a branch office to Cisco Unity Connection (either a direct or forwarded call), routing rules will fail.

When the Cisco Unified SRST router uses PRI/BRI connections, the caller ID for calls from a branch office to Cisco Unity Connection may be the full number (exchange plus extension) provided by the PSTN and therefore may not match the extension of the Cisco Unity Connection user. If this is the case, you can let Cisco Unity Connection recognize the caller ID by using alternate extensions.

Redirected Dialed Number Information Service (RDNIS) needs to be supported when using SRST.

For information on setting up Cisco Unified SRST routers, refer to the "Integrating Voice Mail with Cisco Unified SRST" section of the Cisco Unified SRST System Administrator Guide at http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122limit/122z/122zj15/index.htm.

Impact of Non-Delivery of RDNIS on Voice Mail Calls Routed via AAR

RDNIS needs to be supported when using Automated Alternate Routing (AAR).

AAR can route calls over the PSTN when the WAN is oversubscribed. However, when calls are rerouted over the PSTN, RDNIS can be affected. Incorrect RDNIS information can affect voice mail calls that are rerouted over the PSTN by AAR when Cisco Unity Connection is remote from its messaging clients. If the RDNIS information is not correct, the call will not reach the voice mail box of the dialed user but will instead receive the automated attendant prompt, and the caller might be asked to reenter the extension number of the party they wish to reach. This behavior is primarily an issue when the telephone carrier is unable to ensure RDNIS across the network. There are numerous reasons why the carrier might not be able to ensure that RDNIS is properly sent. Check with your carrier to determine whether it provides guaranteed RDNIS delivery end-to-end for your circuits. The alternative to using AAR for oversubscribed WANs is simply to let callers hear reorder tone in an oversubscribed condition.

(Cisco Unified CallManager 4.2(3) and Later 4.2(x) Releases Only) Impact of the Original Calling Party on Transfer Feature

For Cisco Unified CallManager 4.2(3) and later 4.2(x) releases, when the Original Calling Party on Transfer feature is enabled, the following impacts occur:

•Calls that Cisco Unity Connection transfers to a phone can display the original calling party information rather than the calling party information of the Cisco Unity Connection voice messaging port.

•Live reply will not function correctly.

•Transfers to subscribers on other networked Cisco Unity Connection systems will not succeed.

•Cross-box log in will not succeed.

To enable the Original Calling Party on Transfer feature, in Cisco Unified CallManager Administration, on the Service Parameters Configuration page for the Cisco Unified CallManager server, you must set the Display Original Calling Number on Transfer from Cisco Unity service parameter to True.

Note that if the Original Calling Party on Transfer feature is enabled on Cisco Unified CallManager, a transfer loop can occur when the following happens:

1. Caller A calls user B.

2. User B has set the extension to forward calls to extension C. So Cisco Unity Connection transfers the call to extension C and the call displays the number of caller A.

3. Extension C rings and is not answered.

4. Because the calling number of caller A is displayed, Cisco Unity Connection returns the call to user B, and a transfer loop is created.

To avoid a transfer loop under this condition, users must avoid forwarding calls to extensions that will not be answered.

Also note that if the Original Calling Party on Transfer feature is disabled on Cisco Unified CallManager, the call can be disconnected when the following happens:

1. Caller A calls user B.

2. User B has set the extension to forward calls to extension C. So Cisco Unity Connection transfers the call to extension C and the call displays the number of the Cisco Unity Connection voice messaging port that is handling the call.

3. Extension C rings and is not answered.

4. Because the calling number of a voice messaging port is displayed, Cisco Unity Connection disconnects the call as a forwarded notification call.

To avoid disconnecting calls under this condition, users must avoid forwarding calls to extensions that will not be answered.

Integrations with Multiple Phone Systems

Cisco Unity Connection can be integrated with multiple phone systems at one time. For information on and instructions for integrating Cisco Unity Connection with multiple phone systems, refer to the Multiple Phone System Integration Guide at http://www.cisco.com/en/US/products/ps6509/products_installation_and_configuration_guides_list.html.

Planning How the Voice Messaging Ports Will Be Used by Cisco Unity Connection

Before programming the phone system, you need to plan how the voice messaging ports will be used by Cisco Unity Connection. The following considerations will affect the programming for the phone system (for example, setting up the hunt group or call forwarding for the voice messaging ports):

•The number of voice messaging ports installed.

•The number of voice messaging ports that will answer calls.

•The number of voice messaging ports that will only dial out, for example, to send message notification, to set message waiting indicators (MWIs), and to make telephone record and playback (TRAP) connections.

The following table describes the voice messaging port settings in Cisco Unity Connection that can be set on Telephony Integrations > Port of Cisco Unity Connection Administration.

Table 1 Settings for the Voice Messaging Ports 

Field
Considerations

Enabled

Check this check box to enable the port. The port is enabled during normal operation.

Uncheck this check box to disable the port. When the port is disabled, calls to the port get a ringing tone but are not answered. Typically, the port is disabled only by the installer during testing.

Extension

Enter the extension for the port as assigned on the phone system.

Answer Calls

Check this check box to designate the port for answering calls. These calls can be incoming calls from unidentified callers or from users.

Perform Message Notification

Check this check box to designate the port for notifying users of messages. Assign Perform Message Notification to the least busy ports.

Send MWI Requests

Check this check box to designate the port for turning MWIs on and off. Assign Send MWI Requests to the least busy ports.

Allow TRAP Connections

Check this check box so that users can use the port for recording and playback through the phone in Cisco Unity Connection web applications. Assign Allow TRAP Connections to the least busy ports.

Outgoing Hunt Order

Enter the priority order in which Cisco Unity Connection will use the ports when dialing out (for example, if the Perform Message Notification, Send MWI Requests, or Allow TRAP Connections check box is checked). The highest numbers are used first. However, when multiple ports have the same Outgoing Hunt Order number, Cisco Unity Connection will use the port that has been idle the longest.

Security Mode

Click the applicable security mode:

•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 CallManager 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 CallManager 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 on this port because they will be connected to Cisco Unified CallManager through an authenticated TLS port, and the call-signaling messages will be encrypted. In addition, the media stream will be encrypted.


The Number of Voice Messaging Ports to Install

The number of voice messaging ports to install depends on numerous factors, including:

•The number of calls Cisco Unity Connection will answer when call traffic is at its peak.

•The expected length of each message that callers will record and that users will listen to.

•The number of users.

•The number of ports that will be set to dial out only.

•The number of calls made for message notification.

•The number of MWIs that will be activated when call traffic is at its peak.

•The number of TRAP connections needed when call traffic is at its peak. (TRAP connections are used by Cisco Unity Connection web applications to play back and record over the phone.)

•The number of calls that will use the automated attendant and call handlers when call traffic is at its peak.

It is best to install only the number of voice messaging ports that are needed so that system resources are not allocated to unused ports.

The Number of Voice Messaging Ports That Will Answer Calls

The calls that the voice messaging ports answer can be incoming calls from unidentified callers or from users. Typically, the voice messaging ports that answer calls are the busiest.

You can set voice messaging ports to both answer calls and to dial out (for example, to send message notifications). However, when the voice messaging ports perform more than one function and are very active (for example, answering many calls), the other functions may be delayed until the voice messaging port is free (for example, message notifications cannot be sent until there are fewer calls to answer). For best performance, dedicate certain voice messaging ports for only answering incoming calls, and dedicate other ports for only dialing out. Separating these port functions eliminates the possibility of a collision, in which an incoming call arrives on a port at the same time that Cisco Unity Connection takes the port off-hook to dial out.

The Number of Voice Messaging Ports That Will Only Dial Out, and Not Answer Calls

Ports that will only dial out and will not answer calls can do one or more of the following:

•Notify users by phone, pager, or e-mail of messages that have arrived.

•Turn MWIs on and off for user extensions.

•Make a TRAP connection so that users can use the phone as a recording and playback device in Cisco Unity Connection web applications.

Typically, these voice messaging ports are the least busy ports.

Caution In programming the phone system, do not send calls to voice messaging ports in Cisco Unity Connection 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 Send MWI Requests, do not send calls to it.

Preparing for Programming the Phone System

Record your decisions about the voice messaging ports to guide you in programming the phone system.

Programming the Cisco Unified CallManager Phone System

After Cisco Unified CallManager software is installed, do the following procedures in the order given.

To Add Partitions and a Calling Search Space to Contain the Voice Mail Ports

Step 1 In the Cisco Unified CallManager Administration, click Route Plan > Class of Control > Partition.

Step 2 On the Find and List Partitions page, click Add a New Partition.

Step 3 On the Partition Configuration page, enter the name and description you want for the partition that will contain all voice mail port directory numbers. For example, enter "VMRestrictedPT, Partition for voice mail port directory numbers."

Step 4 Click Insert.

Step 5 Click Add a New Partition.

Step 6 Enter the name and description you want for the partition that will contain the hunt pilot, which will be the voice mail pilot number. For example, enter "VMPilotNumberPT, Partition for the voice mail pilot number."

Step 7 Click Insert.

Step 8 Click Route Plan > Class of Control > Calling Search Space.

Step 9 On the Find and List Calling Search Spaces page, click Add a New Calling Search Space.

Step 10 On the Calling Search Space Configuration page, in the Calling Search Space Name field, enter a name for the calling search space that will include the partition created in Step 2 through Step 4. For example, enter "VMRestrictedCSS."

Step 11 Optionally, in the Description field, enter a description of the calling search space. For example, enter "Voice mail port directory numbers."

Step 12 In the Available Partitions field, double-click the name of the partition created in Step 2 through Step 4. For example, double-click "VMRestrictedPT."

The name of the partition appears in the Selected Partitions field.

Step 13 Click Insert.

Step 14 Click Back to Find/List Calling Search Spaces.

Step 15 On the Find and List Calling Search Spaces page, click Find.

Step 16 Click the name of the calling search space that is used by user phones.

Step 17 On the Calling Search Space Configuration page, in the Available Partitions field, double-click the name of the partition created in Step 5 through Step 7. For example, double-click "VMPilotNumberPT."

Caution If the partition that contains the hunt pilot (which will be the voice mail pilot number) is not in the calling search space that is used by user phones, the phones will not be able to dial the Cisco Unity Connection server.

Step 18 Click Update.

Step 19 Repeat Step 16 through Step 18 for each remaining calling search space that needs to access Cisco Unity Connection.

To Add a Device Pool for the Voice Mail Ports

Step 1 In the Cisco Unified CallManager Administration, click System > Device Pool.

Step 2 On the Find and List Device Pools page, click Add a New Device Pool.

Step 3 On the Device Pool Configuration page, enter the following device pool settings.

Table 2 Settings for the Device Pool Configuration Page 

Field
Setting

Device Pool Name

Enter Cisco Unity Connection Voice Mail Ports or other description for this device pool.

Cisco Unified CallManager Group

Click the Cisco Unified CallManager group to assign to the voice mail ports in this device pool.

Date/Time Group

Click the date/time group to assign to the voice mail ports in this device pool.

Region

Click the Cisco Unified CallManager region to assign to the voice mail ports in this device pool.

Softkey Template

Click the softkey template to assign to the voice mail ports in this device pool.

SRST Reference

If applicable, click the survivable remote site telephony (SRST) reference to assign to the voice mail ports in this device pool.

Network Hold MOH Source

Click None.

User Hold MOH Audio Source

Click None.


Step 4 Click Insert.

In the following procedure, add a voice mail port to Cisco Unified CallManager for each voice mail port that you will connect to Cisco Unity Connection.

To Add Voice Mail Ports to Cisco Unified CallManager

Step 1 In the Cisco Unified CallManager Administration, click Feature > Voice Mail > Cisco Voice Mail Port Wizard.

Step 2 On the What Would You Like to Do page, click Create a New Cisco Voice Mail Server and Add Ports to It, and click Next.

Step 3 On the Cisco Voice Mail Server page, the name of the voice mail server appears. We recommend that you accept the default name for the voice mail server. If you must use a different name, however, the name must have no more than nine characters.

The voice mail server name must match the Device Name Prefix field in Cisco Unity Connection on the Port Group Basics page for the voice messaging ports.

Step 4 Click Next.

Step 5 On the Cisco Voice Mail Ports page, click the number of voice mail ports that you want to add (which must not be more voice mail ports than the Cisco Unity Connection license enables), then click Next.

If you will integrate Cisco Unity Connection with multiple clusters of Cisco Unified CallManager, the number you enter here cannot bring the total number of ports on all clusters integrated with Cisco Unity Connection to more than the number of ports enabled by the Cisco Unity Connection license.

Step 6 On the Cisco Voice Mail Device Information page, enter the following voice mail device settings.

Table 3 Settings for the Voice Mail Device Information Page 

Field
Setting

Description

Enter Cisco Voice Mail Port or another description for the voice mail device.

Device Pool

Click the name of the device pool you created for the voice mail ports. For example, click Cisco Unity Connection Voice Mail Ports.

Calling Search Space

Click the name of a calling search space that allows calls to the user phones and any required network devices.

This calling search space must include partitions that contain all devices Cisco Unity Connection needs to access (for example, during call transfers, message notifications, and MWI activations).

Location

Accept the default of None.


Step 7 Click Next.

Step 8 On the Cisco Voice Mail Directory Numbers page, enter the following voice mail directory number settings.

Table 4 Settings for the Voice Mail Directory Numbers Page 

Field
Setting

Beginning Directory Number

Enter the extension number of the first voice mail port.

Partition

Click the name of the partition that you set up for all voice mail port directory numbers. For example, click "VMRestrictedPT."

Calling Search Space

Click the name of a calling search space that you set up to contain the partition with all voice mail port directory numbers, as set in Step 9 of the "To Add Partitions and a Calling Search Space to Contain the Voice Mail Ports" procedure. For example, click "VMRestrictedCSS."

Because this calling search space is not used by user phones, users are not able to dial the voice mail ports. However, users can dial the voice mail pilot number.

Display

Accept the default of Voicemail.

This text appears on the phone when the pilot number is dialed.

AAR Group

Click the automated alternate routing (AAR) group for the voice mail ports. The AAR group provides the prefix digits that are used to route calls that are otherwise blocked due to insufficient bandwidth. If you click None, no rerouting of blocked calls will be attempted.

External Number Mask

Leave this field blank, or specify the mask used to format caller ID information for external (outbound) calls. The mask can contain up to 50 characters. Enter the literal digits that you want to appear in the caller ID information, and enter X for each digit in the directory number of the device.

Device Security Mode

Click the security mode that you want to use for the voice mail ports. For details on the settings for Cisco Unified CallManager authentication and encryption of the voice mail ports, see the "Appendix: Cisco Unified CallManager Authentication and Encryption of Cisco Unity Connection Voice Messaging Ports" section.


Step 9 Click Next.

Step 10 On the Do You Want to Add These Directory Numbers to a Line Group page, click No, I Will Add Them Later, and click Next.

Step 11 On the Ready to Add Cisco Voice Mail Ports page, confirm that the settings for the voice mail ports are correct, and click Finish.

If the settings are not correct, click Back and enter the correct settings.

To Add Voice Mail Ports to Line Groups

Step 1 On the Cisco Voice Mail Port Wizard Results page, click Line Group.

You can also reach the line group pages by clicking Route Plan > Route/Hunt > Line Group in the Cisco Unified CallManager Administration.

Step 2 On the Find and List Line Groups page, click Add a New Line Group.

This line group will contain directory numbers for voice mail ports that will answer calls. Directory numbers for voice mail ports that will only dial out (for example, to set MWIs) must not be included in this line group.

Step 3 On the Line Group Configuration page, enter the following settings.

Table 5 Settings for the Line Group Configuration Page for Answering Ports 

Field
Setting

Line Group Name

Enter Cisco Unity Connection Answering Ports or another unique name for line groups.

RNA Reversion Timeout

Accept the default of 10.

Distribution Algorithm

Accept the default of Top Down.

No Answer

Accept the default of Try Next Member; Then, Try Next Group in Hunt List.

Busy

Accept the default of Try Next Member; Then, Try Next Group in Hunt List.

Not Available

Accept the default of Try Next Member; Then, Try Next Group in Hunt List.


Step 4 In the Route Partition list, click the name of the partition that you set up for all voice mail port directory numbers. For example, click "VMRestrictedPT."

Step 5 Click Find.

Step 6 In the Available DN/Route Partition list, click the first directory number of a voice mail port that will answer calls, and click Add to Line Group.

Caution The directory numbers in the Selected DN/Route Partition list must appear in numerical sequence with the lowest number on top.

Step 7 Repeat Step 6 for all remaining directory numbers of voice mail ports that will answer calls.

Caution Do not include directory numbers of voice mail ports that will only dial out (for example, to set MWIs).

Step 8 Click Insert.

Step 9 If you will have voice mail ports that will only dial out (will not answer calls), do Step 10 through Step 16.

Otherwise, skip the remaining steps in this procedure and continue on to the "To Add the Line Group to a Hunt List" procedure.

Step 10 Click Add New Line Group.

This line group will contain directory numbers for voice mail ports that will only dial out. Directory numbers for voice mail ports that answer calls must not be included in this line group.

Step 11 On the Line Group Configuration page, enter the following settings.

Table 6 Settings for the Line Group Configuration Page for Dial-Out Ports 

Field
Setting

Line Group Name

Enter Cisco Unity Connection Dial-Out Ports or another unique name.

RNA Reversion Timeout

Accept the default of 10.

Distribution Algorithm

Accept the default of Top Down.

No Answer

Click Stop Hunting.

Busy

Click Stop Hunting.

Not Available

Click Stop Hunting.


Step 12 In the Route Partition list, click the name of the partition that you set up for all voice mail port directory numbers. For example, click "VMRestrictedPT."

Step 13 Click Find.

Step 14 In the Available DN/Route Partition list, click the first directory number of a voice mail port that will only dial out, and click Add to Line Group.

Caution The directory numbers in the Selected DN/Route Partition list must appear in numerical sequence with the lowest number on top.

Step 15 Repeat Step 14 for all remaining voice mail ports that will only dial out.

Caution Do not include directory numbers of voice mail ports that will answer calls.

Step 16 Click Insert.

To Add the Line Group to a Hunt List

Step 1 In the Cisco Unified CallManager Administration, click Route Plan > Route/Hunt > Hunt List.

Step 2 On the Find and List Hunt Lists page, click Add a New Hunt List.

Step 3 On the Hunt List Configuration page, enter the following settings for the hunt list.

Table 7 Settings for the Hunt List Configuration Page for Answering Ports 

Field
Setting

Hunt List Name

Enter Cisco Unity Connection Answering Ports or another unique name for the hunt list.

Description

Enter Cisco Unity Connection ports that answer calls or another description.

Cisco Unified CallManager Group

Click Default or the name of the Cisco Unified CallManager group you are using.


Step 4 Click Insert.

Step 5 When alerted to add a line group to the hunt list, click OK.

Step 6 Under Hunt List Member Information, click Add Line Group.

Step 7 On the Hunt List Detail Configuration page, in the Line Group list, click the line group you created for the directory numbers of voice mail ports that will answer calls, then click Insert.

Caution In the hunt list, do not include line groups with voice mail ports that Cisco Unity Connection will use to dial out. Otherwise, the integration will not function correctly.

Step 8 When alerted that the line group has been inserted, click OK.

Step 9 On the Hunt List Configuration page, click Reset.

Step 10 When asked to confirm resetting the hunt list, click OK.

Step 11 When alerted that the hunt list has been reset, click OK.

To Add the Hunt List to a Hunt Pilot Number

Step 1 In the Cisco Unified CallManager Administration, click Route Plan > Route/Hunt > Hunt Pilot.

Step 2 On the Find and List Hunt Pilots page, click Add a New Hunt Pilot.

Step 3 On the Hunt Pilot Configuration page, enter the following settings for the hunt pilot.

Table 8 Settings for Hunt Pilot Configuration Page 

Field
Setting

Hunt Pilot

Enter the hunt pilot number for the voice mail ports. The hunt pilot number must be different from the extension numbers of the voice mail ports.

The hunt pilot number is the extension number that users enter to listen to their voice messages.

Partition

Click the name of the partition that you set up for the voice mail pilot number. For example, click "VMPilotNumberPT."

Description

Enter Cisco Unity Connection Hunt Pilot or another description.

Numbering Plan

Accept the default setting, or click the numbering plan that you have set up for your system.

Route Filter

Click None, or click the name of the route filter that you set up for your system.

MLPP Precedence

Accept the default setting, or click another setting.

Hunt List

Click the hunt list of voice mail ports that answer calls, which you set up in the "To Add the Line Group to a Hunt List" procedure.

Provide Outside Dial Tone

Uncheck the check box.


Step 4 Click Insert.

To Specify MWI Directory Numbers

Step 1 In the Cisco Unified CallManager Administration, click Feature > Voice Mail > Message Waiting.

Step 2 On the Find and List Message Waiting Numbers page, click Add a New Message Waiting Number.

Step 3 On the Message Waiting Configuration page, enter the following settings for turning MWIs on.

Table 9 Settings for Turning MWIs On 

Field
Setting

Message Waiting Number

Enter the unique extension that turns MWIs on.

Description

Enter DN to turn MWIs on or another description.

Message Waiting Indicator

Click On.

Partition

Click the name of the partition that you set up for the voice mail pilot number. For example, click "VMPilotNumberPT."

Calling Search Space

Click a calling search space that is used by user phones.


Step 4 Click Insert.

Step 5 Click Add a New Message Waiting Number.

Step 6 Enter the following settings for turning MWIs off.

Table 10 Settings for Turning MWIs Off 

Field
Setting

Directory Number

Enter the unique extension that turns MWIs off.

Description

Enter DN to turn MWIs off or another description.

Message Waiting Indicator

Click Off.

Partition

Click the name of the partition that you set up for the voice mail pilot number. For example, click "VMPilotNumberPT."

Calling Search Space

Click a calling search space that is used by user phones.


Step 7 Click Insert.

In the following procedure, you will add the voice mail pilot number, which is the extension that you dial to listen to your voice messages. Your Cisco IP phone automatically dials the voice mail pilot number when you press the Messages button.

To Add a Voice Mail Pilot Number for the Voice Mail Ports

Step 1 In the Cisco Unified CallManager Administration, click Feature > Voice Mail > Voice Mail Pilot.

Step 2 On the Find and List Voice Mail Pilots page, click Add a New Voice Mail Pilot.

Step 3 On the Voice Mail Pilot Configuration page, enter the following voice mail pilot number settings.

Table 11 Settings for the Voice Mail Pilot Configuration Page 

Field
Setting

Voice Mail Pilot Number

Enter the voice mail pilot number that users will dial to listen to their voice messages. This number must be the same as the hunt pilot number that you entered when adding voice mail ports earlier.

Description

Enter Cisco Unity Connection Pilot or another description.

Calling Search Space

Click the calling search space that includes partitions containing the user phones and the partition you set up for the voice mail pilot number.

Make This the Default Voice Mail Pilot for the System

Check this check box. When this check box is checked, this voice mail pilot number replaces the current default pilot number.


Step 4 Click Insert.

To Set Up the Voice Mail Profile

Step 1 In the Cisco Unified CallManager Administration, click Feature > Voice Mail > Voice Mail Profile.

Step 2 On the Find and List Voice Mail Profiles page, click Add a New Voice Mail Profile.

Step 3 On the Voice Mail Profile Configuration page, enter the following voice mail profile settings.

Table 12 Settings for the Voice Mail Profile Configuration Page 

Field
Setting

Voice Mail Profile Name

Enter a name to identify the voice mail profile.

Description

Enter Cisco Unity Connection Profile or another description.

Voice Mail Pilot

Click one of the following:

•The applicable voice mail pilot number that you defined on the Voice Mail Pilot Configuration page

•Use Default

Voice Mail Box Mask

When multitenant services are not enabled on Cisco Unified CallManager, leave this field blank.

When multitenant services are enabled, each tenant uses its own voice mail profile and must create a mask to identify the extensions (directory numbers) in each partition that is shared with other tenants. For example, one tenant can use a mask 972813XXXX, while another tenant can use the mask 214333XXXX. Each tenant also uses its own translation patterns for MWIs.

Make This the Default Voice Mail Profile for the System

Check this check box to make this voice mail profile the default.

When this check box is checked, this voice mail profile replaces the current default voice mail profile.


Step 4 Click Insert.

To Set Up the Voice Mail Server Service Parameters

Step 1 In the Cisco Unified CallManager Administration, click Service > Service Parameters.

Step 2 On the Service Parameters Configuration page, in the Server field, click the name of the Cisco Unified CallManager server.

Step 3 In the Service list, click Cisco Unified CallManager. The list of parameters appears.

Step 4 Under Clusterwide Parameters (Device - H323), locate the H225 DTMF Duration parameter.

Step 5 If you will use the Cisco Unity Connection Bridge or AMIS to connect Cisco Unified CallManager and Cisco Unity Connection to a supported third-party voice messaging system, confirm that this parameter is set to 100.

Step 6 Under Clusterwide Parameters (Feature - General), locate the Multiple Tenant MWI Modes parameter.

Step 7 If you use multiple tenant MWI notification, click True.

When this parameter is set to True, Cisco Unified CallManager uses any configured translation patterns to convert voice mail extensions into directory numbers when turning on or off an MWI.

Step 8 If you changed any settings, click Update. Then shut down and restart the Cisco Unified CallManager server.

Creating a New Integration with the Cisco Unified CallManager Phone System

After ensuring that the Cisco Unified CallManager phone system and Cisco Unity Connection are ready for the integration, do the following procedures to set up the integration and to enter the port settings.

To Create an Integration

Step 1 Log on to Cisco Unity Connection Administration.

Step 2 In Cisco Unity Connection Administration, expand Telephony Integrations, then click Phone System.

Step 3 On the Search Phone Systems page, on the Phone System menu, click New Phone System. The Phone System Integration Wizard appears.

Step 4 On the Select Phone System Manufacturer page, in the Manufacturer field, click Cisco Systems and click Next.

Step 5 On the Select Phone System Model page, in the Model field, click CallManager and click Next.

Step 6 On the Set Up Phone System page, in the Phone System Name field, accept the default name or enter the descriptive name that you want, and click Next.

Step 7 On the Select Port Group Template page, in the Port Group Template field, click SCCP - Skinny Client Control Protocol and click Next.

Step 8 On the Set Up Port Group page, enter the following settings and click Next.

Table 13 Settings for the Set Up Port Group Page 

Field
Setting

Port Group Name

<the display name for the port group; accept the default name, which is composed of the phone system display name followed by an incrementing number, or enter another descriptive name>

Device Name Prefix

<the prefix that Cisco Unified CallManager adds to the device name for voice ports; this prefix must match the prefix used by Cisco Unified CallManager>

MWI On Extension

<the extension that you specified in Cisco Unified CallManager Administration for turning MWIs on>

MWI Off Extension

<the extension that you specified in Cisco Unified CallManager Administration for turning MWIs off>

Security Mode

<the Cisco Unified CallManager security mode that you want to use for the voice messaging ports in this port group>

Number of Ports

<the number of voice messaging ports that you want to create in this port group>

IP Address or Host Name

<the IP address (or host name) of the primary Cisco Unified CallManager server that you are integrating with Cisco Unity Connection>

Test Address

Click this button to test the IP address that you entered. The results of the test appear in the field to the right of the button.

Port

<the TCP port of the primary Cisco Unified CallManager server that you are integrating with Cisco Unity Connection; we recommend that you use the default setting>

TLS Port

<the TLS port of the primary Cisco Unified CallManager server that you are integrating with Cisco Unity Connection; we recommend that you use the default setting>

Server Type

Cisco Unified CallManager


Step 9 On the Confirm Phone System Settings page, confirm the settings that you have entered and click Finish.

Step 10 On the Phone System Creation Summary page, click Close.

Step 11 If Cisco Unity Connection does not connect to an AXL server, skip to Step 17. Otherwise, on the Search Phone Systems page, click the display name of the phone system that you created in Step 9.

Step 12 On the Phone System Basics page, in the Edit menu, click Cisco Unified CallManager AXL Servers.

Connecting to an AXL server is needed when Cisco Unity Connection must have access to the Cisco Unified CallManager database for importing Cisco Unified CallManager users and for changing certain phone settings for users of Cisco Unity Connection personal call transfer rules.

Caution If you plan to import Cisco Unified CallManager users, confirm that the Primary Extension field on the End User Configuration page for each user is filled in. Otherwise, the search will not find any users to select for importing.

Step 13 Under AXL Servers, click Add New.

Step 14 Enter the following settings for the AXL server and click Save.

Table 14 Settings for the AXL Servers 

Field
Setting

Order

<the order of priority for the AXL server; the lowest number is the primary AXL server, the higher numbers are the secondary servers>

IP Address or Host Name

<the IP address (or host name) of the AXL server>

Port

<the AXL server port that Cisco Unity Connection connects to; this setting must match the port that the AXL server will use>

When the connection does not use SSL, the port number is typically 80. When the connection uses SSL, the port number is typically 443.


Step 15 Repeat Step 13 and Step 14 for all remaining AXL servers.

Step 16 Under AXL Server Settings, enter the following settings and click Save.

Table 15 Settings for the AXL Settings 

Field
Setting

User Name

<the user name that Cisco Unity Connection will use to log on to the AXL server>

Password

<the password that Cisco Unity Connection will use to log on to the AXL server>

Cisco Unified CallManager Version

•Pre 5.0 (Non-SSL)

•Pre 5.0 (SSL)

If you select the non-SSL version, the AXL port must be a non-SSL port (typically port 80). If you select the SSL-enabled version, the AXL port must be an SSL-enabled port (typically port 443).


Note After the changes to this page are saved, you can click Test (next to the AXL server port number) to verify the connection to the AXL server. If the AXL port that you enter and the Cisco Unified CallManager Version setting conflict concerning whether SSL is used, the results of the test will require more than 10 minutes to appear.

Step 17 In Cisco Unity Connection Administration, expand Telephony Integrations, then click Port Group.

Step 18 On the Search Port Groups page, click the display name of the port group that you created with the phone system integration in Step 9.

Note By default, the display name for a port group is composed of the phone system display name followed by an incrementing number.

Step 19 On the Port Group Basics page, on the Edit menu, click Servers.

Step 20 On the Edit Servers page, do the following substeps if the Cisco Unified CallManager cluster has secondary servers. Otherwise, skip to Step 21.

a. Under Cisco Unified CallManager Servers, click Add.

b. Enter the following settings for the secondary Cisco Unified CallManager server and click Save.

Table 16 Settings for the Cisco Unified CallManager Server 

Field
Setting

Order

<the order of priority for the Cisco Unified CallManager server; the lowest number is the primary Cisco Unified CallManager server, the higher numbers are the secondary servers>

IP Address or Host Name

<the IP address (or host name) of the secondary Cisco Unified CallManager server>

Port

<the TCP port of the Cisco Unified CallManager server that you are integrating with Cisco Unity Connection; we recommend that you use the default setting>

TLS Port

<the TLS port of the Cisco Unified CallManager server that you are integrating with Cisco Unity Connection; we recommend that you use the default setting>

Server Type

Cisco Unified CallManager


Note You can click Ping to verify the IP address (or host name) of the Cisco Unified CallManager server.

c. Repeat Step 20a. and Step 20b. for all remaining Cisco Unified CallManager servers in the cluster.

Step 21 Do the following substeps if the Cisco Unified CallManager cluster uses authentication or encryption for the voice messaging ports. Otherwise, skip to Step 22.

a. Under TFTP Servers, click Add.

b. Enter the following settings for the TFTP server and click Save.

Table 17 Settings for the TFTP Server 

Field
Setting

Order

<the order of priority for the TFTP server; the lowest number is the primary TFTP server, the higher numbers are the secondary servers>

IP Address or Host Name

<the IP address (or host name) of the TFTP server>


Note You can click Ping to verify the IP address (or host name) of the TFTP server.

c. Repeat Step 21a. and Step 21b. for all remaining TFTP servers in the cluster.

Step 22 In Cisco Unity Connection Administration, expand Telephony Integrations, then click Port.

Step 23