Cisco Unified Communications Manager (CallManager)

Table Of Contents

Release Notes for Cisco CallManager Release 3.3(2)

Contents

Introduction

System Requirements

Determining the Software Version

Compatibility Matrix and Supported Upgrades

Related Documentation

New and Changed Information

New Software Features in Release 3.3(2)

Cisco CallManager Multilevel Administration Access

QSIG Support

Distinctive Ring per Line

Consecutive Call-Waiting Alerting

Mappable Softkeys

Cisco Call Back

Cisco IP Manager Assistant (IPMA)

30,000 Devices Per Cluster

Localization Enhancements

Network-Specific Facilities

Automated Alternate-Routing Groups Enhancements

Serviceability Enhancements

Application Programming Interface Enhancements

H.323 Trunks for Wholesale Voice

Call-by-Call Calling Line Identification Restriction

Bulk Administration Tool Enhancements

Cisco CallManager Administration Enhancements

Enhancements to Cisco CallManager Extension Mobility

Gateway Support of Localized Tones and Cadence

Important Notes

Cisco CallManager Attendant Console

Characters Not Supported in the Directory

Cisco CallManager Integration with Corporate Directories

Installing IPMA Assistant Console on Microsoft Windows XP

Cisco Extension Mobility

Cisco VG248 Analog Phone Gateway (VG248) Support

Cisco CallManager Installation and Upgrade Requirements

Configuring DNS, WINS, or LmHosts File

Assigning a Valid Computer Name

Installing Cisco CallManager on the IBM xSeries 345

Cisco CallManager Extended Services

End-User Notes

Attendant Console

User Login Name and Password

Resolved Caveats for Cisco CallManager - Release 3.3(2)

Open Caveats for Cisco CallManager - Release 3.3(2)

Documentation Updates

Changes

Cisco Call Back Service Name Change

Cisco Catalyst 6000 E1 VoIP Gateway Configuration

Cisco CallManager System Guide

Configuring Enterprise Parameters for User Search

Omissions

Additional Counters

Obtaining Documentation

World Wide Web

Documentation CD-ROM

Ordering Documentation

Documentation Feedback

Obtaining Technical Assistance

Cisco.com

Technical Assistance Center

Contacting TAC by Using the Cisco TAC Website

Contacting TAC by Telephone

Release Notes for Cisco CallManager Release 3.3(2)

---

Dec. 20, 2002

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

For a list of the open and resolved caveats for Cisco CallManager Release 3.3(2), see "Resolved Caveats for Cisco CallManager - Release 3.3(2)" section and "Open Caveats for Cisco CallManager - Release 3.3(2)" 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 3.3 on Cisco Connection Online (CCO) at

http://www.cisco.com/kobayashi/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

•Important Notes

•Resolved Caveats for Cisco CallManager - Release 3.3(2)

•Open Caveats for Cisco CallManager - Release 3.3(2)

•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 3.3 on a Cisco Media Convergence Server (MCS) or on a Cisco Integrated Communications System (ICS) 7750.

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 follow the exact configuration.

---

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

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

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

Determining the Software Version

To determine the software version of Cisco CallManager 3.3, open Cisco CallManager Administration; then, click Details on the main Cisco CallManager Administration page. 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 the minimum versions with which Cisco CallManager Release 3.3(2) has been tested 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 Release3.3(2). For the most current compatibility combinations and defects, refer to the documentation that is distributed with the Cisco IP telephony products.

---

Related Documentation

The following list contains related documents for Cisco CallManager Release 3.3.

•Cisco CallManager Document Locator for Release 3.3(2)

•Cisco IP Telephony Solutions Installation and Configuration Overview

•Installing Cisco CallManager Release 3.3

•Rack-Mount Conversion Kit Installation

•Upgrading Cisco CallManager Release 3.3

•Using Cisco IP Telephony Applications Backup Utility, Version 3.5.6.

•Cisco CallManager Administration Guide

•Cisco CallManager System Guide

•Cisco CallManager Features and Services Guide

•Cisco IP Phone Administration Guide for Cisco CallManager

•Cisco CallManager Serviceability Administration Guide

•Cisco CallManager Serviceability System Guide

•Troubleshooting Guide for Cisco CallManager

•Cisco CallManager Attendant Console User Guide

•Cisco IPMA User Guide. Refer to www.cisco.com/univercd/cc/td/doc/product/voice/c_ipphon/ipma/index.htm

•Cisco IP Manager Assistant: Quick Reference for Managers. Refer to www.cisco.com/univercd/cc/td/doc/product/voice/c_ipphon/ipma/index.htm

•Skinny Client Control Protocol Messaging Guide

•Cisco CallManager Call Detail Record Definition

•Cisco IP Phone Services Application Development Notes

•Cisco CallManager 3.3 JTAPI Installation Guide

•Cisco JTAPI Developer Guide for Cisco CallManager 3.3(2)

•Cisco CallManager 3.3 TAPI Installation Guide

•Cisco TAPI Developer Guide for Cisco CallManager

•Cisco CallManager Extension Mobility API Developer Guide

•System Error Message

•Software License Agreement

New and Changed Information

This section describes new features and changes that are pertinent to this release of Cisco CallManager.

New Software Features in Release 3.3(2)

Cisco CallManager Multilevel Administration Access

Multilevel administration access provides multiple levels of security to Cisco CallManager Administration. Cisco CallManager Multilevel Administration Access allows the creation of different user and functional groups with different access levels to different administration functions. You can get multilevel administration access service for Cisco CallManager Release 3.3 as a separate download from CCO.

QSIG Support

Cisco offers support for Q.SIG basic call and ID services for selected MGCP- controlled gateways and for selected PBX. ID services support depends upon the PBX type. In general, Cisco makes support services available for Calling Line Identification Presentation (CLIP), Calling Name Identification Presentation (CNIP), Connected Name Identification Presentation (CONP), and Calling/Connected Line Identification Restriction (CLIR) for basic calls. The system design guides provide details of compatible PBX software loads, configuration, and operational caveats. Currently supported gateways include WS-6608-T1, WS-6608-E1, Cisco Access Digital Trunk Gateway DT-24+, and Cisco Access Digital Trunk Gateway DE-30+.

Distinctive Ring per Line

This release adds support for seven distinctive ring patterns to Cisco IP phones 7914, 7940, or 7960. Phone users with multiline phones can configure a distinctive ring pattern for each line on the basis of a logical precedence or importance.

Consecutive Call-Waiting Alerting

Prior to Cisco CallManager 3.3, an administrator could only enable or disable audible alerts on a systemwide basis. With Cisco CallManager 3.3, an administrator can configure the audible call-waiting behavior for each line on a Cisco IP Phone 7940 or 7960.

Mappable Softkeys

Cisco CallManager 3.3 allows administrators to create softkey templates that define features, associate softkeys for any call state, and map these features to the softkeys based on call usage patterns. Administrators can apply these templates to individual phones or to groups of phones. This allows administrators to create special templates for managers, assistants, and other special users.

Cisco Call Back

You can enable Cisco Call Back for all users on a Cisco 7940 or 7960 IP Phone. The system makes callback for busy or unanswered calls available between phones that are configured within the same cluster.

---

Note Default softkey templates do not include Cisco Call Back.

---

Cisco IP Manager Assistant (IPMA)

Cisco IP Manager Assistant (IPMA) application allows managers and assistants to handle phone calls more effectively. Each assistant can support up to five manager lines. Managers can enable features, such as Do Not Disturb (DND), Send-All-Calls (SAC), Immediate Divert, Transfer to Voice Mail, Call Intercept, and Set Watch from the softkeys on the IP phone. Assistants can use the Assistant Console application to answer calls for their managers and themselves and to configure manager and assistant preferences.

30,000 Devices Per Cluster

Cisco CallManager Release 3.3 improves scalability to support 30,000 IP phones on a MCS-7845 cluster and 7500 IP phones per MCS-7845-1400 server (dual CPU, 2GB RAM).

Localization Enhancements

Administrators can use Cisco IP Telephony Locale Installer to add new language support directly to a Cisco CallManager server. Cisco CallManager 3.3 supports Japanese, Hungarian, Polish, Greek and all Latin-1 languages. Cisco CallManager Release 3.3 installs the English_United_States locale by default. You can obtain other locales at

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

For information on how to install these locales, refer to the Cisco IP Telephony Locale Installer documentation and the readme file that are posted on the web next to the locale software.

After you download the locale installer, you can display field names in the User area of Cisco CallManager Administration in your chosen language. However, Cisco CallManager only supports the English character set, also known as ISO-Latin1 or ISO-8859-1, in the fields and in all user accounts and passwords that are needed to access these windows. If a user enters data that is not in the English character set, a dialog box displays, stating that the user must enter English data.

---

Note You must install the same locale on all servers in a cluster to maintain locale support during a failover.

---

Network-Specific Facilities

Cisco CallManager Release 3.3 supports outbound call-by-call delivery of AT&T Network-Specific Facilities including Software-Defined Network (SDN) and Megacom services. Support extends to 4ESS and 5ESS switches.The supported voice gateways include Cisco Catalyst 6000 8-port PRI card (WS-6608-T1), Cisco VG200, Cisco 26XX, Cisco 36XX, and Cisco 37XX with PRI ISDN interface configured on a NM-HDV network module.

Automated Alternate-Routing Groups Enhancements

Automated alternate-routing (AAR) groups provide a mechanism to reroute calls through the PSTN or other network by using an alternate number when the Call Admission Control (CAC) rejects a call due to insufficient location bandwidth. Cisco CallManager redirects calls that get forwarded to centralized voice-mail system based on the route path that is specified in the callers AAR Calling Search Space.

Serviceability Enhancements

Cisco CallManager Serviceability includes enhancements to Real-Time Monitoring Tool (RTMT) for device monitoring and real-time reporting, CDR Analysis and Reporting (CAR), and extends Simple Network Management Protocol (SNMP) Management information base (MIB) support to CiscoWorks 2000. Serviceability enhancements include:

•The Quality Report Tool (QRT). QRT is a voice quality and general problem-reporting tool for Cisco CallManager IP Phones.

•Computer-Telephony Interface (CTI) port status

•CTI application station for applications, devices, and line state

•H.323 gatekeeper performance counters

•Query-based device searches

•Localized CAR reports based on existing languages for users who are not CAR administrators.

•IPMA utilization reports in CAR

•CDR search reports based on call termination causes in CAR.

Although CAR is designed to handle any locale, the user interface (UI) supports a limited set of locales. Currently, CAR does not support non-Latin-1 (non-ISO-8859-1) languages such as Russian and Japanese.

Application Programming Interface Enhancements

API enhancements include new TAPI and JTAPI objects and methods to support creation of call park service in Computer-Telephony Interface (CTI) applications and an XML Simple Object Access Protocol (SOAP) base API for accessing the Cisco CallManager configuration database.

H.323 Trunks for Wholesale Voice

Cisco CallManager Release 3.3 improves H.323 interface and added enhancements to support administrative scalability, dial-plan management, and solution redundancy. Enhancements include the following features:

•Alternate gatekeeper

•Alternate endpoints

•Multiple gatekeepers per clusters

•Simple bandwidth resolution query (BRQ) support

•Support of H.323 V2 specification of Registration, Admission, and Status (RAS) retries and timers

•New configuration options

•H.323 call load sharing

•Gatekeeper-controlled gateways

•Call-by-call automated selection of intercluster trunk (ICT) signaling protocols

•CanMapAlias

•Gatekeeper serviceability

Call-by-Call Calling Line Identification Restriction

Prior to Cisco CallManager Release 3.3, an administrator could configure gateway interfaces or IP phone external calling-party mask to not display Calling Line ID (CLID). With Cisco CallManager Release 3.3, an administrator can create a prefix pattern and allow users to enable Calling Line Identification Restriction (CLIR) on a call-by-call basis.

Bulk Administration Tool Enhancements

Cisco CallManager Release 3.3 includes an export utility in Bulk Administration Tool (BAT). The export utility allows the administrator to export phone, user, and user device profile records to a Comma-Separated Values (CSV) file. The administrator can then reinsert the file onto another Cisco CallManager database. BAT now includes support for Cisco IPMA, Cisco VGC phones, and H.323 clients. BAT supports Tool for Auto-Registered Phones Support (TAPS) prompts using Cisco Locale installer on a Cisco Customer Response Server.

---

Note Previous versions of BAT are not compatible with Cisco CallManager Release 3.3(2). You must use BAT Release 4.4(2) with Cisco CallManager Release 3.3(2). You can install BAT Release 4.4(2) from Cisco CallManager Administration by choosing Applications > Install Plugins.

---

---

Note BAT and the export utility only support exporting files and importing files on a Cisco CallManager 3.3 system.

---

Cisco CallManager Administration Enhancements

This release adds the following enhancements to Cisco CallManager Administration:

•Support for Cisco IP Phone 7905G

•Support for new gateway devices

–Cisco Communication Media Module

–ICS7750-MRP3-16FX, -8FX, -8FX0M1

–269X IOS router platform

–3725 IOS router platform

–3745 IOS router platform

•Softkey template support for mappable softkeys on IP phones

•Service parameter page enhancement including the identification of service parameters out of synchronization across a Cisco CallManager cluster and identification of alternate Survivable Remote Site Telephony (SRST) address and association for an IP phone device pool

Enhancements to Cisco CallManager Extension Mobility

This release adds Cisco CallManager Extension Mobility as part of the native Cisco CallManager install. You do not need to install Extended Services or Cisco Customer Response Solution (Cisco CRS) separately. The Cisco CRS version includes the following functional enhancements:

•Usage of alphanumeric or numeric text in userid

•Selection of multiple user device profile at login

•Single IP phone service that supports login and logout

•Alarm and service status support in Real-Time Monitoring Tool (RTMT)

Gateway Support of Localized Tones and Cadence

Cisco CallManager Release 3.3 supports locale-specific tone and cadences on different IOS gateways. The following gateways support four frequency tones:

•WS-6624

•WS-6608

•Cisco 2600XM and Cisco 2691

•Cisco 3640, Cisco 3640A, and Cisco 3660

•Cisco 3700

Important Notes

The following section contains important information that may have been unavailable when the initial release of documentation for Cisco CallManager Release 3.3(2) took place.

Cisco CallManager Attendant Console

Attendant Console has been incorporated into Cisco CallManager Release 3.3. For more information on attendant console, refer to the latest versions of the Cisco CallManager Attendant Console User Guide, Release 1.1(3)

Characters Not Supported in the Directory

Using non-English character sets with DC Directory, Netscape Directory, or Active Directory can cause directory database errors. Cisco CallManager Release 3.3 only supports the English character set, also known as ISO-Latin1 or ISO-8859-1, with any directory.

You cannot add a user with a space in the first, last name or user ID field in this release of Cisco CallManager. If you make changes to the configuration of a user with a space in the first or last name or User ID, you must enter a new name without a space for the user.

Cisco CallManager Integration with Corporate Directories

If you integrated Cisco CallManager with Active Directory or Netscape Directory, you must run the AVVIDCustomerDirectoryPlugin on all Cisco CallManager servers in the cluster, starting with the publisher server. This allows Cisco CallManager to work properly with corporate directories.

Installing IPMA Assistant Console on Microsoft Windows XP

The installation for Assistant Console for IPMA service fails because Internet Explorer 6 on Windows XP does not include Microsoft Java Virtual Machine (JVM). This does not cause a problem if the system has Microsoft Windows XP Service Pack 1 installed. If the system does not have Microsoft Windows XP Service Pack 1, you can use Netscape browsers or install the Sun Java Virtual Machine plugin for Internet Explorer from http://java.sun.com/getjava/download.html.

After installing the Sun JVM plugin, continue the IPMA assistant console installation from http://<server>/ma/Install/IPMAConsoleInstallJar.jspl where <server> represents the IP address of the Cisco CallManager server.

Cisco Extension Mobility

Cisco Extension Mobility Logout replaced Cisco Extension Mobility service.

Cisco VG248 Analog Phone Gateway (VG248) Support

When using the VG248 with Cisco CallManager 3.3, add the device as a Cisco VG248 gateway and configure each port as VGC phone model. This consolidates each of the 48 analog or SMDI ports onto a single device. However, you still must configure these ports in the VG248 interface, and you should not enter any values in the Port Specific fields of the Phone Configuration window. Because these fields are not operational using the VG248 1.2(1) or earlier software, you must configure these settings locally on the VG248.

For details about using the VG248 with this and other Cisco CallManager versions, see the "Configuring VG248 Ports Using Cisco CallManager" in the Cisco VG248 Analog Phone Gateway Software Configuration Guide for details:

http://www.cisco.com/univercd/cc/td/doc/product/voice/c_access/apg/vg248/v1_2/sw_confg/index.htm

To view the latest compatibility information about the VG248 and Cisco CallManager, access the Cisco VG248 Analog Phone Gateway Version Release Notes at the following location on Cisco.com:

http://www.cisco.com/univercd/cc/td/doc/product/voice/c_access/apg/vg248/v1_2/rel_note/vg248rn6.htm

Cisco CallManager Installation and Upgrade Requirements

For a complete list of guidelines and requirements, refer to the Cisco CallManager installation, upgrade, backup and restore, and warning documentation. To obtain the documentation, click the following URL:

http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/3_3/install/index.htm

The following additional requirements apply to the installation, upgrade, and backup and restore process:

Configuring DNS, WINS, or LmHosts File

To upgrade or install Cisco CallManager on the publisher database server, you must configure DNS, WINS, or lmHosts file. Before you upgrade or install Cisco CallManager on the subscriber servers, you must configure DNS name resolution on all subscriber servers.

Assigning a Valid Computer Name

Before you upgrade the publisher database server, verify that you have assigned a valid computer name to the server. Ensure that the computer has a valid unique network name of name of 15 characters or less. The computer name may only contain alphanumeric characters and hyphens (-). The name must start with a letter and end with a letter or digit. Make sure that the computer name follows the rules for ARPANET host names. The upgrade requires that you restore data that is stored on a tape device or network directory. If you do not assign a valid computer name, you cannot restore data that is stored on a network directory.

You must configure DNS and NetBIOS name resolution on the Publisher server when you upgrade to Cisco CallManager 3.3(2) and you are planning to restore the previous data from a backup location on a Network Drive.

You must configure DNS name resolution when you install Cisco CallManager on Subscriber servers.

Installing Cisco CallManager on the IBM xSeries 345

Make sure that you connect your server to the network before you begin installing Cisco CallManager. The special, limited edition of Windows 2000, intended for use with Cisco CallManager only, will not install if you do not connect the server to the network.

To ensure better server performance, make sure that you disable the Hyper-Threading Technology (HTT) after installing Cisco CallManager. Enabling HTT causes Cisco CallManager Busy Hour Call Attempts (BHCA) to decrease. Cisco strongly recommends that you disable this technology on the IBM xSeries 345 server. Perform the following procedure to disable HTT:

Procedure

---

Step 1 Reboot the server.

Step 2 When the IBM logo displays and you see a list of prompts in the lower, left corner of the monitor, press F1 for Configuration/Setup.

Step 3 When the Configuration/Setup Utility window displays, press the arrow keys to choose Advanced Setup; press Enter.

Step 4 Press the arrow keys to choose CPU Options; press Enter.

Step 5 Press the arrow keys to choose Hyper-Threading Technology; then, press the arrow keys to choose Disabled.

Step 6 Press Esc.

Step 7 Press Esc.

Step 8 Press the arrow keys to choose Save Settings; then, press Enter.

Step 9 Press Enter to continue.

Step 10 Press the arrow keys to choose Exit Setup; then, press Enter.

Step 11 Press Enter.

---

For complete information on installation tasks, refer to Installing Cisco CallManager Release 3.3(2).

Cisco CallManager Extended Services

Cisco CallManager Extended Services Version 2 is not supported on Cisco Media Convergence Server MCS-7845-1400.

End-User Notes

The following section contains important information on applications that affect the end user. Cisco suggests you pass the information on to affected end users.

Attendant Console

Be aware that the attendant console user cannot drag a speed-dial entry onto a call in the Call Details pane.

Be aware that the attendant console user cannot rename a speed-dial group from the Edit menu.

User Login Name and Password

Cisco CallManager Release 3.3(2) only supports English data for user accounts and passwords. This affects users who are using application that access the directory to login such as the User Options page and Cisco IPMA.

Resolved Caveats for Cisco CallManager - Release 3.3(2)

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

---

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/cgi-bin/Support/Bugtool/launch_bugtool.pl.

---

Table 1 Resolved Caveats for Cisco CallManager Release 3.3(2) 

Identifier	Summary
CSCdp91423	Call does not get forwarded to voice mail when it is conferenced.
CSCdu38419	H.245 packet precedence does not get properly set.
CSCdu85556	Cisco CallManager does not send a message to an H.323 gateway to play tone on hold.
CSCdv12935	Performance Monitor and Administrator Serviceability Tool reports incorrect values for active calls.
CSCdv61666	User gets invalid conference participant message when user conferences two outside calls.
CSCdv66617	The private directory number (DN) on an IP phone does not ring if the shared line is set to no ring.
CSCdv87998	Cisco CallManager sends a Release Complete message before receiving an EndSessionCommand message when a gateway call is cleared.
CSCdw05993	Backup and restore does not work properly on a secondary Cisco CallManager.
CSCdw08442	Music on Hold live audio source skips like a broken record.
CSCdw27029	H.323 call to a shared line between H.323 client and Cisco IP Phone 7960 fails.
CSCdw46019	Hook-flash transfer to the Cisco WebAttendant pilot point fails.
CSCdw50535	Cisco CallManager displays an error message when you try to add a Cisco 3600 as a Media Gateway Control Protocol (MGCP) gateway.
CSCdw57062	The redirecting and redirection ID do not get returned to the TAPI application when the call is forwarded with No Answer
CSCdw58057	When you search for route pattern by using brackets (contains '[' or ']') as the search criteria, the search always fails
CSCdw68981	Voice-mail numbers do not migrate when Cisco CallManager is upgraded from Release 3.1 to Release 3.2.
CSCdw78663	You cannot change the server name because you cannot update the URL for applications.
CSCdw79147	Dllhost.exe has high memory usage over a period of time.
CSCdw79685	An intercluster-trunk route loop causes Cisco CallManager to fail.
CSCdw83657	Cisco CallManager does not support Cisco fax relay using software Media Termination Point (MTP).
CSCdw87165	TFTP services cannot build files because of DBL exception condition.
CSCdw88191	CallCtlConnEstablishedEv does not get received in an ICD blind conference call.
CSCdw92574	Cisco CallManager CPU usage goes to 100 percent when the user views or updates filters with multiple clauses.
CSCdx02228	CCMCIP process causes high CPU usage when directory searches are done from an IP phone.
CSCdx04968	Cisco CallManager does not send MDCX to 6608 port. The phone receives a reorder tone.
CSCdx06472	Cisco CallManager does not send MGCP notification request (RQNT) after it receives a 401 (already off hook) message.
CSCdx08771	Cisco CallManager has the incorrect MaxTotalNumberOfRegisteredCallingEntities in the service parameter page.
CSCdx09121	IP phones should display "Too Much Traffic Try Again Later" error message when the IP phones request dial tone on a Cisco CallManager with a congested event queue.
CSCdx13166	Cisco CallManager only supports 12 G729 calls when Cisco Catalyst 6000 is used as a MTP.
CSCdx16488	You cannot use all 24 software MTP resources.
CSCdx16935	The performance counter displays the wrong number of conference resources for SW Conf bridge.
CSCdx18548	The MOH does not play when the audio source gets deleted during a call.
CSCdx20222	JTAPI delivers the wrong events to an observer with a synchronized block in the callChangedEvent callback.
CSCdx20355	The route plan wizard creates a incorrect route filter.
CSCdx22241	The TCP handle format has changed.
CSCdx26411	Users get a timeout error when they update or delete a device on a large database.
CSCdx26414	Users get an error when they choose a submenu on the search page.
CSCdx28149	Cisco CallManager does not allow a mask for a caller ID in service parameter.
CSCdx28844	The TFTP server does not send Music On Hold (MOH) file update.
CSCdx31622	The default for Cisco CallManager initialization timer specifies 10 minutes.
CSCdx31959	Origspan field of the CallDetailRecord in CDR gets set to 0 for incoming calls.
CSCdx32334	InsertCDR has a memory leak.
CSCdx33982	A hold event does not get sent in a TAPI/softkey transfer conference scenario.
CSCdx34659	The pilot number did not get migrated after Cisco CallManager was upgraded.
CSCdx35688	CFA set on IP phone should check the CFA CSS.
CSCdx36263	An extra CallConferenceStateChangedEvent gets sent when a party drops from a conference call.
CSCdx36275	Svchost crashes because device.m_WaveList pointer is null.
CSCdx36953	Cisco CallManager does not write Call Management Records (CMR) correctly for MGCP gateway.
CSCdx39020	Cisco CallManager does not detect MOH Fixed Audio Source.
CSCdx40494	Installing and upgrading without configuring Media Streaming Application causes the CPU usage to go to100 percent when the Media Streaming Application service is started.
CSCdx41465	UnknownCallerIDText field displays invalid characters.
CSCdx42221	The service started/stopped alarm for Cisco Call Back, Cisco IP Voice Media Streaming Application, and Cisco RIS Data Collector contains UNKNOWN_PARAMNAME.
CSCdx42412	JTAPI throws an exception when a call generates DTMF.
CSCdx42868	The phone displays unknown for caller's redirection and redirecting ID when the call is redirected to the destination while the call is still in the ringing and accepted state.
CSCdx43063	User cannot transfer conference call.
CSCdx44240	Administration password in the Backup and Restore utility is case insensitive.
CSCdx44401	Multicast MOH stops working.
CSCdx46450	You cannot configure Survivable Remote Site Telephony (SRST) explicitly.
CSCdx46742	Calls skip first shared line on the phone.
CSCdx46753	Some phones show the shared line as being in use remotely after a call has cleared.
CSCdx47142	Svchost.exe crashed.
CSCdx47194	The service started/stopped alarm for Cisco IP Voice Media Streaming Application contains UNKNOWN_PARAMNAME.
CSCdx49380	CiscoTransferStart message gets received before an agent answers a call.
CSCdx50129	Calls to an IP phone fail after a time when a user logs on with extension mobility device profile.
CSCdx50661	Associating a non-CTI devices with a CTI user causes a LINE_CREATE message to be sent.
CSCdx50771	Cisco WebAttendant does not notify Cisco CallManager when a pilot number has changed.
CSCdx51032	Calling lineDevSpecific with CiscoLineDevSpecificRedirectResetOrigCalled request always succeeds even when the redirect is not successful.
CSCdx51077	Reconnect to TSP does not work if CTI Manager is stopped and restarted during ProviderOpen.
CSCdx51423	Agent login fails when the user ID is greater than 11 characters or password is greater than 15 characters.
CSCdx52857	The Trace Analysis and Q931 Translator page does not display the next and last link when 21 files exist.
CSCdx53931	Cisco CallManager resets when too many regions exists.
CSCdx54081	The Media Streaming Application does not notify Cisco CallManager when it detects an ICMP packet.
CSCdx55266	Registration of CTI route points takes longer than phone registration.
CSCdx55641	User cannot change the password from the user page when Cisco CallManager is integrated with Active Directory.
CSCdx55658	RIS Data Collector has a memory leak.
CSCdx57227	Cisco CallManager incorrectly lists the directory number that is assigned to a CTI route point as the original called party on calls that are forwarded from the CTI route point.
CSCdx57258	CPU usage goes to 100 percent when calls to the attendant occur.
CSCdx58041	No Redirecting or RedirectionID information on a caller displays under a forward-all scenario.
CSCdx59603	Cisco CallManager does not identify consult transfer or conference calls.
CSCdx59819	Calls that are routed directly to a registered available device fail with a awaitingCallResponse_SsExtendCallErr. ErrorCode= 2.
CSCdx60185	Caller does not get disconnected when you press the transfer button twice.
CSCdx60407	An incorrect error message gets sent when you change the logout profile on the phone.
CSCdx61476	Svchost.exe crashed after a configuration change when Cisco CallManager server experienced a heavy call volume.
CSCdx61643	The i button help for the EnableconfigurationFileCaching setting does not provide clear information.
CSCdx61771	JTAPI does not receive a AddressInService event after a failover.
CSCdx61821	You cannot make changes to the directory when Cisco CallManager is integrated with Active Directory.
CSCdx62275	ResponseObject in TSP needs to save additional information.
CSCdx62626	Software conference bridge resources do not get released on Cisco CallManager switchback.
CSCdx62770	Unicast MOH stream RTP packets do not get marked with the appropriate TOS/DSCP bits.
CSCdx63366	Updated service parameters for Cisco CallManager do not take effect immediately.
CSCdx63626	The language text in the advanced list appears garbled when Cisco TSP is used with a Japanese OS.
CSCdx63899	CDCC has a memory leak that is caused by late CRCX Ack messages.
CSCdx64318	Transfers to agent devices fail due to CTIERR_TIMEOUT.
CSCdx65821	The OrigSpan and DestSpan fields in the Cisco CallManager Call Detail Record (CDR) database table have negative values.
CSCdx67644	Inbound setup message from the PBX that does not contain a 'Channel IE' gets rejected.
CSCdx68447	A user on a conference call on a Cisco IP Phone 7960 cannot add another call from a PSTN to the conference.
CSCdx69086	Conference request fails when a spurious held event is received for a active call.
CSCdx69088	CTI-based conference request fails when a missing disconnect event occurs during conference tear down.
CSCdx69817	Trace files do not use abbreviated service names.
CSCdx69823	TFTP and publisher servers have high CPU usage when gateway files exist.
CSCdx70293	Users cannot transfer a conference consult call after the call reconnects.
CSCdx70302	JTAPI fails to send a CallCtlConnAlertingEv message for a target device when a held call is redirected.
CSCdx70997	Use the name Cisco CallManager Attendant Console in place of Cisco WebAttendant in Cisco CallManager Administration.
CSCdx71027	The hunt group configuration page does not allow more than 10 lines per user.
CSCdx71094	The phone configuration administration page provides an incorrect HTML link for Cisco VG248 gateways.
CSCdx72430	The cancel button on the External Route Plan Wizard confirmation page does not work.
CSCdx72563	The directory number field for the Fast Dial Entry allows blank entries.
CSCdx72761	CTI should block answers request from Cisco VG248 gateways.
CSCdx73743	You cannot disable Call Forward All from the IP phone after it has been enabled.
CSCdx73978	Transfer failures to agent devices occurs because of CTIERR_TIMEOUT.
CSCdx74857	Cisco CallManager service on a cluster with 800 translation patterns does not start.
CSCdx75623	TAPI does not clean up a consult call when a blind transfer failure occurs.
CSCdx76443	XNTP service disappears after Cisco CallManager release 3.2.2 is installed.
CSCdx76472	TFTP server fails to build devices that are associated with gateway.
CSCdx76564	SNMP service stops when a failover occurs and the phones re-home.
CSCdx76631	Administrator gets an error upon choosing the default 30 SP+ phone button template.
CSCdx76658	Cisco CallManager crashes when CFwdAll is set from one manager phone to another manager phone.
CSCdx76808	Dial pattern does not show up in digit translation table.
CSCdx77387	JTAPI subsystems have partial service. Route points get a fastbusy signal after network failures.
CSCdx77464	The service parameters for CMI lack detailed descriptions and proper validation rules
CSCdx77505	User could not transfer a conference call.
CSCdx78445	The phone remains in a barge state after two failed attempts to barge.
CSCdx78492	Device that is dialing a MeetMe conference bridge fails to join other H.323 devices through G.729 pipe.
CSCdx79045	A redirected call gets routed to the FwdBusy destination when the destination is busy.
CSCdx80054	Cisco CallManager and CTI Manager stopped when the LP queue is extremely high.
CSCdx80060	Cisco CallManager and CTI Manager stopped when the LP queue is extremely high.
CSCdx80574	The service parameters for Cisco TFTP lack detailed descriptions and proper validation rules.
CSCdx80816	The service parameters for Cisco WebAttendant lack detailed description and proper validation rules.
CSCdx81111	Trace does not list the capabilities list for a station during registration.
CSCdx81240	Cisco CallManager administration needs a select unit to limit gateway builds by the TFTP server.
CSCdx81472	DC directory shows errors when extension mobility users log in during a stress test.
CSCdx81967	CDR Analysis and Reporting (CAR) does not display a report in a 800 x 600 screen.
CSCdx82379	AAR Group does not work after the user gets an error message.
CSCdx82418	IP phones display an error message because the network locale for Israel does not exist.
CSCdx82525	Reconnecting to TSP fails, and lines do not come back in service.
CSCdx82537	TSP does not fetch all the lines that are configured for a device when more than 64 lines exist.
CSCdx82553	A user with more than 1024 park DNs causes TSP memory corruption.
CSCdx82839	CTI application cannot recover call.
CSCdx82981	Caller remained on hold because connected message was not received.
CSCdx82991	JTAPI sends an unknown destination handle in the proceeding event.
CSCdx83662	A CTI route point got stuck after a Cisco CallManager failover.
CSCdx83838	The service started/stopped alarm contains UNKNOWN_PARAMNAME.
CSCdx84099	Cisco CallManager has high CPU usage when LP queues are backing up.
CSCdx84394	CTI applications do not get sent information about QuietCleared calls.
CSCdx85157	An extra conference call handle gets created on a three-line conference when a call is parked and unparked.
CSCdx86168	You cannot configure a Cisco IP Phone 7935 in Cisco CallManager Administration.
CSCdx86548	Restarting the devices from the Region page does not work after the Region Field is updated.
CSCdx86670	IP phones do not get the ringback signal when calls are forwarded to shared lines.
CSCdx87109	The incorrect cause code gets sent in certain conference or transfer scenarios.
CSCdx87273	JTAPI subsystem goes out of service after a failover.
CSCdx87330	The field dwConnectedID has incorrect information on a parked call after the call is resumed after being placed on hold.
CSCdx87635	The presentation bit does not get saved when a transfer call is tandem switched.
CSCdx87807	TAPI needs to support park in dwCallfeatures for Cisco VG248 gateways.
CSCdx87868	Removing a call observer after a login or logout causes an exception.
CSCdx87879	The dwDevStatusFlags for MSGWAIT does not get set when a line is closed and reopened for a CTI port device with forward all enabled.
CSCdx88261	TAPI sends an incorrect dwCalledID for a caller on a forwarded call with FwdAll set.
CSCdx88428	The "Only configured in database" search option in the Real-Time Monitoring Tool (RTMT) does not work.
CSCdx88962	Registered phones do not autoregister again when the autoregistration range of a Cisco CallManager server has changed.
CSCdx89263	Upgrades fail when apostrophes exist in the Phone Button Table.
CSCdx89396	Cisco CallManager fails when a call is made from a phone-in location.
CSCdx89539	Cisco CallManager does not send ProviderCallParkDNChangedEvent to the application.
CSCdx89709	CDR Analysis and Reporting (CAR) does not display users with CTI ports enabled.
CSCdx89760	The TFTP file delete parameter does not work.
CSCdx90355	GroupPickUp fails when the pickup DNs are in the partition.
CSCdx90484	Secondary Cisco CallManager fails when a CTI route point that has Call Forward ALL set is called.
CSCdx92563	Cisco CallManager User page displays an error when a user changes locale or the locale profile.
CSCdx92777	Calls do not get propagated to another member of the route group.
CSCdx92952	TAPI application fails in retrieving a call on hold.
CSCdx93516	The H.323 setup message from a Cisco CallManager server does not include the srccallsignaladdress.
CSCdx94892	TSP receives a thread timeout when the CTI Negotiated heartbeat interval is greater than or equal to two times the TSP HeartbeatInterval.
CSCdx95312	Some provider openings fail when more than 100 simultaneous logins occur.
CSCdy00431	JTAPI subsystems have partial service. Route points get a fastbusy signal after network failures.
CSCdy00598	Corporate directory search returns more than 64 entries.
CSCdy00803	Handle leaks occur when H.323 calls are connecting.
CSCdy00894	Database clients that do not use Microsoft Windows NT authentication cannot access the database.
CSCdy01000	Perfmon does not display the Cisco CallManager object.
CSCdy01279	You cannot associate CTI route points and phones with overlapping names to a user.
CSCdy01628	Voice-mail mask field matches directory number (DN) instead of the called number.
CSCdy01689	You cannot instantiate CiscoJtapiVersion class by using JDK 1.4.
CSCdy02117	Cisco CallManager continuously restarts after you install version 3.2(2) ES 07.
CSCdy02335	GetName() returns an empty string when it gets called before ProviderInService.
CSCdy04256	Reset Device on Survivable Remote Site Telephony (SRST) page does not work correctly.
CSCdy04341	The "Parameter for All Server" link in the TFTP configuration page does not work in Netscape Navigator.
CSCdy04471	CTI manager failover events get sent when a parked conference gets a reminder.
CSCdy05087	Connection strings in trace files get truncated.
CSCdy05123	Caller gets PROCEEDING event before Called Party (CTI port) accepts the call.
CSCdy05311	Cisco CallManager incorrectly sets the Original Called Number information element (IE).
CSCdy05414	The originating phone displays the incorrect DN for overlap sending.
CSCdy06578	Called party receives hold tones instead of music when calling party presses the hold softkey.
CSCdy07209	The CTI ports for active calls hangs when Cisco CallManager failover occurs.
CSCdy07585	Cisco CallManager does not handle CtiDisconnectCallReq when StationCdpc shuts down.
CSCdy07597	Service Parameters contain misleading information.
CSCdy07734	JTAPI does not send a directory number (DN) for a device with an Extension Mobility profile.
CSCdy07774	You cannot add a fourth party to a conference after a held call is resumed.
CSCdy08143	Remove CtiDbChangePollingInterval from Cisco CallManager Administration.
CSCdy08200	CTI-initiated extend for transfer does not work when the conference button is pressed once.
CSCdy08879	TSP uses the same named kernel object for several threads within the same TSP and across TSPs to signal thread termination.
CSCdy09108	TSP sends the wrong events when the application attempts to conference a call after one failed conference attempt.
CSCdy11120	Thread Deadlocks result in events not being reported to applications.
CSCdy12274	Administrator cannot deactivate Cisco CallManager NT service to change a publisher server into a TFTP or database service.
CSCdy12437	DeviceOpen fails after a CTI manager failover.
CSCdy12466	CTI keeps sending DeviceRegister, DeviceUnregister, DeviceOutOfService, and DeviceInService events when the parameters in MediaCapability are set as 0.
CSCdy15071	The Cisco IP Voice Media Streaming Application service parameters page displays an error when a user retrieves information.
CSCdy15594	JTAPI installation causes Classpath corruption.
CSCdy15920	A transferred call to a Net Vision phone in SCCP mode does not ring.
CSCdy16223	Data greater than 500 bytes in DeviceDataPassThroughRequest, Response and Event get truncated.
CSCdy16330	Cisco CallManager sends the wrong calling party information to voice mail.
CSCdy16734	JTAPI causes a No Idle Trunk condition in Cisco IP IVR and ICM calls to fail.
CSCdy17460	JTAPI throws timeout exception when a call is unparked.
CSCdy17859	Cisco CallManager does not release entry in locations table.
CSCdy18187	Calls through a nonregistered route point do not get forwarded to voice mail.
CSCdy18893	Adding a Cisco IAD2400 gateway with subunit set to none causes an error.
CSCdy19406	Softphone user with an invalid password causes high CPU usage for the DC Directory.
CSCdy19452	Cisco CallManager server restarts with a StationOutputSetRinger exception.
CSCdy19494	A new installation on a subscriber server cannot use the database for a restored publisher server.
CSCdy20093	Adding MGCP gateways causes TFTP to rebuild all .cnfs files.
CSCdy20167	Cisco CallManager did not start after Cisco CallManager 3.2(2) spA is installed.
CSCdy21425	Updating extension mobility service parameters from Cisco CallManager Administration fails.
CSCdy21693	The System Version Information screen displays an incorrect DSN name.
CSCdy21923	AddMGCPSubunit Function in AXL does not work.
CSCdy22046	Line for Cisco SoftPhone remains out of service after the PC reestablishes network connection.
CSCdy24270	Inserting users with encrypted PIN from exported files in Active Directory fails.
CSCdy24686	Cisco CallManager does not register H.323 gateways after it has been restarted.
CSCdy24693	Cisco CallManager did not route calls after running over 50 days under load.
CSCdy25581	The ethernetPhonePort tag in the ports subelement of Cisco CallManager is mislabeled as ethernetAccessPort.
CSCdy25604	CPU usages stays at 100 percent when you enable extension mobility for devices.
CSCdy25865	CTI rejects request to play invalid DTMF string.
CSCdy26196	Cisco RIS Data Collector does not start when no LAN connectivity exists during bootup.
CSCdy26247	AXL methods addRouteFilter and updateRouteFilter do not insert digits to database.
CSCdy26608	AXL addDevicePool elements networkHoldMOHAudioSourceId should accept a null value.
CSCdy26663	JTAPI does not check CTI error code for incorrect media.
CSCdy27078	Retrieving an element from an empty STL vector can cause TSP to crash.
CSCdy27389	AXL ignores <srstname> element for addDevicePool.
CSCdy27805	CiscoMOHAudioTranslator did not translate audio source wave file.
CSCdy27835	Cisco MOH Audio Translator service fails.
CSCdy28455	Calls through a gatekeeper-controlled H.323 gateway or intercluster trunk fail when calls with no calling party number are sent.
CSCdy28570	IP phone hangs when a user mistakenly chooses line 1 for a call pickup.
CSCdy28585	StationOutputSetRinger signal sends corrupt data.
CSCdy28997	CtiRingTimer should stop when a station stops a ringer by calling StationOutputSetRinger with StationRingOff.
CSCdy30023	PartyAddToConf on a transfer for a four-party conference causes invalid call state in TAPI.
CSCdy30534	Clients cannot connect after network connectivity is restored.
CSCdy30565	CTI manager listens on loopback IP address when no LAN connection exists during startup.
CSCdy30739	Attendant Console pilot point fails to register.
CSCdy31142	Dictionary Files text when translated to different languages causes grammatical errors.
CSCdy31824	AXL returns a SRST reference not found message even if it is in the database.
CSCdy32177	Define the translated text for dynamic strings with placeholders for variables.
CSCdy32349	GenerateProfile() does not retain the add-on module information.
CSCdy32592	Cisco IP Phone restarts when a call is made to a line when "Display (Internal Caller ID) " is configured to display "}."
CSCdy33190	CFNA fails when users with shared-line appearances updated fast dials.
CSCdy33440	Cisco CallManager process stops when Cisco CallManager tracing and XML is enabled.
CSCdy33572	You cannot add CAR Administrators when the userbase does not have group creation rights.
CSCdy35273	The SQL scripts for publishing and pulling subscription need updating.
CSCdy35279	User cannot retrieve a call on shared line 1 with a call on hold.
CSCdy35602	Locations entries do not get deleted under certain scenarios.
CSCdy35717	You cannot delete services from a server that has been removed from a cluster.
CSCdy35722	Restore fails to stop and start the Netscape Directory server on a Cisco uOne server.
CSCdy35877	UOne restore does not work.
CSCdy35885	Inbound calls to an IP phone from an H.323 gateway are clipped.
CSCdy35937	Logging into Cisco CallManager User fails when the administrator creates a password with special characters in Cisco CallManager Administration.
CSCdy36749