Guest

Cisco Unified Communications Manager (CallManager)

Release Notes for Cisco CallManager Release 3.0(6)

 Feedback

Table Of Contents

Release Notes for Cisco CallManager Release 3.0(6)

Contents

Introduction

System Requirements

Determining the Software Version

Related Documents

New and Changed Information

New Software Features in Release 3.0(6)

Cisco WebAttendant

Tech Prefixes

Service Parameter

Important Notes for Release 3.0(6)

Setting Up the wauser Shared Directory for Cisco WebAttendant

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 Release 3.0(5a)

Computer Telephony Integration

BAT Reinstallation

IOS Version

Intercluster Trunk Configuration

Cisco CallManager Integration with Corporate LDAP Directories

Maintenance Release 3.0(4a)

Maintenance Release 3.0(4)

Call Forward No Answer and Call Forward Busy

Performance Monitor Counter Name Changes

Maintenance Release 3.0(3b)

Maintenance Release 3.0(3)

Maintenance Release 3.0(2d)

Resolved Caveats

Resolved Caveats - Release 3.0(6)

Resolved Caveats - Release 3.0(5a)

Resolved Caveats - Release 3.0(4a)

Resolved Caveats - Release 3.0(4)

Resolved Caveats - Release 3.0(3b)

Resolved Caveats - Release 3.0(3)

Resolved Caveats - Release 3.0(2d)

Open Caveats

Open Caveats for Cisco CallManager Release 3.0(6)

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 Connection Online

Technical Assistance Center

Documentation Feedback


Release Notes for Cisco CallManager Release 3.0(6)


December 15, 2000

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

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

http://www.cisco.com/public/sw-center/internet/callmgr/callmgr.html

Contents

These release notes discuss the following topics:

Introduction

System Requirements

Determining the Software Version

Related Documents

New and Changed Information

Important Notes for Release 3.0(5a)

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(6) 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(6).

Determining the Software Version

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

Cisco CallManager Administration Guide for Release 3.0(6)

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(6)

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(6)

Quick Start Guide for Cisco CallManager Release 3.0

New and Changed Information

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 the Cisco CallManager.

Step 2 Choose Cisco CallManager from Configured Services.

Step 3 Enter GateKeeperSupportedPrefix in the Params section.

Step 4 Choose String as the typ.e

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)

Setting Up the wauser Shared Directory for Cisco WebAttendant

By default, the client uses stored directory information from the Cisco CallManager Directory user database. The Cisco WebAttendant client displays user and line information in the Directory section of its user interface.

If you choose the default TCD database setting during Cisco WebAttendant client configuration, you must perform the following procedure to ensure that the Cisco WebAttendant client can display the directory information from the Cisco CallManager directory database.


Note If you are running Cisco CallManager in a cluster environment, perform this procedure on every Cisco CallManager in the cluster.

Perform the following steps to set up the wauser shared directory:


Step 1 Log in to the Cisco CallManager server.

Step 2 Use Windows Explorer to browse to the following folder:

C:\Program Files\Cisco\Users

Step 3 Right-click the Users folder and choose Sharing.

Step 4 Click the Share this Folder radio button.

Step 5 Change the default share name from "Users" to "wausers." Make sure the share name, which is not case sensitive, is "wausers" so that directory information can display.

Step 6 Click the Permissions button. Click the Share Permissions tab if it does not automatically appear.

Step 7 Choose Everyone in the Name pane, if it is not already chosen.

Step 8 Check the Full Control, Change, and Read check boxes; then, click OK.

Step 9 Click the Security tab.

Step 10 Uncheck the Allow inheritable permissions from parent to propagate to their object check box.

Step 11 A security dialog box appears. Click the Remove button in the dialog box.

Step 12 If the Name pane has any entries in it, choose them one-by-one and click Remove after each selection.

Step 13 Click Add.

Step 14 In the Look In field, choose the name of the machine you are currently using.

Step 15 Choose Everyone in the Name pane; then, click Add.

Step 16 Click OK.

Step 17 The Users Properties Security window appears. Make sure that only Everyone appears in the Name Pane.

Step 18 In the Permissions pane, check the Full Control check box.


Note When you check the Full Control check box, you automatically choose all available permission selections.

Step 19 Click Apply.

Step 20 Click OK.

Step 21 Perform this procedure on every Cisco CallManager in the cluster.


Note To ensure that the changes made to the Shared As properties are visible to Cisco WebAttendant clients, Cisco WebAttendant users should exit the client, log out of Windows, and then log back in to Windows.

Note Refer to CSCdt52841 in the "Resolved Caveats" section for more information.

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

Maintenance Release 3.0(4a)

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

Maintenance Release 3.0(4)

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

Call Forward No Answer and Call Forward Busy

When the administrator sets a call forward in the Cisco CallManager Administration web pages, Calling Search Space must also be set. The value set in the Calling SearchSpace by the administrator overrides any settings on the device. If no value is set, then the null partition will be assumed.

Performance Monitor Counter Name Changes

Two Performance Monitor counters that are assigned new names function differently:

"RegisteredPhones" has changed to "RegisteredHardwarePhones"—The RegisteredHardwarePhones counter indicates the number of hardware phones, which includes the Cisco IP 7900 Family, Cisco IP Phone 30 VIP, and Cisco IP Phone model 12 SP+, that are currently registered with a specific Cisco CallManager.

"LicenseAvailableStation" has been changed to "RegisteredOtherStationDevices"—The RegisteredOtherStationDevices counter represents the number of devices registered with a particular Cisco CallManager that use the SCCP protocol and are not hardware phones.

Maintenance Release 3.0(3b)

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

Maintenance Release 3.0(3)

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

Maintenance Release 3.0(2d)

Cisco CallManager Release 3.0(2d), a maintenance release, addresses Cisco Media Convergence Server installation issues and resolves other high-priority caveats. The release adds no new features. Refer to the "Resolved Caveats" section for more information.

Resolved Caveats

Resolved Caveats - Release 3.0(6)

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

Table 1 Cisco CallManager Release 3.0(6) Resolved Caveats 

DDTS Number
Summary
Explanation

CSCdt52841

Cisco WebAttendant documents instruct the user to have read access when they need change access to open the database.

Users were getting an error when the folder was not set to share, so the documention for Cisco CallManager 3.1 instructs the user how to set the folder to share.

Refer to the "Important Notes for Release 3.0(6)" section for further instructions.

CSCds82156

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

The screen was changed to be read more clearly.

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

CSCds79952

Cisco CallManager stackwalk for CM2 of Dallas Alpha

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

CSCds79716

UserPrefs do not work after an upgrade from preEncore to Encore.

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.

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

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.

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.

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.

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.

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.

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.

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.

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.

CSCds67120

CTI logs out TCDSRV and drops TCP connection.

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

CSCds66507

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

Windows operating systems' version of regsvr32.exe could not load the DLLs 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.

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.

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.

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.

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.

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.

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.

CSCds57574

WebAttendant will not install on Win98 client machine

Windows operating systems' version of regsvr32.exe could not load the DLLs 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.

CSCds53378

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

The code for unlimited bandwidth in location for Cisco CallManager .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.

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.

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.

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.

CSCds18156

Symbol Phone create multiple H225D registered with Line Control

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

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.

CSCdr22835

Cannot change WS-X6608 port type once set without resetting card

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


Resolved Caveats - Release 3.0(5a)

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

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

DDTS Number
Summary
Explanation

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.

CSCds71367

Automated install upgrade does not stop Microsoft SNMP service.

Microsoft SNMP service is now automatically stopped prior to 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.

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.

CSCds53566

Unable to unpause backup service in MCS backup utility

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

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.

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.

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 CallingSearchSpace. A combination of these two methods might be the optimal solution.

CSCds21377

The Cisco CallManager service was up but was not running. Looking at PerfMon stats 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.

CSCds19447

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

The AutoAttendant Administrative Guide documents the information.

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

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.

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.

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.

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.

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

CSCdr80088

Metalink import error message occurs.

Reinstallation fixed the problem.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.


Resolved Caveats - Release 3.0(4a)

Table 3 Cisco CallManager 3.0(4a) Resolved Caveats

DDTS Number
Summary
Explanation

CSCds72728

The wrong version number appeared in the Cisco CallManager administration page.

The software was updated so that the correct version number now appears when you click on Details from the Cisco CallManager Administration page.

CSCds64152

Parking conference call and not retrieving causes stack walk.

The Cisco CallManager software has been changed to correctly handle the situation in which the conference call is parked and not retrieved.

CSCds58697

AVVID: Upgrading to CM3.03B SQL Server Screen is confusing.

The text "Create Primary Database" makes users think that they will overwrite their existing database, so most users will select the hostname loca@tion and this is the incorrect choice. The dialog has been revised.

CSCds58388

CiscoWebs folder security should be defaulted as EveryOne FullCntrl.

While installing Cisco CallManager CiscoWebs folder, security can be defaulted from C:\ ,and the security for child folders under CiscoWebs should be performed by concerned applications like Cisco CallManager Admin, ART, BAT, etc. This will assure:

1. Complete security because only the folder CiscoWebs is accessible, but all folders under this will be protected by individual applications.

2. If an application needs to set permissions in a different way, the application needs to be set to not keep track of what is happening on CiscoWebs; i.e., parent folder.

CSCds55666

Search space cannot handle partitions more than 1K.

The problem was caused by an attempt to concatenate the calling search space associated with a device to the end of a calling search space associated with a line.

CSCds53528

Cisco CallManager sends nonconforming H.323 messages to the gateway.

A nonconforming H.225 Information message was sent to the gateway when call forwarding hop counts were exceeded for an inbound call to an extension number that is set up with call forward all to itself.

CSCds49615

Cisco uOne Call Forward hop count is independent from normal Call Forward hop count.

The Cisco CallManager software has been modified to allow the customer to add the VoiceMailMaximumHopCount so that the voice mail hop count can be separated from the forward hop count, by doing so, we can allow the customer to access all the Cisco uOne ports without the limitation of the forward hop count.

CSCds47721

MWI state is not correct after phone resets.

After failover scenario, failback to database publisher did not occur.

CSCds47622

Cisco CallManager subscriber 100% CPU usage possibly due to high Cisco uOne use.

 

CSCds43525

AVVID: Devices will not reset from Cisco CallManager. They must be manually reset.

The problem occurred because the buffer size In SSAPIServer and SSAPIClient was not being set large enough to accommodate large customer calling search spaces. The buffer sizes were changed, and this fixed the error.

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.

CSCds33345

Call from PSTN: forward no answer to PSTN rings once, then is dropped.

The Cisco CallManager software has been modified so, if the call was connected and service parameter "NoProgressForAlertingFlag" was not set, send Progress message when receiving the Alert message and the Alert message was suppressed.

CSCds33334

Cisco CallManager Service stops unexpectedly for 1 minute.

An unsupported CTI device caused the Cisco CallManager to stop.

CSCds31447

Call comes in from the CO via an IOS-Gateway(A); the call then gets Call Forward All back out a different IOS-Gateway(B), and there are audio problems.

Cisco CallManager software only sends the Alert message to a Symbol phone device when it receives a call progress message followed by Connect message (without the Alert message) from the terminating party.

CSCds29375

MWI with Lucent/DPA Migration Configuration with no Device Reg. = 100% CPU.

Engineers created two mailboxes on Octel system that are connected to a Calista DPA. The two mailboxes can turn on a message lamp if a message is received. The Cisco CallManager does not have a phone that corresponds to these mailboxes, so if the mailbox attempts to turn on an MWI, it will be an invalid phone number to the Cisco CallManager.

CSCds26179

Voice mail forwarding consumes near 100% of Cisco CallManager's resources.

Cisco CallManager has been modified so that it consumes less CPU time to find the available Cisco uOne port. When many users simultaneously access voice mail, the Cisco CallManager will not go to 100% CPU usage. Other users can still get a dial tone and make calls as normal.

CSCds24423

Call Forward process hangs.

Cisco CallManager software has been modified to delete the forwarding process after the call finishes to a DN, which was set up to have call pickup group service but no call forwarding.

CSCds23120

Forward no answer to PSTNextension provides dead air.

The Cisco CallManager software has been modified so, if the call was connected and service parameter "NoProgressForAlertingFlag" was not set, then send Progress message when receiving the Alert message and the Alert message was suppressed.

CSCds23080

Cisco CallManager crashes due to SNMP code failure.

The SNMP code now implements structured exception handling to avoid this failure type.

CSCds21447

Cisco uOne ports do not register with secondary Cisco CallManager on failover.

The Cisco uOne port possibly was connected to Cisco CallManager but not registered. The Cisco CallManager accelerates registration attempts by dropping registration requests but keeps the connection up and provides keep-alives. The device showed reregister after some timeout, but Cisco uOne does not do this.

CSCds18584

Web security and crash protection for web were invalid.

Changes were made to the authentication methods in the Cisco CallManager software.

CSCds18567

Updating Call Forwarding parameter does not take effect.

The errors in the layer/DB Admin were affecting other parts of the system because the IIS process for the Cisco CallManager Administration web was not set to run as isolated (Application Protection set to High). Install needs to set the Cisco CallManager Administrator and Cisco CallManager User applications to run isolated to prevent problems in the web pages from affecting other services, including DB Layer Monitor and Cisco CallManager.

CSCds11693

30-hop call forwarding uses 100% CPU.

Cisco CallManager software has been enhanced to make call forwarding more efficient.

CSCds04998

IIS services fail and restart after a period of time.

This problem occurred when a Foreign key violation caused a database layer to throw a huge number of errors. Protection on BAT virtual Directory was set to HIGH(ISOLATED) to preclude a crash of whole of IIS even if this error occurs.

CSCdr49092

The dialing plan script incorrectly blocks n11 office codes.

An NANP file caused the software to reject n11 office codes when entered into the system. As a result, the Cisco CallManager software was upgraded to allow those digits to be dialed.


Resolved Caveats - Release 3.0(4)

Table 4 Cisco CallManager 3.0(4) Resolved Caveats

DDTS Number
Summary
Explanation

CSCds64152

Parking conference call and not retrieving causes stack walk.

The Cisco CallManager software has been changed to correctly handle the situation in which the conference call is parked and not retrieved.

CSCds58697

AVVID: Upgrading to CM3.03B SQL Server Screen is confusing.

The text "Create Primary Database" makes users think that they will overwrite their existing database, so most users will select the hostname loca@tion and this is the incorrect choice. The dialog has been revised.

CSCds58388

CiscoWebs folder security should be defaulted as EveryOne FullCntrl.

While installing Cisco CallManager CiscoWebs folder, security can be defaulted from C:\ ,and the security for child folders under CiscoWebs should be performed by concerned applications like Cisco CallManager Admin, ART, BAT, etc. This will assure:

1. Complete security because only the folder CiscoWebs is accessible, but all folders under this will be protected by individual applications.

2. If an application needs to set permissions in a different way, the application needs to be set to not keep track of what is happening on CiscoWebs; i.e., parent folder.

CSCds55666

Search space cannot handle partitions more than 1K.

The problem was caused by an attempt to concatenate the calling search space associated with a device to the end of a calling search space associated with a line.

CSCds53528

Cisco CallManager sends nonconforming H.323 messages to the gateway.

A nonconforming H.225 Information message was sent to the gateway when call forwarding hop counts were exceeded for an inbound call to an extension number that is set up with call forward all to itself.

CSCds49615

Cisco uOne Call Forward hop count is independent from normal Call Forward hop count.

The Cisco CallManager software has been modified to allow the customer to add the VoiceMailMaximumHopCount so that the voice mail hop count can be separated from the forward hop count, by doing so, we can allow the customer to access all the Cisco uOne ports without the limitation of the forward hop count.

CSCds47721

MWI state is not correct after phone resets.

After failover scenario, failback to database publisher did not occur.

CSCds47622

Cisco CallManager subscriber 100% CPU usage possibly due to high Cisco uOne use.

 

CSCds43525

AVVID: Devices will not reset from Cisco CallManager. They must be manually reset.

The problem occurred because the buffer size In SSAPIServer and SSAPIClient was not being set large enough to accommodate large customer calling search spaces. The buffer sizes were changed, and this fixed the error.

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.

CSCds33345

Call from PSTN: forward no answer to PSTN rings once, then is dropped.

The Cisco CallManager software has been modified so, if the call was connected and service parameter "NoProgressForAlertingFlag" was not set, send Progress message when receiving the Alert message and the Alert message was suppressed.

CSCds33334

Cisco CallManager Service stops unexpectedly for 1 minute.

An unsupported CTI device caused the Cisco CallManager to stop.

CSCds31447

Call comes in from the CO via an IOS-Gateway(A); the call then gets Call Forward All back out a different IOS-Gateway(B), and there are audio problems.

Cisco CallManager software only sends the Alert message to a Symbol phone device when it receives a call progress message followed by Connect message (without the Alert message) from the terminating party.

CSCds29375

MWI with Lucent/DPA Migration Configuration with no Device Reg. = 100% CPU.

Engineers created two mailboxes on Octel system that are connected to a Calista DPA. The two mailboxes can turn on a message lamp if a message is received. The Cisco CallManager does not have a phone that corresponds to these mailboxes, so if the mailbox attempts to turn on an MWI, it will be an invalid phone number to the Cisco CallManager.

CSCds26179

Voice mail forwarding consumes near 100% of Cisco CallManager's resources.

Cisco CallManager has been modified so that it consumes less CPU time to find the available Cisco uOne port. When many users simultaneously access voice mail, the Cisco CallManager will not go to 100% CPU usage. Other users can still get a dial tone and make calls as normal.

CSCds24423

Call Forward process hangs.

Cisco CallManager software has been modified to delete the forwarding process after the call finishes to a DN, which was set up to have call pickup group service but no call forwarding.

CSCds23120

Forward no answer to PSTNextension provides dead air.

The Cisco CallManager software has been modified so, if the call was connected and service parameter "NoProgressForAlertingFlag" was not set, then send Progress message when receiving the Alert message and the Alert message was suppressed.

CSCds23080

Cisco CallManager crashes due to SNMP code failure.

The SNMP code now implements structured exception handling to avoid this failure type.

CSCds21447

Cisco uOne ports do not register with secondary Cisco CallManager on failover.

The Cisco uOne port possibly was connected to Cisco CallManager but not registered. The Cisco CallManager accelerates registration attempts by dropping registration requests but keeps the connection up and provides keep-alives. The device showed reregister after some timeout, but Cisco uOne does not do this.

CSCds18584

Web security and crash protection for web were invalid.

Changes were made to the authentication methods in the Cisco CallManager software.

CSCds18567

Updating Call Forwarding parameter does not take effect.

The errors in the layer/DB Admin were affecting other parts of the system because the IIS process for the Cisco CallManager Administration web was not set to run as isolated (Application Protection set to High). Install needs to set the Cisco CallManager Administrator and Cisco CallManager User applications to run isolated to prevent problems in the web pages from affecting other services, including DB Layer Monitor and Cisco CallManager.

CSCds11693

30-hop call forwarding uses 100% CPU.

Cisco CallManager software has been enhanced to make call forwarding more efficient.

CSCds04998

IIS services fail and restart after a period of time.

This problem occurred when a Foreign key violation caused a database layer to throw a huge number of errors. Protection on BAT virtual Directory was set to HIGH(ISOLATED) to preclude a crash of whole of IIS even if this error occurs.


Resolved Caveats - Release 3.0(3b)

Table 5 Cisco CallManager Release 3.0(3b) Resolved Caveats 

DDTS Number
Summary
Explanation

CSCds32253

If you install the publisher, then change the Administrator password for SQL Srv, installing further subscribers will fail.

After changing the password on the publisher (specifically the SQL Svc user), you cannot successfully add further subscribers into the cluster.

CSCds29243

The Cisco IP Phone 7960 stops responding and only displays the text "Opening."

This problem can occur when all Cisco CallManagers in the phone's redundancy group list are unavailable. After attempting to connect to the Cisco CallManagers in its group list, the phone stops responding eventually.

CSCds21180

After Cisco CallManager failure, some phones require reboot to reregister.

A Cisco IP Phone 7960 that unregisters from all configured Cisco CallManagers after a Cisco CallManager failure may require rebooting to restore connectivity.

CSCdr95107

The Cisco IP Phone 7960 crashes when receiving malformed audio packets.

When connecting to Cisco uOne voice mail (where a G.729 connection is forced), Cisco uOne sends malformed G.729 packets, which cause the phone to crash and reboot.

CSCdr49092

The dialing plan script incorrectly blocks the n11 office code.

This problem will cause the calls to get a reorder tone if the dialer enters the office code as X11.


Resolved Caveats - Release 3.0(3)

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

Table 6 Cisco CallManager Release 3.0(3) Resolved Caveats 

DDTS Number
Summary
Explanation
Cisco CallManager

CSCds21424

Cisco CallManager terminated abnormally with memory corruption and a faulty alarm message.

An alarm message with an incorrect parameter caused memory corruption.

CSCds19482

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

CPU was tracking between about 70% and 40% in a regular cycle (20 seconds high; 20 seconds low). All the other Cisco CallManagers were below 10%. A Cisco IP Phone 7960 that was constantly requesting the same information because it missed a message caused this event.

CSCds18538

MessageWaitingOn or MessageWaitingOff string update causes runtime error in service parameters.

When the user attempts to assign a number to the MessageWaitingOn or MessageWaitingOff service parameters, a run-time error line 74 displays.

CSCds17394

Cisco CallManager consumes 100% CPU usage.

Cisco CallManager CPU usage went to near 100%, and users experienced very slow response from Cisco CallManager.

CSCds07855

Call pickup of blind transfer occurs.

1. Phone A calls Phone B.

2. Phone B answers call.

3. Phone B presses transfer, then dials Phone C, then presses transfer button and hangs up phone.

4. Phone C rings.

5. Phone D tries to do a call pickup, fails, and puts itself On-Hook.

6. Phone A hears reorder, and Phone C continues to ring.

7. Phone C is answered.

8. Connection completes between Phone A and Phone C.

Duplicate of CSCds09040 (call pickup groups are not working if transfer started the call to the pickup group number).

CSCds06332

Call forward is not working when multiple hops are down.

 

CSCds05118

Calls drop randomly on a 5300 phone load when an error occurs.

Calls drop through a 7200 or 5300 gateway randomly. A TCP error coming from a call that is disconnecting normally causes this problem.

CSCds02656

Intercluster dead air promotes zero bandwidth.

This occurs when an entry in the route list does not respond. If bandwidth is used up, call is being routed to the secondary CM and then the call eventually times out after a long period of "dead air."

CSCds02623

Intercluster dead air equates to busy.

Cluster 09 Phone 99999 calls Cluster 04 Phone 43520. DN 43520 is off hook; DN 99999 gets dead air.

CSCds02309

Subscriber Dial Pattern Change needs Cisco CallManager stop/start.

The problem occurs because the Cisco CallManager software does not handle registration of more than 64 DNs/route patterns per route list.

CSCdr99090

Symbol phone calling out via gateway does not complete.

Symbol phone calling out via a 5300 to a PSTN number rings twice, and then the symbol phone goes idle. Symbol phone calling out via a DT24+ to a PSTN number rings twice, and then the symbol phone says call declined. If the PSTN number is forwarded directly to voice mail, (it does not ring), then the call completes, and voice mail can be accessed

CSCdr97447

Call pickup groups stop working.

Call pickup groups seem to work OK for a while after they are created or after the Cisco CallManager is restarted. However, after an undetermined period of time, they cease to function.

CSCdr84584

Cisco CallManager fails to cut-through voice-path after progress message.

Gateway used: AS5300. The gateway is handling the progress message correctly; on receiving progress message, the conference is created, and an H245 cap request is sent to Cisco CallManager.

Cisco CallManager responds with status message: message not compatible with call state or message type nonexistent or not implemented.

CSCdr80083 is a duplicate of this caveat.

CSCdr79073

DisplayIEDeliveryFlag=True causes no connect through T1 CAS.

Under Cisco CallManager Service Parameters, if DisplayIEDeliveryFlag=T for True, a call will not set up if routed to PBX via PRI then off PBX to other equipment via T1 CAS. The IP phone caller will get fast busy.

With this flag set to T(rue), you normally see the calling and called party name delivery in the SETUP and CONNECT messages.

CSCdr70073

Cisco CallManager server reboots forever if you do not log in.

Several Cisco CallManager servers would reboot forever if you did not log in. This problem began after upgrading to Release 3.0(1) from an earlier version of Release 3.0. The problem only occurs when the Publisher cannot contact the subscriber. Approximately 65 seconds after the message displays on the screen asking the user to press Control-Alt-Delete to logon, the server reboots.

CSCdr58885

There was an illegal sequence of DT 24+ for releasing the line.

When DT 24+ disconnects the line, it always takes 30 seconds (thus, until T305 timer expires) to release the B-channel completely.

CSCdr57966

A feature request for tone on hold.

A ToneOnHold service parameter has been added for Cisco CallManager.

CSCdr57963

No hold tone when a user places a particular call on hold.

No hold tone occurs when a call is released from hold if the other party has also put the call on hold.

CSCdr57950

Ringing tone on the phone does not correspond with the call state.

 

CSCdr57872

DT 24+ ignores progress indicator No.8 if disconnect message is received.

DT 24+ ignores the DISCONNECT message that contains progress indicator No. 8, "in-band information or appropriate pattern now available." It seems that DT 24+ seems to consider only the DISCONNECT message. The DT 24+ releases the call.

CSCdr57383

Line lamp does not blink at different rates on multiple-line phones.

When phone has same line appearance on multiple phones, A, B and C, call comes in, and A answers call. A places call on hold. All occurrences of this line appear the same on all phones. No differentiation designates phone that actually placed call on hold.

CSCdr57362

No hold tone occurs while call is parked.

When a call is received and parked, the calling party hears nothing while parked.

CSCdr57272

OutofBandwidthText message will not display on a Cisco IP Phone 7960.

The "Not Enough Bandwidth" message that displays on a Cisco IP Phone when calling between locations that are out of bandwidth will not display on a Cisco IP Phone 7960. This text displays correctly on the Cisco IP Phone model 12 SP and other Cisco IP Phones.

CSCdr56276

Call waiting times out after 22 seconds.

Phone A calls phone C. Call is established, A and C are conversing.

Phone B calls phone C. Phone C hears call waiting beep, and phone B hears ringback.

Phone C does not immediately switch to the new call, so, after ~22 seconds, phone B gets reorder.

All phones are set up for no call forwarding of any kind.

In New Zealand, the phone company does not timeout calls until 3 minutes elapse. If you call someone and they do not answer, their phone will ring for 3 minutes or until the originator hangs up, whichever occurs first. The customer thinks call waiting should behave the same way. The customer wants to know whether there is a timer they can configure.

A new system parameter called CallWaitingTimeout was added. The default value for this parameter, if not present, is 180 seconds (3 minutes).

CSCdr55758

There was a 45-second delay to reorder on invalid # intercluster call, 2 Cisco CallManagers per cluster.

A number of problems exist where calls have no progress and, after approximately 45 seconds, revert to reorder tone.

This problem relates to defining intercluster H.323 from source cluster to primary and secondary Cisco CallManagers in another cluster using route groups with both primary and secondary defined.

CSCdr55189

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

When a Cisco  IP Phone 7960 is attached to a Cisco Catalyst 6000 switch, if the pvid on the switch port is changed, the phone may take up to 7 minutes to reconfigure and connect to the Cisco CallManager.

CSCdr52811

No call progress occurs when calling a busy user over DE 30+.

This problem occurs when placing a call out a DE 30+, and the called user is busy. The Cisco IP Phone displays date and time instead of user busy tone.

CSCdr49092

The dialing plan script incorrectly blocks the n11 office code.

This problem will cause the calls to get a reorder tone if the dialer enters the office code as X11.

CSCdr39846

Cisco CallManager is not interpreting Screening Indicator correctly.

Cisco IP phone prefixes a random or garbage character to the number display on the LCD screen. This occurs when a call is placed from the PSTN to an IP phone with the following configuration: PSTN—>AS5300—>
Cisco CallManager—>Cisco IP Phone.

The AS5300 uses ISDN PRI signalling to set up the call.

CSCdr35729

Cisco CallManager with Cisco Catalyst 6000 does not support G.723.1 variable voice payload.

The problem was fixed in transcoder load M001A300 and conference bridge load C001A300.

CSCdr14562

Clicking too rapidly on the Update button in the Cisco CallManager Administration Configuration screen can cause the browser to stop responding.

The browser seems to be connecting to the server, but it remains in a wait state from which it cannot recover. The browser does not respond to any user input. The status area at the bottom of the window displays the message Validating....

CSCdp97606

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 will experience audio feedback.

The fix prevents a Meet Me conference participant from transferring the call to the same Meet Me conference number, thus preventing the feedback problem from occurring. Now, when the Meet Me conference participant attempts to transfer the call to the same Meet Me conference number, Cisco CallManager will ignore the transfer button.

DC Directory

CSCdr88591

Opening up the 64th provider crashes the Cisco CallManager.

When JTAPI tries to open provider one after another without shutting down previously open providers, at the most, 63 providers could be open. If an attempt is made to open the 64th provider, the Cisco CallManager crashes.

The Cisco CallManager service must be restarted manually. The problem was caused by DC Directory not allowing more than 64 simultaneous connections to the directory. The client hung while opening the 65th connection, thus causing the SDL Router services to time out, leading to the Cisco CallManager crash.

CSCdr86719

You must delete a user twice before the user is removed from user list.

The problem is another manifestation of browser (IE) caching. The request to delete a user was not being submitted to the web server. The browser simply displayed a previous deletion results page from its cache.

This has been resolved by setting the CacheControl property on the Response object to force IE to always refresh certain pages from the web server rather than rendering them from its cache.

CSCdr84999

User Preferences pages must not display all of the Cisco CallManager devices by default.

The User Preferences pages no longer support sorting because of CPU intensive nature on the server side and because of the potentially large amount of data that would need to transmitted to the client if it were performed on the client side.

CSCdr53243

MetaLink does not continue to pull data from database after reboot.

DC Directory does not pull all needed information from the database after rebooting.

CSCdr51705

DCX500.exe is taking up 1 GB of memory.

Memory leaks in DC Directory can occur in customer environments containing very large numbers of phones and users.

CSCdr39475

When using Add a New User, session object timeout error occurs.

When creating the first user from the Cisco CallManager User > Add a New User screen, the resulting page states:

Error

The following error occurred while trying to load the requested page. Sorry, your session object has timed out.

Click here to Begin a New Search.

This error occurs only on the first instance. Subsequent execution of User > Add a New User proceeds without errors, and you can continue defining a new user. If you open another browser, the first instance will fail, but subsequent attempts will succeed.

CSCdr36464

500-device limit leads to bad User Preferences screens.

The implementation of the search limit for devices that can be associated with users can result in an inaccurate representation of which devices a user currently controls. When a subset of devices is shown that contains devices that the user controls, these devices may be inaccurately represented as not being associated with the user.

CSCdr36451

First call to Associate Devices burdens CPU badly.

When a new user is created using the User Preference pages, addition of the user to the directory proceeds flawlessly. However, once the user is installed, attempting to associate devices leads to a very badly burdened CPU.

Watching the appropriate performance monitor and task manager screens shows that DC directory jumps to 100% processor utilization in three distinct segments, over a space of roughly 30 seconds. Because the web page is providing no feedback at this time, an end user could decide that the system is hung.

CSCdr32527

After adding a device, you must close the browser to display the updated, added device.

If devices are associated with a user, the list of available devices is cached for faster retrieval. Consequently, if new devices are added after the device information for users is cached, the new devices will not be available for association with users.

CSCdr20006

Incorrect search results display in the User Directory search.

The problem occurs when

1. A search is executed from either the basic or advanced search pages.

2. The browser Back button is clicked.

3. A new search is entered and executed.

After the above steps are performed, the results of the first search display as the results for the second search, which is incorrect.

CSCdr05501

Cisco User Preferences upgrade removed DC Directory service.

The Cisco User Preferences Pages upgrade installation ran with no apparent problems. After the install completed, the machine was rebooted as instructed. When the system came back up, no DC Directory service was present.

CSCdr02305

DC Directory takes up to an hour to restart due to an IPC initialization failure.

 

CSCdr02303

DC Directory crashes under severe network conditions.

DC Directory stops working.

CSCdp98131

DC Directory server fails on restart during avvid_cfg.

The problem was due to Windows not cleaning up the shared memory resources quickly enough. Instead of stooping and restarting DCD, avvid_cfg now sleeps for 65 seconds to allow MetaLink sufficient time to discover the DC Directory admin node.

CSCdp60775

DC Directory exits with no warning or alert.

The Cisco CallManager User pages are not accessible, or the user administration pages return errors when accessed.

Under extreme conditions such as low memory or network problems, the DCD Directory Server service could stop running. This causes the web pages mentioned to function incorrectly or not at all.

Cisco IP Phone

CSCdr77894

Intermittent cutouts are heard on Cisco IP Phone 79xx phones when talking to Cisco uOne Messaging.

Intermittent cutouts of Cisco uOne Messaging system prompts sent to Cisco IP Phone 7900 family phones occur. The problem is not reproducible on Cisco IP Phone model 30VIP and Cisco IP Phone model 12-SP+ . Actual voice recordings such as spoken names and voice messages seem to be unaffected.


Resolved Caveats - Release 3.0(2d)

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

Table 7 Cisco CallManager Release 3.0(2d) Resolved Caveats 

DDTS Number
Summary
Explanation
Automated Installation

CSCdr80536

The SQL license is set to per server with a default of 5 concurrent connections.

The automated install of SQL server sets the licensing to 'per server' with a default of 5 concurrent connections; per our licensing, no restrictions on concurrent connections for systems supporting up to 10,000 phones, exist. The current setting prohibits installs of more than 5 servers in a cluster.

CSCdr71568

The automated installation program does not cap SQL memory on the database publisher or subscriber.

When using the automated installation, SQL memory usage is not capped on publishers or subscribers. A potential exists of a Cisco CallManager crash if SQL consumes too much memory.

CSCdr66413

Cisco Call Manager will not start after being installed from the Cisco CallManager 3.0(1) installation CDs.

If the DNS suffix is populated in the My Computer > Properties > Network Identification tab, Cisco Call Manager will not start after being installed from the Cisco CallManager 3.0(1) installation CDs.

CSCdr65911

Installation CD does not install Compaq Utilities correctly on the Cisco Media Convergence Server MCS-7830.

Disc 1 of the Cisco CallManager 3.0(1) CDs does install the Compaq Utilities 39 MB partition. However, for some reason, when the user presses F10 during the boot sequence, an error message displays:

The System Partition Utilities are not available on this system.

Press any key to continue...

This error occurs on the MCS-7830 platform.

CSCdr58051

The automated installation program restricts users to top-level domain names without special characters.

During the automated installation, the Domain Name field is limited to a top-level domain name (for example, Cisco.com is acceptable, but selsius.cisco.com would not be acceptable).

CSCdr46034

The automated installation program does not allow you to use a dash (-) or an underscore (_) in a workgroup or server name.

When the operating system is installed from the "Operating System Installation and Recovery CD-ROM," the machine name entry field is limited to only alphanumeric characters.

Cisco CallManager

CSCdr69851

Timer T200 should be set to 1200 ms instead of 1000 ms.

In certain digital sessions, the default value of timer T200 may be too small to ensure proper operation. Therefore, the default value for this timer was changed to 1300 ms.

Cisco TFTP

CSCdr58199

Cisco TFTP stops building files and accepting database requests.

When devices are deleted, TFTP does not serve a file for a device that is in the database.

Cisco Catalyst 6000 24 Port FXS Analog Interface Module (WS-X6624-FXS)

CSCdr68352

WS-X6624-FXS ports are out of service.

Shortly after all ports become concurrently off hook, Cisco Call Manager will report some ports status as "d" or "3" for anywhere from an hour to all day. Dick Tracy will report ports as either "NormalTalking Undefined!!" or "CallClearing Loop Open." Status via Telnet shows the ports as either on hook or off hook.

When the ports are in either of these two states, they appear to be unusable because Cisco CallManager is using the next analog gateways in the route list.

CSCdr64557

VAD causes multiple audio dropouts with Octel voice mail.

The user complains that audio, when accessing the Octel voice mail system, drops out intermittently. The dropout was reported to be from a fraction of a second to several seconds in duration, of almost continuous frequency. The problem was noted to occur even during the Octel voice prompts at the beginning of the session, indicating a problem in the stream from the Octel to the IP phone through the Cisco Catalyst 6000 24 Port FXS Analog Interface Module (WS-X6624-FXS) gateway.

Cisco Catalyst 6000 8 Port Voice T1/E1 and Services Module (WS-X6608-T1/E1)

CSCdr79799

Hold tone is not played out by DSPs when holding.

The WS-X6608 Digital Gateway will not play hold tones every 10 seconds when a Cisco IP Phone places the call on hold. No workaround exists.

This problem occurred because of misprocessing of the DtHoldTone message. It has been fixed in D004C300.

CSCdr69871

WS-X6608-T1/E1 did not pass ISDN PRI Layer 2 homologation test.

This was resolved by setting the T200 default timer to 1300 ms.

Cisco IP Phone

CSCdr69914

Disabling VAD for G.729 by setting the service parameter SilenceSuppressionSystemWide to FALSE does not seem to work.

When VAD is disabled for G729 and a call is made between two Cisco IP Phones, there is no continuous streaming.

CSCdr54497

Cisco IP Phone 7960 displaying DSP keepalive timeout message.

The message "dsp keepalive timeout" appears after the following actions:

1. Create a Meet Me conference.

2. Ad-hoc the Meet Me into itself.

3. dsp keepalive timeout" replaces the word "connected" on the Cisco IP Phone 7960.

SNMP

CSCdr59957

SNMP agent sends bad response packet for certain Cisco IP Phone addresses.

Given any IP Phone, with IP address X.X.X.Y, where

X is any valid IP address range, and

Y ranges from 0 to 15

the Cisco CallManager SNMP agent cannot decode the last byte of the IP address correctly (in the preceding case, the byte represented by 'Y').

This causes the Cisco CallManager SNMP Agent to report an incorrect IP address for the Cisco IP Phone in question. The last byte of the IP address for that phone would be reported incorrectly.

The only case for which the IP address will be reported correctly is when a Cisco IP Phone is assigned a network address greater than 15 for its last byte.

Using the preceding example of X.X.X.Y, where Y ranges from 16 to 255, the Cisco CallManager SNMP agent will correctly report the IP address of the phone.


Open Caveats

Open Caveats for Cisco CallManager Release 3.0(6)

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

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

DDTS number
Description

CSCds87815

AVVID: Call group pickup no longer works.

Workaround: In order 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, then you can pick up the call by pressing the callPickup button. If the ringing call is part of another call pickup group then 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 pickup a call under any condition.

CSCds82957

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

Workaround: Immediately after an upgrade, let the Cisco CallManager sit for 10 minutes; then, stop it; shut down DBL COM+ object, restart MSSQLServer service, count to five; after it starts, restart Cisco CallManager.

If this sequence is successful, the problem appears to be eliminated. If this sequence is unsuccessful, try a full power-cycle and perform the sequence again.

CSCds83956

Cisco CallManager does not send DRQ to GK after Cisco CallManager receives ARJ, bandwidth control.

Workaround: From the gatekeeper, issue the following command: clear h323 gatekeeper calls <local-id>.

CSCds84062

Calls between Cisco CallManagers using H.323 disconnect after 5 seconds.

Workaround: Expanding MediaExchangeInterfaceCapsTimeout=10, and MediaExchangeTimeout=9 may help the issue.

CSCds82725

Conference fails intermittently when inviting external extension.

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

CSCds82314

Cisco CallManager will not initialize if a lot of translation patterns exist.

Workaround: Do not add more than 300 H.323 translation patterns. Do this maintenance during nonpeak hours.

CSCds81538

Calls through AS5300 do not operate properly with IAQ.

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

CSCds76274

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

Workaround: Restart the Ciscco CallManager to restore the bandwidth counts.

CSCds85150

CTI: Gateway call is not producing RINGBACK event.

Workaround: No workaround exists.

CSCds77604

Cisco IP Phone 7960 rings after call transfer even if ring is disabled.

Workaround: No workaround exists.

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.

CSCds72297

Dead air appears when calling from PSTN if FWRall is in a loop.

Workaround: No workaround exists. The system is not designed to function this way.

CSCds72110

Ringback not heard on external calls after redirected to station.

Workaround: This is a known problem when using an IOS gateway, a fix is being explored. This operation works with a WS-X6608 board.

CSCds72125

DisconnectedEvent received with Cause=CtiResourcesNAvail.

Workaround: No workaround exists.

CSCds79206

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

Workaround: No workaround exists.

CSCds72145

Call should not go idle if Redirect Request fails.

Workaround: No workaround exists.

CSCds43712

PerfMon statistics appear to be unreliable.

Workaround: Use CiscoLines statistic or restart Cisco CallManager to get statistics in sync.

CSCds87815

AVVID: Call group pickup no longer works.

Workaround: No workaround exists.

CSCds90743

Cisco CallManager crashes when attempting to add 17 participants to Call Forward Back.

Workaround: Under Conference Bridge Parameters, do not allow more than 16 users in either an Ad Hoc or Meet Me conference.

CSCds91718

Include CTI Messages in default SDL trace setting.

Workaround: Set the following "Call Manager" parameter from the Cisco CallManager Administration page, select Service>Service Parameters, change the SDLTraceTypeFlag value as indicated and then click the Update button.

SdlTraceTypeFlag - set to 0x00000CB05

CSCds74266

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

Workaround: This workaround involves two parts.

1. When making a large number of gatekeeper calls, you must monitor the virtual memory using Perfmon. When virtual memory gets to 1.5 gigabytes, you need to schedule a switchover after hours. If the system gets to 1.9 gigabytes, you must standby and restart as soon as the Cisco CallManager quits making calls. Your limit is 2 gigabytes, and the Cisco CallManager will quit at that point. A manual restart may be necessary. It sometimes restarts by itself, but the virtual memory issue has negative side effects, which caused the Cisco CallManager to act differently in different situations.

2. Or, simply get faster IOS hardware. The problem occurred while using a Cisco 2600 Series gateway. Cisco believes the problem would be much less likely to occur when using a fa3640 IOS gateway.

CSCds67777

Blind transfer cannot complete successfully.

Workaround: No workaround exists.

CSCds67657

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

Workaround: If the virtual memory for the Cisco CallManager is less than 1.5 GB, the system is operating normally. If the system exceeds 1.5 GB, schedule a maintenance reboot.

CSCds65137

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

Workaround: There is no known workaround on the Cisco side; however, the switch may be reprovisioned to accept these calls under a different numbering type.

CSCds62385

Cisco CallManager sends alerting before connect while in progress state.

Workaround: No workaround exists for this problem.

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

CSCds57777

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

Workaround: No workaround exists for this problem.

CSCds57155

Inside DialTone signal changed to the Alerting signal.

Workaround: No workaround exists.

CSCds55942

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

Workaround: Avoid conferencing a call back on itself.

CSCds55389

Backup installation starts after exiting the Cisco CallManager installation.

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

CSCds55086

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

Workaround: Microsoft has a fix, contact Microsoft support for details.

CSCds53113

Dual ringback tone is heard when calling PSTN using H.323 gateway.

Workaround: Using a Digital Access Gateway eliminates this problem.

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.

CSCds50763

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

Workaround: No workaround exists for ethicist IP Phone model 12sp+ or Cisco IP Phone model 30 VIP; however, this operations works on the Cisco IP 7900 Family Phones.

CSCds50672

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

Workaround: Do not forward a phone to itself.

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.

CSCds50352

System Unavailable displays on Cisco IP Phone 7960.

Workaround: No workaround exists.

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, it must be changed back before proceeding.

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.

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.

CSCds46274

960 user on G.729 call hears hiss after digit during IVR prompt.

Workaround: No workaround exists.

CSCds46040

One WS-X6608 port not taking configuration changes.

Workaround:

1) Delete the new.CNF file.

If a CFB port or MTP port (with Mac address mac12345) fails to change to a digital gateway, find the configuration file SDAmac12345.cnf in the TFTPpath directory of the Cisco CallManager server (or the special TFTP server). Delete SDAmac12345.cnf.

If a SDA port (with Mac address mac12345) fails to change to a transcoder, find the configuration file MTPmac12345.cnf in the TFTPpath directory of the Cisco CallManager server (or the special TFTP server). Delete MTPmac12345.cnf.

If a SDA port (with Mac address mac12345) fails to change to a hardware conference bridge, find the configuration file CFBmac12345.cnf in the TFTPpath directory of the Cisco CallManager server (or the special TFTP server). Delete CFBmac12345.cnf.

2) Restore the deleted .CNF file.

When the port resets automatically next time (because it can never register with a wrong TCP port), it will use the default .CNF file of the old device type to register to a Cisco CallManager and receive the load IDof the new port type for program update

@.

After program update, the new program will use the default .CNF file of the new load type to register to a Cisco CallManager. At this time, you may restore the deleted .CNF file.

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.

CSCds43411

Changes to Calling Search Spaces do not happen until Cisco CallManager reloads.

Workaround: Stop and restart Cisco CallManager.

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.

CSCds39670

Incorrect MsgWaitingLampMode in CTI LineGetInfoResp for Rt points Workaround: No workaround exists.

CSCds37131

Cisco CallManager CPU usage spikes upon updating translation tables.

Workaround: No workaround exists.

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.

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.

CSCds34596

Can't Delete A Server - Error: 1576 UNDEFINED

Workaround: Take the following text and create RemoveServerFromDB.bat. Then, execute RemoveServerFromDB.bat without command line parameters. This will display the command line parameters required. The batch file will remove all services, devices, parameters, and associated server records.

CSCds28310

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

Workaround: Always keep the Softphone in a low-bandwidth region.

CSCds26003

Lack of AutoRegistration DNs causes memory leak in DLLHOST.EXE.

Workaround: Increase the range of DNs to be used by AutoRegistration. Then, to reduce the memory used by DLLHOST.EXE, open Component Services from the Administrative Tools menu. Open the Components and find the DBL component. Shut down DBL by right clicking and selecting shutdown. The DBL component will restart on its own when needed.

CSCds18680

Users cannot set URL for plug-ins.

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

CSCds12355

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

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

CSCds11354

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

With Cisco Call Manager 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 hear dead air; they will not hear ringback.

Workaround: Resolving this caveat requires IOS changes. To work around the problem, replace the IOS gateway with a Cisco Digital Access Trunk Gateway (DE30, DT24+) or a Cisco Catalyst 6000 8 Port Voice T1/E1 and Services Module.

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. Lower resolutions are not supported.

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 7960. The directory number displays instead.

Workaround: None. This feature is not currently supported.

CSCdr93939

In times of network congestion or high variable delay, the jitter buffer on a Cisco IP Phone 7960 will grow to a large value in an attempt to compensate for the large amount of jitter. When network conditions improve and the jitter returns to a low value, the phone will continue to buffer packets for a long time in its jitter buffer, thereby causing unacceptable voice delay.

Workaround: Put the call on hold and then resume it; this will start a new RTP stream and reset the jitter buffer.

CSCdr91539

Messages button on Cisco IP Phone 7900 Family 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 line that the user intended to retrieve.

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 in the case where two different phones share the same directory number. Default is still F.

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

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

CSCdr82850

Alerting message from JTAPI is delayed > 2 seconds.

Workaround: No workaround exists.

CSCdr81185

Windows media player crashed on Cisco SoftPhone client when user tried to play video.

Workaround: Download the latest Windows Media Player, or for more information on a workaround for this problem, see the Microsoft Knowledge Base article Q253798. The Knowledge Base article can be found at http://search.support.microsoft.com/kb.

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

CSCdr80638

Locations do not recognize a transcoder correctly.

Workaround: No workaround exists.

CSCdr61739

dbprocs - error - getProcessConFigInt - SdlMaxRouterLatencySecs

Workaround: This message can be ignored.

CSCdr53720

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

Workaround: Have phones forward on busy to voice mail.

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.

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.

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 (say 1006); then, the call you will no longer experience the problem.

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.

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 shared-line capability is not supported for other analog gateways in this release.

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 are reflected on the MIB table that is local to the change but not in all MIB tables throughout the cluster. Updates will only be reflected 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 will reflect the change.

When groups and regions are added, no MIB tables will reflect 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.

CSCdr36406

A <CmdArg>[Object Error]<noCmdArg> error message returns when a user is added via the Cisco CallManager User Administration web pages.

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.

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

There is no workaround to this problem other than limiting the number of calls through a given transcoder device by expanding the number of transcoders available.

If at least twice as many transcoders are available as there are calls that need them at any given time, the problem should be eliminated.

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. Reorder is not recognized by the Cisco uOne port, 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.

CSCdr20726

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

Workaround: None. This feature is not supported in Cisco CallManager Release 3.0(6).

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 9 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 9 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 10 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 10 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 as 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 Connection Online

Cisco continues to revolutionize how business is done on the Internet. Cisco Connection Online is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information and resources at any time, from anywhere in the world. This highly integrated Internet application is a powerful, easy-to-use tool for doing business with Cisco.

CCO's broad range of features and services helps customers and partners to streamline business processes and improve productivity. Through CCO, you will find information about Cisco and our networking solutions, services, and programs. In addition, you can resolve technical issues with online support services, 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 CCO to obtain additional personalized information and services. Registered users may order products, check on the status of an order and view benefits specific to their relationships with Cisco.

You can access CCO in the following ways:

WWW: www.cisco.com

Telnet: cco.cisco.com

Modem using standard connection rates and the following terminal settings: VT100 emulation; 8 data bits; no parity; and 1 stop bit.

From North America, call 408 526-8070

From Europe, call 33 1 64 46 40 82

You can e-mail questions about using CCO to cco-team@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, for your convenience many documents contain a response card behind the front cover. Otherwise, you can mail your comments to the following address:

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

We appreciate and value your comments.