[an error occurred while processing this directive]

Cisco Unified Communications Manager (CallManager)

Release Notes for Cisco CallManager Release 3.3(2)


Table Of Contents

Release Notes for Cisco CallManager Release 3.3(2)



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


Cisco Call Back Service Name Change

Cisco Catalyst 6000 E1 VoIP Gateway Configuration

Cisco CallManager System Guide

Configuring Enterprise Parameters for User Search


Additional Counters

Obtaining Documentation

World Wide Web

Documentation CD-ROM

Ordering Documentation

Documentation Feedback

Obtaining Technical Assistance


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


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



These release notes discuss the following topics:


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


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


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


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


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:



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:


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:


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:


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:


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

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


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



Call does not get forwarded to voice mail when it is conferenced.


H.245 packet precedence does not get properly set.


Cisco CallManager does not send a message to an H.323 gateway to play tone on hold.


Performance Monitor and Administrator Serviceability Tool reports incorrect values for active calls.


User gets invalid conference participant message when user conferences two outside calls.


The private directory number (DN) on an IP phone does not ring if the shared line is set to no ring.


Cisco CallManager sends a Release Complete message before receiving an EndSessionCommand message when a gateway call is cleared.


Backup and restore does not work properly on a secondary Cisco CallManager.


Music on Hold live audio source skips like a broken record.


H.323 call to a shared line between H.323 client and Cisco IP Phone 7960 fails.


Hook-flash transfer to the Cisco WebAttendant pilot point fails.


Cisco CallManager displays an error message when you try to add a Cisco 3600 as a Media Gateway Control Protocol (MGCP) gateway.


The redirecting and redirection ID do not get returned to the TAPI application when the call is forwarded with No Answer


When you search for route pattern by using brackets (contains '[' or ']') as the search criteria, the search always fails


Voice-mail numbers do not migrate when Cisco CallManager is upgraded from Release 3.1 to Release 3.2.


You cannot change the server name because you cannot update the URL for applications.


Dllhost.exe has high memory usage over a period of time.


An intercluster-trunk route loop causes Cisco CallManager to fail.


Cisco CallManager does not support Cisco fax relay using software Media Termination Point (MTP).


TFTP services cannot build files because of DBL exception condition.


CallCtlConnEstablishedEv does not get received in an ICD blind conference call.


Cisco CallManager CPU usage goes to 100 percent when the user views or updates filters with multiple clauses.


CCMCIP process causes high CPU usage when directory searches are done from an IP phone.


Cisco CallManager does not send MDCX to 6608 port. The phone receives a reorder tone.


Cisco CallManager does not send MGCP notification request (RQNT) after it receives a 401 (already off hook) message.


Cisco CallManager has the incorrect MaxTotalNumberOfRegisteredCallingEntities in the service parameter page.


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.


Cisco CallManager only supports 12 G729 calls when Cisco Catalyst 6000 is used as a MTP.


You cannot use all 24 software MTP resources.


The performance counter displays the wrong number of conference resources for SW Conf bridge.


The MOH does not play when the audio source gets deleted during a call.


JTAPI delivers the wrong events to an observer with a synchronized block in the callChangedEvent callback.


The route plan wizard creates a incorrect route filter.


The TCP handle format has changed.


Users get a timeout error when they update or delete a device on a large database.


Users get an error when they choose a submenu on the search page.


Cisco CallManager does not allow a mask for a caller ID in service parameter.


The TFTP server does not send Music On Hold (MOH) file update.


The default for Cisco CallManager initialization timer specifies 10 minutes.


Origspan field of the CallDetailRecord in CDR gets set to 0 for incoming calls.


InsertCDR has a memory leak.


A hold event does not get sent in a TAPI/softkey transfer conference scenario.


The pilot number did not get migrated after Cisco CallManager was upgraded.


CFA set on IP phone should check the CFA CSS.


An extra CallConferenceStateChangedEvent gets sent when a party drops from a conference call.


Svchost crashes because device.m_WaveList pointer is null.


Cisco CallManager does not write Call Management Records (CMR) correctly for MGCP gateway.


Cisco CallManager does not detect MOH Fixed Audio Source.


Installing and upgrading without configuring Media Streaming Application causes the CPU usage to go to100 percent when the Media Streaming Application service is started.


UnknownCallerIDText field displays invalid characters.


The service started/stopped alarm for Cisco Call Back, Cisco IP Voice Media Streaming Application, and Cisco RIS Data Collector contains UNKNOWN_PARAMNAME.


JTAPI throws an exception when a call generates DTMF.


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.


User cannot transfer conference call.


Administration password in the Backup and Restore utility is case insensitive.


Multicast MOH stops working.


You cannot configure Survivable Remote Site Telephony (SRST) explicitly.


Calls skip first shared line on the phone.


Some phones show the shared line as being in use remotely after a call has cleared.


Svchost.exe crashed.


The service started/stopped alarm for Cisco IP Voice Media Streaming Application contains UNKNOWN_PARAMNAME.


CiscoTransferStart message gets received before an agent answers a call.


Calls to an IP phone fail after a time when a user logs on with extension mobility device profile.


Associating a non-CTI devices with a CTI user causes a LINE_CREATE message to be sent.


Cisco WebAttendant does not notify Cisco CallManager when a pilot number has changed.


Calling lineDevSpecific with CiscoLineDevSpecificRedirectResetOrigCalled request always succeeds even when the redirect is not successful.


Reconnect to TSP does not work if CTI Manager is stopped and restarted during ProviderOpen.


Agent login fails when the user ID is greater than 11 characters or password is greater than 15 characters.


The Trace Analysis and Q931 Translator page does not display the next and last link when 21 files exist.


Cisco CallManager resets when too many regions exists.


The Media Streaming Application does not notify Cisco CallManager when it detects an ICMP packet.


Registration of CTI route points takes longer than phone registration.


User cannot change the password from the user page when Cisco CallManager is integrated with Active Directory.


RIS Data Collector has a memory leak.


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.


CPU usage goes to 100 percent when calls to the attendant occur.


No Redirecting or RedirectionID information on a caller displays under a forward-all scenario.


Cisco CallManager does not identify consult transfer or conference calls.


Calls that are routed directly to a registered available device fail with a awaitingCallResponse_SsExtendCallErr. ErrorCode= 2.


Caller does not get disconnected when you press the transfer button twice.


An incorrect error message gets sent when you change the logout profile on the phone.


Svchost.exe crashed after a configuration change when Cisco CallManager server experienced a heavy call volume.


The i button help for the EnableconfigurationFileCaching setting does not provide clear information.


JTAPI does not receive a AddressInService event after a failover.


You cannot make changes to the directory when Cisco CallManager is integrated with Active Directory.


ResponseObject in TSP needs to save additional information.


Software conference bridge resources do not get released on Cisco CallManager switchback.


Unicast MOH stream RTP packets do not get marked with the appropriate TOS/DSCP bits.


Updated service parameters for Cisco CallManager do not take effect immediately.


The language text in the advanced list appears garbled when Cisco TSP is used with a Japanese OS.


CDCC has a memory leak that is caused by late CRCX Ack messages.


Transfers to agent devices fail due to CTIERR_TIMEOUT.


The OrigSpan and DestSpan fields in the Cisco CallManager Call Detail Record (CDR) database table have negative values.


Inbound setup message from the PBX that does not contain a 'Channel IE' gets rejected.


A user on a conference call on a Cisco IP Phone 7960 cannot add another call from a PSTN to the conference.


Conference request fails when a spurious held event is received for a active call.


CTI-based conference request fails when a missing disconnect event occurs during conference tear down.


Trace files do not use abbreviated service names.


TFTP and publisher servers have high CPU usage when gateway files exist.


Users cannot transfer a conference consult call after the call reconnects.


JTAPI fails to send a CallCtlConnAlertingEv message for a target device when a held call is redirected.


Use the name Cisco CallManager Attendant Console in place of Cisco WebAttendant in Cisco CallManager Administration.


The hunt group configuration page does not allow more than 10 lines per user.


The phone configuration administration page provides an incorrect HTML link for Cisco VG248 gateways.


The cancel button on the External Route Plan Wizard confirmation page does not work.


The directory number field for the Fast Dial Entry allows blank entries.


CTI should block answers request from Cisco VG248 gateways.


You cannot disable Call Forward All from the IP phone after it has been enabled.


Transfer failures to agent devices occurs because of CTIERR_TIMEOUT.


Cisco CallManager service on a cluster with 800 translation patterns does not start.


TAPI does not clean up a consult call when a blind transfer failure occurs.


XNTP service disappears after Cisco CallManager release 3.2.2 is installed.


TFTP server fails to build devices that are associated with gateway.


SNMP service stops when a failover occurs and the phones re-home.


Administrator gets an error upon choosing the default 30 SP+ phone button template.


Cisco CallManager crashes when CFwdAll is set from one manager phone to another manager phone.


Dial pattern does not show up in digit translation table.


JTAPI subsystems have partial service. Route points get a fastbusy signal after network failures.


The service parameters for CMI lack detailed descriptions and proper validation rules


User could not transfer a conference call.


The phone remains in a barge state after two failed attempts to barge.


Device that is dialing a MeetMe conference bridge fails to join other H.323 devices through G.729 pipe.


A redirected call gets routed to the FwdBusy destination when the destination is busy.


Cisco CallManager and CTI Manager stopped when the LP queue is extremely high.


Cisco CallManager and CTI Manager stopped when the LP queue is extremely high.


The service parameters for Cisco TFTP lack detailed descriptions and proper validation rules.


The service parameters for Cisco WebAttendant lack detailed description and proper validation rules.


Trace does not list the capabilities list for a station during registration.


Cisco CallManager administration needs a select unit to limit gateway builds by the TFTP server.


DC directory shows errors when extension mobility users log in during a stress test.


CDR Analysis and Reporting (CAR) does not display a report in a 800 x 600 screen.


AAR Group does not work after the user gets an error message.


IP phones display an error message because the network locale for Israel does not exist.


Reconnecting to TSP fails, and lines do not come back in service.


TSP does not fetch all the lines that are configured for a device when more than 64 lines exist.


A user with more than 1024 park DNs causes TSP memory corruption.


CTI application cannot recover call.


Caller remained on hold because connected message was not received.


JTAPI sends an unknown destination handle in the proceeding event.


A CTI route point got stuck after a Cisco CallManager failover.


The service started/stopped alarm contains UNKNOWN_PARAMNAME.


Cisco CallManager has high CPU usage when LP queues are backing up.


CTI applications do not get sent information about QuietCleared calls.


An extra conference call handle gets created on a three-line conference when a call is parked and unparked.


You cannot configure a Cisco IP Phone 7935 in Cisco CallManager Administration.


Restarting the devices from the Region page does not work after the Region Field is updated.


IP phones do not get the ringback signal when calls are forwarded to shared lines.


The incorrect cause code gets sent in certain conference or transfer scenarios.


JTAPI subsystem goes out of service after a failover.


The field dwConnectedID has incorrect information on a parked call after the call is resumed after being placed on hold.


The presentation bit does not get saved when a transfer call is tandem switched.


TAPI needs to support park in dwCallfeatures for Cisco VG248 gateways.


Removing a call observer after a login or logout causes an exception.


The dwDevStatusFlags for MSGWAIT does not get set when a line is closed and reopened for a CTI port device with forward all enabled.


TAPI sends an incorrect dwCalledID for a caller on a forwarded call with FwdAll set.


The "Only configured in database" search option in the Real-Time Monitoring Tool (RTMT) does not work.


Registered phones do not autoregister again when the autoregistration range of a Cisco CallManager server has changed.


Upgrades fail when apostrophes exist in the Phone Button Table.


Cisco CallManager fails when a call is made from a phone-in location.


Cisco CallManager does not send ProviderCallParkDNChangedEvent to the application.


CDR Analysis and Reporting (CAR) does not display users with CTI ports enabled.


The TFTP file delete parameter does not work.


GroupPickUp fails when the pickup DNs are in the partition.


Secondary Cisco CallManager fails when a CTI route point that has Call Forward ALL set is called.


Cisco CallManager User page displays an error when a user changes locale or the locale profile.


Calls do not get propagated to another member of the route group.


TAPI application fails in retrieving a call on hold.


The H.323 setup message from a Cisco CallManager server does not include the srccallsignaladdress.


TSP receives a thread timeout when the CTI Negotiated heartbeat interval is greater than or equal to two times the TSP HeartbeatInterval.


Some provider openings fail when more than 100 simultaneous logins occur.


JTAPI subsystems have partial service. Route points get a fastbusy signal after network failures.


Corporate directory search returns more than 64 entries.


Handle leaks occur when H.323 calls are connecting.


Database clients that do not use Microsoft Windows NT authentication cannot access the database.


Perfmon does not display the Cisco CallManager object.


You cannot associate CTI route points and phones with overlapping names to a user.


Voice-mail mask field matches directory number (DN) instead of the called number.


You cannot instantiate CiscoJtapiVersion class by using JDK 1.4.


Cisco CallManager continuously restarts after you install version 3.2(2) ES 07.


GetName() returns an empty string when it gets called before ProviderInService.


Reset Device on Survivable Remote Site Telephony (SRST) page does not work correctly.


The "Parameter for All Server" link in the TFTP configuration page does not work in Netscape Navigator.


CTI manager failover events get sent when a parked conference gets a reminder.


Connection strings in trace files get truncated.


Caller gets PROCEEDING event before Called Party (CTI port) accepts the call.


Cisco CallManager incorrectly sets the Original Called Number information element (IE).


The originating phone displays the incorrect DN for overlap sending.


Called party receives hold tones instead of music when calling party presses the hold softkey.


The CTI ports for active calls hangs when Cisco CallManager failover occurs.


Cisco CallManager does not handle CtiDisconnectCallReq when StationCdpc shuts down.


Service Parameters contain misleading information.


JTAPI does not send a directory number (DN) for a device with an Extension Mobility profile.


You cannot add a fourth party to a conference after a held call is resumed.


Remove CtiDbChangePollingInterval from Cisco CallManager Administration.


CTI-initiated extend for transfer does not work when the conference button is pressed once.


TSP uses the same named kernel object for several threads within the same TSP and across TSPs to signal thread termination.


TSP sends the wrong events when the application attempts to conference a call after one failed conference attempt.


Thread Deadlocks result in events not being reported to applications.


Administrator cannot deactivate Cisco CallManager NT service to change a publisher server into a TFTP or database service.


DeviceOpen fails after a CTI manager failover.


CTI keeps sending DeviceRegister, DeviceUnregister, DeviceOutOfService, and DeviceInService events when the parameters in MediaCapability are set as 0.


The Cisco IP Voice Media Streaming Application service parameters page displays an error when a user retrieves information.


JTAPI installation causes Classpath corruption.


A transferred call to a Net Vision phone in SCCP mode does not ring.


Data greater than 500 bytes in DeviceDataPassThroughRequest, Response and Event get truncated.


Cisco CallManager sends the wrong calling party information to voice mail.


JTAPI causes a No Idle Trunk condition in Cisco IP IVR and ICM calls to fail.


JTAPI throws timeout exception when a call is unparked.


Cisco CallManager does not release entry in locations table.


Calls through a nonregistered route point do not get forwarded to voice mail.


Adding a Cisco IAD2400 gateway with subunit set to none causes an error.


Softphone user with an invalid password causes high CPU usage for the DC Directory.


Cisco CallManager server restarts with a StationOutputSetRinger exception.


A new installation on a subscriber server cannot use the database for a restored publisher server.


Adding MGCP gateways causes TFTP to rebuild all .cnfs files.


Cisco CallManager did not start after Cisco CallManager 3.2(2) spA is installed.


Updating extension mobility service parameters from Cisco CallManager Administration fails.


The System Version Information screen displays an incorrect DSN name.


AddMGCPSubunit Function in AXL does not work.


Line for Cisco SoftPhone remains out of service after the PC reestablishes network connection.


Inserting users with encrypted PIN from exported files in Active Directory fails.


Cisco CallManager does not register H.323 gateways after it has been restarted.


Cisco CallManager did not route calls after running over 50 days under load.


The ethernetPhonePort tag in the ports subelement of Cisco CallManager is mislabeled as ethernetAccessPort.


CPU usages stays at 100 percent when you enable extension mobility for devices.


CTI rejects request to play invalid DTMF string.


Cisco RIS Data Collector does not start when no LAN connectivity exists during bootup.


AXL methods addRouteFilter and updateRouteFilter do not insert digits to database.


AXL addDevicePool elements networkHoldMOHAudioSourceId should accept a null value.


JTAPI does not check CTI error code for incorrect media.


Retrieving an element from an empty STL vector can cause TSP to crash.


AXL ignores <srstname> element for addDevicePool.


CiscoMOHAudioTranslator did not translate audio source wave file.


Cisco MOH Audio Translator service fails.


Calls through a gatekeeper-controlled H.323 gateway or intercluster trunk fail when calls with no calling party number are sent.


IP phone hangs when a user mistakenly chooses line 1 for a call pickup.


StationOutputSetRinger signal sends corrupt data.


CtiRingTimer should stop when a station stops a ringer by calling StationOutputSetRinger with StationRingOff.


PartyAddToConf on a transfer for a four-party conference causes invalid call state in TAPI.


Clients cannot connect after network connectivity is restored.


CTI manager listens on loopback IP address when no LAN connection exists during startup.


Attendant Console pilot point fails to register.


Dictionary Files text when translated to different languages causes grammatical errors.


AXL returns a SRST reference not found message even if it is in the database.


Define the translated text for dynamic strings with placeholders for variables.


GenerateProfile() does not retain the add-on module information.


Cisco IP Phone restarts when a call is made to a line when "Display (Internal Caller ID) " is configured to display "}."


CFNA fails when users with shared-line appearances updated fast dials.


Cisco CallManager process stops when Cisco CallManager tracing and XML is enabled.


You cannot add CAR Administrators when the userbase does not have group creation rights.


The SQL scripts for publishing and pulling subscription need updating.


User cannot retrieve a call on shared line 1 with a call on hold.


Locations entries do not get deleted under certain scenarios.


You cannot delete services from a server that has been removed from a cluster.


Restore fails to stop and start the Netscape Directory server on a Cisco uOne server.


UOne restore does not work.


Inbound calls to an IP phone from an H.323 gateway are clipped.


Logging into Cisco CallManager User fails when the administrator creates a password with special characters in Cisco CallManager Administration.


The update button on the Enterprise Parameters Configuration page does not work when a URL has an ampersand character (&).


An error displays when High Density Analog Voice Network Modules (NM-HDA) get inserted with the same sub-unit type.


CTI application cannot add VG248 devices in user.


TSP does not allow hostname with more than two dots.


CTI does not send the correct information in the call state event for route point.


Music on hold has location bandwidth leak.


Cisco CallManager removes route patterns from memory after a voice-mail pilot update.


Removing a clause causes a DBLX.RouteFilter error.


TSP sends an incorrect dwCalledID for a call from a phone with call forward all enabled.


The example in Cisco CallManager help files for the usage of the + wild card is incorrect.


DwParkModes get set incorrectly to 0 for IP phones and CTI ports.


TSP sends incorrect LINEADDRESSCAPS fields.


Cisco CallManager traces do not indicate when the maxqueuesize limit is reached.


Repetitive <getUser> requests in AXL has a memory leak.


Connected call state does not update after a CTI manager failover.


Cisco Unity and Cisco Messaging Interface (CMI) have inconsistent reason code.


Redial fails with overlap sending in a MGCP gateway that is in a routelist.


User cannot connect to port 2000 on Cisco CallManager server.


Intercepts for forwarded calls have problems when device profile is moved.


AXL returns errors when you try to add a line without call forward information.


Callback does not work on a Cisco ATA 186 Analog Telephone adapter.


Users cannot see personal address book entries when an entry uses the maximum number of characters in the first and last name fields.


Cisco CallManager crashes when MaxStationInitPerSecond is set to zero.


Agent gets a device is busy message.


Calls from a CTI application fail.


Call pickup fails when a phone has multiple lines in different CallPickup Groups.


CTI reopens a line without a CTI device to accept the new call.


Phone loses shared-line state and no longer supports shared-line functionality.


Cisco CallManager returns blind transfers to Cisco Unity.


CTI does not close line when a new user logs in with an existing DN.


DwOrigin gets incorrectly set to OUTBOUND on target DN in conference.


Redirecting a conference call fails with invalid address message.


A conference scenario causes incorrect values to be set in RedirectingIDFlags and RedirectionIDFlags field.


Calls to CTI route point fail after a failover.


Pilot points do not work when multiple Cisco CallManager servers are down.


Cisco CallManager does not support Shift-JIS Japanese character set.

The following firmware caveats apply to this release.


Caller ID overwrites the call-parked number.


Cisco IP Phone 7960 speakerphone does not operate properly.


IP phone does not display TFTP Server 2.


Out-of-order packets cannot be reassembled.


The phone does not ring when an incoming call comes in while a user is modifying the ring type.


Users cannot dial a number by using the Placed Calls selection when the IP phone is off hook.


The dial softkey for Cisco IP Phone 7960 does not work when line 1 is in use by a shared phone.


Port in "sh cdp neighbors" displays in the localize language.


Cisco IP Phone 7910 displays incorrect text.


Phones do not work when the wrong URL is used in Enterprise Parameters.


You cannot upgrade or downgrade a Cisco IP Phone 7914 phone load.


Phone attempts registration with secondary Cisco CallManager server.


Answer softkey does not work after the phone is reset with the handset off hook.


Call progression debug message displays the wrong CP Tone value.


Cisco IP Phone 7960 dials the first number in the fast dial list when it is off hook and it is displaying the IDLE URL icon.


Phone directories do not work after upgrading phone firmware.


Cisco IP Phone 7960 resets when the configured Cisco IP Phone 7914 Expansion Module is not attached.

Open Caveats for Cisco CallManager - Release 3.3(2)

Table 2 describes possible unexpected behaviors by Cisco CallManager Release 3.3(2). Unless otherwise noted, these caveats apply to all Cisco CallManager 3.0 releases up to and including Cisco CallManager Release 3.3(2).

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


Table 2 Open Caveats for Cisco CallManager Release 3.3(2) 





Memory leak (svchost/tapisrv) occurs during lineInit/Shutdown.

Memory leak occurs in TSP. This situation occurs when an application starts up, opens devices and lines, and then shuts down.

Workaround: None exists.


Administrators cannot delete a location when another record is using it.

This situation occurs when an administrator chooses an item to configure and associates another item to it. When the administrator tries to delete the original item, an error message displays that it is in use and cannot be deleted. No additional information displays on how to delete it.

Workaround: Check other records to see whether the records are using this location and remove the association.


Administrators cannot delete a device pool when another record is using it

This situation occurs when an administrator chooses an item to configure and associates another item to it. When the administrator tries to delete the original item, an error message displays that it is in use and cannot be deleted. No additional information displays on how to delete it.

Workaround: Check other records to see whether the records are using the device pool and remove any associations.


Cisco CallManager needs a search tool for finding Media Resource Group List (MRGL).

Workaround: None exists.


Cisco CallManager Administration cannot display all DN for a pickup group.

Workaround: None exists.


Pipe truncation error causes device to automatically log out at the wrong time.

Occasionally, a device using the automatic logout feature gets logged out much earlier than expected because a pipe-truncation error causes the last digit of the duration to be dropped.

Workaround: Restart Cisco Extension Mobility Logout Service.


Maximum login time does not always get enforced.

This situation occurs when the user logs in before automatic logout is enabled.

Workaround: Have the user log out and log back in after


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

Cisco CallManager currently does not accept more than 24 dialed digits for placing a call. This situation presents an issue if an account or authorization code must be dialed in conjunction with an international call that uses 15 digits.

Workaround: Rearchitect your dial plan, so you never have more than 24 digits in the dial string.


Calls get disconnected when the calls are transferred across an intercluster trunk.

This happens when IP phone 1 in cluster1 calls IP phone 2 in cluster2, and then transfers IP phone 2 to IP phone 3 in cluster2.

Workaround: Enable MTP on the intercluster trunk.


No audio path exists when a transcoder is used.

With the G.729 bandwidth established between IP-1 and Symbol phone, IP-1 calls Symbol phone, and the transcoder is allocated, but no audio path exists.

This situation occurs when you assign MRGL-1 to IP-1 and MRGL-3 to Symbol phone. MRGL-1 has MRG-1 (which has MOH-1, Transcoder-1), and MRGL-3 has MRG-3 (which has MOH-3, Transcoder-3). Assign G.729 bandwidth between IP-1 and Symbol phone (between regions in which these devices are located).

Workaround: None exists.


Incorrect reason code gets sent when user chooses the transfer to voice-mail button.

This situation occurs on a Cisco Unity system and affects outgoing calls only.

Workaround: None exists.


H.323 call to a shared line between H.323 client and Cisco IP Phone 7960 fails.

H.323 client call to another H.323 client that shares a line appearance with an IP phone does not work.

Workaround: None exists.


Trace file do not get saved in the specified drive and file path.

The trace files in C:\Progam Files\Cisco\Trace\CULS folder did not get saved in the new trace path specified in the trace file configuration parameter. The trace files stayed in the standard CULS folder.

Workaround: None exists.


Cisco CallManager discards prefix digits for route list.

Prefix Digits (Outgoing Calls) that are configured on the route pattern configuration page get discarded along with access code when the route pattern uses a route list for the Gateway/Route list field.

Workaround: None exists.


RTMT - You cannot monitor the Perfmon counters of a recovered node.


1. When this problem occurs, shut down all related browsers including both the AST applet window and Cisco CallManager Administration parent browser. Then, bring up a new AST applet window. This workaround works 70 percent of the time.

2. You can also solve this problem by restarting the IIS service.


Change notification for changing partition does not work.

Cisco CallManager does not use the new route pattern when the administrator changes the route pattern to a different partition from Route Pattern Configuration

Workaround: Restart Cisco CallManager service.


Call Park stops working for some call park extensions.

Some call park extensions stop, and this allows calls to be retrieved after an undetermined time. Other call park extensions continue functioning despite the failure.

The only way to retrieve a call from a failed extension is to wait for the call reversion timer to expire and have it ring the phone that parked the call.

Workaround: Rebooting the Cisco CallManager brings all failed call park extensions back. The problem, however, may return.


A phone that connects to Cisco Catalyst FXS module does not receive ringback on call transfers.

This occurs under the following situation:

IP phone A calls the FXS phone on the hop-off gateway. IP phone A does a blind transfer to IP phone B. IP phone A receives ringback. The FXS phone does not receive any ringback. When the call is answered on IP phone B, the voice path between the FXS phone and IP phone B works fine.

Both clusters uses hardware MTP.

Workaround: None exists.


CTI ignores indicator and displays number instead of displaying Private.

An incoming call with blocked caller ID will show the calling number instead of a null value or a descriptive value such as Private.

Workaround: None exists.


The CTI service parameters default to a 1 CPU /1G RAM platform.

You need to adjust some parameters such as CTIDatabaseQueriesPerIteration, CTIDatabaseQueryInterval, and CTIDbDnQueryInterval for a standard dual-CPU/2G RAM platform.

Workaround: Change the CTI service parameters manually.


Cisco CallManager does not have link to Cisco IP Telephony Locale Installer web page.

Workaround: You can obtain different locales at http://www.cisco.com/kobayashi/sw-center/telephony/callmgr/locale-installer.shtml.


User gets an error when accessing cdr.asp on an IBM server.

This situation occurs on systems with OS version 2000.2.0(4).

Workaround: Perform the following steps to change the security settings for the CCN folder:

1. Log on as an Administrator

2. Use Explorer to navigate to C:\CiscoWebs directory.

3. Right click the CCN directory.

4. Choose Properties.

5. Choose the Security tab.

6. Click the Add button.

7. Locate WebUsers and click Add.

8. Click OK

9. Choose Read, Write & Execute for WebUsers.

10. Click Apply

11. Click OK

Perform the following steps to change the CCN directory to allow anonymous authentication:

1. Choose Manager

2. Expand Services and Applications.

3. Expand Internet Information Services.

4. Expand Default Web Site.

5. Right click the CCN folder

6. Choose Properties.

7. Choose Directory Security.

8. Click Edit.

9. Choose Anonymous access.

10. Click OK twice.


Routing loops cause high CPU usage.

Workaround: None exists.


G.723 calls between Cisco IOS gateway and Cisco ATA186 that is using SCCP get disconnected.

G.723 calls between Cisco IOS gateway and Cisco ATA186 get disconnected. Calls between Cisco ATA186 and IP phones that support G.723 receive one-way audio. This occurs on Cisco ATA 186 that is using SCCP.

Workaround: Set up Cisco ATA 186 to use H.323.


Extension mobility multi-login behavior does not work properly.

User can still log in to multiple devices when the service parameter for multi-login is set to Not Allowed or Auto Logout. This behavior occurs when the multiple logins are enabled on different devices simultaneously.

Workaround: None exists.


Users cannot set passwords with the bracket character "{."

Workaround: Do not use a password that begins with "{."


The database has a memory leak.

In a cluster of five Cisco CallManager servers, Simclient registered 1500 phones on all the subscribers. Calls occurred for 24 hours on subscriber1. The Private Bytes for the DllHost.exe on subscriber1 increased from 4.6MB to 6.4MB in 12 hours. After completing the test, SimClient was reset. The Private bytes for DllHost.exe on publisher increased from 4.6 MB to 10.3 MB.

Workaround: None exists.


The All option for the port field for gateways in the Route Group Configuration page should be deleted.

Workaround: None exists.


Real-time Information Services (RIS) on one server cannot contact RIS on another server.

RIS got restarted at the same time in a cluster with two Cisco CallManager servers. When you launch RTMT on both servers, both servers report that the remote RIS is down.

Workaround: None exist.


Collect procedure generated an exception in winspool.drv.

Workaround: None exists.


The open procedure for PerfDisk service times out and generates an error.

Workaround: None exists.


Cisco CallManager does not do a true blind transfer for MGCP calls.

If the analog phone goes on hook before the Cisco CallManager server receives ALERTING from the PSTN, the server terminates the PSTN call, and the original calling party gets left on hold.

Workaround: The analog phone must remain off hook until dial tone is detected.


Users receive reorder tone instead of a dial tone when they enter an incomplete speed dial.

Workaround: None exists.


The SQLSvc account does not get created during installation.

Cisco CallManager server joins a Windows Domain with a defined password policy. If the default SQLSvc password does not meet the policy requirement, account creation fails.

Workaround: Three options exist:

1. Manually create the SQLSvc Account on the publisher and all subscriber servers. Then reconfigure all Services and Component Services to use the SQLSvc account and password.

2. Remove the Windows domain enforced policies from the Cisco CallManager server.

3. Remove the Cisco CallManager from the Windows domain.


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

Internet Explorer displays a HTTP 500- Internal server error.

Workaround: Reload the page, and Cisco CallManager user displays.


RTMT Directory monitoring gets stuck while updating status.

Workaround: None exists.


Second line goes off hook on the phone.

Two phones have shared lines in which the primary line of one phone is the secondary line of the other and vice versa. When phone A selects the speaker button, the second line goes off hook instead of the first line.

Workaround: None exists.


Incoming calls from Alcatel PBX through a WS-6608 fail.

This situation occurs when thee system is configured as follows:

CCM --6608--e1--Alcatel PBX

Workaround: None exists.


IP phone does not display the dialed number.

This situation happens when Cisco CallManager receives a NOTIFY message with a Display IE but no Connected Number IE.

Workaround: None exists.


You cannot delete a Cisco VG248 gateway in the Find/List Gateways Page.

This situation happens when a user deletes a gateway soon after creating it. User gets an error message and an empty child window.

Workaround: Delete it at a later time.


The file delete parameter does not delete the .cnfs for MGCP gateways.

Workaround: None exists.


The help text for the i button and ? button for Cisco IP Phone models 7960 or 7940 have inaccurate description

Help text should indicate, "This field is not currently used. Leave this field blank."

Workaround: None exists.


Cisco CallManager Administration needs to verify whether a browser has cookies enabled.

Some Cisco CallManager Administration pages do not work properly when cookies are disabled.

Workaround: Enable cookies in your Microsoft Internet Explorer or Netscape Navigator browser.


Gatekeeper Configuration needs a validation function for the Registration Request Time To Live and Registration Retry Timeout field.

This situation happens when user enters invalid input.

Workaround: Use valid inputs.


Active Directory deletes leading zeros in the PIN field.

Active Directory stores PIN as an integer by truncating the leading zeros. For example, if a user enters a PIN of 0001, AD stores the pin as 1.

Workaround: Do not use leading zeros as part of the PIN.


Eight simultaneous logins cause high CPU usage on a subscriber server.

The publisher and subscriber use 1GHZ CPU/1G RAM servers. The CTI parameters are set to default, MaxSimultaneousCTILogins = 8, and SDL traces are disabled.

Workaround: None exists.


Cisco CallManager sends unknown DestinationType in the Proceeding event.

Workaround: None exists.


You cannot change access code for toll bypass and fallback calls in the External Route Plan Wizard.

The Access code for toll bypass and fallback calls value remains ineffective in the Routing Options page in the External Route Plan Wizard. This access code never gets reflected in the prefix digits (outgoing calls) of the route groups for the toll bypass route lists.

Workaround: Manually change the field Prefix digits (outgoing calls) in the route detail configuration page to the desired value.


When intrusion detection systems (IDS) or antivirus software is running, installation of Cisco CallManager fails.

Workaround: Turn off IDS and McAffee antivirus software before installing Cisco CallManager.


Cisco CallManager Administration does not have a Denmark locale.

Workaround: None exists.


Event log errors reference previous Cisco CallManager database.

This situation happens during an upgrade in a clustered environment. The publisher server deletes its publication of the previous database, but the subscriber server does not.

Workaround: Manually create the publication on the publisher server for the previous database or delete the subscriptions for the previous database on the subscriber servers.


CallPark number in Calling Search Space (CSS) partitions toggles from busy to callable.

This situation occurs in the follow scenario:

phA - CSS01 Dirn - RPART01

phB - CSS01 Dirn - RPART01

phC - CSS02 Dirn - RPART02








8000 / RPART01

8000 / RPART02

C alternates between being able to pick up the call and not being able to retrieve it when A calls B and parks the call.

Workaround: Configure different callpark numbers for different partitions.


Perfmon and Real Time Monitoring Tool (RTMT) reports a greater number of active calls than calls in progress.

Performance Monitor or Real Time Monitoring Tool reports a greater number of Active Calls than Calls in Progress. Active Calls represent the number of streaming connections that are currently in use. Calls in Progress represent the number of calls that are currently in progress. When a phone goes off hook, this represents call in progress until it goes back on hook. It includes all active calls. If all calls that are in progress are connected, the number of calls in progress remains the same as the number of active calls.

Workaround: Restart the Cisco CallManager Service.


The subscriber database does not have the store procedure SP_MSSyn_Del_Plugins.

User receives "can not find the store procedure sp_mssyn_del_plugin" error.

Workaround: Add a subscription on the subscriber server. Run a snapshot on the publisher server.


Cisco CallManager has incomplete voice port settings for the 269x gateways

You cannot adjust echo cancel enable and echo cancel coverage voice port settings on the 269X gateway that is using MGCP-controlled FXO analog interface.

Workaround: Manually configure the IOS gateway.


The ccmupgrd script launches stage3.exe when installation is aborted.

The ccmupgrd script should only launch stage3.exe after successful execution of the first stage.

Workaround: Use Task Manager to kill Stage3.exe and Installshield process.


User does not receive ringback on a headset when a second call is received.

Workaround: None exists.


You cannot configure Cisco IPMA if Cisco CallManager is integrated with Active Directory.

This situation happens when Cisco IPMA is installed on a Cisco CallManager server that is integrated with Active Directory and you make changes to the user in IPMA Manager or Assistant.

Workaround: You cannot deploy Cisco IPMA on a Cisco CallManager server that is integrated with Active Directory.


Call pickup fails with blind conference calls.

Workaround: None exists.


Cisco CallManager ignores the VoiceMailMaximumHopCount service parameter.

Calls into voice mail received a busy tone after WS-X6624 ports were swapped out for Cisco VG248 ports. Calls received a busy tone when the first 23 ports were in use. VoicemailMaximumHopCount service parameter was set to 20. VoicemailMaximumHopCount was increased to 145 with no effect.

Workaround: Increase ForwardMaximumHopCount to 132 (135 maximum inbound calls minus 3).


The wrong reason in CallStateChangeEvent gets sent after a conference completes.

Workaround: None exists.


You cannot use a line while Cisco CallManager server is processing a call forward no answer call.

Users on phones that have been forwarded receive the silent tone when they try to answer a call during the call establishment timeframe. The call establishment timeframe represents the time from when Cisco CallManager starts redirecting a call to a new destination and when Cisco CallManager finishes disconnecting the call at the forwarded phone. During this time, the user cannot make new calls or answer calls even when the phone is ringing. At the end of the call establishment timeframe, the user can make and answer calls normally. The length of the call establishment timeframe varies depending on the Cisco CallManager traffic and network traffic while the call is directed to the new destination.

Workaround: None exists.


Cisco CallManager has a memory leak when a PRI call is parked and retrieved on a different node.

Workaround: None exists.


User personal directory and fast dials get deleted when the users samAccountName is change on Microsoft Active Directory.

The Personal Address Book and Personal Fast Dials services use the samAccountName to build a directory structure and to store information.

Workaround: None exists.


SEP.cnf.xml file does not get removed from TFTP cache when a Cisco ATA186 is deleted.

Cisco ATA186 that is deleted from the Cisco CallManager database does not auto-register as an ATA-type device because the SEP configuration file stays in the TFTP cache.

Workaround: Remove the old SEP file from the cache and replace it with an ATA configuration where the file name is ATA <mac address>.cnf.xml.


Cisco IP phones always play a call waiting tone (zip tone) when a second call is forwarded to the second line.

Cisco CallManager ignores ToneOnCallForward service parameter to disable the tone.

Workaround: None exists.


Locations Bandwidth get out of synchronization across Cisco CallManager servers in a cluster.

This occurs on a backup Cisco CallManager. The locations table get reset during a failover.

Workaround: Reset Cisco CallManager service on the server that is out of synchronization during a maintenance window.


SNMP GET-NEXT operation returns TABLE-ENTRY in sysApplMIB.

Workaround: None exists.


Cisco IP Softphone allows user to exit from a share line connection.

Workaround: None exists.


Installation using Virtual Network Computing (VNC) hangs on IBM x330 and x342.

Installation hangs before the application starts copying files and after the application accepts the user data.

Workaround: Click the mouse on the client or server, and the install resumes.


Call pickup fails.

Call pickup does not work for 5 minutes after call pickup group is updated.

Workaround: Wait 5 minutes before attempting call pickups.


A Search in Cisco CallManager Administration using characters such as x, X, ?, +, or * does not work properly.

Workaround: None exists


Fetching park DN gets wrong result.

This occurs under the following conditions:

Configure park DN 8000, 8001 on Cisco CallManager Administration.

Start ctitest.

Fetch park DN by sending GetMonitorDNFetchRequest.

In the 1st GetMonitorDNFetchRequest, count = 1

Get response DN = 8000, more = false.

In the 2nd GetMonitorDNFetchRequest, count = 1

Get response DN = 8000, more = true

Workaround: Specify count = 2 in GetMonitorDNFetchRequest


RedirectionID on a forwarded no answer call does not get sent.

Workaround: None exists.


User can pick up call after deleting the Pickup group number.

Cisco CallManager does not allow group pickup after deletion, but it allows call pickup

Workaround: Update and reset the phone.


The .cnf files stays in the TftpPath even after file caching is turned on.

Workaround: None exists.


LineOpen fails when the caller hangs up before lineUnhold completes.

Line remains unusable until Cisco CallManager server is restarted.

Workaround: Restart Cisco CallManager.


The second appearance of a line does not disappear after the conference has ended.

This occurs under the following situation:

Phone A has a Cisco IP Phone 7914 Expansion Module with multiple shared lines among different users

Phone B and C have 1 line.

Phone D has 4 same DN shared with phone A. The DNs are in different partitions.

Phone A calls Phone B using a shared line with phone D.

Phone A presses CNFR and calls phone C. C answers.

Run simclient traffic on all nodes.

Press CNFR on phone A to conference phones A, B and C.

Phone D displays the second appearance of the line.

Workaround: None exists.


A missing step does not appear in online documentation.

Attendant Console failed to initialize the call control at login, and the error message "Initialization of Call Control Failed--Retrying" displayed.

Workaround: Add a step at the end to check the Call Park Retrieval Allowed check box for the ac user that was created in the user pages.

Online help should appear as follows:

Configuring the ac User through the User Information Window:

1. From Cisco CallManager Administration, choose User > Add a New User.

2. In the First Name and Last Name fields, enter ac.

3. In the User ID field, enter ac.

4. In the User Password field, enter 12345.

5. In the Confirm Password field, enter 12345.

6. Enter a PIN and telephone number.

7. Check the Enable CTI Application Use check box. You must check this box for the attendant console to interact with CTI manager.

8. Click Insert.

9. Associate the devices by performing the procedure in Associating Devices.

10. Check the Enable Call Park Retrieval Allowed check box for ac user.


Redial does not pick up the last called number when the last call was busy.

Workaround: None exists.


Cisco CallManager server requests incorrect packet size of 1ms.

The phone gets "DSP Keepalive Timeout" message after receiving a call from an H.323 gateway. The user may receive a popping noise. The speaker button remains illuminated after the call disconnects.

Workaround: None exists.


You cannot use the answer softkey key when there is an active call and no incoming call.

Workaround: None exists


User cannot easily choose partitions in Cisco CallManager Administration when a large number of them exists.

Choosing a partition from the dropdown list when there are over 100 partitions defined in the system proves difficult.

Workaround: Scroll down the list and choose the desired partition.


Calls fail intermittently over intercluster trunk with an AF cause.

Both sides receive dead air followed by reorder tone. This happens when a call from PSTN through a WS-6608 gets forwarded out via the intercluster trunk to another cluster.

Workaround: None exists.


TSP has a memory and handle leak in some make call and answer scenario.

Application closes calls that have incomplete asynchronous requests. With a Busy Hour Call Completions (BHCC) of 6000 calls per hour and 100 active lines(50 calling, 50 receiving), there is a leak of approximately 2000 bytes per call.

Workaround: The application should add a delay before closing a call that has outstanding asynchronous requests.


TSP has a memory leak in some consult transfer scenario.

Application closes line immediately after it closes calls on that line. There is a leak of 1704 bytes per call.

Workaround: The application should add a delay before closing a line. This allows TSP to complete call object removal.


JTAPI client has a memory leak in some consult conference scenario.

The leak happens when the application adds more than one CallObserver instance to an Address.

Workaround: Add only one CallObserver to an address.


The IOS MGCP Gateway .cnf file does not get updated when its endpoint gets deleted.

Workaround: Update the gateway through Cisco CallManager Administration. This will force TFTP to rebuild the .cnf file.


Music On Hold (MOH) with wideband codec uses an incorrect payload type 25 in RTP stream.

RTP packets defined as payload type 25 (0x19) is assigned to Sun Microsystems for their variable bit rate video encoding scheme called CellB.

Workaround: None exists.


Cisco SoftPhone does not go back in service after line connection is reestablished

Cisco SoftPhone goes out of service when it lose network connectivity to the CTI Cisco CallManager server. When the connection is reestablished, the device does not go back in service.

Workaround: Close or exit Cisco SoftPhone application and restart it.


Newly created location does not get propagated to all servers in a cluster.

Workaround: Stop and restart the Cisco CallManager service.


Cisco CallManager does not allocate bandwidth to the barged phone.

Phone C calls Phone B. Cisco CallManager allocates 80 kbps in each location. Phone A barges in successfully; however, Cisco CallManager does not allocate 80 kbps to Phone A.

Workaround: None exists.


Gatekeeper rejects Cisco CallManager server registration when there are multiple clusters with duplicate H.323 alias

In Cisco CallManager 3.2(2c),the servers register with the gatekeeper as an anonymous device using the IP address as the H323 alias. In Cisco CallManager Release 3.3, the servers register with the gatekeeper using an AnonymousDevice name and appending the digit which identifies the node at the end (anonymousdevice_1). This creates a registration problem when there are multiple clusters with duplicate H323 alias.

Workaround: Change the Device Name to uniquely identify the device in Cisco CallManager Administration.


The phone displays Forwarded to message when CFA is enabled on the second line.

Workaround: None exists.


No help page exists for Dial Rules Configuration.

Workaround: None exists.


No help page exists for IPMA Configuration Wizard.

Workaround: None exists.


A shared line on a Cisco IP Phone 7914 Expansion Module appears in use when the line is really idle.

This situation happens on a Cisco CallManager server (release 3.1) that it running in a cluster environment with multiple share lines.

Workaround: Reset the phones.


CTI manager crashed.

Workaround: Start CTImanager or set the Recovery option in Service Control Manager to "Restart the service."


TAPI application has a slow failover to the subscriber server when the primary CTI manager is powered down or taken off of the network.

Workaround: None exists.


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

Workaround: None exists.


CalledID name does not exist for the unparking party after the call is unparked.

Workaround: None exists.


Duplicate dial rules get added to the list when you refresh the dial configuration page.

Workaround: Use the update button or page link to refresh the screen.


User could not see updates that was made in the dial rules page on subscriber Cisco CallManager Administration.

User had a browser opened on the subscriber server while he was working on a dial rule entry.

Workaround: Close and open Cisco CallManager Administration on the subscriber server.


Location information does not get propagated when you use the update button.

This situation happens in a clustered environment with multiple servers involved in call processing. Specifically, a new location gets created when a call-processing server in the cluster is not online. When the server becomes available, it does not have the new location information. Clicking the update button for that location does not work.

Workaround: Stop and restart the Cisco CallManager service.


JTAPI does not handle the new CTI call state (CtiProgressingState).

The new CTI call state contains the far-end information. It get used when a call across a gateway that does not send ringback occurs.

Workaround: None exists.


A few phones failed to be inserted when you use BAT to insert over 1000 phones.

Workaround: Manually reinsert the failed phones.


Update fails and user gets a duplicate dial rules error message when the rules overlap.

This situation occurs in the follow scenario:

Current Dial Rule 1:

remove digits=1

prefix it with=1

Current Dial Rule 2:

remove digits=2

prefix it with=1

If you update the two rules to

Dial Rule 1:

remove digits=2

prefix it with=1

Dial Rule 2:

remove digits=2

prefix it with=2

You get an error message, and update fails.

Workaround: Move Dial Rule 2 above Dial Rule 1 and change Dial Rule 1 to 2,2.


Links on the page do not work when you delete dial rules with no numeric pages.

This situation happens when a user deletes a dial rule with an empty text box.

Workaround: Reload the page by choosing Route Plan > Application Dial Rules.


Inserting, deleting, or updating dial rules fails with no warning when DCD service is paused.

Workaround: Start DCD Service before doing any operation that involves DC directory.


You cannot view the voice quality reports on a subscriber server.

Workaround: None exists.


UpdatePhone returns an error when the ring setting value is set to 'Use System Default.'

Workaround: None exists.


Primary Cisco CallManager server that was not involved in another Cisco CallManager failover had high CPU usage.

This server had approximately 5000 phones, 100 T1 gateways, and 30 analog phones. The other primary Cisco CallManager server had the same number of devices.

Workaround: Reboot or restart the Cisco CallManager service.


Media channel setup fails when you park a call from one node and pick up the call from another node.

This happens on MTP required calls involving H.323 client, H.323 gateways and H.323 intercluster trunks.

Workaround: Do not use MTP.


When you enter an invalid page number in Route Plan, the dial rule list disappears, and links stop working.

Workaround: Use Internet Explorer.


User gets error message when simultaneous locale installations are attempted.

Workaround: Run only one locale installer.


JTAPI does not send CiscoProvCallParkEv when the parking party unparks a call.

This happens under the following scenario:

A(2000) and B(2001) use the same provider. A registers with the publisher server. B registers with subscriber server.

Application registers to monitor park DN.

A calls B.

B answers.

B parks the call.

B unparks the call.

Workaround: Register B with the publisher server.


Makecall with custom media fails with DISCONNECTED/TEMPFAILURE event.

Workaround: None exists.


MOH Audio Source web page takes 12 seconds to load.

The time to load the page is linked to the number of files in the MOH folder. To improve performance, remove files for audio sources that are no longer in use.

Workaround: None exists.


Cisco CallManager registered a a frame relay network that has a misconfigured MGCP FXO port with FRF12.

Workaround: None exists.


The route plan wizard does not create a PBX route pattern.

Workaround: Configure the additional route plan using Cisco CallManager Administration.


Database throws an exception during a TFTP read, and the TFTP service restarts.

Workaround: If the symptoms persist, reboot the entire cluster.


TFTP stops responding to file download requests.

Workaround: Restart TFTP service or reboot server.


Cisco IPMA wizard has typographical and grammatical errors.

Workaround: None exists.


Users get a run-time error when they try to launch multiple instances of Cisco IPMA wizard.

Workaround: Relaunch the browser.


The chosen partition in the Calling Search Space Creation page does not get saved when you go back from the next page.

Workaround: None exists.


The Assistant console does not display Cisco IPMA version correctly.

If the version is 1.1(1.14), the assistant console (Help -> About Cisco IPMA Assistant Console) displays it as (1.14)1.1

Workaround: None exists.


Cisco IPMA does not display message that filtering and divert All is not possible when it cannot open the route point.

Cisco IPMA fails to open the route point device/lines when it is started.

Workaround: Restart Cisco IPMA service by restarting the Cisco Tomcat Service from Windows Administrative tools.


The phone displays the wrong DN when a call gets transferred between intercluster phones.

This happens during the second transfer.

Workaround: None exists.


DC Directory on the subscriber server fails during installation when the publisher server has Active Directory plugin installed.

Subscriber installation fails when you install a publisher server, install Directory Configuration plugin, and then install the subscriber server.

Workaround: Start DC Directory server on publisher and install Cisco CallManager again.


Route plan wizard does not create local call fallback route pattern.

The route pattern does not get generated when you configure local call fallback between two sites, with two gateways each.

Workaround: Configure the additional route plan from Cisco CallManager Administration after you have generated the patterns with the wizard.


Application loses track of a call transferred by operator.

Call stays connected to the destination.

Workaround: None exists.


Cisco IPMA wizard displays obscure message when the SQL server is down.

Workaround: Make sure that the SQL database is up and running.


Configuration file build for gateways takes much longer than configuration file build for phones.

Workaround: None exists.


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

Workaround: None exists.


System level users get displayed on directory searches on an IPMA assistant console.

Workaround: None exists.


Quality Report Tool (QRT) softkey does not get inserted into a database because of Open Database Connectivity (ODBC) errors.

Workaround: None exists.


Cisco CallManager Virtual Memory usage on large primary Cisco CallManager system reads around 1.484GB to 1.611GB.

Workaround: None exists.


BAT displays error message if the server name begins with a number.

BAT displays the error message - "Failed to create ASP Object."


1. Access pages by using IP addresses.

2. Use Internet Explorer.


You cannot add entries in call park, call pickup, meetme number, etc., using Netscape Navigator when the server name starts with a number.


1. Access pages by using IP addresses.

2. Use Internet Explorer.


Subsequent calls do not go through when MF digits are configured on a Cisco VG200 T1-CAS.

Workaround: None exists.


CTI manager terminated unexpectedly during a failover.

Workaround: None exists.


Cisco CallManager CPU usage goes to 100 percent when there is a call to a location in the same automated alternate routing (AAR) group that is out of bandwidth.

This situation happens when the AAR Group is configured with a blank Prefix digits within AAR_1. This occurs on the Cisco CallManager server that the calling phone registers with.

Workaround: Restart Cisco CallManager service and configure the prefix digits within AAR_1 for that particular AAR Group.


Cisco CallManager does not always send Q.931 disconnect sequence to WS-6608.

Workaround: None exists.


No online help exists for the Continuous Channel Number option in Channel IE type.

Workaround: None exists.


CAR registry does not have Company Name parameter.

The following error displays when you view a report in PDF format:

error code 10011 "System Error. Contact System Administrator"

Workaround: Manually add a name for the parameter "Company Name" in System -> System Parameters -> System Preferences.


Phone shows incorrect shared-line state after a call is released.

Workaround: None exists.


The shared-line status icon does not display the true line state on all phones that are sharing a line.

Workaround: None exists.


Some online help links for Cisco IPMA do not display the correct information.

The following online help links for Cisco IPMA do not work correctly:

Edit->Preferences - The help button does not display any information.

Manager Configuration for the Manager -> The help link brings up Assistant Console help.

Workaround: Invoke help from the main menu. Scroll down to the relevant sections.


Backup and Restore Utility displays unauthenticated server in the target list.

Unauthenticated servers do not get backed up.

Workaround: Delete the target or make sure that the server has proper authentication.


Cisco CallManager Administration displays unknown registration status for registered phones.

Workaround: None exists.


Cisco Messaging Interface Service Parameters have incorrect definition.

Keep Alive DN does not accept "F" as a DN.

Output DN parameter represents the Calling Party Number.

Output External Format parameter represents the Called Party number.

Workaround: None exists.


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

Workaround: None exists.


The AXL getphone method has a memory leak.

This happens when you use this method to get objects that do not exists in the database.

Workaround: Do not use this method to get objects that do not exists in the database.


AXL has inconsistent callpark schema.

AddCallPark schema allows CallPark to be configured in a null partition.

Workaround: Place callpark in a different partition and specify a route filter ID.


IPMA Service Configuration does not display correct information.

IPMA selected lines in manager configuration and proxy line assignments in the assistant configuration pages incorrectly displays as empty/None. This occurs when the Application Dial Rules in Cisco CallManager Administration -> Route Plan -> Application Dial Rules is accessed before Cisco IPMA service configuration is accessed.

Workaround: Two workarounds exist:

1) Access Cisco IPMA Configuration for manager and assistant before accessing Dialrules.

Both the IPMA user configuration pages and dial rules pages work correctly when you access Cisco IPMA configuration first.

2) Restart the WWW (World Wide Web) service from Windows Administrative tools - Services menu.


Cisco IPMA assistants cannot dial international DN with dial rule.

Cisco IPMA assistant cannot make calls to phone numbers beginning with + from the directory search window or the speed-dial window.

When calls are made to international numbers and the numbers begin with +44, the IPMA rule parser sends the number string as 44.

Workaround: Choose the user or speed dial with phone number beginning with +; right click the number and choose dial. You can also drag and drop the speed dial or the directory entry to the "My Calls" window.


AXL returns an error when you do not include the description and callparty tags while you are adding a CTI route point.

Workaround: Specify a description and callparty.


AXL returns an error when CSSclause is specified.

Workaround: Do not specify a clause in your message. You must also add a description tag.


OS Upgrade 2000.2.3 Phase 3 did not execute.

OS version 2000.2.3 executes three phases with a reboot between each phase. This upgrade should run all three phases on every computer.

Workaround: The following requirements apply for the OS upgrade to work properly:

Disable all antivirus and HIDS software at the services, so they do not start during the reboots.

Make sure that you have enough disk space. Cisco recommends that you have 1 GB free disk space before you copy the upgrade file to the server.

Perform the following procedure if you met the above requirements and are still having the problem.

Start the OS Upgrade again by executing the following file:

1. C:\Mcsosupg\Mcsosupg.exe. This restarts to OS Upgrade from Phase 1.

If Phase 3 still does not run, look at the last lines in the log file

C:\Program Files\Common Files\Cisco\Logs\mscosupg.log

11:48:00-MCSOSUP|End modSP3
SaveRegistryValueString: Saved value
                |  ce\zzzzMCSOSUpg
11:48:00-MCSOSUP|Phase 2 of 3 upgrade 
complete. Attempting shutdown

Manually start Phase 3 with the following command:

C:\Mcsosupg\Mcsosupg.exe /Postboot


Directory search on the console returns an error.

User gets the error that a user is not found when searching for a name in the directory search area. This happens when the directory search has not executed for some time. The message gets displayed for the first two attempts. The directory search succeeds on the third attempt.

Workaround: Repeat the search.


Unanswered parked call does not get reversed.

An IP phone places a call to PSTN and the call is connected. The IP phone then parks this call. If the parked call is not retrieved by another phone after 60 seconds, the parked call does not get reversed back to the IP phone. The PSTN caller receives a fast busy signal.

Workaround: Define and apply calling party transform mask in the Route List or in the "Caller ID DN" field in the gateway configuration.


Shortcuts in the Start Menu do not get installed.

The name for the Program folder gets translated in other languages.

Workaround: Manually add the Shortcuts in the Programs folder.


NewCall and EndCall softkeys should not be mandatory.

The administrator cannot remove NewCall or EndCall from a softkey template.

Workaround: None exists.


Auto answer gets triggered on a IP phone during a ringout

Workaround: None exists.


The listRoutePlanByType AXL method causes a memory leak.

Workaround: None exists.


ART automatic purge goes into infinite looping when a large number of records in the database are deleted.

Workaround: None exists.


Cisco CallManager sends wrong MDCX to the gateway.

User cannot make g729 intercluster calls.

Workaround: Set both sides of ICT to 729.


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

Workaround: None exists.


Cisco Tomcat Service and Cisco Customer Response Solution (CRS) use the same default port of 8080.

Cisco Tomcat Service and Cisco Customer Response Solution (CRS) use the same default port of 8080. In other instances, Cisco Tomcat Service fails when there is another service using port 8998.


1. Reconfigure Cisco Customer Response Solution and Cisco Personal Assistant to use different ports.

2. Open the file C;\Program Files\Cisco\Tomcat\conf\server.xml in a text editor, such as notepad or wordpad, search for '8998', replace it with another port number not in use, and save the file. Restart the Cisco Tomcat Service.


Cisco CallManager loses communication with VG200 when doing MGCP PRI backhaul.

When MGCP PRI backhaul is configured between an IOS gateway and a Cisco CallManager server, a race condition exists that the server does not handle correctly when the server loses and then regains the TCP backhaul link to the gateway while calls are still active.

Workaround: Reload the gateway or configure the gateway with no MGCP.


Phone registration with TAPS fails in Active Directory or Netscape Directory.

Workaround: None exists.


CAR reports same call twice in the Gateway Detail Report.

Workaround: None exists.


Searching for a user in Cisco Callmanager Administration fails when Netscape is used.

You cannot perform subsequent user searches by using Netscape browser.

Workaround: Close and Restart Netscape to perform another search.


Route Filter with no value gets inserted.

Insert a route filter with a clause that contains the condition as '= =' and some valid value in the input box. After clicking the Insert button, delete your input in the input box and click the Update button. Error message displays and asks the user to give a valid value for the input box. Click Ok 'button. Click Update button again. The route filter gets inserted.

Workaround: Provide valid value in the input field.


AXLAPI.wsdl has a schema error.

Workaround: None exists.


Cisco CallManager server display "AAREnable - cannot find entry" error in the trace file.

This error occurs during Cisco CallManager startup.

Workaround: Go to Cisco CallManager Administration->System->Enterprise Parameters, and click update.


Default fax Payload Size is set too small, and FDL Channel parameters are missing.

Workaround: None exists.


Auto download of configuration file from TFTP server for IOS MGCP gateway fails for Cisco CallManager Version 3.3.

Manual MGCP configuration works.

Workaround: None exists.


CTI manager ignores the exception thrown by CTI device list.

The applications stop getting lines from CTI manager.

Workaround: Restart the CTI manager.


Administrators cannot access Cisco CallManager Administration.

This happens when the server is not on the network.

Workaround: Add the server to a workgroup or domain.


Web services fail after you get an error from trying to attach a user to a device profile.

When you add a new Device profile and get the error message "Error getting user login ID," you cannot use the global directory page. You get the error, "Active Server Pages error ASP 0115."

Workaround: Restart IIS Administrative Services.


Callback does not work when users call a Cisco IPMA enabled manager phone.

Workaround: None exists.


AXL addRoutePattern automatically enables "Use Calling Party's External Phone Number Mask."

When you insert a route pattern by using AXL addRoutePattern, the check box "Use Calling Party's External Phone Number Mask" gets checked by default.

Workaround: Uncheck the "Use Calling Party's External Phone Number Mask" check box in Cisco CallManager Administration.


User's Alarm definitions Cisco CallManager got deleted during upgrade.

Workaround: None exists.


The help menu for Service Parameter (DB debounce timer) has an inadequate description.

Workaround: None exists.


CallEvent for held call did not get sent.

Workaround: None exists.


Translation Pattern does not work.

Calls received from a gateway do not properly match translation patterns in the database for the Cisco CallManager cluster.

The cluster contains the pattern 37[1-8]524XXXX.

The incoming called number was 3745240001. The pattern match failed.

Workaround: None exists.


Cisco CallManager does not use Media Termination Points (MTP) in Intercluster Trunks (ICT) call.

Cisco CallManager does not support two intercluster trunks between the same server on two clusters.

Workaround: Do not configure two intercluster on Cisco CallManager servers that are in two different clusters.


RouteEndEv does not get sent if Call Forward No answer is used in Route Point.

Workaround: None exists.


RTMT directory monitoring has a memory leak.

There is a 0.4Mb memory lost per day when you enable directory monitoring.

Workaround: Turn off directory monitoring.


IP phone identifies the wrong value for Cyrillic character set.

Cisco CallManager database contains an error in the name for the character set encoding that is used for Cyrillic text in the Russian User Locale. The incorrect information gets passed to web sites that hosts IP Phone Services. Some services may not function correctly or may not return correct data because of the incorrect encoding.

Workaround: None exists.


Cisco CallManager crashed during a location-to-location call.

Workaround: None exists.


Cisco CallManager has high CPU usage when user accesses LDAP search.

The value for the User Search Limit in the Enterprise Parameter is set > 500.

Workaround: Set User Search Limit value to 64.


After upgrading Cisco CallManager, a directory search does not return any results.

The new enterprise parameter, Enable All User Search that determines whether the user directory search should be enabled, is set to FALSE.

Workaround: Set Enable All User Search enterprise parameter to TRUE.


The voice mail profile does not scale when configuring directory numbers.

You cannot load the Directory Number Configuration page when there are over 5000 voice mail profiles.

Workaround: None exists.


Destination type unknown gets sent in the proceeding event message.

When you make a call across a gateway that does not support ringback, CTI cannot pass the far end information in the ring back state.

Workaround: None exists.


Calls to Customer Response Application (CRA) Auto Attendant fail.

Workaround: None exists.


Non-Cisco CallManager subscriber server have active Call Detail Records (CDR) threads.

Workaround: None exists.


The fourth party conference call fails after the call is resumed from a hold in OnHoldPendConf.

Workaround: None exists.


Version field does not migrate correctly.

Locale installer displays a message that it is downgrading the locale version when it is actually upgrading.

Workaround: You can ignore the message.and continue with install of the new locale.


SQL server has a shared memory leak.

This happens when you enable the shared Memory option in SQL.

Workaround: Disable the Shared Memory option by setting the value of the following registry key to "0" (zero) on all the servers and reboot the servers: HKLM\SOFTWARE\Microsoft\MSSQLServer\Client\SharedMemoryOn


Route point does not get the offering event on incoming call after a CTI failover.

Route point does not get the offering call state on incoming call when CTImanager stops and fails over.

Workaround: Restart CCM.exe.


User experiences intermittent loss of sound on the Cisco IP Conference Station 7935

Workaround: None exists.


Redirected calls from a CTI route point fail.

Calls redirected from a CTI route point result in a TAPI error LINEERR_INVALCALLSTATE.

Workaround: None exists.


Cisco-IP PBX Service Provider displays duplicate language names in the Japanese version of Windows98SE.

Cisco-IP PBX Service Provider displays three lines of German, two lines of Norwegian, and two lines of Portuguese in the language drop-down list on the Japanese version of Windows98SE.

Workaround: Install Pan-European Text Display Support in the Multi-language Support bundle with Internet Explorer 5.5+SP2 or Internet Explorer 6.0.


Cisco CallManager does not display changed attributes for a phone when you reset from the phone.

Workaround: None exists.


Cisco CallManager user options page does not display the phone online help link.

Workaround: None exists.


Some Cisco CallManager servers fail to pull subscription from a publisher server when 10 nodes are upgraded.

Subscription pull fails when multiple subscribers get upgraded simultaneously.

Workaround: Upgrade one Cisco CallManager server at a time.


TFTP unexpectedly restarts.

Workaround: None exists.


Cisco CallManager installation does not prompt users to choose correct NIC configuration for their network configuration.

Workaround: None exists.


Administration Utility for changing password should not run on subscriber servers.

Workaround: None exists.


You cannot update the add-on modules by using AVVID XML Layer (AXL).

Workaround: None exists.


RingDisabled returns a non-Boolean value.

Workaround: None exists.


Cisco IPMA manager does not support extension mobility mobile manager.

This situation occurs when the extension mobility manager logs into the same device again.

Workaround: Restart Cisco IPMA Service by restarting the Cisco Tomcat service using Microsoft Windows Administrative tools.


Administration utility displays error message when the administrator tries to change the password to default for all the users.

The error message displays after the user passwords get changed on publisher server but before they get changed on the subscriber server.

Workaround: Click OK, and the utility continues.


Administration utility needs documentation.

Workaround: None exists.


Administration utility has incorrect message sequence if the user enters an incorrect password.

Workaround: Click OK and login again.


Internet Information Server (IIS) stops working on a Cisco CallManager server.

When the failure first occurs, users get an IIS error code 500. If IIS continues to receive get requests for the failing virtual directory, then IIS stops servicing requests and does not log any get or post requests to the w3svc logs.

This happened on a server hosting services and directories for over 6000 phones.


Stop and restart the IIS Administrative Service.

If IIS or World Wide Web publishing fail to start, perform the following tasks:

1. Change IIS Administrative Service startup type to disabled.

2. From a cmd prompt, cd to c:\utils. Enter the command 'kill inetinfo.exe' without the quotes.

3. Change the IIS Administrative Service startup type back to automatic.

4. Start the IIS Administrative Service and World Wide Web Publishing Service.


Administration utility hangs when subscriber server cannot be reached.

The administration utility repeats the same messages when you click OK.

Workaround: Use Windows task manager and delete the AdminUtility.exe process.


You cannot install or upgrade the subscriber server without a name entry for the publisher server in the local DNS or host file.

Workaround: None exists.


The administration utility incorrectly reports a successful password change on the subscriber server.

The administration utility shows that the password on the subscriber has been updated even if the subscriber goes down during the update process.

Workaround: None exists.


Parking a call on hold takes eight seconds.

This happens when two phones are on a call and the first phone places the call on hold and then the second phone places the call on hold, resumes the call, and then parks the call.

Workaround: None exists.


Call Park reversion fails when you transfer a call that is initiating a conference.

Workaround: None exists.


Cisco CallManager Release 3.3 has higher CPU and memory usage.

Workaround: None exists.


Installation logs do not show subscription pull failures.

This situation occurs when you upgrade multiple Cisco CallManager servers.

Workaround: Check the replication monitor in the SQL database to see if the subscriber is pulling the database.


Administrators cannot open QRT logfiles.

Workaround: None exists.


MGCP T1 PRI gateways do not use all channels after a failover.

Calls do not get tracked correctly when a Cisco CallManager server has a failover. When the gateway reregisters to the primary Cisco CallManager, not all channels of the T1 PRI get used. This happened on a WS-6608 T1 gateway registered to a Cisco CallManager server on Release3.2(2c).

Workaround: Reset the gateway from Cisco CallManager Administration.


Cisco IP Phone locks up and MGCP endpoint unregisters when they share a line.

MGCP endpoint unregisters with a Cisco CallManager server under the following situation:

1. Call comes in on a line that is shared between a MGCP endpoint and an IP phone.

2. IP phone picks up the call, places it on hold, and resumes the call.

3. MGCP endpoint goes off hook.

When the call ends, the MGCP endpoint has unregistered with the Cisco CallManager server.

IP phone locks up under the following situation:

1. Call comes in on a line that is shared between a MGCP endpoint and an IP phone.

2. IP phone picks up the call and places it on hold.

3. MGCP endpoint goes off hook and then back on hook.

Workaround: To register the MGCP endpoint, reset the gateway. Resetting the MGCP endpoint does not work. To unlock the phone, reset the IP phone.


The wrong phone rings during callpark reversion when the call is parked after it is transferred.

This happens under the following scenario:

Phone-A and Phone-B are connected.

Phone-B transfers the call to Phone-C.

Phone-C parks the call.

After the CallParkReversionTimeout, Phone-B rings instead of Phone-C.

Workaround: None exists.


The tag for getGatewayEndpointResponse returns a value in the incorrect format.

It does not have the expected curly brackets {}.

Workaround: None exists.


GetGatewayEndPoint returns the <line> tag without an index attribute.

Workaround: None exists.


When you configure the Cisco VG200 as a Media Termination Point (MTP) and mask the codecs for G729br8, G729abr8 and G729ar8, incoming calls from a Catalyst 6000 WS-6608 module do not go through.

Workaround: Do not mask Codecs on a Cisco VG200 MTP.


A TAPI application cannot retrieve a user controlled device.

Workaround: None exists.


Call Detail Records (CDRs) do not get written to the CDR database.

This happens after upgrading to Cisco CallManager Version 3.2(2c)spE. You find errors in the CDR trace.

Workaround: Edit the OffCluster Data Source Name (DSN) and restart InsertCDR Service.

For Release 3.2:


For Release 3.3



CFA fails when you restart devices from Cisco CallManager Administration.

Workaround: None exists.


Subscriber servers display error message when you use Cisco CallManager Service Activation.

You get a popup message "You must install CallManager using CCMSetup.exe."

Workaround: Click "OK. " When the same popup appears a second time, click "OK" again. The popup message does not appear again.


Cisco Database Layer Monitor service does not restart automatically after the Cisco CallManager server is rebooted.

Cisco CallManager server displays a message "At least one service/driver has failed to restart, check event log for details."

Workaround: Use Windows Administrative Tools to change Cisco Database Layer Monitor service from Automatic to Manual. Reboot the server and start the service manually.


Music-on-Hold servers do not send packets with the correct quality of service (QoS) information.

Cisco CallManager server only includes QoS information on packets sent on port 2000.

Workaround: None exists.


User reports display an incorrect title, description, and help file.

The user report for CTI Application users is incorrectly titled CTI Port. The description should include users who do not have CTI ports such as Cisco IPMA users. The wrong help file gets displayed.

Workaround: None exists.


Cisco DB Layer Monitor service does not get activated.

This situation occurred on a Cisco CallManager server, Release 3.3 with Cisco Customer Response Solution Version 3.0(2).

Workaround: Change Cisco DB Layer Monitor service to manual and reboot the server.


Cisco CallManager Administration displays CTI framework as a user.

Cisco CallManager Administration displays the user ctifw when you search with an empty user search field.

First Name: CTI

Last Name: Framework

Userid: ctifw

This happens when you upgrade from 3.1 or 3.2 to 3.3(2). Cisco CallManager Release 3.3 filters out system users and special users in search results when the Description field is CiscoPrivateUser.

Workaround: The description field for user, ctifw, did not get set after restoring the data. Run the following command to set the description field.

ldapmodify -h <server name> -p 8404 -D "cn=Directory Manager,o=cisco.com" -w <DCDAdmin Password> -c -f <input file>

The filename with full path should be specified in -f option and have the following contents:

dn: cn=CTI Framework,ou=users,o=cisco.com

changeType: modify

replace: Description

Description: CiscoPrivateUser


IP phone gets the wrong callback notification when it calls a connected phone.

Workaround: None exists.


The password utility does not work when the computer name is 15 characters.

Workaround: Assign a computer with less than 15 characters prior to installing Cisco CallManager.


Cisco AS-8 gateway fails to register with the Cisco CallManager server.

Workaround: None exists.


The service URL for Cisco IP Conference Station 7935 is missing in the cnf.xml file.

Workaround: None exists.


Assistant console client cannot log in.

This situation happens after a failover with a large number of assistants logged in.

Workaround: Restart the IMPA service (Cisco Tomcat Service).


Blind transfer failure error message does not get displayed on the assistant console.

This situation happens occasionally when an assistant logs out and back in again.

Workaround: Exit the console and relaunch the application.


You cannot drag and drop entries from the speed dial or directory on to toolbar panel.

Workaround: Use the menu or right click the mouse to transfer a call by using speed dial or directory.


Cisco CallManager servers crash when a conference bridge sends negative active streams.

Workaround: None exists.


Assistant console closes without displaying any errors.

An assistant, who is associated to more than one manager, cannot log in to the console when you restart the Cisco IPMA server after deleting a manager that is associated with the assistant.

Workaround: Update the assistant association when you delete the manager.


You cannot upgrade existing Cisco Attendant Console client by using the Attendant Console Help Upgrade menu option.

Workaround: Uninstall the existing client first. Install Attendant Console by using Cisco CallManager Administration ->Application -> Install Plugins.


Cisco CallManager sends incorrect message ordering for intercluster calls.

Workaround: None exists.


IP phone does not display CiscoIPPhoneImage XML object.

This happens on an idle Cisco IP Phone 7940 or 7960 and the phone retrieves a CiscoIPPhoneImage object with the IDLE URL or the phone respond to a HTTP Push request.

Workaround: Set the Image object to return a HTTP Refresh header. This forces the page to be immediately reloaded.

The following firmware caveats apply to this release.


Cisco 30VIP phones does not play multicast, external audio files.

When you use a CD player as an external source for multicast audio file and a Cisco IP Phone puts a on a Cisco IP Phone model 30VIP, the Cisco IP Phone model 30VIP does not play music on hold.

Workaround: Do not configure the MOH server music streams to use more than five IP ports for a single IP address. The phone cannot handle ALL the streams associated with one IP address.


The D-channel does not come up after Cisco CallManager sends a reset to a WS-6608 E1.

When Cisco CallManager sends a reset to an E1 port on a 6608, the D-Channel does not come up.

Workaround: Physically remove the E1 connector and plug it back in.


The LCD display for Cisco IP Phone 7936 is too small to support IP phone services.

Workaround: None exists.


The LCD display on the Cisco IP Conference Station 7935 is too small to support IP phone services.

Workaround: None exists.


Audio path does not get created between an IP phone and a Symbol phone when transcoder is used.

The G.723 bandwidth gets established between a Cisco IP Phone 7960 (IP Phone 1) and a Symbol phone. When IP phone 1 calls Symbol phone, the transcoder resources get allocated, but no audio path exists.

Workaround: None exists.


The status in the Assistant Watch window does not display correctly in Japanese.

This situation only occurs when you specify the managers user locale as Japanese.

Workaround: Specify "United States" as user locale for managers.


A WS-6608 with T1-CAS in the CSEmWaitFeOffHookOr2ndWink state disconnects a call after 65 seconds if the call is not answered.

Workaround: None exists.


Calls on WS-X6608 T1/PRI experience delayed ringback.

User experiences an approximate 8-second delay in receiving ringback.

Workaround: Reboot the T1 switch.


WS-X6608 and WS-X6624 do not re-enable the echo canceller upon detecting V.21 flags.

Fax transmissions fail because the echo canceller is disabled when it should remain enabled for a standard G3 Fax transmission.

Workaround: None exists.


WS-6608E1 could not negotiate fax relay with ECM turned on.

Workaround: Turn ECM off.


Modem calls fail when WS-6624 and WS-6608 are configured for G.711 or G.729 and the SVC-CMM module is configured for g.729.

Workaround: None exists.


WS-X6624 does not mark MGCP keepalive packets properly for Cisco CallManager servers.

Workaround: None exists.


WS-X6608 does not mark MGCP keepalive packets properly for Cisco CallManager servers.

Workaround: None exists.


WS-6624-FXS does not mark QOS packets properly for RTP streams for IP phones.

Workaround: None exists.


WS-6608-T1 does not mark QOS packets properly for RTP streams for IP phones.

Workaround: None exists.


Assistant phone resets when caller ID is greater than 24 Japanese characters.

The assistant phone reset when it received a call for a manager, and the caller ID is longer than 24 Japanese (Hankaku-Katakana) characters.

Workaround: Specify a display ID of less than 24 characters.


Cisco IP Conference Station 7935 stops working when you upgrade to Cisco CallManager 3.3(2).

This happens when you use a script to limit the devices that can go into the voice VLAN and you are upgrading to Cisco CallManager 3.3(2) and the Cisco IP Conference Station 7935 is using firmware version P005A302-P005C302. The Cisco IP Conference Station 7935 stays in a configuration state.

Workaround: To prevent this from happening, you can upgrade to firmware P00503010100 before upgrading to Cisco CallManager Release 3.3(2).

To recover the phone, you must create a scope on the router with the correct option 150. Place the port that the Cisco IP Conference Station 7935 is connected to into the VLAN. The phone will register with the Cisco CallManager server. You can leave the scope as is or force it into the voice VLAN. The auxiliary port will no longer work on the Cisco IP Conference Station 7935.


IP phone loses dial tone when you send it multicast audio or text messages.

This happens on phones using firmware p00303030200.

Workaround: Reset the phone.

Documentation Updates

This section provides documentation changes that were unavailable when the Cisco CallManager Release 3.3(2) documentation suite was released.


This section contains changes that have occurred since the original release of the Cisco CallManager Administration Guide Release 3.3. These changes do not currently appear in the Release 3.3 Cisco CallManager Administration Guide or the online help for the Cisco CallManager application.

Cisco Call Back Service Name Change

The service name for the call back feature that appears in the Cisco CallManager Systems Guide, Cisco CallManager Serviceability System Guide, and Cisco CallManager Serviceability Administration Guide as Cisco Call Back Service has been changed to Cisco Extended Functions.

Cisco Catalyst 6000 E1 VoIP Gateway Configuration

Cisco CallManager Gateway Configuration for the Catalyst 6000 E1 VoIP Gateway has changed some fields to accommodate continuous channel numbering.

The Channel IE Type field now contains the following options:

Timeslot Number (replaces Number)

Slotmap (not changed)

Use Number when 1B (not changed)

Continuous Number (new)

Cisco CallManager System Guide

The following section contains information that was not included in the Managing User Directory Information chapter of the Cisco CallManager System Guide.

Configuring Enterprise Parameters for User Search

To limit the search time for accessing users in the corporate directory and to reduce overhead for Cisco CallManager, set one of two enterprise parameters. The parameters apply to the user search from the Cisco CallManager User window and from the Cisco IP Phone directories button.

Enterprise Parameter Enable All User Search

This parameter specifies False by default. The False setting requires that a user search the corporate directory by entering search criteria (e.g., first name, last name, DN).

If the parameter is set to True, the system allows searches without search criteria, and this method could cause performance degradation of Cisco CallManager.

Enterprise Parameter User Search Limit

By default, this parameter specifies 64 search results at a time. This parameter remains invalid if the Enable All User Search parameter is set to False.

A value of 1 represents the minimum value for this parameter. A value higher than 500 could cause performance degradation of Cisco CallManager.


This section lists new and additional information that is not included in the current Cisco CallManager documentation.

Additional Counters

Cisco CallManager Release 3.3 includes the Cisco CallManager System Performance object. The counters within the Cisco CallManager System Performance object provide system performance information. They are available for use with Microsoft Performance counters and Cisco CallManager Real-Time Monitoring tool (RTMT):

QueueSignalsPresent 1 through QueueSignalsPresent 4

QueueSignalsProcessed 1 through QueueSignalsProcessed 4

EngineeringCounter1 through EngineeringCounter8

Obtaining Documentation

The following sections provide sources for obtaining documentation from Cisco Systems.

World Wide Web

You can access the most current Cisco documentation on the World Wide Web at the following sites:




Documentation CD-ROM

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

Ordering Documentation

Cisco documentation is available in the following ways:

Registered Cisco Direct Customers can order Cisco Product documentation from the Networking Products MarketPlace:


Registered Cisco.com users can order the Documentation CD-ROM through the online Subscription Store:


Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco corporate headquarters (California, USA) at 408 526-7208 or, in North America, by calling 800 553-NETS(6387).

Documentation Feedback

If you are reading Cisco product documentation on the World Wide Web, you can submit technical comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco.

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

To submit your comments by mail, use the response card behind the front cover of your document, or write to the following address:

Attn: Document Resource Connection
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-9883

We appreciate your comments.

Obtaining Technical Assistance

Cisco provides Cisco.com as a starting point for all technical assistance. Customers and partners can obtain documentation, troubleshooting tips, and sample configurations from online tools. For Cisco.com registered users, additional troubleshooting tools are available from the TAC website.


Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information and resources at anytime, from anywhere in the world. This highly integrated Internet application is a powerful, easy-to-use tool for doing business with Cisco.

Cisco.com provides a broad range of features and services to help customers and partners streamline business processes and improve productivity. Through Cisco.com, you can find information about Cisco and our networking solutions, services, and programs. In addition, you can resolve technical issues with online technical support, download and test software packages, and order Cisco learning materials and merchandise. Valuable online skill assessment, training, and certification programs are also available.

Customers and partners can self-register on Cisco.com to obtain additional personalized information and services. Registered users can order products, check on the status of an order, access technical support, and view benefits specific to their relationships with Cisco.

To access Cisco.com, go to the following website:


Technical Assistance Center

The Cisco TAC website is available to all customers who need technical assistance with a Cisco product or technology that is under warranty or covered by a maintenance contract.

Contacting TAC by Using the Cisco TAC Website

If you have a priority level 3 (P3) or priority level 4 (P4) problem, contact TAC by going to the TAC website:


P3 and P4 level problems are defined as follows:

P3—Your network performance is degraded. Network functionality is noticeably impaired, but most business operations continue.

P4—You need information or assistance on Cisco product capabilities, product installation, or basic product configuration.

In each of the above cases, use the Cisco TAC website to quickly find answers to your questions.

To register for Cisco.com, go to the following website:


If you cannot resolve your technical issue by using the TAC online resources, Cisco.com registered users can open a case online by using the TAC Case Open tool at the following website:


Contacting TAC by Telephone

If you have a priority level 1 (P1) or priority level 2 (P2) problem, contact TAC by telephone and immediately open a case. To obtain a directory of toll-free numbers for your country, go to the following website:


P1 and P2 level problems are defined as follows:

P1—Your production network is down, causing a critical impact to business operations if service is not restored quickly. No workaround is available.

P2—Your production network is severely degraded, affecting significant aspects of your business operations. No workaround is available.

[an error occurred while processing this directive]