Cisco CallManager Release 3.0(10, CallManager Release 3.0 Specification

Release Notes for Cisco CallManager
Release 3.0(10)

Original CCO appearance: June 20, 2001
Revised: July 2, 2001

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

Fora list of the open and resolved caveats for Cisco CallManager Release 3.0(10),
see “Resolved Caveats” section on page 20 and “Open Caveats” section on

page 64. These release notes are updated every maintenance and major release.

Use these release notes in conjunction with the Installing Cisco CallManager
Release 3.0(10) document, located on Cisco Connection Online (CCO), and the
Cisco Documentation CD-ROM. The Installing Cisco CallManager Release

3.0(10) document is also packaged with your CDs or convergence server.
Access the latest software upgrades and release notes for Cisco CallManager

3.0(10) on Cisco Connection Online (CCO) at

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

Corporate Headquarters:
Cisco Systems, Inc., 170 West Tasman Drive, San Jose, CA 95134-1706 USA

Copyright © 2001. Cisco Systems, Inc. All rights reserved.

Contents

Contents

These release notes discuss the following topics:

• Introduction, page 2

• System Requirements, page 3

• Related Documentation, page 3

• New and Changed Information, page 4

• Resolved Caveats, page 20

• Open Caveats, page 64

• Documentation Updates, page 82

• Obtaining Documentation, page 100

• Obtaining Technical Assistance, page 102

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.

Release Notes for Cisco CallManager Release 3.0(10)

2

78-13493-02

System Requirements

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

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

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

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

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

System Requirements

Determining the Software Version

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

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

• Installing Cisco CallManager 3.0(10)

• Quick Start Guide for Cisco CallManager Release 3.0

• Cisco CallManager Administration Guide for Release 3.0(5)

• Troubleshooting Guide for Cisco CallManager Release 3.0(5)

78-13493-02

Release Notes for Cisco CallManager Release 3.0(10)

3

New and Changed Information

• Cisco IP Phone 7900 Family Administration Guide

• Configuring Remote Serviceability for Cisco CallManager Release 3.0

• Using Cisco CallManager Trace Gathering Tool for Diagnostic Traces

• Cisco WebAttendant Quick Start Guide

• Cisco WebAttendant User Guide

• Cisco JTAPI Developer Guide

• Cisco TAPI Developer Guide

• Software License Agreement

New and Changed Information

New Software Features for Release 3.0(10)

Cisco CallManager Release 3.0(10) adds features and provides additional
workarounds to open caveats and resolves caveats.

Refer to “Resolved Caveats - Release 3.0(10)” section on page 20, “Open

Caveats” section on page 64, and the “Important Notes for Release 3.0(10)”
section on page 5 for more information.

Customer Enterprise Directory Integration Component for Microsoft Active
Directory and Netscape Directory Server

Cisco CallManager Release 3.0(10) supports the customer enterprise directory
integration component for Microsoft Active Directory and Netscape Directory
Server.

The enterprise directory integration component allows the customers' enterprise
directories to maintain the association of devices to users. Using these directories,
administrators can add users manually or link to them from an existing corporate
Lightweight Directory Access Protocol (LDAP) directory.

To read installation instructions, refer to

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

Release Notes for Cisco CallManager Release 3.0(10)

4

78-13493-02

Backup Utility

The Backup Utility now creates backup files with the .sti extension instead of
using the .tar extension.

If you have .tar files already on your system, such as from an upgrade, the Backup
Utility restores those files as well, but all current back ups are saved as a .sti
extension.

Important Notes for Release 3.0(10)

Compatibility Matrix

Table 1 lists versions with which Cisco CallManager 3.0(10) has been tested.

Table 1 Compatibility Matrix

New and Changed Information

Component/Application Version Tested

Cisco Unity 2.4.6.102
Cisco Unity TSP 1.0.0.28
Cisco Personal Assistant 1.1
Apps 2.1 and 2.2
Cisco Customer Response

Application
IOS 12.2(2T)
Cisco WebAttendant 3.0(3.36)
Cisco IP SoftPhone 1.1(1), 1.1(2) and 1.2(1)
ICD 2.1(1a)
Firmware:Cisco IP Phone 7960 P003D310
Firmware: Cisco IP Phone 7940 P003D310
Firmware: Cisco IP Phone 7910 P004D310
IPCC/ICM Do not upgrade to

2.2

Cisco CallManager Release

3.0(10)

78-13493-02

Release Notes for Cisco CallManager Release 3.0(10)

5

New and Changed Information

Table 1 Compatibility Matrix

Component/Application Version Tested

Cisco Unity 2.4.6.102
JTAPI 1.1(1.19)
TAPI 3.0(1.18)

Service Parameters

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

New Software Features in Release 3.0(9)

The following section contains new and changed software features in
Cisco CallManager Release 3.0(9).

User Interface Enhancement

A new configuration parameter check box exists on the Cisco CallManager
Administration H.323 Gateway ConfigurationWeb page. This allowsa H.225D to
"run on every node.”If you select this option (by default it is on), theH.225D runs
on every node.

When upgrading an existing system, your current configuration remains.

Note See CSCdt40606 in the Resolved Caveats - Release 3.0(9) section

for more information.

Release Notes for Cisco CallManager Release 3.0(10)

6

78-13493-02

Service Parameters

Cisco CallManager Release 3.0(9) supports new service parameters.
Refer to Table 9 on page 83 for a complete listing of all service parameters, which

includes descriptions and default values, that were not included in Release 3.0(5)

of Cisco CallManager Administration Guide.

New Software Features in Release 3.0(8)

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

Strong Encryption

New and Changed Information

Note Versions preceding Cisco CallManager Release 3.0(8) included

Global Call ID

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

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

TNDconnect.exe(Bridged Telnetapplication)and DC Directory .dll
extensions. These files contain strong encryption (128-bit).

The TAPI Service Provider (TSP) Version 3.0, which is packaged with
Cisco CallManager 3.0, supports Global Call ID.

Applications use the Global Call ID to identify a specific call as it traverses
various resources in the Cisco CallManager. For example, a Call Center
application uses Global Call ID to track a call that comes into a CTI route point,
gets redirected to a CTI port, and terminates at an Agent IP phone.

78-13493-02

Release Notes for Cisco CallManager Release 3.0(10)

7

New and Changed Information

New Software Features in Release 3.0(7)

Cisco CallManager Release 3.0(7), a maintenance release, adds no new features.
Refer to the “Resolved Caveats - Release 3.0(7)” section on page 47 for more
information.

Important Notes for Release 3.0(7)

Service Parameter Restart Conditions

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

• Digital Port

• Ethernet Phone Port

• Analog Port

• MGCP Listen Port

• MGCP Keep-alive Port

• MessageWaitingOffDN

• MessageWaitingOnDN

• StatisticsEnabled

• MaxDaResponseTimeoutErrorCount

• MaxTotalNumberOfRegisteredCallingEntities

Note The service parameter restart conditions apply to all versions up to

an including Cisco CallManager 3.0(7).

Note Refer to Table 9 on page 83 for more information on service

parameter definitions and defaults.

Release Notes for Cisco CallManager Release 3.0(10)

8

78-13493-02

New and Changed Information

Cisco IP Phone 7910 and Cisco IP Phone 7940 Compatibility Issue

Cisco IP Phone 7910 and Cisco IP Phone 7940 are only supported by
Cisco CallManager Release 3.0(5a) and higher. If you are running an earlier
version, you must upgrade to a later version at
http://www.cisco.com/cgi-bin/tablebuild.pl/callmgr.

New Software Features in Release 3.0(6)

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

Cisco WebAttendant

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

78-13493-02

As one of its primary benefits over traditional attendant console systems, Cisco
WebAttendant monitors the state of everyline 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.

Release Notes for Cisco CallManager Release 3.0(10)

9

New and Changed Information

Tech Prefixes

Step 1 Choose Cisco CallManager.
Step 2 Choose Cisco CallManager from Configured Services.
Step 3 Enter GateKeeperSupportedPrefix in the Params section.
Step 4 Choose String as the type.
Step 5 Click update.
Step 6 Select GateKeeperSupportedPrefix from the Configured Service Parameters.
Step 7 Add the proper value; i.e., 1#, 2#, etc. Only one tech prefix is allowed.

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:

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.

Note Refer to Table 9 on page 83 for more information on service

parameter definitions and defaults.

Important Notes for Release 3.0(6)

Cisco IP Phone 7910 and Cisco IP Phone 7940 Compatibility Issue

Cisco IP Phone 7910 and Cisco IP Phone 7940 are only supported by
Cisco CallManager Release 3.0(5a) and higher. If you are running an earlier
version, you must upgrade to a later version at
http://www.cisco.com/cgi-bin/tablebuild.pl/callmgr.

Release Notes for Cisco CallManager Release 3.0(10)

10

78-13493-02

New and Changed 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

78-13493-02

Release Notes for Cisco CallManager Release 3.0(10)

11

New and Changed Information

• 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):

Release Notes for Cisco CallManager Release 3.0(10)

12

78-13493-02

New and Changed Information

• Simpler configuration—Previousversions 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

78-13493-02

Release Notes for Cisco CallManager Release 3.0(10)

13

New and Changed Information

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 developmentassistance will be made available in
the near-term through a specificallytaskedhelp 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.

Release Notes for Cisco CallManager Release 3.0(10)

14

78-13493-02

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.

New and Changed Information

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

78-13493-02

Release Notes for Cisco CallManager Release 3.0(10)

15

New and Changed Information

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.

Release Notes for Cisco CallManager Release 3.0(10)

16

78-13493-02

• 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

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

New and Changed Information

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.

78-13493-02

Release Notes for Cisco CallManager Release 3.0(10)

17

New and Changed Information

BAT Reinstallation

IOS Version

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.

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

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

Intercluster Trunk Configuration

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

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

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

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

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

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

• Cluster-1 configures 4 intercluster trunks (to CCM-D and CCM-E in

Cluster-2 and CCM-F and CCM-G in Cluster-3).

Release Notes for Cisco CallManager Release 3.0(10)

18

78-13493-02

New and Changed Information

• 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 configurationand you still

want to maintain the intercluster links, you must modify the
configurationfor each cluster to add the necessary links between the
cluster to all of the Cisco CallManagers in the new cluster. You must
also configure the new cluster with intercluster trunks to all of the
Cisco CallManagers in the existing clusters.

Cisco CallManager Integration with Corporate LDAP Directories

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

Cisco IP Phone 7910 and Cisco IP Phone 7940 Compatibility Issue

Cisco IP Phone 7910 and Cisco IP Phone 7940 are only supported by
Cisco CallManager Release 3.0(5a) and higher. If you are running an earlier
version, you must upgrade to a later version at
http://www.cisco.com/cgi-bin/tablebuild.pl/callmgr.

78-13493-02

Release Notes for Cisco CallManager Release 3.0(10)

19

Resolved Caveats

Resolved Caveats

Resolved Caveats - Release 3.0(10)

Table 2 lists and describes Caveats that were resolved in Cisco CallManager

Release 3.0(10).

Note If you have an account with Cisco.com (Cisco Connection Online), you can

use the Bug Toolkit to find caveats of any severity for any release.

To access the Bug Toolkit, log on to http://www.cisco.com/support/bugtools.

Table 2 Cisco CallManager Release 3.0(10) Resolved Caveats

DDTS Number Summary Explanation

CSCdr51841 When a shared line appearance is

updated, all line appearances change.

CSCdr81185 Windows Media Player may crash when

streaming media.

CSCds20015 Cisco IP Phone7960 P3 port does not

forward for first 9 seconds after link-up.

When the shared line is changed, only this
one appearance now changes.

A problem existed with the co-existence of
a TAPI service provider and the Windows
Media Player. If a TAPI service provider is
installed, the Windows Media Player may
hang or generate an error message when
streaming media.

A Cisco CallManager code change corrects
this behavior.

A Cisco CallManager code change adds a
service parameter to Settings/Network
Configuration/Forwarding Delay YES/NO.

Set to YES for connecting twoswitches. Set
to NO for connecting a PC\workstation.

The default setting designates Forwarding
Delay YES.

Release Notes for Cisco CallManager Release 3.0(10)

20

78-13493-02

Table 2 Cisco CallManager Release 3.0(10) Resolved Caveats (continued)

DDTS Number Summary Explanation

Resolved Caveats

CSCds43704 Call looping uses CPU and other

resources in Cisco CallManager.

CSCds74822 Service Configuration application does

not function properly.

CSCds82957 SQLdatabase does not properly instruct

Cisco CallManager to start after
upgrade.

CSCdt29182 Analog gateway sends caller name to

Cisco CallManager in calling party
number IE.

CSCdt31211 A forwarded call to a particular cellular

phone on a Cisco CallManager
disconnects.

A Cisco CallManager code change fixes
this problem.

A Cisco CallManager code change fixes
this behavior.

DBLR used code that was not setting up
CDR connection strings. This situation
preventedCisco CallManager from coming
up. The new code retries the CDR setup
until it completes.

The code now ensures forward and
backward capability to correct this
behavior.

When Cisco 7960 IP Phone with
Cisco CallManager 3.0(7) redirects
(forwards) a call from PSTN to the AU
phone via PRI with WS-X6608-T1 gateway
or Cisco Digital Access Gateway DT24+,
PSTN side terminates the forwarded call
and the originator phone receives no
ringback tone.

CSCdt41472 Cisco WebAttendant client cannot log

in because the UserID is already
reported as logged in.

CSCdt41479 Cisco WebAttendant client install does

not have default port number of 4321.

CSCdt41493 Cisco WebAttendant selects operating

system web browser to create client
shortcut.

Release Notes for Cisco CallManager Release 3.0(10)

78-13493-02

A code change fixes this problem.
This results from a problem with the

verbiage on the display. A message now
displays to say that the device was not
found, instead of showing that the login
failed.

When the Cisco WebAttendant client is
installed, the default value "4321" is in the
TcdSrv Listen Port.

The Cisco WebAttendant shortcut in the
Start Menu will now open
Cisco WebAttendant with Microsoft
Internet Explorer.

21

Resolved Caveats

Table 2 Cisco CallManager Release 3.0(10) Resolved Caveats (continued)

DDTS Number Summary Explanation

CSCdt42403 User loses a call after transferring

toward a busy line.

CSCdt47805 High CPU usage during directory

searches from Cisco IP Phone 7960
occurs.

CSCdt46334 Bandwidth doesnotrelease to pool after

normal call clearing.

CSCdt49472 User cannot assign an all-numeric

pattern to Gatekeeper-controlled H.225
device.

CSCdt51077 User cannot use hostname as

Cisco CallManager server name when
primary DNS suffix is set.

CSCdt59773 Cisco IP Phone 7960 is susceptible to a

ping attack and may crash and reboot.

A Cisco CallManager code change corrects
this behavior. This item duplicates
CSCdt45632, CSCdt82239, and
CSCdr58998.

This only occurred when 3-4 phones were
set to simultaneously do a corporate
directory search with blank search criteria
that the publisher CPU hits 95+% for 10-20
seconds.

A Cisco CallManager code change corrects
this behavior.

A code change allows entry of numeric
patterns.

The software now allows a user to use
hostname as Cisco CallManager server
name when primary DNS suffix is set.

This occurred when scrolling through
various menus on the phone while it is
under a ping attack. This no longer occurs.

CSCdt62462 Synchronous Data Link (SDL) router

service stopped.

CSCdt65935 CallForward SDL update does not work

(SsapiPtr->SsDbChangeFwdInfoReq).

CSCdt66312 Message WaitingIndicator(MWI)stays

off when message is left while SP is up,
but line is closed.

Release Notes for Cisco CallManager Release 3.0(10)

22

A Cisco CallManager code change corrects
this behavior.

A Cisco CallManager code change puts in
an alarm to collect more information when
the Cisco CallManager fails to update the
local database tables when it receives
change notification from database layer.

A newer version of Cisco Unity TSP
appears to have made this caveat
unreproducible.

78-13493-02

Table 2 Cisco CallManager Release 3.0(10) Resolved Caveats (continued)

DDTS Number Summary Explanation

Resolved Caveats

CSCdt71276 Backing up Media Convergence Server

takes about 50 minutes; in previous
versions, this took much less time.

The priority of the backup engine was
reduced, so it does not interfere with the
operation of the Cisco CallManager.

A code change corrects this behavior, so the
backup takes less time.

CSCdt71631 Name changes to partitions do not take

effect until the Cisco CallManager
reboots.

A code change ensures that, after changing
the name of partition, the renaming will
take effect without restarting database layer
and calling search space.

CSCdt72448 “lineGetCallInfo” fails after call

transitions from CONF to IDLE.

If an application tries to do a
lineGetCallInfo on a call that has
transitioned from the CONFERENCED
state to the IDLE state, the TSP returns
LINEERR_OPERATIONFAILED.

The problem occured on
Cisco CallManager 3.0(6) with TSP

3.0(0.42).

CSCdt72868 The existing route pattern update fails. A Cisco CallManager code change inserts

an alarm to collect more information when
the Cisco CallManager fails to update the
local database tables when it receives
change notification from database layer.

CSCdt73576 Deleting multiple CTI route points

causes a JavaScript runtime error.

CSCdt74051 Pilot point stops working after TCD

stops and starts.

CSCdt74385 A need exists for CDR

globalCallID_callid to be more than 20
bits.

CSCdt74871 A need exists to delete unassigned

directory numbers from previous
versions.

78-13493-02

A modification fixes the JavaScript error.

A Cisco CallManager code change corrects
this behavior.

The code now allows globalCallID to be 24
bits so that the CDR database can hold more
than 1,048,575 unique records.

Directory numbers now disappear from this
list after upgrade.

Release Notes for Cisco CallManager Release 3.0(10)

23

Resolved Caveats

Table 2 Cisco CallManager Release 3.0(10) Resolved Caveats (continued)

DDTS Number Summary Explanation

CSCdt75620 A need exists for TAPI dwCalledID to

reflect original called party.

CSCdt75990 Calls with compatible regions and

capabilities fail.

CSCdt78337 If call park range overlaps at pattern,

Cisco CallManager router thread may
stop.

CSCdt80375 Cisco Access Digital Trunk Gateway

DT-24+ may not reregister after failure.

A code change ensures that TAPI
dwCalledID reflects the original called
party.

A code change resolves this behavior.

If call park range overlapped an external
dial pattern, and you dialed one of the call
park numbers, Cisco CallManager may
have displayed a router thread stopped
error.

A code change corrects this behavior.
Rare circumstances can lead

Cisco CallManager to perceive a
Cisco Access Digital Trunk Gateway
DT-24+ D-channel as still online when, in
reality, it is down and has unregistered with
the Cisco CallManager. This causes
CallManager to bar the Cisco Access
Digital Trunk GatewayDT-24+ from
reregistering because it perceives the
D-channel to be up.

CSCdt82340 Cisco CallManager does not restart

when experiencing race condition.

CSCdt83029 When an extension has a call on hold

and an active call, the held call does not
disconnect when each caller hangs up
on the call.

CSCdt83360 After Cisco CallManager is upgraded,

some services do not appear.

Release Notes for Cisco CallManager Release 3.0(10)

24

A Cisco CallManager code change corrects
this behavior.

Cisco CallManager software modification
in the initilization procedure makes it exit
abnormally when there is a problem
(exception returned from DBL) with
initializing the CDR thread.

CTI now sends an event indicating that the
call on HOLD and an active call exist, and
the active call hangs up.

A code change extends the services URL
maximum length to beyond 128 characters.

78-13493-02

Resolved Caveats

Table 2 Cisco CallManager Release 3.0(10) Resolved Caveats (continued)

DDTS Number Summary Explanation

CSCdt83902 User cannot answer a consult transfer. The fix releases the answer thread when

applications invoke an answer request on a
consult call that is cleared due to transfer.

CSCdt84284 AVVID: Cisco WebAttendent client

does not have access to wausers share.

CSCdt84616 Blind transfer from voice mail to

MeetMe does not bridge audio.

CSCdt86530 AVVID:SMDI LTN does not increment

across PRI spans

CSCdt86741 Pressing the line soft key button does

not answer call.

CSCdt88683 Transfer button fails with call waiting

enabled.

CSCdt91200 A Cisco Media Convergence Server

backup operation hangs when manually
initiated.

Microsoft security is inherited, which in
certain sites, caused problems where
adminstrators changed security settings at
higher point than the WAUSERS directory,
which then prevented domain users from
accessing the data with the advertised
method.

A code change enables transfer to work
properly.

The solution allows SMDI port to
increment accross PRI spans.

A code change allows the user to answer the
phone by pressing the line button.

A code change resolves this behavior.

A Cisco CallManager code change corrects
this behavior.

CSCdt91533 Changes to ringlist.xml can cause

phone-booting loop.

CSCdt91824 A need exists for a method to clear stale

held calls.

CSCdt92019 No events occur to third party when

second party drops consult transfer call.

78-13493-02

The problem occurred because the phone
was resetting after the ring list was
shortened.

A code change allows applications to clear
a connection in a stale or disconnected
state.

This problem occurred using the Cisco TSP
that is bundled with Cisco CallManager

3.0(8). The problem intermittently
occurred about one in four times.

Cisco CallManager code change corrects
this behavior.

Release Notes for Cisco CallManager Release 3.0(10)

25

Resolved Caveats

Table 2 Cisco CallManager Release 3.0(10) Resolved Caveats (continued)

DDTS Number Summary Explanation

CSCdt94077 Device tables do not update correctly

after failover occurs.

CSCdt94179 Redirect fails, and subsequent redirect

gets no response.

CSCdt95027 Cisco CallManager does not allow

simulated phones to register.

Calls going out through a digital gateway
were being dropped after one
Cisco CallManager in a cluster fails in a
certain way (links to other
Cisco CallManagers in the cluster stay up,
even though its devices fail over), and its
phones and gateways have registered with
the backup Cisco CallManager.

A user running Cisco CallManager Release

3.0(8) or earlier in a clustered environment
more likely encounters this problem.

A Cisco CallManager code change corrects
this behavior.

A Cisco CallManager code change ensures
that orphaned destinations get cleaned up
properly during a redirect of the originator.

Anydevice,whichduringregistrationsends
the MaxFramePacketSize as zero during
registration, cannot register with the
Cisco CallManager.The device needs to
send the correct capabilities to be able to
register.

CSCdt95612 When a user right-clicks on the backup

utility icon in the task tray, then clicks
somewhere on the desktop, part of the
popup menu remains on the screen.

CSCdt95934 After Cisco CallManager is upgraded,

the Cisco CallManager server IP
address changes to the
Cisco CallManager DNS name.

Release Notes for Cisco CallManager Release 3.0(10)

26

A Cisco CallManager code change corrects
this behavior.

To correct this caveat, the database layer
now resolves the host name and IP address
better.

78-13493-02

Table 2 Cisco CallManager Release 3.0(10) Resolved Caveats (continued)

DDTS Number Summary Explanation

Resolved Caveats

CSCdt96338 The simultaneous call limit for H.323

device equals 248 when it should be

360.

CSCdt96745 H.245 negotiation fails on intercluster

trunk for forwarded call.

CSCdu00792 Calls were getting dropped for constant

delay.

Intercluster calls stop at 248 active calls per
H.323 device. A code change allows 360
calls to be in place simultaneously.

Users experience this problem only with
Cisco CallManager Release 3.0(8) or
earlier.

In certain scenarios, when a call across an
intercluster trunk is forwarded to another
gateway, the call will fail due to a Media
Capabilities Exchange timeout. This has
only been observed when the subscriber
machines in a cluster are up. This behavior
no longer exists in Cisco CallManager
Release 3.0(10).

When large packet delays were inserted
between gateways and Cisco CallManager,
some timers were expiring.

The code change compensates several
internal timers for inaccuracy and sets a
higher minimum default value for the
configurable timer
MediaExchangeTimeout.

CSCdu02128 A race condition can cause transfer

table corruption.

CSCdu03062 RDNIS does not appear in Q931

message.

78-13493-02

Only customers who install
Cisco CallManager 3.0(10) for the firsttime
receive this bug fix. A customer who
upgrades to Cisco CallManager 3.0(10)
does not get this bug fix.

A code change prevents the race condition
from occurring.

The RDNIS was sometimes not being sent
out the digital gateway, even though the
Redirecting Number IE Delivery box is
checked in the gateway configuration.

Release Notes for Cisco CallManager Release 3.0(10)

27

Resolved Caveats

Table 2 Cisco CallManager Release 3.0(10) Resolved Caveats (continued)

DDTS Number Summary Explanation

CSCdu04286 After conferencing, if only two parties

are left in the conference, TAPI redirect
causes both parties to be dropped
instead of just the one doing the
redirect.

CSCdu05420 Locations bandwidth takes more than

20 hours to free up.

CSCdu05485 Sending out 3.1 kHz causes problems

for some calls. This occurs when using
the Cisco Catalyst 6000 E1.

CSCdu06291 Cisco IP phone accepts only one default

router from Unix Dynamic Host
configuration Protocol (DHCP) server.

CSCdu07051 Cisco CallManager users can have a

user ID with an underscore, but they
cannot log in to CCMUser page with a
login name with an underscore.

A Cisco CallManager code change corrects
this behavior.

Although this problem could not be exactly
reproduced, from the provided trace we
gather that a problem with media occurs
when media are being set up and then torn
down before completing the set up.

A Cisco CallManager code change corrects
this behavior.

Cisco IP Phone 7960 now accepts
additional routers.

The software now accepts an underscore in
the user ID.

CSCdu08613 Cisco uOne port hangs after transfer to

a device where call forward all and/or
call forward back fails.

CSCdu09807 H.323 endpoint always uses display

name of the first line.

CSCdu09917 A need exists for a user to be able to

change AnonymousDevice protocol to
H.225.

Release Notes for Cisco CallManager Release 3.0(10)

28

Cisco CallManager now sends an onhook
signal when the device uses call forward all
and/or call forward back to an unreachable
directory number.

A code change allows for the H.323
gateway to operate differently.

The AnonymousDevice protocol can be
changed to H.225.

78-13493-02

Table 2 Cisco CallManager Release 3.0(10) Resolved Caveats (continued)

DDTS Number Summary Explanation

Resolved Caveats

CSCdu10146 Locations bandwidth calculation is

wrong with software conference and
codec change.

CSCdu12450 AnonymousDevice does not work until

Cisco CallManager stops/starts.

CSCdu13710 Dual-tone multifrequency (DTMF)

intermittenly fails.

CSCdu19849 Cisco CallManager may crash when a

user performs a directory look up to a
partially initialized directory.

CSCdu20435 lineSetupTransfer sometimes returns

call in ONHOLD not OHPT state.

A caller initiates a call to a low bandwidth
(30 KB) location with codec G.729. The
caller initiates a conference using a
software conference bridge, and the codec
changes to G.711. The called party in the
low bandwidth location changes to G.711
and joins the conference even though not
enough bandwidth exists.

A code change corrects this behavior.
A Cisco CallManager code change corrects

this behavior.
A Cisco CallManager code change corrects

this behavior.
This problem occurred because the

directory was not properly configured.

The TSP was not setting the TAPIcall state
appropriately.

CSCdu20892 Pilot point stops working due to

CtiDeviceOpenReq failure.

CSCdu43517 Cisco IP Phone [phone] headset

transmit level is too low versus the
handset level.

Release Notes for Cisco CallManager Release 3.0(10)

78-13493-02

The customer’s pilot point was not
registering with digit analysis.

Three decibals were added to the headset
microphone.

29

Resolved Caveats

Table 2 Cisco CallManager Release 3.0(10) Resolved Caveats (continued)

DDTS Number Summary Explanation

CSCdu68211 The default SdlTraceTypeFlags value is

inadequate for debugging needs.

CMTerminals -- Firmware

CSCdt68876 WS-X6608 port resets when setting up a

FAX call.

The default value SdlTraceTypeFlags
changed to 0x00004B15. This change only
occurs on new installs. On upgrade
installations, the previous setting for the
"SDLTraceTypeFlags" service parameter
remains at 0x00004B05.

Customers who install Cisco CallManager

3.0(10) for the firsttimereceivethisbugfix.
A customer who upgrades to

Cisco CallManager 3.0(10) does not
receive a bug fix for this.

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

A code change resolves a problem that was
causing a timer to restart, which initially
caused this caveat.

CSCdt97510 DTMF tones are sometimes not sent

through 6608 PRI from IP phone.

CSCdu09034 Phones lose IP leases at renewal. They

are forced to unregister from the
Cisco CallManager and acquire a new
IP address.

Release Notes for Cisco CallManager Release 3.0(10)

30

A code change corrects this behavior.

A problem no longer exists in
Cisco CallManager Release 3.0(10).

78-13493-02