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

Hierarchical Navigation

Cisco Unity

Cisco Unified CallManager 4.2 Integration Guide for Cisco Unity 4.0

Downloads

Table Of Contents

Cisco Unified CallManager 4.2 Integration Guide for Cisco Unity 4.0

Integration Tasks

Task List to Create the Integration

Task List to Make Changes to an Integration

Task List to Change the Number of Voice Messaging Ports

Task List to Delete an Existing 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

Programming the Cisco Unified CallManager Phone System

For a Cisco Unity Server Without Failover or for a Cisco Unity Primary Server

For a Cisco Unity Secondary Server

Setting Up the Gateways That Service Cisco Unity

Creating a New Integration with the Cisco Unified CallManager Phone System (SCCP)

Creating an Integration with an Additional Cisco Unified CallManager Cluster

Setting Up Cisco Unified CallManager Authentication and Encryption with Cisco Unity 4.0(5) or Later

Testing the Integration

Integrating a Secondary Server for Cisco Unity Failover

Requirements

Integration Description

Setting Up the Secondary Server for Failover

Changing the Settings for an Existing Integration

Changing the Number of Voice Messaging Ports

Deleting an Existing Integration


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

Cisco Unified CallManager Security Features

Functional Overview

Cisco Unified CallManager Cluster Security Mode Settings in Cisco Unity


Appendix: Using Alternate Extensions and MWIs

Alternate Extensions

Setting Up Alternate Extensions

Alternate MWIs

Setting Up Alternate MWIs for Extensions on the Same Phone System

MWIs for Extensions on a Non-Integrated Phone System

Setting Up MWIs for Extensions on a Non-Integrated Phone System


Appendix: Integrated Mailbox Configuration Account Manager

Setting up the Cisco Unity Logon Account and Environment

Creating a Cisco Unity Voice Mailbox

Using the Integrated Mailbox Configuration Account Manager

Integrated Mailbox Configuration Troubleshooting

Diagnostics

Error Messages

Cisco Unity Cisco Unified CallManager Integrated Mailbox Configuration Wizard or Integrated Mailbox Configuration Account Manager

Integrated Mailbox Configuration


Appendix: Documentation and Technical Assistance

Conventions

Obtaining Documentation

Cisco.com

Product Documentation DVD

Ordering Documentation

Documentation Feedback

Cisco Product Security Overview

Reporting Security Problems in Cisco Products

Product Alerts and Field Notices

Obtaining Technical Assistance

Cisco Technical Support & Documentation Website

Submitting a Service Request

Definitions of Service Request Severity

Obtaining Additional Publications and Information


Cisco Unified CallManager 4.2 Integration Guide for Cisco Unity 4.0

Revised September 8, 2006

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

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 settings.

Integration Tasks

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

The following task lists describe the process for creating, changing, and deleting 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 server by using the applicable Cisco Unity 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 server requirements have been met. See the "Requirements" section.

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

3. Program Cisco Unified CallManager.

•Without Cisco Unity failover—Do the procedures in the "For a Cisco Unity Server Without Failover or for a Cisco Unity Primary Server" section, in the order given.

•Cisco Unity failover primary server—Do the procedures in the "For a Cisco Unity Server Without Failover or for a Cisco Unity Primary Server" section, in the order given.

•Cisco Unity failover secondary server—Do the procedures in the "For a Cisco Unity Secondary Server" section, in the order given.

4. Set up the gateways that service Cisco Unity. See the "Setting Up the Gateways That Service Cisco Unity" section.

5. Create the integration. See the "Creating a New Integration with the Cisco Unified CallManager Phone System (SCCP)" section.

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

7. If you have a secondary server for Cisco Unity failover, integrate the secondary server. See the "Integrating a Secondary Server for Cisco Unity Failover" section.

Task List to Make Changes to an Integration

Use the following task list to make changes to an integration after it has been created.

1. Start the Cisco Unity Telephony Integration Manager (UTIM). See the "Changing the Settings for an Existing Integration" section.

2. Make the changes you want to the existing integration. See the "Changing the Settings for an Existing Integration" section.

Note You can create Cisco Unity voice mailboxes one at a time from the Cisco Unified CallManager Administration by using the Integrated Mailbox Configuration Account Manager. For details, see the Appendix: Integrated Mailbox Configuration Account Manager.

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 the Cisco Unified CallManager Administrator. See the "Changing the Number of Voice Messaging Ports" section.

2. Make the changes you want to the number of voice messaging ports in Cisco Unity. See the "Changing the Number of Voice Messaging Ports" section.

Task List to Delete an Existing Integration

Use the following task list to remove an existing integration.

1. Start the Cisco Unity Telephony Integration Manager (UTIM). See the "Deleting an Existing Integration" section.

2. Delete the existing integration. See the "Deleting an Existing 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, subscribers can dial an extension on another Cisco Unified CallManager cluster without having to dial a trunk access code or prefix.

Cisco Unity Server

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

•Cisco Unity installed and ready for the integration, as described in the applicable Cisco Unity installation guide at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/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, the Cisco Unity-CM TSP, Cisco CallManager, and Cisco CallManager Express at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_device_support_tables_list.html.

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

Note For Cisco Unified CallManager authentication and encryption of voice messaging ports, you must have Cisco Unity version 4.0(5) or later.

Integration Description

The Cisco Unified CallManager integration uses the LAN to connect Cisco Unity 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

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 uses this information to answer the call appropriately. For example, a call forwarded to Cisco Unity is answered with the personal greeting of the subscriber. If the phone system routes the call to Cisco Unity without this information, Cisco Unity answers with the opening greeting.

Integration Functionality

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

•Call forward to personal greeting

•Call forward to busy greeting

•Caller ID

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

•Identified subscriber messaging (Cisco Unity identifies the subscriber 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, 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, the internal greeting cannot play. Because the PSTN provides the calling number of the FXO line, the caller is not identified as a subscriber.

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

•Identified subscriber messaging—When the Cisco Unified SRST router uses FXO/FXS connections to the PSTN and a subscriber at a branch office leaves a message or forwards a call, the subscriber 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.

•Message notification—Because an access code is needed to reach the PSTN, message notifications from Cisco Unity to a branch office will fail.

•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 (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 may be the full number (exchange plus extension) provided by the PSTN and therefore may not match the extension of the Cisco Unity subscriber. If this is the case, you can let Cisco Unity recognize the caller ID by using alternate extensions (for instructions, see the "Appendix: Using Alternate Extensions and MWIs" section) or by using extension remapping (for instructions, refer to the "Remapping Extension Numbers" section of the "System Settings" chapter in the applicable Cisco Unity System Administration Guide (release 4.0(3) or later), available at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_maintenance_guides_list.html.

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 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 transfers to a phone can display the original calling party information rather than the calling party information of the Cisco Unity voice messaging port.

•Live reply will not function correctly.

•Transfers to subscribers on other networked Cisco Unity 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 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 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 transfers the call to extension C and the call displays the number of the Cisco Unity 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 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

Depending on the version, Cisco Unity can be integrated with two or more phone systems:

•Cisco Unity 4.0 and 4.1 can be integrated with a maximum of two phone systems at one time. For information on and instructions for integrating Cisco Unity with two phone systems, refer to the Dual Phone System Integration Guide at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/integuid/multi/itmultin.htm.

•Cisco Unity 4.2 and later can be integrated with two or more phone systems at one time. For information on the maximum supported combinations and instructions for integrating Cisco Unity with multiple phone systems, refer to the Multiple Phone System Integration Guide at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/integuid/multi/multcu42.htm.

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

Before programming the phone system, you need to plan how the voice messaging ports will be used by Cisco Unity. 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), to make AMIS deliveries, and to make telephone record and playback (TRAP) connections.

The following table describes the voice messaging port settings in Cisco Unity that can be set in UTIM, and that are displayed as read-only text on the System > Ports page of the Cisco Unity Administrator.

Table 1 Settings for the Voice Messaging Ports 

Field
Considerations

Extension

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

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.

Answer Calls

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

Message Notification

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

Dialout MWI

(not used by serial or SMDI integrations)

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

AMIS Delivery

(available with the AMIS licensed feature only)

Check this check box to designate the port for making outbound AMIS calls to deliver voice messages from Cisco Unity subscribers to users on another voice messaging system. Cisco Unity supports the Audio Messaging Interchange Specification (AMIS) protocol, which provides an analog mechanism for transferring voice messages between different voice messaging systems.

This setting affects outbound AMIS calls only. All ports are used for incoming AMIS calls.

Because the transmission of outgoing AMIS messages may tie up voice ports for long periods of time, you may want to adjust the schedule on the Network > AMIS > Schedule page so that outgoing AMIS calls are placed during closed hours or at times when Cisco Unity is not processing many calls.

TRAP Connection

Check this check box so that subscribers can use the phone as a recording and playback device in Cisco Unity web applications and e-mail clients. Assign TRAP Connection to the least busy ports.


Note If you enable Cisco Unified CallManager authentication and encryption for the Cisco Unity voice messaging ports, we recommend not changing the Security Mode settings for individual voice messaging ports except for troubleshooting purposes.

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 will answer when call traffic is at its peak.

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

•The number of subscribers.

•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 AMIS delivery calls.

•The number of TRAP connections needed when call traffic is at its peak. (TRAP connections are used by Cisco Unity 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 subscribers. 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 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 subscribers by phone, pager, or e-mail of messages that have arrived.

•Turn MWIs on and off for subscriber extensions.

•Make outbound AMIS calls to deliver voice messages from Cisco Unity subscribers to users on another voice messaging system. (This action is available only with the AMIS licensed feature.)

•Make a TRAP connection so that subscribers can use the phone as a recording and playback device in Cisco Unity 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 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 Dialout MWI, 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 procedures in the applicable section to program Cisco Unified CallManager to work with Cisco Unity:

•A Cisco Unity server without failover—Do the procedures in the "For a Cisco Unity Server Without Failover or for a Cisco Unity Primary Server" section, in the order given.

•A Cisco Unity failover primary server—Do the procedures in the "For a Cisco Unity Server Without Failover or for a Cisco Unity Primary Server" section, in the order given.

•A Cisco Unity failover secondary server—Do the procedures in the "For a Cisco Unity Secondary Server" section, in the order given.

For a Cisco Unity Server Without Failover or for a Cisco Unity Primary Server

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 subscriber 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 subscriber phones, the phones will not be able to dial the Cisco Unity 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.

Caution For Cisco Unified CallManager 4.0 and later, annunciators must not be associated with the device pool for the voice mail ports. Otherwise, under certain circumstances, annunciator recordings or tones may play while callers are recording messages.

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 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.

To Add Voice Mail Ports to Cisco Unified CallManager

Add a voice mail port to Cisco Unified CallManager for each port that you are connecting to Cisco Unity (either for a Cisco Unity server without failover or for a Cisco Unity primary server).

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.

Caution If Cisco Unity is configured for failover, the name of the voice mail server and voice mail ports that serve the secondary server must be different from the name of the voice mail server and voice mail ports that serve the primary server. Otherwise, the secondary server cannot function correctly.

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 license enables), then click Next.

If you will integrate Cisco Unity 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 to more than the number of ports enabled by the Cisco Unity 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 Voice Mail Ports.

Calling Search Space

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

This calling search space must include partitions that contain all devices Cisco Unity 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 subscriber phones, subscribers are not able to dial the voice mail ports. However, subscribers 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.)

Caution If Cisco Unity is configured for failover, do not change the default setting for this field. Otherwise, the integration will not function correctly.

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 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

•Without Cisco Unity failover—Enter Cisco Unity Answering Ports or another unique name for line groups.

•Primary failover server—Enter Cisco Unity Primary 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

•Without Cisco Unity failover—Accept the default of Try Next Member; Then, Try Next Group in Hunt List.

•Primary failover server—Click Skip Remaining Members, and Go Directly to Next Group.

Busy

•Without Cisco Unity failover—Accept the default of Try Next Member; Then, Try Next Group in Hunt List.

•Primary failover server—Click Try Next Member, but Do Not Go to Next Group.

Not Available

•Without Cisco Unity failover—Accept the default of Try Next Member; Then, Try Next Group in Hunt List.

•Primary failover server—Click Skip Remaining Members, and Go Directly to Next Group.


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

•Without Cisco Unity failover—Enter Cisco Unity Dial-Out Ports or another unique name.

•Primary failover server—Enter Cisco Unity Primary 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 Answering Ports or another unique name for the hunt list.

Description

Enter Cisco Unity 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.

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 subscribers 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 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 subscriber 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 subscriber phones.


Step 7 Click Insert.

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

The voice mail pilot number 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.

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 subscribers 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 Pilot or another description.

Calling Search Space

Click the calling search space that includes partitions containing the subscriber 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 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. It is also necessary to set up 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 Bridge or AMIS to connect Cisco Unified CallManager and Cisco Unity 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.

If your Cisco Unity system is not configured for failover, skip to the "Setting Up the Gateways That Service Cisco Unity" section. If your system uses failover, continue on to the "For a Cisco Unity Secondary Server" section.

Note You can use alternate extensions to create multiple line appearances, enable easy message access from cell phones, and simplify addressing messages to subscribers at different locations in Cisco Unity. When you enable alternate MWIs, Cisco Unity can turn MWIs on at more than one extension. For details, see the "Appendix: Using Alternate Extensions and MWIs" section.

For a Cisco Unity Secondary Server

When you program Cisco Unified CallManager for the secondary Cisco Unity server, do the following procedures in the order given.

To Add Voice Mail Ports to Cisco Unified CallManager (Secondary Cisco Unity Server)

Add a voice mail port to Cisco Unified CallManager for each port that you are connecting to the secondary Cisco Unity server.

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. Enter a unique name for the voice mail server; the name must have no more than nine characters.

Caution The name of the voice mail server and voice mail ports that serve the secondary server must be different from the name of the voice mail server and voice mail ports that serve the primary server. Otherwise, the secondary server cannot function correctly.

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 license enables), then click Next.

If you will integrate Cisco Unity 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 to more than the number of ports enabled by the Cisco Unity license.

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

Table 13 Settings for the Cisco Voice Mail Device Information Page 

Field
Setting

Description

Enter Cisco Voice Mail Secondary Port or another description.

Device Pool

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

Calling Search Space

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

This calling search space must include partitions that contain all devices Cisco Unity 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 14 Settings for the Cisco Voice Mail Directory Numbers Page 

Field
Setting

Beginning Directory Number

Enter the extension number of the first voice mail port that will connect to the secondary Cisco Unity server.

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 subscriber phones, subscribers are not able to dial the voice mail ports. However, subscribers 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 setting up Cisco Unified CallManager security for the voice mail ports, see the "Appendix: Cisco Unified CallManager Authentication and Encryption of Cisco Unity 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 t