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.

11
Release Notes for Cisco CallManager Release 3.0(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

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

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

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

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

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

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

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

19
Release Notes for Cisco CallManager Release 3.0(10)
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 configuration and you still
want to maintain the intercluster links, you must modify the
configuration for each cluster to add the necessary links between the
cluster to all of the Cisco CallManagers in the new cluster. You must
also configure the new cluster with intercluster trunks to all of the
Cisco CallManagers in the existing clusters.
Cisco CallManager Integration with Corporate LDAP Directories
Cisco CallManager integration with corporate LDAP directories, such as
Microsoft Active Directory and Netscape Directory Services, is not available in
Cisco CallManager Release 3.0(5a). The availability of this feature will be
announced at a later date, pending completion of integration testing
Cisco IP Phone 7910 and Cisco IP Phone 7940 Compatibility Issue
Cisco IP Phone 7910 and Cisco IP Phone 7940 are only supported by
Cisco CallManager Release 3.0(5a) and higher. If you are running an earlier
version, you must upgrade to a later version at
http://www.cisco.com/cgi-bin/tablebuild.pl/callmgr.

Resolved Caveats
20
Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02
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. When the shared line is changed, only this one appearance now changes.
CSCdr81185 Windows Media Player may crash when
streaming media. 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.
CSCds20015 Cisco IP Phone7960 P3 port does not
forward for first 9 seconds after link-up. A Cisco CallManager code change adds a service parameter to Settings/Network
Configuration/Forwarding Delay YES/NO.
Set to YES for connecting two switches. Set
to NO for connecting a PC\workstation.
The default setting designates Forwarding
Delay YES.