Cisco CallManager Release 3.0(10 User manual

Corporate Headquarters:
Copyright © 2001. Cisco Systems, Inc. All rights reserved.
Cisco Systems, Inc., 170 West Tasman Drive, San Jose, CA 95134-1706 USA
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).
For a 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.

Contents
2
Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02
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.

3
Release Notes for Cisco CallManager Release 3.0(10)
78-13493-02
System Requirements
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).
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)

New and Changed Information
4
Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02
•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.

5
Release Notes for Cisco CallManager Release 3.0(10)
78-13493-02
New and Changed Information
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
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 2.2
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
Cisco CallManager Release
3.0(10)

New and Changed Information
6
Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02
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 Configuration Web page. This allows a 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.
JTAPI 1.1(1.19)
TAPI 3.0(1.18)
Table 1 Compatibility Matrix
Component/Application Version Tested
Cisco Unity 2.4.6.102

7
Release Notes for Cisco CallManager Release 3.0(10)
78-13493-02
New and Changed Information
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
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.
Note Versions preceding Cisco CallManager Release 3.0(8) included
TNDconnect.exe (Bridged Telnet application) and DC Directory .dll
extensions. These files contain strong encryption (128-bit).
Global Call ID
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.

New and Changed Information
8
Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02
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.

9
Release Notes for Cisco CallManager Release 3.0(10)
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.
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.

New and Changed Information
10
Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02
Tech Prefixes
Cisco CallManager Release 3.0(6) supports tech prefixes in the Gatekeeper. To
properly configure the Cisco CallManager to register with a tech prefix you must
go to service parameters and perform the following steps:
Step 1 Choose Cisco CallManager.
Step 2 Choose Cisco CallManager from Configured Services.
Step 3 Enter GateKeeperSupportedPrefix in the Params section.
Step 4 Choose String as the type.
Step 5 Click update.
Step 6 Select GateKeeperSupportedPrefix from the Configured Service Parameters.
Step 7 Add the proper value; i.e., 1#, 2#, etc. Only one tech prefix is allowed.
Service Parameter
Cisco CallManager Release 3.0(6) supports a new service parameter.
MaxCTIConnections—This parameter sets the maximum number of
simultaneous active CTI connections between an application and the
Cisco CallManager. The default value is 400 connections.
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.