[an error occurred while processing this directive]

Cisco Unified Communications Manager (CallManager)

Release Notes for Cisco CallManager Release 3.2(3)


Table Of Contents

Release Notes for Cisco CallManager Release 3.2(3)



System Requirements

Determining the Software Version

Compatibility Matrix and Supported Upgrades

Related Documentation

New and Changed Information

Cisco CallManager Release 3.2(3)

Important Notes

Cisco Communication Media Module

Transcoder Bandwidth Allocation

Changing User IDs

Resolved Caveats for Cisco CallManager - Release 3.2(3)

Open Caveats for Cisco CallManager - Release 3.2(3)

Documentation Updates


Cisco VG248 Analog Phone Gateway (VG248) Support

T1-CAS Connection Reference Removed

Procedure for Starting the Cisco Telephony Call Dispatcher

Updated Service Parameters Configuration


Obtaining Documentation

World Wide Web

Documentation CD-ROM

Ordering Documentation

Documentation Feedback

Obtaining Technical Assistance


Technical Assistance Center

Contacting TAC by Using the Cisco TAC Website

Contacting TAC by Telephone

Release Notes for Cisco CallManager Release 3.2(3)

Feb. 27, 2003

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

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

To access the documentation suite for voice products, refer to


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



These release notes discuss the following topics:


System Requirements

Compatibility Matrix and Supported Upgrades

Related Documentation

New and Changed Information

Important Notes

Resolved Caveats for Cisco CallManager - Release 3.2(3)

Open Caveats for Cisco CallManager - Release 3.2(3)

Obtaining Documentation

Obtaining Technical Assistance


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

System Requirements

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

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

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

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


Determining the Software Version

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

Cisco CallManager System version

Cisco CallManager Administration version

Database information and database DLL versions

Compatibility Matrix and Supported Upgrades

You can find the minimum versions with which Cisco CallManager Release 3.2(3) has been tested and which previous release of Cisco CallManager has upgrade support at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/ccmcomp.htm

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

Related Documentation

The following list contains related documents for Cisco CallManager Release 3.2:

Cisco CallManager Document Locator for Release 3.2(3)

Quick Start Guide for Cisco CallManager Release 3.2

Installing Cisco CallManager Release 3.2

Upgrading Cisco CallManager Release 3.2

Using the Cisco IP Telephony

Applications Backup Utility, Version 3.5.10 (or later)

Cisco CallManager Administration Guide

Cisco CallManager System Guide

Cisco IP Phone Administration Guide for Cisco CallManager

Cisco CallManager Serviceability Administration Guide

Cisco CallManager Serviceability System Guide

Personal Directory Configuration Guide

Cisco Attendant Console User Guide

Cisco CallManager 3.2 JTAPI Developer's Guide

Cisco CallManager 3.2 TAPI Developer's Guide

Cisco CallManager 3.2 Extension Mobility API Developer's Guide

System Error Message

Software License Agreement

Cisco CallManager Extended Services Administrator's Guide. Refer to


Release Notes for Cisco CallManager Extended Services. Refer to


New and Changed Information

This section describes any new features and or changes pertinent to this release of Cisco CallManager.

Cisco CallManager Release 3.2(3)

Cisco CallManager Release 3.2(3), a maintenance release, adds no new features. This release resolves caveats, and this document provides workarounds for open caveats.

Tip To see the feature descriptions that were added to Cisco CallManager Release 3.2(1), refer to http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/3_2/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.2(3).

Cisco Communication Media Module

The Communication Media Module is referenced as Cisco Catalyst 6000 AVVID Services Module in the Cisco CallManager Administration, documentation, and online help.

Transcoder Bandwidth Allocation

Cisco CallManager only supports location configurations where a transcoder and a G.711 device are co-located. Cisco CallManager allocates 24 kbytes of bandwidth for calls that are using this configuration where the endpoint devices are using G.711 and G.729. Cisco CallManager does not allocate the correct bandwidth when you use a different codec or when the transcoder is located in a remote location.

Changing User IDs

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

Resolved Caveats for Cisco CallManager - Release 3.2(3)

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

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

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

Table 1 Resolved Caveats for Cisco CallManager Release 3.2(3) 



H.245 packet precedence does not get properly set.


Phones do not have distinctive rings for calls through a Media Gateway Control Protocol (MGCP) gateway.


IP phone does not ring private DN if the shared line is set to no ring.


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


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


Cisco CallManager does not retry admission request (ARQ).


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


The user experiences 2 seconds of clipping when there is a WAN delay of 100 ms.


Cisco CallManager User cannot get associated phone from Active Directory referral.


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


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


Cisco CallManager should support Cisco fax relay in Software-based Media Termination Point (MTP).


Cisco CallManager delays forwarding calls after you activate or deactivate call forward all.


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


Call park fails when there are other active park sessions.


You cannot enable Cisco Discovery Protocol (CDP) on both ethernet interfaces.


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


Cisco CallManager displays negative SdlTimer value error message in the SDL logs.


Java Telephony Application Programming Interface (JTAPI) delivers the wrong events to an observer with a synchronized block in the callChangedEvent callback.


Directory change notification fails intermittently.


The SQL server driver sends a timeout error when a large number of devices are updated or deleted.


The default for Cisco CallManager initialization timer specifies 10 minutes.


Call Detail Records (CDR) pruning process causes high CPU usage.


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


The Call Forward All (CFA) Calling Search Space (CSS) does not get checked when CFA is enabled on an IP phone.


InsertCDR service fails to start when the universal naming convention (UNC) path has a domain name.


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


Call Management Records (CMR) display no data even when Call Diagnostics is enabled.


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


Multicast Music On Hold (MOH) stops working.


Directory replication reconfiguration process needs to be simplified.


Calls skip first shared line on the phone.


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


Media Gateway Control Protocol (MGCP) caller ID timestamp displays the wrong format.


Manual purge of CDR data causes the CPU usage to increase to 100 percent.


The application receives a CiscoTransferStart before an agent answers.


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


Associating non-CTI devices with a Computer Telephony Integration (CTI) user causes a LINE_CREATE message to be sent.


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


Cisco CallManager does not forward access codes to the MGCP gateway.


The Media Streaming Application does not notify Cisco CallManager when it detects an Internet Control Message Protocol (ICMP) packet.


Real-Time Information Server (RIS) Data Collector has a memory leak.


Cisco CallManager incorrectly lists the directory number that is assigned to a CTI route point as the original called party on calls that are forwarded from the CTI route point.


Blind transfer to a phone on a MGCP Foreign Exchange Station (FXS) gateway does not work.


Cisco CallManager does not identify consult transfer or conference calls.


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


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


JTAPI does not receive a AddressInService event after a failover.


The language text in the advanced list appears garbled when Cisco Telephony Service Provider (TSP) is used with a Japanese OS.


Call Dependent Call Control (CDCC) has a memory leak that is caused by late CRCX Ack messages.


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


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


Cisco CallManager does not send the announcement from PSTN when a user dials a nonexisting number and the Cisco CallManager server is configured with overlap sending.


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


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


Phone continues to ring after the user picks up the handset.


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


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


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


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


Call Forward No Answer (CFNA) to a cell phone does not work with fast start.


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


Transfer failures to agent devices occurs because of CTIERR_TIMEOUT.


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


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


Cisco CallManager server restarts when it processes a call with a route pattern !@.


Phone does not reject attempts by Cisco CallManager to barge into a G.729 call.


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


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


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


Fast dials fail when they are configured in the German or Spanish Cisco CallManager User page.


CTI application cannot recover call.


Caller remained on hold because connected message was not received.


JTAPI sends an unknown destination handle in the NetworkReachedEv and NetworkAlertingEv message.


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


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


CTI applications do not get sent information about QuietCleared calls.


CallInvalidEv does not get sent when a redirected conference call goes into an idle state.


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


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


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


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


Registration fails when the Cisco CallManager server uses a H.323 ID as its IP address when it registers with a central gatekeeper.


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


Cisco CallManager does not send a H.225 release complete message to the gateway when the IP phone goes on hook.


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


TAPI application fails in retrieving a call on hold.


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


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


Second line goes off hook on the phone.


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


Corporate directory search returns more than 64 entries.


Handle leaks occur when H.323 calls are connecting.


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


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


You cannot instantiate CiscoJtapiVersion class by using JDK 1.4.


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


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


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


Cisco CallManager server has a memory leak when a gatekeeper is used.


Location counters on Cisco CallManager servers in a cluster get out of synchronization.


Fault response for invalid content type has typographical error in the XML tag.


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


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


CPU usage goes to 100 percent when a call that is put on hold gets dropped.


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


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


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


Thread Deadlocks result in events not being reported to applications.


Cisco CallManager region information does not get updated in the Real-Time Information Server.


DeviceOpen fails after a CTI manager failover.


Cisco CallManager server restarts when it cannot open the Signal Distribution Layer (SDL) index file.


JTAPI installation causes Classpath corruption.


A transferred call to a Net Vision phone in Skinny Client Control Protocol (SCCP) mode does not ring.


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


JTAPI causes a No Idle Trunk condition in Cisco Internet Protocol Interactive Voice Response (IP IVR) and Cisco Intelligent Contact Management (ICM) calls to fail.


Cisco IP Phone does not display the 24th digit of a DN on a received call.


Cisco CallManager does not release entry in locations table.


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


Cisco CallManager server restarts with a StationOutputSetRinger exception.


Call forward all does not work properly when a peer is taken off the network.


Two Cisco CallManager servers generated the same random number for an intercluster trunk (ICT) call.


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


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


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


JTAPI does not check CTI error code for incorrect media.


JTAPI does not check CTI error code for incorrect media.


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


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


StationOutputSetRinger signal sends corrupt data.


Devices cannot register after the Cisco CallManager server restarted.


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


TFTP rebuilds all files when the administrator enables extension mobility from the phone device page for a phone that is currently not enabled.


CTI rejected request to play invalid dual-tone multifrequency (DTMF) signal.


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


The Call Forward No Answer (CFNA) parameter cannot be used to signal a voice-mail failure when advanced linear hunting is used.


Cisco CallManager server generated a DBL exception error while upgrading from Release 3.2(2c) ES 11 to ES 14.


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


Call Forward No Answer (CFNA) fails when users with shared-line appearances updated fast dials.


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


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


Locations entries do not get deleted under certain scenarios.


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


Blind transfers from a Cisco Unity server to a Cisco IP Integrated Contact Distribution (ICD) route point fail due to an assertion failure in the JTAPI client.


Transfer fails after an agent conferences the Voice Response Unit (VRU).


TSP does not allow hostname with more than two dots.


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


CTI returns TimeoutException with a CTIFAILURE.UNRECOGNIZABLE_PDU.


TSP sends incorrect LINEADDRESSCAPS fields.


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


Route point failover does not work.


Administrator gets an error message when a valid line text label is added.


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


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


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


Cisco CallManager sends improper responses to ConfigStatRequest and ServerRequest messages.


DwCallFeatures for disconnected call does not display the drop status.


Setup transfer on a disconnected call fails. This results in an invalid call status.


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


Cisco CallManager crashes when MaxStationInitPerSecond is set to zero.


Call gets disconnected when group pickup fails.


JTAPI does not send RouteEvent when the same call is presented again.


Agent gets a device is busy message.


Cisco CallManager ignores the VoiceMailMaximumHopCount service parameter.


Calls from a CTI application fail.


Calls do not ring on all shared lines.


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


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


Database failback does not always work.


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


Cisco CallManager has a memory leak when a Primary Rate Interface (PRI) call is parked and retrieved on a different node.


CTI needs to check index before accessing mCtiLineHandleList.


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


Cisco CallManager returns blind transfers to Cisco Unity.


Call Forward Busy (CFB) forwards call one more hop than the Forward Maximum Hop Count.


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


Cisco CallManager Release 3.2(2c)spE installation hangs.


Calls fail on devices where speaker phone and auto answer is disabled on a line.


You cannot stop Cisco CallManager service after CCM trace file generation is disabled.


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


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


Shared line stops ringing when another line goes on or off hook.


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


Cisco CallManager and CTI manager have missing trace information.


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


Cisco CallManager decrements location bandwidth incorrectly for Global System for Mobile Communications (GSM) codec.


Cisco CallManager service restarted due to SdlNetworkService thread access violation.


Cisco CallManager disconnected a call when it received a progress indicator (PI)=8.


Transfer and conference softkeys do not work when you attempt to transfer a call the second time.


CPU usage goes to 100 percent when you access the script authenticate.asp in CCMCIP.


Calls to CTI route point fail after a failover.


The default state for SDLtrace flag for CTIManager gets set to false.


Intercluster calls fail when the media fails setup.


LineOpen fails when the caller hangs up before lineUnhold completes.


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


IPC connection fails when Active Directory plugin is running.


IP phone resets when you set or remove call forward all in the CCMuser page.


DC directory installation does not clean up obsolete profiles in the DC Directory Administration.


WS-6608 PRI gateway uses the wrong Pulse Code Modulation (PCM) type after a failover.


Call forwarding fails intermittently.


The reconfig_cluster.pl script does not wait for DC Directory (DCD) to stop on the subscriber servers.


The reconfig_cluster.pl script fails when it encounters a stopped DCD service on a subscriber server.


The reconfig_cluster.pl script fails when the PERLLIB environment variable does not get set.


Cisco IP Phone 7960 locks up when heavy network traffic exists.


Transcoder does not get allocated on a G.723 call through a Cisco VG200 gateway.


DN gets orphaned when you change the directory number for a profile.


Call Park reversion does not work when the phone has been configure to forward all calls to the meetme number.


CTI retrieve request fails.


Call Dependent Call Control (CDCC) process has a memory leak that bandwidth for locations not being returned causes.


Phones display To CallManager when there is not enough bandwidth available for a conference call.


DTMF Relay fails when the source and destination endpoints are the same.


Phones take up to 40 minutes to register when you reset the phone in Default Voice Mail Profile.


Conference fails when you resume a consult call after you put it on hold.


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


The wrong call information displays when a phone has forward no answer (FNA) set to a CTI route point.


LineNegotiateExtVersion fails when another application opens a device.


NetMeeting has no audio path when it is configured as a shared line.


JTAPI sent the wrong callControl cause for a blind transfer.


You cannot delete a user in Cisco CallManager Release 3.2(2c) ES23.


IP phone displays a garbage character prior to displaying the name of the caller in a H.225 call.


JTAPI sends a false Cisco Start Conference Event.


You cannot delete a DCD user in Cisco CallManager Release 3.2(2c) ES23.


You can add or update an incorrect value in the DNS/IP Address field.


You cannot use a shared line on a phone when the required bandwidth between the two locations is not available.


You cannot enable call forward all on a phone that is registered with a subscriber server.


You can set incorrect values in Service Parameters.


Agent cannot complete a conference because of a missing CiscoConferenceEnd event.


DCD Server service reports a memory page allocation failure in base replication.


Cisco CallManager server failed when SDL process stopped.


Agent device did not receive a TermConnDroppedEv for a consult call from the CTI port.


Conference ID displays on the phone when CFNA is enabled.


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


Device.EnumerateLines() changes when lines are changed on devices.


Agent cannot log in because of PlatformExceptionImpl.


You cannot resume a hold call on a shared line when there insufficient bandwidth exists between the two locations.


When Cisco CallManager servers are restarted, the first meet-me conference call across the servers in a cluster fails.


Transfer and hold with MTP enabled on a H.323 gateway does not work.


Updates fail when the database has a false failover.


Directory plugin does not work properly.


Call reappears at redirecting address when call forward busy (CFB) is enabled.


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


You cannot use the answer softkey to answer a second incoming call.


Cisco CallManager does not support Q931 Progress Indicator (PI) Information Element (IE) in a Notify message.


The names for dwCalledID and RedirectingID do not display on a forward all call.


Call detail record (CDR) process grabs memory when CDR purging fails.


Cisco CallManager does not send Call State 12 (Call Proceeding) when T.302 timer expires.


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


CTI Manager process fails which causes lines on application to go out of service.


You cannot generate department bill reports in PDF format when there are more than 5000 users.


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


Calls from a DMS250 switch fail.


You can only use the general tab in Cisco IP PBX Service Provider when you change languages on a Microsoft Windows 95 or Microsoft Windows 98 machine.


The conference softkey does not get activated when there is a second call on the conference controller DN.


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


Directory change notification with LINE_REMOVE event get sent every 20 seconds when multiple DN for a user is deleted.


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


Changing the SilenceSuppressionWithGateways and SilenceSuppressionSystemWide service parameters from false to true on the WS-X6608 T1 does not work.


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


Cisco CallManager server restarts when calling party information is changed on gateway.


Transfer softkey becomes unusable when there is a failed hold and resume call.


CDCC has a memory leak when all nodes in a cluster are not online.


TSP name in TSP substring of ProviderServerInfo string is incorrect.


Setting a value of 1 or 2 for MaxMeetMeConferenceUnicast does not work.


You cannot add an incoming call to a conference if you did not initiate the conference.


Users cannot answer a phone with a shared line when the other shared line phone is disconnected from the network.


Transferred call remains active after a consult transfer.


Agent gets left in a held state with a call in the CTI agent application for Cisco IP Contact Center (IPCC) after transferring a call to the Cisco IP Interactive Voice Response.


Cisco CallManager server assigns the same port number to the submodules for NM-HDA module.


Phone played the inside ring on an outside call.


Entries of user locales disappear when you click the cancel button.


When you press the conference softkey on a phone, users on the other line receive a dial tone.


Call back notification does not get sent in a connected call scenario.


The performance monitor counter does not display 0 CallsInProgress due to a leak in the CDCC process with PSTN transfers.


You can insert a H.323 gateway without entering a value in the Num Digits field.


The PRI SETUP message has a missing Redirected dialed number identification service (RDNIS) value when a call is forwarded to voice mail.


Cisco CallManager administration does not display all registered route points.


An IP phone displays local time in the Greenwich Mean Time time zone when you reset a phone that is configured for Athens time zone.


Cisco CallManager server does not handle the database timer when the forwardmanager process is trying to read the forwarding information from the database.


JTAPI does not send a CallCtlConnInitiatedEv or DialingEv message.


You cannot initiate a conference while another phone is in the process of starting a conference.


Call park reversion of a conference call fails when the phone has call forward no answer (CFNA)enabled.


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


Application loses track of a call that is transferred by operator.


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


Cisco CallManager server sends invalid MGCP endpoint ID to FXO ports.


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


Out of provider party does not receive connect events.


CDR Analysis and Reporting (CAR) registry does not have a company name field.


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


CAUSE_CONFERENCE gets sent when an unobserved party from a conference call disconnects.


Route point fails to redirect a consult call that was redirected from a CTI port.


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


OS Upgrade 2000.2.3 Phase 3 did not execute.


Unanswered parked call does not get reversed.


Allocated bandwidth gets released in a blind conference call with phones in different locations.


Uninstall fails, and system switches to in-use mode.


CCMUser web page does not display CTI route point as an associated device.


Cisco CallManager subscriber server fails.


Auto answer gets triggered on a IP phone during a ringout


On a fresh installation, Cisco CallManager does not support VGC endpoint in System/Device Defaults/


Bandwidth does not get released for a park reversion call that was on hold.


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


Calling lineMonitorDigits with dwMonitorMode = 0 fails.


Service parameters accept the wrong values.


Users in a conference hear the voice mail of a dropped party.


CTI route point does not start after a Peripheral Gateway (PG) user is added.


A partition without a name gets inserted in the database.


The Enterprise Parameters and Service Parameters web pages in Cisco CallManager Administration do not display the database content.


You cannot resume a call from a shared line when a conference attempt fails.


JTAPI client does not reinitialize the phone profile after an extension mobility logout.


Cisco CallManager has high CPU usage when you place a call to the pilot point.


Intercept table does not get updated when the forwarding change notification from the database is out of sequence.


CTI manager ignores the exception thrown by CTI device list.


Cisco CallManager sends out two disengage request (DRQ) message when the primary Cisco CallManager fails over.


Cisco CallManager displays error message when you remove a clause from a route filter with only one clause.


CallEvent for held call did not get sent.


Real-Time Monitoring Tool (RTMT) directory monitoring has a memory leak.


The default value for the initialization timer on Cisco CallManager server is too small.


Cisco CallManager has high CPU usage when user accesses Lightweight Directory Access Protocol (LDAP) search.


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


The voice-mail profile does not scale when directory numbers are configured.


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


The DN for Cisco IP Phone 30VIP does not get printed correctly.


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


No ConnConnectedEvent or CallControlEstablishedEv gets sent when a call is redirected from a DN to the same DN.


CTI Manager process fails which causes the IPCC system to go out of service.


Bandwidth does not get released when one party is on hold in a conference.


Parking a call on hold takes 8 seconds.


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


You cannot add a call to a conference on a shared line when the conference call is on hold.


Cisco CallManager sends a Modify Connection (MDCX) message without a Create Connection (CRCX) message when it receives a PROGRESS message on the B side.


Cisco CallManager server does not release the bandwidth for phones that are placed on hold and registered to the subscriber server when the call ends.


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


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


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


Call pickup fails in a certain scenario.


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


Cisco CallManager does not send a CONNECT ACK message when route group or route list is used.


Phones do not register when you upgrade from Cisco CallManager Release 3.1(4b)SPC to 3.2(2c)SPF.


Cisco CallManager cannot CFA to a cell phone in Japan.


JTAPI does not handle events properly when CFwdAll key is pressed.


Phones with a shared line have inconsistent behavior on incoming calls.


The timeDataInfo field of the StationDefineTimeDate message does not get enumerated in the Cisco CallManager trace file.


The conference softkey does not activate when you invite H.323 endpoints into an Ad Hoc conference.


Call pickup answers an existing call.


TAPI application receives a LINEERR_BADDEVICEID error on a lineOpen.


Cisco CallManager has a locations bandwidth leak on conference calls.


Find and List Route Patterns fails to return matching record when an exact search is done.


Cisco CallManager User login fails when Active Directory is used.


Call gets dropped when you try to resume a call from a shared-line endpoint.


User information gets duplicated in Active Directory and Microsoft Exchange when adding user to Cisco CallManager phone address book.


Music On Hold (MOH) Server gets updated without a Device Pool.


IOS MGCP FXS can resume held call from shareline IP phone.


Cisco CallManager does not release bandwidths on a park reversion G.729 call in a cluster.


Call does not get forwarded to voice mail when application fails.


Subscriber servers do not get configured when reconfig_cluster.cmd script is run.


Controller drops the conference when the RmLstC softkey is pressed.


Users cannot initiate a conference when they drop out of a conference.


The Voice Mail Port wizard throws a COM error when invalid Pilot DN is entered.


MaxMeetMeConference parameter does not work for parked conferences.


CAR cannot access the LDAP directory when the DCD password is changed.


You cannot transfer MGCP FXO calls.


Enabling and disabling CFA does not work.


Cisco CallManager does not delete all the ports when you change VG248 Installed Ports to None.


Phone does not ring when you set CFNA to the second line of the phone.


User cannot complete a conference call when a peripheral gateway fails over and the consult call has not been answered.


T1 configuration page does not work when you use a Netscape browser.


Cisco CallManager server crashes due to an out-of-bound array.


CDCC has a location bandwidth leak.


Park reversion fails when call forward all is enabled.


Route Plan wizard displays an HTTP Error when you use a long tenant name.


Device register table gets out of synchronization.


Phone does not go on hook when you press CFA and then you press pick up.


Certain search criteria return erroneous user information.


You cannot reset a Cisco Catalyst 6500 Communication Media Module gateway when you use a long domain name.


Phone speaker does not work when you resume a call after a failed barged call.


Cisco CallManager service restarts due to an invalid line instance in StationSoftkeyEvent.


The backup utility fails to install when a newer version on the server exists.


CtftpChangeNotify dll has a WSAEMSGSIZE socket error.


The getUserIDForDeviceName method uses initial User Search Attribute.


The timerListIndex in SdlTimers can contain negative value.


User gets on device associated with your user id error message after Cisco CallManager server was upgraded to Release 3.2(2c).


Pilot points do not work when multiple servers go down.


Cisco CallManager does not send a H.225 disconnect message when IP connectivity to the Originating GW (OGW) goes down.


CPU usage goes up when Cisco CallManager server does not receive a No MGCP-MGCP cause from the Cisco Catalyst 6500 Communication Media Module gateway


A query to ldapDetails.asp returns no data.


Phones do not display To Conference when you call a meet me conference through a WS-6608 E1 gateway.


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


Phones with shared line behaves inconsistently.


TsConnected message gets sent after TsOnHook when you resume a call.

This release also resolves the following firmware caveats.


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


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


Cisco IP Phone 7960 speakerphone does not operate properly.


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


D-Channel does not come back up after Cisco CallManager sends a reset to the 6608 E1.


Transfer key does not display when dialed number is chosen from directory.


Audio volume level fluctuates during a call.


A Cisco IP Phone 7960 does not clear the idle URL when a call is initiated from CTI call control and the headset key is active.


The fourth call between two IP phones that have two lines each does not connect when you dial by using the dial softkey.


Out-of-order packets cannot be reassembled.


AXL restart request causes IP phone to reset.


IP phone resets when it receives messages URL with special characters.


Cisco IP Phone 7960 displays "Ringer Is Busy!" error message.


You cannot resume a call on shared line when another call comes in.


Volume level does not always get saved when there are two active calls on one line.


Phone experiences one-way audio that is caused by unicast packets that are sent to the PC that is attached to the phone.


Phones take up to 8 seconds to get dial tone after regaining network connectivity.


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


FXS blade does not send dial tone to phone.


Phone may take up to 13 minutes to obtain phone firmware.


Total digits and directory placed call digits allowed do not match.


Phone dials displaying digits when you answer an incoming call while viewing your missed calls.


Scripts do not work on phones with firmware release P00303030009.


You cannot edit DN in the directories screen.


The volume level on an IP phone fluctuates on a phone call.


Cisco IP phones continue to display the last message.


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


Cisco CallManager sends unknown Destination Type in the Proceeding event.


Phone resets when you do a directory search on a Cisco IP Phone 7940 and no matching records exist.


Cisco IP Phone 7910 displays incorrect text.


Music on hold has location bandwidth leak.


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


WS-6608 sends the wrong payload type for fax-relay switchovers.


Phones do not register to their primary Cisco CallManager server when the service is restored to the server.


Cisco IP Phone resets when line rate traffic is sent from the PC port of the phone.


The link state of the expansion module goes to idle state when you upgrade or downgrade the firmware.


You receive loud static when you answer a G.729 call on a Cisco IP Phone 7960 speaker.


Ports on the WS-X6608 do not work after upgrade to firmware version D004030145S1 occurs.


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


Call progression debug message displays the wrong CP Tone value.


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


The DSP on the WS-6624 and WS-6608 crash when you configure the port only for fax support.


Fax transmissions fail between a fax that is connected to a WS-6624 and a fax machine on the PSTN via a WS-6608.


Phone displays HTTP Error [8] message when you enter a new search after aborting a previous search.


IP phones do not play the DTMF tone when tone is sent through a WS-6608 gateway on a T1 line.


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


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


The answer softkey displays when you use onhook dialing.


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


The German translation for the Edit Dial screen has the wrong syntax.


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


User does not receive the offhook tone when the user is in the missed calls directory and no calls are listed.


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


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


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


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


Phone plays a fast busy signal on calls from a WS-6624.


A WS-6608 with T1 CAS cannot send more than 21 digits.


Phone remains in Survivable Remote Site Telephony (SRST) mode when Domain Name System (DNS) on the primary Cisco CallManager server cannot be resolved.

Open Caveats for Cisco CallManager - Release 3.2(3)

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

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

Table 2 Open Caveats for Cisco CallManager Release 3.2(3) 





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

Svchost.exe has a memory leak of approximately 8Kbytes in svchost.exe when a TAPI application starts up and then shutdowns. There is an additional memory leak of approximately 4 Kbytes when Cisco TSP is installed. This is cause by the COM object initialization routine that is performed by Cisco TSP when it uses the TAPI wave driver.


For client based applications such as Cisco SoftPhone, a memory leak of 12Kbytes does not get notice, since the PC or laptop gets shut down on a regular basis. Shutting down the machine cleans up the memory.

For server based applications which typically do not get shut down, avoid restarting an application without restarting the server.

In the scenario where you have a PC on throughout the year and you start and stop an application 3-4 times a day, the unreleased memory increases to 13-18MB total per year. To free the unreleased memory, restart svchost.exe when the application is not running or restart the PC.


The response time is slow for a lineAnswer() request for a CTI port.

Workaround: None exists.


Cisco IP Phone 7940 does not allow a second line when a user logs in using extension mobility.

Workaround: None exists.


You cannot update calling search space after you change the selected partitions

Workaround: Delete the Calling Search Space and insert a new one.


Service Configuration Tool gives timeout error.

Cisco Configuration manager (service install/remove) functionality acts intermittently. Executing config.exe is problematic (it works some times, and it is hard to maintain).

Workaround: Use install CD or web download to add services. (In future release, this function will be added to a separate web page.)


If a transcoder is used, no audio path exists.

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

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

Workaround: None exists.


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

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

Workaround: None exists.


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


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

2. The second way to solve this problem is to restart the IIS service.


Searching the phone directory with an empty parameter in the name field causes an error.

Workaround: None exists.


Call Park stops working for some call park extensions.

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

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

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


No ringback occurs on call transfers to a phone that is attached to a FXS module.

Workaround: None exists.


CTI ignores indicator and displays number instead of displaying Private.

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

Workaround: None exists.


DBLX does not parse some non-English characters properly.

Unlike DC Directory, Active Directory can store non-English characters in the first and last name field for users. When Cisco CallManager is integrated with Active directory by using AD plugin, the corporate directory search returns "?" for some non-English (single byte) characters on the XML pages.

Workaround: None exists.


Definition for BaudRate and DataBits in CMI service needs to be modified.

The definition for Cisco Messaging Interface Parameters indicates that Databits and BaudRate are defined as the same. Baudrate usually refers to speed whereas DataBits also refers to size.

Workaround: None exists.


Calls that are associated with a device that specifies Media Termination Point (MTP) Required in the device configuration page connect with no MTP when there are no more MTP resources.

Supplementary services do not work when there are no MTP resources.

Workaround: None exists.


Calls got lost when Cisco CallManager and Cisco Catalyst 6000 got out of synchronization.

Workaround: None exists.


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

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

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


Extension mobility multi-login behavior does not work properly.

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

Workaround: None exists.


User gets an error if the user did not apply the settings for Backup and Restore utility during the initial installation.

The user cannot configure backup and restore settings when the user presses the cancel button on the settings screen during the initial installation of Cisco CallManager.

Workaround: Run the local file _stibacksetup.exe to configure the settings.


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

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


You cannot search for a user with a digit in the name fields from CCMUser page.

Workaround: Search for the user on the Cisco IP Phone.


Cisco CallManager server sends Simplified Message Desk Interface (SMDI) packets with zeros for an unknown calling party when the Cisco Messaging Interface (CMI) service Parameter UseZeroForUnknownDn is disabled.

Workaround: None exists.


Cisco CallManager service restarted due to corrupted data after a destructor was sent.

Workaround: None exists.


Internationally forwarded voice mail traversing a gateway to a PBX fails to route locally.

Calls from an international Octel voice-mail system and forwarded to another Octel mailbox failed.

Workaround: Use the following firmware on the Cisco Catalyst 6000 24 Port FXS Analog Interface Module:

App: A00203010014

DSP: A003F031


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

Workaround: None exists.


The SQLSvc account does not get created during installation.

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

Workaround: Three options exist:

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

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

3. Remove the Cisco CallManager from the Windows domain.


User did not get an error when SQL Replication failed during an upgrade.

The new CCM03XX database did not get created, and the Cisco CallManager server does not work. The C:\DBConvert.log file displays the following lines:

CDataConverter::ProcessScript Error 1205, [Microsoft][ODBC SQL Server Driver][SQL Server]Your transaction (process ID #59) was deadlocked with another process and has been chosen as the deadlock victim. Rerun your transaction.

Workaround: Go back to the backup version and rerun the upgrade. Make sure that all passwords for the administrator and sqlsvc users are synchronized and that name resolution is correct. To ensure proper name resolution, use hosts and LMHOSTS files on all the nodes in the cluster.


Control Center reports errors on subscriber server connectivity

Workaround: None exists.


Installation on subscriber server fails because pull subscriptions from the publisher server failed.

Workaround: Start the installation on the subscriber server again with the first CD.


IP phone does not display the dialed number.

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

Workaround: None exists.


The CCM.EXE process did not get CPU cycles when the hard drive failed.

Workaround: None exists.


Cisco CallManager allows an uninstalled TFTP Service to be inserted.

Workaround: None exists.


Cisco CallManager allows a user to disable extension mobility without logging out first.

This leaves the phone in the EM mode.

Workaround: Delete the phone from the database and let it auto-register. The phone configuration will be lost.


Upgrading to Cisco CallManager Release 3.2(2c) fails when the SQLSvc NT account gets locked out due to a lockout policy on the domain controller.

A "Ikernel.exe - Application Error" message displays during a Cisco CallManager server upgrade. Click OK to terminate the program.

Workaround: Set your domain security policy such that the Cisco CallManager servers will not lock out an account due to failed login attempts and then rerun the upgrade, preferably starting from a known good backup because, after Ikernel.exe crashes, the system remains in an unknown state.

To ensure that the upgrade completes successfully, you must disable any security policies that cause the SQLSvc account to lock. If the Cisco CallManager server exists in a domain, you must disable the Domain Security Policies on the server that acts as the Domain Controller. You also must disable the Local Security Policies on the local Cisco CallManager server(s), even if the server does not exist in a domain.

For detail information on how to perform these tasks, refer to Upgrading Cisco CallManager Release 3.2(2c).

Caution Disabling the security policies makes any server in the domain vulnerable to attacks. Immediately after you upgrade every server in the cluster, re-enable security policies.


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

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

Workaround: None exists.


Cisco Extension Mobility Logout service does not get installed when you upgrade Cisco CallManager to Release 3.2(2c).

Workaround: From the command prompt, enter C:\Program Files\Cisco\bin\LogoutService\Install

Change service startup type from manual to automatic and start Cisco logout service.


You cannot add subscriber servers to a cluster.

Workaround: None exists.


Event log errors reference previous Cisco CallManager database.

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

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


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

This situation occurs in the follow scenario:

phA - CSS01 Dirn - RPART01

phB - CSS01 Dirn - RPART01

phC - CSS02 Dirn - RPART02








8000 / RPART01

8000 / RPART02

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

Workaround: Configure different callpark numbers for different partitions.


Netmeeting calls get dropped when the IP voice media streaming application is restarted.

Workaround: None exists.


Corporate Directory does not get displayed on Cisco IP Phone 7940 or 7960.

Workaround: Rename the global.asa file located in directory c:\ciscowebs\ipphoneservices\ccmcip.


Call pickup fails with blind conference calls.

Workaround: None exists.


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

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

Workaround: None exists.


Cisco CallManager server does not recover its ports or TCP sockets after correcting a H.323 Routing Loop configuration.

This occurs when you create a route loop that crosses two or three clusters with H.323 intercluster trunk (ICT).

Workaround: Reboot every Cisco CallManager server in all the clusters.


Cisco CallManager needs to manage H.323 routing loops.

Resources are used up when a route loop across a large H.323 ICT cluster-to-cluster configuration (Route Pattern, Route List and a Route Group with 6 H.323 ICTs) is created.

Workaround: Do not create routing loops.


CTI Framework user displays when you do a corporate directory search.

Workaround: None exists.


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

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

Workaround: Update and reset the phone.


Calls disconnect when you make toll-free calls from an IP phone that is configured to display name.

This happens when Cisco CallManager server receives a display IE cause status message.

Workaround: Disable name display on the phone lines or disable Display IE on the gateway.


A malformed XML rule causes errors in the database installation.

Workaround: None exists.


Call forward all to a PSTN endpoint through a Cisco VG200 H.323 gateway fails.

Call from the PSTN to an IP phone with CFA out to a PSTN phone failed to connect.

Workaround: None exists.


Cisco CallManager rules cause gateway errors in the database.

This occurred on Release 3.2(2c)spF.

Workaround: None exists.


Perfmon does not count hardware Media Termination Point (MTP) session in MediaTerminationPointsResourceActive.

Workaround: None exists.


The reset devices button on Directory Number Configuration page does not work.

Workaround: None exists.


The MaxForwardstoDN parameter does not get updated

Workaround: None exists.


Searches for Phones, Gateways, CTI Routepoints, Route Patterns, Partitions, CSS, Route Group, Route List, Route Filter or Translation Pattern with underscore in the search field return default search results.

This situation does not happen when you choose 'is exactly' option.

Workaround: None exists.


Transcoder resource gets allocated for an IP phone in a G. 729 ICT Call between a Cisco IP Phone 12 SP + and a Cisco IP 7900 series phone.

This happens when you set up a ICT between two clusters that are using G.729 on both sides. The transcoder is placed in the Media Resource Group. When you make a call from Cisco IP Phone 12 SP + to the Cisco IP 7900 series phone, a transcoder is used for the Cisco IP Phone 12 SP +, and another transcoder is used for the Cisco IP 7900 series phone.

Workaround: None exists.


Cisco CallManager server sends Simplified Message Desk Interface (SMDI) packets with zeros for an unknown calling party when the Cisco Messaging Interface (CMI) service Parameter UseZeroForUnknownDn is disabled.

Workaround: None exists.


IP phone fails to connect second FXO phone to an adhoc conference.

This occurred on a MGCP gateway with FXO port that is using ground start.

Workaround: None exists.


The gateway .cnf file does not get updated when you delete its endpoint.

Workaround: Update the gateway on the Gateway Configuration page in Cisco CallManager Administration. This forces TFTP to rebuild the .cnf file.


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

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

Workaround: None exists.


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

Workaround: None exists.


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

Workaround: None exists.


User received dial tone while switching between two occupied shared lines.

PhoneB has a shared line with PhoneC. Make a call from PhoneA to the second line on PhoneB. Make a call from PhoneD to PhoneB's first line. Pick it up on PhoneC.

When you switch between the lines on phone C, you receive a dial tone.

Workaround: Press the EndCall softkey and resume the call on the second line.


You cannot use hook flash to transfer a call on a MGCP FXS Phone on a CiscoVG200 when the call is connected to a MOH server.

Workaround: None exists.


Data exceeds the amount of audio data being transmitted.

This situation occurs on a Cisco CallManager server that is using a fixed audio source for Music on Hold (MOH). Users receive a single skip every few hours.

Workaround: None exists.


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

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

Workaround: Do not use MTP.


The first line of an IP phone goes to the connected state when you go off hook on a second line.

Workaround: None exists.


You cannot add 100 Media Resource Groups (MRG) to a Media Resource Group List (MRGL).

User receives a "URL too long" error message.

Workaround: None exists.


Application does not receive call events after operating for several hours under heavy load.

This happens when the application receives data via RTP streams.

Workaround: Restart the machine that is running the application.


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

Workaround: None exists.


Phone stays in a ringing state after the call has been answered.

This situation occurs on Cisco CallManager Release 3.2(2) servers in a clustered environment with IP phones that are sharing lines.

Workaround: None exists.


IP phone with shared lines hangs when user gets a new call.

The shared line on a phone hangs when you resume a call after getting a new call. The two phones share a DN.

Workaround: Restart all the phones with shared lines.


Cisco CallManager does not allow blind transfers on conference calls.

Workaround: Use consult transfer to transfer the conference call.


JTAPI sends incorrect information in the transfer events on consult calls when you hold and resume a call.

JTAPI send incorrect information in CiscoTransferStartEv and CiscoTransferEndEv.

Workaround: None exists.


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

This happens during the second transfer.

Workaround: None exists.


Forwarding a phone fails because of a missing LINE_ADDRESSSTATE event state.

Workaround: None exists.


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

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


1. Access pages by using IP addresses.

2. Use Internet Explorer.


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


1. Access pages by using IP addresses.

2. Use Internet Explorer.


IP Phone Services respond to the NetworkConfigurationX request with the <ProxyServerURL> and <AuthenticationURL> elements in reversed order.

Workaround: Use the specified elements in reverse order.


IPCC Agents get logged out when the SDL link fails.

Workaround: None exists.


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

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

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


Anonymous user login fails after long period of inactivity.

Users cannot use the Services or Directories buttons on their phone.

Workaround: Restart of the IIS Service.


IP phone displays a blank screen when it gets a HTTP response, with a CiscoIPPhoneInput object and a refresh header that redirects the client to a different URL.

Workaround: None exists.


Softkeys continue to display on a new screen when you push CiscoIPPhoneExecute object to a phone that is displaying a CiscoIPPhoneInput object.

Workaround: None exists.


Forwarded name does not display on an IP phone when you CFA from a CTI RP.

Workaround: None exists.


Media termination point load sharing does not work.

Workaround: None exists.


You cannot pick up a parked call from ICT in the middle of a transfer.

Workaround: None exists.


Call Pickup and Group Call Pickup stop working.

This occurs on Cisco CallManager server Release 3.2(2c) sp F.

Workaround: In Directory Number Configuration,

1. Change the Call Pickup Group number to another DN numbers and press "Update" button.

2. Change it back to the old DN and press "Update" button.


The wrong codec gets used when you transfer calls from a intercluster trunk (ICT).

Configure phoneA in a G.711 region (within the region G.711) and phoneB in a G.729(within the region G.729). Set up the ICT in the same region as B. PhoneB calls a phone on the ICT. Transfer the call to phone A. The call uses G.729 codec instead of G.711.

Workaround: None exists.


Cisco CallManager disconnects H.323 calls when a third-party vendor sends an open logical channel ACK message.

Workaround: None exists.


Resume softkey does not activate when you disable the speaker on a phone with shared lines.

Workaround: None exists.


Cisco CallManager has timing conflicts between the interdigit timeout and the overlap sending and receiving timeout.

Workaround: None exists.


Cisco CallManager crashed during destruction of stationD object.

Workaround: None exists.


IP phone service redirects fail to expire.

This happens when IP phone service uses HTTP redirect response with an immediate expiration in the header.

Workaround: None exists.


DCX500.exe had a Microsoft Dr. Watson crash.

Workaround: None exists.


Publisher server stopped replicating data.

Workaround: None exists.


Error message displays when a Personal Address Book Search is done.

This occurs in the following scenario:

1. Go to PAB on the phone.

2. Search for a string or a name that does not match any entries.

3. You receive a message that no entries match the criteria.

4. Enter a new search.

You receive Error: -1:[Internal Error] Unknown User message.

Workaround: None exists.


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

Workaround: None exists.


Calls get forwarded to the wrong voice-mail system.

This happens in the following scenario:

Phone A and Phone B have voice-mail profile A, and Phone A is configured to forward all calls to voice mail.

The CTI route point for Cisco Personal Assistant has voice-mail profile B.

When Phone B calls A, the CTI route point intercepts the call and forwards it to the voice-mail pilot number that is associated with Profile B.

Workaround: Set the CTI route point for Cisco Personal Assistant to not use a voice-mail profile.


The Message Waiting Indication (MWI) lamp does not activate on the second line of an unregistered phone.

Workaround: None exists.


Bandwidth does not get used when you resume a call on a shared line.

This happens when a DN is shared across two Locations and MOH server is in NO LOCATION. You place the call on hold, and resume the call on a shared phone.

Workaround: None exists.


Users get an error when they upgrade Tool for Auto-Registered Phones Support (TAPS) by using Bulk Administration Tool (BAT) Version 4.3(1).

Users do not get an error when upgrading BAT.

Workaround: Uninstall BAT and TAPS before installing the application.


The TAPS log file displays inconsistent MAC address for device name.

Workaround: None exists.


Cisco CallManager does not have help information for the SRST reference in Device Pool Configuration.

Workaround: None exists.


MGCP DN changes does not take effect until the gateway or Cisco CallManager server is restarted.

Workaround: Reset the MGCP Gateway.


Error displays when you view modifications in the ADP Auto-Generated Device Profile line page.

1) In Cisco CallManager administration, open any registered phone.

2) Choose 'Enable Extension Mobility Feature' checkbox.

3) Choose <Use Current Device Settings> for Log Out Profile.

4) Click update and reset the phone.

5) Open the phone page.

6) Select ADPXXXXXXXXX page for any line. (The XXXXXXXXX are same as that of the line SEPXXXXXXXXX)

7) Make a modification and click update.

8) Click OK.

User receives an error that the current item is not valid and may have been deleted since the page was last refreshed.

Upon going to the phone page again and viewing the ADPXXXXXXXXX page, the changes that were made would be there.

Workaround: Access the phone by using the Cisco CallManager Administration


The log file for CCM0303 database gets full.

This occurred on a backup call processing subscriber node that is hosting the Cisco IP 7960 Phone and CTI registration for Cisco IP Contact Center (IPCC). The size of CCM030x_log.ldf file is more than 1GB.

Workaround: Back up the transaction log and then shrink the database.


DC Directory Server service fails to start waiting for journal process to complete.

This happens when the server gets powered off without a graceful shutdown of the operating system. The journal becomes corrupt and the transactions in the journal do not get committed to the directory.


1. Rename c:\dcdsrvr\run\dcx500\journal\JOURNAL.DAT to journal.old.

2. Start DC Directory Server Service.

3. Execute DCDREPCL TRIGGER ALL from the command line.

DCD pauses while this command executes. This can take up to 30 minutes when there are 10,000 users in the directory.


Lines go out of service and take a long time to go back in service when Cisco CallManager fails over.

An accumulation of timeouts in the database layer and the application layer can cause this situation. When the Cisco CallManager fails over from publisher server to a subscriber server, the database layer does not recognize this change until it receives a query. The client initialization can take up to 40 seconds for the database query to timeout before the database layer connects to the database on the subscriber. The application layer also times out while waiting for the initialization to complete during this interval. The application waits a set interval to reconnect. It can take up to 2 minutes to connect successfully.

Workaround: Increase the application ProviderOpenTimeout timeout to a minimum of 50 seconds. This will allow the first initialization to complete.


Cisco CallManager does not have help information for the SRST reference

Workaround: None exists.


Calls from NetMeeting application that is registered with the secondary Cisco CallManager server in a cluster fails when the gatekeeper is shut down.


1. Configure NetMeeting as a H. 323 gateway. Enable "Run H. 225D on All Nodes" flag in the H.323 gateway page for releases prior to 3.3.

2. Register NetMeeting with the Gatekeeper and do not configure NetMeeting in Cisco CallManager Administration.


Original consult call gets dropped when a conference call is aborted.

Workaround: Code should handle unexpected behavior.


IP phone cannot complete a transfer after redirect fails.

Workaround: None exists.


Cisco 7960 IP Phone cannot access intercluster trunk gateway when partitions and calling search spaces are not configured.

Workaround: None exists.


AD authentication fails when space in the user base container exists.

Workaround: None exists.


Users receives an error message when they configure Sub-Unit 0 after the module to a Cisco VG200 is changed.

Workaround: Reconfigure the slot by ignoring the messages.


Transcoder resources do not get released when phones are powered off.

This happens on calls that are made from phones with transcoders.

Workaround: Reset the transcoder.


Intercluster trunk (ICT) call park reversion from NetMeeting to a IP phone in a G.729 region fails.

This happens when the interregion codec between two clusters is set for G.729.

Workaround: Place both ICT trunks and NetMeeting in a G.711 region.


Multiline phone displays empty line for a conference call.

Workaround: Use the scroll button to move to the line, and the display gets corrected.


Phones with shared line do not display To Conference message.

This happens in the following scenario:

PhoneA - 2013

PhoneB - 88888

PhoneC - 88888

PhoneD - 2010

1. PhoneA calls 88888.

2. Pick up the call on PhoneB.

3. Start a conference on PhoneB and dial PhoneD.

4. Complete the conference

5. PhoneB displays "To Conference," but the display on the shared line on PhoneC does not.

Workaround: Resume the call on the shared line.


You cannot use Netscape to add a device hunt group member when the DN is in a partition other than none.

This occur when you use Netscape 4.79.

Workaround: Use Internet Explorer.


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

Workaround: Use a smaller Pilot DN.


MCS-7815 has memory timing issues.

MCS-7815-1000 servers with memory in Slot 1 and Slot 2 may crash.

Workaround: Move the memory into Slot 2 and Slot 3. Consult the diagram on the inside cover of the MCS-7815-1000 for the numbering of the DIMM slots.

You should always populate memory starting with slot (3) and work towards slot (1).

When you use the same size memory modules,

one DIMM - slot (3)

two DIMM - slot (3) and slot (2)

three DIMM - slot (3), slot (2), and slot (1)

When you use different size memory module, use the largest in slot (3) and then the next largest in slot (2).

Example: 512 MB - slot (3) and 256 MB in slot(2)


Call park reversion fails when you park a call from a meetme conference.

Workaround: None exists.


User do not receive tone on hold through a H.323 gateway.

Workaround: None exists.


Phone displays You Have VoiceMail message when MWI lamp is disabled.

The phone displays You Have VoiceMail message when any line on the phone has a voice-mail message, even when the MWI lamp policy is disabled.

Workaround: None exists.


User gets a COM error when an invalid character is used in the login user id field.

This happens when you add a new User Device Profile.

Workaround: Remove the invalid character and enter profile again.


Cisco CallManager establishes two conference controllers when you unpark a call from a subscriber server.

Workaround: None exists.


The shared line of a extension mobility phone does not get forwarded when the user is not logged in.

Workaround: None exists.


Administrators receive an error when they associate a route group to a route list without selecting a route group.

This happens when you use Netscape browser 4.79.

Workaround: Use Internet Explorer.


Cisco CallManager does not answer status enquires from a gatekeeper.

This causes the gatekeeper to disconnect the call.

Workaround: None exists.


The third party SQL trigger interrupts CDR data.

When you upgrade Cisco CallManager, the database name increments, such as CCM0300 to CCM0301. Third-party billing software has SQL triggers that are hard coded to the original database name. The trigger points to the old database name and causes all the CDR data to be written to the wrong directory on the publisher.

Workaround: Edit the trigger to point to the current name of the database.

You can find the trigger on the publisher server by Start > Programs > Microsoft SQL Server 7.0 > Enterprise Manager. Expand Microsoft SQL Servers. Expand SQL Server Group. Expand Local (machine name). Expand Databases.

Choose and expand the CDR database. Choose Tables and right click the entry on the window named CallDetailRecord> All Tasks > Manage Triggers. When you have more than one trigger, you can choose the desired trigger from the pulldown menu.

Copy the contents to a text editor and replace all instances of the previous name with the new name of the database. Copy the trigger back and check the syntax.


Calls forwarded to voice mail receive the unconditional greeting instead of busy greeting.

When the first voice-mail port gets unregistered, the originalCdpnRedirectReason gets set to 0 instead of 1. When the first voice-mail port gets registered, a call forward busy from a phone arrives at the first voice-mail port with call information of originalCdpnRedirectReason=1.

Workaround: Keep all voice-mail ports registered. When you unregister a port, change the forwarding information of the previous port to skip the unregistered port.


Internet Explorer crashed when you choose the gateway in the left panel on the CAR gateway utilization report.

Workaround: None exists.


CTI does not send switch information.

Workaround: None exists.


Call diagnostic data does not get generate for call leg that originated or terminated on the MGCP/PRI gateway.

Workaround: None exists.


Cisco Database layer monitor service does not start up when you reboot a Cisco CallManager server.

Cisco Database Layer monitor service stays in the "starting" state during the system reboot.

Workaround: Restart the service manually with the Component Services utility.


Call to a phone with Call Forward No Answer (CFNA) set to a busy DN with Call Forward Busy(CFB) fails

This occurs in the following scenario:

1. You have three phones A, B, and C.

2. Configure B for CFB to C and C for CFNA for to B.

3 Call B from A while B is busy.

4. The call gets routed A->B(Busy)->C (because of CFB).

5. Do not answer C. It should now go to Step 4 again because of CFNA, but CFNA to B fails, and the user receive the reorder tone.

Workaround: None exists.


Cisco CallManager does not send a second ring back call state event for a redirected call.

Workaround: None exists.


The Cisco IP Telephony Applications Backup Utility does not always get installed automatically.

This situation occurs on OS version 2000.2.3 on a MCS-7835-1000 server.

Workaround: Install the backup utility manually by running Setup.exe in the \Setups\Backup\ folder on the Cisco CallManager CD-ROM.


Cisco CallManager does not display an error when you unselect the enable multicast checkbox.

No error displays when you uncheck the enable Multicast check box in the Music On Hold Server configuration page when you have a audio sources configured to allow multicasting.

Workaround: Remove the 'Allow Multicasting' configuration manually from the audio source configuration page for MOH servers.


Users experience one way audio on outbound calls.

This situation occurs when you place a call to third party H.323 gateways and the Cisco CallManager server changes the mediaControlChannel's IP address and port number from is sent in the Open Logical Channel and the Open Logical Channel Ack.

Workaround: None exists.


Help points to a sample service file (sample.asp) that does not exist.

Workaround: Do not add the sample service.


DCD installation fails when the password for Microsoft Windows administration has special characters.

This occurs when the administration password uses one of these characters: \, ", %, and ^.

Workaround: None exists.


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

Workaround: None exists.


Cisco CallManager displays error message when you conduct an empty search for DCD users while adding users with the Bulk Administration Tool.

The following error message gets displayed: "Couldn't perform getUserInfo(null)Error getting all the UserInformation."

Workaround: Narrow the search criteria or search again after the users have been added.


A DBLX error gets displayed when you insert a route filter with a duplicate name.

Workaround: Use a unique name for the route filter.


You cannot delete or update a DCD user when the user ID uses a character with double quotes.

Workaround: None exists.


DCD installation on a subscriber fails when the password field has special characters.

Workaround: Do not use special characters in DCD password.


Cisco CallManager had SQL issues after adding a new subscriber server to a cluster.

You cannot access Cisco CallManager Administration on the subscriber and phones registered to the server cannot transfer or conference calls.

Workaround: Change the Default Network library for SQL7.0 from "Named Pipes" to "Multiprotocol." This parameter is found in MS SQL 7.0 ->Client Network Utility -> General.


Cisco CallManager allows administrators to enter special characters such as { ; and " to be in the SQL SA password field.

Installation on subscriber servers fail because the subscriber servers cannot authenticate with the publisher database.

Workaround: None exists.


Calls cannot be retrieved when you use [^0-9] as the call park number range.

Workaround: None exists.


Cisco CallManager displays error message when you search for a user with a user profileString DN with spaces.

This occurs when the user repository is in Microsoft Active Directory.

Workaround: None exists.


Changing AdvancedCallForwardHopFlag does not take effect until you restart Cisco CallManager service.

Workaround: None exists.


Cisco CallManager does not verify that m < n when you use a restricted pattern [m-n].

Workaround: Do not use a range with the type [m-n] where n<m.


Cisco IP IVR throws an exception error when you unsuccessfully resume a held call.

Workaround: None exists.


The Caller ID does not get displayed when the caller redirects the call.

Workaround: None exists.


Connection manager disconnects a call after it has been connected.

This occurs under the following scenario:


Cluster1--6608-e1---Meridian PBX--phoneA

IPphone2 configured to CFNA to phoneA.

When IPhone1 calls IPphone2, the IP phones display ringout to phoneA. PhoneA rings, but the call is disconnected.

Workaround: None exists.


Application did not get TermConnActive message after transferring a call.

Workaround: None exists.


IP phone loses Calling Search Space (CSS) configuration when the phone is reset.

This happens on a IP phone registered to a subscriber server.

Workaround: Register the IP phone on the publisher server OR reboot the subscriber server.


Cisco CallManager does not use the value in the T302 timer field for partial speed dials.

Workaround: Dial the digit within three seconds.


Cisco CallManager displays an error message when upgrading from Release 3.2(2c) to 3.2(3).

Cisco CallManager displays the error message halfway through the upgrade process. This situation occurs on systems that are running Entercept Intrusion Detection System(IDS) and is caused by Entercept IDS installing an incompatible SQL dynamic link library (DLL) file.


1. Disabled the installed IDS.

2. Delete the ntwdblib.dll file in the c:\winnt\system32 folder.

2. Download and install SQL7 SP4 from CCO at http://www.cisco.com/cgi-bin/tablebuild.pl/cmva-3des. This service patch installs a compatible SQL 7 DLL file.

Note You may need to reinstall SQL 7 SP 4 to replace the DLL file listed above.

3. Upgraded to Cisco CallManager Release 3.2(3).

4. Enable IDS.

5. Verify that the IDS agent still communicates and reports no errors to the IDS Console.


Second call fails when you configure Override Auto Answer If DisableSpeaker to be false and the speaker is disabled.

Workaround: None exists.


User receives ringback tone on a plain old telephone service (POTS) phone after the call is disconnected.

Workaround: End the call manually at the POTS phone.


VG248 ports do not automatically register with the Cisco CallManager server.

This happens on Cisco CallManager Release 3.2(2c) spG.


1. Manually register the gateway on the Cisco CallManager server.

2. Configure port 1.

3. Then select configure all ports like Port 1.


Agents receive one way audio.

Workaround: None exists.


Call gets dropped when an agent leaves the conference call.

Workaround: None exists.


Agent receive one way audio when media termination is enabled.

Workaround: Change the port number on CTIOS Media Phone.


Log file does not display final number when you use TAPS to auto-register phones.

Workaround: None exists.


GateKeeper controlled intercluster trunk (ICT) calls with zone prefix route always send admission confirmation (ACF) message.

Workaround: None exists.


The voice-mail partition is Case Sensitive.

Workaround: Update the partition to reflect the correct case and restart Cisco Messaging.


The numberPacketsLost in the Call Management Records (CMR) data stored in the CallDetailRecordDiagnostics table in Call Detail Record (CDR) displays a negative number.

Workaround: Interpret the raw binary number stored in SQL as an unsigned integer.


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

Workaround: None exists.


Cisco CallManager sends odd message timings with intercluster calls.

The sequence of operations that causes the problem:

1) Dial a number on a different cluster.

2) Put the intercluster call on hold.

3) Choose "New Call" and establish another call on the same cluster.

4) Put the intracluster call on hold.

5) Resume the intercluster call.

6) Choose "End Call" for the intercluster call.

7) Resume the intracluster call.

A minimal gap exists between stages 6 and 7 because the VG248 is faster than a human. The resume soft key is pressed very soon after the "TsOnHook" state message arrives for the intercluster call. The resumption of the intracluster call happens very quickly. A CloseReceiveChannel and a StopMediaTransmission message display as part of the teardown for the intercluster call. A StartMediaTransmission for the old call that contains the intercluster call recipient's IP address displays.

Workaround: None exists.


Speech path does not get created when you transfer a call from a H.323 network.

When a user attempts to transfer a call made from a Cisco H.323 Signaling Interface (HSI), the transferred call has no speech path because HSI can not handle the OpenLogicalChannelAck with RTP transport address set to "0". Cisco CallManager sets RTP transport address to "0" when the destination device is a Music on Hold server (MOH) server.

Workaround: Turn off the Music on Hold server.


An IP phone cannot transfer a Public Switched Telephone Network (PSTN) call to another PSTN phone through a Cisco H.323 Signaling Interface (HSI).

This occurred on a Cisco PGW 2200 Softswitch Release 2.3.2 patch 4.

Workaround: None exists.

The following firmware caveats apply to this release.


WS-X6608 does not automatically pick up the firmware load if the firmware was not available originally.

The firmware load initially was not copied to the correct location on the primary TFTP server. When the files are copied to the correct location, the WS-X6608 does not reset to pick up the files.


1.Use the command: 0 reset hard (Zero reset hard) on the Dick Tracy Utility. You will need to execute this command on every port.

2. Power down the module.


Double talk causes clipping on the near-end voice on the Cisco Catalyst 6000 8 Port Voice T1 and E1 port.

Workaround: None exists.


Fax calls fail when fax-relay and Error Correction Mode (ECM) are enabled on the WS-6624.

Workaround: Disable fax relay.


Phone gets stuck redirecting user to a web page.

This happens on a Cisco IP Phone 7960 when the user presses the services button and the services URL Enterprise Parameter is redirected to another URL. The phone displays the Redirecting message but never displays the services page.

Workaround: Change the services URL to point directly to the final web page instead of a web page that redirects to a second page.


User experienced bad audio signal on a ICT call between a Cisco IP Phone 12 SP + and a Cisco IP Phone 7900 series that is using G.729.

The Region Setting in the cluster with Cisco IP Phone 12SP+ was configured as follows:

RegA - RegB -> G729

RegA - RegA -> G711

RegB - RegB -> G711

Workaround: Set the Region Setting in cluster as follows:

RegA - RegB -> G729

RegA - RegA -> G711

RegB - RegB -> G711


You cannot configure the Cisco IP Phones not to send StationTimeDateReq at 00:00, 10:00, and 20:00.

Workaround: None exists.


Unicast URI (Uniform Resource Identifier) transmit fails.

This occurs in phone firmware version P0303020215.

Workaround: Use the previous version.


A Cisco 7935 IP Conference Phone cannot display more than nine characters.

Workaround: None exists.


Phone displays ± on calls through a Cisco DT-24+ digital gateway.

Workaround: None exists.


Cisco 7935 IP Conference Phone does not accept TFTP server name from the DHCP server.

Workaround: None exists.


Cisco IP Phones 7940 and 7960 do not guard against invalid timestamps in the G.729 RTP stream.

This occurs on Cisco IP Phones in G.729 region that are using G.711 to connect to Cisco Conference Connection (CCC) server.

Workaround: Use G.711 only.


Phone line icon gets distorted, and phone displays missed calls message after 65535 CFNAs between two phones.

Workaround: Reset Cisco CallManager.


Cisco IP Phone 7960 reboots when it receives an XML request.

This occurs when you access voice mail through the Cisco IP Phone Productivity Services (PPS) application.

Workaround: Use firmware versionP00303020100.

Documentation Updates

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


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

Cisco VG248 Analog Phone Gateway (VG248) Support

Cisco VG248 Analog Phone Gateway (VG248) enables you to integrate analog telephones, modems, and fax machines with the Cisco CallManager IP telephony system. Using version 1.1(1) or later of the VG248 software, you can now integrate legacy voice mail and PBX systems with Cisco CallManager by using Simplified Message Desk Interface (SMDI).

When using the VG248 with Cisco CallManager 3.2, you have access to the following new feature:

The addition of a VG248 gateway type allows you to add the device as a gateway to Cisco CallManager and to configure each port as VGC phone model. This consolidates each of the 48 analog or SMDI ports onto a single device. However, after you add the gateway and ports to Cisco CallManager, you still must configure these ports in the VG248 interface. An additional port, port 00[VMI], appears on the VG248 Gateway Configuration window. This port appears regardless whether you are using the VG248 to integrate analog or SMDI devices. However, the VG248 uses this port only when you are setting or clearing MWIs on phones that are using SMDI.

For details about using the VG248 for SMDI integration, refer to Chapter 5, "Integrating Cisco CallManager with Voice Mail Systems Using SMDI" in the Cisco VG248 Analog Phone Gateway Software Configuration Guide for details:


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


T1-CAS Connection Reference Removed

References for immediate start for T1-CAS connection (DT-24+) in the Cisco Access Digital Trunk Gateways DT-24+/DT30+ section of the Cisco CallManager System Guide were removed.

Procedure for Starting the Cisco Telephony Call Dispatcher

The Cisco WebAttendant Configuration section of the Cisco CallManager Administration Guide updates the following procedure.

Starting the Cisco Telephony Call Dispatcher

The Cisco Telephony Call Dispatcher (TCD) service starts running automatically when Cisco CallManager is started. The following procedure describes how to verify that the Cisco TCD service is running and how to start Cisco TCD if it is stopped.

Note If you add new attendant console users or modify the user information or password for an existing user, you must wait approximately 6 minutes for the changes to take effect.


Step 1 Choose Application > Cisco CallManager Serviceability.

Step 2 Choose Tools > Control Center.

Step 3 From the server list on the left side of the window, choose a Cisco CallManager server. The window refreshes.

The Service Name column lists all services that are configured on this server.

Step 4 Look at the Service Status column for the Cisco Telephony Call Dispatcher:

If an arrow icon displays, the Cisco TCD service is running.

If a square icon displays, the Cisco TCD service is stopped.

Step 5 If the Cisco TCD service is not running, click the Start button in the Service Control column.

Note The Cisco TCD service must have an Activation Status of Activated before you can start the service. For information on activating services, refer to the Cisco CallManager Serviceability Administration Guide.

Updated Service Parameters Configuration

The Service Parameters Configuration section of the Cisco CallManager Administration Guide updates the following procedure.

Service parameters for Cisco CallManager allow you to configure different services on selected servers. You can view a list of parameters and their descriptions, by clicking the i button in the upper, right corner of the Service Parameter Configuration window. You can view the list with a particular parameter at the top by clicking that parameter.

If you deactivate a service by using Cisco CallManager Serviceability, Cisco CallManager deletes any updated service parameter values. If you start the service again, Cisco CallManager sets the service parameters to the default values.

Note If you set a service parameter value to the suggested value that displays on the Service Parameters Configuration window and the suggested value changes in a subsequent Cisco CallManager release, the system automatically changes the parameter value to match the updated suggested value when you upgrade to that release. If you set a service parameter to a value other than the suggested value, the system does not change the parameter value when you upgrade.

Before You Begin

Ensure the following prerequisites are met before proceeding with the steps:

Make sure that servers are configured. See the "Server Configuration" section for more information.

Make sure that the service is activated. Refer to the Cisco CallManager Serviceability Administration Guide for more information.

Caution Some changes to service parameters may cause system failure. Cisco recommends that you do not make any changes to service parameters unless you fully understand the feature that you are changing or unless the Cisco Technical Assistance Center (TAC) specifies the changes.


Step 1 Choose Service > Service Parameters.

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

Step 3 From the Services drop-down list box, choose the service that contains the parameter that you want to update.

Note If the service that you want to configure does not appear in the drop-down list box, you must activate the service on the server by using Cisco CallManager Serviceability.

Step 4 Update the appropriate parameter value. To set all service parameters for this instance of the service to the default values, click the Set to Default button.

To view a list of parameters and their descriptions, click the i button in the upper, right corner of the window. To view the list with a particular parameter at the top, click that parameter in the Service Parameter Configuration window.

Note Some services contain service parameters that should rarely be changed. The Cisco CallManager Administration does not automatically display these parameters when you access the Service Parameter Configuration window. To view all parameters, click Advanced. After all parameters are displayed, you can redisplay the basic parameters by clicking Condensed.

Step 5 Click Update.

The window refreshes, and Cisco CallManager updates the service parameter with your changes.


You can temporarily change the language for the User Information window by choosing a different language in the "View page in" drop-down list box. Doing so only changes the language that displays for the current web session. The next time that you log into Cisco CallManager Administration, the User Information window will display in English.

You can use the 6-port T1 and E1 interface modules of the Cisco Catalyst 6000 AVVID Services Module to connect to PBXs or to the PSTN.

Obtaining Documentation

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

World Wide Web

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




Documentation CD-ROM

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

Ordering Documentation

Cisco documentation is available in the following ways:

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


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


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

Documentation Feedback

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

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

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

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

We appreciate your comments.

Obtaining Technical Assistance

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


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

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

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

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


Technical Assistance Center

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

Contacting TAC by Using the Cisco TAC Website

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


P3 and P4 level problems are defined as follows:

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

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

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

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


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


Contacting TAC by Telephone

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


P1 and P2 level problems are defined as follows:

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

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

[an error occurred while processing this directive]