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 Communications Manager 6.x SCCP Integration Guide for Cisco Unity 4.0

Downloads

Table Of Contents

Cisco Unified Communications Manager 6.x SCCP Integration Guide for Cisco Unity 4.0

Integration Tasks

Task List to Create the 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 Communications Manager Phone System

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

For a Cisco Unity Secondary Server

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

Creating an Integration with an Additional Cisco Unified Communications Manager Cluster

Setting Up Cisco Unified Communications Manager 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


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

Cisco Unified CM Security Features

Functional Overview

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: Documentation and Technical Assistance

Obtaining Documentation and Submitting a Service Request


Cisco Unified Communications Manager 6.x SCCP Integration Guide for Cisco Unity 4.0

Revised November 20, 2007

This document provides instructions for integrating Cisco Unified Communications Manager (CM) (formerly known as Cisco Unified CallManager) with Cisco Unity by Skinny Call Control Protocol (SCCP).

Cisco Unity supports an SCCP integration when the Cisco Unified CM cluster has only SCCP phones or has both SCCP and SIP phones.

Note If you are configuring MWI relay across trunks in a distributed phone system, you must refer to the Cisco Unified CM 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 CM 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 list describes the process for creating the integration.

Task List to Create the Integration

Use the following task list to set up a new integration with the Cisco Unified CM 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 CM:

•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. Create the integration. See the "Creating a New Integration with the Cisco Unified Communications Manager Phone System (SCCP)" section.

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

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

Requirements

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

Phone System

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

For details on compatible versions of Cisco Unified CM, refer to the SCCP Compatibility Matrix: Cisco Unity, the Cisco Unity-CM TSP, Cisco Unified Communications Manager, and Cisco Unified Communications Manager Express at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_device_support_tables_list.html.

•The following phones or combinations of phones for the Cisco Unified CM extensions:

–Only IP phones for the Cisco Unified CM extensions.

–Both IP phones and SIP phones for the Cisco Unified CM extensions without a media termination point (MTP) on the Cisco Unified CM server.

–Both IP phones and SIP phones for the Cisco Unified CM extensions with a media termination point (MTP) on the Cisco Unified CM server.

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

•For multiple Cisco Unified CM clusters, the capability for subscribers to dial an extension on another Cisco Unified CM 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 SCCP Compatibility Matrix: Cisco Unity, the Cisco Unity-CM TSP, Cisco Unified Communications Manager, and Cisco Unified Communications Manager 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 SCCP Compatibility Matrix: Cisco Unity, the Cisco Unity-CM TSP, Cisco Unified Communications Manager, and Cisco Unified Communications Manager 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.

Integration Description

The Cisco Unified CM integration uses a LAN or WAN to connect Cisco Unity and the phone system. The gateway provides connections to the PSTN.

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

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

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/en/US/products/sw/voicesw/ps2169/products_installation_and_configuration_guides_list.html.

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

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/en/US/products/sw/voicesw/ps2237/products_installation_and_configuration_guides_list.html.

•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/en/US/products/sw/voicesw/ps2237/products_installation_and_configuration_guides_list.html.

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

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 CM 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 Communications Manager Phone System

After the Cisco Unified CM software is installed, do the procedures in the applicable section to program Cisco Unified CM 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 Cisco Unified CM Administration, click Call Routing > Class of Control > Partition.

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

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

Step 5 Click Add New.

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

Step 8 Click Call Routing > Class of Control > Calling Search Space.

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

Step 10 On the Calling Search Space Configuration page, in the 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, click "VMRestrictedPT."

Step 13 Click the down arrow below the Available Partitions list.

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

Step 14 Click Save.

Step 15 In the Related Links field, click Back to Find/List and click Go.

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

Step 17 Click the name of the calling search space that is used by subscriber phones.

Step 18 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, 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 19 Click the down arrow below the Available Partition list.

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

Step 20 Click Save.

Step 21 Repeat Step 17 through Step 20 for each remaining calling search space that needs to access Cisco Unity.

Caution 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 Cisco Unified CM Administration, click System > Device Pool.

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

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 Communications Manager Group

Click the Cisco Unified Communications Manager 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 CM region 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.


Step 4 Click Save.

In the following procedure, add a voice mail port to Cisco Unified CM for each voice mail port that you will connect to Cisco Unity (either for a Cisco Unity server without failover or for a Cisco Unity primary server).

To Add Voice Mail Ports to Cisco Unified CM

Step 1 In Cisco Unified CM Administration, click 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, then 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 CM, 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 Cisco 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 that 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).

AAR Calling Search Space

Accept the default of None.

Location

Click Hub_None.

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 CM authentication and encryption of the voice mail ports, see the "Appendix: Cisco Unified Communications Manager Authentication and Encryption of Cisco Unity Voice Messaging Ports" section.


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

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.

Internal Caller ID 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.

Internal Caller ID Display
(ASCII Format)

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.

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.


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 In Cisco Unified CM Administration, click Call Routing > Route/Hunt > Line Group.

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

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

Click 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 Under Line Group Member Information, in the 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. Otherwise, the integration will not function correctly.

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). Otherwise, the integration will not function correctly.

Step 8 Click Save.

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.

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

Click Top Down.

No Answer

Click Stop Hunting.

Busy

Click Stop Hunting.

Not Available

Click Stop Hunting.


Step 12 Under Line Group Member Information, in the 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. Otherwise, the integration will not function correctly.

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. Otherwise, the integration will not function correctly.

Step 16 Click Save.

To Add the Line Group to a Hunt List

Step 1 In Cisco Unified CM Administration, click Call Routing > Route/Hunt > Hunt List.

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

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 Communications Manager Group

Click Default or the name of the Cisco Unified Communications Manager group that you are using.

Enable This Hunt List

Check this check box.

For Voice Mail Usage

Check this check box.


Step 4 Click Save.

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

Step 6 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 Save.

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

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

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

Step 9 When asked to confirm resetting the hunt list, click Reset.

Step 10 When alerted that the hunt list has been reset, click Close.

To Add the Hunt List to a Hunt Pilot Number

Step 1 In Cisco Unified CM Administration, click Call Routing > Route/Hunt > Hunt Pilot.

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

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.

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

To Specify MWI Directory Numbers

Step 1 In Cisco Unified CM Administration, click Voice Mail > Message Waiting.

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

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.

Partition

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

Description

Enter DN to turn MWIs on or another description.

Message Waiting Indicator

Click On.

Calling Search Space

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


Step 4 Click Save.

Step 5 Click Add New.

Step 6 Enter the following settings for turning MWIs off.

Table 10 Settings for Turning MWIs Off 

Field
Setting

Message Waiting Number

Enter the unique extension that turns MWIs off.

Partition

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

Description

Enter DN to turn MWIs off or another description.

Message Waiting Indicator

Click Off.

Calling Search Space

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


Step 7 Click Save.

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 Cisco Unified CM Administration, click Voice Mail > Voice Mail Pilot.

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

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.

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.

Description

Enter Cisco Unity Pilot or another description.

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

To Set Up the Voice Mail Profile

Step 1 In Cisco Unified CM Administration, click Voice Mail > Voice Mail Profile.

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

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 CM, 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 Save.

To Set Up the Voice Mail Server Service Parameters

Step 1 In Cisco Unified CM Administration, click System > Service Parameters.

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

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

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

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

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

Step 6 If you changed any settings, click Save. Then shut down and restart the Cisco Unified CM server.

If your Cisco Unity system is not configured for failover, skip to the "Creating a New Integration with the Cisco Unified Communications Manager Phone System (SCCP)" procedure. If your system uses failover, continue on to the "For a Cisco Unity Secondary Server" section.

For a Cisco Unity Secondary Server

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

In the following procedure, you will add a voice mail port to Cisco Unified CM for each port that you are connecting to the secondary Cisco Unity server.

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

Step 1 In Cisco Unified CM Administration, click 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, then 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 CM, 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 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).

AAR Calling Search Space

Accept the default of None.

Location

Accept the default of None.

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 CM authentication and encryption of the voice mail ports, see the "Appendix: Cisco Unified Communications Manager Authentication and Encryption of Cisco Unity Voice Messaging Ports" section.


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

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.

Internal Caller ID Display

Accept the default of VoiceMail.

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

Internal Caller ID Display
(ASCII Format)

Accept the default of VoiceMail.

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

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.


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 (Secondary Cisco Unity Server)

Step 1 In Cisco Unified CM Administration, click Call Routing > Route/Hunt > Line Group.

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

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 15 Settings for the Line Group Configuration Page for Answering Ports 

Field
Setting

Line Group Name

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

RNA Reversion Timeout

Accept the default of 10.

Distribution Algorithm

Click Top Down.

No Answer

Click Try Next Member, but Do Not Go to Next Group.

Busy

Click Try Next Member, but Do Not Go to Next Group.

Not Available

Click Try Next Member, but Do Not Go to Next Group.


Step 4 Under Line Group Member Information, in the 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. Otherwise, the integration will not function correctly.

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). Otherwise, the integration will not function correctly.

Step 8 Click Save.

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 (Secondary Cisco Unity Server)" procedure.

Step 10 Click Add New.

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 16 Settings for the Line Group Configuration Page for Dial-Out Ports 

Field
Setting

Line Group Name

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

RNA Reversion Timeout

Accept the default of 10.

Distribution Algorithm

Click Top Down.

No Answer

Click Stop Hunting.

Busy

Click Stop Hunting.

Not Available

Click Stop Hunting.


Step 12 Under Line Group Member Information, in the 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. Otherwise, the integration will not function correctly.

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

Caution Do n