Release Notes for Cisco CallManager Release 4.0(2) [Cisco Unified Communications Manager (CallManager)]

Table Of Contents

Release Notes for Cisco CallManager Release 4.0(2)

Contents

Introduction

System Requirements

Determining the Software Version

Compatibility Matrix and Supported Upgrades

Related Documentation

New and Changed Information

Upgrading to Cisco CallManager Release 4.0(2)

Cisco CallManager Extension Mobility Enhancements

System Enhancement for Route Group and Line Group Processing

Voice Mail Configuration Enhancements

Voice-Mail Pilot Configuration

Voice-Mail Profile Configuration

Cisco Unity Voice-Mail Port Adjustments

Route List Redundancy Configuration

SRST Algorithm Enhancements

Operating System Installation Guidelines

Disabling Cisco RIS Data Collector Prior to Upgrading to Cisco CallManager Release 4.0(2)

New and Updated Support for Cisco IP Phones

Support for Cisco VT Advantage

Dialed Number Analyzer

International Dial Plan

Changes to Type Specific Information in the Gateway Configuration Settings

Calling Search Space Enhancements

Conference Enhancements

Attendant Console Enhancements

NM-HDV2 and NM-HD Support for Cisco CallManager

Security Enhancements

Static Digit Analysis

Using Query to Delete Phones

Using Immediate Divert with Hunt Lists

New and Changed Information for Cisco CallManager Serviceability

Cisco CallManager Renamed After Restarting Services

TroubleShooting Trace Setting

Cisco CallManager Trace Collection Tool

Real-Time Monitoring Tool as Standalone Plug-in

Serviceability Reports Archive

SNMP and Performance Counter Enhancements

CDR Analysis and Reporting (CAR) Enhancements

New and Changed Information for Third-Party and SDK Applications

Important Notes

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

Adding Cisco CallManager Servers

Installing IPMA Assistant Console on Microsoft Windows XP

Locale Installer for Cisco CallManager

Line Group/Route Group Support for MLPP-Enabled Devices

Using the JTAPI Update Utility with CRS

End User Notes

Attendant Console

Resolved Caveats for Cisco CallManager - Release 4.0(2)

Open Caveats for Cisco CallManager - Release 4.0(2)

Documentation Updates

Errors

Deleting a Conference Device

Deleting a Music On Hold Server

Deleting a Media Termination Point

System Requirements for Barge and Privacy

Configuring Maximum Calls and Busy Trigger Settings for Shared Line Appearances

User Configuration Settings

Cisco CallManager Service Activation/Deactivation

Cisco IP Phone Support

SIP/UDP Port Configuration

Route Pattern Configuration Fields

Cisco IP Phone Configuration Fields

Malicious Call Identification

Translation Pattern Configuration

Calling Search Space Configuration

Partition Field Configuration

Configuring Digits in Configuration Fields

Cisco Call Back Synchronous Request Timeout Configuration

Cisco CallManager Dialed Number Analyzer Private Phrase Requirement

Cisco CallManager Extension Mobility Logout

Using Attendant Console and Shared Lines

Date/Time Configuration Changes

Adding and Deleting Users by Using Cisco CallManager Administration

Changes

IPMA Clusterwide Parameters for Softkey Templates

Ad Hoc Conference Limitations

Meet-Me Conference Limitations

Omissions

CTI Monitored Lines

Quality Report Tool Configuration Settings

SRST Fallback Algorithm Enhancements

Defining the Quality of Service (QoS) Values

User Settings in Cisco CallManager Administration

Updated BAT Field Descriptions

Fax and Modem Connectivity

Using Annunciator with Conference Bridges

Static Digit Analysis

Q.SIG Support with JTAPI and TAPI

Cisco Unity Voice-Mail Port Changes

Obtaining Documentation

Cisco.com

Ordering Documentation

Documentation Feedback

Obtaining Technical Assistance

Cisco Technical Support Website

Submitting a Service Request

Definitions of Service Request Severity

Obtaining Additional Publications and Information

Release Notes for Cisco CallManager Release 4.0(2)

Updated June 23, 2008

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

Note To view the release notes for Cisco CallManager release 4.0(1), which contains information about prior release changes, go to the following URL: http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/rel_notes/4_0/cucm-rel_notes-401.html

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

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

To access the documentation suite for voice products, refer to the following URL:

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

You can access the latest software upgrades and release notes for Cisco CallManager 4.0 on Cisco Connection Online (CCO) at:

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

Contents

These release notes discuss the following topics:

•Introduction

•System Requirements

•Compatibility Matrix and Supported Upgrades

•Related Documentation

•New and Changed Information

•New and Changed Information for Cisco CallManager Serviceability

•New and Changed Information for Third-Party and SDK Applications

•Important Notes

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

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

•Documentation Updates

•Obtaining Documentation

•Obtaining Technical Assistance

Introduction

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

System Requirements

Make sure that you install and configure Cisco CallManager release 4.0 on a Cisco Media Convergence Server (MCS).

For information about installing Cisco CallManager release 4.0 on a Cisco Integrated Communications System (ICS) 7750, go to http://www.cisco.com/public/sw-center/telephony/ics-7750/ics-compatibility.shtml.

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

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

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

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

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

Determining the Software Version

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

•Cisco CallManager System version

•Cisco CallManager Administration version

•Database information and database DLL versions

Compatibility Matrix and Supported Upgrades

You can find which application versions are compatible with Cisco CallManager release 4.0(2) and which previous release of Cisco CallManager has upgrade support by referring to the Cisco CallManager Compatibility Matrix at http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/compat/ccmcompmatr1.pdf

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

Related Documentation

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

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

Along with the documents listed in the Cisco CallManager Document Guide, the following list specifies other related documents for Cisco CallManager release 4.0:

•Cisco CallManager Call Detail Record Definition

•Cisco IP Phone Services Application Development Notes

•Cisco JTAPI Installation Guide for Cisco CallManager 4.0(1)

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

•Cisco TAPI Installation Guide for Cisco CallManager 4.0(1

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

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

•System Error Message

•Cisco CallManager 4.0(1) AXL Programming Guide

•Cisco CallManager 4.0(1) AXL Serviceability Programming Interface Guide

•Cisco CallManager Dialed Number Analyzer Guide

•Cisco WebDialer API Reference

New and Changed Information

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

•Upgrading to Cisco CallManager Release 4.0(2)

•Cisco CallManager Extension Mobility Enhancements

•System Enhancement for Route Group and Line Group Processing

•Voice Mail Configuration Enhancements

•Cisco Unity Voice-Mail Port Adjustments

•Route List Redundancy Configuration

•SRST Algorithm Enhancements

•Operating System Installation Guidelines

•Disabling Cisco RIS Data Collector Prior to Upgrading to Cisco CallManager Release 4.0(2)

•New and Updated Support for Cisco IP Phones

•Support for Cisco VT Advantage

•Dialed Number Analyzer

•International Dial Plan

•Changes to Type Specific Information in the Gateway Configuration Settings

•Calling Search Space Enhancements

•Conference Enhancements

•Attendant Console Enhancements

•NM-HDV2 and NM-HD Support for Cisco CallManager

•Security Enhancements

•Static Digit Analysis

•Using Query to Delete Phones

•New and Changed Information for Cisco CallManager Serviceability

•New and Changed Information for Third-Party and SDK Applications

Upgrading to Cisco CallManager Release 4.0(2)

If your server runs Cisco CallManager release 4.0(1), you can upgrade your server to release 4.0(2) by using the web download file that is available at http://www.cisco.com/public/sw-center/sw-voice.shtml.

If your server runs Cisco CallManager release 3.2 or 3.3, you must use the CD-ROM disks from the Cisco CallManager release 4.0(2) software kit to upgrade the Cisco CallManager software to version 4.0(2); you cannot use the version that is posted on CCO. For detailed instructions, refer to Upgrading Cisco CallManager Release 4.0(2).

Cisco CallManager Extension Mobility Enhancements

Cisco CallManager release 4.0(2) enhances extension mobility functionality by throttling login requests. When extension mobility is used with a large number of users, this system activity controls the number of concurrent extension mobility service requests to ensure optimal system performance.

For more information, refer to http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed28469.

Where to Find More Information

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

•"Device Profile Configuration," Cisco CallManager Administration Guide

•"Device Profile Default Configuration," Cisco CallManager Administration Guide

System Enhancement for Route Group and Line Group Processing

Cisco CallManager release 4.0(2) provides enhancements to route group functionality by modifying the default distribution algorithm of a new route group from "top down" to "circular." Cisco CallManager 4.0(2) also enhances new line group creation by setting the default distribution algorithm to "longest idle time."

The system defines these system changes, which enable increased performance for call setup; the user cannot configure them.

Where to Find More Information

•"Line Group Configuration," Cisco CallManager Administration Guide

•"Route Group Configuration," Cisco CallManager Administration Guide

Voice Mail Configuration Enhancements

Cisco CallManager release 4.0(2) provides the following voice messaging system configuration enhancements.

Voice-Mail Pilot Configuration

Starting with Cisco CallManager 4.0(2), you do not need to reset devices when you update a voice-mail pilot.

•The Reset Devices button no longer displays on the Voice Mail Pilot Configuration window.

•Cisco CallManager no longer automatically resets the devices that are assigned to a voice-mail pilot when the voice-mail pilot gets updated.

Voice-Mail Profile Configuration

Starting with Cisco CallManager 4.0(2), you do not need to restart devices when you update a voice-mail profile.

•The Restart Devices button no longer displays on the Voice Mail Profile Configuration window.

•Cisco CallManager no longer automatically restarts the devices that are assigned to a voice-mail profile when the voice-mail profile gets updated.

Where to Find More Information

•"Cisco Voice-Mail Pilot Configuration," Cisco CallManager Administration Guide

•"Voice-Mail Profile Configuration," Cisco CallManager Administration Guide

Cisco Unity Voice-Mail Port Adjustments

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

Where to Find More Information

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

Route List Redundancy Configuration

With Cisco CallManager release 4.0(2), route list handling and redundancy change to improve performance. Pre-4.0(2) implementations included route lists on every server in a cluster. After upgrade to release 4.0(2), only one instance of the active route list configuration associates with a Cisco CallManager group. This change requires that you configure the Cisco CallManager Group(s) to maintain load balancing and redundancy.

After you upgrade the Cisco CallManager servers to 4.0(2), and if two or more primary CallManager servers exist in the cluster, the system creates new CallManager Group(s) with a default name of "RLCMG_<primary Cisco CallManager name>." The system creates one CallManager Group for each primary server and the secondary server in the CallManager Group, which is the dedicated backup server. Depending on the number of servers in the cluster, the system creates one or multiple CallManager Groups.

One instance of the active route list configuration then attaches to the primary Cisco CallManager server in the first CallManager Group. New CallManager Groups get assigned to the existing route list configuration by using a round-robin algorithm to ensure redundancy.

To complete the upgrade, you must perform the following tasks:

1. Create new CallManager Group(s) to replace the default CallManager Group(s) that are named "RLCMG_<primary Cisco CallManager name>" and that were created during the upgrade.

2. Evaluate the CallManager Group and route list configuration for load balancing and redundancy.

3. Reconfigure the route list(s) to the user-created CallManager Group(s).

4. Delete the default CallManager Group(s).

Caution These activities drop all dependent active calls and cause significant overhead while you perform the reconfiguration.

For more information, refer to http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCee30571.

Where to Find More Information

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

•Upgrading Cisco CallManager Release 4.0(2)

SRST Algorithm Enhancements

Implementation of Survivable Remote Site Telephony (SRST) algorithm enhancements resolves Wide Area Network (WAN) link flapping issues between Cisco CallManager and SRST, which can lead to IP phone instability. The system provides enhancement through an enterprise parameter and a device pool configuration setting, Connection Monitor Duration.

Connection Monitor Duration

An IP phone that is connected to SRST over a WAN reconnects itself to Cisco CallManager as soon as it can establish a connection with Cisco CallManager over the WAN link. However, if the WAN link is unstable, the IP phone switches back and forth between SRST and Cisco CallManager, which can cause temporary loss of phone service (no dial tone). These reconnect attempts, known as WAN link flapping issues, continue until the IP phone successfully reconnects itself to Cisco CallManager.

WAN link disruptions comprise two types: infrequent random outages that occur on an otherwise stable WAN, and sporadic, frequent disruptions that last a few minutes.

To resolve the WAN link flapping issues between Cisco CallManager and SRST, Cisco CallManager provides an enterprise parameter and a setting in the Device Pool Configuration window called Connection Monitor Duration. (Depending upon system requirements, the administrator decides which parameter to use.) The XML configuration file delivers the value of the parameter to the IP phone.

•Use the enterprise parameter to change the connection duration monitor value for all IP phones in the Cisco CallManager cluster. The default for the enterprise parameter specifies 120 seconds.

•Use the Device Pool Configuration window to change the connection duration monitor value for all IP phones in a specific device pool.

Where to Find More Information

•SRST Fallback Algorithm Enhancements

•Cisco CallManager Administration Guide

Operating System Installation Guidelines

Cisco recommends that you install Cisco IP Telephony operating system version 2000.2.6 with the latest service release 2000.2-6-sr1 (or later) before you upgrade to Cisco CallManager release 4.0(2).

Disabling Cisco RIS Data Collector Prior to Upgrading to Cisco CallManager Release 4.0(2)

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

This procedure applies for upgrades from Cisco CallManager 3.3 to 4.0(2) and upgrades from Cisco CallManager 4.0(1) to 4.0(2).

Procedure

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

The Service Parameters Configuration window displays.

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

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

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

Step 5 Click Update.

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

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

New and Updated Support for Cisco IP Phones

The following information describes new and updated phone support for Cisco CallManager release 4.0(2):

•Cisco Call Back supports Cisco IP Phone models 7905, 7912, 7940, 7960, and 7970.

•Cisco CallManager release 4.0(1)sr2, 4.0(2), and later provide support for the Cisco IP Phone models 7902G, 7905G, and 7912G.

For more information, refer to the following URL for the appropriate
Cisco IP Phone guide for your model IP phone:
http://www.cisco.com/univercd/cc/td/doc/product/voice/c_ipphon/index.htm.

Where to Find More Information

•Cisco IP Phone 7902G/7905G/7912G Release Notes for Firmware Release 3.3(8) for Cisco CallManager Version 4.0.1 or Later

•Cisco IP Phone Administrator Guide for Cisco CallManager Models 7902G, 7905G, and 7912G

•Cisco IP Phone 7905G/7912G Guide for Cisco CallManager

•Cisco IP Phone 7902G Guide for Cisco CallManager

•Customizing Your Cisco IP Phone on the Web

Support for Cisco VT Advantage

Cisco CallManager release 4.0(1)sr2, 4.0(2), and later provide support for Cisco VT Advantage. Cisco VT Advantage brings video telephony functionality to Cisco IP Phones, which provides users with the ability to add video to their communications experience.

Where to Find More Information

•Cisco VT Advantage Administration Guide

•Cisco VT Advantage User Guide

•Cisco VT Advantage Quick Start Guide

Dialed Number Analyzer

The Dialed Number Analyzer (DNA) tool, an installable plug-in for Cisco CallManager, 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. DNA runs as a service on the server.

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

Where to Find More Information

•Cisco CallManager Dialed Number Analyzer Guide

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 the dial plans that specific countries use.

Cisco CallManager currently supports international dial plans for Australia, Japan, Netherlands, New Zealand, Portugal, Russia and Singapore.

Where to Find More Information

•Cisco CallManager International Dial Plan Deployment Guide

Changes to Type Specific Information in the Gateway Configuration Settings

After you install Cisco CallManager 4.0(2), the following check boxes in the Cisco CallManager Administration Gateway Configuration window are unchecked by default for some gateways:

•Display IE Delivery

•Redirecting Number IE Delivery-Inbound

•Redirecting Number IE Delivery-Outbound

The gateways that are affected include the following:

•Catalyst 6000 T1 VoIP Gateway (Digital Access PRI)

•Catalyst 6000 E1 VoIP Gateway

•DE-30+ Gateway

•DE-24+ Gateway (Digital Access PRI)

•H.323 Gateway

If you upgrade your server to Cisco CallManager 4.0(2) and you did not uncheck the check boxes before the upgrade, the check boxes remain checked after the upgrade. If you add an affected gateway after the upgrade, the check box is unchecked.

To determine when you should check the check box(es), refer to the guidelines specified in the Cisco CallManager Administration Guide.

Where to Find More Information

•Cisco CallManager Administration Guide

Calling Search Space Enhancements

Cisco CallManager provides database enhancements for Calling Search Spaces (CSS) that allow you to make updates to calling search spaces during normal 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.

Tip To save your updates, remember to click Update after you make changes.

Where to Find More Information

•"Calling Search Space Configuration," Cisco CallManager Administration Guide

Conference Enhancements

Cisco CallManager release 4.0 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.

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

Where to Find More Information

•Cisco IP Phones, Cisco CallManager System Guide

•"Softkey Template Configuration," Cisco CallManager Administration Guide

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

•Cisco IP Phone Guide

Attendant Console Enhancements

Cisco CallManager Attendant Console includes the following enhancements:

•Support for call queuing—When a call comes in to a pilot point and all hunt groups members are busy, Cisco CallManager answers the call and inserts it into the queue when the queue is not full. If the queue is full, the call redirects to the "AlwaysRoute" member. If the "AlwaysRoute" member is not configured, the call gets dropped.

While the call is in the queue, the system places the call on hold, and music on hold plays to the caller. Cisco CallManager redirects the call to the next available hunt group member. When the call is in the queue for longer than the configured HoldTime, the call gets redirected to the "AlwaysRoute" member. If the "AlwaysRoute" member is not configured, no action gets taken. Attendants cannot see calls in the queue.

•Support for broadcast calls—When a call arrives at the broadcast hunting pilot point, Cisco CallManager answers the call and inserts it into the queue if the queue is not full. Cisco CallManager Attendant Console broadcasts the call to all available attendants. If the queue is full, the call redirects to the "AlwaysRoute" member. If the "AlwaysRoute" member is not configured, the call drops.

While the call is in the queue, the system places the call on hold, and music on hold plays to the caller. Cisco CallManager redirects the call to the attendant who answers the call.

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

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

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

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

Configuration Tips

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

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

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

How this Feature Affects the User

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

Where to Find More Information

•"Cisco CallManager Attendant Console," Cisco CallManager System Guide

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

•"Configuring IP Phones," Cisco CallManager Administration Guide

NM-HDV2 and NM-HD Support for Cisco CallManager

In Cisco CallManager release 4.0(2), 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:

Note 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 The 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/GSMER—96

Per NM-HD:

•G.711 only conference—24

•G.729 conference—6

•GSM FR conference—2

•GSM EFR conference—1

Tip The 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

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

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

Where to Find More Information

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

•"Media Termination Points," Cisco CallManager System Guide

•"Transcoders," Cisco CallManager System Guide

•"Conference Bridges," Cisco CallManager System Guide

•"Conference Bridge Configuration," Cisco CallManager Administration Guide

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

Security Enhancements

Cisco CallManager provides the following additional security implementation capabilities.

•After the Cisco CallManager installation, the cluster boots up in nonsecure mode, and all devices register as nonsecure with Cisco CallManager. If you upgrade the cluster from Cisco CallManager 4.0(1) to 4.0(2), the cluster boots up in the mode that you configured in Cisco CallManager 4.0(1).

•If the server does not contain a self-signed certificate, the Cisco CallManager installation/upgrade creates a self-signed X.509 certificate for each server in the cluster. If the server contains a self-signed certificate, the upgrade does not reinstall or update the certificate on the server.

Configuration Tips

•Cisco does not support Network Address Translation (NAT) with Cisco CallManager if you configure the cluster for mixed mode; Application Layer Gateways (ALG) that allow VoIP to traverse firewalls and NAT do not work with signaling encryption. You can enable UDP ALG in the firewall to allow media stream firewall traversal. Enabling the UDP ALG allows the media source on the trusted side of the firewall to open a bidirectional media flow through the firewall by sending the media packet through the firewall.

Tip Hardware DSP resources cannot initiate this type of connection, and, therefore, must exist outside of the firewall.

•Signaling encryption does not support NAT traversal. Instead of using NAT, consider using LAN extension VPNs.

•You can use the Microsoft Certificate Services with CAPF if the Microsoft Certificate Services software runs on a Windows 2003 server. For information about how to use this software or for troubleshooting support, contact the certificate authority vendor directly.

If CAPF requests certificates from Microsoft Certificate Services, you must enter the necessary configuration information, for example, the IP address or hostname, for this certificate authority in the applicable CAPF service parameter. In addition, you must install the SCEP addon on the server where you install Microsoft Certificate Services. To obtain the SCEP addon, contact the certificate authority vendor directly.

•You can use Keon Utility to generate certificates for CAPF. You must enter the necessary configuration information, for example, the IP address or hostname, for this certificate authority in the applicable CAPF service parameter. For information on how to use the Keon software or for troubleshooting support, contact the certificate authority vendor directly.

Where to Find More Information

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

•Cisco IP Phone administration guide that matches your phone model

•Firmware release notes for your model IP phone

Static Digit Analysis

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

Configuration Tip

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

Where to Find More Information

•Static Digit Analysis

Using Query to Delete Phones

You can delete phones by creating a query to locate the phone records by using the following procedure.

Procedure

Step 1 In the Delete Phones Options window, choose Use query and click Next.

The Delete Phones window displays.

Caution If you do not specify a query, you will delete all phones.

Step 2 In Select Phones to Query drop-down list box, choose the field to query, such as Model or Directory Number.

Step 3 If you chose Unassigned DN in Step 2 then go to Step 9. Otherwise, continue with Step 4

Step 4 In the second drop-down list box, choose the search criteria, such as begins with, contains, or is empty.

Step 5 In the search field list box, choose or enter the value that you want to locate, such as the model name from the list or directory number range.

Step 6 To add the defined filter to the query, click Add To Query.

Step 7 To add multiple filters, you can click AND or OR; to further define your query, repeat Step 2 through Step 6.

Note You cannot perform multiple queries when Directory Number or Unassigned DN is used in the first drop-down list box; that is, AND or OR do not act as valid operators with Directory Number.

Step 8 To check that the query returns the results that you need, click View Query Results.

Note Ensure that you have located the correct phones to delete; the delete action is final, so you cannot retrieve deleted records.

If you need to make a correction, click the Clear Query button to remove the query; then, return to Step 2 and restart.

Caution If you do not enter any information in the query text box, the system deletes all phone records. Because the delete action is final, you cannot retrieve deleted records.

Step 9 To delete the records, click Delete.

Note If you chose Unassigned DN in the Select Phones to Query drop-down list box, then the selected unassigned DNs will be deleted. You can delete a maximum of 2000 unassigned DNs from the Route Plan Report.

Step 10 A message displays that advises you of approximately how long it will take to delete the records from the Cisco CallManager database. You can cancel the transaction or click OK to continue.

Step 11 To display the log file that BAT generated, click the View Latest Log File link.

The log file displays the number of phones that were deleted and the number of records that failed, including an error code.

Where to Find More Information

•Bulk Administration Tool User Guide

Using Immediate Divert with Hunt Lists

When you use a phone that is part of a line group in a hunt list and it has the iDivert softkey assigned to it, the iDivert softkey does not display when the phone receives a call from within the hunt list.

When the phone receives a call that is not associated with a hunt list, however, the iDivert softkey displays on the phone.

For more information, refer to http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCee84214 and http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCef15654.

Where to Find More Information

•Cisco CallManager Features and Services Guide

New and Changed Information for Cisco CallManager Serviceability

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

•Cisco CallManager Renamed After Restarting Services

•TroubleShooting Trace Setting

•Cisco CallManager Trace Collection Tool

•Real-Time Monitoring Tool as Standalone Plug-in

•Serviceability Reports Archive

•SNMP and Performance Counter Enhancements

•CDR Analysis and Reporting (CAR) Enhancements

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. Therefore, 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.

TroubleShooting Trace Setting

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

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

You can find the TroubleShooting Trace Setting tool in the Trace menu in Cisco CallManager Serviceability.

Cisco CallManager Trace Collection Tool

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

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

•Chosen Cisco CallManager services

•Chosen Cisco CallManager applications

•Chosen Cisco CallManager system traces

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

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

Real-Time Monitoring Tool as Standalone Plug-in

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

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

In addition to service parameter enhancements, the following list comprises the RTMT enhancements for Cisco CallManager release 4.0:

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

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

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

•You can install RTMT on a remote PC by using the Cisco CallManager Plug-ins window.

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

–Memory and CPU Utilization

–Disk Utilization

–Critical Cisco CallManager and System Services

–Call Activity

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

–Cisco TFTP

–Directory

–Cisco CallManager Heartbeat Information

–Summary of Registered Devices

–CTIManager

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

–NumberOfRegisteredPhonesDropped

–NumberOfRegisteredGatewayDevicesDecreased

–NumberOfRegisteredGatewayDevicesIncreased

–NumberOfRegisteredMediaDevicesDecreased

–NumberOfRegisteredMediaDevicesIncreased

–MediaListExhausted

–MgcpDChannelOutOfService

–RouteListExhausted

–CriticalServiceDown

–CallProcessingNodeCpuPegging

–NonCallProcessingNodeCpuPegging

–LowInAvailableMemory

–LowInAvailableDiskSpace

–LowCallManagerHeartbeatRate

–LowTFTPServerHeartbeatRate

–LowTcdServerHeartbeatRate

–DirectoryConnectionFailed

–DirectoryReplicationFailed

–MaliciousCallTrace

–ExcessiveVoiceQualityReports

–CodeYellowEntry

–CodeRedEntry

•Cisco CallManager Serviceability Reporter logs reports and CSV files of key performance counters for troubleshooting and trending. The following reports automatically generate:

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

–Device Statistics Report

–Server Statistics Report

–Service Statistics Report

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

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

Serviceability Reports Archive

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

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

SNMP and Performance Counter Enhancements

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

•New MIB objects:

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

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

•A new table, ccmSIPDeviceTable, provides SIP trunk information.

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

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

•Deprecation of existing static (enum-based) device type definitions occurs.

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

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

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

•ccmQualityReportAlarmEnable flag enables/disables ccmQualityReport Trap.

•Release 4.0 adds Cisco IP Phone 7970 in ccmPhoneType.

•Release 4.0 adds several media device types in ccmMediaDeviceType.

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

Where to Find More Information

•Cisco CallManager Serviceability System Guide

•Cisco CallManager Serviceability Administration Guide

CDR Analysis and Reporting (CAR) Enhancements

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

The following list describes the CAR enhancements for release 4.0:

•New hunting features

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

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

–You can perform Route Pattern searches.

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

–Call Summary by Precedence Level

–CDR Search changes by Call Precedence Level

•Malicious Call ID—New reports and changes for Malicious Call ID

–Malicious Call Details

–Call Detail Search for Malicious Calls

•CDR Management

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

–You can purge CDR between two dates by using Manual Purge.

–No change occurs in Automatic Purge of CDRs facility.

•Conference Reports

–Conference Reports—Support Cisco CallManager ad hoc and Meet-me conferences.

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

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

Configuration Tip

The menu on the left side of the pane lists only the top 50 route patterns.

Where to Find More Information

•Cisco CallManager Serviceability System Guide

•Cisco CallManager Serviceability Administration Guide

New and Changed Information for Third-Party and SDK Applications

There are no new features and changes that are pertinent to this release of Cisco CallManager and third-party and SDK applications.

For information about third-party and SDK applications, refer to the Cisco CallManager 4.0 Developer Documents at the following URL:

http://www.cisco.com/univercd/cc/td/doc/product/voice/vpdd/cdd/4_0/

Important Notes

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

•CSCso79248 Do Not Run installxml.vbs in CallManager Release 3.3 and Later

•Adding Cisco CallManager Servers

•Installing IPMA Assistant Console on Microsoft Windows XP

•Locale Installer for Cisco CallManager

•Line Group/Route Group Support for MLPP-Enabled Devices

•Using the JTAPI Update Utility with CRS

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

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

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

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

Adding Cisco CallManager Servers

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

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 plug-in for Internet Explorer from http://java.sun.com/getjava/download.html.

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

Locale Installer for Cisco CallManager

You can obtain locale specific versions of the Cisco IP Telephony Network Locale installer for Cisco CallManager 4.0 at the following URL:

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

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

Line Group/Route Group Support for MLPP-Enabled Devices

MLPP-enabled devices are not supported in line groups. As such, Cisco recommends the following guidelines:

•MLPP-enabled devices should not be configured in a line group. Route groups, however, are supported. Both trunk selection and hunting methods are supported.

•If an MLPP-enabled device is configured in a line group or route group, in the event of preemption, if the route list does not lock onto the device, the preempted call may be rerouted to other devices in the route/hunt list and preemption indication may be returned only after no devices are able to receive the call.

•Route lists can be configured to support either of two algorithms of trunk selection and hunting for precedence calls:

–In method 1, perform a preemptive search directly.

–In method 2, first perform a friendly search. If this search is not successful, perform a preemptive search. This method requires two iterations through devices in a route list.

If route lists are configured for method 2, in certain scenarios involving line groups, route lists may seem to iterate through the devices twice for precedence calls.

For more information, refer to http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCee32579.

Where to Find More Information

•Cisco CallManager Features and Services Guide

Using the JTAPI Update Utility with CRS

Cisco Customer Response Solutions (CRS) servers include a JTAPI Update Utility that performs synchronization of the Cisco CallManager Plugin with the CRS server and the Cisco Agent Desktop (CAD). This update tool must be run to ensure successful operation of your CRS server.

If you have CRS or Cisco CallManager Extended Services installed (either co-located with the Cisco CallManager server or on a separate server) and you upgrade and/or install Cisco CallManager, you must take additional action to ensure plugin synchronization.

•Because an upgrade to a Cisco Call Manager server may include an updated JTAPI Plugin component, make sure that you run the JTAPI Update Utility on the CRS server to upgrade the JTAPI client. Running the JTAPI Update Utility on your CRS server, after you upgrade Cisco CallManager, ensures that the JTAPI Plugin is properly installed.

Note Simply executing the plugin installer to install the JTAPI Plugin on the CRS server (in lieu of running the JTAPI Update Utility) does not copy the jtapi.jar file to the CRS share folder, leaving the update in an unfinished state.

For detailed information about the JTAPI Update Utility, refer to the Cisco Customer Response Applications Administrator Guide at http://www.cisco.com/univercd/cc/td/doc/product/voice/sw_ap_to/apps_3_5/english/admn_app/apadm35.pdf.

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 of the following information as it relates to attendant console:

•The attendant console user cannot drag a speed-dial entry onto a call in the Call Details pane.

•The attendant console user cannot rename a speed-dial group from the Edit menu.

•The Call Forward All to the voice-messaging icon and the Forward All to another directory number icon do not display in the Speed Dial window.

Resolved Caveats for Cisco CallManager - Release 4.0(2)

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

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

To access the Bug Toolkit, log on to

http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl

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

Identifier

Summary

CSCdr53384

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

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

CSCds07952

LineAccept fails when a call is already in connected state.

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

CSCds09562

Cisco CallManager does not have an error code to distinguish between invalid and out-of-service extension.

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

CSCds50763

Spurious NewCall gets created when you redirect a resumed call.

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

CSCdu34874

The number does not display on an associated IP phone when you use Cisco Softphone to dial a number.

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

CSCdu59769

CTIManager SDL log information does not always display all necessary trace information.

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

CSCdx64502

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

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

CSCdx78896

Invalid service parameter input for Extension Mobility could cause service failure.

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

CSCdx80567

Invalid service parameter input for serviceability could cause service failure.

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

CSCdx80828

Invalid service parameter input for music on hold could cause service failure.

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

CSCdx80834

Invalid service parameter input for Call Back could cause service failure.

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

CSCdx93516

SrcCallSignallingAddress does not appear in the H.323 Setup message.

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

CSCdy86076

Users need to restart the TSP client after logging off and logging back in on Cisco Extension Mobility.

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

CSCdy87034

Cisco TAPI Service Provider (TSP) has a memory leak in some consult transfer scenario.

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

CSCdy88595

The gateway configuration file does not get updated when the endpoint is deleted.

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

CSCdz72286

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

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

CSCea03826

The second ringback call state event does not get sent when a call gets redirected after connecting to an external number across a gateway.

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

CSCea05766

Cisco IP Phone 7912 does not support Call Back.

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

CSCea34211

Incoming call does not automatically get answered when you place the current call on hold.

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

CSCea42609

The Real Time Monitoring Tool does not correctly report information that is related to CTI devices and lines

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

CSCea50515

You cannot disconnect a call on hold through a CTI application.

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

CSCea51241

The online help for Attendant Console does not correctly display in Hungarian.

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

CSCea72465

"File in use" problem occurs with the uninstallation process.

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

CSCea73575

The event viewer displays failed audit reports for CCMService user.

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

CSCea85505

Calls to a domain name system (DNS) server-based trunking fail.

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

CSCeb05663

Line status stops working after you transfer a call from a shared-line phone to the same shared-line phone.

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

CSCeb13733

Uninstallation of release 3.2(3)SR01 causes a backslash error.

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

CSCeb25708

Path name gets created incorrectly when the system is trying to open the jtapi.ini file.

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

CSCeb40762

JTAPI disables Cisco Customer Response Solution traces along with all other traces.

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

CSCeb48689

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

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

CSCeb53739

The phoneSetLamp/phoneGetLamp requests do not set the lamp on the Cisco IP Phone 79xx models.

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

CSCeb55563

You cannot add a user to a user group if the user ID contains a slash character (/).

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

CSCeb57003

Cisco CallManager User Options do not display updated speed-dial entries.

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

CSCeb57154

Cisco CallManager LSS fails to send Idle state after call ends.

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

CSCeb58036

Phone displays an incorrect message when you edit a personal address book (PAB) entry.

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

CSCeb58068

Users get an error when adding a PAB on the Cisco CallManager User window.

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

CSCeb60407

ICT call does not get cleared when the transcoder is reset.

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

CSCeb62212

Cisco IP Phone models 12SP and 30VIP cannot start an ad hoc conference by using the speakerphone.

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

CSCeb62769

Cisco IP Phone does not display a DN when the number contains a wildcard character.

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

CSCeb63018

You get duplicate entries in the address book because the nickname format is inconsistent.

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

CSCeb66170

The IOS Conference Bridge name field only allows 15 characters.

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

CSCeb67247

Selecting Dependency Records for regions causes the CPU to spike.

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

CSCeb67397

Shared-line phone can have more calls than the number for which it is configured.

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

CSCeb67677

The MLPP Domain Configuration for Enterprise Parameters uses decimal format.

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

CSCeb68038

Cisco CallManager assigned a DN that is out of the auto registration range to a phone that was deleted from the database.

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

CSCeb68131

Call on hold gets dropped when you try to resume the call after another phone barged in to the call.

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

CSCeb69927

Extension mobility phones do not have call history.

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

CSCeb71190

Call fails because a SCCP device does not consider location in the bandwidth computation.

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

CSCeb71221

Call fails because a H.323 device does not consider location in the bandwidth computation.

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

CSCeb71231

Call fails because a SIP device does not consider location in the bandwidth computation.

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

CSCeb74440

Phone gets disconnected with a normal cause code but does not play the reorder tone.

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

CSCeb76250

Administrators receive a system message when they delete a large number of locations from the external route plan wizard.

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

CSCeb80938

Conference drops when the controller hangs up (CIA-76).

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

CSCeb83883

Incorrect call information exists in unpark scenario.

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

CSCeb85104

JTAPI returns null for a calling terminal when a shared-line device makes a call.

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

CSCeb87713

Subscriber installation uses the wrong database if the installation is launched before the publisher server is upgraded.

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

CSCec04720

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

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

CSCec05284

Event viewer displays a JavaPerfMon error.

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

CSCec06088

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

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

CSCec07003

Cisco CallManager Administration lists user access rights in the user menu.

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

CSCec11141

The DirUser.jar and DirUserNotification.jar files are missing after upgrade.

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

CSCec11376

Cisco Real-Time Information Server (RIS) fails to collect Perfmon data from the remote node if the node temporarily loses connection.

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

CSCec18269

JTAPI does not send a ConnConnectedEv message when a call is redirected through a gateway.

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

CSCec19569

Phones cannot enter a Meet-me conference when the conference is initiated by using a translation pattern.

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

CSCec21799

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

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

CSCec23359

Call information does not get updated when a barged call is dropped.

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

CSCec25549

With Cisco CallManager 3.3(3), the contents of the CDR flat file might become corrupted, causing failure of the call record insertion into the CDR database.

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

CSCec26136

The Message Waiting Indicator (MWI) light does not go on after the phone is unplugged and reregistered.

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

CSCec26277

The ciscoupdate.txt log does not indicate the latest SQL version after engineering special or support patch/service release upgrades.

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

CSCec28915

Users get a run-time error when they access Cisco CallManager Administration help file.

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

CSCec34474

Unsetting CFwdAll to the voice-messaging system (set manually) from TAPI does not work.

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

CSCec39201

CTL client does not recognize when different eTokens are inserted.

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

CSCec39276

You cannot use a voice-mail port that has call forward all and call forward busy that are configured to a route point.

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

CSCec40191

PSTN users report call drop when they are hearing ringback.

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

CSCec40884

LineOpen results in CTI error message 0x8CCC0003.

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

CSCec41691

Define VG224 gateway to Cisco CallManager configuration options.

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

CSCec43718

Input data gets lost when Character Set is selected after a DN or speed dials are added.

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

CSCec44751

Tool for Auto-registered Phone Support (TAPS) phone does not reset with new number, so a manual reset is required.

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

CSCec45179

DC Directory terminates unexpectedly with version 3.3(3)SR2.

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

CSCec45732

DSCP registry entries reset when the TSP configuration UI is accessed.

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

CSCec46604

User gets a "IsRes.dll file could not be removed. Access is Denied" error message.

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

CSCec47867

Cisco CallManager sends an incorrect termconn state when you unpark a barge call.

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

CSCec48919

Q.SIG calling party PI gets used to encode DivertingNumber/DivertingName.

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

CSCec49580

DwCalledID block occurs when OrigCdpnPI is set to restricted.

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

CSCec50080

Application Event Viewer log warning message does not always generate when the Cisco CallManager service stops.

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

CSCec50488

Delayed response occurs when request to hold a call is made.

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

CSCec51393

A call park number does not display in the popup message when the number contains special characters.

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

CSCec51712

Modification is needed to prevent TSP from using NULL device object pointer.

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

CSCec51987

Notification does not get sent when you change the built-in bridge service parameter.

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

CSCec52677

Cisco CallManager Administration allows you to add an orphan directory number to the hunt list of a Cisco CallManager Attendant Console.

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

CSCec53844

Cisco CallManager server does not correctly handle a reset device message if it is received within 5 seconds of a default change notification message from the device.

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

CSCec54062

Inconsistent behavior occurs between Cisco CallManager User and Admin windows for user password.

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

CSCec54145

Blocked flag should be present in AddressCaps for caller, redirection, and connectedID.

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

CSCec54439

User cannot login with the Administrator password after upgrade from 3.3(2) to 4.0.

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

CSCec55257

Incorrect held event CallCtl_Cause gets sent when a shared-line device transfers a call.

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

CSCec56355

Calling terminal is null when a shared-line device makes a consult call.

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

CSCec57585

The signal distribution layer (SDL) traces generate even when you disable trace configuration.

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

CSCec57714

Cisco CallManager sends an incorrect last redirected address.

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

CSCec58205

The TSPAutoInstall UI does not run on Microsoft Windows NT.

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

CSCec58844

The TSPAutoInstall UI displays invalid text in certain dialog windows.

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

CSCec59109

User cannot make inbound calls when using "2-stage dialing" from PSTN to IP phone.

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

CSCec60220

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

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

CSCec61469

Users do not receive the video signals from a third-party video endpoint when they are on a call to another third-party video endpoint.

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

CSCec61667

Microsoft windows 2000 advance servers do not support CTL client.

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

CSCec61974

Redirect destination does not connect when redirect call goes through gateway.

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

CSCec62144

FXS ports in version 4.0 do not show product-specific GUI.

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

CSCec62297

Updates to a route group take 10 - 11 minutes to complete.

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

CSCec62336

No option exists to retry a video call as audio across an intercluster trunk.

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

CSCec62727

Incorrect CallManagerID exists in LineConferenceEndedEvent.

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

CSCec63078

Under CRS load, calls get rejected.

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

CSCec63187

Call party information change does not display when redirecting across a gateway.

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

CSCec64242

Cisco CallManager terminates unexpectedly in version 3.3(3).

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

CSCec64547

Cisco CallManager Administration changes the number of items that it displays per window to 10 when you click on the window link in Region Configurations.

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

CSCec64748

Incorrect behavior in routing scenario occurs.

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

CSCec65193

JTAPI logs for redirect scenario show NullPointerException.

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

CSCec65305

Incorrect display shows on IPMA manager phone when assistant is in conference.

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

CSCec65506

The call for TransfertoVM goes to the FwdNoAnswerDn if the DestDN and SetOriginalCalledTo is the CTI port and is not registered.

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

CSCec65830

The online help for WS-6624 FXS gateway device configuration does not exist.

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

CSCec65850

Incorrect conference bridge model displays in the Real-Time Monitoring Tool.

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

CSCec66060

The MohNoMoreResourcesAvailable and MediaResourceListExhausted alarms might generate incorrectly for devices that are not present/not registered.

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

CSCec66461

When sent via e-mail, CDR search output does not show all CDR fields.

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

CSCec66820

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

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

CSCec66867

Cisco CallManager Administration displays an ODBC error message when you search for gateways with a Calling Search Space is not empty parameter.

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

CSCec66964

Cisco CallManager Administration displays end points when you search for gateways with calling search spaces parameter and the hide endpoint option.

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

CSCec67194

Cisco CallManager service recovery does not get set to default after upgrade.

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

CSCec67279

When Multilevel Administration Access (MLA) is enabled, the "List Files" buttons become disabled for user who has read-only right in serviceability.

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

CSCec67323

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

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

CSCec68479

Cryptographic notification does not display on the Help > About window.

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

CSCec69160

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

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

CSCec69222

Cisco CallManager sends the wrong call information when the calling party parks a call.

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

CSCec69327

Call connection record is incomplete.

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

CSCec69367

CAR generates extra reports for conference call.

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

CSCec69371

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

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

CSCec69497

Cisco CallManager does not handle MGCP 400 error messages correctly.

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

CSCec71628

The idivert feature does not work as expected when a call exists on a line that has Call Forward Busy (CFB) or Call Forward No Answer (CFNA) enabled and the voice-messaging system is down.

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

CSCec71675

The Cisco CallManager service parameter SDL Max UnHandled Exceptions needs redefinition for clear interpretation of its function.

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

CSCec72451

Cisco CallManager service restarts when a large number of route lists, devices, and route patterns exist.

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

CSCec73266

CDP.sys produces bugcheck when stressed.

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

CSCec73503

Input data gets lost when "Character Set" is selected in speed dial and IP services windows.

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

CSCec73828

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

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

CSCec74272

The Cisco CallManager service parameter SDL Max UnHandled Exceptions needs redefinition for clear interpretation of its function.

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

CSCec75146

Call gets stuck in JTAPI after being dropped (no CallCtlConnDisconnect).

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

CSCec75237

LineChangeEventFilterRequest does not fail when a line is closed.

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

CSCec75273

LineClosedEvent does not get sent to application when user logs in by using extension mobility.

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

CSCec75824

Incorrect call information displays when barged to call from out-of-provider device.

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

CSCec76154

Call events are missing when Internal Caller ID is set from Cisco CallManager Administration.

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

CSCec76306

A video endpoint that is sharing a line with an audio endpoint does not receive the video portion of the phone call.

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

CSCec77271

Cisco CallManager does not purge old hunt list data in the Real-Time Information Server (RIS).

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

CSCec77759

Call Back softkey displays incorrectly.

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

CSCec77797

The getDeviceProfileResponse:model returns a value that is not found in the XL schema.

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

CSCec78290

Voice-mail ports display call-forwarding information.

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

CSCec79510

CTI Manager traces do not show responses that are sent to the CTI client.

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

CSCec79898

An unknown dialog window displays in the upper, left corner of the TraceCollectionTool window.

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

CSCec80041

The previous installation of the Upgrade Assistant utility still gets deleted when you select cancel while upgrading the Upgrade Assistant utility.

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

CSCec80231

User gets a Self Registration error message when Upgrade Assistant is deleted.

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

CSCec80292

DCD validation fails on a Cisco CallManager subscriber server, release 3.3(2), when you use upgrade assistant.

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

CSCec80293

A remote scripting error occurs after a CTI route point device is deleted.

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

CSCec81438

A CDBLException error occurs after a partition with one unassigned DN is deleted.

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

CSCec81512

The Cisco CallManager Trace Configuration Page for SDL and SDI traces includes incorrect information about the size of trace log files.

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

CSCec81913

NewCallAcceptTimer does not stop when a call is redirected in the offering state.

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

CSCec82019

The route filter clause does not display properly in the dialed number analyzer (DNA).

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

CSCec82021

Translation pattern CSS does not get configured in DNA.

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

CSCec82145

The online help for Cisco CallManager has misleading information on the Code Yellow Exit Latency Calculation service parameter.

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

CSCec82154

The online help for Cisco CallManager does not clearly define the maximum events allowed service parameter.

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

CSCec82250

Default information does not display in the "Find and List Voice Mail Pilots" window.

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

CSCec82312

Cisco CallManager displays the wrong callCtlCause code when a cBarge call is parked.

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

CSCec82337

The "Object doesn't support this action (-2146827843)" error message displays when changes are made on a subscriber server and the publisher server is either offline or not accessible.

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

CSCec82372

Cisco CallManager does not send a connection event when a cBarge call is unparked.

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

CSCec82409

Cisco CallManager and CTI Manager do not start after upgrade to 3.3(3) because of missing contents in SQL table ProcessConfigDefaults.

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

CSCec82411

Service parameters are needed to control failover/failback throttling.

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

CSCec82793

Cisco CallManager Administration displays endpoints when you choose the hide endpoint option in a search for gateways.

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

CSCec82981

TSP does not set a timeout of 0 in the DeviceDisplayString message.

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

CSCec83007

Applications that use CTI Manager directly cannot set the timeout value.

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

CSCec83663

The "Echo Cancellation Coverage" field does not have a preconfigured value.

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

CSCec83747

The CallsInProgress counter incorrectly displays calls in progress after all calls are cleared.

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

CSCec83813

Cisco CallManager includes incorrectDestPrecedenceLevel value in a call pickup scenario.

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

CSCec84986

Accessing the AAR Group Dependency Record window does not display gateways and terminates Cisco CallManager Administration.

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

CSCec85371

Call Back fails when translation pattern drops digits.

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

CSCec85514

User with no access rights to RTMT can log in.

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

CSCec85541

The QRT Viewer records display incorrect OriginCalledNumber and FinalCalledNumber when CFwdAll is used.

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

CSCec86158

"ODBC error 64" displays on the Find/List User Device Profiles results window when searching on DN.

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

CSCec86576

TFTP cannot generate configuration files for all devices.

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

CSCec86798

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

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

CSCec87055

RTMT cannot monitor the directory service on a node that does not have Cisco CallManager services enabled.

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

CSCec87256

Calls made to route points hang intermittently.

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

CSCec87300

The applet version of RTMT does not run on the Perfmon Monitoring icon.

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

CSCec87398

You cannot delete a Call Pickup Group number by using the AVVID XML Layer (AXL) removeCallPickupGroup request method.

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

CSCec88129

A race condition within Cisco CallManager causes the MWI child process to hang and increase CPU usage.

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

CSCec88319

Some devices do not have Multilevel Precedence and Preemption (MLPP) Domain configuration options.

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

CSCec88531

Call instance does not get released when a CiscoVG200 gateway is used for a shared DN.

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

CSCec89280

You cannot configure a shared line for a line group member on Cisco IP Softphone.

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

CSCec89321

You cannot use MLPP to preempt a call on a SIP trunk.

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

CSCec89794

The Aupair.exe service fails to stop causing the subscriber server installation to fail.

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

CSCec89831

Deleting a RouteList by using AXL fails when the route list does not contain a route group or a line group.

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

CSCec90003

Duplicate deviceUnRegisteredEvent messages get sent when an application closes a device.

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

CSCed00108

Updating CSS with 20K devices causes slow system recovery.

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

CSCed00455

A Cisco IOS H.323 gateway that is running IOS release 12.3 does not forward calls out to the PSTN.

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

CSCed00458

Phone continuously plays a reorder tone when CFwdALL is invoked and the publisher server is offline.

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

CSCed00699

User gets an error message when a hunt list is created with a Route group that is followed by a line group.

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

CSCed01306

The real-time information server data collector (RISDC) on a subscriber server cannot be reached when the Cisco CallManager and CTI service are deactivated.

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

CSCed01709

Call redirect to an external party gets blocked.

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

CSCed01740

CmiPerfmon.dll causes thread deadlock.

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

CSCed01745

CtiMgrPerfMon.dll causes thread deadlock.

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

CSCed01755

MediaAppPerfMon.dll causes thread deadlock.

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

CSCed01758

TcdSrvPerfmon.dll causes thread deadlock.

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

CSCed01763

TFTPPerfmon.dll causes thread deadlock.

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

CSCed02874

The "Set Ringer" configuration does not work if "Tone on Call Forward" is disabled.

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

CSCed02974

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

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

CSCed03294

Installation software for Large Scale Audio Conference Solution disposition needs modification.

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

CSCed03303

Administrators cannot add a line group to a route list after a Q.SIG gateway is deleted.

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

CSCed04678

Cisco CallManager does not send the RedirectingID-Name on a blind transfer call from a shared-line phone.

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

CSCed05265

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

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

CSCed05307

The manager phone displays the wrong number for an assistant call.

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

CSCed05329

CPU usages spikes on the publisher server when you enable department billing and the user hierarchy in directory is not set up properly.

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

CSCed05522

The Call Back Cancel softkey does not work.

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

CSCed05621

A call does not get routed to the second available phone when the first phone is busy.

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

CSCed05797

Cisco CallManager includes the incorrect forwarding information in lineGetAddressStatus message when you remove call forwarding.

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

CSCed06318

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

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

CSCed06632

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

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

CSCed06664

The MOH server does not use available streams for non-default codecs.

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

CSCed06815

Login fails for Cisco CallManager Administration, Cisco CallManager User Option, and Cisco CallManager Service due to a memory leak in LDAP connection.

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

CSCed06910

A call remains active after it is disconnected.

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

CSCed07090

When a Cisco CallManager PRI trunk is configured as PRI-NI2, it does not support Service and Service Ack messages for B-channel maintenance.

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

CSCed07330

Cisco CallManager cannot update international dial plans that have route or translation patterns.

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

CSCed07853

B-channels that are configured to be out of service in Cisco CallManager may continue to process calls.

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

CSCed08398

The MLA online help link points to the incorrect help file.

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

CSCed08525

Online definitions do not include CallThrottlingGenericCounters.

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

CSCed08682

ISDN B-channels that are configured for busy-out may be marked as in service and accept calls.

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

CSCed09180

The Conference key does not work after conferencing with a parked number.

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

CSCed09363

The differentiated services code point (DSCP) parameter only controls the marking of signalling packets of Cisco IP Phone models 7940 and 7960.

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

CSCed09497

Caller ID does not get blocked on blind transferred calls when the destination has Translation Pattern with All Restricted parameter enabled in the progress indicator (PI).

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

CSCed09808

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

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

CSCed10115

Line/Device open does not return an error when the station is closing.

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

CSCed10649

FailureResponse shows an incorrect sequence number when a barged call is redirected.

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

CSCed13398

The Trace Collection Tool cannot resume zipping if the user chooses "no" to cancel the operation.

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

CSCed13415

Cisco Security Agent prevents SQL agent from creating a SQL log on a Cisco ICS 7750 server.

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

CSCed14072

Administrators receives an error message in bold letters when the administrator deletes a route filter from the configuration window.

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

CSCed14348

Cisco CallManager does not respond to a LineCallInitiate request when the handle is absent.

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

CSCed14408

Users may not receive the video signal when they resume a video call on hold.

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

CSCed14584

The AdminUtility.exe tool does not display if passwords are synchronized on all servers in the cluster.

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

CSCed14650

DC directory fails during the backup and restore process.

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

CSCed14717

User with no access to real-time monitoring tool can still access the login screen.

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

CSCed14818

Empty route list gets created when administrators copy the route or hunt list.

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

CSCed14895

User preference page does not change locale.

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

CSCed14934

Cisco CallManager documentation does not inform the administrator that the number of available CSS that are listed in a drop down box is configurable.

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

CSCed14969

Cisco CallManager documentation does not inform the administrator that the number of partitions that are listed in the drop-down box is configurable.

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

CSCed14978

IP phones cannot register to the standby CallManager server during failover.

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

CSCed14981

Cisco CallManager documentation includes inconsistent information on string length for different fields.

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

CSCed15955

Change notification for a renamed device does not get updated in the user's control list.

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

CSCed16095

Calls that are conferenced to IP/IVR CTI ports may get abnormally disconnected with cause code 0.

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

CSCed16137

CTL client does not work properly on Microsoft Windows XP.

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

CSCed16298

An incorrect online help description for the Extension Mobility Log Out Time field exists.

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

CSCed16350

Cisco CallManager Administration documentation describes a field that no longer exists in Translation Pattern Configuration.

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

CSCed17201

Cisco Security Agent (CSA) continues to run during an upgrade to Cisco CallManager release 3.3(3)SR3.

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

CSCed17319

Incorrect auto accept status gets returned.

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

CSCed17554

Cisco CallManager might ignore a call setup message from the ISDN if the setup message is received for an active call.

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

CSCed17889

A COM error message displays when attempting to delete a Meet-me number from the subscriber server and the publisher server is offline.

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

CSCed17921

Sending a Message Waiting Indicator request to lines with no CFwdAll setting causes increased memory.

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

CSCed18107

When CallManager is integrated with Active Directory, the AD user department field displays incorrectly on the Cisco CallManager Administration window.

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

CSCed18717

A blank window displays when attempting to delete a route filter configuration on the subscriber server and the publisher server is offline.

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

CSCed18721

The Trace Collection Tool cannot collect multivolume files after user-selected cancellation while the files are being zipped.

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

CSCed18859

A large number of gateways causes processing delays on the "Find and List Route Groups" window.

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

CSCed19071

RNA is received when transferring a call to a phone that is set up with call forward to a voice messaging system.

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

CSCed19172

An existing call event in progressing state results in an idle call.

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

CSCed19795

CallManager PRIChannelsActive counter incorrectly displays active calls.

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

CSCed20295

Digital gateways do not send SMDI message when SMDI base port number is set to zero in digital trunk and a call arrives on the digital trunk.

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

CSCed21213

CPU spikes on the client machine when user chooses cancel to the zip operation when using the Trace Collection Tool.

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

CSCed21260

Incorrect dependency for H.323 client phone displays nonexisting trunk.

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

CSCed21526

JTAPI does not send CallCtlAddFWDEv message when an application cancels call forward.

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

CSCed21566

Cisco CallManager terminates unexpectedly with invalid instruction in CConnectionHolder.

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

CSCed21668

Monitored Call Park DN opened by application does not display in the Perfmon data.

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

CSCed21675

Cisco CallManager Serviceability adds a "CM" prefix to the IP address of the Cisco CallManager server when you restart Cisco CallManager and CTI Manager services.

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

CSCed23026

CDBLException error message displays when attempting to delete partitions.

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

CSCed23028

Cisco CallManager sends an incorrect reason code when a transformation mask is used in a route point.

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

CSCed23683

Restore log displays a number of errors.

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

CSCed23864

The Certificate Trust List (CTL) utility allows the CTL file to be signed with the new etoken.

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

CSCed24195

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

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

CSCed24235

H323-VideoCallsActive nd H323-VideoCallsCompleted counters can be inaccurate.

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

CSCed24373

Incorrect call information displays on dwRedirecting/dwRedirectionID for a direct call if the line is opened after the call.

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

CSCed24405

LINEFORWARD structure in LINEADDRESSSTATUS does not get cleared when FwdAll is turned off.

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

CSCed24859

Cisco CallManager attempts to make SDL connections with deactivated CallManager and CTI nodes.

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

CSCed24881

A monitoring system reported that the Voice Media Streaming Application and MOH Audio Translator stopped.

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

CSCed25111

CDR record still displays the owner userID for a device when the userID is deleted.

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

CSCed25256

SDL link does not include the status of node router thread.

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

CSCed25306

Phone registration takes over 2 minutes when phones fail over from SRST to Cisco CallManager.

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

CSCed25508

Change notification does not get sent to Cisco CallManager server when a shared line is deleted.

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

CSCed25707

Cisco IP Phone 7905 played a reorder tone in a call scenario.

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

CSCed26547

Cisco CallManager Features and Services Guide includes an incorrect default of 20,000 for synchronous request timeout; the default specifies 15,000.

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

CSCed26570

The minimum and maximum value swaps on overlapping MLA privilege parameters.

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

CSCed26619

Voice-mail pilot change causes MWI, CFwd, and Extension Mobility login/logout delays.

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

CSCed27219

Cisco MGCP gateway does not cut audio through when it receives call progress with PI=8.

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

CSCed27328

Inserting a record in BAT fails when the file name contains a comma.

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

CSCed27619

When the Privacy button is pressed for a selected call in a held state, the privacy setting does not update and the call information displays on the phone.

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

CSCed27972

Duplicate state event warning prints in the SDL logs.

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

CSCed28069

The CallsInProgress counter in the Performance monitor tool might not reset and incorrectly display the number of calls in progress after Cisco CallManager has been processing calls.

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

CSCed28356

JTAPI fails to connect to the CTI manager when CTI Service restarts.

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

CSCed28469

The Tomcat service uses 735 Mb and causes CPU to reach 100 percent with more than 2000 Extension Mobility logins per hour.

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

CSCed28757

Built-in bridge parameter does not get migrated after upgrade to Cisco CallManager, release 4.0.

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

CSCed28953

DBL traces indicate queries for deleted gateway devices.

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

CSCed29239

New Operating System installations, OS version 2000.2.4, designates drive E as the default trace drive on the MCS-7845H-3.06 servers.

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

CSCed29548

Preferences display the previously chosen locale when a user chooses the Chinese Taiwan locale on Cisco WebDialer.

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

CSCed29687

Memory usage increases dramatically when 6000+ phones are exported by using BAT.

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

CSCed29929

Cdcc/Forwarding Leak causes False Forward Loop Detection.

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

CSCed29942

A method for clearing the fwdLoop tables without restarting Cisco CallManager needs definition.

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

CSCed30099

No connection exists for the forwarded destination in a forward busy scenario.

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

CSCed30174

Cisco CallManager does not reset or audit a trunk when it receives a setup message from a gateway.

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

CSCed31675

The MLA logs do not list the user ID for any actions.

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

CSCed32414

Alarms that CTI generates show an invalid IP address of 0.0.0.0 for devices.

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

CSCed32570

Administrators cannot apply troubleshooting trace settings twice.

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

CSCed32615

Music on hold server does not send multicast music to a conference bridge.

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

CSCed32700

A video call from a Tandberg Video Terminal to a plain old telephone service (POTS) phone fails to connect.

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

CSCed32946

User cannot access the subscriber server DC Directory after reinstallation or upgrade if the DCD administrator password is changed and if the new password contains the "|" (pipe symbol) character.

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

CSCed33281

AXL API failed to update the Cisco CallManager service parameters.

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

CSCed33473

You cannot use TAPS to reset a phone with an external number.

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

CSCed34082

Administrators get an error when they insert a H.323 client phone with an empty signal port field.

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

CSCed34104

You cannot use the CTL client to delete the CAPF server from CTL file.

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

CSCed35600

The Webdialer window does not open in Netscape.

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

CSCed35589

Cisco CallManager Service Parameter IP Precedence Bitmask does not work.

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

CSCed35938

Contact gets stuck in queue on the IPCC Express Real Time Reports.

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

CSCed36504

CPU utilization gradually increases under a constant video load.

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

CSCed36630

SIP trunks do not use the correct date format in the Cisco CallManager date header.

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

CSCed38214

Dependency Records search for a Route Group shows trunk as a dependent entity.

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

CSCed38646

CTI receives multiple responses for a redirect request if the redirect destination has configured call forwarding.

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

CSCed38779

Cisco CallManager has a memory leak.

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

CSCed39013

Call redirect fails when running IPMA on Cisco CallManager.

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

CSCed39551

Cisco CallManager Administration allows users to define a network module for the fourth slot of a Communication Media Module.

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

CSCed40428

Service parameter maximums are too low for MaxDbUpdatesAllowed and DbThrottleThreshold.

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

CSCed41072

Incorrect GMT time zone calculation displays on the phones for some time zones.

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

CSCed41107

The Line Group Configuration window times out when a large number of DNs are to display.

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

CSCed41115

Cisco CallManager release 3.3(3) does not include the AdminUtility-Readme.html file.

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

CSCed41279

The device defaults window does not include the Digital Access + gateway type.

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

CSCed41452

Cisco RIS Data Collector initialization errors display in the Application Event Viewer.

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

CSCed41589

SIF does not get negotiated between Cisco CallManager and H.323 endpoints.

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

CSCed41741

The updateRouteGroup AXL request halts the Cisco CallManager service and spikes CPU usage to 100 percent.

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

CSCed42581

The Route Pattern update display takes 30 seconds and CPU usage spikes to 100 percent.

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

CSCed42893

The comma from the slot module name needs to be removed.

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

CSCed43028

A semicolon needs to be added to the English version of the userwebdictionary.asp file.

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

CSCed43586

The "Retry Video Call as Audio" button needs to be added to the Cisco IP Phone models 7940 and 7960 device information window.

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

CSCed43731

IOS gateways with analog POTS ports assigned incorrectly contain the trunkselectionorder parameter in the .XML file.

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

CSCed44168

IP phones might disconnect and become idle when a reorder tone should be heard.

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

CSCed44223

MLA has permission problems when two users have common character strings.

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

CSCed44907

MLA user with full access permissions cannot query AXL and SOAP interface.

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

CSCed44936

Incorrect number of active calls are reported for route points when there are more than two calls.

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

CSCed45149

There is no video between two SCCP video endpoints.

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

CSCed45218

Aupair.exe application error occurs when the database layer monitor is stopped.

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

CSCed45853

The gateway-tones.xml file does not include the XML CPTONE_SIT and CPTONE_PREC_RINGBACK tags.

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

CSCed46552

Cisco CallManager sends SIF resolution without dynamic payload type support.

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

CSCed47587

Information gets lost after resizing the Cisco CallManager Administration window.

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

CSCed48483

The TFTP server does not cache the os7920.txt file.

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

CSCed48579

The dllhost.exe process for Cisco CallManager Administration fails to shut down and contributes to memory leak.

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

CSCed48598

JTAPI reports incorrect error message when routing to a CTI route point with CFwdAll.

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

CSCed49325

Failover takes a longer time in secure mode.

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

CSCed49450

CTI applications fail to open provider when user authentication is delayed.

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

CSCed50408

The Cisco CallManager User window presents too many options to users.

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

CSCed50770

Incorrect TAPI RedirectingIDFlags and RedirectionIDFlags display on a direct call via a DT24+ gateway.

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

CSCed51080

Running the CAR manager report increases CPU when Cisco CallManager is integrated with Active Directory.

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

CSCed51099

Directory authentication delay causes high CTI Manager CPU usage.

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

CSCed51455

Unanswered Call Park reversion display is infinite when the Call Park Display Timer service parameter equals 0.

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

CSCed51460

The Find/List Phone results window returns an error message when the database contains 15,000 phones.

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

CSCed51479

IP phone device profile disappears after BAT import and Extension Mobility logout.

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

CSCed52214

Encoding DL1 fails on a Q.SIG connection.

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

CSCed52779

Corrupted Japanese Katakana IP Phone Service Name exists.

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

CSCed52875

The CCM.exe process does not prevent a secondary CCM.exe process from executing when it is initiated from a Terminal Services connection.

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

CSCed53701

Memory leak occurs on Cisco CallManager after a long run of CP/CTI load.

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

CSCed54060

The Cisco RIS Data Collector service terminates unexpectedly on the subscriber server.

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

CSCed54206

Call to an unallocated number via the PSTN gateway incorrectly records as RNA.

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

CSCed55398

Device resets might not work correctly.

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

CSCed55971

Cisco CallManager release 4.0(1) does not support Cisco IP Communicator.

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

CSCed56053

The "Data Collection Polling Rate" does not affect RTMT data polling.

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

CSCed57003

When the user-side Cisco CallManager in disconnect_request11 state receives PRI status with callstate=19, the PSTN switch restarts the PRI span and drops the active calls.

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

CSCed57100

Device goes out-of-service during CallManager/CTI Manager failover failback.

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

CSCed57233

AutoInstall does not work from TSP 4.0(0.18) to TSP 4.0(0.1801).

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

CSCed57893

The RTMT console generate erroneous alarms for the DCD service when Cisco CallManager 4.0(1) is integrated with AD.

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

CSCed59226

The NM-HDV2 voice network module for Cisco CallManager 3.3(4) and 4.0 needs definition.

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

CSCed59822

The CFwdAll information does not display on the phone when the phone is registered to the subscriber server and the publisher server is offline.

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

CSCed60561

Cisco CallManager breaks up the "Connect DL3" message into two messages while in transit.

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

CSCed60593

The Route Plan Report database entry prevents calls from completing.

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

CSCed60975

The Answer button does not work on the phone when Conference is used.

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

CSCed61018

The Cisco CallManager Administrator password change does not get updated in the directory and registry following 4.0(1)SR1 installation.

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

CSCed61649

The CTI Manager service stops when the Call Back feature is registered twice.

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

CSCed62033

CTI-based applications time out because of long delays in authenticating users to DC Directory.

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

CSCed62199

Using ">" special characters in the User Group Base or Administrative User Base on the MLA Enterprise Parameter Configuration window causes a Java Script error.

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

CSCed62262

The called party does not display on the phone with overlap sending.

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

CSCed62269

Call Back notification does not get sent to the phone.

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

CSCed62908

Cisco CallManager displays "runtime error 380" when you click Next in the Select Service window and the date on the server is later than 2/1/2004.

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

CSCed63344

The Cisco Voice Mail Directory Numbers window in the Cisco Voice Mail Port Wizard returns a maxNumSize error message.

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

CSCed63429

DT-24+ gateways and ws-6608-T1 cards cannot be reset from the Cisco CallManager Administration window.

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

CSCed63670

Phones cannot reach the hunt list.

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

CSCed63741

Default profiles cannot be removed when Extension Mobility is disabled.

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

CSCed64534

The phone button template cannot be changed for an Extension Mobility phone.

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

CSCed64633

IPMA does not create proper phone templates for BAT.

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

CSCed64640

Drop intercom call does not drop the call.

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

CSCed64699

Dialing DTMF digits in the IPMA Assistant console behaves inconsistently.

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

CSCed64857

Originating phone does not terminate when SRV SIP trunk is used.

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

CSCed65108

Press the Update button twice for changes in the Max List Box Items enterprise parameter to take effect.

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

CSCed65446

The ProcessNode Change Notify signal from Aupair.exe does not get sent when a node is added.

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

CSCed66063

The Cisco CallManager Password Change Utility displays an erroneous error message.

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

CSCed66155

A cosmetic popup error message displays when attempting to delete multiple DNs from the Cisco CallManager Administration window.

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

CSCed66260

When the IPMA softkeys are removed from the softkey layout, the system deletes them from the "Unselected Softkeys" list, and they must be redefined and reapplied.

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

CSCed66771

The system ignores/nulls the addDeviceProfile and updateDeviceProfile fields in getDeviceProfile.

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

CSCed67082

The Trace Collection Tool displays an error message and cannot continue from the authentication window.

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

CSCed67276

Cisco CallManager upgrade from 3.3(2) with MLA 1.2(1) to 4.0(1) fails.

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

CSCed67643

No prompt to restart the Cisco CallManager service displays after the SCCP port number is changed.

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

CSCed68193

Cisco CallManager 4.0(1)SR1-rc3 includes empty SNMP cdpGlobalDeviceID.

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

CSCed68455

The MLA User Group Configuration window displays distorted Last Name/First Name/Dept fields.

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

CSCed68461

MLA User Group Configuration window cannot search on the Last Name field if it contains a slash ("\").

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

CSCed68532

Attendant Console does not log in the Attendant if the phone configuration changes.

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

CSCed68542

Long descriptions in the Voice Mail Port Wizard prevent it from working.

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

CSCed68590

LRP remains null during consult transfer between shared lines.

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

CSCed68617

CallPark number in the database does not display on the CallPark window.

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

CSCed68845

A video call that is made over an intercluster trunk might not have video after hold and resume operations.

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

CSCed69274

When BAT is used to add new DCD users, two user IDs may have the same GUID.

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

CSCed69403

T1 CAS channel continuously resets after it is busied out on the opposite side.

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

CSCed70291

Cisco CallManager may not send calling party name for incoming tandem calls.

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

CSCed70858

Adding a new music on hold source with special characters in the filename causes an error.

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

CSCed70911

The Cisco CallManager User window does not allow the use of some special characters when the user's password is changed.

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

CSCed70916

User cannot log in to the Cisco CallManager User Options Log On window if the password contains double quotes.

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

CSCed70985

Intercluster calls cannot connect after the trunk is reset.

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

CSCed71523

MLA does not display an error message if a password change fails.

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

CSCed71845

RTMT does not work after Cisco CallManager 4.0(1)SR01-rc04 is installed.

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

CSCed71853

The DN/Route Pattern window lists gateways with no DNs assigned if the search contains a "%" character.

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

CSCed71857

The DN/Route Pattern window lists CTI route points with no DNs assigned if the search contains a "%" character.

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

CSCed71861

The Find/List CTI Route Points results window does not display a CSS that is defined as "None."

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

CSCed71864

The DN search does not work on the Device Selection window for trace monitoring.

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

CSCed72033

The TSP installation accepts characters and special characters if they are placed after a number.

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

CSCed72046

Call Back displays an incorrect DN as being available with CFNA.

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

CSCed72311

IPMA user configuration does not work with Active Directory following an upgrade.

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

CSCed72489

The Cisco Extended Functions service terminates unexpectedly when Call Back is used.

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

CSCed72676

An incorrect error message displays when attempting to add invalid characters in the Nickname field.

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

CSCed72684

Ad hoc conference call drops during Cisco CallManager failover.

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

CSCed73599

Calls that are routed out of a Cisco CallManager Q.SIG trunk do not contain the redirecting party number in the FacilityIE for Q.SIG.

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

CSCed74445

Calls do not reroute immediately following a T1 CAS MGCP setup failure.

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

CSCed74559

Cisco CallManager might incorrectly use the line CSS in a forwarding request made through a CTI application when the line CSS and the CFwdAll CSS contain different partitions, causing the request to fail or forward to an incorrect DN.

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

CSCed74984

Incorrect message displays after deleting and updating a deleted attendant console user is deleted and updated.

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

CSCed75314

The CDP.SYS file version incorrectly displays 1.0.0.0 instead of 4.0.0.0.

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

CSCed75328

The CDPINTF.DLL file does not include a version that is assigned to the file properties.

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

CSCed75500

After upgrade to Cisco CallManager 3.3(3)SR4, some PRI connections on a 6608 module might not become active if they are using NI2.

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

CSCed75940

An incorrect message displays after attempting to update a deleted attendant console pilot point.

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

CSCed75954

The Find/Device Profile window does not display any records if the description contains a slash or a quote.

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

CSCed76123

CTI Manager does not send a DisplayChangedEvent after a phone goes idle.

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

CSCed76463

The H.323 and Cisco CallManager VideoCallsCompleted perfmon counters increment at different times.

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

CSCed76880

Add/update phone requests do not affect the <vendorConfig> element.

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

CSCed76932

Any subsequent CtiLineCloseLineReq closes multiple CTI lines that are opened for the same line appearance.

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

CSCed77334

The DigitsDialed for an outbound call record in the TCD as "null" when the call is placed from an Agent to "000."

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

CSCed78108

Information related to CTI devices and lines does not get reported correctly in RTMT.

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

CSCed78143

The IP Telephony Monitor (ITEM) reports that the Cisco CallManager database status is not operational when the sqlmangr.exe process is not running on the server.

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

CSCed78326

The CInsertVersionFromFile function inserts a version into the database when the EXE file does not contain version information.

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

CSCed78510

The call history for a parked call in "Placed Calls" differs from Cisco CallManager release 3.3(2) to release 3.3(3).

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

CSCed78712

The Delete button in the Find/List CSS results window fails to respond.

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

CSCed78741

The User Configuration Device Association window does not list any phones if the description contains a slash character.

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

CSCed79059

Cisco CallManager 4.0 fails to parse incoming Q.SIG MWI requests.

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

CSCed79124

Cisco CallManager mishandles malformed H.323 messages.

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

CSCed79346

Route list requires reconfiguration or deletion to use a new dial plan.

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

CSCed79429

The system does not allow the manager in the User Configuration Manager User ID field to be deleted.

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

CSCed79583

Voice Interface Card (VIC) options do not display for MGCP gateways with NMHDV2-2PORT-T1/E1 modules.

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

CSCed79630

The Softkey Layout should not allow use of an empty template.

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

CSCed79835

Call Back notification does not work with redial.

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

CSCed79954

The Cisco ICS 7750 System Manager fails to detect Cisco CallManager 4.0(1)SR1.

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

CSCed80030

A COM error displays when attempting to delete a Meet-me number from the subscriber server when the publisher server is offline.

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

CSCed80547

The component version in Cisco CallManager does not report the correct version of c:\CiscoPlugins\Client\CiscoAttendantConsoleClient.exe.

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

CSCed80703

Cisco CallManager with an H.323 gateway does not send a RELEASE_COMP after expiration of the T303 timer.

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

CSCed80870

The controller name truncates in the transfer, conference, barge, and cBarge start events.

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

CSCed81207

An incorrect Default Device profile name displays in the "Subscribe IP Phone Service" popup message.

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

CSCed81218

A conference with a "quite clear party" clears before that last user hangs up.

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

CSCed82223

The system uses an older user profile string query for some of the CDR Analysis and Reporting (CAR) queries for IPMA.

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

CSCed80547

Dependency Records for analog, BRI endpoints, and CallManager groups cannot be viewed if the description of the MGCP gateway is more than 64 characters.

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

CSCed83154

Line state changes do not get reported because of late line event filter updates.

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

CSCed84914

The called number information displays incorrectly in the called party transformations tags in the DNA output.

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

CSCed84935

Users without entries in the First Name field in the directory do not get listed in a search on the first name.

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

CSCed84989

Cisco CallManager terminates unexpectedly when multiple 18x responses are received via a SIP trunk.

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

CSCed85385

The default behavior for call-forwarding calling search spaces does not work correctly.

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

CSCed85447

A memory leak that is associated with the NTP process causes a degradation of system performance.

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

CSCed87354

Cisco CallManager does not send H.225 setup to alternate endpoints when the primary endpoint is out of service.

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

CSCed87618

Incorrect CFwdALL logic uses the line CSS of the destination DN when the CSS does not include the partition that is assigned to the DN.

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

CSCed88126

Using the Transfer or Conference softkeys while a second call is ringing on the same line places the first call on hold and transfers the second call.

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

CSCed88946

Upgrade Assistant 4.0(1) displays incorrect information about the operating system service release minimum version requirements.

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

CSCed88989

Upgrade Assistant uses incorrect logic when doing an operating system version check.

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

CSCed89773

Some database tables that are located on the publisher server do not replicate to the subscriber servers.

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

CSCed90281

The alarm interface reports that DC Directory failed during a backup when DCD is in a paused state.

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

CSCed90365

A too-small window displays for the PIN change popup window in the German version of Internet Explorer.

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

CSCed91643

Periodically, the CTI port hangs and the Cisco CallManager logs show "Internal error: illegal line number" error message.

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

CSCed92523

Deleting a Cisco CallManager group that is used by a VG200 causes a remote scripting error.

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

CSCed92574

Cisco CallManager sends old information for the alternate endpoint after a reboot of the peer server.

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

CSCed92842

A call to an unallocated number via the PSTN gateway records as a RNA instead of an unallocated number.

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

CSCed92994

The Quality Report Tool (QRT) stops responding on a phone after Call Back and QRT report processing.

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

CSCed93725

The Snapshot agent takes longer than normal to replicate the database after the last subscriber server is upgraded.

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

CSCed93825

A user ID cannot be deleted if it contains a valid locale-related character.

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

CSCed95528

TSP tries too early to open the second line on the same CTI port as line one opened.

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

CSCee00446

Consult transfer of a conference call does not work on the IPMA Assistant GUI.

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

CSCee00570

Because the Min-SE timer cannot be changed from its default value in Cisco CallManager release 4.0(1), it causes rejection of the SIP trunk INVITE with the Min-SE header that is set to a value of less than 360 seconds.

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

CSCee01180

A Service URL button cannot be assigned from the Device Profile window.

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

CSCee02160

Change notifications are lost after the Aupair client thread stops responding.

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

CSCee02193

Integration of the OpenSSL patch CAN-2004-0079 with Cisco CallManager is needed.

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

CSCee02373

The "Retry Video As Audio Flag" parameter should default to True for all phones.

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

CSCee02852

Cisco CallManager 4.0 drops calls when it receives a SIP INVITE message that contains an unrecognizable parameter in the Record-Route header.

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

CSCee03346

Long counter names cause RTMT to terminate unexpectedly.

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

CSCee03636

The Adminutility.exe process should reset SQLSvc passwords and services before starting Cisco CallManager.

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

CSCee03771

Outbound calls via the 6608 PRI gateway that is using DMS100 do not display the dialed number on the originating Cisco IP Phone 7960.

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

CSCee04067

Performance degrades in Cisco CallManager when a CTI provider is closed.

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

CSCee04178

CRS calls may be aborted on a co-located server when conferencing is running along with CRS.

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

CSCee04282

The DNA trace files might be overwritten after large change notifications occur.

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

CSCee04526

The processing time for an initial device lookup on the Find/List Phones window is delayed and the status of the devices displays "Not found."

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

CSCee04972

TSP terminates unexpectedly when lineInitializeEx is requested directly after a new device is added.

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

CSCee05724

Cisco CallManager terminates unexpectedly after the SDL router thread stalls because of an internal error.

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

CSCee05780

DCD latencies occur with upgrades and change notifications due to indexing issues.

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

CSCee06453

Cisco CallManager terminates unexpectedly when the trace files cannot be written.

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

CSCee06698

When a 6624 port is out of service, calls receive a fast busy tone.

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

CSCee06810

The VCB window displays a remote script error when the product configuration data entry is too long.

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

CSCee07070

The incorrect icon for the CallManager Group displays in the Cisco CallManager Dependency Record.

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

CSCee07142

When Cisco CallManager fails over, a held PRI call via an IOS MGCP gateway does not terminate, and the caller hears dead air.

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

CSCee08380

DNA trace files display an error while inserting forward intercepts on DNA version 2.0 and 3.0.

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

CSCee08447

An incorrect status message displays when a user is deleted from a user group.

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

CSCee08463

A remote error displays when a functional group with all fields unchecked is updated.

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

CSCee08483

The Voice Mail Port Wizard help window does not exist.

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

CSCee09495

Audio files drop when the source file contains the "&" character.

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

CSCee09716

Run-time change notification fails and must be restarted.

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

CSCee09728

A change notification storm locks out the Aupair client thread.

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

CSCee09965

TermConn displays the InUse state after a shared-line device holds a call.

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

CSCee10023

ProcessGKIFHandler incorrectly doubles video bandwidth.

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

CSCee10439

JtapiPeer.getProvider(loginStr) sends a NullPointerException because of a new key (UseProgressAsDisconnectedDuringErrorEnabled) that is added in the jtapi.ini file but is not present by default.

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

CSCee10655

A CDBLException error message displays when the design limit of 500 regions is almost reached.

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

CSCee10739

Remote endpoint channel state displays incorrectly on Performance Monitor for the T1-CAS(6608) busyout feature.

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

CSCee10909

Inconsistent information displays for the CallPark feature.

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

CSCee10974

The system limits the number of prefix digits to five in the Route/Hunt List Detail Configuration window.

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

CSCee11611

Call resume fails for H.323 inbound faststart call from gateway over intercluster trunk.

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

CSCee11683

The Attendant DN does not display correctly for an FXO MGCP analog endpoint.

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

CSCee11972

The Find/List Meet-Me Numbers results window displays an error when searching for a description that begins with the "`" character.

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

CSCee12180

A number greater than the maximum number of registered devices can register to Cisco CallManager.

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

CSCee13139

The Service Parameters Configuration window displays a stack overflow for long entries.

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

CSCee14224

Delayed dial tone occurs after update to voice mail profile.

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

CSCee14445

The call-forwarding icon continues to display on the IP phone after call forwarding is disabled from the softkey display.

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

CSCee14666

QRT does not display the localized text on the phone.

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

CSCee14761

The online help for the Device Profile Default Configuration window displays a message showing that the page is not found.

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

CSCee14765

The audio path may prematurely shut down when a SIP phone is connected to third party devices that initiate call features, such as hold and transfer.

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

CSCee14877

Calls across a T1 PRI that is configured for the PRI-Q.SIG protocol might not be established correctly.

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

CSCee15189

Too many concurrent TFTP client requests for the same file cause a "file open" error message.

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

CSCee16090

User information cannot be updated when trying to add a user to the Directory where only a single character is inserted for each field.

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

CSCee16407

Cisco CallManager cannot process the deletion of a large number of DNs at one time.

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

CSCee16842

Delayed response occurs when the Cisco CallManager 4.0 JTAPI client is used to complete the addition of callObserver.

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

CSCee17294

A remote script error displays when Netscape browser 4.61 is used to add a new region.

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

CSCee17299

A blank page displays when Netscape browser 4.61 is used to update a region.

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

CSCee17454

Calls cannot be answered when the third-party voice messaging system is busy and the iDivert softkey is pressed on a forwarded call.

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

CSCee17477

On an intercluster trunk with a gatekeeper, Cisco CallManager sends an RRQ message with the incorrect alternate endpoint information to the gatekeeper.

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

CSCee18324

When CTI Manager restarts and cannot acquire device status, JTAPI needs to reacquire devices on CTI Manager.

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

CSCee18647

The User ID Lookup page in the Phone Configuration window lists all user IDs when the search includes the "*" character.

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

CSCee18731

An "Unable to locate DLL" error message occurs during the execution of tabsync.exe because the tabsync install shield contains the wrong location for .dll files.

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

CSCee18751

The "Tone on Call Forward" service parameter does not work.

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

CSCee19058

When the TFTP and Cisco CallManager services are disabled on the publisher server, the CTL client configuration fails.

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

CSCee19367

When a Cisco CallManager-controlled, network-side T1 CAS does not receive the proper message from the gateway, the call does not terminate after the T301 timer expires.

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

CSCee19789

Modify the help window for the "Tone on Call Forward" service parameter to account for changes that were made for the call-waiting feature.

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

CSCee19811

CallPark does not work after an update is made to Park Settings.

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

CSCee19913

Inconsistent characters display on the directory pages.

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

CSCee19916

A line text label that contains a Russian character cannot be deleted on the Cisco IP Phone 7960.

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

CSCee20247

Cisco CallManager Upgrade Assistant 3.3.4a on a release 3.1 subscriber server does not perform some file validations.

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

CSCee21283

Cisco CallManager displays an incorrect message when attempting to delete a line group associated with a hunt list from the Find/List Line Group results window.

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

CSCee21442

RTMT perfmon monitoring does not work when one of the active CallManager servers is offline.

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

CSCee21452

Pressing the Hold and NewCall softkeys on the first call answers a ringing call.

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

CSCee21785

The OS Flag file validation fails when Cisco CallManager Upgrade Assistant release UA 3.3(4)b is used because the system cannot find the recovery flag.

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

CSCee21883

During a load test, a small number of conference calls fails because of a "Could not meet post conditions" exception.

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

CSCee22178

Invoking the malicious caller ID (MCID) feature causes a memory leak.

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

CSCee22740

The number prefix supports only digits 0 through 9 for inbound calling line ID numbers.

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

CSCee22801

Restarting the RISDC on the primary Cisco RIS Data Collector node, or changing the primary Cisco RIS Data Collector, causes the RISDC on the primary Cisco RIS Data Collector to stop.

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

CSCee23006

When an SCCP device registers with Cisco CallManager, the Video Bridge Control (VBC) does not inform the SCCP device of its version by returning the maxProtocolVersion in the StationRegisterAck.

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

CSCee23128

When CTI Manager is located on one node and the Call Manager processes are spread among different nodes, call control might process two redirects for one call, which causes the second redirect to fail.

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

CSCee24023

Incorrect RedirectionID-Name displays on a connected call that is redirected.

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

CSCee24106

The Find/List Route Patterns/Hunt Pilots searches that contain a "[" character correctly display the number of matches but not the patterns that match.

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

CSCee24128

After the SCA receives an ACK to data that it sent, it sends an ACK with a decremented TCP sequence number.

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

CSCee24388

When BAT is used to import a phone that includes a Call Pickup Group, the import might fail if the Call Pickup Group partition is included in the device CSS but it is not included in the line CSS.

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

CSCee25461

The Cisco CallManager installation or upgrade might stall when attempting to install DCD if the popup window that displays behind the setup progress bar is not acknowledged.

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

CSCee25587

Voice mail pilot changes cause MWI, CFwd, and Extension Mobility login/logout delays.

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

CSCee26213

Accessing help on the Q.931 translation window causes a Java Script error.

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

CSCee26221

Choosing "IOS Format" on the Q.931 translation window causes a Java Script error.

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

CSCee26934

For an H.323 to H.323 call, Cisco CallManager drops the call if the audio rate is zero.

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

CSCee27177

Cisco CallManager cannot handle the deletion of a large number of DNs at one time.

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

CSCee27416

When a busy extension is called, a short ringback tone is heard before a busy signal when an inbound call is intercepted and accepted by a CTI application, such as IPMA.

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

CSCee28062

All available DNs might not display in the line group configuration when more than 96 ports are added to a line group by using the Voice Mail Wizard.

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

CSCee28103

Route/Hunt lists might be taken out of service if they are configured with a Cisco CallManager Group that contains only one Cisco CallManager.

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

CSCee28470

No help page for Q931Translator.asp is available.

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

CSCee29638

On the Phone Configuration window, the Delete button stops responding if the Cancel button is clicked when the alert message prompt window displays.

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

CSCee29834

The Find/List Phones results window does not display the details of the phones and instead displays "The page cannot be found" message.

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

CSCee30267

There is no voice recognition or only the first answer is recognized when the IP RTP communications from the CRS ipvms driver to the voice-recognition server is terminated because of receiving ICMP messages.

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

CSCee30277

Users who are created through Netscape iPlanet administration cannot be updated.

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

CSCee30417

ISDN calls that are made through a loopback connection in the TI PRI interface do not proceed.

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

CSCee30571

Route/Hunt List redundancy is lost after upgrade where the Cisco CallManager Group contains only one Cisco CallManager.

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

CSCee30600

Cisco IP Phone 7970 sends encrypted audio after an H.323 call is placed on hold and then resumed.

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

CSCee30662

Cisco CallManager traces do not show encryption information for SCCP messages.

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

CSCee30744

Running CRS co-resident on the same Cisco CallManager server exceeds the Heap size required to run all services concurrently.

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

CSCee30975

Translation Pattern CSS changes do not take effect after an update.

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

CSCee31432

Cisco JTAPI call control does not work with IBM Java Virtual Machine (JVM).

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

CSCee31508

Cisco CallManager terminates unexpectedly when it tries to bring up the MGCP T1 PRI loopback gateway.

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

CSCee31635

Entering extra digits while annunciator is active generates a reorder tone.

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

CSCee32441

When the SIP Default Telephony Event Payload Type service parameter field is set to 96, internetworking problems might occur.

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

CSCee32515

Upgrade from Cisco CallManager 3.3(3)SR4a to release 4.0(1) fails because the device table PhoneTemplateClause column is removed as part of the installation.

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

CSCee32579

MLPP call causes hunt list to scroll twice.

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

CSCee33348

Cisco CallManager does not check for square brackets in a valid DN pattern, which causes the DN to not be found in updateDeviceProfileRequest.

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

CSCee33737

A large number of D-channel out-of-service devices causes a memory leak and delays device status lookup on the publisher server.

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

CSCee33828

Adding and modifying more than 10 regions at a time causes an error.

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

CSCee33850

Old notification information is sent in the outbound facility message, so path replacement does not occur between another-vendor PBX and Cisco CallManager release 3.3(2)FP2.

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

CSCee34025

IP phone fails to dial an entire 24-digit number from the Directories > Placed Calls menu.

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

CSCee34578

A Locations Call Admission Control (CAC) bandwidth leak causes a leaked call to appear as a call in progress.

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

CSCee34908

Conference between multiple call instances of the same line might occur if Cisco CallManager does not terminate the conference instance when the first conference request is rejected.

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

CSCee35017

If FwdAll CSS is configured differently than the line CSS and set forward is called from the API, the request might fail or forwarding might be set to the incorrect DN.

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

CSCee35265

A route pattern update causes a DBLException error.

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

CSCee35342

RTMT intermittently reports that the monitored services have a low heartbeat rate.

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

CSCee35959

Call Back activation/notification does not show the DN.

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

CSCee36765

No QRT documentation is available.

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

CSCee36965

T1 CAS gateway does not register to Cisco CallManager because of an invalid setting.

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

CSCee37796

The IP Media Streaming Application (MSA) process stops on outbound SIP trunk calls when multiple resets on an MTP device create orphan MSA streams in call-preservation mode.

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

CSCee37857

ProviderServiceInfo for park devices returns an invalid TSP version.

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

CSCee38006

Cisco CallManager terminates unexpectedly during new device registration.

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

CSCee38024

Cisco CallManager does not provide checks to validate a valid user device profile during an addition or update of the user profile.

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

CSCee38625

Upgrade to 4.0(1)SR2-rc6 results in jarhead.exe reports failure in the Ciscoupdate.txt log file because of the subdirectory location of Cisco CallManager Serviceability.

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

CSCee39120

One-way audio might occur after a SIP phone that is connected to a third party SIP PBX initiates placing a call on hold.

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

CSCee39967

An IP phone incorrectly displays its own number when a held call from an MGCP or H.323 gateway is resumed.

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

CSCee40016

The "CDR File Time Interval" enterprise parameter incorrectly changes from the maximum set value to 0.

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

CSCee40142

Incorrect information about service dependencies appear in the Service Control Manager database.

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

CSCee41183

Adding a DN and configuring a device for the port on a 3745 gateway result in a CDBLException error.

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

CSCee42544

Updating or deleting a route list through ERPW causes an error.

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

CSCee42571

Cisco IP Phone loses the Service URL that is assigned to a line when a user logs out of the Extension Mobility service.

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

CSCee42572

The help page for the User Configuration Settings "View page in" field displays an incorrect explanation of the field.

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

CSCee42723

Calls from a Centrex PBX operator to an IP phone via a Q.SIG trunk cannot be transferred.

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

CSCee43112

Delayed dial tone occurs when T1/PRI (MGCP) gateways fail over to the backup Cisco CallManager.

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

CSCee43591

Calls can be made from a deleted line unless the line/phone is manually reset.

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

CSCee43707

Improper display appears when conferencing a SIP intercluster trunk.

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

CSCee44141

The appropriate error message for the entry of the number of MultiTSP installs does not display.

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

CSCee44483

XML request for listAllProcessNodes results in an XML error.

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

CSCee45015

An IP phone that fails over to a secondary Cisco CallManager may not make calls out a remote H.323 gateway if the H.323 gateway does not fail over because its primary Cisco CallManager remains available.

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

CSCee46732

MWI does not work for an SMDI integration that is using the Cisco Messaging Interface.

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

CSCee47172

The Aupair connection cannot properly handle an unknown exception.

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

CSCee47341

A device cannot be associated to a user in the Russian locale.

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

CSCee47880

When LineOpen is attempted for a device that is not in the control list and the user is not superprovider, CTI Manager does not send any response to the application.

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

CSCee48304

An ad hoc conference call cannot hear PSTN caller audio.

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

CSCee48985

An interface that lists the phone names by the service name to which they are subscribed needs definition.

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

CSCee50439

Cisco CallManager terminates unexpectedly because the CalledParty is out of boundary.

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

CSCee52285

If you press CFwdAll on the phone but do not enter any digits, Cisco CallManager checks the CallForwardAll check box in the Phone Configuration window.

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

CSCee52921

SMDI messages for a voice-messaging system do not generate.

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

CSCee54571

Calls through a SIP trunk that require a transcoder receive a busy signal.

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

CSCee54687

Cisco CallManager traces do not explicitly state when the maximum number of calls has been exceeded.

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

CSCee54919

Dial Tone Delay/OutOfSync status triggers sequential route list retry.

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

CSCee56312

The MLA Phone Administration user group cannot delete a line from a phone.

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

CSCee57433

A barged call does note get encrypted even if it is capable of encryption.

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

CSCee57528

Calls to an Extension Mobility DN fail when using Cisco CallManager 4.0(1)SR1 or SR2 with Extension Mobility and IPMA.

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

CSCee57531

Cisco CallManager installation allows web upgrade from release 3.3(x) to 4.0(x).

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

CSCee58108

Upgrade from Cisco CallManager release 3.3(2)FP2/3.3(3) to 4.0(1.60) fails because of a database migration failure.

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

CSCee58223

An incorrect message displays when all ports of a line group are deleted by using the Voice Mail Wizard.

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

CSCee60323

DNA installation causes DB Error: 1544 CDBLException on the trace page.

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

CSCee60952

Users with special character maps result in error on deletion and update after upgrade from Cisco CallManager 3.3(3) to 4.0(2).

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

CSCee62312

One-way audio occurs over a SIP trunk in delayed media situations.

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

CSCee63815

Call Forward All fails intermittently.

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

CSCee64467

Conferees in a Meet-me conference hear a long beep when other parties join.

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

CSCee64928

Removing line group from Route/Hunt List causes out-of-service condition for about 20 minutes.

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

CSCee67392

Modify the help description for the service parameter "Max forward hops to DN" to clarify that the parameter is applicable when using an intercluster trunk and does not apply to normal IP-to-IP calls.

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

CSCee68440

Calls to SMDI-based voice messaging systems might fail when the calling party number is longer than 10 digits.

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

CSCee69225

Cisco CallManager file open/close latency creates high SDL queue counts.

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

CSCee69277

Cannot add VG248 gateway.

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

CSCee70057

Calls to an Attendant Console pilot number fail because of insufficient bandwidth for IP phones in the same location when the location is set to use less than 80 KB.

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

CSCee73359

Secure calls fail after transferring a call from an IP phone to an IP-STE (gateway).

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

CSCee84214

Pressing the iDivert softkey on a phone that is part of a line group in a hunt list causes iDivert to become inactive, hunting to stop, and the phone to ring until it times out.

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

CSCee86257

Running the IPMA configuration wizard with about 2500 selected calling search spaces causes the CPU to reach 100%.

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

CSCee94298

Calls cannot join in a conference when one of the phones is configured for CFNA to voice mail and the voice mail system is offline.

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

CSCef09709

MGCP gateway cnf.xml files are not created when MGCP gateways are configured.

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

CSCef18182

Phones do not register with the backup Cisco CallManager server.

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

CSCef23393

Call forwarding fails intermittently.

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

CSCin53398

The message that displays when services are being stopped during the uninstallation process for Cisco CallManager 3.3(3)SR1 needs clarification.

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

CSCin55125

Null values get inserted for parameter field in route filters.

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

CSCin57144

The correct multicast IP address and port number validation for a music on hold server does not display in the music on hold configuration window.

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

CSCin59391

Cisco CallManager does not validate the availability of a gateway when DNs are inserted into a route group.

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

CSCin61098

The pilot number in the Pilot Point Configuration window does not allow "*" or "#" as valid characters.

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

CSCin61478

Calls to Personal Assistant route points hang intermittently.

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

CSCin61590

Cisco CallManager Administration does not have an is empty and is not empty search parameter that is available for finding Meet-me numbers.

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

CSCin61718

The Copy, Update, and Delete buttons in the Phone Configuration window stop responding after the delete and then cancel options are chosen.

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

CSCin62402

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

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

CSCin62724

Accessing MTP from the firmware load information window causes an error.

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

CSCin62741

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

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

CSCin62870

The firmware load information window does not show the Cisco IP Phone 7970 with a special load for the expansion modules.

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

CSCin63437

Administrators get a remote scripting error message when they enter invalid characters during the configuration of a NM-HD-2VE network module.

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

CSCin64126

The Dependency Record of the "Default" and "No Voice Mail" Voice Mail Pilots do not show the proper names.

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

CSCin64416

The Device Name field in the H.323 client phone configuration window accepts incomplete IP addresses and allows phone registration with an unknown IP address.

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

CSCin64454

The Update and Delete buttons in the IP Phone Services Configuration window stop responding after the delete and then cancel options are chosen.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCin64454

CSCin64520

Cisco CallManager allows assignment of the 14-button extension mobility template to the Cisco IP Phone 7960 and 7970 from the Device Defaults window.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCin64520

CSCin66269

The Attendant DN does not display when the FXO port configuration is accessed from the Route Pattern Configuration window.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCin66269

CSCin66881

The service parameter "Port Release Timer" resets when the WS-X6624 FXS port goes off hook and on hook, but the perfmon counter does not reset and increments the value for "FxsPortsActive."

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCin66881

CSCin67332

The search display for "device pool" in Find/list Annunciator results window shows the description and name interchanged.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCin67332

CSCin67333

A user ID with the "`" character can be inserted but it cannot be associated in the Phone Configuration window.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCin67333

CSCin67507

Entering an intermediate page number in the "Page" field for Find/List Phones results window does not display the requested page.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCin67507

CSCin67542

Cisco CallManager does not handle the deletion of MGCP gateways correctly.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCin67542

CSCin67748

Entering an intermediate page number in the "Page" field for Find/List CTI Route Points results window does not display the requested page.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCin67748

CSCin67749

Entering an intermediate page number in the "Page" field for Find/List Gateways does not display the requested page.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCin67748

CSCin67750

Entering an intermediate page number in the "Page" field for Find/List Annunciators does not display the requested page.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCin67748

CSCin67923

The caller ID of a phone that is calling through a route pattern or translation pattern with restricted "Calling Line ID Presentation" gets revealed when the phone is added to a conference and the "ConfList" softkey is pressed.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCin67923

CSCin67936

The conference controller does not display when the "ConfList" softkey is pressed on the phone.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCin67936

CSCin67968

Call Back shows an incorrect DN as available with CFNA.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCin67968

CSCin68055

The DeviceCloseMaxEventsExceeded alarm displays UNKNOWN_PARAMTYPE when Cisco CallManager throttles faulty devices.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCin68055

CSCin68212

The Dependency Record displays a blank page when multicasting is enabled for a music on hold server.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCin68212

CSCin68292

Transcoding resources display an incorrect value after reset.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCin68292

CSCin68416

Gateway cnf files do not update when an MGCP CAS port is deleted/modified.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCin68416

CSCin68793

A reorder tone cannot be heard when an invalid DN is dialed through an MGCP FXS prefix DN.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCin68793

CSCin68939

Call Back notification does not work after Call Back is set to busy on the phone.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCin68939

CSCin70378

Include a prompt message to reset the WS-X6624 gateway after adding an FXS port.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCin70378

CSCin71278

The help window does not open when it is accessed from the "Add Application" window from the Softkey Template Configuration window.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCin71278

CSCin72270

Analog Telephone Adapter (ATA) phones display in the incorrect table in Cisco CallManager release 3.3(3)SR4 and 4.0.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCin72270

CSCin72506

A search pattern that includes double quotes in the Q.931 translator window causes an error.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCin72506

CSCin72522

IP phone service parameters cannot be updated when the service name includes a space character.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCin72522

CSCin72755

The performance monitor displays incorrect values for the far-end and near-end gateway endpoints after they are out of service and reset.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCin72755

CSCin73646

Adding a new Route/Hunt List causes an error in Cisco CallManager 4.0(1)SR2.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCin73646

CSCin73721

The performance monitor incorrectly shows the channel status as "1" for channels that were not configured for out of service.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCin73721

CSCin73896

Attempting to activate Call Back to a forwarded call causes the call to disconnect.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCin73896

CSCin73943

An MGCP POTs phone continues to ring after the originating IP phone disconnects because of a "no answer" timer expiration.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCin73943

CSCin74007

Calls cannot be made to Manager phones when the IPMA service is down.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCin74007

CSCin74262

Resetting a 6608 T1 module with back-to-back connected T1 ports can restart channels that were out of service.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCin74262

CSCin74386

The performance monitor displays an incorrect status for a far-end 6608 T1 CAS gateway when MLPP is enabled.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCin74386

CSCuk48169

The LineGetInfoResponse incorrectly displays the total active and held calls for all lines on the device instead of on a per-line basis.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCuk48169

CSCuk49514

The Cisco CallManager Upgrade Assistant Utility does not check all keys in the system registry, which causes an error.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCuk49514

CSCuk49586

Cisco CallManager allows the configuration of unsupported overlap route patterns on MGCP-controlled FXO gateways.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCuk49586

CSCuk49803

The AXL API interface needs modification so that the Device Profile is not mandatory when adding a phone through AXL API.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCuk49803

CSCuk51665

IPMA immediate divert fails when calling a user who is on a different server than the assistants.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCuk51665

The following firmware caveats apply to this release

CSCeb69347

Cisco IP Phone 7910 displays a misleading message when user selects a call park number that is out of range.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeb69347

CSCec20794

Cisco IP Phone does not display the 200th call instance.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec20794

CSCec58677

IP phone displays the original called information on a call when the calling party name or calling party number is restricted.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec58677

CSCec76440

Cisco IP Phone 7910 returns a success for a phoneSetDisplay and a phoneGetDisplay request from a TAPI application, but it does not display the text.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec76440

CSCec78423

Cisco IP Phones 7940 and 7960 reset when no results exist in the corporate directory and the user presses the dial softkey.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec78423

CSCed02259

User cannot answer the ninth call on an IP Phone that is using a TAPI application.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed02259

CSCed02271

Phone resets after a call to a CTI port with Dynamic Registration Port setting is dropped in fast mode.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed02271

CSCed20153

Cisco IP Phone displays a corrupted screen when you push an execute request object to the phone in the network configuration window.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed20153

CSCed23335

Cisco IP Phone 7970 does not immediately display the digits when you dialed with the phone on hook.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed23335

CSCed26357

Cisco IP Phone 7960 and Cisco IP Phone 7905 have different remote in use icons.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed26357

CSCed34320

Cisco IP Phone 7970 does not work when you choose a nonactive audio preference setting.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed34320

CSCed59942

Calls forwarded to the PSTN get disconnected after a brief ring.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed59942

CSCed93832

One-way audio may occur on some calls from the PSTN when a 6608 gateway sends 0 as the RTP port number.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed93832

CSCed94450

Crosstalk occurs on two individual calls through a 6608 after a hairpinned call if the telephony side of one call hangs the channel.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed94450

CSCee0057

A 6608 T1 port must use 22 timeslots or less to register with Cisco CallManager release 3.2.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCee0057

CSCed09672

Calls from remote endpoints do not work after a 6608 T1 CAS busyout is set from out of service to in service on Cisco CallManager 4.0(1)SR2.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed09672

CSCee17932

An originating T1 CAS Catalyst 6000 channel gets locked and calls fail when the terminating phone does not pick up the call.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCee17932

CSCin67349

6608/6624 gateways fail to register with Cisco CallManager after the IP addresses are changed by using the "set port voice interface dhcp disable" CLI command from the Catalyst 6000 switch console.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCin67349

CSCin68941

The ws-x6608 port configuration details window does not reflect port direction.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCin68941

CSCin72112

Calls that are placed by using 6608 T1 CAS ports with delay dial fail because of a timer resolution issue.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCin72112

CSCin72395

Calls that are placed from a 6624 to an IOS MGCP FXS gateway fail after receiving an incoming call from the IOS MGCP FXS port.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCin72395

Note For complete Cisco IP Phone firmware release note information, refer to the applicable firmware release notes for your specific model IP phone at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_ipphon/english/.

Open Caveats for Cisco CallManager - Release 4.0(2)

Table 2 describes possible unexpected behaviors by Cisco CallManager release 4.0(2). Unless otherwise noted, these caveats apply to all Cisco CallManager 3.0 releases up to and including Cisco CallManager release 4.0(2).

If you have an account with Cisco.com (Cisco Connection Online), you can use the Bug Toolkit to find caveats of any severity for any release.

To access the Bug Toolkit, log on to

http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl

Table 2 Open Caveats for Cisco CallManager Release 4.0(2)

Identifier

Headline

CSCeb39815

After upgrading Cisco CallManager, the Remember Last Userid feature only works the first time that it is used.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeb39815

CSCeb71965

Phone displays incorrect text for missed and placed calls.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeb71965

CSCeb75996

You cannot restart Microsoft Internet Information Services (IIS) on a Cisco CallManager server.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeb75996

CSCec57609

Cisco CallManager service stops when the database has over 24,000 phones.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec57609

CSCec63322

Phone configuration changes do not take effect until the Trivial File Transfer Protocol (TFTP) service is restarted.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec63322

CSCec66251

When Cisco Multilevel Administration Access (MLA) is enabled, a user with read-only access can update trace configuration.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec66251

CSCec68278

IP phone does not download updated phone load configuration until TFTP service is restarted.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec68278

CSCec68721

New trace settings in Serviceability Trace Configuration for CTL Provider do not take effect until the CTL provider service is restarted.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec68721

CSCec70462

Cisco CallManager Administration should have an enterprise-level parameter for configuring phone web access.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec70462

CSCec70975

Calls from a TAPI application fail when Cisco CallManager server has busy hour call attempts (BHCA) of 15,000.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec70975

CSCec85629

Cisco CallManager Administration does not provide codec selections other than G711u and G711a in Session Initiation Protocol (SIP) trunk configuration.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec85629

CSCed00948

The dialog boxes for some warning messages do not pop to the top of a user screen.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed00948

CSCed01028

Cisco IPMA service stops responding when you repeatedly stop and restart the service.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed01028

CSCed06085

Cisco CallManager does not stop the Cisco Tomcat Service gracefully.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed06085

CSCed07230

JTAPI sends an incorrect callCtl_cause code when a shared-line device redirects a barged call.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed07230

CSCed12260

Server recovery fails when groups do not get added before a backup is started.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed12260

CSCed14917

IP phone displays the wrong time when users choose the Brussels, Paris, Madrid timezone.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed14917

CSCed16182

Web dialer displays windows in English when other locales are chosen.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed16182

CSCed18284

Phones do not work when Cisco CallManager fails over.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed18284

CSCed19335

Cisco CallManager slows down the delivery of events to a directory number as calls accumulate on a route point.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed19335

CSCed19620

Music on hold servers might experience performance degradation in Cisco CallManager release 4.0.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed19620

CSCed19775

Cisco CallManager does not release hardware conference port resources.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed19775

CSCed19892

Cisco CallManager does not send a H.225 information message for a blind transfer call.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed19892

CSCed20527

Annunciator does not get allocated because Unicast Bridge is not assigned annunciator resources.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed20527

CSCed22524

The CTL client displays a misleading message when a connection is queued.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed22524

CSCed25430

Cisco IP Authentication and Encryption for Cisco CallManager 4.0(1) documentation does not state that the Certificate Authority Proxy Function (CAPF) utility supports third-party RSA Keon Certificate Authority.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed25430

CSCed25556

The CAPF utility supports the RSA Keon Certificate Authority.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed25556

CSCed28145

The eToken service does not get installed when you reboot a computer while installing the CTL client.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed28145

CSCed54165

CTI Manager uses more CPU cycles than previous version.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed54165

CSCed61042

The Cisco Extended Functions Service does not reconnect to CTI Manager after an Ethernet NIC outage.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed61042

CSCed64586

Cisco IP Manager Assistant watch on the manager IP phone does not update when a call is parked and retrieved from another IP phone.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed64586

CSCed68538

Incorrect CDR values display for NetMeeting calls.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed68538

CSCed69980

Software Conference Bridge resets when Meet-me conference is connected overnight.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed69980

CSCed70801

The Cisco IPMA User Configuration window returns an error if the user last name contains a "\" character.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed70801

CSCed73305

CTL client fails on the first connection attempt after upgrade to Cisco CallManager release 4.0(2).

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed73305

CSCed89411

Extension Mobility login fails when used as service URL button.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed89411

CSCee05963

Cannot associate a device to a user name that contains spaces in the user ID field.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCee05963

CSCee12748

The IPMA "filtering down" message does not display on phones that are running certain versions.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCee12748

CSCee13077

The i-button help contains "&gt," "&amp," "&kt," and "&lt" characters in some of the help content.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCee13077

CSCee13104

Some IPMA mnemonics do not work in the Italian locale.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCee13104

CSCee13120

Certain characters do not show up correctly on the CFwdAll help display.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCee13120

CSCee13705

JTAPI sends out of service events when the system time is moved forward.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCee13705

CSCee15964

IPMA softkeys become inactive after failover.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCee15964

CSCee16237

Calls fail to go through the intercom line of the IPMA Assistant.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCee16237

CSCee18778

Call details on the IPMA Manager status window do not display after logout and login.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCee18778

CSCee19908

Extension Mobility on a Cisco IP Phone 7970 shows English in all locales.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCee19908

CSCee20231

Gaps of up to 10 seconds occur in between the first and second signals in the SDL traces, and DATimeout Emergency errors display in the traces.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCee20231

CSCee21350

The Route Pattern Configuration Window does not respond when Update is clicked twice.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCee21350

CSCee24094

Slow memory leak occurs on the publisher/TFTP server.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCee24094

CSCee25670

When using Cisco CallManager automated configuration, MGCP T1-CAS ports do not come into service and call attempts fail.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCee25670

CSCee28162

Speed dials that are not associated to an IP phone button cannot be accessed from the phone.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCee28162

CSCee31250

Called party number does not display in the CDR record if unallocated.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCee31250

CSCee32676

Because the IPMA icons on the IP phone are too large, they block speed-dial text.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCee32676

CSCee35979

IPMA Assistant Watch changes from off to on after upgrade to 4.0(2).

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCee35979

CSCee37526

BAT query does not allow update or deletion of phones.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCee37526

CSCee39828

Searching DC Directory from an IP phone causes errors and high CPU.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCee39828

CSCee39850

Cisco CallManager upgrade fails after failure to stop MSSQLSERVER service(s).

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCee39850

CSCee40271

Cannot make calls after creating a new H.323 gateway and assigning route patterns.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCee40271

CSCee46159

The External Route Plan Wizard creates invalid route lists because it does not associate route lists with Cisco CallManager Groups.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCee46159

CSCee48504

Route/hunt lists do not register on a very large cluster.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCee48504

CSCee50169

Ad hoc conference call drops when sixth participant is added before answering.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCee50169

CSCee51610

The "H323 faststart inbound" command causes calls to drop when a call on hold is retrieved or when an attempt is made to transfer a call.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCee51610

CSCee54781

The Upgrading Cisco CallManager documentation needs an update for the MCS server model 7835I.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCee54781

CSCee56942

Incorrect LRPName displays in a redirect scenario when shared lines are used.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCee56942

CSCee57071

When used with a large cluster, Cisco CallManager takes about 10-15 minutes longer to initialize over previous version.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCee57071

CSCee58352

Directory record of the line group displays orphan directory numbers when the partition is assigned.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCee58352

CSCee58381

Directory report of a voice-mail port that is associated with a line group does not display the line group as a dependent record.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCee58381

CSCee60011

Cisco Unity subscriber information does not display for a recalled call forward busy transfer.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCee60011

CSCee61962

The IPMA wizard can run without installing BAT.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCee61962

CSCee62378

Incorrect RedirectionIDName displays on the redirected call.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCee62378

CSCee65806

Incorrect state displays in existing call event for a connected call.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCee65806

CSCee66489

RTP events do not get identified as TAPI Call DevSpecific events.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCee66489

CSCee67314

Services cannot be activated from subscriber servers.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCee67314

CSCee67395

Route filter deletion from the subscriber server Find/List Route Filter results window displays an incorrect error message when the publisher server is down.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCee67395

CSCee68493

Conference call detail records do not get retrieved from the CDR Analysis and Reporting (CAR) tool.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCee68493

CSCee69564

When Call Forward All is removed via softkey, dialtone plays to the headset on the Cisco IP Phone 7960.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCee69564

CSCee69888

MWI does not illuminate when leaving a message.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCee69888

CSCee70066

Shared line loses call count when MLPP is set to on.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCee70066

CSCee70109

Music on hold fails on the phones.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCee70109

CSCee70737

MLPP domain field should not allow more than six hex characters in the phone configuration window.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCee70737

CSCee72640

Cisco CallManager does not route calls to the hunt group that is configured with the longest idle time.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCee72640

CSCee77385

When Extension Mobility and NAT are used between an IP phone and Cisco CallManager, the login request times out because the Extension Mobility service sends the inside IP address instead of the hostname.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCee77385

CSCee78349

Cisco CallManager upgrade from 3.3(3)SR4 to 4.0(1) fails because of a SQL database migration failure.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCee78349

CSCee78501

In certain configurations, a memory leak may occur that involves the risDC.exe process and the regsvc.exe process.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCee78501

CSCee81959

The "Hold Type" service parameter does not function in Cisco CallManager 4.0.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCee81959

CSCee84479

The addPhone request fails unexpectedly with an "Internal Error" Simple Object Access Protocol (SOAP) fault.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCee84479

CSCef14152

Cisco CallManager service terminates unexpectedly after updating the encryption certificates.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCef14152

CSCef19262

CalledPartyName shows as null on calls that are made through an ICT.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCef19262

CSCef20669

C2691 T1 CAS channels are undefined, causing T1 CAS calls to fail after upgrade or reload of Cisco CallManager.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCef20669

CSCef22120

Cisco CallManager stops writing data to the log files.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCef22120

CSCef23053

Preemption of lower priority calls does not occur in the PNR (preemption and not reuse) unanswered scenario over a T1 PRI.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCef23053

CSCef25167

The CTL Provider service does not start after BARS version 4.0(2) or 4.0(4) is run to restore data after replacing a Cisco CallManager 4.0(x) server.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCef25167

CSCef26679

Restricted Connected Name ID/Connected Line ID displays when the ConfList softkey is pressed.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCef26679

CSCef27811

The ring settings configured for idle/busy phones (in the line configuration page) do not take effect when the "MLPP Indication Status" enterprise parameter is turned on.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCef27811

CSCef30459

All devices might not register to Cisco CallManager 4.0(x) if there is a large number of route lists (registered devices) and the value of the "Maximum Number of Registered Devices" service parameter is not increased.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCef30459

CSCef31740

The recovery property setting of some Cisco CallManager services gets reset to the default option of Restart the Service after upgrade.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCef31740

CSCef31285

Data restoration fails when BARS is installed as a backup server on a CRS server.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCef31285

CSCef32917

Outbound calls fail for about 70 seconds after Route List/Hunt List fails back from the secondary to the primary Cisco CallManager server before the primary server is able to process calls.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCef32917

CSCef33105

Call transfers made through an ICT do not complete successfully.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCef33105

CSCef35814

LineDevStatus > dwLineFeatures do not contain makecall | devspecific line features for a media terminating route point.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCef35814

CSCef36160

CDR entries include incorrect calling party information after a conference call.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCef36160

CSCin68056

Inconsistent display of Call Park information occurs.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCin68056

CSCin69640

Called number transformations do not work when a partially-matching number exists in the prefix digit or the Called Number Transformation Mask field.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCin69640

CSCin72126

Calls that originate from the console use the first physical line from the assistant phone.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCin72126

CSCin72130

Dial from console does not work if the focus is not on lines.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCin72130

CSCin72313

TransferVM and ImmDiv softkeys do not work after barging on shared manager/assistant line.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCin72313

CSCin72385

Calls do not roll over to IPMA first assistant after Ring No Answer timeout on last assistant.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCin72385

CSCin72387

IPMA Assistant does not get call if assistant goes online after call.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCin72387

CSCin72393

Any assistant can modify the manager configuration settings.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCin72393

CSCin72985

Call control on the console displays incorrect status for assistant phone when it is down.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCin72985

CSCin75561

When Call Forward All is used, incorrect forward information displays on the phone.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCin75561

CSCin75716

Call Park reversion timeout does not occur when Meet-me conference is used.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCin75716

CSCin76178

QBE Helper cannot reconnect to CTI Manager after the Ethernet cable is removed and reconnected.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCin76178

CSCuk45896

Administrators cannot modify Cisco CallManager glare properties for a PRI port that is connected to a DMS100.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCuk45896

CSCuk51290

User cannot log in to the Cisco CallManager User Options Log On window if the common name contains special characters.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCuk51290

The following firmware caveats apply to this release.

CSCeb80892

Phone displays a mixture of English and German in the personal address book when the German locale is chosen.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeb80892

CSCec34487

Cisco IP Phone 7970 does not update the call forward icon when an extension mobility user logs in.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec34487

CSCed12269

Cisco IP Phone 7979 takes 1.8 seconds to display call information when the user presses the messages button.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed12269

CSCed13862

Users hear a low pop intermittently on the speaker when they answer a call by using the answer softkey.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed13862

CSCee42575

The Extension Mobility service cannot be accessed via the line button on the phone.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCee42575

CSCee69956

Perfmon on FE channel resets to "2" after Cisco CallManager restarts when out of service mode is applied.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCee69956

Note For complete Cisco IP Phone firmware release note information, refer to the applicable firmware release notes for your specific model IP phone at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_ipphon/english/.

Documentation Updates

This section provides documentation changes that were unavailable when the Cisco CallManager release 4.0(2) documentation suite was released.

This section contains the following types of updates:

•Errors

•Changes

•Omissions

Errors

This section includes errors that the Cisco CallManager Documentation suite contains.

•Deleting a Conference Device

•Deleting a Music On Hold Server

•Deleting a Media Termination Point

•System Requirements for Barge and Privacy

•Configuring Maximum Calls and Busy Trigger Settings for Shared Line Appearances

•User Configuration Settings

•Cisco CallManager Service Activation/Deactivation

•Cisco IP Phone Support

•SIP/UDP Port Configuration

•Route Pattern Configuration Fields

•Cisco IP Phone Configuration Fields

•Translation Pattern Configuration

•Calling Search Space Configuration

•Partition Field Configuration

•Configuring Digits in Configuration Fields

•Cisco Call Back Synchronous Request Timeout Configuration

•Cisco CallManager Dialed Number Analyzer Private Phrase Requirement

•Cisco CallManager Extension Mobility Logout

•Using Attendant Console and Shared Lines

•Date/Time Configuration Changes

•Adding and Deleting Users by Using Cisco CallManager Administration

Deleting a Conference Device

The Conference Bridge Configuration chapter in the Cisco CallManager Administration Guide contains incorrect information about deleting the conference device that contains a Media Resource Group.

This following information describes how to delete a Conference Device.

Before You Begin

You cannot delete the last device that is in a Media Resource Group. To find out which media resource groups are using the conference device, click the Dependency Records link from the Conference Bridge Configuration window. If the dependency records are not enabled for the system, the dependency records summary window displays a message. For more information about dependency records, see "Appendix A" in the Cisco CallManager Administration Guide.

If you try to delete a conference device that is in use, Cisco CallManager displays a warning message. If you try to delete the last device, Cisco CallManager displays a second message, and the device will not get deleted.

Before deleting a conference bridge that is currently in use and is the last device in the Media Resource Group, you must perform either or both of the following tasks:

•Assign a different conference bridge to the media resource groups that are using the conference bridge that you want to delete

•Delete the media resource groups that are using the conference bridge that you want to delete.

Procedure

Step 1 Locate the conference bridge by using the procedure that is detailed in the "Conference Bridge Configuration" chapter in the Cisco CallManager Administration Guide.

Step 2 Click the conference bridge that you want to delete.

Step 3 Click Delete.

A message displays the following warning:

You are about to permanently delete this Conference Bridge. This action cannot be undone.

Continue?

Step 4 To delete the conference device, click OK.

If this is the last device in the Media Resource Group, a second message displays, and you cannot delete the conference bridge.

Step 5 Click OK.

Deleting a Music On Hold Server

The Music On Hold chapter in the Cisco CallManager Features and Services Guide contains incorrect information about deleting the Music On Hold Server that contains a Media Resource Group.

Perform the following procedure to delete an existing Music On Hold server.

Before You Begin

You cannot delete the last device that is in a Media Resource Group. To find out which media resource groups are using the Music On Hold server, click the Dependency Records link from the Music On Hold Server Configuration window. For more information about dependency records, see the Cisco CallManager Administration Guide.

If you try to delete a Music On Hold server that is in use, Cisco CallManager displays a warning message. If you try to delete the last device, Cisco CallManager displays a second message, and the device will not get deleted.

Before deleting a Music On Hold server that is currently in use and is the last device in the Media Resource Group, you must perform either or both of the following tasks:

•Assign a different Music On Hold server to the media resource groups that are using the Music On Hold server that you want to delete.

•Delete the media resource groups that are using the Music On Hold server that you want to delete.

Procedure

Step 1 Find the music on hold server by using the procedure in the Cisco CallManager Features and Services Guide.

Step 2 Click the Music On Hold server that you want to delete.

The Music On Hold Server title displays the name of the chosen Music On Hold server.

Step 3 Click the Delete button.

A message displays the following warning:

You are about to permanently delete this Music On Hold Server. This action cannot be undone.

Continue?

Step 4 To delete the Music On Hold server, click OK.

If this is the last device in the Media Resource Group, a second message displays, and you cannot delete the Music On Hold server.

Step 5 Click OK.

Deleting a Media Termination Point

The Media Termination Point chapter in the Cisco CallManager Administration Guide contains incorrect information about deleting a Media Termination Point that contains a Media Resource Group.

Follow this procedure to delete a Media Termination Point (MTP).

Before You Begin

You cannot delete the last device that is in a Media Resource Group. To find out which media resource groups are using the media termination point, click the Dependency Records link from the Media Termination Point Configuration window. If the dependency records are not enabled for the system, the dependency records summary window displays a message. For more information about dependency records, see the Cisco CallManager Administration Guide.

If you try to delete a media termination point that is in use, Cisco CallManager displays a message. If you try to delete the last device, Cisco CallManager displays a second message, and the device will not get deleted.

Before deleting a media termination point that is currently in use and is the last device in the Media Resource Group, you must perform either or both of the following tasks.

•Assign a different media termination point to the media resource groups that are using the media termination point that you want to delete.

•Delete the media resource groups that are using the media termination point that you want to delete.

Procedure

Step 1 Locate the media termination point by using the procedure in the Cisco CallManager Administration Guide.

Step 2 Click the media termination point that you want to delete.

Step 3 Click Delete.

A message displays the following warning:

You are about to permanently delete this Media Termination Point. This action cannot be undone.

Continue?

Step 4 To delete the media termination point, click OK.

If this is the last device in the Media Resource Group, a second message displays, and you cannot delete the media termination point.

Step 5 Click OK.

System Requirements for Barge and Privacy

The Barge and Privacy Release chapter of the Cisco CallManager Features and Services Guide contains incorrect information about the Cisco IP Phone model 7905.

Barge and Privacy require the following software component to operate:

•Cisco CallManager 4.0 or later

The following phones support Barge by using the Barge or cBarge softkey in any Cisco CallManager softkey template:

•Cisco IP Phones (models 7920, 7940, 7960, 7970)

Note Cisco IP Phone models 7905 and 7912 support cBarge only.

The following phones support Privacy with the Privacy button on the phone button template:

•Cisco IP Phones (models 7905, 7912, 7940, 7960, 7970)

The following phones support the built-in conference bridge capability:

•Cisco IP Phones (models 7940, 7960, 7970)

Note If the phone does not support a Privacy button, by default, the privacy for that phone remains Off (all devices sharing a line with that phone will display the phone information).

Configuring Maximum Calls and Busy Trigger Settings for Shared Line Appearances

The Cisco IP Phones chapter of the Cisco CallManager System Guide contains incorrect information about the settings for busy trigger and maximum number of calls.

A shared line phone should not be able to interact with the call that it rejects, due to the limitation of the maximum number of calls per directory number (DN) or for other reasons.

For example, AA and AB share the same DN. AB and AA have the maximum number of calls set to 1 and 2, respectively. When C and D call the share line DN, AB answers these two calls. AA can only interact with the first call, as it rejects the second call due to its own maximum number of calls per DN limitation.

Note For this reason, Cisco recommends that the same value be configured for the maximum number of calls for all shared-line MCID devices. For N number of devices sharing the same line, ensure both Maximum Calls setting and Busy Trigger setting are set to N. This allows each shared line user to receive at least one call.

The shared line phone should not interact with the call that it does not receive (because the Line Control does not maintain call information). So, a newly registered device will not recognize any existing calls on that line. The newly registered device cannot resume any held call if the call started before this device was registered with the Line Control. For example, AA and AB share the same line, AA is powered down (or logged out for the extension mobility user), and AB receives an active call. After phone AA is on and it registers with Cisco CallManager, AA should not see the existing active call in this line.

Note If shared-line phones calls should interact with each other, Cisco recommends that you set the maximum number of calls for all shared-line MCID devices to 2*N, where N is the number of shared-line devices.

User Configuration Settings

The Adding A New User chapter in the Cisco CallManager Administration Guide contains incorrect information about the types of characters that are allowed in the User First Name, User Last Name, and User Password fields.

Table 3 describes the user configuration settings. (See Table 11 for additional user configuration settings that are not included in the documentation.)

Table 3 User Configuration Settings

Field

Description

First Name

Enter the user first name. You may use the following special characters: =, +, <, >, #, ;, \, , "", and blank spaces.

Last Name

Enter the user last name. You may use the following special characters: =, +, <, >, #, ;, \, , "", and blank spaces.

UserID

Enter the user identification name. Cisco CallManager does not permit modifying the user ID after it is created.

Cisco CallManager does not support the use of the following special characters: =, +, <, >, #, ;, \, , "", and blank spaces.

User Password

Enter five or more alphanumeric or special characters for the user password. You may use the following special characters: =, +, <, >, #, ;, \, , "", and blank spaces.

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. You may use the following special characters: (, ), and - .

Manager UserID

Enter the name of the user manager ID. The manager user ID that you enter must already exist in the directory as a user.

Department

Enter the user department information (for example, the department number or name).

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 the default device profile specifies.

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.

Enable Calling Party Number Modification

Choose this field to allow an application such as Cisco Emergency Responder (CER) to change the calling number when it initiates a feature request from an application programming interface (API). Refer to the Cisco Emergency Responder documentation for more information.

Associated PC

This field, which is required for Cisco SoftPhone and Cisco CallManager Attendant Console users, displays after the user is added.

Primary Extension

This field displays after the user is added and represents the primary directory number for the user. You choose no primary line when you associate devices to the user. Users can have multiple lines on their phones.

If the system is configured for Unity Integration, the Create Voice Mailbox link displays.

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 capability is enabled, this field displays True; if disabled, this field displays False.

Controlled Device Profiles

This field displays after the user is added. This field displays a list of controlled device profiles that are associated with a user who is configured for Cisco CallManager Extension Mobility.

View page in

From the drop-down selection box, choose the language for the User Configuration window; this changes the language that displays only for the current session.

Note Upon your next log on, the User Configuration window displays in the default language. To choose the language that you wish to use, download and install the appropriate Locale Installer.

Cisco CallManager Service Activation/Deactivation

The Cisco CallManager Configuration chapter in the Cisco CallManager Administration Guide contains incorrect information about the activation/deactivation of the Cisco CallManager service.

The following requirement applies to Cisco CallManager service activation and deactivation:

Cisco CallManager Service Activation

Before adding a new Cisco CallManager to the database, activate the Cisco CallManager service as described in the Cisco CallManager Serviceability Administration Guide.

For more information about Service Activation, refer to the Cisco CallManager Serviceability System Guide and the Cisco CallManager Serviceability Administration Guide.

Cisco IP Phone Support

The Cisco IP Phone Services chapter in the Cisco CallManager System Guide incorrectly states that Cisco IP Phone services support the Cisco IP Phone 7902.

The statement should read "Cisco IP Phone services support Cisco IP Phone Models 7970, 7960, 7940, 7905, and 7912."

SIP/UDP Port Configuration

The Trunk Configuration chapter of the Cisco CallManager Administration Guide contains incorrect information about the configuration of SIP trunk incoming and outgoing ports.

Incoming Port Configuration

Each SIP trunk requires a separate incoming UDP or TCP port but does not require a separate outgoing UDP or TCP port.

Table 4 Trunk Configuration Settings for SIP Trunks

Field

Description

Incoming Port

Choose the incoming port. The value that you enter can be any unique port from 1024 - 65535. The default port value for incoming TCP and UDP SIP messages specifies 5060.

Outgoing Transport Type

Indicate the preferred outgoing transport mode of UDP or TCP.

Route Pattern Configuration Fields

The Route Pattern Configuration chapter in the Cisco CallManager Administration Guide contains incorrect information about the following Route Pattern Configuration fields: Provide Outside Dial Tone, Allow Overlap Sending, and Urgent Priority.

Table 5 describes these fields.

Table 5 Route Pattern Configuration Fields

Field

Description

Provide Outside Dial Tone

Outside dial tone indicates that Cisco CallManager routes the call off the local network. Check this check box for each route pattern that you consider to be off-net (also provides outside dial tone to the calling device). To route the call in the network, leave the check box unchecked.

Allow Overlap Sending

With overlap sending enabled, when Cisco CallManager passes a call to the PSTN, it relies on overlap sending in the PSTN to determine how many digits to collect and where to route the call. Check this check box for each route pattern that you consider to be assigned to a gateway or route list that routes the calls to a PSTN that supports overlap sending.

Urgent Priority

If the dial plan contains overlapping route patterns, Cisco CallManager would not route the call until the interdigit timer expires (even if it is possible to dial a sequence of digits to choose a current match). Check this check box to interrupt the interdigit timer when Cisco CallManager must route a call immediately.

Cisco IP Phone Configuration Fields

Log Out Time Field

The Cisco IP Phone Configuration chapter in the Cisco CallManager Administration Guide contains incorrect information about the Log Out Time field for Extension Mobility.

Table 6 describes this field.

Table 6 Phone Configuration Log Out Time Field

Field

Description

Log Out Time

This field remains blank until a user logs in. When a user logs in to the device by using Cisco CallManager Extension Mobility, the time at which the system will log out the user displays in this field.

Display Internal Caller ID Field

The Cisco IP Phone Configuration chapter in the Cisco CallManager Administration Guide contains incorrect information about the Display Internal Caller ID field.

Table 7 describes this field.

Table 7 Phone Configuration Display Internal Caller ID Field

Field

Description

Display (Internal Caller ID)

Leave this field blank to have the system display the extension.

Use a maximum of 30 alphanumeric characters (typically, the user name or the directory number; if the directory number is used, the person that is receiving the call may not see the proper identity of the caller).

This setting applies only to the current device unless you check the check box at the right and click the Propagate selected button. (The check box at the right displays only if other devices share this directory number.)

Malicious Call Identification

The Cisco CallManager Features and Services Guide identifies a PRI gateway that uses the MGCP PRI backhaul interface for T1 (NI2) as a gateway that supports MCID.

Nonstandard NI-2 PRI trunk interfaces do not support the Cisco CallManager MCID feature.

Translation Pattern Configuration

The Translation Pattern Configuration chapter in the Cisco CallManager Administration Guide contains incorrect information about the Allow Overlap Sending check box.

The Allow Overlap Sending check box, which appeared under Pattern Definition on the Translation Pattern Configuration window, no longer displays because it is no longer valid.

Calling Search Space Configuration

The Cisco CallManager Administration Guide erroneously mentions that the Restart button exists in the Calling Search Space window.

Several chapters in the Cisco CallManager Administration Guide contain incorrect information about configuring the Calling Search Space (CSS) field. The following Cisco CallManager Administration windows contain the CSS field and are updated:

•Message Waiting Configuration

•Device Pool Configuration

•Translation Pattern Configuration

•Cisco CallManager Attendant Console Configuration

•Cisco Voice-Mail Port Configuration

•Cisco Voice-Mail Port Wizard Configuration

•Cisco Voice-Mail Pilot Configuration

•CTI Route Point Configuration

•Gateway Configuration (FXS/FXO, E1/T1 PRI, T1-CAS, H.323, Analog Access)

•Phone Configuration

•Directory Number Configuration

•Trunk Configuration (H.225, Intercluster, SIP)

Table 8 shows the information that the Calling Search Space field now includes for the preceding configuration windows.

Table 8 Calling Search Space Field

Field

Description

Calling Search Space

From the drop-down list box, choose the appropriate calling search space for the <appropriate configuration window>. The calling search space specifies the collection of route partitions that are searched to determine how to route a collected (originating) number.

You can configure the number of calling search spaces that display in this drop-down list box by using the Max List Box Items enterprise parameter. If more calling search spaces exist than the number that are configured in the Max List Box Items enterprise parameter, the ellipsis button (...) displays next to the drop-down list box.

1. Click the ... button to display the Select Calling Search Space window.

2. Enter a partial calling search space name in the List items where Name contains field.

3. Click the desired calling search space name in the list of calling search spaces that displays in the Select item to use box.

4. Click OK.

Note To set the maximum list box items, choose System > Enterprise Parameters and choose CCMAdmin Parameters.

Partition Field Configuration

The Cisco CallManager Administration Guide incorrectly states that the Partition drop-down list box only displays the ellipsis when there are 250 partitions; however, this number is configurable in enterprise parameters, so the statement is untrue. This affects the following Cisco CallManager Administration windows that have the partition field:

•Pilot Point Configuration

•Hunt Group Configuration

•Cisco IP Phone Configuration

•Directory Number Configuration

•Translation Pattern Configuration

•Call Pickup Configuration

•Call Park Configuration

•Meet-Me Number/Pattern Configuration

•Message Waiting Configuration

•Cisco Voice-Mail Port Configuration

•Cisco Voice-Mail Port Wizard Configuration

•Line Group Configuration

Table 9 shows the information that is now included in the Partition field for the preceding configuration windows.

Table 9 Partition Field Configuration

Field

Description

Partition

You can configure the number of partitions that display in this drop-down list box by using the Max List Box Items enterprise parameter. If more partitions exist than the Max List Box Items enterprise parameter specifies, the ellipsis button (. . .) displays next to the drop-down list box.

1. Click the . . . button to display the Select Partition window.

2. Enter a partial partition name in the List items where Name contains field.

3. Click the desired partition name in the list of partitions that displays in the Select item to use box.

4. Click OK.

Note To set the maximum list box items, choose System > Enterprise Parameters and choose CCMAdmin Parameters.

Configuring Digits in Configuration Fields

The Cisco CallManager Administration Guide contains incorrect information about the number of digits in some of the configuration fields.

•The Directory Number Configuration field External Phone Number Mask should be 24 digits.

The Cisco CallManager System Guide contains incorrect information about the number of digits in the Prefix Digits fields.

•For calling party or called party number transformation settings, Prefix Digits (Outgoing Calls) can contain up to 50 digits on route patterns or up to 24 digits on DNs.

Cisco Call Back Synchronous Request Timeout Configuration

The Cisco Call Back chapter in the Cisco CallManager Features and Services Guide contains incorrect information about the Synchronous Request Timeout service parameter. The following information should have been included:

•Synchronous Request Time Out—Default specifies 15000. This parameter specifies the wait time of the Cisco Extended Functions service after a synchronous request is issued. If this requested timeout changes, restart the Cisco Extended Functions service.

Cisco CallManager Dialed Number Analyzer Private Phrase Requirement

The Installing Cisco CallManager Dialed Number Analyzer chapter in the Cisco CallManager Dialed Number Analyzer Guide contains incorrect information about the Private Phrase Requirement in step 6.

Procedure

Step 1 Access Cisco CallManager and choose Application > Install Plugins.

The Install Plug-ins window displays.

Step 2 Locate the Dialed Number Analyzer Plugin.

Step 3 Click the executable icon for Dialed Number Analyzer Plugin to launch the InstallShield Wizard.

Step 4 Click Open. The InstallShield Wizard for Cisco Dialed Number Analyzer window displays.

Step 5 At the Welcome to the InstallShield Wizard for Cisco Dialed Number Analyzer window, click Next.

The Enter Private Phrase window displays.

Step 6 In the Enter Private Phrase window, enter the private phrase for this cluster.

Step 7 Click Next.

If the private phrase is incorrect, a message displays. Return to Step 6. If the private phrase is correct, the Ready to Install the Program window displays.

Step 8 At the Ready to Install the Program window, click Install.

Step 9 At the InstallShield Wizard Completed window, click Finish.

The tool installs the Cisco Dialed Number Analyzer service on the machine.

Cisco CallManager Extension Mobility Logout

The 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.

The Cisco CallManager System Guide also incorrectly states that the Cisco CallManager Extension Mobility feature requires that the Cisco CallManager Extension Mobility Logout service be run on servers that have devices that are registered to the feature.

In fact, the Cisco Extension Mobility Logout service does not need to be running on the same machine where the devices are registered. The Cisco Extension Mobility application accesses the server that is configured in the directory. The Cisco Extension Mobility Logout server needs to run on the server that the Cisco Extension Mobility application accesses.

Using Attendant Console and Shared Lines

The Cisco CallManager Attendant Console chapter in the Cisco CallManager System Guide contains incorrect information about shared lines. The following information provides an update:

•Administrators can use a shared-line appearance for hunt group members.

•Attendant phones can share lines with other attendants or non-attendants.

•Calls to a pilot point route to a shared-line phone only when the shared line is not in use on another remote phone.

•Administrators cannot use a shared-line appearance for pilot points.

Date/Time Configuration Changes

The Cisco CallManager Administration Guide incorrectly states that the "local time zone of CallManager" option exists in the Date/Time Configuration window, Time Zone parameter. However, this option is not available in the drop-down box in Cisco CallManager 4.0(2).

If you upgrade from a compatible Cisco CallManager release and you use "local time zone of CallManager" in the configuration, the Cisco CallManager database determines the appropriate time zone for the publisher database server and then displays that time zone as replacement for the CallManager time zone.

If you perform a fresh installation of Cisco CallManager, the default setting for Time Zone in the Date/Time Group equals GMT (Monrovia, Casablanca).

Adding and Deleting Users by Using Cisco CallManager Administration

The Installing the Cisco Customer Directory Configuration Plugin for Cisco CallManager Release 4.0(1) does not contain all of the steps that are required for adding and deleting users by using Cisco CallManager Administration. The following information provides an update to this procedure.

Procedure

Step 1 Browse to C:\dcdsrvr\config, and open the file, UMDirectoryConfiguration.ini, in Notepad.

Note You must open the file in Notepad. Opening the file in another text editor application may corrupt the file.

Step 2 In the UMDirectoryConfiguration.ini file, locate the key, UserDirAccess.

Step 3 Change the UserDirectAccess value to true.

Step 4 In Notepad, choose File > Save to save the file.

Step 5 Close the UMDirectoryConfiguration.ini file.

Step 6 Choose Start > Run.

Step 7 Enter regedit in the Open field and click OK.

Step 8 Browse to \\HKEY_LOCAL_MACHINE\Software\Cisco Systems, Inc.\Directory Configuration within the registry.

Step 9 In the right pane, double-click the DirAccess registry key.

Step 10 Delete the false registry entry and enter true as the new registry entry.

Step 11 Restart the IIS Admin Service and its dependent services by choosing Start > Programs > Administrative Tools> Services.

Step 12 Right-click IIS Admin Service and then choose Restart.

A dialog box prompts you to restart dependent services. These services may differ depending on your configuration.

Step 13 Click Yes.

Step 14 Restart the dependent services.

You may now add, update, or delete users within Cisco CallManager Administration. Refer to the latest version of the Cisco CallManager Administration Guide for information on how to perform these tasks.

Changes

This section contains changes that have occurred since the original release of the Cisco CallManager release 4.0 documentation. These changes do not currently appear in the current documentation or the online help for the Cisco CallManager application.

•IPMA Clusterwide Parameters for Softkey Templates

•Ad Hoc Conference Limitations

•Meet-Me Conference Limitations

IPMA Clusterwide Parameters for Softkey Templates

The Cisco IPMA for Shared Line Mode chapter in the Cisco CallManager Features and Services Guide is updated to include the following information about the clusterwide parameters for softkey templates.

•Clusterwide Parameters for Softkey Templates

–Manager Softkey Template for Proxy Mode—This service parameter does not apply to shared line support.

Ad Hoc Conference Limitations

Cisco CallManager supports a maximum of 100 simultaneous ad hoc conferences for each Cisco CallManager server.

Meet-Me Conference Limitations

Cisco CallManager supports a maximum of 100 simultaneous meet-me conferences for each Cisco CallManager server.

Omissions

This section lists new and additional information that is not included in the current Cisco CallManager documentation.

•CTI Monitored Lines

•Quality Report Tool Configuration Settings

•User Settings in Cisco CallManager Administration

•SRST Fallback Algorithm Enhancements

•Defining the Quality of Service (QoS) Values

•User Settings in Cisco CallManager Administration

•Updated BAT Field Descriptions

•Using Annunciator with Conference Bridges

•Static Digit Analysis

•Q.SIG Support with JTAPI and TAPI

CTI Monitored Lines

To calculate the number of CTI monitored lines in a system, use the following formula:

number of pilot point DNs + (number of clients open * number of directory numbers per phone) + (number of parked directory numbers * number of open clients) = CTI Monitored Lines

Quality Report Tool Configuration Settings

Cisco CallManager 3.3 introduced 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 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 choose 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 choose 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 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 ranges 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 ranges 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 ranges 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.

SRST Fallback Algorithm Enhancements

The Device Pool Configuration chapter in the Cisco CallManager Administration Guide and the System-Level Configuration Settings chapter in the Cisco CallManager System Guide do not include the following information about the Connection Monitor Duration setting.

Table 10 shows the updated information.

Table 10 Device Pool Configuration Settings

Field

Description

Connection Monitor Duration

This setting defines the length of time that the IP phone monitors its connection to Cisco CallManager before it unregisters from SRST and reregisters to Cisco CallManager.

The default value, which specifies 120 seconds, resides in the Connection Monitor Duration enterprise parameter.

Change this setting if you need to disable the connection monitor (by changing the value to zero) or if you want to extend the connection monitor time.

Note When you change the value of the connection monitor duration, it applies only to the device pool that is being updated. All other device pools use the value in their own connection monitor duration fields or use the value that is configured in the enterprise parameter.

For more information, refer to the Cisco CallManager System Guide.

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, you must enter these values exactly as shown; the system does not support other forms.

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 11 provides a description of the user settings that are not included in the documentation. (See Table 3 for a complete listing of user configuration settings.)

Table 11 User Settings in Cisco CallManager Administration

Field

Description

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.

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.

Updated BAT Field Descriptions

The Bulk Administration Tool User Guide does not include information about some of the fields that are available in the Bulk Administration Tool.

The Bulk Administration Tool User Guide does not include the following information for the device security mode and the web access fields in the BAT Update Phones Page.

Table 12 provides a description of these fields.

Table 12 Additional Configuration Fields for the BAT Update Phones Page

Field

Description

Device Security Mode

From the drop-down list box, choose the mode that you want to set for the device:

•Use System Default—The phone uses the value that you specified for the enterprise parameter, Device Security Mode.

•Non-secure—No security features exist for the phone. A TCP connection opens to Cisco CallManager.

•Authenticated—Cisco CallManager provides integrity and authentication for the phone. A TLS connection that is using NULL/SHA opens.

•Encrypted—Cisco CallManager provides integrity, authentication, and encryption for the phone. A TLS connection that is using AES128/SHA opens

Note This field displays only if the phone model supports authentication or encryption.

Web Access

Choose Enabled or Disabled to control whether the user has Web Access.

Disabling the web server functionality for the phone blocks access to the phone internal web pages, which provide statistics and configuration information. Features, such as Cisco Quality Report Tool, do not function properly without access to the phone web pages. Disabling the web server also affects any serviceability application, such as CiscoWorks, that relies on web access.

Note Phone users cannot access the Cisco User Option Pages if you disable this option.

The Bulk Administration Tool User Guide does not include the following information about the field descriptions for phones and for adding lines in the BAT Spreadsheet.

Table 13 shows the phone field descriptions in the BAT spreadsheet.

Table 13 Phone Field Descriptions

Field

Description

Display

Enter the text that you want to display on the called party's phone display, such as the user name or the phone location. The default language specifies English.

Note If this field is blank, the system uses the value that is entered in the Directory Number field.

Table 14 shows the field descriptions for adding lines by using the BAT spreadsheet.

Table 14 Field Descriptions for Adding Lines

Field

Description

Display

Enter the text that you want to display on the called party's phone display, such as the user name or the phone location. The default language specifies English.

Note If this field is blank the system uses the value that is entered in the Directory Number field.

Fax and Modem Connectivity

The Understanding Cisco CallManager Voice Gateways chapter in the Cisco CallManager System Guide omitted the following information about fax and modem connectivity for the Cisco VG248 Gateway.

Fax and Modem Connectivity

The Cisco VG248 supports legacy fax machines and modems. When fax machines are used, the Cisco VG248 uses either the Cisco fax relay or pass-through/up speed technology to transfer faxes across the network with high reliability.

You can connect any modem to the Cisco VG248 by using pass-through mode.

Using Annunciator with Conference Bridges

Cisco CallManager System Guide does not include the following information about annunciator support.

Cisco CallManager provides annunciator resource support to a conference bridge under the following circumstances:

•If the media resource group list that contains the annunciator is assigned to the device pool where the conference bridge exists.

•If the annunciator is configured as the default media resource, which makes it available to all devices in the cluster.

Note Cisco CallManager does not provide annunciator resource support for a conference bridge if the media resource group list is assigned directly to the device that controls the conference.

Static Digit Analysis

The Cisco CallManager documentation does not include information about static digit analysis.

In Cisco CallManager 4.0, the new digit analysis process builds a static digit analysis engine with the patterns that are configured in the database during system initialization. This digit analysis engine reduces the propagation of patterns within a cluster of Cisco CallManagers and makes Cisco CallManager more scalable.

In releases before the Cisco CallManager 4.0 release, the individual device control process read pattern information from the database and dynamically registered the patterns to the digit analysis process to build its digit analysis engine. Each pattern had a mapping to its control process ID in the digit analysis engine. The control process ID of a pattern got changed dynamically if its associated device was reset or if a Cisco CallManager server restarted. If a change to the control process ID took place, the digit analysis engine had to be changed dynamically, and its contents required propagation to other Cisco CallManager servers. During call processing, the digit analysis engine returned the control process ID of a matched pattern.

In the current release, the digit analysis process reads the pattern information directly from the database to build the static digit analysis engine during Cisco CallManager initialization. With the static digit analysis engine, each pattern has a mapping to its callable endpoint name, which is a NumPlanPkID of the pattern in the database, a unique identifier to a configured pattern in Cisco CallManager. The static digit analysis engine no longer holds the control process ID of a pattern.

Static digit analysis integrates with the changes to the device manager to support all existing functions and features. The device manager includes a table where a NumPlanPkID shows a one-to-one mapping to the control process ID of a pattern. When processing a call, digit analysis asks the device manager to get the control process ID for a matched pattern.

Feature Description

The current Cisco CallManager system includes these pattern types: Call Park, Call Forward, Meet-me Conference, Device, Translation, Call Pickup Group, Route, and Message Waiting. The Device, Translation, and Route pattern types represent static patterns. The digit analysis process reads these patterns directly and inserts them into the static digit analysis engine during the initialization of a Cisco CallManager. Other pattern types (Call Park, Call Forward, Meet-me Conference, Call Pickup Group, and Message Waiting), which are intercept patterns, remain dynamic patterns. Their individual control process reads the pattern information from the database and then asks the digit analysis process to insert the pattern into the static digit analysis engine via registration messages.

All static patterns remain unchanged until their records are changed in the database. Static patterns do not require propagation, because the database change notification is broadcast to the servers within a cluster. Dynamic patterns still use the existing propagating and updating mechanism to update the static digit analysis engines.

Regardless of its pattern type, each static pattern in the static digit analysis engine has a mapping to its PkID in the NumPlan table in the database. When a device registers its patterns to the device manager, the same PkID gets saved and mapped to its control process ID in the device manager. A new interface between the digit analysis and device manager retrieves the control process ID when a matched pattern is found in the static digit analysis engine during call processing.

Caveat 1

A potential loss of change notification exists in the current Cisco CallManager release. This loss could cause a device that is registered with Cisco CallManager to become unreachable by other devices. The following paragraphs provide troubleshooting for this potential problem.

The most common cause for this problem occurs when the DN that is assigned to the device belongs to a partition that the calling search space of other devices does not contain. If the calling search space of other devices does contain the partition for that DN, other reasons may apply. For example, the DN was changed only for that device, and the change notification from the database to Cisco CallManager was lost. In release 4.0(2) of Cisco CallManager, resetting the device may not resolve the problem.

To resolve this problem in Cisco CallManager release 4.0(2), remove the DN and re-add the DN to the system. Remove the DN from its device on the Directory Number Configuration window and on the Route Plan Report window. After you remove the DN, add it back in with the same partition, pattern, and other configuration information. The problem should be resolved after you re-add the new DN to Cisco CallManager.

The same workaround applies to route patterns and translation patterns if similar problems exist.

Tip Be sure to document all configurations before removing the patterns.

Caveat 2

Static digit analysis disables the configuration of several applications. These applications rely on the provision of duplicate patterns in the same calling search space. For example, the CTI application may be pattern 5000 in partition A, and a particular phone may be pattern 5000 in partition B. In releases before Cisco CallManager 4.0, if the CTI route point was down, the phone will ring. With static digit analysis, however, the caller receives a busy tone. This limitation implies that the application failure cannot be handled.

Administrators would normally use Call Forward No Answer and Call Forward on failure to handle application failure, but when the pattern on the CTI route point is 5XXX, the administrator cannot configure a forward destination of 5XXX. To resolve this limitation, you can now perform configuration of X characters in Call Forward destinations.

The following example demonstrates the functionality of digit analysis prior to release 4.0(2) (with dynamic digit analysis) and in Release 4.0(2) (with static digit analysis) for the IPMA application.

IPMA Example with Digit Analysis Prior to Release 4.0

Given the following configuration
Partitions: IPMA, Managers, Everyone
CSS-I-E: IPMA:Everyone
CSS-M-E: Managers:Everyone
Line-1/CSS-I-E: EveryOne/1000
Line-2/CSS-M-E: Manager/1001
CTI RP: IPMA/1XXX
Translation Pattern/CSS-M-E: EveryOne/1XXX
if the CTI route point (RP) is up, 1000/IPMA:EveryOne calls 1001. The call routes by using the CTI route point IPMA/1XXX.

If the CTI route point is down, 1000/IPMA:EveryOne calls 1001. The call goes through the translation pattern Everyone/1xxx, and the call reaches Manager/1001 after the translation and achieves the goal of the IPMA application.

IPMA Example with Static Digit Analysis in Release 4.0(2)

Given an identical configuration, in Cisco CallManager 4.0, you must make the following modification: configure 1xxx as a CFNA mask and CSS-E as a CFNA calling search space for the CTI route point to handle the CTI route point failure case.

In Release 4.0, using static digit analysis, the following processing takes place:

•If the CTI route point (RP) is up, 1000/IPMA:EveryOne calls 1001. The call routes through CTI route point IPMA/1XXX. (Routing does not change from previous releases.)

•If the CTI route point is down, 1000/IPMA:EveryOne calls 1001. The call goes to the CTI route point, and its CFNA is triggered. The forwarding feature routes the call through the translation pattern Everyone/1xxx, and the call reaches Manager/1001 after translation.

Without configuring the CFNA in the CTI route point, the translation pattern never gets matched, and the IPMA application fails.

Q.SIG Support with JTAPI and TAPI

The Cisco JTAPI Developer Guide for Cisco CallManager 4.0(1) and the
Cisco TAPI Developer Guide for Cisco CallManager 4.0(1) do not specifically state that JTAPI and TAPI do not support Q.SIG in Cisco CallManager release 4.0(x).

Although Cisco CallManager release 4.0(x) supports the Q.SIG feature, Q.SIG is not supported by JTAPI or TAPI. Because there is no support provided for Q.SIG by JTAPI or TAPI, call information that is reported by the Q.SIG gateway, for a call connecting through a Q.SIG gateway, may not be reported to the applications.

Cisco Unity Voice-Mail Port Changes

This section describes various voice-mail port configurations in Cisco CallManager. Use the scenarios and procedures that follow to ensure that migration from Cisco CallManager 3.3(x) to Cisco CallManager 4.0(2) properly migrates the voice-mail port settings. This section describes voice-mail port configurations in Cisco CallManager 3.3(x) as well as the expected configuration after migration to Cisco CallManager 4.0(2). This section also describes the voice-messaging system changes that take place after you upgrade your system to Cisco CallManager 4.0(2).

This section contains the following topics:

•Changes After Upgrading to Cisco CallManager 4.0(2)

•Before Upgrading to Cisco CallManager 4.0(2)

•Unity Failover Voice-Mail Port Setup

Changes After Upgrading to Cisco CallManager 4.0(2)

You will need to reconfigure a few items to maintain your original voice-mail port functionality, depending on what type of scenario you have set up. You must also change your setup as described in this section.

Things That May Affect Your Setup

If your last voice-mail port is forwarded to a route pattern (gateway or intercluster trunk [ICT]), this configuration will no longer exist after the upgrade. You will need to add the intercluster trunk or gateway to a route group, then add the route group to the corresponding route/hunt list of the route patterns that are attached to the voice-mail pilot number. The route group represents the last member of the route/hunt list.

Note Cisco does not recommend use of the Broadcast distribution algorithm in conjunction with the implementation of voice-mail ports for Cisco Unity.

Line Group Forwarding and Cisco Unity Failover

If you are using the recommended Cisco Unity failover voice-mail port setup, you need to configure the following values for the line groups that are used for the voice-mail ports:

•No Answer: Skip Remaining members and go directly to next group.

•Busy: Try Next member, but do not go to next group.

•Not Available: Skip Remaining members and go directly to next group.

The descriptions of the various scenarios throughout this document provide specific information about these values.

If your final voice-mail port is configured to go to an operator, and the operator is set up to Call Forward No Answer (CFNA) and Call Forward Busy (CFB) back to the voice-mail pilot, you will no longer be able to CFB or CFNA back to the same voice-messaging system. You can add an additional line group that contains the operator line to the voice-mail hunt list.

After an upgrade, the system places the line group where the failover voice-mail ports reside in the route/hunt list that is associated with the hunt list pilot number. You need to manually select the hunt options on the basis of your original configuration.

Changes That You Will Notice After the Upgrade

After the upgrade from previous versions of Cisco CallManager to Cisco CallManager 4.0(2), you will notice the following changes:

•The Cisco Voice Mail Port Configuration window no longer has forwarding fields.

•Voice-mail ports now use line groups, route/hunt lists, and hunt pilot numbers.The system creates these entities automatically after the upgrade if the database contained an existing voice-mail port setup. You need to select the hunt options on the basis of your original configurations.

•The pilot number now represents a route pattern with the same number as the first voice-mail port, but in a different partition. The partition that is used for the pilot number was originally the partition that associated with the first voice-mail port.

•The system places voice-mail ports in a newly created partition during the upgrade process.

•The system places voice-mail ports that are used for MWI and for outbound calls on their own separate line groups, route/hunt lists, and hunt list pilot numbers.

Before Upgrading to Cisco CallManager 4.0(2)

Perform the following step on the voice-mail ports to ensure proper migration:

1. Important: Remove any call forwarding that is set on voice-mail ports that are used only for outbound calls and message waiting indication.

Unity Failover Voice-Mail Port Setup

Two supported failover configurations exist. The following white paper discusses these failover configurations: Cisco CallManager Port Configuration for Cisco Unity Failover (Cisco Unity Versions 4.0 and 3.1(2) and Later).

This section provides example configurations in Cisco CallManager 3.3(x) and then outlines what each configuration should resemble after an upgrade to Cisco CallManager 4.0(2) occurs. Some manual configuration needs to take place after an upgrade to Cisco CallManager version 4.0(2). This section also outlines these changes.

This section covers the following topics:

•Unity Failover Configuration 1 in Cisco CallManager 3.3(x) (Recommended)

•Unity Failover Configuration 1 After Migration to Cisco CallManager 4.0(2) (Recommended)

•Single Cisco Unity Server with Single Cisco CallManager Cluster

•Single Cisco Unity Server with Single Cisco CallManager Cluster in Cisco CallManager 3.3(x)

•Single Cisco Unity Server with Single Cisco CallManager Cluster After Migration to Cisco CallManager 4.0(2)

Unity Failover Configuration 1 in Cisco CallManager 3.3(x) (Recommended)

In this example, on each server, four ports handle incoming calls, and two ports handle outbound calls and MWI. PhoneCSS contains partition(s) that are assigned to subscriber phones, as well as VMPilotNumberPT. VMRestrictedCSS contains only VMRestrictedPT, which is assigned only to VM ports.

Primary Cisco Unity server VM ports configuration:
Port 1: (Line: 2001) Device Settings - CSS = PhoneCSS
Port 1: (Line: 2001) Directory Number Settings - Partition = VMPilotNumberPT, CSS = 
VMRestrictedCSS
Ports 2 to 6: (Lines: 2002-2006) Device Settings - CSS = PhoneCSS
Ports 2 to 6: (Lines: 2002-2006) Directory Number Settings - Partition = VMRestrictedPT, 
CSS = VMRestrictedCSS
Ports 1 to 6: (Lines: 2001-2006) Call Forwarding Settings on Busy and No Answer CSS = 
VMRestrictedCSS
Line: 2001, CFNA = 3001, CFB = 2002
Line: 2002, CFNA = 3001, CFB = 2003
Line: 2003, CFNA = 3001, CFB = 2004
Line: 2004, CFNA = 3001, CFB = 2001
Line: 2005, CFNA = 2001, CFB = Blank (for outbound calls and MWI)
Line: 2006, CFNA = 2001, CFB = Blank (for outbound calls and MWI)
The following example shows secondary Cisco Unity server VM ports (call does not get sent to operator if all ports are busy or ring no answer [RNA]) configuration:
Ports 1 to 6: (Lines: 3001-3006) Device Settings - CSS = PhoneCSS
Ports 1 to 6: (Lines: 3001-3006) Directory Number Settings - Partition = VMRestrictedPT, 
CSS = VMRestrictedCSS
Ports 1 to 6: (Lines: 3001-3006) Call Forwarding Settings on Busy and No Answer CSS = 
VMRestrictedCSS
Line: 3001, CFNA = 3002, CFB = 3002
Line: 3002, CFNA = 3003, CFB = 3003
Line: 3003, CFNA = 3004, CFB = 3004
Line: 3004, CFNA = 3001, CFB = 3001
Line: 3005, CFNA = 3001, CFB = Blank (for outbound calls and MWI)
Line: 3006, CFNA = 3001, CFB = Blank (for outbound calls and MWI)
The following example shows secondary Cisco Unity server VM ports (call gets sent to operator if all ports are busy or RNA) configuration:
Ports 1 to 6: (Lines: 3001-3006) Device Settings - CSS = PhoneCSS
Ports 1 to 6: (Lines: 3001-3006) Directory Number Settings - Partition = VMRestrictedPT, 
CSS = VMRestrictedCSS
Ports 1 to 6: (Lines: 3001-3006) Call Forwarding Settings on Busy and No Answer CSS = 
VMRestrictedCSS
Line: 3001, CFNA = 3002, CFB = 3002
Line: 3002, CFNA = 3003, CFB = 3003
Line: 3003, CFNA = 3004, CFB = 3004
Line: 3004, CFNA = operator DN, CFB = operator DN
Line: 3005, CFNA = 3001, CFB = Blank  (for outbound calls and MWI)
Line: 3006, CFNA = 3001, CFB = Blank  (for outbound calls and MWI)
Unity Failover Configuration 1 After Migration to Cisco CallManager 4.0(2) (Recommended)

In this example, on each server, four ports handle incoming calls, and two ports handle outbound calls and MWI. PhoneCSS contains partition(s) that are assigned to subscriber phones, as well as VMPilotNumberPT. VMRestrictedCSS contains only VMRestrictedPT, which is assigned only to VM ports. The VMPilotPartition gets created automatically and gets assigned to the voice-mail ports.

The following example shows primary Cisco Unity server VM ports configuration:
Ports 1 to 6: (Lines: 2001-2006) Device Settings - CSS = PhoneCSS
Ports 1 to 6: (Lines: 2001-2006) Directory Number Settings - Partition = VMPilotPartition, 
CSS = VMRestrictedCSS
The following example shows secondary Cisco Unity server VM ports configuration:
Ports 1 to 6: (Lines: 3001-3006) Device Settings - CSS = PhoneCSS
Ports 1 to 6: (Lines: 3001-3006) Directory Number Settings - Partition = VMPilotPartition, 
CSS = VMRestrictedCSS
The following example shows Line Groups (calls not sent to operator if all ports are busy or RNA) configuration:

1. Line Group Name: LG2001 includes 2001-2004, with the following settings:
No Answer: Skip remaining members, and go directly to next group (Because this setting 
is not the default, you must set it manually.)
Busy: Try next member, but do not go to next group (Because this setting is not the 
default, you must set it manually.)
Not Available: Skip remaining members, and go directly to next group (Because this 
setting is not the default, you must set it manually.)
2. Line Group Name: LG3001 includes 3001-3004, with the following settings:
No Answer: Try next member, but do not go to next group
Busy: Try next member, but do not go to next group
Not Available: Try next member, but do not go to next group
Ensure that these values are set manually after the upgrade.

The following example shows Line Groups (calls sent to the operator if all ports are busy or RNA) configuration:

Note Configure only incoming line groups; line groups that dial out remain the same.

1. Line Group Name: LG2001 includes 2001-2004, with the following settings:
No Answer: Skip remaining members, and go directly to next group
Busy: Try next member, but do not go to next group
Not Available: Skip remaining members, and go directly to next group
Ensure that these values are set manually after the upgrade.

2. Line Group Name: LG3001 includes 3001-3004 with the following settings:
No Answer: Try next member, but do not go to next group
Busy: Try next member, but do not go to next group
Not Available: Skip remaining members, and go directly to next group
Ensure that these values are set manually after the upgrade.

3. Line Group Name: Operator includes Operator extension (example 1000):
No Answer: Try next member, but do not go to next group
Busy: Try next member, but do not go to next group
Not Available: Try next member, but do not go to next group
After an upgrade, a hunt list automatically gets configured as follows:
Hunt List Name: HL2001, includes Line Groups LG2001 and LG3001, and operator LG if used, 
in this order.
After an upgrade, a hunt pilot automatically gets configured as follows:
Hunt Pilot: 2001, Partition: VMPilotNumberPT, Hunt List: HL2001
Single Cisco Unity Server with Single Cisco CallManager Cluster

This section outlines the voice-mail port configurations with a single Cisco Unity server and a single Cisco CallManager cluster. The examples describe following configurations:

•Single Cisco Unity Server with Single Cisco CallManager Cluster in Cisco CallManager 3.3(x)

•Single Cisco Unity Server with Single Cisco CallManager Cluster After Migration to Cisco CallManager 4.0(2)

Single Cisco Unity Server with Single Cisco CallManager Cluster in Cisco CallManager 3.3(x)

In this example, voice-mail ports get configured as follows:
Port 1: (Line: 2001) Device Settings - CSS = PhoneCSS
Port 1: (Line: 2001) Directory Number Settings - Partition = VMPilotNumberPT, CSS = 
VMRestrictedCSS
Ports 2 to 6: (Lines: 2002-2006) Device Settings - CSS = PhoneCSS
Ports 2 to 6: (Lines: 2002-2006) Directory Number Settings - Partition = VMRestrictedPT, 
CSS = VMRestrictedCSS
Ports 1 to 6: (Lines: 2001-2006) Call Forwarding Settings on Busy and No Answer CSS = 
VMRestrictedCSS
Line: 2001, CFNA = 2002, CFB = 2002
Line: 2002, CFNA = 2003, CFB = 2003
Line: 2003, CFNA = 2004, CFB = 2004
Line: 2004, CFNA = 2001, CFB = 2001
Line: 2005, CFNA = 2001, CFB = Blank  (for outbound calls and MWI)
Line: 2006, CFNA = 2001, CFB = Blank  (for outbound calls and MWI)
Single Cisco Unity Server with Single Cisco CallManager Cluster After Migration to Cisco CallManager 4.0(2)

In this example, voice-mail ports get configured as follows:
Ports 1 to 6: (Lines: 2001-2006) Device Settings - CSS = PhoneCSS
Ports 1 to 6: (Lines: 2001-2006) Directory Number Settings - Partition = VMPilotPartition, 
CSS = VMRestrictedCSS
Line groups get configured as follows:

Line Group Name: LG2001 includes 2001-2004 with the following settings:
No Answer: Try next member, but do not go to next group
Busy: Try next member, but do not go to next group
Not Available: Try next member, but do not go to next group
Create the following line groups for outbound ports:
LG2005, include 2005 and 2006
Configure these line groups with the following settings:
No Answer: Stop hunting. (Because this setting is not the default, you must set it 
manually.)
Busy: Stop hunting. (Because this setting is not the default, you must set it 
manually.)
Not Available: Stop hunting. (Because this setting is not the default, you must set it 
manually.)
Hunt lists get configured as follows:
Hunt List Name: HL2001, includes Line Groups LG2001
Hunt List Name: HL2004, includes Line Groups LG2004 and LG2001, in that order
Hunt List Name: HL2005, includes Line Groups LG2005 and LG2001, in that order
Hunt pilot gets configured as follows:
Hunt Pilot: 2001, Partition: VMPilotNumberPT, Hunt List: HL2001
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 at this URL:

http://www.cisco.com/univercd/home/home.htm

You can access the Cisco website at this URL:

http://www.cisco.com

You can access international Cisco websites at 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 send 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, Cisco Technical Support provides 24-hour-a-day, award-winning technical assistance. The Cisco Technical Support Website on Cisco.com features extensive online support resources. In addition, Cisco Technical Assistance Center (TAC) engineers provide telephone support. If you do not hold a valid Cisco service contract, 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 website is available 24 hours a day, 365 days a year at this URL:

http://www.cisco.com/techsupport

Access to all 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 user ID or password, you can register at this URL:

http://tools.cisco.com/RPF/register/register.do

Submitting a Service Request

Using the online TAC Service Request Tool is the fastest way to open S3 and S4 service requests. (S3 and S4 service requests are those in which your network is minimally impaired or for which you require product information.) After you describe your situation, the TAC Service Request Tool automatically provides recommended solutions. If your issue is not resolved using the recommended resources, your service request will be assigned to a Cisco TAC engineer. The TAC Service Request Tool is located at this URL:

http://www.cisco.com/techsupport/servicerequest

For S1 or S2 service requests or if you do not have Internet access, contact the Cisco TAC by telephone. (S1 or S2 service requests are those in which your production network is down or severely degraded.) Cisco TAC engineers are assigned immediately to S1 and S2 service requests to help keep your business operations running smoothly.

To open a service request 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 list of Cisco TAC contacts, go to this URL:

http://www.cisco.com/techsupport/contacts

Definitions of Service Request Severity

To ensure that all service requests are reported in a standard format, Cisco has established severity definitions.

Severity 1 (S1)—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.

Severity 2 (S2)—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.

Severity 3 (S3)—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.

Severity 4 (S4)—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. Visit Cisco Marketplace, the company store, at this URL:

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 at this URL:

http://www.ciscopress.com

•Packet magazine is the Cisco Systems technical user magazine for maximizing Internet and networking investments. Each quarter, Packet delivers coverage of the latest industry trends, technology breakthroughs, and Cisco products and solutions, as well as network deployment and troubleshooting tips, configuration examples, customer case studies, certification and training information, and links to scores of in-depth online resources. You can access Packet magazine at this URL:

http://www.cisco.com/packet

•iQ Magazine is the quarterly publication from Cisco Systems designed to help growing companies learn how they can use technology to increase revenue, streamline their business, and expand services. The publication identifies the challenges facing these companies and the technologies to help solve them, using real-world case studies and business strategies to help readers make sound technology investment decisions. 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

•World-class networking training is available from Cisco. You can view current offerings at this URL:

http://www.cisco.com/en/US/learning/index.html

This document is to be used in conjunction with the documents listed in the "Related Documentation" section.

CCSP, the Cisco Square Bridge logo, Cisco Unity, Follow Me Browsing, FormShare, and StackWise are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, and iQuick Study are service marks of Cisco Systems, Inc.; and Aironet, ASIST, BPX, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Empowering the Internet Generation, Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step, GigaDrive, GigaStack, HomeLink, Internet Quotient, IOS, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, LightStream, Linksys, MeetingPlace, MGX, the Networkers logo, Networking Academy, Network Registrar, Packet, PIX, Post-Routing, Pre-Routing, ProConnect, RateMUX, Registrar, ScriptShare, SlideCast, SMARTnet, StrataView Plus, SwitchProbe, TeleRouter, The Fastest Way to Increase Your Internet Quotient, TransPath, and VCO are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.

All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0406R)

Copyright © 2004 Cisco Systems, Inc. All rights reserved.

Cisco Unified Communications Manager (CallManager)

Release Notes for Cisco CallManager Release 4.0(2)

Hierarchical Navigation

Downloads

Table Of Contents

Release Notes for Cisco CallManager Release 4.0(2)

Contents

Introduction

System Requirements

Determining the Software Version

Compatibility Matrix and Supported Upgrades

Related Documentation

New and Changed Information

Upgrading to Cisco CallManager Release 4.0(2)

Cisco CallManager Extension Mobility Enhancements

System Enhancement for Route Group and Line Group Processing

Voice Mail Configuration Enhancements

Voice-Mail Pilot Configuration

Voice-Mail Profile Configuration

Cisco Unity Voice-Mail Port Adjustments

Route List Redundancy Configuration

SRST Algorithm Enhancements

Operating System Installation Guidelines

Disabling Cisco RIS Data Collector Prior to Upgrading to Cisco CallManager Release 4.0(2)

New and Updated Support for Cisco IP Phones

Support for Cisco VT Advantage

Dialed Number Analyzer

International Dial Plan

Changes to Type Specific Information in the Gateway Configuration Settings

Calling Search Space Enhancements

Conference Enhancements

Attendant Console Enhancements

NM-HDV2 and NM-HD Support for Cisco CallManager

Security Enhancements

Static Digit Analysis

Using Query to Delete Phones

Using Immediate Divert with Hunt Lists

New and Changed Information for Cisco CallManager Serviceability

Cisco CallManager Renamed After Restarting Services

TroubleShooting Trace Setting

Cisco CallManager Trace Collection Tool

Real-Time Monitoring Tool as Standalone Plug-in

Serviceability Reports Archive

SNMP and Performance Counter Enhancements

CDR Analysis and Reporting (CAR) Enhancements

New and Changed Information for Third-Party and SDK Applications

Important Notes

CSCso79248 Do Not Run installxml.vbs in CallManager Release 3.3 and Later

Adding Cisco CallManager Servers

Installing IPMA Assistant Console on Microsoft Windows XP

Locale Installer for Cisco CallManager

Line Group/Route Group Support for MLPP-Enabled Devices

Using the JTAPI Update Utility with CRS

End User Notes

Attendant Console

Resolved Caveats for Cisco CallManager - Release 4.0(2)

Open Caveats for Cisco CallManager - Release 4.0(2)

Documentation Updates

Errors

Deleting a Conference Device

Deleting a Music On Hold Server

Deleting a Media Termination Point

System Requirements for Barge and Privacy

Configuring Maximum Calls and Busy Trigger Settings for Shared Line Appearances

User Configuration Settings

Cisco CallManager Service Activation/Deactivation

Cisco IP Phone Support

SIP/UDP Port Configuration

Route Pattern Configuration Fields

Cisco IP Phone Configuration Fields

Malicious Call Identification

Translation Pattern Configuration

Calling Search Space Configuration

Partition Field Configuration

Configuring Digits in Configuration Fields

Cisco Call Back Synchronous Request Timeout Configuration

Cisco CallManager Dialed Number Analyzer Private Phrase Requirement

Cisco CallManager Extension Mobility Logout

Using Attendant Console and Shared Lines

Date/Time Configuration Changes