Release Notes for Cisco Unified CallManager Release 4.1(3) [Cisco Unified Communications Manager (CallManager)]

Table Of Contents

Release Notes for Cisco CallManager Release 4.1(3)

Contents

Introduction

System Requirements

Determining the Software Version

Compatibility Matrix and Supported Upgrades

Related Documentation

New and Changed Information

Cisco CallManager Installation, Upgrade, and Backup Guidelines

Installation and Upgrade

Upgrade Assistant Utility

Backup and Restore

Operating System Installation Guidelines

Upgrading to Cisco CallManager Release 4.1(3)

Before Upgrading to Cisco CallManager 4.13

Call Pickup and Group Call Pickup Enhancements

Call Pickup Enhancements

Group Call Pickup Enhancements

Other Group Pickup Enhancements

Call Transfer Enhancements

New Feature Support with Cisco IP Manager Assistant

New Service Parameter to Enable Music On Hold and Annunciator Duplex Streaming

Updated Support for Cisco IP Phones

New Hunt Pilot Configuration Parameters for Automated Alternate Routing

Support for Annex M1 over H.225 Trunks and H.323 Gateways

Security Enhancements

Support for Secure Cisco IOS MGCP Gateway Troubleshooting

Configuring Security for Voice-Mail Ports

Bulk Administration Tool Enhancements

BAT Support for Call Pickup Groups

New Call Classification Field Description

Dialed Number Analyzer Enhancements

New and Changed Information for Cisco CallManager Serviceability

Call Type Update in the CDR Search Results

New and Changed Information for Third-Party and SDK Applications

JTAPI Enhancements

CDR Records Update for Call Pickup Features

Important Notes

CSCso79248 Do Not Run installxml.vbs in Unified CM Release 3.3 and Later

Using Cisco Unity Consult Transfer with Cisco CallManager Onhook Call Transfer

Performing CAPF Operations on Cisco IP Phones via VPN Connection

Adding Cisco CallManager Servers

Locale Installer for Cisco CallManager Release 4.1(3)

Using the JTAPI Update Utility with CRS

Upgrade Requirements for CRS and Cisco CallManager 4.1

NetMeeting Calls Fail When T.38 is Advertised to NetMeeting

Cisco CallManager Installation Status Bar

CTI Route Point Considerations

Cisco CallManager Extension Mobility Scalability Update

Disabling IPSec for Cisco CallManager Upgrades

Disabling IPSec on the Cisco CallManager Server

Enabling IPSec on the Cisco CallManager Server

Support for Multicluster Integration with Active Directory

Requirement for Installation of Java Virtual Machine

JRE Installation

Resolved Caveats for Cisco CallManager - Release 4.1(3)

Using Bug Toolkit

Saving Bug Toolkit Queries

Open Caveats for Cisco CallManager - Release 4.1(3)

Documentation Updates

Errors

Java Runtime Environment

Cisco CallManager Dialed Number Analyzer Service Startup Type

Barging into Encrypted Calls with the Cisco IP Phone Model 7970

Using Valid Characters in Cisco CallManager User IDs

Cisco CallManager Security Guide Corrections

Removing a Subscriber Server from Cisco CallManager

Using Script Files to Remove a Subscriber Server from Cisco CallManager

Clarification to MLPP Interaction with Call Transfer

Correction to Forward No Coverage Internal/External Configuration

Correction to the Procedure for Adding a Cisco CallManager

Cisco Call Back Supports Lines Not Devices

Changes

Associating H.323 Devices to Users

Ad Hoc Conference Limitations

Meet-Me Conference Limitations

Omissions

CTI Monitored Lines

? Icon Displays Incorrect Online Help for Region and Calling Search Space Pop Up Windows

Name Change for the Cisco IAD 2400 Gateway Type in Cisco CallManager Administration

Route List Redundancy Configuration

Cisco IP Phone Models 7940/7960 Built-In Bridge and Device Security Considerations

CAPF Interaction When Cisco IP Phone Resets

Using Server Authentication, Third-Party CA Certificates

Using Shared Lines with Encrypted Devices

Reinstalling Dialed Number Analyzer After a Cisco CallManager Upgrade

Personal Directory

Support for the Cisco VG224 Gateway

Call Back Feature Interactions with Call Forward, iDivert, and Voice-Mail System Features

Tool for Autoregistered Phone Support Information for End Users

Time-of-Day Routing Chapter Omits Information About Defined Time Periods

Obtaining Documentation

Cisco.com

Documentation DVD

Ordering Documentation

Documentation Feedback

Cisco Product Security Overview

Reporting Security Problems in Cisco Products

Obtaining Technical Assistance

Cisco Technical Support Website

Submitting a Service Request

Definitions of Service Request Severity

Obtaining Additional Publications and Information

Release Notes for Cisco CallManager Release 4.1(3)

Updated July 09, 2009

These release notes describe the new features and caveats for Cisco CallManager release 4.1(3).

Note To view the release notes for previous versions of Cisco CallManager, go to: http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/index.htm

Before you install Cisco CallManager, Cisco recommends that you review the "Important Notes" section for information about issues that may affect your system.

For a list of the open and resolved caveats for Cisco CallManager release 4.1(3), see the "Resolved Caveats for Cisco CallManager - Release 4.1(3)" section and the "Open Caveats for Cisco CallManager - Release 4.1(3)" section. Updates for these release notes occur with every maintenance release and major release.

To access the documentation suite for voice products, refer to the following URL:

http://www.cisco.com/univercd/cc/td/doc/product/voice/

You can access the latest software upgrades and release notes for all versions of Cisco CallManager on Cisco Connection Online (CCO) at the following URL:

http://www.cisco.com/public/sw-center/sw-voice.shtml

Contents

These release notes discuss the following topics:

•Introduction

•System Requirements

•Compatibility Matrix and Supported Upgrades

•Related Documentation

•New and Changed Information

•New and Changed Information for Cisco CallManager Serviceability

•New and Changed Information for Third-Party and SDK Applications

•Important Notes

•Resolved Caveats for Cisco CallManager - Release 4.1(3)

•Open Caveats for Cisco CallManager - Release 4.1(3)

•Documentation Updates

•Obtaining Documentation

•Obtaining Technical Assistance

Introduction

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

System Requirements

Make sure that you install and configure Cisco CallManager release 4.1(3) on a Cisco Media Convergence Server (MCS).

You may also install Cisco CallManager on a Cisco-approved HP server configuration or a Cisco-approved IBM server configuration.

Note Cisco CallManager 4.1(3) requires upgraded memory for Cisco CallManager servers. See the "Upgraded Memory Requirement" section for additional information.

Caution The installation does not complete if you do not have the exact configuration.

Access the supported Cisco-approved server configuration for an IBM server or an HP server at the following URL:

http://www.cisco.com/en/US/products/hw/voiceapp/ps378/prod_brochure_list.html

For system hardware component information and system requirements, refer to Installing Cisco CallManager Release 4.1(3).

Determining the Software Version

To determine the software version of Cisco CallManager, open Cisco CallManager Administration; then, click Details on the main Cisco CallManager Administration window. The following information displays:

•Cisco CallManager System version

•Cisco CallManager Administration version

•Database information and database DLL versions

Compatibility Matrix and Supported Upgrades

You can find which application versions are compatible with Cisco CallManager release 4.1(3) and which previous release of Cisco CallManager has upgrade support by referring to the Cisco CallManager Compatibility Matrix at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/ccmcomp.htm

Note Be aware that the release of Cisco IP telephony products does not always coincide with Cisco CallManager releases. If a product does not meet the compatibility testing requirements with Cisco CallManager, you need to wait until a compatible version of the product becomes available before you can upgrade to Cisco CallManager release 4.1(3). For the most current compatibility combinations and defects, refer to the documentation that is distributed with the Cisco IP telephony products.

Related Documentation

Refer to the Cisco CallManager Document Guide for a list of documents that are related to Cisco CallManager release 4.1 at the following URL:

http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/4_1/doc_gd.

Along with the documents that are listed in the Cisco CallManager Document Guide, the following list specifies other related documents for Cisco CallManager release 4.1:

•Cisco CallManager Call Detail Record Definition

•Cisco IP Phone Services Application Development Notes

•Cisco JTAPI Installation Guide for Cisco CallManager 4.1(3)

•Cisco JTAPI Developer's Guide for Cisco CallManager 4.1(3)

•Cisco TAPI Installation Guide for Cisco CallManager 4.1(3)

•Cisco TAPI Developer's Guide for Cisco CallManager 4.1(3)

•Cisco CallManager Extension Mobility API Developer's Guide Release 4.1(3)

•Cisco CallManager 4.1(3) AXL Programming Guide

•Cisco CallManager 4.1(3) AXL Serviceability Programming Interface Guide

•Cisco CallManager Dialed Number Analyzer Guide

•Cisco WebDialer API Reference

•System Error Messages for Cisco CallManager 4.1

New and Changed Information

This following sections describe new features and changes that are pertinent to this release of Cisco CallManager. The sections may include configuration tips for the administrator, information about users, and where to find more information.

•Cisco CallManager Installation, Upgrade, and Backup Guidelines

•Operating System Installation Guidelines

•Upgrading to Cisco CallManager Release 4.1(3)

•Call Pickup and Group Call Pickup Enhancements

•Call Transfer Enhancements

•New Feature Support with Cisco IP Manager Assistant

•New Service Parameter to Enable Music On Hold and Annunciator Duplex Streaming

•Updated Support for Cisco IP Phones

•New Hunt Pilot Configuration Parameters for Automated Alternate Routing

•Support for Annex M1 over H.225 Trunks and H.323 Gateways

•Security Enhancements

•Bulk Administration Tool Enhancements

•Dialed Number Analyzer Enhancements

•New and Changed Information for Cisco CallManager Serviceability

•New and Changed Information for Cisco CallManager Serviceability

•New and Changed Information for Third-Party and SDK Applications

Cisco CallManager Installation, Upgrade, and Backup Guidelines

This section includes information about the guidelines that apply to Cisco CallManager 4.1(3) installation, upgrade, and backup and restore procedures:

•Installation and Upgrade

•Upgrade Assistant Utility

•Backup and Restore

Installation and Upgrade

Cisco CallManager 4.1(3) implements the following installation and upgrade guidelines:

•You can upgrade your servers from Cisco CallManager release 3.3(5), 4.0(2a), and 4.1(2) to Cisco CallManager release 4.1(3). See the "Compatibility Matrix and Supported Upgrades" section for more information about supported upgrade paths.

•The upgrade process requires Cisco IP Telephony operating system (OS) version 2000.2.4 with OS upgrade 2000.2.7 or a fresh installation of OS version 2000.2.7 and the latest service release 2000.2-7-sr(x). See the "Operating System Installation Guidelines" section for additional information.

This section includes the following topics:

•Upgraded Memory Requirement

•Adding Cisco CallManager Servers as Members of a Windows Domain

Upgraded Memory Requirement

The Cisco CallManager installation requires a minimum of 1 GB of memory on the Cisco CallManager publisher server. If the installation process detects less than 1 GB of memory, the installation aborts.

The installation process performs a similar check on the Cisco CallManager subscriber server; it may allow the installation to continue if it detects less than the minimum requirement.

Note To avoid system problems, such as dropped calls, make sure that your servers have a minimum of 1 GB of memory installed.

Adding Cisco CallManager Servers as Members of a Windows Domain

Cisco does not recommend adding Cisco CallManager servers as members of a Microsoft Windows domain. To prevent failures that may occur by the server being a member of a domain, Cisco CallManager 4.1(3) modifies the installation process to abort the installation and displays the following message if it detects that the server is in a Windows domain:

"The installation has detected that the server exists in a domain. When a server exists in a domain, authentication between servers may fail, or the non-default domain security policies may be too restrictive for the Cisco CallManager installation to build critical NT Accounts during an upgrade. Your server must be removed from the domain and added to a workgroup to reduce installation and upgrade errors, failures, or a total system failure, which would result in a loss of data and a complete reinstallation of Cisco CallManager. The installation will now abort."

Note Prior to this change, the installation process provided a warning about removing servers from a domain and a user option to continue or abort the installation.

To continue, you must first remove the Cisco CallManager server from the Windows domain and add it as a Workgroup member before you can install or upgrade Cisco CallManager on your server.

If your system architecture depends on servers joining a Windows domain, you must disable the Network Time Protocol (NTP) software, which Cisco CallManager installed, when you add the server as a member of a domain and use Microsoft time service. You must disable the NTP service on every server in your cluster.

Note During installation, you must choose to install Cisco CallManager as a server in a workgroup.

Note Do not make any modifications to the installed NTP configuration file (NTP.CONF); otherwise, you may encounter synchronization problems with CDRs, Traces, and Event Logging. Cisco does not support any modifications to the installed NTP configuration file.

Follow this procedure to disable the Cisco-installed NTP software on a server:

Procedure

Step 1 Choose Start > Programs > Administrative Tools > Services.

Step 2 Double-click the Network Time Protocol service.

Step 3 Choose Disabled in the Startup type field.

Step 4 Click Stop.

Step 5 Click OK.

Caution Cisco CallManager 4.1(3) will abort the installation process if it detects that the server is in a Windows domain. Therefore, you must first remove the Cisco CallManager server from the Windows domain and add it as a workgroup member before you can install or upgrade Cisco CallManager on your server.

When you complete your upgrade and you are adding the server to the Windows domain, you must disable the Cisco-installed NTP services again.

If you are joining the server to a Microsoft Windows 4.0 domain, you must also perform an additional procedure for synchronizing time. Refer to How to Synchronize the Time on a Windows 2000-Based Computer in a Windows NT 4.0 Domain at http://www.microsoft.com.

For more information, refer to http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeg67072

Upgrade Assistant Utility

Cisco CallManager Upgrade Assistant Utility 4.1(3) replaces previous versions of Cisco CallManager Upgrade Assistant Utility, release 3.3(5), 4.0(2a), and 4.1(2).

This updated release of Cisco CallManager Upgrade Assistant Utility adds support for multiple version upgrades; that is, you can use Cisco CallManager Upgrade Assistant Utility version 4.1(3) or later to detect the health of your servers before you upgrade to Cisco CallManager release 3.3(5), 4.0(2a), 4.1(2), or 4.1(3).

For additional information, refer to Using Cisco CallManager Upgrade Assistant Utility 4.1(3) at the following URL. http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/4_1/install/upgrade/index.htm

Backup and Restore

The following guidelines apply to Cisco CallManager backup and restore procedures:

•The Cisco IP Telephony Backup and Restore System (BARS) version 4.0(7) or later supports Cisco CallManager 4.1(3).

•Cisco CallManager release 3.3 and later no longer supports Cisco IP Telephony Applications Backup Utility version 3.5.

For additional information about backup and restore procedures, refer to the Cisco IP Telephony Applications Backup website at the following URL: http://www.cisco.com/univercd/cc/td/doc/product/voice/backup/.

Note Be sure to check the Cisco CallManager Compatibility Matrix for the latest information about supported compatibility combinations. See the "Compatibility Matrix and Supported Upgrades" section for more information.

Where to Find More Information

•Installing Cisco CallManager Release 4.1(3)

•Upgrading Cisco CallManager Release 4.1(3)

•Cisco IP Telephony Backup and Restore System (BARS)

Operating System Installation Guidelines

Cisco recommends that you install Cisco IP Telephony operating system version 2000.2.7 with the latest service release 2000.2-7-sr(x) before you upgrade to Cisco CallManager release 4.1(3).

Tip Refer to the following URL for information about the latest version of the Cisco-provided operating system, installation procedures, and release notes: http://www.cisco.com/univercd/cc/td/doc/product/voice/iptel_os/install/index.htm.

Note Newer servers, such as the MCS-7835-H1-IPC1, require the operating system installation kits that contain CD/DVD media. Use the operating system upgrade only to upgrade earlier versions of the operating system to the new level (service packs, hotfixes, configuration settings, BIOS, firmware, and drivers).

Where to Find More Information

•Installing the Operating System on the Cisco IP Telephony Applications Server, Version 2000.2.7

Upgrading to Cisco CallManager Release 4.1(3)

For detailed information about upgrading to Cisco CallManager 4.1(3), refer to Upgrading Cisco CallManager Release 4.1(3). For additional guidelines about Cisco CallManager installation and upgrades, see the "Cisco CallManager Installation, Upgrade, and Backup Guidelines" section.

Tip To verify which versions of Cisco CallManager are compatible for upgrade, refer to the most recent version of the Cisco CallManager Compatibility Matrix at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/ccmcomp.htm

•Valid upgrades to Cisco CallManager 4.1(3) include Cisco CallManager versions 3.3(5), 4.0(2a), and 4.1(2). (You can use updated Cisco CallManager software kit CD-ROM disks that are available for this upgrade.)

•If your server runs Cisco CallManager release 4.0(2a) or 4.1(2), you can upgrade your server to release 4.1(3) by using the web download file that is available at http://www.cisco.com/public/sw-center/sw-voice.shtml.

•If your server runs a version of Cisco CallManager release 3.2 or earlier, you must use the Cisco CallManager software kit CD-ROM disks to first upgrade every server in the cluster to the latest version of Cisco CallManager release 3.3 or 4.0 before you can upgrade to a version of Cisco CallManager release 4.1.

Note For information about upgrading to Cisco CallManager release 3.3 or 4.0, refer to the appropriate version of the Upgrading Cisco CallManager document.

•You cannot upgrade directly from Cisco CallManager release 3.2 or earlier to Cisco CallManager release 4.1.

Tip Be sure to refer to the Cisco CallManager Compatibility Matrix for important information about the supported upgrade path for each Cisco CallManager release.

Before Upgrading to Cisco CallManager 4.13

Perform the following step on the voice-mail ports to ensure proper migration:

Important: Remove any call forwarding that is set on voice-mail ports that are used only for outbound calls and message waiting indication.

Call Pickup and Group Call Pickup Enhancements

Cisco CallManager 4.1(3) introduces the following enhancements to the Call Pickup and Group Call Pickup features:

•Automatic (one-touch) Pickup—This feature provides the ability to pick up a call by pressing a single softkey on the phone. (The existing Call Pickup and Group Call Pickup features require the user to press multiple softkeys before connecting to a call that is ringing on another device.)

•Availability of three softkeys—Pickup, GPickup, and OPickup—in both onhook and offhook call states to enable one-touch invocation of these call pickup features. (The existing Call Pickup and Group Call Pickup features require the user to press the NewCall softkey before invoking a pickup feature.)

Tip By default, the standard softkey template does not include these three softkeys for the onhook call state. To enable these softkeys for the onhook call state, you must configure the Standard Feature softkey template layout. To do this, access the Standard Feature Softkey Template by using Cisco CallManager Administration (Device > Device Settings > Softkey Template). Navigate to the Cisco CallManager Administration Softkey Layout Configuration window by choosing Standard Feature > Configure Softkey Layout. Click the On Hook link in the Call States field. From the Unselected Softkeys list, choose the Group Pick Up softkey and click the right arrow to move this softkey to the Selected Softkeys list. Repeat this procedure for the Other Pickup and the Pick Up softkeys.

To enable the OPickup softkey in the offhook state, follow the procedure to configure the softkey layout. Click the Off Hook call state. From the Unselected Softkeys list, choose the Other Pickup softkey and click the right arrow to move this softkey to the Selected Softkeys list.

You can retrieve calls from a queue in your group by pressing one of the following pickup softkeys:

•Pickup—Picks up the longest alerting call in your group.

•GPickup—Picks up the longest alerting call in the group that you specify by the pickup group number that your administrator provides to you.

•OPickup—Picks up the longest alerting call in your group or any associated group without requiring a pickup group number.

Note If auto-pickup is enabled, calls that you pickup by using any of these softkeys will automatically connect to your phone. If you are not in a pickup group and you use one of these softkeys, you will hear a fast busy tone. If you do not have auto-pickup enabled, other phones can pick the call up from you while it is still ringing or while you are transferring the call.

•Other Group Pickup—This feature allows the administrator to configure other pickup groups. A new softkey, OPickup, allows you to pick up calls for your group and to also pick up calls for other associated groups that your administrator has configured. Associated pickup groups include a list of pickup groups that are defined under a specific Pickup Group. Each Pickup Group can have up to 10 associated Pickup Groups; by default, the Pickup Group itself appears first in its associated pickup group list.

•New Clusterwide Service Parameters—The following service parameters enable configuration of the enhanced call pickup features; they display under the Clusterwide Parameters (Feature - Call Pickup) section in the Cisco CallManager Administration Service Parameters Configuration window:

•Auto Call Pickup Enabled—Configure this service parameter to enable or disable the auto pickup feature by choosing one of the following options:

True—Set this service parameter to True to enable the automatic, or one-touch, pickup functionality.

False—Set this service parameter to False to use the existing call pickup and group call pickup functionality.

The default value specifies False to retain backward compatibility with earlier versions of Cisco CallManager.

Note Automatic Call Pickup, Group Call Pickup, and Other Group Pickup display as pickup calls in CDR Analysis and Reporting (CAR). See the "Call Type Update in the CDR Search Results" section for more information.

•Call Pickup Locating Timer—Configure this service parameter to search for the longest alerting call in a specific group. This parameter specifies the maximum time in seconds for a pickup to wait to get all alerting calls in the pickup groups from all the Cisco CallManager servers in the cluster.

The default value specifies 1 second.

Note CTI applications do not currently support the call pickup features, and they will not support the new softkeys that this release includes.

Refer to the Cisco CallManager Administration Guide for detailed information about these administration configuration windows.

Call Pickup Enhancements

Cisco CallManager 4.1(3) enhances the Call Pickup feature by allowing you to automatically answer a call that is ringing in your pickup group by pressing only the Pickup softkey. This enhancement streamlines call pickup functionality by removing the need to press the NewCall and Answer softkeys to complete a call pickup.

The administrator configures the pickup groups, and enables the automatic pickup functionality by configuring the Auto Call Pickup Enabled service parameter in the Cisco CallManager Administration Service Parameters Configuration window. The following valid configuration values apply:

•True—This setting enables the automatic pickup functionality; it allows call pickup functionality by pressing a single softkey.

•False—This setting disables the automatic pickup functionality. The default value specifies False to preserve backward compatibility.

You invoke the Call Pickup feature by pressing the Pickup softkey on the phone. The phone picks up the longest alerting call in the group.

1. When you hear the call ring on another phone in your group, press the Pickup softkey. (If you want to pick up the call on a line other than your primary line, go off hook on that line first; then, press Pickup.)

2. If auto-pickup is enabled for your phone, the call transfers automatically.

3. If your phone is not configured for auto-pickup, you can view the caller information and then press the Answer softkey to take the call.

Group Call Pickup Enhancements

This release enhances the Group Call Pickup feature by allowing you to answer a call that is ringing at another device in another specified pickup group by pressing the GPickup softkey and then entering the Group Pickup number of the group that you want to pick up. When auto-pickup is enabled, the Group Pickup feature allows you to perform a call pickup by pressing a single softkey followed by the Group Pickup number.

Like the Call Pickup feature, the one-touch Group Pickup feature removes the need to press the NewCall and Answer softkeys to complete a group pickup.

To enable the automatic Group Pickup feature, the administrator configures the Auto Call Pickup Enabled service parameter in the Cisco CallManager Administration Service Parameters Configuration window. See the "Call Pickup Enhancements" section for additional information.

You invoke the Group Call Pickup feature by pressing the GPickup softkey on the phone. The phone picks up the longest alerting call in the group.

1. When you hear the call ring on another phone in another group, press the GPickup softkey. (If you want to pick up the call on a line other than your primary line, go off hook on that line first; then, press GPickup.)

2. Enter the number of the group that you want to pick up.

3. If auto-pickup is enabled for your phone, the call transfers automatically.

4. If your phone is not configured for auto-pickup, you can view the caller information and then press the Answer softkey to take the call.

Note The administrator configures the pickup groups, assigns pickup group numbers, and enables auto-pickup.

Other Group Pickup Enhancements

Cisco CallManager 4.1(3) allows the administrator to provision other pickup groups for each pickup group. The OPickup softkey allows you to pick up calls in one of the associated groups that are configured as an other pickup group.

With auto-pickup enabled, the Other Pickup Group feature allows you to pick up calls in your group and in other associated groups that your administrator has configured, without the need to enter the group number. The phone will follow the sequence that the administrator configured to check each pickup group and will pick up the longest alerting call in the first group in which it finds calls.

The administrator defines the Other Group Pickup feature on the Cisco CallManager Administration Pickup Group Configuration window. The system supports up to 10 other pickup groups per pickup group.

You invoke the Other Group Pickup feature by pressing the OPickup softkey on the phone. The phone picks up the longest alerting call in the first group in which it finds calls.

1. When you hear the call ring on another phone in your group or an associated group, press the OPickup softkey. (If you want to pick up the call on a line other than your primary line, go off hook on that line first; then, press OPickup.)

2. If auto-pick is enabled for your phone, the call transfers automatically.

3. If your phone is not configured for auto-pickup, you can view the caller information and then press the Answer softkey to take the call.

Note The administrator configures your pickup groups and enables auto-pickup.

Note See the "Call Type Update in the CDR Search Results" section for information about the addition of "pickup" in the Call Type field in the Cisco CallManager Call Detail Record (CDR) search results.

Where to Find More Information

•Cisco CallManager Administration Guide

•Cisco CallManager System Guide

•Cisco CallManager Features and Services Guide

•Cisco CallManager Serviceability Administration Guide

•Cisco CallManager Serviceability System Guide

Call Transfer Enhancements

Cisco CallManager 4.1(3) introduces the following enhancements to the Call Transfer feature:

•Onhook Call Transfer—This feature provides the ability to press a single Transfer softkey and then go on hook to complete a call transfer. (The existing Call Transfer feature requires the user to press the Transfer softkey a second time to complete the function.)

•New Clusterwide Service Parameter—The following service parameter enables configuration of the Onhook Call Transfer feature; it displays under the Clusterwide Parameters (Device - Phone) section in the Cisco CallManager Administration Service Parameters Configuration window:

•Transfer On-hook Enabled—Configure this service parameter to enable or disable the Onhook Call Transfer feature by choosing one of the following options:

True—Set this service parameter to True to enable the onhook call transfer functionality; this functionality allows the user to complete a call transfer by either going on hook or by pressing the Transfer softkey.

False—Set this service parameter to False to maintain the existing call transfer functionality; that is, the user completes the call transfer by pressing the Transfer key. The default value specifies False to preserve backward compatibility with earlier versions of Cisco CallManager.

Refer to the Cisco CallManager Administration Guide for detailed information about this administration configuration window.

•Support for Onhook Call Transfer when the secondary call is in the following call states:

•Alerting

•Progress

•Connected

Note CTI applications do not support the Onhook Call Transfer feature. As it currently operates, the CTI disconnect request will disconnect a consult transfer call if the Onhook Call Transfer feature is enabled. To provide this functionality from a Cisco IP Softphone CTI application user interface, the application must map "onhook" to the CTI complete transfer request instead of the CTI disconnect request.

With Onhook Call Transfer enabled, you can invoke this feature by pressing the Transfer softkey. If you do not need to announce the caller who you are transferring, you can perform a regular call transfer by following these steps:

1. During a call, press the Transfer softkey; this action puts the call on hold.

2. Dial the number to which you want to transfer the call.

3. When you hear ringing, hang up the phone to complete the transfer.

To perform a consult transfer and announce the caller that you are transferring, follow these steps:

1. During a call, press Transfer; this action puts the call on hold.

2. Dial the number to which you want to transfer the call.

3. When the party answers, announce the call and then hang up. If the party refuses the call, press Resume to return to the original call.

Note Be sure that you do not press the EndCall softkey to complete a call transfer function; if you press the EndCall softkey before the call transfer completes, the system cancels the call transfer operation.

Where to Find More Information

•Cisco CallManager Administration Guide

•Cisco CallManager System Guide

•Cisco CallManager Features and Services Guide

New Feature Support with Cisco IP Manager Assistant

Cisco IP Manager Assistant (Cisco IPMA) does not provide support for the following feature enhancements in Cisco CallManager 4.1(3):

•Onhook Call Transfer

•Automatic Call Pickup

For additional information about Cisco IPMA, refer to the Cisco CallManager Features and Services Guide.

New Service Parameter to Enable Music On Hold and Annunciator Duplex Streaming

Cisco CallManager 4.1(3) includes a new service parameter, Duplex Streaming Enabled, for music on hold (MOH) and Annunciator. This service parameter determines whether MOH and Annunciator use duplex (two-way) or simplex (one-way) audio streams.

You can configure one of the following values for this service parameter:

•True—Set this parameter to True to set up the connection for duplex streaming media when MOH and Annunciator are used. Because certain firewalls and NAT devices require duplex audio streams, this option facilitates interoperability with these products.

•False—Set this parameter to False to set up the connection for simplex streaming media when MOH and Annunciator are used. The default value specifies False.

Set the Duplex Streaming Enabled service parameter by using Cisco CallManager Administration to access the service parameters (Service > Service Parameters). Choose the server where the Cisco CallManager application resides. On the Cisco CallManager Administration Service Parameters Configuration window, scroll down to the Cluserwide Parameters (Service) section to configure the Duplex Streaming Enabled parameter.

For more information, refer to http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeg49352.

For detailed information about configuring service parameters, refer to the Cisco CallManager Administration Guide.

Updated Support for Cisco IP Phones

Cisco CallManager 4.1(3) updates support for the following Cisco IP Phones to include the call pickup and call transfer feature enhancements:

•Cisco IP Phone 7940/ 7960

•Cisco IP Phone 7970

•Cisco IP Phone 7905/7912

The following Cisco IP Phones do not provide support for the feature enhancements in this release:

•Cisco IP Conference Station 7935/7936

•Cisco Wireless IP Phone 7920

•Cisco IP Softphone

For more information about Cisco IP Phones, refer to the following URL for the appropriate Cisco IP Phone guide for your model of Cisco IP Phone:
http://www.cisco.com/univercd/cc/td/doc/product/voice/c_ipphon/index.htm.

Where to Find More Information

•Cisco IP Phone administration guide for your model of Cisco IP Phone

•Firmware release notes for your model of Cisco IP Phone

•Cisco CallManager Administration Guide

•Cisco CallManager System Guide

•Customizing Your Cisco IP Phone on the Web

•Cisco IP Phone Guide

New Hunt Pilot Configuration Parameters for Automated Alternate Routing

Automated Alternate Routing (AAR) enables call reroute through the PSTN or other network by using an alternate number when Cisco CallManager blocks a call because of insufficient location bandwidth. Using AAR provides a benefit because the caller does not need to hang up and redial the called party.

Cisco CallManager 4.1(3) extends the Automated Alternate Routing functionality to include the hunt pilot number. (Cisco CallManager does not provide support for this enhanced functionality in Cisco CallManager version 4.x and earlier.)

In Cisco CallManager releases earlier than version 4.x, when a remote user tries to connect to the voice-messaging system in a central location and bandwidth is not available on the WAN link, Cisco CallManager could reroute the call through the PSTN gateway to the voice-messaging system.

Beginning with Cisco CallManager 4.0, AAR does not work with hunt pilots. Because the fully qualified directory number (DN) of the hunt pilot is unknown, AAR cannot initiate the reroute.

Hunt Pilot Configuration

To preserve the AAR functionality, Cisco CallManager 4.1(3) introduces the following new AAR Group Settings parameters on the Cisco CallManager Administration Hunt Pilot Configuration window:

•External Number Mask—This field provides a configurable external number mask on a hunt pilot number (similar to an external phone mask that is configured for a line). The system uses the mask to format calling line identification information for external (outbound) calls. When AAR initiates a reroute, the system applies this external number mask to the hunt pilot number to form a fully qualified DN of the called party, which allows AAR to reroute properly in out-of-bandwidth conditions.

•AAR Group—The AAR group represents the dialing area where the line/DN, the Cisco voice mail port, and the gateway are located. Choose the name of the desired AAR Group from the drop-down list box. (The names that display in this list include the names that you assigned in the Cisco CallManager Administration Automated Alternate Routing Group Configuration window, which is accessible from Route Plan > AAR Group).

Note You can enable AAR on a hunt pilot only if all members of the line group are in the same location.

You can access the AAR Group Settings parameters on the Hunt Pilot Configuration window from Cisco CallManager Administration by navigating to Route Plan > Route/Hunt > Hunt Pilot. On the Cisco CallManager Administration Hunt Pilot Configuration window, scroll down to the AAR Group Settings section.

Service Parameter Configuration

In addition to configuring the AAR Group Settings, make sure that you configure the following service parameter to enable the proper function of AAR:

•Automated Alternate Routing Enable—Configure this parameter to True to enable AAR. This clusterwide service parameter determines whether to use automated alternate routing when the system does not have enough bandwidth. Valid values include True (use AAR in low-bandwidth situations) or False (do not use AAR). The default specifies False.

You can access the Automated Alternate Routing Enable parameter on the Service Parameters Configuration window from Cisco CallManager Administration by navigating to Service > Service Parameters. Choose the server where the Cisco CallManager application resides. On the Cisco CallManager Service Parameters Configuration window, scroll down to the Clusterwide Parameters (System - CCM Automated Alternate Routing) section to configure this parameter.

For additional information about AAR, refer to the Cisco CallManager Administration Guide and the Cisco CallManager System Guide.

Where to Find More Information

•Automated Alternate Routing Group Configuration, Cisco CallManager Administration Guide

•Understanding Route Plans, Cisco CallManager System Guide

Support for Annex M1 over H.225 Trunks and H.323 Gateways

Cisco CallManager 4.1(3) extends its interoperability by adding support for QSIG tunneling via Annex M1 over H.225 trunks and H.323 gateways. With this enhancement, Cisco CallManager expands QSIG functionality by allowing you to configure tunneled protocol for H.225 trunks and H.323 gateways as you can currently configure for intercluster trunks.

Note This enhanced capability has been tested only with designated third-party switch equipment. Refer to the Cisco CallManager Compatibility Matrix for information about Annex M1 feature interoperability with third-party vendor(s): http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/ccmcomp.htm

For information about other feature support and third-party interoperability with Cisco CallManager, refer to the Cisco Interoperability Portal at the following URL: http://www.cisco.com/go/interoperability.

In this release, Cisco CallManager Administration updates enable configuration of tunneled protocol for H.225 trunks and H.323 gateways in the Cisco CallManager Administration Trunk Configuration and Gateway Configuration windows.

Trunk Configuration

From Cisco CallManager Administration, navigate to the Trunk Configuration window (Device > Trunk > Add a New Trunk) and configure the following fields:

•Tunneled Protocol—Choose QSIG from the drop-down list box to enable tunneled protocol for H.225 trunks. The default specifies None.

•Path Replacement Support—The system automatically checks this check box when you choose the QSIG option from the Tunneled Protocol drop-down list box. By default, the check box remains unchecked.

Gateway Configuration

To complete the configuration, configure the same fields for H.323 gateways. From Cisco CallManager Administration, navigate to the Gateway Configuration (Device > Gateway > Add a New Gateway) and configure the following fields:

•Tunneled Protocol—Choose QSIG from the drop-down list box to enable tunneled protocol for H.323 gateways. The default specifies None.

•Path Replacement Support—The system automatically checks this check box when you choose the QSIG option from the Tunneled Protocol drop-down list box. By default, the check box remains unchecked.

For additional information, refer to the Cisco CallManager Administration Guide and the Cisco CallManager System Guide.

Where to Find More Information

•Trunk Configuration, Cisco CallManager Administration Guide

•Gateway Configuration, Cisco CallManager Administration Guide

•Understanding IP Telephony Protocols, Cisco CallManager System Guide

Security Enhancements

This section includes information about the following security enhancements in Cisco CallManager 4.1(3):

•Support for Secure Cisco IOS MGCP Gateway Troubleshooting

•Configuring Security for Voice-Mail Ports

Support for Secure Cisco IOS MGCP Gateway Troubleshooting

Cisco CallManager 4.1(3) introduces support for secure Cisco IOS MGCP gateway troubleshooting. With this release, a new TAC debugging tool allows for the capture of encrypted MGCP messages and backhaul messages exchanged between Cisco CallManager and the secure Cisco IOS MGCP gateway. This troubleshooting tool diagnoses VoIP signaling and Real-Time Transport Protocol (RTP) streaming problems by analyzing the sniffed network traffic.

To successfully debug signaling problems, troubleshooting tools need to capture the plain text (decrypted) signaling packets that are sent to and received from the secure devices. To debug media problems, the tools need to capture the Secure Real-Time Transport Protocol (SRTP) encryption keys that are exchanged in MGCP signaling messages. Cisco CallManager 4.1(3) adds an interface to supply the plain text signaling packets for debugging Cisco IOS MGCP gateways. The gateway signaling packets include UDP-based MGCP messages and TCP-based backhaul messages.

The debugging tool establishes the encrypted Transport Layer Security (TLS) session with Cisco CallManager. Cisco CallManager and the troubleshooting tool authenticate each other by examining the certificate in the TLS session establishment. Cisco CallManager also determines whether the troubleshooting tool has administrative privileges to receive the secure signaling messages.

When a secure Cisco IOS MGCP gateway registers with Cisco CallManager, the system retrieves the configured Signal Packet Capture Mode and Packet Capture Duration settings for all devices on the gateway. When a device is configured for packet capturing, Cisco CallManager sends MGCP messages and backhaul messages for the gateway that is configured for real-time monitoring through the TLS connection. All the MGCP and backhaul messages that are sent to the debugging tool are nonencrypted in plain text format but are encrypted by a TLS session between Cisco CallManager and the troubleshooting tool.

Troubleshooting Tool Modes

The troubleshooting tool, which is configurable on a per-device basis, operates in two modes:

•Real-time operation mode—In this mode, Cisco CallManager sends decrypted (nonencrypted) messages over a secure channel to analyzing devices, which eliminates sniffing over the network. A TLS connection opens between Cisco CallManager and the debugging tool. After Cisco CallManager and the debugging tool authenticate, Cisco CallManager sends the SCCP messages (phone) or UDP and TCP backhaul messages (gateway) to all connected, real-time debugging tools for the devices that have packet capturing enabled. The debugging tool captures the SRTP packets and decrypts the packets by using the key material that is extracted from the decrypted SCCP, UDP, or TCP backhaul messages.

•Batch processing operation mode—In this mode, Cisco CallManager writes the decrypted messages to file. The system encrypts each file and, on a daily basis, it creates a new file with a new encryption key. Cisco CallManager stores the file for seven days and it stores the keys that encrypt the file in a secure location. The debugging tool uses HTTPS, administrator username and password, and the specified day to request a single encrypted file that contains the captured packets; it also requests the key information to decrypt the encrypted compressed file.

Configuring Packet Capturing in the MGCP Gateway Configuration Window

Cisco CallManager Administration supports the following Cisco IOS MGCP gateways with configurable settings for Packet Capture Mode and Packet Capture Duration on a per-port basis in the Gateway Configuration window:

•2600 XM

•2691

•28XX series including 2801, 2811, 2821, and 2851

•3660

•3725

•3745

•38XX series including 3825 and 3845

•VG224 (in MGCP mode)

The default value and range for Packet Capture Mode and Packet Capture Duration specify None (indicates that no packet capturing is occurring) and 60, respectively. Packet Capture Duration specifies the maximum number of minutes for one session of packet capturing. The default setting specifies 60; the allowable values range from 0 to 300 minutes.

Note Be aware that the settings for Packet Capture Mode and Packet Capture Duration are not configurable for the Cisco Catalyst 6000 24-port FXS gateways and the Cisco Catalyst 6000 T1/E1 VoIP gateways until these devices support SRTP.

Troubleshooting Encryption for Cisco IP Phones and Cisco IOS MGCP Gateways

Because third-party troubleshooting tools that sniff media and TCP packets do not work after you enable encryption, you must use Cisco CallManager Administration to perform the following tasks if a problem occurs:

•Analyze the packets for messages that are exchanged between Cisco CallManager and the device (phone or Cisco IOS MGCP gateway).

•Capture the SRTP packets between the devices.

•Extract the media encryption key material from the messages and decrypt the media between the devices.

Configuration Tips (for Administrators)

•You can capture packets for Cisco IP Phone models 7940, 7960, and 7970.

•You can capture packets for the Cisco IOS MGCP gateways that are listed in the "Configuring Packet Capturing in the MGCP Gateway Configuration Window" section.

•To troubleshoot encryption for Cisco IOS MGCP gateways and Cisco IP Phones, you must configure the Signaling Packet Capturing Mode and the Packet Capture Duration fields on a per-device basis in Cisco CallManager Administration.

•Configure these fields only when you are troubleshooting encrypted traffic for the device.

•Cisco strongly recommends that you do not enable packet capturing for many devices at the same time because this task may cause increased CPU usage in your Cisco CallManager server.

•You must use a network packet sniffing tool to capture the SRTP packets between the devices. After you capture the packets, set the Signal Packet Capture Mode to None and the Packet Capture Enable service parameter to False.

•After you capture the packets, contact the Cisco Technical Assistance Center (TAC) to analyze the packets.

Where to Find More Information

•Cisco CallManager Security Guide

•Gateway Configuration, Cisco CallManager Administration Guide

Configuring Security for Voice-Mail Ports

When you configure security for Cisco CallManager voice-mail ports and Cisco Unity SCCP devices, a TLS connection (handshake) opens for authenticated devices after each device accepts the other device's certificate. The system also sends SRTP streams between devices if you configure the devices for encryption.

•When the device security mode specifies authenticated or encrypted, the Cisco Unity TSP connects to Cisco CallManager through the Cisco CallManager TLS port.

•When the security mode specifies nonsecure, the Cisco Unity TSP connects to Cisco CallManager through the Cisco CallManager SCCP port.

Configuration Tips (for Administrator)

•You must run Cisco Unity 4.0(5) or later with this version of Cisco CallManager.

•You can use the Voice Mail Port Wizard to configure security for new voice-mail servers. You cannot change the Device Security Mode for existing voice-mail servers through the Voice Mail Port Wizard. If you add ports to an existing voice-mail server, the device security mode that is currently configured automatically applies to the new ports.

•To configure security by using the Voice Mail Port Wizard, choose Feature > Voice Mail > Cisco Voice Mail Port Wizard in Cisco CallManager Administration.

•To configure the Device Security Mode for a single voice-mail port, choose Feature > Voice Mail > Cisco Voice Mail Port in Cisco CallManager Administration.

•Setting the Device Security Mode enterprise parameter configures the same default security setting for all voice-mail ports and Cisco IP Phone models 7940, 7960, and 7970 in the cluster.

•In addition to the procedures that are described in the Cisco CallManager Security Guide, you must copy the Cisco Unity certificate from the Cisco Unity server to C:\Program Files\Cisco\Certificates on each server in the cluster, as described in Cisco CallManager Integration Guide for Cisco Unity 4.0. After you copy the certificate, restart the Cisco CallManager service in Cisco CallManager Serviceability by navigating to Application > Cisco CallManager Serviceability > Tools > Control Center.

•In addition to Cisco CallManager Administration configuration tasks, you must perform security tasks for Cisco Unity by using the Cisco Unity Telephony Integration Manager; for information about performing these tasks, refer to Cisco CallManager Integration Guide for Cisco Unity 4.0.

•If Cisco Unity certificates expire or change for any reason, ensure that the new certificates exist on each server in the cluster. The TLS authentication fails when certificates do not match.

•The setting that you specify in the Cisco Unity Telephony Integration Manager must match the voice-mail port Device Security Mode that is configured in Cisco CallManager Administration.

•Changing the device security mode requires a reset of Cisco CallManager devices in Cisco CallManager Administration and a restart of the Cisco Unity Integration Manager. If you change the setting in Cisco CallManager Administration, you must also change the setting in Cisco Unity.

Where to Find More Information

•Cisco CallManager Security Guide

•Cisco CallManager Integration Guide for Cisco Unity 4.0

Bulk Administration Tool Enhancements

The Bulk Administration Tool (BAT) version 5.1(4) supports Cisco CallManager release 4.1(3) and provides support for the following features and enhancements:

•BAT Support for Call Pickup Groups

•New Call Classification Field Description

BAT Support for Call Pickup Groups

BAT 5.1(4) now provides support for call pickup groups. The following guidelines apply when you use BAT to configure call pickup groups:

•You can create a comma separated value (CSV) file through BAT.xlt, or you can create a custom text-based CSV file to add call pickup group settings for the first time.

•To update, delete, or add subsequent call pickup group settings, you can edit an existing CSV file or create a custom text-based CSV file.

•In the file/spreadsheet, make sure that you only designate a single line for each pickup group name and corresponding setting. (Do not enter two or more pickup group names on a single line.)

For example, use the following format when you enter information for pickup groups:

(Pickup Group Name, Pickup Group Number, Partition, Other Pickup Group Name-Member1... Other Pickup Group Name-Member10)

Marketing,7815,Part1,Marketing,Managers,Training

•When you add new pickup groups, you must complete all required fields; for example, pickup group name, pickup group number, and partition. You must provide the information in the file for all mandatory entries.

•You must use separate CSV files when you need to insert and update records.

•When you delete information from a file and leave a blank value in its place, the information remains in the Cisco CallManager database; that is, a blank value does not overwrite an existing value in the database. You must update the value to overwrite the existing value in the database.

•Make sure that you copy the appropriate CSV files into the correct directory. BAT provides the following directory for call pickup groups on the Cisco CallManager publisher server: C:\BatFiles\CPG\Insert\.

•Whenever you create or change a CSV file, you must insert the CSV file in BAT.

New Call Classification Field Description

The BAT 5.1(4) web interface reflects a name change for the Device Destination field for non-FXS endpoints for a VG200 gateway to Call Classification. With this change, the Call Classification field replaces the Device Destination field in the gateway template.

You can use the following Call Classification field description when you are adding or updating values for the E&M ports for T1 CAS trunks on a Cisco VG200 gateway and when you are adding or updating values for T1 PRI or E1 PRI trunks on a Cisco VG200 gateway.

Table 1 Call Classification Field Description

Field

Description

Call Classification

From the drop-down list box, choose an option to configure the device as on net, off net, or system default. If you chose `Use System Default' at the device level, the system uses the value of the service parameter to determine whether the device is internal (on net) or external (off net).

For additional information about BAT features and functionality, refer to the Bulk Administration Tool User Guide.

Where to Find More Information

•Working with Call Pickup Groups, Bulk Administration Tool User Guide

•Working with Gateways and Ports, Bulk Administration Tool User Guide

•Bulk Administration Tool User Guide

Dialed Number Analyzer Enhancements

Dialed Number Analyzer (DNA) enables analysis of a configured Cisco CallManager dial plan (one pattern at a time) and provides details about the call flow of dialed digits. In the pre-deployment phase, you can use the tool to identify problems in a complex dial plan; in the post-deployment phase, you can use the tool to identify real-time problems in the call flow of dialed digits.

Cisco CallManager 4.1(3) updates DNA to support analysis of multiple dialed numbers by providing an interface to allow multiple analysis and dial plan bulk testing, along with generation of a corresponding bulk output report.

DNA Analysis by Using Multiple Analyzer

In this release of Cisco CallManager, DNA provides a Multiple Analyzer window that allows you to choose a CSV file that contains a list of data that is required for analysis. DNA then processes the CSV file and displays the bulk output results.

During DNA installation, the template, DNATemplate.zip, loads on the server. Use this template to create a CSV file that contains multiple sets of calling party numbers and corresponding dialed digits, calling search spaces, device time zones, time zones, and date and time information. You can upload or download these files by using the Multiple Analyzer window in DNA.

Note The system supports a maximum of 500 entries in the CSV file for multiple analysis.

Refer to the Cisco CallManager Dialed Number Analyzer Guide for additional information about Multiple Analyzer, include creating a CSV input file by using the DNA template, uploading or downloading the files, and viewing and analyzing the file contents.

Caution The multiple analysis feature consumes a large amount of CPU resources, which may greatly impact database performance. Cisco strongly recommends that you perform multiple analysis only during offpeak hours to minimize network performance issues.

Where to Find More Information

•Cisco CallManager Dialed Number Analyzer Guide

New and Changed Information for Cisco CallManager Serviceability

This section describes the following new serviceability features and changes that pertain to this release of Cisco CallManager:

•Call Type Update in the CDR Search Results

Call Type Update in the CDR Search Results

Cisco CallManager 4.1(3) updates CDR Analysis and Reporting (CAR) by populating the Call Type field in the Cisco CallManager Call Detail Record (CDR) search results with "pickup" for automatic pickup, automatic group pickup, and automatic other pickup calls. CAR can distinguish between automatic pickup/group pickup calls and forwarded calls because the CDRs distinguish between these call types.

With this addition, the CDR search provides the following Call Type field descriptive information:

The type of call: simple, transfer, forward, pickup, or conference.

As in previous releases, CDRs still categorize pickup, group pickup, and other pickup calls as forwarded calls, and CAR populates the Call Type field for these call types with forward.

For additional information about CDR Analysis and Reporting (CAR), refer to the Cisco CallManager Serviceability Administration Guide. For more information about automatic pickup and automatic group pickup, see the "Call Pickup and Group Call Pickup Enhancements" section and refer to the Cisco CallManager Administration Guide and the Cisco CallManager System Guide.

Where to Find More Information

•Cisco CallManager Serviceability System Guide

•Cisco CallManager Serviceability Administration Guide

•Cisco CallManager Administration Guide

•Cisco CallManager System Guide

New and Changed Information for Third-Party and SDK Applications

This section describes the following new Cisco CallManager and third-party SDK applications features and changes that pertain to this release of Cisco CallManager:

•JTAPI Enhancements

•CDR Records Update for Call Pickup Features

JTAPI Enhancements

Cisco CallManager 4.1(3) includes support for the Microsoft Windows 2003 operating system in the JTAPI InstallShield.

Refer to the Cisco JTAPI Installation Guide for a complete list of supported operating systems.

Where to Find More Information

For information about third-party and SDK applications, refer to the Cisco JTAPI Developer Guide for Cisco CallManager 4.1(3) at the following URL:

http://www.cisco.com/univercd/cc/td/doc/product/voice/vpdd/cdd/4_1/

CDR Records Update for Call Pickup Features

With Cisco CallManager 4.1(3), the enhanced content of the CDR records provides support for the automatic pickup feature. (See the "Call Pickup and Group Call Pickup Enhancements" section for more information about the call pickup enhancements.)

Automatic Pickup

The new automatic pickup feature generates only two CDR records:

•CDR for the ringing call—The system sets the origTerminationOnBehalfOf and destTerminationOnBehalfOf fields to 16 (Pickup); this setting indicates that the call was terminated on behalf of the Pickup feature.

•CDR for the final connected call that is picked up—The system sets the lastRedirectOnBehalfOf and joinOnBehalfOf fields to 16 (Pickup); this setting indicates that the call was joined on behalf of the Pickup feature. The lastRedirectDn contains the party that was ringing when the call was picked up. The lastRedirectRedirectReason contains the redirect reason 5 (Pickup).

Both CDRs have the same Call ID.

Pickup

The CDRs remain the same for the existing call pickup features (Call Pickup, Group Call Pickup, and Other Group Pickup).

The existing Pickup features generate only one CDR record. The system sets the origCalledPartyRedirectOnBehalfOf, lastRedirectRedirectOnBehalfOf, and joinOnBehalfOf fields to 5 (Call Forward); this setting indicates that the Call Forward feature redirected the call. The origCalledPartyRedirectReason and lastRedirectRedirectReason contain the redirect reason code of 5 (Pickup).

Where to Find More Information

•Cisco CallManager Serviceability System Guide

•Cisco CallManager Serviceability Administration Guide

Important Notes

The following section contains important information that may have been unavailable upon the initial release of documentation for Cisco CallManager release 4.1.

•CSCso79248 Do Not Run installxml.vbs in Unified CM Release 3.3 and Later

•Using Cisco Unity Consult Transfer with Cisco CallManager Onhook Call Transfer

•Performing CAPF Operations on Cisco IP Phones via VPN Connection

•Adding Cisco CallManager Servers

•Locale Installer for Cisco CallManager Release 4.1(3)

•Using the JTAPI Update Utility with CRS

•Upgrade Requirements for CRS and Cisco CallManager 4.1

•NetMeeting Calls Fail When T.38 is Advertised to NetMeeting

•Cisco CallManager Installation Status Bar

•CTI Route Point Considerations

•Cisco CallManager Extension Mobility Scalability Update

•Disabling IPSec for Cisco CallManager Upgrades

•Support for Multicluster Integration with Active Directory

•Requirement for Installation of Java Virtual Machine

CSCso79248 Do Not Run installxml.vbs in Unified CM Release 3.3 and Later

In previous releases, during the Unified CM installation, the installxml.vbs VB script got used to parse all the display instances and rules in the XML files, and upload the data into a table in the default database. In Unified CM Release 3.3 and later, the DBInstall.dll function CInstallXML performs the parsing of the XML files.

The troubleshooting guide for Cisco Unified CallManager (and Cisco CallManager) suggests that you can initialize the installxml.vbs script to fix problems with blank parameters after an upgrade. Do not initialize the installxml.vbs script as the troubleshooting guide recommends. Initializing the script erases all service parameters on the server.

Caution Cisco Unified CM releases 3.3.x or later do not use the installxml.vbs script. Running this script erases all Service Parameters in the server.

Using Cisco Unity Consult Transfer with Cisco CallManager Onhook Call Transfer

When Cisco Unity is configured to perform a consult transfer of an incoming call, the called party has the option to either press "1" to accept the call or "2" to send the call to voice mail.

Cisco CallManager 4.1(3) adds the Onhook Call Transfer feature, which has interactions with the transfer function of Cisco Unity.

•When the Transfer On-hook Enabled service parameter is set to False (default), this functionality works as designed.

•However, if you configure the Transfer On-hook Enabled service parameter to True (to enable the onhook call transfer functionality), Cisco Unity completes the call transfer instead of sending the call to voice mail when the called party presses "2."

This problem occurs when you use Cisco Unity version 4.04 and Cisco CallManager version 4.1(3).

For more information, refer to http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCsa71042

For more information about the Onhook Call Transfer feature, see the "Call Transfer Enhancements" section.

Performing CAPF Operations on Cisco IP Phones via VPN Connection

When you perform any Certificate Authority Proxy Function (CAPF) operations, such as installing, upgrading, or deleting locally significant certificates (LSC), on a Cisco IP Phone that connects to Cisco CallManager via VPN, you must take special action to ensure that the CAPF phone port is not blocked. (If the CAPF phone port is blocked, all CAPF operations will fail.)

Note The Cisco IP Phone uses the CAPF phone port to connect to CAPF. You cannot perform any certificate operations through CAPF when the CAPF phone port is blocked.

Before any CAPF operations can occur, CAPF must authenticate and communicate with the Cisco IP Phone by using the port that you specify in Cisco CallManager Administration. (This port value can be found in the "CAPF Phone Port" field on the Cisco CallManager Administration Enterprise Parameters Configuration window by accessing System > Enterprise Parameters and scrolling down to the Security Parameters section.)

After CAPF authentication, the phone can download its LSC and register with Cisco CallManager in secure mode. If the Cisco CallManager cluster is configured for mixed-mode and the phone is configured for secure mode (authenticated or encrypted), the phone can download its certificate from CAPF before its security mode is turned on. If the phone cannot download its LSC, it cannot register with Cisco CallManager in secure mode but it retains the ability to register with Cisco CallManager in non-secure mode.

Performing any CAPF operation on a Cisco IP Phone that connects to Cisco CallManager via VPN will fail if the CAPF phone port is blocked for any reason, such as by a firewall. When this blockage occurs, the phone cannot download its LSC from CAPF and it cannot register with Cisco CallManager in secure mode even though the device security mode is authenticated or encrypted. In this situation, the phone displays the "Registration Rejected" message.

To resolve this situation, you can perform either of the following actions:

•Configure the firewall to open up the CAPF phone port that is specified in Cisco CallManager Administration to allow connection to the CAPF phone port.

•Connect the phone to the corporate network to perform all security-related configuration tasks, including CAPF operations; then, plug the phone into the VPN network to enable secure mode functionality with Cisco CallManager. (This action enables the phone to work with the current certificate; if the CAPF phone port is blocked by a firewall, any new CAPF-related operations on the phone will fail.)

For more information, refer to http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCsa67823

Where to Find More Information

•Cisco CallManager Security Guide

Adding Cisco CallManager Servers

In Cisco CallManager Administration, make sure that you add each server only once on the Server Configuration window (System > Server). If you add a server by using the host name and add the same server by using the IP address, Cisco CallManager cannot accurately determine component versions for the server after a Cisco CallManager upgrade. If you have two entries in Cisco CallManager Administration for the same server, delete one of the entries before you upgrade.

Locale Installer for Cisco CallManager Release 4.1(3)

For optimal performance, be sure that you use Cisco IP Telephony Locale Installer version 4.1(3) with Cisco CallManager release 4.1(3).

Note Be aware that all phrases may not display in the desired locale when you install this version of Locale Installer on a system that is running anything other than Cisco CallManager 4.1(3); that is Cisco CallManager 4.1(3) SR(x) and later or Cisco CallManager 4.1(2) SR(x) and earlier.

Refer to the readme file that is posted with the Cisco IP Telephony Locale Installer software on http://www.cisco.com for the complete list of supported languages.

For a list of available locale installers that are supported for use with specific versions of Cisco CallManager, go to the following URL: http://www.cisco.com/kobayashi/sw-center/telephony/callmgr/locale-installer.shtml.

Tip When using locales, Cisco recommends that you wait until the locale installer that specifically supports Cisco CallManager 4.1(3) becomes available before you upgrade your system to this release of Cisco CallManager. Because some incompatibilities may exist between releases, be sure to only use the locale installer that specifically supports your version of Cisco CallManager.

Note Each release of Cisco CallManager may support a different number of locales. You can find the full suite of Locale Installers that work with Cisco CallManager 4.1(3) at http://www.cisco.com about eight to ten weeks after the English version becomes available. You can download the Locale Installers for all languages that are supported with Cisco CallManager 4.1 from the following location: http://www.cisco.com/pcgi-bin/tablebuild.pl/callmgr-locale-41.

Where to Find More Information

•Cisco CallManager Features and Services Guide

Using the JTAPI Update Utility with CRS

Cisco Customer Response Solutions (CRS) servers include a JTAPI Update Utility that performs synchronization of the Cisco CallManager Plugin with the CRS server and the Cisco Agent Desktop (CAD). You must run this update tool to ensure successful operation of your CRS server.

If you have CRS or Cisco CallManager Extended Services installed (either co-located with the Cisco CallManager server or on a separate server) and you upgrade and/or install Cisco CallManager, you must take additional action to ensure plug-in synchronization.

Because an upgrade to a Cisco Call Manager server may include an updated JTAPI Plugin component, make sure that you run the JTAPI Update Utility on the CRS server to upgrade the JTAPI client. Running the JTAPI Update Utility on your CRS server, after you upgrade Cisco CallManager, ensures that the JTAPI Plugin is properly installed.

Note Simply executing the plug-in installer to install the JTAPI Plugin on the CRS server (instead of running the JTAPI Update Utility) does not copy the jtapi.jar file to the CRS share folder, leaving the update in an unfinished state.

For detailed information about the JTAPI Update Utility, refer to the Cisco Customer Response Applications Administrator Guide at http://www.cisco.com/univercd/cc/td/doc/product/voice/sw_ap_to/apps_3_5/english/admn_app/apadm35.pdf.

Upgrade Requirements for CRS and Cisco CallManager 4.1

Cisco CRS customers who currently run CRS version 3.5(1) with Cisco CallManager 4.0 (either co-located with the Cisco CallManager server or on a separate server) must upgrade their CRS servers to version 3.5(2) before they upgrade to Cisco CallManager 4.1.

Note Because the CRS 3.5(1) installer is not compatible with Cisco CallManager 4.1, the CRS 3.5(1) installer may fail if you run it after you upgrade your server to Cisco CallManager 4.1.

Because of the incompatibility issue, you must rerun the CRS 3.5(1) installer after deployment in the following situations:

•Disaster recovery where stabilizing the system requires a reinstallation of the CRS 3.5(1) software—In this case, a restore from backup requires CRS 3.5(1); otherwise, historical data and some configuration data will be lost.

•Upgrade of the CRS product license to obtain additional functionality—In this case, the CRS 3.5(1) installer fails, but the CRS 3.5(2) installer succeeds.

Note CRS 3.5(2) is compatible with both Cisco CallManager 4.0 and Cisco CallManager 4.1.

For more information, refer to http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCef83104

NetMeeting Calls Fail When T.38 is Advertised to NetMeeting

When a call is made to or from NetMeeting, and the calling/called device advertises T.38 to NetMeeting in the Terminal Capability Set (TCS), NetMeeting does not correctly acknowledge the TCS, and the call times out. If T.38 is not advertised to NetMeeting, the call completes.

To ensure successful call completion, configure the calling/called device to not advertise T.38 to NetMeeting or use a calling/called device that does not advertise T.38.

For more information, refer to http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCef36817.

Cisco CallManager Installation Status Bar

During the installation or upgrade of Cisco CallManager 4.1, you may see the installation program reset the status bar multiple times. The progress of the status bar may reset as each software package is being installed and as the installation program configures your machine. Make sure that you do not reboot the server unless the installation process prompts you to do so.

CTI Route Point Considerations

When a CTI route point contains 200 calls, the additional calls (above 200) exhibit slower performance. If the CTI application needs more than 200 calls, Cisco recommends that you configure multiple CTI route points.

Note Although Cisco CallManager Administration, Directory Number Configuration, provides a default value of 5000 for the Maximum Number of Calls parameter, degradation begins to display after 200 active calls.

Cisco CallManager Extension Mobility Scalability Update

The Cisco CallManager Features and Services Guide states that Cisco CallManager Extension Mobility supports a maximum of 2000 sequential login and logout operations per hour. This number represents the minimum supported logins or logouts.

Cisco CallManager Extension Mobility that is running on larger hardware platforms, such as the MCS-7845, may support more sequential login (or logout) operations per hour. For example, the MCS-7845 can support 4500 login or logout operations per hour.

Disabling IPSec for Cisco CallManager Upgrades

Cisco recommends that you temporarily disable the IP Security Protocol (IPSec) before you upgrade your Cisco CallManager server to release 4.1.

•If you enabled IPSec on your server, you must perform the configuration steps as shown in "Disabling IPSec on the Cisco CallManager Server" section to disable this security protocol before you begin the upgrade process.

•After you complete the Cisco CallManager upgrade, you must reenable IPSec. See the "Enabling IPSec on the Cisco CallManager Server" section for configuration information.

Disabling IPSec on the Cisco CallManager Server

To disable IPSec, perform the following steps:

Procedure

Step 1 Choose Start > Programs > Administrative Tools > Local Security Policy.

Step 2 Double-click IP Security Policies on Local Machine to view the local security settings.

Tip You can enter the secpol.msc command from a command prompt as an alternative to following Step 1 and Step 2.

Step 3 Look for the Policy Assigned column, which displays in the right window pane, to identify the active policy for the Cisco CallManager server.

Tip Be sure to make a note of the active security policy, so you can enable this policy after the upgrade.

Step 4 Right-click the active policy and choose unassign.

Enabling IPSec on the Cisco CallManager Server

After you complete the Cisco CallManager upgrade to release 4.1, you must reenable IPSec on your Cisco CallManager server.

To enable IPSec, perform the following steps:

Procedure

Step 1 Choose Start > Programs > Administrative Tools > Local Security Policy.

Step 2 Double-click IP Security Policies on Local Machine to view the local security settings.

Tip You can enter the secpol.msc command from a command prompt as an alternative to following Step 1 and Step 2.

Step 3 Look for the Policy Assigned column, which displays in the right window pane, to identify the policy for the Cisco CallManager server.

Step 4 Right-click the policy that was previously active on your server and choose assign.

Support for Multicluster Integration with Active Directory

Cisco supports the integration of multiple Cisco CallManager clusters with the same Microsoft Windows Active Directory (AD) forest with the following caveats:

•Because of the complex nature of a large number of potential combinations of customer AD configurations and Cisco voice applications that can be deployed together with Cisco CallManager and that also use the directory, you must adhere to specific guidelines.

•Before you proceed with a multicluster integration, you must contact your local Cisco sales team to initiate a request for this specific support.

•When you deploy other Cisco voice applications besides Cisco CallManager, including CAR, Multilevel Administration (MLA), Cisco IP Contact Center (IPCC), and Cisco IPCC Express, additional limitations may apply. For additional information, refer to the applicable documentation and release notes for your specific product.

For more information, refer to http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeh02155

Requirement for Installation of Java Virtual Machine

The following requirement went into effect with Cisco CallManager 4.1.

The Microsoft Java Virtual Machine (MSJVM) technology allows Java applications to run on Microsoft Windows-based computers. Some versions of Microsoft Internet Explorer (a component of the Windows operating systems) included MSJVM, but Microsoft has since discontinued distribution of MSJVM in its software and announced end-of-life support for the product.

MSJVM was installed by default in all client workstation versions of the current Windows operating systems, except for the following versions:

•Windows XP Professional with SP1 slipstreamed into the installation

•Windows 2000 Server/Professional with SP4 slipstreamed into the installation

Note Because the Cisco CallManager Administration windows depend on remote scripts, which depend on the JVM for web interaction, Cisco CallManager requires the use of JVM on the client machine to ensure that the Cisco CallManager Administration windows display correctly.

•If your client machine runs MSJVM, you can continue to use the existing configuration to browse into the Cisco CallManager Administration windows and perform administration tasks.

•If you do not have MSJVM installed on your client machine (or if you receive an error message stating that Cisco CallManager cannot detect JVM on the client machine), and you need to perform Cisco CallManager Administration tasks, you must install and configure the Sun Microsystems Java Virtual Machine (JVM) on the client machine. (The Sun JVM comprises part of the Java 2 Runtime Environment—JRE.) In addition, you must configure the browser security to be Java-enabled. See the "JRE Installation" section for information about installing JRE on the client machine.

•If you are not sure whether MSJVM is installed on the client machine, you can install the Sun J2RE anyway. You would then have two Java Runtime Environments that are installed and running on your machine.

Tip If you run two separate JVM products (MSJVM and Sun J2RE) on your client machine, be sure to download and install patches and security updates for each JVM from the appropriate software vendor (Microsoft and Sun).

JRE Installation

As part of the Cisco CallManager installation, the system provides the Sun JRE client software in a zip file that is installed on the Cisco CallManager server.

Note Windows XP/XP Professional includes a built-in tool that handles zip files. If you use Windows 2000 as your operating system, you must obtain a separate compression utility (such as WinZip) to store and access zip files.

Tip Be sure to install Cisco IP Telephony operating system version 2000.2.7 with the latest service release 2000.2-7-sr(x) before you upgrade to Cisco CallManager release 4.1(3). See the "Operating System Installation Guidelines" section for additional information.

To install the JRE software on the client PC, follow these steps:

Procedure

Step 1 From the Cisco CallManager server, navigate to the C:\utils\JRE directory and search for the J2RE_Client_<jre version>.zip file.

The following shows an example of the zip file name:
J2RE_Client_1.4.2_05.zip
Note Only the Cisco CallManager Administrator can access the JRE software on the Cisco CallManager server; to enable access to other users, copy the J2RE_Client_<jre version>.zip file to a server that can be shared by all users.

Step 2 Right-click the J2RE_Client_<jre version>.zip file and click Copy to copy the file to your client PC.

Step 3 Double-click the J2RE_Client_<jre version>.zip file to unzip the Sun J2RE installation executable.

Step 4 Double-click the installation executable file on the client PC.

The following shows an example of the installation executable file name:
j2re-1_4_2_04-windows-i586-p.exe
Note The exact name of the installation executable file changes with each version as the new version number is incorporated into the name.

The JRE software installs in the C:\Program Files\Cisco\Java\JRE directory.

Note Refer to the Cisco CallManager Administration Guide for detailed information about the updated administration configuration windows.

Where to Find More Information

•Cisco CallManager Administration Guide

Resolved Caveats for Cisco CallManager - Release 4.1(3)

You can find the latest resolved caveat information for Cisco CallManager release 4.1(3) by using Bug Toolkit, which is an online tool that is available for customers to query defects according to their own needs.

Tip You need an account with Cisco.com (Cisco Connection Online) to use the Bug Toolkit to find open and resolved caveats of any severity for any release.

To access the Bug Toolkit, log on to http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl.

This section includes the following topics:

•Using Bug Toolkit

•Saving Bug Toolkit Queries

Using Bug Toolkit

To access Bug Toolkit, you need the following items:

•Internet connection

•Web browser

•Cisco.com user ID and password

To use Bug Toolkit, follow this procedure.

Procedure

Step 1 To access the Bug Toolkit, go to http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl.

Log on with your Cisco.com user ID and password.

Step 2 Click the Launch Bug Toolkit hyperlink.

Step 3 If you are looking for information about a specific caveat, enter the ID number in the "Enter known bug ID:" field.

To view all caveats for Cisco CallManager, go to the "Search for bugs in other Cisco software and hardware products" section, and enter Cisco CallManager in the Product Name field. Alternatively, you can scroll through the product name list and click Cisco CallManager.

Step 4 Click Next. The Cisco CallManager search window displays.

Step 5 Choose the filters to query for caveats. You can choose any or all of the available options:

a. Choose the Cisco CallManager version:

•Choose the major version for the major releases (such as, 4.1, 4.0, 3.3).

A major release contains significant new features, enhancements, architectural changes, and/or defect fixes.

•Choose the revision for more specific information; for example, choosing major version 4.1 and revision version 3 queries for release 4.1(3) caveats.

A revision (maintenance) release primarily contains defect fixes to address specific problems, but it may also include new features and/or enhancements.

b. Choose the Features or Components to query; make your selection from the "Available" list and click Add to place your selection in the "Limit search to" list.

•To query for all Cisco CallManager caveats for a specified release, choose "All Features" in the left window pane.

Note The default value specifies "All Features" and includes all of the items in the left window pane.

•To query only for Cisco CallManager-related caveats, choose "ciscocm" and then click Add.

•To query only for phone caveats, choose "ciscocm-phone" and then click Add.

•To query only for gateway caveats, choose "voice-gateway" and then click Add.

c. Enter keywords to search for a caveat title and description, if desired.

Note To make queries less specific, use the All wildcard for the major version/revision, features/components, and keyword options.

d. Choose the Set Advanced Options, including the following items:

•Bug Severity level—The default specifies 1-3.

•Bug Status Group—Check the Fixed check box for resolved caveats.

•Release Note Enclosure—The default specifies Valid Release Note Enclosure.

e. Click Next.

Bug Toolkit returns the list of caveats on the basis of your query.

•You can modify your results by submitting another query and using different criteria.

•You can save your query for future use. See the "Saving Bug Toolkit Queries" section.

Note For detailed online help with Bug Toolkit, click Help on any Bug Toolkit window.

Saving Bug Toolkit Queries

Bug Toolkit allows you to create and then save your queries to monitor a specific defect or network situation. You can edit a saved search at any time to change the alert conditions, the defects being watched, or the network profile.

Follow this procedure to save your Bug Toolkit queries.

Procedure

Step 1 Perform your search for caveats, as described in the "Using Bug Toolkit" section.

Step 2 In the search result window, click the This Search Criteria button that displays at the bottom of the window.

A new window displays.

Step 3 In the Name of saved search field, enter a name for the saved search.

Step 4 Under My Bug Groups, use one of the following options to save your defects in a bug group:

•Click the Existing group radio button and choose an existing group name from the drop-down list box.

•Click the Create new group named: radio button and enter a group name to create a new group for this saved search.

Note This bug group will contain the bugs that are identified by using the search criteria that you have saved. Each time that a new bug meets the search criteria, the system adds it to the group that you chose.

Bug Toolkit saves your bugs and searches, and makes them available through the My Stuff window. (The My Stuff window allows you to view, create, and/or modify existing bug groups or saved searches. Choose the My Stuff link to see a list of all your bug groups.)

Step 5 Under Email Update Options, you can choose to set optional e-mail notification preferences if you want to receive automatic updates of a bug status change. Bug Toolkit provides the following options:

•Do NOT send me any email updates—If you choose this default setting, Bug Toolkit does not send e-mail notifications.

•Send my updates to:—Click the radio button to choose this option to send e-mail notifications to the user ID that you enter in this field. Additional notification options include

•Updates as they occur—Bug Toolkit provides updates that are based on status change.

•Weekly summaries—Bug Toolkit provides weekly summary updates.

•Apply these email update options to all of my saved searches—Check this check box to use these e-mail update options for all of your saved searches.

Step 6 To save your changes, click Save.

Step 7 A window displays the bug group(s) that you have saved. From this window, you can click a bug group name to see the bugs and the saved searches; you can also edit the search criteria.

Note For complete Cisco IP Phone firmware release note information, refer to the applicable firmware release notes for your specific model IP phone at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_ipphon/english/.

Open Caveats for Cisco CallManager - Release 4.1(3)

Table 2 describes possible unexpected behaviors by Cisco CallManager release 4.1(3), sorted by component. Unless otherwise noted, these caveats apply to all Cisco CallManager 3.0 releases up to and including Cisco CallManager release 4.1(3).

Tip For more information about an individual defect, click the associated Identifier in Table 2 to access the online record for that defect, including workarounds.

Understanding the Fixed-in Version and the Integrated-in Fields in the Online Defect Record

When you open the online record for a defect, you may see data in the "First Fixed-in Version" or "Integrated-in" fields. The information that displays in these fields identifies the list of Cisco CallManager interim versions in which the defect was fixed. These interim versions then get integrated into Cisco CallManager releases.

Some more clearly defined versions include identification for Engineering Specials (ES) or Service Releases (SR); for example 03.3(04)ES29 and 04.0(02a)SR1. However, the version information that displays for the Cisco CallManager maintenance releases may not be as clearly identified.

The following examples show how you can decode the maintenance release interim version information. These examples show you the format of the interim version along with the corresponding Cisco CallManager release that includes that interim version. You can use these examples as guidance to better understand the presentation of information in these fields.

•003.003(002.079) = Cisco CallManager release 3.3(3)

•003.003(003.144) = Cisco CallManager release 3.3(4)

•004.000(000.123) = Cisco CallManager release 4.0(1)

•004.000(001.008) = Cisco CallManager release 4.0(2)

•004.001(002.201) = Cisco CallManager release 4.1(3)

Note Because defect status continually changes, be aware that Table 2 reflects a snapshot of the defects that were open at the time this report was compiled. For an updated view of open defects, access Bug Toolkit and follow the instructions as described in the "Using Bug Toolkit" section.

Tip Bug Toolkit requires that you have an account with Cisco.com (Cisco Connection Online). By using the Bug Toolkit, you can find caveats of any severity for any release. Bug Toolkit may also provide a more current listing than this document provides. To access the Bug Toolkit, log on to http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl.

Table 2 Open Caveats for Cisco CallManager Release 4.1(3)

Identifier

Headline

Component: Attendant Console

CSCeg65803

Attendant Console incorrectly displays an error message when a high-precedence call preempts a normal call on the Attendant Phone.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeg65803

CSCsa61136

Call attempts continue to increase when the pilot point is called and when the pilot point and the associated device are in different locations.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCsa61136

CSCsa65580

Transfer intermittently does not ring the destination phone and returns the initial caller to the line when you do a consult transfer via the Attendant Console GUI.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCsa65580

Component: AXL

CSCsa66735

Running the AXL updateCallPickupGroup request fails when you add members with the same priority as that of existing members.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCsa66735

CSCsa68093

The AXL getPhoneResponse does not return the same IP Phone Service URL as saved in the addPhone AXL API.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCsa68093

CSCsa69800

AXL returns an error if you try to add a second, different route pattern after you successfully insert the first route pattern.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCsa69800

CSCsa70109

Sending consecutive AXL requests in quick succession causes the system to not respond to some requests.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCsa70109

Component: BAT

CSCsa66174

BAT fails to import phones when the Alerting Name field contains a comma.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCsa66174

CSCsa71691

You cannot delete phones that use a shared DN when you the shared DN is included in the custom file option.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCsa71691

Component: Call Processing

CSCeh04163

CAC: Bandwidth that the system consumes before fallback to a secondary Cisco CallManager server gets reset during fallback.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeh04163

CSCsa70684

CAC: Cisco CallManager deducts twice the audio bandwidth and returns only half when the call completes when you have a Cisco IP Phone 7970 with VTA running behind it.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCsa70684

CSCeg14558

Call Control: If an application redirects a call before accepting it, the call redirect succeeds, but the CP component sends an error message.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeg14558

CSCeg89652

Call Control: A failed call pickup operation disconnects the original call when lack of bandwidth occurs.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeg89652

CSCeh00393

Call Control: Calls drop when you perform a blind transfer on a SIP trunk.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeh00393

CSCuk55946

Call Control: When you call from an IP phone to the PSTN via a congested H.323 gateway, the phone correctly plays a reorder tone, but it also incorrectly displays the "Enter Number" message.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCuk55946

CSCsa69696

Change Notify: Cisco CallManager does not set the message waiting light (MWI) on the phones after initial activation of the CMI service.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCsa69696

CSCsa70907

Change Notify: Change notification fails and phones cannot be reset or restarted via Cisco CallManager Administration.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCsa70907

CSCeg72693

Database: Memory corruption for table CiCrCrpTable causes the ccm.exe service to terminate unexpectedly.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeg72693

CSCin87038

Database: MOH does not play if all the MOH resources are included in a Media Resource Group.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCin87038

CSCeg67765

Device-Manager: Changes to the Cisco CallManager Service Parameter Maximum Number of Registered Devices requires a system restart for the changes to take effect.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeg67765

CSCeg79000

H.323: H.323 gateway does not synchronize or recover, so calls made on the gateway cannot complete.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeg79000

CSCsa63267

H.323: When an inbound call through an H.323 gateway is answered and presentation is set to restricted for the calling number, the display incorrectly shows the calling party number.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCsa63267

CSCsa65147

H.323: Ringback does not stop when an H.323 gateway is reset in Cisco CallManager Administration during call setup.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCsa65147

CSCsa65190

H323: IP Phone gets a reorder tone when an active call between an IP phone and Netmeeting is terminated from the Netmeeting side.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCsa65190

CSCsa68351

H323: The IP phone displays "From 0" instead of "Unknown Number" for incoming PSTN calls via an H.323 gateway when configured to prepend PSTN access code to calling party number for incoming calls and Calling Line ID is set to restricted.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCsa68351

CSCeg33875

Hunt List: Incorrect Caller ID information displays when a call from a Unity voice messaging system rolls over to the second line group in the hunt list.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeg33875

CSCeh03030

Hunt List: The phone displays an incorrect DN in the "From <Phone DN>" message when the call is transferred to the hunt list.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeh03030

CSCsa63894

Hunt List: Circular line group drops calls if an EM user logs out during call hunting.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCsa63894

CSCef11657

Media Control: When insufficient video bandwidth is available for a video/audio call, the video window displays, but no video transmits.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCef11657

CSCeg24375

Media Control: When an IP phone calls a phone on a specific third-party H.323 gateway and hold is pressed, MOH plays out to the gateway, but Cisco CallManager disconnects the call after 10 seconds.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeg24375

CSCeg49681

Media Control: Transfer of H.323 video end points from an audio-only device to a video-enabled device get only audio in certain intercluster call scenarios where the region does not match.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeg49681

CSCeg56200

Media Control: One-way video occurs when sufficient bandwidth is available for at least half of a video stream after Cisco CallManager sends video capabilities when a call is retried as audio, and a gatekeeper rejects the call because of insufficient bandwidth.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeg56200

CSCeg75431

Media Control: Cisco CallManager does not support configuration of asymmetric regions across an intercluster trunk for H.245.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeg75431

CSCsa71443

Media Control: H.323 faststart to MGCP calls fail when the H.323 gateway has "wait for far end H.245 terminal capability" set to False.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCsa71443

CSCef58219

MGCP: Inbound calls to an MGCP-controlled gateway may fail if Cisco CallManager placed some channels Out Of Service (OOS) and failed to provide the status of the channels to the gateway.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCef58219

CSCsa71292

MGCP: Cisco CallManager does not instruct the 6624 to generate an outside dial tone.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCsa71292

CSCsa61861

QSIG: Invalid call diversion APDUs sent in a facility message may cause interoperability problems.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCsa61861

CSCsa72387

QSIG: Call diversion by reroute occurs only for alternate calls when video-enabled endpoints are involved in the call.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCsa72387

CSCuk55454

QSIG: No ringback tone plays when calling from a phone connected to Cisco CallManager Express to a phone connected to a QSIG PBX via Cisco CallManager.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCuk55454

CSCeg71178

SCCP: Barge may not function correctly when you attempt to barge on multiple calls.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeg71178

CSCeg88241

SCCP: Reorder tone stops on the called phone after you press hold and then resume on the calling phone.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeg88241

CSCsa66536

SCCP: When Cisco CallManager detects a keep alive timeout between a Skinny endpoint and Cisco CallManager, it closes the TCP connection, unregisters the endpoint and posts an incorrect reason code in the DeviceUnregistered alarm in the event viewer.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCsa66536

CSCsa70674

SCCP: StationUpdateCapability from VTA does not list all codecs in the Cisco CallManager trace.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCsa70674

CSCeg71244

SIP: Connected Line ID (CLID) presentation does not display the correct information when it is configured as restricted for inbound calls through a SIP trunk.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeg71244

CSCsa72501

SIP: When Cisco CallManager receives an INVITE with a session-expires header that contains a value that is smaller than the default MIN-SE value, the system sends a 422 response without a MIN-SE header.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCsa72501

CSCsa60533

SIP-Trunk: SIP calls inbound from a third-party gateway include RTP header packets that are incorrectly marked as G.711 A-law.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCsa60533

CSCsa61775

SIP-Trunk: The system displays "Unknown" when CLID is set to restricted for a SIP trunk and after you transfer an incoming call through a SIP trunk.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCsa61775

CSCef62437

SS-Callback: When two Cisco CallManager clusters connect via QSIG trunks, the system may display a Callback notification when a monitored phone is disconnected and then reconnected to the network.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCef62437

CSCeg68954

SS-Callback: When a 6608-T1-CAS call is made, Callback notification is received though the phone even though the phone does not go offhook and onhook.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeg68954

CSCsa61117

SS-Callback: The system sends incorrect Callback notification for a phone in a line group when the call is not answered.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCsa61117

CSCuk55930

SS-Pathreplace: When the QSIG Path Replacement service is invoked on a call, media can take up to 5 seconds to establish on a PBX blind transfer via Cisco CallManager to Cisco CallManager Express.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCuk55930

CSCsa68436

Supplementary Services: Hook flash transfer from an MGCP FXS port to a phone that is configured for CFA to another MGCP FXS endpoint does not display the correct reason code of CFA.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCsa68436

CSCsa60938

System: Under heavy call load in an IPCC configuration with a cluster of five Cisco CallManager servers and 1000 agents, the CPU on the Cisco CallManager server spikes at 100%.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCsa60938

CSCsa64684

System: Change notify stops working after the Cisco CallManager service stops on any node and the connection between the processes that monitor the database for changes and the Cisco CallManager processes on all nodes fail to re-establish.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCsa64684

CSCsa68521

System: Cisco CallManager terminates unexpectedly due to access violation.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCsa68521

CSCef97154

Unknown: SDL file write causes trace disk drive fragmentation and surge to disk I/O, which can render Cisco CallManager inactive for a period of time.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCef97154

CSCeg84637

Unknown: Deactivating the Cisco CallManager service terminates SDL links even if the deactivation fails.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeg84637

CSCsa72247

Unknown: Offnet to Offnet transfer blocking does not work in all scenarios.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCsa72247

Component: CAR

CSCsa65681

CDR/CMR Export displays an error if the selected date range does not contain any CDR and/or CMRs.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCsa65681

Component: CCM-Serviceability

CSCsa66775

The system prompts for a restart after uninstallation of the Trace Collection Tool.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCsa66775

CSCsa67753

The Trace Collection Tool does not collect full messages in Cisco CallManager traces.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCsa67753

Component: CM-Documentation

CSCee69769

The documentation about the RemoveServerFromDB.bat and RemoveSubscription.bat scripts needs to be updated.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCee69769

CSCeg74702

The default value for the maximum number of files incorrectly displays 250 instead of 300 in the SDI/SDL Help window.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeg74702

Component: CPI-OS

CSCsa70955

CPI installation returns an error if you enter a password that is less than 6 characters long, even though the supported number of characters for a password during installation range between 1 and 31.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCsa70955

Component: Database

CSCeg39344

The Cisco CallManager Subscriber upgrade process locks up and hangs when the upgrade is initiated before the TFTP service completes building its files.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeg39344

CSCeg64225

The system does not allow the addition of certain valid route patterns by using the range notation (for example, [14-7]).

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeg64225

CSCeh05281

Call Forward and Message Waiting Indicator (MWI) failure occurs for phones that are registered to a Cisco CallManager subscriber server when the Database Layer Monitor fails to start after the subscriber server reboots.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeh05281

CSCsa64360

EM login succeeds but the phone does not get the DN that is configured for EM in the device profile.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCsa64360

CSCsa65596

The Cisco CallManager subscriber server initialization does not complete successfully if the publisher server reboots during this initialization.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCsa65596

CSCsa72439

Access to the Cisco CallManager Administration window on the Cisco CallManager subscriber server is delayed or not accessible if the publisher server is shut down or disconnected from the network.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCsa72439

Component: Database Administration

CSCef42822

Cisco CallManager Administration windows do not function properly on the client machine when the Cisco CallManager server web browser is configured to use a proxy server for web access.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCef42822

CSCeg45116

The Cisco Voice Mail Port Wizard displays a type mismatch error when it tries to delete voice-mail ports after some of the ports were manually deleted.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeg45116

CSCeg71254

After removing a device association from a user, the system allows you to choose the "No Primary Extension" radio button, but the update for the user fails.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeg71254

CSCeh23839

Migration from Cisco CallManager version 3.3(2) to version 4.1(2) for AIM-VOICE-30(332) to AIM-VOICE-30-SLOT-0 (412) fails.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeh23839

CSCin59391

Cisco CallManager displays gateways that already have associated DNs.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCin59391

CSCsa61742

The system resets the Personal Address Book parameters (userID and password) to the default value after you make changes on the Add/Update Service URL Button window.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCsa61742

CSCsa66709

The system displays "Type Mismatch (-2146828275)" when you enter an invalid character in the Start Directory Number in Cisco CallManager Administration.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCsa66709

CSCsa71841

The Cisco Wireless IP Phone 7920 user guide cannot be loaded from the Cisco CallManager User window.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCsa71841

CSCsa72046

Adding a shared line DN causes the system to hang in the Validating status.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCsa72046

CSCsa72397

Modify the Hunt Pilot validation check warning message to show all characters that are allowed and disallowed in the Hunt Pilot field in the Hunt Pilot Configuration window.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCsa72397

CSCsa72410

The system displays incorrect results in the Find/List windows when you enter `$' as the search text.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCsa72410

Component: ES-SR-Wrapper

CSCeg76037

When you install or uninstall a Cisco CallManager SR, the uninstall process changes the Load Digital Access WS-X6608 load to default.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeg76037

CSCsa64567

The Cisco CallManager Subscriber server upgrade from 4.1(2) to 4.1(2)sr1 fails because the SNMP service cannot be stopped.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCsa64567

Component: Ext-Mobility

CSCeg24154

With Active Directory integration, servers that are not running Extension Mobility (EM) should not appear in the profile and when an EM server retrieves the labeledURIs, its own address should appear first in the list.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeg24154

Component: Install_Product

CSCeg10766

The Cisco CallManager installation package needs to include updated JRE 1.4.2_07 to resolve intermittent errors that occur when you use the IE browser with the Sun JRE.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeg10766

Component: IPMA-Service

CSCee73576

The IPMA Manager Configuration window does not display a warning about saving invalid characters and becomes nonfunctional after you save an invalid character such as \.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCee73576

CSCef07143

The search results window displays a blank screen when you modify the user configuration window for a manager without updating it and then you access a different Cisco CallManager window.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCef07143

CSCeg15030

The system does not display an error message when a divert target contains invalid characters.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeg15030

CSCeg37274

IPMA Manager client times out after initial log in.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeg37274

CSCin82373

The assistant console window on the manager phone may not display during IPMA service failover.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCin82373

CSCsa61152

The system displays different messages on the assistant phone and on the GUI when you try to retrieve a parked call.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCsa61152

CSCsa63927

The system displays incorrect information on the assistant console after immediate divert from manager is done.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCsa63927

CSCsa65533

The system displays "OutOfMemoryError" message in the IPMA CTI logs after 1100 IPMA assistant logins with 1250 managers in the server.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCsa65533

Component: JTAPISDK/TAPISDK

CSCsa62756

JTAPISDK: Under 150 agent load test, calls might get rejected and drop due to the JTAPI error CTIERR_REDIRECT_CALL_DESTINATION_BUSY=0x8ccc003f.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCsa62756

CSCee66279

TAPISDK: Deallocating the confparent call on a third-party-controlled CTI port does not close the conferenced calls.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCee66279

CSCsa66381

TAPISDK: The Cisco TSP wave driver increments the RTP header sequence numbers even during periods of silence (no data from application) when no RTP packets are being generated.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCsa66381

Component: Media Streaming Application

CSCef72456

Cisco CallManager stops responding after you issue a reload command when a USB multicast MOH audio source is configured.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCef72456

Component: MLA

CSCeg58688

Last search string should be retained in the "Refine Search" window on the MLA User Group Configuration window.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeg58688

Component: RTMT

CSCef71974

The Real-Time Monitoring Tool (RTMT) installation aborts if the destination file name is too long.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCef71974

Component: Security

CSCee40155

The Cisco CTL Provider and the Cisco CAPF Service services need to update the SCM database with the correct list of services that it depends on.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCee40155

CSCef91121

CTL client allows CTLFile to be signed by new eToken, whose signature is not recognized by the phones, which prevents connection to Cisco CallManager.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCef91121

CSCeh02812

The security icon does not display on the called device when the phones fall back to secure SRST.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeh02812

CSCsa63280

Calls to a non-secure voice-mail port fail when Cisco Unity and Cisco CallManager are in secure mode.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCsa63280

CSCsa72569

Voice-Mail ports fail to register with Cisco CallManager when they are created with the UseSystemDefault security option and the enterprise parameter for the default security flag is encrypted.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCsa72569

Component: Upgrade Assistant

CSCsa64483

Upgrade Assistant version 4.1(2.108) runs on Cisco CallManager 4.1(3); it should display a message that the version is not compatible and abort.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCsa64483

Component: Webdialer-Service

CSCeg52750

The CallsCompleted performance counter incorrectly increments when the Dial button is clicked and again when the HangUp button is clicked.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeg52750

The following firmware caveats apply to this release.

CSCeg71130

SW-6608: Calls do not clear through a T1-CAS if the calls end quickly.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeg71130

CSCeg74747

SW-6608: User receives no preemption tone when a call is made across a T1-CAS.

http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeg74747

Note For complete Cisco IP Phone firmware release note information, refer to the applicable firmware release notes for your specific model of Cisco IP Phone at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_ipphon/english/.

Documentation Updates

This section provides documentation changes that were unavailable when the Cisco CallManager release 4.1 documentation suite was released.

This section contains the following types of documentation updates:

•Errors

•Changes

•Omissions

Errors

This section includes information about errors in the Cisco CallManager Documentation suite.

•Java Runtime Environment

•Cisco CallManager Dialed Number Analyzer Service Startup Type

•Barging into Encrypted Calls with the Cisco IP Phone Model 7970

•Using Valid Characters in Cisco CallManager User IDs

•Cisco CallManager Security Guide Corrections

•Removing a Subscriber Server from Cisco CallManager

•Using Script Files to Remove a Subscriber Server from Cisco CallManager

•Clarification to MLPP Interaction with Call Transfer

•Correction to Forward No Coverage Internal/External Configuration

•Correction to the Procedure for Adding a Cisco CallManager

•Cisco Call Back Supports Lines Not Devices

Java Runtime Environment

The Cisco CallManager Administration Guide does not contain the most current information about installing JRE for use with Cisco CallManager Administration. See the "Call Pickup and Group Call Pickup Enhancements" section for the complete information.

Cisco CallManager Dialed Number Analyzer Service Startup Type

The "Installing Cisco CallManager Dialed Number Analyzer" chapter in the Cisco CallManager Dialed Number Analyzer Guide contains incorrect information about setting the service startup type to "Manual" after successful installation of DNA. The Dialed Number Analyzer service startup type actually gets set to "Automatic."

The text in the Cisco CallManager Dialed Number Analyzer Guide should state the following:

When installation is successful, the Dialed Number Analyzer service installs and starts. The service startup type gets set to Automatic.

Barging into Encrypted Calls with the Cisco IP Phone Model 7970

The Cisco CallManager Security Guide does not specify the phone models that are affected by barging into encrypted calls. The following information pertains only to the Cisco IP Phone model 7970 and becomes applicable with availability of the compatible phone firmware image.

Cisco CallManager 4.1 does not support barging into an encrypted call if the phone that is used to barge is not configured for encryption. When barge fails in this situation, a busy tone plays on the phone where the user initiated the barge.

Using Valid Characters in Cisco CallManager User IDs

The Add A New User chapter in the Cisco CallManager Administration Guide and the Cisco CallManager online help documentation contain incorrect information about the use of special characters in the User ID field.

Specifically, the UserID field in the User Configuration Settings under the
User > Add a New User menu incorrectly states that you may use special characters when you configure a Cisco CallManager user ID.

Special characters, such as =, +, <, >, #, ;, \, , "" and blank spaces, are not valid and may not be used. You must use alphanumeric characters only.

For more information, refer to http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCef71945.

Cisco CallManager Security Guide Corrections

The following corrections apply to the Cisco CallManager Security Guide.

Incorrect Reference

The Cisco CallManager Security Guide in the Cisco CallManager Administration 4.1(2) online help erroneously refers to Cisco CallManager version 4.1(1). The document should refer to Cisco CallManager version 4.1(2).

The online version of the Cisco CallManager Security Guide includes reference to the correct Cisco CallManager release number.

Replacing a Failed/Existing Secure Subscriber Server

The "Replacing a Failed/Existing Secure Subscriber Server" section in the Cisco CallManager Security Guide erroneously states that you must restart only the Cisco CallManager service after you run the Cisco CTL client.

The section should state that you must restart both the Cisco CallManager and Cisco TFTP services after you run the Cisco CTL client.

Removing a Subscriber Server from Cisco CallManager

The following information provides corrections and replaces the contents of the Cisco CallManager Administration Guide, Appendix B, Removing a Subscriber Server from Cisco CallManager.

You can delete a subscriber server from the Cisco CallManager cluster by using the Server Configuration window in Cisco CallManager Administration. This deletion removes the server from the Cisco CallManager Administration database, but it does not delete all server dependencies.

To fully delete a server from the system, you must perform the following steps:

Procedure

Step 1 Remove all dependencies from the server; for example, delete the Cisco CallManager service.

For additional information, refer to the Cisco CallManager Administration Guide, Deleting a Server chapter.

Tip To view the dependencies, click the Dependency Records link on the Server Configuration window. For more information about Dependency Records, refer to the Cisco CallManager Administration Guide, Appendix A.

Step 2 Deactivate the services from the server.

Refer to the Cisco CallManager Serviceability Administration Guide, Service Activation chapter, for more information.

Step 3 Remove the server from Cisco CallManager Administration.

Refer to the Cisco CallManager Administration Guide, Deleting a Server chapter, for more information.

Step 4 If the Cisco CallManager cluster is integrated with the local DC Directory, run the command file from the command prompt that removes the DCD replication agreements from the publisher server.

See the "Remove Redundant DCD Replication Agreements" section for more information.

Remove Redundant DCD Replication Agreements

After you remove the subscriber server from the cluster, you must clean the DCD replication information from the publisher DCD by running the Clean_publisher command file. (This command file only executes on the publisher server.)

You can access this command file on servers that are running Cisco CallManager release 3.3 and later. Cisco CallManager installs the Clean_publisher command file on the server during installation of the Cisco Directory component.

To clean the DCD replication information, enter the following command from any directory on the publisher server:

c:\Clean_publisher.cmd

Note If you remove the server without running the Clean_publisher.cmd command file and then add the server back with the same host name into the same cluster from where it was removed, the DCD script that is used to configure the subscriber DCD will clean up the previous DCD replication agreement from the publisher DCD database during the Directory installation of the Cisco CallManager installation on the server.

Using Script Files to Remove a Subscriber Server from Cisco CallManager

The following information provides corrections and replaces the content that appears in the Cisco CallManager Administration Guide, Appendix B.

To remove a subscriber server from Cisco CallManager, see the "Removing a Subscriber Server from Cisco CallManager" section.

If your attempts to remove a server were not successful, perform the following steps:

Procedure

Step 1 Run the script file that cleans up subscriber-related database records and removes the SQL replication information from the publisher server.

See the "Remove Subscriber Information" section.

Step 2 If the Cisco CallManager cluster is integrated with the local DC Directory, run the command file that removes the DCD replication agreements from the publisher.

For more information, refer to the Cisco CallManager Administration Guide, Appendix A.

Remove Subscriber Information

If the server removal was unsuccessful, run the script file that cleans up subscriber-related database records and removes the SQL replication information. Run the script file for the publisher server and the script file for the subscriber server.

See the "Contents of the RemovePublisher.bat Script File" section and the "Contents of the RemoveSubscriber.bat Script File" section for more information.

Tip Copy the script file contents from Example 1 and Example 2 to a Notepad file and save it with a .bat extension; for example, RemovePublisher.bat and RemoveSubscriber.bat.

Run RemovePublisher.bat Script on Publisher Server

Execute the RemovePublisher.bat script file from the Cisco CallManager publisher server for the cluster that contains the subscriber that you want to remove. This script runs from the command prompt from any directory.

Tip To view the procedure that runs the script, run the script with no parameters.

From any directory on the publisher server, enter the following command:

<path where you saved the script>:\RemovePublisher "server" "database" "name_of_server_to_delete_from_database connection string"

To find the database connection string name, follow these steps:

Procedure

Step 1 Navigate to Service > Service Parameters.

Step 2 Choose Cisco Database Layer Monitor.

Step 3 Click Advanced.

Step 4 Obtain the name from the Database Connection String field:

For example, DSN=CiscoCallManager;Server=ABC2.

When you run this command from the command prompt, errors display; no separate error log file gets generated.

To view the contents of the script file, see the "Contents of the RemovePublisher.bat Script File" section.

Contents of the RemovePublisher.bat Script File

Example 1 displays the contents of the script file that cleans up subscriber-related database records and removes the SQL replication information from the publisher server.

Example 1 Script File Contents
@echo off 
@if "%3x" == "x" goto Usage 
echo Install stored procedure in database %2 
echo USE %2 > templ  
echo GO >> temp.sql 
echo DROP PROCEDURE dblRemoveServerFromDB >> temp.sql 
echo GO >> temp.sql 
echo CREATE PROCEDURE [dblRemoveServerFromDB] >> temp.sql 
echo (@servername NVARCHAR(50),@ispublisher NVARCHAR(50)) AS >> temp.sql 
echo BEGIN TRANSACTION >> temp.sql 
echo DECLARE @nodeid NVARCHAR(50), @deviceid NVARCHAR(50), @pnsid NVARCHAR(50) >> temp.sql 
echo -- >> temp.sql 
echo PRINT 'Get the Node ID' >> temp.sql 
echo SELECT @nodeid=pkid from ProcessNode where name=@servername >> temp.sql 
echo -- >> temp.sql 
echo PRINT 'Delete associated Device and MediaMixer' >> temp.sql 
echo WHILE (SELECT COUNT(*) FROM Device WHERE fkProcessNode=@nodeid) ^> 0 >> temp.sql 
echo BEGIN >> temp.sql 
echo     SELECT @deviceid=pkid from Device where fkProcessNode=@nodeid >> temp.sql 
echo     PRINT 'Delete MediaMixer' >> temp.sql 
echo     DELETE FROM MediaMixer WHERE fkDevice=@deviceid >> temp.sql 
echo     PRINT 'Delete MOHServer' >> temp.sql 
echo     DELETE FROM MOHServer WHERE fkDevice=@deviceid >> temp.sql 
echo     PRINT 'Delete Device' >> temp.sql 
echo     DELETE FROM Device WHERE pkid=@deviceid >> temp.sql 
echo END >> temp.sql 
echo -- >> temp.sql 
echo PRINT 'Delete associated CallManager records' >> temp.sql 
echo DELETE FROM CallManagerGroupMember FROM CallManagerGroupMember AS M >> temp.sql 
echo   JOIN CallManager AS C ON C.pkid=M.fkCallManager WHERE C.fkProcessNode=@nodeid >> 
temp.sql 
echo DELETE FROM CallManager WHERE fkProcessNode=@nodeid >> temp.sql 
echo -- >> temp.sql 
echo PRINT 'Delete associated ProcessConfig records' >> temp.sql 
echo DELETE FROM ProcessConfig WHERE fkProcessNode=@nodeid >> temp.sql 
echo -- >> temp.sql 
echo PRINT 'Delete associated AlarmConfig records' >> temp.sql   
echo DELETE FROM AlarmConfig FROM AlarmConfig AS A JOIN ProcessNodeService >> temp.sql   
echo   AS S ON A.fkProcessNodeService=S.pkid WHERE S.fkProcessNode=@nodeid >> temp.sql   
echo PRINT 'Delete associated ProcessNodeService records' >> temp.sql 
echo DELETE FROM ProcessNodeService WHERE fkProcessNode=@nodeid >> temp.sql 
echo -- >> temp.sql 
echo PRINT 'Delete associated ComponentVersion records' >> temp.sql 
echo DELETE FROM ComponentVersion WHERE fkProcessNode=@nodeid >> temp.sql 
echo -- >> temp.sql 
echo PRINT 'Delete the node' >> temp.sql 
echo DELETE FROM ProcessNode WHERE pkid=@nodeid >> temp.sql 
echo -- >> temp.sql 
echo COMMIT TRANSACTION >> temp.sql 
echo GO >> temp.sql 
echo -- Execute procedure on server %1                                                                                                                 
echo exec dblRemoveServerFromDB '%3' >> temp.sql 
osql -S %1 -d %2 -E -e -i temp.sql                                                                                              
del temp.sql                                                                                                                    
echo USE %2 > temp1.sql  
echo sp_dropsubscription @publication = %2, @subscriber = '%3', @article='all' >> 
temp1.sql 
echo GO >> temp1.sql 
osql -S %1 -d %2 -E -e -i temp1.sql 
del temp1.sql 
goto endd                                                                                                                       
:Usage 
@echo Usage:   RemoveServerFromDB "server" "database" "name_of_server_to_delete_from_ProcessNode.Name"  
@echo Example: RemoveServerFromDB . CCM0300 fred.cisco.com  
:endd 
Contents of the RemoveSubscriber.bat Script File

Example 2 displays the contents of the script file that removes the SQL replication information from the subscriber server.

Example 2 Script File Contents
@echo off 
@if "%2x" == "x" goto Usage 
echo Install stored procedure in database %2 
echo sp_removedbreplication @dbname = %2 > temp1.sql 
echo GO >> temp1.sql 
osql -S %1 -d %2 -E -e -i temp1.sql 
del temp1.sql 
goto endd                                                                                                                                          
:Usage 
@echo Usage:   RemoveSubscription "server" "database"  
@echo Example: RemoveSubscription . CCM0300  
:endd 
Clarification to MLPP Interaction with Call Transfer

The Multilevel Precedence and Preemption (MLPP) chapter in the Cisco CallManager Features and Services Guide contains information about the following interaction between MLPP and Call Transfer:

MLPP interacts with the call-transfer feature. For blind transfers and consult transfers, each connection of the transferred call, including the consult call, maintains the precedence that the connection was assigned when the call was established.

The following information provides clarification about the interaction between MLPP and Call Transfer:

•A transferred call has two legs or connections and each leg/connection may have a different precedence level associated with it. For example, the first leg/connection may be a priority call and the second leg/connection may be a routine call.

•Cisco CallManager maintains the precedence of the individual legs/connection of all calls; that is, each individual leg of the transfer or conference call maintains the precedence that it was assigned when that call was established.

•The call transfer function does not preserve the MLPP precedence level from one individual leg/connection to the next individual leg/connection, so precedence levels may be lost or changed during a call transfer.

Correction to Forward No Coverage Internal/External Configuration

The "Configuring Directory Numbers" section in the "Cisco IP Phone Configuration" chapter in the Cisco CallManager Administration Guide, contains incorrect information about the Forward No Coverage Internal and Forward No Coverage External configuration settings that appear in Table 57-3, Directory Number Configuration Settings.

This section incorrectly states the following information:

The field applies only to CTI route points and CTI ports. The settings in this row specify the forwarding treatment for internal/external calls to this CTI route point or CTI port if the CTI route point or CTI port has no coverage.

The Forward No Coverage Internal and Forward No Coverage External fields do not apply to CTI route points or CTI ports. This following information provides corrections to the text in this section:

1. The Forward No Coverage Internal/External fields only apply if you configure one of the other forwarding fields—Call Forward All (CFA), Call Forward Busy (CFB), or Call Forward No Answer (CFNA)—with a hunt pilot number in the Coverage/Destination DN field.

2. For the hunt pilot settings, you must also configure the Forward Hunt No Answer/Forward Hunt Busy fields and check the Use Personal Preferences check box under the Hunt Forward Settings section on the Hunt Pilot Configuration window; otherwise, the Forward No Coverage configuration in the Directory Number Configuration window has no affect.

You can set the Hunt Forward Settings parameters by using Cisco CallManager Administration to access the Hunt Pilot Configuration window (Route Plan > Route/Hunt > Hunt Pilot). On the Cisco CallManager Administration Hunt Pilot Configuration window, scroll down to the Hunt Forward Settings section to configure the personal preferences parameters.

Correction to the Procedure for Adding a Cisco CallManager

The "Adding a Cisco CallManager" section in the Cisco CallManager Configuration" chapter in the Cisco CallManager Administration Guide, erroneously states in the "Before You Begin" section that you must activate the Cisco CallManager service before you configure the address of the server where the Cisco CallManager is installed.

The following information provides corrections to this procedure:

Before You Begin

Before adding a new Cisco CallManager to the database, perform the following tasks:

•Configure the address of the server where this Cisco CallManager is installed.

•Activate the Cisco CallManager service as described in the Cisco CallManager Serviceability Administration Guide.

•If you want to specify a partition for directory numbers that are used in auto-registration with this Cisco CallManager, configure that partition.

Note When you activate the Cisco CallManager service, a CallManager entry is automatically added to the database. Once you have activated the Cisco CallManager service, you should not have to manually add the Cisco CallManager to the database, unless that Cisco CallManager has been deleted.

For more information, refer to http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCsa71897.

Cisco Call Back Supports Lines Not Devices

In Cisco CallManager release 4.0, the Cisco Call Back feature supported devices; in other words, when Phone A initiated Call Back to Phone B because it was busy or unanswered, the Call Back feature would ring Phone A when Phone B went on hook.

In Cisco CallManager release 4.1, the Cisco Call Back features supports individual lines on a device. Consider the following scenario.

Phone A: Line 1 - 3011

Phone A: Line 2 - 3012

Phone B: Line 1 - 3013

Phone B: Line 2 - 3014

1. Phone A/Line2 goes off hook and dials 3014 (Phone B/Line 2).

2. While in RingOut State, the user presses the CallBack Softkey on Phone A/Line 2.

3. Phone B presses the speaker button to get dialtone and then presses the speaker button again to end the call. Because Line 1 on Phone B is the default line when going off hook, Phone A did not receive a call back notification. If Phone B/Line 2 had gone off hook, then Phone A/Line 2 would have received a notification that Phone B/Line 2 was available.

Changes

This section contains changes that have occurred since the original release of the Cisco CallManager release 4.1 documentation. These changes may not appear in the current documentation or the online help for the Cisco CallManager application.

•Associating H.323 Devices to Users

•Ad Hoc Conference Limitations

•Meet-Me Conference Limitations

Associating H.323 Devices to Users

In Cisco CallManager release 4.0, administrators could not associate H.323 devices with a user; therefore, the administrator could not configure features on the H.323 end points in the Cisco CallManager Administration User Configuration window.

Cisco CallManager release 4.1 corrects this behavior by displaying all devices, in addition to CTI-controllable devices, and by allowing the administrator to choose H.323 devices in the Device Association window.

For devices that are not CTI-controllable, such as H.323 devices, an asterisk (*) displays next to the device icon. All device association behavior remains identical regardless of the type of device for which the feature is configured.

Ad Hoc Conference Limitations

Cisco CallManager supports a maximum of 100 simultaneous ad hoc conferences for each Cisco CallManager server.

Meet-Me Conference Limitations

Cisco CallManager supports a maximum of 100 simultaneous meet-me conferences for each Cisco CallManager server.

Omissions

This section lists new and additional information that the current version of the Cisco CallManager documentation may not include:

•CTI Monitored Lines

•? Icon Displays Incorrect Online Help for Region and Calling Search Space Pop Up Windows

•Name Change for the Cisco IAD 2400 Gateway Type in Cisco CallManager Administration

•Route List Redundancy Configuration

•Cisco IP Phone Models 7940/7960 Built-In Bridge and Device Security Considerations

•CAPF Interaction When Cisco IP Phone Resets

•Using Server Authentication, Third-Party CA Certificates

•Using Shared Lines with Encrypted Devices

•Reinstalling Dialed Number Analyzer After a Cisco CallManager Upgrade

•Personal Directory

•Support for the Cisco VG224 Gateway

•Call Back Feature Interactions with Call Forward, iDivert, and Voice-Mail System Features

•Tool for Autoregistered Phone Support Information for End Users

•Time-of-Day Routing Chapter Omits Information About Defined Time Periods

CTI Monitored Lines

To calculate the number of CTI monitored lines in a system, use the following formula:

number of pilot point DNs + (number of clients open * number of directory numbers per phone) + (number of parked directory numbers * number of open clients) = CTI Monitored Lines

? Icon Displays Incorrect Online Help for Region and Calling Search Space Pop Up Windows

When you press the "?" bubble for online help in either the Regions or CSS popup search window, the online help for Partitions displays instead.

The online help for Regions/CSS should state the following information:

If more than 250 regions/calling search spaces exist, the ellipsis (...) button displays next to the Regions/CSS drop-down list box on the Cisco CallManager Administration windows where the button appears. You can click the (...) button to search for the region/CSS that you want.

Use the following procedure to search for a region/CSS:

Procedure

Step 1 Click the ... button next to the Region/Calling Search Space drop-down list box.

The Select Region/Select Calling Search Space window displays.

Step 2 In the List items where Name contains field, enter a partial region/calling search space name.

Step 3 In the list of regions/calling search spaces that displays in the Select item to use box, click the desired region/calling search space name.

Step 4 Click OK.

Name Change for the Cisco IAD 2400 Gateway Type in Cisco CallManager Administration

In the "Add a New Gateway" window in Cisco CallManager Administration, the "Cisco IAD 2420 (end-of-sale product)" gateway type replaced the Cisco IAD 2400 gateway type.

Use the Cisco IAD 2420 gateway type to add a new Cisco IAD 2420 gateway to Cisco CallManager.

Note The system does not support the Cisco IAD 2430 gateway for use with Cisco CallManager.

For more information, refer to http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCef30742.

Route List Redundancy Configuration

The Cisco CallManager System Guide does not include the following information about route list redundancy.

From Cisco CallManager release 4.0(2), route list handling and redundancy was changed to improve performance. Pre-4.0(2) implementations included route lists on every server in a cluster. After upgrade to release 4.0(2) or later, only one instance of the active route list configuration associates with a Cisco CallManager group. This change requires that you configure the Cisco CallManager Group(s) to maintain load balancing and redundancy.

After you upgrade the Cisco CallManager servers to 4.0(2) or later, and if two or more primary Cisco CallManager servers exist in the cluster, the system creates new Cisco CallManager Group(s) with a default name of "RLCMG_<primary Cisco CallManager name>." The system creates one Cisco CallManager Group for each primary server and the secondary server in the Cisco CallManager Group, which is the dedicated backup server. Depending on the number of servers in the cluster, the system creates one or multiple Cisco CallManager Groups.

One instance of the active route list configuration then attaches to the primary Cisco CallManager server in the first Cisco CallManager Group. New Cisco CallManager Groups get assigned to the existing route list configuration by use of a round-robin algorithm to ensure redundancy.

To complete the upgrade, you must perform the following tasks:

1. Create new Cisco CallManager Group(s) to replace the default Cisco CallManager Group(s) that are named "RLCMG_<primary Cisco CallManager name>" and that were created during the upgrade.

2. Evaluate the Cisco CallManager Group and route list configuration for load balancing and redundancy.

3. Reconfigure the route list(s) to the user-created Cisco CallManager Group(s).

4. Delete the default Cisco CallManager Group(s).

Caution These activities drop all dependent active calls and cause significant overhead while you perform the reconfiguration.

For more information, refer to http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCee30571.

Where to Find More Information

•"Route List Configuration," Cisco CallManager Administration Guide

Cisco IP Phone Models 7940/7960 Built-In Bridge and Device Security Considerations

The "Cisco IP Phone Configuration" chapter in the Cisco CallManager Administration Guide, the "Barge" chapter in the Cisco CallManager Features and Services Guide, and the Cisco CallManager System Guide do not contain the following information about the configuration of the built-in bridge and device security for the Cisco IP Phones models 7940 and 7960.

Cisco IP Phone models 7940 and 7960 cannot support two media stream encryptions or SRTP streams simultaneously. This condition occurs when the phone is being barged from another phone and all of the phones in the call are using SRTP (the built-in bridge is enabled).

Note To prevent phone instability due to this condition, the system automatically disables the built-in-bridge for the Cisco IP Phone models 7940 and 7960 when the device security mode is set to encrypted.

If you attempt to configure barge for Cisco IP Phone models 7940 and 7960 that are configured for encryption, the following message displays:

If you configure encryption for Cisco IP Phone models 7940 and 7960, those encrypted devices cannot accept a barge request when they are participating in an encrypted call. When the call is encrypted, the barge attempt fails.

The message displays whenever you perform the following tasks in Cisco CallManager Administration:

•In the Phone Configuration window, you choose Encrypted for the Device Security Mode (or System Default equals Encrypted), On for the Built In Bridge setting (or default setting equals On), and you click Insert or Update after you create this specific configuration.

•In the Enterprise Parameter window, you update the Device Security Mode parameter.

•In the Service Parameter window, you update the Built In Bridge Enable parameter.

Tip You must reset the dependent Cisco IP devices for changes to take effect.

Refer to the Cisco CallManager Security Guide for additional information.

CAPF Interaction When Cisco IP Phone Resets

The Cisco CallManager Security Guide does not contain the following information about how CAPF interacts with the Cisco IP Phone when a user or Cisco CallManager resets the phone.

In the following examples, if an LSC does not already exist in the phone and if By Existing Certificate is chosen for the CAPF Authentication Mode, the CAPF certificate operation will fail.

Example —Nonsecure Device Security Mode

In this example, the phone resets after you configure the Device Security Mode to Nonsecure and the CAPF Authentication Mode to By Null String or By Existing Certificate (Precedence...). After the phone resets, it immediately registers with the primary Cisco CallManager and receives the configuration file. The phone then automatically initiates a session with CAPF to download the LSC. After the phone installs the LSC, configure the Device Support Mode to Authenticated or Encrypted.

Example—Authenticated/Encrypted Device Security Mode

In this example, the phone resets after you configure the Device Security Mode to Authenticated or Encrypted and the CAPF Authentication Mode to By Null String or By Existing Certificate (Precedence...). The phone does not register with the primary Cisco CallManager until the CAPF session ends and the phone installs the LSC. After the session ends, the phone registers and immediately runs in authenticated or encrypted mode.

Note You cannot configure By Authentication String in this example because the phone does not automatically contact the CAPF server; the registration fails if the phone does not have a valid LSC.

Using Server Authentication, Third-Party CA Certificates

The Cisco CallManager Security Guide does not contain the following information about using a server authentication, third-party CA certificate instead of the self-signed HTTPS certificate.

Follow these steps to ensure that Cisco CallManager HTTPS-enabled applications can download the third-party certificate when you use server authentication, third-party CA certificates for HTTPS:

1. Refer to the Cisco CallManager Security Guide for information about deleting the HTTPS certificate and installing the third-party CA certificate on the IIS default website.

2. Install the third-party CA certificate on the IIS default website, as documented in the Cisco CallManager Security Guide.

3. Rename the Root CA certificate to httpscert.cer.

4. Copy the certificate to C:\program files\cisco\certificates in DER format.

Using Shared Lines with Encrypted Devices

The Cisco CallManager Security Guide does not contain the following information about using shared lines with encrypted devices.

When you configure a shared line for an encrypted Cisco IP Phone model 7970, be sure to configure all devices that share the lines for encryption; that is, ensure the device security mode for all devices is set to encrypted.

Reinstalling Dialed Number Analyzer After a Cisco CallManager Upgrade

The Cisco CallManager Dialed Number Analyzer Guide does not contain the following information about reinstalling DNA after a Cisco CallManager upgrade.

•If you upgrade Cisco CallManager on every server in a cluster, you must reinstall the Dialed Number Analyzer plugin on the required node in the cluster.

•If you have installed Dialed Number Analyzer to use data from Cisco CallManager to perform analysis of a numbering plan, you must reinstall Dialed Number Analyzer plugin on the server that you are using for numbering plan analysis. Reinstalling the plugin synchronizes any additional data entries that are available in Cisco CallManager with the Dialed Number Analyzer database.

Follow this procedure to install Dialed Number Analyzer:

Procedure

Step 1 Access Cisco CallManager and choose Application > Install Plugins.

The Install Plugins window displays.

Step 2 Locate the Dialed Number Analyzer Plugin.

Step 3 Click the executable icon for Dialed Number Analyzer Plugin to launch the InstallShield Wizard.

Step 4 Click Open. The InstallShield Wizard for Cisco Dialed Number Analyzer window displays.

Step 5 Click Next at the Welcome to the InstallShield Wizard for Cisco Dialed Number Analyzer window.

The Enter Private Phrase window displays.

Step 6 Enter the private phrase for this cluster in the Enter Private Phrase window.

Step 7 Click Next.

If the private phrase is incorrect, a message displays. Return to Step 6. If the private phrase is correct, the Ready to Install the Program window displays.

Step 8 Click Install at the Ready to Install the Program window.

Step 9 Click Finish at the InstallShield Wizard Completed window.

The tool installs the Cisco Dialed Number Analyzer service on the machine.

Note When installation is successful, the Dialed Number Analyzer service installs and starts; the service sets the startup type to Automatic.

Personal Directory

Personal Directory provides a personal address book that is stored in the Cisco CallManager LDAP directory, a Cisco IP Phone synchronizer, and two Cisco IP Phone services: Personal Address Book and Personal Fast Dials.

The Cisco CallManager documentation does not contain the following information about configuring and using Personal Directory:

•System Requirements

•Configuring Personal Directory

•Configuring the Personal Address Book Service

•Configuring the Personal Fast Dials Service

•Downloading the Cisco IP Phone Address Book Synchronizer

•Preparing the Phone User for Personal Directory

System Requirements

The system requires the following components for use with Personal Directory:

•Cisco IP Phone models 7940, 7960, 7970

•A PC that is running Cisco CallManager 3.1 or later

•A PC that is running Windows 2000

•A Microsoft IIS Server

•Microsoft Outlook and/or Outlook Express

Note Ensure that Microsoft Outlook is set up in Internet-only mode and the Windows Address Book is configured to share entries.

Configuring Personal Directory

To configure the Personal Directory, you must configure the Personal Address Book Service and the Personal Fast Dials Service.

•Configuring the Personal Address Book Service

•Configuring the Personal Fast Dials Service

Configuring the Personal Address Book Service

You configure the Personal Address Book by adding the service to Cisco CallManager Administration and configuring the service parameters.

Follow this procedure to configure the Personal Address Book service:

Procedure

Step 1 Choose Feature > Cisco IP Phone Services.

The Cisco IP Phone Services Configuration window displays.

Step 2 In the Service Name field, enter the name of the service that you want to display in the menu of available services on the Cisco IP Phone User Options window, for example, My Address Book.

Step 3 In the Service Description field, enter a description of the content that the service provides; for example, Personal Directory - Personal Address Book.

Step 4 In the Service URL field, enter the URL of the server where the application for the Personal Address Book service is located:

http://<CallManager hostname or IP address>/ccmpd/xmlAddressBookInput.asp

Step 5 Click Insert.

Step 6 Click the New button to the right of the Parameters list box.

The Configure Cisco IP Phone Service Parameter window displays.

Step 7 Add each parameter as described in Table 3, beginning with UserID. When you are asked to do so, enter the parameter name exactly as it appears in the table.

Step 8 Click Insert to add the parameter.

Step 9 When you have added the last service parameter, click Insert and Close to insert that parameter and close the window.

The Cisco IP Phone Services Configuration window displays.

Step 10 Click Update Subscriptions.

Personal Address Book Service Parameter Settings

Table 3 shows the service parameter settings for the three service parameters that are required for the Personal Address Book service. Where indicated, use the exact parameter name.

Table 3 Personal Address Book Service Parameter Settings

Field

Definition

Definition

Definition

Parameter Name

UserID

(Use this exact name.)

UserPIN

(Use this exact name.)

PreDial

Parameter Display Name

User Identification

PIN

Outside Access code

Default Value

None

None

None

Parameter Required

Yes

Yes

No

Parameter Description

Use the same user identification that is used with the Cisco IP Phone User Options window.

Use the same user PIN that is used with the Cisco IP Phone User Options window.

This access code gets added as a prefix to the stored directory number to provide access to an outside line.

Parameter is a Password (mask contents)

None

None

None

Note To mask a parameter entry such as a password, check the Parameter is a Password (mask contents) check box.The default for this parameter specifies None. The parameter is provisioned at runtime.

Configuring the Personal Fast Dials Service

You configure Personal Fast Dials by adding the service to Cisco CallManager Administration and configuring the appropriate service parameters.

Follow this procedure to configure the Personal Fast Dials service:

Procedure

Step 1 Choose Feature > Cisco IP Phone Services.

The Cisco IP Phone Services Configuration window displays.

Step 2 In the Service Name field, enter the name of the service that you want to display in the menu of available services on the Cisco IP Phone User Options window; for example, My Fast Dials.

Step 3 In the Service Description field, enter a description of the content that the service provides; for example, Personal Directory - Personal Fast Dials.

Step 4 In the Service URL field, enter the URL of the server where the application for the Personal Address Book service is located:

http://<CallManager hostname or IP address>/ccmpd/xmlFastDials.asp

Step 5 Click Insert.

Step 6 Click the New button to the right of the Parameters list box.

The Configure Cisco IP Phone Service Parameter window displays.

Step 7 Add each parameter as described in Table 4, beginning with UserID. When specified, enter the parameter name exactly as it appears in the table.

Step 8 Click Insert to add the parameter.

Step 9 When you have added the last service parameter, click Insert and Close to insert that parameter and close the window.

The Cisco IP Phone Services Configuration window displays.

Step 10 Click Update Subscriptions.

Personal Fast Dials Service Parameter Settings

Table 4 shows the service parameter settings for the three service parameters that are required for Personal Fast Dials service. Where indicated, use the exact parameter name.

Table 4 Personal Fast Dials Service Parameter Settings

Field

Definition

Definition

Definition

Parameter Name

UserID

(Use this exact name.)

UserPIN

(Use this exact name.)

PreDial

Parameter Display Name

User Identification

PIN

Outside Access code

Default Value

None

None

None

Parameter Required

Yes

Yes

No

Parameter Description

Use the same user identification that is used with the Cisco IP Phone User Options window.

Use the same user PIN that is used with the Cisco IP Phone User Options window.

This access code gets added as a prefix to the stored directory number to provide access to an outside line.

Parameter is a Password (mask contents)

None

None

None

Downloading the Cisco IP Phone Address Book Synchronizer

Users must install the Cisco IP Phone Address Book Synchronizer plug-in on their computers before they can use the Personal Directory.

Use the following procedure to download the Cisco IP Phone Address Book Synchronizer installation file. After you download the file, you can distribute it to the users in your network.

Procedure

Step 1 Choose Applications > Install Plugins.

Step 2 Choose Cisco IP Phone Address Book Synchronizer.

Follow the online instructions.

Step 3 Make the installation file available to the end users to install the Cisco IP Phone Address Book Synchronizer application on their own work station.

a. Include tabsync in the file downloads.asp to make the application available to the users.

b. Provide users with the following URL to download the application: http://<ccm>/ccmuser/downloads.asp

Preparing the Phone User for Personal Directory

After you have added the Personal Directory services and configured the service parameters, provide the phone user with the following information:

•Notification of the feature's availability

•Access to the installation file for the Cisco IP Phone Address Book Synchronizer for users to install on their own workstations

•Their user ID and PIN, if they do not already have it

•The URL for the Cisco IP Phone User Options web page for the user, if they do not already have it

•Information on using the Personal Directory services. Direct them to the Customizing Your Cisco IP Phone on the Web.

Support for the Cisco VG224 Gateway

The Cisco CallManager System Guide omitted information about the Cisco VG224 gateway, which is new in Cisco CallManager release 4.1, from the "Understanding Cisco CallManager Voice Gateways" chapter. The Cisco VG224 gateway uses both MGCP and SCCP gateway control protocols.

The "Gateway Configuration" chapter of the Cisco CallManager Administration Guide in "Adding a Cisco IOS SCCP Gateway" details the configuration of the Cisco VG224 gateway. You should also add the Cisco VG224 gateway to the list of gateways in "Adding a Cisco IOS MGCP Gateway."

Call Back Feature Interactions with Call Forward, iDivert, and Voice-Mail System Features

The Cisco CallManager Features and Services Guide omitted the following information about Cisco Call Back feature interactions.

The following call states describe the expected behaviors, for the calling party, that occur when Cisco CallManager Call Back interacts with the Call Forward, iDivert, and voice-mail system features.

When a called party (Phone B) either forwards an incoming call using Forward All, Forward Busy, or Forward No Answer, or diverts a call using iDivert, to a voice-mail system, the calling party (Phone A) can enter one of the following states with respect to the Call Back feature:

•VM-Connected state—The call is connected to voice-mail. The Call Back softkey is inactive on the calling party's (Phone A) phone.

•Ring-Out state with the original called party—The voice-mail profile of the called party does not have a voice-mail pilot. The called party (Phone B) sees "Key Is Not Active" after pressing the iDivert softkey. The calling party (Phone A) should be able to activate Call Back against the original called party (Phone B).

•Ring-Out state with voice-mail feature and voice-mail pilot number as the new called party—The call encounters either a voice-mail system failure or network failure. The called party (Phone B) sees "Temp Failure" after pressing the iDivert softkey. The calling party (Phone A) cannot activate Call Back against the original called party (Phone B) because the call context includes the voice-mail pilot number as the "new" called party.

•Ring-Out state with busy voice-mail port and voice-mail pilot number as the new called party—The call encounters a busy voice-mail port. The called party (Phone B) sees "Busy" after pressing the iDivert softkey. The calling party (Phone A) cannot activate Call Back against the original called party (Phone B) because the call context includes the voice-mail pilot number as the "new" called party.

For more information, refer to http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCef84035

Where to Find More Information

•Immediate Divert, Cisco CallManager Features and Services Guide

•Phone Features, Cisco CallManager System Guide

Tool for Autoregistered Phone Support Information for End Users

The "TAPS Information for End Users" section in the "Working with the Tool for Auto-Registered Phones Support" chapter in the Bulk Administration Tool User Guide omits the following information between Step 1 and Step 2 in the procedure to configure your new phone:

To configure a new phone, dial the CTI Route Point number provided by your system administrator and follow the prompts.

Time-of-Day Routing Chapter Omits Information About Defined Time Periods

The "Time-of-Day Routing" chapter of the Cisco Unified Communications Manager System Guide omits the following information.

•If you defined a time period with a specific date, on that specified date, that period overrides other periods that are defined on a weekly basis.

Example:

Consider the following example:

•A time period, afterofficehours, that is defined as 00:00 to 08:00 from Monday to Friday exists.

•A time period, newyearseve, that is defined as 14:00 to 17:00 on December 31st exists.

In this case, on December 31st, the afterofficehours period will not be considered because it gets overriden by the more specific newyearseve period.

Obtaining Documentation

Cisco documentation and additional literature are available on Cisco.com. Cisco also provides several ways to obtain technical assistance and other technical resources. These sections explain how to obtain technical information from Cisco Systems.

Cisco.com

You can access the most current Cisco documentation at this URL:

http://www.cisco.com/univercd/home/home.htm

You can access the Cisco website at this URL:

http://www.cisco.com

You can access international Cisco websites at this URL:

http://www.cisco.com/public/countries_languages.shtml

Documentation DVD

Cisco documentation and additional literature are available in a Documentation DVD package, which may have shipped with your product. The Documentation DVD is updated regularly and may be more current than printed documentation. The Documentation DVD package is available as a single unit.

Registered Cisco.com users (Cisco direct customers) can order a Cisco Documentation DVD (product number DOC-DOCDVD=) from the Ordering tool or Cisco Marketplace.

Cisco Ordering tool:

http://www.cisco.com/en/US/partner/ordering/

Cisco Marketplace:

http://www.cisco.com/go/marketplace/

Ordering Documentation

You can find instructions for ordering documentation at this URL:

http://www.cisco.com/univercd/cc/td/doc/es_inpck/pdi.htm

You can order Cisco documentation in these ways:

•Registered Cisco.com users (Cisco direct customers) can order Cisco product documentation from the Ordering tool:

http://www.cisco.com/en/US/partner/ordering/

•Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco Systems Corporate Headquarters (California, USA) at 408 526-7208 or, elsewhere in North America, by calling 1 800 553-NETS (6387).

Documentation Feedback

You can send comments about technical documentation to bug-doc@cisco.com.

You can submit comments by using the response card (if present) behind the front cover of your document or by writing to the following address:

Cisco Systems
Attn: Customer Document Ordering
170 West Tasman Drive
San Jose, CA 95134-9883

We appreciate your comments.

Cisco Product Security Overview

Cisco provides a free online Security Vulnerability Policy portal at this URL:

http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html

From this site, you can perform these tasks:

•Report security vulnerabilities in Cisco products.

•Obtain assistance with security incidents that involve Cisco products.

•Register to receive security information from Cisco.

A current list of security advisories and notices for Cisco products is available at this URL:

http://www.cisco.com/go/psirt

If you prefer to see advisories and notices as they are updated in real time, you can access a Product Security Incident Response Team Really Simple Syndication (PSIRT RSS) feed from this URL:

http://www.cisco.com/en/US/products/products_psirt_rss_feed.html

Reporting Security Problems in Cisco Products

Cisco is committed to delivering secure products. We test our products internally before we release them, and we strive to correct all vulnerabilities quickly. If you think that you might have identified a vulnerability in a Cisco product, contact PSIRT:

•Emergencies — security-alert@cisco.com

•Nonemergencies — psirt@cisco.com

Tip We encourage you to use Pretty Good Privacy (PGP) or a compatible product to encrypt any sensitive information that you send to Cisco. PSIRT can work from encrypted information that is compatible with PGP versions 2.x through 8.x.

Never use a revoked or an expired encryption key. The correct public key to use in your correspondence with PSIRT is the one that has the most recent creation date in this public key server list:

http://pgp.mit.edu:11371/pks/lookup?search=psirt%40cisco.com&op=index&exact=on

In an emergency, you can also reach PSIRT by telephone:

•1 877 228-7302

•1 408 525-6532

Obtaining Technical Assistance

For all customers, partners, resellers, and distributors who hold valid Cisco service contracts, Cisco Technical Support provides 24-hour-a-day, award-winning technical assistance. The Cisco Technical Support Website on Cisco.com features extensive online support resources. In addition, Cisco Technical Assistance Center (TAC) engineers provide telephone support. If you do not hold a valid Cisco service contract, contact your reseller.

Cisco Technical Support Website

The Cisco Technical Support Website provides online documents and tools for troubleshooting and resolving technical issues with Cisco products and technologies. The website is available 24 hours a day, 365 days a year, at this URL:

http://www.cisco.com/techsupport

Access to all tools on the Cisco Technical Support Website requires a Cisco.com user ID and password. If you have a valid service contract but do not have a user ID or password, you can register at this URL:

http://tools.cisco.com/RPF/register/register.do

Note Use the Cisco Product Identification (CPI) tool to locate your product serial number before submitting a web or phone request for service. You can access the CPI tool from the Cisco Technical Support Website by clicking the Tools & Resources link under Documentation & Tools. Choose Cisco Product Identification Tool from the Alphabetical Index drop-down list, or click the Cisco Product Identification Tool link under Alerts & RMAs. The CPI tool offers three search options: by product ID or model name; by tree view; or for certain products, by copying and pasting show command output. Search results show an illustration of your product with the serial number label location highlighted. Locate the serial number label on your product and record the information before placing a service call.

Submitting a Service Request

Using the online TAC Service Request Tool is the fastest way to open S3 and S4 service requests. (S3 and S4 service requests are those in which your network is minimally impaired or for which you require product information.) After you describe your situation, the TAC Service Request Tool provides recommended solutions. If your issue is not resolved using the recommended resources, your service request is assigned to a Cisco TAC engineer. The TAC Service Request Tool is located at this URL:

http://www.cisco.com/techsupport/servicerequest

For S1 or S2 service requests or if you do not have Internet access, contact the Cisco TAC by telephone. (S1 or S2 service requests are those in which your production network is down or severely degraded.) Cisco TAC engineers are assigned immediately to S1 and S2 service requests to help keep your business operations running smoothly.

To open a service request by telephone, use one of the following numbers:

Asia-Pacific: +61 2 8446 7411 (Australia: 1 800 805 227)
EMEA: +32 2 704 55 55
USA: 1 800 553-2447

For a complete list of Cisco TAC contacts, go to this URL:

http://www.cisco.com/techsupport/contacts

Definitions of Service Request Severity

To ensure that all service requests are reported in a standard format, Cisco has established severity definitions.

Severity 1 (S1)—Your network is "down," or there is a critical impact to your business operations. You and Cisco will commit all necessary resources around the clock to resolve the situation.

Severity 2 (S2)—Operation of an existing network is severely degraded, or significant aspects of your business operation are negatively affected by inadequate performance of Cisco products. You and Cisco will commit full-time resources during normal business hours to resolve the situation.

Severity 3 (S3)—Operational performance of your network is impaired, but most business operations remain functional. You and Cisco will commit resources during normal business hours to restore service to satisfactory levels.

Severity 4 (S4)—You require information or assistance with Cisco product capabilities, installation, or configuration. There is little or no effect on your business operations.

Obtaining Additional Publications and Information

Information about Cisco products, technologies, and network solutions is available from various online and printed sources.

•Cisco Marketplace provides a variety of Cisco books, reference guides, and logo merchandise. Visit Cisco Marketplace, the company store, at this URL:

http://www.cisco.com/go/marketplace/

•Cisco Press publishes a wide range of general networking, training and certification titles. Both new and experienced users will benefit from these publications. For current Cisco Press titles and other information, go to Cisco Press at this URL:

http://www.ciscopress.com

•Packet magazine is the Cisco Systems technical user magazine for maximizing Internet and networking investments. Each quarter, Packet delivers coverage of the latest industry trends, technology breakthroughs, and Cisco products and solutions, as well as network deployment and troubleshooting tips, configuration examples, customer case studies, certification and training information, and links to scores of in-depth online resources. You can access Packet magazine at this URL:

http://www.cisco.com/packet

•iQ Magazine is the quarterly publication from Cisco Systems designed to help growing companies learn how they can use technology to increase revenue, streamline their business, and expand services. The publication identifies the challenges facing these companies and the technologies to help solve them, using real-world case studies and business strategies to help readers make sound technology investment decisions. You can access iQ Magazine at this URL:

http://www.cisco.com/go/iqmagazine

•Internet Protocol Journal is a quarterly journal published by Cisco Systems for engineering professionals involved in designing, developing, and operating public and private internets and intranets. You can access the Internet Protocol Journal at this URL:

http://www.cisco.com/ipj

•World-class networking training is available from Cisco. You can view current offerings at this URL:

http://www.cisco.com/en/US/learning/index.html

This document is to be used in conjunction with the documents listed in the "Related Documentation" section.

CCSP, CCVP, the Cisco Square Bridge logo, Follow Me Browsing, and StackWise are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, and iQuick Study are service marks of Cisco Systems, Inc.; and Access Registrar, Aironet, ASIST, BPX, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Empowering the Internet Generation, Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step, FormShare, GigaDrive, GigaStack, HomeLink, Internet Quotient, IOS, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, LightStream, Linksys, MeetingPlace, MGX, the Networkers logo, Networking Academy, Network Registrar, Packet, PIX, Post-Routing, Pre-Routing, ProConnect, RateMUX, ScriptShare, SlideCast, SMARTnet, StrataView Plus, TeleRouter, The Fastest Way to Increase Your Internet Quotient, and TransPath are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.

All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0502R)

Copyright © 2005 Cisco Systems, Inc. All rights reserved.

Cisco Unified Communications Manager (CallManager)

Release Notes for Cisco Unified CallManager Release 4.1(3)

Hierarchical Navigation

Downloads

Table Of Contents

Release Notes for Cisco CallManager Release 4.1(3)

Contents

Introduction

System Requirements

Determining the Software Version

Compatibility Matrix and Supported Upgrades

Related Documentation

New and Changed Information

Cisco CallManager Installation, Upgrade, and Backup Guidelines

Installation and Upgrade

Upgraded Memory Requirement

Adding Cisco CallManager Servers as Members of a Windows Domain

Upgrade Assistant Utility

Backup and Restore

Operating System Installation Guidelines

Upgrading to Cisco CallManager Release 4.1(3)

Before Upgrading to Cisco CallManager 4.13

Call Pickup and Group Call Pickup Enhancements

Call Pickup Enhancements

Group Call Pickup Enhancements

Other Group Pickup Enhancements

Call Transfer Enhancements

New Feature Support with Cisco IP Manager Assistant

New Service Parameter to Enable Music On Hold and Annunciator Duplex Streaming

Updated Support for Cisco IP Phones

New Hunt Pilot Configuration Parameters for Automated Alternate Routing

Support for Annex M1 over H.225 Trunks and H.323 Gateways

Security Enhancements

Support for Secure Cisco IOS MGCP Gateway Troubleshooting

Configuring Security for Voice-Mail Ports

Bulk Administration Tool Enhancements

BAT Support for Call Pickup Groups

New Call Classification Field Description

Dialed Number Analyzer Enhancements

New and Changed Information for Cisco CallManager Serviceability

Call Type Update in the CDR Search Results

New and Changed Information for Third-Party and SDK Applications

JTAPI Enhancements

CDR Records Update for Call Pickup Features

Important Notes

CSCso79248 Do Not Run installxml.vbs in Unified CM Release 3.3 and Later

Using Cisco Unity Consult Transfer with Cisco CallManager Onhook Call Transfer

Performing CAPF Operations on Cisco IP Phones via VPN Connection

Adding Cisco CallManager Servers

Locale Installer for Cisco CallManager Release 4.1(3)

Using the JTAPI Update Utility with CRS

Upgrade Requirements for CRS and Cisco CallManager 4.1

NetMeeting Calls Fail When T.38 is Advertised to NetMeeting

Cisco CallManager Installation Status Bar

CTI Route Point Considerations

Cisco CallManager Extension Mobility Scalability Update

Disabling IPSec for Cisco CallManager Upgrades

Disabling IPSec on the Cisco CallManager Server

Enabling IPSec on the Cisco CallManager Server

Support for Multicluster Integration with Active Directory

Requirement for Installation of Java Virtual Machine

JRE Installation

Resolved Caveats for Cisco CallManager - Release 4.1(3)

Using Bug Toolkit

Saving Bug Toolkit Queries

Open Caveats for Cisco CallManager - Release 4.1(3)

Documentation Updates

Errors

Java Runtime Environment

Cisco CallManager Dialed Number Analyzer Service Startup Type

Barging into Encrypted Calls with the Cisco IP Phone Model 7970

Using Valid Characters in Cisco CallManager User IDs

Cisco CallManager Security Guide Corrections

Removing a Subscriber Server from Cisco CallManager

Remove Redundant DCD Replication Agreements

Using Script Files to Remove a Subscriber Server from Cisco CallManager

Remove Subscriber Information

Run RemovePublisher.bat Script on Publisher Server

Contents of the RemovePublisher.bat Script File

Contents of the RemoveSubscriber.bat Script File