Table Of Contents
Cisco CallManager 3.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 Features
Integrations with Two Phone Systems
Planning How the Voice Messaging Ports Will Be Used by Cisco Unity
Preparing for Programming the Phone System
Programming the Cisco CallManager Phone System
Setting Up the Gateways That Service Cisco Unity
Creating a New Integration with the Cisco CallManager Phone System
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
Troubleshooting the Cisco CallManager Integration
Cisco Unity Does Not Answer When the Extension for Cisco Unity Is Dialed
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
Conventions
Cisco Unity Documentation
Obtaining Documentation
Cisco.com
Ordering Documentation
Documentation Feedback
Obtaining Technical Assistance
Cisco Technical Support Website
Opening a TAC Case
TAC Case Priority Definitions
Obtaining Additional Publications and Information
Cisco CallManager 3.2 Integration Guide for Cisco Unity 4.0
Revised November 14, 2005
This document provides instructions for integrating the phone system with Cisco Unity.
Integration Tasks
Before doing the following tasks to integrate Cisco Unity with the Cisco CallManager phone system, confirm that the Cisco Unity server is ready for the integration by completing the applicable tasks in the 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 CallManager phone system. If you are installing a new Cisco Unity server by using the 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 CallManager. See the "Programming the Cisco CallManager Phone System" section.
•When configuring voice mail ports for a Cisco Unity server without failover or the primary server with failover, do all the procedures in this section.
•When configuring voice mail ports for a secondary server with failover, do only the "To Add Voice Mail Ports to Cisco CallManager" procedure.
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 CallManager Phone System" 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.
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. See the "Changing the Number of Voice Messaging Ports" section.
2. Start the Cisco Unity Telephony Integration Manager (UTIM). See the "Changing the Settings for an Existing Integration" section.
3. Make the changes you want to the existing integration. See the "Changing the Settings for an Existing Integration" 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 CallManager integration supports configurations of the following components:
Phone System
•A Cisco IP telephony applications server consisting of Cisco CallManager 3.2(1) or later, running on a Cisco Media Convergence Server (MCS) or customer-provided server meeting approved Cisco configuration standards.
•Cisco licenses for all phone lines, IP phones, and other H.323-compliant devices or software (such as Cisco VirtualPhone and Microsoft NetMeeting clients) that will be connected to the network, as well as one license for each Cisco Unity port.
•IP phones for the Cisco CallManager extensions.
•A LAN connection in each location where you will plug an IP phone into the network.
•For multiple Cisco CallManager clusters, subscribers can dial an extension on another Cisco CallManager cluster without having to dial a trunk access code or prefix.
Cisco Unity Server
•Cisco Unity version 4.0(1) or later, installed and ready for the integration as described in the Cisco Unity Installation Guide.
•A license that enables the applicable number of voice messaging ports.
Integration Description
The Cisco 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 Features
The Cisco CallManager integration with Cisco Unity provides the following features.
Call forward to personal greeting
|
When an incoming call is routed to an unanswered extension, the call is forwarded to the voice mail of the subscriber. The caller then hears the personal greeting of the subscriber and can leave a message.
|
Call forward to busy greeting
|
When an incoming call is routed to a busy extension, the call is forwarded to the voice mail of the subscriber. The caller then hears the busy greeting (if the subscriber enabled it) and can leave a message.
|
Caller ID
|
Cisco Unity receives caller ID information from the phone system (if available). This information appears in the subject line of the message in the desktop messaging application.
|
Easy message access
|
A subscriber can retrieve messages without entering an ID. Cisco Unity identifies a subscriber based on the extension from which the call originated. A password may be required.
|
Identified subscriber messaging
|
Cisco Unity automatically identifies a subscriber who leaves a message during a forwarded internal call, based on the extension from which the call originated.
|
Message waiting indication
|
When a message is waiting for a subscriber, Cisco Unity notifies Cisco CallManager to activate the message waiting indicator (MWI) on the subscriber extension.
|
When a Cisco Survivable Remote Site Telephony (SRST) router is part of the network and the Cisco SRST router takes over call processing functions (for example, because the WAN link is down), the Cisco SRST integration with Cisco Unity has the following feature limitations:
•Call forward to busy greeting—When the Cisco 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 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 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 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 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/products_administration_guides_list.html.
For information on setting up Cisco SRST routers, refer to the "Integrating Voice Mail with Cisco SRST" section of the "Cisco SRST System Administrator Guide," available at http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122limit/122z/122zj15/index.htm.
Integrations with Two Phone Systems
Cisco Unity can be integrated with two phone systems at one time. For information on and instructions for integrating Cisco Unity with two phone systems, see the Dual Phone System Integration Guide, available at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/integuid/multi/itmultin.htm.
Having two integrations requires that an adequate number of voice messaging ports on the Cisco Unity server are connected to the phone systems. This number of ports must not exceed the maximum number of ports that are enabled by the Cisco Unity license files.
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 number of voice messaging ports that will be dedicated to set MWIs if Cisco Unity is connected to multiple clusters of Cisco CallManager and if the Cisco CallManager server has dedicated MWI voice messaging ports.
Table 1 describes the voice messaging port settings in Cisco Unity that can be set in UTIM and 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. As a general guideline, set Answer Calls on approximately 75 percent of the ports.
|
Message Notification
|
Check this check box to designate the port for notifying subscribers of messages. Assign Message Notification to the least busy ports, which typically are those with the highest port numbers for the phone system. As a general guideline, set Message Notification, Dialout MWI, and TRAP Connection on approximately 25 percent of the 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, which typically are those with the highest port numbers for the phone system. As a general guideline, set Message Notification, Dialout MWI, and TRAP Connection on approximately 25 percent of the 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, which typically are those with the highest port numbers for the phone system. As a general guideline, set Message Notification, Dialout MWI, and TRAP Connection on approximately 25 percent of the ports.
|
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 and e-mail clients to play back and record over the phone.)
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, these voice messaging ports are the busiest. They also have the lowest port numbers for the phone system.
You can set voice messaging ports to both answer calls and to dial out (for example, to send message notifications).
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 and e-mail clients.
Typically, these voice messaging ports are the least busy ports. They also have the highest port numbers for the phone system.
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.
The Number of Voice Messaging Ports That Will Be Dedicated to Activating MWIs on Other Cisco CallManager Clusters
If Cisco Unity services multiple clusters of Cisco CallManager, there must be at least one voice messaging port per cluster dedicated for turning MWIs on and off for each cluster. For example, if the system has four clusters, at least four ports on Cisco Unity must be dedicated to activating MWIs, one port for each cluster.
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 CallManager Phone System
After Cisco CallManager software is installed, do the procedures in this section to program Cisco CallManager to work with Cisco Unity:
•When configuring voice mail ports for a Cisco Unity server without failover, or the primary server with failover, do all the procedures in this section.
•When configuring voice mail ports for a secondary server with failover, do only the "To Add Voice Mail Ports to Cisco CallManager" procedure.
To Add Partitions and a Calling Search Space to Contain the Voice Mail Ports
Step 1 In the Cisco CallManager Administration, click Route Plan > Partition.
Step 2 Click Add a New Partition.
Step 3 Enter the name and description you want for the partition that will contain all voice mail port directory numbers except for the first voice mail port, which will be assigned the voice mail pilot number. For example, enter "VMRestrictedPT, Partition for voice mail port directory numbers." For a diagram of the configuration, see Figure 2. For a diagram of the configuration with Cisco Unity failover, see Figure 3.
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 directory number of the first voice mail port, which will be assigned the voice mail pilot number. For example, enter "VMPilotNumberPT, Partition for the voice mail pilot number." For a diagram of the configuration, see Figure 2. For a diagram of the configuration with Cisco Unity failover, see Figure 3.
Step 7 Click Insert.
Step 8 Click Route Plan > Calling Search Space.
Step 9 Click Add a New Calling Search Space.
Step 10 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 If you want, 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." For a diagram of the configuration, see Figure 2. For a diagram of the configuration with Cisco Unity failover, see Figure 3.
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 Click the name of the calling search space that is used by subscriber phones.
Step 16 In the Available Partitions field, double-click the name of the partition created in Step 5 through Step 7. For example, double-click "VMPilotNumberPT." For a diagram of the configuration, see Figure 2. For a diagram of the configuration with Cisco Unity failover, see Figure 3.
Caution If the partition that contains 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 17 Click Update.
Step 18 Repeat Step 15 through Step 17 for each remaining calling search space that needs to access Cisco Unity.
Figure 2 Partitions for Voice Mail Port Directory Numbers
Figure 3 Partitions for Voice Mail Port Directory Numbers with Cisco Unity Failover
To Add a Device Pool for the Voice Mail Ports
Step 1 In the Cisco CallManager Administration, click System > Device Pool.
Step 2 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 CallManager Group
|
Click the Cisco 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 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
|
Click the survivable remote site telephony (SRST) reference to assign to the voice mail ports in this device pool.
|
Network Hold MOH Audio Source
|
Click None.
|
User Hold MOH Audio Source
|
Click None.
|
Step 3 Click Insert.
To Add Voice Mail Ports to Cisco CallManager
Add a voice mail port to Cisco CallManager for each port that you are connecting to Cisco Unity.
Step 1 In the Cisco CallManager Administration, click Feature > Voice Mail > Cisco Voice Mail Port Wizard.
Step 2 Click Create a New Cisco Voice Mail Server and Add Ports to It and click Next.
Step 3 The name of the voice mail server appears. We recommend that you accept the default name for the voice mail server, or, if necessary, enter a different name with no more than nine characters, then click Next.
The default name (CiscoUM), even if you do not use it, becomes part of the name for ports as follows:
<the voice mail server name>1 (for example, CiscoUM1).
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 Enter the number of ports you want to add (which must not be more ports than the Cisco Unity license enables), then click Next.
If you will integrate Cisco Unity with multiple clusters of Cisco 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 5 Enter the following voice mail device settings, then click Next.
Table 3 Settings for the Voice Mail Devices
Field
|
Setting
|
Description
|
Enter Cisco Voice Mail Port or other description that you want.
|
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 6 Enter the following voice mail directory number settings, then click Next.
Table 4 Settings for the Voice Mail Directory Numbers
Field
|
Setting
|
Pilot Number
|
Enter the pilot number for the voice mail ports.
The pilot number is the extension number of the first voice mail port and is the number subscribers enter to listen to their voice messages.
If Cisco Unity is configured for failover and you are adding voice mail ports for the secondary server, the pilot number is the extension number of the first voice mail port on the secondary server, but it is not the number subscribers enter to listen to their voice messages.
|
Partition
|
Click the name of the partition that you set up for all voice mail port directory numbers except the first voice mail port. 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 except the first voice mail port, as set in Step 9 of the "To Add Partitions and a Calling Search Space to Contain the Voice Mail Ports" section. For example, click "VMRestrictedCSS."
Because this calling search space is not used by subscriber phones, subscribers cannot dial any voice mail ports except 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.
|
Step 7 Enter the operator number or the number you want the last port to forward to when busy, if applicable, and click Next.
Step 8 The settings for the new ports appear. Click Finish.
Step 9 Click Go to Cisco Voice Mail Ports Page.
Note If Cisco Unity is configured for failover and you are setting ports for the secondary server, skip the remaining procedures in this section and continue to the "Creating a New Integration with the Cisco CallManager Phone System" section. For further instructions on configuring the voice mail ports, see the "Integrating a Secondary Server for Cisco Unity Failover" section.
To Set the Partition for the First Voice Mail Port
Step 1 On the Cisco Voice Mail Port Configuration page, in the Cisco Voice Mail Ports list, click the first voice mail port, which is assigned the voice mail pilot number.
Step 2 Under Directory Number Information, in the Partition field, click the partition that you set up to contain the first voice mail port. For example, click "VMPilotNumberPT."
Step 3 Click Update.
To Specify MWI Directory Numbers
Step 1 In the Cisco CallManager Administration, click Feature > Voice Mail > Message Waiting.
Step 2 In the Message Waiting Directory Numbers list of the Message Waiting Configuration page, click Add a New Directory Number.
Step 3 Enter the following settings for turning MWIs on.
Table 5 Settings for Turning MWIs On
Field
|
Setting
|
Directory Number
|
Enter the unique extension that turns MWIs on.
|
Message Waiting Indicator
|
Click On.
|
Partition
|
Click the name of the partition that you set up for the first voice mail port. For example, click "VMPilotNumberPT."
|
Calling Search Space
|
Click a calling search space that is used by subscriber phones.
|
Step 4 Click Insert.
Step 5 In the Message Waiting Directory Numbers list, click Add a New Directory Number.
Step 6 Enter the following settings for turning MWIs off.
Table 6 Settings for Turning MWIs Off
Field
|
Setting
|
Directory Number
|
Enter the unique extension that turns MWIs off.
|
Message Waiting Indicator
|
Click Off.
|
Partition
|
Click the name of the partition that you set up for the first voice mail port. 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 CallManager Administration, click Feature > Voice Mail > Voice Mail Pilot.
Step 2 In the Voice Mail Pilot Numbers list of the Voice Mail Pilot Configuration page, click Add a New Voice Mail Pilot Number.
Step 3 Enter the following voice mail pilot number settings.
Table 7 Settings for the Voice Mail Pilot Number
Field
|
Setting
|
Voice Mail Pilot Number
|
Enter the pilot number for the voice mail ports. This number must be the same pilot number that you entered when adding voice mail ports earlier.
The pilot number is typically the extension number of the first voice mail port and is the number subscribers enter to listen to their voice messages.
|
Description
|
Enter Cisco Unity Pilot or another description that you want.
|
Calling Search Space
|
Click the calling search space that includes partitions containing the subscriber phones and the partition you set up for the first voice mail port.
|
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 CallManager Administration, click Feature > Voice Mail > Voice Mail Profile.
Step 2 In the Find and List Voice Mail Profiles page, click Add a New Voice Mail Profile.
Step 3 In the Voice Mail Profiles Configuration page, enter the following voice mail profile settings.
Table 8 Settings for the Voice Mail Profile
Field
|
Setting
|
Voice Mail Profile Name
|
Enter a name to identify the voice mail profile.
|
Description
|
Enter Cisco Unity Profile or another description that you want.
|
Voice Mail Pilot
|
Click one of the following:
•The applicable voice mail pilot number that you defined in the Voice Mail Pilot Configuration
•None (to use the default voice mail pilot number)
|
Voice Mail Box Mask
|
When multitenant services are not enabled on Cisco CallManager, leave this field blank.
When multitenant services are enabled, each tenant uses its own voice mail profile. Create a mask to identify the extensions (directory numbers) in each partition. 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.
If you check the check box, 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 CallManager Administration, click Service > Service Parameters.
Step 2 In the Server field on the Service Parameters Configuration page, click the voice mail server that you created earlier.
Step 3 In the Services list, click Cisco CallManager. The list of parameters appears.
Step 4 Scroll down the list until you locate the parameters listed in Table 9 (about three-quarters of the way).
Step 5 Enter the parameter settings shown in the following table.
Table 9 Settings for the Service Parameters
Service Parameter to Configure
|
Setting
|
Voice Mail Maximum Hop Count
|
Used together with AdvancedCallForwardHopFlag, the maximum number of voice mail ports skipped to find the next available voice mail port. Specify a value that is three less than the number of Cisco CallManager ports that are connected to the Cisco Unity server. For example, if you have a 48-port Cisco Unity system, enter 45 for this setting.
If you have configured failover for Cisco Unity, specify a value that is three less than the total number of Cisco CallManager ports that are connected to both Cisco Unity servers. For example, if the primary and secondary Cisco Unity servers each have 48 ports, enter 93 for this setting.
|
Multiple Tenant MWI Modes
|
Enables multitenant MWI notification. When set to True, Cisco CallManager uses any configured translation patterns to convert voice mail extensions into directory numbers when turning on or off an MWI.
|
H225 DTMF Duration
|
Specifies the duration (in milliseconds) of outbound DTMF digits for H.323 devices.
If you will use the Cisco Unity Bridge or AMIS to connect Cisco CallManager and Cisco Unity to a supported third-party voice messaging system, confirm that this parameter is set to 100.
|
Advanced CallForward Hop Flag
|
Enables Cisco CallManager to skip busy or unregistered voice mail ports when searching for an available voice mail port. Set to True.
|
Step 6 Click Update to save the settings.
Step 7 Click Select Another Service at the top of the page.
Step 8 In the Services list, click Cisco Messaging Interface. The list of parameters appears.
Step 9 Confirm that the VoiceMailDn parameter setting is blank.
Step 10 If you changed the parameter setting to blank, click Update to save the setting.
Step 11 Shut down and restart the Cisco CallManager server.
If the plan for voice mail ports in Cisco Unity (see the "Planning How the Voice Messaging Ports Will Be Used by Cisco Unity" section) includes ports that do not answer calls (for example, ports that only dial out to set MWIs), do the following procedure so that incoming calls are not forwarded to these ports.
To Set Up Voice Mail Ports So Incoming Calls Are Forwarded Only to Answering Ports
Step 1 In the Cisco CallManager Administration, click Feature > Voice Mail > Cisco Voice Mail Port.
Step 2 In the Cisco Voice Mail Ports list of the Cisco Voice Mail Port Configuration page, click the name of the last voice mail port that answers calls in Cisco Unity.
Step 3 Set the Forward Busy and Forward No Answer fields to forward to the first voice mail port that answers calls in Cisco Unity.
Step 4 Click Update.
Step 5 In the Cisco Voice Mail Ports list, click the name of a the first voice mail port that does not answer calls in Cisco Unity.
Step 6 Under Call Forwarding Information, delete the extensions in the Forward Busy field, and set the Forward No Answer field to forward to the first voice mail port that answers calls in Cisco Unity.
Step 7 Click Update.
Step 8 Repeat Step 5 through Step 7 for all remaining voice mail ports that do not answer calls in Cisco Unity.
If the Cisco Unity server services multiple clusters of Cisco CallManager, do the following procedure to enable MWIs to be activated on extensions in each cluster.
To Set Up MWI Voice Mail Ports for Multiple Clusters of Cisco CallManager
Step 1 In the Cisco Unity Administrator, select at least one voice mail port per cluster to be dedicated for sending MWIs to each cluster. For example, if the system has four clusters, dedicate at least four ports to send only MWIs, one port from each cluster.
Step 2 In the Cisco CallManager Administration, click Feature > Voice Mail > Cisco Voice Mail Port.
Step 3 In the Cisco Voice Mail Ports list of the Cisco Voice Mail Port Configuration page, click the name of the port before the first dedicated MWI port.
Step 4 Under Call Forwarding Information, change the extensions to the number of the first voice mail port or of the operator.
Step 5 Click Update.
Step 6 In the Cisco Voice Mail Ports list, click the name of a dedicated MWI port.
Step 7 Under Call Forwarding Information, delete the extensions so that the fields are empty and call forwarding for this port is disabled.
Step 8 Click Update.
Step 9 Repeat Step 6 through Step 8 for all remaining dedicated MWI ports.
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.
Setting Up the Gateways That Service Cisco Unity
In certain situations, DTMF digits are not recognized when processed through VoIP dial-peer gateways. To avoid this problem, certain gateways must be configured to enable DTMF relay. The DTMF relay feature is available in Cisco IOS software version 12.0(5) and later.
Cisco IOS software-based gateways that use H.245 out-of-band signaling must be configured to enable DTMF relay.
Enable dtmf-relay h245-alphanumeric on this dial-peer.
The Catalyst 6000 T1/PRI and FXS gateways enable DTMF relay by default and do not need additional configuration to enable this feature.
To Enable DTMF Relay
Step 1 On a VoIP dial-peer servicing Cisco Unity, use the following command:
dtmf-relay h245-alphanumeric
Step 2 Create a destination pattern that matches the Cisco CallManager voice mail port numbers. For example, if the system has voice mail ports 1001 through 1016, enter the dial-peer destination pattern 10xx.
Step 3 Repeat Step 1 and Step 2 for all remaining VoIP dial-peers servicing Cisco Unity.
Creating a New Integration with the Cisco CallManager Phone System
After ensuring that the Cisco CallManager phone system and the Cisco Unity server are ready for the integration, do the following procedures to set up the integration and to enter the port settings.
Note If you are integrating with multiple clusters of Cisco CallManager, you must integrate Cisco Unity with each additional cluster. Skip to the "To Create an Integration with a Second Cluster of Cisco CallManager" procedure.
To Create an Integration
Step 1 If UTIM is not already open, on the Windows Start menu, click Programs > Cisco Unity > Manage Integrations. UTIM appears.
Step 2 On the Integration menu of the UTIM window, click New. The Telephony Integration Setup Wizard appears.
Step 3 On the Welcome page, click Cisco CallManager, then click Next.
Step 4 On the Name Cisco CallManager Integration and Cluster page, enter the following settings, then click Next.
Table 10 Settings for the Name Cisco CallManager Integration and Cluster Page
Field
|
Setting
|
Integration Name
|
<the name you will use to identify this Cisco CallManager integration; accept the default name or enter another name>
|
Cluster Name
|
<the name you will use to identify this Cisco CallManager cluster; accept the default name or enter another name>
|
Step 5 On the Enter Cisco CallManager IP Address and Port page, enter the following settings, then click Next.
Table 11 Settings for the Enter Cisco CallManager IP Address and Port Page
Field
|
Setting
|
IP Address/Name
|
<the IP address (or DNS name) of the Cisco CallManager server that you are connecting to Cisco Unity; if you are connecting to a Cisco CallManager cluster, we recommend entering the IP address (or DNS name) of a subscriber (secondary) Cisco CallManager server>
|
TCP Port
|
<the TCP port of the Cisco CallManager server that you are connecting to Cisco Unity; we recommend using the default setting>
|
You can click Ping Server to confirm that the IP address is correct.
Step 6 On the Enter Secondary Server Settings page, in the IP Address/Name field, enter the IP address (or DNS name) and port of all remaining subscriber (secondary) Cisco CallManager servers in the cluster and of the publisher (primary) Cisco CallManager server. Then click Add after entering each so that the IP addresses of all secondary servers appear in the list. If there is only one Cisco CallManager server in the cluster, leave this page blank.
The IP addresses of the subscriber (secondary) Cisco CallManager servers must appear in descending order, so that the subscriber (secondary) Cisco CallManager server at the top of the list is the first to take over call processing functions during failover, and the publishing (primary) Cisco CallManager server is the last.
You can click Ping Servers to confirm that the IP addresses are correct.
Step 7 If you want Cisco Unity to automatically reconnect to the primary Cisco CallManager server after failover has been corrected, check the Reconnect to Primary Cisco CallManager Server check box.
Step 8 Click Next.
Step 9 On the Enter Cisco CallManager MWI Extensions page, enter the following settings, then click Next.
Table 12 Settings for the Enter CallManager MWI Extensions Page
Field
|
Setting
|
MWI On Extension
|
<the extension you specified in Cisco CallManager Administration for turning MWIs on>
|
MWI Off Extension
|
<the extension you specified in Cisco CallManager Administration for turning MWIs off>
|
Step 10 On the Set Number of Voice Messaging Ports page, enter the following settings, then click Next.
Table 13 Settings for the Set Number of Voice Messaging Ports Page
Field
|
Setting
|
Number of Ports
|
<the number of voice messaging ports connecting Cisco Unity to the Cisco CallManager server; if Cisco Unity is connected to a single Cisco CallManager server, this number cannot be more than the number of ports set up on Cisco CallManager; if Cisco Unity is connected to multiple clusters of Cisco CallManager, this number cannot be more than the number of ports set up on the Cisco CallManager cluster, and the total number of ports on all clusters connected to Cisco Unity cannot be more than the number of ports enabled by the Cisco Unity license>
|
CallManager Device Name Prefix
|
<the prefix Cisco CallManager adds to the device name for voice messaging ports; this prefix must match the prefix used by Cisco CallManager>
|
You can click Verify to confirm that the CallManager device name prefix is correct.
Step 11 If another integration already exists, the Enter Trunk Access Code page appears. Enter the extra digits that Cisco Unity must use to transfer calls through the gateway to extensions on the other phone system with which it is integrated. Then click Next.
Step 12 On the Completing page, verify the settings you entered, then click Finish.
Step 13 At the prompt to restart the Cisco Unity services, click Yes. The Cisco Unity services restart.
Alternatively, you can restart the Cisco Unity services in UTIM on the Tools menu by clicking Restart Cisco Unity. Do not use the taskbar icon to restart the Cisco Unity for UTIM changes because the taskbar icon does not restart all of the Cisco Unity services.
To Enter the Voice Messaging Port Settings for the Integration
Step 1 After the Cisco Unity services restart, on the Windows Start menu, click Programs > Cisco Unity > Manage Integrations. UTIM appears.
Step 2 In the left pane of the UTIM window, click the phone system integration you are creating.
Step 3 In the right pane, click the phone system or cluster name.
Step 4 In the right pane, click the Ports tab.
Step 5 Enter the settings shown in Table 14 for the voice messaging ports.
For the voice messaging ports assigned to a given Cisco CallManager cluster, to get the best performance use the first voice messaging ports for incoming calls and the last ports to dial out. This helps minimize 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. Set the ports assigned to each Cisco CallManager cluster in this manner.
If the Cisco Unity server is connected to multiple clusters of Cisco CallManager and if the Cisco CallManager server has dedicated MWI voice messaging ports, set each dedicated MWI voice messaging port to Dialout MWI. For example, if the system has four clusters, dedicate four ports to send only MWIs, and assign one port to each cluster.
Caution In programming Cisco CallManager, 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.
Table 14 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. As a general guideline, set Answer Calls on approximately 75 percent of the ports.
|
Message Notification
|
Check this check box to designate the port for notifying subscribers of messages. Assign Message Notification to the least busy ports, which typically are those with the highest port numbers for the phone system. As a general guideline, set Message Notification, Dialout MWI, and TRAP Connection on approximately 25 percent of the 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, which typically are those with the highest port numbers for the phone system. As a general guideline, set Message Notification, Dialout MWI, and TRAP Connection on approximately 25 percent of the 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, which typically are those with the highest port numbers for the phone system. As a general guideline, set Message Notification, Dialout MWI, and TRAP Connection on approximately 25 percent of the ports.
|
Step 6 Repeat Step 5 for the remaining clusters, if any.
Step 7 Click Save.
Step 8 If Cisco Unity integrates with only one cluster of Cisco CallManager, exit UTIM, skip the remaining procedures in this section, and continue to the "Testing the Integration" section.
If Cisco Unity integrates with multiple clusters of Cisco CallManager, continue to the next procedure.
To Create an Integration with a Second Cluster of Cisco CallManager
If Cisco Unity integrates with only one cluster of Cisco CallManager, skip this procedure.
Step 1 In the left pane of the UTIM window, click the Cisco CallManager integration.
Step 2 On the Cluster menu, click New. A new cluster appears in the Cisco CallManager integration.
Step 3 Click the Servers tab, and enter the following settings.
Table 15 Settings for the Servers Tab
Field
|
Setting
|
Display Name
|
Enter Cisco CallManager Cluster 02 or another name you will use to identify this Cisco CallManager cluster.
|
Primary Server
|
IP Address/Name
|
<the IP address (or DNS name) of a subscriber (secondary) Cisco CallManager server>
|
Port
|
<the TCP port of the Cisco CallManager server that you are connecting to Cisco Unity; we recommend using the default setting>
|
CallManager Device Name Prefix
|
<the prefix Cisco CallManager adds to the device name for voice messaging ports; this prefix must match the prefix used by the Cisco CallManager cluster>
|
Secondary Servers
|
IP Address/Name
|
<the IP address (or DNS name) of all remaining subscriber (secondary) Cisco CallManager servers in the cluster and the publisher (primary) Cisco CallManager server; then click Add after entering each so that the IP addresses of all secondary servers appear in the Address list; if there is only one Cisco CallManager server in the cluster, leave this field blank>
|
Port
|
<the TCP port of the Cisco CallManager server that you are connecting to Cisco Unity; we recommend using the default setting>
|
Reconnect to the Primary Cisco CallManager server
|
Check this check box if you want Cisco Unity to automatically reconnect to the primary Cisco CallManager server in the cluster after failover has been corrected.
|
Step 4 Click the MWI tab, and enter the following settings.
Table 16 Settings for the MWI Tab
Field
|
Setting
|
On Extension
|
<the extension you specified in Cisco CallManager Administration of the cluster for turning MWIs on>
|
Off Extension
|
<the extension you specified in Cisco CallManager Administration of the cluster for turning MWIs off>
|
Step 5 Click the Ports tab, and click Add Port.
Step 6 In the Add Port dialog box, enter the number of voice messaging ports on Cisco Unity you want to connect to the Cisco CallManager cluster, and click OK.
This number cannot be more than the number of ports set up on the Cisco CallManager cluster. This number cannot bring the total number of port installed on the Cisco Unity server to more than the number of ports enabled by the Cisco Unity license.
Step 7 Click the Servers tab, and click Verify Servers to confirm that the Cisco CallManager server information is correct.
Step 8 Click the RTP tab, and confirm that the Automatically Assign option is selected.
Step 9 In the UTIM window, click Save.
Step 10 At the prompt to restart the Cisco Unity services, click Yes. The Cisco Unity services restart.
Note When restarting Cisco Unity, use the UTIM prompt instead of the Cisco Unity icon in the Windows taskbar. The taskbar icon does not restart all of the Cisco Unity services.
Step 11 After the Cisco Unity services restart, on the Windows Start menu, click Programs > Cisco Unity > Manage Integrations. UTIM appears.
Step 12 In the left pane of the UTIM window, click the Cisco CallManager integration.
Step 13 In the right pane, click the name of the cluster name you created in this procedure.
<
