Guest

Cisco Unified Communications Manager (CallManager)

Release Notes for Cisco CallManager Release 3.1(4a)

Table Of Contents

Release Notes for Cisco CallManager Release 3.1(4a)

Contents

Introduction

System Requirements

IBM xSeries 340 and 330 Server Recommendations

Determining the Software Version

Upgrading to 3.1(4a)

SQL Service Pack 4

Compatibility Matrix

Related Documentation

New and Changed Information

Important Notes

Important Notes for Release 3.1(4a)

Restore Procedure

Enabling Microsoft Performance Monitor for troubleshooting

Resolved Caveats for Cisco CallManager Release 3.1(4a)

Open Caveats for Cisco CallManager Release 3.1(4a)

Documentation Updates

Changes

Getting Started Title Changes

Cisco IP Phone 7900 Family Administration Guide Title Changes

Remote Serviceability and Troubleshooting Information Changes Book

T1-CAS connection reference removed

Procedure for Starting the Cisco Telephony Call Dispatcher

Updated Service Parameters Configuration

Omissions

Maintaining Cisco IP Phone Services List

Corrections

Obtaining Documentation

World Wide Web

Documentation CD-ROM

Ordering Documentation

Documentation Feedback

Obtaining Technical Assistance

Cisco.com

Technical Assistance Center

Contacting TAC by Using the Cisco TAC Website

Contacting TAC by Telephone


Release Notes for Cisco CallManager Release 3.1(4a)


July 17, 2002

These release notes describe the new feature and caveats for Cisco CallManager Release 3.1(4a).

For a list of the open and resolved caveats for Cisco CallManager Release 3.1(4a), see "Resolved Caveats for Cisco CallManager Release 3.1(4a)" section and "Open Caveats for Cisco CallManager Release 3.1(4a)" section. These release notes get updated every maintenance and major release.

To read the feature descriptions implemented in Cisco CallManager Release 3.1(3a), refer to

http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/3_1/rel_note/

To access the Cisco CallManager documentation suite, refer to

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

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

http://www.cisco.com/cgi-bin/tablebuild.pl/callmgr

Contents

These release notes discuss the following topics:

Introduction

System Requirements

Compatibility Matrix

New and Changed Information

Important Notes

Resolved Caveats for Cisco CallManager Release 3.1(4a)

Open Caveats for Cisco CallManager Release 3.1(4a)

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 you install and configure Cisco CallManager Release 3.1 on a Cisco Media Convergence Server.

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


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

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

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

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

IBM xSeries 340 and 330 Server Recommendations

For xSeries 340 servers that have the ServerRAID-4Lx Ultra 160 (part number 06P5740), you must upgrade the RAID controller BIOS/firmware to a minimum level of 4.80.26. Without this BIOS/firmware load, CD 1 will not install.

Cisco recommends that if you are deploying an xSeries 340 server with a 20/40 GB DDS/4 4-mm tape drive (marketing part number for tape drive 00N7991), update your tape drive firmware to the latest version 8.160 with a release date of 2/19/01. This upgrade improves the performance of your tape drive.

Cisco recommends that if you are deploying the IBM xSeries 330 or 340 servers, update your Advanced Systems Management Processor (ASMP) firmware if necessary.

For the xSeries 340, the ASMP firmware load should be v1.15 dated 4/16/2001, and for the xSeries 330, the ASMP firmware load should be v1.04 dated 4/9/2001. The firmware upgrade ensures UM Services compatibility.

Access the correct server configuration and firmware location for IBM server or Compaq server at

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

Determining the Software Version

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

Cisco CallManager System version

Cisco CallManager Administration version

Database information and database DLL versions

Upgrading to 3.1(4a)

Cisco recommends that you upgrade to Cisco CallManager 3.1(4a) from the latest Cisco CallManager version 3.0(12) or any version of 3.1.

SQL Service Pack 4

Before upgrading to Cisco CallManager 3.1(4a), you should install SQL Service Pack 4. Refer to Upgrading Cisco CallManager Release 3.1(4a) for more information.

Compatibility Matrix

You can find the minimum versions with which Cisco CallManager Release 3.1(4a) has been tested at

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


Note Please review the product-specific release notes to make sure that no known defects exist that will prevent the component or application from working with Cisco CallManager.


Related Documentation

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

Cisco CallManager Document Locator for Release 3.1(4a)

Quick Start Guide for Cisco CallManager Release 3.1

Installing Cisco CallManager Release 3.1

Rack-Mount Conversion Kit Installation

Upgrading Cisco CallManager Release 3.1

Backing Up and Restoring Cisco CallManager Release 3.1

Cisco CallManager Administration Guide

Cisco CallManager System Guide

Cisco IP Phone Administration Guide for Cisco CallManager

Cisco CallManager Serviceability Administration Guide

Personal Directory Configuration Guide

Cisco WebAttendant User Guide, Release 3.1

Cisco CallManager 3.1 JTAPI Developer's Guide

Cisco CallManager 3.1 TAPI Developer's Guide

Cisco CallManager 3.1 Extension Mobility API Developer's Guide

System Error Message

Software License Agreement

New and Changed Information

The following sections describes the new features for Cisco CallManager Release 3.1(4a).


Tip To see the feature descriptions that were added to Cisco CallManager Release 3.1(3a), refer to http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/3_1/rel_note/


Important Notes

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

Important Notes for Release 3.1(4a)

Restore Procedure

In the unlikely event of a catastrophic multiserver failure, you must restore every server in the Cisco CallManager cluster. Consider the following guidelines before you restore the cluster.


Step 1 Restore the publisher database server first.


Note Cisco requires that you restore the server to the version of the last successful Cisco CallManager database backup.


Step 2 Restore the Cisco CallManager database.

Step 3 Install Cisco CallManager on all subscribers in the cluster.


Enabling Microsoft Performance Monitor for troubleshooting

Microsoft Performance Monitor is an application that monitors and logs resource counters from the Cisco CallManager nodes in the network and displays the system activities and status information in real time.


Tip Use the following procedure to collect and display system and device statistics for any Cisco CallManager installation. The collected information enables Cisco TAC to help you with potential installation problems.


Procedure


Step 1 Access Performance Monitor by choosing
Start > Programs > Administration Tools > Performance.

Step 2 Choose Action > New log settings and enter a name for the counter log.

Step 3 Click Counters.

Step 4 Click Add.

Step 5 Click Performance Object.

Step 6 Click Process.

Step 7 In Select Counters from List and Select Instances from List, choose the following counters and associated instances:

% Processor Time/_Total

% Processor Time/ccm

% Processor Time/AudioTranslator

% Processor Time/Aupair

% Processor Time/CiscoMessagingI

% Processor Time/ctftp

% Processor Time/CTIManager

% Processor Time/DLLHOST

% Processor Time/sqlservr

% Processor Time/TcdSrv

% Processor Time/RisDC

% Processor Time/snmp

% Processor Time/CallBackService

% Processor Time/LogoutService

% Processor Time/InsertCDR

Virtual Bytes/_Total

Virtual Bytes/AudioTranslator

Virtual Bytes/Aupair

Virtual Bytes/ccm

Virtual Bytes/CiscoMessagingI

Virtual Bytes/ctftp

Virtual Bytes/CTIManager

Virtual Bytes/DLLHOST

Virtual Bytes/sqlservr

Virtual Bytes/TcdSrv

Virtual Bytes/RisDC

Virtual Bytes/snmp

Virtual Bytes/CallBackService

Virtual Bytes/LogoutService

Virtual Bytes/InsertCDR

Private Bytes/_Total

Private Bytes/ccm

Private Bytes/AudioTranslator

Private Bytes/Aupair

Private Bytes/CiscoMessagingI

Private Bytes/ctftp

Private Bytes/CTIManager

Private Bytes/DLLHOST

Private Bytes/sqlservr

Private Bytes/TcdSrv

Private Bytes/RisDC

Private Bytes/snmp

Private Bytes/CallBackService

Private Bytes/LogoutService

Private Bytes/InsertCDR

Step 8 Click the General tab.

Step 9 Enter the collection interval of 60 and for Units choose seconds so that the data is averaged and collected over 60-second intervals.

Step 10 Click Apply.

Step 11 Click the Schedule tab.

Step 12 Choose the At option for Start log and enter the current time and date.

This will enable the logging to continue after a reboot.

Step 13 Click Save to save your settings, such as the Objects you selected.

This allows you to load the same data again, if necessary.


Note The log files will expand in size. Manually purge the log files to maintain optimal disk space.



Performance Monitor can simultaneously collect data from multiple installed systems and store the information in a single log file. You can export the log file into a Tab Separated Value (TSV) file or a Comma Separated Value (CSV) file. View the TSV file or CSV file in a spreadsheet application.


Note You must enable Statistics in the Cisco CallManager Administration for the Performance Monitor to collect data.


Cisco CallManager directly updates Microsoft Performance Monitor counters. The call perfmon counters are call-processing-related counters, which contain simple, useful counts such as number of registered phones, number of active calls, and number of available conference bridge resources.

The following list identifies the Cisco CallManager performance counters:

Cisco CallManager

Cisco Phones

Cisco Lines

Cisco H323

Cisco MGCP Gateways

Cisco MOH Device

Cisco Analog Access

Cisco MGCP FXS Device

Cisco MGCP FXO Device

Cisco MGCP T1CAS Device

Cisco MGCP PRI Device

Customize Performance Monitor to view the Cisco CallManager-related parameters that you want to monitor by choosing the object, counter, and the instance.

Resolved Caveats for Cisco CallManager Release 3.1(4a)

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


Note 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/support/bugtools


Table 1 Resolved Caveats for Cisco CallManager Release 3.1(4a)

DDTS Number
Description

CSCdr41623

A feedback loop gets created when a port on a Cisco Unicast Conference Bridge is conferenced back to itself.

CSCds88657

Gatekeeper calls cause memory loss on a Cisco CallManager server.

CSCds89957

Wave installation does not have the correct path to install avaudio.dll.

CSCdt24024

Calls from CTI ports that are redirected to a busy destination fail.

CSCdt28379

CallerID does not display correctly.

CSCdt34467

Two skinny protocol messages should be deleted from Cisco CallManager.

CSCdt37112

User does not get sent progress tones on intercluster trunk transfers.

CSCdt42334

Conference function key remains active upon reaching the maximum conference participants.

CSCdt53938

Binary files do not get placed in non-default TFTPPATH during an upgrade.

CSCdt71376

WS-X6608 E1 does not establish D-channel with Cisco CallManager server.

CSCdt82549

Every MaxForwardsToDn call on a phone in a call pickup group gets sent a reorder tone.

CSCdt85519

Bandwidth does not get returned when the location is updated before a call ends.

CSCdt91655

STI backup utilities need to run at a low priority.

CSCdu10765

Unity cannot identified AS-8 port when the voice message field is used.

CSCdu17718

A call forwarded with no answer reason gets busy greeting.

CSCdu21141

A lineAnswer returns SUCCESS, but state does not change.

CSCdu21191

An anonymous device can be configured but not selected or used from the route pattern page.

CSCdu28942

Real time transport protocol (RTP) packets are dropped when using Cisco Catalyst 6000 24 Port FXS Analog Interface Module or Cisco Catalyst 6000 8 Port Voice and Services Module and Cisco CallManager has a failover.

CSCdu29953

Ad hoc conference fails when H.323gateway has a matching destination Pattern in VOIP Dial-peer.

CSCdu31336

Call gets dropped when the CTI port is reset.

CSCdu52785

External calls through a MGCP gateway do not have a distinctive ring.

CSCdu60691

Phone connected to H323 does not get ringback after a blind transfer.

CSCdu61027

Cisco CallManager has problems in the initialization code for gateways.

CSCdu70546

DT24 needs to be removed from the database and from the device default table.

CSCdu77516

Failure response occurs from lineUnHold when consult call is offering.

CSCdu77983

CTI redirect of a party in a conference causes an erroneous conference state.

CSCdu78398

When the phone goes off hook, it uses the shared line appearance instead of the primary line.

CSCdu86461

Caller gets incorrect voice mailbox when the DN is not registered.

CSCdv02729

Cisco CallManager sent an ICMP Unreachable (IU) event to the gateway.

CSCdv05069

Administrator gets an error when an administrator is upgrading Cisco CallManager if the server is not part of the Active Directory domain.

CSCdv12935

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

CSCdv20206

Call through H.323 gateway that is using G729 code gets dropped when the call is put on hold.

CSCdv35147

Call gets disconnected due to havingthe same timeout value for MGCP and MediaExchange.

CSCdv53855

Call park does not work with partitions.

CSCdv54109

Personal Directory does not work if Cisco CallManager server is integrated with Active Directory.

CSCdv58628

Cisco SoftPhone displays error message when it is integrated with Microsoft Outlook.

CSCdv61425

Cisco CallManager logic can cause CPU to spike when many CTI devices are registered.

CSCdv61666

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

CSCdv64729

Wave ID for a CTI port changes after a failover.

CSCdv65210

Some parameters do not get added to the ProcessConfigDefaults table after a Cisco CallManager upgrade.

CSCdv65358

Intercluster trunks advertise wrong codecs.

CSCdv66602

Calls that are redirected from Cisco IP ICD do not pass the correct called party number.

CSCdv73539

Hookflash transfer from a MGCP gateway to a H.323 gateway fails.

CSCdv79972

You cannot delete a personal address book entry from a Cisco IP Phones.

CSCdv80693

ToneOnHold Service Parameter does not affect calls through a WS-6608.

CSCdv82985

Translation pattern changes do not take effect until Cisco CallManager restarts.

CSCdv84016

Cisco CallManager forwards calls as CFNA when extension mobility user is not logged in.

CSCdv84097

Administrators cannot modify existing Active Directory user in Cisco CallManager Administration.

CSCdv84631

Telephony Call Dispatcher (TCD) service stops.

CSCdv87213

Error message gets written in Cisco CallManager event logs for call busy condition.

CSCdv87998

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

CSCdv89329

Cisco Softphone displays unknown string when it is joining a meet me conference.

CSCdw00421

VGC device default profile is missing in the Cisco CallManager after a new installation.

CSCdw02285

User directory service crashes when one of its fields is empty.

CSCdw05097

Calls transferred from Octel fail when progress gets returned.

CSCdw05630

Changing the timezone to the Adelaide Date/Time group (GMT +9:30) does not work for IP Phones.

CSCdw05993

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

CSCdw08627

An ICD agent displays a phantom call when an H.323 call disconnects at the same time that the call is redirected from the route point to the agent.

CSCdw14079

CPU usage goes high when TAPI application attempts to call provideropen on 2500 controlled devices.

CSCdw15247

The assistant's attended time does not get charged if the call is diverted.

CSCdw16745

External calling mask does not get applied when phone is unregistered.

CSCdw19697

The call leg from the PSTN to the transcoder does not release the transcoding session when a call completes.

CSCdw25967

No LINE_REPLY gets returned on lineDrop on a conferenced call state.

CSCdw22250

A call redirected with a CALLDEFLECTION reason does not get the proper greeting.

CSCdw23235

LineGetInfoReq to CTI does not return all call handles.

CSCdw24078

TAPS application sends a message that the phone is already configured.

CSCdw26569

Handle timeout is needed for DeviceLineInfoFetchReq so as not to remove lines.

CSCdw27029

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

CSCdw27828

A call disconnects when it is redirected to a busy CTI port.

CSCdw27971

User cannot answer an offering conference call on a CTI port.

CSCdw28309

Phones with shared lines do not display line in use message.

CSCdw28469

An IP phone device fail due to missing in service event.

CSCdw28382

A consult call does not get cleared from the CTI port at the end of the first call.

CSCdw28981

Phones with call forward all enable cannot receive calls from a MGCP T1-CAS.

CSCdw30417

Application fails to create JTAPI provider.

CSCdw31284

CiscoAddrInServiceEv does not get sent to applications.

CSCdw31525

Cisco CallManager does not send the correct ISDN disconnect messge.

CSCdw32515

Translation pattern does not get updated properly.

CSCdw34190

JTAPI returns an error after a successful call transfer.

CSCdw34631

Cisco IP ICD calls are aborted due to transfer failure.

CSCdw34847

CiscoTransferStartEv has consultCall and finalCallIDs reversed.

CSCdw34925

Only one TermConnDropped gets received in certain scenario when two are expected.

CSCdw35123

LineOpen returns with a resource unavailable error.

CSCdw35875

Cisco CallManager restarts during router verifications.

CSCdw36247

TermconnDropped does not get sent to agent when a consult call is held.

CSCdw36848

A leak occurs in the lineInitializeEx, and Shutdown handles.

CSCdw36906

A CTI message with out of bounds index causes Cisco CallManager to restart.

CSCdw38412

Call transfer fails during Cisco IP ICD load test.

CSCdw38150

Three call handles get created on a two-party conference call.

CSCdw38206

Disconnect event does not occur when a call is dropped on unplugged phone.

CSCdw39225

Cisco CallManager does not send the caller ID time correctly when the call is made over the MGCP gateway.

CSCdw42053

Cisco CallManager restarts due to an out of bounds index in the locations array.

CSCdw42138

Race condition causes phantom call.

CSCdw42229

Cisco CallManager restarts due an out of bounds index array in StationD.

CSCdw42358

The CTI port does not get released after a transferred call goes idle.

CSCdw43706

Phones that are added with extension mobility enabled generate event log error messages.

CSCdw44070

Ipvmsapp.exe crashed with a kDeviceMgrThreadException error.

CSCdw46019

Hookflash transfer to the webattendant pilot point fails.

CSCdw47724

Requested Heartbeat Interval of 300 seconds causes TSP connection to fail.

CSCdw47748

Uninstall program for TSP has an incorrect option.

CSCdw47868

Redirect reason code is received for normal disconnect.

CSCdx49380

CiscoTransferStart message is received before an agent answers a call.

CSCdw49964

Provider Open for a TAPI application needs to be optimized.

CSCdw50179

Phone does not ring when a Call Forward No Answer (CFNA) is enabled from a shared line to a primary line.

CSCdw50721

An out-of-bounds stimulus causes Cisco CallManager to reset.

CSCdw55276

CTI manager becomes unresponsive under 25000 BHCC after 31 hours.

CSCdw55611

Incorrect called address displays for calls made from an observed device.

CSCdw55631

Cisco CallManager has a memory leak when it is under high call load, and many uncompleted calls occur.

CSCdw56095

Snapshot talking events are received late when you are observing a call in progress.

CSCdw57062

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

CSCdw57393

Call.getCalledAddress returns the CTI port address instead of the RP address.

CSCdw57571

Message waiting is not enable if it is sent before the application starts.

CSCdw57815

Transfer failures occur during Cisco IP Integrated Contact Distribution (Cisco IP ICD) load test.

CSCdw63219

The CTI Manager process increases CPU utilization over time.

CSCdw60938

Timer creations get removed when no delay for DbDnQuery is requested.

CSCdw61917

Cisco CallManager service stops after a failover.

CSCdw63622

Cisco CallManager crashes intermittently when it is using the EURO protocol.

CSCdw64526

Calls through the gatekeeper stop working after the gateway resets.

CSCdw64810

Call failure occurs when Cisco CallManager encounters IE error messages during setup.

CSCdw65106

User cannot transfer or hold a call on line 2. Line1 goes off hook when line 2 is answered.

CSCdw65946

LowPriorityQueueThrottlingFlag does not always work correctly.

CSCdw66164

LineGetAddressStatus() does not provide existing forwarding status.

CSCdw66560

Cisco CallManager Administration takes a long time to display user information.

CSCdw66759

NullPointer gets thrown in JTAPI Provider and Cisco CallManager classes.

CSCdw69311

QBEHelper Support does not handle error conditions.

CSCdw69929

Digital signal processor (DSP) memory corruption causes entire port to reset.

CSCdw71833

Residential Gateway (RGW)/Line Side Gateway calls fails when VoAL2 is used as the voice bearer.

CSCdw72636

Cisco Catalyst 6000 sends TFTP requests at a very high rate when it fails to receive the XML file from the TFTP server.

CSCdw72645

Call Pickup stops working.

CSCdw72865

Svchost.exe crashed under load.

CSCdw73031

CallPark reversion does not display if Call Forward Busy and Call Forward no Answer are enabled on the phone.

CSCdw75522

CTI route points are unavailable after a failover.

CSCdw77135

Cisco CallManager does not send a restart_ack.

CSCdw77358

MaxForwardtoDN does not allow sequential calls.

CSCdw77924

MSGWAIT is missing on dwDevStausFlags when the lamp is enabled on the phone.

CSCdw78066

Back button does not work in the Destination Location window.

CSCdw79042

No TermConnDropped message gets received in a chained-transfer scenario.

CSCdw79075

Svchost crashed.

CSCdw79147

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

CSCdw80332

No LINE_REPLY gets sent on a lineUnHold request on ONHOLDPENDCONF.

CSCdw80824

Cisco CallManager does not respond to IRQ.

CSCdw81189

Cisco CallManager had an access violation while it is decoding Setup UUIE.

CSCdw81294

The firmware for Cisco IP Phone models 7940 and 7960 cannot be upgraded from version P003AM30 to P00303010106.

CSCdw82990

T305/HangupTimeout value does not get set correctly.

CSCdw84396

Cisco CallManager does not send a NOTIFY message immediately.

CSCdw87026

DCD subscriber does not have indexing.

CSCdw88178

Calls get stuck in the CTI port after a redirect failure.

CSCdw88191

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

CSCdw88290

Cisco CallManager does not support CanMapAlias.

CSCdw89859

Call Park stops working for some call park extensions.

CSCdw90402

Resetting route groups causes high CPU usage.

CSCdw90846

Redirect ORIGINATOR_ABANDONED call should mapped to INVALCALLSTATE.

CSCdw92874

The method call.connect() throws an exception when a call is made to a phone behind H.323 gateway.

CSCdw93017

Cisco IP Phone model 7940 speakerphone does not operate in full duplex.

CSCdw93403

Redirect occurs even though LineRedirect request line reply returns LINEERR_INVALLINESTATE.

CSCdw93592

Two applications monitoring the same CTI route point causes route errors.

CSCdw94897

Call gets dropped when it is redirected to a nonestablished MeetMe extension.

CSCdx00431

CTI ignores indicator and displays number instead of displaying Private.

CSCdx00851

FXO port on Cisco VG200 running MGCP locks up when phone sets call forward all (CFA) to a H.323 device.

CSCdx02228

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

CSCdx02301

Redirected calls fail when the caller redirects the call.

CSCdx03070

The original caller gets dropped when a user transfers a call to the phone's second line.

CSCdx04595

Directory search on an IP phone does not allow both upper-case and lower-case letters.

CSCdx04903

Phone continues to ring after a call is answered.

CSCdx04968

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

CSCdx06472

Cisco CallManager does not send MGCP notification request (RQNT) after receiving a 401 (Already offhook) message.

CSCdx07018

Call Park fails where there are other active park sessions.

CSCdx07448

Creating DBLException from COM Error causes an exception.

CSCdx07563

Phones with shared lines do not ring when there is an incoming call.

CSCdx09121

IP phones should display "Too Much Traffic Try Again Later" error message when the IP phones request dial tone on a Cisco CallManager with a congested event queue.

CSCdx10078

The subscriber Cisco CallManager sends registration request (RRQ) messages every 3 seconds when the primary Cisco CallManager goes down.

CSCdx10416

Phone cannot boot up if the URL has special characters.

CSCdx11296

Cisco SoftPhone did not receive a LINE_GENERATE event.

CSCdx11616

Cisco WebAttendant gets missing JTAPI class error.

CSCdx13166

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

CSCdx14064

IP phone does not display calling party number in the status line.

CSCdx15306

JTAPI throws an exception when parking and the parked party are not in the same provider.

CSCdx15510

User gets an error when an expansion module is added.

CSCdx15755

Cisco CallManager drops the call when it receives an IZCT token in the ACF message.

CSCdx15818

Overlap sending does not work for phones registered to back up Cisco CallManager servers.

CSCdx16259

You get an error when you try to use the 7914 template after upgrading Cisco CallManager from version 3.0(11) to 3.1(3a).

CSCdx16935

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

CSCdx17788

GetConsultingTerminalConnection returns incorrect value.

CSCdx18236

The Cisco CallManager process monitor trace level should be set to ARBITRARY.

CSCdx20355

The route plan wizard creates a incorrect route filter.

CSCdx20377

Cisco CallManager has disk I/O contention issues with SDI tracing and logging.

CSCdx20568

Invalid Connected ID gets displayed after a consult-transfer of a conference call.

CSCdx24175

You cannot update the routelist after removal of a routegroup that was created by the route plan wizard.

CSCdx24497

Directory change notification fails.

CSCdx24602

User gets an error when user tries to view line details for a Cisco VG248 with Cisco CallManager 3.1(3a).

CSCdx24931

A connection clear event does not get sent when a gateway call is dropped from a conference.

CSCdx25239

You cannot add or delete a device in the user pages after adding a device that is not registered with Cisco CallManager.

CSCdx25581

Cisco CallManager sends a Display IE in a NOTIFY message when the "Display IE Delivery" is disabled.

CSCdx25593

H.323 ICT calls fail due to Q931 Cause Codes AF.

CSCdx25986

StationD with StationOutputSetLamp access out of bound array.

CSCdx26023

Problems occur when an active call exists on a non-CTI-controlled line and the CTI application sends a "Change Line Filter" request to the CTI application for the CTI-controlled line.

CSCdx26254

JTAPI sends a bogus conference event and missing AlertingEv when a device redirects a conference call.

CSCdx26294

User does not display when the first or last name is missing in Active Directory or Netscape Directory.

CSCdx26300

JTAPI sends a bogus conference event and missing AlertingEv when a device redirects a connected call.

CSCdx26394

Backup utility does not install properly.

CSCdx28101

IP phone does not register to the subscriber Cisco CallManager.

CSCdx28149

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

CSCdx28501

CtiLineClosed alarms do not get sent when a TAPI or JTAPI application shuts down.

CSCdx29157

Cisco CallManager has high CPU usage when there are a large number of calls forwarded to a voicemail system with a high number of ports.

CSCdx29508

Perfmon counter displays the incorrect available bandwidth for remote locations.

CSCdx29677

Cisco CallManager does not apply external phone mask to calls on phones with CFA enabled.

CSCdx31771

CDR pruning process causes high CPU usage.

CSCdx31790

The database maintenance task needs to clear the sysreplicationalerts table.

CSCdx31959

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

CSCdx31981

You cannot associate a device to a user if Cisco CallManager is integrated with Active Directory.

CSCdx32407

Cisco CallManager server does not initialize when there are more than 100 locations.

CSCdx33171

All digits for a call with RDNIS information does not get forwarded to the MGCP gateway.

CSCdx33982

A hold event does not get sent in a TAPI/soft-key transfer conference scenario.

CSCdx34358

Aupair logs on Cisco CallManager servers display*ERROR* tableName is empty message.

CSCdx35058

ASP error gets displayed when the all button is chosen on the Route Plan Report.

CSCdx35252

Removing RIS from the database causes an error to be recorded in the event log.

CSCdx35254

Updating IP Phone Services subscription freezes the screen temporarily.

CSCdx35637

Service Parameter modifications do not appear after a support patch installation.

CSCdx35688

CFA set on IP phone should check the CFA CSS.

CSCdx35838

JTAPI sends wrong CallCtlTermConnTalkingEv when a device redirect a held call.

CSCdx35964

The Caller ID does not display correctly on phone load 00303010400.

CSCdx36263

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

CSCdx36275

Svchost crashes because device.m_WaveList pointer is null.

CSCdx36718

JTAPI call processing gets errors when CTI passes empty calling party.

CSCdx36721

Classpath for DCD Change Notification does not get set when upgrading Cisco CallManager.

CSCdx36953

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

CSCdx37137

JTAPI needs to have a clearCall method.

CSCdx37672

Ringback gets played after the transfer completes.

CSCdx38050

A caller using PSTN receives ringback after a transfer while the person who is answering can hear the caller.

CSCdx38723

The restart devices for changes to take effect window does not pop up when the directory number is added for the second line on a Cisco IP phone 7960 or 7940.

CSCdx39255

Calls from IP phone to another IP phone receives the reorder tone when 60+ regions exist.

CSCdx39416

Applications do not recover following a JTAPI provider Out-Of-Service Event.

CSCdx39942

Multiple transfer failures cause the agent desktop to go repeatedly from the Ready state to the Reserved state and then back to the Ready state again.

CSCdx40962

Phones continuously request xml file because of conflicting <vendorConfig> tag.

CSCdx41461

The UnknownCallerID Field allows the user to enter nonnumeric characters.

CSCdx41601

SNMP Data Collector service does not get removed when upgrading from Cisco CallManager release 3.1 to 3.2 occurs.

CSCdx42085

Intermittently, a user cannot answer calls on a Cisco IP Phone model 7960 with a Cisco IP phone 7914 Expansion Module with shared lines.

CSCdx42412

JTAPI throws an exception when a call generates DTMF.

CSCdx42891

Origin field should default to internal rather than external on the redirected destination.

CSCdx43160

Consult call request causes a conference call.

CSCdx44401

Callers on hold do not receives music after a period of time.

CSCdx46281

Cisco CallManager servers need an alarm for applications that failed to handle calls in time.

CSCdx46742

Calls skip first shared line on the phone.

CSCdx46753

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

CSCdx46809

Inbound calls with an IE in Codeset 7 get dropped.

CSCdx47142

Svchost.exe crashed.

CSCdx47150

User does not get displayed when the last name field is empty on Active Directory.

CSCdx48097

MGCP Caller ID Timestamp has an incorrect format.

CSCdx48500

A handle leak occurs when clients close sockets.

CSCdx50661

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

CSCdx51032

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

CSCdx51077

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

CSCdx51278

Presentation restricted does not get preserved when a call is tandem switched.

CSCdx51423

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

CSCdx52074

Cisco CallManager does not forward access or accounting code after the 1-digit (long distance) number has been sent to MGCP gateway.

CSCdx52173

Cisco CallManager has a memory leak when heavy traffic exists.

CSCdx52691

User cannot delete the entry for the email field in the personal address book.

CSCdx53797

Incorrect calling party information gets sent in existing CallEvent for unparked calls.

CSCdx53931

Cisco CallManager resets when more than 130 regions exist.

CSCdx54081

Media Streaming Application does not notify the Cisco CallManager server when it detects ICMP messages.

CSCdx54678

The back button on the user information page does not work properly.

CSCdx55658

RIS data collector uses a large amount of memory.

CSCdx57227

Cisco CallManager incorrectly lists the directory number assigned to a CTI route point as the originalcalledparty on calls forwarded from the CTI route point.

CSCdx57258

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

CSCdx57679

Blind transfers to a MGCP FXS does not work.

CSCdx58041

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

CSCdx58440

Incorrect called party number gets displayed on the phone.

CSCdx58956

A gateway call in a conference does not get preserved when the primary Cisco CallManager server goes down.

CSCdx59603

Cisco CallManager does not identify consult transfer or conference calls.

CSCdx59819

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

CSCdx60233

User cannot hear the dialtone after pressing either the transfer or new call softkey.

CSCdx60789

Application experiences long delay for login and logout requests.

CSCdx60790

The owner field does not get populated when a user is created with Active Directory or Netscape console and updated with Cisco CallManager Administration.

CSCdx61068

CPU usage goes to 100 percent during call clearing.

CSCdx61476

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

CSCdx61771

JTAPI does not receive AddressInService events after the failover.

CSCdx61918

Out of bounds index array causes Cisco CallManager to restart.

CSCdx62770

Unicast music-on-hold stream RTP packets do not get marked with the appropriate TOS/DSCP bits.

CSCdx63899

Cdcc has a memory leak caused by late CRCX Ack messages.

CSCdx65311

Cisco CallManager has high CPU and memory usage after four days of heavy traffic.

CSCdx65821

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

CSCdx66813

ProviderOPen fails

CSCdx69086

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

CSCdx69088

CTI based conference request fails when there is a missing disconnect event during conference tear down.

CSCdx70302

JTAPI fails to send a CallCtlConnAlertingEv for target device when redirectinga held call.

CSCdx70714

Service parameters do not appear on Cisco CallManager Administration.

CSCdx72592

Updating or inserting regions on a Cisco CallManager with a large number of regions cause high CPU usage.

CSCdx73384

Cisco CallManager has a handle leak.

CSCdx75623

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

CSCdx77648

User cannot make intercluster calls.

CSCdx76826

CDRBackup registry key does not get inserted when upgrading backup and restore utility.

CSCdx77387

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

CSCdx80054

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

CSCdx80060

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

CSCdx80842

Cisco CallManager adds a 0 to the enterprise ID trap.

CSCdx81203

A held call gets partially torn down when it is retrieved.

CSCdx82991

JTAPI passes unknown destination handle in the proceeding event.

CSCdx83662

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

CSCdx84099

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

CSCdx84796

You cannot add or delete 96 voice ports using the voice mail wizard.

CSCdx85997

The Cancel Changes button does not work for Route List.

CSCdx86548

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

CSCdx86588

Cisco CallManager does not support a true blind transfer when a phone connected to a MGCP gateway does a hookflash transfer.

CSCdx86770

HeldConferenceController is nullwhen conf erencing a transferred consult call.

CSCdx89263

Upgrades fail when there are apostrophes in the PhoneButton Table.

CSCdy00431

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

CSCdy01278

The cdrbackup registry key does not get updated when performing a CD upgrade.

CSCin07380

Address remains out of service when CallObserver is added.

CSCin08805

Dialing an invalid DN causes Cisco CallManager to play an improper tone.

CSCuk32907

A call forwarded to a busy number does not get a busy tone.

This release also resolves the following firmware caveats.

CSCdu27127

Devices do not use the TFTP server when DNS cannot resolve the Cisco CallManager server name.

CSCdv05279

You receive an echo on handset calls when the volume is set to over 75 percent.

CSCdv17901

XML services can take up to 60 seconds to display after an URL redirect.

CSCdv82750

User cannot answer a call when the directory number is highlighted in the directory menu.

CSCdv86760

Cisco IP Phone model 7960 continues to try and register with default gateway while it is registered with a Cisco CallManager server.

CSCdv90113

Voice quality and volume get reduced when Cisco IP phone 7960 speakerphone is used.

CSCdw01273

Directory button displays host not found when a URL is wrong.

CSCdw05779

Cisco CallManager has high CPU usage when it gets over 1200 off hook requests from a phone in less than 3 seconds.

CSCdw08972

Cisco IP Phone models 7940 and 7960 reset after XML services are accessed.

CSCdw12609

Uninstall shield does not exist for Cisco WebAttendant on Windows 98 or Windows NT platform.

CSCdw16720

Illegally fragmented packets reboot phones.

CSCdw33151

Rehoming fails on IP phones if multiple occurrences of failover/failback happen.

CSCdw46312

An incoming call that causes the MWI light to flash is not obvious to the user.

CSCdw48094

Cisco IP Phone model 7960 does not complete configuration download when extension mobility user logs in or logs out while the speaker is disabled.

CSCdw50535

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

CSCdw51824

Cisco IP phone model 7960 emits a popping noise when the speaker is used after a long idle time.

CSCdw53320

Cisco IP Phone 7960 speakerphone does not operate properly.

CSCdw55207

User receives beeps on a phone with a shared line that has call forward all enabled.

CSCdw62847

Two IP phones on a switch experience one-way delay.

CSCdw64263