Guest

Cisco Unified Communications Manager (CallManager)

Release Notes for Cisco CallManager Release 3.3(4)

 Feedback

Table Of Contents

Release Notes for Cisco CallManager Release 3.3(4)

Contents

Introduction

System Requirements

Determining the Software Version

Compatibility Matrix and Supported Upgrades

Related Documentation

New and Changed Information

Forced Authorization Codes and Client Matter Codes

Cisco WebDialer

Cisco IP Telephony Backup and Restore System (BARS)

New and Updated Phone Support

Extension Mobility Enhancements

Cisco Security Agent

Dialed Number Analyzer (DNA)

Image Authentication

NM-HDV2 and NM-HD Support for Cisco CallManager

Conferencing Enhancements

Block External To External Transfer Service Parameter

International Dial Plan

Calling Search Space Enhancements

Default Trace Level Changed for Cisco Database Layer Monitor Service

Important Notes

Application Error During an Upgrade

Adding Cisco CallManager Servers

Using the Ping Command During Installation

Locale Installer for Cisco CallManager Release 3.3(4)

MLA for Cisco CallManager 3.3(4)

Cisco CallManager Renamed After Restarting Services

VirusScan on Cisco CallManager Servers

Region Configuration

QSIG Support

Supported Characters in the Directory

Cisco CallManager Integration with Corporate Directories

Installing IPMA Assistant Console on Microsoft Windows XP

Cisco VG248 Analog Phone Gateway (VG248) Support

Changing User IDs

Settings Access on Cisco IP Phone 7940/7960

Cisco CallManager Attendant Console

Upgrading Cisco CallManager Extension Mobility

End User Notes

Attendant Console

Ring Settings

Cisco IPMA

User Login Name and Password

Phone Hardening

Resolved Caveats for Cisco CallManager - Release 3.3(4)

Open Caveats for Cisco CallManager - Release 3.3(4)

Documentation Updates

Errors

Locale Installer

Microsoft Outlook Support with Cisco WebDialer

Changes

Cisco CallManager Attendant Console

Calling Search Space

Cisco CallManager Extension Mobility Logout

Custom Phone Rings

Omissions

New Service Parameter for Cisco CallManager Extension Mobility

H.323 Configuration Settings

Defining the Quality of Service (QoS) Values

Quality Report Tool Configuration Settings

Exporting and Importing Phones with More Than One User

Device Profile Default Configuration

Subscribing Services to a Device Profile Default

User Settings in Cisco CallManager Administration

Obtaining Documentation

Cisco.com

Ordering Documentation

Documentation Feedback

Obtaining Technical Assistance

Cisco Technical Support Website

Opening a TAC Case

TAC Case Priority Definitions

Obtaining Additional Publications and Information


Release Notes for Cisco CallManager Release 3.3(4)


June 28, 2004

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

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

To access the documentation suite for voice products, refer to

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

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

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

Contents

These release notes discuss the following topics:

Introduction

System Requirements

Compatibility Matrix and Supported Upgrades

Related Documentation

New and Changed Information

Important Notes

Resolved Caveats for Cisco CallManager - Release 3.3(4)

Open Caveats for Cisco CallManager - Release 3.3(4)

Documentation Updates

Obtaining Technical Assistance

Introduction

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

System Requirements

Make sure that you install and configure Cisco CallManager Release 3.3 on a Cisco Media Convergence Server (MCS) or on a Cisco Integrated Communications System (ICS) 7750.

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


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

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

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

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(4) 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 Release 3.3(4). For the most current compatibility combinations and defects, refer to the documentation that is distributed with the Cisco IP telephony products.


Related Documentation

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

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

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

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's Guide for Cisco CallManager 3.3(3)

Cisco CallManager 3.3 TAPI Installation Guide

Cisco TAPI Developer's Guide for Cisco CallManager 3.3(3)

Cisco CallManager Extension Mobility API Developer's Guide

System Error Message

New and Changed Information

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

Forced Authorization Codes and Client Matter Codes

Forced Authorization Code (FAC) and Client Matter Code (CMC) allow you to manage call access and accounting. CMC assists with call accounting and billing for billable clients, while FACs regulate the types of calls that certain users can place.

Client Matter Codes force the user to enter a code to specify that the call relates to a specific client matter. You can assign CMC to customers, students, or other populations for call accounting and billing purposes. The Forced Authorization Code feature forces the user to enter a valid authorization code before the call completes.

The CMC and FAC features require that you make changes to route patterns and perform configuration tasks for CMC and FAC in Cisco CallManager Administration (Choose Feature > Client Matter Code or Feature > Forced Authorization Code).

You can use BAT to insert, update, and delete CMC and FAC and CDR Analysis and Reporting (CAR) to run reports that provide call details for authorization code names, authorization levels, and CMCs.


Caution When you enable FAC or CMC in route patterns, applications that do not pass the FAC or CMC code cannot complete a call. The call times out and fails. This affects all applications, such as Cisco Customer Response Solutions (Cisco CRS) that pass calls through a route pattern with FAC or CMC enabled. You must use a route pattern with FAC and CMC disabled or configure the application to pass the FAC or CMC code that was entered by the user to Cisco CallManager. Refer to the application's documentation to find out how you can configure your application to support FAC/CMC.


Note In the Cisco CallManager 3.3(4) release, CTI does not support the tones that are associated with FAC/CMC; if a user places a call through a TAPI or JTAPI application that uses a FAC/CMC-enabled route pattern, the call times out and fails. Cisco strongly recommends that you do not configure FAC/CMC-enabled route patterns for any 3.3(4) compatible TAPI or JTAPI application, including Cisco-supported or Cisco-approved, third-party applications (for example, IVR, SoftPhone, etc.).


How This Feature Affects the User

When enabled, these features force the user to enter a valid account code or authorization code before the call completes. A distinctive tone prompts the user.

You should tell affected end users how to recognize the audio prompts, and the codes that users need to enter, as well as the consequences or symptoms that are associated with failing to enter a valid code.

Currently, the end-user documentation does not contain any instructions about how to use these features.

Where to Find More Information

Cisco CallManager Features and Services Guide

Bulk Administration Tool User Guide

Cisco CallManager Serviceability Administration Guide

Cisco CallManager Serviceability System Guide.

Cisco WebDialer

Cisco WebDialer allows Cisco IP Phone users to make telephone calls by using web and desktop applications. When you enable your company directory search page by using Cisco WebDialer, a user can make calls by clicking a hyperlinked telephone number.

In Cisco CallManager 3.3(3), users obtains Cisco WebDialer as a download from www.cisco.com. In Cisco CallManager 3.3(4), Cisco WebDialer exists as a service in Cisco CallManager Serviceability.

How This Feature Affects the User

Some current versions of model-specific user guides do not mention Cisco WebDialer features—even though the phone supports these features and the feature might be accessible to end users. Refer users to Customizing Your Cisco IP Phone on the Web for instructions on using these features.

Where to Find More Information

Cisco CallManager Features and Services Guide

Cisco IP Telephony Backup and Restore System (BARS)

Cisco CallManager 3.3(4) uses the Cisco IP Telephony Backup and Restore System (BARS) for backup and restore operations, including backing up data, restoring data, and restoring servers. This application, which you can use for manual or scheduled backups, supports compatible versions of Cisco CallManager, Cisco Emergency Responder, Cisco Customer Response Applications/Solutions (CRA/CRS), and Cisco CDR Analysis and Reporting (CAR).

Where to Find More Information

Cisco CallManager Compatibility Matrix to identify which version of BARS supports this version of Cisco CallManager

Cisco IP Telephony Backup and Restore System (BARS) documentation that supports this version of Cisco CallManager.

New and Updated Phone Support

The following information describes new and updated phone support for this Cisco CallManager release. The applicable documentation may not provide the following information.

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

Cisco CallManager 3.3(4) supports Cisco IP Communicator, a Skinny Client Control Protocol (SCCP) based desktop application that turns your computer into a full-featured Cisco IP Phone.

Cisco CallManager Attendant Console supports Cisco IP Phone Models 7902, 7905, 7912, 7940, 7960, and 7970.

Cisco CallManager allows you to tighten security on certain phones by disabling phone settings in Cisco CallManager Administration.

Cisco CallManager supports phone image authentication.To identify which phones support image authentication, see "Image Authentication" section.

Where to Find More Information

Cisco IP Conference Station 7936 Administration Guide

Cisco Wireless IP Phone 7920 Administrator Guide

Cisco IP Phone 7970 Administration Guide for Cisco CallManager

Cisco IP Communicator Administration Guide

Cisco CallManager System Guide

Extension Mobility Enhancements

Cisco CallManager 3.3(4) extends Cisco CallManager Extension Mobility functionality to Cisco IP Phones 7905, 7912, 7970, and Cisco IP Communicator.

How This Feature Affects the User

Some current versions of model-specific user guides do not mention Cisco Extension Mobility—even though the phone supports these features are and the features might be accessible to end users. Refer users to Customizing Your Cisco IP Phone on the Web for instructions on using these features

Cisco Security Agent

Cisco CallManager 3.3(4) supports Cisco Security Agent with specific Cisco CallManager profiles. Cisco Security Agent provides host intrusion detection capability on Cisco CallManager servers.

Where to Find More Information

Cisco CallManager Compatibility Matrix to identify which version of Cisco Security Agent supports this version of Cisco CallManager.

Dialed Number Analyzer (DNA)

The Dialed Number Analyzer tool (DNA), an installable plug-in for Cisco CallManager, runs as a service on the server, and it allows you to test a Cisco CallManager dial plan configuration prior to deploying it or to analyze dial plans after the dial plan is deployed. You can use the results to diagnose a dial plan, to identify potential problems, and to tune a dial plan.


Note Cisco CallManager Dialed Number Analyzer does not support Netscape Navigator, version 4.61. Use Internet Explorer to analyze dial plans.


Where to Find More Information

Cisco CallManager Dialed Number Analyzer Guide

Image Authentication

Image authentication prevents tampering with the binary image; that is, the firmware load, prior to loading it on the phone. Tampering with the image causes the phone to fail the authentication process and reject the image. Image authentication occurs through signed binary files that are automatically installed with this version of Cisco CallManager. Likewise, firmware updates that you download from cisco.com also provide signed binary images.

Cisco IP Phone models 7970, 7960, 7940, 7912, 7910, 7905G, and 7902G support image authentication with Cisco CallManager Release 3.3(4).

NM-HDV2 and NM-HD Support for Cisco CallManager

In Cisco CallManager 3.3(4), NM-HDV2 and NM-HD, which support Cisco 2600XM, Cisco 2691, Cisco 3725, Cisco 3745, and Cisco Access Routers, can provide the following number of transcoder and conference sessions, which serve as the maximum number of sessions that are supported:


Tip Some supported gateways, for example, the Cisco 2600XM, cannot support the maximum number of sessions because of a CPU power limitation.

In addition to the preceding gateways, NM-HD supports the Cisco 3660.


Per NM-HDV2

G.711 only conference—50

G.729 conference—32

GSM FR conference—14

GSM EFR conference—10


Tip Maximum number of participants per conference equals eight.


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

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

Per NM-HD

G.711 only conference—24

G.729 conference—6

GSM FR conference—2

GSM EFR conference—1


Tip Maximum number of participants per conference equals eight.


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

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

To configure Cisco CallManager 3.3(4) transcoder and conference support for these modules, choose the following existing options in Cisco CallManager Administration:

For conference support, choose Cisco IOS Conference Bridge in the Conference Bridge Configuration window.

For transcoder support, choose Cisco IOS Media Termination Point in the Transcoder Configuration window.


Tip In Cisco CallManager Administration, ensure that you enter the same conference bridge name that exists in the gateway Command Line Interface. For specific information on configuring conference bridges and transcoders in Cisco CallManager Administration, refer to the Cisco CallManager Administration Guide that supports 3.3(4).



Caution To maintain full functionality in your network, you may need to perform additional configuration tasks on the supported gateway. For information on any additional tasks that you must perform, refer to the specific documentation for your gateway.

Conferencing Enhancements

Cisco CallManager Administration provides the clusterwide service parameter, Drop Ad hoc Conference When Creator Leaves, so you can drop ad hoc conferences after the conference controller hangs up the phone.

By default, Cisco CallManager sets the parameter to False. If you set the parameter to True, the conference automatically ends when the conference controller hangs up; likewise, Cisco CallManager releases all resources that are assigned to the conference. Be aware that Cisco CallManager does not support both options; that is, all conferences will support the same functionality depending on the option that you choose.


Tip If the conference controller transfers, parks, or redirects the conference to another party, the party that retrieves the call acts as the virtual controller for the conference. If you set the parameter to True and a virtual controller exists, the conference does not end until the virtual controller hangs up the phone.

A virtual controller cannot add new parties to the conference, but a virtual controller can transfer, park, or redirect the conference to another party, who would, in turn, become the virtual controller of the conference.


To change the value of the service parameter, perform the following procedure:

Procedure


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

Step 2 From the Server drop-down list box, choose a server in the cluster.

Step 3 From the Service drop-down list box, choose Cisco CallManager.

Step 4 From the Drop Ad hoc Conference When Creator Leaves drop-down list box, choose True.

Step 5 Click Update.


Block External To External Transfer Service Parameter

The Block External To External Transfer service parameter of the Cisco CallManager service allows administrators to prevent users from transferring external calls to another external number. This parameter specifies values as True or False. Setting the parameter to True blocks external calls from being transferred to another external device. The default value specifies False. You can modify the Block External To External Transfer service parameter in the Service Parameters Configuration window.

International Dial Plan

Cisco CallManager International Dial Plan provides country-specific dialing functionality for countries outside the North American Numbering Plan (NANP). The international dial plan includes route pattern wildcards, special characters, calling party transformation settings, and called party transformation settings that non-NANP dial plans use. It also describes the Discard Digit Instructions (DDIs) and tags that dial plans of specific countries use. Cisco CallManager currently supports international dial plans for Japan, the Netherlands, and Portugal.

Where to Find More Information

Cisco CallManager International Dial Plan Deployment Guide.

Calling Search Space Enhancements

Cisco CallManager 3.3(4) provides database enhancements for Calling Search Spaces, so you can make updates to Calling Search Spaces during regular business hours. Cisco removed the Restart Devices button from the Calling Search Space Configuration window in Cisco CallManager Administration because you do not need to restart the associated devices after you update a calling search space. To save your updates, remember to click Update after you make changes.

Default Trace Level Changed for Cisco Database Layer Monitor Service

In Cisco CallManager 3.3(4), the default trace level for the Cisco Database Layer Monitor service changed from Error to Significant.

If you change the default trace level before you upgrade the cluster to Cisco CallManager 3.3(4), your setting does not change after the upgrade. If you do not change the default trace level before the upgrade, the setting changes to Significant.

Important Notes

The following section contains important information that may not have been available in the initial release of documentation for Cisco CallManager Release 3.3(4).

Application Error During an Upgrade

When you upgrade to Cisco CallManager 3.3(4), you may encounter the following error message:

InsertCDR.exe - Application Error, The instruction at "0x10250fe7" referenced memory at "0x0000000". The memory could not be "read". Click OK to terminate program.

You should click OK to exit the dialog box and to continue with the installation of Cisco CallManager 3.3(4). Clicking OK does not terminate your installation; in fact, clicking OK will allow you to successfully upgrade your Cisco CallManager system.

Adding Cisco CallManager Servers

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

Using the Ping Command During Installation

The publisher database server serves as the master database for all servers in the cluster. All servers except the publishing database server maintain subscriber databases, which are copies of the publisher database server. If you are configuring a subscriber database server, make sure that the server that you are installing can connect to the publishing database server before the installation can continue. The installation process necessitates this connection, so the publisher database server can be copied to the local drive on the subscriber server. To make sure a good connection exists between the servers, issue a ping command from the subscriber server to the publisher database server before you try to authenticate to it. Use only a hostname (for example, `hostname.cisco.com') with the ping command. If the ping command is not successful, you must exit the installation program, fix the problem, and begin the installation process again.

The Installing Cisco CallManager Release 3.3(4) and Upgrading Cisco CallManager Release 3.3(4) documents incorrectly state to use a fully qualified domain name with the ping command.

Locale Installer for Cisco CallManager Release 3.3(4)

You can use Cisco IP Telephony Locale Installer version 3.3(3) with Cisco CallManager Release 3.3(4). Be aware that all phrases may not display in the desired locale when you install Locale Installer on a Cisco CallManager 3.3(4) system.

Refer to the readme file that is posted next to the Cisco IP Telephony Locale Installer software on www.cisco.com for the complete list of supported languages.

MLA for Cisco CallManager 3.3(4)

To maintain full multilevel administration access functionality in Cisco CallManager 3.3(4), you must use Cisco CallManager Multilevel Administration Access, Release 1.2(3). If you do not install Cisco MLA 1.2(3), you will only be able to log in to Cisco CallManager Administration with the administrator password.

Cisco CallManager Renamed After Restarting Services

If you deactivate the Cisco CallManager service in Cisco CallManager Serviceability, the Cisco CallManager where you deactivated the service no longer exists in the database. Hence, you cannot choose the Cisco CallManager for configuration operations in Cisco CallManager Administration because it will not display in the graphical user interface (GUI).

If you reactivate the Cisco CallManager service on the Cisco CallManager, the database creates a Cisco CallManager and adds a "CM_" prefix to the server name or IP address; for example, if you reactivate the Cisco CallManager service on a server with an IP address of 172.19.140.180, CM_172.19.140.180 displays in Cisco CallManager Administration. You can choose the new Cisco CallManager in Cisco CallManager Administration.

VirusScan on Cisco CallManager Servers

If you are using Microsoft Windows OS version 2000.2.4SR5 or 2000.2.5 with McAfee Netshield 2000 or McAfee VirusScan Enterprise Edition, you may encounter a problem authenticating to Cisco CallManager Administration or accessing some areas of Cisco CallManager Administration. Cisco CallManager displays an "HTTP Error 500-12 Application Restarting" error message.

To resolve this problem, you will need to upgrade McAfee Netshield and McAfee VirusScan to use VirusScan Engine Version 4.2.60 or later. You can obtain the latest Virus Scan updates from the Network Associates website.

Region Configuration

The Region Configuration window displays an Items per page drop-down list box that allows you to list 10, 20, 50, 100, or All configured regions. If you choose to display 100 or more regions, Cisco CallManager may experience performance degradation.

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. You can find a list of compatible gateways for which Cisco CallManager Release 3.3(4) has been tested at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/ccmcomp.htm

Supported Characters in the Directory


Caution Using non-ISO-Latin1 characters greater than 127 with DC Directory, Netscape Directory, or Active Directory can cause directory database errors. Cisco CallManager Release 3.3 supports all ISO-Latin1 (ISO-8859-1) characters and all non-ISO-Latin1 characters in the range 0-127 with any directory.

Cisco CallManager only supports ISO-Latin1 and ASCII characters in the User area of Cisco CallManager Administration.

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 ISO-Latin1 (ISO-8859-1) characters and non-ISO-Latin1 characters in the range 0-127 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 allowed character range, a dialog box displays and states that the user must enter data by using only ISO-Latin1 characters and non-ISO-Latin1 characters in the range 0-127.

CDR Analysis and Reporting (CAR) supports all ISO-Latin1 (ISO-8859-1) characters and non-ISO-Latin1 characters in the range 0-127.

Cisco CallManager Integration with Corporate Directories

If you have integrated Cisco CallManager with Active Directory or Netscape Directory, you must run the Cisco Customer Directory Configuration Plugin that is packaged with this release on all the Cisco CallManager servers in the cluster beginning with the publisher. You must complete this step after you have successful upgraded your Cisco CallManager server to Release 3.3(4). To ensure that Cisco CallManager can install the latest schema and new configuration information in the directory, you must enter a user, who has the rights to update the schema, in the Directory Administrator DN. For more information on installing the Cisco Customer Directory Configuration Plugin, refer to Installing the Cisco Customer Directory Configuration Plugin for Cisco CallManager Release 3.3.

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 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 when you are using the VG248 1.2(1) or earlier software, you must configure these settings locally on the VG248.

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

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

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

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

Changing User IDs

Cisco CallManager does not support changing an existing user ID in the directory. Some applications, such as Cisco IPMA and Extension Mobility, may not function properly when you change the user ID.

Settings Access on Cisco IP Phone 7940/7960

Users cannot access any button settings when you disable Settings Access for an individual Cisco IP Phone. This includes the settings to change ring type, volume level, and contrast level.

Cisco CallManager Attendant Console

Cisco CallManager Administration 3.3(4) provides the Cisco CallManager Attendant Console 1.2(1) plugin, although Cisco CallManager Administration Guide 3.3(4) and Cisco CallManager System Guide 3.3(4) support Cisco CallManager Attendant Console 1.1(3). To obtain documentation for attendant console 1.2(1), click the following URL: http://www.cisco.com/univercd/cc/td/doc/product/voice/attendnt/call_att/index.htm.

Upgrading Cisco CallManager Extension Mobility

If you run Cisco CallManager Extension Mobility and Cisco CallManager 3.1 or 3.2 before the upgrade, you must perform additional configuration tasks after the upgrade, so Cisco CallManager Extension Mobility runs as expected. For more information on configuration tasks, refer to the Cisco CallManager Extension Mobility upgrade section of the Cisco CallManager Features and Services Guide for 3.3.

End User Notes

The following section contains important information that affects the end user. Some features affect Cisco IP Phone end users but might not be included in model-specific documentation for the end user. Cisco suggests that 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.

Be aware that the Call Forward All to the voice mail icon and the Forward All to another directory number icon do not display in the Speed Dial window.

Ring Settings

The Ring Settings window, a new feature in the Cisco IP Phone User Options GUI, allows end users to assign distinctive ring tones to their phone line(s) from their computers. Users can access the Ring Settings window from the User Options main menu. The system administrator determines feature availability.

Cisco IPMA

Be aware that a Cisco IPMA assistant can support up to 33 proxy lines.

Be aware that a Cisco IPMA manager can have up to 10 assistants.

User Login Name and Password

Cisco CallManager supports only ISO-Latin1 (ISO-8859-1) characters and non-ISO-Latin1 characters in the range 0-127 in user login fields. This restriction affects services or applications that retrieve user login data from the Cisco CallManager database (such as the Cisco IP Phones, Cisco User Options, and the Cisco IPMA service).

If a user enters data that is not in the allowed character range, a dialog box displays and states that the user must enter data by using only ISO-Latin1 characters and non-ISO-Latin1 characters in the range 0-127. System administrators can advise end users who encounter this error message to enter a user name and/or password in only one of the following languages: Danish, Dutch, English, French, German, Italian, Norwegian, Portuguese, Spanish, Swedish, Hungarian, Polish, Greek, or Japanese.

Phone Hardening

Phone hardening options allow you to configure settings that restrict phone features and functionality for security purposes.

As part of phone hardening, you can disable user access to Cisco CallManager User Options and some phone settings (including those settings that are normally accessible via the Settings button). Because disabling access to these features will directly impact end users, you should advise affected users about the restrictions.

For more information about phone hardening, refer to the "Cisco IP Phone" chapter in Cisco CallManager System Guide.

End-user documentation mentions the possibility of restricted access to some settings; however, Cisco suggests that you provide more detailed information to users who are affected by phone hardening.


Note You configure phone hardening options in the Phone Configuration window of Cisco CallManager Administration. Phone hardening configuration options vary by phone model.


Resolved Caveats for Cisco CallManager - Release 3.3(4)

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


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

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


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

Identifier
Summary

CSCdv59928

Cisco CallManager does not remove a CTI device from an internal table when the CTI device unregisters.

CSCdv88850

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

CSCdx00431

CTI ignores indicator and displays incoming number instead of displaying a message indicating that the call is private.

CSCdy88595

The configuration file for IOS MGCP Gateway does not get updated when the endpoints are deleted.

CSCdz04480

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

CSCdz22424

Cisco Messaging Interface Service Parameters have incorrect definition.

CSCdz24796

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

CSCdz25060

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

CSCdz72286

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

CSCea01730

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

CSCea03795

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

CSCea11716

Cisco CallManager did not respond immediately to a clear MWI message.

CSCea13557

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

CSCea14510

DC directory replication fails when you upgrade a system that has a large database.

CSCea45346

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

CSCea52428

The connection list displays a connection when it should be empty.

CSCea53538

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

CSCea54802

H.323 inbound faststart intercluster call fails.

CSCea55522

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

CSCea59099

An external PSTN call stays in the queue after an attendant console transfer.

CSCea59673

Java Telephony Application Programming Interface (JTAPI) does not send a CallCtlConnEstablished event for an unmonitored device after a blind transfer.

CSCea62899

Cisco CallManager upgrade fails when DC Directory does not terminate properly.

CSCea72465

Services hang when you reboot a server.

CSCea78545

Cisco CallManager sends an incorrect disconnect cause code for the calls to locations where bandwidth is not available.

CSCea82254

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

CSCea83525

Call Detail Records (CDR) login fails when Cisco CallManager is integrated with Active Directory and Cisco CallManager Multilevel Administration Access.

CSCea84836

You cannot configure Authentication Proxy Rights on Cisco CallManager users page.

CSCea85171

The wrong event gets sent when you enable forward all on route points.

CSCea87355

Administrators get an error message when locations and CTI route points are added.

CSCea89916

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

CSCea90465

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

CSCea92986

The audio translator does not work on files in a remote directory.

CSCeb00216

Administrators cannot set default values on clusterwide service parameters.

CSCeb00463

Some queries in the route plan report return incorrect results.

CSCeb02342

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

CSCeb04068

You cannot enter SQL wildcard characters and bracketed expressions in the fields for a region search.

CSCeb09099

Cisco CallManager needs to update the object identifiers (OID) for labeledURI during the upgrade process.

CSCeb11140

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

CSCeb11416

JTAPI sends a CallCtlConnNetworkReachedEv message before a call can be completed.

CSCeb13814

Cisco CallManager services restart when a H.323 trunk is reset.

CSCeb15723

Call gets dropped on an intercluster trunk when a call is transferred to a CTI route point.

CSCeb15742

Cisco CallManager does not update conference bridge resources properly.

CSCeb22383

A shared-line phone's ring state is not synchronized after a blind transfer call.

CSCeb23273

Cisco CallManager does not check and validate some CTI service parameters.

CSCeb23320

Cisco CallManager does not send a forward busy reason code for a call that is Call Forward Busy (CFB).

CSCeb23668

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

CSCeb23944

Installation does not delete the temporary files after upgrading Cisco CallManager server.

CSCeb24227

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

CSCeb24635

JTAPI sends the wrong callCtl_Cause code in the CallCtlConnAlertingEv message.

CSCeb24981

Cisco CallManager displays a CDBLException error message when you provide an entry with a missing quote character.

CSCeb25014

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

CSCeb25389

Cisco CallManager needs a new method to close connections for DirUser object.

CSCeb27289

CiscoIPPhoneExecute command fails to authenticate and execute with the proper credentials.

CSCeb27723

Cisco CallManager Serviceability treats the percent character (%) as wildcard in Q931 Translator Trace.

CSCeb27730

Cisco CallManager Administration displays a Javascript error when you enter a single quote in Alarm Details.

CSCeb27869

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

CSCeb28229

JTAPI did not send a CallCtlConnDisconnectedEv message.

CSCeb29036

The Call Detail Records (CDR) for Ad hoc conference (TP, Net Meeting) has incorrect values.

CSCeb30328

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

CSCeb30414

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

CSCeb30508

Call Throttling fails on an H.225 intercluster trunk.

CSCeb30537

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

CSCeb31088

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

CSCeb31499

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

CSCeb31503

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

CSCeb31505

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

CSCeb31562

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

CSCeb31601

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

CSCeb32022

Cisco CallManager Administration does not display the dependency records for a call pickup number.

CSCeb32294

Cisco CallManager Administration displays directory numbers of phones and voice mail port devices in the dependency records of calling search space.

CSCeb32323

Cisco CallManager Administration does not display Russian characters correctly.

CSCeb32402

Phone displays wrong call information for a third party when a call is answered after completing a conference.

CSCeb32712

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

CSCeb32714

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

CSCeb32728

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

CSCeb32736

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

CSCeb32856

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

CSCeb32886

Cisco CallManager Administration displays an undefined error message when you insert a quote character in the prefix DN field for a non-gatekeeper controlled ICT trunk.

CSCeb32915

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

CSCeb32923

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

CSCeb34125

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

CSCeb34131

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

CSCeb34759

Cisco CallManager Administration does not display the pilot number in the dependency records for calling search space.

CSCeb35479

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

CSCeb35496

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

CSCeb35547

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

CSCeb35575

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

CSCeb35591

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

CSCeb35719

Users cannot change user locale on Cisco CallManager User page.

CSCeb36091

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

CSCeb36220

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

CSCeb36432

Call aborts when the agent conferences a gateway caller to Cisco Customer Response Solution (CRS) server.

CSCeb36706

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

CSCeb36921

Administrators get an error message when they delete a device that is a part of a Media Resource Group.

CSCeb36949

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

CSCeb37599

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

CSCeb38185

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

CSCeb38251

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

CSCeb38344

Cisco CallManager service does not start when the SDL trace file cannot be opened.

CSCeb38778

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

CSCeb39111

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

CSCeb40111

Administrators get a COM error when they delete a CTI route point that is used in a hunt group.

CSCeb40490

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

CSCeb40745

Cisco CallManager does not use the software media termination point as a transcoder resource between alaw and ulaw.

CSCeb40746

Cisco CallManager does not escape SQL wildcard characters and bracketed expressions in a Device Name Based Trace Monitoring query.

CSCeb40808

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

CSCeb41467

When a user has no associated device, BAT exports the MAC device entry for the previous user.

CSCeb41912

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

CSCeb42012

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

CSCeb42026

A phone that is attempting to barge in a call rings because a media path exists.

CSCeb42129

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

CSCeb42197

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

CSCeb42451

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

CSCeb43164

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

CSCeb43189

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

CSCeb43209

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

CSCeb43285

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

CSCeb44077

Redirected call fails when the call is redirected from Cisco IP Auto Attendant to another route point.

CSCeb44185

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

CSCeb44465

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

CSCeb44608

The readme file in ServPrep has spelling errors.

CSCeb44800

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

CSCeb45432

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

CSCeb45857

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

CSCeb45871

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

CSCeb45905

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

CSCeb45952

Third-party CTI application causes CTI manager process to stop.

CSCeb46547

Cisco IP Phone 7970 and Cisco IP Communicator does not close the service window when an extension mobility user logs in or logs out.

CSCeb46797

Region Configuration displays Video Call Bandwidth configuration parameters.

CSCeb47016

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

CSCeb47032

Cisco CallManager Administration allows you to enter IP addresses.

CSCeb47066

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

CSCeb47114

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

CSCeb47300

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

CSCeb47393

CTI Manager service stops when a route point has 256 lines.

CSCeb47435

User experiences one-way audio on calls that are transferred from PSTN to an analog phone across Cisco CallManager cluster.

CSCeb48385

Cisco CallManager does not immediately clear a call when a transcoder is not unavailable for an intercluster call.

CSCeb48454

Callback fails in a multiple callback scenario.

CSCeb49059

The ring tone cadence changes for inbound calls.

CSCeb49606

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

CSCeb50331

Cisco CallManager Administration displays the exceed time limit error message when the session times out.

CSCeb50784

Cisco CallManager displays an error message when you search on voice mail by description.

CSCeb50787

Cisco CallManager returns incorrect results when you search with an empty CSS field in the Voice Mail Pilot page.

CSCeb50803

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

CSCeb50805

Phone plays a false ringback when the ringing phone is not connected to the intercluster trunk.

CSCeb51155

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

CSCeb51456

An error displays when user integrates Cisco CallManager server with a newly installed Netscape Directory server.

CSCeb52339

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

CSCeb52379

The upgrade assistant does not document how to contact technical support.

CSCeb52723

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

CSCeb53245

The CDR values for transfer and conference calls are incorrect.

CSCeb53318

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

CSCeb53374

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

CSCeb53658

Cisco CallManager displays a GetVersion message during installation.

CSCeb53947

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

CSCeb54081

IP phone continues to ring when you choose callback.

CSCeb54528

Cisco CallManager displays a MohNoMoreResourcesAvailable error message when music on hold server is not configured.

CSCeb54623

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

CSCeb54721

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

CSCeb54770

Users cannot log in after modifying the service parameter.

CSCeb54778

Cisco CallManager Serviceability does not display the CDR Analysis and Reporting tool.

CSCeb55405

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

CSCeb55470

A PBX or ISDN PRI switch restarts when the user-to-user information element (UUIE) is longer than the 260 octets that is defined in Q.931.

CSCeb55532

Administrators get a CDBL exception error when they add a server that is not on the network by using the hostname.

CSCeb55686

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

CSCeb56142

Cisco CallManager does not release the channel when a phone is disconnected.

CSCeb56524

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

CSCeb56832

The information in Cisco CallManager management information base (MIB) appears out of order.

CSCeb57026

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

CSCeb57154

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

CSCeb57852

MTP resources do not get released when the preexisting media connection of one endpoint fails to connect to another endpoint.

CSCeb58054

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

CSCeb58118

Cisco CallManager uses a non-ISO standard for the facility information element.

CSCeb59294

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

CSCeb59427

Cisco CallManager does not immediately drop a call when it receives a H.225 release complete message.

CSCeb59743

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

CSCeb60323

Cisco CallManager displays an incorrect message when you add conference bridge with the same name as pilot point.

CSCeb60440

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

CSCeb60593

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

CSCeb62505

Cisco CallManager has 100 percent CPU usage when you register phones with duplicate lines.

CSCeb63007

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

CSCeb63020

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

CSCeb63096

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

CSCeb64249

Bandwidth does not get released and becomes oversubscribed when you resynchronize a music on hold server.

CSCeb65001

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

CSCeb65473

Cisco IP SoftPhone in an ad hoc conference call does not get released when the last party is dropped.

CSCeb65481

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

CSCeb65498

CTI TSP stops while a user logs in and out of extension mobility.

CSCeb66123

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

CSCeb66149

Phone does not display a user name on a call between QSIG gateways.

CSCeb66617

The locale element in addUser method only works in the English locale.

CSCeb66884

Extension mobility user cannot log out on IP phone.

CSCeb67162

System users did not get created during an upgrade.

CSCeb67194

User gets a HTTP 500 error when accessing Cisco CallManager user.

CSCeb67247

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

CSCeb67383

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

CSCeb68802

After a consult transfer call is received, the Cisco Agent Desktop (CAD) transfer button is grayed out.

CSCeb69344

The voice mail port wizard displays a JavaScript error message when you enter a backslash in the description or display field.

CSCeb69507

Cisco CallManager Administrator does not allow you to enter a maximum hop for multicast value between 100 and 127.

CSCeb69959

The patch.sql file did not get updated when Cisco CallManager was upgraded.

CSCeb70727

External route plan gets deleted even when a user chooses the cancel button.

CSCeb70825

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

CSCeb71025

Cisco CallManager displays an older version of JTAPI after an upgrade.

CSCeb71853

Cisco CallManager displays the media mixer on the dependency record for a media termination point.

CSCeb72096

DCD upgrades fail when the DCD password ends with a backslash.

CSCeb72114

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

CSCeb72452

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

CSCeb72469

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

CSCeb73240

Cisco CallManager Administration displays an ASP error message when you choose the Close and go Back Link in Dependency Records.

CSCeb74725

Tone on hold does not work over an ICT trunk when the MOH server is not in service.

CSCeb75037

Cisco CallManager Administration does not display department information for a user when the system is integrated with Active Directory.

CSCeb75452

The Change B-Channel Maintenance Status advanced service parameter does not work on a Cisco Catalyst 6000 T1 PRI channel.

CSCeb75867

ART Scheduler Service does not start after an upgrade to Cisco CallManager Release 3.3(3)SR1.

CSCeb75869

Transfer does not work on a G.723-G.711-G.711 call.

CSCeb76259

Translation pattern does not take effect when you reset Calling Search Space.

CSCeb76286

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

CSCeb76332

Cisco VG200FXS VM port failure causes call forward failure.

CSCeb76796

IP phone displays an unknown number when it receives a transfer meetme call from a Cisco IP SoftPhone.

CSCeb76809

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

CSCeb78325

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

CSCeb78357

Administrators get a HTTP 500 error when they click on the Close and Go Back button from the Dependency Record window after the pilot point is deleted.

CSCeb78362

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

CSCeb78365

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

CSCeb78383

Cisco CallManager Administration displays an Error Getting User Information message when you update a user that has been deleted.

CSCeb78496

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

CSCeb78498

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

CSCeb78500

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

CSCeb78807

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

CSCeb79667

IP phone does not display the forward setting after the phone goes off hook.

CSCeb80480

Cisco RIS Data Collector does not start after the passwords are reset with the Admin Utility.

CSCeb80508

Calls go idle, and Cisco Telephony Application Programming Interface (TAPI) service provider (TSP) does not report the idle CallState because CTI does not handle the cause code the LmKeyReleaseReq message reports.

CSCeb80938

Conference call does not get dropped when the controller hangs up.

CSCeb80969

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

CSCeb81051

Administrators get an error when they click on the Close and Go Back button from the Dependency Record window for ICT.

CSCeb81074

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

CSCeb81140

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

CSCeb82270

The Route Group window stops working when you attempt to update a deleted route group.

CSCeb82274

The Route Configuration window stops working when you attempt to update a deleted route filter.

CSCeb82323

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

CSCeb82330

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

CSCeb82398

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

CSCeb82415

Cisco CallManager installations create a WAUSERS share directory.

CSCeb82431

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

CSCeb82437

Cisco CallManager allocates an incorrect bandwidth for MOH streams that are using G.729A audio.

CSCeb82701

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

CSCeb82764

The Admin Utility tool has inconsistent behavior for updating server passwords.

CSCeb83042

The Peer Mode Enable Code enterprise parameter has no effect on the system.

CSCeb83500

Cisco 3640 gateway using QSIG stops receiving calls.

CSCeb83527

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

CSCeb83541

CCMPasswordChanger incorrectly changes the password on a subscriber server.

CSCeb85021

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

CSCeb85056

Cisco CallManager incorrectly handles CcUserInfo.

CSCeb86014

Cisco CallManager Administration takes up to 3 minute to display the device window.

CSCeb86240

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

CSCeb87424

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

CSCeb87713

The subscriber server uses the wrong database when you start an upgrade on the subscriber server prior to completing the publisher server upgrade.

CSCec00019

Cisco CallManager trunk may unexpectedly unregister with a gatekeeper.

CSCec00266

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

CSCec00336

Cisco CallManager server cannot use a Active Directory child server as a domain controller.

CSCec00420

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

CSCec00591

Cisco CallManager Administration displays both sub-modules of VWIC-1MFT-T1 with slot/port = 3/0 in the user defined gateway module NM-HD-2VE.

CSCec00892

Cisco CallManager Administration does not display available pickup groups in the drop down menu when you add a shared line.

CSCec00957

A logged out user device profile (UDP) does not get selected when the user chooses the backspace key.

CSCec01392

Cisco CallManager Administration does not display CTI Route Point immediately when you add a new CTI Route Point to a system with a large number of partitions.

CSCec01522

Cisco Wireless IP Phone 7920 cannot automatically register because the file extension on the TFTP server is case sensitive.

CSCec01526

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

CSCec02481

Bulk Administration Tool (BAT) takes up to 20 minutes to add IP phone when Cisco CallManager server has a large number of configured entries.

CSCec02756

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

CSCec02788

The tomcat-users.xml file contains clear text userid and password.

CSCec03800

CTI application receives events out of order.

CSCec04712

Simple Messaging Desktop Interface (SMDI) packet does not get generated when a device selects a new route list.

CSCec04720

You cannot configure a Cisco VG 248 gateway with unassigned DN on port 2 through port 48.

CSCec04947

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

CSCec05097

JTAPI disconnected events do not get sent at the completion of a conference call when the JTAPI application is restarted.

CSCec05189

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

CSCec06211

CTI Manager does not send DeviceInServiceEvent and LineInServiceEvent messages.

CSCec06462

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

CSCec07161

Cisco CallManager should not allow a MWI request on a Cisco IP Conference Station 7936.

CSCec07174

Cisco IP Conference Station 7936 does not display contents when you configure settings with a TAPI application.

CSCec11141

The diruser.jar and dirusernotification.jar files are missing after an upgrade.

CSCec11536

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

CSCec11642

Call back service has high CPU usage.

CSCec11662

Cisco CallManager displays a remote script error when you update call park configurations.

CSCec11770

Cisco CallManager displays a remote script error when you update call pickup configurations

CSCec11775

Cisco IP Phone 7960 continues to ring after the call has been answered.

CSCec13038

Cisco CallManager displays a cryptic error message when you change the device pool for a Q.SIG gateway.

CSCec13128

CTI does not dynamically rehome to the correct server on a failover for Cisco IPMA.

CSCec14907

Intermittently, Cisco CallManager will not enable the MWI lamp on an IP phone.

CSCec15529

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

CSCec16419

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

CSCec16771

Cisco CallManager registers multiple intercluster trunks with a gatekeeper.

CSCec17454

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

CSCec17485

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

CSCec17938

Cisco CallManager does not print a signal in SDL trace for troubleshooting MWI problems.

CSCec18647

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

CSCec19224

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

CSCec19265

After upgrading to Cisco CallManager Release 3.3(3), Cisco IP SoftPhone takes up to 15 seconds to complete a call.

CSCec19316

Cisco CallManager process stops.

CSCec19444

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

CSCec19813

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

CSCec20285

The BAT Phone Template page becomes unresponsive when you configure calling search space (CSS) on a system with a large number of CSS entries.

CSCec20305

The Attendant Console client cannot log in.

CSCec20373

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

CSCec20441

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

CSCec20481

The CTIDeviceList causes a memory leak in CTI Manager.

CSCec20693

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

CSCec21653

User does not receive any audio signal on a call waiting call.

CSCec21681

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

CSCec22860

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

CSCec23324

Failed Cisco CallManager upgrades do not have helpful error message.

CSCec24635

Phone does not ring when an inbound call is received before the outbound call is answered on another line.

CSCec25500

Cisco Customer Response Solution (CRS) does not display resource names on the resource list.

CSCec25549

Call Management Record (CMR) gets corrupted and cannot be inserted into the call detail record (CDR) database.

CSCec26168

The real-time information server (RIS) data collector periodically restarts.

CSCec26277

The ciscoupdate.txt log does not display the current SQL version.

CSCec26776

IP phone displays registration rejection message when you reset the phones.

CSCec27119

Cisco CallManager does not increment the hop count for Call Forward All (CFA) calls to voice messaging system.

CSCec29576

Cisco TAPI service provider (TSP) allows a GetDisplay to succeed in a Cisco IP Conference Station 7935.

CSCec30008

Cisco CallManager does not use the CSS when you configure CFA from Cisco CallManager Administration or from Cisco CallManager User pages.

CSCec31671

Cisco CallManager Administration does not display an icon for the Cisco IP phone 7970.

CSCec32565

CTI Manager process stopped in the directory thread.

CSCec32889

CTI Manager process stopped in the directory thread when the connection to the LDAP server timed out.

CSCec32991

Device Name Based Trace Monitoring does not have a Cisco IP Phone 7970 icon.

CSCec33004

Cisco CallManager Administration displays an error message when you query by using a single quote character in the Find list Route Pattern window.

CSCec33755

Call setup fails when Cisco CallManager receives a progress indicator message on a Q.SIG call.

CSCec34816

SDLRouterThreadDead times out due to misconfiguration in Perfmon.

CSCec36220

Consult transfer fails, and an agent is stuck in the hold state.

CSCec37010

The DNA tool does not restrict viewing to selected XML files.

CSCec37513

TAPI has an unknown device type for Cisco IP Communicator and Cisco IP Conference Station 7936.

CSCec37576

The backup and restore utility does not migrate all locale CSV files.

CSCec39499

You can only browse the first page in Automated Alternate Routing Group Configuration when you use Netscape Navigator.

CSCec39512

You can only browse the first page in Region Configuration when you use Netscape Navigator.

CSCec39517

CDR records do not get generated when you change the Universal Naming Convention (UNC) or local path.

CSCec39872

Dial tones can be delayed because of the default database debounce timer.

CSCec40191

PSTN user had a dropped call upon receiving ringback.

CSCec40884

LineOpen () returns an error message.

CSCec40936

Cisco CallManager Administration user configuration does not work when the French locale is selected.

CSCec41220

Call transfer fails when Cisco IP Interactive Voice Response (IVR) transfers a call to Cisco Customer Response Solution (CRS).

CSCec41691

Cisco CallManager does not have a definition for a Cisco VG224 gateway.

CSCec42868

Calls fail on Cisco CallManager controlled Media Gateway Control Protocol (MGCP) gateways when mismatched endpoint state results exist.

CSCec43564

Cisco CallManager Administration does not display the Cisco VG224 icon in the Tracing Selection Search Page.

CSCec43591

Region Configuration fails when you use Netscape Navigator and there are more than 10 items.

CSCec43710

Cisco IPMA configuration wizard failed to create IP phone services and populate Cisco IP Manager Assistant service parameters.

CSCec43718

Data gets lost when you enter data for a new DN before choosing the character set.

CSCec44460

Route lists fail when the DbRouteListResTimer times out.

CSCec44894

Cisco CallManager Administration needs a servicewide parameter to block call transfers from an external number to another external number.

CSCec45097

Cisco CallManager Administration takes up to 2 minutes to display a route pattern.

CSCec45179

DC Directory stopped.

CSCec45754

Updating route lists fail when a large number of route lists exist.

CSCec46110

The Find/List Pilot Point query displays incorrect pilot point number when the pilot number has 10 or more digits.

CSCec46310

CPU usage goes to 100 percent when you load the device default page.

CSCec46451

Cisco CallManager takes a long time to load the Calling Search Space Configuration when more than 100 calling search spaces are configured.

CSCec46544

Cisco CallManager drops calls to a cell phone when the call is routed through the PSTN.

CSCec46577

Administrators need to click on the reset button twice on phone configuration.

CSCec47646

Administrators cannot configure the length of a trace file in DCDsrv-log folder.

CSCec48050

Cisco CallManager responds to the primary gatekeeper when an IRQ message is received from an alternate gatekeeper.

CSCec48892

Cisco CallManager Administration does not list CSS option in the Find and List Phones.

CSCec48902

Device Pool search criteria does not work in Find and List Phones.

CSCec48931

Cisco CallManager Administration takes up to 5 minutes to display the dependency record for a route list.

CSCec50080

Application Event viewer did not display a warning message that Cisco CallManager services restarted.

CSCec50178

Cisco CallManager incorrectly reports a call on hold as cleared to the application.

CSCec50488

Cisco CallManager includes a delayed response to a request for holding a call.

CSCec50868

Cisco CallManager queries for inactive calls after receiving a Interrupt Request (IRQ) message.

CSCec51393

A call park number does not display in the pop-up message when the number contains special characters.

CSCec51609

Cisco CallManager, Release 3.3(3) ES14 has Cisco CallManager User page errors.

CSCec52887

Calls from Netmeeting clients to IP phones do not work when a Lucent Soft Switch is configured as a gatekeeper.

CSCec52954

Cisco CallManager server unregisters with a gatekeeper when a registration request (RRQ) is lost.

CSCec54062

Cisco CallManager Administration and Cisco CallManager User windows have inconsistent user password behavior.

CSCec55234

Route Pattern page does not display when a configured Cisco VG 200 gateway exists.

CSCec55242

CALL PROCEEDING message does not include Channel ID.

CSCec59109

Two-stage dialing through a MGCP FXO to Cisco CallManager fails.

CSCec60220

Cisco CallManager installation does not check for forward and reverse name resolution at the beginning of the installation.

CSCec61117

You cannot delete a user when Cisco CallManager points to an Active Directory child server.

CSCec61820

Device Defaults display the default load for the Cisco IP Phone 7970 as TERM70.DEFAULT.LOADS.

CSCec63052

Calls to a device on the WS-6624 gateway fail after the directory number is changed.

CSCec63078

Cisco CallManager rejects calls when CRS is under load.

CSCec64242

Cisco CallManager service terminates unexpectedly.

CSCec65183

Cisco IPMA does not handle underscore character in the user ID field after the TomCat service is restarted.

CSCec65193

JTAPI logged a NullPointerException for Redirect scenario.

CSCec65850

The real-time monitoring tool displays the wrong conference bridge model.

CSCec66510

TAPI failed to remove CFA setting for a DN.

CSCec66820

Cisco CallManager Administration always returns zero records when you search for a CTI route point with a Calling Search Space is empty search parameter.

CSCec67323

Cisco IP Phones 7940 and 7960 incorrectly display the call forwarded icon.

CSCec67457

Administrators received an internal server error when they tried to view DN configurations.

CSCec68362

Cisco CallManager service restarted during a phone registration.

CSCec68766

After updating a translation pattern, Cisco CallManager routes calls for both old and new translation patterns.

CSCec69160

Cisco CallManager Administration displays a CDBLException error when users choose the propagate icon for line text display.

CSCec69371

Cisco IPMA phone with do not disturb enabled rings when the phone receives a callback signal.

CSCec69497

Cisco CallManager does not handle MGCP 400 errors correctly.

CSCec69693

Upgrade assistant fails on backup validation when it encounters a catalog file of 0 bytes.

CSCec70373

Callback failed on an extension mobility shared-line phone.

CSCec71675

Cisco CallManager does not clearly define the Sdl Max UnHandled Exceptions service parameter.

CSCec72451

Cisco CallManager service restarts when a large number of route lists exists.

CSCec73503

Cisco CallManager does not retain information when you choose Character Set in Add/Update Speed Dials.

CSCec73810

Cisco CallManager stops accepting calls on a port on Catalyst 6608 after a PRI setup retry.

CSCec73828

TAPI does not respond immediately to either the LINE_REPLY or the LINE_ADDRESSSTATE event on lineForward request.

CSCec75146

Call lingers in JTAPI after call is dropped.

CSCec75896

ListAllProcessNodesResponse has a malformed format.

CSCec76154

Cisco CallManager does not receive some call events when Internal Caller ID is set to a value in Cisco CallManager Administration.

CSCec77797

GetDeviceProfileRes:model returns a value not found in AXL schema

CSCec79510

CTI manager traces do not display the quick buffer encoding (QBE) messages for both directions.

CSCec79739

Cisco CallManager attempts to answer a connected call when call is placed on hold.

CSCec79800

TSP failed while communicating with the voice-messaging system.

CSCec82337

When you submit a change on the subscriber server while the publisher server is offline, Cisco CallManager Administration displays an error message indicating that the object does not support this action.

CSCec82409

Cisco CallManager and CTI services do not start after an upgrade because of missing content in the SQL table.

CSCec83663

The Echo Cancellation Coverage setting does not have a preconfigured value.

CSCec83747

Cisco CallManager incorrectly displays calls in the CallsInProgress counter when no calls are being processed.

CSCec84793

Cisco IPMA Assistant Watch window remains after a mobile manager logs off.

CSCec84986

Cisco CallManager Administration does not display the gateways in the dependency record of the automated alternate routing (AAR) group.

CSCec85371

Callback fails when translation pattern drops digits.

CSCec86798

The addOnModule in AVVID XML Layer (AXL) accepts phoneTemplate type.

CSCec87873

Call Dependent Call Control (CDCC) has a memory leak when a conference call terminates.

CSCec89794

Installation on a subscriber server failed when it could not stop the aupair service.

CSCed00108

Phones have to reregister when Cisco CallManager has a CSS update with over 20,000 devices.

CSCed00455

Cisco 2651XM does not forward calls to PSTN on NM-HD-2V interface.

CSCed00458

Phone with CFA enabled continuously plays the reorder tone when the publisher server is down.

CSCed01709

Redirecting to an external party fails.

CSCed01740

CmiPerfmon.dll causes thread deadlock.

CSCed01745

CtiMgrPerfMon.dll causes thread deadlock.

CSCed01755

MediaAppPerfMon.dll causes thread deadlock.

CSCed01758

TcdSrvPerfmon.dll causes thread deadlock.

CSCed01763

TftpPerfmon.dll causes thread deadlock.

CSCed01883

Transfer to Voicemail stops working for an assistant after a new manager is added.

CSCed02728

Phone remains in a dialing state when the phone receives a call while CFA is being removed.

CSCed02874

Set Ringer does not work when Tone on Call Forward is disabled.

CSCed02974

Music on hold does not stop after a call on H.323 gateway is resumed.

CSCed05265

Cisco CallManager Administration displays a CDBLException Dump message when a Calling Search Space (CSS) is deleted.

CSCed05368

Cisco CallManager records excess CTI traces when the trace level is set to ERROR LEVEL.

CSCed06318

Administrators cannot delete a Cisco CallManager group even when the group has no dependent records.

CSCed06632

Cisco CallManager Administration does not allow you to configure the calculateAverageExpectedDelay option in trace settings.

CSCed07090

Cisco CallManager does not support SERVICE and SERVICE ACK messages for B-channel maintenance in PRI NI2.

CSCed07853

Cisco CallManager continues to process calls on an out-of-service B channel.

CSCed08525

The online help does not define the CallThrottlingGenericCounter field.

CSCed08682

ISDN B-channels remains in service after the gateway is restarted.

CSCed09180

The conference button does not work after a user conferences a parked number.

CSCed09808

TSP does not support dwNumEntries=NULL in lineForward().

CSCed10710

Cisco CallManager does not forward H.225 connect message when it is waiting for the H.245 channel to be established.

CSCed13338

Administrators get an error message when they delete a route group in route group configuration.

CSCed14978

IP phone cannot register to standby Cisco CallManager during a failover.

CSCed15955

Change Notification for a renamed device does not update the user device list.

CSCed16095

Cisco CallManager disconnected calls with a cause code of 0.

CSCed17201

Installation of Cisco CallManager Release 3.3(3) SR3 proceeds even though Cisco Security Agent is still running.

CSCed17317

The Resume softkey does not get disabled when a user is not allowed to resume a held call.

CSCed17414

Cisco CallManager process stops with a dead SDL timer.

CSCed17554

Administrators cannot troubleshoot a setup when Cisco CallManager ignores a call Setup message for an active call.

CSCed17889

Cisco CallManager Administration displays a COM error when you attempt to delete a meetme number while the publisher server is down.

CSCed18107

The department field does not get displayed when a Cisco CallManager system is integrated with Active Directory.

CSCed18630

IP phone continues to display the EndCall softkey after CFA was enabled.

CSCed19172

Adding a call observer when a call is in progressing state can result in a stale call where the call cannot be removed.

CSCed19683

Administrators get a remote scripting error when they update the default device profile.

CSCed19795

Cisco CallManager incorrectly displays active calls on the PRIChannelsActive counter.

CSCed21260

The dependency link for a H.323 client phone incorrectly displays a trunk device.

CSCed21566

Cisco CallManager service stops unexpectedly with invalid instruction in CConnectionHolder.

CSCed21668

Performance data for a monitored call park DN does not get logged when the DN is opened by an application.

CSCed22113

The call forward no answer service parameter does not work for boundary values.

CSCed22130

Multiple CtiLineCloseCallReq messages cause Cisco CallManager service to stop.

CSCed22925

Two answerReq messages from an application for the same call causes a call to be placed on hold.

CSCed22985

Administrators cannot add devices to route groups when they apply Cisco CallManager Version ES54.

CSCed23028

Cisco CallManager sends the incorrect reason code when a transformation mask is used on route pattern.

CSCed24195

TSP does not set the dwCallerAddressSize and dwCallerAddressOffset fields to 0 in the LINEFORWARD structure that is contained in the LINEADDRESSSTATUS structure.

CSCed25256

Signal Distribution Layer (SDL) link lost status of a router thread on a node.

CSCed25707

Cisco IP Phone 7905 should not play the reorder tone.

CSCed26230

Cisco CallManager does not translate the ISDN cause code 1 to CTI CALLSTATECAUSE=1.

CSCed27298

Personal Address Book (PAB) stops working when you change the User ID in Lightweight Directory Access Protocol (LDAP).

CSCed27637

AddGatewayEndpoint request returns a "NULL value not allowed" error.

CSCed28069

Cisco CallManager incorrectly displays a number of calls in the CallsInProgress counter when no calls are being processed.

CSCed28356

JTAPI fails to connect to CTI when the CTI service is restarted.

CSCed28953

Database Layer (DBL) traces logs queries for gateway devices that were deleted.

CSCed29929

Calls to CTI route point fail with a trace message that a forward loop has been detected.

CSCed30099

Connection does not get created for a destination in a CFB scenario.

CSCed30578

Transferred call does not get cleared.

CSCed31103

A hairpin call to a PSTN with call forwarding fails when Cisco CallManager is configure for overlap sending.

CSCed32311

Administrators cannot search for partition by using the underscore character in Route Patterns.

CSCed32849

The online help for Locations Trace Details Enabled parameter is confusing.

CSCed32946

You cannot access the subscriber DC directory after installation or an upgrade when the DC Directory administrator password contains the pipe symbol ( | )

CSCed33153

Perfmon for CTI Manager displays incorrect number of lines open in the counter.

CSCed34579

Cisco CallManager service stops when a number of TCP connections are waiting to close.

CSCed34780

The Tone on Call Forward and Call Waiting service parameters do not work correctly.

CSCed37332

Cisco CallManager placed softkey events in the low-priority queue.

CSCed37807

Cisco CallManager stops when calls are forwarded to an unregistered voice mail port.

CSCed39907

Call gets dropped when the value in Auto Answer Timer is greater than the value in T301 Timer.

CSCed40428

Cisco CallManager needs to allow a higher maximum value for MaxDbUpdatesAllowed Service Parameter.

CSCed41072

Cisco CallManager has incorrect time zone for Brussels and Prague.

CSCed41115

The readme file for the admin utility is missing from Cisco CallManager installation 3.3(3).

CSCed41452

Application Event Viewer displays Cisco RIS Data Collector initialization errors.

CSCed43731

Cisco CallManager inserts trunk selection order parameter for analog POTS ports on IOS gateways.

CSCed44168

IP phone gets disconnected when a reorder tone is expected.

CSCed46850

Administrators get a remote scripting error when they delete route groups.

CSCed47587

Information gets lost when you resize the Cisco CallManager Administration window.

CSCed47893

TSP ignores the Progressing State message.

CSCed48483

The CTFTP service retains the OS7920.TXT file in its cache memory.

CSCed48579

The dllhost for Cisco CallManager Administration fails to shut down, which causes additional memory loss.

CSCed48598

JTAPI reports an incorrect error when it routes a call to a CTI route point with call forward all enabled.

CSCed49314

Cisco CallManager does not tag Software Defined Network (SDN) calls with the correct parameters.

CSCed51080

The Active Directory server has high CPU usage when CAR is running a report.

CSCed51086

The Active Directory server has high CPU usage when CAR is running a report.

CSCed51455

IP phone continues to display CallPark Reversion when CallPark Display Timer Service Parameter is set to 0 and you do not answer the call.

CSCed52779

You cannot use Japanese Katakana for an IP phone service name.

CSCed52795

Cisco CallManager generates a log file with the wrong file name when you install Cisco CallManager 3.3(3) SR4.

CSCed52796

Another phone in the pickup group hijacks the active call.

CSCed52875

Administrators cannot easily detect multiple active Cisco CallManager processes on the same server.

CSCed54060

RIS Data Collector service stops on a subscriber server.

CSCed54206

Cisco CallManager does not send a call failure code to a SCCP or JTAPI device when a call is placed to an invalid number

CSCed56107

Administrations get an ODBC error when they query for DN and a large number of configured phones exist.

CSCed57003

Cisco CallManager does not send a RELEASE COMPLETE message when it receives a status with a callstate=19.

CSCed57917

Call gets stuck when you initiate a blind transfer and the controller drops the call.

CSCed59917

Cisco CallManager does not allow gatekeeper-controlled H.323 and intercluster trunks to use the sourceCallSignalAddress to select an appropriate gateway.

CSCed63741

You cannot remove a default profile when extension mobility is disabled.

CSCed64717

CTI Manager terminates unexpectedly.

CSCed66155

Administrators get an error message when they delete multiple DN, by using Cisco CallManager Administration.

CSCed68542

Voice Mail Port wizard displays an error and does not continue when the description exceeds 140 characters.

CSCed70916

Users cannot log in to Cisco CallManager User Option page when their password contains the double quote character.

CSCed74445

Call does not reroute immediately when the IOS T1 CAS MGCP setup has a failure.

CSCed75500

PRI NI2 Service Message Support Service parameter should only be outgoing.

CSCin41617

Cisco CallManger generates a new call when you do a consult transfer of a conference call by using Attendant Console.

CSCin44653

Device name field in H.323 gateway configuration window accepts incomplete IP addresses.

CSCin45681

Cisco SoftPhone user could not rejoin a conference call after an unsuccessful attempt to transfer a call to a park number.

CSCin46237

Cisco CallManager does not release a Cisco SoftPhone in a conference call when the conference controller presses the RmLstC softkey.

CSCin49357

Cisco CallManager server has high CPU usage when an administrator incorrectly configures the ending port number to be smaller than the beginning port number in a MGCP CAS configuration.

CSCin49927

Cisco CallManager Administration accepts an invalid IP Address in the server IP address in non-Gatekeeper Controlled Trunk Configurations.

CSCin50848

Cisco CallManager has high CPU usage on a call to an analog MGCP phone.

CSCin52268

Administrators get an error when they click on the Back to Voice Mail Profile link from the Dependency Record window for Voice Mail Profile.

CSCin52362

The dependency records of voice mail pilot number display unusual entries when the pilot number does not have a description.

CSCin52563

Cisco CallManager Administration fails when you change Cisco VG248 48_PORTS to None.

CSCin53107

Cisco CallManager Administration displays incorrect entries for route plans when you query by using Find by Partition.

CSCin53117

Cisco CallManager Administration does not have Advanced Integration Modules (AIM) VOICE-30 option for Cisco 2600 series of routers.

CSCin53141

The HWConferenceActiveParticipants counter in Performance Monitor does not reset upon completion of a conference.

CSCin53385

Cisco CallManager does not release the PRI channel when Cisco CallManager service is restarted during an active call.

CSCin53396

Cisco CallManager Administration appends spaces to the product-specific parameters in T1-CAS Configuration.

CSCin53582

The RmLstC softkey removes the incorrect participant in a conference call.

CSCin53749

The HWConferenceResourceActive counter in Performance Monitor does not display the correct value.

CSCin55039

You cannot use Microsoft Internet Explorer Version 5.00.3502.1000 to add a partition to a calling search space.

CSCin55125

Null values get inserted for parameter field in route filters.

CSCin55131

Cisco CallManager Administration does not trim preceding blank spaces in a route filter name.

CSCin56550

You cannot use Microsoft Internet Explorer Version 5 to add calling search space with the Cisco IPMA configuration wizard.

CSCin56725

Cisco CallManager does not switch back to lower priority route groups.

CSCin56794

Administrators get a remote scripting error when they add a new IP phone service.

CSCin57059

The event viewer displays many File Update failed Alarm messages when trace configuration is enabled to detailed database tracing.

CSCin57353

You get an error when you delete a music on hold server that is a part of a media resource group.

CSCin57852

Cisco CallManager still has the onhook notification service parameter.

CSCin58533

Administrators get an error message when they add a phone button template with the single quote character.

CSCin59221

Cisco CallManager Administration does not display an error message when you try to delete a route group while the publisher server is down.

CSCin59387

Cisco CallManager doe s not validate selected gateways when a route pattern is inserted.

CSCin61098

Pilot Number field in Pilot point Configuration does not accept asterisk and pound symbol (*, #) as valid characters.

CSCin61718

The Copy, Update, and Delete buttons in Phone Configuration stop working.

CSCin62402

Cisco CallManager Administration always shows the MWI icon as being enabled (green) in Dependency records.

CSCin62724

Administrators get an error when they access MTP from the firmware load page.

CSCin62741

Firmware information does not display a VGC gateway that has a non-default version.

CSCin62870

Cisco CallManager Administration does not list the firmware for Cisco IP Phone 7970 with the expansion modules.

CSCin62989

Cisco CallManager Administration throws an exception error when you search for a Login User ID by using a quote or a semicolon.

CSCin64126

The dependency record for Voice Mail pilot with the default or no voice mail option does not display proper names.

CSCin64416

Cisco CallManager Administration accepts incomplete IP addresses in the device name field of H.323 Client Phone Configuration.

CSCin64454

The update and delete buttons in IP Phone Services Configuration stopped working.

CSCin64520

Cisco CallManager allows you to assign 14-Button Expansion Module Phone Template to a Cisco IP Phone model 7960 or 7970 from Device Defaults.

CSCin65487

Cisco CallManager Administration displays Add Route Group when you choose the cancel button while deleting a route group.

CSCin66269

The Attendant DN does not get displayed when you access FXO configuration from the route point page.

CSCin66899

Conference does not get dropped even when only one single participant exists.

CSCuk45312

You cannot add QSIG gateways with intercluster trunks to route groups or route lists.

CSCuk45931

You cannot do a blink transfer on a PSTN call to another PSTN over a MGCP gateway.

CSCuk46135

Phone receives a busy tone instead of the reorder tone when a call is made to an H.323 gateway that is busy.

CSCuk46223

Call fails when Cisco CallManager sends an overlap message to a backhauled PRI link with an invalid Number Plan Indicator (NPI).

CSCuk46251

Cisco IPMA assistants do not get updated when the assistant has more than nine lines configured.

The following firmware caveats apply to this release.

CSCdz12384

Cisco IP Phone 7910 reboots and cannot register with the Cisco CallManager server.

CSCdz77730

Cisco IP Phones 7940 and 7960 display untranslated Hungarian text.

CSCea08063

Cisco IP Phone 7970 displays multiple lines for the same DN.

CSCea28342

User experiences 2 to 4 seconds delay on a call from the PSTN when Message Transport Protocol (MTP) is not in use.

CSCea47998

WS-6608 does not resolve the DNS name of the Cisco CallManager server when the primary DNS server is removed from the switch configuration.

CSCea67753

Cisco IP Phones 7940 and 7960 do not display the Registration Rejected message when Auto-registration is disabled.

CSCea72810

User receives an echo as a result of duplicate RTP sequence number.

CSCea77050

IP phone does not display information for the first call when you resume the call with a softkey while using the speakerphone.

CSCea77359

User receives an echo when one party has the volume set to 75percent or higher.

CSCea79644

The phone on an auxiliary VLAN cycles through configuring IP when the link is toggled.

CSCea81159

The exit softkey takes the user to the root of directory tree.

CSCea87612

The text labels that are assigned to the speed dials on the second sidecar module disappear when the network locale is changed.

CSCea89552

Phone does not fail over to next DNS server when the host is not found.

CSCea90298

You must enter TFTP information again if the phone initially receives an incorrect phone load.

CSCeb04237

IP phone does not dial all entered digits.

CSCeb04302

Cisco IP Phone 7960 does not update its IP address after receiving new IP address from the DHCP server.

CSCeb09560

The PC port on Cisco IP Phone 7960 has packet losses.

CSCeb11801

Cisco IP Phone resets and gets stuck in the "registering" cycle when it receives partial data while the connection is closed.

CSCeb13737

Conference ports do not get released when Cisco CallManger service is restarted.

CSCeb14547

Error response from a failed authentication returns an incorrect error code of 0

CSCeb16040

Two and one-half minutes after a call has been connected, Cisco IP Conference Station 7935 unregisters from the Cisco CallManager server.

CSCeb19725

Intermittent one-way/no-way audio may occur for the first 10 seconds of a call when TCP packets are received out of order during the call setup.

CSCeb27021

User needs to submit two XML messages to the Cisco IP Phone.

CSCeb42445

User does not receive the correct greeting in a voice-mail scenario.

CSCeb47121

User receives a lot of noise when mute is enabled on Cisco IP 7900 series phones.

CSCeb47122

Shared-line phone keeps ringing after the call has ended.

CSCeb53777

WS-6608 T1 CAS port stops processing calls.

CSCeb60327

Cisco IP Phone cannot make calls when a 24-digit directory number (DN) is assigned to the second line.

CSCeb62999

WS-6624 Digital Signal Processor (DSP) cannot recognized the DTMF after the first call.

CSCeb63095

Phone accepts a firmware file that is too big.

CSCeb64628

WS-6608-T1 does not support superframe (SF) and alternate mark inversion (AMI) framing.

CSCeb66915

HTTP service stops working on IP phone.

CSCeb69539

Phone reboots when you press the dial softkey and no entries exist in the directory.

CSCeb71168

Cisco IP Phone 7970 does not display any error messages when the URLs are empty.

CSCeb72009

Phones randomly reset after upgrading Cisco CallManager to Release 3.3(3).

CSCeb74797

WS-6624 displays incorrect port configurations.

CSCeb76938

Phone reboots when user logs in or out of extension mobility.

CSCeb77397

Cisco IP Phone 7912 ignores the StopMediaTransmission messages and continues to stream audio.

CSCeb80739

Multicast Music on Hold (MOH) works intermittently on a WS-6608.

CSCeb83975

Fax relay and fax passthrough do not work between a WS-6608 and a Cisco 2600 router.

CSCeb84716

Cisco Wireless IP Phone 7920 has the same ring pattern for both internal and external calls.

CSCeb87418

Disabling the port on Cisco Catalyst 6500 6608 T1 card does not disable the telco connection.

CSCeb87436

Users cannot use predialed digits to make a call when an incoming call exists on a shared line.

CSCec04257

Cisco IP Phones that are using signed phone loads on Cisco CallManager Release 3.1 do not enable the message-waiting indicator.

CSCec04924

Call in the forward direction fails when a transcoder is using G.723 with MGCP or H.323.

CSCec05748

You cannot configure the number of frames per packet for a G.729 call on Cisco IP Phones 7902/7905/7912.

CSCec08229

Phone does not recognize Cisco Discovery Protocol (CDP) packets bigger than 500 bytes.

CSCec10766

Cisco IP Phone 7970 fails to register when you reset the phone from Cisco CallManager Administration.

CSCec10815

Cisco IP Phone 7902 does not use the DHCP server IP address (siaddr) as the TFTP server IP address.

CSCec13125

Cisco IP Phones 7940 and 7960 do not update the etherRX interrupt counter correctly.

CSCec18043

WS-6608 gateway does not work because of a missing file.

CSCec20271

Different phone models display different translated numbers

CSCec21459

Cisco IP Phone 7902G does not stay registered to a Cisco CallManager server.

CSCec25054

Calls fail when WS-6608 T1 CAS is configured for ground-start signalling.

CSCec28216

Cisco IP Phone 7905 does not display the correct prompt when another call comes in.

CSCec29304

Phone randomly resets.

CSCec31298

User cannot answer an incoming call when the phone is in the directory menu.

CSCec31746

Existing extension mobility and Cisco IPMA users cannot use fast dials or the personal address book services.

CSCec36983

Phones reset when you are entering characters for a directory search in a non-English locale.

CSCec42600

Phone has greyed-out exit softkey in the settings menu.

CSCec46477

The battery on a Cisco Wireless IP Phone 7920 drains faster when keylock is enabled.

CSCec48701

Cisco IP Phones 7905 and 7912 cannot replay the DTMF tones when a keypadbutton message is received.

CSCec51337

Cisco IP Phones 7902, 7905, and 7912 do not play the correct tone for the Israel locale.

CSCec53044

Cisco IP Phone 7912 resets when you use the FastDial service.

CSCec59100

The configuration page for Cisco IP Phone 7970 accepts invalid values for the Display On Time, Display On duration, and Display Idle Timeout fields.

CSCec60616

Cisco IP Phone 7970 continues to display the request selection prompt.

CSCec65300

Cisco IP Phone 7912 resets when a high level of broadcast traffic exists on the virtual LAN (VLAN).

CSCec65479

Cisco IP Phone 7912 engages in a Address Resolution Protocol (ARP) storm.

CSCec71843

Phone does not display the last entry in the microphone selection menu.

CSCec72815

The phoneSetDisplay method returns success but Cisco IP Phones 7905, 7912, and 7910 does not display it.

CSCec75440

MGCP gateway is forced to restart in progress when it receives a duplicate transmission ID.

CSCec81626

Silence suppression does not work on Cisco IP Phones 7902, 7905, and 7910.

CSCec82466

Interactive voice response (IVR) menu does not work on the Cisco IP Phone 7902.

CSCec83603

Multicast MOH stops working after 3 to 6 minutes on a WS-6608-T1 module.

CSCec83661

After a reset, Cisco IP Phone 7912 does not re-register with a Survivable Remote Site Telephony (SRST) router

CSCec88295

Inbound calls fail on a WS-6608 T1 CAS ground-start port.

CSCed03520

 

CSCed05625

Cisco IP Phone 7912 reboots when the corporate directory returns more than 32 entries.

CSCed11655

WS-6608 does not follow the Q.921 specifications for rejecting frames.

CSCed17585

You cannot use the maximum valid port value for RTP streaming on a Cisco IP Phone 7970.

CSCed18290

MGCP gateways stop working when a partial failover occurs.

CSCed21561

You cannot push a file to a Cisco IP Phone 7912.

CSCed23847

Cisco IP Phone 7905 or 7912 on SCCP receives noise during the voice mail announcement.

CSCed44788

Cisco IP Phone 7970 does not work on February 29.

CSCed44839

Cisco IP Phone 7970 does not accept new user locales.

CSCed45379

Cisco IP Phone 7970 cannot fall back to a primary Cisco CallManager server.

CSCed52701

Cisco IP Phone 7970 has missing on and off times fields.

CSCuk44598

Cisco IP Phones 7940/7960 has unacceptable push performance.

CSCuk45784

Cisco IP Phones 7902, 7905, and 7912 do not use the configured packet size.

CSCuk45787

Cisco IP Phones 7902, 7905, and 7912 lock up for 40 seconds after a phone call.


Open Caveats for Cisco CallManager - Release 3.3(4)

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


Tip If you have an account with Cisco.com (Cisco Connection Online), you can use the Bug Toolkit to find caveats of any severity for any release. To access the Bug Toolkit, log on to http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl.


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

Identifier

Headline

CSCdz31748

Administrators cannot access Cisco CallManager.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCdz31748

CSCdr53384

Minor memory leak (svchost/tapisrv) occurs when a TAPI application stops.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCdr53384

CSCdv61446

Cisco CallManager installation does not check for a Primary DNS suffix.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCdv61446

CSCdx05609

Line control buttons do not display properly on a phone with multiple shared lines.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCdx05609

CSCdx64502

The audio connection gets delayed when Cisco CallManager server waits for an acknowledgement message from a MGCP gateway.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCdx64502

CSCdy25627

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

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCdy25627

CSCdy67641

User can pick up calls after the Pickup group number is deleted.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCdy67641

CSCdy80350

The DN on the phone does not change when an extension mobility user logs in.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCdy80350

CSCdz08071

The line information that is returned for the element <ringDisabled> is incorrect when you retrieve the phone information by using axl:getPhone.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCdz08071

CSCdz12937

MOH Audio Source web page takes 12 seconds to load.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCdz12937

CSCdz34248

Translation Pattern does not work.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCdz34248

CSCdz37189

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

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCdz37189

CSCdz39950

RingDisabled returns a non-Boolean value.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCdz39950

CSCdz56115

Cisco CallManager does not send error message for calls to out-of-service numbers.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCdz56115

CSCdz73098

Cisco does not completely describe the TabSync utility for Personal Address Book.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCdz73098

CSCdz90449

Cisco CallManager Attendant Console does not allow you to assign keyboard shortcuts from a Russian keyboard.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCdz90449

CSCea01715

Cisco CallManager sends an incorrect mediaControlChannel address in the Open Logical Channel message.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=

CSCea14821

The Cisco CallManager Compatibility Matrix has incorrect upgrade information.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCea14821

CSCea30059

Call gets offered in two locations when you do a simultaneous redirect and transfer.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCea30059

CSCea42126

Cisco CallManager sends a setup acknowledgement message when ISDN switchtype is primary-ni.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCea42126

CSCea51241

The online help for Attendant Console has incorrect encoded Hungarian characters.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCea51241

CSCea74484

Cisco CallManager services display an incorrect default value for the H.225 User Info Message field.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCea74484

CSCea81906

Cisco CallManager delays playing the welcome prompt for Tool for Auto-Registered Phone Support (TAPS) for 30 seconds.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCea81906

CSCeb05385

Users cannot use the phone to edit phone numbers in the personal address book.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeb05385

CSCeb05386

You cannot choose users with long first and last names on the phone.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeb05386

CSCeb06498

Calls drop when the barged phone disconnects from the network.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeb06498

CSCeb06793

Cisco CallManager services fail to initialize when more than 15,000 Call Park entries exist.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeb06793

CSCeb26986

A COM error displays when a user sends an AXL updateRouteGroup request.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeb26986

CSCeb30404

The help file for H.225 InterCluster Call Throttle Timer has a misspelling.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeb30404

CSCeb31088

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

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeb31088

CSCeb35584

Phone does not display the assigned fast dial entries.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeb35584

CSCeb48689

The Cisco Communication Media Module (CMM) displayed an unregistered gateway as being registered with Cisco CallManager.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeb48689

CSCeb56532

You cannot use Netscape Navigator to add a User device profile.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeb56532

CSCeb56736

You cannot use Netscape Navigator to add a User device profile default.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeb56736

CSCeb59326

The drive letters for the CD and Trace drives (E and F) get swapped during Same Server Recovery.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeb59326

CSCeb66293

Cisco CallManager sets the wrong error code on lineSetupTransfer for a disconnected call.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeb66293

CSCeb66550

The Calls Completed counter has a greater value than the Calls Attempted counter in performance monitor.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeb66550

CSCeb70951

Call Pickup and Group Pickup feature do not work when the Cisco Wireless IP Phone 7920 is ringing.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeb70951

CSCeb80892

Phone displays a mixture of English and German in the personal address book when the German locale is selected.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeb80892

CSCec06088

CDR Analysis and Reporting (CAR) does not align the menu in the PDF report for the Norwegian locale.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec06088

CSCec07049

Consult call on a CTI route point times out.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec07049

CSCec16209

Redirected calls on Cisco CRS fail under load.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec16209

CSCec18250

Cisco IPMA does not check the phone status for an assistant when a manager is activated.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec18250

CSCec19768

Extension Mobility login failed when the DBL could not access the subscriber server.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec19768

CSCec21319

The cqmghost.exe process stops on a Cisco CallManager server.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec21319

CSCec21799

DC Directory attempts to bind to a renamed Cisco CallManager server.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec21799

CSCec23437

Cisco CallManager server did not use all the voice-mail ports during a load test.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec23437

CSCec24295

Users logging in fail to authenticate.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec24295

CSCec27400

Administrators get an error message when they use brackets in the MOH fixed audio source name.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec27400

CSCec32997

Cisco IP Phone 7940 with firmware version P00305000101 has delayed dial tone.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec32997

CSCec34389

After changing a server password, BARS allow you to add the server with the old password.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec34389

CSCec38364

User cannot barge in on a call from an IP phone to a Cisco VG248 analog phone.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec38364

CSCec38402

Cisco MCS 7825H server locks up.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec38402

CSCec39492

Cisco CallManager rejects a call with release cause value 34 when the location call admission control (CAC) does not have enough available bandwidth to service the call.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec39492

CSCec42532

Default setting for SDL Tracing causes call throttling under moderate call load.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec42532

CSCec49110

Cisco IOS Telephony Services (ITS) phone does not play the ringback tone when a call is CFNA back to another Cisco ITS phone.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec49110

CSCec51986

Phone displays question mark characters when an extension mobility user logs out and the user ID contains extended characters.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec51986

CSCec52864

Cisco CallManager uses the last redirect reason when it forwards a call.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec52864

CSCec53082

Cisco CallManager cannot transfer a call from a Cisco ITS phone to another Cisco ITS phone that has been CFA to voice messaging.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec53082

CSCec58464

Event viewer displays an active server page exception error the first time that the Cisco CallManager User pages are opened.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec58464

CSCec59783

Attendant Console displays the incorrect connected number.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec59783

CSCec59862

Primary Cisco CallManager servers hang under heavy load.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec59862

CSCec60183

Call Back to a phone with a * or # in the DN fails.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec60183

CSCec60491

Associating a device with a large number of other devices takes a long time.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec60491

CSCec62401

Call control window for attendant console incorrectly displays the pilot point of Cisco Conference Connection.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec62401

CSCec62896

Event Viewer displayed a One service or driver failed to start properly message after a subscriber server is removed from the cluster.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec62896

CSCec65305

A manager phone does not display message that an assistant is in a conference.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec65305

CSCec65884

Cisco CallManager cannot forward a call to a phone on an intercluster trunk when call originates on a Cisco ITS phone.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec65884

CSCec72922

Attendant Console does not allow a user to create a speed-dial entry by using the plus character (+).

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec72922

CSCec79339

You cannot save a primary extension number for a device when the extension is shared on another device that is associated to the same user.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec79339

CSCec80457

Cisco CallManager assigns a busy reason on calls from QSIG trunks that are going directly to voice messaging.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec80457

CSCec80730

Phone resets when extension mobility user logs out.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec80730

CSCec82145

The online help for Cisco CallManager has misleading information on the Code Yellow Exit Latency Calculation service parameter.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec82145

CSCec82154

The online help for Cisco CallManager does not clearly define the maximum events allowed service parameter.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec82154

CSCec82695

Users get a duplicate value message when they import users after using the backup utility and upgrading Cisco CallManager.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec82695

CSCec83549

IPMA configuration wizard displays a blank message when the status has a long text string.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec83549

CSCec83614

Barged phone does not display correct DN when the transfer key is pressed.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec83614

CSCec87031

Not all documentation states that extension mobility is solely configured on a Cisco CallManager server as of Release 3.3(3).

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec87031

CSCed02757

Cisco CallManager fails to initialize when more than 2700 configured route patterns exist.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed02757

CSCed05307

The manager phone displays the wrong number for an assistant call.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed05307

CSCed05323

Administrators get an error message when Upgrade Assistant is uninstalled.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed05323

CSCed05329

Cisco CallManager has high CPU usage when you configure ART scheduler.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed05329

CSCed06857

Updating a calling search space that has large number of associated devices generates a forward signal storm that results in phones having delayed dial tones.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed06857

CSCed09683

Phones receive delay dial tones when you update a calling search space that is assigned to a pilot point number.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed09683

CSCed12260

Server recovery fails when groups do not get added before the backup is started.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed12260

CSCed13359

Users cannot enable the call forward all feature from the phone.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed13359

CSCed13391

Cisco CallManager has non-critical errors in the log after installation of Release 3.3(2)FP2 on the subscriber server.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed13391

CSCed14584

The Admin Utility tool does not display a warning message when the service account passwords are not the same on all servers in a cluster.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed14584

CSCed15174

Call gets forwarded to the wrong voice mail pilot number when the call is on a Q.SIG network.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed15174

CSCed16876

Cisco CallManager sets the Suppress DebugInformation for Router Death service parameter to 1 by default.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed16876

CSCed17381

Additional discard digits instruction (DDI) does not get presented in the dial plan.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed17381

CSCed18553

Email IDs get erased when you modify user information from an IP phone.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed18553

CSCed18717

Cisco CallManager displays a blank page when you delete a route filter while the publisher server is down.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed18717

CSCed18719

Cisco CallManager has an incorrect reason code when an IPMA phone is CFNA or CFB to a Cisco Unity voice-messaging system.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed18719

CSCed19703

Browser stops working when you query on profile names in Find/List Device Profile.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed19703

CSCed20359

The voice mail mask does not get applied when a call is forwarded through an intercluster trunk.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed20359

CSCed20832

Cisco CallManager displays the wrong synchronization status message in Cisco IP Address Book when the rule option is set to Do not Modify duplicate entries.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed20832

CSCed20907

During OS installation, administrators get an error message that states that no more partition can be created.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed20907

CSCed21059

Cisco IPMA assistant console displays error messages in the Call Details window.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed21059

CSCed21135

OS installation fails when the server is connected to a USB Keyboard/Video/Mouse (KVM) switch.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed21135

CSCed21675

Cisco CallManager Serviceability adds a CM prefix to the IP address of the server when you stop and restart Cisco CallManager and CTI Manager services.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed21675

CSCed22341

Cisco CallManager Administration failed after the server had been running for several days.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed22341

CSCed24478

BAT displays an error message when you delete phones by using custom files.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed24478

CSCed24859

Cisco CallManager attempts to establish SDL links with remote Cisco CallManager and CTI Manager nodes that are no longer in the cluster.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed24859

CSCed26619

Forwarded calls fail where a large number of devices are restarting.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed26619

CSCed27237

Search for Cisco IPMA assistants times out when more than 8000 objects exist in the directory.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed27237

CSCed27328

BAT inserts fail when you attempt to use a file name with a comma.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed27328

CSCed27859

The database layer registry does not point to the new database after an upgrade.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed27859

CSCed29687

Cisco CallManager server has high memory usage when you use BAT to export over 6000 phones.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed29687

CSCed29942

Cisco CallManager does not have a method for clearing the forward loop table without restarting the Cisco CallManager service.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed29942

CSCed30174

Cisco CallManager does not reset or audit a trunk when it receives a setup message from a gateway.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed30174

CSCed31009

Browser page crashes when you click the next button on the fourth page of External Route Plan Wizard after waiting for more than 20 minutes.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed31009

CSCed31026

Administrators get a remote scripting error message when you update the logout profile for different devices.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed31026

CSCed31154

Log file shows a successful insertion of a custom manager/assistant that was previously inserted.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed31154

CSCed31292

The wave driver does not release its buffers.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed31292

CSCed32488

ToneChangedEvents do not get sent to consult calls.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed32488

CSCed32958

Cisco IPMA assistant console does not automatically get updated.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed32958

CSCed35600

Cisco WebDialer does not work with Netscape Navigator.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed35600

CSCed39143

Performance Monitor does not define the Engineering Counters for Cisco CallManager System Performance.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed39143

CSCed40915

Administrators get an error message when they delete records that another table is using.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed40915

CSCed41711

The Skinny Client Control Protocol (SCCP) document does not define the message definition for StationDisplayPriNotifyMessageID.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed41711

CSCed43618

Cisco IP Phone does not correctly display the status of a shared line when the remote phone is rebooted.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed43618

CSCed44667

Cisco Messaging Interface (CMI) Service stops with a kUnknownException message.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed44667

CSCed47592

Cisco CallManager Administration should not allow anyone to enter special characters in the user information fields.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed47592

CSCed47782

Phone display only gets updated after an alert message when you use route lists.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed47782

CSCed48018

IP phone displays the barge softkey momentarily when the barge feature is disabled.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed48018

CSCed48468

Cisco CallManager Administration should not allow anyone to use special characters in the user password field.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed48468

CSCed51479

After phone profile is imported with BAT, IP phone loses line parameters when extension mobility user logs out.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed51479

CSCed52147

Cisco CallManager server stops.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed52147

CSCed52735

The manager lines get greyed out on Cisco IPMA assistant console when the scratch table orphans the manager records.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed52735

CSCed52773

Managers cannot log in to the Cisco IPMA manager web page in the Japanese locale.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed52773

CSCed53620

Updates to CSS do not take affect until Cisco CallManager service is restarted.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed53620

CSCed54137

Performance counters do not support specific channel activities on E1 PRI gateways.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed54137

CSCed54476

The personal address book in Cisco CallManager User does not support accented characters.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed54476

CSCed54956

IP phone hangs when it calls a device that is attached to a FXS port.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed54956

CSCed55022

TAPS does not log entries while the Cisco Security Agent is running.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed55022

CSCed55071

Cisco CallManager incorrectly reports that the PRI endpoint is registered.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed55071

CSCed55393

Consult conference call failed with Platform Error UNSPECIFIED message.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed55393

CSCed56086

Application Event Viewer logs numerous errors when the Real-Time Monitoring tool (RTMT) is started.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed56086

CSCed57491

Phone imports failed when extension mobility is enabled on a phone.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed57491

CSCed57970

The readme file for DC Directory Version 1.05 does not specify which version of Cisco CallManager is supported.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed57970

CSCed58020

Cisco.com does not have DC Directory scripts available for Cisco CallManager, Release 3.3(3).

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed58020

CSCed58739

Cisco CallManager throws an exception error when the call forward all database is updated.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed58739

CSCed59122

RTMT Performance Monitoring does not function properly.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed59122

CSCed59924

Extension mobility users cannot log out.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed59924

CSCed60875

Extension mobility users experience inconsistent behavior when CFA is enabled from Cisco CallManager Administration.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed60875

CSCed61186

Cisco CallManager inserts the wrong DN in the information element for a redirecting number.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed61186

CSCed61744

DC directory services fail to start because it is missing a file.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed61744

CSCed62262

IP phone does not display the called party number on a phone that has overlap sending enabled.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed62262

CSCed62483

Cisco CallManager Administration does not allow you to configure call throttling for individual nodes.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed62483

CSCed64712

After the publisher server is rebooted, incoming calls to a voice mail that uses dummy phone or route points fail.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed64712

CSCed66115

Phone erroneously displays the CFA icon after the phone reregisters.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed66115

CSCed66138

Cisco CallManager sends out-of-order alerting and established events.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed66138

CSCed66424

Application log displays many SQLCTR80.DLL exception errors.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed66424

CSCed66771

GetDeviceProfile, addDeviceProfile, and updateDeviceProfile have missing fields

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed66771

CSCed67344

IP phone does not display your current options label.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed67344

CSCed67643

Cisco CallManager Administrator does not prompt you to restart Cisco CallManager service after the Ethernet Phone Port has been changed.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed67643

CSCed68617

Cisco CallManager Administrator does not display all the call park numbers in the database.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed68617

CSCed68730

The event log reports a worldwide web counter error every 10 minutes when the worldwide web services is disabled.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed68730

CSCed69274

Cisco CallManager server does not assign unique Global Unique Identifier (GUID) for each user in DC directory.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed69274

CSCed69825

The network interface card (NIC) on IBM Media Convergence Servers with gigabit ethernet does not support hard-coded settings.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed69825

CSCed70072

The devices that are assigned to a media resource group (MRG) do not share the traffic load.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed70072

CSCed70985

Cisco CallManager drops intercluster trunk (ICT) call when you reset the trunk.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed70985

CSCed71032

International dial plan has limited translation pattern functionality.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed71032

CSCed71252

Interdigit timeout does not work on international call.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed71252

CSCed72311

You cannot create a Cisco IPMA link between a manager and a user on systems with Active Directory.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed72311

CSCed72524

Cisco Digit Number Analysis displays the overflow text message outside of the text box.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed72524

CSCed72607

Cisco CallManager Administration does not escape SQL wildcard characters and bracketed expressions when you attempt to search for a trunk.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed72607

CSCed72676

Cisco CallManager User Option displays an incorrect error message when users enter invalid characters in the nickname field.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed72676

CSCed72922

Fax calls fail when the ISDN Bearer Capability is set to 3.1 kHz audio.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed72922

CSCed73660

Cisco CallManager Administration has incorrect copyright information on the main page.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed73660

CSCed73666

Cisco CallManager Administration has incorrect copyright information on the Cisco CallManager User page.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed73666

CSCed73667

Cisco CallManager Administration has incorrect copyright information in User Login.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed73667

CSCed73689

Phone displays "To Private" when the MOH server is disabled.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed73689

CSCed74984

Cisco CallManager Administration displays incorrect error messages when you delete or update an already deleted attendant console user.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed74984

CSCed75390

Find route-pattern by partition fails when the name has an underscore character.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed75390

CSCed75754

LineDial takes 1 second to go from a dialing state to the connected state.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed75754

CSCed75940

Cisco CallManager Administration does not display an error message when you delete an already deleted pilot point number.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed75940

CSCed76063

Cisco IPMA displays an error when you change user device association.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed76063

CSCed77530

You cannot add Cisco ATA 186 phones.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed77530

CSCed77769

Cisco CallManager services stopped after an upgrade.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed77769

CSCed78143

Cisco IP Telephony Monitor (ITEM) cannot check the status of the check the status of the Cisco CallManager database without an active sqlmangr.exe process.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed78143

CSCed78326

DBInstall inserts a version number to the database even when no version number exists.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed78326

CSCed78510

Cisco CallManager logs different history sequences for placed calls in Release 3.3(2) and Release 3.3(3).

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed78510

CSCed78657

McAfee Netshield cannot automatically update the DAT files under Microsoft Windows OS version 2000.2.5 SR7.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed78657

CSCed78748

Administrators get error no.-2146828282 message when an invalid port is added to a Cisco 366x gateway.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed78748

CSCed79346

You cannot use new dial plans until you reconfigure or delete the route list.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed79346

CSCed79371

IP Voice Media Streaming application service failed to start.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed79371

CSCed79630

Cisco CallManager allows softkey template with an empty softkey call state template.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed79630

CSCed79852

BAT has missing Help information for a line text label in Gateway Directory Number.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed79852

CSCed79945

Administrators get a LDAP exception error when they query with an "is exactly" search filter in Active Directory.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed79945

CSCed79987

A Call Pickup Group contains "" query if DNA returns a list of phones without DN.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed79987

CSCed79991

IP phone displays the Cisco IPMA status window when a nonmanager extension mobility user logs in to a manager phone.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed79991

CSCed80030

Administrators get a COM error when they attempt to delete a meet me number from a subscriber server while the publisher server is down.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed80030

CSCed80547

Component version displays the incorrect version for the attendant console plugin.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed80547

CSCed80737

Cisco CallManager has delays when a partition name is changed.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed80737

CSCed80858

Cisco CallManager incorrectly reports that all servers are in the same domain.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed80858

CSCed81058

A query on DN or RP with a is exactly "" filter returns different results than a query on DN or RP with a is empty filter.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed81058

CSCed81124

Cisco CallManager disconnected an H.323 client call when the user unparked a number.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed81124

CSCed81127

No online help information exists for new user configuration fields.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed81127

CSCed81131

Cisco CallManager Administration does not properly validate name dialing entries.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed81131

CSCed81137

Help information for user configuration is incorrect.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed81137

CSCed81207

Default Device Profile Name in Subscribe IP Phone Service is incorrect.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed81207

CSCed81863

Cisco CallManager does not allow you to troubleshoot the accesses to the database when Cisco CallManager service accesses the database by using a fast access method.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed81863

CSCed82018

TAPI reused a call handle for a conference call that went into an idle state.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed82018

CSCed82223

GetAllARTMAManagers does not look for old profiles.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed82223

CSCed82702

Users encountered an error while the user is adding a perfmon counter.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed82702

CSCed83055

You cannot use Cisco CallManager Administration to add MGCP subunits.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed83055

CSCed86656

Extension mobility user, who logs out with callback enabled, does not get callback notification once the user logs back in.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed86656

CSCef26258

If you configure a duplicate directory number for multiple lines that are in different or the same Cisco CallManager partition, CTI only sends one instance of the line in response to requests from WebAttendant, ARC Console, and Attendant Console.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCef26258

CSCin18384

Cisco CallManager does not send an H.225 disconnect message when it loses connectivity with the originating gateway.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCin18384

CSCin24844

The IPMA manager display and softkeys do not work after a failover.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCin24844

CSCin51597

Cisco CallManager sets the source IP address for unicast music on hold at 0.0.0.0.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCin51597

CSCin52799

The == operator in Route filter accepts more than 10 digits.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCin52799

CSCin57144

Cisco CallManager does not properly validate the multicast IP address and port number in the Music on Hold Configuration.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCin57144

CSCin59045

Help for Cisco Extension Mobility Logout parameters has an incorrect default value.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCin59045

CSCin59391

Cisco CallManager does not properly validate the availability of a gateway when a route group is inserted.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCin59391

CSCin63437

Administrators get a remote scripting error message when they enter invalid characters during the configuration of a NM-HD-2VE network module.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCin63437

CSCin64094

The DNA tool displays a block this pattern result for calls that can be made matching that pattern.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCin64094

CSCin64169

Cisco CallManager Administration does not list the Default voice mail pilots and no voice mail pilots option when you search by Voice Mail Pilot Number.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCin64169

CSCin64572

User configuration displays a deleted pilot point as a primary extension.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCin64572

CSCin65128

Administrators get COM and exception errors when they update a subscriber server while the publisher SQL service is stopped.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCin65128

CSCin65337

The help page crashes when you select the next page from the home page.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCin65337

CSCin66359

MOH stops streaming when a call has a NetMeeting endpoint.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCin66359

CSCin69640

The called number transformation does not always occur for a translation pattern.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCin69640

CSCin69737

Cisco CallManager Dialed Number Analyzer cannot display results when you use Netscape Navigator, version 4.61.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCin69737

CSCuk45896

Administrators cannot modify Cisco CallManager glare properties for a PRI port that is connected to a DMS100.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCuk45896

CSCuk46137

IP phone does not play the ring tone when it receives an alerting message without Progress Indicator (PI).

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCuk46137

CSCuk46472

Cisco CallManager only updates the last configuration changes when you reset the gateway after updating FXO ports.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCuk46472

CSCuk48682

Cisco CallManager does not send the notify message when Call Forwarding Unconditional (CFU) is enabled.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCuk48682

CSCuk48829

Cisco CallManager does not include the display information in the notify message when a call is forwarded.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCuk48829

The following firmware caveats apply to this release.

CSCdz37347

Speed Dials do not display correctly in the Cisco CallManager User option pages for the Greek locale.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCdz37347

CSCea41220

Cisco IP Phone 7970 behaves inconsistently when you attempt to dial out from the directory menu while on an active call.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCea41220

CSCea67991

Cisco IP Phone 7970 does not display some messages during reregistration.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCea67991

CSCea69883

Cisco IP Phone 7970 does not automatically hang up a call when the phone is configured to auto-answer by using the speaker and the speakerphone is disabled.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCea69883

CSCea90398

A deleted user can access a phone.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCea90398

CSCeb32270

Call hangs up when you press digits on a phone that is attached to a WS-6608 during a transfer.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeb32270

CSCeb61038

Cisco IP Phones 7910 do not display the tilde or backslash characters properly.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeb61038

CSCeb85080

IP phone displays the DSP keepalive timeouts.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeb85080

CSCec09013

Cisco IP Phone 7970 has different streaming statistics than the Cisco IP Phone 7960.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec09013

CSCec20531

Cisco IP Conference Stations 7935 has a complicated upgrade process.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec20531

CSCec24177

Cisco IP Conference Stations 7935 and 7936 display the call forward all softkey.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec24177

CSCec35655

IP phone displays the translated number instead of the dialed digits.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec35655

CSCec42265

Users cannot change the software port configuration on a Cisco IP Phone 7910.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec42265

CSCec44490

You cannot enable or disable the PC port from the Network Configuration menu on Cisco IP Phones 7940 and 7960.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec44490

CSCec50629

User cannot access the shared line when the remote phone is in use.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec50629

CSCec63667

IP phone has display problems when you choose and save the same distinctive ring for the same line twice.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec63667

CSCec63670

Cisco IP Phone 7970 has display problems when you select distinctive rings for the different lines.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec63670

CSCec69956

While using inline power, the Cisco IP Phone 7970 cannot detect when the power supply is connected to the phone.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec69956

CSCec73534

Phone does not stop ringing when a call is disconnected on the far end.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec73534

CSCec78298

Cisco IP Phone 7910 cannot display the complete caller ID.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec78298

CSCed12269

Cisco IP Phone 7979 takes 1.8 second to display call information when the user presses the messages button.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed12269

CSCed19242

Cisco IP Conference Station 7936 fails to complete an upgrade when the Cisco CallManager server is down.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed19242

CSCed26422

Cisco IP Conference Station 7936 fails to upgrade to a new image when it encounters a Cisco CallManager server failure.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed26422

CSCed26723

Cisco IP Conference Station 7936 does not display the correct CAT IOS version for the Cisco Catalyst switch.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed26723

CSCed26786

Cisco IP Conference Station 7936 cannot display the corporate directory softkey when the conference station first registers.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed26786

CSCed31507

WS-6608 expands the In-Band DTMF Tone play time to greater than 40 msecs.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed31507

CSCed42262

Cisco IP Phone address book synchronization uses the display name in Outlook as a nickname.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed42262

CSCed52752

User experienced one-way audio on a call from a Cisco Wireless IP Phone 7920 to a Cisco IP Phone 7960.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed52752

CSCed57596

IP phone at the lowest volume setting is still audible.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed57596

CSCed57619

Call audio becomes choppy when you press keys during a call.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed57619

CSCed63528

Cisco IP Phone 7970 cannot display information when the user selects the Edit or FastDial softkeys and the nickname entry is longer than 28 characters

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed63528

CSCed64735

Cisco Wireless IP Phone 7920 cannot support more than two simultaneous calls on the same line.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed64735

CSCed65633

Cisco Wireless IP Phone 7920 cannot automatically reregister with the Cisco CallManager server when the phone returns to the coverage area.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed65633

CSCed66094

Cisco Wireless IP Phone 7920 reports that all reset codes are initialized during registration.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed66094

CSCed66121

Cisco IP Phone 7970 resets during a stress test.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed66121

CSCed66561

Cisco IP Phone 7970 cannot boot up after it loads new locale files.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed66561

CSCed67037

DHCP server cannot assign an IP address to a Cisco IP Phone 7912G.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed67037

CSCed68683

You cannot view information on another line on the Cisco IP Phone 7970 without answering the call.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed68683

CSCed69127

User receives a busy signal on the Cisco Wireless IP Phone 7920 when the phone is not in use.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed69127

CSCed69782

Cisco IP Conference Station 7935 cannot register with the Cisco CallManager server.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed69782

CSCed71035

Documentation does not warn users of potential loopback problems that are caused by Cisco IP Phones that are not powered up.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed71035

CSCed73971

Cisco IP Conference Station 7935 lost connectivity when it received a RTP broadcast message.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed73971

CSCed77772

IP Phone does not send Voice VLAN ID (VVID) in the dot1q frame.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed77772

CSCed79381

User receives robotic or tinny voices on a call when another call in the same gateway is connected to multicast MOH.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed79381

CSCin60521

You cannot configure the administrative VLAN ID by using the Cisco IP Conference Station 7935 web page.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCin60521

CSCin66926

Phones cannot display the callback notification message when the phones are displaying predialed digits on the LCD screen.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCin66926

CSCin69586

You cannot link one input page to another on a Cisco IP Phone.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCin69586


Documentation Updates

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

Errors

This section includes errors that the Cisco CallManager Documentation suite contains.

Locale Installer

The Cisco CallManager Documentation Guide for Release 3.3(4) incorrectly refers to Using the Cisco IP Telephony Locale Installer for Cisco CallManager 3.3(4). The correct document is Using the Cisco IP Telephony Locale Installer with Cisco CallManager 3.3(3)sr1.

Microsoft Outlook Support with Cisco WebDialer

The Cisco WebDialer API Reference chapter in the Cisco WebDialer Guide states that the makeCallSoap interface (that is used by plug-in clients such as Microsoft Outlook Plug-In) is accessed by initiating a Simple Object Access Protocol (SOAP) request to a specified URL. The specified URL contains the IP address of the Cisco CallManager server. However, Cisco does not provide a Cisco WebDialer plug-in that works with Microsoft Outlook. If you require this type of plug-in, contact a third-party vendor or partner.

Changes

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 CallManager Attendant Console

The name Cisco CallManager Attendant Console now appears as Cisco CM Attendant Console on the drop-down menu items under Service in Cisco CallManager Administration. The menu items for Cisco CallManager Attendant Console User and Cisco CallManager Attendant Console Server now appear as Cisco CM Attendant Console User and Cisco CM Attendant Console Server.

Calling Search Space

When you update a Calling Search Space in Cisco CallManager Administration, you do not have to restart the devices for the changes to take effect.


Note If you choose to restart the devices, be aware that calls on the affected gateways drop.


Cisco CallManager Extension Mobility Logout

Cisco CallManager System guide incorrectly states that Cisco Extension Mobility Logout service requires the Cisco CallManager service when Cisco Extension Mobility Logout service actually has no dependency on the Cisco CallManager service.

Cisco CallManager System guide also incorrectly states that Cisco CallManager Extension Mobility feature requires that the Cisco Extension Mobility Logout service be run on servers that have devices that are registered to the feature. In fact, the Extension Mobility Logout service does not need to be running on the same machine where the devices are registered. The Extension Mobility application accesses a set of servers that are configured in the directory (one server is active at a time). The Extension Mobility Logout service needs to run on the server that the Extension Mobility application accesses.

Custom Phone Rings

The "Custom Phone Rings" chapter now exists in the Cisco CallManager Features and Services Guide.

Omissions

This section lists new and additional information that the current Cisco CallManager documentation does not include.

New Service Parameter for Cisco CallManager Extension Mobility

Cisco CallManager 3.3(3) introduces a new service parameter for Cisco CallManager Extension Mobility. The Cisco CallManager Extension Mobility chapter in the Cisco CallManager Features and Services Guide does not document this information.

At the service parameter field, Remember last user logged in, you can choose True to specify that the Extension Mobility application remembers the user ID of the last user that logged in to the phone. The default value for the service parameter specifies False.


Note As with all system parameters, the setting of this system parameter applies it to all users in the Cisco CallManager cluster.


This setting proves useful in situations where individuals use their own phone on a regular basis and no one else uses that phone. For example, user may use Cisco CallManager Extension Mobility to enable the types of calls that are allowed from a phone. Individuals who are using their office phone in a logout state can make only internal or emergency calls, but after logging in using Cisco CallManager Extension Mobility, the user also can make local, long-distance, and international calls. In this scenario, only this user regularly logs in to the phone. It makes sense to set the Extension Mobility application to remember the last user ID that is logged in.

In a true hoteling scenario, where users can come into any office and use any phone on a temporary basis, set this parameter to false.

H.323 Configuration Settings

The following configuration settings for H.323 have been added to the Phone Configuration Settings table in the Phone Configuration chapter in Cisco CallManager Administration Guide.

Table 3

Field
Description
H.323 Information

Outgoing Caller ID Pattern

For incoming calls to the phone, enter the pattern, from 0 to 24 digits, that you want to use for caller ID.

Calling Party Selection

Choose the directory number that is sent on an outbound call on a gateway.

The following options specify which directory number is sent:

Originator—Send the directory number of the calling device.

First Redirect Number—Send the directory number of the redirecting device.

Last Redirect Number—Send the directory number of the last device to redirect the call.

First Redirect Number (External)—Send the external directory number of the redirecting device.

Last Redirect Number (External)—Send the external directory number of the last device to redirect the call.

Calling Party Presentation

Choose whether the Cisco CallManager transmits or blocks caller ID.

Choose Allowed if you want the Cisco CallManager to send caller ID.

Choose Restricted if you do not want the Cisco CallManager to send caller ID.

Display IE Delivery

This check box enables delivery of the display information element (IE) in SETUP and CONNECT messages for the calling and called party name delivery service.

The default setting checks this check box.

Redirecting Number IE Delivery - Outbound

Check this check box to include the Redirecting Number IE in the outgoing SETUP message from the Cisco CallManager to indicate the first redirecting number and the redirecting reason of the call when the call is forwarded.

Uncheck the check box to exclude the first redirecting number and the redirecting reason from the outgoing SETUP message.

You use Redirecting Number IE for voice-messaging integration only. If your configured voice-messaging system supports Redirecting Number IE, you should check the check box.

Note The default setting leaves this check box unchecked.

Redirecting Number IE Delivery - Inbound

Check this check box to accept the Redirecting Number IE in the incoming SETUP message to the Cisco CallManager.

Uncheck the check box to exclude the Redirecting Number IE in the incoming SETUP message to the Cisco CallManager.

You use Redirecting Number IE for voice-messaging integration only. If your configured voice-messaging system supports Redirecting Number IE, you should check the check box.

Note Default leaves the check box unchecked.

Media Termination Point Required

Indicate whether a media termination point (MTP) is used to implement features that H.323 does not support (such as hold and transfer).

Check the Media Termination Point Required check box if you want to use a media termination point to implement features. Uncheck the Media Termination Point Required check box if you do not want to use a media termination point to implement features.

Use this check box only for H.323 clients and those H.323 devices that do not support the H.245 empty capabilities set or if you want media streaming to terminate through a single source.

If you check this check box to require an MTP and this device becomes the endpoint of a video call, the call will be audio only.


H.323 Configuration Settings

Defining the Quality of Service (QoS) Values

Because the "NA" and "Infinity" values for the QoS parameters that the Cisco CallManager Serviceability CDR Analysis and Reporting (CAR) tool uses are case-sensitive, these values must be entered exactly as shown; the system does not support other forms.

Quality Report Tool Configuration Settings

Cisco CallManager 3.3 introduces the Quality Report Tool (QRT) feature. The Cisco CallManager 3.3 release documentation does not provide specific information about configuring and using the QRT feature.

The Cisco CallManager Features and Services Guide for Cisco CallManager release 4.1 will include the following information about QRT:

QRT Overview

User Interfaces

Creating a Softkey Template with the QRT Softkey

Configuring the QRT Softkey Template in Device Pool

Adding the QRT Softkey Template in Phone Configuration

Activating the Cisco Extended Functions Service for QRT

Configuring Alarms and Traces for QRT

Setting the Cisco Extended Functions Service Parameters for QRT

Using the QRT Viewer

QRT Overview

The Quality Report Tool, a voice-quality and general problem-reporting tool for Cisco IP Phones, extends to IP phones as a Windows NT service.

As a feature within the Cisco Extended Functions service, QRT automatically loads with the Cisco CallManager installation. The Cisco CallManager system administrator enables the QRT feature through the use of softkey templates.

Perform these steps after installation to enable QRT availability for users and to set up reporting capabilities:

1. Properly configure the QRT feature for Cisco IP Phone users. You can configure QRT availability for up to four different call states (Connected, Connected Transfer, Connected Conference, and On Hook).

2. From Cisco CallManager Serviceability, activate the Cisco Extended Functions service and configure alarms and traces for use with QRT.

3. Define how the QRT feature will work in your system by configuring the applicable system parameters for the Cisco Extended Functions.

4. Create, customize, and view phone problem reports by using the QRT Viewer application.


Note Users with administrator privileges can configure QRT and view the reports.


User Interfaces

You can choose to enable two different user modes, depending upon the amount of information that you want users to submit:

Interview Mode—In this mode, the user sees extended menu choices, allowing additional user input related to audio quality on the IP phone and providing the ability to report other, non-audio-related problems such as the phone rebooting or the inability to make calls.

The system supports interview mode only when the IP phone is in the Connected or On Hook call state.

Silent Mode—In this mode, the user does not see extended menu choices. When the user presses the QRT softkey, the system collects streaming statistics and logs the report without additional user interaction.

The system supports silent mode only when the IP phone is in the Connected, Connected Conference, or Connected Transfer call state.

When users experience problems with their IP phones, they can invoke QRT by pressing the QRT softkey on their Cisco IP Phone to easily and accurately report voice quality and other general problems.

Creating a Softkey Template with the QRT Softkey

Perform the following procedure to create a new softkey template with the QRT softkey.

Procedure


Step 1 From Cisco CallManager Administration, choose Device > Device Settings > Softkey Template.

The Softkey Template Configuration window displays.

Step 2 From the Softkey Template list, or from the drop-down list box in the Create a softkey template based on field, choose the Standard User softkey template. (If you choose the first option, the Softkey Template Configuration window automatically displays with new information. Go to Step 3.)

Step 3 Click the Copy button.

The Softkey Template Configuration window displays with new information.

Step 4 In the Softkey Template Name field, enter a new name for the template; for example, QRT Standard User.

Step 5 Click the Insert button.

The Softkey Template Configuration redisplays with new information.

Step 6 To add the QRT softkey to the template, click the Configure Softkey Layout link.

The Softkey Layout Configuration window displays. You must add the QRT softkey to the Connected, Connected Conference, Connected Transfer, and On Hook call states.

Step 7 To add the QRT softkey to the On Hook call state, click the On Hook link in the Call States field.

The Softkey Layout Configuration window redisplays with the Unselected Softkeys and Selected Softkeys lists.

Step 8 From the Unselected Softkeys list, choose the Quality Report Tool (QRT) softkey and click the right arrow to move the softkey to the Selected Softkeys list.

Step 9 To save and continue, click the Update button.

Step 10 To add the QRT softkey to the Connected, Connected Conference, and Connected Transfer call states, repeat Step 7 through Step 9 for each individual call state.


Note Ensure that you configure the QRT softkey only for the supported call states and click the Update button after each entry.



Configuring the QRT Softkey Template in Device Pool

Perform the following procedure to add the QRT softkey template to the device pool.

Procedure


Step 1 From Cisco CallManager Administration, choose System > Device Pool.

The Device Pool Configuration window displays.

Step 2 Choose the Default device pool or any previously created device pool that is listed in the Device Pools.

You can add the template to the default device pool if you want all users to have access to the QRT softkey, or you can create a customized device pool for QRT feature users.

Step 3 In the Softkey Template field, choose the softkey template that contains the QRT softkey from the drop-down list box.

Step 4 Click the Update button.


Adding the QRT Softkey Template in Phone Configuration

Perform the following procedure to add the QRT softkey template to each user phone.

Procedure


Step 1 From Cisco CallManager Administration, choose Device > Phone.

The Find and List Phones window displays.

Step 2 Find the phone to which you want to add the softkey template.

In the Softkey Template field, choose the softkey template that contains the QRT softkey from the drop-down list box.

Step 3 Click the Update button.


Activating the Cisco Extended Functions Service for QRT

Follow this procedure to activate the Cisco Extended Functions service for use with the QRT feature.

Procedure


Step 1 From Cisco CallManager Serviceability, choose Tools > Service Activation.

A list of Cisco CallManager servers displays.

Step 2 Click on the Cisco CallManager server to choose it for activation of the Cisco Extended Functions service.

Step 3 Check the Cisco Extended Functions check box.

Step 4 Click Update.


Configuring Alarms and Traces for QRT

Follow this procedure to configure alarms and SDI traces through Cisco CallManager Serviceability.

Procedure


Step 1 For alarm configuration, choose Alarm > Configuration from the Cisco CallManager Serviceability window.

A list of Cisco CallManager servers displays.

Step 2 Click the Cisco CallManager server to select it for alarm configuration.

Step 3 From the Configured Services window, click Cisco Extended Functions.

Step 4 Check the Enable Alarm check box for both Event Viewer and SDI Trace.

Step 5 Click Update.

Step 6 For trace configuration, choose Trace > Configuration from the Cisco CallManager Serviceability window.

A list of Cisco CallManager servers displays.

Step 7 Click the Cisco CallManager server to select it for trace configuration.

Step 8 From the Configured Services window, click Cisco Extended Functions.

Step 9 Check the Cisco Extended Functions Trace Fields check box.

Step 10 Click Update.


For more information, refer to the Cisco CallManager Serviceability Administration Guide.

Setting the Cisco Extended Functions Service Parameters for QRT

Set the Cisco Extended Functions service parameters by using Cisco CallManager Administration to access the service parameters (Service > Service Parameters). Choose the server where the QRT application resides and then choose the Cisco Extended Functions service.

Cisco recommends that you use the default service parameters settings unless the Cisco Technical Assistance Center (TAC) instructs you to do otherwise.

Cisco Extended Functions includes the following parameters for QRT:

Display extended menu choices—Determines whether extended menu choices are presented to the user. Set this field to true to display extended menu choices (interview mode) or set this field to false to not display extended menu choices (silent mode).

Recommended default value specifies false (silent mode).

Streaming statistics polling duration—Determines the duration that is used for polling streaming statistics. Set this field to -1 to poll until the call ends, set it to 0 to not poll at all, or set it to any positive value to poll for that many seconds. Polling stops when the call ends.

Recommended default value specifies -1 (poll until the call ends).

Streaming statistics polling frequency (seconds)— Designates the number of seconds to wait between each poll. The value range is between 30 and 3600.

Recommended default value specifies 30.

Log File—Specifies the path where the QRT report files are located. Users must have the proper privileges to access these files.

Recommended default value specifies
C:\Program Files\Cisco\QRT\QRT.xml.

Maximum No. of Files—Specifies the maximum number of files before restarting the file count and overwriting old files. The value range is between 1 and 10000.

Recommended default value specifies 250.

Maximum No. of Lines per File—Specifies the maximum number of lines in each file before starting the next file. The value range is between 100 and 2000.

Recommended default value specifies 2000.

Using the QRT Viewer

You can use the QRT Viewer to view the IP phone problem reports that the Quality Report Tool generates. The QRT Viewer allows you to filter, format, and view the tool-generated phone problem reports, so they provide you with the specific information that you need.

For detailed information about accessing, configuring, using, and customizing the IP phone problem reports, refer to the Cisco CallManager Serviceability Administration Guide.

Exporting and Importing Phones with More Than One User

When you use BAT to export phone records that have multiple users who control a phone, the export utility generates a unique phone record for each user. (The phone information remains the same, but each record has a different user ID.) When you import the exported file that contains phones with multiple users, the first phone record inserts with the associated user. However, subsequent phone records fail to insert, even though BAT attempts to insert all records and accepts the user association to the phone. In this case, the log file for the import transaction shows that the phone insertions failed for all users except the first user who is associated with the phone.

Device Profile Default Configuration

The online help for the Cisco CallManager application does not include information about Device Profile Defaults. The following sections provide information about configuring and updating device profile defaults:

Device Profile Default Overview

Adding a New Device Profile Default

Updating Device Profile Defaults

Deleting a Device Profile Default

Device Profile Default Configuration Settings

Device Profile Default Overview

Use the device profile default whenever a user logs on to a phone model for which no user device profile exists. To create a device profile default for each phone model that supports Cisco Extension Mobility, use the Cisco CallManager Device Profile Default Configuration window. The maximum number of device profile defaults cannot exceed the number of phone models that support Cisco CallManager Extension Mobility.

For example, a user logs on to a Cisco IP Phone model 7960 for which there is a user device profile. The user device profile for the user gets downloaded to the phone to which the user logged on. Later, the same user logs on to a Cisco IP Phone model 7940 for which no user device profile exists. In this case, the device profile default for the Cisco IP Phone model 7940 gets downloaded to the phone.

A device profile default comprises the set of attributes (services and/or features) that are associated with a particular device. Device profiles include device type, user locale, phone button template, softkey template, and Cisco IP Phone services.

Adding a New Device Profile Default

The device profile default contains attributes such as device type, phone template, user locale, expansion modules, softkey template, and subscribed Cisco IP Phone services. Perform the following procedure to add a device profile default.

Procedure


Step 1 Choose Device > Device Settings > Device Profile Default.

The Device Profile Default Configuration window displays.

Step 2 Click the Add a New Device Profile Default link.

Step 3 Configure each field as described in Table 4.

Step 4 Click Insert.

The device profile displays in the Device Profile Default pane.


Updating Device Profile Defaults

This section describes how to update a device profile default.

Procedure


Step 1 Choose Device > Device Settings > Device Profile Default.

Step 2 From the Device Profile Default pane, click the device profile that you want to update.

The Device Profile Default Configuration window displays the profile information of the profile that you chose.

Step 3 Make the desired changes to the profile as described in Table 4.

Step 4 Click Update.


Deleting a Device Profile Default

This section describes how to delete a device profile default.

Procedure


Step 1 Choose Device > Device Settings > Device Profile Default.

Step 2 From the Device Profile Default pane, click the device profile that you want to delete.

The Device Profile Default Configuration window displays the profile information of the profile that you chose.

Step 3 Click Delete.

A message displays that states that this action cannot be undone.

Step 4 To delete the device profile default, click OK or, to cancel the deletion, click Cancel.


Device Profile Default Configuration Settings

Table 4 describes the fields that are available in the Cisco CallManager Device Profile Default Configuration window.

Table 4 Device Profile Default Configuration Settings 

Field
Description
Device Profile Default Information

Device Type

This field specifies the device (such as an IP phone) for which a profile gets created.

User Hold Audio Source

To specify the audio source that plays when a user initiates a hold action, click the drop-down arrow and choose an audio source from the list that displays.

If you do not choose an audio source, Cisco CallManager uses the audio source that is defined in the device pool or uses the system default if the device pool does not specify an audio source ID.

Note You define audio sources in the Music On Hold Audio Source Configuration window. For access, choose Service > Music On Hold.

User Locale

From the drop-down list box, choose the locale that is associated with the phone user interface. The user locale identifies a set of detailed information, including language and font, to support users.

Cisco CallManager makes this field available only for phone models that support localization.

Note If no user locale is specified, Cisco CallManager uses the user locale that is associated with the device pool.

Note If the users require information to display (on the phone) in any language other than English, verify that the locale installer is installed before configuring user locale. Refer to the Cisco IP Telephony Locale Installer documentation.

Phone Button Template Information

Phone Button Template

Choose the appropriate phone button template. The phone button template determines the configuration of buttons on a phone and identifies which feature (line, speed dial, and so on) is used for each button.

Softkey Template Information

Softkey Template

Choose the appropriate softkey template. The softkey template determines the configuration of the softkeys on Cisco IP Phones. Leave this field blank if the device pool contains the assigned softkey template.

Expansion Module Information

Module 1

If these fields display for the phone model, choose the 7914 14-button expansion module or none.

Module 2

If these fields display for the phone model, choose the 7914 14-button expansion module or none.


Subscribing Services to a Device Profile Default

To subscribe a service such as Cisco CallManager Extension Mobility to the device profile default, perform the following procedure:

Procedure


Step 1 Choose Device > Device Settings > Device Profile Default.

Step 2 From the Device Profile Default pane, click the device profile that you want to update.

The Device Profile Default Configuration window displays the profile information of the profile that you chose.

Step 3 Click the Subscribe/Unsubscribe Services link to add Cisco IP Phone services to this profile.

The Subscribe Cisco IP Phone services window displays.

Step 4 From the Select a Service drop-down list box, choose the service that you want to add to the profile.

Step 5 Click Continue.

The window displays with the service that you chose. If you want to choose a different service, click Back and repeat Step 4.

Step 6 If a parameter exists for the service, enter the value for the parameter. For information on the parameter, click the Description link.

Step 7 Click Subscribe.

The service appears in the Subscribed Services list.


User Settings in Cisco CallManager Administration

The Cisco CallManager Administration Guide does not provide information for all the user settings that display in Cisco CallManager Administration. Table 5 provides a description of the user settings.

Table 5 User Configuration Settings 

Setting
Description

First Name

Enter the user first name.

Last Name

Enter the user last name.

UserID

Enter the user identification name. Cisco CallManager does not permit modifying the user ID after it is created.

User Password

Enter five or more alphanumeric characters for the user password.

Confirm Password

Enter the user password again.

PIN

Enter five or more numeric characters for the Personal Identification Number.

Confirm PIN

Enter the PIN again.

Telephone Number

Enter the user telephone number.

Manager UserID

Enter the name of the user manager ID. The manager name that you enter must already exist in the directory as a user.

Department

Enter the user department number.

User Locale

From the drop-down list box, choose the locale that is associated with the user. The user locale identifies a set of detailed information to support users, including language and font.

Cisco CallManager uses this locale for Extension Mobility and the Cisco IP Phone User Options. For Cisco CallManager Extension Mobility log on, the locale that is specified here takes precedence over the device and device profile settings. For Cisco CallManager Extension Mobility log off, Cisco CallManager uses the user locale that is specified in the default device profile.

Note If you do not choose a user locale, the locale that is specified in the Cisco CallManager service parameters as Default User Locale applies.

Enable CTI Application Use

To configure users so they can use Computer Telephony Integration (CTI) applications, check the Enable CTI Application Use check box.

Call Park Retrieval Allowed

To configure users so they can retrieve parked calls, check the Call Park Retrieval Allowed check box.

Name Dialing

This field, which is required for Cisco Auto Attendant, displays after you enter the attendant name and associate Cisco Auto Attendant with Cisco CallManager.

Associated PC

This field, which is required for Cisco SoftPhone and Cisco CallManager Attendant Console users, displays after you enter the IP address or hostname for the user PCs. For Cisco SoftPhone, you enter the information in the User Configuration window in Cisco CallManager Administration. For Cisco CallManager Attendant Console, you enter the IP address/hostname after you log in to the client PC for the first time.

Primary Extension

This field displays after the user is added and represents the primary directory number for the user. You choose no primary extension when you associate devices with users.

This configuration affects the No Primary Extension and Primary Ext. settings in the Device Association window.

ICD Extension

This field, which displays after you have configured the agent for CRA/CRS, indicates that the device is associated with the agent user.

This configuration affects the No ICD Extension and ICD Ext. settings in the Device Association window.

Controlled Devices

This field displays after the user is added. After the device is associated, this field displays the description information (for example, the MAC address) that the user controls.

Enable Authentication Proxy Rights

This field, which is required if the authentication proxy rights for a user with Cisco CallManager Extension Mobility is enabled, displays after the user is added. If authentication proxy rights is enabled, this field displays True; if disabled, this field displays False.

View page in

From the drop-down list box, choose the language in which the information in the User Configuration window will display.

Choosing an option only changes the language that displays for the current web session. The next time that you log in to Cisco CallManager Administration, the User Configuration window will display information in the default language.

If your preferred language does not display from the drop-down list box, install the appropriate Cisco IP Telephony Locale Installer that is available on the locale installer software page on the web.

Check All on Page

When you check this check box, the system automatically checks all check boxes for the devices that display in the current Device Association window.

Check All in Search

When you check this check box in the Device Association window, the system automatically checks all checks box for all devices that display after the search occurs.


Obtaining Documentation

Cisco documentation and additional literature are available on Cisco.com. Cisco also provides several ways to obtain technical assistance and other technical resources. These sections explain how to obtain technical information from Cisco Systems.

Cisco.com

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

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

You can access the Cisco website at this URL:

http://www.cisco.com

International Cisco websites can be accessed from this URL:

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

Ordering Documentation

You can find instructions for ordering documentation at this URL:

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

You can order Cisco documentation in these ways:

Registered Cisco.com users (Cisco direct customers) can order Cisco product documentation from the Ordering tool:

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

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

Documentation Feedback

You can submit e-mail comments about technical documentation to bug-doc@cisco.com.

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

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

We appreciate your comments.

Obtaining Technical Assistance

For all customers, partners, resellers, and distributors who hold valid Cisco service contracts, the Cisco Technical Assistance Center (TAC) provides 24-hour-a-day, award-winning technical support services, online and over the phone. Cisco.com features the Cisco Technical Support Website as an online starting point for technical assistance. If you do not hold a valid Cisco service contract, please contact your reseller.

Cisco Technical Support Website

The Cisco Technical Support Website provides online documents and tools for troubleshooting and resolving technical issues with Cisco products and technologies. The Cisco Technical Support Website is available 24 hours a day, 365 days a year. The Cisco Technical Support Website is located at this URL:

http://www.cisco.com/tac

Accessing all the tools on the Cisco Technical Support Website requires a Cisco.com user ID and password. If you have a valid service contract but do not have a login ID or password, register at this URL:

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

Opening a TAC Case

Using the online TAC Case Open Tool is the fastest way to open P3 and P4 cases. (P3 and P4 cases are those in which your network is minimally impaired or for which you require product information.) After you describe your situation, the TAC Case Open Tool automatically recommends resources for an immediate solution. If your issue is not resolved using the recommended resources, your case will be assigned to a Cisco TAC engineer. The online TAC Case Open Tool is located at this URL:

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

For P1 or P2 cases (P1 and P2 cases are those in which your production network is down or severely degraded) or if you do not have Internet access, contact Cisco TAC by telephone. Cisco TAC engineers are assigned immediately to P1 and P2 cases to help keep your business operations running smoothly.

To open a case by telephone, use one of the following numbers:

Asia-Pacific: +61 2 8446 7411 (Australia: 1 800 805 227)
EMEA: +32 2 704 55 55
USA: 1 800 553-2447

For a complete listing of Cisco TAC contacts, go to this URL:

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

TAC Case Priority Definitions

To ensure that all cases are reported in a standard format, Cisco has established case priority definitions.

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

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

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

Priority 4 (P4)—You require information or assistance with Cisco product capabilities, installation, or configuration. There is little or no effect on your business operations.

Obtaining Additional Publications and Information

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

Cisco Marketplace provides a variety of Cisco books, reference guides, and logo merchandise. Go to this URL to visit the company store:

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

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

http://cisco.com/univercd/cc/td/doc/pcat/

Cisco Press publishes a wide range of general networking, training and certification titles. Both new and experienced users will benefit from these publications. For current Cisco Press titles and other information, go to Cisco Press online at this URL:

http://www.ciscopress.com

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

http://www.cisco.com/packet

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

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

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

http://www.cisco.com/ipj

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

http://www.cisco.com/en/US/learning/index.html