Guest

Cisco Unified Communications Manager (CallManager)

Release Notes for Cisco CallManager Release 3.0(8)

 Feedback

Table Of Contents

Release Notes for Cisco CallManager Release 3.0(8)

Contents

Introduction

System Requirements

Determining the Software Version

Related Documents

New and Changed Information

New Software Features in Release 3.0(8)

Strong Encryption

Global Call ID

New Software Features in Release 3.0(7)

Important Notes for Release 3.0(7)

Service Parameter Restart Conditions

Cisco IP Phone 7910 and Cisco IP Phone 7940 Compatibility Issue

New Software Features in Release 3.0(6)

Cisco WebAttendant

Tech Prefixes

Service Parameter

Important Notes for Release 3.0(6)

Cisco IP Phone 7910 and Cisco IP Phone 7940 Compatibility Issue

New Hardware and Software Features in Release 3.0(5a)

Support for New Cisco IP Phones

TAPI 2.1 and JTAPI 1.2 Service Providers

Multicluster Scalability and ITU-T H.323 Enhancements

Cisco IP Phone Services on Cisco Pixel-Based Display Phones

Corporate Directory Dialing from Cisco IP Phones

Additional MGCP Support for Cisco VoIP Gateways

Cisco VG200 FXO Hookflash Support

AMIS-A Support

User Interface Enhancements

Important Notes for Cisco CallManager Release 3.0(5a)

Computer Telephony Integration

BAT Reinstallation

IOS Version

Intercluster Trunk Configuration

Cisco CallManager Integration with Corporate LDAP Directories

Cisco IP Phone 7910 and Cisco IP Phone 7940 Compatibility Issue

Resolved Caveats

Resolved Caveats - Release 3.0(8)

Resolved Caveats - Release 3.0(7)

Resolved Caveats - Release 3.0(6)

Resolved Caveats - Release 3.0(5a)

Open Caveats

Open Caveats for Cisco CallManager Release 3.0(8)

Troubleshooting

Documentation Updates

New Service Parameters

Configuring the Microsoft Telnet Daemon for Bridged Telnet

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

Service and Support

Obtaining Documentation

World Wide Web

Documentation CD-ROM

Ordering Documentation

Obtaining Technical Assistance

Cisco.com

Technical Assistance Center

Documentation Feedback


Release Notes for Cisco CallManager Release 3.0(8)


February 22, 2001

These release notes describe the new features and caveats for Cisco CallManager Release 3.0(8). Use these release notes in conjunction with the Installing Cisco CallManager Release 3.0(8) document, located on Cisco Connection Online (CCO), and the Cisco Documentation CD-ROM. The Installing Cisco CallManager Release 3.0(8) document is also packaged with your CDs or convergence server.

The latest software upgrades and release notes for Cisco CallManager 3.0(8) are available on Cisco Connection Online (CCO) at

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

Contents

These release notes discuss the following topics:

Introduction

System Requirements

Determining the Software Version

Related Documents

New and Changed Information

Resolved Caveats

Open Caveats

Troubleshooting

Documentation Updates

Service and Support

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

Cisco CallManager Release 3.0 must be installed and configured on a Cisco Media Convergence Server.

When upgrading to Cisco CallManager Release 3.0(8) from CCO, you are prompted to install Service Pack 1 and then the hot fix.


Caution You must first install the Service Pack 1 and then the hot fix. Installing them in the improper order causes the installation to fail.

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

Determining the Software Version

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

Related Documents

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

Cisco CallManager Administration Guide for Release 3.0(8)

Cisco WebAttendant User Guide

Cisco WebAttendant Quick Start Guide

Cisco JTAPI Developer Guide

Cisco TAPI Developer Guide

Troubleshooting Guide for Cisco CallManager Release 3.0(8)

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

Software License Agreement

Installing Cisco CallManager 3.0(8)

Quick Start Guide for Cisco CallManager Release 3.0

New and Changed Information

New Software Features in Release 3.0(8)

The following sections contain new and changed software features in Cisco CallManager Release 3.0(8).

Strong Encryption

Cisco CallManager Release 3.0(8) contains low encryption (56-bit or less) in all of its components.

Access the Cryptographic Software link from the main CCO download location at http://www.cisco.com/pcgi-bin/tablebuild.pl/callmgr for applications that contain 128-bit encryption, such as, TNDconnect.exe (Bridged Telnet application) and DC directory .dll extensions.


Note Versions preceding Cisco CallManager Release 3.0(8) included TNDconnect.exe (Bridged Telnet application) and DC Directory .dll extensions that contain strong encryption (128-bit).

Global Call ID

The TAPI Service Provider (TSP) version 3.0 that is packaged with Cisco CallManager 3.0 supports Global Call ID.

Applications use the Global Call ID to identify a specific call as it traverses various resources in the Cisco CallManager. For example, a Call Center application uses Global Call ID to track a call that comes into a CTI Route Point, gets redirected to a CTI Port, and terminates at an Agent's IP Phone.

New Software Features in Release 3.0(7)

Cisco CallManager Release 3.0(7), a maintenance release, adds no new features. Refer to the "Resolved Caveats" section for more information.

Important Notes for Release 3.0(7)

Service Parameter Restart Conditions

If you modify any of the service parameters in the following list, you must restart the Cisco CallManager 3.0(7) 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).

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/pcgi-bin/tablebuild.pl/callmgr.

New Software Features in Release 3.0(6)

The following sections contain new and changed hardware and software features in Release 3.0(6) of Cisco CallManager.

Cisco WebAttendant

Cisco WebAttendant supports the traditional role of a manual attendant console. Associated with a Cisco IP Phone, the application allows the attendant to quickly accept and dispatch calls to enterprise users. An integrated directory service provides traditional busy lamp field (BLF) and direct station select (DSS) functions for any line in the system. The application is Web-enabled and, therefore, portable to Windows 98, NT, and 2000 platforms.

As one of its primary benefits over traditional attendant console systems, Cisco WebAttendant monitors the state of every line in the system to efficiently dispatch calls. The absence of a hardware-based line monitor device offers a much more affordable and distributable manual attendant solution than traditional consoles.


Note Each Cisco CallManager in a cluster can process as many as 2000 Cisco WebAttendant calls per hour.

Tech Prefixes

Cisco CallManager Release 3.0(6) supports tech prefixes in the Gatekeeper. To properly configure the Cisco CallManager to register with a tech prefix you must go to service parameters and perform the following steps:


Step 1 Choose Cisco CallManager.

Step 2 Choose Cisco CallManager from Configured Services.

Step 3 Enter GateKeeperSupportedPrefix in the Params section.

Step 4 Choose String as the type.

Step 5 Click update.

Step 6 Select GateKeeperSupportedPrefix from the Configured Service Parameters.

Step 7 Add the proper value; i.e., 1#, 2#, etc. Only one tech prefix is allowed.

Service Parameter

Cisco CallManager Release 3.0(6) supports a new service parameter.

MaxCTIConnections—This parameter sets the maximum number of simultaneous active CTI connections between an application and the Cisco CallManager. The default value is 400 connections.

Important Notes for Release 3.0(6)

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/pcgi-bin/tablebuild.pl/callmgr.

New Hardware and Software Features in Release 3.0(5a)

The following sections contain new and changed hardware and software features in Release 3.0(5a) of Cisco CallManager.

Support for New Cisco IP Phones

These new phone models, Cisco IP Phone 7910, Cisco IP Phone 7910-SW+, and Cisco IP Phone 7940, broaden the product line of Cisco IP phones.

Cisco IP Phone 7910—This is a single-line Cisco IP Phone with the following features:

Two-line, 24-character display

Four fixed function buttons (Line, Hold, Transfer, Settings)

Six programmable buttons

Hands-free dialing speaker

Single 10 BaseT (RJ-45) connector

Message waiting indicator

Provision for either inline or local plug power

Cisco IP Phone 7910-SW+—This is a single-line Cisco IP Phone with the following features:

Two-line, 24-character display

Four fixed function buttons (Line, Hold, Transfer, Settings)

Six programmable buttons

Hands-free dialing speaker

Dual 10/100 BaseT (RJ-45) connectors into dual port 10/100 BaseT switch

Message waiting indicator

Provision for either inline or local plug power

Cisco IP Phone 7940—This is a two-line Cisco IP Phone with the following features:

Line buttons assignable as either lines or speed dials

Pixel-based display

Four soft keys with context-sensitive features

Five fixed function buttons (Messages, Services, Information, Directory, Settings)

Full-duplex speakerphone

Message waiting indicator

Dual 10/100 BaseT (RJ-45) connectors into dual port 10/100 BaseT switch

Provision for either inline or local plug power

TAPI 2.1 and JTAPI 1.2 Service Providers

The Microsoft Telephony Application Programming Interface (TAPI) and Java Telephony API (JTAPI) service providers enable development of sophisticated, converged multimedia applications. These APIs support the following Cisco applications in this release:

Cisco IP SoftPhone

Cisco IP Contact Center

Cisco IP Interactive Voice Response System

Cisco IP Auto Attendant

E-Services Application Engine

In addition, third-party software vendors may develop applications using these APIs. This release does not support Service Providers Interface redundancy.

Multicluster Scalability and ITU-T H.323 Enhancements

Cisco CallManager Release 3.0(5a) adds the following scalability and ITU-T H.323 enhancements for multicluster environment in which call admission control is provided by Cisco's H.323 gatekeeper, the Cisco Multimedia Conference Manager (MCM):

Simpler configuration—Previous versions of Cisco CallManager required all Cisco CallManagers in separate clusters to be configured in the Cisco MCM as a source address/destination address (SA/DA) pair. Registration by cluster pairs meant that for a ten-site system, 90 (9 x 10) separate entries would be required in the Cisco MCM configuration. Also, because the SA/DA name required a hexadecimal address, configuration at the Cisco MCM and in the Cisco CallManager database was error prone. Cisco CallManager Release 3.0(5a) allows individual gatekeeper-controlled Cisco CallManagers to be configured at the Cisco MCM and allows a Cisco CallManager host name or dotted decimal IP address to be used instead of a hexadecimal address.

More efficient Cisco CallManager to H.323 Gatekeeper registration—Cisco CallManager can register to the Cisco MCM using full RRQ upon Cisco CallManager initialization. Subsequent RRQs are periodically sent to the gatekeeper as a keep-alive function. In Cisco CallManager Release 3.0(5a) the lightweight RRQ format of H.225 RAS specification is used to reduce periodic-processing burden on the Cisco MCM CPU.

Admission Request (ARQ) enhancements—When an intercluster call is initiated, the gatekeeper-controlled Cisco CallManager in a cluster issues the E.164 address of the destination in its ARQ to the MCM. Also, the gatekeeper-controlled Cisco CallManager in the source cluster accepts the IP address of the destination device in the resulting Admission Confirm (ACF) message.

Gatekeeper-controlled Cisco CallManagers, during the initial RRQ, send a full E.164 address range Cisco MCM—Cisco MCM will accept the registration now that it is aware of the full E.164 address range of the cluster associated with that gatekeeper-controlled Cisco CallManager. Future enhancements to the Cisco MCM software will include the ability for Cisco MCM to automatically add the address ranges to the Cisco MCM dial plan.

Cisco IP Phone Services on Cisco Pixel-Based Display Phones

Cisco IP Phone 7940 and Cisco IP Phone 7960 have an HTTP client with an XML parser. When a user presses the Services fixed-function button, the HTTP client will attach to a preconfigured (by the administrator) URL. This URL will display a menu of available HTML/XML services for the user. These services are normally located on an HTTP server separate from the Cisco CallManager or applications server. When the user selects one of the services, the service emits XML tags to the same phone according to the design behavior of the service. XML tags for menu display, item selection, graphics display, and character display are available. Customers may create HTML/XML services that are accessible to pixel-based Cisco IP Phone displays.


Note The eXtensible Markup Language (XML) Application Programming Interface (API) is available for end-user application development. The description of this API is documented in Cisco IP Phone Services Application Development Note, which is available for download from CCO at http://www.cisco.com/univercd/cc/td/doc/product/voice/sw_ap_to/ under the category "Third-Party Application Development Guides."

Assistance to resolve bugs in the API is available through TAC. Assistance for application development is not available through TAC. Applications development assistance will be made available in the near-term through a specifically tasked help desk. Until that help desk is available, application development support is not available for the XML API.

Corporate Directory Dialing from Cisco IP Phones

The Cisco IP Phone 7940 and Cisco IP Phone 7960 display a menu of directories when a user presses directories. When the user selects Corporate Directory from the menu, the phone presents the option of specifying characters to find the destination user's first name, last name, or directory number. The user may enter any number of characters in any of these fields, then press Search. An HTTP request goes to an HTML service, which queries the embedded Cisco CallManager directory. The HTML service then delivers, through XML tags, the complete listing of matched user entries to the phone's display. The user may then scroll to select the destination entry and press Dial to initiate the dial sequence to that destination.

Additional MGCP Support for Cisco VoIP Gateways

Media Gateway Configuration Protocol (MGCP) support provides two primary benefits over H.323 support. First, MGCP provides a centralized dial plan. An H.323 network requires that the dial plan for each gateway be statically configured. Every dial plan change requires updating the dial plan in every gateway. MGCP provides centralized dial plan configuration support at the Cisco CallManager.

Cisco CallManager Release 3.0(5a) adds MGCP support for the following Cisco VoIP gateways:

Cisco 2600 Series gateways with FXS and FXO analog interfaces

Cisco 3600 Series gateways (362X, 364X, 366X) with FXS and FXO analog interfaces


Note At Cisco CallManager Release 3.0(5a), MGCP code support in the 36XX router/gateways was not complete. Once complete and tested, these gateways will be supported in an AVVID network.

Cisco VG200 FXO Hookflash Support

The added Cisco VG200 FXO hookflash support Symbol NetVision Phones, which are configured as H.323 client devices. The Cisco VG200 can be configured to provide hookflash feature support from H.323 NetVision phones through Cisco VG200 FXO ports attached to PBXs. The NetVision Phones issue H.245 messages through the Cisco CallManager to Cisco VG200 FXO gateways on initiation by the user of PBX functions. The Cisco VG200 gateway interprets the signals and translates them to an FXO hookflash followed by a PBX-specific feature code.

AMIS-A Support

Signaling within the Skinny Gateway Control Protocol client and Skinny Gateway stacks in Cisco CallManager has been extended to properly interpret and pass out-of-band equivalent signals for "A," "B," "C," and "D" DTMF signals. These additional signals can be passed from AMIS-A compliant messaging system through the Cisco AVVID network, out of TDM networks to another AMIS-equivalent voice messaging system. The capabilities allowed include the ability to reply to and forward messages from one messaging system to another.

User Interface Enhancements

Cisco CallManager Release 3.0(5a) makes the following enhancements to the Cisco CallManager Administration configuration pages:

Cisco IP Phone Services Configuration—This new page enables administrators to add, modify, or delete Cisco IP Phone services to which users can subscribe to at their site. To access this page from the main Cisco CallManager Administration page, select Feature > Cisco IP Phone Services.

Cisco uOne Port Wizard—The Cisco uOne Port Wizard enables administrators to quickly configure ports associated with a Cisco uOne messaging server to the Cisco CallManager database. To access the wizard from the main Cisco CallManager Administration page, select Device > Cisco uOne Port; then, click the Cisco uOne Port Wizard link.

CTI Route Point Configuration—This new page enables administrators to add, modify, and delete CTI route points. A CTI route point is a virtual device that can receive multiple, simultaneous calls for the purpose of application-controlled redirection. Applications that use CTI route points include the Cisco IP Interactive Voice Response System. To access this page from the main Cisco CallManager Administration page, select Device > CTI Route Point.

CTI Port Configuration—This new page enables administrators to add, modify, and delete a CTI port configuration. CTI ports are virtual devices that are used by software-based Cisco CallManager applications such as Cisco SoftPhone, Cisco AutoAttendant, and Cisco IP Interactive Voice Response (IVR). To access this page from the main Cisco CallManager Administration page, select Device > Phones; then, select CTI Ports.

Gatekeeper Configuration—You can now access gatekeeper configuration as a separate configuration page where administrators can configure one gatekeeper, or Cisco MCM, per Cisco CallManager cluster. A gatekeeper device supports the H.225 RAS message set used for call admission control, bandwidth allocation, and dial pattern resolution. To access this page from the main Cisco CallManager Administration page, select Device > Gatekeeper.

Cisco WebAttendant Configuration—A new set of added pages enables administrators to configure Cisco WebAttendant pilot points, hunt groups, and users. To access this page from the main Cisco CallManager Administration page, select Service > Cisco WebAttendant.

Gateway Configuration—The modified Cisco CallManager Administration interface includes support for additional MGCP gateways, such as Cisco 2600 Series gateways with FXS and FXO analog interfaces. The MGCP gateway configuration no longer appears as a separate menu item under Device. To access gateway configuration pages from the main Cisco CallManager Administration pages, select Device > Add a New Device; then, select Gateway from the drop-down listbox menu.

Important Notes for Cisco CallManager Release 3.0(5a)

Computer Telephony Integration

Computer Telephony Integration 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 BAT after installing Cisco CallManager 3.0(5a) because of a change made to the database.

IOS Version

The Cisco CallManager Release 3.0(5a) was tested with IOS 12.1(3x)XI2.

Intercluster Trunk Configuration

An intercluster trunk, a virtual .H323 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 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

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/pcgi-bin/tablebuild.pl/callmgr.

Resolved Caveats

Resolved Caveats - Release 3.0(8)

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

Table 1 Cisco CallManager Release 3.0(8) Resolved Caveats 

DDTS Number
Summary
Explanation

CSCdr60534

The Cisco IP Phone 7960 allows Call Forward All to be set even when digits are not dialed.

Changes were made in CMI by way of CSCdt08716 to resolve the issue and not allow CMI to register with an empty DN pattern. If the CMI application doesn't have a valid Mailbox number, it will not start. The forwarding function works as expected after this and gives out a reorder after the timer expires and no digits have been dialed.

CSCds13646

AVVID: SNMP agent is missing on Cisco CallManager. MIBII Host Branch

The vendor's SNMP Extension Agent provides the functionalities for browsing the MIB II tree through the SNMP Agent; therefore, it is not in the domain of the Cisco CallManager SNMP Extension Agent.

CSCds34122

A failure to delete or reset the MGCP gateway exists in the find&list gateway page.

The Cisco CallManager code change handles MGCP gateway delete and reset from Find&List gateway page.

CSCds43704

Call looping uses CPU and other resources in Cisco CallManager

A Cisco CallManager code change fixed this problem.

CSCds50672

Call Forward All from a directory number to the same directory number causes high CPU usage.

Call Forward All can no longer be used to call the same directory number.

CSCds53113

User hears a dual ringback tone when calling PSTN using H.323 gateway.

Call control no longer directs the originating device to play ringback on alerting if call control has already cut through media.

CSCds57777

AVVID: PerfMon H.323 gateway is reinstantiated at Cisco CallManager reset of gateway.

The H.323 PerfMon statistics are removed when the H.225D stops.

CSCds65137

No option exists for Subscriber for called and or calling party; i.e., number type.

A Cisco CallManager code changes adds support for Subscriber Number option for Calling/Called party IE number type in the digital PRI gateway configuration page.

CSCds66475

Cisco CallManager does not allow a Automated Install on top of a FAT32b partition. This caveat is fixed on the MCS 7825/7835/7835-1000.

This issue only occurs if the C: drive is changed to FAT32. The auto install will be modified to install over a FAT32 partition regardless of the specific drive associated to that partition.

CSCds67657

1GB virtual memory grab occurs on Cisco CallManager with hot fix.

This fix causes the base virtual memory footprint to be larger than in the past, but it solves the memory losses seen in the past.

CSCds69496

External Call Forward All loop causes high Cisco CallManager CPU usage.

Setting the CallManager Service Parameter MaxForwardsToDn to 0 disables the cause of this problem.

CSCds72125

DisconnectedEvent is received with Cause=CtiResourcesNAvail.

When an external call called a CTI route point, the call was redirected back and forth between a CTI port and an IP phone several times. A code change fixed this problem.

CSCds74298

A call to a shared line results in unreleased bandwidth.

Shared line checks the bandwidth for each device and only consumes for the device active.

CSCds82957

SQL database does not properly tell Cisco CallManager to start after upgrade.

The Cisco CallManager was coming up before the SQL Server. A code change a fixed this problem.

CSCds84419

AVVID: Null translation pattern prevents dialtone on Cisco IP Phone 7960.

This works as designed in the Cisco CallManager.

CSCds88597

Display issue exists during MeetMe and AdHoc conference calls.

The display change no longer shows the Conference number. The screen displays "To Conference" for MeetMe as well as AdHoc Conferences.

CSCds89614

Call Pickup stops working.

Cisco CallManager software has been modified to fix a call scenario that will break the Call Pickup feature. The call pick up table entry needs to be removed after the original destination party has had a Call Forward No Answer put into effect to a new destination and that new destination has a Call Forward setup to another destination.

CSCds89808

Cisco CallManager crashes when receiving ISDN setup with non-call-associated signaling.

Cisco CallManager software was modified to block the call because it does not support non-call-associated signaling on a D-channel.

CSCds91028

Cisco CallManager does not apply the calling party transform mask.

The code change allows a customer to configure a Caller ID mask on the gateway configuration web page, so the last redirecting or first redirecting numbers display in the "Calling Party" field of the ISDN primary setup message in the full E.164 format.

CSCds91320

AVVID: PerfMon ccmActivePhones counter is incorrect.

A Cisco CallManager code change allows the PerfMon counter to display correctly.

CSCdt02726

Consult call fails throwing exception.

A Cisco CallManager code change corrected this problem.

CSCdt04309

Disable ring on a shared line does not work properly on blind transfer.

The problem of keying on the wrong directory number was fixed.

CSCdt06347

When device is deleted, the forward intercept table is not updated.

The call-forwarding properties associated with this deleted device remain valid to Cisco CallManager even though the device no longer exists.

CSCdt07520

User receives error message when changing partition on phone line.

A Cisco CallManager code change corrected this problem.

CSCdt07581

Insert new user page does not update WA AutoDial name correctly

In the Cisco CallManager Release 3.1 User Preferences, the user manually configures the Auto Attendant name dialing and it will not be populated automatically.

CSCdt08275

Call forward does not work for the second time with IVR route point

A Cisco CallManager code change corrected this problem.

CSCdt08446

Gatekeeper Device pool change requires resetting the PC.

A Cisco CallManager code change corrected this problem.

CSCdt09642

Deleting a gateway gives error message.

When the deletion succeeds, no error message is given.

CSCdt11706

The wrong redirecting parameters exist for Call Forward No Answer.

A Cisco CallManager code change fixed this caveat.

CSCdt12383

Cisco CallManager may crash when making gatekeeper-controlled calls.

A Cisco CallManager code change corrected this problem.

CSCdt12794

Consult failed due to InvalidStateException.

A Cisco CallManager code change corrected this problem.

CSCdt13681

A directory number started returning busy to callers because too many calls had been forwarded to that number.

A Cisco CallManager code change corrected this problem.

CSCdt15151

A calling party transform mask returns an invalid digit.

A Cisco CallManager code change checks and drops calling party Microsoft Internet Explorer if calling party transform mask returns invalid digit.

CSCdt15834

Deleted shared lines do not auto register.

A Cisco CallManager code change auto registers deleted lines.

CSCdt18271

Phone displays "You have Voice Mail" when the mailbox is empty.

A previously unresolved caveat caused this problem.

CSCdt18312

Call Forward with IVR and Hunt Groups fails after 4 forwards.

The Cisco CallManager code change resets a variable to false when it receives a message, and the new destination number has an intercept table entry. By doing so the Cisco CallManager continues to forward the call after the CTI application redirects the call to a new destination.

CSCdt18313

Select devices button takes you to the wrong web page.

A Cisco CallManager code change fixed this caveat.

CSCdt18621

User cannot delete H.323 gateway without receiving error message.

The error message will not be given if the deletion is successful.

CSCdt18904

Users cannot insert gatekeepers.

A Cisco CallManager code change fixed this caveat.

CSCdt18911

When user adds a phone line, the web page freezes.

A Cisco CallManager code change fixed this caveat.

CSCdt19231

Double forwarding gives transfer exception but no dropped event.

A Cisco CallManager code change resets a variable to false when it receives a message, and the new destination number has an intercept table entry. By doing so, the Cisco CallManager continues to forward the call after the CTI application redirects the call to a new destination.

CSCdt19887

MTP resources reporting status=1, but Cisco CallManager will not jump to better resources.

The Cisco CallManager software has been modified to handle error code 255 from the Cisco Catalyst 6000 - DSP Resource device when there is error in opening the receive channel due to out of resource (transcoder); either the DSP is dead, or no more DSP available in the device. The Cisco CallManager marks the device unavailable, so that the next call uses the next transcoder device. The Cisco Catalyst 6000 - DSP Resource device will wait until all the active calls existing in the device become idle; then, it will reset itself and reregister with the Cisco CallManager.

CSCdt20323

The 3660 router MGCP configuration fails with Cisco CallManager 3.0(6).

A Cisco CallManager code change fixed this caveat.

CSCdt20674

Manual DA restart causes Cisco CallManager restart.

The Cisco Access Digital Trunk Gateway DT - 24+ control process was stopping before a related thread that reads the udp messages coming in from the gateway had stopped. This udp read thread was then trying to access Cisco Access Digital Trunk Gateway DT - 24+ data members that no longer existed in memory, thus causing a crash of Cisco CallManager.

CSCdt21490

MTP resets on 23rd 729-711 transcoding(VAD enabled)

When the CPU time is lower than a low_ watermark, the transcoder takes no new calls (and the calls will not be complete). All new calls will be rejected. The transcoder will not accept new calls until CPU idle time goes above a high watermark. CPU time is regained after some active calls go idle. A high watermark is used to reopen the new channels after entering into a rejection mode, which is entered when a call is rejected by a low watermark. After the change, #24 call or more calls will be rejected but will not cause the transcoder to reset.

CSCdt21581

User experiences a fast busy when transferring a conference.

A Cisco CallManager code change resolved this caveat.

CSCdt23132

Bandwidth control with shared lines results in only 1 line ringing.

A Cisco CallManager code change fixed this problem.

CSCdt25478

Call forwarding on the same phone inherits ring of forwarded lines.

A Cisco CallManager code change fixed this caveat.

CSCdt27176

When user resets DT24 gateway, Cisco CallManager crashes with DrWatson.

A Cisco CallManager code change fixed this caveat.

CSCdt27572

Inbound callers get reorder; B channel is out of service.

A CcRejReq message coming into the B channel process (processpn9cuser) and not being handled caused this bug. The B channel hung in an uncertain state, but the CO in the PSTN received it as available for new calls.

CSCdt27581

User cannot delete partitions. This is an error but m_com_error was not valid.

A Cisco CallManager code change fixed this caveat.

CSCdt28640

Cisco IP Phone 7960 intermittently delays dialtone when going off-hook.

The off hook message was getting delayed only in certain scenarios. A Cisco CallManager code change resolved this caveat.

CSCdt29217

Call Park code correction to avoid blocking of Call Park numbers.

A Cisco CallManager code change fixed this caveat.

CSCdt31546

A DBL exception in MWI message may crash the Cisco Callmanager.

A Cisco CallManager code change corrected this problem.

CSCdt38000

Cisco IP Phone 7960 does not register after cluster-wide outage.

A Cisco CallManager code change insures that if registration is not acknowledged that the phone will recover.

CSCdt38916

CallingParty=Unknown Number does not work with Cisco uOne

A Cisco CallManager code change checks the calling party length field before calling the related function.

CSCdt39262

Cisco CallManager may allow more calls than limited by Locations.

The problem was that the bandwidth to be consumed (24kbps or 80kbps) was an "unsigned int" and it was being compared for greater than a negative "int."

CSCdt39402

Oneway audio exists with DT-24+ Load D003H300.

During the ARP cache timeout, removal of a dynamic entry was causing the port count to go negative. The port count prevents the removal of an address that is being used by several streams. A Cisco CallManager code change prevents the port count variable from going negative during ARP cache timeout.


Resolved Caveats - Release 3.0(7)

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

Table 2 Cisco CallManager Release 3.0(7) Resolved Caveats 

DDTS Number
Summary
Explanation

CSCds11354

No ringback occurs on transfer from PSTN calls coming in on IOS gateway.

With Cisco CallManager 3.0(1) connecting to the PSTN via an H.323 gateway, if a call comes into a phone and it is blind transferred to another phone, the PSTN side will only receive dead air; ringback does not occur.

The Cisco CallManager software has been modified to send the H225UserInfo message to the IOS gateway with Q931 Signal IE, so the IOS gateway can play/stop ringback tone for the call that is being transferred to another party. This fix has to work with the fix for CSCds87266, which was opened against the IOS gateway. The fix for CSCds87266 may not be ready until the next major feature release. Therefore, even the Cisco CallManager can send the h.225 Suriname message to the IOS gateway. The problem cannot be verified until the IOS gateway is fixed.

CSCds28310

Users cannot dial to Cisco uOne using low-bandwidth codec.

Transcoder will now be involved allowing low-bandwidth calls from Cisco SoftPhone to access Cisco uOne.

CSCds34596

 Can't Delete A Server - Error: 
1576 UNDEFINED displays.

The database layer was modified to remove the Database Layer Service when the server is removed.

CSCds35388

AVVID: Installing Cisco CallManager Release 3.0 document incorrectly instructs the administrator to change the password for Cisco CallManagerAdmin and SQLSvc accounts.

Installing Cisco CallManager Release 3.0(5) document has been updated to reflect that you must set the same password for all the Cisco CallManager Admin accounts and the same password for all the SQLSvc accounts for each server in the cluster.

CSCds39670

Incorrect MsgWaitingLampMode is set in CTI LineGetInfoResp for route points.

Set the messageWaitingLampMode member variable to FALSE. Also print out the value of dwMessageWaitiingLampMode in CTIHandler.

CSCds41030

DB Admin does not limit the input for URLs on phone config page.

Limit the input length of "External Data Locations" fields for the Cisco IP Phone 7960 and Cisco IP Phone 7940, and the "URL too long" message will not appear.

CSCds53834

GateKeeper configuration page does not display.

This page does not display with Netscape Navigator.

CSCds55086

Access violation occurs in svchost during Win2K startup on client running Cisco SoftPhone.

Microsoft has a fix, contact Microsoft support for details at the following URL: http://support.microsoft.com/support/kb/articles/q278/7/18.asp.

CSCds58392

Putting a call on hold generates a new call with wrong data.

CallManager.java was modified so it does not set the LastHeldTerminalConn when it is not Consult call.

CSCds65594

Cisco CallManager does not accept a non-ISDN call progress information element when using the 4ESS protocol.

Resolved dropped message by message translation due to the presence of codeset 6 information elements in the SETUP message. MsgTrans shall not drop any ISDN message if locking shift information elements are received. It is up to the pn9* to decide whether the message can be discarded. Also added support of progress indicator for PRI 4ESS setup message.

CSCds73845

Wrong last redirected address in blind transfer where b is only po

CallManager.java was modified to create TransferManager with proper transferController.

CSCds74306

Transfers across locations do not release all bandwidth resources.

Bandwidth is now released after transfer.

CSCds76274

Bandwidth is not returned to pool after H.323 intercluster trunk call failure.

The code was changed to compensate for a failed call and return bandwidth as expected.

CSCds78107

A need exists for a new error message from CTI for directory login timeout.

In the code that queries the directory for user authentication, a case was added to distinguish a directory timeout due to high demand from a login failure. A new error code was also added, so the APIs can also distinguish the two cases and act accordingly.

CSCds78869

Cisco IP Phone 7910 sends cdp with POWER TLV as 6300 mw instead of 5040 mw.

Per hardware engineering, all Cisco IP Phones in the 7900 Family developed thus far have a maximum requirement of 6300 mwatts. This value is now reported via the appropriate TLV in the CDP response in loads P004P301 (Cisco IP Phone 7910) and P003P301 (Cisco IP Phone 7960 and Cisco IP Phone 7940).

CSCds81134

Release messages are missing from Cisco CallManager.

Changes were made to the translation pattern to amend this problem.

CSCds82314

Cisco CallManager will not initialize if many translation patterns exist.

The ability to initialize quickly even if hundreds (tested with 2000 translations) of translation patterns exist was added to the software.

CSCds85150

CTI: gateway call is not producing ringback event.

CTI call state notification is sent, so ringback will be heard.

CSCds85215

Application gets Talking event even though call is over.

CallManager.java was modified to process callClosedEvent, so that it does not send any getCallInfo request.

CSCds85283

Memory leak occurs in call waiting scenario

The Cisco CallManager software was changed to keep memory from growing in specific call waiting scenario.

CSCds87448

IP voice media streaming application uses 100% CPU.

The Cisco CallManager code was changed to recover from a random unhandled internal error causing high CPU usage.

CSCds87552

Blind transfer from voice mail locks up port.

Cisco CallManager software has been modified to reset the intercept entry's dnActive field even when it cannot find the active call entry for the ssParty when receiving the ssDataInd msg.

CSCds90217

CiscoAddrInServiceEv is not sent for softphone.

ProviderImpl and TerminalImpl were changed, so JTAPI opens the CTI Port when DeviceRegisteredEvent for a third-party observer as a result of first-party observers register the CTI Port.

CSCds90743

Cisco CallManager crashes when attempting to add 17 participants to conference bridge.

Cisco CallManager was fixed to prevent crashes caused by array boundary exceeded when the number of conference participants is more than 16.

CSCds91718

Need exists to include CTI Messages in default SDL trace setting.

The default database was changed to facilitate this problem.

CSCds92026

No disconnect event occurs when disconnecting consult conference.

CallManager.java was modified not to set setConferenceFeature during the initialization of the consult Conference call.

CSCds92393

SDL router services are declared dead.

When stationD process receives the ccNotifyReq message and there is no CI associated with the StationCdpc process before we display the information in CcNotifyReq message, one more check needs to be added to make sure there is valid CI to route pattern association; otherwise it will crash the Cisco CallManager.


Resolved Caveats - Release 3.0(6)

Table 3 lists and describes Caveats that were resolved in Cisco CallManager Release 3.0(6).

Table 3 Cisco CallManager Release 3.0(6) Resolved Caveats 

DDTS Number
Summary
Explanation

CSCdr22835

Users cannot change WS-X6608 port type once set without resetting card

Cisco CallManager software was changed to find the correct WS-X6608 port type.

CSCdr74342

DCD: DC Directory gets suspended due to FileSystem error

The problem was due to the file system backup utility locking the file using the win32 LockFile(). LockFile either allows a shared Read lock or an exclusive Read or Write lock. If a shared Read lock has been obtained by a process; no process (including the one that had first opened the file) can write to that file. Thus, if a user attempted to update DCD while the backup utility held a lock on DCD's DB volumes, DCD was unable to write to disk and consequently got into an awkward state. DCD now obtains an exclusive Read/Write lock on startup on its DB volumes. This lock prevents any other process from even opening the file. Thus, DCD is guaranteed that no process can deny it (DCD) write access to its own files once it (DCD) successfully comes up.

CSCdr74342

DC Directory gets suspended due to file system error.

The problem was due to the file system backup utility locking the file using the win32 LockFile(). LockFile either allows a shared Read lock or an exclusive Read or Write lock. If a shared Read lock has been obtained by a process; no process (including the one that had first opened the file) can write to that file. Thus, if a user attempted to update DCD while the backup utility held a lock on DCD's DB volumes, DCD was unable to write to disk and consequently got into an awkward state. DCD now obtains an exclusive Read/Write lock on startup on its DB volumes. This lock prevents any other process from even opening the file. Thus, DCD is guaranteed that no process can deny it (DCD) write access to its own files once it (DCD) successfully comes up.

CSCds18156

Symbol Phone create multiple H225D registered with Line Control

The code has been changed to allow only one H225D to register with LineControl.

CSCds20015

Cisco IP Phone 7960 P3 port does not forward for first 9 seconds after linkup.

A parameter was added to Settings/Network Configuration/Forwarding Delay YES/NO.

CSCds43712

PerfMon statistics appear to be unreliable.

The Cisco CallManager software has been modified so that the PerfMon statistics appear correctly.

CSCds43792

Sending Disconnect with cause equals an unallocated number.

The protocol violation on inbound call was fixed. According to Q.931 standard, Cisco CallManager shall send RELEASE COMPLETE instead of DISCONNECT when unassigned number is received in the SETUP message.

CSCds46180

Slow SDL timer Service using call load of 2.25 cps and IVR

Internal data structures that kept track of call information were not being cleaned up correctly which lead to some inefficiencies over time.

CSCds53378

AVVID: Cisco CallManager upgrade with locations prevents SW-based conference from working.

The code for unlimited bandwidth in location for Cisco CallManager 3.0 does not currently work. Migration has been changed to remove the 0 bandwidth location records and set any devices location using it to NULL. This will, in effect, give that situation no bandwidth limitation.

CSCds57574

WebAttendant will not install on Win98 client machine

Windows operating systems' version of regsvr32.exe could not load the .dll extensions containing the Cisco WebAttendant controls. Each Cisco WebAttendant DLL tries to start a multimedia timer when the DLL is loaded. Starting the timer was moved from the loading of the DLL to when the actual loading of the control by the web browser occurs. This allows the regsvr32.exe to load and register the DLL.

CSCds61655

GetCallInfo returns wrong info on call fwded to route point.

A changed was made previously to save information about the calling, called, and redirected parties during call setup, so this information can be returned in the lineGetCallInfo when the call is forwarded. These changes were made to the code that handles the stations but also needed to be made to the code that handles route points.

CSCds61871

No error message occurs on unauthorized CTI user via TSP.

The problem was corrected by using a timer to introduce a delay between sending the response and closing the pipe.

CSCds63460

BLIND TRANSFER: caller/calledid information becomes messed up on blind transfer.

Cisco CallManager software has been modified to correctly display the calling, called party number, and name for the scenario of a call that was blind transferred to a line, which already had an active call (call-waiting scenario). After the change, the calling, called party number, and name correctly display for both the active call and incoming call.

CSCds63489

Call waiting call is not idled on Call Forward No Answer.

A fix was made to CTI to allow the 3rd and subsequent calls to roll to voicemail or be answered instead of disconnecting or going to fast busy.

CSCds65046

Server logs out Cisco WebAttendant client when the client is idle for 2 minutes.

A race condition was causing TCD to corrupt its keepalive tracking registers for some logged-on clients. This would cause TCD to erroneously determine that the client was dead, closing the TCP connection to the client. Changes were made to prevent this multi threaded race condition from affecting the keep alive logic.

CSCds66353

Cisco CallManager tells MGCP gateway to use VAD when SilenceSuppression is set to False.

The Cisco CallManager software's code was modified to support SilenceSuppression accordingly.

CSCds66507

Cisco WebAttendant client will not install on Windows NT operating system.

Windows operating systems' version of regsvr32.exe could not load the .dll extensions containing the Cisco WebAttendant controls. Each Cisco WebAttendant DLL tries to start a multimedia timer when the DLL is loaded. Starting the timer was moved from the loading of the DLL to when the actual loading of the control by the web browser occurs. This allows the regsvr32.exe to load and register the DLL.

CSCds67120

CTI logs out TCDSRV and drops TCP connection.

The fix was made to process the heartbeat at normal priority.

CSCds67147

Illegal characters are accepted when setting user password.

There are no checks in place when users first enters their password, this is causing the problem since there is a check in place when their password gets validated.

CSCds67766

Install: SAenvProperties.ini is not updated after the install.

The silent portion of the install that Automated Install executes was not calling the code to set this up.

CSCds68278

CTI ports are disabled during upgrades.

The DCD upgrade process has been changed to preserve the existing value of the CTI Application Use Enabled global flag. Thus, if a user has set the value of the global flag to true, the value would still be set to true after an upgrade.

CSCds69538

Conference is in bad state when Cisco AutoAttendant redirects call back to its own ports

When Cisco AutoAttendant is redirected to a second CTI port, a redirect signal is sent to the Conference process inside of Cisco CallManager. The logic in this process was not expecting a conference resource to be an origination point for a redirection. As a result, it never checked for that possibility and did not correctly delete the old information and add new information into its tables regarding the present configuration of the conference.

CSCds70328

Cisco WebAttendant timed out and gave no reorder tone.

Cisco CallManager software was modified to use the correct call reference identifier to build the CcRejInd message when the CtiNewCallAcceptTimer was received so that the CcRejInd message was sent to the correct process to clear the call with reorder tone.

CSCds72813

CTI: Gigantica crashes when opening provider with ctifw user.

Cisco CallManager is crashing when user passes a device name bigger than 15 characters. The problem is happening as user copies longer than 15-character names in CtiDeviceName variable, causing it to have nonnull terminated string. Terminating the string with Null corrected the problem.

CSCds73688

SdlMaxUnHandledExceptions=0 results in StackWalk.

The value was hard coded to 5 and not read from database, and the code was not checking for not equal to zero in 3 of the 16 places.

CSCds74266

Cisco CallManager crashes and restarts; then, it sits idle until manual restart.

The Cisco CallManager software has been modified to rectify this problem.

CSCds76640

State of Logout and Go Offline buttons does not change.

This problem was solved by syncing up the TCD server and the Cisco WebAttendant.

CSCds77578

Cisco CallManager does not cut through after progress with DE30+ (overlap sending).

At the overlap sending situation, the channel ID can be received in setup pack.

CSCds79716

UserPrefs do not work after an upgrade from versions prior to Cisco CallManager 3.0(5a) to Cisco CallManager 3.0(5a).

A race condition between DCD's initialization and the execution of avvid_upgrade caused the problem. The avvid_upgrade script now waits 20 seconds for DCD to finish its initialization before continuing with the upgrade process.

CSCds79952

Cisco CallManager stackwalk for CM2 of Dallas Alpha

Buffer was increased to allow large display names on CTI and phone devices.

CSCds81073

PRIUser ringback does not perceive reorder tone with CallForward Incorrect.

Cisco CallManager software has been modified to process the CcInfoReq message in state:

call_received7 (ProcessPn9cuser) and call_delivered4 (ProcessPn9cnet and ProcessH225Cdpc), and if the cause code value in the CcInfoReq is temporary failure, send the Disconnect message to disconnect the call. By doing so, it prevents the caller from the gateway receiving the ringback tone for a long period of time even when the call was dismissed due to the error while accessing the voice mail (such as voice mail configuration error or hop count exceeded).

CSCds82156

Confusing screen occurs on auto upgrade when selecting publisher/subscriber is selected

The screen was changed to be read more clearly.


Resolved Caveats - Release 3.0(5a)

Table 4 lists and describes Caveats that were resolved in Cisco CallManager Release 3.0(5a).

Table 4 Cisco CallManager Release 3.0(5a) Resolved Caveats 

DDTS Number
Summary
Explanation

CSCdp96950

CPU usage stays up to 100% with svchost.exe.

This was determined to be a Microsoft problem. Currently, a new version of tapisrv.dll fixes this problem.

CSCdr35751

This problem occurs when Call Forward All is cleared from the user preference pages for a DN that is shared by multiple phones (that is, a multiline).

When Call Forward All is cleared on a multiline, a reset is only sent down to one phone that shares the multiline, and the call forward lights are cleared on that phone only. The call forward is cleared for the specified DN, but the forward lights on all other phones will remain on, thus giving a false indication that the phone is still forwarded, when it really is not.

CSCdr40345

Errors are returned by the Cisco CallManager User Administration web pages.

These errors appear when the directory does not contain a complete listing of the devices in the Cisco CallManager database. This occurs when the directory is first configured with a large number of devices to import from the database to the directory.

CSCdr41614

DTMF digits are not propagated to members of a conference.

When a DTMF digit is pressed when a phone is connected to a conference, the digit is dropped.

For example, if a ringing phone is added to a conference, and the phone is subsequently not answered and forwards to voice mail, there is no way to remove that party from the conference, or to exit or shut down voice mail.

CSCdr42883

Memory leaks in the database occur as a result of normal operation of the system.

DLLHost.exe as the executable grows in memory size as changes are made to the database via services or Cisco CallManager Administration. If a long time elapses, the memory size will drop. However, if several services poll the database periodically, this may not occur.

CSCdr49680

When the Cisco Catalyst 6000 8 Port Voice T1 and Services Module is reset while conferences are in progress, the Cisco CallManager will not set up any more conferences.

This occurs when the device re-registers with the Cisco CallManager, and the callers have not yet hung up the phones.

CSCdr50642

After the initial installation, changing a server name to an IP address will cause phones not to boot. Auto-registering phones will not connect to Cisco CallManager.

The reason they do not connect is that the configuration file still contains the server name.

CSCdr51675

When using the Cisco CallManager Control Center web page, the services for a server do not appear when it is selected. The screen displays "A connection to the server could not be established."

This problem occurs under any of the following conditions:

The server hosting the Cisco CallManager Administration web pages cannot resolve the name or IP address of the target server.

The target server is offline.

The target server no longer exists, but it is still configured in the Cisco CallManager Administration pages.

The target server's name in DNS does not match the server's machine name.

CSCdr57242

OutofBandwidthText is not on by default.

A call from a Cisco IP Phone to another Cisco IP Phone gets a reorder tone intermittently. Nothing on the phone display indicates the reason. Further troubleshooting showed that the call was made between locations, and it was out of bandwidth. The Cisco IP Phone should have displayed the "Not Enough Bandwidth" message by default.

CSCdr68109

Cisco CallManager service does not display in Windows 2000 services after subscriber installation.

The publisher and subscriber Cisco CallManager servers are installed. All the Cisco CallManager services appear in Windows 2000 services on the subscriber after installation.

CSCdr75417

Backspace in Telecaster could crash Cisco Call Manager.

While attempting to make an outgoing call from a Cisco IP Phone 7960, if the user presses the "BackSpace <<" quickly enough, it can intermittently cause a Cisco CallManager restart.

CSCdr78651

Ability to park call by directory number is missing.

Modified park code allocation to use the same park code number when call park reversion occurred. This allows the parking party to repark the same call to the same park code in effect when call park reversion occurred.

CSCdr80088

Metalink import error message occurs.

Reinstallation fixed the problem.

CSCdr80095

Large number of File Does Not Exist appear messages in event viewer.

Automated install was changed to include the following directory: C:\WINNT\Help\iisHelp

CSCdr92982

CMI trace will not create trace files after configuring TraceFile.

The Cisco Messaging Interface service has to be stopped and started to create the new file.

CSCdr93620

Database migration of Cisco uOne ports from Cisco CallManager Release 2.4 to Release 3.0 fails.

The administrator must remove the VoiceMail DNs from NumPlan table when migrating from 2.4 to 3.0 in order to fix this problem.

CSCds09586

100% CPU utilization occurs on the web server (inetinfo).

This problem occurred when trying to set the Speed Dial on an administrator's phone.

CSCds10242

Cisco IP Phone 7960 to NetMeeting G.711 calls without MTP have poor audio quality.

Calls from a Microsoft NetMeeting client to a Cisco 7960 IP phone result in poor audio quality heard on the Cisco IP Phone 7960 side of the conversation. If the 'i' button is pressed twice while the call is active, the RxSize shows up as 32, although it should be 20. This problem is not observed on Cisco IP PHone model 30 VIP or Cisco IP Phone model 12 SP+ phones.

CSCds14106

Cisco CallManager 3.0(2d) stops responding after starting; it will not accept any connections.

Cisco CallManager may stop responding and stop accepting connections after starting up if a high number of route patterns are configured (greater than 300).

CSCds19447

No information about Cisco AutoAttendant install exists in Cisco CallManager install documents.

The AutoAttendant Administrative Guide documents the information.

CSCds21377

The Cisco CallManager service was up but was not running. Looking at PerfMon statistics showed that the CPU utilization of Cisco CallManager was zero, but Cisco CallManager did show as running.

During standard installation, an error occurred making the processing of Cisco CallManager shut down, but the CCM.exe service did not clear itself from memory.

CSCds26356

MGCP cannot do a one-to-one port mapping with an IP phone.

Changes were made in Cisco CallManager code to support the Service Parameter flag MatchingCgpnWithAttendantFlag, though, for a large site, using this flag is not an optimal solution for call completion rate. With 1500 FXO ports, call completion rate could be reduced by 4. Cisco recommends to spend the initial configuration effort to use Partition and Calling Search Space. A combination of these two methods might be the optimal solution.

CSCds36692

Having in excess of 200 translation patterns causes Cisco CallManager to take more than 10 minutes to initialize.

This has been fixed by increasing the timeout from 10 to 20 minutes.

CSCds38023

Non-unique timer ID causes transfer and hold to stop working.

After long periods, there was a chance that unique timer ID was no longer unique. This would cause various timers to fail. The problem was identified and fixed.

CSCds53566

Unable to unpause backup service in MCS backup utility

Automated Install fixed this problem for Cisco CallManager 3.0(5a).

CSCds67376

Auto install on 7820/22 locks up on final reboot after upgrade.

When performing upgrades on the MCS7820 or 7822, the server would lock up on the final reboot. This issue is resolved if Windows 2000 service pack 1 is installed prior to upgrading Cisco CallManager. The Cisco CallManager CD will now detect whether SP1 is installed and end the upgrade if it is not. SP1 will have to be installed before proceeding with the upgrade.

CSCds69615

SDL router services declared dead with Cisco CallManager 3.0(5a).

The problem was caused by the network specific facility IE, which the Cisco CallManager could not handle correctly. The software has been amended.

CSCds71367

Automated install upgrade does not stop Microsoft SNMP service.

Microsoft SNMP service is now automatically stopped prior to the upgrade.

CSCds76544

DBL trace files grow without bound if number of minutes is not set.

This problem occurred when the time limit for trace is set to 0. Under these conditions, the trace file for the database layer is ignored.


Open Caveats

Open Caveats for Cisco CallManager Release 3.0(8)

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

Table 5 Open Caveats for Cisco CallManager Release 3.0(8) 

DDTS number
Description

CSCdp63900

User needs a way to identity which Cisco CallManager is currently running in the box.

Workaround: Identify which Cisco CallManager is currently running on a box via the CallManager Table in the Cisco CallManager MIB. The Cisco CallManager at index 1 will be the Cisco CallManager running on the box where the SNMP Agent is running. This is always the case: i.e., the first entry in the Cisco CallManager table is the Cisco CallManager running on the same box as the SNMP Agent.

CSCdr20726

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

Workaround: No workaround exists. Cisco CallManager Release 3.0(7) does not support this feature.

CSCdr25206

Line state server is not updating the Cisco WebAttendant.

Workaround: Call the phone to update the phone status, or going off-hook on the phone also updates the status.

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

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

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.

In Cisco CallManager clusters, changes to global values in a cluster environment will not be reflected in all the MIB tables. You must restart all SNMP data collectors to show consistent values in the MIB tables throughout the cluster.

Examples (cluster):

When adding or deleting multiline extensions of an existing telephone, you must restart the Cisco CallManager system associated with that particular phone to activate the change in the MIB table for phone extensions.

When changing the primary Cisco CallManager name and description, you must restart Cisco CallManager to see the changes in the Primary MIB table. If the update involves a Cisco CallManager cluster, you must restart all Cisco CallManagers in the cluster to see the changes reflected in all the tables.

CSCdr39493

You cannot assign the same extension to a Cisco Catalyst 6000 24 Port FXS Analog Interface Module and a Cisco IP Phone.

Workaround: None. For Cisco CallManager Release 3.0, only MGCP gateways (VG 200s) allow FXS ports to share the same phone number with a Cisco IP Phone. This release does not support shared-line capability for other analog gateways in this release.

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.

CSCdr44668

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

Workaround: Configure a forward on no answer destination to point to some arbitrary other phone; then, the call will not have the problem.

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.

CSCdr51841

AVVID: When updating shared line appearance, all line appearances change.

Workaround: Delete the shared line appearance and re-add the line appearance with the new line information.

CSCdr53720

Transfer from Cisco uOne to busy phone without forwarding does not complete.

Workaround: Have phones forward on busy to voice mail.

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.

CSCdr61739

dbprocs - error - getProcessConFigInt - SdlMaxRouterLatencySecs

Workaround: This message can be ignored.

CSCdr80638

Locations do not recognize a transcoder correctly.

Workaround: No workaround exists.

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.

CSCdr82850

Alerting message from JTAPI is delayed less than 2 seconds.

Workaround: No workaround exists.

CSCdr85945

Incorrect help definitions appear for Hold 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 proceeding definitions instead of the definitions in the Cisco CallManager Administration Guide and online help.

CSCdr91539

Messages button on Cisco IP Phone 7900 exhibits incorrect behavior with multiple MWI.

Workaround: Once the user accesses the voice mail, the user can enter the DN of the line from which the user wants to retrieve the voice mail, and the user can retrieve the voice mail for the intended line.

CSCds03249

Label line setting for phone is inoperable.

Customer has a requirement to change the display of the line buttons to show information other than the directory number.

If the "Line settings for device" under the phone configuration is set with a label other than the default (directory number), the string entered in the configuration does not display on the Cisco IP Phone 7960. The directory number displays instead.

Workaround: None. This release does not currently support this feature. The directory number is the information that appears.

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

CSCds18680

Users cannot set URL for plug-ins.

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

CSCds20133

Call Forward Back fails when Cisco CallManager attempts to use unavailable Chopin 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 Chopin provided.

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: Refer to CSCds34596 in this document for a way to remove the server from the cluster if this is the desired end result.

CSCds42397

Terminal Services are nonfunctional.

Workaround: This is a Microsoft limitation. Refer to the following URL for more details: http://support.microsoft.com/support/kb/articles/Q186/6/27.

CSCds43822

SQL timeouts occur during Mass Deletion.

Workaround: Try setting the 'MaxCDRRecords' in increments (9,500,000, 9,000,000, ...) and restarting the 'Database Layer Monitor' service between increments. This will accelerate the delete process.

CSCds46274

Cisco IP Phone 7960 user on G.729 call hears hiss after digit during IVR prompt.

Workaround: No workaround exists.

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.

CSCds49125

Users must be logged on as the Administrator, or install will fail.

Workaround: When doing upgrades, the user must be logged in as Administrator. If the `Administrator' user ID has been changed, change it back before proceeding.

CSCds50352

System Unavailable displays on Cisco IP Phone 7960.

Workaround: No workaround 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).

CSCds55942

AVVID: Call produces cumulative feedback when conferencing back to itself.

Workaround: Avoid conferencing a call back on itself.

CSCds57155

Inside DialTone signal changed to the Alerting signal.

Workaround: No workaround exists.

CSCds59268

When Call Forward No Answer is configured on a line with partition, the calls are Forwarded 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.

CSCds63333

CTI framework shows up in phone corporate directory.

Workaround: No workaround exists.

CSCds63434

CALL INIT: User cannot successfully place international calls when using Cisco Softphone.

Workaround: Remove the OFFNET option on a international call dialing patter; then, you will receive 10 seconds of silence before placing the call. Decreasing T302 will also decrease the amount of time the dial tone plays or time waiting for an inter-digit timeout.

CSCds63897

PerfMon CallsInProgress is not accurate.

Workaround: Restarting the Cisco CallManager resets the counter and syncs it up.

CSCds67777

Blind transfer cannot complete successfully.

Workaround: No workaround 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

CSCds77431

No ringback occurs with de30+ when PI is not present.

Workaround: Configure the PBX or CO switch to treat the connection as non-ISDN and force the "network" to play ringback.

CSCds79206

Request exists for capability to hardcode speed and duplex 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.

CSCds81538

Calls through AS5300 do not operate properly with IAQ.

Workaround: Add a check for streaming in the workflow engine.

CSCds82725

Conference fails intermittently when inviting external extension.

Workaround: Call the external extension first and then conference in the Cisco IP Phones.

CSCds84446

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

Workaround: No workaround exists.

CSCds87815

AVVID: Call group pickup no longer works.

Workaround: To pick up any call (from any group), you must be a member of a call pickup group. If you are a member of the same group as the ringing phone, you can pick up the call by pressing the callPickup button. If the ringing call is part of another call pickup group, you can press Group Call Pickup and dial the group number of the phone that is ringing.

If you are not part of a call pickup group, you cannot pick up a call under any condition.

CSCds88617

GWY_ERR_C80ERR_RESOURCEUNAVAILABLE is reported from DT-24+.

Workaround: Contact the TAC for the DT-24+ load that will fix this issue.

CSCds88657

Gatekeeper calls cause memory loss and staying 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.

CSCdt02533

Memory leaks occur in ccm.exe.

Workaround: Stopping and starting Cisco CallManager service or rebooting the MCS restores the memory.

CSCdt02575

SMDI sends no or wrong info on transfer from Octel.

Workaround: No workaround 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.

CSCdt04394

A need exists for option to disable Call Transfer Timeout.

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

CSCdt06512

FXS port deletion makes the directory number an orphan.

Workaround: Assign the desired directory number to a phone; remove the directory number from the phone. This process removes the directory record from the database and the Analog Access FXS port page will work correctly.

CSCdt07744

Cisco CallManager does not reregister to gatekeeper after receiving a URQ from the gatekeeper.

Workaround: Reset the gatekeeper device in Cisco CallManager.

CSCdt08062

SNMP incorrectly reports registered phone and gateway counts.

Workaround: No workaround exists.

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.

CSCdt17567

Conference master drops from conference while adding 24th party into the conference.

Workaround: No workaround exists.

CSCdt17762

Cisco CallManager does not show as an option in service parameters for primary SPE.

Workaround: No workaround exists.

CSCdt18455

Conference does not work with two outgoing calls through VG200.

Workaround: Reassign the vg200 ports in the route group without using the "ALL!."

CSCdt20517

Calls placed on IP phones show translated No.

Workaround: The problem doesn't occur when no translation is done, but if dial translations are required, there is no work around.

CSCdt25121

User cannot transfer some calls between IP phones.

Workaround: No workaround exists.

CSCdt25949

DB Error (objTraceList) = 1542 undefined error displays.

Workaround: No workaround exists.

CSCdt26019

Upgrading to Cisco CallManager 3.0(5a) from an earlier version results in one Cisco IP Phone 7940 button template.

Workaround: No workaround exists.

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

CSCdt29182

Analog gateway sends caller name to Cisco CallManager in Calling Party Number IE.

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 a 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 3rd party voicemail system.

For example:

Route Pattern 17050

Partition vm

.....

VoiceMailDn 17050

VoiceMailPartition vm

CSCdt30584

Cisco Messaging Interface does not start.

Workaround: This is not a 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 3rd party voicemail system.

For example:

Route Pattern 17050

Partition vm

.....

VoiceMailDn 17050

VoiceMailPartition vm

CSCdt31211

A call that is forwarded to an AU phone always disconnects on Cisco CallManager.

Workaround: No workaround exists.

CSCdt32400

User hears no ringback tone when calling via H.323 device PRI interface.

Workaround: No workaround exists.

CSCdt33031

Pilot number stops working and does not distribute calls.

Workaround: Restart the TCD, and the pilot starts again. If this does not rectify your problem, bounce the Cisco CallManager.

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 3rd party voicemail system.

Example:

Route Pattern 17050

Partition vm

.....

VoiceMailDn 17050

VoiceMailPartition vm

CSCdt46584

New install back buttons do not work.

Workaround: You can select cancel and reboot the server with the OS CD in the drive. The install will start over.

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.


Troubleshooting

For specific troubleshooting information, refer to the Cisco IP Telephony Troubleshooting Guide for Release 3.0. You can access this guide at the following web site address:

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

Documentation Updates

This section contains the latest documentation updates for Release 3.0 of the Cisco CallManager. Included in these updates are any changes or late-breaking information that occurred after production of the Release 3.0 Cisco CallManager Administration Guide, 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 6 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 6 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 7 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 7 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 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 CMI primary. 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 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

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.

Configuring the Microsoft Telnet Daemon for Bridged Telnet

To make it possible for the Cisco Service Engineer (CSE) to log into the Telnet service on your Cisco CallManager system, you must configure the Microsoft Telnet daemon.

Use the tlntadmn command to accomplish this task.


Step 1 Select Start > Programs > Command Prompt.

Step 2 In the command window, enter the Telnet administration command:

tlntadmn

Step 3 Enter the following options from the lists displayed at the prompt.

a. From the first list, select option number 3, Display/change registry settings.

b. From the second list, select option number 7, NTLM.

Step 4 Next, set the value of NTLM to zero by responding to the prompts.

Current value of NTLM = 2
Do you want to change this value ? [y/n]y
NTLM [ current value = 2; acceptable values 0, 1 or 2 ] :0
Are you sure you want to set NTLM to :0 ? [y/n]y

Step 5 To finish, enter the following options from the lists displayed at the prompt.

a. From the first list, select option number 0, Exit this menu.

b. From the second list, select option number 0, Quit this application.

Step 6 Restart the Telnet service to enable the setting to take effect.


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 Release 3.0 Cisco CallManager Administration Guide 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:

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.

Service and Support

For service and support, contact Cisco Technical Assistance Center (TAC) at

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

Obtaining Documentation

This section provides different methods of obtaining Cisco documentation.

World Wide Web

You can access the most current Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or 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; therefore, it is probably more current than printed documentation. The CD-ROM package is available as a single unit or through an annual subscription.

Ordering Documentation

Registered CCO users can order the Documentation CD-ROM and other Cisco Product documentation through our online Subscription Services at http://www.cisco.com/pcgi-bin/subcat/kaojump.cgi.

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

Obtaining Technical Assistance

Cisco provides Cisco Connection Online (CCO) as a starting point for all technical assistance. Warranty or maintenance contract customers can use the Technical Assistance Center. All customers can submit technical feedback on Cisco documentation using the web, e-mail, a self-addressed, stamped response card included in many printed docs, or by sending mail to Cisco.

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 Technical Assistance Center (TAC) is available to warranty or maintenance contract customers who need technical assistance with a Cisco product that is under warranty or covered by a maintenance contract.

To display the TAC web site that includes links to technical support information and software upgrades and for requesting TAC support, use www.cisco.com/techsupport.

To contact by e-mail, use one of the following addresses:

Language
E-mail Address

English

tac@cisco.com

Hanzi (Chinese)

chinese-tac@cisco.com

Kanji (Japanese)

japan-tac@cisco.com

Hangul (Korean)

korea-tac@cisco.com

Spanish

tac@cisco.com

Thai

thai-tac@cisco.com


In North America, call TAC at 800 553-2447 or 408 526-7209. For other telephone numbers and TAC e-mail addresses worldwide, consult the following web site: http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml.

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:

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

We appreciate and value your comments.