Guest

Cisco Unified Communications Manager (CallManager)

Release Notes for Cisco CallManager Release 4.0(1)

 Feedback

Table Of Contents

Release Notes for Cisco CallManager Release 4.0(1)

Contents

Introduction

System Requirements

Determining the Software Version

Compatibility Matrix and Supported Upgrades

Related Documentation

New and Changed Information

Installation and Backup Enhancements

Disabling RIS Data Collector Prior to Upgrading to Cisco CallManager Release 4.0 and Above

Support for New Cisco IP Phones

Menu Changes

Multiple Calls on Directory Numbers (lines)

Shared-Line Enhancements

Unassigned Directory Numbers

Phone Button Template Consolidation for Cisco IP Phone Model 7960 and Cisco Expansion Module Model 7914

Conference and Transfer Enhancements

Configurable Call Forward Information Displayed

Abbreviated Dialing

Configuring Service URL on Phone Buttons

Immediate Divert

Barge and Privacy Enhancements

Barge and cBarge

Privacy

Malicious Call Identification

Annunciator

Multilevel Precedence and Preemption

Attendant Console Enhancements

Cisco CallManager Extension Mobility Enhancements

Cisco IP Manager Assistant (IPMA) Enhancement

Static Digit Analysis

Directory Enhancements

Routing Enhancements

Cisco Unity Voice-Mail Port Adjustments

Additional Media Resources Support

Multilevel Administration Access Enhancements

QSIG Protocol

Session Initiation Protocol (SIP) Trunk

Support for Video Calls

H.323 Enhancements

Removing a Deleted Subscriber

Security

Bulk Administration Tool Enhancements

Tool for Auto-Registered Phone Support Enhancements

CDR Analysis and Reporting (CAR) Enhancements

Tomcat Web Server

New and Changed Information for Cisco CallManager Serviceability

TroubleShooting Trace Setting

Cisco CallManager Trace Collection Tool

Real-Time Monitoring Tool (RTMT) as Standalone Plugin

Serviceability Reports Archive

SNMP and Performance Counter Enhancements

New and Changed Information for Third-Party and SDK Applications

Cisco CallManager Call Detail Record Definition

Cisco CallManager Extension Mobility API Developer Guide Release 4.0(1)

Cisco IP Phone Services Application Development Notes

Cisco JTAPI Developer Guide for Cisco CallManager 4.0(1)

Cisco JTAPI Installation Guide for Cisco CallManager 4.0(1)

Cisco TAPI Developer and Installation Guides for Cisco CallManager 4.0(1)

Changes From CiscoTSP 3.3 to CiscoTSP 4.0

Important Notes

CSCso79248 Do Not Run installxml.vbs in Unified CM Release 3.3 and Later

Uninstall CDR Analysis and Reporting Plugin Before Upgrading to Cisco CallManager 4.0(1)

Locale Installer for Cisco CallManager

Using TAPS to Configure Shared-line Phones

Survivable Remote Site Telephony (SRST) Support

Uninstalling Backup and Restore (BARS) Version 4.0(1)

Adding Cisco CallManager Servers

Softkey Support for Cisco IP Phone Models 7905 and 7912

Resolved Caveats for Cisco CallManager - Release 4.0(1)

Open Caveats for Cisco CallManager - Release 4.0(1)

Documentation Updates

Errors

Installation and Upgrade Document References Incorrect Version of Backup and Restore (BARS)

Cisco Video Link Codec

Cisco IP Communicator

Malicious Call Identification

Changes

Route Pattern/Hunt Pilot Configuration

Troubleshooting Security

Omissions

Fax and Modem Connectivity with Cisco CallManager

Cisco Unity Voice-Mail Port Changes

Static Digit Analysis

Obtaining Documentation

Cisco.com

Ordering Documentation

Documentation Feedback

Obtaining Technical Assistance

Cisco TAC Website

Opening a TAC Case

TAC Case Priority Definitions

Obtaining Additional Publications and Information


Release Notes for Cisco CallManager Release 4.0(1)


Updated June 23, 2008

These release notes describe the new features and caveats for Cisco CallManager Release 4.0(1).

Before you install Cisco CallManager, we recommend that you review the "Important Notes" section for information on issues that may affect your system.

For a list of the open and resolved caveats for Cisco CallManager Release 4.0(1), see "Resolved Caveats for Cisco CallManager - Release 4.0(1)" section and "Open Caveats for Cisco CallManager - Release 4.0(1)" section. Updates for these release notes occur with every maintenance and major release.

To access the documentation suite for voice products, refer to

http://www.cisco.com/univercd/cc/td/doc/product/voice/

Access the latest software upgrades and release notes for Cisco CallManager 4.0 on Cisco Connection Online (CCO) at

http://www.cisco.com/public/sw-center/sw-voice.shtml

Contents

These release notes discuss the following topics:

Introduction

System Requirements

Compatibility Matrix and Supported Upgrades

Related Documentation

New and Changed Information

New and Changed Information for Cisco CallManager Serviceability

New and Changed Information for Third-Party and SDK Applications

Important Notes

Resolved Caveats for Cisco CallManager - Release 4.0(1)

Open Caveats for Cisco CallManager - Release 4.0(1)

Documentation Updates

Obtaining Documentation

Obtaining Technical Assistance

Introduction

Cisco CallManager, a network business communication system, provides high-quality telephony over IP networks. Cisco CallManager enables the conversion of conventional, proprietary, circuit-switched PBXs to multiservice, open LAN systems.

System Requirements

Make sure that you install and configure Cisco CallManager Release 4.0 on a Cisco Media Convergence Server (MCS). For information about installing Cisco CallManager Release 4.0 on a Cisco Integrated Communications System (ICS) 7750, go to http://www.cisco.com/public/sw-center/telephony/ics-7750/ics-compatibility.shtml

You may also install Cisco CallManager on a Cisco-approved HP server configuration or a Cisco-approved IBM server configuration.


Caution The installation does not complete if you do not have the exact configuration.

Access the correct Cisco-approved server configuration for IBM server or HP server at

http://www.cisco.com/en/US/products/hw/voiceapp/ps378/prod_brochure_list.html

For system hardware component information and system requirements, refer to Installing Cisco CallManager Release 4.0.

Determining the Software Version

To determine the software version of Cisco CallManager, open Cisco CallManager Administration; then, click Details on the main Cisco CallManager Administration window. The following information displays:

Cisco CallManager System version

Cisco CallManager Administration version

Database information and database DLL versions

Compatibility Matrix and Supported Upgrades

You can find which application versions are compatible with Cisco CallManager Release 4.0(1) and which previous release of Cisco CallManager has upgrade support at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/ccmcomp.htm


Note Be aware that the release of Cisco IP telephony products does not always coincide with Cisco CallManager releases. If a product proves to be incompatible with Cisco CallManager, you need to wait until a compatible version of the product becomes available before you upgrade to Cisco CallManager Release 4.0(1). For the most current compatibility combinations and defects, refer to the documentation that is distributed with the Cisco IP telephony products.


Related Documentation

Refer to the Cisco CallManager Document Guide for a list of documents that are related to Cisco CallManager Release 4.0 at

http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/4_0/doc_gd

Along with the documents listed in the Cisco CallManager Document Guide, the following list gives other related documents for Cisco CallManager Release 4.0.

Skinny Client Control Protocol Messaging Guide

Cisco CallManager Call Detail Record Definition

Cisco IP Phone Services Application Development Notes

Cisco JTAPI Installation Guide for Cisco CallManager 4.0(1)

Cisco JTAPI Developer's Guide for Cisco CallManager 4.0(1)

Cisco TAPI Installation Guide for Cisco CallManager 4.0(1

Cisco TAPI Developer's Guide for Cisco CallManager 4.0(1)

Cisco CallManager Extension Mobility API Developer's Guide Release 4.0(1)

System Error Message

Cisco CallManager 4.0(1) AXL Programming Guide

Cisco CallManager 4.0(1) AXL Serviceability Programming Interface Guide

Cisco CallManager Dialed Number Analyzer Guide

Cisco WebDialer API Reference

New and Changed Information

This following sections describe new features and changes that are pertinent to this release of Cisco CallManager. The sections include configuration tips for the administrator, information about users, and where to find more information.

Installation and Backup Enhancements

Disabling RIS Data Collector Prior to Upgrading to Cisco CallManager Release 4.0 and Above

Support for New Cisco IP Phones

Menu Changes

Multiple Calls on Directory Numbers (lines)

Shared-Line Enhancements

Unassigned Directory Numbers

Phone Button Template Consolidation for Cisco IP Phone Model 7960 and Cisco Expansion Module Model 7914

Conference and Transfer Enhancements

Configurable Call Forward Information Displayed

Abbreviated Dialing

Configuring Service URL on Phone Buttons

Immediate Divert

Barge and Privacy Enhancements

Malicious Call Identification

Annunciator

Multilevel Precedence and Preemption

Attendant Console Enhancements

Cisco CallManager Extension Mobility Enhancements

Cisco IP Manager Assistant (IPMA) Enhancement

Static Digit Analysis

Directory Enhancements

Routing Enhancements

Cisco Unity Voice-Mail Port Adjustments

Additional Media Resources Support

Multilevel Administration Access Enhancements

QSIG Protocol

Session Initiation Protocol (SIP) Trunk

Support for Video Calls

H.323 Enhancements

Removing a Deleted Subscriber

Security

Bulk Administration Tool Enhancements

Tool for Auto-Registered Phone Support Enhancements

CDR Analysis and Reporting (CAR) Enhancements

Tomcat Web Server

New and Changed Information for Cisco CallManager Serviceability

New and Changed Information for Third-Party and SDK Applications

Installation and Backup Enhancements

Cisco implemented the following changes for Cisco CallManager 4.0(1) release.

Backup Changes

Cisco provides two backup utilities:

Cisco IP Telephony Backup Utility

Cisco IP Telephony Backup Restore System (BARS)

You use the Cisco IP Telephony Backup utility version 3.5.53 (or later) for servers that are running Cisco CallManager 3.2(x). You use BARS 4.0(2) or later for servers that are running Cisco CallManager 3.3(x) or later.

Both backup utilities support CER 1.2(1) or later and all CRA/CRS and Cisco CAR releases that are compatible with Cisco CallManager.

Changes That Apply to Cisco CallManager 4.0(1) Installations and Upgrades

The following changes apply to all Cisco CallManager 4.0(1) installations and upgrades:

Cisco CallManager 4.0(1) requires Cisco-provided operating system version 2000.2.5 (or later) and the service release 2000-2-5sr2 (or later.)

Cisco CallManager 4.0(1) uses two installation disks:

Cisco CallManager 4.0(1) Installation, Upgrade, and Recovery Disk 1

Cisco CallManager 4.0(1) Installation, Upgrade, and Recovery Disk 2

You are prompted to insert the appropriate disk during the installation process.

The Cisco CallManager installation contains additional and more meaningful error messages.

New Installation Changes

The following changes apply to all Cisco CallManager 4.0(1) installations:

The installation program requires that you have 2.0 gigabytes of available disk space on your server.

SQL 2000 SP3a installs automatically during the Cisco CallManager installation.

To back up your system, install and configure the Cisco IP Telephony Backup and Restore System (BARS), version 4.0(2) or later. For more information, refer to the Cisco IP Telephony Backup and Restore System (BARS) Administration Guide, Version 4.0(2) (or later). To obtain the most recent version of this document, go to http://www.cisco.com/univercd/cc/td/doc/product/voice/backup/index.htm.

Important Notes Regarding Upgrades from Cisco CallManager 3.2(x)

The following important notes apply to upgrades from Cisco CallManager 3.2(x) to Cisco CallManager 4.0(1):

The upgrade program requires that you have 3.0 gigabytes of available disk space on your server.

You must use Cisco IP Telephony Backup utility version 3.5.53 (or later) to back up your system before you upgrade.

Cisco CallManager 4.0(1) requires Cisco-provided operating system version 2000.2.5 (or later) and the service release 2000-2-5sr2 (or later.) You must install OS version 2000.2.4 (or later) by using the Same Server Recovery method, upgrade to OS version 2000.2.5 (or later), and then upgrade to the latest service release.

Important Notes Regarding Upgrades from Cisco CallManager 3.3(x)

The following important notes apply to upgrades from Cisco CallManager 3.2(x) to Cisco CallManager 4.0(1):

The upgrade program requires that you have 3.0 gigabytes of available disk space on your server

Cisco CallManager 4.0(1) requires Cisco-provided operating system version 2000.2.5 (or later) and the service release 2000-2-5sr2 (or later.) You can upgrade the operating system from version 2000.2.3 (or later.)

You must install Microsoft SQL Server 2000 Service Pack 3a (or later) before you upgrade to Cisco CallManager 4.0(1).

To back up your system, install and configure the Cisco IP Telephony Backup and Restore System (BARS), version 4.0(2) or later. For more information, refer to the Cisco IP Telephony Backup and Restore System (BARS) Administration Guide, Version 4.0(2) (or later). To obtain the most recent version of this document, go to http://www.cisco.com/univercd/cc/td/doc/product/voice/backup/index.htm.

Upgrade Tips

Clicking the Cancel button during the Cisco CallManager installation/upgrade process causes Cisco CallManager to become nonfunctional. If you click Cancel during the installation process, you must restart the installation from the beginning before you can use Cisco CallManager.

You can increase the system performance on servers with four drives by configuring a drive to collect trace files. The Cisco CallManager documentation instructs you to configure the F: drive to collect trace files; however, you need to configure the drive that is labeled Trace. To determine which drive is labeled Trace, log in to the system by using the local Administrator account and double-click My Computer on the system Desktop. Note the drive letter of the drive that is labeled Trace. Use this drive letter when configuring a drive to collect trace files.

Disabling RIS Data Collector Prior to Upgrading to Cisco CallManager Release 4.0 and Above

Before upgrading to Cisco CallManager Release 4.0 and above, Cisco recommends that the administrator disables the RIS Data Collector to minimize system problems and prevent false alerts. The following procedure describes how to disable the RIS Data Collector.

Procedure


Step 1 From Cisco CallManager Administration, choose Service > Service Parameters.

The Service Parameters Configuration window displays.

Step 2 From the Server pull-down menu, choose any server.

Step 3 From the Service pull-down menu, choose RIS Data Collector.

Step 4 In the Data Collection Enabled field, choose False.

Step 5 Click Update.

You can now perform the upgrade to Cisco CallManager 4.0 and above.


Note After you complete the Cisco CallManager upgrade, be sure to reset the parameter to "True" in the Data Collection Enabled field from the Service Parameters Configuration window to enable RIS data collection.


Related Documentation

Cisco CallManager Serviceability System Guide

Cisco CallManager Serviceability Administration Guide

Support for New Cisco IP Phones

Cisco CallManager Release 4.0(1) includes support for Cisco Wireless IP Phone model 7920, the Cisco IP Conference Station 7936, and the Cisco IP Phone model 7970.

Where to Find More Information

Cisco Wireless IP Phone 7920 Administration Guide

Cisco IP Conference Station 7936 Administration Guide

Cisco IP Phone 7970 Administration Guide for Cisco CallManager

Menu Changes

In Cisco CallManager Release 4.0(1), the Automated Alternate Routing (AAR) Group menu option moves from the System menu to the Route Plan menu.

Where to Find More Information

"Automated Alternate Routing Group Configuration," Cisco CallManager Administration Guide

Multiple Calls on Directory Numbers (lines)

In previous releases of Cisco CallManager, a maximum of 2 calls could exist on a single line (one active and one on hold). In Cisco CallManager release 4.0, multiple calls can exist on the same line. (Depending on the phone model, some phones can display up to 200 calls on a single line. The user scrolls to view each call.) This capability eliminates the need to create multiple instances of the same directory number in different partitions to allow users to share a line and still be able to receive and place multiple calls out of the same line. To easily manage more than one call on the line and to view calling name and number of the calls on the line, a new user-interaction model exists on the phone display.

You can configure up to 200 calls for a line on a device in a cluster, with the limiting factor being the device. As you configure the number of calls for one line, the calls that are available for another line decrease. Cisco IP Phones that support the multicall display (such as a Cisco IP Phone 7960) support up to 200 calls per DN and 2 calls per DN for non-multicall display devices (such as Cisco IP Phone 7905).

Phones that are capable of supporting multiple calls display information for all concurrent calls. For each call, the phone displays a unique call identifier, the selected call status, call information, and the call state.


Note Only the Cisco IP Phone models 7940 and 7960 support multiple calls on directory numbers in release 4.0(1).


Configuration Tips

Using Directory Number Configuration, administrators configure the following multiple call/call waiting line parameters on each phone that is capable of supporting multiple calls:

No Answer Ring Duration—Used in conjunction with Call Forward No Answer Destination, this field sets the timer for how long the phone will ring before it gets forwarded. Leave this setting blank to use the value that is set in the Cisco CallManager service parameter, Forward No Answer Timer.

Maximum Number of Calls—You can configure up to 200 calls for a line on a device, with the limiting factor being the total number of calls that are configured on the device. As you configure the number of calls for one line, the calls that are available for another line decrease.

Call Forward No Answer—This field forwards calls when the phone is not answered after the configured no answer ring duration.

Busy Trigger—This setting, which works in conjunction with Maximum Number of Calls and Call Forward Busy, determines the maximum number of calls that can be presented at the line.

Example

Max number of calls = 50

Busy trigger = 40

If no calls are present on the line, this line can receive a maximum of 40 calls. If this line originated 40 calls, the line can originate 10 more calls but cannot receive any additional calls. The following formula decides the number of calls that this line can receive: Busy Trigger minus the number of calls that are currently present on this line. So, with 40 calls present on this line, new incoming call 41 gets rejected with a busy cause (and will get forwarded if Call Forward Busy is set). If this line is shared, all the lines must be busy before the incoming calls get rejected. The call initiates alerts on all lines with that DN until the configured No Answer Ring Duration timer value is exceeded. Once the timer value is exceeded, the call diverts to the configured Call Forward No Answer target. To disable call waiting, set the busy trigger to 1. If this line is shared and you want to disable call waiting, set the busy trigger to 1 on all shared DNs.

Configuration Comparisons

Table 1 illustrates the multicall display line configuration differences between Cisco CallManager release 4.0 and release 3.3.

Table 1 Line Configuration Differences for Multicall Display Phones

Feature
Release 3.3
Release 4.0

Maximum number of calls for each line

2

Up to 200, default specifies 4.

Call waiting

If call forward busy trigger is set to 1, Call Waiting is disabled. If call forward busy trigger is set to 2, Call Waiting is enabled

Set the Busy Trigger to be less than or equal to the Maximum Number of Calls per DN. Default specifies 2.


Table 2 illustrates the single line display configuration differences between Cisco CallManager release 4.0 and release 3.3.

Table 2 Line Configuration Differences for Single-Line Display Phones

Feature
Release 3.3
Release 4.0

Maximum number of calls for each line

2

Default specifies 2.

Call waiting

If call forward busy trigger is set to 1, Call Waiting is disabled. If call forward busy trigger is set to 2, Call Waiting is enabled.

If call forward busy trigger is set to 1, Call Waiting is disabled. If call forward busy trigger is set to 2, Call Waiting is enabled.


How this Feature Affects the User

In previous releases, the user could have only two calls on the same line. Improved display text provides information for managing multiple calls on the same line. The display shows whether a call is holding, alerting or connected. The user can select a call to connect with by navigating between calls in the list.

Where to Find More Information

"Cisco IP Phone Configuration," Cisco CallManager Administration Guide

"Cisco IP Phones," Cisco CallManager System Guide

Shared-Line Enhancements

Cisco CallManager supports the following enhancements to shared lines:

Administrators can now configure devices that are sharing a line to support multiple calls. This allows users on shared-line phones to make or receive a call while the remote phone is in use.

Call information (such as calling party or called party) displays on all devices that are sharing a line. If the Privacy feature is turned on by one of the devices, other devices that are sharing the line will not see outbound calls made from the device that turned privacy on. All devices will still see inbound calls to the shared line.

Devices with shared-line appearance support the Call Forward Busy Trigger and the Maximum Number of Calls settings. You can configure Call Forward Busy Trigger per line appearance, but the configuration cannot exceed the maximum number call setting for that directory number.

Cisco IPMA with shared-line support allows managers and assistants to share lines (refer to the Cisco CallManager Features and Services Guide).

Configuration Tip

Cisco IP Phones without pixel-based displays (such as the Cisco IP Phone model 7910) cannot manage more than two calls (one inbound, one outbound) per line.

How this Feature Affects the User

Users that have shared lines can manage multiple calls for the same line appearance. For example, when one user answers a call for the shared line appearance, another user can answer the next incoming for that line appearance. New call display information helps users manage calls on shared lines.

Where to Find More Information

"Cisco IP Phone Configuration," Cisco CallManager Administration Guide

"Cisco IP Phones," Cisco CallManager System Guide

Unassigned Directory Numbers

Directory numbers get associated with devices such as phones, route points, CTI ports, and H.323 clients. Administrators manage directory numbers from the Directory Number Configuration and Route Plan Report windows in Cisco CallManager Administration.

When you remove a directory number from a phone, the number still exists within Cisco CallManager. To see a list of directory numbers that are not associated with phones, use the Route Plan Report menu option.

Unassigned DNs allow customers to continue forwarding to voice messaging or another destination for DNs that are no longer assigned to devices. This can happen when employees are reassigned or terminated.

Previous to release 4.0, the system automatically deleted directory numbers when a device was deleted. Because line group support is a feature of release 4.0, you must now keep unassigned DNs.

Configuration Tips

To permanently remove a directory number, you must perform a two-step procedure:

1. Use the Directory Number Configuration window to add, update, and remove directory numbers from a device, route point, or port.

2. Use the Route Plan Report window to delete or update unassigned directory numbers from Cisco CallManager database.

Where to Find More Information

"Cisco IP Phone Configuration," Cisco CallManager Administration Guide

"Route Plan Report," Cisco CallManager Administration Guide

"Line Group Configuration," Cisco CallManager Administration Guide

Phone Button Template Consolidation for Cisco IP Phone Model 7960 and Cisco Expansion Module Model 7914

The standard phone button template for the Cisco IP Phone Model 7960, which supports the Cisco IP Phone Model 7914 Expansion Module, includes buttons for both devices (up to 34 buttons). The template uses buttons 1 and 2 for lines and assigns buttons 3 through 34 as speed dials or lines or for the features privacy and service URL.

If you are upgrading from an earlier release of Cisco CallManager and you have separate templates for the Cisco IP Phone Expansion Module model 7914 and Cisco IP Phone model 7960, Cisco CallManager automatically creates a consolidated phone button template.

The following reasons explain why the Cisco IP Phone model 7960 and Cisco Expansion Module model 7914 phone button templates were updated in release 4.0:

Make all phone button templates for a model dependent on the maximum number of buttons that are possible for base plus expansion modules.

Remove the phone button template for the expansion module

Limit the appearance of features across the base and expansion modules

Configuration Tips

To create a consolidated phone button template for new users, use the following procedure:

From the Phone Button Template Configuration window, choose a standard 7960 phone button template.

Copy the 7960 phone button template, rename it; for example, 7960 with expansion buttons, and click Update. The new phone button template displays with all 34 buttons available for configuring features such as speed dial, service URL, and Privacy.

Make the applicable feature configurations and click Update.

Find the phone button template that is available for all Cisco IP Phone models 7960 in the Phone Configuration window, phone button template field.

After an upgrade to Cisco CallManager release 4.0(1), verify the following phone configuration:

The field, Phone Button Template, should contain the information, ConsolidatedPhoneTemplate_x, where x is a number that Cisco CallManager assigns.

The field, Module 1 (and Module 2, if applicable), should contain the information, 7914 14-Button Expansion Module.

How This Feature Affects the User

Users will now see up to 99 speed dials on the User Options page. To view the speed dials, the user chooses the Add/Update Your Speed Dials link.

Where to Find More Information

"Cisco IP Phone Configuration," Cisco CallManager Administration Guide

"Phone Button Template Configuration," Cisco CallManager Administration Guide

"Cisco IP Phones," Cisco CallManager System Guide

Customizing Your Cisco IP Phone on the Web

Cisco IP Phone Guide

Conference and Transfer Enhancements

Cisco CallManager release 4.0 supports several conference and transfer enhancements. The system tears down ad hoc conferences when only two conference participants remain in the conference. This release supports Call Join (join multiple parties on a line into an ad hoc conference) and Direct Transfer (directly transfer two parties on a line to each other without joining the user invoking the Direct Transfer). Participants in an ad hoc conference can list the participants of the conference call, and the originator can selectively drop any participant.

Cisco CallManager supports the following conference call enhancements:

Join—Using the Join softkey, a user can join up to 15 established calls (for a total of 16) to create an ad hoc conference call.

Direct Transfer—This enhancement allows a user to transfer two callers on the same line to each other.

Ad hoc conference—Ad hoc conferences now support multiple concurrent conferences on the same device. When only two participants remain in a conference, Cisco CallManager frees up conference resources and reconnects the two participants in a point-point call.


Note This release does not support Conference bridge chaining for ad hoc conference and barged calls that are created within the cluster.


Conference List—The conference list feature provides a list of participant directory numbers that are in an ad hoc conference. The name of the participant displays if it is configured in Cisco CallManager Administration. Any participant can invoke the conference list feature on the phone by pressing the ConfList softkey and can view the participants. The conference controller can invoke the conference list feature and can view and remove any participant in the conference by using the Remove softkey.


Note Only the conference initiator can drop any conference party. Any participant in the ad hoc conference can display the list of conference participants if their IP phone has display capabilities. When the ConfList softkey gets pressed, the list of conference participants remains static. The user must press the Update softkey to get the latest list. The list does not update automatically if any participant ends the call or a new participant is added.


Configuration Tips

To make the conference features available for the user, perform the following procedures:

Add the Join, RmConf, and Select softkeys by using the Softkey Configuration window.

Assign the softkey template to the user phone by using the Phone Configuration window.

Using the Join operation requires conference bridge resources. This release does not support Join across different lines. The total number of participants in the joined call must be less than the configured setting in the Maximum Ad-hoc Conference service parameter. You can configure the number from a default of 4 calls to a maximum of 64 calls depending on the number of calls that the network conference resource can support.

How this Feature Affects the User

Direct Transfer—When a user has two calls on the same line, the user can transfer the callers to each other. The user highlights the two calls and presses the Select softkey, or when already connected to one call, selects the other call. A check mark appears adjacent to selected calls. After selecting only two calls, the user presses the DirTrfr softkey. The two callers then connect and the user that initiated the direct transfer gets dropped.

Join—Users can easily join several calls in an ad hoc conference call. With all calls holding on the same line, the user chooses each call for the conference by highlighting the call and pressing the Select softkey. After choosing all calls for the conference, the user presses the Join softkey to establish the ad hoc conference call. A check mark appears adjacent to selected calls. The ad hoc conference remains connected until only two parties remain, and then the conference call reverts to a two-party call.

List of Conference Participants—Ad hoc conference members can see a list of conference participants by pressing the ConfList softkey. The conference initiator can select a conference participant in the conference list and press Remove to drop the participant from the conference.

Where to Find More Information

Cisco IP Phones, Cisco CallManager System Guide

"Softkey Template Configuration," Cisco CallManager Administration Guide

"Cisco IP Phone Configuration," Cisco CallManager Administration Guide

Cisco IP Phone Guide

Configurable Call Forward Information Displayed

An administrator can now configure each line on a phone to display the following information for a forwarded call:

Original Dialed Number (ODN)—This feature, which is enabled by default, causes the original dialed number to display upon call forward.

Redirected Dialed Number (RDN)—This feature, which is disabled by default, causes the number that was redirected to display upon call forward.

Calling Line ID (CLID)—This feature, which is enabled by default, causes the caller number to display upon call forward.

Calling Name ID (CNID)—This feature, which is disabled by default, causes the caller name to display upon call forward.

Configuration Tip

Configure these fields in the Directory Number Configuration window.

How This Feature Affects the User

Incoming Call Displays—The Cisco IP Phone can now display both the name and number of the calling party. In addition, if the incoming call was forwarded from a another phone, the phone can display the original called number.

Outgoing Call Displays—When a user dials a number on the network, the Cisco IP Phone can now display both the called party name and number. If an outgoing call forwards to another phone, the display can provide the "forwarded to" information.

Information might not display for all calls because some network facilities do not support calling and called party displays. Administrators can restrict the use of display information for some calls.

Where to Find More Information

"Cisco IP Phone Configuration," Cisco CallManager Administration Guide.

Abbreviated Dialing

Abbreviated dialing allows users to quickly access up to 99 speed-dial numbers. While the phone is onhook, users can access the additional speed-dial numbers that are not assigned to speed-dial buttons by using the AbbrDial softkey and an index number.

Configuration Tip

Administrators configure speed-dial numbers for users in the Phone Configuration window by using the Add/Update Speed Dial link.

How This Feature Affects the User

Users configure their own speed-dial list by accessing the User Options Menu web page and choosing the Add/Update Your Speed Dials link.

The user can assign some speed-dial numbers to unused line buttons. The remaining speed dials get assigned to index numbers. Assign these numbers by using the Add/Update Your Speed Dials link in the section called "Speed dials not associated with a phone button."

To access these speed-dial numbers, the user dials the index number with the phone on-hook and then presses the AbbrDial softkey. The system receives the speed-dial index and dials the associated number.

Where to Find More Information

"Cisco IP Phone Configuration," Cisco CallManager Administration Guide

"Cisco IP Phones," Cisco CallManager System Guide

Cisco IP Phone Guide

Configuring Service URL on Phone Buttons

You can now program phone buttons that are used for lines or speed dial for access to phone services. Use Cisco CallManager Administration to configure the programmable buttons as Service URL buttons for the users phone.

Configuration Tips

Creating Service URL buttons requires a six-step process:

1. Create an IP Phone service.

2. Create a phone button template to include the service.

3. Add the new phone button template to all phones that require access to the Service URL.

4. Subscribe to the service.

5. Add the Service URL button.

6. Notify users to use the Add/Update Your Service URL Button link on the User Options Menu web page.

How This Feature Affects the User

Users can program special phone buttons to access a service URL such as FastDials or a weather service. The user accesses the Cisco CallManager User Options Menu web page to subscribe to the phone service and then assigns the service to a Service URL button on the phone.

Where to Find More Information

"Cisco IP Phones," Cisco CallManager System Guide

Customizing Your Cisco IP Phone on the Web

Immediate Divert

The Immediate Divert feature immediately diverts a call to a voice-messaging system. Managers and assistants, or anyone who shares lines, use this feature. When the call gets diverted, the line becomes available to make or receive new calls. Both the caller and the called party can use Immediate Divert.

Important Configuration Tips

Configure this softkey by using the Softkey Template Configuration window of Cisco CallManager Administration.

The softkey template gets assigned to phones that are in the Cisco CallManager system.

Feature interaction with route/hunt lists: all calls distributed by a line group will not be diverted to voice messaging.

No support for immediate divert for inbound calls extended through a Q.SIG trunk.

No support for immediate divert invocation at hunt list members when the original call is received directly from other than the hunt list.

How This Feature Affects the User

Users access the Immediate Divert feature by using the iDivert softkey.

When an incoming call displays on the users phone, the user can choose to answer the call or press the iDivert softkey to send the incoming call to a voice messaging system mail box.

The called party can divert the incoming call while the call is ringing, after answering the call, or when the call is on hold.

The calling party can also divert the call to a voice messaging system mail box after the call is connected or when the call is on hold.

Where to Find More Information

"Immediate Divert," Cisco CallManager Features and Services Guide

Barge and Privacy Enhancements

The Barge and Privacy features work together. Both features work with shared lines only.

Barge and cBarge

Barge adds a user to a call that is in progress. Pressing the Barge or cBarge softkey automatically adds the user (initiator) to the shared-line call (target), and the users currently on the call receive a tone.

Phones support Barge in two conference modes:

Built-in conference bridge at the target device (the phone that is being barged). This mode uses the Barge softkey.

Shared (network) conference bridge. This mode uses the cBarge softkey.

Barge supports the following features:

Three-way barge maximum

G.711 only

When the barge target hangs up, the call reverts to a two-way call between the original connected caller and barge initiator, and Cisco CallManager releases the barge resources on the targeted phone.

cBarge includes the following features:

Creates an ad hoc conference by using network conference resources.

Maximum number of parties that is supported is based on the Maximum AdHoc Conference service parameter and the maximum number of conference participants that conference bridge resources support.

Supports all codecs that are available on the conference bridge.

The conference controller acts as the barge target.

When two parties are left, Cisco CallManager releases networked conference resources, and the call reverts to a two-party call.

Configuration Tips

System administrators should not configure both the Barge and cBarge softkeys on one phone.

cBarge requires availability of network conferencing resource (DSP resource card for bridging media streams during the barge).

The Party Entrance Tone service parameter has a global effect on Barge, cBarge, Conference, Join, and Meet-Me conference.

JTAPI and TSP applications do not support barge.

How This Feature Affects the User

Barge—Users can enter a two-party call on a shared line by pressing the Barge softkey. A party entrance tone alerts the barge targets that a user entered the call.

Conference Barge—Users can enter a call on a shared line by pressing the cBarge softkey to establish an ad hoc conference call.

Privacy

Privacy lets a user allow or disallow other users of shared-line devices to view its call information or to allow another user to barge into its active calls.

Administrators enable privacy for each device that is sharing a line. Users toggle the Privacy button to enable or disable privacy on their phone. When privacy is enabled, the remote phone that is sharing the line does not display the calling name and number, and remote users cannot barge into a call. Default specifies that Privacy is disabled.

Configuration Tips

Privacy does not affect call history (missed, placed, received) display on phones with shared-line appearances. If privacy is enabled on phone A and user at phone A places a call on the shared-line appearance, the real-time call information will not display on the other phones; however, the placed call history will show call information on the other phones.

Cisco CallManager APIs such as JTAP and TSP do not support privacy.

How This Feature Affects the User

Users can place the phone in privacy mode.

Users that share lines with a phone in privacy mode cannot barge in to a call.

Calling name and number do not display on other shared-line phones.

The administrator assigns the Privacy feature button to a phone, and this affects all lines on the phone. To enable the feature, press the Privacy button. A privacy status icon displays next to the Privacy button and indicates that the Privacy feature is enabled. When Privacy feature is enabled, the user can press Privacy again to disable the feature.

Where to Find More Information

"Barge and Privacy," Cisco CallManager Features and Services Guide.

Malicious Call Identification

System administrators enable malicious call identification (MCID) service, so a user can identify a suspicious call. While the malicious call is in progress, the user presses the MCID softkey to start the following sequence of events:

Immediately notifies the Cisco CallManager system administrator by setting an alarm.

Flags the Cisco CallManager cluster CDR as a malicious call.

Notifies off-net resources such as the Public Switched Telephone Network (PSTN) of the malicious call, so off-net resources can to take action.

The following devices and features support MCID:

All SCCP gateways

MGCP PRI-Backhaul network interface for E1(ETSI) and standard T1(NI2)

H.323 trunks and gateways

Extension Mobility

Conference calls

The system sends notifications of malicious calls through facility information element (IE) messages by using the following protocol standards:

Q.932-Digital Subscriber Signaling System 1 (DSS 1)—Generic Procedures for the Control of ISDN Supplementary Services

Q.951.7—Stage 3 description for number identification supplementary service using DSS 1: Malicious Call Identification (MCID)

EN 300 130-1—ISDN Malicious Call Identification (MCID)

Configuration Tips

To configure MCID, the administrator must set a service parameter, configure an alarm, add a softkey to a template, and assign the softkey template to the user phone.

Because QSIG has no standard for MCID the feature does not work on a QSIG connection.

Intercluster trunks do not support MCID because Cisco CallManager does not support the MCID-T component. MCID-T, a terminating function, accepts an MCID invocation and responds with a success or failure to perform the action.

How This Feature Affects the User

When the user has access to the MCID feature and is connected to a suspicious call, the user presses the MCID softkey and receives a tone and display (if a display is available) to confirm the action. This action alerts the administrator by setting an alarm and by creating a special CDR record.

Where to Find More Information

"Malicious Call Identification," Cisco CallManager Features and Services Guide

Annunciator

An annunciator, a Skinny Client Control Protocol (SCCP) device that uses the Cisco IP Voice Media Streaming Application service, enables Cisco CallManager to play prerecorded announcements (.wav files) and tones to Cisco IP Phones, gateways, and other configurable devices. The annunciator, which works with Cisco CallManager Multilevel Precedence Preemption (MLPP), enables Cisco CallManager to alert callers as to why the call fails. Annunciator can also play tones for some transferred calls and some conferences.

Annunciator includes the following features:

You can use up to two recorded audio WAV files for an announcement.

Announcements can play once or can repeat at regular intervals.

The annunciator.xml defines announcements and tones.

The annunciator device reads the database for service parameters, device settings, user locales, and network (country) locales.

Annunciator supports Wideband, G.711 mu-law, G.711 a-law, and G.729a codecs.

Annunciator supports multiple user locales and multiple network (country) locales.

Annunciator supports up to 400 simultaneous announcements, depending on your network configuration and server capability. The default setting equals 48.

A single annunciator device gets inserted into the database when you activate Cisco IP Voice Media Streaming Application service in Cisco CallManager Administration.

Where to Find More Information

"Annunciator," Cisco CallManager System Guide

"Annunciator Configuration," Cisco CallManager Administration Guide

Multilevel Precedence and Preemption

The Multilevel Precedence and Preemption (MLPP) service, introduced in Cisco CallManager 4.0, allows properly validated users to complete higher-priority calls by preempting lower-priority calls. Higher-priority calls take precedence over lower-priority calls. MLPP complies with ANSI T1.619/T1.619a and Generic Switching Center Requirements (GSCR).

MLPP plays a tone to indicate to users on an IP-to-IP phone call that their call is being preempted. A user with higher precedence can also preempt a call with lower precedence that is made through a gateway. MLPP also provides Alternate Party Diversion (APD), which allows Cisco CallManager to route the priority call to a different phone if the target party does not answer the call.

The following terms pertain to MLPP service:

Precedence—Priority level that is associated with a call

Preemption—Process of terminating lower-precedence calls that are currently using the target device such that a call of higher precedence can be extended to or through the device.

Domain—Subscription option of the originating user determines the domain. Only higher-precedence calls in the same domain can preempt connections that calls in one domain are using.

Administrators configure the MLPP indication, preemption, and domain ID at the device and device pool level. Administrators can configure five precedence levels: Flash Override (highest), Flash, Immediate, Priority, and Routine (lowest). Administrators configure precedence patterns within route patterns and translation patterns.

Users can only preempt lower-priority calls on devices that are in the same domain ID. Predefined audio tones and announcement messages that are sent by the annunciator device notify users of the higher-precedence call.

The following devices currently support MLPP: Cisco IP Phone models 7905, 7912, 7940, and 7960,7970, Cisco IP SoftPhone that uses SCCP, and MGCP-controlled TDM trunks that are using PRI/CAS.

MLPP service exhibits the following features:

PRI signals MLPP messages. T1-CAS signals via DTMF tones.

Calling search spaces (CSS) control user permissions to dial a precedence pattern.

MLPP service does not restrict the construction of route patterns. Typically, a route pattern or translation pattern contains a precedence digit.

Alternate party target and Ring No Answer (RNA) timer can be configured per line.

MLPP settings can be configured by using the Bulk Administration Tool (BAT).

From Cisco IP Phone to Cisco IP Phone, a user initiates a precedence call by dialing a well-known route pattern or translation pattern with embedded precedence selectors as part of the pattern. The device's calling search space determines whether the user is authorized for the specified precedence. If the precedence is not authorized, the call does not get extended.

The target of the precedence call receives appropriate visual and/or audible notification of a precedence call, depending upon the relative precedence of the existing calls in progress. If the target user acknowledges the precedence call attempt, the precedence call gets extended to the target.

Provision exists for optional configuration of precedence alternate party diversion target in the event that the target does not acknowledge the precedence call request. If no alternate party target is defined, normal Call Forward No Answer (CFNA) and Call Forward Busy (CFB) paths get followed. Preempted parties on Cisco IP Phones receive a tone until they hang up. Gateway parties simply get disconnected. The system does not permit modifying the precedence level of a call in midcall.

From Cisco IP Phone to trunk, MLPP service first authenticates precedence call setup through an MLPP-enabled gateway that is configured in the Cisco CallManager cluster. If the target gateway is fully subscribed (that is, all DS0s are in use), the precedence of other calls on the route group gets sampled for precedence level. A call with lower precedence gets selected, all participants in the call receive audible notification of the imminent call preemption, and the selected lower-precedence call gets terminated. The selected channel gets reserved, and a precedence call gets extended across the trunk to the destination. Precedence level gets passed over a gateway trunk, but not the domain ID, which should be configured on the trunk.

Configuration Tips

No support exists for precedence and preemption of ad hoc conference calls.

MLPP supports single-site deployments. No provision exists for extending a precedence calls and preempting existing calls across an IP trunk.

MLPP does not support the Lookahead For Busy (LFB) option.

Annunciator supports only MLPP announcements. The annunciator is not available as a general-purpose annunciator.

How This Feature Affects the User

When the administrator enables MLPP for a phone, users can perform the following tasks:

Users can choose a priority (precedence) level for an outgoing call.

Users can make a priority call.

Users can receive a priority call.

Users can accept a higher priority call (preemption).

When a user makes or receives an MLPP-enabled call, special ring tones, call waiting tones, and icons identify the type of call.

Where to Find More Information

"Multilevel Precedence and Preemption," Cisco CallManager Features and Services Guide

"Device Pool Configuration," Cisco CallManager Administration Guide

"Enterprise Parameters Configuration," Cisco CallManager Administration Guide

"Associated Alternate Routing Group Configuration," Cisco CallManager Administration Guide

"Partition Configuration," Cisco CallManager Administration Guide

"Calling Search Space Configuration," Cisco CallManager Administration Guide

"Route Pattern/Hunt Pilot Configuration," Cisco CallManager Administration Guide

"Translation Pattern Configuration," Cisco CallManager Administration Guide

"Annunciator," Cisco CallManager System Guide

"Annunciator Configuration," Cisco CallManager Administration Guide

"Gateway Configuration," Cisco CallManager Administration Guide

"Cisco IP Phone Configuration," Cisco CallManager Administration Guide

"Device Profile Configuration," Cisco CallManager Administration Guide

"Device Profile Defaults Configuration," Cisco CallManager Administration Guide

Cisco IP Phone administration guide that matches your phone model

Firmware release notes for your phone model

Attendant Console Enhancements

Cisco CallManager Attendant Console, Release 1.3(1) is compatible with Cisco CallManager, Release 4.0(1). The following list gives Cisco CallManager Attendant Console enhancements:

Support for Call Queuing—When a call comes in to a pilot point and all hunt groups members are busy, Cisco CallManager answers the call and inserts it into the queue when the queue is not full. If the queue is full, the call gets redirected to "AlwaysRoute" member. If the "AlwaysRoute" member is not configured, the call gets dropped. While the call is in the queue, the call gets put on hold, and MOH plays to the caller. Cisco CallManager redirects the call to the next available hunt group member. When the call is in the queue for longer than the configured HoldTime, the call gets redirected to the "AlwaysRoute" member. If the "AlwaysRoute" member is not configured, no action gets taken. Attendants cannot see calls in the queue.

Support for broadcast calls—When a call arrives at the broadcast hunting pilot point, Cisco CallManager answers the call and inserts it into the queue if the queue is not full. Cisco CallManager Attendant Console broadcasts the call to all available attendants. If the queue is full, the call gets redirected to "AlwaysRoute" member. If the "AlwaysRoute" member is not configured, the call gets dropped. While the call is in the queue, the call gets put on hold and MOH plays to the caller. Cisco CallManager redirects the call to the attendant who answers the call.

Support for shared lines—Calls to a pilot point get routed to a shared-line phone only when the shared line is not in use on another remote phone. Attendant phones can share lines with other attendants or non-attendants.

Multiple calls on a single line—Cisco CallManager Attendant Console supports multiple calls on a single line based on the line setting configuration in Cisco CallManager Administration.

Support for direct transfer and Join—Direct transfer merges two independent calls into one single call. Join merges a group of calls, including the attendant, into a conference call.

A configuration tool that enables you to set the JTAPI user name and password, set directory values, enable call queuing for a pilot point, set the queue parameters (such as the queue size and hold time), and configure circular hunt groups and broadcast hunt groups.

Configuration Tips

You enable queuing for a pilot point by using the Attendant Console Configuration Tool.

You enable queuing for a pilot point by using the Attendant Console Configuration Tool.

To configure the number of calls on a line, enter the appropriate value in the Maximum Number of Calls on the Directory Number Configuration window.

This release reimplements Transfer to Voicemail with JTAPI support. Administrators no longer need to edit the VoiceMailProfiles.xml property file to enable users to access voice messaging system from the Cisco CallManager Attendant Console.

How this Feature Affects the User

From the Broadcast Calls window in the Attendant Console application, users can view and answer calls.

Where to Find More Information

"Cisco CallManager Attendant Console," Cisco CallManager System Guide

"Cisco CallManager Attendant Console Configuration," Cisco CallManager Administration Guide

"Configuring IP Phones," Cisco CallManager Administration Guide

Cisco CallManager Extension Mobility Enhancements

Cisco CallManager 4.0(1) extends extension mobility functionality to most Cisco IP Phone models. Using Cisco CallManager Administration, you configure a device profile default for each Cisco IP Phone model that you want to support Cisco CallManager Extension Mobility. That phone model then takes on the device profile default whenever a user logs in to a phone model for which the user does not have a user device profile. For example, you can configure a device profile default for the Cisco IP Phone 7905 to allow a user with a user device profile for a Cisco IP Phone 7960 to use Cisco CallManager Extension Mobility on a Cisco IP  Phone 7905. The extension mobility functionality has not changed.


Note Check the Cisco IP Phone model documentation to verify that Cisco CallManager Extension Mobility is supported.


Other changes include:

The service architecture now uses Cisco Tomcat.

Cisco Extension Mobility designates the renamed extension mobility service.

The service URL follows:

http://<IP address of server>/emapp/EMAppServlet?device=
#DEVICENAME#

You use Cisco CallManager Serviceability to control the service.

The following access URLs have changed:

The URL to access Request and Query follows:

http://<IP address of server>/emservice/EMServiceServlet

The URL to access tools by application follows:

http://<IP address of server>/emservice/jsp/Tools/sampleloginapp.jsp

The URL to access tools by XML follows:

http://<IP address of server>/emservice/jsp/Tools/XMLFormRequest.html

Where to Find More Information

"Cisco CallManager Extension Mobility," Cisco CallManager Features and Services Guide

Device Profile Configuration, Cisco CallManager Administration Guide

Device Profile Default Configuration, Cisco CallManager Administration Guide

Cisco IP Manager Assistant (IPMA) Enhancement

With Cisco CallManager Release 4.0, an assistant can now support up to 33 different lines. The assistant console supports the new Join and direct transfer feature as well as the sending of DTMF digits from the assistant console. Assistants have the option to automatically launch the assistant console application when they start up their computers. Administrators have the option of not configuring an intercom line for the manager and assistant.

Cisco CallManager release 4.0 supports the use of shared lines between managers and assistants. The assistant shares the manager primary line. New phone button templates and softkey templates support phones in shared-line mode. Cisco IPMA in shared-line mode does not support call routing, and calls to a manager primary line will ring on both the manager and assistant phone.

Configuration Tips for IPMA That Is Using Shared Line

Manager phone—The manager phone includes a new softkey template called Standard IPMA Shared Mode Manager. This template includes the following softkeys:

DND—Do Not Disturb (turn ringer off)

ImmDiv—Immediate Divert (divert the selected call to a preconfigured target)

TransferToVM—Transfer To Voice Mail (redirect the selected call to the manager voice-messaging mail box)

IP Phone Service for managers—No IP Phone service for managers exists in shared-line mode

Assistant Desktop supports the following capabilities:

Handle calls for managers—When the assistant receives a call on the shared line, the calls show up on the My Calls window under the Manager Lines tree and also on the My Managers window.

Assistant can view the call state, caller ID, and time in call.

Assistant can handle calls by using context sensitive buttons or various menus and shortcuts.

Assistant can also handle calls from the phone, and the state will be reflected on the console

Assistant can search for people in the corporate/Cisco CallManager directory:

Search on the corporate directory or the Cisco CallManager directory.

Displays up to 25 entries at a time.

Provides call features such as dial, transfer, and conference.

Drag and drop a call to an entry to transfer the call.

Cisco CallManager directory search requires no extra work; however, for corporate directory, the ldapconfig.ini file needs to be updated on the IPMA server.

Configure Dial Rules by using Cisco CallManager Administration.

Assistant phone

Two new softkeys added

TrnsfVM—Transfer To Voice Mail (redirect the selected call to the corresponding manager voice-messaging mail box)

ImmDiv—Immediate Divert (redirects the selected call to a preconfigured target)

Softkeys activated after the assistant logs in from the desktop

No login required from the phone. Unified login from the desktop

Release supports Barge and allows invoking barge on a call on a shared line.

Privacy Release is supported. The call events that have privacy enabled will not display on the console.

Configuration Tips for Both Modes of IPMA

Multiple calls per line—IPMA supports multiple calls per line, which enables assistants to have multiple calls on the same line and see those calls on the console.

System supports the Direct Transfer feature from the assistant console.

System supports the Join feature from the assistant console.

Dial Digits—The ability exists to send DTMF digits from the console on connected calls.

Message Waiting Indicator—The assistant console displays the MWI status of the manager phone.

Auto Start Console on Computer Startup—The assistant preferences have an option to auto start console on computer startup.

Configuration Tips for IPMA That Is Using Proxy Mode

Call filtering mode—Call filtering mode refers to the operational mode of IPMA where the Assistant Console is configured with a manager proxy line. This proxy line represents s a line appearance that represents the manager line. This line does not get configured with a common DN with that of the manager. In this mode, the system allows call filtering, but Barge and Privacy are not offered.

Because support for multiple calls per line appearance removes the need to support multiple line appearances on same phone with common DNs, the system does not support common directory number support for multiple lines on same device (manager phone, assistant phone, assistant console). Therefore, the system does not support call rollover from one line to another as configured in Cisco CallManager release 3.3 and earlier in IPMA.

Where to Find More Information

"Cisco IPMA with Proxy Line Support," Cisco CallManager Features and Services Guide

"Cisco IPMA with Shared Line Support," Cisco CallManager Features and Services Guide

Cisco IPMA User Guide

Static Digit Analysis

Prior to Release 4.0 of Cisco CallManager, unregistered devices without configured forwarding got removed from the digit analysis (DA) table and required dynamic digit analysis. Prior to Release 4.0, when a phone unregistered, call processing allowed a call to pass to the next closest match in the Calling Search Space (CSS) list. With the introduction of static DA in Release 4.0, whether a phone is registered or not, the device remains in the DA table, and the directory number intercepts the call.

Configuration Tips

Administrators should note that the IPMA and PA applications can no longer use translation patterns for failover. Instead, administrators must set up Call Forward No Answer (CFNA) with the data that was in the translation pattern for all IPMA and PA failed route points, and these route points must be removed.

Where to Find More Information

Static Digit Analysis

Directory Enhancements

This release of Cisco CallManager includes the following directory enhancements:

Personal Address Book (PAB)—You cannot search for PAB using a default directory query from Active Directory or other third-party tools.

DCD reconfiguration scripts are now written in Perl.

CCMRegbrowser—a new tool to check the DCD version, install status, etc.

CCMPwrdChanger—a new tool to change the password for special Cisco CallManager users.

Routing Enhancements

Cisco CallManager Release 4.0 supports new routing functionality. A hunt list can contain line groups and route groups.


Note Administrators still use the Hunt Group Configuration window to configure routing for Cisco CallManager Attendant Console.


This release of Cisco CallManager supports the new concept of line groups. Cisco CallManager defines a line group as an ordered list containing one or more valid directory number members and identifies each line group by a unique group name. Administrators can configure the following line group properties:

Line Group Name

Ring No Answer (RNA) Reversion Timeout

Distribution Algorithm

Top Down (default)

Circular

Longest Idle Time

Broadcast—Cisco CallManager alerts all idle members about the call.

Hunt Options—Administrators can configure the behavior of the line group to have the following behaviors when the line group receives a no answer, busy, or not available signal:

Try next member, then try next group in hunt list. This is the default option.

Try next member, but do not go to the next group.

Skip remaining members and go directly to next group.

Stop hunting.

List of valid directory numbers


Note CTI route points and ports are not allowed.


Route groups function as designed in earlier releases. Support of route groups within a hunt list allows outbound call distribution through VoIP gateways, gatekeepers, H.323 logical trunks, and SIP logical trunks. Route groups do not support RNAR. Route groups support the Top Down and Circular call distribution algorithms.

Route lists have been renamed Route/Hunt List with the following expanded functionality and properties:

Configurable name and description

Associated hunt pilot number that is a route pattern. A caller can reach someone by dialing the hunt pilot number.

Associated line groups. Multiple line groups can be configured in a route/hunt list to create a variety of different hunt possibilities.

Associated route groups


Note No line groups can follow a route group once a route group is inserted into a route/hunt list.


Route/hunt lists have associated Perfmon counters to track hunt list performance. Performance enhancements support 1500 hunt lists with ten members each with broadcast hunting on an MCS-7835-1400.

Route/hunt lists replace voice-mail forwarding chains in Unity configuration. To effect this change, place voice-mail ports in a line group. For redundant Unity systems, add additional line groups. Set the No Answer Hunt option to "Skip remaining members and go directly to next group."

Configuration Tips

The following caveats exist for line groups, route groups, route/hunt lists, and route patterns/hunt pilots:

No voice-mail profile exists for a hunt pilot number. Immediate Divert and Call Forwarding to voice mail are not allowed.

No forwarding is allowed for a hunt pilot number.

Call pickup is not allowed for a hunt pilot number.

A caller/application only sees the hunt pilot number as a destination and not the actual number of a person with whom the caller is talking.

When a parked call reverts to the original caller, the reversion goes back to the hunt pilot and therefore may not go back to the phone that parked the call.

A hunt list can contain line groups only, route groups only, or line groups followed by route groups only. A line group cannot follow a route group in the same hunt list.

No call queuing engine is provided with native Cisco CallManager hunt group mechanisms in this release. The Attendant Console hunt groups do have a queuing capability that the TCD service implements.

No support exists for CTI route points or ports in line groups.

No support exists for multiple chaining of multiple hunt lists.

Cisco Call Back is not functional for lines/DNs configured as line group members.

The iDivert feature is not functional for lines/DNs configured as line group members.

Where to Find More Information

"Understanding Route Plans," Cisco CallManager System Guide

"Line Group Configuration," Cisco CallManager Administration Guide

"Route Group Configuration," Cisco CallManager Administration Guide

"Route/Hunt List Configuration," Cisco CallManager Administration Guide

"Route Pattern/Hunt Pilot Configuration," Cisco CallManager Administration Guide

"Voice Mail Connectivity to Cisco CallManager," Cisco CallManager System Guide

"Cisco Voice-Mail Port Configuration," Cisco CallManager Administration Guide

"Cisco Voice Mail Port Wizard," Cisco CallManager Administration Guide

Cisco Unity Voice-Mail Port Adjustments

Migration from Cisco CallManager 3.3(3) to Cisco CallManager 4.0(1) requires adjustments to the voice-mail port settings.

Where to Find More Information

Refer to the "Cisco Unity Voice-Mail Port Changes" section

Additional Media Resources Support

Cisco CallManager 4.0(1) includes the following new media resource enhancements or features:

Cisco CallManager provides support for Annunciator, as described in the "Annunciator" section.

Cisco CallManager supports DTMF relay based on RFC-2833 for Session Initiation Protocol (SIP) trunks.

Cisco CallManager provides MTP, transcoding, and conferencing support for NM-HD on Cisco 2600XM, Cisco 2691, Cisco 3725, Cisco 3745, and Cisco 3660 gateways.

The following list represents the maximum number of sessions that are available for conferences, transcoding, and MTP with the NM-HD:

G.711 only conference—24

G.729 conference—6

GSM FR conference—2

GSM EFR conference—1


Tip Maximum number of participants per conference equals 8.


Transcoding for G.711 to G.729a/G.729ab/GSMFR—24

Transcoding for G.711 to G.729/G.729b/GSM EFR—18

For a software MTP (DSP-less with same packetization period for both devices that support G.711 to G.711 or G.729 to G.729 codecs), 500 sessions can occur per gateway; for a hardware MTP (with DSP, using G.711 codec only), 48 sessions can occur per NM-HD.

Cisco CallManager adds a new type of conference bridge, the Cisco Video Conference Bridge (IPVC-35xx).

Where to Find More Information

"Cisco DSP Resources for Transcoding, Conferencing, and MTP," Cisco CallManager System Guide

"Media Termination Points," Cisco CallManager System Guide

"Transcoders," Cisco CallManager System Guide

"Conference Bridges," Cisco CallManager System Guide

"Conference Bridge Configuration," Cisco CallManager Administration Guide

Cisco IP/VC 3511 MCU and Cisco IP/VC 3540 MCU Module Administrator Guide

Multilevel Administration Access Enhancements

In Release 4.0 of Cisco CallManager, Multilevel Administration (MLA) functions as follows:

MLA no longer requires separate installation: Cisco CallManager comes with an integrated MLA component. Find MLA functions under the User > Access Rights menu item.

By default, MLA remains disabled except in the following case: if an upgrade from Cisco CallManager 3.3 with MLA 1.2 takes place, data migrates to the Cisco CallManager 4.0 database, and MLA 1.2 gets uninstalled.

If a previous Cisco CallManager release had MLA installed, MLA migrates data, enables MLA, and preserves the CCMAdministrator password.

Important Login and Configuration Tips

Without MLA, login authentication uses the local NT administrative account. If MLA is disabled, log in as the NT administrator.

With MLA, login authentication changes to use LDAP authentication. The CCMAdministrator or an LDAP user in an MLA user group performs login. If access takes place to virtual directories that are set with basic authentication that MLA does not support, a dialog pop-up window asks for the NT Administrator and password.

To enable MLA, use the MLA Enterprise Parameters Configuration window under menu item User > Access Rights > Configure MLA Parameters. Set the Enable MultiLevelAdmin field to True and perform an update to the window.

If MLA is enabled, log in for the first time as the CCMAdministrator. The special login user, CCMAdministrator, represents the only user that can access Cisco CallManager Administration and Serviceability when MLA gets enabled for the first time. This user also represents the only user that can log in even if LDAP is down. This user has full access to all windows.

Set up the CCMAdministrator password upon enabling MLA. In the case of an upgrade from Cisco CallManager 3.3, the existing CCMAdministrator password remains in effect after installation of Cisco CallManager 4.0.

Where to Find More Information

"Multilevel Administration Access," Cisco CallManager System Guide

"Multilevel Administration Access Configuration," Cisco CallManager Administration Guide

QSIG Protocol

Cisco CallManager supports the ISO variant of QSIG that provides connections and some feature transparency between these tested QSIG PBXs:

Avaya Definity

Nortel Meridian

Alcatel 4400

Siemens Hicom

Ericsson MD110

IPC IPMX trading turret key system

BT Syntegra trading turret system

This release supports the following QSIG supplementary services:

Configure calling display information on the gateway or on a call-by-call basis by using route patterns and translation patterns. Restrictions for calling name display information include Calling Name Identification Restriction (CNIR) and Connected Name Identification Restriction (CONR).

Enable the Message Waiting Indicator (MWI) and disable the MWI through application protocol data unit (APDU) messages. Cisco CallManager can send MWI and receive MWI over connections with QSIG PBXs.

Cisco CallManager implements call diversion by using forward switching and protects calls from going into forwarding loops by using Call Diversion Counters. APDUs carry the call diversion information. Cisco CallManager supports the following supplementary services:

Call Forward Unconditional (SS-CFU)

Call Forward Busy (SS-CFB)

Call Forward No Reply (SS-CFNR)

Calls transfers to QSIG PBXs by using join, not by reroute. When a call transfers to another PBX, the system synchronizes post-transaction line identification and called or connected identification. Release does not support QSIG path replacement.

Where to Find More Information

"Understanding IP Telephony Protocols," Cisco CallManager System Guide

"Gateway Configuration," Cisco CallManager Administration Guide

Session Initiation Protocol (SIP) Trunk

Cisco CallManager Release 4.0 fully supports SIP as it is defined in RFC 2543 bis4 and partially supports the protocol as it is defined in RFC 3261. Administrators can configure SIP trunks to support communication to a SIP network and to support intercluster communication. For calls through a SIP trunk, Cisco CallManager supports initiating the following supplementary services from SCCP devices after the completion of call setup:

Hold

Transfer

Ad hoc conference

Call Forward (All, Busy, and No Answer)

Call Pickup

Call Park

Join

SIP-initiated supplementary services include the following capabilities:

Hold when the SIP endpoint initiates it

Call Forward (Busy/All/No answer)

Not supported: SIP-initiated Transfer, both blind and consultation transfer

Cisco CallManager supports bidirectional identification for the following services:

Calling Line Identification (CLID)/Calling Line Identification Restriction (CLIR)

Calling Party Name Identification (CNID)/Calling Party Name Identification Restriction (CNIR)

Connected Party Line Identification (COLD)/Connected Party Line Identification Restriction (COLR)

Connected Party Name Identification (COND)/Connected Party Name Identification Restriction (CONR)

Redirected Dial Number ID Service (RDNIS) information for voice-messaging support

In addition, Cisco CallManager supports domain name system (DNS) Server (SRV) Resource Record (RR) lookup as specified in RFC 2782, "A DNS RR for Specifying the Location of Services (DNS SRV)."

Cisco CallManager includes session description protocol (SDP) port information to support early media cut-through and faster call setup.

Configuration Tips

Administrators can restrict the calling or connected party information on the SIP trunk level or on a call-by-call basis by using route patterns, with trunk level restriction taking precedence.

Currently, the system defines no SIP standard for connected party identification services. Cisco CallManager uses IETF Remote-Party-Id draft to implement these functionalities. If this draft is not implemented by networked SIP devices, connected party identification may not be synchronized with Cisco CallManager controlled devices after supplementary services such as call transfer are invoked.

Cisco CallManager also supports the RFC 2833, "RTP Payload for DTMF Digits, Telephony Tones and Telephony Signals." Administrators configure Cisco CallManager to support dynamic payload type for DTMF tones by setting the SIPTelephonyEventPayloadType service parameter.

Although SIP trunk performance is the same as that of H.323 trunks, all SIP calls require a Media Termination Point (MTP); therefore, sustained calls are limited to the number of available MTP resources that are configured in the Media Resource List. Administrators can configure multiple SIP logical trunks similar to the use of H.323 logical trunks.

SIP interoperability testing included the following items:

Cisco SIP-enabled IP Phones

Cisco SIP-enabled VoIP gateways

Microsoft Messenger

G.711 pass-through fax

Clusters that run Cisco CallManager 4.0(1)

Where to Find More Information

"Understanding Session Initiation Protocol," Cisco CallManager System Guide

"Trunk Configuration," Cisco CallManager Administration Guide

"A DNS RR for Specifying the Location of Services (DNS SRV)," RFC 2782

"RTP Payload for DTMF Digits, Telephony Tones and Telephony Signals," RFC 2833

Support for Video Calls

This release adds support for video calls. Cisco CallManager Release 4.0 overcomes the high cost of video and the difficulty of use by providing user-friendly access to video calls, including a single number for voice and audio, video calls that are dialed like voice calls, and a single point of administration. Cisco CallManager 4.0 allows integration of video networks with voice networks, which have been separate until now. Enhancements to H.323 and SCCP signaling and call processing within Cisco CallManager allow video calls to be placed with the same model as audio calls.

Cisco CallManager provides a common control agent for setting up configurations, signaling endpoints, and the servicing of voice and video endpoints. This allows Cisco CallManager to provide the following features:

A uniform dial plan for common calling patterns

A complete set of serviceability capabilities, including Call Detail Records and Perfmon counters, captures video information

Call admission control for quality-of-service support through enhancements to regions, locations, and the new Retry Video Call as Audio setting

Call rerouting

Support for features currently available on voice phones to video phones such as park, hold, resume, transfer, forward, conference, join, and music on hold

Support for remote camera control and video endpoint management

Support for Cisco IP V/C Media Control Units (MCU) using H.323 or SCCP

H.323 endpoint support for call-routing features such as common dialing, call forwarding, shared lines, and hunt groups. Full H.323 endpoint capabilities depend on their support of the Empty Capability Set (ECS).

Signaling and media control video awareness. Because Cisco CallManager is aware of the media capabilities of video-capable endpoints, system administrators can more intelligently manage system and user policy.

Cisco CallManager supports the typical video call with two or three RTP streams in each direction by using video codecs H.261 and H.263, as well as current audio codecs plus G.722 and G.728, and far-end camera control. The total bandwidth of a video call comprises the sum of both the audio bandwidth and the video bandwidth plus overhead.

Cisco CallManager Release 4.0 operates with Cisco's current video portfolio, which includes the following devices:

Cisco IP/VC 3511 (video bridge)

Cisco IP 3520 (V.35/BRI H.323/H.320 gateway)

Cisco IP/VC 3525 (PRI H.323/H.320 gateway)

Cisco IP/VC 3540 (chassis-based bridge/gateway unit)

IOS H.323 gatekeeper

Cisco IP/VC 3526 (PRI H.323/H.320 Gateway)

Cisco CallManager Release 4.0 supports existing Cisco IP Phones with video capabilities and extends their capabilities. Release 4.0 also supports new Cisco SCCP-controlled voice-video IP phones, IP phone calls with video on PCs, third-party SCCP room and executive systems, and far-end camera control (FECC) between SCCP endpoints and compatible H.323 endpoints.

Where to Find More Information

"Understanding Video Telephony," Cisco CallManager System Guide

"Call Admission Control," Cisco CallManager System Guide

"Location Configuration," Cisco CallManager Administration Guide

"Conference Bridge Configuration," Cisco CallManager Administration Guide

"Media Resource Group Configuration," Cisco CallManager Administration Guide

"Media Resource Group List Configuration," Cisco CallManager Administration Guide

"Automated Alternate Routing Group Configuration," Cisco CallManager Administration Guide

"Route/Hunt List Configuration," Cisco CallManager Administration Guide

"Gateway Configuration," Cisco CallManager Administration Guide

"Cisco IP Phone Configuration," Cisco CallManager Administration Guide

"Trunk Configuration," Cisco CallManager Administration Guide

Cisco CallManager Serviceability System Guide

Cisco CallManager Serviceability Administration Guide

H.323 Enhancements

Some H.323 endpoints wait for the far end device to send Terminal Capability Set before sending their own Terminal Capability Set. These endpoints may become deadlocked where neither endpoints send a Terminal Capability Set. The "Active Capability" feature has been added to address this. Prior to Cisco CallManager 4.0, the active capability feature was only active on Intercluster Trunks.


Note Do not enable this feature if your calls are currently working.


Configuration Tips

You enable active capability by unchecking the Wait for Far End H.245 Terminal Capability Set onH.323 clients, gateways and H.225 trunks.

Active capability is disabled by default. You cannot disable active capabilities on intercluster trunks; by default, intercluster trunks are active capable.

Cisco Callmanager may not be able to allocate transcoder resources in some scenarios when capabilities are sent before Cisco CallManager server receives the capabilities of the far end device. When you need a transcoder with Active Capabilities enabled, add the transcoder to the Media Resource Group List (MRGL) that the H.323 devices uses, and check the Media Termination Required check box in the H.323 device configuration. All MTPs and transcoders in the MRGL must support all the codecs that are used by the H.323 device.

Cisco CallManager does not connect a call when neither endpoint initiate capabilities. Configure one of the endpoints to initiate capabilities.

H.323 calls may still fail when Cisco CallManager cannot allocate transcoder resources. To ensure that Cisco CallManager allocates transcoder resources for an H.323 call, add the transcoder to the Media Resource Group List and check the Media Termination Required check box in the H.323 device configuration.

Removing a Deleted Subscriber

You delete a subscriber server from the Cisco CallManager cluster by using the Server Configuration window in Cisco CallManager Administration. This deletion, however, deletes the server from the Cisco CallManager Administration database, but not all server dependencies get deleted.

Configuration Tips

1. Remove all dependencies from the server; for example, delete the Cisco CallManager service.

2. Remove the server from Cisco CallManager Administration.

3. Run a script file that removes the SQL replication information from the database.

4. Run a script file that removes the DCD replication agreements from the publisher if Cisco CallManager cluster is integrated with local DCDirectory.

Where to Find More Information

"Server Configuration," Cisco CallManager Administration Guide

"Removing a Subscriber Server from Cisco CallManager," Cisco CallManager Administration Guide

Security

You implement authentication and encryption to prevent identity theft of phones and the Cisco CallManager server, data tampering, and call-signaling/media-stream tampering. To alleviate these threats, Cisco CallManager establishes and maintains authenticated communication streams between the phone and the server, digitally signs files before the file is transferred to the phone, and encrypts media streams and call signaling between Cisco IP Phones.

The following information applies to security:

The Cisco CallManager 4.0(1) cluster boots up in nonsecure mode, and all devices register as nonsecure with Cisco CallManager.

The Cisco CallManager installation creates a self-signed X.509 certificate for each server in the cluster.

Encryption installs automatically when you install Cisco CallManager.

Cisco CallManager supports authentication, integrity, and encryption for Cisco IP Phone to Cisco IP Phone calls in a single cluster where no media services are used.

Configuration Tips

Not all Cisco IP Phone models support authentication and encryption; refer to the Cisco IP Phone authentication and encryption document, the phone administration guide, or the firmware release notes.

You cannot implement encryption if authentication does not exist in the cluster; that is, if you do not install and configure the Cisco CTL client.

Before you install the Cisco CTL client, verify that the workstation or server runs Windows 2000 sp3a (or later) and has a USB port.

Do not use Terminal Services or Virtual Network Computing (VNC) to install or use the Cisco CTL client.

To use the Cisco CTL client, you must activate the Cisco CTL Provider service on every server in the cluster that runs the Cisco CallManager or Cisco TFTP services.

You must obtain at least two Cisco System Administrator Security Tokens, which contain a X.509 certificate, to create the CTL file.

To update the Cisco CTL file, you must obtain one security token that exists in the current Cisco CTL file.

The Cisco CallManager cluster can run in either nonsecure or mixed mode, but only mixed mode supports security.

You set the clusterwide security mode to mixed mode through the Cisco CTL client; you cannot set this parameter in Cisco CallManager Administration.

With multicluster TFTP configurations, you must configure all Cisco CallManager clusters for the same security mode through the Cisco CTL client. You must install the Cisco CTL client in each cluster and choose the same clusterwide security mode during the configuration.

Ensure that the TFTP path and alternate TFTP paths for building configuration files are unique; if the paths are not unique, a TFTP server may overwrite the CTL file that the other cluster creates.

Auto-registration does not work when you configure the cluster for mixed mode.

After you configure security, the Cisco CallManager server cannot use NETBIOS over TCP to send messages.

Application Layer Gateways (ALG) that allow Voice over IP to traverse firewalls and Network Address Translation (NAT) do not work with signaling encryption.

After you configure encryption, management/debug tools that sniff packets do not work.

Do not use Terminal Services to install the CAPF utility. You can use VNC to install the CAPF utility, but do not use VNC when you use the CAPF utility to generate certificates.

Use Windows native mode IPSEC for authenticated and encrypted signaling to gateways and other application servers; for example, Cisco Unity, or Cisco IP Contact Center (IPCC), or other Cisco CallManager servers.

You can use Integrated Windows Authentication.

In Cisco CallManager Administration, you can disable HTTP and telnet ports for phones.

How This Feature Affects the User

A security enabled phone supports these types of calls:

Non-secure Call—At least one of the phones or the connection does not support security features.

Authenticated Call—The system verifies identities of all phones that are connected to the call.

Encrypted Call—The system encrypts data (conversation) in the call, so no one can listen in, and only the intended recipient receives the call. The system also authenticates encrypted calls.

A security status icon displays on the phone and identifies the type of security for the connected call.

Support for encrypted and authenticated calls differs on midrange and high-end phones.

Where to Find More Information

Cisco IP Phone Authentication and Encryption for Cisco CallManager 4.0(1)

Cisco IP Phone administration guide that matches your phone model

Firmware release notes for your phone model

Bulk Administration Tool Enhancements

Bulk Administration Tool (BAT) release 5.0(1) includes the following enhancements:

The Bulk Administration Tool Wizard guides administrators through bulk configuration tasks with step-by-step procedures that link to the web pages for each task. Administrators can easily update phones and lines by using the BAT web interface.

Administrator s can use a flexible comma-separated values (CSV) data input file format for phones and user device profiles. Administrators can choose the phone or user device profile fields to use in the CSV file and arrange the order of the fields. The first record of the CSV file shows the customized file format. Values in the CSV file take precedence over template values.

A BAT report utility generates reports in CSV format with information about phones, users, user device profiles, managers and assistants, and gateway records. Reports do not get generated for the Cisco Catalyst 6000 FXS ports. Administrators can customize reports for phones and user device profiles by selecting and arranging the order of the fields in the report. You can import report data into Microsoft Excel to format and print the report.

By using a master template, administrators can configure phones or user device profiles with a variable number of lines provided the number of lines is less than or equal to the number of lines in the master template.

When using the export utility, a new device summary report shows all existing devices in the system with the number of lines that are configured on each device. This report information helps the administrator create queries for BAT export transactions.

Administrators can use a custom file to update and delete users now, when using queries is not feasible.

Configuration Tips

Be aware of the following limitations:

You cannot insert user records that are exported from one type of directory into a different type of directory. Exporting user data does not export a user that is his own manager.

When user records are migrated from Active Directory, passwords do not get exported. Administrators or users will need to assign a password after completing the migration.

Database changes between releases make it impossible to export records from a former Cisco CallManager release such as 3.3.3 and insert these records into a later Cisco CallManager release such as 4.0.

Where to Find More Information

Bulk Administration Tool User Guide

Tool for Auto-Registered Phone Support Enhancements

The Tool for Auto-Registered Phone support (TAPS) 5.0(1) has the following enhancements:

This release separates TAPS installation from the BAT installation. Administrators can perform the TAPS installation once on a server with both Cisco CallManager and Cisco Customer Response Solution.

TAPS includes a web interface for configuring the TAPS settings. System Administrators can access TAPS administration from the BAT configuration menu.

Administrators can select different locales and languages for TAPS prompts by using the TAPS administration windows. The first prompt plays in the systemwide user locale default language.

Configuration Tip

If you are planning to use TAPS to configure shared-line phones, you must create a unique external phone number mask for each shared-line phone.

Where to Find More Information

Bulk Administration Tool User Guide

CDR Analysis and Reporting (CAR) Enhancements

In Cisco CallManager Release 4.0, the CDR Analysis and Reporting Tool (CAR) supports new hunting features for MLPP and Malicious Call and new conference reports. This release enhances CDR management to export CDR records for date range and allows specific purging.

The following list describes the CAR enhancements for Release 4.0:

New hunting features

Route Patterns will now list the configured Route/Hunt List.

Route/Hunt List will now list the Line Groups in addition to Route Groups

You can perform Route Pattern searches.

MLPP (Multilevel Preemption and Precedence) service—New reports and changes for Call Precedence

Call Summary by Precedence Level

CDR Search changes by Call Precedence Level

Malicious Call—New reports and changes for Malicious Call

Malicious Call Details

Call Detail Search for Malicious Calls

CDR Management

Export CDR/CMR Records obtains the CDR/CMR dump information for the given date range in CSV format.

You can purge CDR between two dates by using Manual Purge

No change in Automatic Purge of CDRs

Conference Reports

Conference Reports support Cisco CallManager ad hoc and meet me conferences and supports newly added Application Controlled Conference Bridge.

Conference Call Details Summary Report—Displays the summary information of conference calls that took place during the chosen date/time range.

Conference Call Details Detailed Report—Displays the detailed information about the conference calls that took place during the chosen date/time range, including information about each participant call leg.

Configuration Tip

Only the top 50 Route Patterns will be listed in the menu on the left side of the pane.

Where to Find More Information

Cisco CallManager Serviceability System Guide

Cisco CallManager Serviceability Administration Guide

Tomcat Web Server

Cisco CallManager 4.0 uses Tomcat 4.1(12) web server and the Tomcat Web Application Manager for Cisco IPMA, Cisco WebDialer, Cisco Extension Mobility, and Cisco CDR Analysis and Reporting.

Configuration Tips

You can stop and start any individual application without having to restart the Tomcat services.

Users who belong to the group Administrator within the Microsoft Windows NT domain can access the Tomcat Web Application Manager on the Cisco CallManager server by going to http://<server-name>/manager/list.

New and Changed Information for Cisco CallManager Serviceability

This section describes the following new serviceability features and changes that are pertinent to this release of Cisco CallManager:

TroubleShooting Trace Setting

Cisco CallManager Trace Collection Tool

Real-Time Monitoring Tool (RTMT) as Standalone Plugin

Serviceability Reports Archive

SNMP and Performance Counter Enhancements

TroubleShooting Trace Setting

The TroubleShooting Trace Setting tool allows users to set/reset the troubleshooting traces for chosen services in the Cisco CallManager cluster from a single window, as well as set adequate trace (SDI and SDL) settings to troubleshoot Cisco CallManager services. Using this tool, users can choose the required services on different Cisco CallManager nodes in the cluster, so the trace settings of the chosen services get changed to reflect the predetermined trace settings.

Troubleshooting trace settings differ from the default trace settings. The development team for troubleshooting predetermines the troubleshooting trace settings for each Cisco CallManager service. While troubleshooting trace is set, most trace configuration parameters are disabled in the trace configuration windows.

Find the TroubleShooting Trace Setting tool, which is new with Release 4.0(1), in the Trace menu in Cisco CallManager Serviceability.

Cisco CallManager Trace Collection Tool

Release 4.0 removes trace collection for Cisco CallManager from the Trace menu of Cisco CallManager Serviceability Administration and installs as a Cisco CallManager client plugin tool that users can download from the Plugins page and installs on a client machine. This tool collects traces for a Cisco CallManager cluster into a single zip file. The collection includes all traces for Cisco CallManager and logs, such as Event Viewer (Application, System, Security), Dr. Watson log, Cisco Update, Prog logs, RIS DC logs, SQL, and IIS logs.

The Trace Collection Tool collects traces from a remote machine for the following components on chosen servers in the Cisco CallManager cluster:

Chosen Cisco CallManager services

Chosen Cisco CallManager applications

Chosen Cisco CallManager system traces

The Trace Collection Tool collects the traces and saves them in the form of a zip file (as a single file or split into multiple files) by using a different compression factor. You can collect traces for a chosen period or for all available traces.

You can install the Trace Collection Tool on Windows 2000, 98, or XP client.

Real-Time Monitoring Tool (RTMT) as Standalone Plugin

Real-Time Monitoring Tool (RTMT) enhancements provide client-side functionality that did not exist in previous versions of Cisco CallManager. With the 4.0 version, RTMT monitors and reports on typical precanned (preconfigured) alerts. This type of monitoring allows the system administrator to have a comprehensive view of the entire Cisco CallManager cluster with little RTMT configuration. The precanned alerts allow the administrator to be alerted, via e-mail or e-mail pager, about typical Cisco CallManager server or service problems.The precanned reporting allows some minor trending as well as troubleshooting problems after they occur.

The new client-side RTMT plugin continuously monitors real-time behavior of the components in a Cisco CallManager cluster. It uses HTTP and TCP to monitor system performance, critical services, call activity, device status, and CTI applications.

The following list comprises the RTMT enhancements for Cisco CallManager Release 4.0:

RTMT runs as a standalone java application (prior to Release 4.0, RTMT ran as a java applet).

Because typical monitoring views are precanned, the majority of desired views come ready to run upon installation.

Backend Alerting allows system administrators to set up alerts on critical services to send by e-mail or page.

Service parameter enhancements

You can install RTMT on remote PC by using the Cisco CallManager Plugins window.

RTMT includes the following precanned monitors (packaged with RTMT, so no configuration is required by the system administrator):

Memory and CPU Utilization

Disk Utilization

Critical Cisco CallManager and System Services

Call Activity

SDL Queue Depth—Shows when Cisco CallManager queues get backed up, which indicates potential poor Cisco CallManager performance.

Cisco TFTP

Directory

Cisco CallManager Heartbeat Information

Summary of Registered Devices

CTIManager

Precanned Alerts (typical Cisco CallManager and system parameters that can detect problems in the network) cam alert the system administrator via e-mail or pager, and administrators can troubleshoot accordingly. The following list comprises the precanned alerts that RTMT includes:

NumberOfRegisteredPhonesDropped

NumberOfRegisteredGatewayDevicesDecreased

NumberOfRegisteredGatewayDevicesIncreased

NumberOfRegisteredMediaDevicesDecreased

NumberOfRegisteredMediaDevicesIncreased

MediaListExhausted

MgcpDChannelOutOfService

RouteListExhausted

CriticalServiceDown

CallProcessingNodeCpuPegging

NonCallProcessingNodeCpuPegging

LowInAvailableMemory

LowInAvailableDiskSpace

LowCallManagerHeartbeatRate

LowTFTPServerHeartbeatRate

LowTcdServerHeartbeatRate

DirectoryConnectionFailed

DirectoryReplicationFailed

MaliciousCallTrace

ExcessiveVoiceQualityReports

CodeYellowEntry

CodeRedEntry

Cisco CallManager Serviceability Reporter logs reports and CSV files of key performance counters for troubleshooting and trending. (See the "Serviceability Reports Archive" section for information on viewing the reports that by Reporter generates.) The following reports automatically generate:

Alert Report (shows what alerts were generated on a daily basis)

Device Statistics Report

Server Statistics Report

Service Statistics Report

CSV files get saved for the customer, TAC (Technical Assistance Center), or development engineer for use in troubleshooting problems.


Note RTMT continues to monitor real-time behavior of Cisco CallManager components in the background, even when RTMT is not running.


Serviceability Reports Archive

The Cisco CallManager Serviceability Reports Archive allows users to view reports that the NT service Cisco CallManager Serviceability Reporter generates. Reporter generates five daily reports in Cisco CallManager Serviceability Administration: Device Statistics, Server Statistics, Service Statistics, Call Activities, and Alert. Each report provides a summary that comprises different charts that display the statistics for that particular report.

Users can view the reports by accessing Cisco CallManager Serviceability > Tools > Serviceability Reports Archive.

SNMP and Performance Counter Enhancements

Cisco CallManager SNMP for Release 4.0 provides the following changes and enhancements:

New MIB objects:

ccmSystemVersion—As the installed version of the local Cisco CallManager system, it matches the system version that displays in the Cisco CallManager Administration main window.

ccmInstallationId—As the installation component identifier of the local Cisco CallManager component (ccm.exe), it matches the Installation ID that displays in the Cisco CallManager Administration main window.

A new table, ccmSIPDeviceTable, provides SIP trunk information.

Dynamic population of product types in CCM MIB means that the CCM MIB will always be up to date with all the new device types that Cisco CallManager supports. A new table, ccmProductTypeTable, provides the list of all the product types that Cisco CallManager supports.

A new column that was added in each device table in CCM MIB relates to the product type in the ccmProductTypeTable.

Existing static (enum based) device type definitions are deprecated.

The following SNMP traps, with associated trap objects, that were added alert the system administrator of a malicious call or quality report: ccmMaliciousCall and ccmQualityReport.

ccmMaliciousCall—This notification gets sent when a user registers a call with the local Cisco CallManager as malicious.

ccmQualityReport—This notification gets sent when a user reports a quality problem while using the Quality Report Tool.

ccmQualityReportAlarmEnable flag enables/disables ccmQualityReport Trap.

Release 4.0 adds Cisco IP Phone 7970 in ccmPhoneType.

Release 4.0 adds several media device types in ccmMediaDeviceType.

Release 4.0 adds several new performance objects and counters to support new Cisco CallManager features. Release 4.0 adds performance counters for the application-controlled bridge device, annunciator, security, video, hunt lists, SIP, transcoders, MTP, software conference bridge, and hardware conference bridge. The release also renamed and/or deleted some system performance counters.

Where to Find More Information

Cisco CallManager Serviceability System Guide

Cisco CallManager Serviceability Administration Guide

New and Changed Information for Third-Party and SDK Applications

This following sections describe new features and changes that are pertinent to this release of Cisco CallManager and third-party and SDK applications.

Cisco CallManager Call Detail Record Definition

Cisco CallManager Extension Mobility API Developer Guide Release 4.0(1)

Cisco IP Phone Services Application Development Notes

Cisco JTAPI Developer Guide for Cisco CallManager 4.0(1)

Cisco JTAPI Installation Guide for Cisco CallManager 4.0(1)

Cisco TAPI Developer and Installation Guides for Cisco CallManager 4.0(1)

Refer to each guide for specific details.

Cisco CallManager Call Detail Record Definition

This section describes any new features and or changes for CDRs that are pertinent to Cisco CallManager release 4.0(1):

Identifies Multilevel Precedence and Preemption (MLPP)

Adds the new field origPrecendenceLevel for the precedence level of the originating leg of the call

Adds the new field destPrecedenceLvel for the precedence level of the destination leg of the call

MLPP utilizes existing cause codes 8, 9, 46, 50, and 128.

Identifies malicious calls by adding a new Comment field

Drop any party feature utilizes existing cause fields: origCause_value and destCause_value.

OnBehalfOf field contains a new code (value = 14) for the Immediate Divert feature and value = 15 for Barge.

The following new fields support video in Cisco CallManager:

origVideoCap_Codec

destVideoCap_Codec

origVideoCap_Bandwidth

destVideoCap_Bandwidth

origVideoCap_Resolution

destVideoCap_Resolution

origVideoTransportAddress_IP

origVideoTransportAddress_Port

destVideoTransportAddress_IP

destVideoTransportAddress_Port

Adds user login fields (callingPartyLoginUserID and finalCalledPartyLoginUserID) to ensure that a valid UserID is associated with a newly created phone device and is properly reported in CDRs

Adds CDRView Utility examples for different call scenarios including IDivert, Barge, and cBarge

Cisco CallManager Extension Mobility API Developer Guide Release 4.0(1)

The following list provides the features or changes for Cisco Extension Mobility service API developers in Cisco CallManager release 4.0(1):

Tomcat Servlet architecture replaces the ASP block.

Connection from the IIS to the Tomcat server uses the established AJP mechanism.

The Login Service Java Object runs in the Tomcat Servlet.

The Tomcat Servlet Logout Scheduler assumes the functionality that the Logout NT Service previously performed and contains a new data structure in the scheduling information.

Communication from the Extension Mobility service to the DBL uses JNI instead of COM.

Cisco IP Phone Services Application Development Notes

The following list provides the features or changes for Cisco IP Phone developers in Cisco CallManager 4.0(1):

Cisco IP Phones 7905, 7912, and 7920 support XML services.

RTP streaming includes the Volume feature.

The CiscoIPPhoneImageFile object supports advanced higher-resolution displays. The CiscoIPPhoneImageFile object behaves identically to the CiscoIpPhoneImage object except that the image data no longer gets embedded in the XML object by using the <Data> tag. Instead, a <URL> tag points to the PNG image file.

The CiscoIPPhoneGraphicFileMenu object exposes the touchscreen capability for devices that can receive and process pointer events.

The IP phone client request to send the relevant information from the IP phone to the web server application includes the following HTTP headers:

x-CiscoIPPhoneModelName

x-CiscoIPPhoneDisplay

x-CiscoIPPhoneSDKVersion

Accept

The updated <ExecuteItem> tag of the <CiscoIPPhoneExecute> object with an optional attribute called Priority informs the phone of the urgency of the execute request and whether the phone should be interrupted to perform the request. The Priority levels determine whether the phone must be idle to perform the requested action.

Cisco JTAPI Developer Guide for Cisco CallManager 4.0(1)

The following list provides the features or changes for Cisco JTAPI in Cisco CallManager release 4.0(1):

Multiple Calls Per DN—Enables applications to have multiple calls on the same line with feature operations.

Shared Line Support—Provides the following abilities to applications:

Control shared DN terminals

Hold a call on one shared DN terminal and unhold the same call from another shared DN terminal

Make calls between two shared lines

Initiate a call from one shared-line terminal while another active call exists on another shared-line terminal with the same DN

Transfer and DirectTransfer—Provides the following enhancements:

Application can transfer two held calls.

Application can have one held call and one connected call in any order.

Application can transfer any two calls that are present on the line.

Conference and Join—Enhanced to perform Arbitrary Conference of multiple calls.

Barge, CBarge, and Privacy Event Notification—For Barge and CBarge, Cisco JTAPI supports manual feature activation on the application-controlled IP phones. The system does not support feature activation through the API. The Privacy feature provides a shared address ability to enable or disable other shared addresses to barge into a call.

CallSelect and UnSelect Even Notification—Provides events for applications when they monitor RemoteInUse terminals. Applications cannot invoke an API on the Passive or InUse TerminalConnection.

Dynamic CTIPort Registration Per Call—Enables applications to provide an ipAddress and port number for each call or whenever media gets established.

Media Termination at Route Point—Enables applications to terminate media for all active calls by specifying an ipAddress and port number for each call or whenever media gets established.

Redirect Set Original Called ID—Provides applications the ability to specify preferred original called party DN apart from the destination party information in the redirect request.

Single Step Transfer—Provided applications with the following enhancements:

A new call does not get created.

CiscoTransferStartEv and CiscoTransferEndEv do not get delivered to applications.

The state of the original call gets retained if the transfer operation fails.

Auto Update of API—Provides a facility by which an application at startup can identify itself to a web server via an HTTP request and receives a response with the version of the required JTAPI API. The application compares the version available on the server to the local version in the application classpath and determines whether an upgrade is necessary.

CiscoTerminal Filter and ButtonPressedEvents—Enables applications to receive the CiscoTermButtonPressedEv when a digit gets pressed on the phone.

Modifying Calling Number—Enables applications to modify the calling party in the select route API from a route point.

AutoAccept support for CTIPort and RoutePoint—Provides applications the ability to enable or disable AutoAccept for the addresses on the CTIPort and RoutePoint. When changes occur to AutoAccept on the address, the application receives CiscoAddrAutoAcceptStatusChangedEv on AddressObservers.

CiscoTermRegistrationFailed event—Provides the applications with an event when CiscoMediaTerminal or CiscoRouteTerminal registration asynchronously fails.

SelectRoute Interface Enhancement—Enhances the SelectRoute interface to take the parameters "PreferedOriginalCalledNumber" and "PreferedOriginalCalledOption," which enables applications to reset the OriginalCalled value to a specified "PreferedOriginalCalledNumber" when the call gets routed.

Presentation Indicator (PI) for the Call—Provides applications with the ability to hide or reveal Calling/Called/CurrentCalling/CurrentCalled/LastRedirecting parties name and number to the end user.

Cisco JTAPI Installation Guide for Cisco CallManager 4.0(1)

Auto Install for Upgrades provides a facility by which an application at startup can identify itself to a Cisco CallManager web server via an HTTP request and receive a response with the version of the required JTAPI API. The application compares the version that is available on the server to the local version in the application classpath and determines whether an upgrade is necessary.

The application makes changes in the init process to instantiate an updater API to discover the server-installed component and download the component as needed.

The feature allows applications to refresh the jtapi.jar component to match the Cisco CallManager, and also a way to centrally deploy the jtapi.jar to which applications can auto update.

Packaging for the API that is required to perform this functionality comes in the form of an updater.jar. jtapi.jar, and updater.jar are packaged with a standard manifest that can be used to compare versions. A application does not have to resort to instantiating a Version class because this could make the API write protected from an update.

This feature, when specified with the location and component, downloads jtapi.jar from server and copies it to local directory. The application can either copy downloaded jtapi.jar with its copy by overwriting it or change the classpath to access the new jtapi.jar.


Note Auto Install does not update JTAPI preferences, TAPITestTools, updater.jar, and javadoc components. If applications require these components, install JTAPI from the Cisco CallManager plugin pages.


Cisco TAPI Developer and Installation Guides for Cisco CallManager 4.0(1)

The following list describes the CiscoTSP 4.0 enhancements for Cisco CallManager 4.0:

Dynamic Port Registration—The Dynamic Port Registration feature allows applications to specify the IP address and UDP port number on a call-by-call basis.

Media Termination at Route Point—The Media Termination at Route Point feature allows applications to terminate media at route points. This feature enables applications to pass the IP address and port number where they want the call at the route point to have media establish.

The system supports the following features at route points:

Answer

Multiple active calls

Redirect

Hold

UnHold

Blind transfer

DTMF digits

Tones

Redirect Support for Blind Transfer—The Redirect support for blind transfer eliminates problems that arise from the consult call that is created during a blind transfer in the earlier CiscoTSPs and also bring it in accordance with TAPI specification. This means that the system now properly supports lineBlindTransfer().

Redirect Set Original Called ID—The Redirect Set Original Called ID allows applications to redirect a call on a line to another destination while allowing the applications to set the OriginalCalledID to any value. This request can be used to implement the Transfer to Voice Mail feature (TxToVM).

Multiple Calls per Line Appearance

Maximum Number of Calls—In Cisco CallManager 4.0, the maximum number of calls per LA has changed to be database configurable. This means that the CiscoTSP has been enhanced to support more than 2 calls per line on MCD (Multiple Call Display) devices. For non-MCD devices, the CiscoTSP will only support a maximum of 2 calls per line. The absolute maximum number of calls per line appearance specifies 200.

Busy Trigger—You cannot modify the busy trigger setting by using the CiscoTSP; no changes occur in the TAPI interface that is exposed by the CiscoTSP as a result of this feature, but it will have an effect on applications that use the existing call waiting flag per DN.

CFNA Timer—The Call Forward No Answer (CFNA) timer changes in Cisco CallManager 4.0 to be database configurable, per DN, per cluster. You cannot configure this timer by using the CiscoTSP, so no changes occur to the CiscoTSP to support this feature, but this change will have an effect on applications that use the CFNA feature of Cisco CallManager.

Shared Line Appearance—The enhanced CiscoTSP in Release 4.0 supports Shared Line Appearances. The CiscoTSP does not support shared lines on CTI Route Point devices.

Select Calls—A new softkey, Select, on the IP phones allows a user to select call instances to perform feature activation, such as transfer or conference, on those calls. The CiscoTSP does not support the ability to select calls. The CiscoTSP supports the events that are caused by a user selecting a call on a line that is being monitored by the application. When a call on a line is selected, all other lines that share the same line appearance will see the call state change to dwCallState=CONNECTED and dwCallStateMode=INACTIVE.

Transfer Changes—The CiscoTSP has removed the lineDevSpecific() - Swap Hold Setup Transfer function. The lineDevSpecific() - Swap Hold Setup Transfer function performs the functionality that is described in behavior #2 and as mentioned is not needed any more because of the addition of the Direct Transfer feature.

Direct Transfer—The addition of the Direct Transfer feature makes the CiscoTSP function lineDevSpecific() - Swap Hold Setup Transfer obsolete. A TAPI application can invoke the Direct Transfer feature by using the TAPI lineCompleteTransfer() function on two calls that are already in the established state. This also means that the two calls do not have to be initially set up by using the lineSetupTransfer() function.

Conference Changes—In Cisco CallManager 4.0, the Conference softkey changed, so it always initiates a new consultation call. The Conference softkey can no longer be used to perform "Arbitrary Conference" because that is not necessary any more with the addition of the Join feature.

Call Join—In Cisco CallManager 4.0, the CiscoTSP exposed the Join feature as a new device-specific function, which will be known as lineDevSpecific() - Join. You can perform this function on two or more calls that are already in the established state. This also means that the two calls do not have to be initially set up by using the lineSetupConference() or linePrepareAddToConference() functions.

Privacy Release—In Cisco CallManager 4.0, the CiscoTSP was not enhanced to support the Privacy Release feature.

Barge and cBarge—In Cisco CallManager 4.0, changes in the CallManager allow the TSP to support the events that are caused by the Barge feature. Also in Cisco CallManager 4.0, Cisco CallManager implemented a new feature, cBarge, which always uses the shared conference resource in the Cisco CallManager, also known as a conference bridge, as opposed to the builtin bridge on the phone. In Cisco CallManager 4.0, the TSP does not support an API to invoke either the Barge feature or the cBarge feature. The TSP was only modified to support the events that are caused by the invocation of the Barge and cBarge features.

TSP Auto Update Functionality—CiscoTSP supports auto update functionality, so the latest plugin can be downloaded and installed on a client machine. The new plugin will be QBE compatible with the connected CTIManager. When Cisco CallManager is upgraded to a higher version, and CiscoTSP auto update functionality is enabled, user will receive the latest compatible CiscoTSP, which will work with the upgraded Cisco CallManager. Do not update CiscoTSP by using Auto Update functionality.

QoS Support—CiscoTSP 4.0 supports the Cisco baseline for quality of service. No change occurs in the TAPI interface to support QoS.

Forwarding Changes—A slight change takes place in behavior in CiscoTSP 4.0 in forwarding. In CiscoTSP 4.0 and Cisco CallManager 4.0, the calls that come into the line no longer get forwarded to a voice messaging system.

Presentation Indication Flag—In Cisco CallManager 4.0, the CiscoTSP enhancement supports this feature. If calls are made via Translation patterns with the all the flags set to Restricted, the CallerID/Name, ConnectedID/Name and RedirectionID/Name get sent to applications as Blank. The LINECALLPARTYID flags will also be set to Blocked if both the Name and Party number are set to Restricted.

Modified CiscoTSP 4.0 Entities—Several Cisco TAPI device structures, functions, and messages that have been modified in this version enhance overall functionality. This table lists each modified entity and its type.

Entity
Type

LINE_CALLSTATE

TAPI Line Message

LINEADDRESSCAPS

TAPI Line Device Structure

LINECALLSTATUS

TAPI Line Device Structure

lineAddToConference

TAPI Line Function

lineCompleteTransfer

TAPI Line Function

lineDevSpecific

TAPI Line Function


Changes From CiscoTSP 3.3 to CiscoTSP 4.0

Line In Service or Out of Service—If the device is out of service, the application should wait for an in-service message before initiating a TAPI request that results in Cisco CallManager interaction. If an application initiates such a request while the device is out of service, CiscoTSP responds with a resource unavailable message.

This represents a change from the behavior in CiscoTSP 3.0. In CiscoTSP 3.0, when a device successfully opened, it was always in-service.

LINE_CALLINFO—This release added complete support for the fields of the LINE_CALLINFO message in CiscoTSP 3.1. The LINE_CALLINFO parameter dwCalledID correctly reflects the OriginalCalledParty information.

User Deletion from Directory—In CiscoTSP 3.3, when the TSP user is removed, the TSP now closes all lines and phones and sends LINE_CLOSE/PHONE_CLOSE messages. After doing this, the TSP removes all lines and phones and sends LINE_REMOVE/PHONE_REMOVE messages.

Removal of lineDevSpecific() - Swap Hold Setup Transfer—In CiscoTSP 4.0, the lineDevSpecific() - Swap Hold Setup Transfer function was removed because of the changes made to the Transfer feature in the Cisco CallManager and because of the addition of the Direct Transfer feature.

Call Reason Enhancements—In CiscoTSP 4.0, the TSP properly supports call reasons as defined in the TAPI specification.

Changes to phoneSetDisplay()—In Cisco CallManager 4.0, the message that is sent to the phone in the phoneSetDisplay() API will remain on the phone until the phone is rebooted. To clear the text from the display and see the Cisco CallManager messages again, pass a NULL string, not spaces, in the phoneSetDisplay() API. In other words, ensure that the lpsDisplay parameter is NULL and the dwSize is set to 0.

Important Notes

The following section contains important information that may have been unavailable upon the initial release of documentation for Cisco CallManager Release 4.0(1).

CSCso79248 Do Not Run installxml.vbs in Unified CM Release 3.3 and Later

Uninstall CDR Analysis and Reporting Plugin Before Upgrading to Cisco CallManager 4.0(1)

Locale Installer for Cisco CallManager

Using TAPS to Configure Shared-line Phones

Survivable Remote Site Telephony (SRST) Support

Uninstalling Backup and Restore (BARS) Version 4.0(1)

CSCso79248 Do Not Run installxml.vbs in Unified CM Release 3.3 and Later

In previous releases, during the Unified CM installation, the installxml.vbs VB script got used to parse all the display instances and rules in the XML files, and upload the data into a table in the default database. In Unified CM Release 3.3 and later, the DBInstall.dll function CInstallXML performs the parsing of the XML files.

The troubleshooting guide for Cisco Unified CallManager (and Cisco CallManager) suggests that you can initialize the installxml.vbs script to fix problems with blank parameters after an upgrade. Do not initialize the installxml.vbs script as the troubleshooting guide recommends. Initializing the script erases all service parameters on the server.


Caution Cisco Unified CM releases 3.3.x or later do not use the installxml.vbs script. Running this script erases all Service Parameters in the server.

Uninstall CDR Analysis and Reporting Plugin Before Upgrading to Cisco CallManager 4.0(1)

If you have installed CDR Analysis and Reporting (CAR) plugin on a Cisco CallManger 3.3(4) system, you must perform the following pre-upgrade and post-upgrade tasks when you upgrade to Cisco CallManager 4.0(1) or risk corrupting your CAR database. Refer to Upgrading Cisco CallManager Release 4.0(1) for complete information.

Procedure


Step 1 Uninstall CAR. Be sure to save the CAR database. Click No when you are prompted to remove the ART database.

Step 2 Upgrade to Cisco CallManager Release 4.0(1).

Step 3 Install Cisco CallManager Service Release 4.0(1) or later.

Step 4 Install CAR from the Plugins.


If you upgrade to Cisco CallManager 4.0(1)and you did not follow the recommended steps , see http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed29872 for more information on how to recover your CAR database.

Locale Installer for Cisco CallManager

You can obtain locale specific versions of the Cisco IP Telephony Network Locale installer for Cisco CallManager 4.0 when they become available at

http://www.cisco.com/kobayashi/sw-center/telephony/callmgr/locale-installer.shtml.

Refer to the readme file that is posted next to the Cisco IP Telephony Locale Installer software for the complete list of supported languages and localized features.

Using TAPS to Configure Shared-line Phones

If you are planning to use TAPS to configure shared-line phones, you must create unique external mask for each shared-line phone. Enter a unique combination of numbers and asterisks (*) for the external mask. For more information, see http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec20093.

Survivable Remote Site Telephony (SRST) Support

Cisco CallManager 4.01 using Cisco SRST 3.0 does not support the Cisco IP Phone model 7970G. All other Cisco IP Phones are supported in SRST mode.

New Cisco CallManager 4.01 phone features, such as multiple calls per DN, join, direct transfer, immediate divert to voicemail, are not supported in SRST mode.

Uninstalling Backup and Restore (BARS) Version 4.0(1)

If you have installed Cisco IP Telephony Applications Backup and Restore System (BARS) Version 4.0(1), Cisco recommends that you upgrade to BARS version 4.0(2). If you have installed BARS version 4.0(1), do not uninstall this utility without first upgrading to BARS version 4.0(2). Uninstalling BARS 4.0(1) without first upgrading to BARS version 4.0(2) or later may result in users and applications losing access permission to certain files and directories. You can download the latest version of BARS from Cisco.com at http://cisco.com/cgi-bin/tablebuild.pl/cmva-3des.

Adding Cisco CallManager Servers

In Cisco CallManager Administration, make sure that you only add each server once on the Server Configuration window (System > Server). If you add a server using the host name and add the same server using the IP address, Cisco CallManager cannot accurately determine component versions for the server after a Cisco CallManager upgrade. If you have two entries in Cisco CallManager Administration for the same server, delete one of the entries before you upgrade.

Softkey Support for Cisco IP Phone Models 7905 and 7912

Cisco CallManager 4.0(1) allows the administrator to configure the Standard User and Standard Feature softkey templates on the Cisco IP Phone Model 7905 and model 7912; however, these phones do not support all of the Cisco CallManager features available on the softkey templates; for example, Barge. Consult the phone documentation that came with the phone for information about the specific features these model phones support.

Resolved Caveats for Cisco CallManager - Release 4.0(1)

Table 3 lists and describes caveats that were resolved in Cisco CallManager Release 4.0(1).


Tip If you have an account with Cisco.com (Cisco Connection Online), you can use the Bug Toolkit to find caveats of any severity for any release.

To access the Bug Toolkit, log on to http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl.


Table 3 Resolved Caveats for Cisco CallManager Release 4.0(1) 

Identifier
Summary

CSCdu59769

The SDL log for CTI Manager does not display all necessary trace information.

CSCdv66773

Cisco CallManager should pass more than 24 digits to digit analysis.

CSCdv73552

An invalid directory number (DN) request causes the tapisrv process to stop.

CSCdw08994

Cisco Telephony Service Provider (TSP) does not send event messages on the completion of a consult call.

CSCdw57219

After receiving an LINEERR_OPERATIONFAILED error, TAPI fails when there is a load on the system.

CSCdx02003

The information for Redirecting/RedirectionID for a a caller does not get sent when a call is forwarded.

CSCdx29132

E1-PRI TS014 layer 3 does not reject a PROGRESS message.

CSCdx63645

The user gets an error when the user selects the cancel prompt during the initial installation on the Backup and Restore utility.

CSCdx92507

Users receive an HTTP error when they connect to Cisco CallManager User for the first time.

CSCdy30248

The Call Forward No Answer (CFNA) parameter cannot be used to signal a voice-messaging failure when advanced linear hunting is used.

CSCdy73288

Call Dependent Call Control (CDCC) process has a memory leak, and the bandwidth for locations does not get returned.

CSCdz04480

Updates to the Music on Hold (MOH) server do not occur until you reset the server.

CSCdz05726

Conference controller does not go to an idle state when a conference call is released.

CSCdz18500

RedirectingID/RedirectionID for a caller does not get sent when a call is forwarded with FwdNoAnswer.

CSCdz22424

Cisco Messaging Interface Service Parameters have incorrect definition.

CSCdz22676

The CONFERENCED call state remains when a fourth party is added and the calls are dropped.

CSCdz24796

Cisco CallManager does not set a default codec when you add a region in Cisco CallManager Administration.

CSCdz25060

Cisco CallManager only redirects calls for the first nine pickup groups.

CSCdz26529

Cisco CallManager installation does not display a warning when you install over an older version.

CSCdz41461

It takes 8 seconds to park a call on hold.

CSCdz56346

The quality report tool (QRT) on the phone does not include the source directory number (DN) and device type.

CSCdz61912

Cisco CallManager Administration displays an error message when you view modifications in Auto-Generated Device Profile Line.

CSCdz69981

Intercluster trunk (ICT) call park reversion from NetMeeting to a IP phone in a G.729 region fails.

CSCdz72286

The Voice Mail Port wizard throws a COM error when you enter a long pilot DN.

CSCdz81567

Cisco CallManager database restoration fails when subscriber servers are connected.

CSCdz81791

Calls forwarded to registered device fail with ssExtendCallErr.ErrorCode= 14.

CSCdz82894

Links in the service parameter window do not work when there are invalid values in the required fields.

CSCdz82973

RouteFilter configuration window accepts duplicate clauses.

CSCea00342

The voice-mail profile name field in Voice Mail Profile Configuration accepts invalid characters.

CSCea01730

Cisco CallManager displays a CDBLException Dump message when an administrator deletes a partition that is in use by a call park/call pickup/meetme number.

CSCea02305

The backup and restore utility does not support 11 servers in a cluster.

CSCea03795

The names and descriptions for IP Phone Service Parameters on the Cisco CallManager User window do not display Russian characters.

CSCea04708

Cisco CallManager displays an error message when you conduct an empty search for DCD users while an administrator is adding users with the Bulk Administration Tool.

CSCea04828

The number of stored procedures increases after the database is restoredwith backup and restore utility, version 3.5(6).

CSCea05931

Cisco CallManager forwarded a call to the wrong phone in a call pickup scenario.

CSCea11716

Cisco CallManager did not respond immediately to a clear message waiting indicator (MWI) message.

CSCea11987

Administrators cannot uninstall a standalone version of the backup and restore utility.

CSCea13557

The Music on Hold (MOH) server displays the incorrect number of resources when a Cisco CallManager cluster is rebooted.

CSCea13972

Calls get rejected when over 200 registered agents exist.

CSCea14510

DC directory replication fails on the subscriber server when you upgrade a system with a large database.

CSCea18597

The phones do not display updates to the date/time group.

CSCea24820

DeviceListX request fails when more than 20,000 devices exist.

CSCea27607

Remote Registry service in Cisco CallManager Serviceability has a memory leak.

CSCea35002

The incorrect MOH audio source plays when a call is transferred.

CSCea41890

A database error occurs when you attempt to obtain directory number information on a Cisco IP Conference Station 7935 line.

CSCea44652

Java Telephony Application Programming Interface (JTAPI) has a missing calling connection.

CSCea45346

WS-6608-E1 does not support mu-law pulse code modulation (PCM).

CSCea49571

Administrators can select an uninstalled network locale for a WS-6608 gateway by using Cisco CallManager Administration.

CSCea52745

Software Conference Bridge does not release the transmission stream when a phone is unplugged from the network.

CSCea52901

Access rights for splkRASReader and splkRASUser got swapped when the database was restored.

CSCea53538

Cisco CallManager displays an error message when you conduct a search of the subscriber global directory after adding a new user to the DC directory database.

CSCea55522

The art_log.ldf transaction log increases to 1 GB in size.

CSCea59247

Intercluster call does not get removed when park reversion fails.

CSCea59673

JTAPI does not send a CallCtlConnEstablished event for an unmonitored device after a blind transfer.

CSCea65097

Users get an error when they attempt to add fast dials to a subscriber server in a cluster.

CSCea76103

JTAPI has a memory leak when an application registers to receive park events and attaches a park observer to the provider.

CSCea79698

Perfmon does not display the Network Interface process parameter.

CSCea80926

Enabling the always use primary line parameter does not always work.

CSCea82254

Cisco CallManager Administration displays a DBLE exception when a server is deleted.

CSCea86172

Cisco CallManager Administration displays an empty error window when an administrator attempts to delete a server with an empty host name/IP address field.

CSCea86784

Performance monitor does not display locations that are added to a cluster until the Cisco CallManager server is restarted.

CSCea87355

Cisco CallManager Administration displays an error message when locations and CTI route points are added.

CSCea88402

IP phone displays the wrong error message.

CSCea88612

Cisco CallManager Administration displays incorrect dependencies in the media resource group list.

CSCea88944

You cannot use the underscore ( _ ) character in a query string in the route plan report page.

CSCea89916

The subscriber journal file can increase in size to over 1 GB.

CSCea90465

Using an "is empty" query on a translation pattern does not work.

CSCea91334

Searching on the softkey template description does not work.

CSCea92986

The audio translator does not work if the files are in a remote directory.

CSCeb00216

Administrators cannot set clusterwide service parameters to a default value by clicking on the set to default button.

CSCeb00463

Some queries in the route plan report return incorrect results.

CSCeb02342

CDR Analysis and Reporting (CAR) Quality of Service (QoS) intermittently reports that data was not available for internal IP phone to IP phone calls.

CSCeb04068

You cannot use SQL wildcard characters and bracketed expressions in a region search query.

CSCeb05737

Cisco IP Manager Assistant service log displays user password in clear text.

CSCeb09099

Cisco CallManager does not update the object identifiers (OID) for labeledURI during the upgrade process.

CSCeb10484

Find/List Regions has a different behavior than other Cisco CallManager Administration windows when the Delete All parameter is selected.

CSCeb11140

You cannot add a MOH audio file with a single quote in the file name.

CSCeb13814

Cisco CallManager service restarts when an H.323 trunk is reset.

CSCeb15742

Cisco CallManager does not update conference bridge resources properly.

CSCeb21240

Cisco CallManager Administration does not highlight the pilot point field in the error page when you attempt to insert a pilot point without entering a pilot point number.

CSCeb22406

Phone does not display the call-forwarded number in an intercluster trunk (ICT) call.

CSCeb23668

Cisco CallManager trace file reports an error on basic intercluster trunk calls.

CSCeb23944

Installation does not delete the temporary files when you upgrade Cisco CallManager.

CSCeb24227

Cisco CallManager Administration does not inform administrators that they need to reset or restart a device after an the Device Status Poll Interval service parameter has been updated.

CSCeb24635

JTAPI sends an incorrect callCtl_Cause code in the CallCtlConnAlertingEv message.

CSCeb25014

Cisco CallManager Administration allows you to use an invalid character in the description field in server configuration.

CSCeb27289

Cisco IP Phone Execute command fails to authenticate and execute with the proper credentials.

CSCeb27723

Cisco CallManager Serviceability treats the % character as a wildcard when you conduct a search in Q931 translator.

CSCeb27730

Users get an Javascript error when they enter a quote in the User Defined Text field.

CSCeb27869

TSP locks up after completing a call with the Microsoft Outlook auto-dial feature.

CSCeb29036

The Call Detail Records (CDR) for Adhoc conference(TP,TP,NET Meeting) has incorrect values.

CSCeb29083

The aupair services have a memory leak and high CPU usage when 200 phones auto-register.

CSCeb30328

Cisco IPMA wizard stops when two entries exist for the same host—one entry has the hostname, and the other entry has the IP address.

CSCeb30414

Cisco CallManager does not use ISO global ID in QSIG calling name.

CSCeb30508

Call Throttling fails on an H.225 intercluster trunk.

CSCeb30537

Event Viewer on Cisco CallManager displays a large number of transient connections for the Cisco IP Phone model 30 VIP.

CSCeb31088

Administrators get an application error message at the end of an installation on a publisher server.

CSCeb31499

Cisco CallManager Administration does not prompt you to restart a device when you update the default date time group settings.

CSCeb31503

Cisco CallManager Administration does not prompt you to restart a device when you update the media resources in a media resource group.

CSCeb31505

Cisco CallManager Administration does not prompt users to restart a device when you update the media resource group for a device.

CSCeb31562

Cisco CallManager sends an incorrect Redirecting Information Element identification for forwarded calls.

CSCeb31601

Changes to H.323 service parameter do not take effect until Cisco CallManager service is restarted.

CSCeb31829

JTAPI does not send a ConnDisconnectedEv message to a caller when a call is redirected.

CSCeb31852

JTAPI sends two ConnCreratedEv messages.

CSCeb32323

Cisco CallManager Administration does not display Russian characters correctly.

CSCeb32712

Cisco  CallManager does not validate the server name in the syslog; syslog traces display the incorrect server name in the trace.

CSCeb32714

Cisco  CallManager does not validate the host name that is entered in the update plugin URL field.

CSCeb32718

User gets an error message when a % character is entered in the Cisco IPMA Manager window.

CSCeb32728

CDR Analysis and Reporting (CAR) does not display the QoS detail report correctly when special characters exist in the user ID field.

CSCeb32736

Users return to the same window when they click on the directory number (DN) on the dependency record link in the CTI route point window.

CSCeb32856

Cisco CallManager Administration displays a Javascript error when you attempt to add a non-gatekeeper controlled intercluster trunk by using an invalid server name.

CSCeb32915

CAR does not accept input that starts with a decimal point in the multiplication factor field.

CSCeb32923

Links in the Cisco IP Auto Attendant (AA) user preference window do not work when the name dialing value has a space.

CSCeb33435

You cannot complete a conference call when the other party transfers the call.

CSCeb34125

The Set Limits for Notification window does not display in Netscape Navigator when you click on the back button after receiving an error message.

CSCeb34131

CAR displays an error message when you enter a n multiplication factor of 999.999.

CSCeb34742

Cisco CallManager Administration allows you to delete a music on hold server that a media resource group is using.

CSCeb34782

Cisco CallManager Administration does not display a warning message when you delete a conference bridge that is part of the media resource group.

CSCeb35479

Cisco CallManager Administration displays an error message when you attempt to retrieve information for a phone button template with an invalid label.

CSCeb35496

Cisco CallManager displays an error message when you enter an invalid name in the phone button template window.

CSCeb35547

Cisco CallManager displays an error message when you enter a single quote in the description field while searching for a media termination point (MTP).

CSCeb35575

Cisco CallManager returns an incorrect description when you enter a space in the description field while searching for a MTP.

CSCeb35591

Cisco CallManager Administration does not allow you to use the slash (\) character in the search by description field.

CSCeb36091

Cisco IPMA Assistant Console does not display the Save and Cancel button for some non-English languages.

CSCeb36220

Some DC Directory default keys do not get enabled after Cisco CallManager is upgraded.

CSCeb36432

Call was aborted when an agent conferenced a caller from a gateway to a route point.

CSCeb36706

A deleted Media Resource group appears in the Find and List window when the group has a dependent record.

CSCeb36949

Deleting a user fails when the user ID field contains special characters.

CSCeb37008

Users get an exception error when they delete a transcoder that is a part of the Media Resource Group.

CSCeb37599

Music on Hold server does not receive a registration ack message from the Cisco CallManager server.

CSCeb38185

You cannot update a directory number when you use a backslash in the display field.

CSCeb38251

Cisco CallManager Administration displays an undefined error when you use the double quote character in the gatekeeper configuration description field.

CSCeb38778

Cisco CallManager does not use the value in the Offhook to First Digit Timer field on a WS-6624 gateway.

CSCeb39111

Users in a conference call experience bad audio quality for a few seconds.

CSCeb39291

Cisco CallManager Administration allows you to delete a hardware conference bridge when it is part of a media resource group.

CSCeb39294

Cisco CallManager Administration allows you to delete a Media Termination Point (MTP) when it is a part of a media resource group

CSCeb39684

The backup and restore utility attempts to find installxml.ini files in a Cisco CallManager subscriber server, 3.2 version.

CSCeb40490

Cisco CallManager sends an incorrect response to a 510 error message from a Media Gateway Control Protocol (MGCP) gateway.

CSCeb40808

Cisco CallManager Serviceability displays the same results for gateways whether you enable or disable the search by trace field.

CSCeb41467

The export utility displays the previous Media Access Control (MAC) address when a user has no device association

CSCeb41912

Cisco CallManager Administration displays an error message at the end of the Route Plan wizard when an administrator is using the Japanese locale.

CSCeb42012

Cisco CallManager Administration displays a misleading error message when you add a gateway without selecting a gateway type.

CSCeb42129

The upgrade assistant reports a domain check failure as an informational message.

CSCeb42197

CAR displays an incorrect key for the traffic summary report bar graph when the On Net box is not checked.

CSCeb42451

Cisco Agent Desktop (CAD) loses call control when a call is transferred to a extension that has Call Forward No Answer (CFNA) to voice-messaging enabled.

CSCeb43164

Entries in the CiCcp table do not get deleted during a redirect loop.

CSCeb43189

Cisco CallManager Administration displays a Javascript error in Trace Configuration when Cisco CTI Manager Service is stopped.

CSCeb43209

Cisco CallManager has high CPU usage when 3000 CTI users exist and a user attempts to open the CTI Enabled Users Report window.

CSCeb43285

Cisco CallManager reports incorrect values on park reversion calls in the Call Detail Record (CDR).

CSCeb44185

Administrators cannot run the backup utility by clicking on the backup utility link on the first CD.

CSCeb44465

You cannot disable a device level trace after reducing the trace parameter value.

CSCeb44608

The readme file in ServPrep has spelling errors.

CSCeb44800

Cisco CallManager Administration loads slowly when a large number of calling search space exists.

CSCeb45432

Calls to phantom directory numbers that are forwarded to voice mesaging fail.

CSCeb45857

Cisco CallManager Administration does not display an alert message when you use special characters.

CSCeb45871

Netscape Navigator does not clear the search criteria from the previous search in User Preferences.

CSCeb45905

Cisco CallManager Administration does not display the first window of Device Association when you choose the link for it.

CSCeb47016

Netscape Navigator does not display the dependency records for route partition or automated alternate routing (AAR) groups when the route partition name contains a space.

CSCeb47032

Cisco CallManager Administration allows you to enter IP addresses.

CSCeb47066

Administrators get a Javascript error on Microsoft Internet Explorer when they add a pilot point without selecting a device pool.

CSCeb47114

Cisco CallManager Administration displays an error message when you enter a quote in the description field while adding a new voice-mail pilot number.

CSCeb47300

Cisco CallManager Administration fails to update associated lines when you update a device profile.

CSCeb47393

The CTIManager service stops when a route point has 256 lines.

CSCeb48454

Callback fails in a multiple callback scenario.

CSCeb49606

You cannot select the language locale in the Add/Delete Assistant window when an assistant has not been added.

CSCeb50803

Cisco CallManager incorrectly shows that a phone is available for a callback.

CSCeb51155

Cisco CallManager displays a nondescriptive error message when a user adds an already existing entry to the personal address book

CSCeb51456

Administrators get an error when they integrate a Cisco CallManager server with a newly installed Netscape Directory server.

CSCeb52339

Cisco CallManager server displays a confusing message when you are replacing a server.

CSCeb52723

Cisco CallManager server upgrade failed when you upgrade a system that is using Microsoft Active Directory or Netscape Directory.

CSCeb53318

Cisco CallManager does not check for valid characters in the host name/IP Address field in the gatekeeper configuration window.

CSCeb53374

You cannot increase the maximum number of hops for a multicast Music on Hold (MMOH) server beyond 15.

CSCeb53739

The phoneSetLamp and phoneGetLamp requests do not work on Cisco IP Phones.

CSCeb53947

Cisco CallManager Release 3.3 installation fails if you cancelled a previous installation.

CSCeb54081

IP phone continues to ring when you choose callback.

CSCeb54623

Cisco CallManager trace files display errors for unassigned lines on a Cisco IP Phone Expansion Module 7914.

CSCeb54721

Filter active appears in English after you initiate a search on a device profile.

CSCeb55405

Installation of a Cisco Customer Directory Configuration Plugin fails when the directory administrator password contains special characters.

CSCeb55686

The updateServiceParameter request in AVVID XML Layer (AXL) fails to find some service parameters.

CSCeb56524

Cisco CallManager installation displays an error message that states that it cannot find the existing Administrative Reporting Tool (ART) database version.

CSCeb56832

The information in Cisco CallManager management information base (MIB) is not in order.

CSCeb57026

The callback key does not display when overlapping route patterns exist.

CSCeb57154

Cisco CallManager does not send the Idle state to Cisco Attendant Console at the end of a call.

CSCeb58054

When Cisco CallManager server has overlap sending enabled, IP phone does not play the fast busy signal when a call disconnects.

CSCeb59183

Cisco CallManager Administration displays a prompt for resetting devices when administrators insert new Media Resource List.

CSCeb59294

IP phone does not display the dialed number after it receives a progress message.

CSCeb59743

Cisco CallManager subscriber servers have high CPU usage when a CTI route loop with Personal Assistant exist.

CSCeb60440

Directory installation fails when the directory administrator password contains special characters.

CSCeb60593

Cisco CallManager server continues to route calls to a Primary Rate Interface (PRI) after the interface goes out of service.

CSCeb63007

Callback to managers phone in Cisco IPMA does not work when a route point is defined as [xxx]xxx.

CSCeb63020

DC directory configuration fails when the administrator password has special character.

CSCeb63096

CDR Analysis and Reporting (CAR) does not display all users in a report.

CSCeb63529

System users did not get created after Cisco CallManager is upgraded.

CSCeb65001

Incoming calls through Cisco Catalyst 6608 Primary Rate Interface (PRI) do not get cleared when the caller ends the call.

CSCeb65481

Call Detail Record (CDR) does not display the cause code for the last party dropped from a conference call.

CSCeb66123

Active Directory (AD) plugin installation displays Schema Update Failed error message.

CSCeb67247

The CPU usage spikes when you select the dependency records for a region.

CSCeb67383

The configuration window in Cisco CallManager Administration displays 10 regions at a time.

CSCeb70825

Users get an error when they select a service parameter after changing the locale region setting to German.

CSCeb72114

The H.225 dual tone multifrequency (DTMF) duration default value should be changed to 100 ms.

CSCeb72452

Cisco IPMA assistant console displays the incorrect line setting for an extension mobility manager.

CSCeb72469

The line status of an extension mobility manager does not get updated on the assistant console when the manager logs out and then logs back in.

CSCeb75951

The backup and restore utility does not restore the correct user permission in the CAR database.

CSCeb76286

Cisco CallManager does not use signaling port 1719 for gatekeeping Reliability, Availability, and Serviceability (RAS) messages.

CSCeb76332

Cisco VG200FXS VM port failure causes call forward failure.

CSCeb76809

Cisco IP SoftPhone does not have the hold, transfer, and conference button after a parked conference call is retrieved.

CSCeb78325

The main window on Cisco CallManager Administration displays when you click the Back to Find/List CTI route points.

CSCeb78357

You get a HTTP 500 error when you select the Close and Go Back button from the Dependency Record window after the pilot point is deleted.

CSCeb78362

You get an error when you click on the Close and Go Back button from the Dependency Record window after the IP phone service is deleted.

CSCeb78365

Cisco CallManager Administration returns an empty record when you search for a device by using the description begins with option.

CSCeb78496

Administrators get a remote script COM error when they attempt to update a deleted call park number.

CSCeb78498

Administrators get a remote script COM error when they attempt to update a deleted call park number.

CSCeb78500

Cisco CallManager Administration lists deleted meet me numbers and patterns in the results from the Find and List search.

CSCeb78807

IP phone stops ringing when an incoming call occurs on the second line after you have resumed a call on the first line.

CSCeb80508

Calls go idle, and Cisco TAPI service provider (TSP) does not report the idle CallState because CTI does not handle the cause code that is reported in the LmKeyReleaseReq message.

CSCeb80969

Cisco IP Phone 7910 displays all 10 digit instead of the extension number.

CSCeb81074

Cisco CallManager Administration does not update pilot point information for a user.

CSCeb81140

The automated alternate routing (AAR) enabled service parameter should be listed under Cisco CallManager service parameter and not an enterprise service parameter.

CSCeb82274

Route Filter Configuration stops working when you attempt to delete a route filter that has already been deleted.

CSCeb82323

The Cisco IP Phone Services Configuration window stops working when you attempt to add service parameter information to an IP Phone service that has already been deleted.

CSCeb82330

Administrator gets an HTTP 500 error message when you attempt to change the character set for an IP phone service that has already been deleted.

CSCeb82398

The arrow buttons to reorder the Media Resource Groups within the Media Resource Group List does not display.

CSCeb82415

Cisco CallManager installations create a WAUSERS share directory.

CSCeb82431

Cisco CallManager installations create UsersDB1.mdb and UsersDB2.mdb files.

CSCeb82701

Cisco CallManager server sends redirect request messages as a low priority message.

CSCeb83527

Cisco CallManager trace files display ConnectionManager - ERROR deleteMediaInfoEntry(0): ENTRY NOT FOUND message for a simple transfer call.

CSCeb85021

You cannot use wildcards to search for phones in Cisco CallManager Administration.

CSCeb86240

The quality report tool (QRT) uses commas as data and as a delimiter in the Comma-Separated Values (CSV) report.

CSCeb87424

Call gets stuck in Cisco Telephony Service Provider (TSP).

CSCec00019

Cisco CallManager trunk may unregister unexpectedly with a gatekeeper.

CSCec00266

Dependency records displays common results for voice mail pilot numbers that do not have a description.

CSCec00420

CDRs do not get inserted after upgrade to Cisco CallManager Release 3.3(3) occurs.

CSCec00591

Cisco CallManager administration displays both submodules of VWIC-1MFT-T1 with slot/port = 3/0 in the user defines gateway module NM-HD-2VE.

CSCec00892

The Call Pickup Group dropdown menu does not display any available Pickup Groups when you add a shared-line extension to an IP phone.

CSCec01526

Administrators do not get a message to restart the WS-X6624-FXS port after the prefix directory number (DN) has been updated.

CSCec02756

The jvm.stderr and jvm.stdout files increase without bound and cannot be deleted.

CSCec04947

Cisco VG 248 VGC port 0 incorrectly registers as a virtual phone type 11.

CSCec05189

Cisco CallManager fails to obtain a heart beat when the traces cannot be written.

CSCec06462

Calling party number transformation does not get saved correctly and gets overwritten by the calling name update.

CSCec07174

CAR does not get installed when a third-party tool, such as Prognosis, locks the database.

CSCec11536

Cisco CallManager process has high CPU usage during a MeetMe software conference bridge when a conference participant streams a high rate of DTMF.

CSCec11642

Call back service has high CPU usage.

CSCec15529

Cisco CallManager process stops when two conflicting route patterns exist within the same partition.

CSCec16419

Cisco CallManager sends a release complete message to WS-6608 MGCP gateway when it receives the setup message.

CSCec16771

Cisco CallManager registers multiple intercluster trunks with a gatekeeper.

CSCec17454

Cisco CallManager Database Layer (DBL) trace indicates queries for a deleted gateway exist.

CSCec17485

Cisco CallManager Administrator displays "%20" in the Device Pool name field when the name contains a space.

CSCec18647

Cisco CallManager server does not respond with the national ISDN specification to an invalid call proceed message.

CSCec19224

The conference controller fails to conference a call after the consult call is unparked.

CSCec19444

Upgrade to Cisco CallManager Release 3.3(3) fails when the Cisco CallManager Administrator password is blank.

CSCec19813

Application event viewer displays a GetNewFileName-fopen(ffileNumberfile)=NULL,error=0x error message.

CSCec20373

The help text for the Change B-Channel Maintenance Status service parameter needs to be updated.

CSCec20441

Application event viewer displays Cisco IPMA error messages when Cisco IPMA is deactivated.

CSCec20693

User receives extra DTMF tones (startTone 50) when a call is placed from an agent who is using a third-party Integrated Contact Distribution (ICD) application.

CSCec21681

Application event logs displays errors that the Alarm Interface is not initialized.

CSCec22860

Calls from IP phone to public switched telephone network (PSTN) disconnects after 5 to 10 minutes.

CSCec23324

Failed Cisco CallManager upgrades do not have helpful error message.

CSCec25245

The jvm.stderr file increases without bound and cannot be deleted.

CSCec25500

Cisco Customer Response Solution (CRS) resource window does not display resource names.

CSCec25549

Call Management Records (CMR) file gets corrupted and cannot be inserted into the CDR database.

CSCec26136

The message waiting indicator (MWI) lamp stops working properly when the phone is unplugged from the network and the phone gets a MWI update message.

CSCec26168

The real-time information server (RIS) data collector periodically restarts.

CSCec26776

IP phone displays registration rejection message when you reset the phones.

CSCec29576

Cisco TAPI service provider (TSP) allows a GetDisplay to succeed in a Cisco IP Conference Station 7935.

CSCec31716

Administrators get a lblmaErrorCreatingManagerObject error message when a manager is configured for Cisco IPMA.

CSCec32565

CTI Manager process stopped in the directory thread.

CSCec32889

CTI Manager process stopped in the directory thread when the connection to the LDAP server timed out.

CSCec33004

Cisco CallManager Administration displays an error message when you query by using a single quote character in the Find list Route Pattern window.

CSCec33156

Cisco Security Agent displays error message to terminate Extension Mobility program.

CSCec33755

Call setup fails when Cisco CallManager receives a progress indicator message on a Q.SIG call.

CSCec34492

Cisco CallManager Administration does not correctly handle the at character (@) that is used in email addresses when it sends out URLs.

CSCec37576

The backup and restore utility does not migrate all locale CSV files.

CSCec40884

LineOpen () returns an error message.

CSCec40936

Cisco CallManager Administration user configuration does not work when the French locale is selected.

CSCec41220

Call transfer fails when Cisco IP Interactive Voice Response (IVR) transfers a call to Cisco Customer Response Solution (CRS).

CSCec41691

Cisco CallManager does not have a definition for a Cisco VG224 gateway.

CSCec42868

Calls fail on Cisco CallManager controlled Media Gateway Control Protocol (MGCP) gateways when mismatched endpoint state results exist.

CSCec43710

Cisco IPMA configuration wizard failed to create IP phone services and populate Cisco IP Manager Assistant service parameters.

CSCec43718

Data gets lost when you enter data for a new DN before selecting the character set.

CSCec45097

Cisco CallManager Administration takes up to 2 minutes to display a route pattern.

CSCec45179

DC Directory stopped.

CSCec45754

Updating route lists fail when a large number of route lists exist.

CSCec46110

The Find/List Pilot Point query displays incorrect pilot point number when the pilot number has 10 or more digits.

CSCec46310

CPU usage goes to 100 percent when you load the device default page.

CSCec46577

The administrators need to click on the reset button twice on phone configuration.

CSCec48050

Cisco CallManager responds to the primary gatekeeper when an IRQ message is received from an alternate gatekeeper.

CSCec48931

Cisco CallManager Administration takes up to 5 minutes to display the dependency record for a route list.

CSCec50080

Application Event viewer did not display a warning message that Cisco CallManager services restarted.

CSCec52954

Cisco CallManager server unregisters with a gatekeeper when a registration request (RRQ) is lost.

CSCec54062

Cisco CallManager Administration and Cisco CallManager User windows have inconsistent user password behavior.

CSCec54439

The CCMAdministrator cannot log in after Cisco CallManager is upgraded from Release 3.3(2) when Multilevel administration Access (MLA) is installed.

CSCec55234

Route Pattern page does not display when a configured Cisco VG 200 gateway exists.

CSCec63052

Calls to a device on the WS-6624 gateway fail after the directory number has been changed.

CSCec64242

Cisco CallManager service terminates unexpectedly.

CSCec65850

The real-time monitoring tool displays the wrong conference bridge model.

CSCec66461

The email output for a CDR search does not display all CDR fields.

CSCec66820

Cisco CallManager Administration returns zero records when you search for CTI route points with an empty calling search space field.

CSCec68362

Cisco CallManager service restarted during a phone registration.

CSCec69371

The Do Not Disturb setting on a phone gets reset when a device initiates callback.

CSCec69693

Upgrade assistant fails on backup validation when it encounters a catalog file of 0 bytes.

CSCec70373

Callback failed on an extension mobility shared-line phone.

CSCec72451

Cisco CallManager service restarts when a large number of route list exists.

CSCec75146

Call lingers in JTAPI after call is dropped.

CSCec76154

Cisco CallManager does not receive some call events when Internal Caller ID is set to a value in Cisco CallManager Administration.

CSCec79510

CTI manager traces do not display the quick buffer encoding (QBE) messages for both directions.

CSCec82337

Cisco CallManager Administration displays an Object does not support this action error message when you submit a change on the subscriber server while the publisher server is offline.

CSCec84986

Cisco CallManager Administration does not display the gateways in the dependency record of the automated alternate routing (AAR) group.

CSCec86576

TFTP does not generate all the configuration files for a device when the device configuration is greater than 2 MB.

CSCed09650

Cisco CallManager sets the MaxCdrRecords service parameter to a value of 1 when you upgrade from Cisco CallManager Release 3.3(3) to 4.0(1).

CSCed16054

There is no documentation that describes how to set up a trusted ODBC.

CSCed33171

Media Resource Group List (MRGL) updates in Device Pool do not work.

CSCin44653

Device name field in H.323 gateway configuration window accepts incomplete IP addresses.

CSCin45681

Cisco IP SoftPhone cannot rejoin a conference call after transferring a call to a parked number.

CSCin46237

You cannot remove the last caller with the RmLstC button if the caller is using Cisco IP SoftPhone.

CSCin49357

Cisco CallManager has high CPU usage when 200 Channel Associated Signaling (CAS) ports are configured and they are in descending order.

CSCin52362

The dependency records of voice mail pilot number display unusual entries when the pilot number does not have a description.

CSCin52563

Cisco CallManager Administration fails when you change Cisco VG248 48_PORTS to None.

CSCin53396

Cisco CallManager Administration appends spaces to the product-specific parameters in T1-CAS Configuration.

CSCin53582

The RmLstC softkey removes the incorrect participant in a conference call.

CSCin55039

You cannot use Microsoft Internet Explorer Version 5.00.3502.1000 to add a partition to a calling search space.

CSCin55131

Cisco CallManager Administration does not trim preceding blank spaces in a route filter name.

CSCin56550

You cannot use Microsoft Internet Explorer Version 5 to add calling search space with the Cisco IPMA configuration wizard.

CSCin57059

The event viewer displays many File Update failed Alarm messages when trace configuration is enabled to detailed database tracing.

CSCin57353

You get an error when you delete a music on hold server that is a part of a media resource group.

CSCuk45312

You cannot add QSIG gateways with intercluster trunks to route groups or route lists.

CSCuk45931

You cannot do a blink transfer on a PSTN call to another PSTN over a MGCP gateway.

CSCuk46135

Phone receives a busy tone instead of the reorder tone when a call is made to a H.323 gateway that is busy.

CSCuk46223

Call fails when Cisco CallManager sends an overlap message to a backhauled PRI link with an invalid Number Plan Indicator (NPI).

CSCuk46251

Cisco IPMA assistants do not get updated when the assistant has more than 9 lines configured.

The following firmware caveats apply to this release.

CSCdw79582

The idle URL on the phone does not get cleared when an incoming call occurs.

CSCdy25368

The help text for the i button and ? button for Cisco IP Phone models 7960 or 7940 has inaccurate description.

CSCdz12384

Cisco IP Phone 7910 reboots and cannot register with the Cisco CallManager server.

CSCdz25635

IP Phone Services respond to the NetworkConfigurationX request with the <ProxyServerURL> and <AuthenticationURL> elements in reversed order.

CSCdz53716

You cannot configure the Cisco IP Phones not to send StationTimeDateReq at 00:00, 10:00, and 20:00.

CSCdz64808

The Ring Type menu shows other DN on the phone when you change the ring type from the default.

CSCdz65109

Phone does not ring on some lines after the ring type is changed.

CSCdz71206

Multiline phone displays an empty line for a conference call.

CSCdz84679

The display on the Cisco IP Phone Expansion Module 7914 becomes unreadable after the network locale is changed.

CSCdz85700

Phone line icon gets distorted, and phone displays missed calls message after 65535 CFNAs between two phones.

CSCea09124

The phone does not encode query string in the locale character set.

CSCea10351

The LED on a Cisco IP Phone Expansion Module 7914 do not get cleared when the phone is deleted from the database.

CSCea10942

IP phone displays only characters 1-24 and 26-30 in the results from a Corporate Directory Search.

CSCea20258

Message button on Cisco IP Phone with disabled speaker initiates call to voice messaging system.

CSCea20376

Phone does not play the mute on and mute off tones when the mute is activated and deactivated.

CSCea28342

User experiences 2-4 seconds delay on a call from the PSTN when Message Transport Protocol (MTP) is not in use.

CSCea32745

Cisco IP Phone 7960 receives packet glitch that affects TTY performance.

CSCea35126

Phone displays incorrect directory menu after you press the i button.

CSCea57305

Cisco IP Phone Expansion Module 7914 does not receive the line information for the last line when two expansion modules are attached to a Cisco IP Phone 7960.

CSCea73013

User receives echo or feedback when two phones use a multicast service and both phones receive and transmit simultaneously.

CSCea79644

The phone on an auxiliary VLAN cycles through configuring IP when the link is toggled.

CSCea81159

The exit softkey takes the user to the root of directory tree.

CSCeb09560

The PC port on Cisco IP Phone 7960 has packet losses.

CSCeb10185

Phone restarts when multiple incoming Multilevel Precedence and Preemption (MLPP) calls exist.

CSCeb11801

Cisco IP Phone resets and gets stuck in the "registering" cycle when it receives partial data while the connection is closed.

CSCeb19725

Intermittent one-way/no-way audio may occur for the first 10 seconds of a call when TCP packets are received out of order during the call setup.

CSCeb27021

User needs to submit two XML messages to the Cisco IP Phone.

CSCeb40626

Cisco IP phone does not display the comma symbol correctly in the Chinese locale.

CSCeb60327

Cisco IP Phone cannot make calls when a 24-digit directory number (DN) is assigned to the second line.

CSCeb64628

WS-6608-T1 does not support superframe (SF) and alternate mark inversion (AMI) framing.

CSCeb69539

Phone reboots when no entries exist in the directory and you press the dial softkey.

CSCec31746

Existing extension mobility and Cisco IPMA users cannot use fast dials or the personal address book services.

CSCec78423

Cisco IP Phone 7960 resets when a user chooses the dial softkey after receiving blank results from a corporate directory query.

CSCuk39530

Cisco IP Phone does not display Idle URL objects or HTTP push responses.


Open Caveats for Cisco CallManager - Release 4.0(1)

Table 4 describes possible unexpected behaviors by Cisco CallManager Release 4.0(1). Unless otherwise noted, these caveats apply to all Cisco CallManager 3.0 releases up to and including Cisco CallManager Release 4.0(1).


Tip If you have an account with Cisco.com (Cisco Connection Online), you can use the Bug Toolkit to find caveats of any severity for any release. To access the Bug Toolkit, log on to http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl.


Table 4 Open Caveats for Cisco CallManager Release 4.0(1) 

Identifier

Headline

CSCdr53384

Minor memory leak (svchost/tapisrv) occurs when a TAPI application stops.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCdr53384

CSCds07952

LineAccept fails when a call is already in connected state.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCds07952

CSCds09562

Cisco CallManager does not have an error code to distinguish between invalid and out-of-service extension.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCds09562

CSCds50763

Spurious NewCall gets created when you redirect a resumed call.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCds50763

CSCdu34874

The number does not display on an associated IP phone when you use Cisco Softphone to dial a number.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCdu34874

CSCdx64502

The audio connection gets delayed when Cisco CallManager server waits for an acknowledgement message from a MGCP gateway.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCdx64502

CSCdy86076

Users need to restart the TSP client after logging off and logging back in on Cisco Extension Mobility.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCdy86076

CSCdy87034

Cisco TAPI Service Provider (TSP) has a memory leak in some consult transfer scenario.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCdy87034

CSCdy88595

The gateway configuration file does not get updated when the endpoint is deleted.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCdy88595

CSCdz72286

The Voice Mail Port wizard throws a COM error when you enter a long pilot DN.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCdz72286

CSCea03826

The second ringback call state event does not get sent when a call gets redirected after connecting to an external number across a gateway.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCea03826

CSCea05766

Cisco IP Phone 7912 does not support callback.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCea05766

CSCea34211

Incoming call does not automatically get answered when you place the current call on hold.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCea34211

CSCea50515

You cannot disconnect a call on hold through a CTI application.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCea50515

CSCea51241

The online help for Attendant Console does not correctly display in Hungarian.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCea51241

CSCea73575

The event viewer displays failed audit reports for CCMService user.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCea73575

CSCea85505

Calls to a domain name system (DNS) server-based trunking fail.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCea85505

CSCeb05663

Line status stops working after you transfer a call from a shared-line phone to the same shared-line phone.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeb05663

CSCeb34496

Cisco CallManager Administration allows you to delete a transcoder that a media resource group is using.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeb34496

CSCeb39815

After upgrading Cisco CallManager, the Remember last Userid feature only works the first time that it is used.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeb39815

CSCeb40762

JTAPI disables Cisco Customer Response Solution traces along with all other traces.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeb40762

CSCeb48689

The Cisco Communication Media Module (CMM) displayed an unregistered gateway as being registered with Cisco CallManager.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeb48689

CSCeb55563

You cannot add a user to a user group if the user ID contains a slash character (/).

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeb55563

CSCeb57003

Cisco CallManager User Options does not display updated speed-dial entries.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeb57003

CSCeb58036

Phone displays an incorrect message when you edit a personal address book (PAB) entry.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeb58036

CSCeb58068

Users get an error when adding a PAB on the Cisco CallManager User window.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeb58068

CSCeb59038

BAT Excel template mixes up line and speed-dial information.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeb59038

CSCeb60407

ICT call does not get cleared when the transcoder is reset.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeb60407

CSCeb62212

Cisco IP Phone models 12SP and 30VIP cannot start an ad hoc conference by using the speakerphone.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeb62212

CSCeb62769

Cisco IP Phone does not display a DN when the number contains a wild card character.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeb62769

CSCeb63018

You get duplicate entries in the address book because the nickname format is inconsistent.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeb63018

CSCeb66170

The IOS Conference Bridge name field only allows 15 characters.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeb66170

CSCeb67397

Shared-line phone can have more calls than the number for which it is configured.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeb67397

CSCeb68038

Cisco CallManager assigned a DN that is out of the auto registration range to a phone that was deleted from the database.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeb68038

CSCeb68131

Call on hold gets dropped when you try to resume the call after another phone barged in to the call.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeb68131

CSCeb69927

Extension mobility phones do not have call history.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeb69927

CSCeb71190

Call fails because a SCCP device does not consider location in the bandwidth computation.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeb71190

CSCeb71221

Call fails because a H.323 device does not consider location in the bandwidth computation.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeb71221

CSCeb71231

Call fails because a SIP device does not consider location in the bandwidth computation.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeb71231

CSCeb71965

Phone displays incorrect text for missed and placed calls.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeb71965

CSCeb74440

Phone gets disconnected with a normal cause code but does not play the reorder tone.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeb74440

CSCeb75996

You cannot restart Microsoft Internet Information Services (IIS) on a Cisco CallManager server.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeb75996

CSCeb76250

Administrators receive an error message when they delete a large number of locations from the external route plan wizard.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeb76250

CSCeb83429

Backup and Restore (BARS) does not get properly installed on a Microsoft Windows 2003 server.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeb83429

CSCeb85104

JTAPI returns null for a calling terminal when a shared-line device makes a call.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeb85104

CSCec04720

You cannot configure a Cisco VG 248 gateway with unassigned DN on port 2 through port 48.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec04720

CSCec05284

Event viewer displays a JavaPerfMon error.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec05284

CSCec06088

CDR Analysis and Reporting (CAR) does not align the menu in the PDF report for the Norwegian locale.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec06088

CSCec07003

Cisco CallManager Administration lists user access rights in the user menu.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec07003

CSCec11376

Cisco Real-Time Information Server (RIS) fails to collect Perfmon data from the remote node if the node temporarily loses connection.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec11376

CSCec18269

JTAPI does not send a ConnConnectedEv message when a call is redirected through a gateway.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec18269

CSCec21799

DC Directory attempts to bind to a renamed Cisco CallManager server.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec21799

CSCec23192

Corresponding perfmon counters do not get reset when you reset the devices in a hunt list.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec23192

CSCec23359

Call information does not get updated when a barged call is dropped.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec23359

CSCec23671

The Simple Network Management Protocol (SNMP) CCMTable has an extra null entry.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec23671

CSCec24295

Administrators get a HTTP Error 500-12 Application Restarting message when they access Cisco CallManager Administration with Multilevel Administration Access (MLA) installed.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec24295

CSCec25422

Cisco CDR insert process failed to start.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec25422

CSCec28915

Users get a run-time error when they access Cisco CallManager Administration help file.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=

CSCec32053

Language locale setup stops when you choose a locale with missing Tool for Auto-Registered Phones Support (TAPS) file.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec32053

CSCec39201

CTL client does not recognize when different eTokens are inserted.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec39201

CSCec39276

You cannot use a voice-mail port that has call forward all and call forward busy that are configured to a route point.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec39276

CSCec46604

User gets a "IsRes.dll file could not be removed. Access is Denied" error message.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec46604

CSCec47867

Cisco CallManager sends an incorrect termconn state when you unpark a barge call.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec47867

CSCec51393

A call park number does not display in the pop-up message when the number contains special characters.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec51393

CSCec51987

Notification does not get sent when you change the builtin bridge service parameter.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec51987

CSCec52677

Cisco CallManager Administration allows you to add an orphan directory number to the hunt list of a Cisco CallManager Attendant Console.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec52677

CSCec53844

Cisco CallManager server does not correctly handle a reset device message if it is received within 5 seconds of a default change notification message from the device.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec53844

CSCec53872

TAPI passes call information when the presentation indication (PI) is set to restricted.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec53872

CSCec57585

The signal distribution layer (SDL) traces generate even when you disable trace configuration.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec57585

CSCec57609

Cisco CallManager service stops when the database has over 24,000 phones.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec57609

CSCec57714

Cisco CallManager sends an incorrect last redirected address.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec57714

CSCec60220

Cisco CallManager installation does not check for forward and reverse name resolution at the beginning of the installation.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec60220

CSCec61469

Users do not receive the video signals from a third-party video endpoint when they are on a call to another third-party video endpoint.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec61469

CSCec61667

Microsoft windows 2000 advance servers do not support CTL client.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec61667

CSCec62297

Updates to a route group take 10 - 11 minutes to complete.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec62297

CSCec63322

Phone configuration changes do not take effect until the Trivial File Transfer Protocol (TFTP) service is restarted.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec63322

CSCec64547

Cisco CallManager Administration changes the number of items that it displays per page to 10 when you click on the page link in Region Configurations.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec64547

CSCec65305

Phone does not display the correct assistant status on a manager phone when the assistant is in a conference call.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec65305

CSCec65830

The online help for WS-6624 FXS gateway device configuration does not exist.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec65830

CSCec66251

When Cisco Multilevel Administration Access (MLA) is enabled, a user with read-only access can update trace configuration.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec66251

CSCec66820

Cisco CallManager Administration always returns zero records when you search for a CTI route point with a Calling Search Space is empty search parameter.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec66820

CSCec66867

Cisco CallManager Administration displays an ODBC error when you search for gateways with a Calling Search Space is not empty parameter.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec66867

CSCec66964

Cisco CallManager Administration displays end points when you search for gateways with calling search spaces parameter and the hide endpoint option.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec66964

CSCec67279

When MLA is enabled, the "List Files" buttons are disabled for user who has read-only right in serviceability.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec67279

CSCec67323

Cisco IP Phones 7940 and 7960 incorrectly display the call forwarded icon.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec67323

CSCec68278

IP phone does not download updated phone load configuration until TFTP service is restarted.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec68278

CSCec68721

New trace settings in Serviceability Trace Configuration for CTL Provider do not take effect until the CTL provider service is restarted.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec68721

CSCec69160

Cisco CallManager Administration displays a CDBLException error when users choose the propagate icon for line text display.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec69160

CSCec69222

Cisco CallManager sends the wrong call information when the calling party parks a call.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec69222

CSCec69371

Cisco IPMA phone with do not disturb enabled rings when the phone receives a callback signal.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec69371

CSCec69497

Cisco CallManager does not handle MGCP 400 errors correctly.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec69497

CSCec70462

Cisco CallManager Administration should have an enterprise level parameter for configuring phone web access.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec70462

CSCec70975

Calls from a TAPI application fail when Cisco CallManager server has busy hour call attempts (BHCA) of 15,000.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec70975

CSCec71628

The idivert feature does not work as expected when a call exists on a line that has Call Forward Busy (CFB) or Call Forward No Answer (CFNA) enabled and the voice-messaging system is down.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec71628

CSCec71905

Cisco IPMA assistant console displays an error when an assistant logs in to the assistant console.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec71905

CSCec72451

Cisco CallManager service restarts when a large number of route lists, devices, and route patterns exist.

http:/ /www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec72451

CSCec73828

TAPI does not respond immediately to either the LINE_REPLY or the LINE_ADDRESSSTATE event on lineForward request.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec73828

CSCec75237

LineChangeEventFilterRequest does not fail when a line is closed.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec75237

CSCec75273

LineClosedEvent does not get sent to application when user logs in by using extension mobility.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec75273

CSCec77271

Cisco CallManager does not purge old hunt list data in the Real-Time Information Server (RIS).

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec77271

CSCec76306

A video endpoint that is sharing a line with an audio endpoint does not receive the video portion of the phone call.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec76306

CSCec78290

Voice-mail ports display call forwarding information.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec78290

CSCec80041

The previous installation of the Upgrade Assistant utility still gets deleted when you select cancel while upgrading the Upgrade Assistant utility.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec80041

CSCec80231

User gets a Self Registration error message when Upgrade Assistant is deleted.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec80231

CSCec80242

TSP receives incorrect call state events when a lineDrop request occurs less than 500 msec after a lineCompleteTransfer with LINETRANSFERMODE_CONFERENCE request.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec80242

CSCec80292

DCD validation failed on a Cisco CallManager subscriber server, Release 3.3(2), when you use upgrade assistant.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec80292

CSCec81512

The Cisco CallManager Trace Configuration Page for SDL and SDI traces has incorrect information on the size of trace log files.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec81512

CSCec81913

NewCallAcceptTimer does not stop when a call is redirected in the offering state.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec81913

CSCec82019

The route filter clause does not display properly in the dialed number analyzer (DNA).

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec82019

CSCec82021

Translation pattern CSS does not get configured in DNA.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec82021

CSCec82145

The online help for Cisco CallManager has misleading information on the Code Yellow Exit Latency Calculation service parameter.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec82145

CSCec82154

The online help for Cisco CallManager does not clearly define the maximum events allowed service parameter.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec82154

CSCec82312

Cisco CallManager has the wrong callCtlCause code when a cBarge call is parked.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec82312

CSCec82372

Cisco CallManager does not send a connection event when a cBarge call is unparked.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec82372

CSCec82793

Cisco CallManager Administration displays endpoints when you choose the hide endpoint option in a search for gateways.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec82793

CSCec82981

TSP does not set a timeout of 0 in the DeviceDisplayString message.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec82981

CSCec83813

Cisco CallManager has incorrectDestPrecedenceLevel value in a call pickup scenario.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec83813

CSCec85371

Callback fails when translation pattern drops digits.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec85371

CSCec85514

User with no access rights to Real-Time Monitoring Tool (RTMT) can log in to RTMT.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec85514

CSCec85629

Cisco CallManager Administration does not provide codec selections other than G711u and G711a in Session Initiation Protocol (SIP) trunk configuration.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec85629

CSCec86798

The addOnModule in AVVID XML Layer (AXL) accepts phoneTemplate type.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec86798

CSCec87055

RTMT cannot monitor the directory service on a node that does not have Cisco CallManager services enabled.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec87055

CSCec87398

You cannot delete a Call Pickup Group number by using the AVVID XML Layer (AXL) removeCallPickupGroup request method.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec87398

CSCec88319

Some devices do not have Multilevel Precedence and Preemption (MLPP) Domain configuration options.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec88319

CSCec88531

Call instance does not get released when a CiscoVG200 gateway is used for a shared DN.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec88531

CSCec89280

You cannot configure a shared line for a line group member on Cisco IP Softphone.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec89280

CSCec89321

You cannot use MLPP to preempt a call on a SIP trunk.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec89321

CSCec89831

Deleting a RouteList by using AXL fails when the route list does not contain a route group or a line group.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec89831

CSCec90003

Duplicate deviceUnRegisteredEvent messages get sent when an application closes a device.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec90003

CSCed00699

User gets an error message when they create a hunt list with a Route group that is followed by a line group.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed00699

CSCed00948

The dialog boxes for some warning messages do not pop to the top of a user screen.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed00948

CSCed01028

Cisco IPMA service stops responding when you repeatedly stop and restart the service.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed01028

CSCed01306

The real-time information server data collector (RISDC) on a subscriber server cannot be reached when the Cisco CallManager and CTI service are deactivated.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed01306

CSCed01740

CmiPerfmon.dll causes thread deadlock.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed01740

CSCed01755

MediaAppPerfMon.dll causes thread deadlock.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed01755

CSCed02974

Music on hold does not stop after a call on H.323 gateway is resumed.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed02974

CSCed03303

Administrators cannot add a line group to a route list after a Q.SIG gateway is deleted.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed03303

CSCed04678

Cisco CallManager does not send the RedirectingID-Name on a blind transfer call from a shared-line phone.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed04678

CSCed05265

Cisco CallManager Administration displays a CDBLException Dump message when a Calling Search Space (CSS) is deleted.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed05265

CSCed05307

The manager phone displays the wrong number for an assistant call.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed05307

CSCed05329

CPU usages spikes on the publisher server when you enable department billing and the user hierarchy in directory is not set up properly.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed05329

CSCed05621

A call does not get routed to the second available phone when the first phone is busy.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed05621

CSCed05797

Cisco CallManager has the incorrect forwarding information in lineGetAddressStatus message when you remove call forwarding.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed05797

CSCed06085

Cisco CallManager does not stop the Cisco Tomcat Service gracefully.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed06085

CSCed06318

Administrators cannot delete a Cisco CallManager group even when the group has no dependent records.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed06318

CSCed06632

Cisco CallManager Administration does not allow you to configure the calculateAverageExpectedDelay option in trace settings.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed06632

CSCed06664

The MOH server does not use available streams for non-default codecs.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed06664

CSCed06815

Login fails for Cisco CallManager Administration, Cisco CallManager User Option, and Cisco CallManager Service due to a memory leak in LDAP connection.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed06815

CSCed06910

A call remains active after it is disconnected.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed06910

CSCed07230

JTAPI sends an incorrect callCtl_cause code when a shared-line device redirects a barged call.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed07230

CSCed07330

Cisco CallManager cannot update international dial plans that have route or translation patterns.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed07330

CSCed09363

The differentiated services code point (DSCP) parameter only controls the marking of signalling packets of Cisco IP Phone models 7940 and7960.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed09363

CSCed09497

Caller ID does not get blocked on blind transferred calls when the destination has Translation Pattern with All Restricted parameter enabled in the progress indicator (PI).

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed09497

CSCed09808

TSP does not support dwNumEntries=NULL in lineForward().

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed09808

CSCed12260

Server recovery fails when groups do not get added before a backup is started.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed12260

CSCed12826

Cisco IPMA fails when a CTI route point does not start.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed12826

CSCed13415

Cisco Security Agent prevents SQL agent from creating a SQL log on a Cisco ICS server.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed13415

CSCed14072

Administrators receives an error message in bold letters when the administrator deletes a route filter from the configuration window.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed14072

CSCed14348

Cisco CallManager does not respond to a LineCallInitiate request when the handle is absent.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed14348

CSCed14408

Users may not receive the video signal when they resume a video call on hold.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed14408

CSCed14650

DC directory fails during the backup and restore process.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed14650

CSCed14717

User with no access to real time monitoring tool can still access the login screen.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed14717

CSCed14818

Empty route list gets created when administrators copy the route or hunt list.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed14818

CSCed14895

User preference page does not change locale.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed14895

CSCed14917

IP phone displays the wrong time when users select the Brussels, Paris, Madrid timezone.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed14917

CSCed14934

Cisco CallManager documentation does not inform the administrator that the number of available CSS that are listed in a drop down box is configurable.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed14934

CSCed14969

Cisco CallManager documentation does not inform the administrator that the number of partitions that are listed in the drop-down box is configurable.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed14969

CSCed14981

Cisco CallManager documentation has inconsistent information on string length for different fields.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed14981

CSCed16137

CTL client does not work properly on Microsoft Windows XP.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed16137

CSCed16182

Web dialer displays page in English when other locales are selected.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed16182

CSCed16298

The online help description for Extension Mobility Log Out Time field is incorrect.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed16298

CSCed16350

Cisco CallManager Administration documentation describes a field that no longer exists in Translation Pattern Configuration.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed16350

CSCed16706

Intercluster Trunk calls to an MGCP gateway fail.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed16706

CSCed18284

Phones do not work when Cisco CallManager fails over

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed18284

CSCed18761

Single route group with gateways in different orders becomes multiple route groups when you migrate the database.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed18761

CSCed19335

Cisco CallManager slows down the delivery of events to a directory number as calls accumulate on a route point.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed19335

CSCed19620

Music-on-hold servers has performance degradation in Cisco CallManager Release 4.0.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed19620

CSCed19775

Cisco CallManager does not release hardware conference port resources.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed19775

CSCed19892

Cisco CallManager does not send a H.225 information message for a blind transfer call.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed19892

CSCed20527

Annunciator does not get allocated because Unicast Bridge is not assigned annunciator resources.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed20527

CSCed20295

Digital gateways do not send SMDI message when SMDI base port number is set to zero in digital trunk and a call arrives on the digital trunk.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed20295

CSCed21487

Application cannot cancel call forward in one call scenario.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed21487

CSCed21526

JTAPI does not send CallCtlAddFWDEv message when an application cancels call forward.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed21526

CSCed21675

Cisco CallManager Serviceability adds a "CM" prefix to the IP address of the Cisco CallManager server when you restart Cisco CallManager and CTI Manager services.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed21675

CSCed22052

Users gets exception error when they update the protocol of an existing T1 PRI gateway with AXL.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed22052

CSCed22524

The CTL client displays a misleading message when a connection is queued.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed22524

CSCed23028

Cisco CallManager sends an incorrect reason code when a transformation mask is used in a route point.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed23028

CSCed23112

The subscriber server does not display data when the publisher server goes down.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed23112

CSCed23683

Restore log displays a number of errors.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed23683

CSCed23864

The Certificate Trust List (CTL) utility allows the CTL file to be signed with the new etoken.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed23864

CSCed24195

TSP does not set the dwCallerAddressSize and dwCallerAddressOffset fields to 0 in the LINEFORWARD structure contained in LINEADDRESSSTATUS.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed24195

CSCed24235

H323-VideoCallsActive nd H323-VideoCallsCompleted counters can be inaccurate.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed24235

CSCed24405

LINEFORWARD structure in LINEADDRESSSTATUS does not get cleared when FwdAll is turned off.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed24405

CSCed24881

A monitoring system reported that the Voice Media Streaming Application and MOH Audio Translator stopped.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed24881

CSCed25111

CDR record still displays the owner userID for a device when the userID is deleted.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed25111

CSCed25306

Phone registration takes over 2 minutes when phones fail over from SRST to Cisco CallManager.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed25306

CSCed25430

Cisco IP Authentication and Encryption for Cisco CallManager 4.0(1) documentation does not state that the Certificate Authority Proxy Function (CAPF) Utility supports third-party RSA Keon Certificate Authority.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed25430

CSCed25508

Change notification does not get sent to Cisco CallManager server when a shared line is deleted.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed25508

CSCed25556

The CAPF utility supports the RSA Keon Certificate Authority.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed25556

CSCed25707

Cisco IP Phone 7905 played a reorder tone in a call scenario.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed25707

CSCed26547

Cisco CallManager Features and Services Guide has an incorrect default of 20,000 for synchronous request timeout; the default is 15,000.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed26547

CSCed26570

The minimum and maximum value was swapped on overlapping MLA privilege parameters.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed26570

CSCed27328

Inserting a record in BAT fails when the file name contains a comma.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed27328

CSCed27619

IP phone did not receive privacy updates.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed27619

CSCed28145

The eToken service does not get installed when you reboot a computer while installing the CTL client.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed28145

CSCed28356

JTAPI failed to connect to the CTI manager when CTI Service was restarted.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed28356

CSCed28757

Built-in bridge parameter does not get migrated after upgrading to Cisco CallManager, release 4.0.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed28757

CSCed29023

Database replication failed on a publisher server when MLA is configured.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed29023

CSCed29239

New Operating System installations, OS version 2000.2.4, designates drive E as the default trace drive on the MCS-7845H-3.06 servers.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed29239

CSCed29548

Preferences display the previously selected locale when a user select the Chinese Taiwan locale on Cisco WebDialer.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed29548

CSCed30174

Cisco CallManager does not reset or audit a trunk when it receives a setup message from a gateway.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed30174

CSCed31292

Wave drivers do not release the buffers.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed31292

CSCed32570

Administrators cannot apply troubleshooting trace settings twice.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed32570

CSCed32615

Music-on-hold server does not send multicast music to a conference bridge.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed32615

CSCed32700

A video call from a Tandberg Video Terminal to a plain old telephone service (POTS) phone fails to connect.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed32700

CSCed33281

AXL API failed to update the Cisco CallManager service parameters.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed33281

CSCed33473

You cannot use TAPS to reset a phone with an external number.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed33473

CSCed34082

Administrators get an error when they insert a H.323 client phone with an empty signal port field.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed34082

CSCed34104

You cannot use the CTL client to delete the CAPF server from CTL file.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed34104

CSCed35081

You cannot associate a H.323 phone with a user.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed35081

CSCed35589

Cisco CallManager Service Parameter IP Precedence Bitmask does not work.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed35589

CSCed38779

Cisco CallManager has a memory leak.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed38779

CSCed39551

Cisco CallManager Administration allows users to define a network module for the 4th slot of a Communication Media Module.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed39551

CSCed44223

MLA has permission problems when two users have common character strings.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed44223

CSCed44907

MLA user with full access permissions cannot query AXL and SOAP interface.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed44907

CSCed49450

CTI applications fail to open provider when user authentication is delayed.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed49450

CSCed55971

Cisco CallManager Release 4.0(1) does not support Cisco IP Communicator.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed55971

CSCin55125

Null values get inserted for parameter field in route filters.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCin55125

CSCin61590

Cisco CallManager Administration does not have a is empty and is not empty search parameter available for finding meet me numbers.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCin61590

CSCin62402

Cisco CallManager Administration always shows the MWI icon as being enabled (green) in Dependency records.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCin62402

CSCin62741

Firmware information does not display a VGC gateway that has a non-default version.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCin62741

CSCin63437

Administrators get a remote scripting error message when they enter invalid characters during the configuration of a NM-HD-2VE network module.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCin63437

CSCuk45896

Administrators cannot modify Cisco CallManager's glare properties f.or a PRI port connected to a DMS100.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCuk45896

The following firmware caveats apply to this release.

CSCeb69347

Cisco IP Phone 7910 displays a misleading message when user selects a call park number that is out of range.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeb69347

CSCeb80892

Phone displays a mixture of English and German in the personal address book when the German locale is selected.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeb80892

CSCec20794

Cisco IP Phone does not display the 200th call instance.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec20794

CSCec34487

Cisco IP Phone 7970 does not update the call forward icon when an extension mobility user logs in.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec34487

CSCec58677

IP phone displays the original called information on a call when the calling party name or calling party number is restricted.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec58677

CSCec76440

Cisco IP Phone 7910 returns a success for a phoneSetDisplay and a phoneGetDisplay request from a TAPI application, but it does not display the text.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec76440

CSCec78423

Cisco IP Phones 7940 and 7960 resets when there are no results in the corporate directory and the users presses the dial softkey.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec78423

CSCed02259

User cannot answer the ninth call on an IP Phone using a TAPI application.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed02259

CSCed02271

Phone resets after a call to a CTI port with Dynamic Registration Port setting is dropped in fast mode.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed02271

CSCed12269

Cisco IP Phone 7979 takes 1.8 seconds to display call information when the user presses the messages button.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed12269

CSCed13862

Users hear a low pop intermittently on the speaker when they answer a call using on the answer softkey.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed13862

CSCed20127

Cisco IP phone does not immediately access the screen shot image for a 303 redirect URL.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed20127

CSCed20153

Cisco IP phone displays a corrupted screen when you push an execute request object to the phone in the network configuration screen.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed20153

CSCed23335

Cisco IP Phone 7970 does not immediately display the digits when you dialed with the phone onhook.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed23335

CSCed26357

Cisco IP Phone 7960 and Cisco IP Phone 7905 have different remote in use icons.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed26357

CSCed34320

Cisco IP Phone 7970 does not work when you select a non-active audio preference setting.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed34320

CSCed34994

Cisco IP Phone 7970 does not have the correct display after Cisco CallManager restarts the phone.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed34994


Documentation Updates

This section provides documentation changes that were unavailable when the Cisco CallManager Release 4.0(1) documentation suite was released.

Errors

This section contains errors that are contained in the Cisco CallManager Documentation suite.

Installation and Upgrade Document References Incorrect Version of Backup and Restore (BARS)

The documents, Installing Cisco CallManager Release 4.0(1) and Upgrading Cisco CallManager Release 4.0(1) refer to Cisco IP Telephony Applications Backup and Restore System (BARS) Version 4.0(1). BARS Version 4.0(2) replaces BARS Version 4.0(1), so instead, you should install and configure Cisco IP (BARS) Version 4.0(2) or later.

Cisco Video Link Codec

Cisco CallManager documentation incorrectly references a Cisco Video Link codec. For Cisco Video Link codec, read wideband video codec. Any other references to Cisco Video Link are not valid.

Cisco IP Communicator

Cisco CallManager documentation incorrectly references Cisco IP Communicator. Cisco CallManager Release 4.0(1) does not support Cisco IP Communicator. For complete information, see http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed55971.

Malicious Call Identification

The Cisco CallManager Features and Services Guide identifies a PRI gateway that uses the MGCP PRI backhaul interface for T1 (NI2) as a gateway that supports MCID. Note, non-standard NI-2 PRI trunk interfaces do not support the Cisco CallManager MCID feature.

Changes

This section contains changes that have occurred since the original release of the Cisco CallManager Release 4.0 documentation. These changes do not currently appear in the current documentation or the online help for the Cisco CallManager application.

Route Pattern/Hunt Pilot Configuration

Provide outside dial tone, Allow overlap sending and Urgent priority are fields that are described in "Route Pattern/Hunt Pilot Configuration," of the Cisco CallManager Administration Guide.

Provide outside dial tone

Outside dial tone indicates that Cisco CallManager routes the calls off the local network. Check this box for each route pattern that you consider to be off-network.

Allow overlap sending

With overlap sending enabled, when Cisco CallManager passes a call to the PSTN, it relies on overlap sending in the PSTN to determine how many digits to collect and where to route the call. Check this box for each route pattern that you consider to be assigned to a gateway or route list that routes the calls to a PSTN that supports overlap sending.

Urgent priority

If the dial plan contains overlapping route patterns, Cisco CallManager would not route the call until the interdigit timer expires (even if it is possible to dial a sequence of digits to select a current match). Check this box to interrupt interdigit timing when Cisco CallManager must route a call immediately.

Troubleshooting Security

Symptom    Security Token Locks When You Consecutively Enter an Incorrect Security Token Password

Possible Cause    Each Cisco System Administrator Security Token (CSAST) contains a retry counter, which specifies the number of consecutive attempts to log in to the etoken Password window. The retry counter value for the CSAST equals 15. If the number of consecutive attempts exceeds the counter value, that is, 16 unsuccessful consecutive attempts occur, an error message indicates that the security token is locked and unusable. Corrective Action: You cannot reenable a locked CSAST. Obtain additional security token(s) and configure the Cisco CTL file, as described in Cisco IP Phone Authentication and Encryption for Cisco CallManager 4.0(1). If necessary, purchase new security token(s) to configure the file.

Omissions

This section lists new and additional information that is not included in the current Cisco CallManager documentation.

Fax and Modem Connectivity with Cisco CallManager

Cisco Unity Voice-Mail Port Changes

Static Digit Analysis

Fax and Modem Connectivity with Cisco CallManager

Cisco CallManager supports only modem pass-through technology with voice gateways.

For fax connectivity, Cisco CallManager supports SuperG3 to SuperG3 fax on gateways that provide fax pass-through mode using G.711 codecs. A SuperG3 fax call uses a V.34 modem connection. For SuperG3 to SuperG3 fax calls, no V.21 tones are acknowledged by either of the Cisco gateways. The call is answered as a modem call by using a 2100Hz answer tone plus phase reversal. Both gateways disable echo cancellation (ECAN). SuperG3 must use Error Correction Mode (ECM).

The Cisco fax relay mode supports SuperG3 to SuperG3 fax under the following conditions:

Use all G.711 codec regions to allow the SuperG3 fax call to complete as a modem-pass-through call. Be aware that this can impact bandwidth usage.

Force both of the SuperG3 fax machines to use a maximum speed of 14400 bps (G3)

Force both SuperG3 fax machines to disable ECM causing the fax machine to use 14400 bps with no ECM (G3).

For more information about configuring fax, refer to the Implementing Fax Over IP on Cisco Voice Gateways document on Cisco.com.

Cisco VG248 Analog Phone Gateway

The Cisco VG248 supports legacy fax machines and modems. When using fax machines, the Cisco VG248 uses either the Cisco fax relay or pass-through/up speed technology to transfer faxes across the network with high reliability.

You can connect any modem to the Cisco VG248 by using pass-through mode.

Cisco Catalyst 6000 24 Port FXS Analog Interface Module

The Cisco Catalyst 6000 FXS module also supports fax relay and pass-through/up speed. Fax relay enables compressed fax transmission over the IP WAN and preserves valuable WAN bandwidth for other data applications.

Cisco Unity Voice-Mail Port Changes

This section describes various voice-mail port configurations in Cisco CallManager. Use the scenarios and procedures that follow to ensure that migration from Cisco CallManager 3.3(x) to Cisco CallManager 4.0(1) properly migrates the voice-mail port settings. This section describes voice-mail port configurations in Cisco CallManager 3.3(x) as well as the expected configuration after migration to Cisco CallManager 4.0(1). This section also describes the voice-messaging system changes that take place after you upgrade your system to Cisco CallManager 4.0(1).

This section contains the following topics:

Changes After Upgrading to Cisco CallManager 4.0(1)

Before Upgrading to Cisco CallManager 4.0(1)

Unity Failover Voice-Mail Port Setup

Changes After Upgrading to Cisco CallManager 4.0(1)

You will need to reconfigure a few items to maintain your original voice-mail port functionality, depending on what type of scenario you have set up. You must also change your setup as described in this section.

Things That May Affect Your Setup

If your last voice-mail port is forwarded to a route pattern (gateway or intercluster trunk [ICT]), this configuration will no longer exist after the upgrade. You will need to add the intercluster trunk or gateway to a route group, then add the route group to the corresponding route/hunt list of the route patterns that are attached to the voice-mail pilot number. The route group represents the last member of the route/hunt list.


Note Cisco does not recommend use of the Broadcast distribution algorithm in conjunction with the implementation of voice-mail ports for Cisco Unity.


Line Group Forwarding and Cisco Unity Failover

If you are using the recommended Cisco Unity failover voice-mail port setup, you need to configure the following values for the line groups that are used for the voice-mail ports:

No Answer: Skip Remaining members and go directly to next group.

Busy: Try Next member, but do not go to next group.

Not Available: Skip Remaining members and go directly to next group.

The descriptions of the various scenarios throughout this document provide specific information about these values.

If your final voice-mail port is configured to go to an operator, and the operator is set up to Call Forward No Answer (CFNA) and Call Forward Busy (CFB) back to the voice-mail pilot, you will no longer be able to CFB or CFNA back to the same voice-messaging system. You can add an additional line group that contains the operator line to the voice-mail hunt list.

After an upgrade, the system places the line group where the failover voice-mail ports reside in the route/hunt list that is associated with the hunt list pilot number. You need to manually select the hunt options on the basis of your original configuration.

Changes That You Will Notice After the Upgrade

After the upgrade from previous versions of Cisco CallManager to Cisco CallManager 4.0(1), you will notice the following changes:

The Cisco Voice Mail Port Configuration window no longer has forwarding fields.

Voice-mail ports now use line groups, route/hunt lists, and hunt pilot numbers.The system creates these entities automatically after the upgrade if the database contained an existing voice-mail port setup. You need to select the hunt options on the basis of your original configurations.

The pilot number now represents a route pattern with the same number as the first voice-mail port, but in a different partition. The partition that is used for the pilot number was originally the partition that associated with the first voice-mail port.

The system places voice-mail ports in a newly created partition during the upgrade process.

The system places voice-mail ports that are used for MWI and for outbound calls on their own separate line groups, route/hunt lists, and hunt list pilot numbers.

Before Upgrading to Cisco CallManager 4.0(1)

Perform the following step on the voice-mail ports to ensure proper migration:

1. Important: Remove any call forwarding that is set on voice-mail ports that are used only for outbound calls and message waiting indication.

Unity Failover Voice-Mail Port Setup

Two supported failover configurations exist. The following white paper discusses these failover configurations: Cisco CallManager Port Configuration for Cisco Unity Failover (Cisco Unity Versions 4.0 and 3.1(2) and Later).

This section provides example configurations in Cisco CallManager 3.3(x) and then outlines what each configuration should resemble after an upgrade to Cisco CallManager 4.0(1) occurs. Some manual configuration needs to take place after an upgrade to Cisco CallManager version 4.0(1). This section also outlines these changes.

This section covers the following topics:

Unity Failover Configuration 1 in Cisco CallManager 3.3(x) (Recommended)

Unity Failover Configuration 1 After Migration to Cisco CallManager 4.0(1) (Recommended)

Single Cisco Unity Server with Single Cisco CallManager Cluster

Single Cisco Unity Server with Single Cisco CallManager Cluster in Cisco CallManager 3.3(x)

Single Cisco Unity Server with Single Cisco CallManager Cluster After Migration to Cisco CallManager 4.0(1)

Unity Failover Configuration 1 in Cisco CallManager 3.3(x) (Recommended)

In this example, on each server, four ports handle incoming calls, and two ports handle outbound calls and MWI. PhoneCSS contains partition(s) that are assigned to subscriber phones, as well as VMPilotNumberPT. VMRestrictedCSS contains only VMRestrictedPT, which is assigned only to VM ports.

Primary Cisco Unity server VM ports configuration:

Port 1: (Line: 2001) Device Settings - CSS = PhoneCSS
Port 1: (Line: 2001) Directory Number Settings - Partition = VMPilotNumberPT, CSS = 
VMRestrictedCSS
Ports 2 to 6: (Lines: 2002-2006) Device Settings - CSS = PhoneCSS
Ports 2 to 6: (Lines: 2002-2006) Directory Number Settings - Partition = VMRestrictedPT, 
CSS = VMRestrictedCSS
Ports 1 to 6: (Lines: 2001-2006) Call Forwarding Settings on Busy and No Answer CSS = 
VMRestrictedCSS
Line: 2001, CFNA = 3001, CFB = 2002
Line: 2002, CFNA = 3001, CFB = 2003
Line: 2003, CFNA = 3001, CFB = 2004
Line: 2004, CFNA = 3001, CFB = 2001
Line: 2005, CFNA = 2001, CFB = Blank (for outbound calls and MWI)
Line: 2006, CFNA = 2001, CFB = Blank (for outbound calls and MWI)

The following example shows secondary Cisco Unity server VM ports (call does not get sent to operator if all ports are busy or ring no answer [RNA]) configuration:

Ports 1 to 6: (Lines: 3001-3006) Device Settings - CSS = PhoneCSS
Ports 1 to 6: (Lines: 3001-3006) Directory Number Settings - Partition = VMRestrictedPT, 
CSS = VMRestrictedCSS
Ports 1 to 6: (Lines: 3001-3006) Call Forwarding Settings on Busy and No Answer CSS = 
VMRestrictedCSS
Line: 3001, CFNA = 3002, CFB = 3002
Line: 3002, CFNA = 3003, CFB = 3003
Line: 3003, CFNA = 3004, CFB = 3004
Line: 3004, CFNA = 3001, CFB = 3001
Line: 3005, CFNA = 3001, CFB = Blank (for outbound calls and MWI)
Line: 3006, CFNA = 3001, CFB = Blank (for outbound calls and MWI)

The following example shows secondary Cisco Unity server VM ports (call gets sent to operator if all ports are busy or RNA) configuration:

Ports 1 to 6: (Lines: 3001-3006) Device Settings - CSS = PhoneCSS
Ports 1 to 6: (Lines: 3001-3006) Directory Number Settings - Partition = VMRestrictedPT, 
CSS = VMRestrictedCSS
Ports 1 to 6: (Lines: 3001-3006) Call Forwarding Settings on Busy and No Answer CSS = 
VMRestrictedCSS
Line: 3001, CFNA = 3002, CFB = 3002
Line: 3002, CFNA = 3003, CFB = 3003
Line: 3003, CFNA = 3004, CFB = 3004
Line: 3004, CFNA = operator DN, CFB = operator DN
Line: 3005, CFNA = 3001, CFB = Blank  (for outbound calls and MWI)
Line: 3006, CFNA = 3001, CFB = Blank  (for outbound calls and MWI)

Unity Failover Configuration 1 After Migration to Cisco CallManager 4.0(1) (Recommended)

In this example, on each server, four ports handle incoming calls, and two ports handle outbound calls and MWI. PhoneCSS contains partition(s) that are assigned to subscriber phones, as well as VMPilotNumberPT. VMRestrictedCSS contains only VMRestrictedPT, which is assigned only to VM ports. The VMPilotPartition gets created automatically and gets assigned to the voice-mail ports.

The following example shows primary Cisco Unity server VM ports configuration:

Ports 1 to 6: (Lines: 2001-2006) Device Settings - CSS = PhoneCSS
Ports 1 to 6: (Lines: 2001-2006) Directory Number Settings - Partition = VMPilotPartition, 
CSS = VMRestrictedCSS

The following example shows secondary Cisco Unity server VM ports configuration:

Ports 1 to 6: (Lines: 3001-3006) Device Settings - CSS = PhoneCSS
Ports 1 to 6: (Lines: 3001-3006) Directory Number Settings - Partition = VMPilotPartition, 
CSS = VMRestrictedCSS

The following example shows Line Groups (calls not sent to operator if all ports are busy or RNA) configuration:

1. Line Group Name: LG2001 includes 2001-2004, with the following settings:

No Answer: Skip remaining members, and go directly to next group (Because this setting 
is not the default, you must set it manually.)
Busy: Try next member, but do not go to next group (Because this setting is not the 
default, you must set it manually.)
Not Available: Skip remaining members, and go directly to next group (Because this 
setting is not the default, you must set it manually.)

2. Line Group Name: LG3001 includes 3001-3004, with the following settings:

No Answer: Try next member, but do not go to next group
Busy: Try next member, but do not go to next group
Not Available: Try next member, but do not go to next group

Ensure that these values are set manually after the upgrade.

The following example shows Line Groups (calls sent to the operator if all ports are busy or RNA) configuration:


Note Configure only incoming line groups; line groups that dial out remain the same.


1. Line Group Name: LG2001 includes 2001-2004, with the following settings:

No Answer: Skip remaining members, and go directly to next group
Busy: Try next member, but do not go to next group
Not Available: Skip remaining members, and go directly to next group

Ensure that these values are set manually after the upgrade.

2. Line Group Name: LG3001 includes 3001-3004 with the following settings:

No Answer: Try next member, but do not go to next group
Busy: Try next member, but do not go to next group
Not Available: Skip remaining members, and go directly to next group

Ensure that these values are set manually after the upgrade.

3. Line Group Name: Operator includes Operator extension (example 1000):

No Answer: Try next member, but do not go to next group
Busy: Try next member, but do not go to next group
Not Available: Try next member, but do not go to next group

After an upgrade, a hunt list automatically gets configured as follows:

Hunt List Name: HL2001, includes Line Groups LG2001 and LG3001, and operator LG if used, 
in this order.

After an upgrade, a hunt pilot automatically gets configured as follows:

Hunt Pilot: 2001, Partition: VMPilotNumberPT, Hunt List: HL2001

Single Cisco Unity Server with Single Cisco CallManager Cluster

This section outlines the voice-mail port configurations with a single Cisco Unity server and a single Cisco CallManager cluster. The examples describe following configurations:

Single Cisco Unity Server with Single Cisco CallManager Cluster in Cisco CallManager 3.3(x)

Single Cisco Unity Server with Single Cisco CallManager Cluster After Migration to Cisco CallManager 4.0(1)

Single Cisco Unity Server with Single Cisco CallManager Cluster in Cisco CallManager 3.3(x)

In this example, voice-mail ports get configured as follows:

Port 1: (Line: 2001) Device Settings - CSS = PhoneCSS
Port 1: (Line: 2001) Directory Number Settings - Partition = VMPilotNumberPT, CSS = 
VMRestrictedCSS
Ports 2 to 6: (Lines: 2002-2006) Device Settings - CSS = PhoneCSS
Ports 2 to 6: (Lines: 2002-2006) Directory Number Settings - Partition = VMRestrictedPT, 
CSS = VMRestrictedCSS
Ports 1 to 6: (Lines: 2001-2006) Call Forwarding Settings on Busy and No Answer CSS = 
VMRestrictedCSS
Line: 2001, CFNA = 2002, CFB = 2002
Line: 2002, CFNA = 2003, CFB = 2003
Line: 2003, CFNA = 2004, CFB = 2004
Line: 2004, CFNA = 2001, CFB = 2001
Line: 2005, CFNA = 2001, CFB = Blank  (for outbound calls and MWI)
Line: 2006, CFNA = 2001, CFB = Blank  (for outbound calls and MWI)

Single Cisco Unity Server with Single Cisco CallManager Cluster After Migration to Cisco CallManager 4.0(1)

In this example, voice-mail ports get configured as follows:

Ports 1 to 6: (Lines: 2001-2006) Device Settings - CSS = PhoneCSS
Ports 1 to 6: (Lines: 2001-2006) Directory Number Settings - Partition = VMPilotPartition, 
CSS = VMRestrictedCSS

Line groups get configured as follows:

Line Group Name: LG2001 includes 2001-2004 with the following settings:

No Answer: Try next member, but do not go to next group
Busy: Try next member, but do not go to next group
Not Available: Try next member, but do not go to next group

Create the following line groups for outbound ports:

LG2005, include 2005 and 2006

Configure these line groups with the following settings:

No Answer: Stop hunting. (Because this setting is not the default, you must set it 
manually.)
Busy: Stop hunting. (Because this setting is not the default, you must set it 
manually.)
Not Available: Stop hunting. (Because this setting is not the default, you must set it 
manually.)

Hunt lists get configured as follows:

Hunt List Name: HL2001, includes Line Groups LG2001
Hunt List Name: HL2004, includes Line Groups LG2004 and LG2001, in that order
Hunt List Name: HL2005, includes Line Groups LG2005 and LG2001, in that order

Hunt pilot gets configured as follows:

Hunt Pilot: 2001, Partition: VMPilotNumberPT, Hunt List: HL2001

Static Digit Analysis

In Release 4.0(1) of Cisco CallManager, the new digit analysis process builds a static digit analysis engine with the patterns that are configured in the database during system initialization. This digit analysis engine reduces the propagation of patterns within a cluster of Cisco CallManagers and makes Cisco CallManager more scalable.

In previous releases, the individual device control process read pattern information from the database and dynamically registered the patterns to the digit analysis process to build its digit analysis engine. Each pattern had a mapping to its control process ID in the digit analysis engine. The control process ID of a pattern got changed dynamically if its associated device was reset or if a Cisco CallManager server restarted. If a change to the control process ID took place, the digit analysis engine had to be changed dynamically, and its contents required propagation to other Cisco CallManager servers. During call processing, the digit analysis engine returned the control process ID of a matched pattern.

In the current release, the digit analysis process reads the pattern information directly from the database to build the static digit analysis engine during Cisco CallManager initialization. With the static digit analysis engine, each pattern has a mapping to its callable endpoint name, which is a NumPlanPkID of the pattern in the database, a unique identifier to a configured pattern in Cisco CallManager. The static digit analysis engine no longer holds the control process ID of a pattern.

Static digit analysis integrates with the changes to the device manager to support all existing functions and features. The device manager includes a table where a NumPlanPkID shows a one-to-one mapping to the control process ID of a pattern. When processing a call, digit analysis asks the device manager to get the control process ID for a matched pattern.

Feature Description

The current Cisco CallManager system has these pattern types: Call Park, Call Forward, Meet-Me Conference, Device, Translation, Call Pickup Group, Route, and Message Waiting. The Device, Translation, and Route pattern types represent static patterns. The digit analysis process reads these patterns directly and inserts them into the static digit analysis engine during the initialization of a Cisco CallManager. Other pattern types (Call Park, Call Forward, Meet-Me Conference, Call Pickup Group, and Message Waiting), which are intercept patterns, remain dynamic patterns. Their individual control process reads the pattern information from the database and then asks the digit analysis process to insert the pattern into the static digit analysis engine via registration messages.

All static patterns remain unchanged until their records are changed in the database. Static patterns do not require propagation, because the database change notification is broadcast to the servers within a cluster. Dynamic patterns still use the existing propagating and updating mechanism to update the static digit analysis engines.

Regardless of its pattern type, each static pattern in the static digit analysis engine has a mapping to its PkID in the NumPlan table in the database. When a device registers its patterns to the device manager, the same PkID gets saved and mapped to its control process ID in the device manager. A new interface between the digit analysis and device manager retrieves the control process ID when a matched pattern is found in the static digit analysis engine during call processing.

Caveat 1

A potential loss of change notification exists in the current Cisco CallManager release. This loss could cause a device that is registered with Cisco CallManager to become unreachable by other devices. The following paragraphs provide troubleshooting for this potential problem.

The most common cause for this problem occurs when the DN that is assigned to the device belongs to a partition that is not contained in the calling search space of other devices. If the calling search space of other devices does contain the partition for that DN, other reasons may apply. For example, the DN was changed only for that device, and the change notification from the database to Cisco CallManager was lost. In Release 4.0(1) of Cisco CallManager, resetting the device may not resolve the problem.

To resolve this problem in Release 4.0(1), remove the DN and re-add the DN to the system. Remove the DN from its device on the Directory Number Configuration window and on the Route Plan Report window. After you remove the DN, add it back in with the same partition, pattern, and other configuration information. The problem should be resolved after you re-add the new DN to Cisco CallManager.

The same workaround applies to route patterns and translation patterns if similar problems exist.


Tip Be sure to document all configurations before removing the patterns.


Caveat 2

Static digit analysis disables the configuration of several applications. These applications rely on the provision of duplicate patterns in the same calling search space. For example, the CTI application may be pattern 5000 in partition A, and a particular phone may be pattern 5000 in partition B. In previous releases, if the CTI route point is down, the phone will ring. With static digit analysis, however, the caller receives a busy tone. This limitation implies that the application failure cannot be handled.

Administrators would normally use Call Forward No Answer and Call Forward on failure to handle application failure, but when the pattern on the CTI route point is 5XXX, a forward destination of 5XXX cannot be configured. To resolve this limitation, you can now perform configuration of X characters in Call Forward destinations.

The following example demonstrates the functionality of digit analysis prior to Release 4.0(1) (with dynamic digit analysis) and in Release 4.0(1) (with static digit analysis) for the IPMA application.

IPMA Example with Digit Analysis Prior to Release 4.0(1)

Given the following configuration

Partitions: IPMA, Managers, Everyone
CSS-I-E: IPMA:Everyone
CSS-M-E: Managers:Everyone
Line-1/CSS-I-E: EveryOne/1000
Line-2/CSS-M-E: Manager/1001
CTI RP: IPMA/1XXX
Translation Pattern/CSS-M-E: EveryOne/1XXX

if the CTI route point (RP) is up, 1000/IPMA:EveryOne calls 1001. The call routes by using the CTI route point IPMA/1XXX.

If the CTI route point is down, 1000/IPMA:EveryOne calls 1001. The call goes through the translation pattern Everyone/1xxx, and the call reaches Manager/1001 after the translation and achieves the goal of the IPMA application.

IPMA Example with Static Digit Analysis in Release 4.0(1)

Given an identical configuration, in Release 4.0(1), you must make the following modification: configure 1xxx as a CFNA mask and CSS-E as a CFNA calling search space for the CTI route point to handle the CTI route point failure case.

In Release 4.0(1), using static digit analysis, the following processing takes place:

If the CTI route point (RP) is up, 1000/IPMA:EveryOne calls 1001. The call routes through CTI route point IPMA/1XXX. (Routing does not change from previous releases.)

If the CTI route point is down, 1000/IPMA:EveryOne calls 1001. The call goes to the CTI route point, and its CFNA is triggered. The forwarding feature routes the call through the translation pattern Everyone/1xxx, and the call reaches Manager/1001 after translation.

Without configuring the CFNA in the CTI route point, the translation pattern never gets matched, and the IPMA application fails.

Obtaining Documentation

Cisco documentation and additional literature are available on Cisco.com. Cisco also provides several ways to obtain 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

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 Ordering tool:

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, USA) at 408 526-7208 or, elsewhere in North America, by calling 800 553-NETS (6387).

Documentation Feedback

You can submit e-mail comments about technical documentation 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

For all customers, partners, resellers, and distributors who hold valid Cisco service contracts, the Cisco Technical Assistance Center (TAC) provides 24-hour-a-day, award-winning technical support services, online and over the phone. Cisco.com features the Cisco TAC website as an online starting point for technical assistance. If you do not hold a valid Cisco service contract, please contact your reseller.

Cisco TAC Website

The Cisco TAC website provides online documents and tools for troubleshooting and resolving technical issues with Cisco products and technologies. The Cisco TAC website is available 24 hours a day, 365 days a year. The Cisco TAC website is located at this URL:

http://www.cisco.com/tac

Accessing all the tools on the Cisco TAC website requires a Cisco.com user ID and password. If you have a valid service contract but do not have a login ID or password, register at this URL:

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

Opening a TAC Case

Using the online TAC Case Open Tool is the fastest way to open P3 and P4 cases. (P3 and P4 cases are those in which your network is minimally impaired or for which you require product information.) After you describe your situation, the TAC Case Open Tool automatically recommends resources for an immediate solution. If your issue is not resolved using the recommended resources, your case will be assigned to a Cisco TAC engineer. The online TAC Case Open Tool is located at this URL:

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

For P1 or P2 cases (P1 and P2 cases are those in which your production network is down or severely degraded) or if you do not have Internet access, contact Cisco TAC by telephone. Cisco TAC engineers are assigned immediately to P1 and P2 cases to help keep your business operations running smoothly.

To open a case by telephone, use one of the following numbers:

Asia-Pacific: +61 2 8446 7411 (Australia: 1 800 805 227)
EMEA: +32 2 704 55 55
USA: 1 800 553-2447

For a complete listing of Cisco TAC contacts, go to this URL:

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

TAC Case Priority Definitions

To ensure that all cases are reported in a standard format, Cisco has established case priority definitions.

Priority 1 (P1)—Your 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.

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

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

Priority 4 (P4)—You require information or assistance with Cisco product capabilities, installation, or configuration. There is little or no effect on your business operations.

Obtaining Additional Publications and Information

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

Cisco Marketplace provides a variety of Cisco books, reference guides, and logo merchandise. Go to this URL to visit the company store:

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

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://cisco.com/univercd/cc/td/doc/pcat/

Cisco Press publishes a wide range of general networking, training and certification titles. Both new and experienced users will benefit from these publications. 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/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/ipj

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

http://www.cisco.com/en/US/learning/index.html