Cisco Systems 3.0(10) manual BAT Reinstallation, IOS Version, Intercluster Trunk Configuration

New and Changed Information

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

	Release Notes for Cisco CallManager Release 3.0(10)
18	78-13493-02