Cisco CallManager Configuration

Use Cisco CallManager configuration to specify the ports and other properties for each Cisco CallManager that is installed in the same cluster. A cluster comprises a set of Cisco CallManagers that share the same database.

Use the following topics to add, update, or delete a Cisco CallManager configuration or to view system component version information:

Finding a Cisco CallManager

Because you might have several Cisco CallManagers in your network, Cisco CallManager Administration lets you locate specific Cisco CallManagers on the basis of specific criteria. Use the following procedure to locate Cisco CallManagers.

Note During your work in a browser session, Cisco CallManager Administration retains your Cisco CallManager search preferences. If you navigate to other menu items and return to this menu item, Cisco CallManager Administration retains your Cisco CallManager search preferences until you modify your search or close the browser.

Procedure

Step 1 Choose System > Cisco CallManager.

The Find and List Cisco CallManagers window displays. Use the two drop-down list boxes to search for a Cisco CallManager.

Step 2 From the first Find Cisco CallManagers where drop-down list box, choose one of the following criteria:

•Name

•Description

Note The criterion that you choose in this drop-down list box specifies how the list of Cisco CallManagers that your search generates will be sorted. For example, if you choose Description, the Description column will display as the left column of the results list.

From the second Find Cisco CallManagers where drop-down list box, choose one of the following criteria:

•begins with

•contains

•ends with

•is exactly

•is not empty

•is empty

Step 3 Specify the appropriate search text, if applicable, and click Find. You can also specify how many items per page to display.

Tip To find all Cisco CallManagers that are registered in the database, click Find without entering any search text.

A list of discovered Cisco CallManagers displays by

•Cisco CallManager icon

•Cisco CallManager name

•Description

Note You can delete multiple Cisco CallManagers from the Find and List Cisco CallManagers window by checking the check boxes next to the appropriate Cisco CallManagers and clicking Delete Selected. You can delete all Cisco CallManagers in the window by checking the check box in the Matching records title bar and clicking Delete Selected.

Step 4 From the list of records, click the Cisco CallManager icon or name or the Description that matches your search criteria.

•If a Cisco CallManager already exists with settings that are similar to the one that you want to add, choose the existing Cisco CallManager to display its settings, click Copy, and modify the settings as needed.

Changes to the settings for auto-registration partition, external phone number mask, and voice message box mask do not take effect until you restart Cisco CallManager. For information on restarting the Cisco CallManager service, refer to the Cisco CallManager Serviceability Administration Guide.

Caution The Reset Devices button shuts down all devices that are registered with this Cisco CallManager and then brings the devices back up again. This action temporarily interrupts call processing for those devices. Use this button only if you have made configuration changes to most of the devices on this Cisco CallManager and you want to reset all of them at once. For configuration changes to smaller groupings of devices, reset only the affected devices. If possible, avoid resetting devices during peak hours.

Deleting a Cisco CallManager

This section describes how to delete a Cisco CallManager configuration from the database.

Before You Begin

You cannot delete a Cisco CallManager while it is running. To find out which Cisco CallManager groups or features are using the Cisco CallManager, click the Dependency Records link from the Cisco CallManager Configuration window. For more information about dependency records, see the "Accessing Dependency Records" section on page A-1. If you try to delete a Cisco CallManager that is in use, an error message displays. Before deleting a Cisco CallManager that is currently in use, you must perform either or both of the following tasks:

Note If you delete a Cisco CallManager configuration from the database, the Cisco CallManager service continues to run in the background on the server. To deactivate the service, use Cisco CallManager Serviceability. Refer to the Cisco CallManager Serviceability Administration Guide for more information.

Note Assign each Cisco CallManager server address only once (that is, you assign only one Cisco CallManager per server). After you assign a server address to a particular Cisco CallManager, that address disappears from the list.

Cisco CallManager Name

Enter the name that you want to assign to this Cisco CallManager.

Description

Enter a description of the Cisco CallManager.

Starting Directory Number

Enter the first directory number to use for auto-registration of devices.

Ending Directory Number

Enter the last directory number to use for auto-registration of devices.

Specifying a valid range of directory numbers in the Starting Directory Number and Ending Directory Number fields automatically enables auto-registration.

Setting the starting and ending directory numbers to the same value disables auto-registration.

Partition

If you are not using partitions, choose <None>.

If you are using partitions, choose the partition to which auto-registered directory numbers belong from the drop-down list box.

You must choose a range for auto-registration before you can choose a partition, external phone number mask, or voice message box mask.

If more than 250 partitions exist, the ellipsis (...) button displays next to the drop-down list box. Click the ... button to display the Select Partition window. Enter a partial partition name in the List items where Name contains field. Click the desired partition name in the list of partitions that displays in the Select item to use box, and click OK.

External Phone Number Mask

Specify the mask that is used to format caller ID information for external (outbound) calls that are made from the auto-registered devices. The mask can contain up to 50 characters. Enter the literal digits that you want to appear in the caller ID information and use Xs to represent the directory number of the auto-registered device.

For example, if you specify a mask of 972813XXXX, an external call from extension 1234 displays a caller ID number of 9728131234 if the Use External Phone Number Mask option is checked on the route pattern that is used to make the external call.

If you specify a mask of all literal digits, such as 9728135000 to represent a main attendant number, that literal number (9728135000) displays as the caller ID for an external call from any auto-registered device.

Auto-registration Disabled on this Cisco CallManager

Cisco CallManager disables the auto-registration by default to prevent unauthorized connections to the network:

•Uncheck the Auto-registration Disabled check box to enable auto-registration for this Cisco CallManager.

•Check the Auto-registration Disabled check box to disable auto-registration for this Cisco CallManager.

When auto-registration is disabled, you must configure the directory numbers manually whenever you add new devices to your network.

Setting the Starting Directory Number and Ending Directory Number to the same value also disables auto-registration.

If starting and ending directory numbers are currently specified when you disable auto-registration by checking this option, Cisco CallManager sets the starting and ending directory numbers to the same value.

Cisco CallManager uses this TCP port to communicate with the Cisco IP Phones on the network. Accept the default port of 2000 unless this port is already in use on your system. Ensure all port entries are unique. Valid port numbers range from 1024 to 49151.

Digital Port

Cisco CallManager uses this TCP port to communicate with Cisco Access Digital Trunk Gateways (such as the DT-24+ or DE-30+) on the network. Accept the default port of 2001 unless this port is already in use on your system. Ensure all port entries are unique. Valid port numbers range from 1024 to 49151.

Analog Port

Cisco CallManager uses this TCP port to communicate with Cisco Access Analog Gateways (such as the WS-6624 FXS) on the network. Accept the default port of 2002 unless this port is already in use on your system. Ensure all port entries are unique. Valid port numbers range from 1024 to 49151.

MGCP Listen Port

Cisco CallManager uses this TCP port to detect messages from its associated MGCP gateway. Accept the default port of 2427 unless this port is already in use on your system. Ensure all port entries are unique. Valid port numbers range from 1024 to 49151.

MGCP Keep-alive Port

Cisco CallManager uses this TCP port to exchange keepalive messages with its associated MGCP gateway. Accept the default port of 2428 unless this port is already in use on your system. Ensure all port entries are unique. Valid port numbers range from 1024 to 49151.

Viewing Cisco CallManager Component Versions

The Cisco CallManager Component Versions page in Cisco CallManager Administration displays view-only software component version information for any Cisco CallManager server, lists servers in the cluster with out-of-sync software components, and displays latest installed component version information across all Cisco CallManager servers in the cluster.

Use the following procedure to display version information for system software components.

Procedure

Step 1 Choose Help > Component Versions.

Step 2 From the Servers list, choose a server to display component version information for that server.

The information that displays includes the name of the component, the version number of the component, and the installation ID of the program that installed the component. The list will vary, depending on which components are currently installed on that server.

Step 3 Click Out of Sync to locate any system components that are installed on Cisco CallManager servers in the cluster that do not match the latest component version that is installed in the cluster.

Step 4 Click Latest Installed Version to list the most recent (highest numbered) installed version of each system component across all servers in the cluster.