Home | Skip to Content | Skip to Search | Skip to Navigation | Skip to Footer |
Worldwide [change] |Register |About Cisco
Guest

Hierarchical Navigation

Cisco Unified Communications Manager (CallManager)

Release Notes for Cisco CallManager Release 3.0(6)

Downloads

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/kobayashi/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