Cisco CallManager 3.0 Integration Guide for Cisco Unity 3.1 [Cisco Unity]

Table Of Contents

Cisco CallManager 3.0 Integration Guide for Cisco Unity 3.1

Integration Overview

Integration Steps When Integrating with Cisco CallManager for the First Time

Integration Steps When Updating to a More Recent Version of Cisco CallManager

Integration Steps When Converting from a Dual Phone System Integration to a Cisco CallManager-Only Integration

Integration Steps When Converting from an Integration with a Traditional, Circuit-Switched Phone System to an Integration with Cisco CallManager

Requirements

Integration Description

Integration Features

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

Programming the Cisco CallManager Phone System

Setting Up the Gateways Servicing Cisco Unity

Installing, Configuring, and Testing the TSP

Configuring Cisco Unity for the Integration

Testing the Integration

Integrating a Secondary Server for Cisco Unity Failover

Requirements

Integration Description

Setting Up the Secondary Server for Failover

Switching Call Processing from a Cisco CallManager Failover Server to the Primary Server

Changing TSP Settings

Changing the Number of uOne Ports

Removing Dialogic Voice Card Software

Troubleshooting the Cisco CallManager Integration

The Default Ear Piece and Speaker Volume on Cisco 7960 Phones Is Too Loud

Cisco Unity Does Not Answer When the Extension for Cisco Unity Is Dialed

Dual Phone System Integration

Dual Phone System Integration Overview

Integration Steps When No Phone Systems Are Installed

Integration Steps When a Circuit-Switched Phone System Is Already Installed

Integration Steps When Cisco CallManager Is Already Installed

Requirements

Changing Cisco Unity Administrator Settings

Changing the Number of Installed Ports

Appendix: Remapping Extension Numbers

The Remapping Feature

Setting Up Cisco Unity to Remap Extension Numbers

Syntax and Examples

Appendix: Assigning Dialogic Ports for a Dual Phone System Integration

Appendix: Documentation and Technical Assistance

Conventions

Cisco Unity Documentation

Obtaining Documentation

Cisco.com

Documentation CD-ROM

Ordering Documentation

Documentation Feedback

Obtaining Technical Assistance

Cisco.com

Technical Assistance Center

Cisco TAC Website

Cisco TAC Escalation Center

Obtaining Additional Publications and Information

Cisco CallManager 3.0 Integration Guide for Cisco Unity 3.1

Revised May 2 2003

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

Integration Overview

Before doing the following integration steps, confirm that the Cisco Unity server is ready for the integration by completing the applicable tasks in the Cisco Unity Installation Guide.

Integration Steps When Integrating with Cisco CallManager for the First Time

To set up a new integration with only Cisco CallManager, follow these steps.

1. Review the system and equipment requirements to confirm that all Cisco CallManager and Cisco Unity system 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.

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

5. Install and configure the TSP on the Cisco Unity server. See the "Installing, Configuring, and Testing the TSP" section.

6. Configure Cisco Unity for the integration. See the "Configuring Cisco Unity for the Integration" section.

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

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

Integration Steps When Updating to a More Recent Version of Cisco CallManager

To set up an integration with an updated version of Cisco CallManager, follow these steps.

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

The Cisco Unity system key does not need to be upgraded when you update Cisco CallManager. If you are changing the number of ports, the system key must be upgraded.

2. Program Cisco CallManager. See the "Programming the Cisco CallManager Phone System" section.

3. If necessary, install and configure the appropriate version of the TSP on the Cisco Unity server. Refer to the TSP release notes for the required version of the TSP and the installation instructions, available at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/tsp/index.htm.

4. Configure Cisco Unity for the integration. See the "Configuring Cisco Unity for the Integration" 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.

Integration Steps When Converting from a Dual Phone System Integration to a Cisco CallManager-Only Integration

To convert from a dual phone system integration to a Cisco CallManager-only integration, follow these steps.

1. Upgrade the system key.

2. Confirm that the integration is enabled. See the "To Confirm That the Integration Is Enabled" section.

3. Remove the existing TSP on Cisco Unity. See the "To Remove the Existing TSP" section.

4. Remove the Dialogic voice cards from the Cisco Unity server.

5. Remove the Dialogic voice card software that is installed on the Cisco Unity server. See the "To Remove Dialogic Voice Card Software" section.

6. Remove the Cisco Unity dependence on the Dialogic service. See the "To Remove the Cisco Unity Dependence on the Dialogic Service" section.

7. Reinstall the TSP. See the "To Reinstall the TSP" section.

8. Change the Cisco Unity Administrator settings. See the "Changing Cisco Unity Administrator Settings" section.

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

Integration Steps When Converting from an Integration with a Traditional, Circuit-Switched Phone System to an Integration with Cisco CallManager

To convert an existing integration of Cisco Unity and a traditional, circuit-switched phone system to an integration of Cisco Unity and Cisco CallManager, do the following steps.

1. Upgrade the system key.

2. Confirm that the integration is enabled. See the "To Confirm That the Integration Is Enabled" section.

3. Install, configure, and test the TSP. See the "Installing, Configuring, and Testing the TSP" section.

4. Remove the Dialogic voice card software that is installed on the Cisco Unity server. See the "To Remove Dialogic Voice Card Software" section.

5. Remove the Cisco Unity dependence on the Dialogic service. See the "To Remove the Cisco Unity Dependence on the Dialogic Service" 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 CallManager integration supports configurations of the following components:

Phone System

•A Cisco IP telephony applications server consisting of Cisco CallManager 3.0(x), 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.

Cisco Unity Server

•Cisco Unity version 3.1(x), installed and ready for the integration as described in the Cisco Unity Installation Guide.

•A system key with the integration type set to "TAPI" and with the appropriate number of voice messaging ports enabled. If you are integrating Cisco Unity with two phone systems (Cisco CallManager and a second, non-IP phone system), the integration type on the system key must be set to "Multiple Integrations."

•A Cisco license for each Cisco Unity port.

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

Some countries require a phone system between the public phone network and the gateway.

The following steps give an overview of the path an external call takes through the Cisco AVVID network.

1. When an external call arrives, the Cisco gateway sends the call over the LAN to the machine on which Cisco CallManager is installed.

2. For Cisco CallManager lines that are configured to route calls to Cisco Unity, CallManager routes the call to an available Cisco Unity extension.

3. Cisco Unity answers the call and plays the opening greeting.

4. During the opening greeting, the caller enters either the name of a subscriber or an extension, for example, 1234.

5. Cisco Unity notifies Cisco CallManager that it has a call for extension 1234.

6. At this point, the path of the call depends on whether Cisco Unity is set up to do supervised transfers or release transfers.

Supervised transfers

While Cisco Unity holds the call, Cisco CallManager attempts to establish a connection with extension 1234.

•If the line is available, Cisco CallManager connects the call from Cisco Unity to extension 1234. Cisco CallManager and Cisco Unity drop out of the loop, and the call is connected directly from the Cisco gateway to extension 1234.

•If the line is busy or unanswered, Cisco CallManager gives that information to Cisco Unity, and Cisco Unity does the operation the subscriber has specified, for example, it takes a message.

Release transfers
(or blind transfers)

Cisco Unity passes the call to Cisco CallManager, and CallManager sends the call to extension 1234 without waiting to determine if the line is available. Then CallManager and Cisco Unity drop out of the loop. If Cisco Unity is set up to do release transfers, and if you want Cisco Unity to take a message when a line is busy or unanswered, you must configure each phone to forward calls to Cisco Unity when the line is busy or unanswered.

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's extension.

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 to be 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 Media Master connections.

•If Cisco Unity is connected to multiple clusters of Cisco CallManager and if the Cisco CallManager server has dedicated MWI voice messaging ports, the number of voice messaging ports that will be dedicated to set MWIs.

The Number of Voice Messaging Ports to Install

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

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

•The expected length of each message that calls 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 Media Master connections needed when call traffic is at its peak. (Media Master connections are used by Cisco Unity web applications and e-mail clients to playback and record over the phone.)

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. As a general guideline, assign approximately 75% of the voice messaging ports to answer calls.

You can set voice messaging ports to both answer calls and to dial out (for example, to set MWIs).

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

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

•Turn MWIs on and off for the subscriber extension.

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

•Make a Media Master 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. As a general guideline, assign approximately 25% of the voice messaging ports to dial out.

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 Activate 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 activate 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 uOne ports for a Cisco Unity server without failover or the primary server with failover, do all the procedures in this section.

•When configuring uOne ports for a secondary server with failover, do only the "To Add uOne Ports to Cisco CallManager" procedure.

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

Step 1 In the Cisco CallManager Administration, click Route Plan > Partition.

Step 2 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 3 Click Insert.

Step 4 Click New.

Step 5 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 6 Click Insert.

Step 7 Click Route Plan > Calling Search Space.

Step 8 In the Calling Search Space Name field, enter a name for the calling search space that will include the partition created in Step 2 and Step 3. For example, enter "VMRestrictedCSS."

Step 9 If you want, in the Description field, enter a description of the calling search space. For example, enter "Voice mail port directory numbers."

Step 10 In the Available Partitions field, double-click the name of the partition created in Step 2 and Step 3. 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 11 Click Insert.

Step 12 In the list of calling search spaces on the left, click the name of the calling search space that includes the partitions containing the subscriber phones.

Step 13 In the Available Partitions field, click the name of the partition created in Step 4 through Step 6. For example, click VMPilotNumberPT. Then, click the down arrow to add the partition to the Selected Partitions list. 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 included in the calling search space with the partition containing the subscriber phones, the phones will not be able to dial the Cisco Unity server.

Step 14 Click Update.

Step 15 Repeat Step 12 through Step 14 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 uOne Ports to Cisco CallManager

Add a uOne port to Cisco CallManager for each port that you are connecting to Cisco Unity.

Step 1 In the Cisco CallManager Administration, click Device > Cisco uOne Port.

Step 2 In the upper-right corner of the Cisco uOne Port Configuration page, click Use the Cisco uOne Port Wizard. The Cisco uOne Port Wizard appears.

Step 3 Click Create a New Cisco uOne Server and Add Ports to It and click Next.

Step 4 The name of the uOne server appears. We recommend that you accept the default name for the uOne server or, if necessary, enter a different name with no more than nine characters, then click Next.

The default name (even if you do not use it) becomes part of the name for ports as follows:
<the uOne port name>-VI

For example, the default uOne port name is CiscoUM1, and the device name prefix for ports is CiscoUM1-VI. The device name prefix is used by the Cisco Unity-CM service provider. For details, see Table 4.

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

Step 5 Enter the number of ports you want to add but not more than is enabled on the system key, then click Next.

Step 6 Enter the following uOne device settings, then click Next.

Table 1 Settings for the uOne Devices

Field

Setting

Description

Enter Cisco uOne Port or other description that you want.

Device Pool

Click Default.

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 and message notifications).

Location

Accept the default of None.

Step 7 Enter the following uOne directory number settings, then click Next.

Table 2 Settings for the uOne Directory Numbers

Field

Setting

Pilot Number

Enter the pilot number for the uOne ports.

The pilot number is the extension number of the first uOne port and is the number subscribers enter to listen to their voice messages.

If Cisco Unity is configured for failover and you are adding uOne ports for the secondary server, the pilot number is the extension number of the first uOne port on the secondary server, but it is not the number subscribers enter to listen to their voice messages.

Route Partition

Click the name of the partition that you set up for all uOne port directory numbers except the first uOne 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 uOne port directory numbers except the first uOne port, as set in Step 8 of the "To Add Partitions and a Calling Search Space to Contain the uOne Ports" section. For example, click VMRestrictedCSS.

This calling search space does not include partitions containing subscriber phones, so subscribers can dial the uOne pilot number but not any other uOne ports.

Display

Accept the default of Voicemail.

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

Step 8 Enter the operator number or the number you want the last port to forward to when busy, if applicable, and click Next.

Step 9 The settings for the new ports appear. Click Finish.

Step 10 Click Go to Cisco uOne 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 "Configuring Cisco Unity for the Integration" section. For further instructions on configuring the uOne ports, see the "Integrating a Secondary Server for Cisco Unity Failover" section.

To Set the Partition and Calling Search Space for the First uOne Port

Step 1 On the Cisco uOne Port Configuration page, in the Cisco uOne Ports list, click the first uOne port, which is assigned the uOne pilot number.

Step 2 Under Directory Number Information, in the Partition field, click the partition that you set up to contain the first uOne port. For example, click VMPilotNumberPT.

Step 3 Click Update.

To Specify MWI and Voice Mail Directory Numbers

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

Step 2 On the left of the Service Parameters Configuration page, click the server that you created in the "To Add uOne Ports to Cisco CallManager" procedure.

Step 3 In the Configured Services list, click Cisco CallManager. The list of service parameters appears.

Step 4 Click one of the service parameters shown in the following table.

Table 3 Settings for the Service Parameters

Service Parameter to Configure

Setting

MessageWaitingOffDN

The unique extension that turns MWIs off.

MessageWaitingOnDN

The unique extension that turns MWIs on.

VoiceMail

The extension that users call to access Cisco Unity. This is typically the extension number (Directory Number, in the Cisco CallManager Administration) of the first uOne port. If you specify an extension for VoiceMail, then users can call Cisco Unity by pressing the Messages button on their Cisco phones.

VoiceMailMaximumHopCount

Used together with AdvancedCallForwardHopFlag, the maximum number of uOne ports skipped to find the next available uOne 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 in the Value field.

Step 5 Change or enter a setting, as applicable.

Step 6 Click Update to save the setting.

Step 7 Repeat Step 4 through Step 6 to specify the setting for the remaining service parameters.

Step 8 In the Configured Services list, click Cisco Messaging Interface.

Step 9 In the Configured Service Parameters list, click VoiceMailDn.

Step 10 Confirm that the Value field is blank.

Step 11 If you changed the service parameter setting to blank, click Update to save the setting.

Step 12 Shut down and restart the Cisco CallManager server.

If the plan for 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 uOne Ports So Incoming Calls Are Forwarded Only to Answering Ports

Step 1 In the Cisco CallManager Administration, click Device > Cisco uOne Port.

Step 2 In the Cisco uOne Ports list, click the name of the last port that answers calls in Cisco Unity.

Step 3 Set the Forward Busy and Forward No Answer fields to forward to the first port that answers calls in Cisco Unity.

Step 4 Click Update.

Step 5 In the Cisco uOne Ports list, click the name of a the first 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 uOne port that answers calls in Cisco Unity.

Step 7 Click Update.

Step 8 Repeat Step 5 through Step 7 for all remaining 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 Ports for Multiple Clusters of Cisco CallManager

Step 1 In the Cisco Unity Administrator, select at least one 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 Device > Cisco uOne Port.

Step 3 In the Cisco uOne Ports list, 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 uOne port or of the operator.

Step 5 Click Update.

Step 6 In the Cisco uOne Ports list, click the name of a dedicated MWI port.

Step 7 Delete the extensions in the Forward Busy and Forward No Answer fields 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.

If you want to remap extension numbers (for example, when multiple subscribers use a single phone, or when multiple extension numbers on a single phone should go to a single subscriber greeting), see the "Appendix: Remapping Extension Numbers" section.

Setting Up the Gateways Servicing 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.

Installing, Configuring, and Testing the TSP

Do the following procedures in the order given.

If you are converting an integration with a circuit-switched phone system to an integration with Cisco CallManager, see the "Integration Steps When Converting from a Dual Phone System Integration to a Cisco CallManager-Only Integration" section for additional instructions.

While the Cisco Unity compact disc has the most recent version of the TSP at the time of publication, new versions are released periodically. The most recent version of the TSP is available through Cisco Connection Online (CCO) at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/tsp/index.htm.

To Remove the Existing TSP

If the most recent version of the TSP is already installed on the Cisco Unity server, or if the TSP is not installed, skip to the procedure "To Install the TSP and Wave Driver."

In all other cases (for example, when upgrading Cisco Unity from an earlier version), do this procedure.

Step 1 Stop Cisco Unity (right-click the Cisco Unity icon in the system tray, then click Stop Unity).

Step 2 On the Windows Start menu, click Settings > Control Panel > Add/Remove Programs.

Step 3 In the list, click Cisco Unity-CM TSP.

Note In versions earlier than 3.1(1), the Cisco Unity-CM TSP was known as the AV-Cisco TSP.

Step 4 Click Remove.

Step 5 Click Yes.

Step 6 Close Control Panel.

Step 7 Continue with the next procedure.

To Install the TSP and Wave Driver

Cisco Unity 3.1(1) or later must be installed before you install the TSP and wave driver.

Step 1 On the Cisco Unity server, exit the Cisco Unity software.

Step 2 Insert Cisco Unity Disc 1 into the CD-ROM drive on the Cisco Unity server.

Step 3 Browse to the \Cisco directory.

Step 4 Run SkinnySetup.exe.

Step 5 Follow the on-screen instructions.

Step 6 When you are prompted to restart the server, remove the Cisco Unity disc from the CD-ROM drive, exit the Cisco Unity software, then restart the server.

Step 7 Continue with the next procedure.

To Configure the TSP

Step 1 Log on to Windows. The Cisco Unity-CM Service Provider dialog box appears.

The Cisco Unity-CM Service Provider dialog box appears automatically only the first time you log on after installing the TSP and wave driver. To change settings later, see the "Changing TSP Settings" section.

Step 2 Click Add. The Add CallManager IP Address dialog box appears.

Step 3 Enter the IP address of the Cisco CallManager server that is connected to Cisco Unity, and click OK.

Step 4 In the Cisco Unity-CM Service Provider Settings dialog box, enter values as shown in the following table.

Table 4 Settings for the Cisco Unity-CM Service Provider Settings Dialog Box

Field

Setting

Primary CallManager IP Address

The IP address of the Cisco CallManager server that Cisco Unity will usually receive calls from.

Primary CallManager IP Port

The IP port that Cisco CallManager uses. The default is 2000.

Number of Voice Ports

The number of Cisco CallManager uOne ports that are connected to Cisco Unity.

Device Name Prefix

Enter the following characters without any spaces:

•<the uOne port name>

•-VI

For example, if the uOne port name is CiscoUM1, the device name prefix is CiscoUM1-VI.

Make sure you enter this prefix exactly as it appears in the Cisco CallManager Administration. Otherwise, the integration will not work.

The uOne port name is set in the "To Add uOne Ports to Cisco CallManager" section.

MessageWaitingOnDN

The extension that you specified, in the Cisco CallManager Administration, for turning MWIs on. See the "To Specify MWI and Voice Mail Directory Numbers" section.

MessageWaitingOffDN

The extension that you specified, in the Cisco CallManager Administration, for turning MWIs off. See the "To Specify MWI and Voice Mail Directory Numbers" section.

CallManager Failover IP Addresses

The IP addresses of backup Cisco CallManager servers, if any. Backup Cisco CallManager servers must be in the same cluster as the primary Cisco CallManager server.

CallManager Device List

A display-only list of the names of the uOne ports that Cisco Unity looks for on the current Cisco CallManager server. This list is constructed by appending numbers starting with 1 to the setting of device name prefix.

The names in this list must exactly match the names of the uOne ports in the Cisco CallManager Administration. Otherwise, calls will not be correctly transferred to Cisco Unity.

Automatically Reconnect to the Primary CCM on Failover

A check box that enables Cisco Unity to reconnect to the primary Cisco CallManager server after a failover is corrected.

If there is no secondary Cisco CallManager server for failover, uncheck this box.

Step 5 Repeat Step 2 through Step 4 for each additional Cisco CallManager cluster that you want to link to Cisco Unity. Each IP address is the primary Cisco CallManager of a cluster.

Step 6 Click OK to close the Cisco Unity-CM Service Provider Settings dialog box.

Step 7 Continue with the next procedure.

To Test the TSP

Step 1 If the Cisco Unity-CM Service Provider dialog box is already displayed, skip to Step 7. Otherwise, continue with Step 2.

Step 2 On the Cisco Unity server, log on to Windows as an administrator.

Step 3 Click Start > Settings > Control Panel.

Step 4 Double-click Phone and Modem Options. The Phone and Modem Options dialog box appears.

Step 5 Click the Advanced tab.

Step 6 Click Cisco Unity-CM Service Provider, then click Configure. The Cisco Unity-CM Service Provider dialog box appears.

Step 7 Click Test. The settings you specified in Step 4 of the "To Configure the TSP" section are checked against the current settings in the Cisco CallManager Administration.

If the test succeeds, a message box displays the message "The test completed successfully." If the test fails, one of the error messages shown in the following table appears. Troubleshoot the problem as described in the "Comments" column, and repeat this step until the test succeeds. Then continue with Step 8.

Table 5 Error Messages from the Integration Test

Error Message

Comments

Pinging CallManager server (<IP address>) failed. Make sure the IP address is valid, the server is running, and the network connection is working.

No computers on the network have the IP address that you specified in Primary CallManager IP Address. Confirm that this address is valid. If the value is correct, or if the problem persists after you change the value, troubleshoot the problem as you would a network connectivity problem.

The voice device named <device name> does not respond to registration requests. Ensure that the device has been created in the CallManager database and that the device name prefix is correct.

Confirm that the values in CallManager Device List (see Step 4 of the "To Configure the TSP" section) match the names of the uOne ports that you created (see the "To Add uOne Ports to Cisco CallManager" section). If not, change the setting for Device Name Prefix or the names of the uOne ports, as necessary.

Could not connect to the CallManager. Confirm that all Cisco services are started on the CallManager server.

The IP address that you specified in Primary CallManager IP Address is a valid address, but Cisco CallManager services are not running on that computer, possibly because Cisco CallManager is not installed on the server with that IP address. Confirm that this address is correct and that the Cisco CallManager services are running.

No wave devices were found on the system. The wave driver is either not installed correctly or the computer needs to be rebooted to update its configuration.

Exit the Cisco Unity software, then restart the server.

Step 8 Click OK to close the Cisco Unity-CM Service Provider dialog box. The following message appears:
This computer needs to be rebooted to update the wave driver.
Step 9 Click OK.

Step 10 Click Close to close the Phone and Modem Options dialog box.

Step 11 Close Control Panel.

Step 12 Exit the Cisco Unity software, then restart the server.

Configuring Cisco Unity for the Integration

After ensuring that the Cisco Unity server is ready for the integration by completing the appropriate tasks in the Cisco Unity Installation Guide, do the following procedures to confirm that the integration is enabled and to enter the port settings.

To Confirm That the Integration Is Enabled

Step 1 On the Cisco Unity server, go to the Cisco Unity Administrator by doing one of the following:

•In Internet Explorer, go to http://<server name>/web/sa.

•Double-click the desktop shortcut to the Cisco Unity Administrator.

Step 2 Go to System > Licensing > Licensed Features.

Step 3 In the Integration field, confirm that the setting is TAPI for a single phone system integration or Multiple Integrations for a dual phone system integration.

Step 4 If the setting is not TAPI or Multiple Integrations, contact your sales representative for the necessary system key.

Step 5 Go to System > IP Switch. Confirm that the settings match those in the following table. If the settings are incorrect, integration features may not be enabled.

Table 6 Switch Settings

Switch Parameter

Required Setting

Manufacturer

Cisco

Model

CallManager

Switch PBX Software Version

3.01 or later

Integration

TAPI

Step 6 Click the Save icon.

Step 7 Close the Cisco Unity Administrator.

Step 8 For the phone system settings to take effect, exit the Cisco Unity software, then restart the server.

To Enter Port Settings

Step 1 In the Cisco Unity Administrator, go to System > Ports.

Step 2 Select a port in the table.

Step 3 Indicate the settings for the port.

For the voice messaging ports assigned to a given Cisco CallManager cluster, 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.

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.

If the Cisco Unity server is connected to multiple clusters of Cisco CallManager, dedicate one voice messaging port to each cluster and set the port to Dialout MWI. Do not include these dedicated MWI voice messaging ports in the Cisco Call Manager hunt group for incoming calls but include the ports in a hunt group for sending MWIs to all clusters. For example, if the system has four clusters, dedicate four ports to send only MWIs, and assign one to port to each cluster. For details, see the "To Set Up MWI Ports for Multiple Clusters of Cisco CallManager" section.

Step 4 Repeat Step 2 and Step 3 for the remaining ports.

Step 5 Click the Save icon.

Step 6 For the settings to take effect, exit and restart the Cisco Unity software.

Testing the Integration

To test whether Cisco Unity and the phone system are integrated correctly, do the procedures in the order listed.

If any of the steps indicates a failure, refer to the following documentation as appropriate:

•The installation guide for the phone system

•Cisco Unity Troubleshooting Guide

•The setup information earlier in this document

To Set Up the Test Configuration

Step 1 Set up two test extensions (Phone 1 and Phone 2) on the same phone system that Cisco Unity is connected to.

Step 2 Set Phone 1 to forward calls to the Cisco Unity pilot number when calls are not answered.

Step 3 In the Cisco Unity Administrator, go to the Subscribers > Subscribers > Profile page.

If Example Subscriber is not displayed, click the Find icon (the magnifying glass) in the title bar, then click Find, and select Example Subscriber in the list that appears.

Step 4 In the Extension field, enter the extension of Phone 1.

Step 5 Click the Save icon.

Step 6 In the navigation bar, click Call Transfer to go to the Subscribers > Subscribers > Call Transfer page for Example Subscriber.

For more information on transfer settings, refer to the "Subscriber Template Call Transfer Settings" section in the online Help for the Cisco Unity Administrator.

Step 7 Under Transfer Incoming Calls, click Yes, Ring Subscriber's Extension, and confirm that the extension number is for Phone 1.

Step 8 Under Transfer Type, click Release to Switch.

Step 9 Click the Save icon.

Step 10 In the navigation bar, click Messages to go to the Subscribers > Subscribers > Messages page for Example Subscriber.

Step 11 Under Message Waiting Indicators (MWIs), check Use MWI for Message Notification.

Step 12 In the Extension field, enter x.

Step 13 Click the Save icon.

Step 14 Open the Status Monitor by doing one of the following:

•In Internet Explorer, go to http://<server name>/web/sm.

•Double-click the desktop shortcut to the Status Monitor.

•On the Windows taskbar next to the clock, right-click the Cisco Unity icon and click Status Monitor.

To Test an External Call with Release Transfer

Step 1 From Phone 2, enter the access code necessary to get an outside line, then enter the number outside callers use to dial directly to Cisco Unity.

Step 2 On the Status Monitor, note the port that handles this call.

Step 3 When you hear the opening greeting, enter the extension for Phone 1. Hearing the opening greeting means that the port is configured correctly.

Step 4 Confirm that Phone 1 rings and that you hear a ringback tone on Phone 2. Hearing a ringback tone means that Cisco Unity released the call and transferred it to Phone 1.

Step 5 Leaving Phone 1 unanswered, confirm that the state of the port handling the call changes to "Idle." This state means that release transfer is successful.

Step 6 Confirm that, after the number of rings that the phone system is set to wait, the call is forwarded to Cisco Unity and that you hear the greeting for Example Subscriber. Hearing the greeting means that the phone system forwarded the unanswered call and the call-forward information to Cisco Unity, which correctly interpreted the information.

Step 7 On the Status Monitor, note the port that handles this call.

Step 8 Leave a message for Example Subscriber and hang up Phone 2.

Step 9 On the Status Monitor, confirm that the state of the port handling the call changes to "Idle." This state means that the port was successfully released when the call ended.

Step 10 Confirm that the MWI on Phone 1 is activated. The activated MWI means that the phone system and Cisco Unity are successfully integrated for turning on MWIs.

To Test an Internal Call with Release Transfer

Step 1 From Phone 1, enter the internal pilot number for Cisco Unity.

Step 2 When asked for your password, enter 12345. Hearing the request for your password means that the phone system sent the necessary call information to Cisco Unity, which correctly interpreted the information.

Step 3 Confirm that you hear the recorded voice name for Example Subscriber. Hearing the voice name means that Cisco Unity correctly identified the subscriber by the extension.

Step 4 When asked whether you want to listen to your messages, press 1.

Step 5 After listening to the message, press 3 to delete the message.

Step 6 Confirm that the MWI on Phone 1 is deactivated. The deactivated MWI means that the phone system and Cisco Unity are successfully integrated for turning off MWIs.

Step 7 Hang up Phone 1.

Step 8 On the Status Monitor, confirm that the state of the port handling the call changes to "Idle." This state means that the port was successfully released when the call ended.

To Set Up Supervised Transfer on Cisco Unity

Step 1 In the Cisco Unity Administrator, go to the Subscribers > Subscribers > Call Transfer page.

If Example Subscriber is not displayed, click the Find icon (the magnifying glass) in the title bar, then click Find, and select Example Subscriber in the list that appears.

For more information on transfer settings, refer to the "Subscriber Template Call Transfer Settings" section in the online Help for the Cisco Unity Administrator.

Step 2 Under Transfer Type, click Supervise Transfer.

Step 3 Set the Rings to Wait For field to 3.

Step 4 Click the Save icon.

To Test Supervised Transfer

Step 1 From Phone 2, enter the access code necessary to get an outside line, then enter the number outside callers use to dial directly to Cisco Unity.

Step 2 On the Status Monitor, note the port that handles this call.

Step 3 When you hear the opening greeting, enter the extension for Phone 1. Hearing the opening greeting means that the port is configured correctly.

Step 4 Confirm that Phone 1 rings and that you do not hear a ringback tone on Phone 2. Instead, you should hear the indication your phone system uses to mean that the call is on hold (for example, music or beeps).

Step 5 Leaving Phone 1 unanswered, confirm that the state of the port handling the call remains "Busy." This state and hearing an indication that you are on hold mean that Cisco Unity is supervising the transfer.

Step 6 Confirm that, after three rings, you hear the greeting for Example Subscriber. Hearing the greeting means that Cisco Unity successfully recalled the supervised-transfer call.

Step 7 During the greeting, hang up Phone 2.

Step 8 On the Status Monitor, confirm that the state of the port handling the call changes to "Idle." This state means that the port was successfully released when the call ended.

To Return Example Subscriber to the Default Settings

Step 1 In the Cisco Unity Administrator, go to the Subscribers > Subscribers > Call Transfer page.

If Example Subscriber is not displayed, click the Find icon (the magnifying glass) in the title bar, then click Find, and select Example Subscriber in the list that appears.

Step 2 Under Transfer Incoming Calls, click No (Send Directly to Subscriber's Greeting).

Step 3 In the navigation bar, click Profile to go to the Subscribers > Subscribers > Profile page.

Step 4 In the Extension field, enter 99990.

Step 5 Click the Save icon.

Step 6 In the navigation bar, click Messages to go to the Subscribers > Subscribers > Messages page for Example Subscriber.

Step 7 Under Message Waiting Indicators (MWIs), uncheck Use MWI for Message Notification.

Step 8 Click the Save icon.

Integrating a Secondary Server for Cisco Unity Failover

A Cisco Unity failover server is a secondary (or backup) server that provides voice messaging services if the primary Cisco Unity server becomes inactive. For information on installing a secondary server, refer to the Cisco Unity Installation Guide, available on Cisco.com at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_installation_and_configuration_guide_books_list.html.

For information on failover, refer to the Cisco Unity Failover Guide, available on Cisco.com at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_installation_and_configuration_guide_books_list.html.

Note Cisco Unity failover is supported only for release 3.1(2) and later.

Requirements

The following components are required to integrate a secondary Cisco Unity server:

•One secondary Cisco Unity server for each primary server installed and ready for the integration, as described in the Cisco Unity Installation Guide and earlier in this integration guide.

•A system key that enables the integration, the appropriate number of voice messaging ports, and the secondary server.

Integration Description

The phone system communicates with both the primary and secondary servers through the LAN. Figure 4 shows the required connections.

Figure 4 Connections Between Cisco CallManager and the Cisco Unity Servers

The primary and secondary servers act in the following manner:

•When the primary server is operating normally, the secondary server is inactive.

•When the primary server becomes inactive, the secondary server becomes active.

•When the primary server becomes active again, the secondary server becomes inactive.

Setting Up the Secondary Server for Failover

Before proceeding, confirm that Cisco CallManager is configured as described in the "Programming the Cisco CallManager Phone System" section earlier in this integration guide, including the following:

•For each uOne port, the Forward Busy and Forward No Answer fields are set to forward to the next uOne port (the default configuration of the Cisco uOne Port Wizard).

•The name of the uOne server and uOne ports that serve the secondary server are different from the name of the uOne server and uOne ports that serve the primary server.

Do the following two procedures to integrate the secondary server.

To Configure Cisco CallManager

Step 1 In the Cisco CallManager Administration, click Device > Cisco uOne Port.

Step 2 For the last uOne port that answers calls on the primary server, set the Forward Busy field to the first uOne port on the primary server.

If there are uOne ports on the primary server that do not answer calls (for example, ports set only to Dialout MWI), leave the Forward Busy field blank.

Caution In programming Cisco CallManager, do not send calls to ports in Cisco Unity that cannot answer calls (ports that are not set to Answer Calls). For example, if a port is set only to Dialout MWI, do not send calls to it.

For a diagram of the port settings, see Figure 5.

Step 3 For all uOne ports that answer calls on the primary server, set the Forward No Answer field to the first uOne port on the secondary server.

If there are uOne ports on the primary server that do not answer calls (for example, ports set only to Dialout MWI), set the Forward No Answer field to the first uOne port on the primary server.

Caution In programming Cisco CallManager, do not send calls to ports in Cisco Unity that cannot answer calls (ports that are not set to Answer Calls). For example, if a port is set only to Dialout MWI, do not send calls to it.

For a diagram of the port settings, see Figure 5.

Step 4 For the last uOne port that answers calls on the secondary server, set the Forward Busy and Forward No Answer fields to the first uOne port on the secondary server.

If there are uOne ports on the secondary server that do not answer calls (for example, voice mail ports set only to Dialout MWI), leave the Forward Busy field blank and set the Forward No Answer field to the first uOne port on the secondary server.

Caution In programming Cisco CallManager, do not send calls to ports in Cisco Unity that cannot answer calls (ports that are not set to Answer Calls). For example, if a port is set only to Dialout MWI, do not send calls to it.

For a diagram of the port settings, see Figure 5.

Figure 5 Cisco CallManager uOne Port Configuration for Cisco Unity Failover

To Set Up the Secondary Server for Failover

Step 1 Install a secondary server with the same configuration as the primary server. For installation instructions, refer to the Cisco Unity Installation Guide.

Step 2 In the Cisco Unity Administrator of the secondary server, go to the System > IP Switch page.

Step 3 Enter the settings to match the integration settings on the primary server.

Step 4 Go to the System > Ports page, and enter the settings to match the port settings on the primary server.

Step 5 For the settings to take effect, exit the Cisco Unity software, then restart the server.

Switching Call Processing from a Cisco CallManager Failover Server to the Primary Server

If the primary Cisco CallManager server fails and a failover server starts processing calls, Cisco Unity automatically starts sending calls to the failover server. When the problem with the primary Cisco CallManager server has been resolved, Cisco Unity automatically resumes sending calls to that server.

If the primary Cisco CallManager server is not set up for automatic reconnect, and you are ready for that server to start processing calls again, do the following procedure.

To Switch Call Processing from a Failover Cisco CallManager Server to the Primary Cisco CallManager Server

Caution Do not do this operation during regular business hours. When you switch from the failover Cisco CallManager to the primary Cisco CallManager, all current calls are immediately disconnected.

Step 1 On the Cisco Unity server, log on to Windows as an administrator.

Step 2 Click Start > Settings > Control Panel.

Step 3 Double-click Phone and Modem Options. The Phone and Modem Options dialog box appears.

Step 4 Click the Advanced tab.

Step 5 Click Cisco Unity-CM Service Provider, then click Configure. The Cisco Unity-CM Service Provider dialog box appears.

Step 6 Click Reset. The following message appears:
WARNING: This operation will reset the TSP and reconnect to the primary Cisco CallManager. 
Any current calls will be dropped. Proceed with the reset?
Step 7 Click Yes to reset.

Step 8 Click OK to close the Cisco Unity-CM Service Provider dialog box.

Step 9 Click Close to close the Phone and Modem Options dialog box.

Step 10 Close Control Panel.

Changing TSP Settings

If you want to change or review the values that you specified when you installed and configured the Cisco Unity-CM TSP, do the following procedure.

Note In versions earlier than 3.1(1), the Cisco Unity-CM TSP was known as the AV-Cisco TSP.

To Change and Test TSP Settings

Step 1 On the Cisco Unity server, log on to Windows as an administrator.

Step 2 Click Start > Settings > Control Panel.

Step 3 Double-click Phone and Modem Options. The Phone and Modem Options dialog box appears.

Step 4 Click the Advanced tab.

Step 5 Click Cisco Unity-CM Service Provider, then click Configure. The Cisco Unity-CM Service Provider dialog box appears.

Step 6 In the Select CallManager list, click the IP address of the Cisco CallManager server that is connected to Cisco Unity, then click Settings.

If the Select CallManager list does not contain the IP address you want, click Add, enter the IP address, and then click OK.

Step 7 In the Cisco Unity-CM Service Provider Settings dialog box, enter values as shown in the following table.

Table 7 Settings for the Cisco Unity-CM Service Provider Settings Dialog Box

Field

Setting

Primary CallManager IP Address

The IP address of the Cisco CallManager server that Cisco Unity will usually receive calls from.

Primary CallManager IP Port

The IP port that Cisco CallManager uses. The default is 2000.

Number of Voice Ports

The number of Cisco CallManager uOne ports that are connected to Cisco Unity.

Device Name Prefix

Enter the following characters without any spaces:

•<the Cisco uOne port name>

•-VI

For example, if the uOne port name is CiscoUM1, the device name prefix is CiscoUM1-VI.

Make sure you enter this prefix exactly as it appears in the Cisco CallManager Administrator. Otherwise, the integration will not work.

MessageWaitingOnDN

The extension that you specified, in the Cisco CallManager Administration, for turning MWIs on. See the "To Specify MWI and Voice Mail Directory Numbers" section.

MessageWaitingOffDN

The extension that you specified, in the Cisco CallManager Administration, for turning MWIs off. See the "To Specify MWI and Voice Mail Directory Numbers" section.

CallManager Failover IP Addresses

The IP addresses of backup Cisco CallManager servers, if any. Backup Cisco CallManager servers must be in the same cluster as the primary Cisco CallManager server.

CallManager Device List

A display-only list of the names of the uOne ports that Cisco Unity looks for on the current Cisco CallManager server. This list is constructed by appending numbers starting with 1 to the setting of device name prefix.

The names in this list must exactly match the names of the uOne ports in the Cisco CallManager Administration. Otherwise, calls will not be correctly transferred to Cisco Unity.

Step 8 Click OK to close the Cisco Unity-CM Service Provider Settings dialog box.

Step 9 In the Cisco Unity-CM Service Provider dialog box, click Test. The settings you specified in Step 7 are checked against the current settings in the Cisco CallManager Administration.

If the test succeeds, a message box displays the message, "The test completed successfully." If the test fails, one of the error messages shown in the following table appears. Troubleshoot the problem as described in the "Comments" column, and repeat this step until the test succeeds. Then continue with Step 10.

Table 8 Error Messages from the Cisco Unity-CM Service Provider Test

Error Message

Comments

Pinging CallManager server (<IP address>) failed. Make sure the IP address is valid, the server is running, and the network connection is working.

No computers on the network have the IP address that you specified in Primary CallManager IP Address. Confirm that this address is valid. If the value is correct, or if the problem persists after you change the value, troubleshoot the problem as you would a network connectivity problem.

The voice device named <device name> does not respond to registration requests. Ensure that the device has been created in the CallManager database and that the device name prefix is correct.

Confirm that the values in CallManager Device List match the names of the voice mail ports that you created in Cisco CallManager Administrator (see the "To Add uOne Ports to Cisco CallManager" section). If not, change the setting in Device Name Prefix or the names of the voice mail ports, as necessary.

Could not connect to the CallManager. Verify that all Cisco services are started on the CallManager server.

The IP address that you specified in Primary CallManager IP Address is a valid address, but Cisco CallManager services are not running on that computer, possibly because Cisco CallManager is not installed on the server with that IP address. Confirm that this address is correct and that the Cisco CallManager services are running.

No wave devices were found on the system. The wave driver is either not installed correctly or the computer needs to be rebooted to update its configuration.

Exit the Cisco Unity software, then restart the server.

Step 10 Click OK to close the Cisco Unity-CM Service Provider dialog box. The following message appears:

This computer needs to be rebooted to update the wave driver.

Step 11 Click OK.

Step 12 Click Close to close the Phone and Modem Options dialog box.

Step 13 Close Control Panel.

Step 14 Exit the Cisco Unity software, then restart the server.

Changing the Number of uOne Ports

To change the number of uOne ports after you have finished installing and setting up Cisco CallManager, do the following procedures.

To Change the Number of uOne Ports in the Cisco CallManager Administration

Step 1 On the Cisco CallManager server, use the Cisco uOne Port Wizard to add or remove uOne ports, as appropriate.

For information on adding uOne ports, see the "To Add uOne Ports to Cisco CallManager" section. For information on removing uOne ports, see the online Help in the Cisco CallManager Administrator.

Step 2 Continue with the next procedure.

To Update the Cisco Unity System Key for Additional uOne Ports

Step 1 If the Cisco Unity system key is not enabled for the additional uOne ports you added, see your sales representative to request an upgrade activation code.

Step 2 Once you have the upgrade activation code, on the Cisco Unity server, click Programs > Cisco Unity > Upgrade License.

Step 3 Follow the on-screen instructions.

If you increase the number of voice messaging ports from 32 or fewer to more than 32, you must also install SQL Server 2000 as described in the Cisco Unity Installation Guide. Otherwise, continue on to the procedure "To Change the Number of uOne Ports Specified for the TSP."

To Change the Number of uOne Ports Specified for the TSP

Step 1 On the Cisco Unity server, click Start > Settings > Control Panel.

Step 2 Double-click Phone and Modem Options. The Phone and Modem Options dialog box appears.

Step 3 Click the Advanced tab.

Step 4 Click Cisco Unity-CM Service Provider, and click Configure. The Cisco Unity-CM Service Provider dialog box appears.

Step 5 Select the IP address of the Cisco CallManager server that you added uOne ports to.

Step 6 Click Settings. The Cisco Unity-CM Service Provider Settings dialog box appears.

Step 7 Change Number of Voice Ports to the number of uOne ports configured in the Cisco CallManager Administration.

Step 8 Click OK to close the Cisco Unity-CM Service Provider Settings dialog box.

Step 9 Click OK to close the Cisco Unity-CM Service Provider dialog box.

Step 10 Click Close to close the Phone and Modem Options dialog box.

Step 11 Click OK to continue.

Step 12 Close Control Panel.

Step 13 Exit the Cisco Unity software, then restart the server.

Removing Dialogic Voice Card Software

If you are converting an integration with a circuit-switched phone system to an integration with Cisco CallManager, see the "Integration Steps When Converting from a Dual Phone System Integration to a Cisco CallManager-Only Integration" section and do the following two procedures.

To Remove Dialogic Voice Card Software

Step 1 Exit the Cisco Unity software, then restart the server.

Step 2 On the Windows Start menu, click Programs > Dialogic Systems Software > Dialogic Configuration Manager - DCM.

Dialogic Configuration Manager may display an error message about not detecting devices. This error is harmless. Click OK.

Step 3 On the Service menu, click Stop Service.

Step 4 Click Close.

Step 5 Close the DCM.

Step 6 On the Windows Start menu, click Settings > Control Panel > Phone and Modem Options.

Step 7 Click the Advanced tab.

Step 8 Click Dialogic Generation 2 Service Provider for NT.

Step 9 Click Remove.

Step 10 Click Yes.

Step 11 Click Close to close the Phone and Modem Options dialog box.

Step 12 In Control Panel, double-click Sounds and Multimedia.

Step 13 In the Sounds and Multimedia Options dialog box, click the Hardware tab.

Step 14 Click Legacy Audio Drivers.

Step 15 Click Properties. The Legacy Audio Drivers Properties dialog box appears.

Step 16 Click Properties.

Step 17 In the Legacy Audio Drivers Properties dialog box, click the Properties tab.

Step 18 Expand Audio Devices.

Step 19 Click Audio for Dialogic WAVE.

Step 20 Click Remove. The Legacy Audio Drivers Properties dialog box closes.

Step 21 Click Yes to confirm.

Step 22 When prompted to restart the server, click Don't Restart Now.

Caution If you restart now, the WAVE driver is not removed.

Step 23 Click OK to close the Legacy Audio Drivers Properties dialog box.

Step 24 Click OK to close the Sounds and Multimedia Properties dialog box.

Step 25 Close Control Panel.

Step 26 On the Windows Start menu, click Programs > Dialogic System Software > Uninstall.

Step 27 Follow the on-screen prompts until a dialog box asks whether you want to delete shared files.

Step 28 Click No to all.

Step 29 Click OK.

Step 30 Click Yes to restart. (The Dialogic-triggered restart may not restart the session; in this case, manually restart the Cisco Unity server.

Step 31 After the system restarts, log on.

Step 32 In the Windows Explorer, browse to the \CommServer directory, and delete the Dialogic directory.

To Remove the Cisco Unity Dependence on the Dialogic Service

Step 1 On the Cisco Unity server, click Start > Run.

Step 2 In the Open field, enter Regedit and press Enter. The Registry Editor appears.

Caution Changing the wrong registry key or entering an incorrect value can cause the server to malfunction. Before you edit the registry, confirm that you know how to restore it if a problem occurs. (Refer to the "Restoring" topics in Registry Editor Help.) Note that a typical backup of the Cisco Unity server does not back up the registry. Also note that for a Cisco Unity failover system, registry changes on one Cisco Unity server must be made manually on the other Cisco Unity server, because registry changes are not replicated. If you have any questions about changing registry key settings, contact Cisco TAC.

Step 3 If you do not have a current backup of the registry, click Registry > Export Registry File, and save the registry settings to a file.

Step 4 Go to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Service\AvCsMgr.

Step 5 In the right pane of the Registry Editor, double-click the DependOnService value.

Step 6 In the Edit Binary Value dialog box, select the string for Dialogic, and delete it.

Step 7 Click OK.

Step 8 Close the Registry Editor.

Step 9 Restart the Cisco Unity server.

Troubleshooting the Cisco CallManager Integration

This section provides information about common integration problems.

The Default Ear Piece and Speaker Volume on Cisco 7960 Phones Is Too Loud

To Change the Volume on Cisco 7960 Phones

Step 1 On the 7960 phone, press the Speaker button.

Step 2 Use the Volume button to change the volume.

Step 3 Press the Settings button.

Step 4 Press the Save soft key.

Cisco Unity Does Not Answer When the Extension for Cisco Unity Is Dialed

If you hear a fast busy or number unobtainable signal when you dial Cisco Unity, do the following procedure.

To Confirm That the Phone System Programming Is Complete

Step 1 Review the phone system programming to confirm that it is complete. Specific actions to take are:

•Confirming that the uOne ports and phones are in the same calling search space. For details, see the "To Add uOne Ports to Cisco CallManager" section.

•Confirming that the uOne ports are correctly set up. For details, see the "To Add uOne Ports to Cisco CallManager" section.

•Testing the TSP. For details, see the "To Test the TSP" section.

Step 2 Exit the Cisco Unity software, then restart the server.

Dual Phone System Integration

Cisco Unity can be integrated with one each of the following phone systems at the same time:

•A traditional, circuit-switched phone system. Any circuit-switched phone system that Cisco Unity integrates with can be used in a dual phone system integration.

•Cisco CallManager.

All extensions for subscribers and call handlers must be unique regardless of which phone system a subscriber (or call handler) uses. To transfer calls from one phone system to the other, Cisco Unity must dial the same access codes that a subscriber dials when calling someone on the other phone system.

Dual Phone System Integration Overview

Before doing the following integration steps, confirm that the Cisco Unity server is ready for the integration by completing the appropriate tasks in the Cisco Unity Installation Guide.

Integration Steps When No Phone Systems Are Installed

Follow these steps to set up the dual phone system integration when no phone systems are installed.

1. Install the circuit-switched phone system.

2. Integrate the circuit-switched phone system and Cisco Unity. See the appropriate Cisco Unity integration guide, located on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/index.htm and on the Cisco Documentation CD-ROM.

3. Install Cisco CallManager.

4. Integrate Cisco CallManager and Cisco Unity. See the "Integration Overview" section.

5. Change the Cisco Unity Administrator settings. See the "Changing Cisco Unity Administrator Settings" section.

Integration Steps When a Circuit-Switched Phone System Is Already Installed

Follow these steps to set up the dual phone system integration when the circuit-switched phone system is already installed and Cisco CallManager is being newly installed.

1. Install Cisco CallManager.

2. Integrate Cisco CallManager and Cisco Unity. See the "Integration Overview" section.

3. Change the Cisco Unity Administrator settings. See the "Changing Cisco Unity Administrator Settings" section.

Integration Steps When Cisco CallManager Is Already Installed

Follow these steps to set up the dual phone system integration when Cisco CallManager is already installed and a circuit-switched phone system is being newly installed.

1. Remove the existing TSP on Cisco Unity. See the "To Remove the Existing TSP" section.

2. Install the circuit-switched phone system.

3. Integrate the circuit-switched phone system and Cisco Unity. See the appropriate Cisco Unity integration guide, located on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/index.htm and on the Cisco Documentation CD-ROM.

4. Reinstall the TSP. See the "To Reinstall the TSP" section.

5. Change the Cisco Unity Administrator settings. See the "Changing Cisco Unity Administrator Settings" section.

Requirements

The dual phone system integration supports configurations of the following components:

•A Cisco Unity system key with the integration type set to "Multiple integrations" and with the appropriate number of voice messaging ports enabled.

•The Cisco Unity server set up and Cisco Unity 3.1(x) installed, as described in the Cisco Unity Installation Guide.

•A circuit-switched phone system installed and integrated with Cisco Unity. For details, see the appropriate Cisco Unity integration guide, located on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/index.htm and on the Cisco Documentation CD-ROM. The circuit-switched phone system (including the voice card software used in the integration) must be installed and integrated with Cisco Unity before Cisco CallManager is integrated.

•Cisco CallManager, version 3.0(1) or later, and the Cisco Unity-CM service provider (TSP) installed and configured. For information about integrating Cisco Unity with Cisco CallManager and the Cisco Unity-CM service provider, see the "Integration Overview" section.

Changing Cisco Unity Administrator Settings

After Cisco Unity is installed and the phone systems have been separately integrated, you need to adjust settings on pages in the Cisco Unity Administrator so that Cisco Unity can work with both phone systems.

Follow these steps to set up the dual phone system integration.

1. Specify settings for the circuit-switched phone system on the System > Switch > Switch page. For details, see the "To Specify Switch Settings for the Circuit-Switched Phone System" section.

Caution Specify settings for the circuit-switched phone system before specifying settings for Cisco CallManager. You must proceed in this order, or the integration may not work.

2. Specify settings for Cisco CallManager on the IP Switch page. For details, see the "To Specify Switch Settings for Cisco CallManager" section.

3. On the Ports page, assign port ranges to the circuit-switched phone system first, then to CallManager, and adjust settings for the ports assigned to each phone system. For details, see the "To Modify Voice Port Settings" section.

4. Select the phone system that subscribers and call handlers use. For details, see the "To Select Which Phone System Subscribers and Call Handlers Use" section.

5. Select the phone system that Cisco Unity uses when dialing out to send message notifications. For details, see the "To Select Which Phone System Cisco Unity Uses for Message Notification" section.

Caution If you need to add or remove voice cards or uninstall the voice card software after the dual phone system integration is set up, you must also reinstall the TSP (Cisco Unity-CM service provider). Do not reinstall the TSP until after you have set up the voice cards or reinstalled the voice card software. For more information, see the "Changing the Number of Installed Ports" section.

To Specify Switch Settings for the Circuit-Switched Phone System

Step 1 Go to System > Switch > Switch. The settings for the circuit-switched phone system selected during the Cisco Unity Setup program appear.

Step 2 In the Access Code field, enter the trunk access code that Cisco Unity must dial to transfer calls to Cisco CallManager from the circuit-switched phone system.

The access code is the same number that subscribers on the circuit-switched phone system dial to reach someone on the Cisco CallManager system.

Step 3 Adjust other settings as appropriate. For more information about the other settings on the Switch page, see the online Help in the Cisco Unity Administrator.

Step 4 Click the Save icon, then click OK in the Warning dialog box.

To Specify Switch Settings for Cisco CallManager

Step 1 Go to System > Switch > IP Switch.

Step 2 In the Set Active Switch Type section, enter values as shown in the following table:

Table 9 Switch Settings

Switch Parameter

Required Setting

Manufacturer

Cisco

Model

CallManager

Switch PBX software version

3.01 or later

Integration

TAPI

Step 3 Click Set As Active, then click OK in the Warning dialog box.

Step 4 In the Access Code field, enter the trunk access code that Cisco Unity must dial to transfer calls to the circuit-switched phone system from Cisco CallManager.

The access code is the same number that subscribers on Cisco CallManager dial to reach someone on the circuit-switched phone system.

Step 5 Click the Save icon, then click OK in the Warning dialog box.

To Modify Voice Port Settings

Step 1 Go to System > Ports.

Step 2 In the Port Assignments section, indicate the range of ports to be assigned to the circuit-switched phone system. The port range for the circuit-switched phone system begins with 1 and extends to no more than the number of ports that are on the installed voice cards. Do not assign more ports to the circuit-switched phone system than the number of ports on the voice cards.

Caution If you assign fewer voice ports to the circuit-switched phone system than are available on the installed voice cards, you must edit the registry for this port range to take effect. Otherwise, all available voice ports on the voice cards are used in the integration regardless of the Port Assignments settings. For information on editing the registry for the port range, see the "Appendix: Assigning Dialogic Ports for a Dual Phone System Integration" section.

Step 3 In the Port Assignments section, indicate the range of ports to be assigned to Cisco CallManager. The port range must begin with the next port after the last port for the circuit-switched phone system. The range for Cisco CallManager must end with the port number of the last port displayed on the Ports page, or the number of licensed voice ports on the system key, whichever is lower. In other words, the number of ports available for Cisco CallManager is the difference between the number of licensed voice ports on the system key and the number of ports assigned to the circuit-switched phone system.

Step 4 Enter an extension for each port.

Step 5 Specify other settings as appropriate. For each phone system, confirm that an appropriate number of ports are used to answer calls and to dial out for message waiting indicators (MWIs), message notifications, and Media Master recordings by phone.

Step 6 Click the Save icon.

Caution The port range for each phone system must be set as specified in Step 2 and Step 3 above. If there is a port range mismatch, Cisco Unity will be unable to answer incoming calls and to dial out.

To Select Which Phone System Subscribers and Call Handlers Use

For existing subscriber templates, subscriber accounts, and call handlers, Cisco Unity uses the circuit-switched phone system as its default. Therefore, during the initial setup of the dual phone integration, you will modify only those pages that will be using Cisco CallManager. Note that changes made to subscriber templates do not affect existing subscriber accounts.

Step 1 In Cisco Unity Administrator, go to the appropriate page:

•Subscribers > Subscriber Template > Profile

•Subscribers > Subscribers > Profile

•Call Management > Call Handlers > Profile

Step 2 In the Switch list, select the appropriate phone system.

Step 3 Adjust other settings as appropriate. For more information, see the online Help in the Cisco Unity Administrator.

Caution If the Switch setting on the Profile page for the subscriber or call handler does not match the phone system actually used by a subscriber or call handler, Cisco Unity will not be able to transfer calls to or from the subscriber or call handler. Additionally, Cisco Unity will be unable to turn the MWIs for the subscriber on or off and will be unable to reach the extension for the subscriber when recording by phone with Media Master.

To Select Which Phone System Cisco Unity Uses for Message Notification

If subscribers use message notification, you can select which phone system Cisco Unity dials out on when notifying subscribers of new messages. Note that changes made to subscriber templates do not affect existing subscribers.

Step 1 In Cisco Unity Administrator, go to the appropriate page:

•Subscribers > Subscriber Template > Message Notification

•Subscribers > Message Notification.

Step 2 For each device, in the Switch list select the phone system that Cisco Unity uses to dial out when notifying subscribers of new messages. Each notification device can be associated with a specific phone system (except for text pagers).

Cisco Unity uses the phone system specified on the subscriber template's Profile page as the default.

Step 3 Adjust other settings as appropriate. For more information, see the online Help in the Cisco Unity Administrator.

Caution The selected phone system must have at least one port set to dial out for message notifications on the System > Ports page. If the selected phone system does not have any ports set for this function, notifications will fail.

Changing the Number of Installed Ports

After the dual phone system integration is set up, if you need to add or remove voice cards or uninstall voice card software, follow these steps:

1. Remove the existing TSP. For details, see the "To Remove the Existing TSP" section.

2. As appropriate, remove or add voice cards, or uninstall and reinstall the voice card software. For information about removing Dialogic voice card software, refer to the appendix about voice cards in the Cisco Unity Installation Guide.

3. Reinstall the TSP after you have set up the voice cards or reinstalled the voice card software. For details, see "To Reinstall the TSP" section.

4. Adjust the port assignments on the System > Ports page. The voice messaging ports must appear in this order in the list of ports: first are all the ports connected to the circuit-switched phone system, second are the ports connected to CallManager.

If you completely remove the circuit-switched phone system, you must adjust the port assignments for Cisco CallManager on the System > Ports page, after the voice cards and voice card software used in the integration with the circuit-switched phone system have been removed.

To Remove the Existing TSP

Step 1 On the Cisco Unity server, log on to Windows as an administrator.

Step 2 Stop Cisco Unity (right-click the Cisco Unity icon in the system tray, then click Stop Unity).

Step 3 On the Windows Start menu, click Settings > Control Panel > Add/Remove Programs.

Step 4 In the list, click Cisco Unity-CM TSP.

Note In versions earlier than 3.1(1), the Cisco Unity-CM TSP was known as the AV-Cisco TSP.

Step 5 Click Remove.

Step 6 Click Yes.

Step 7 Close Control Panel.

To Reinstall the TSP

Step 1 On the Cisco Unity server, log on to Windows as an administrator.

Step 2 On the Windows Start menu, click Settings > Control Panel.

Step 3 Double-click Phone and Modem Options. The Phone and Modem Options dialog box appears.

Step 4 Click the Advanced tab.

Step 5 Click Add. The Add Driver dialog box appears.

Step 6 Click Cisco Unity-CM Service Provider, then click Add. A dialog box appears confirming the installation of the TSP.

Step 7 Click OK to close the dialog box.

Step 8 Click Close to close the Phone and Modem Options dialog box.

Step 9 Close Control Panel.

Step 10 Restart the Cisco Unity server.

Appendix: Remapping Extension Numbers

The Remapping Feature

The extension remapping feature lets you convert the calling numbers and forwarding numbers of calls that Cisco Unity handles to the extensions of your choice. This feature is useful, for example, when the phone system cannot map multiple extension numbers on a subscriber's phone to a single Inbox.

Remapping can change one or both of the following extension numbers in a call:

•Calling number (the number from which a call originates). For example, Cisco Unity changes the calling number of calls that the phone system sends it so that the caller ID appears to be a different extension than the one that actually placed the call.

•Forwarding number (the number that a call is going to). For example, unanswered calls to all line extensions on a single phone can be forwarded to the Inbox of a single subscriber; or unanswered calls to phones not assigned to subscribers can be forwarded to the Inbox of a supervisor.

Setting Up Cisco Unity to Remap Extension Numbers

This section includes a procedure for enabling the remapping feature. There are also examples of extension remapping syntax.

By doing the procedure, you can create multiple files in either or both of two directories:

•In the Calling directory, one or more .exm files remap caller ID numbers.

•In the Forwarding directory, one or more .exm files remap numbers that Cisco Unity provides with calls it forwards.

Creating remapping instructions in an .exm file in a directory remaps only the type of extension number that the directory is named for. For example, if you want to remap only the extensions that Cisco Unity provides with calls it forwards, you must enter the instructions in an .exm file in the Forwarding directory; the Calling directory needs no file in this case.

In each directory, you can have several .exm files with different file names but the same .exm extension to help organize the remapping information (for example, Ports_1-12.exm and Ports_13-24.exm). Cisco Unity reads all files that have the .exm extension in these directories.

To Remap Extension Numbers

Step 1 On the Cisco Unity server, browse to the CommServer\IntLib\ExtensionMapping directory. In this directory is the file Sample.txt and two more directories: Calling and Forwarding.

Step 2 To remap calling numbers, go to the Calling directory.

Step 3 Using a text editor, create (or open) an .exm file in one directory.

For a sample file, see the file Sample.txt in the \CommServer\IntLib\ExtensionMapping directory. To create a section for indicating which voice messaging ports will be monitored for remapping calls, enter [Range] and press Return.

An .exm file can have only one [Range] section.

Step 4 Enter ports= followed by the numbers of the voice messaging ports separated by commas. Ranges are designated by a hyphen (-) without spaces. To monitor all voice messaging ports, enter ports=* on this line. Then press Return.

For example, you might enter:
ports=1,2,5-34,10
Step 5 To create a section for the remapping rules, press Return, enter [Number Mappings], and then press Return.

An .exm file can have only one [Number Mappings] section.

Step 6 Using the wildcards and examples in the following "Syntax and Examples" section, enter one remapping rule on the line. Then press Return. The rule format is:

<original number>, <new number>

The rules cannot include spaces between digits. However, the numbers must be separated by a comma and a single space. Wildcard characters cannot appear at the beginning of a number.

Step 7 For all remaining rules, repeat Step 6.

Step 8 Save and close the .exm file.

Step 9 To remap forwarding numbers, go to the directory \CommServer\IntLib\ExtensionMapping\Forwarding.

Step 10 Do Step 3 through Step 8.

Step 11 For extension remapping to take effect, restart the Cisco Unity software.

Syntax and Examples

Table 10 lists the wildcard characters you can use in the .exm files.

Table 10 Wildcard Characters

Wildcard

Result

*

Matches zero or more digits.

?

Matches exactly one digit. Use ? as a placeholder for a single digit.

Table 11 gives examples for the syntax and results of rules in the .exm files.

Table 11 Syntax Examples

Rule

Original Number

New Number

2189, 1189

3189, 1189

4189, 1189

2189

3189

4189

1189

1189

1189

2???, 1???

2189

2291

1189

1291

3???, 1???

3189

3291

1189

1291

8???, 61???

8000

8765

61000

61765

123*, 44*

12300

12385

4400

4485

Cisco Unity executes rules in the order they appear in the .exm file. For example, the .exm file might contain the following rules:
1234, 1189
3189, 1189
4189, 1189
123?, 8891
The extension 1234 would be remapped to 1189 while extensions 1233 and 1235 would be remapped to 8891, because the rule mapping 1234 appears earlier.

An .exm file might contain the following:
[Range]
ports=1,2,5-34,10
[Number Mappings]
2189, 1189
3189, 1189
4189, 1189
8???, 9???
Appendix: Assigning Dialogic Ports for a Dual Phone System Integration

In a dual phone system integration, Cisco Unity assigns a voice messaging port to the traditional, circuit-switched phone system for every port available on the installed voice cards before assigning voice messaging ports to Cisco CallManager. The result is that Cisco Unity may not have enough voice messaging ports remaining to assign to Cisco CallManager.

The maximum number of voice messaging ports are assigned to the circuit-switched phone system in spite of the settings on the Ports page in the System Administrator.

For example, a dual phone system integration might have the following configuration:

•A circuit-switched phone system has a four-port voice card installed.

•Cisco CallManager has six Voice Mail ports set up.

•The Cisco Unity server has a system key enabled for a total of eight ports.

•The Ports page on System Administrator indicates that Ports 1 and 2 are assigned to the circuit-switched phone system and Ports 3 through 8 are assigned to Cisco CallManager.

Even so, Ports 1 through 4 (the total voice card ports) will be assigned to the circuit-switched phone system, and Ports 5 through 6 will be assigned to Cisco CallManager.

If you want to assign fewer than the total voice card ports to the circuit-switched phone system, you must first set the Port assignments on the Ports page of the System Administrator, then do the following procedure.

To Set the Port Assignments in the Registry

Step 1 On the Cisco Unity server, click Start > Run.

Step 2 In the Open field, enter Regedit and press Enter. The Registry Editor appears.

Caution Changing the wrong registry key or entering an incorrect value can cause the server to malfunction. Before you edit the registry, confirm that you know how to restore it if a problem occurs. (Refer to the "Restoring" topics in Registry Editor Help.) Note that a typical backup of the Cisco Unity server does not back up the registry. If you have any questions about changing registry key settings, contact Cisco TAC.

Step 3 If you do not have a current backup of the registry, click Registry > Export Registry File, and save the registry settings to a file.

Step 4 Go to HKEY_LOCAL_MACHINE\Software\ActiveVoice\MIU\1.0\Initialization\ServiceProvider <x>, where <x> is a number.

You will find several subkeys with this name.

Step 5 Locate the subkey in which the value Service Provider Name is D41MT.TSP.

Step 6 In this subkey, in the Edit menu click New > DWORD Value. A new value appears in the subkey.

Step 7 Enter the name DeviceID Lower Bound and press Enter.

Step 8 Double-click the DeviceID Lower Bound value. The Edit DWORD Value dialog box appears.

Step 9 In the Value Data field, enter 1 and click OK.

Step 10 in the Edit menu click New > DWORD Value. A new value appears in the subkey.

Step 11 Enter the name DeviceID Upper Bound and press Enter.

Step 12 Double-click the DeviceID Upper Bound value. The Edit DWORD Value dialog box appears.

Step 13 In the Value Data field, enter the number of Dialogic ports you want to assign and click OK.

Step 14 Close the Registry Editor.

Step 15 For the settings to take effect, exit and restart the Cisco Unity software.

Appendix: Documentation and Technical Assistance

Conventions

The Cisco CallManager 3.0 Integration Guide for Cisco Unity 3.1 uses the following conventions.

Table 12 Cisco CallManager 3.0 Integration Guide for Cisco Unity 3.1 Conventions

Convention

Description

boldfaced text

Boldfaced text is used for:

•Key and button names. (Example: Click OK.)

•Information that you enter. (Example: Enter Administrator in the User Name box.)

< >

(angle brackets)

Angle brackets are used around parameters for which you supply a value. (Example: In the Command Prompt window, enter ping <IP address>.)

-

(hyphen)

Hyphens separate keys that must be pressed simultaneously. (Example: Press Ctrl-Alt-Delete.)

>

(right angle
bracket)

A right angle bracket is used to separate selections that you make:

•On menus. (Example: On the Windows Start menu, click Settings > Control Panel > Phone and Modem Options.)

•In the navigation bar of the Cisco Unity Administrator. (Example: Go to the System > Configuration > Settings page.)

The Cisco CallManager 3.0 Integration Guide for Cisco Unity 3.1 also uses the following convention:

Note Means reader take note. Notes contain helpful suggestions or references to material not covered in the document.

Caution Means reader be careful. In this situation, you might do something that could result in equipment damage or loss of data.

Cisco Unity Documentation

For descriptions and URLs of Cisco Unity documentation on Cisco.com, refer to About Cisco Unity Documentation. The document is shipped with Cisco Unity and is available on Cisco.com at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_pre_installation_guides_list.html.

Obtaining Documentation

Cisco provides several ways to obtain documentation, technical assistance, and other technical resources. These sections explain how to obtain technical information from Cisco Systems.

Cisco.com

You can access the most current Cisco documentation on the World Wide Web at this URL:

http://www.cisco.com/univercd/home/home.htm

You can access the Cisco website at this URL:

http://www.cisco.com

International Cisco websites can be accessed from this URL:

http://www.cisco.com/public/countries_languages.shtml

Documentation CD-ROM

Cisco documentation and additional literature are available in a Cisco Documentation CD-ROM package, which may have shipped with your product. The Documentation CD-ROM is updated regularly and may be more current than printed documentation. The CD-ROM package is available as a single unit or through an annual or quarterly subscription.

Registered Cisco.com users can order a single Documentation CD-ROM (product number DOC-CONDOCCD=) through the Cisco Ordering tool:

http://www.cisco.com/en/US/partner/ordering/ordering_place_order_ordering_tool_launch.html

All users can order monthly or quarterly subscriptions through the online Subscription Store:

http://www.cisco.com/go/subscription

Ordering Documentation

You can find instructions for ordering documentation at this URL:

http://www.cisco.com/univercd/cc/td/doc/es_inpck/pdi.htm

You can order Cisco documentation in these ways:

•Registered Cisco.com users (Cisco direct customers) can order Cisco product documentation from the Networking Products MarketPlace:

http://www.cisco.com/en/US/partner/ordering/index.shtml

•Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco Systems Corporate Headquarters (California, U.S.A.) at 408 526-7208 or, elsewhere in North America, by calling 800 553-NETS (6387).

Documentation Feedback

You can submit comments electronically on Cisco.com. On the Cisco Documentation home page, click Feedback at the top of the page.

You can e-mail your comments to bug-doc@cisco.com.

You can submit comments by using the response card (if present) behind the front cover of your document or by writing to the following address:

Cisco Systems
Attn: Customer Document Ordering
170 West Tasman Drive
San Jose, CA 95134-9883

We appreciate your comments.

Obtaining Technical Assistance

Cisco provides Cisco.com, which includes the Cisco Technical Assistance Center (TAC) website, as a starting point for all technical assistance. Customers and partners can obtain online documentation, troubleshooting tips, and sample configurations from the Cisco TAC website. Cisco.com registered users have complete access to the technical support resources on the Cisco TAC website, including TAC tools and utilities.

Cisco.com

Cisco.com offers a suite of interactive, networked services that let you access Cisco information, networking solutions, services, programs, and resources at any time, from anywhere in the world.

Cisco.com provides a broad range of features and services to help you with these tasks:

•Streamline business processes and improve productivity

•Resolve technical issues with online support

•Download and test software packages

•Order Cisco learning materials and merchandise

•Register for online skill assessment, training, and certification programs

To obtain customized information and service, you can self-register on Cisco.com at this URL:

http://tools.cisco.com/RPF/register/register.do

Technical Assistance Center

The Cisco TAC is available to all customers who need technical assistance with a Cisco product, technology, or solution. Two types of support are available: the Cisco TAC website and the Cisco TAC Escalation Center. The type of support that you choose depends on the priority of the problem and the conditions stated in service contracts, when applicable.

We categorize Cisco TAC inquiries according to urgency:

•Priority level 4 (P4)—You need information or assistance concerning Cisco product capabilities, product installation, or basic product configuration. There is little or no impact to your business operations.

•Priority level 3 (P3)—Operational performance of the network is impaired, but most business operations remain functional. You and Cisco are willing to commit resources during normal business hours to restore service to satisfactory levels.

•Priority level 2 (P2)—Operation of an existing network is severely degraded, or significant aspects of your business operations are negatively impacted by inadequate performance of Cisco products. You and Cisco will commit full-time resources during normal business hours to resolve the situation.

•Priority level 1 (P1)—An existing network is "down," or there is a critical impact to your business operations. You and Cisco will commit all necessary resources around the clock to resolve the situation.

Cisco TAC Website

The Cisco TAC website provides online documents and tools to help troubleshoot and resolve technical issues with Cisco products and technologies. To access the Cisco TAC website, go to this URL:

http://www.cisco.com/tac

All customers, partners, and resellers who have a valid Cisco service contract have complete access to the technical support resources on the Cisco TAC website. Some services on the Cisco TAC website require a Cisco.com login ID and password. If you have a valid service contract but do not have a login ID or password, go to this URL to register:

http://tools.cisco.com/RPF/register/register.do

If you are a Cisco.com registered user, and you cannot resolve your technical issues by using the Cisco TAC website, you can open a case online at this URL:

http://www.cisco.com/tac/caseopen

If you have Internet access, we recommend that you open P3 and P4 cases online so that you can fully describe the situation and attach any necessary files.

Cisco TAC Escalation Center

The Cisco TAC Escalation Center addresses priority level 1 or priority level 2 issues. These classifications are assigned when severe network degradation significantly impacts business operations. When you contact the TAC Escalation Center with a P1 or P2 problem, a Cisco TAC engineer automatically opens a case.

To obtain a directory of toll-free Cisco TAC telephone numbers for your country, go to this URL:

http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml

Before calling, please check with your network operations center to determine the Cisco support services to which your company is entitled: for example, SMARTnet, SMARTnet Onsite, or Network Supported Accounts (NSA). When you call the center, please have available your service agreement number and your product serial number.

Obtaining Additional Publications and Information

Information about Cisco products, technologies, and network solutions is available from various online and printed sources.

•The Cisco Product Catalog describes the networking products offered by Cisco Systems, as well as ordering and customer support services. Access the Cisco Product Catalog at this URL:

http://www.cisco.com/en/US/products/products_catalog_links_launch.html

•Cisco Press publishes a wide range of networking publications. Cisco suggests these titles for new and experienced users: Internetworking Terms and Acronyms Dictionary, Internetworking Technology Handbook, Internetworking Troubleshooting Guide, and the Internetworking Design Guide. For current Cisco Press titles and other information, go to Cisco Press online at this URL:

http://www.ciscopress.com

•Packet magazine is the Cisco quarterly publication that provides the latest networking trends, technology breakthroughs, and Cisco products and solutions to help industry professionals get the most from their networking investment. Included are networking deployment and troubleshooting tips, configuration examples, customer case studies, tutorials and training, certification information, and links to numerous in-depth online resources. You can access Packet magazine at this URL:

http://www.cisco.com/go/packet

•iQ Magazine is the Cisco bimonthly publication that delivers the latest information about Internet business strategies for executives. You can access iQ Magazine at this URL:

http://www.cisco.com/go/iqmagazine

•Internet Protocol Journal is a quarterly journal published by Cisco Systems for engineering professionals involved in designing, developing, and operating public and private internets and intranets. You can access the Internet Protocol Journal at this URL:

http://www.cisco.com/en/US/about/ac123/ac147/about_cisco_the_internet_protocol_journal.html

•Training—Cisco offers world-class networking training. Current offerings in network training are listed at this URL:

http://www.cisco.com/en/US/learning/le31/learning_recommended_training_list.html

Copyright © 2003 Cisco Systems, Inc. All rights reserved.

Cisco Unity

Cisco CallManager 3.0 Integration Guide for Cisco Unity 3.1

Hierarchical Navigation

Downloads

Table Of Contents

Cisco CallManager 3.0 Integration Guide for Cisco Unity 3.1

Integration Overview

Integration Steps When Integrating with Cisco CallManager for the First Time

Integration Steps When Updating to a More Recent Version of Cisco CallManager

Integration Steps When Converting from a Dual Phone System Integration to a Cisco CallManager-Only Integration

Integration Steps When Converting from an Integration with a Traditional, Circuit-Switched Phone System to an Integration with Cisco CallManager

Requirements

Integration Description

Integration Features

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

Programming the Cisco CallManager Phone System

Setting Up the Gateways Servicing Cisco Unity

Installing, Configuring, and Testing the TSP

Configuring Cisco Unity for the Integration

Testing the Integration

Integrating a Secondary Server for Cisco Unity Failover

Requirements

Integration Description

Setting Up the Secondary Server for Failover

Switching Call Processing from a Cisco CallManager Failover Server to the Primary Server

Changing TSP Settings

Changing the Number of uOne Ports

Removing Dialogic Voice Card Software

Troubleshooting the Cisco CallManager Integration

The Default Ear Piece and Speaker Volume on Cisco 7960 Phones Is Too Loud

Cisco Unity Does Not Answer When the Extension for Cisco Unity Is Dialed

Dual Phone System Integration

Dual Phone System Integration Overview

Integration Steps When No Phone Systems Are Installed

Integration Steps When a Circuit-Switched Phone System Is Already Installed

Integration Steps When Cisco CallManager Is Already Installed

Requirements

Changing Cisco Unity Administrator Settings

Changing the Number of Installed Ports

Appendix: Remapping Extension Numbers

The Remapping Feature

Setting Up Cisco Unity to Remap Extension Numbers

Syntax and Examples

Appendix: Assigning Dialogic Ports for a Dual Phone System Integration

Appendix: Documentation and Technical Assistance

Conventions

Cisco Unity Documentation

Obtaining Documentation

Cisco.com

Documentation CD-ROM

Ordering Documentation

Documentation Feedback

Obtaining Technical Assistance

Cisco.com

Technical Assistance Center

Cisco TAC Website

Cisco TAC Escalation Center

Obtaining Additional Publications and Information

Copyright © 2003 Cisco Systems, Inc. All rights reserved.