Guest

Cisco Unified Communications Manager (CallManager)

Release Notes for Cisco CallManager Release 3.0(12)

 Feedback

Table Of Contents

Release Notes for Cisco CallManager Release 3.0(12)

Contents

Introduction

System Requirements

Determining the Software Version

Compatibility Matrix

Related Documentation

New and Changed Information

New Software Features for Release 3.0(12)

Important Notes

BIOS Update

Service Parameters

Service Parameter Restart Conditions

Cisco IP Phone 7910 and Cisco IP Phone 7940 Compatibility Issue

Computer Telephony Integration

BAT Reinstallation

Intercluster Trunk Configuration

Cisco CallManager Integration with Corporate LDAP Directories

Resolved Caveats

Resolved Caveats for Cisco CallManager Release 3.0(12)

Open Caveats

Open Caveats for Cisco CallManager Release 3.0(12)

Documentation Updates

New Service Parameters

Service Parameters

Server Name Change

Running Show Tech

Changes

Default Value Changed for SdlTraceTotalNumFiles Service Parameter

Omissions

Cisco CallManager Service Parameters

Cisco TFTP Service Parameters

Cisco Messaging Interface Service Parameters

Cisco IP Voice Media Streaming Service Parameters

Cisco Enterprise Service Parameters

Errors

Incorrect Name of MwiSearchSpace Service Parameter

Incorrect Definition for HoldType and ToneOnHoldTime

Obtaining Documentation

World Wide Web

Documentation CD-ROM

Ordering Documentation

Documentation Feedback

Obtaining Technical Assistance

Cisco.com

Technical Assistance Center

Contacting TAC by Using the Cisco TAC Website

Contacting TAC by Telephone


Release Notes for Cisco CallManager Release 3.0(12)


October 30, 2001

Cisco CallManager Release 3.0(12), a maintenance release, adds no new features. This document displays the caveats that were resolved in this release and displays workarounds for open caveats.

To view caveats for Cisco CallManager Release 3.0(12), see "Resolved Caveats" section and "Open Caveats" section. To view minimum versions with which Cisco CallManager Release 3.0(12) has been tested, see "Compatibility Matrix" section. These release notes are updated every maintenance and major release.

To read the feature descriptions implemented in Cisco CallManager Release 3.0(12) and prior, refer to:

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

To access the Cisco CallManager documentation suite, refer to:

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

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

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

Contents

These release notes discuss the following topics:

Introduction

System Requirements

Related Documentation

New and Changed Information

Resolved Caveats

Open Caveats

Documentation Updates

Obtaining Documentation

Obtaining Technical Assistance

Introduction

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

System Requirements

Make sure Cisco CallManager Release 3.0 is installed and configured on a Cisco Media Convergence Server. You may also install Cisco CallManager on a Cisco-approved Compaq server configuration or a Cisco-approved IBM server configuration.


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

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

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

For other system hardware component information and system requirements, refer to Installing Cisco CallManager Release 3.0(12).

Determining the Software Version

To determine the software version of Cisco CallManager 3.0(12), 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

Table 1 lists minimum versions with which Cisco CallManager Release 3.0(12) has been tested. Previous versions of Cisco CallManager will not work with the versions listed below.

Table 1

Component/Application

Firmware

Version 3.0(10)

Version 3.0(11)

Version 3.0(12)

CM-AA (Cisco CallManager Auto Attendant)

 

2.1(1) and 2.1(2)

2.1 and 2.2

2.1(1a), 2.1(2), and 2.1(3)

Applications (including IP IVR, IP ICD, Auto Attendant)

   

2.2 and 2.1(1a)

2.1(1a), 2.1(2), and 2.1(3)

Cisco Conference Connection

 

Not listed

Not listed

 

Cisco IP Softphone

 

1.1(1), 1.1(2), and 1.2(1)

1.1(1), 1.1(2), and 1.2(1)

1.2(1) and 1.2(2)

Cisco Personal Assistant

 

1.1

1.1

1.1

Cisco Unity

 

2.4.6.102

2.4.6.102

2.4.6.135, 3.0(1), 3.0(2), and 3.0(3)

Cisco Unity TSP

 

1.0.0.28

1.0.0.28

1.0(0.39) and 3.0(3)

Firmware:

Cisco IP Phone 7960

P003D310

 

P003H310

 

Cisco IP Phone 7940

P003D310

 

P003H310

 

Cisco IP Phone 7910

P004D310

 

P004H310

 

Cisco IP Phone 7935

Not listed

Not listed

P005S301

 

Digital Access - DT-24+

Not listed

Not listed

D003T300

 

Digital Access - DE-30+

Not listed

Not listed

D003T300

 

Analog Access - AT

Not listed

Not listed

A001C031

 

Analog Access - AS

Not listed

Not listed

A001C031

 

Analog Access WS-X6624

Not listed

Not listed

A002I3A0

 

Digital Access WS-X6608

Not listed

Not listed

D004I3A0

 

Conference Bridge WS-X6608

Not listed

Not listed

C001H301

 

Media Termination Point WS-X6608

Not listed

Not listed

M001H301

IOS

 

12.2(2T)

12.2(2T)

12.2(2T)

IPCC/ICM

 

Does NOT work

Do NOT upgrade; known incompatibilities exist with current version.

ICM 4.1 service pack 5 and ICM 4.5 service pack 0

JTAPI

 

1.1(1.19)

1.1(1.19)

1.1(1.25)

TAPI

 

3.0(1.18)

3.0(1.18)

3.0(1.23)


Compatibility Matrix for Release 3.0(12)

Related Documentation

The following list shows related documents for Release 3.0(12) of Cisco CallManager:

Installing Cisco CallManager 3.0(12)

Quick Start Guide for Cisco CallManager Release 3.0

Cisco CallManager Administration Guide for Release 3.0(5)

Troubleshooting Guide for Cisco CallManager Release 3.0(5)

Cisco IP Phone 7900 Family Administration Guide

Configuring Remote Serviceability for Cisco CallManager Release 3.0

Using Cisco CallManager Trace Gathering Tool for Diagnostic Traces

Cisco WebAttendant Quick Start Guide

Cisco WebAttendant User Guide

Cisco JTAPI Developer Guide

Cisco TAPI Developer Guide

Software License Agreement

New and Changed Information

New Software Features for Release 3.0(12)

Cisco CallManager Release 3.0(12), a maintenance release, adds no new features. This release resolves caveats, and this document displays workarounds for open caveats.


Tip To review the feature descriptions that were implemented prior to Cisco CallManager Release 3.0(12), refer to http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/3_0/rel_note/

Important Notes

The following sections contain notes on Cisco CallManager performance that may not be included in the Cisco CallManager documentation suite.

BIOS Update

Before you upgrade the BIOS and operating system on your Cisco CallManager server, click http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/osbios.htm to review the latest Cisco-supported BIOS and operating system files available for web download.

Service Parameters

During an upgrade, Cisco CallManager does not overwrite service parameter values that the system administrator manually configures in Cisco CallManager Administration.

Service Parameter Restart Conditions

If you modify any of the service parameters in the following list, you must restart the Cisco CallManager before the modifications take effect.

Digital Port

Ethernet Phone Port

Analog Port

MGCP Listen Port

MGCP Keep-alive Port

MessageWaitingOffDN

MessageWaitingOnDN

StatisticsEnabled

MaxDaResponseTimeoutErrorCount

MaxTotalNumberOfRegisteredCallingEntities


Note The service parameter restart conditions apply to all versions up to an including Cisco CallManager 3.0(7).

Note Refer to Table 4 for more information on service parameter definitions and defaults.

Cisco IP Phone 7910 and Cisco IP Phone 7940 Compatibility Issue

Cisco IP Phone 7910 and Cisco IP Phone 7940 are only supported by Cisco CallManager Release 3.0(5a) and higher. If you are running an earlier version, you must upgrade to a later version at http://www.cisco.com/public/sw-center/sw-voice.shtml.

Computer Telephony Integration

Computer Telephony Integration (CTI) serves as the base interface to Cisco CallManager for TAPI and JTAPI applications as well as direct CTI applications such as Cisco WebAttendant. Cisco CallManager 3.0(5a) allows you to control CTI application usage on a per-user basis. You can enable CTI application use for a particular user by browsing to entry in the User->Global Directory in the Cisco CallManager Administration Console and selecting the "Enable CTI Application Use" checkbox.


Note By default, CTI application use is disabled for all users.

In addition, Cisco CallManager 3.0(5a) also enforces a limit of 400 concurrent CTI connections per Cisco CallManager server. Each CTI application opens a single CTI connection to the Cisco CallManager on successful initialization. Alive CTI connection is required for the application to function.


Note A CTI connection is simply a TCP connection between the CTI application and the Cisco CallManager server and is distinct from a CTI port that is a virtual device.

The following example highlights the difference:

The Cisco IP Interactive Voice Response System typically opens several CTI route points and CTI ports; it will always open a single CTI connection to a Cisco CallManager in the cluster. The 400 connection limit applies to the CTI connection and not the CTI ports or route points.

BAT Reinstallation

Administrators must reinstall the Bulk Administration Tool (BAT) after installing Cisco CallManager 3.0(5a) because of a change made to the database.

Intercluster Trunk Configuration

An intercluster trunk, a virtual H.323 gateway, interlinks Cisco CallManagers in different clusters. Beginning with Cisco CallManager Release 3.0(4), intercluster trunks were configured differently. To ensure redundancy and proper failover operation, each cluster must configure an intercluster trunk to each Cisco CallManager in the remote cluster with which it shares a link.

For example, assume that you are configuring intercluster trunks among three Cisco CallManager clusters: Cluster-1, Cluster-2, and Cluster-3C:

Cluster-1 has three Cisco CallManagers: CCM-A, CCM-B, and CCM-C.

Cluster-2 has two Cisco CallManagers: CCM-D and CCM-E.

Cluster-3 has two Cisco CallManagers: CCM-F and CCM-G.

In the preceding scenario, you must configure 14 intercluster trunks to ensure redundancy:

Cluster-1 configures 4 intercluster trunks (to CCM-D and CCM-E in Cluster-2 and CCM-F and CCM-G in Cluster-3).

Cluster-2 configures 5 intercluster trunks (to CCM-A, CCM-B, and CCM-C in Cluster1 and to CCM-F and CCM-G in Cluster-3).

Cluster-3 configures 5 intercluster trunks (to CCM-A, CCM-B, and CCM-C in Cluster-1 and to CCM-D and CCM-E in Cluster-2).


Note If you add another cluster to this example configuration and you still want to maintain the intercluster links, you must modify the configuration for each cluster to add the necessary links between the cluster to all of the Cisco CallManagers in the new cluster. You must also configure the new cluster with intercluster trunks to all of the Cisco CallManagers in the existing clusters.

Cisco CallManager Integration with Corporate LDAP Directories

Cisco CallManager integration with corporate Lightweight Directory Access Protocol (LDAP) directories, such as Microsoft Active Directory and Netscape Directory Services, is not available in Cisco CallManager Release 3.0(5a). The availability of this feature will be announced at a later date, pending completion of integration testing.

Resolved Caveats

Resolved Caveats for Cisco CallManager Release 3.0(12)

Table 2 lists and describes caveats that were resolved in Cisco CallManager Release 3.0(12).


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

Table 2 Resolved Caveats for Cisco CallManager Release 3.0(12) 

DDTS number
Description

CSCds09042

A mandatory H.225 field is missing (H245Tunneling).

CSCds21211

Cisco CallManager trace lacks certain diagnostic details.

CSCds63434

User cannot successfully place international calls when using Cisco Softphone.

CSCdt02898

A call to a destination remains in ringback state.

CSCdt29182

An analog gateway sends caller name to Cisco CallManager in calling party number information element.

CSCdt37112

No call progress occurs on intercluster trunk transfer.

CSCdt37112

No call progress on intercluster trunk transfer.

CSCdt57230

Cisco CallManager upgrade adds extra ProcessNode for the same Cisco CallManager.

CSCdt67002

User may experience an installation error where the file stiview.exe is in use.

CSCdt67644

Cisco IP Phone 79xx does not respond to restart request if it is sent while it is offhook.

CSCdt69770

Pilot number does not support redundancy.

CSCdt75404

CP-7910 IP Phone displays "esB or x_@" instead of "Unknown Caller."

CSCdt84616

Blind transfer from voice mail to MeetMe does not bridge audio.

CSCdu01246

A dialtone exists even after key entered on Cisco IP SoftPhone.

CSCdu03062

RDNIS is not in Q931 message.

CSCdu08613

Cisco uOne port hangs after transfer to device where CFA/CFB fails.

CSCdu14893

"Not Enough Bandwidth Message" does not appear on Cisco IP Phone model 12 SP+ and Cisco IP Phone model 30VIPs.

CSCdu18827

A need exists for Cisco CallManager to support leading display character for DMS protocol.

CSCdu18892

When the publisher is down, call forward can be configured from the phone, which should not be possible.

CSCdu19175

Message Waiting Indicator (MWI) does not work when phone is off line.

CSCdu20075

Cisco WebAttendant fails to install on Cisco CallManager Release 3.0(9).

CSCdu21447

Cisco CallManager subscriber does not refresh database upon network recovery.

CSCdu25544

TCP communication errors appear after H.225 release completes.

CSCdu27665

Presentation bit has no effect on H.323 gateway.

CSCdu27941

Sdl Timer negative value index causes problems with Cisco CallManager.

CSCdu28192

Administrator can use invalid characters in user password.

CSCdu28490

UnknownCallerIdText does not work.

CSCdu29405

When a call redirects to phone with call waiting set to off, the unhold fails.

CSCdu29952

A disconnect occurs because of missing mandatory IE, but they are present.

CSCdu31205

User cannot blind transfer when receiving a PROGRESS instead of ALERTING.

CSCdu32197

AutoSelectHeldCallFlag set to T can cause wrong active line.

CSCdu32288

Memory leak caused by Cisco Catalyst 6000 8 Port Voice T1 or E1 and Services Module registration when database is down.

CSCdu33935

Two CallStateChanged dialing events for arbitrary call occur.

CSCdu35217

Cisco WebAttendant does not handle SSRedirectCallErr message from Cisco CallManager.

CSCdu36484

Pilot point does not forward to second hunt group member.

CSCdu37329

Apps receives a talking event for non-ICD extension.

CSCdu37873

Transfer button does not work without pressing it multiple times.

CSCdu38512

Cisco CallManager does not send mandatory UUIEs when calling party number is missing.

CSCdu39751

An explicit interface ID is not set in the restart ACK.

CSCdu41221

Calls on hold may not clear after user hangs up call.

CSCdu41898

Administrator could not revoke administrator rights from a user in Cisco CallManager Release 3.0(5a) or higher build.

CSCdu41924

The display covers some digits with a phone with shared line and more than seven digits.

CSCdu43386

Click-off flags and OK results equal failed to find CallManager Messaging Interface (CMI) service in database.

CSCdu44444

Cisco WebAttendant client is logged out of TCD server.

CSCdu44817

Cisco CallManager upgrade changes directory type back to DC directory.

CSCdu44827

Possibly sending incorrect restart code across a 6608 port.

CSCdu45048

Some MWI lamps do not light up when phones are reset.

CSCdu46509

Transfer fails on second call when coming through gateway.

CSCdu46851

GroupMappingTable information is not correct.

CSCdu47838

CLI problems with call forward and multitenancy.

CSCdu49392

Cisco CallManager does not accept IP phone or JtapiClient connections.

CSCdu49686

Forward no answer occurs even after a call is redirected.

CSCdu49947

Held call by Cisco CallManager Release 3.1 or higher cluster results in drop call when Music on Hold (MOH) is attached.

CSCdu51644

CTI LastRedirectingParty set incorrectly when call forward to TAPI voice mail.

CSCdu51668

TSP setting dwCalledIDName is incorrect.

CSCdu52215

No distinctive ring on calls through H.323 gateway occurs.

CSCdu52785

No distinctive ring on calls through MGCP gateway occurs.

CSCdu52827

Network time protocol service may hang.

CSCdu54191

Cisco WebAttendant hunt group does not work after failover.

CSCdu54281

Intermittent one-way audio occurs; no packets are generated from IP phone.

CSCdu55552

User cannot place inbound call to Cisco Access Digital Trunk Gateway DT24+.

CSCdu55729

Parking a call does not deliver DROPPED event to JTAPI.

CSCdu56944

Cisco CallManager allows same CTI port to be opened simultaneously.

CSCdu57794

If you have region names containing more than 32 characters, upgrading to Cisco CallManager 3.0(10) fails.

CSCdu59002

TCDSRV service terminates unexpectedly.

CSCdu59551

PRI NTT does not work.

CSCdu60386

Invalid data in Services XML may corrupt phone and cause phone to reset.

CSCdu60830

Cisco IP Phone 7960 directory displays are limited to 17 digits.

CSCdu63731

CTI timeout during a transfer does not clean up CTI port.

CSCdu64390

"dwConnectedID" is incorrect in route point redirect scenario.

CSCdu65567

Unattended blind transfers to cell phones fail.

CSCdu65765

Directory plugin allowCisco CallManger user to login with field other than CN.

CSCdu65809

Wrong metacode for conference scenario occurs.

CSCdu66155

Redirect fails with caller abandoned but call does not go idle.

CSCdu66424

The file, xmldirectorylist.asp, only returns 32 records with no search parameters.

CSCdu66685

No termconncropped event for park and transfer scenario.

CSCdu71657

Unhold error due to resource unavailable exception locks up CTI port.

CSCdu75418

MWI does not light for new partition without restarting Cisco CallManager service.

CSCdu77670

Cisco CallManager sends status with 0x80E2 and causes calls to disconnect.

CSCdu78354

When using shared line appearances, one cannot pick up a call on hold.

CSCdu81988

TFTP problems with SRST phone loads.

CSCdu83145

Cisco CallManager cannot login if the LDAP is Netscape directory server.

CSCdu83181

TCP connections to Cisco CallManager are terminated by Cisco CallManager unexpectedly.

CSCdu84568

Phone goes off hook when screen saver password is entered.

CSCdu86904

6608 sends bad G.729 packets.

CSCdv00255

WS-X6608 conference bridge uses different RTP send/recv port fails with Network Address Translation (NAT).

CSCdv01811

High CPU usage for extended time after MaxCdrRecords change.

CSCdv02030

Svchost.exe/TSP crash under high TAPI application load.

CSCdv03757

Phone will not reconnect to Cisco CallManager if Cisco CallManager is unreachable for more than 15 minutes.

CSCdv03924

Incoming faxes through WS-X6624 with UserUserIE=T resets Cisco CallManager.

CSCdv04960

Cisco IP Phone 7960/7940 listening on port 80 when no web server is present.

CSCdv05292

Cisco IP Phone 79XX volume control step size is too large at 4db.

CSCdv05574

Corporate directory search fails with phone load P003D310.

CSCdv07810

RST is not sent when SYN is received on an unopened TCP port.

CSCdv10033

Tcp SendThread timeout on select needs to be handled.

CSCdv10118

Cisco IP Phone 7910 LCD displays external phone mask in place of line number.

CSCdv12888

Call.connect() on the failed device causes JTAPI memory leak.

CSCdv14330

Wrong CallObservationEndedEv occurs when transferring a conference call.

CSCdv14432

User has to press the transfer button 3 times to complete function.

CSCdv14544

No termvonnheld is received for NON ICD call.

CSCdv15701

Phones are registering when auto-reg is disabled on CM1, enabled on CM2.

CSCdv15761

ICD agent phone gets into bad state and cannot accept ICD calls.

CSCdv17497

Display IE on redirected calls incorrect.

CSCdv20676

Phone idle user presses NewCall button, and line two goes offhook.

CSCdv21831

Cisco CallManager does not forward disconnect signal right away over intercluster trunk.

CSCdv22483

User pages reload after attempting to log in.

CSCdv23520

Transfer table corruption causes transfer to be ignored.

CSCdv27023

Cisco CallManager access violation occurs on shutdown.

CSCdv33549

Call forward busy (CFB) and call forward no answer stop working.

CSCdv35821

A need exists to include XMLDefault.cnf.xml in next Cisco CallManager Release 3.0 upgrade.

CSCdv39872

User cannot create multi-party conference using TAPI.

CSCdv46524

Cisco IP Phone 7910 resets if the ringer volume is too high.

CSCdv58269

Clicking the left arrow fails to place a call on hold in Windows NT.

CSCdv61305

Cisco IP Phone 79xx truncates CLID name if extended ASCII characters present.

CSCdv63452

Password option does not show up in user option page.



Open Caveats

Open Caveats for Cisco CallManager Release 3.0(12)

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


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

Table 3 Open Caveats for Cisco CallManager Release 3.0(12) 

DDTS number
Description
Release-note

CSCdr20726

H.323 phone does not receive progress tones during call setup.

Workaround: No workaround exists.

CSCdr25206

Line state server does not update the Cisco WebAttendant.

Workaround: Call the phone to update the phone status or go off-hook on the phone to update the status.

CSCdr26521

A nested call forward back drives Cisco CallManager CPU usage to 100 percent.

For large systems, Cisco CallManager can have up to 400 voice-mail ports. The issue is the delay imposed by 400 call forward hops. As a workaround until station hunt groups are available in a future release, the number of hops should be minimized. The hops can be minimized if the calls to voice mail can be spread more evenly over the number of ports. The total number of voice mail ports should all be forwarded to each other and last voice-mail port will be forwarded back to the first port. The configuration parameter max number of hops will control the end of the search for an available port. With this setup, a search can start at any port in the list to find an available port. The call forward all and busy DN can then be configured to split the users into groups to spread the search load and increases the chances of finding an available port with fewer searches. Since the message button is a system parameter the message button will always start at the top of the list.

Workaround: The number of hops will be limited by the max number of hops configuration parameter.

CSCdr26539

A nested call forward no answer takes too much time to forward through a linear list.

For large systems, Cisco CallManager can have up to 400 voice-mail ports. The issue is the delay imposed by 400 call forward hops. As a work around until station hunt groups are available in a future release, the number of hops should be minimized. The hops can be minimized if the calls to voice mail can be spread more evenly over the number of ports. The total number of voice mail ports should all be forwarded to each other and last voice mail port will be forwarded back to the first port. The configuration parameter max number of hops will control the end of the search for an available port. With this setup, a search can start at any port in the list to find an available port. The call forward all and busy DN can then be configured to split the users into groups to spread the search load and increases the chances of finding an available port with fewer searches. Since the message button is a system parameter the message button will always start at the top of the list.

Workaround: The number of hops will be limited by the max number of hops configuration parameter.

CSCdr28947

Transfers from Cisco uOne to invalid extensions by pressing * 8 leave the caller in silence.

For example, if a user logs into a mailbox, presses * 8 to transfer, and enters an invalid extension, the transfer is attempted, but the user does not hear anything after the standard Cisco uOne prompt plays.

In this situation, the caller is on hold pending transfer completion. The transfer never completes because the extension was invalid, and reorder was returned to the uOne port. The Cisco uOne port does not recognize reorder, so no further action is taken. The caller is left on hold.

Workaround: The user can hang up the call and call the person directly. Always transfer calls through Cisco uOne using a valid extension.

CSCdr30366

User experiences a long dial tone (10-12secs) before dialing the phone via AT-2.

When using CTI to dial out through an AT-2 gateway, dialtone is heard for 10 to 12 seconds before the numbers are dialed.

This occured using a TAPI test tool, calling out through an AT-2 gateway with 10-digit dialing. Dialing 7 digits will cause the Cisco CallManager to wait for a timeout in case there are more digits. While waiting, this timeout period dialtone is played then the number is dialed. To avoid this, setup a route filter with LCOAL-AREA-CODE set to DOES-NOT-EXIST and END-OF-DIALING set to DOES-NOT-EXIST.

Workaround: None exists.

CSCdr36331

Going from low bit rate to low bit rate, the wrong counter is sent from a transcoder. The problem occurs when the system is configured, so a transcoder is invoked to transcode between two low-bit-rate codecs (for example, from a G.723 to a G.729).


Note Cisco CallManager Release 3.0 does not support the use of a transcoder to support low-bit-rate to low-bit-rate transcoding.

When a transcoder is invoked to transcode between two low-bit-rate codecs, the transcoder consumes the internal resources of two transcoders, but only one transcoder is allocated.

As a result, more transcoders are available to be allocated in the system than there are internal transcoding resources to support them. When all available internal transcoding resources are in use, and another transcoder is allocated and begins transcoding, the voice quality on all calls going through that transcoder device degrades noticeably and, sometimes, severely.

Workaround: Cisco highly recommends that the system be carefully configured, so that transcoding between low-bit-rate codecs is not required.

No workaround exists for this problem other than limiting the number of calls through a given transcoder device by expanding the number of transcoders available.

Having at least twice as many transcoders available as there are calls that need them at any given time should eliminate this problem.

CSCdr36406

A <CmdArg>[Object Error]<noCmdArg> error message returns when a user is added via the Cisco CallManager administration page.

If users have been added to the system via private scripts, the directory may not allow some userid name conflicts to occur but does not properly report the conflict. For example, a user with the userid of "jsmith@company.com" will conflict with the proposed userid of "jsmith." This problem should not appear through normal usage of the product.

Workaround: Use a different userid for the new user or access the directory directly to delete the conflicting user.

CSCdr36513

The TSP does not see login changes until bouncing back from telephony.

While the telephony service is running, if the username and/or password is changed, the TSP will not pick up the change unless the telephony service is stopped and started.

This occurs while the telephony service is running.

Workaround: Restart telephony.

CSCdr39403

Database notification does not work in certain situations. Updates made from the Cisco CallManager administration page are registered but not reflected in the MIB tables until the SNMP data collector or Cisco CallManager (depending on the type of update) is restarted.

In Cisco CallManager clusters, changes to global values in a cluster environment appear on the MIB table that is local to the change but not in all MIB tables throughout the cluster. Updates will only appear on the MIB table that is local to the change, with the following exceptions:

When a time, region, or any static item is deleted, no MIB tables reflects the change.

When groups and regions are added, no MIB tables reflects the change.

Workaround: Restart the SNMP data collector or Cisco CallManager to display updated values in the MIB tables. If a Cisco CallManager cluster is involved, you must restart all SNMP data collectors to show consistent values in the MIB tables throughout the cluster.

Examples (local):

To remedy the two exceptions to local MIB table updating when deleting a time, region, or any static item, restart the SNMP data collector for the local Cisco CallManager installation to see the update reflected in the MIB table.

When adding groups and regions to a Cisco CallManager cluster, restart the SNMP data collector, which will help to update the MIB table.

CSCdr41623

When a port on a Cisco Unicast Conference Bridge is conferenced back to itself, a feedback loop is created in the conference bridge, and all participants experience audio feedback. Even if all phones involved in the conference hang up, the conference bridge still has a feedback loop because two or more ports of the conference bridge are conferenced together, and neither has disconnect supervision.

Workaround: You must perform a conference bridge reset to clear the conference.

CSCdr43111

Call only forwards once if route point does not have forward on no answer.

Workaround: Configure a forward on no answer destination for 3000 to point to some arbitrary other phone (i.e., 1006); then, you will no longer experience the problem.

CSCdr43369

When primary database disk is full, Cisco CallManager memory rises more than 700MB.

Cisco CallManager memory grows unbounded.

This may occur in a standard installation when the disk is full and CDR records are being written; the CDR write to the DB fails; deletion of the CDR records causes the transaction log to grow, so no disk space is recovered.

Workaround: Most Cisco CallManager servers will have plenty of disk space (more than 10 GB). You can resolve this problem by lowering the MaxCDR service parameter, so CDR records are deleted. Then, back up the server. Backing up the server will checkpoint the database and shrink the transaction log.

CSCdr46216

Wild characters !, ?, and + do not work with translation patterns.

While the telephony service is running, if the username and/or password is changed, the TSP will not pick up the change unless the telephony service is stopped and started.

This occurs while the telephony service is running.

Workaround: Restart telephony.

CSCdr48076

Cisco IP Phone 7960 transfer button causes malfunction of Resume button.

Workaround: The workaround is for caller A to go on and off hook and then press the EndCall softkey. This will enable the Resume softkey.

CSCdr52476

Cisco IP Phone 7960 documentation does not reflect a complete list of headsets.

The Cisco IP Phone Administrator's Guide does not accurately reflect the supported Headset models. The overview section states: The Cisco IP Phone 7960 supports a four or six-wire headset jack (Plantronic's compatible is required) for the Cisco IP Phone 7960. The Volume and Mute controls will also adjust volume to the earpiece and mute the speech path of the headset. The headset activation key is located on the front of the Cisco IP Phone. It has been verified that not all Plantronic's compatible headsets will function in the headset jack. There needs to be documentation to list each Plantronic's headset model that is supported; otherwise, this could generate alot of support calls to CA asking what exactly is supported.

Workaround: Provide a complete list of compatible headsets.

CSCdr54928

Cisco CallManager stops using Cisco Catalyst 4000 conference bridge.

Workaround: No workaround exists.

CSCdr55953

SNMP requires Cisco CallManager service to be restarted for phone addition/deletion.

Workaround: After you add or remove an extension from a phone, you must restart the Cisco CallManager service for SNMP agent to report the new information, so User Tracking can discover the changes.

CSCdr57791

Users cannot join MeetMe conference if one number is used instead of a range.

Workaround: Configure a pattern for the MeetMe number. This allows the users from other Cisco CallManagers to use the MeetMe number.

CSCdr60978

A terminal drops when a user tried to do a conference transfer scenario.

Transfer operation will be cancelled. All the calls remain in their own call states with no impact.

This problem occurs in one of the conference transfer scenarios. A party is trying to transfer the conference consultation call during a conference call setup.

Workaround: Restart transfer operation after the conference setup completes.

CSCdr64159

Cisco CallManager does not start if DNS suffix is conf in Network Ident tab.

The Cisco CallManager 3.0(1) installer CD will not work with servers in Cisco CallManager 3.0(1) that are configured with DNS names.

Workarounds: Change the Cisco CallManager names from DNS names to IP addresses (and ensure reverse DNS entries exist on the DNS server for those IP addresses). Change the Cisco CallManager name to non-fully qualified DNS names and remove the DNS Suffix from the Cisco CallManager using the following procedure:

1. Right click on My Computer.

2. Select Properties.

3. Click the Network Identification tab.

4. Click Properties.

5. Click More....

6. Remove the suffix from the Primary DNS suffix of this computer box.

7. Uncheck the Change primary DNS suffix when domain membership changes box

8. Click OK for all the open dialogs -- A window prompts you to restart.

9. Restart the Cisco CallManager.

CSCdr65502

Automated install may require user to reboot after reprogramming firmware.

During the installation of the Cisco CallManager 3.0(1), the MCS-7830 may stop at the following point: Running array F/W Update: COMPAQ H/W Upgrade Utility 4.0.1A (R): Reprogramming Firmware: DO NOT RE-BOOT OR POWER CYCLE MACHINE!!! Development Engineering is investigating the cause. The update should not take more than a minute or two.

Workaround: Reboot the machine after about 10 minutes (to be safe) and the installation will successfully complete.

CSCdr66431

Reinstallaing a subscriber Cisco CallManager from scratch does not work.

When a subscriber Cisco CallManager machine is replaced or reinstalled from scratch, steps must be taken for that subscriber to function.

Workaround: The administrator must use the Cisco CallManager Administration to remove the subscriber Cisco CallManager as a server. In order to do this, all devices, Groups, Pools, etc. that reference that subscriber server must also be removed. If this is done prior to installing the replaced or refreshed subscriber machine then installation will function correctly.

CSCdr67468

H.323 gateway configured as H.225 will not work with Cisco CallManager 3.0(1).

When configuring a H.323 gateway between two Cisco CallManagers running 3.0(1), the device protocol must be inter-cluster trunk.

Workaround: Add this information to the gateway sections of the Cisco CallManager Administration Guide.

CSCdr70322

CAUSE for arbitrary conference is CAUSE_TRANSFER sometimes.

On some circumstances, the cause code for the events related to the conference operation is set to TRANSFER instead of CONFERENCE.

Workaround: Application may use the CiscoConferenceStartEv/CiscoTransferStartEv events to ensure that they are in a conference or transfer.

CSCdr77184

Call park numbers do not recycle through configured range.

Workaround: Go to Feature > Call Park, select a range, and click Update; or create a new range.

CSCdr80075

A need exists for the Cisco CallManager to check the assignment of lines and speed-dial keys for errors.

Workaround: Put all lines at the top of the button template (before speed dials) or update the phone load to version P003H300 or later.

CSCdr80638

Locations do not recognize a transcoder correctly.

Workaround: No workaround exists.

CSCdr80728

Automated install CD does not load Cisco Media Convergence Server 7835 (MCS7835) without locking up.

Workaround: Update the server BIOS.

CSCdr81135

Devices cannot be associated to user using Netscape; Javascript error displays.

Using Netscape 4.7 or 4.73 on different PCs, go to Global Directory, choose user, press Associate Devices, and go to User Device Assignment screen. When you check a device box, at the bottom of the browser, it displays "Javascript error: Type 'Javascript:' into Location for details." When you press update, the device does not get associated with the user.

Workaround: Use Microsoft Internet Explorer 5.0.

CSCdr85945

Incorrect help definitions appear for Hold service parameters.

The following two definitions are the correct service parameters.

HoldType — Determines whether the hold light flashes more rapidly for the user who placed a call on hold when two different phones share the same directory number. Default is still F.

ToneOnHoldTime — Determines the interval between tones when a call is on hold. Default is 10 seconds, and the value range is 3 to 99999.

Workaround: Use the preceding definitions instead of the definitions in the Cisco CallManager Administration Guide and online help.

CSCdr89154

Using MTP causes delay in audio path.

The scenario described in the bug may occur when using a H.323 gateway with a MTP. The media part in the Cisco CallManager cannot wait for the establishment of media signalling path on both ends before letting the devices start streaming when using a MTP device in between. Hence the AA starts streaming even before the path between the GW and the MTP was being setup. The problem does not occur when a MTP device is not used.

Workaround: None exists.

CSCdr97481

Line button does not answer call on Cisco IP Phone model 30 VIP/12 SP+ with call pickup.

Workaround: Use the hookflash to retrieve the call.

CSCds04904

IVR greeting is clipped through call via FXS or T1.

When calling to IVR through ICS7750 MRP200, greeting message from IVR is clipped. Fragment of the very first word may be missing. No functionality is affected.

Workaround: None exists.

CSCds07952

"lineAccept" fails when already in connected state.

For CTI ports when a call-waiting call comes in, it is automatically accepted by the CTI port. If an application tries to accept the call, an error will be returned.

This occurs under normal conditions when calls to a CTI port stay in the offering state until an application accepts or answers them. The exception is call waiting calls. If a call is already active on a line and a second call comes in, this call will be automatically accepted by CTI.

Workaround: Ignore the error from the lineAccept request.

CSCds09562

A need exists for an error code to distinguish between invalid and out-of-service extension.

The problem is that no distinction is made between calling a DN that is not configured in the Cisco CallManager and calling a DN that is not registered. The reason for this is that digit analysis does not know about DNs that are not registered, so calling a CTI port that is not open is the same as calling a CTI port that is not configured. To digit analysis, these are the same error.

Workaround: Provide a generic message at the application level to cover both cases.

CSCds09623

The scroll bar does not appear on Device/Phone list page.

Workaround: The Administration web pages are designed for a minimum display resolution of 800 x 600. This release does not support lower resolutions.

CSCds12355

Cisco CallManager reboot causes no-answer condition in random Cisco uOne in cluster.

Workaround: Whenever the primary Cisco CallManager is rebooted, after the primary Cisco CallManager is active, stop and start "uTel" and any other dependant services.

CSCds12709

User cannot reset/restart any phone from Cisco CallManager 3.0 Device/phone.

Attempting to reset any device from the Cisco CallManager Administration web pages results in a window displaying an error message similar to this: ErrorNo. 1542: CDBLException Dump: [comerror]hr: 80070424 com error Description = [][the specified service does not exist as an installed service.] Cause: The Cisco Database Layer Monitor service was not installed as a service during install or upgrade.

Workaround: Manually install the Cisco Database Layer Monitor service. Open a command window, and at the command prompt, type the following:

<CmdBold>c:\progra~1\cisco\bin\aupair.exe -service<NoCmdBold>.

To confirm that the Cisco Database Layer Monitor service is installed, open the Component Services console (Start>Programs>Administrative Tools>Component Services), and look for Cisco Database Layer Monitor in the list of Services. The service starts automatically when it is first accessed.

CSCds14138

AVVID: A need exists for the automated install to allow reinstall option.

Workaround: You may have to wipe the disk completely to get the install to work. Do this by downloading the Compaq System Erase Utility from Compaq.com and erasing the machine completely.

CSCds18615

Redirect to wrong address via DT24 disconnects two party call.

The application will not be able to reroute the call again, and the caller will hear reorder tone.

Workaround: None exists.

CSCds18680

Users cannot set URL for plug ins.

Workaround: Install the plug in again on the first server. URLs will be set back again.

CSCds19482

CPU usage cycles from 40% to 70% every 20 seconds.

Cisco CallManager Release 3.0(3) resolves this bug.

Workaround: None exists.

CSCds20133

Call Forward Back fails when Cisco CallManager attempts to use unavailable Catalyst 4000 Access Gateway Module Call Forward Back resource.

Workaround: In the Admin/GUI page, under the conference bridge page, set the number of parties per ad hoc conference to the number of streams that a DSP on the Catalyst 4000 Access Gateway Module provided.

CSCds28204

AVVID: Call Forward No Answer and Call Forward Back does not use device Call Search Space when forwarding.

Workaround: Add the Call Search Space to the Call Forward No Answer and Call Forward Back numbers.

CSCds30227

Cisco CallManager does not reroute MWI request.

To avoid this problem, configure Cisco uOne properly. Cisco uOne is designed to work with multiple Cisco CallManagers, so there is an .ini file where you can list all the SSMWI devices in your clusters/cloud/domain/map with corresponding range of phone numbers. So when we deal with a phone number, we look up which range it falls and use the device and host.

Workaround: None exists. This works as designed.

CSCds33062

If an MWI light is on a phone, and the CM is reset, after the user logs in to the mailbox and deletes the voice messages, the MWI light stays on.

Workaround: Use at least version Cisco CallManager 3.1 or use a version below Cisco CallManager 3.5(a).

CSCds34785

SQL server passwords cannot be changed.

Workaround: Refer to the Installation Guide instructions for changing the SQLsvc and the Cisco CallManager administration user IDs.

CSCds36697

Users cannot delete database service from service parameters configuration page.

Workaround: See CSCds34596 in this document for a way to remove the server from the cluster if this is the desired end result.

CSCds38058

DBL takes too long (more than 20 minutes) to return 10,000 devices.

Query and analysis of result set using the database layer take a long time to execute.

Workaround: None exists.

CSCds42397

Terminal services do not function.

Workaround: This is a Microsoft limitation.

CSCds48200

Missing Disconnected, Established & TransferEnd in conference-transfer scenario.

Workaround: Avoid the scenario in which one party of the call is doing consult transfer and other party from the same call is performing consult conference.

CSCds48216

Missing DisconnEv, EstablishedEv & ConferenceEnd if conference PNC transfer.

Workaround: Avoid cases of starting as a consult transfer and invoking consult conference without completing the transfer first or vice versa. If you start an operation, finish it, and then perform next operation.

CSCds49273

Cisco CallManager prompts for MCS & SA pass, even though there is an existing password.

If you have already installed one Cisco CallManager which used the latest OS CD and Cisco CallManager, give it a password for MCS and SA as cisco, for instance. Then upgrade the Cisco CallManager to the latest version. At the install completes, it will still prompt the user to enter the password for MCS and SA again.

Workaround: When Cisco CallManager is being installed, the passwords are set to default and must be changed by the user.

CSCds50352

A System Unavailable message sporadically appears on Cisco IP Phone 7960.

This occurs under normal operating conditions.

Workaround: None exists.

CSCds50413

Missing Disconnected, Established & TransferEnd in conference transfer scenario.

Workaround: No workaround exists.

CSCds50626

STIBOOT caused an exception c0000006H in module MSVBVM50.DLL at 0137.

Workaround: Do not remove the media during the installation. If the media is removed, restart the install.

CSCds50763

Spurious NewCall is created when a redirect is done following an unhold state.

Workaround: No workaround exists for either Cisco IP Phone model 12 SP+ or Cisco IP Phone model 30 VIP; however, this operations works on the Cisco IP Phone 7900 family.

CSCds50786

Users must create conference parent call before sending out conferenced events.

Workaround: Microsoft will not fix this bug until Service Pack 3 of Windows 2000; therefore, to work around this problem, you must configure the multiprocessor machine to use only one of the processors on that machine.

CSCds55389

Backup installation starts after the Cisco CallManager installation is exited.

Workaround: This works as designed. Even if the install is exited, the backup utility needs to be configured (or server chosen as target).

CSCds55703

Cisco IP Phones do not forward large NFS datagrams.

The phone does not forward NFS datagrams for packet sizes larger than 11832 bytes.

Workaround: Configure the network port to match the speed of the access port.

CSCds56040

A transfer from second call incorrectly connects to first call on hold.

A hold call is mistakenly joined together when incoming call arrives on the same line.

To reproduce this problem, hit transfer button twice on an incoming call while another call on is on hold at the same line.

Workaround: It works as design. For the Cisco CallManager Release 3.0, this is how the transfer works on a single line appearance. It will be different when secretary-boss feature is implemented in the post Cisco CallManager Release 3.1.

CSCds59268

When Call Forward No Answer is configured on a line with partition, the calls forward to Call Forward No Answer.

Workaround: To continue using the Personal Assistant feature, the following configuration can be used as a workaround until this problem is fixed. Using setup as example, configure the calling search space PA to has partition PA only. Phone1 with DN 2007 has calling search space of PA; then, it can only call phone3; so, when phone1 dials 2003, phone3 (Personal Assistant) will receive the call.

CSCds62385

Cisco CallManager sends alerting before connect while in progress state.

Workaround: No workaround exists for this problem.

CSCds66500

Directory number does not show up on Cisco WebAttendant interface.

Workaround: The administrator should copy one of the two databases (UsersDB1.mdb, UsersDB2.mdb) to the local machine of the Cisco WebAttendant user. After the database has been copied, click the Settings button on the WebAttendant client. This will bring up the settings dialog box where the administrator may enter the local database path of the newly copied database. The administrator must then click OK on the settings dialog and restart the WebAttendant. The draw back to this fix is that the administrator must recopy the database file every time the user information changes.

CSCds67113

Cisco IP phone does not forward Network File System (NFS) datagrams for packet sizes larger than 11832 bytes.

Workaround: Configure the network port to match the speed of the access port.

CSCds67777

Blind transfer cannot complete successfully.

Workaround: No workaround exists.

CSCds69228

Even after Cisco WebAttendant logs out, calls are still directed to an extension.

After an "APPARENT" logout request by a Cisco WebAttendant user, the hunt group redirected calls still arrive at a phone that is only in the hunt group as an associated number to a users. Not as specific directory numbers.

This occurred when the Cisco WebAttendant client application experienced a local crash and therefore the logout request or message was never sent to the TcdSrv server component. So from the TcdSrv's perspective the client or Cisco WebAttendant was still active and logged in. Therefore calls where still being redirected to this station or phone.

Workaround: If the client disappears for any reason (crash, network outage etc...), TcdSrv detects the loss (no keepalives) and destroys the Cisco WebAttendant logical components. This will cause the calls to be routed to other directory numbers or user that are still logged in or available. The key here is to wait for a period long enough for TcdSrv to detect the lost client (3 miniutes). So until the keepalive timer expires for a lost client calls will still be routed to the associated client phone.

CSCds72057

Incorrect information appears in call block for conference call.

In a third-party conference, if one of the parties drops out and is conferenced in again, then the roster is incomplete (does not show all the participants), although the user has audio path with everyone

Workaround: None exists.

CSCds75317

A lineRedirect() call back to calling party causes problems.

Workaround: Do not redirect the call back to the caller, which should not happen under normal circumstances

CSCds76447

Cisco plugins incomplete and install.asp for plugins incorrect

Cisco WebAttendant will not function correctly on some installations because of CSCds66507.

Workaround: Do not install Cisco WebAttendant.

CSCds77984

Cisco IP Phone 7960 sends unregistermessageid and phone resets

Cisco IP Phone 7960s randomly send an unregistermessageid to the CallManager. The phone resets and registers with the same CallManager.

CSCds79206

Request exists for capability to hardcode speed and duplex on Cisco IP Phone 7960.

Workaround: No workaround exists.

CSCds79401

AVVID: Audio is heard through the handset when using the headset on Cisco IP Phone 7960.

Workaround: No workaround exists.

CSCds80198

Call pickup does not pick up a call even when line is Call Forward All.

Workaround: No workaround exists

CSCds81268

Cisco WebAttendant is not supported but plugin allows the installation.

Workaround: As the Release Notes for Cisco CallManager Release 3.0(5a) suggest, do not install Cisco WebAttendant.

CSCds84446

AVVID: Volume from Cisco Access Digital Trunk Gateway DT-24+ to Cisco uOne is too low to hear voice mail.

Workaround: No workaround exists.

CSCds87289

Hunt groups made from UserIDs and line numbers cannot cross Cisco CallManagers.

TcdSrv in one cluster handling a pilot point call redirects a call to a hunt group member in another cluster even when the line is busy. This occurs when the line state information is shared between TcdSrv's inside clusters only. Therefore if the hunt group contains members that are in fact in other clusters the calls will alays be routed to this number even if it is active or busy.

Workaround: Keep hunt group members within the same cluster as the pilot point when ever possible.

CSCds88617

GWY_ERR_C80ERR_RESOURCEUNAVAILABLE is reported from Cisco Access Digital Trunk Gateway DT-24+..

Workaround: Contact the TAC for the Cisco Access Digital Trunk Gateway DT-24+ load that will fix this issue

CSCds88657

Gatekeeper calls cause memory loss and stay up after being closed.

Workaround: Place calls at a slower rate if using SimClient or other test software. This defect should not occur during "normal," non-automated-calling scenarios.

CSCdt01353

DBL cannot start on subscriber after upgrade to Cisco CallManager 3.0(5a)

The Database Layer Monitor will hang during startup and Win2000 will report "At least one service failed to start."

Workaround: None exists.

CSCdt02575

SMDI sends no or wrong info on transfer from Octel.

Workaround: No workaround exists.

CSCdt02828

Mute button on Cisco IP Phone 7960 enables VAD even with VAD disabled system-wide.

The Cisco IP Phone 7960 stops sending RTP packets when you press the mute button, even if it has been disabled via the Service Parameters SilenceSuppressionSystemWide and SilenceSuppressionWithGateways.

Workaround: None exists.

CSCdt04394

Timer set to 0 does not disable the timer.

Workaround: Configure Call Forward No Answer to route calls to a voice-mail system or to an attendant.

CSCdt05077

Reinstalling the subscriber Cisco CallManager with a different hostname does not take effect.

Workaround: Changing the server host name is not supported due to SQL server limitation on SQL server. If you need to change the server name (CM name), you must reinstall from scratch.

CSCdt10505

When phone1 is forwarded to Cisco AutoAttendant, phone2 never transfers to Call Forward No Answer destination.

Workaround: Assign the first DID to the route point or use a translation pattern to reroute the call.

CSCdt11416

Conference master can transfer the ability to add participants.

Workaround: No workaround exists.

CSCdt12390

Cisco IP Phone sends no busy tone when Cisco WebAttendant lines are full.

This occurs when all members in a hunt group are busy in active calls, and a new call arrives at the pilot point number. So two passes are made through the hunt group looking for a destination. If none is found, then the call drops to prevent starvation of all pilot point callers. This is the classic ACD overflow conditions that would normally be handled by a message queue or some sort.

Workaround: Make sure that the hunt group has some sort of overflow handling; such as, the last number in the HG could be a voice-mail number or pilot-point number that can always except calls. In the Cisco WebAttendant hunt group administration window, a checkbox for always Route exists. This means that even if TcdSrv knows the number is busy, it can handle more than one call at a time, so when reached in a hunt group search, TcdSrv always redirects the call to this number.

CSCdt13722

Cisco WebAttendant screen does not display call-forwarding information.

Workaround: No workaround exists.

CSCdt20517

Calls placed on IP phones show translated No.

Workaround: The problem does not occur when no translation is done, but if dial translations are required, no workaround exists.

CSCdt21522

User cannot make more than 20 729-711 transcodings with Voice Activity Detection (VAD) disabled.

Workaround: Set PreferedG711MillesecondPacketSize = 20msec PreferedG729MillesecondPacketSize = 20msec PreferedG723MillesecondPacketSize = 30msec SilenceSupressionSystemWide = True and False.

CSCdt25949

DB Error (objTraceList) = 1542 undefined error displays.

Workaround: No workaround exists.

CSCdt26108

User cannot open two lines on one Computer Telephony Integration (CTI) port.

Workaround: Configure the Cisco CallManager to have only one line per CTI port device.

CSCdt27464

Documents for Call Forward Answer do not mention special case of CSS set to <none>.

Workaround: When the Call Forward All button or Call Forward from the Cisco CallManager user administration are used, if the Calling Search Space for Call Forward All is set to <none>, the Calling Search Space that is used for Call Forward All (CFA) is the Search Space on the Line and the phone, not the Search Space that is configured for Call Forward All, which is <none> in this case. In the context of the Call Forward All Calling Search Space, <none> does not mean the NULL Calling Search Space, but rather means the combination of the line and phone Calling Search Space for the device initiating the Call Forward All.

CSCdt28706

Phones stop playing ringback after OLC.

Workaround: No workaround exists.

CSCdt29275

Cisco CallManager 3.0(5a) upgrades reset enterprise parameter URLs to default.

Workaround: After the upgrade, change the URLs to the values that existed prior to the upgrade.

CSCdt30332

Cisco Messaging Interface stops after Cisco CallManager 3.0(7) upgrades.

Workaround: This is not an error. A blank VoiceMailDN is an invalid configuration. If using partitions and Calling Search Spaces when configuring CMI, verify that the same partition applies to both the CMI partition and the route pattern assigned to the third-party voice-mail system.

For example:

Route Pattern 17050

Partition vm

.....

VoiceMailDn 17050

VoiceMailPartition vm

CSCdt30432

Cisco CallManager does not handle SUS/RES satisfactorily.

If the IP phone goes on-hook first, the Cisco AS5300 Network Access Server (NAS) will never receive a H.225 RELEASE message from the Cisco Call Manager. This will result in the calling party in the SS7 network experiencing fast-busy, or reorder tones.

In a Cisco SS7 Interconnect for Voice Gateways solution, if a call is made from an phone in the SS7 network to a Cisco Call Manager IP phone, the call will not be torn down gracefully if the IP phone goes on-hook first. The call flow is as follows:

SS7 phone -> Cisco MGC -> NI2+ -> AS5300 -> Cisco CM -> Cisco IP phone

If the IP phone goes on-hook first, the Cisco AS5300 Network Access Server (NAS) will never receive a H.225 RELEASE message from the Cisco Call Manager. This will result in the calling party in the SS7 network experiencing fast-busy, or reorder, tones. In addition, this behavior prohibits end-to-end SUSPEND and RESUME functionality from working correctly within the context of this call flow. The workaround is for the calling party in the SS7 network to hang up first.

Workaround: None exists.

Cisco CallManager does not support SUS/RES capabilities over PRI or H323. When IP phone goes on hook, the call is considered to be cleared right away.

CSCdt35469

Logging on to Cisco CallManager user pages transmits a clear text password.

Workaround: Choose Start > Administrative tool > Internet Information Service

Right click on CCMUser.

Click on Properties.

Select Directory Security tab.

Click Edit and set the security lever. This may only allow IE to browse the page.

CSCdt36334

Poor interface response with large number of records

Slow interface response in Route Plan-related screens when adding or changing records with large number (several hundreds) of records defined in Route Partition, Calling Search Space, Route Filter, Route Group and Route Lists.

Workaround: None exists.

CSCdt40683

Cisco Messaging Interface partition must match route partition when configuring Cisco Messaging Interface.

Workaround: If you are using partitions and calling search spaces, when configuring CMI, verify that the same partition applies to both the CMI partition, and the route pattern assigned to the third-party voice-mail system.

Example:

Route Pattern 17050

Partition vm

.....

VoiceMailDn 17050

VoiceMailPartition vm

CSCdt41163

User cannot dial complete digits.

User cannot dial digits when a particular translation pattern is set.

Workaround: None exists.

CSCdt44000

Call detail records are intermittently not written locally.

Workaround: No workaround exists.

CSCdt44611

Cisco WebAttendant Line State Server LSS is not correct when TCD starts.

Workaround: Take any phones that have the line state as not present off hook and put them back on hook. Any line state change will update the Cisco WebAttendant directory area.

CSCdt45104

Calls may drop when changing between Cisco WebAttendant SL lines.

When a multiline phone has multiple calls, taking one of the calls off hold, causes the currently active call to be disconnected.

Workaround: Allow a second or two in between clicking on calls.

CSCdt45118

Abnormally high memory usage occurs by SQL server.

Workaround: Turn off the BAT and ART tools; then, restart the Cisco CallManager.

CSCdt45861

Failed SetupTransfer request incorrectly modifies existing calls.

Workaround: The application should not be calling lineSetupTransfer() in this scenario.

CSCdt48558

A need exists to dynamically add route points for Cisco WebAttendant.

Workaround: No workaround exists.

CSCdt49265

The web upgrade allows user to perform a new install.

When the upgrade is performed, the user is not prompted with any messages stating a previous version of Cisco CallManager needs to be installed prior to continuing. The install proceeds with no noticeable errors. Following the install reboot, if the user goes to the start menu, Cisco CallManager does not appear.

Workaround: An older version of Cisco CallManager should exist on the system prior to upgrade; otherwise, the upgrade fails.

CSCdt49736

Some memory goes up when adding phones using BAT, and it never goes down.

Memory in dllhost, ccm, and aupair goes up and never goes down when using BAT to add a 2500 phones.

Workaround: None exists.

CSCdt50317

Cisco CallManager 3.0(7) call detail records do not move from subscriber to publisher.

Workaround: No workaround exists.

CSCdt50538

A shared line problem occurs when one of the phones returns from reset.

If a phone with a shared line appearance resets, there is no indication that the line is actively in use on another phone until the phone that just reset tries to go offhook. The phone will send an offhook message to Cisco CallManager but the display will indicate "Line in use"

Workaround: None exists.

CSCdt51159

Resetting H.225 device by any means causes AnonymousDevice failure.

Anonymous calls stop working when changing configuration of unrelated devices.

This problem occurs when any H.225 device is reset.

Workaround: In Release 3.0(8), none exists, but in Release 3.0(9), press the Reset Gateway button on the Gatekeeper configuration page to reset AnonymousDevice.

CSCdt52823

There are orphaned DNs listed in the View in File Route Plan Report that have no Device Name info.

If the DN was previously assigned to a device, when a device partition is changed the DN is orphaned.

Workaround: Assign the desired DN to a phone. Then remove the DN from the phone. The DN record will be removed from the database, and the Route Plan Report will work correctly.

CSCdt52841

Cisco WebAttendant documentation calls for read access to the wausers share, but change access is required to open the database.

Workaround: Allow change access to the wausers share.

CSCdt53938

Upgrade does not put BINs in nondefault TFTPPATH.

Workaround: Two known workarounds exist.

1) Upgrade the primary TFTP server first

2) Place the device loads on the primary TFTP server before upgrading any of the other clusters.

CSCdt54310

Call Detail Records are written incorrectly when digit manipulation is performed on Route List.

Workaround: Perform digit manipulation on the Route Pattern. This may cause other ill effects, such as causing the Placed Calls directory on the Cisco IP phone to not include the correct number.

CSCdt57270

Publisher and or subscriber servers have difficulty with different passwords.

Workaround: Use the same administrator password for the publisher and all subscriber servers.

CSCdt62091

Directory number entries remain in database.

Workaround: Assign the desired directory number to a phone; then, remove the directory number from the phone. The directory number record will be removed from the database.

CSCdt62208

Cisco IP Phone 7960 reports two missed calls if unanswered.

Workaround: Mask the problem by increasing the CallManager T301 timer so that the ringout time is greater than the PSTN ringout time.

CSCdt62292

Call from PSTN to an undefined directory number records 0 in CDR.

Workaround: No workaround exists.

CSCdt64163

User cannot delete partition from Cisco Callmanager.

Workaround: Contact TAC.

CSCdt65088

Cisco WebAttendant SL1 fails after numerous transfers.

Workaround: Stop and start the TCD service.

CSCdt65122

Active Directory users added with Cisco CallManager or BAT do not get valid UserID.

The problem occurs you enter users with Cisco CallManager or BAT, and you enter passwords with Active Directory. A valid UserID and password for User Preference Pages cannot be found.

Workaround: This bug has two workarounds.

1. Add users from Active Directory server. Set Registry entry DIRACCESS to False. Do not use BAT to add users.

2. Enable the user from the Active Directory interface; change the password. Then, you can log in.

CSCdt66176

Speed dial update delays 45 to 60 seconds on Cisco IP Phone 7960.

Updating speed dials from Cisco CallManager user interface takes up to 60 seconds to appear on the Cisco IP Phone 7960. Information is seen to update immediately in all databases. This happens in a multiple Cisco CallManager system running 3.0(8) where phones are registered to the subscriber. This problem also appears when updating line appearances from the Cisco CallManager Administration page. Problem: The Cisco IP Phone 7960s do not retrieve the new directory information. Regardless of the number of Cisco IP Phone 7960 updates or resets, it will take 45-60 seconds for this information to appear on the Cisco IP Phone 7960. Information is populated immediately to the databases of all Cisco CallManagers. This has been tested with multiple phone loads (P003Q301 and P003V301) with no change.

Workaround: Doing a hard reboot of all Cisco CallManagers corrects this problem.

CSCdt66634

User cannot execute find queries within Cisco CallManager.

Symptom: Can not use "Find" to query database within Call Manager. Get the following error when trying to query "HTTP 500.100 - Internal Server Error - ASP error Internet Information Services."

Workaround: None exists.

CSCdt67550

To change system server from a name to IP requires user to restart of the TFTP service.

Workaround: Go to System > Server in CallManager Administration, change the server name to its IP address. Then go to Service > Control Center, and stop and start the Cisco TFTP server.

CSCdt67779

If more than 100 Call Detail Records (CDRs) are written per the defined interval, the process stops after the first 100 and waits for the next timed interval.

Workaround: Shorten the defined time interval.

CSCdt69873

Corporate directory does not exist intermittently in the Cisco IP Phone 7960.

Workaround: No workaround exists.

CSCdt73651

Cisco WebAttendant cannot log in when lines are not contiguous on phone.

Workaround: Configure lines on Cisco IP Phones so that they are contiguous.

CSCdt73926

CDR CallID is reset with Cisco CallManager restart.

Upon examining the CDRs, you may see a large number of records with the same globalCallID_callId number.

Workaround: If Cisco CallManager must be restarted, extract CDRs before restarting Cisco CallManager. Otherwise, related records will need to be determined by examination of the time and date of the record.

CSCdt73926

CDR CallID is reset with Cisco CallManager restart.

Workaround: If Cisco CallManager must be restarted, extract CDRs before restarting Cisco CallManager. Otherwise, relate records will need to be determined by examination of the time and date of the record.

CSCdt76403

CDR records are incorrect when recording conference calls.

Workaround: No workaround exists.

CSCdt83560

User cannot change load of Cisco IP Phone 7960.

Cisco IP Phone 7960 will not upgrade its load. The appropriate configuration file is missing.

Workaround: 1. Connect the phone to a Cisco CallManager Release 3.1(1) to back-rev its load.

2. Build and install a Cisco CallManager Release 3.1(1) compatible configuration file for the phone.

CSCdt85557

Group call pickup with insufficient bandwidth causes failure and bandwidth miscalculation.

Calls fail when the bandwidth is not sufficient for group call pickup.

Workaround: None exists.

CSCdt86164

Cisco Access Digital Trunk Gateway DT-24+ power cycle causes a call to fail.

Workaround: Reset the Cisco Access Digital Trunk Gateway DT-24+ device.

CSCdt87371

Transfer fails after system is online for a couple of days.

Workaround: Reboot system.

CSCdt90453

The Conference Bridge and the MTP do not run if the server does not have a device pool that points to the Cisco CallManager group that is configured as the highest priority in the Cisco CallManager.

The online help for the Cisco CallManager Administration for the Conference Bridge and MTP incorrectly states that you can choose one of the available device pools or select a device pool from the drop-down menu in the Device Pool field. Workaround: The documentation and online help have been corrected to read: Choose a device pool having the highest priority within the Cisco CallManager group you are using or choose Default.

CSCdt90457

After you restart the TCD, Cisco WebAttendent GUI misses directory numbers.

This occurs when Cisco WebAttendent is running on a winNT client machine with normal configuration.

Workaround: Close the Cisco WebAttendant window, and open a new one; all missed information will come back to normal.

CSCdt91509

A need exists for the dialing digits to exceed 24.

Workaround: Decrease the number of digits in the route pattern, so the dialed digits equal less than 24.

CSCdt95272

User cannot end process on backup.

When trying to end process on the backup utility, the utility never ends.

If you go into Task Manager and try to end process on Backup utility viewer, the system acts as if it ends process, but the process never ends. If you start the backup process again, you will see it never stopped.

Workaround: Ctrl-alt-delete may be used to stop programs but not services. Many services can be killed this way; however, it will leave the machine in an unreliable state. Go to "cancel backup" menu selection to shut down the backup.

CSCdt95739

Caller ID overwrites a call-parked number.

Workaround: No workaround exists.

CSCdu01040

With G729 codec, Unity never detects silence.

Workaround: No workaround exists.

CSCdu01080

Digital PBX Adapter (DPA) 7630 will not allow symbols in the password field.

DPA 7630 running 1.0(1.5) software allows the administrator to use symbols in the password field, such as (*&^%$#@!), but then will not accept the same symbols when trying to log into the DPA.

Workaround: None exists.

CSCdu06412

Cisco CallManager incorrectly interprets the disconnect cause.

Workaround: Use the route group that chooses local gateway.

CSCdu06749

Echo occurs over 6608 T1 gateway.

Echo using Cisco Catalyst 6000 8 Port Voice E1 or T1 and Services Module VoIP gateway occurs.

Workaround: To reduce echo you may adjust the "Audio signal adjustment into IP network," "Audio signal adjustment from IP network," and "Tx-level CSU" fields under the Cisco CallManager gateway screen.

CSCdu09364

Cisco WebAttendant screen does not fit on an 800x600 screen.

The scroll bars are missing on the screen.

Workaround: None exists.

CSCdu10456

Transfer succeeds after first party drops.

Workaround: No workaround exists.

CSCdu14186

Transferred outbound calls appear as inbound in CDR.

When a call to the PSTN is made from an IP phone (Cisco IP Phone 7960 in this case), it is recorded as outbound. If the call is then transferred to another IP phone the second portion of the phone call is recorded in CDR as an inbound call originating from the PSTN.

Workaround: None exists.

CSCdu16388

Using Netscape causes problems with add user and associate devices.

Using Netscape Navigator 4.7 can result in confusing and sometimes incorrect behavior when trying to add a new user through the ICS System Manager (Configure > Call Manager > User > Add a New User). Problem 1: You fill in the new user fields correctly. Then you click on Insert. The web page shows a blank page instead of indicating success. In this case the user is actually added. The only problem is that the display is confusing to the user. Problem 2: You add a user. Click on Modify User. Then click on Associate Devices. Do a Select Search for devices. Check one of the devices returned by the search. Then click on Update. Nothing happens. In this case the device selected is not associated with the user profile you are modifying.

Workarounds: Both of the above problems can be avoided by using Internet Explorer 5.

CSCdu17141

Call from callpark cannot be retrieved.

Workaround: No workaround exists.

CSCdu20404

No message displays to show the administrator if the user has been created or not in Cisco CallManager.

Using Netscape Navigator 4.7 can result in confusing display behavior when trying to add a new user through the ICS 7700 System Manager (Configure Call Manager > User > Add a New User). Using an incorrect Manager's UserID causes Netscape to display a blank page after clicking the Insert button. It should display an error message. Giving a blank or correct Manager's UserID causes Netscape to display a blank page after clicking the Insert button. It should display a successful completion message.

Workaround: Since the correct action is taken internally by the software in each case above, this is mostly just a user confusion problem. If the user wants to completely avoid this confusion, the user can use Microsoft Internet Explorer 5, which behaves properly in both of the cases above.

CSCdu21141

A lineAnswer returns SUCCESS, but state does not change.

Workaround: Use blind transfer or consult transfer instead of arbitrary transfer.

CSCdu23382

Route filters do not display in exported route plan reports.

Workaround: No workaround exists.

CSCdu27800

Cisco WebAttendant 3.0(3.42) is installed, and user cannot uninstall previous version.

Workaround: Manually remove previous Cisco WebAttendant directories, shortcuts, and registry entries.

CSCdu32422

Phone call is not forwarded as indicated in the parameter ForwardNoAnswerTimeout. There is a difference of 4 seconds. This unexpected behavior only occurs when this timer is set to 20 or greater.

ForwardNoAnswer timer expires earlier than expected.

If the ForwardNoAnswerTimeout is set to 20, the phone call will be forwarded (If it is not answered) after 16 seconds. If this timer is set to 24, the phone call will be forwarded after 20 seconds.

Workaround: None exists.

Note: The problem is resolved in Cisco CallManager Release 3.1 and beyond with more accurate timer component.

CSCdu32724

No audio on external transfer.

Making an arbitrary transfer of two outside calls results in the two calls being connected but there is no media setup. The two parties cannot hear one another.

Workaround: Use a consult transfer.

CSCdu38419

H.245 packet precedence is not set properly.

This only occurs when the TCP connection is attempted. Once the TCP connection is established, the precedence bit is set properly on all H.245 messages.

Workaround: None exists.

CSCdu42536

Windows 2000 appears to freeze when installing on some IBM xSeries 330s, but it is actually just installing slowly.

Workaround: You can wait for about an hour for the install of Windows 2000 to complete. You can also select F8 upon boot up and choose Enable Boot Logging. Problem is not consistently reproducible.

CSCdu42662

Cisco CallManager does not start if you enter DNS suffices.

At system server page, the server configuration does not accept full name (name with DNS suffix such as callmg09.Cisco.com). CallManager will have no heart beat after rebooting.

Workaround: Use just host name such as callmg09 or IP address instead of full DNS name, callmg09.Cisco.com.

CSCdu45086

"m_DropPending" flag does not clear after it is set by lineDrop request.

If a lineDrop() on a call causes the call to go to the DISCONNECTED state, instead of the IDLE state, and you try to call lineDrop() again on that same call, the second lineDrop() request will fail and you may never be able to drop the call.

The problem would not occur under normal working situations. This problem was actually found because of a bug in the CTI code.

Workaround: Call lineDeallocateCall() on the call to get rid of it.

CSCdu45966

Audio cut-through delay on PSTN transfer from CTI port.

There is a three-second delay in the audio stream being cut through on calls transferred to or from the PSTN through an H.323 gateway.

Workaround: None exists.

CSCdu46744

Cisco CallManager holds memory during a high volume of calls.

During a scalability test a call volume of approximately 40000 calls per hour are originated from a Callgen router ( simulating IP phones) and terminated set of Callgens. If some calls are not answered, a memory leak is seen to occur. Over one 10 hour test, 950 megabytes of memory are used. After 4 additional hours with no call activity the memory has not been freed. Calls are simulated IP phone to IP phone. The leak is occurring when calls are not answered.

Workaround: None exists.

CSCdu47097

"MwiSearchSpace" parameter value truncated upon upgrade.

The MWISearchSpace parameter value for the messaging interface was truncated to 128 characters.

Workaround: None exists, or use value less than 128 characters.

CSCdu54108

Cisco WebAttendant does not start if WAUSERS share is down.

Workaround: Your server has to fail back before your Cisco WebAttendant will work properly.

CSCdu58609

Modifying route list parameter within existing route pattern fails.

Workaround: Restart the Cisco CallManager service.

CSCdu61188

H.323 calls do not provide tone on hold.

No tone on hold occurs when call is via H.323 trunk, but works with pri.

Workaround: None exists.

CSCdu62484

Cisco WebAttendant screen is not refreshing line updates for users.

Cisco WebAttendant screen is not always updating the line status of the phones.

Workaround: None exists.

CSCdu64285

Cisco CallManager stops writing to Cisco CallManager trace and event application log.

Workaround: None exists.

CSCdu69819

Phone with two identical DNs may have transfer problem.

If customer has a phone with two lines that have the same number but are in different partitions, when one line has one call active and another on hold and there is a call coming in to the second line, the transfer button might be disabled on this second line incorrectly.

Workaround: Do not create phones that have two lines with the same DN but different partitions until this bug is fixed.

CSCdu71087

Setting LINETRANSFERMODE_CONFERENCE in completeXfer should fail.

Application sends lineCompleteTransfer() with dwTransferMode set to LINETRANSFERMODE_CONFERENCE. This request should fail because LINETRANSFERMODE_CONFERENCE is not supported by the TSP. But, the request succeeds and the operation is treated like a transfer which is incorrect.

Workaround: Application should never set the dwTransferMode to LINETRANSFERMODE_CONFERENCE since it is not supported by the CiscoTSP.

CSCdu71551

Administrator cannot reset phones from Cisco CallManager Administration.

Administrator cannot change the forwarding information for IP phones or reset phones through the GUI interface.

Workaround: Reset phones manually. None exists for changing forwarding information.

CSCdu77516

Failure response from lineUnHold when consult call is offering.

"lineUnhold() " returns a negative response after a lineSetupConference() and before the consultation call is answered, even though the call is successfully retrieved.

Workaround: None exists.

CSCdu78398

A shared line goes off hook instead of primary line.

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

Workaround: Have the user press the primary line button before dialing.

CSCdu79328

Software conferencing stops working until IP Voice Media Streaming App restarts.

Users get message "No Conference Bridge Available" when attempting to conference in other users.

This can occur if you are using the software conference bridge, and it has been running for some time.

Workaround: The only way to resolve this problem is to stop/start the "IP Voice Media Streaming App" service from Call Manager Control Center

CSCdu83844

Devices do not register correctly after quick cluster reboot.

Workaround: Manually reboot or power cycle the devices.

CSCdu86461

No translation when DN is unregistered (gets wrong mailbox).

PSTN caller gets incorrect voice-mail box This may occur when called IP phone DN is un-registered, and translation pattern to that DN exists.

Workaround: None exists.

CSCdv01110

CTI does not send IDLE event after unhold failed by Cisco CallManager.

Unhold call request fails after unsuccesful consultWithOutMedia attempt.

Workaround: Workaround is implemented in JTAPI. It clears the connection in the disconnect method if it fails with INVALID_CALL_STATE. That "unlocks" CTIPort.

CSCdv03481

One-way audio occurs when doing CTI transfer.

When using a CTI application to transfer a call, a race condition can occur where a Cisco CallManager does not wait long enough for an OpenLogicalChannelAck leading to the following error message in the Cisco CallManager trace: AgenaInterface::OpenLogicalChannelAck error: ParentPid not match .

Workaround: None exists.

CSCdv10611

One-way audio on outbound calls when MTP is enabled

When hardware MTP is used, outbound calls from IP phone have one-way audio.

Workaround: Remove MTP.

CSCdv13266

Software conference bridge uses different RTP send/recv port breaks using NAT/PAT.

When using the software conference bridge or media termination point ,two different UDP/RTP ports are used, one for the TX side and another for the RX side.

This will cause problems when trying to route the RTP packets through a NAT gateway.

Workaround: None exists.

CSCdv15124

Media_SilenceSuppression value sent to phone is invalid.

Silence Suppression starting in calls when it is disabled.

Workaround: None exists.

CSCdv15163

SJCLSTR2D crashed when it ran out of memory.

Cisco CallManager may crash after consuming all of its virtual memory.

Workaround: None exists.

CSCdv17783

With shared line appearance, user cannot resume call placed on hold from another phone.

Workaround: Hit resume before picking up the handset.

CSCdv22744

ToneOnCallForward parameter gives one quiet beep.

When a customer sets "ToneOnCall Forward" parameter to true, he misses hearing the tone because it is so brief.

Workaround: None exists.

CSCdv26354

Cisco WebAttendant should NOT allow two or more lines with same DN on agent phone.

This might be the problem if Cisco WebAttendant agents cannot log in. This may occur when Cisco WebAttendant agents fail to login if their phones are configured with two lines that have the same directory number.

Workaround: Remove duplicate line entry.

CSCdv29094

Route loop restarts Cisco CallManager.

Workaround: Remove the Route Pattern from Cisco CallManager and/or PBX database.

CSCdv30394

Call.consult hit CCNException under call load.

Call.consult hits CCNException if there is a outstanding consult call on a line.

Workaround: None exists.

CSCdv31675

Wrong events are seen in one conference transfer scenario.

Workaround: None exists.

CSCdv31832

Conference parent handle missing in conference message

LINEDCALLSTATE_CONFERENCED message does not contain the conference parent handle when the conference has been set up manually using IP phones. The value is present if the conference was created programmatically (via lineSetupConference/lineAddToConference.)

Workaround: Identify the handle by examining the handle of the conference parent call itself. Implies control of that device.

CSCdv31832

Conference parent handle is missing in conference message.

LINEDCALLSTATE_CONFERENCED message does not contain the conference parent handle when the conference has been set up manually using IP phones. The value is present if the conference was created programmatically (via lineSetupConference/lineAddToConference.)

This occurred when the conference call was created manually using IP phones.

Workaround: Identify the handle by examining the handle of the conference parent call itself. Implies control of that device.

CSCdv32130

Call through VG200 gateway drops for JTAPI routing application scenario.

A call coming across VG200 gateway gets dropped if routing application waits beyond JTAPI Route select timeout before invoking "routeselect."

Workaround: None exists.

CSCdv34425

CMI LTN fails to increment when route group device uses port All.

When adding devices to a route group, users have the choice of port "All" or "1". If port "All" is selected and the route group is used for SMDI integration, then the CMI service sends LTN 0001 for all route group members. This causes SMDI integration to fail.

Workaround: Delete all devices from the route group and re-add them using port "1".

CSCdv36262

User login.asp does not accept the "/" character in the user name.

LINEDCALLSTATE_CONFERENCED message does not contain the conference parent handle when the conference has been set up manually using IP phones. The value is present if the conference was created programmatically (via lineSetupConference/lineAddToConference.)

The occurs when conference call was created manually using IP Phones.

Workaround: Identify the handle by examining the handle of the conference parent call itself. Implies control of that device.

CSCdv37532

On Cisco CallManager Administration window, the IP phone accepts the alpha characters for phone number attribute.

Cisco CallManager should throw an exception.

Workaround: None exists.

CSCdv37562

Admin cannot modify/add user if the Cisco CallManager is unplugged from the network.

This occur when network cable is disconnected from Cisco CallManager.

Workaround: Restore the network cable connection and add user.

CSCdv41896

Cisco CallManager sends an open logical channel message to the IP phone and gateway with an all-zero RTP address. The gateway then tries unsuccessfully to send voice traffic to 0.0.0.0.

This occurs when the user gets no-way audio when calling between analog phones on a PBX and IP phone.

Workaround: Restarting the Cisco CallManager temporarily fixes the problem, but it has resurfaced after a few days.

CSCdv43780

MCS Backup Utility does not have low priority by default.

By default, the MCS Backup Utility is installed with the process priority set to medium. In at least one case, this has caused the Cisco CallManager process to stop because of heavy processor utilization. (CSCdv34316).

Workaround: In the Backup Utility Configuration application, select Performance tab, and set the Priority to Low.

CSCdv44292

Cisco CallManager Backup Utility does not clear CDR and Cisco CallManager .DMP fails after backup.

Cisco CallManager available hard drive space diminishes over time.

Workaround: If hard drive space is at a premium, the CDR.DMP and CCM030x.DMP files may be removed once the MCS.TAR / MCS.STI file has been physically backed up and verified.

CSCdv46861

Meetme Conf does not end after call transferred into it from Unity

A call, whether from the PSTN or internal that joins a Meetme conference by being transferred from a Unity Call Handler prevents the MeetMe conference from closing when all parties have left the conference. The bridge remains up and anybody can call the bridge number and join the conference.

Workaround: None exists.

CSCdv46861

MeetMe conference does delete after a call is transferred into it by Cisco Unity.

A call, whether from the PSTN or internal, that joins a MeetMe conference by being transferred from a Cisco Unity Call Handler prevents the MeetMe conference from being destroyed when all parties have left the conference. The bridge remains up and anybody can call the bridge number and join the conference.

Workaround: None exists.

CSCdv49164

Subscriber install does not work with special characters in password.

When installing C isco CallManager Release 3.0(8) from CD, the subscriber install does complete if the passwords for the administrator and SQL SA accounts contain special characters such as "=" or "/." A message indicates that the subscriber could not authenticate successfully to the publisher.

Workaround: Change the administrator and SA passwords, so they do not contain special characters on the publisher.

CSCdv54488

Transfer button intermittently fails to work.

When the user pushes the Transfer button, it does not provide a secondary dial tone, and you can still hear the user on the line.

Workaround: None exists.

CSCdv55707

The DEFAULT column of ccmGroup table is incorrect.

The value of this column is 0 for Non-Default groups.

Workaround: None exists.

CSCdv55720

TimeZoneOffset of CMLocal is incorrect.

It returns 0 but the correct value should be -8.

Workaround: None exists.

CSCdv55900

Voice-mail ports are not handled correctly during a voice-mail port failure.

If the first configured voice-mail port (the voice mail pilot number) is not currently registered to Cisco CallManager for any reason and a phone rolls as call forward busy or call forward no answer to voice mail, the VoiceMailMaximumHopCount service parameter setting is not honored. Instead the ForwardMaximumHopCount service parameter will be used. If the ForwardMaximumHopCount is set to a number less than the total number of configured voice mail ports, the calling party may receive a reorder tone even if there are available voice-mail ports.

Workaround: Increase ForwardMaximumHopCount value to match the number of configured voice-mail ports or 50, whichever is the lesser value.

CSCdv56339

The Cisco WebAttendant version number is not correct on the Cisco WebAttendant interface.

If you look at the product version of the Cisco WebAttendant plugin download, it is 3.0(12.0). But on the Cisco WebAttendant interface setting, the version is 3.0(10.0).

Workaround: None exists.

CSCdv57272

Calls to ICM do not work without JTAPI bounce after Cisco CallManager updates.

Agents can no longer log into their phone.

This occurs because the CTI layer in the Cisco CallManager is not informed of changes on the lines of the phones when the agents try to log in their new lines the Cisco CallManager.

Workaround: Stop and Start the JTAPI process.

CSCdv58415

Calls route to the incorrect pilot point hunt group.

Calls destined for the members of a pilot point hunt group are incorrectly routed to the members of another pilot point hunt group.

Workaround: Restart the telephony call dispatcher services.

CSCdv58770

Updating the translation pattern causes the Cisco CallManager to reset.

Numerous translation patterns (750 ) using the @ symbol cause the Cisco CallManager to hang while performing digit analysis when trying to add new patterns or update existing patterns.

Workaround: Perform changes only once a day during non-peak hours. This still causes the Cisco CallManager to reset, but has less impact to users.

CSCdv60233

User admin page does not query userid added by AD.

After installing AD plug-in, the User admin page cannot query the user by userid. The userid is added by active directory users and computers. Duplicate by the following steps: Add a user from AD server with the following:

User Name abc

Last Name def

Userid xyz

From CCMAdmin, go to User and Global Directory page

Enter xyz for the basic search

Result: No records found matching your query

Workaround: None exists.

CSCdv61222

Unanswered blind tranfer is charged twice.

Blind transfer calls which are unanswered get charged for even the failed call length.

This occurs only when the blind transfer is attempted by the called party. It does not happen when the calling party is involved in the transfer.

Workaround: None exists.

CSCdv61441

MCS Backup utility should back up hosts file in addition to LMHOSTS.

The MCS Backup utility that ships with Cisco CallManager currently makes a backup of the LMHOSTS file on the server that is being backed up; however, it does not backup the hosts file.

Workaround: Manually rebuild the hosts file after a restore, or manually do a backup of the hosts file in case a restore is needed.

CSCdv61446

A need exists for Cisco CallManager install to check for primary DNS suffix before the install occurs.

On a Cisco CallManager, if you right click on My Computer, click Network Identification tab, click Properties, click more.... The Primary DNS suffix of this computer should be blank. Having anything in this space could cause install problems. The install wrapper should check this field before allowing Cisco CallManager to be installed.

Workaround: Remove anything in the primary DNS suffix prior to installing Cisco CallManager.

CSCdv63172

User cannot drag and drop the dial button on speed-dial numbers.

If you drag the dial button and drop it on any speed dial number, the function does not work. It works the first time after the speed-dial button was assigned a DN number. Next time the SL line of the Cisco WebAttendant goes off hook and does nothing.

Workaround: Drag the speed-dial button and drop on the dial button.

CMTerminals -- Firmware

 

CSCdr53488

Cisco IP Phone 7960 did not work after a Cisco CallManager was stopped and then restarted after about a 30 minute interval.

Workaround: Using the **#** reset sequence on the phone brings it back into operation.

CSCdr55189

Cisco IP Phone 7960 takes 7min to work if pvid of phone is not equal to pvid of Cisco CallManager.

Workaround: No workaround exists.

CSCdt40012

DE 30+ loses D Channel under stress.

This occurs when SimClient is calling into back-to-back DE-30s towards an IVR.

SimClient makes 29 calls. The 30th call is made manually.

Workaround: None exists.

CSCdu44028

Cisco IP Phone 7960 causes slow response when connected to a 10MB NIC card. This problem only occurs when the PC port is running at a different speed from the SW port.

Workaround: No workaround exists.

CSCtr84167

When you enable the service parameter "Block Offnet to Offnet Transfer" and make a blind transfer with Cisco Unity Connection, the Q.931 SETUP message which CUCM sends to the PSTN gateway for an outbound PRI call still reaches the gateway. This transfer results in a dropped call.

Workaround: No workaround exists.



Documentation Updates

This section contains the latest documentation updates for Release 3.0 of the Cisco CallManager, and the latest service parameters that were not included in Release 3.0(5) of the Cisco CallManager documentation. Included in these updates are any changes or late-breaking information that occurred after production of the Cisco CallManager Administration Guide, Release 3.0, Configuring Remote Serviceability for Cisco CallManager Release 3.0, and/or the online help for the Cisco CallManager application, as well as any information that was omitted from the Release 3.0 documents.

New Service Parameters

Table 4 contains new Cisco CallManager service parameters, with descriptions, that were not included in the Release 3.0(5) Cisco CallManager Administration Guide or the online help for the Cisco CallManager application.

Table 4 Cisco CallManager Service Parameter Updates

ParamName
Values
Description

CcmPriorityClass

Default: 0

CcmPriorityClass = 0: Cisco CallManager process runs in normal priority class.

CcmPriorityClass = 1: Cisco CallManager process switches between normal and high priority class every second.

CcmPriorityClass = 2: Cisco CallManager process runs in high priority class.

CTINewCallAcceptTimeout

Default: 4 (seconds)

Specifies timeout interval. Timer ensures that, for calls made into CTI ports and CTI route points, the calls are not suspended, so that callers hear only silence; if the CTI application controlling the CTI ports/route points does not handle the call.

After the Cisco CallManager notifies the application (using JTAPI/TAPI) of an incoming call at a CTI port or CTI route point, the Cisco CallManager waits for a configurable time for the application to handle the call (as in accept, answer, redirect, or disconnect). If the application does not respond within the set time, Cisco CallManager forwards the call to the call forward busy number configured for the CTI port or CTI route point. If no call forward busy is configured, caller receives a fast busy tone.

CTIRequestTimeout

Default: 5 (seconds)

Specifies timeout interval. Timer ensures responses to CTI requests are generated for situations where network or remote Cisco CallManager node problems prevent the normal processing of the CTI requests.

This timer services the following specific CTI requests:

LINE_CALL_INITIATE_REQUEST

CALL_ACCEPT_REQUEST

CALL_ANSWER_REQUEST

CALL_BLIND_TRANSFER_REQUEST

CALL_DISCONNECT_REQUEST

CALL_HOLD_REQUEST

CALL_RETRIEVE_REQUEST

CALL_SETUP_CONFERENCE_REQUEST

CALL_SETUP_TRANSFER_REQUEST

DtSilenceFlag

Default: F

Designates whether silence plays. When this flag is set, the digital gateway does not play silence after receiving the Alert message. This may enable a full duplex path before the Connect message is received on ISDN calls.

IpTosCm2Cm

Default: 3

Controls Class of Service for IP traffic and signals between Cisco CallManager to Cisco CallManager.


Note The following list shows that the valid value for IpTosCm2Cm is between 0 and 7 and is represented as follows:

0 = routine
1 = priority
2 = immediate
3 = flash
4 = flashOver
5 = critical
6 = internet
7 = network

 

IpTosCm2Dvce

Default: 3

Controls class of service of IP traffic and signals between Cisco CallManager to device.

Controls class of service of IP traffic and signals between Cisco CallManager to Cisco CallManager.


Note The following list shows the valid value for IpTosCm2Dvce is between 0 and 7 and is represented as follows:

0 = routine
1 = priority
2 = immediate
3 = flash
4 = flashOver
5 = critical
6 = internet
7 = network

 

MaxCTI Connections

Default: 400

Designates the maximum number of CTI connections. Cisco CallManager allows a maximum number of CTI connections. Typically, each CTI application (or instance of the application) has a single CTI connection to the Cisco CallManager; for example, each Cisco IP Softphone instance has a single CTI connection to the Cisco CallManager. This limit on the number of CTI connections is independent of the number of CTI devices that the application can control.

MaxStationsInitPerSecond

Default: 10

Designates throttling the number of phones allowed to concurrently register with Cisco CallManager without being queued. Parameter as an integer value ranges usually between 5 and 15.


Note If the performance value is set too high, phone registrations could slow the Cisco CallManager real-time response. If set too low, the total time for a large group of phones to register will be slow.

NumberingPlanInfo

Default: 1

Gives some control over the ISDN Numbering Plan Information field on the Called Party Number. This control that is available for H.323 calls and ISDN calls has the following characteristics:

If set to 0: disabled

If set to 1: a check determines what the ISDN Type of Number on the called party information element is. If the Type of Number is set to UNKNOWN, the Numbering Plan Information is also set to UNKNOWN.

If set to 2: The Numbering Plan Information is set to a PRIVATE PLAN, and the Type of Number is set to UNKNOWN.

ReorderRouteList

Default: F

Specifies when set to true that devices that have the same selection order in a route group, and are associated with a route list, are re-ordered when a call is placed using the associated route list.

StopRoutingOnOutOfBandwidthFlag

Default: F

Specifies when set to true, that if a call being routed through a route list detects the associated "cause" during the release of the call, no re-routing to the next device in the route list is attempted and the call is released with the associated cause.

StopRoutingOnUnallocatedNumberFlag

Default: F

Specifies when set to true, that if a call being routed through a route list detects the associated "cause" during the release of the call, no re-routing to the next device in the route list is attempted and the call is released with the associated cause.

StopRoutingOnUserBusyFlag

Default: F

Specifies when set to true, that if a call being routed through a route list detects the associated "cause" during the release of the call, no re-routing to the next device in the route list is attempted and the call is released with the associated cause.

TosBitPosition

Default: 3

Allows setting a bit between bit 0 and bit 4 along with IPTOS settings to make it compatible with Cisco DIFF-SERV (Differentiated Service).

VoiceMailMaximumHopCount

Default: 12

Used together with AdvancedCallForwardHopFlag, allows the Cisco CallManager to select the next available voicemail port by skipping the busy or unregistered voicemail ports.


Note Set VoiceMailMaximumHopCount to the number of voice-mail ports in the system.

 


Service Parameters

Table 5 contains new Cisco CallManager service parameters, with descriptions, that were not included in the Release 3.0 Cisco CallManager Administration Guide or the online help for the Cisco CallManager application.


Caution Do not modify any defaults or settings of the following parameters without the assistance of the Cisco Technical Assistance Center (TAC).

Table 5 Cisco CallManager Service Parameters Not Included in Release 3.0 Documentation 

ParamName
Description

EnableSNMP

This parameter enables the collection of SNMP data from the Cisco CallManager.

EnableStatistics

This parameter enables or disables collection of performance monitor statistics by the Cisco CallManager.


Table 6 contains new Cisco Messaging Interface (CMI) service parameter definitions that were not included in the Release 3.0 Cisco CallManager Administration Guide or the online help for the Cisco CallManager application.


Caution Do not modify any defaults or settings of the following parameters without the assistance of the Cisco Technical Assistance Center (TAC).

Table 6 CMI Service Parameters Not Included in Release 3.0 Documentation   

ParamName
Description

BackupCallManagerName

This parameter defines the names of the Cisco CallManagers that are going to be used for the Cisco CMI backup. You can use either the name of a Cisco CallManager or its IP address.

BaudRate

Cisco CMI connects to the voice mail system via an ETA/TIA-232 connection. This parameter defines that connection.

Recommended default value: 9600


Note Many voice mail systems can be configured to use different baud rates, but the one shown here will frequently be correct.

CallManagerName

This parameter defines the names of the Cisco CallManagers that are going to be used for the primary Cisco CMI. You can use either the name of a Cisco CallManager or its IP address.

DataBits

CMI connects to the voice mail system via an ETA/TIA-232 connection. This parameter defines that connection.

Recommended default value: 7

DialingPlan

This parameter is one of four that are required by Cisco CMI to register an intercept for the voice mail system with which CMI is going to work.


Note Small systems without a complex dialing plan usually only need the VoiceMailDn parameter. The remaining parameters, DialingPlan, RouteFilter, and VoiceMailPartition, will default to empty strings.

InputDnSignificantDigits

This parameter is designed to accommodate the differences between voice mail mailbox numbers and DNs. If a Legacy voice mail system has mailbox numbers that are longer than the DNs on the system, this parameter can be used to strip the most significant digits. The numeric value of this parameter indicates how many digits should be used.


Note No provision exists for stripping digits other than leading ones.

Recommended default value: 10

KeepAliveDn

For most voice mail systems, a value of F is acceptable for a string parameter. However, some Octel systems periodically send an invalid DN specifically for the purpose of verifying that the attached Cisco CallManager is functioning properly. In this case, you can turn off ValidateDns if you know the DN that the Octel system will use as a keepalive. By programming that DN into the KeepAliveDn parameter, you will ensure that the invalid DN message is returned to the voice mail system when needed.

OutputDnFormat

Use this parameter to format the DNs sent to the voice mail system. Most numbers passed to the voice mail system are formatted using this parameter.

Default value: %010s

OutputExternalFormat

Use this parameter is to format the DNs sent to the voice mail system. Calling party DNs that are seven digits or longer are formatted using this parameter.

Default value: %010s

Parity

Cisco CMI connects to the voice mail system via an EIA/TIA-232 connection. This parameter defines that connection.

Recommended default value: Even


Note The parity settings can be None, Even, Odd, Mark, or Space. Settings are usually Even and None, with Mark and Space rarely being used. Just using the first character of the parity name also works.

RouteFilter

Cisco CMI requires this parameter is one of four required to register an intercept for the voice mail system with which CMI is going to work.


Note Small systems without a complex dialing plan usually only need the VoiceMailDn parameter. The remaining parameters, DialingPlan, RouteFilter, and VoiceMailPartition, will default to empty strings.

SerialPort

Cisco CMI connects to the voice mail system via an EIA/TIA-232 connection. This parameter defines that connection.

Recommended default value: COM1


Note The SerialPort name should be the same name that you see in Device Manager under NT.

SsapiKeepAliveInterval

During normal operations, CMI will be attached to a Cisco CallManager. When this is the case, CMI sends a keepalive message to the Cisco CallManager at the rate specified by this numeric parameter.

Default value: 30 seconds


Caution Do not change this parameter from the default value unless directed by the Cisco Technical Assistance Center (TAC).

StopBits

Cisco CMI connects to the voice mail system via an EIA/TIA-232 connection. This parameter defines that connection.

Recommended default value: 1

ValidateDns

When CMI receives incoming lamp commands from the voice-mail system, it normally validates the DN against the NumPlan table. This is an attempt to verify that the DN matches an existing DN known to Cisco CallManager. If the DN is not found in NumPlan, an invalid DN message is sent to the voice mailbox.

Default value: T


Note On a system with a lot of traffic to and from the voice mail system, you may choose to skip this validation process by setting the ValidateDns parameter default to F.

VoiceMailPartition

CMI requires this parameter is one of four required by to register an intercept for the voice mail system with which CMI is going to work.


Note Small systems without a complex dialing plan usually only need the VoiceMailDn parameter. The remaining parameters, DialingPlan, RouteFilter, and VoiceMailPartition will default to empty strings.

Server Name Change

Change the CiscoWorks2000 server name by editing the SAenvproperties.ini file manually, then restarting the Cisco Syslog Collector service. In future releases, an administrative interface will be available for this purpose.

Running Show Tech

To run show tech correctly, use this example to construct your command:

        show -f output.txt -v -w480 db

The example given in the Show Command chapter of Configuring Remote Serviceability for Cisco CallManager 3.0 (page 3-2) lacks a space before "db."

Changes

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

Default Value Changed for SdlTraceTotalNumFiles Service Parameter

SdlTraceTotalNumFiles is a service parameter for the Cisco CallManager service type. The default has been changed to 250. This is the correct default for this service parameter.

Omissions

This section contains lists of service parameters for the Cisco CallManager that were not included in the initial production of the Cisco CallManager Administration Guide, Release 3.0 and online help for the Cisco CallManager application. A later release of the document will define these parameters.


Caution Do not modify any of the defaults or settings of the following parameters without the assistance of the Cisco Technical Assistance Center (TAC).

Cisco CallManager Service Parameters

The following list contains the service parameters, which can be configured for the Cisco CallManager service type, that were omitted from the Release 3.0 Cisco CallManager Administration Guide and online help for the Cisco CallManager application:

AlwaysUsePrimeLine

CallAcceptTimer

CallerId

CgpnScreeningIndicator

CtiApplicationHeartBeatTime

DeviceStatusPollInterval_msec

DialPlanPath

EnableSNMP

EnableStatistics

FlashHookDuration_msec

GatekeeperRefresh

H225BlockSetupDestination

MaxDaResponseTimeoutErrorCount

MaxNumberOf723Calls

MGCPConnectTime

MGCPRespTimeout

MGCPTimeout

RASInboundLRQFlag

RASOutboundLRQFlag

SdlListeningPort

SdlTraceDataFlags

SdlTraceDataSize

SdlTraceFilePath

SdlTraceFlag

SdlTraceTypeFlags

SendingCompleteIndicator

ToneOnCallForward

TypeOfCalledNumberForH225Devices

VoiceMail

Cisco TFTP Service Parameters

The following list contains the service parameters, which can be configured for the Cisco TFTP service type, that were omitted from the Release 3.0 Cisco CallManager Administration Guide and online help for the Cisco CallManager application:

AlternateFileLocation1

AlternateFileLocation2

AlternateFileLocation3

AlternateFileLocation4

AlternateFileLocation5

AlternateFileLocation6

AlternateFileLocation7

AlternateFileLocation8

AlternateFileLocation9

AlternateFileLocation10

Cisco Messaging Interface Service Parameters

The following list contains the service parameters, which can be configured for the Cisco Messaging Interface (CMI) service type, that were omitted from the Release 3.0 Cisco CallManager Administration Guide and online help for the Cisco CallManager application.

BackupCallManagerName

BaudRate

CallManagerName

DataBits

DialingPlan

InputDnSignificantDigits

KeepAliveDn

OutputDnFormat

OutputExternalFormat

Parity

RouteFilter

SsapKeepAliveInterval

StopBits

ValidateDns

VoiceMailParition

Cisco IP Voice Media Streaming Service Parameters

The following list contains the service parameters, which can be configured for the Cisco IP Voice Media Streaming service type, that were omitted from the Release 3.0 Cisco CallManager Administration Guide and online help for the Cisco CallManager application:

CFB:CallCount

CFB:RunFlag

MTP:CallCount

Cisco Enterprise Service Parameters

The following list contains the service parameters, which can be configured for the Cisco Enterprise service type, that were omitted from the Release 3.0 Cisco CallManager Administration Guide and online help for the Cisco CallManager application:

DBL:DatabaseVersion

MessageWaitingDirn

Errors

This section contains any errors contained in the Cisco CallManager Administration Guide for Release 3.0 and/or the online help for the Cisco CallManager application. The upcoming release of the document and online help application will correct these errors.

Incorrect Name of MwiSearchSpace Service Parameter

The name of the Cisco Messaging Interface (CMI) service parameter appears incorrectly in the documentation and online help application. The parameter name should be MwiSearchSpace. The documentation is also missing a description of the value to be entered. The value to enter for MwiSearchSpace is a colon-separated list of partition names. For example, dallas01:dallas02:dallas03, where dallas01, dallas02, and dallas03 are names of partitions.

Incorrect Definition for HoldType and ToneOnHoldTime

The definitions for the Cisco CallManager HoldType and ToneOnHoldTime service parameters are incorrect in the Cisco CallManager Administration Guide and online help for Cisco CallManager Release 3.0. The correct definitions are as follows:

HoldType — Determines whether the hold light flashes more rapidly for the user who placed a call on hold in the case where two different phones share the same directory number. The default value is still F.

ToneOnHoldTime — Determines the time interval between tones when a call is on hold. The default is 10 seconds, and the value range is 3 to 99999.

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:

http://www.cisco.com

http://www-china.cisco.com

http://www-europe.cisco.com

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:

http://www.cisco.com/public/ordsum.html

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

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

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

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:

http://www.cisco.com

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:

http://www.cisco.com/tac

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:

http://www.cisco.com/register/

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:

http://www.cisco.com/tac/caseopen

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:

http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml

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.