Guest

Cisco Unified Communications Manager (CallManager)

Release Notes for Cisco CallManager Release 3.0(3b)

 Feedback

Table Of Contents

Release Notes for Cisco CallManager Release 3.0(3b)

Contents

Introduction

System Requirements

New and Changed Information

Maintenance Release 3.0(3b)

Maintenance Release 3.0(3)

Maintenance Release 3.0(2d)

New Hardware and Software Features in Release 3.0

Distributed Call Processing

Digit Analysis Replication

Multiple Line Appearance

Route Lists and Route Groups

Address Assignments (Route Pattern)

Number Transformations

Data Driven Dial Plan

Dial Plan Report

Select Ringing State for a Phone Device

Disable Ring Per Line

Database Layer/Replication

Device Reset Control

Device Recovery

Intra-Cluster Distributed Cisco CallManager Feature Transparency

Inter-Cluster Distributed Cisco CallManager Feature Transparency

Distributed Cisco CallManager Scalability

Cisco CallManager Redundancy on the Cisco ICS 7750

Digit Analysis Multi-Tenant

Digit Analysis Multi-Location

Digit Analysis Toll Restriction

MGCP Support for VG200

MGCP Device Recovery

Cisco IP Phone 7960 Support

Comfort Noise

IP Voice Streaming Application

Services Management

Global Directory User Pages

Empty Terminal Capability Set

CDR Modifications

Hold Feature Modifications

E-911 Support

VG200 Hook Flash Transfer

AMIS-A Support

Bulk Administration Tool (BAT)

DtSilenceFlag Service Parameter

Modems and Faxes

End User Interface

Important Notes

Resolved Caveats

Resolved Caveats - Release 3.0(3b)

Resolved Caveats - Release 3.0(3)

Resolved Caveats - Release 3.0(2d)

Open Caveats

Open Caveats for Cisco CallManager Release 3.0(3b)

Troubleshooting

Documentation Updates

New Service Parameters

Configuring the Microsoft Telnet Daemon for Bridged Telnet

Server Name Change

Running Show Tech

Changes

Default Value Changed for SdlTraceTotalNumFiles Service Parameter

Omissions

Cisco CallManager Service Parameters

Cisco TFTP Service Parameters

Cisco Messaging Interface Service Parameters

Cisco IP Voice Media Streaming Service Parameters

Cisco Enterprise Service Parameters

Errors

Incorrect Name of MwiSearchSpace Service Parameter

Incorrect Definition for HoldType and ToneOnHoldTime

Service and Support

Obtaining Documentation

World Wide Web

Documentation CD-ROM

Ordering Documentation

Obtaining Technical Assistance

Cisco Connection Online

Technical Assistance Center

Documentation Feedback


Release Notes for Cisco CallManager Release 3.0(3b)


October 17, 2000

These release notes describe the new features and caveats for Cisco CallManager Release 3.0(3b). Use these release notes in conjunction with the Installing Cisco CallManager Release 3.0 on the Cisco Media Convergence Server document, located on Cisco Connection Online (CCO), and the Cisco Documentation CD-ROM. The Installing Cisco CallManager Release 3.0 on the Cisco Media Convergence Server document is also packaged with your CDs or convergence server.

The latest software upgrades and release notes for Cisco CallManager 3.0(3b) are available on Cisco Connection Online (CCO) at:

http://www.cisco.com/public/sw-center/internet/callmgr/callmgr.html

Contents

These release notes discuss the following topics:

Introduction

System Requirements

New and Changed Information

Important Notes

Resolved Caveats

Open Caveats

Troubleshooting

Documentation Updates

Service and Support

Obtaining Documentation

Obtaining Technical Assistance

Introduction

Cisco CallManager is a network business communication system providing high-quality telephony over IP networks. Cisco CallManager enables the conversion of conventional, proprietary circuit-switched PBXs to multi-service, open LAN systems.

System Requirements

Cisco CallManager Release 3.0 must be installed and configured on a Cisco Media Convergence Server. For system hardware component information and system requirements, refer to Installing Cisco CallManager Release 3.0 on the Cisco Media Convergence Server.

New and Changed Information

Maintenance Release 3.0(3b)

Cisco CallManager Release 3.0(3b) is a maintenance release that resolves the SQL password problem (CSCds32253) and addresses other high-priority caveats. No new features have been added. Refer to the "Resolved Caveats" section for more information.

Maintenance Release 3.0(3)

Cisco CallManager Release 3.0(3) is a maintenance release. No new features have been added. Refer to the "Resolved Caveats" section on page 17 for more information.

Maintenance Release 3.0(2d)

Cisco CallManager Release 3.0(2d) is a maintenance release that addresses Cisco Media Convergence Server installation issues and resolves other high-priority Caveats. No new features have been added. Refer to the "Resolved Caveats" section for more information.

New Hardware and Software Features in Release 3.0

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

Distributed Call Processing

Cisco CallManager (Release 3.0 and later) provides the capability for distributed call processing. With this feature, you can distribute the call processing load of your system across multiple Cisco CallManagers in a cluster. This feature allows for redundancy, feature transparency, and scalability in a distributed environment.

To support this functionality, a new distributed, replicated database layer has been added to the Cisco CallManager system. This layer allows for the transparent replication of configuration information across the coordinating Cisco CallManagers. The layer manages database consistency and recoverability. Configuration is simplified through a single web interface to the database for the entire system.

Digit Analysis Replication

Digit analysis is the process used by Cisco CallManager to collect, parse, and translate dialed numbers to destination device IP addresses. In Cisco CallManager Release 3.0 and later, the digit analysis function is distributed across all Cisco CallManager servers in a cluster. This distribution allows scalability, load balancing, and redundancy across the cluster.

Multiple Line Appearance

Cisco CallManager supports distributed multiple line appearance which allows multiple phones attached to multiple Cisco CallManagers to share one directory number (DN).

Route Lists and Route Groups

Release 3.0 introduces multiple Cisco CallManager nodes in a system. Access devices (gateways) may be registered in any of the nodes of the system, but must still be reachable using the configured Route Plan. Route Lists (which were called Route Points in Cisco CallManager Release 2.4 and earlier) and Route Groups are configured in the same manner as in Cisco CallManager Release 2.4 and earlier, with the same associations.

Address Assignments (Route Pattern)

This feature allows addresses of devices and virtual endpoints to be specified using a format that allows easy assignment of a range of matching values. This allows ranges of addresses to be easily routed or blocked. New to Release 3.0 is the ability to associate a route pattern to a device through partitions and calling search spaces.

Number Transformations

This new feature allows both called and calling numbers to be modified by truncation, replacement of individual digits, discarding named sub-strings (called number only), or by prepending or appending digits before digit analysis.

Data Driven Dial Plan

The new Dial Plan Wizard enables you to create a dial plan quickly and easily. Also, pre-configured, pre-tested, country-specific dial plans may be created and substituted for the NANP files.

Dial Plan Report

A new Dial Plan Report allows you to see the dial plan configuration at a glance. For each route partition, it lists the call park numbers, call pickup numbers, and conference numbers associated with the partition. For each route pattern, it shows the usage, route list, route group, device, and port numbers associated with the route pattern.Call Pickup and Group Call Pickup

Two types of call pickup can be configured with Cisco CallManager Release 3.0:

Call Pickup allows users to pick up incoming calls within their own group. The appropriate call pickup group number is dialed automatically when a user activates this feature.

Group Call Pickup allows users to pick up incoming calls within their own group or in other groups. Users must dial the appropriate call pickup group number when using this feature.

Select Ringing State for a Phone Device

This new feature allows ringing to be either enabled or disabled on any Cisco IP phone in the database. If ringing is enabled, an incoming call is presented on the phone through the display and/or lights as appropriate for that particular device, and by ringing the phone. If ringing is disabled, an incoming call is presented on the phone through the display and/or lights as appropriate for that particular device, but the phone does not ring audibly.

Disable Ring Per Line

If a DN appears on multiple phones, the database can be set to control which phone will ring or which will just flash, indicating that the phone is ringing, on a phone-by-phone basis.

Database Layer/Replication

The database layer provides an abstraction layer between Cisco CallManager and supporting applications. The abstraction layer provides for single-point system configuration while hiding automated, underlying data store replication.

Device Reset Control

This release of Cisco CallManager significantly reduces the number of database changes that require a Cisco CallManager restart in order to take effect.

Device Recovery

This section applies to Cisco CallManager through Media Gateway Control Protocol (MGCP), as well as Cisco CallManager to Cisco CallManager connections. Each Cisco CallManager device uses the steps in the following list to connect or reconnect to Cisco CallManagers:

A configuration component provides a list of Cisco CallManagers for the device to use. The maximum number of Cisco CallManagers on the redundancy list is three.

A TCP connection to two Cisco CallManagers in the list is maintained. Keep-alive messages are sent to both the active and the standby Cisco CallManager.

If the active Cisco CallManager fails, an IP phone to IP phone call stays active if both phones are on the same Cisco CallManager. If the two IP phones are on different Cisco CallManagers, the call is dropped. IP phone to a gateway calls are also dropped regardless of which Cisco CallManagers the devices are registered. As soon as the IP phone to IP phone call ends, the phones register with their standby Cisco CallManager. This backup is only temporary, until the primary Cisco CallManager is restored.

When keep-alive messages fail to the active Cisco CallManager, the device attempts to register with the standby Cisco CallManager. The device attempts to keep two TCP connections open and always tries to re-connect to the highest priority, available Cisco CallManager.

If a registered device is not registered with the primary, available Cisco CallManager, and no calls are active, the device follows the list starting with the first Cisco CallManager on the list and attempts to re-make a TCP connection. Upon a successful connection, the device de-registers with the current active Cisco CallManager and registers with the new Cisco CallManager.

Intra-Cluster Distributed Cisco CallManager Feature Transparency

The intra-cluster feature transparency provided in Cisco CallManager Release 3.0 allows features such as device display management, device lamp management, media management, call hold and transfer capabilities, call park and pickup capabilities, distributed dial plan, and shared route plan (in the form of partitions and calling search spaces) to be configured and shared across all Cisco CallManagers within a cluster.


Note MTP is not required for intra-cluster communication.

Inter-Cluster Distributed Cisco CallManager Feature Transparency

Clusters of Cisco CallManagers interconnect using H.323 protocol. A given cluster views another cluster as another H.323 device. When configuring one cluster to talk to another, the Configuration Database has an H.225 device configured that points to one of the Cisco CallManagers in the remote cluster. The Dial Plan structure associates the remote cluster's E.164 address range to the H.225 device and signals the remote cluster just as it would an H.323 gateway. New to Release 3.0 are minor bug fixes and support for intercluster transfer, hold, and conferencing through the H.323 empty capabilities set.

Distributed Cisco CallManager Scalability

Beginning with Release 3.0, multiple Cisco CallManagers can be supported per configuration database. This feature allows load distribution for registered devices, call processing, and other functions across all Cisco CallManager servers in a cluster.

Six Cisco CallManagers can reside in a Cisco CallManager cluster. The maximum number of users in a Cisco CallManager cluster is 10,000. A single Cisco CallManager can handle 2,500 phones. When multiple Cisco CallManagers are present in a cluster, the number of IP phones assigned to each Cisco CallManager in a normal state must be such that they can absorb the IP phones from a failed Cisco CallManager so that 2,500 phones on any Cisco CallManager is not exceeded.


Note For redundancy purposes, you could have a Cisco CallManager that only serves as a backup Cisco CallManager, and during normal operations, would have no registered phones. You can also install the Publisher database and TFTP servers on stand-alone platforms if desired.

For the most current information about Cisco IP telephony system design guidelines, refer to the Voice Product Documentation page on Cisco Connection Online, located at http://www.cisco.com/univercd/cc/td/doc/product/voice/

Cisco CallManager Redundancy on the Cisco ICS 7750

Cisco CallManager redundancy is handled differently on the Cisco ICS 7750 than it is in a clustered environment. Only one instance of Cisco CallManager is active at any time on the Cisco ICS 7750. When a redundant System Processing Engine (SPE) runs a secondary instance of Cisco CallManager, the secondary instance is never active unless the primary Cisco CallManager fails. If a failover occurs, the secondary Cisco CallManager becomes active and takes over all call processing and Cisco CallManager database functions. Since only one instance of Cisco CallManager is active on the Cisco ICS 7750, load-balancing is not available, and each Cisco ICS 7750 must be administered separately. For more information about implementing and configuring Cisco CallManager on the Cisco ICS 7750, please refer to the Cisco ICS 7750 documentation.


Note Cisco CallManager clusters are not supported on the Cisco ICS 7750.

Digit Analysis Multi-Tenant

Through partitions, the Cisco CallManager is able to support multiple instances of the same DN at a single site which are treated as independently reachable DNs. Using translation patterns, inbound calls to different direct inward dialing (DID) numbers with common subscriber line identifiers (extensions) can be configured.

Digit Analysis Multi-Location

The Cisco CallManager is able to support routing for devices that are in different geographical regions, of which belong to different area codes within the North American Numbering Plan (NANP). You can configure your dial plan in order to bypass the public network when feasible, and also to fall back to long distance routes when WAN or intranet is unavailable.

Digit Analysis Toll Restriction

Cisco CallManager is able to allow or prohibit types of calls based on the class of the individual device or DN.

MGCP Support for VG200

Cisco CallManager is more tightly integrated with the VG200 series of gateways through Media Gateway Control Protocol (MGCP). MGCP is used to provide inter-working between Cisco CallManager and VG200 gateways. The Cisco CallManager is able to control analog interfaces (FXS and FXO) directly.

MGCP Listen Port

MGCP messages are transmitted over TCP. The MGCP listen port represents the Cisco CallManager TCP listen port. The default for this port should be set to 2427.

MGCP Keep-alive Port

The VG200 gateways use TCP as a keep-alive mechanism with Cisco CallManagers. Each gateway can be configured with one active Cisco CallManager and up to two backup Cisco CallManagers. One TCP keep-alive connection exists between a gateway and an active or backup Cisco CallManager. The MGCP keep-alive port represents the Cisco CallManager TCP server port used for this keep-alive mechanism. The default for this port should be set to 2428.

MGCP Device Recovery

Cisco CallManager health monitoring is the responsibility of the gateway. Inter Cisco CallManager and gateway keep-alives track the health condition of the controlling Cisco CallManager. Once the gateway has detected an outage of the primary Cisco CallManager, it rehomes to the next highest priority Cisco CallManager.

Cisco IP Phone 7960 Support

The Cisco IP Phone 7960 uses the Skinny Station protocol with additional messages as required to support the new functionality of the Cisco IP Phone 7960. The Cisco CallManager controls the display on the Cisco IP Phone 7960 indirectly, by providing call and state information to the phone. The phone display processing itself is stateless. The Cisco IP Phone 7960 supports the G.711 u-law and a-law and the G.729, G.729B Codecs.

Comfort Noise

The Cisco IP Phone 7960 supports comfort noise. When Voice Activity Detection (VAD) is enabled, the Cisco IP Phone 7960 generates a low level white noise hiss to simulate the background circuit noise users experience on non-IP connections. Generated comfort noise is only heard on the handset of the station generating the noise; it is not transmitted to the station at the other end of the call. If VAD is disabled, the Cisco IP Phone 7960 provides a continuously streaming, end-to-end connection. VAD is enabled by default.


Caution If VAD is disabled on a network that exhibits a significant amount of jitter (for example, greater than 100 milliseconds per second), latency becomes noticeable to the user in the forms of delay and packet loss. Also, if the codec clocks are out of sync among the devices participating in the call, latency increases for the duration of the call. For example, if the codec clock at the transmitting end is 100 parts per million faster than the codec clock at the receiving end, latency increases to one-half second over the course of a one hour long connection (at 8 kHz).

The comfort noise level is determined either by information contained in Silence Information Description (SID) frames or by calculations performed on previous information packets. If a call is made from one Cisco IP Phone 7960 to another Cisco IP Phone 7960, the transmitting device sends SID frames that enable the comfort noise generator on the receiving device to generate the proper level of comfort noise. If a call is made between a Cisco IP Phone 7960 and a device that does not send SID frames, the Cisco IP Phone 7960 calculates and generates the proper comfort noise level based on the background noise of previous information packets.

IP Voice Streaming Application

The IP Voice Streaming Application (Media Application) combines the Conference Bridge and the Media Termination Point (MTP) components that were in the previous versions of the Cisco CallManager. The Media Application consists of two parts: a Windows NT service and Windows NT kernel mode driver. The Windows NT service is responsible for registering with the Cisco CallManager and handling Device Recovery. The kernel driver processes and controls the voice data packets.

Services Management

The list of software processing services for the Cisco IP Telephony Solutions for the Enterprise is Cisco CallManager, TFTP Server, Cisco Messaging Interface (CMI), and IP Streaming Application (replaces the previously separate applications for Conference Bridge and MTP). Each of the processing elements are managed consistently using well-known Windows NT system administration tools.

Service Parameters

The behavior of system services is controlled by parametric value adjustment. In Cisco CallManager Release 3.0, the interface to these settings has been consolidated into two Cisco CallManager Administration web pages. These parameters can now be obtained from the database. In earlier versions of Cisco CallManager, these settings were adjusted in .ini files or the Registry, or presented in application configuration dialogs.

Enterprise Parameters

This feature provides system-wide parametric value adjustment for all services within the enterprise.

Global Directory User Pages

In Release 3.0, an embedded Directory (instead of the relational database) is used to store user data (for example, information such as name and DN). The information in this directory is accessed by a variety of applications. This release provides password protected user access to speed dial and Call Forward All numbers.

Empty Terminal Capability Set

This feature allows the start and stop (re-direct) of streaming on an H.323 device without the use of MTP. This allows the use of supplementary services without losing the call or voice stream.

Empty Capabilities set is a technique used in H.323v2 to allow the Cisco CallManager to instruct an H.323 gateway to transfer a call to a new endpoint in mid-call. This is typically done upon no answer or if the IP phone user presses the transfer button. Prior to this capability, it was necessary to send H.323 calls to an intermediate Media Termination Point (MTP) application before connecting to the IP phone.


Note The minimum IOS release required for Empty Terminal Capability set is 12.1(3)T.

CDR Modifications

Even when there are two or more Cisco CallManagers in a cluster, CDR records are written to a common database store. There may be more than one record logged per call.

Hold Feature Modifications

Table 1 contains the hold feature modifications with Release 3.0:

Table 1 Hold Feature Modifications 

Scenarios
Initial State
(1st call ----- 2nd call)
Line Button Pressed
Final State
(1st call ----- 2nd call)

1

OnHook ----- OnHook

Pressed

Dial Tone ----- OnHook

2

Connected ----- OnHook

Pressed

Hold ----- Dial Tone

3

Hold ----- OnHook

Pressed

Connected ----- OnHook

4

Connected ----- Hold

Pressed

Hold ----- Connected

5

Hold ----- Hold

Pressed

Connected ----- Hold

6

Ring Out/Dial Tone ----- OnHook

Pressed

OnHook ----- OnHook

7

Ring Out/Dial Tone ----- Hold

Pressed

OnHook ----- Connected

8

Ring In ----- OnHook

Pressed

Connected ----- OnHook

9

Ring In ----- Hold

Pressed

Connected ----- Hold

10

Ring In ----- Connected

Pressed

Connected ----- Hold

11

Connected ----- OnHook

Pressed (Another Line)

Hold ----- OnHook

12

Ring Out ----- OnHook

Pressed (Another Line)

OnHook ----- OnHook

13

Ring In ----- OnHook

Pressed (Another Line)

Ring In ----- OnHook

14

Connected ----- Hold

Pressed (Another Line)

Hold ----- Hold


E-911 Support

The Cisco CallManager supports delivering the ANI (Automatic Number Identification) through an H.323 interface to the PSTN using two methods: PRI/ISDN trunks and third-party CAMA (Centralized Automated Message Accounting) gateways.

VG200 Hook Flash Transfer

Cisco CallManager Release 3.0 provides the ability to initiate a hook-flash blind transfer from POTS devices connected to any VG200 FXS port that is controlled by Cisco CallManager through MGCP.

AMIS-A Support

AMIS-A (Audio Messaging Interface Specification-Analog) support allows VoIP devices to exchange AMIS-A Dual Tone Multi-Frequency (DTMF) tones (A, B, C, and D) with the Cisco CallManager, in an out of band signal. The purpose of AMIS-A support is to facilitate Cisco uOne voice mail message exchange and feature transparency with legacy voice mail systems.

AMIS-A DTMF tones (A, B, C, and D) are transported in two different schemes. On the IP side, the tones are detected and generated in an out of band signaling format, whereas on the destination side of the gateways, the tones are detected and generated inband along with the voice path.

The main role of Cisco CallManager is to make sure that DTMF digits received from the sending device are correctly mapped to the corresponding signal format (or API) of the terminating device.

The following existing APIs are impacted to include the AMIS-A DTMF tones (A, B, C, and D):

Skinny Station Protocol—StationKeyPadButton and StationOutputKeyPadButton

Skinny Gateway Protocol—GatewayToDeviceReportDigit, DeviceToGatewayPlayTone, and Q.931 and Information message (for analog access gateway).

H323 Protocol—H245 User Input Indication (h245-signal)

MGCP Protocol—NTFY and RQNT

Bulk Administration Tool (BAT)

The Bulk Administration Tool (BAT) is a plug-in application to the Cisco CallManager. BAT enables you to add up to 10,000 phones and users to the Cisco CallManager application. Using BAT, you can also perform bulk modifications to phones and delete several phones at one time. Launch BAT from the Cisco CallManager Administration main window by selecting Application and click on BAT. For more information, refer to the Configuring the Bulk Administration Tool (BAT) document (OL-4086-01).

DtSilenceFlag Service Parameter

The DtSilenceFlag service parameter controls whether or not silence is sent while a caller waits for the phone to be answered at the other end. By default, the DtSilenceFlag service parameter is set to False (disabled). When this parameter is set to False, the audio stream is sent on call proceeding instead of waiting for a connect from the other end. When this parameter is set to True, silence is sent until a connect is received from the phone at the other end.

There is, however, one side effect that occurs when the DtSilenceFlag parameter is set to 0 (disabled). When the DtSilenceFlag parameter is disabled and you are calling an analog phone, you may hear loopback (echo) of your audio until the phone on the other end is answered.

To eliminate this echo, you can manually add the DtSilenceFlag service parameter to the list of CallManager service parameters for each Cisco CallManager and set its value to T (enabled). The DtSilenceFlag service parameter does not automatically appear in the list of Cisco CallManager service parameters.


Caution Setting the DtSilenceFlag service parameter to T can result in one-way audio on 911 calls depending on the local carrier's configuration of the Central Office switch. The problem will only occur if the 911 switch fails to send a connect. If the 911 switch fails to send a connect, the calling phone continues to send silence, and the audio stream from the calling phone is never sent.

Therefore, it is strongly recommended that you schedule a test 911 call with your 911 service provider to verify that this problem does not occur. The test scenario should include the following steps:

1. Schedule a test call with your 911 service provider during off-peak hours.
2. Make sure that the test call will be routed over a Cisco Access Digital Trunk Gateway or a Catalyst 6000 T1/E1 8 Port Voice Service Module.
3. Enable the DtSilenceFlag parameter.
4. Make the 911 call.
5. If the 911 operator can hear you, the test passed, and you can leave the DtSilence setting enabled. If not, disable it immediately.

Perform the following steps only if you wish to enable the DtSilenceFlag service parameter:


Step 1 Open Cisco CallManager Administration.

Step 2 Select Service > Service Parameters

Step 3 Select Cisco CallManager from the list of Configured Services.

Step 4 Type DtSilenceFlag in the Param field. The service parameters are case-sensitive, so it must be typed exactly as it appears.

Step 5 Choose Boolean from the Type drop-down list.

Step 6 Choose T from the Value drop-down list to set it to True (enabled).

Step 7 Click Update.

The DtSilenceFlag service parameter is now added to the list of service parameters and its value is set to T (enabled).


Modems and Faxes

The following list contains the modems and faxes that are either supported or not in Release 3.0:

g.723.1 fax between as/at/dt gateways = not supported

g.711 fax between as/at/dt gateways = not supported

g.729 fax-relay between IOS gateways = supported

g.711 fax-relay between IOS gateways = supported

g.729 fax-relay between cat6k gateways = supported

g.711 fax passthrough between cat6k gateways = supported

g.711 modem passthrough between cat6k gateways = supported

End User Interface

The end user interface for Cisco CallManager Release 3.0 database administration has changed. The new interface provides a system page divided into more precise categories, more links from one page to another, and faster search engines for devices (phones, gateways, etc.).

The main menu of the Cisco CallManager Administration user interface consists of the following:

System

Route Plan

Service

Feature

Device

User

Application

Help

Some configuration screens contain data that are associated with a particular Cisco CallManager. A drop-down menu with all Cisco CallManager names is displayed. To see the data associated with a particular Cisco CallManager, choose the Cisco CallManager from the drop-down list. Data is displayed accordingly.

The following sections contain the grouping of the different menu categories for the Cisco CallManager Database Administration.

System

The System category includes any system-related configurations that set the system's behaviors and options. It includes the following configurations:

Server—Any machine that runs the Cisco CallManager and its application needs to be added in the Server Configuration page. The installation program automatically adds an entry on this page for the machine on which the Cisco CallManager is installed. A unique DNS host name or IP address is needed for each server.

Cisco CallManager—Allows you to define Cisco CallManagers in the system. Each server defined in the system (under Server Configuration) can have only one Cisco CallManager running on it. Therefore, you must define the server on which the Cisco CallManager resides before defining the Cisco CallManager. In every system, there must be one primary Cisco CallManager. You can also configure the auto-registration and port settings for the Cisco CallManager.

Cisco CallManager Group—This configuration page allows you to define groups of Cisco CallManagers. Only one Cisco CallManager Group in the system can be the default Cisco CallManager used by Trivial File Transfer Protocol (TFTP). A Cisco CallManager Group can have up to three Cisco CallManagers in a group.

Date/Time Group—The Date/Time Group configuration page allows you to add, update and delete Date/Time groups. Each group contains time zone, and date and time format preferences. There should be at least one Date/Time group in the system.

Device Defaults—For each Cisco CallManager, this is a load ID, keypad template, and device pool associated with each model type. When a device is created in the system, the system can automatically identify the appropriate load ID (if applicable), keypad template (if applicable), and device pool for the device based on the Cisco CallManager of which it is registered. This configuration page can be viewed based on each Cisco CallManager.

Region—The Regions feature in Data Administration can be used by Cisco CallManager to automatically select the type of call compression used between devices that are assigned to different (or the same) regions. The configuration pages allow you to define a region and set the type of compression within the region and between the new region and all existing regions.

Device Pool—All devices in the Cisco CallManager system associate with a device pool. A device pool contains the region, Date/Time group, Cisco CallManager Group, and calling search space for auto-registration. You can create different device pools for devices in different regions, time zones for each Cisco CallManager Group, and calling search space combinations.

Enterprise Parameters—This configuration page allows you to set parameter values for firmware load of all device types, LDAP settings, and Cisco IP Phone 7960-related settings in the system.

Location—This configuration page allows you to define logical locations in the system and define bandwidth settings for the location.

Route Plan

This category allows you to configure route plans, partitions, and so on. It includes the following menu items:

Partition—A partition is a collection of route patterns or call pickup group numbers. You can create route partitions and view a list of patterns and numbers associated with a specific partition.

Calling Search Space—A Calling Search Space contains a list of partitions. In each partition, there is a list of DNs that a device can call. When a device is assigned to a calling search space, this device can call any number which is contained in its calling search space partition list. The ordering of partitions in a calling search space can be modified.

Route Filter—A route filter allows you to control which dial patterns are routed or blocked. The tags associated with the route filters can only be used by North American Numbering Plan (NANP) patterns. Modification to the database is needed if other numbering plans need to be supported.

Route Group—A route group allows you to order a list of gateways and ports for outgoing trunk preference. Devices that can belong to a route group are: Analog Access ports, Digital Access PRI, Digital Access T1, and H.323 (network side) devices. All devices in a route group must have the same route pattern.

Route List—A route list allows you to specify the order in which route groups are used.

Route Pattern—You define the route patterns for the Cisco CallManager system. The Cisco CallManager uses the route patterns to route internal and outgoing calls.

Translation Pattern—You define the translation patterns for the Cisco CallManager system.

External Route Plan Wizard—The route plan wizard guides you through a number of configuration pages to configure the route plan. It creates route plans for NANP patterns only.

Route Plan Report—Lists all the call park, call pickup, conference, route pattern, and translation patterns defined in the system. You select the pattern or DN and the corresponding configuration page is shown. Since this page can potentially show a long list of records, we recommend viewing only 50 records at a time. You can choose to view all items by clicking on the All button.

Service

The Service category includes any applications that are add-on components, such as the following:

Cisco Messaging Interface—Allows you to configure trace and command line parameter settings for any server, and is most commonly used to interface via SMDI to a third-party voice mail system.

Cisco TFTP—This configuration page allows you to configure Trivial File Transfer Protocol (TFTP) service parameters. The TFTP service must be installed on a server defined in the Server Configuration page.

Conference Bridge—Allows you to define software and hardware conference bridge solutions, as well as Meet-Me numbers/patterns in the system. The initial page shows the Conference Bridge Configuration page. To navigate to other conference bridge-related configuration pages, select the links in the upper right corner. To set up conference bridge, you must define either a conference bridge software or hardware type. The hardware type supports more capabilities than the software type.

Conference Bridge Parameters—Allows you to set the maximum number of users in one ad hoc conference, and the maximum number of users in one Meet-Me conference using Unicast for each Cisco CallManager. You must select the device pool, and the Cisco CallManager belonging to the selected device pool is shown on the item list.

Meet-Me Number/Pattern—Allows you to configure the Meet-Me numbers and ranges for conference bridge calls.


Note You cannot have both hardware and software conference bridge or MTP devices on the same Cisco CallManager. If both exist, the Cisco CallManager will disable the software version.

Media Termination Point—Allows you to configure the Media Termination Point (MTP) settings.

Service Parameters—The configuration page allows you to configure settings for the services installed in the system. By selecting a server in the item list, the configuration page shows all the services that are installed on the selected server. You can select a service of the selected server and configure the service parameter settings. A server must be defined in the Server Configuration page and the services must be installed from the Install Plugins page.

Trace—Allows you to configure trace settings for the services installed in the system. You can display all configured services that are installed on the selected server by selecting a server in the item list. You can select a service from the Configured Services drop-down list box and configure the trace settings for the selected service. A server must be defined in the Server Configuration page and the services must be installed from the Install Plugins page.

Transcoder—Allows you to configure transcoder devices.

Control Center—Allows you to stop and start any services on a selected server.

Feature

The Feature category contains configurations to add phone features and feature-related parameters to the system. It includes the following configurations:

Call Park—This configuration page allows you to specify call a park number or range in the system. Each partition has its own call park number/range.

Call Pickup—This configuration page allows you to specify a call pickup number or range in the system. Each partition has its own call pickup number or range.

Device

The Device category contains configuration pages to configure devices (phones, gateways, and so on.) for the Cisco CallManager. It includes the following configurations:

Add a New Device—This page replaces the Device Wizard in Release 2.4. You can add a gateway, MGCP gateway, phone, or Cisco uOne port from this configuration page. Based on the device type selected, the corresponding configuration page is displayed. Complete the information and click the Insert button to add the device.

Cisco uOne Port—The Cisco Unified Open Network Exchange (uOne) optional software, available as part of Cisco IP Telephony Solutions, provides voice messaging capability to users when they are unavailable to answer calls. This page enables administrators to add, update, and delete Cisco uOne ports in the Cisco CallManager database.

For more information about configuring Cisco CallManager with Cisco uOne, refer to uOne Installation and Configuration, Corporate Edition 4.1E for CallManager 3.0 (OL-0489-01) and other documenting and online help included Cisco uOne.

Gateway—The Release 2.4 Gateway configuration pages included limited devices only. In Release 3.0, the Gateway section of the user interface includes all gateways, including H.323 devices. Specific pages are used to configure different types of gateways. The overall structure of the Gateways user interface is similar to the new Phone interface.

Selecting Gateways—The method of selecting gateways (listing all gateways in a separate menu frame) from Release 2.4, has been replaced with a basic lookup function. The lookup allows you to search for gateways by the following categories: device name, description, DN, calling search space, or device pool. For each category, you can specify whether the content of the selected category begins with specific letters, contains specific letters, ends with specific letters, matches specific letters, contains no empty strings, or contains empty strings. The results are shown in a list of devices from which you can select.

Configuring Gateways—You can select a device from the list of devices that the lookup gives you, and click a link or button to show a detailed view of the device in a secondary window. Any information that can be modified is displayed with a form element so that it can be updated immediately. The only exceptions are the port, span, and trunk configuration details, which are not all shown at once. Instead, a summary of the ports is shown with links to edit the port details (for example, for an Analog Access device, a list of ports that have been configured and each port's type, Loop Start, POTS, and so on.). The actual look and feel of the Gateway configuration pages are similar to what is shown for Phones and Users.

Adding Gateways—A New Gateway device option is included in the menu for Gateways. Clicking the link takes you to the Add a New Gateway page, where you can add a new gateway.

Deleting Gateways—The interface provides a toolbar button in the configuration page for deleting the current device. A confirmation prompt asks if you are sure, and runs the delete script if you respond with yes. If you respond with no, you are returned to the configuration page and no changes are made.

MGCP—Due to the complexity of the MGCP gateways, the MGCP configuration is separated from the other gateway configurations.

Phone—In Release 3.0, the phone list is limited to devices that can be classed appropriately as phones; that is, end user terminal devices. This includes the existing Cisco Phones and the new Cisco IP Phone 7960. Also included in this category is the H.323 Client (for example, NetMeeting), which is used as a phone.

Phone Button Template—Allows you to select a phone button template based on an existing phone template, or to create a new button layout.

User

The User category contains configuration pages that allow you to display and maintain information about users on the network. This category includes the following configurations:

Add a New User—Allows you to complete information for specific users and associate devices with those users.

Global Directory—Allows you to use a basic or advanced search to locate users. The Global Directory contains every user within a Cisco CallManager directory. The Cisco CallManager directory is a Lightweight Directory Access Protocol (LDAP) directory that imports device and extension information from the database. Its primary purpose is to maintain the associations of devices with users.

Application

All plug-in applications are listed under the Application menu. Once the application is installed, the application name is shown under the application menu.

Help

The Help menu includes the following categories: Contents and Index, For this Page, and About Cisco CallManager.

Contents and Index—This window shows an online documentation page. The documentation displayed here is not context-sensitive. It displays the top-level topics of the Cisco CallManager Administration Guide.

For this Page (context-sensitive help)—Context sensitive online documentation is provided for all the Cisco CallManager Administration Guide pages. When you click on this menu item, the documentation related to the selected configuration page is shown in a separate window.

About Cisco CallManager—This menu displays general information about Cisco CallManager. When the Details button is clicked, a list box shows the Cisco CallManager System version number (which is the Installation version), Cisco CallManager Administration version number, database information, and database dynamic link library (DLL) version numbers.

Important Notes

You should perform regular system backups as described in the section "Performing Backup and Restore Procedures," of the Installing Cisco CallManager Release 3.0 on the Cisco Media Convergence Server document.

Resolved Caveats

Resolved Caveats - Release 3.0(3b)

Table 2 lists and describes Caveats that were resolved in Cisco CallManager Release 3.0(3b).

Table 2 Cisco CallManager Release 3.0(3b) Resolved Caveats 

DDTS Number
Summary
Explanation

CSCds32253

If you install the publisher, then change the Administrator password for SQL Srv, installing further subscribers will fail.

After changing the password on the publisher (specifically the SQL Svc user), no further subscribers can be successfully added into the cluster.

CSCds29243

The Cisco IP Phone 7960 stops responding and only displays the text "Opening."

This problem can occur when all Cisco CallManagers in the phone's redundancy group list are unavailable. After attempting to connect to the Cisco CallManagers in its group list, the phone stops responding eventually.

CSCds21180

After Cisco CallManager failure, some phones require reboot to re-register.

A Cisco IP Phone 7960 that unregisters from all configured Cisco CallManagers after a Cisco CallManager failure may require rebooting to restore connectivity.

CSCdr95107

The Cisco IP Phone 7960 crashes when receiving malformed audio packets.

When connecting to Cisco uOne voice mail (where a G.729 connection is forced), Cisco uOne sends malformed G.729 packets, which cause the phone to crash and reboot.

CSCdr49092

The dialing plan script incorrectly blocks the n11 office code.

This problem will cause the calls to get a re-order tone if the dialer enters the office code as X11.


Resolved Caveats - Release 3.0(3)

Table 3 lists and describes Caveats that were resolved in Cisco CallManager Release 3.0(3).

Table 3 Cisco CallManager Release 3.0(3) Resolved Caveats 

DDTS Number
Summary
Explanation
Cisco CallManager

CSCds21424

Cisco CallManager terminated abnormally with memory corruption and a faulty alarm message.

An alarm message with an incorrect parameter caused memory corruption.

CSCds19482

CPU usage cycling 40% to 70% every 20 seconds.

CPU was tracking between about 70% and 40% in a regular cycle (20 seconds high; 20 seconds low). All the other Cisco CallManagers were below 10%. This event was caused by a Cisco IP Phone 7960 that was constantly requesting the same information because it missed a message.

CSCds18538

MessageWaitingOn or MessageWaitingOff string update causes runtime error in service parameters.

When the user attempts to assign a number to the MessageWaitingOn or MessageWaitingOff service parameters, a run time error line 74 is displayed.

CSCds17394

Cisco CallManager 100% CPU usage.

Cisco CallManager CPU usage went to near 100% and users experienced very slow response from CallManager.

CSCds11873

Cisco CallManager 3.0 does not send SMDI during transfer on busy to Octel 250.

Cisco Call Manager 3.0 does not send an SMDI link message to an Octel 250 when the Octel does an unsupervised transfer to a busy (or unregistered) station that forwards back into the Octel.

CSCds07855

Call pickup of blind transfer.

1. Phone A calls Phone B.

2. Phone B Answers call.

3. Phone B Transfer Button pressed, then Dials Phone C, then pressed Transfer button and hangs up phone.

4. Phone C rings.

5. Phone D tries to do a Call Pickup, fails, and puts itself On-Hook.

6. Phone A hears Re-Order and Phone C continues to ring.

7. Phone C is answered.

8. Connection completes between Phone A and Phone C.

Duplicate of CSCds09040 (call pickup groups are not working if transfer started the call to the pickup group number).

CSCds06332

Call forward is not working when multiple hops are down.

 

CSCds05118

Calls drop randomly on a 5300 when an error occurs.

Calls drop through a 7200 or 5300 gateway randomly. This is caused by a TCP error coming from a call which is disconnecting normally.

CSCds02656

Intercluster dead air —Zero bandwidth.

This occurs when there is an entry in the route list which is not responding. If bandwidth is used up, call is being routed to the secondary CM and then the call eventually times out after a long period of "dead air."

CSCds02623

Intercluster dead air—busy.

Cluster 09 Phone 99999 calls Cluster 04 Phone 43520. DN 43520 is offhook; DN 99999 gets dead air.

CSCds02309

Subscriber Dial Pattern Change needs Cisco CallManager stop/start.

The problem occurs because the Cisco CallManager software does not handle registration of more than 64 DNs/route patterns per route list.

CSCdr99090

Symbol phone calling out via gateway does not complete.

Symbol phone calling out via a 5300 to a PSTN number rings twice and then the symbol phone goes idle. Symbol phone calling out via a DT24+ to a PSTN number rings twice and then the symbol phone says call declined. If the PSTN number is forwarded directly to voice mail, (it doesn't ring), then the call completes and voice mail can be accessed

CSCdr97447

Call pickup groups stop working.

Call pickup groups seem to work OK for a while after they have been created or after the Cisco CallManager is restarted. However, after an undetermined period of time, they cease to function.

CSCdr84584

Cisco CallManager fails to cut-through voice-path after progress message.

Gateway used: AS5300. The gateway is handling the progress message correctly; on receiving progress msg, the conference is created and an H245 cap request is sent out to Cisco CallManager.

Cisco CallManager responds with status message: message not compatible with call state or message type non-existent or not implemented.

CSCdr80083 is a duplicate of this caveat.

CSCdr79073

DisplayIEDeliveryFlag=True causes no connect through T1 CAS.

Under Cisco CallManager Service Parameters, if DisplayIEDeliveryFlag=T for True, a call will not set up if routed to PBX via PRI then off PBX to other equipment via T1 CAS. The IP phone caller will get Fast Busy

With this flag set to T(rue), you would normally see the calling and called party name delivery in the SETUP and CONNECT messages.

CSCdr70073

Cisco CallManager server reboots forever if you do not log in.

Several Cisco CallManager servers would reboot forever if you did not log in. This problem began after upgrading to Release 3.0(1) from an earlier version of Release 3.0. The problem only occurs when the Publisher cannot contact the Subscriber. Approximately 65 seconds after the message is displayed on the screen asking the user to press Control-Alt-Delete to logon, the Server reboots.

CSCdr57950

Ringing tone on the phone does not correspond with the call state.

 

CSCdr57966

Request for tone on hold.

A ToneOnHold service parameter has been added for Cisco CallManager.

CSCdr57963

No hold tone when a user places a particular call on hold.

No hold tone when releasing a call from hold if the other party has also put the call on hold.

CSCdr58885

Illegal sequence of DT 24+ for releasing the line.

When DT 24+ disconnects the line, it always takes 30 seconds (thus, until T305 timer is expired) to release the B-channel completely.

CSCdr57872

DT 24+ ignores progress indicator No.8 if disconnect message is received.

DT24+ ignores the DISCONNECT message which contains progress indicator No. 8, "in-band information or appropriate pattern now available." It seems that DT24+ considers only the DISCONNECT message. The DT24+ releases the call.

CSCdr57383

Line lamp does not blink at different rates on multiple line phones.

Have phone with same line appearance on multiple phones, A, B and C. Call comes in and A answers call. A places call on hold. All occurrences of this line appear the same on all phones. No differentiation of phone that actually placed call on hold.

CSCdr57362

No hold tone while call is parked.

Receive a call. Park the call. Calling party hears nothing while parked.

CSCdr57272

OutofBandwidthText message will not display on a Cisco IP Phone 7960.

The "Not Enough Bandwidth" message that displays on a Cisco IP Phone when calling between locations that are out of bandwidth will not display on a Cisco IP Phone 7960. This text displays correctly on the Cisco IP Phone 12 SP and other Cisco IP Phones.

CSCdr56276

Call waiting times out after 22 seconds.

Phone A calls phone C. Call is established A and C are conversing.

Phone B calls phone C. Phone C hears call waiting beep and phone B hears ringback.

Phone C does not immediately switch to the new call, so after ~22 seconds, phone B gets reorder.

All phones are setup for no call forwarding of any kind.

In New Zealand, the phone company does not timeout calls until 3 minutes has elapsed. If you call someone and they do not answer their phone will ring for 3 minutes or until the originator hangs up, whichever occurs first. The customer thinks call waiting should behave the same way. The customer wants to know if there is a timer they can configure.

A new system parameter called CallWaitingTimeout was added. The default value for this parameter, if not present, is 180 seconds (3 minutes).

CSCdr55758

45-second delay to reorder on invalid # intercluster call, 2 Cisco CallManagers per cluster.

There are a number of problems where calls have no progress and after approximately 45 seconds revert to re-order tone.

This problem is related to defining intercluster H.323 from source cluster, to primary and secondary Cisco CallManagers in another cluster using route groups with both primary and secondary defined.

CSCdr55189

Cisco IP Phone 7960 takes 7 minutes to work if the pvid of the phone is not equal to the pvid of the Cisco CallManager.

When a Cisco  IP Phone 7960 is attached to a Cisco Catalyst 6000 switch, if the pvid on the switch port is changed, the phone may take up to 7 minutes to reconfigure and connect to the Cisco CallManager.

CSCdr52811

No call progress when calling a busy user over DE 30+.

This problem occurs when placing a call out a DE 30+, and the called user is busy. The Cisco IP Phone displays date and time instead of user busy tone.

CSCdr39846

Cisco CallManager not interpreting Screening Indicator correctly.

Cisco IP phone prefixes a random or garbage character to the number display on the LCD screen. This occurs when a call is placed from the PSTN to an IP phone, with the following configuration: PSTN—>AS5300—>
Cisco CallManager—>Cisco IP Phone.

The AS5300 uses ISDN PRI signalling to set up the call.

CSCdr14562

Clicking too rapidly on the Update button in the Cisco CallManager Administration Configuration screen can cause the browser to stop responding.

The browser seems to be connecting to the server, but it remains in a wait state from which it can not recover. The browser does not respond to any user input. The status area at the bottom of the window displays the message Validating....

CSCdp97606

When a port on a Cisco Unicast Conference Bridge is conferenced back to itself, a feedback loop is created in the conference bridge and all participants will experience audio feedback.

The fix prevents a Meet Me conference participant from transferring the call to the same Meet Me conference number, thus preventing the feedback problem from occurring. Now when the Meet Me conference participant attempts to transfer the call to the same Meet Me conference number, the transfer button will be ignored by Cisco CallManager.

DC Directory

CSCdp60775

DC Directory exits with no warning or alert.

The Cisco CallManager User pages are not accessible or the user administration pages return errors when accessed.

Under extreme conditions such as low memory, or network problems, it is possible that the DCD Directory Server service may stop running. This will cause the web pages mentioned above to function incorrectly or not at all.

CSCdp98131

DC Directory server fails on restart during avvid_cfg.

The problem was due to Windows not cleaning up the shared memory resources quickly enough. Instead of stooping and restarting DCD, avvid_cfg now sleeps for 65 seconds to allow MetaLink sufficient time to discover the DC Directory admin node.

CSCdr05501

Cisco User Preferences upgrade removed DC Directory service.

The Cisco User Preferences Pages upgrade installation ran with no apparent problems. After the install completed, the machine was rebooted as instructed. When the system came back up, there was no DC Directory service present.

CSCdr20006

Incorrect search results are displayed in the User Directory search.

The problem occurs when:

1. A search is executed from either the basic or advanced search pages.

2. The browser Back button is clicked.

3. A new search is entered and executed.

After the above steps are performed, the results of the first search are displayed as the results for the second search, which is incorrect.

CSCdr32527

After adding a device, you must close the browser to display the updated added device.

If devices are associated with a user, the list of available devices is cached for faster retrieval. Consequently, if new devices are added after the device information for users is cached, the new devices will not be available for association with users.

CSCdr36451

First call to Associate Devices burdens CPU badly.

When creating a new user using the User Preference pages, addition of the user to the directory proceeds flawlessly. However, once the user is installed, attempting to Associate Devices leads to a very badly burdened CPU.

Watching the appropriate performance monitor and task manager screens shows that DC directory jumps to 100% processor utilization in three distinct segments, over a space of roughly 30 seconds. Since the web page is providing no feedback at this time, it's very easy for an end user to decide that the system is hung.

CSCdr36464

500 device limit leads to bad User Preferences screens.

The implementation of the search limit for devices that can be associated with users can result in an inaccurate representation of which devices a user currently controls. When a subset of devices is shown that contains devices that the user controls, these devices may be inaccurately represented as not being associated with the user.

CSCdr39475

Add a New User: session object timeout error.

When creating the first user from the Cisco CallManager User > Add a New User screen, the resulting page states:

Error

The following error occurred while trying to load the requested page. Sorry, your session object has timed out.

Click here to Begin a New Search.

This error occurs only on the first instance. Subsequent execution of User > Add a New User proceeds without errors, and you can continue defining a new user. If you open another browser, the first instance will fail, but subsequent attempts will succeed.

CSCdr51705

DCX500.exe is taking up 1 GB of memory.

Memory leaks in DC Directory can occur in customer environments with very large numbers of phones and users.

CSCdr53243

MetaLink does not continue to pull data from database after reboot.

DC Directory does not pull all needed information from the database after rebooting.

CSCdr84999

User Preferences pages must not display all of the Cisco CallManager devices by default

Sorting is no longer supported by the User Preferences pages because of its CPU intensive nature on the server side and because of the potentially large amount of data that would need to transmitted to the client if it were performed on the client side.

CSCdr86719

You must delete a user twice before it is removed from user list.

The problem is another manifestation of browser (IE) caching. The request to delete a user was not being submitted to the web server. The browser simply displayed a previous deletion results page from its cache.

This has been resolved by setting the CacheControl property on the Response object to force IE to always refresh certain pages from the web server rather than rendering them from its cache.

CSCdr88591

Opening up the 64th provider crashes the Cisco CallManager.

When JTAPI tries to open provider one after another without shutting down previously open providers, it was found that at the most 63 providers could be open. If an attempt is made to open the 64th provider it crashes the Cisco CallManager.

The Cisco CallManager service has to be restarted manually. The problem was caused by DC Directory not allowing more than 64 simultaneous connections to the directory. The client hung while opening the 65th connection, thus causing the SDL Router services to timeout, leading to the Cisco CallManager crash.

CSCdr02303

DC Directory crashes under severe network conditions.

DC Directory stops working.

CSCdr02305

DC Directory takes up to an hour to restart due to an IPC initialization failure.

 
Cisco IP Phone

CSCdr77894

Intermittent cutouts heard on Cisco IP Phone 79xx phones when talking to uOne Messaging.

There are intermittent cutouts of Cisco uOne Messaging system prompts sent to Cisco IP Phone 7900 family phones. The problem is not reproducible on Cisco IP Phone 30VIP and 12-SP+ models. Actual voice recordings such as spoken names and voice messages appear to be unaffected.


Resolved Caveats - Release 3.0(2d)

Table 4 lists and describes Caveats that are resolved in Cisco CallManager Release 3.0(2d).

Table 4 Cisco CallManager Release 3.0(2d) Resolved Caveats 

DDTS Number
Summary
Explanation
Automated Installation

CSCdr80536

The SQL license is set to per server with a default of 5 concurrent connections.

The automated install of SQL server sets the licensing to 'per server' with a default of 5 concurrent connections. Per our licensing there should be no restrictions on concurrent connections for systems supporting up to 10,000 phones. The current setting prohibits installs of more than 5 servers in a cluster.

CSCdr71568

The automated installation program does not cap SQL memory on the database publisher or subscriber.

When using the automated installation, SQL memory usage is not capped on publishers or subscribers. There is a potential of a Cisco CallManager crash if SQL consumes too much memory.

CSCdr65911

Installation CD does not install Compaq Utilities correctly on the Cisco Media Convergence Server MCS-7830.

Disc 1 of the Cisco CallManager 3.0(1) CDs does install the Compaq Utilities 39 MB partition. However, for some reason, when the user presses F10 during the boot sequence there is an error message:

The System Partition Utilities are not available on this system.

Press any key to continue...

This error occurs on the MCS-7830 platform.

CSCdr66413

Cisco Call Manager will not start after being installed from the Cisco CallManager 3.0(1) installation CDs.

If the DNS suffix is populated in the My Computer > Properties > Network Identification tab, Cisco Call Manager will not start after being installed from the Cisco CallManager 3.0(1) installation CDs.

CSCdr58051

The automated installation program restricts users to top-level domain names without special characters.

During the automated installation, the Domain Name field is limited to a top-level domain name (for example, Cisco.com is acceptable, but selsius.cisco.com would not be acceptable).

CSCdr46034

The automated installation program does not allow you to use a dash (-) or an underscore (_) in a workgroup or server name.

When installing the operating system from the "Operating System Installation and Recovery CD-ROM," the machine name entry field is limited to only alpha/numeric characters.

Cisco CallManager

CSCdr69851

Timer T200 should be set to 1200 ms instead of 1000 ms.

In certain digital sessions, the default value of timer T200 may be too small to ensure proper operation. Therefore, the default value for this timer has been changed to 1300 ms.

Cisco TFTP

CSCdr58199

Cisco TFTP stops building files and accepting database requests.

When deleting devices, TFTP does not serve a file for a device that is in the database.

Cisco Catalyst 6000 24 Port FXS Analog Interface Module (WS-X6624-FXS)

CSCdr64557

VAD causes multiple audio dropouts with Octel voice mail.

The user complaint is that audio, when accessing the Octel voice mail system, drops out intermittently. The dropout was reported to be from a fraction of a second to several seconds in duration, of almost continuous frequency. The problem was noted to occur even during the Octel voice prompts at the beginning of the session, indicating a problem in the stream from the Octel to the IP phone through the Cisco Catalyst 6000 24 Port FXS Analog Interface Module (WS-X6624-FXS) gateway.

CSCdr68352

WS-X6624-FXS ports out of service.

Shortly after all ports become concurrently "off-hook," Cisco Call Manager will report some ports status as "d" or "3" for anywhere from an hour to all day. Dick Tracy will report ports as either "NormalTalking Undefined!!" or "CallClearing Loop Open." Status via Telnet shows the ports as either on-hook or off-hook.

When the ports are in either of these two states, they appear to be unusable since Cisco CallManager is using the next analog gateways in the route list.

Cisco Catalyst 6000 8 Port Voice T1/E1 and Services Module (WS-X6608-T1/E1)

CSCdr69871

WS-X6608-T1/E1 did not pass ISDN PRI Layer 2 homologation test.

This was resolved by setting the T200 default timer to 1300 ms.

CSCdr79799

Hold tone not played out by DSPs when holding.

The WS-X6608 Digital Gateway will not play hold tones every 10 seconds when a Cisco IP Phone places the call on hold. There is no workaround.

This problem was due to mis-processing of the DtHoldTone message. It has been fixed in D004C300.

Cisco IP Phone

CSCdr69914

Disabling VAD for G.729 by setting the service parameter SilenceSuppressionSystemWide to FALSE does not appear to work.

When VAD is disabled for G729 and a call is made between two Cisco IP Phones, there is no continuous streaming.

CSCdr54497

Cisco IP Phone 7960 displaying DSP keepalive timeout message.

The message "dsp keepalive timeout" appears after doing the following:

1. Create a Meet Me conference.

2. Ad-hoc the Meet Me into itself.

3. The word "connected" on the Cisco IP Phone 7960 is replaced by "dsp keepalive timeout."

SNMP

CSCdr59957

SNMP agent sends bad response packet for certain Cisco IP Phone addresses.

Given any IP Phone, with IP address X.X.X.Y, where

X is any valid IP address range, and

Y ranges from 0 to 15

the Cisco CallManager SNMP agent is unable to decode the last byte of the IP address correctly (in the above case, the byte represented by 'Y').

This causes the Cisco CallManager SNMP Agent to report an incorrect IP address for the Cisco IP Phone in question. The last byte of the IP address for that phone would be reported incorrectly.

The only case for which the IP address will be reported correctly is when a Cisco IP Phone is assigned a network address greater than 15 for its last byte.

Using the above example of X.X.X.Y, where Y ranges from 16 to 255, the IP address of the phone will be reported correctly by the Cisco CallManager SNMP agent


Open Caveats

This section lists unresolved caveats for this release of Cisco Call Manager. Caveats describe unexpected behavior or defects in Cisco CallManager software and related hardware.

Open Caveats for Cisco CallManager Release 3.0(3b)

Table 5 describes possible unexpected behaviors by Cisco CallManager Release 3.0(3b)3.0(3b). Unless otherwise noted, these caveats apply to all Cisco CallManager 3.0 releases up to and including Cisco CallManager Release 3.0(3b).

Table 5 Open Caveats for Cisco CallManager Release 3.0(3b)

DDTS number
Description

CSCds21447

Cisco uOne ports did not register with secondary Cisco CallManager on failover.

Workaround: Stop and then restart Cisco uOne.

CSCds21377

The CallManager service was up, but was not running. Looking at PerfMon stats showed that the CPU utilization of Cisco CallManager was zero, but Cisco CallManager did show up as running.

Conditions: Standard installation. Some error occurred and the processing of Cisco CallManager shut down, but the CCM.exe service did not clear itself from memory.

Workaround: Stop the Cisco CallManager service from the Service Control Manager and restart it.

CSCds14138

Automated install should have a re-install option.

The problem occurs if the automated CD installation fails for some reason, or is aborted. If you put the disk back in and reboot with the intention of starting over it will pick up where it left off and fail at the same point, or get stuck in a loop. This leaves the machine in a state where you can't complete the installation.

You should be able to select an option at the very beginning that allows you to continue the failed or aborted install or to start over from scratch. It allowed you to do this with the Installation and Recovery CD of Cisco Call Manager 2.4 by pressing the F1 key.

Workaround: You may have to wipe the disk completely to get the install to work. This is accomplished by downloading the Compaq System Erase Utility from Compaq.com and erasing the machine completely.

CSCds14132

Updating a Cisco IP Phone while it is ringing locks up the phone.

When making a change to the speed dial labels on an IP phone, if the Update button is pressed while the phone is ringing, then the IP phone will not allow the call to be hung up (after it is picked up). Also, if the far-end hangs up, the IP phone will no longer return dial tone.

Workaround: Use one of the following workarounds to solve the problem:

Do not update the speed dial settings while the phone is ringing.

Once in this state, power the phone off and then back on to recover.

CSCds14126

Call park only works if Trace is enabled (On) at Arbitrary or Detail level. If Trace is Off, call park will not work.

Workaround: None known at this time.

CSCds14106

Cisco CallManager 3.0(2d) stops responding after starting; will not accept any connections.

Cisco CallManager may stop responding and stop accepting connections after starting up if a high number of route patterns are configured (greater than 300).

Workaround: Simplify your routing plan.

CSCds13646

SNMP agent on CallManager missing: MIBII Host Branch.

Install Cisco Call Manager from CDs. Version 3.0(1). The SNMP Agent does not respond to the requests to the MIBII Host Branch. It appears to be missing.

Install Windows 2000 Server without CDs and Cisco CallManager and the MIBII Host Branch is there and responds.

Workaround: None known at this time

CSCds11693

30-hop call forwarding using 100% CPU.

A single Cisco uOne server was attached to Cisco CallManager. Some or all of the Cisco uOne ports unregistered for some reason. Call forward hop was set to hop up to 30 times. Cisco CallManager was using close to 100% of the CPU while trying to connect to a working voice mail port. 475 users were experiencing slow dial tone and general system slowness.

Workaround: Limit the call forward hop count. The recommended limit is 15 or less.

CSCds11354

No ringback on transfer from PSTN calls coming in on IOS gateway.

With Cisco Call Manager 3.0(1) connecting to the PSTN via an H.323 gateway, if a call comes into a phone and it is blind transferred to another phone, the PSTN side will only hear dead air; they will not hear ringback.

Workaround: IOS changes are required to resolve this caveat. To work around the problem, replace the IOS gateway with a Cisco Digital Access Trunk Gateway (DE30, DT24+) or a Cisco Catalyst 6000 8 Port Voice T1/E1 and Services Module.

CSCds10242

Cisco IP Phone 7960 to NetMeeting G.711 calls without MTP have poor audio quality.

Calls from a Microsoft NetMeeting client to a Cisco 7960 IP phone result in poor audio quality heard on the Cisco IP Phone 7960 side of the conversation. If the 'i' button is pressed twice while the call is active, the RxSize shows up as 32, although it should be 20. This problem is not observed on 30 VIP or 12 SP+ phones.

Workaround: Enable MTP for the Device on the Call Manager Administration screen and ensure you have an available MTP resource.

CSCds09586

100% CPU utilization on the web server (inetinfo).

From Cisco CallManager Administration, update the default button template for Cisco IP Phone 7960 so that all the buttons are set to line. Then, go to the Cisco CallManager User web pages and try and set the Speed Dial on any Cisco IP Phone 7960. The CPU utilization on the inetinfo process goes up to 100% and stays there.

This problem when trying to set the Speed Dial on an admin's phone. In this case a new button template had been created to accommodate all of the 6 lines that were on the phone. As a result no buttons were configured for Speed Dial. Then, when we logged onto the Cisco CallManager User pages and tried to set the Speed Dial we noticed the 100% CPU utilization for inetinfo.

Workaround: Ensure at least one button is configured for Speed Dial for the Cisco IP Phone 7960 default template.

CSCds03249

Label line setting for phone inoperable.

Customer has a requirement to change the display of the line buttons to show information other than the directory number.

If the "Line settings for device" under the phone configuration is set with a label other than the default, (directory number) the string entered in the configuration does not display on the 7960. The directory number is displayed instead.

Workaround: None. This feature is not currently supported.

CSCdr97481

Line button doesn't answer call on 30VIP/12SP+ with call pickup.

Pressing the flashing line button after doing a Call Pickup on a 30 VIP or 12 SP+ phone will not retrieve the call. The phone will continue to ring. The only way to answer the call is by hanging up the handset and picking it up again or just doing a hookflash.

Workaround: Use the hookflash to retrieve the call.

CSCdr96235

Browser caching issues, User/Device Association pages.

Call Manager 3.0.(1) web pages used with browsers (Internet Explorer Version 4, 5, 5.5 and Netscape 4.5) have a problem caching old web content, which creates conflicting information about devices.

To recreate the problem:

1. Add devices.

2. Add users.

3. Associate users with device.

4. Delete device.

Then:

Attempt to modify user-associated device (any user, any device). Click on user from find user list (Update user information screen appears). Click associate devices. Deleted devices still appear on the available devices list.

If you add a new user and click on associate devices, the deleted devices still appear on the available devices list.

Add new device, click on user from find user list (Update user information screen appears), then click associate devices. The added device still appears on the available devices list.

Add new user and click on associate devices. The deleted device still appears on the available devices list.

Modify line number on any device, then add new user or select existing user and associate devices. The original line number still appears on the available devices list.

Select user with associated device. Go to available devices list, select new device to associate. The device selected was previously deleted. An association is made with the deleted device.

Workaround:

Netscape 4.5—Close all instances of Netscape and then reopen it. The caching problem will be resolved.

Internet Explorer Version 4, 5, 5.5—Internet Explorer appears to hold the content even after the browser is closed completely and reloaded. Only moving to another machine with a "fresh" browser will solve the problem.

CSCdr93939

In times of network congestion or high variable delay, the jitter buffer on a Cisco IP Phone 7960 will grow to a large value in an attempt to compensate for the large amount of jitter. When network conditions improve and the jitter returns to a low value, the phone will continue to buffer packets for a long time in its jitter buffer, thereby causing unacceptable voice delay.

Workaround: Put the call on hold and then resume it; this will start a new RTP stream and reset the jitter buffer.

CSCdr93620

Database migration of Cisco uOne ports from Cisco CallManager Release 2.4 to Release 3.0 fails.

After a database migration form Cisco CallManager Release 2.4 to Release 3.0, you cannot create a voice mail port in Cisco CallManager Release 3.0 with same voice mail DN as specified in Release 2.4 (the voice mail ports are not migrated, but Cisco CallManager still reports that the DNs are in being used).

Workaround: Remove voice mail ports and MWI entries in Cisco CallManager Release 2.4 before the migration takes place. Voice mail ports are not migrated from Cisco CallManager Release 2.4 to Release 3.0.

CSCdr92267

One-way voice on consecutive calls; hold or reset will fix.

One way audio can our on consecutive calls from a Cisco IP Phone to another Cisco IP Phone. The problem has occurred on different phones at different times of the day for different users.

Workaround: The known work around at this time is to reset the phone or, while in the call, put it on/off hold.

CSCdr91539

Messages button on Cisco IP Phone 79xx has incorrect behavior with multiple MWI.

A Cisco IP Phone 7960 with multiple line appearances and MWI does not use line 1 when using the messages button. If a line other than line 1 has MWI and line 1 has MWI, then the messages button will go off hook on that line and not the line 1.

Workaround: None.

CSCdr85945

Incorrect help definitions for Hold service parameters.

HoldType — Determines whether the hold light flashes more rapidly for the user who placed a call on hold in the case where two different phones share the same directory number. Default is still F.

ToneOnHoldTime — Determines the time interval between tones when a call is on hold. Default is 10 seconds, and the value range is 3 to 99999.

Workaround: Use the definitions above instead of the definitions in the Cisco CallManager Administration Guide and online help.

CSCdr81135

Can't associate devices to user using Netscape; Javascript error.

Using Netscape 4.7 or 4.73 on different PC's. Go to Global Directory, select user, press Associate Devices and go to User Device Assignment screen. When you check a device box, at the bottom of the browser it says "Javascript error: Type 'Javascript:' into Location for details." When you press update; the device does not get associated with the user.

Workaround: Use Microsoft Internet Explorer 5.0.

CSCdr74342

DC Directory gets suspended due to file system error.

Symptoms: The CCMUser pages are not accessible or the user administration pages return errors when accessed.

Conditions: It is possible that certain file system backup utilities (such as Veritas Backup Exec) may lock DC Directory's database volumes in such a way as to prevent DC Directory from accessing these files. Under these conditions, DC Directory service gets into a suspended state. This will cause the aforementioned web pages to not function at all.

Workaround:

1. First, exclude DC Directory's database folder C:\dcdsrvr\run\dcx500\database from the list of directories that are backed up by the files system backup utility.

2. Second, stop the DC Directory service either from the Services administrative tool or by running the command

net stop DCDirectory

3. Finally, restart the DC Directory service either from the Services administrative tool or by running the command

net start DCDirectory

Additional Information: The problem can be ascertained by verifying the presence of the message "OBPIBSRD ReadFile ERROR 33 !!" in the file c:\dcdsrvr\run\dcx500\dcx500.out.

CSCdr57978

Cancel operation for call transfer causes a problem on the phone lamp.

1. Phone A makes a call Phone B.

2. B answers call.

3. B presses the transfer button.

4. B presses the line button to cancel the transfer operation above.

5. B places call on hold.

The lamp transfer is blinking.

Workaround: None known at this time.

CSCdr57242

OutofBandwidthText is not on by default, but it should be.

A call from a Cisco IP Phone to another Cisco IP Phone gets a reorder tone intermittently. Nothing on the phone display indicates the reason. Further troubleshooting showed that the call was made between locations and it was out of bandwidth. The Cisco IP Phone should have displayed the "Not Enough Bandwidth" message by default.

Workaround: Configure the OutofBandwidthText message that displays on the phone when calling between locations that are out of bandwidth. This should be on by default on a new install but if it is not, then it must be configured.

CSCdr53488

In a system with a single Cisco CallManager, after the Cisco CallManager is brought down and left down for a period of time before being brought back up (perhaps 30 minutes), a Cisco IP Phone appears to be out of operation and displays an "opening......" message.

This phenomenon was observed on IP phones that were off-hook with an active call at the time the Cisco CallManager was brought down. The system is designed for the phone to retain active calls if the Cisco CallManager is lost. In this state, it will not reregister until the call ends. Without a Cisco  CallManager, the only stimulus to indicate termination of a call is the hook switch. In this particular case, if the phones' hook switch had been depressed, the phones would have reregistered.

Workaround: Use the **#** reset sequence on the Cisco IP Phone to bring it back into operation.

CSCdr53109

If you send 500 or more broadcast packets/sec, the Cisco IP Phone does not send ARP reply.

To protect the phone from broadcast storms, the C3PO switch has been programmed for broadcast suppression. Broadcast traffic that exceeds 2.24M bits/sec will be suppressed. Suppression causes dropping of broadcast packets. Since ARP requests are broadcast packets, during a suppression event ARP request that the phones need to communicate can be lost. Unicast transmissions will not be affected.

1. The phone does not have adequate CPU power to process 10Mg of broadcast packets.

2. 10 Mg of broadcast packets, without suppression, would completely consume the internal bandwidth between the C3PO and the phone ASIC.

3. Dropping any broadcast packets can result in the symptom described.

Workaround: None. Works as designed.

CSCdr51675

When using the Cisco CallManager Control Center web page, the services for a server do not appear when it is selected. The message "A connection to the server could not be established" is displayed on the screen.

This symptom can occur under any of the following conditions:

The server hosting the Cisco CallManager Administration web pages can not resolve the name or IP address of the target server.

The target server is offline.

The target server no longer exists, but it is still configured in the Cisco CallManager Administration pages.

The target server's name in DNS does not match the server's machine name.

Workaround: You can start and stop the services on any server by logging onto the server at its console. From the Start menu, open the Administrator Tools program group and double click Services. You can then select the desired service and use the Start, Stop, and Re-Start icons at the top of the window to control the service.

To use the Control Center web page you must correct the configuration in the Cisco CallManager Administration pages or correct the network configuration on either the target server or the web server hosting the Cisco CallManager Administration pages.

CSCdr50642

After the initial installation, changing a server name to an IP address will cause phones not to boot. Auto-registering phones will not connect to Cisco CallManager. The reason they do not connect is that the configuration file still contains the server name.

Workaround: After changing the server name to an IP address, you must stop and then restart the Cisco TFTP service.

CSCdr49680

When the Cisco Catalyst 6000 8 Port Voice T1 and Services Module is reset while conferences are in progress, the Cisco CallManager will not set up any more conferences. This occurs when the device re-registers with the Cisco CallManager, and the callers have not yet hung up the phones.

Workaround: Reset the Cisco CallManager.

CSCdr48343

If you remove the Cisco CallManager service using the Cisco Service Configuration tool and then try to re-add the CallManager service back in using the Cisco Service Configuration tool, the service is never added and Cisco CallManager will not run.

Workaround: To work around the problem, you can re-add and restart the Cisco CallManager service using the following method:

1. Select Start > Run from the Windows Start menu.

2. Type cmd and click OK to open a DOS window.

3. Enter the following command at the C\: prompt:

C:\> ccm.exe -service

4. Press Return.

The CallManager service is now added.

5. Reboot the system.

6. Log in to the system.

7. Select Start > Programs > Cisco CallManager > Cisco CallManager Service Configuration.

8. Click the check box for Cisco CallManager service.

9. Click OK.

10. Click OK to reboot the system when prompted.

11. Log in to the system and open Cisco CallManager Administration.

12. Select Services > Control Center.

13. Verify that the Cisco CallManager service is now listed as an available service.

14. Start the Cisco CallManager service.

CSCdr47810

On a Cisco ICS7700 or a server running Cisco CallManager Release 3.0(1), if you delete the Cisco Database Layer Monitor service from the Service Parameters Configuration screen, the system does not operate properly when you restart it.

Workaround: To correct the problem, re-install the Cisco CallManager software.

CSCdr47046

Route pattern @ without local area-code waits for interdigit timeout. Dialing 7-digit numbers will typically require an interdigit timeout of 10 seconds.

Workaround: Add an "End-Of-Dialing Does-Not-Exist" filter to the route pattern 9.@.

CSCdr46136

Calls between Cisco CallManager clusters do not work. This is due to a database configuration error related to intercluster trunks.

Workaround: Use the following recommended configuration for intercluster trunks.

Recommended configuration for intercluster trunks in Cisco CallManager 3.0 to achieve highest trunk availability:

Given: There are two Cisco CallManager clusters: Clstr-A and Clstr-B (a cluster is one or more CallManager nodes).

Clstr-A configuration:

1. In Clstr-A, create a CallManager group that is to be used for intercluster trunk devices that connect to Clstr-B (for example, "Clstr-A to Clstr-B CM group". Add CallManager nodes from Clstr-A to this group in the order desired (up to three CallManagers can be added to this group). As an example, add nodes 2, 4, and 5 to this group (Clstr-A2, Clstr-A4, and Clstr-A5).

2. In Clstr-A, create a device pool that uses the newly created CallManager group (for example, "Clstr-A to Clstr-B device pool").

3. In Clstr-A, create up to three inter-cluster trunk devices that 'connect' to nodes in Clstr-B.

The device names of these inter-cluster trunks are the IP addresses or computer names (if names can be resolved to IP addresses), of the nodes in Clstr-B with which you wish to connect.

For example: DEVICE NAMEs = Clstr-B1, Clstr-B3, Clstr-B5, for nodes 1, 3 and 5 of Clstr-B.

For these devices, assign the DEVICE POOL that was created in step 2 above.


Note You must reset these devices when you create them to bring them in-service.

Clstr-B configuration:


Note Clstr-B configuration depends on Clstr-A configuration.

4. In Clstr-B, create a CallManager group that is to be used for intercluster trunk devices that connect to Clstr-A (for example, "Clstr-B to Clstr-A CM group"). For each of the intercluster trunks that was created in Clstr-A that connect to Clstr-B (see step 3), add the Clstr-B CM node that corresponds to its DEVICE NAME to this group.

For this scenario, add CallManager nodes Clstr-B1, Clstr-B3, and Clstr-B5 to this newly created group (the "Clstr-B to Clstr-A CM group".

CSCdr46136
(continued)

5. In Clstr-B, create a device pool that uses the newly created CallManager group (for example,"Clstr-B to Clstr-A device pool").

6. In Clstr-B, create intercluster trunk devices that connect to the nodes in Clstr-A that are included in Clstr-A's CM group (that is, the CallManager group created in step 1). Device names of these intercluster trunks are the IP addresses or computer names (if names can be resolved to IP addresses) of the nodes in Clstr-A that were designated in the CallManager group created in step 1, that is, nodes 2, 4 and 5 of Clstr-A (Clstr-A2, Clstr-A4, and Clstr-A5).

For these devices, assign the DEVICE POOL that was created in step 5.


Note You must reset these devices when you create them to bring them in-service.

The configuration described above creates a "web" of intercluster trunks where there is always an available trunk between Clstr-A and Clstr-B, given the following:

one of the nodes in Clstr-A that is designated in CallManager group "Clstr-A to Clstr-B CM group" is running, and

one of the nodes in Clstr-B that is designated in CallManager group "Clstr-B to Clstr-A CM group" is running.

CSCdr43467

Intercluster communication will fail if

A Cisco CallManager name or IP address is used, and the DNS server does not have a reverse lookup zone configured for the subnet in which the Cisco CallManager's IP address exists, and

A DNS server is configured in the network control panel on the Windows 2000 Server on which the Cisco CallManager resides.

Workaround: Use one of the following methods to work around the problem:

If you want to use DNS, make sure that the DNS has reverse-DNS lookup enabled and that the names and IP addresses of the Cisco CallManagers are in the DNS server.

A second workaround is to use only IP addresses for the Cisco CallManagers in the cluster (instead of relying on DNS names) and remove any DNS entries from the network control panel. This ensures that no reverse DNS lookup is attempted on any device connected via IP to the Cisco CallManager.

A third workaround is to modify the hosts file in the winnt/system32/drivers/etc/ directory and add entries for the Cisco CallManagers.

CSCdr42883

Memory leaks in the database occur as a result of normal operation of the system.

DLLHost.exe is the executable under which the Microsoft Transaction Server (MTS) runs. This executable grows in memory size as changes are made to the database via services or Cisco CallManager Administration. If a long enough period of time elapses, then the memory size will drop. However, if there are several services polling the database periodically, this may not occur.

Workaround: Perform the following steps to reset the DLLHost.exe memory

1. Select Start > Administrator Tools > Component Services. > Console > COM+ Components > DBL COM+.

2. Right click on the DBL icon and select Shutdown. This will reset the DLLHost.exe memory.


Note There could be multiple DLLHost.exe applications running and visible in the Task Manager. The other DLLHost.exe programs are for applications other than MTS.

CSCdr42238

When communicating to the PSTN via a Cisco Catalyst 6000 PRI Gateway, audio is lost and the call has to be reinitiated.

Workaround: On the Cisco Voice Gateway 200, enter the following command from the IOS global configuration prompt:

vg200(config)# mgcp modem passthru CA

This command disables FAX operations and should not be used for Cisco VG 200s connected to FAX machines.

CSCdr41623

When a port on a Cisco Unicast Conference Bridge is conferenced back to itself, a feedback loop is created in the conference bridge and all participants will experience audio feedback. Even if all phones involved in the conference hang up, the conference bridge still has a feedback loop because two or more ports of the conference bridge are conferenced together and neither has disconnect supervision.

Workaround: You must perform a conference bridge reset to clear the conference.

CSCdr41614

DTMF digits are not propagated to members of a conference. When a DTMF digit is pressed when a phone is connected to a conference, the digit is dropped.

For example, if a ringing phone is added to a conference, and the phone is subsequently not answered and forwards to voice mail, there is no way to remove that party from the conference, or to exit or shut down voice mail.

Workaround: None. If voice mail is conferenced in by mistake, the only way to correct the problem is to terminate the conference and set it up again.

CSCdr41545

The problems described here can occur during database conversion when migrating from Cisco CallManager Release 2.4 to Cisco CallManager Release 3.0.

Auto-registration and range was enabled in the Cisco CallManager Release 2.4 database, but the migrated Release 3.0 database shows auto-registration disabled.

Workaround: Enable auto-registration using Cisco CallManager Administration.

The default phone templates for a Cisco CallManager may not be what you expect.

This occurs because the defaults table does not migrate from Release 2.4 to Release 3.0. Defaults are inserted per Cisco CallManager when a Cisco CallManager is added. The Cisco CallManager inserts the first Cisco IP Phone model 12 SP+ and model 30 VIPs phone templates found.

Workaround: Change the default phone templates using Cisco CallManager Administration.

A route filter was added during the installation, even though a route filter was not migrated. This route filter has no setting.

Workaround: None needed. The installation adds a default route filter by design.

The Cisco Messaging Interface was set in Release 2.4, but in Release 3.0 the service parameter for the voice mail number is blank. This problem occurs because voice mail records do not migrate from Release 2.4. This is by design. The DBConvert.txt file in c:\ describes any records that do not migrate.

Workaround: Set up the Cisco Messaging Interface using Cisco CallManager Administration.

A Call Park number was migrated, but a Cisco Call Manager was not assigned. Therefore, the Call Park did not work. Call Park migrated, but when you try to edit the Call Park and select a Cisco CallManager, none are displayed in the list. The Cisco CallManager CallParkMap entry is not converted because the Cisco CallManagers are not converted. Cisco CallManager Release 3.0 assigns any parks migrated to the first Cisco CallManager inserted.

Workaround: Delete the Call Park and add another Call Park.

Cisco uOne ports did not migrate. This occurs because voice mail devices do not convert from Release 2.4 to Release 3.0.

Workaround: Add the voice mail ports using Cisco CallManager Administration.

An intercluster gateway migrates from Release 2.4, but is not shown as an intercluster gateway in Release 3.0.

Workaround: Change the gateway to an intercluster gateway using Cisco CallManager Administration.

CSCdr41545
(continued)

Route patterns set up as blocks do not display in the route pattern list. The problem occurs because Release 3.0 migrate these records, but they are listed in the Numplan table as devices instead of routes.

Workaround: To correct the problem, try to find a device that matches the blocking route pattern, delete it, and add it as a route pattern. Another possible workaround is to edit the Numplan entry in the SQL Server Enterprise Manager and change tkPatternUsage from 2 (Device) to 5 (Route) and copy fkDialPlan from another record into this record.

Phone locations are not migrating from Release 2.4 to Release 3.0

Workaround: Set the device location in Cisco CallManager Administration.

CSCdr40345

Errors are returned by the Cisco CallManager User Administration web pages.

These errors are returned when the directory does not contain a complete listing of the devices in the Cisco CallManager database. This occurs when the directory is first configured and there are a large number of devices to import from the database to the directory.

Workaround: Wait for the directory to finish importing the device information. This is indicated by the quiescence of the DCX500.exe process.

CSCdr40194

A route pattern containing more than 24 characters fails. This problem can occur under the following conditions: Create a route pattern in the Route Pattern Configuration Page. Associate this route pattern with a Route List or gateway. The route pattern may or may not be more than 24 characters. Attempt to make a call that matches the route pattern defined. The result is the calling party receives a reorder tone. The call cannot be completed.

Background: Cisco CallManager expands the route pattern and analyze the resulting matching digit strings. If the digits are sent to public networks, the ISDN protocols have a limitation of 24 digits. If the expanded resulting digit string is more than 24 digits. the number will be truncated. This is the limitation of the ISDN protocols.

For example, user enters a route pattern string that has less than 24 characters. The resulting matching digit string can end up being greater than 24 characters (wildcards can present numerous digits). If the resulting matching digit string is greater than 24 digits, only the first 24 digits will be sent. If the resulting matching digit string is less than 24 characters, Cisco CallManager will send all digits to the public networks.

If the user enters in more than 24 characters for a route pattern, the resulting matching digit string can end up with less than 24 characters (for example, if there is a long access code and user selects a digit discard instruction to truncate the access code). If so, the resulted digits will be sent. However, if the resulting matching digit string is still greater than 24 characters, then, only the first 24 digits are sent.

Workaround: Since the route pattern's allowable digits may or may not be exactly what the user enters in the Route Pattern field in the Route Pattern Configuration Page, the page does not limit the user's input to only 24 characters. The database has a limitation of 50 characters for the Route Pattern field, so this field has the number of allowable characters to be 50 characters.

CSCdr40169

No SMDI information is sent to Voice Mail on forward busy if the phone is in a partition. When a call is forwarded due to busy destination, the destination identification information is not sent to the SMDI interface. The caller then gets the Voice Mail generic greeting instead of being mapped into a specific voice mailbox.

Workaround: None.

CSCdr40091

When you change the name of a region, no calls can be made to or from endpoint devices in that region.

Workaround: Use one of the following methods to resolve this issue:

Change the name of the region back to what it was before the name was changed.

Reset all Cisco CallManagers in the cluster that contains the region whose name was changed.

CSCdr39493

You can not assign the same extension to a Cisco Catalyst 6000 24 Port FXS Analog Interface Module and a Cisco IP Phone.

Workaround: None. For Cisco CallManager Release 3.0, only MGCP gateways (VG 200s) allow FXS ports to share the same phone number with a Cisco IP Phone. This shared line capability is not supported for other analog gateways in this release.

CSCdr39403

Database notification does not work in certain situations. Updates made from the Cisco CallManager administration page are registered, but not reflected in the MIB tables until the SNMP data collector or Cisco CallManager (depending on the type of update) is restarted.

In Cisco CallManager clusters, changes to global values in a cluster environment are reflected on the MIB table that is local to the change, but not in all of the MIB tables throughout the cluster. Updates will only be reflected on the MIB table that is local to the change, with the following exceptions:

When deleting a time, region or any static item, no MIB tables will reflect the change.

When adding groups and regions, no MIB tables will reflect the change.

Workaround:

Restart the SNMP data collector or Cisco CallManager in order to display updated values in the MIB tables. If a Cisco CallManager cluster is involved, you must restart all SNMP data collectors in order to show consistent values in the MIB tables throughout the cluster.

Examples (local):

To remedy the two exceptions to local MIB table updating:

When deleting a time, region or any static item, restart the SNMP data collector for the local Cisco CallManager installation to see the update reflected in the MIB table.

When adding groups and regions to a Cisco CallManager cluster, restart the SNMP data collector, which will help to update the MIB table.

In Cisco CallManager clusters, changes to global values in a cluster environment will not be reflected in all of the MIB tables. You must restart all SNMP data collectors in order to show consistent values in the MIB tables throughout the cluster.

Examples (cluster):

When adding or deleting multi-line extensions of an existing telephone, you must restart the Cisco CallManager system associated with that particular phone to activate the change in the MIB table for phone extensions.

When changing the primary Cisco CallManager name and description, you must restart Cisco CallManager to see the changes in the Primary MIB table. If the update involves a Cisco CallManager cluster, you must restart all Cisco CallManagers in the cluster to see the changes reflected in all of the tables.

CSCdr37312

For gatekeeper-controlled intercluster trunks to work properly, the GatekeeperControlRegistrationType flag in System Parameters must be set to T (true).

Workaround: The GatekeeperControlRegistrationType flag must be set to T (true) for each Cisco CallManager that has a gatekeeper-controlled intercluster trunk.

CSCdr36406

A <CmdArg>[Object Error]<noCmdArg> error message is returned when adding a user via the Cisco CallManager User Administration web pages.

If users have been added to the system via private scripts, the directory may not allow some userid name conflicts to occur, but does not properly report the conflict. For example, a user with the userid of "jsmith@company.com" will conflict with the proposed userid of "jsmith". This problem should not appear through normal usage of the product.

Workaround: Use a different userid for the new user or access the directory directly to delete the conflicting user.

CSCdr36331

Going from low bit rate to low bit rate, the wrong counter is sent from a transcoder. The problem occurs when the system is configured so that a transcoder is invoked to transcode between two low-bit-rate codecs (for example, from a G.723 to a G.729).


Note The use of a transcoder to support low-bit-rate to low-bit-rate transcoding is not supported in Cisco CallManager Release 3.0.

When a transcoder is invoked to transcode between two low-bit-rate codecs, the transcoder consumes the internal resources of two transcoders, but only one transcoder is allocated.

As a result, more transcoders are available to be allocated in the system than there are internal transcoding resources to support them. When all available internal transcoding resources are in use, and another transcoder is allocated and begins transcoding, the voice quality on all calls going through that transcoder device degrade noticeably, and sometimes severely.

Workaround: It is highly recommended that the system be carefully configured so that transcoding between low-bit-rate codecs is not required.

There is no workaround to this problem other than limiting the number of calls through a given transcoder device by expanding the number of transcoders available.

If there are at least twice as many transcoders available as there are calls that need them at any given point in time, the problem should be eliminated.

CSCdr35751

This problem occurs when Call Forward All is cleared from the user preference pages for a DN that is shared by multiple phones (that is, a multi-line).

When Call Forward All is cleared on a multi-line, a reset is only sent down to one phone that shares the multi-line, and the call forward lights are cleared on that phone only. The call forward is cleared for the specified DN, but the forward lights on all other phones will remain on, thus giving a false indication that the phone is still forwarded, when it really is not.

Workaround: To work around the problem:

Set and clear all Call Forwards from the phone itself instead of from the user preference pages. This works correctly when done from the phone.

Reset each of the phones that incorrectly displays a call forward light. This can be done either manually from the phone, or from Cisco CallManager Administration.

CSCdr35007

The second Cisco IP Phone 7960 in a daisy chain loses connection after one minute.

If you connect Cisco IP Phone 7960s together in a line (that is, daisy chain them), a problem with one phone can affect all subsequent phones in the line. The bandwidth is also shared among all phones in the line.

Workaround: None. Daisy chaining of Cisco IP Phones is not supported. Each Cisco IP Phone should be directly connected to a switch port.

CSCdr34988

The first Cisco IP Phone 7960 in a daisy chain stopped communicating with the Cisco CallManager.

If you connect Cisco IP Phone 7960s together in a line (that is, daisy chain them), a problem with one phone can affect all subsequent phones in the line. The bandwidth is also shared among all phones in the line.

Workaround: None. Daisy chaining of Cisco IP Phones is not supported. Each Cisco IP Phone should be directly connected to a switch port.

CSCdr34794

With any connections involving two separate low-bit-rate voice compressions, such as calls between different cell-phone networks, connections from an external cell-phone through a VoIP gateway terminating at a Cisco IP Phone running G.729 may result in non-optimal voice quality.

Workaround: It is recommended that calls between Cisco IP Phones and VoIP gateways that reach the external PSTN be configured for G.711 operation.

CSCdr31859

Software conference bridges on a secondary Cisco CallManager are deactivated when a hardware conference bridge fails over to a secondary Cisco CallManager that only has software conference bridges registered.

Hardware conference bridges and software conference bridges cannot be registered on the same Cisco CallManager at the same time. When a hardware conference bridge fails over to a secondary Cisco CallManager and registers with that Cisco CallManager, all software conference bridges currently registered on that Cisco CallManager are deactivated and only the resources of the hardware conference bridges are available.

When the primary Cisco CallManager for that hardware conference bridge comes back up, the hardware conference bridge will un-register from its secondary Cisco CallManager, and re-register with its primary Cisco CallManager. The secondary Cisco CallManager is then left without any registered conference bridge resources, because they have all been deactivated.

Workaround: Use one of the following methods to work around the problem:

Reset the software conference bridges. This will cause them to re-register with the Cisco CallManager. This must be done after all hardware conference bridges have un-registered from that CallManager.

Avoid the problem by configuring the system in such a way that hardware conference bridge devices do not fail over to a Cisco CallManager that uses software conference bridges.

CSCdr30628

The Cisco IP Phone 7960 speakerphone does not automatically save the volume level.

Workaround: To save the current volume level setting, adjust the volume, select Settings, and then select Save.

CSCdr28947

Transfers from Cisco uOne to invalid extensions by pressing * 8 leave the caller in silence.

For example, if a user logs into a mailbox, presses * 8 to transfer, and enters an invalid extension, the transfer is attempted, but the user does not hear anything after the standard Cisco uOne prompt is played.

In this situation, the caller is on hold pending transfer completion. The transfer is never completed because the extension was invalid, and re-order was returned to the uOne port. Re-order is not recognized by the Cisco uOne port, so no further action is taken, and the caller is left on hold.

Workaround:

The user can hang up the call and call the person directly.

Always transfer calls through Cisco uOne using a valid extension.

CSCdr20726

H.323 phone does not hear progress tones during call setup.

Workaround: None. This feature is not supported in Cisco CallManager Release 3.0.

CSCdr13641

Cisco uOne is capable of playing a specific message to the calling party to inform the calling party that the called party was busy or did not answer. Cisco CallManager does not currently distinguish between call forward busy and call forward no answer calls when sending information to a voice mail system. The information sent to the voice mail is the same whether it is a busy or no answer condition.

Workaround: There is no workaround other than to have the user make a generic greeting. Cisco CallManager Release 3.0 does not support this feature.

CSCtr84167

When you enable the service parameter "Block Offnet to Offnet Transfer" and make a blind transfer with Cisco Unity Connection, the Q.931 SETUP message which CUCM sends to the PSTN gateway for an outbound PRI call still reaches the gateway. This transfer results in a dropped call.

Workaround: No workaround exists.


Troubleshooting

For specific troubleshooting information, refer to the Cisco IP Telephony Troubleshooting Guide for Release 3.0. You can access this guide at the following website address:

http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/3_0/index.htm

Documentation Updates

This section contains the latest documentation updates for Release 3.0 of the Cisco CallManager. Included in these updates are any changes or late-breaking information that occurred after production of the Release 3.0 Cisco CallManager Administration Guide, Configuring Remote Serviceability for Cisco CallManager Release 3.0, and/or the online help for the Cisco CallManager application, as well as any information that was omitted from the Release 3.0 documents.

New Service Parameters

Table 6 contains new Cisco CallManager service parameters, with descriptions, that were not included in the Release 3.0 Cisco CallManager Administration Guide or the online help for the Cisco CallManager application.


Caution Please do not modify any of the defaults or settings of the following parameters without the assistance of the Cisco Technical Assistance Center (TAC).

Table 6 Cisco CallManager Service Parameters Not Included in Release 3.0 Documentation 

ParamName
Description

EnableSNMP

This parameter enables the collection of SNMP data from the Cisco CallManager.

EnableStatistics

This parameter enables or disables collection of performance monitor statistics by the Cisco CallManager.


Table 7 contains new Cisco Messaging Interface (CMI) service parameter definitions that were not included in the Release 3.0 Cisco CallManager Administration Guide or the online help for the Cisco CallManager application.


Caution Please do not modify any of the defaults or settings of the following parameters without the assistance of the Cisco Technical Assistance Center (TAC).

Table 7 CMI Service Parameters Not Included in Release 3.0 Documentation   

ParamName
Description

BackupCallManagerName

This parameter is used to define the names of the Cisco CallManagers that are going to be used for the CMI backup. You can use either the name of a Cisco CallManager or its IP address.

BaudRate

Cisco CMI connects to the voice mail system via an RS-232 connection. This parameter defines that connection.

Recommended default value: 9600


Note Many voice mail systems can be configured to use different baud rates, but the one shown here will frequently be correct.

CallManagerName

This parameter is used to define the names of the Cisco CallManagers that are going to be used for the CMI primary. You can use either the name of a Cisco CallManager or its IP address.

DataBits

CMI connects to the voice mail system via an RS-232 connection. This parameter defines that connection.

Recommended default value: 7

DialingPlan

This parameter is one of four that are required by CMI to register an intercept for the voice mail system with which CMI is going to work.


Note Small systems without a complex dialing plan usually only need the VoiceMailDn parameter. The remaining parameters, DialingPlan, RouteFilter, VoiceMailPartition will default to empty strings.

InputDnSignificantDigits

This parameter is designed to accommodate the differences between voice mail mailbox numbers and DNs. If a legacy voice mail system has mailbox numbers that are longer than the DNs on the system, this parameter can be used to strip the most significant digits. The numeric value of this parameter indicates how many digits should be used.


Note There is no provision for stripping digits other than leading ones.

Recommended default value: 10

KeepAliveDn

This is a string parameter. For most voice mail systems a value of F is acceptable. However, some Octel systems periodically send an invalid DN specifically for the purpose of verifying that the attached Cisco CallManager is functioning properly. In this case, you can turn off ValidateDns if you know the DN that the Octel system will use as a keep-alive. By programming that DN into the KeepAliveDn parameter, you will ensure that the invalid DN message is returned to the voice mail system when needed.

OutputDnFormat

This parameter is used to format the DNs sent to the voice mail system. Most numbers passed to the voice mail system are formatted using this parameter.

Default value: %010s

OutputExternalFormat

This parameter is also used to format the DNs sent to the voice mail system. Calling party DNs that are seven digits or longer are formatted using this parameter.

Default value: %010s

Parity

Cisco CMI connects to the voice mail system via an RS-232 connection. This parameter defines that connection.

Recommended default value: Even


Note The parity settings can be None, Even, Odd, Mark, or Space. Settings are usually Even and None, with Mark and Space rarely being used. Just using the first character of the parity name also works.

RouteFilter

This parameter is one of four that are required by CMI to register an intercept for the voice mail system with which CMI is going to work.


Note Small systems without a complex dialing plan usually only need the VoiceMailDn parameter. The remaining parameters, DialingPlan, RouteFilter, VoiceMailPartition will default to empty strings.

SerialPort

Cisco CMI connects to the voice mail system via an RS-232 connection. This parameter defines that connection.

Recommended default value: COM1


Note The SerialPort name should be the same name that you see in Device Manager under NT.

SsapiKeepAliveInterval

This is a numeric parameter. During normal operations, CMI will be attached to a Cisco CallManager. When this is the case, CMI sends a keep-alive message to the Cisco CallManager at the rate specified by this parameter.

Default value: 30 seconds


Caution This parameter should not be changed from the default value unless directed by the Cisco Technical Assistance Center (TAC).

StopBits

Cisco CMI connects to the voice mail system via an RS-232 connection. This parameter defines that connection.

Recommended default value: 1

ValidateDns

When CMI receives incoming lamp commands from the voice mail system, it normally validates the DN against the NumPlan table. This is an attempt to verify that the DN matches an existing DN known to Cisco CallManager. If the DN is not found in NumPlan, an invalid DN message is sent to the voice mailbox.

Default value: T


Note On a system with a lot of traffic to and from the voice mail system, you may choose to skip this validation process by setting the ValidateDns parameter default to F.

VoiceMailPartition

This parameter is one of four that are required by CMI to register an intercept for the voice mail system with which CMI is going to work.


Note Small systems without a complex dialing plan usually only need the VoiceMailDn parameter. The remaining parameters, DialingPlan, RouteFilter, VoiceMailPartition will default to empty strings.

Configuring the Microsoft Telnet Daemon for Bridged Telnet

To make it possible for the Cisco Service Engineer (CSE) to log into the Telnet service on your Cisco CallManager system, you must configure the Microsoft Telnet daemon.

Use the tlntadmn command to accomplish this task.


Step 1 Select Start > Programs > Command Prompt

Step 2 In the command window, enter the Telnet administration command:

tlntadmn

Step 3 Enter the following options from the lists displayed at the prompt.

a. From the first list, select option number 3, Display/change registry settings

b. From the second list, select option number 7, NTLM

Step 4 Next, set the value of NTLM to zero by responding to the prompts.

Current value of NTLM = 2
Do you want to change this value ? [y/n]y
NTLM [ current value = 2; acceptable values 0, 1 or 2 ] :0
Are you sure you want to set NTLM to :0 ? [y/n]y

Step 5 To finish, enter the following options from the lists displayed at the prompt.

a. From the first list, select option number 0, Exit this menu.

b. From the second list, select option number 0, Quit this application.

Step 6 Restart the Telnet service to enable the setting to take effect.


Server Name Change

Change the CiscoWorks2000 server name by editing the SAenvproperties.ini file manually, then restarting the Cisco Syslog Collector service. In future releases, an administrative interface will be available for this purpose.

Running Show Tech

To run show tech correctly, use this example to construct your command:

        show -f output.txt -v -w480 db

The example given in the Show Command chapter of Configuring Remote Serviceability for Cisco CallManager 3.0 (page 3-2) lacks a space before "db".

Changes

This section contains changes that have occurred since the original release of the Cisco CallManager Administration Guide Release 3.0. These changes do not currently appear in the Release 3.0 Cisco CallManager Administration Guide or the online help for the Cisco CallManager application.

Default Value Changed for SdlTraceTotalNumFiles Service Parameter

SdlTraceTotalNumFiles is a service parameter for the Cisco CallManager service type. The default has been changed to 250. This is the correct default for this service parameter.

Omissions

This section contains lists of service parameters for the Cisco CallManager that were not included in the initial production of the Release 3.0 Cisco CallManager Administration Guide and online help for the Cisco CallManager application. These parameters will be defined in a later release of the document.


Caution Please do not modify any of the defaults or settings of the following parameters without the assistance of the Cisco Technical Assistance Center (TAC).

Cisco CallManager Service Parameters

The following list contains the service parameters that can be configured for the Cisco CallManager service type that were omitted from the Release 3.0 Cisco CallManager Administration Guide and online help for the Cisco CallManager application:

AlwaysUsePrimeLine

CallAcceptTimer

CallerId

CgpnScreeningIndicator

CtiApplicationHeartBeatTime

DeviceStatusPollInterval_msec

DialPlanPath

EnableSNMP

EnableStatistics

FlashHookDuration_msec

GatekeeperRefresh

H225BlockSetupDestination

MaxDaResponseTimeoutErrorCount

MaxNumberOf723Calls

MGCPConnectTime

MGCPRespTimeout

MGCPTimeout

RASInboundLRQFlag

RASOutboundLRQFlag

SdlListeningPort

SdlTraceDataFlags

SdlTraceDataSize

SdlTraceFilePath

SdlTraceFlag

SdlTraceTypeFlags

SendingCompleteIndicator

ToneOnCallForward

TypeOfCalledNumberForH225Devices

VoiceMail

Cisco TFTP Service Parameters

The following list contains the service parameters that can be configured for the Cisco TFTP service type that were omitted from the Release 3.0 Cisco CallManager Administration Guide and online help for the Cisco CallManager application:

AlternateFileLocation1

AlternateFileLocation2

AlternateFileLocation3

AlternateFileLocation4

AlternateFileLocation5

AlternateFileLocation6

AlternateFileLocation7

AlternateFileLocation8

AlternateFileLocation9

AlternateFileLocation10

Cisco Messaging Interface Service Parameters

The following list contains the service parameters that can be configured for the Cisco Messaging Interface (CMI) service type that were omitted from the Release 3.0 Cisco CallManager Administration Guide and online help for the Cisco CallManager application.

BackupCallManagerName

BaudRate

CallManagerName

DataBits

DialingPlan

InputDnSignificantDigits

KeepAliveDn

OutputDnFormat

OutputExternalFormat

Parity

RouteFilter

SsapKeepAliveInterval

StopBits

ValidateDns

VoiceMailParition

Cisco IP Voice Media Streaming Service Parameters

The following list contains the service parameters that can be configured for the Cisco IP Voice Media Streaming service type that were omitted from the Release 3.0 Cisco CallManager Administration Guide and online help for the Cisco CallManager application:

CFB:CallCount

CFB:RunFlag

MTP:CallCount

Cisco Enterprise Service Parameters

The following list contains the service parameters that can be configured for the Cisco Enterprise service type that were omitted from the Release 3.0 Cisco CallManager Administration Guide and Online Help:

DBL:DatabaseVersion

MessageWaitingDirn

Errors

This section contains any errors contained in the Cisco CallManager Administration Guide for Release 3.0 and/or the online help for the Cisco CallManager application. These errors will be corrected in the upcoming release of the document and online help application.

Incorrect Name of MwiSearchSpace Service Parameter

The name of the Cisco Messaging Interface (CMI) service parameter appears incorrectly in the documentation and online help application. The parameter name should be MwiSearchSpace. The documentation is also missing a description of the value to be entered. The value to enter for MwiSearchSpace is a colon-separated list of partition names. For example, dallas01:dallas02:dallas03, where dallas01, dallas02, and dallas03 are names of partitions.

Incorrect Definition for HoldType and ToneOnHoldTime

The definitions for the Cisco CallManager HoldType and ToneOnHoldTime service parameters are incorrect in the Cisco CallManager Administration Guide and online help for Cisco CallManager Release 3.0. The correct definitions are as follows:

HoldType — Determines whether the hold light flashes more rapidly for the user who placed a call on hold in the case where two different phones share the same directory number. The default value is still F.

ToneOnHoldTime — Determines the time interval between tones when a call is on hold. The default is 10 seconds, and the value range is 3 to 99999.

Service and Support

For service and support, contact Cisco Technical Assistance Center (TAC) at:

http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml

Obtaining Documentation

This section provides different methods of obtaining Cisco documentation.

World Wide Web

You can access the most current Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.

Documentation CD-ROM

Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM is updated monthly. Therefore, it is probably more current than printed documentation. The CD-ROM package is available as a single unit or as an annual subscription.

Ordering Documentation

Registered CCO users can order the Documentation CD-ROM and other Cisco Product documentation through our online Subscription Services at http://www.cisco.com/pcgi-bin/subcat/kaojump.cgi.

Nonregistered CCO users can order documentation through a local account representative by calling Cisco's corporate headquarters (California, USA) at 408 526-4000 or, in North America, call 800 553-NETS (6387).

Obtaining Technical Assistance

Cisco provides Cisco Connection Online (CCO) as a starting point for all technical assistance. Warranty or maintenance contract customers can use the Technical Assistance Center. All customers can submit technical feedback on Cisco documentation using the web, e-mail, a self-addressed stamped response card included in many printed docs, or by sending mail to Cisco.

Cisco Connection Online

Cisco continues to revolutionize how business is done on the Internet. Cisco Connection Online is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information and resources at anytime, from anywhere in the world. This highly integrated Internet application is a powerful, easy-to-use tool for doing business with Cisco.

CCO's broad range of features and services helps customers and partners to streamline business processes and improve productivity. Through CCO, you will find information about Cisco and our networking solutions, services, and programs. In addition, you can resolve technical issues with online support services, download and test software packages, and order Cisco learning materials and merchandise. Valuable online skill assessment, training, and certification programs are also available.

Customers and partners can self-register on CCO to obtain additional personalized information and services. Registered users may order products, check on the status of an order and view benefits specific to their relationships with Cisco.

You can access CCO in the following ways:

WWW: www.cisco.com

Telnet: cco.cisco.com

Modem using standard connection rates and the following terminal settings: VT100 emulation; 8 data bits; no parity; and 1 stop bit.

From North America, call 408 526-8070

From Europe, call 33 1 64 46 40 82

You can e-mail questions about using CCO to cco-team@cisco.com.

Technical Assistance Center

The Cisco Technical Assistance Center (TAC) is available to warranty or maintenance contract customers who need technical assistance with a Cisco product that is under warranty or covered by a maintenance contract.

To display the TAC web site that includes links to technical support information and software upgrades and for requesting TAC support, use www.cisco.com/techsupport.

To contact by e-mail, use one of the following:

Language
E-mail Address

English

tac@cisco.com

Hanzi (Chinese)

chinese-tac@cisco.com

Kanji (Japanese)

japan-tac@cisco.com

Hangul (Korean)

korea-tac@cisco.com

Spanish

tac@cisco.com

Thai

thai-tac@cisco.com


In North America, TAC can be reached at 800 553-2447 or 408 526-7209. For other telephone numbers and TAC e-mail addresses worldwide, consult the following web site: http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml.

Documentation Feedback

If you are reading Cisco product documentation on the World Wide Web, you can submit technical comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco.

You can e-mail your comments to bug-doc@cisco.com.

To submit your comments by mail, for your convenience many documents contain a response card behind the front cover. Otherwise, you can mail your comments to the following address:

Cisco Systems, Inc.
Document Resource Connection
170 West Tasman Drive
San Jose, CA 95134-9883

We appreciate and value your comments.