Home | Skip to Content | Skip to Search | Skip to Navigation | Skip to Footer |
Worldwide [change] |Register |About Cisco
Guest

Hierarchical Navigation

Cisco Unified Communications Manager (CallManager)

Release Notes for Cisco CallManager Release 3.3(4)

Downloads

Table Of Contents

Release Notes for Cisco CallManager Release 3.3(4)

Contents

Introduction

System Requirements

Determining the Software Version

Compatibility Matrix and Supported Upgrades

Related Documentation

New and Changed Information

Forced Authorization Codes and Client Matter Codes

Cisco WebDialer

Cisco IP Telephony Backup and Restore System (BARS)

New and Updated Phone Support

Extension Mobility Enhancements

Cisco Security Agent

Dialed Number Analyzer (DNA)

Image Authentication

NM-HDV2 and NM-HD Support for Cisco CallManager

Conferencing Enhancements

Block External To External Transfer Service Parameter

International Dial Plan

Calling Search Space Enhancements

Default Trace Level Changed for Cisco Database Layer Monitor Service

Important Notes

Application Error During an Upgrade

Adding Cisco CallManager Servers

Using the Ping Command During Installation

Locale Installer for Cisco CallManager Release 3.3(4)

MLA for Cisco CallManager 3.3(4)

Cisco CallManager Renamed After Restarting Services

VirusScan on Cisco CallManager Servers

Region Configuration

QSIG Support

Supported Characters in the Directory

Cisco CallManager Integration with Corporate Directories

Installing IPMA Assistant Console on Microsoft Windows XP

Cisco VG248 Analog Phone Gateway (VG248) Support

Changing User IDs

Settings Access on Cisco IP Phone 7940/7960

Cisco CallManager Attendant Console

Upgrading Cisco CallManager Extension Mobility

End User Notes

Attendant Console

Ring Settings

Cisco IPMA

User Login Name and Password

Phone Hardening

Resolved Caveats for Cisco CallManager - Release 3.3(4)

Open Caveats for Cisco CallManager - Release 3.3(4)

Documentation Updates

Errors

Locale Installer

Microsoft Outlook Support with Cisco WebDialer

Changes

Cisco CallManager Attendant Console

Calling Search Space

Cisco CallManager Extension Mobility Logout

Custom Phone Rings

Omissions

New Service Parameter for Cisco CallManager Extension Mobility

H.323 Configuration Settings

Defining the Quality of Service (QoS) Values

Quality Report Tool Configuration Settings

Exporting and Importing Phones with More Than One User

Device Profile Default Configuration

Subscribing Services to a Device Profile Default

User Settings in Cisco CallManager Administration

Obtaining Documentation

Cisco.com

Ordering Documentation

Documentation Feedback

Obtaining Technical Assistance

Cisco Technical Support Website

Opening a TAC Case

TAC Case Priority Definitions

Obtaining Additional Publications and Information


Release Notes for Cisco CallManager Release 3.3(4)

June 28, 2004

These release notes describe the new features and caveats for Cisco CallManager Release 3.3(4).

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

To access the documentation suite for voice products, refer to

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

Access the latest software upgrades and release notes for Cisco CallManager 3.3 on Cisco Connection Online (CCO) at

http://www.cisco.com/kobayashi/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

•Important Notes

•Resolved Caveats for Cisco CallManager - Release 3.3(4)

•Open Caveats for Cisco CallManager - Release 3.3(4)

•Documentation Updates

•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 3.3 on a Cisco Media Convergence Server (MCS) or on a Cisco Integrated Communications System (ICS) 7750.

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

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

Access the correct Cisco-approved server configuration for IBM server or HP server at

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

Determining the Software Version

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

•Cisco CallManager System version

•Cisco CallManager Administration version

•Database information and database DLL versions

Compatibility Matrix and Supported Upgrades

You can find the minimum versions with which Cisco CallManager Release 3.3(4) has been tested and which previous release of Cisco CallManager has upgrade support 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 proves to be incompatible with Cisco CallManager, you need to wait until a compatible version of the product becomes available before you upgrade to Cisco CallManager Release 3.3(4). 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 3.3 at

http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/3_3/doc_gd

Along with the documents listed in the Cisco CallManager Document Guide, the following list gives other related documents for Cisco CallManager Release.

•Skinny Client Control Protocol Messaging Guide

•Cisco CallManager Call Detail Record Definition

•Cisco IP Phone Services Application Development Notes

•Cisco CallManager 3.3 JTAPI Installation Guide

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

•Cisco CallManager 3.3 TAPI Installation Guide

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

•Cisco CallManager Extension Mobility API Developer's Guide

•System Error Message

New and Changed Information

This section describes new features and changes that are pertinent to this release of Cisco CallManager.

Forced Authorization Codes and Client Matter Codes

Forced Authorization Code (FAC) and Client Matter Code (CMC) allow you to manage call access and accounting. CMC assists with call accounting and billing for billable clients, while FACs regulate the types of calls that certain users can place.

Client Matter Codes force the user to enter a code to specify that the call relates to a specific client matter. You can assign CMC to customers, students, or other populations for call accounting and billing purposes. The Forced Authorization Code feature forces the user to enter a valid authorization code before the call completes.

The CMC and FAC features require that you make changes to route patterns and perform configuration tasks for CMC and FAC in Cisco CallManager Administration (Choose Feature > Client Matter Code or Feature > Forced Authorization Code).

You can use BAT to insert, update, and delete CMC and FAC and CDR Analysis and Reporting (CAR) to run reports that provide call details for authorization code names, authorization levels, and CMCs.

Caution When you enable FAC or CMC in route patterns, applications that do not pass the FAC or CMC code cannot complete a call. The call times out and fails. This affects all applications, such as Cisco Customer Response Solutions (Cisco CRS) that pass calls through a route pattern with FAC or CMC enabled. You must use a route pattern with FAC and CMC disabled or configure the application to pass the FAC or CMC code that was entered by the user to Cisco CallManager. Refer to the application's documentation to find out how you can configure your application to support FAC/CMC.

Note In the Cisco CallManager 3.3(4) release, CTI does not support the tones that are associated with FAC/CMC; if a user places a call through a TAPI or JTAPI application that uses a FAC/CMC-enabled route pattern, the call times out and fails. Cisco strongly recommends that you do not configure FAC/CMC-enabled route patterns for any 3.3(4) compatible TAPI or JTAPI application, including Cisco-supported or Cisco-approved, third-party applications (for example, IVR, SoftPhone, etc.).

How This Feature Affects the User

When enabled, these features force the user to enter a valid account code or authorization code before the call completes. A distinctive tone prompts the user.

You should tell affected end users how to recognize the audio prompts, and the codes that users need to enter, as well as the consequences or symptoms that are associated with failing to enter a valid code.

Currently, the end-user documentation does not contain any instructions about how to use these features.

Where to Find More Information

•Cisco CallManager Features and Services Guide

•Bulk Administration Tool User Guide

•Cisco CallManager Serviceability Administration Guide

•Cisco CallManager Serviceability System Guide.

Cisco WebDialer

Cisco WebDialer allows Cisco IP Phone users to make telephone calls by using web and desktop applications. When you enable your company directory search page by using Cisco WebDialer, a user can make calls by clicking a hyperlinked telephone number.

In Cisco CallManager 3.3(3), users obtains Cisco WebDialer as a download from www.cisco.com. In Cisco CallManager 3.3(4), Cisco WebDialer exists as a service in Cisco CallManager Serviceability.

How This Feature Affects the User

Some current versions of model-specific user guides do not mention Cisco WebDialer features—even though the phone supports these features and the feature might be accessible to end users. Refer users to Customizing Your Cisco IP Phone on the Web for instructions on using these features.

Where to Find More Information

•Cisco CallManager Features and Services Guide

Cisco IP Telephony Backup and Restore System (BARS)

Cisco CallManager 3.3(4) uses the Cisco IP Telephony Backup and Restore System (BARS) for backup and restore operations, including backing up data, restoring data, and restoring servers. This application, which you can use for manual or scheduled backups, supports compatible versions of Cisco CallManager, Cisco Emergency Responder, Cisco Customer Response Applications/Solutions (CRA/CRS), and Cisco CDR Analysis and Reporting (CAR).

Where to Find More Information

•Cisco CallManager Compatibility Matrix to identify which version of BARS supports this version of Cisco CallManager

•Cisco IP Telephony Backup and Restore System (BARS) documentation that supports this version of Cisco CallManager.

New and Updated Phone Support

The following information describes new and updated phone support for this Cisco CallManager release. The applicable documentation may not provide the following information.

•Cisco CallManager Release 3.3(4) includes support for Cisco IP Conference Station 7936, Cisco Wireless IP Phone 7920, and Cisco IP Phone model 7970.

•Cisco CallManager 3.3(4) supports Cisco IP Communicator, a Skinny Client Control Protocol (SCCP) based desktop application that turns your computer into a full-featured Cisco IP Phone.

•Cisco CallManager Attendant Console supports Cisco IP Phone Models 7902, 7905, 7912, 7940, 7960, and 7970.

•Cisco CallManager allows you to tighten security on certain phones by disabling phone settings in Cisco CallManager Administration.

•Cisco CallManager supports phone image authentication.To identify which phones support image authentication, see "Image Authentication" section.

Where to Find More Information

•Cisco IP Conference Station 7936 Administration Guide

•Cisco Wireless IP Phone 7920 Administrator Guide

•Cisco IP Phone 7970 Administration Guide for Cisco CallManager

•Cisco IP Communicator Administration Guide

•Cisco CallManager System Guide

Extension Mobility Enhancements

Cisco CallManager 3.3(4) extends Cisco CallManager Extension Mobility functionality to Cisco IP Phones 7905, 7912, 7970, and Cisco IP Communicator.

How This Feature Affects the User

Some current versions of model-specific user guides do not mention Cisco Extension Mobility—even though the phone supports these features are and the features might be accessible to end users. Refer users to Customizing Your Cisco IP Phone on the Web for instructions on using these features

Cisco Security Agent

Cisco CallManager 3.3(4) supports Cisco Security Agent with specific Cisco CallManager profiles. Cisco Security Agent provides host intrusion detection capability on Cisco CallManager servers.

Where to Find More Information

•Cisco CallManager Compatibility Matrix to identify which version of Cisco Security Agent supports this version of Cisco CallManager.

Dialed Number Analyzer (DNA)

The Dialed Number Analyzer tool (DNA), an installable plug-in for Cisco CallManager, runs as a service on the server, and it allows you to test a Cisco CallManager dial plan configuration prior to deploying it or to analyze dial plans after the dial plan is deployed. You can use the results to diagnose a dial plan, to identify potential problems, and to tune a dial plan.

Note Cisco CallManager Dialed Number Analyzer does not support Netscape Navigator, version 4.61. Use Internet Explorer to analyze dial plans.

Where to Find More Information

•Cisco CallManager Dialed Number Analyzer Guide

Image Authentication

Image authentication prevents tampering with the binary image; that is, the firmware load, prior to loading it on the phone. Tampering with the image causes the phone to fail the authentication process and reject the image. Image authentication occurs through signed binary files that are automatically installed with this version of Cisco CallManager. Likewise, firmware updates that you download from cisco.com also provide signed binary images.

Cisco IP Phone models 7970, 7960, 7940, 7912, 7910, 7905G, and 7902G support image authentication with Cisco CallManager Release 3.3(4).

NM-HDV2 and NM-HD Support for Cisco CallManager

In Cisco CallManager 3.3(4), NM-HDV2 and NM-HD, which support Cisco 2600XM, Cisco 2691, Cisco 3725, Cisco 3745, and Cisco Access Routers, can provide the following number of transcoder and conference sessions, which serve as the maximum number of sessions that are supported:

Tip Some supported gateways, for example, the Cisco 2600XM, cannot support the maximum number of sessions because of a CPU power limitation.

In addition to the preceding gateways, NM-HD supports the Cisco 3660.

Per NM-HDV2

•G.711 only conference—50

•G.729 conference—32

•GSM FR conference—14

•GSM EFR conference—10

Tip Maximum number of participants per conference equals eight.

•Transcoding for G.711 to G.729a/G.729ab/GSMFR—128

•Transcoding for G.711 to G.729/G.729b/GSM EFR—96

Per NM-HD

•G.711 only conference—24

•G.729 conference—6

•GSM FR conference—2

•GSM EFR conference—1

Tip Maximum number of participants per conference equals eight.

•Transcoding for G.711 to G.729a/G.729ab/GSMFR—24

•Transcoding for G.711 to G.729/G.729b/GSM EFR—18

To configure Cisco CallManager 3.3(4) transcoder and conference support for these modules, choose the following existing options in Cisco CallManager Administration:

•For conference support, choose Cisco IOS Conference Bridge in the Conference Bridge Configuration window.

•For transcoder support, choose Cisco IOS Media Termination Point in the Transcoder Configuration window.

Tip In Cisco CallManager Administration, ensure that you enter the same conference bridge name that exists in the gateway Command Line Interface. For specific information on configuring conference bridges and transcoders in Cisco CallManager Administration, refer to the Cisco CallManager Administration Guide that supports 3.3(4).

Caution To maintain full functionality in your network, you may need to perform additional configuration tasks on the supported gateway. For information on any additional tasks that you must perform, refer to the specific documentation for your gateway.

Conferencing Enhancements

Cisco CallManager Administration provides the clusterwide service parameter, Drop Ad hoc Conference When Creator Leaves, so you can drop ad hoc conferences after the conference controller hangs up the phone.

By default, Cisco CallManager sets the parameter to False. If you set the parameter to True, the conference automatically ends when the conference controller hangs up; likewise, Cisco CallManager releases all resources that are assigned to the conference. Be aware that Cisco CallManager does not support both options; that is, all conferences will support the same functionality depending on the option that you choose.

Tip If the conference controller transfers, parks, or redirects the conference to another party, the party that retrieves the call acts as the virtual controller for the conference. If you set the parameter to True and a virtual controller exists, the conference does not end until the virtual controller hangs up the phone.

A virtual controller cannot add new parties to the conference, but a virtual controller can transfer, park, or redirect the conference to another party, who would, in turn, become the virtual controller of the conference.

To change the value of the service parameter, perform the following procedure:

Procedure

Step 1 From Cisco CallManager Administration, choose Service > Service Parameter.

Step 2 From the Server drop-down list box, choose a server in the cluster.

Step 3 From the Service drop-down list box, choose Cisco CallManager.

Step 4 From the Drop Ad hoc Conference When Creator Leaves drop-down list box, choose True.

Step 5 Click Update.

Block External To External Transfer Service Parameter

The Block External To External Transfer service parameter of the Cisco CallManager service allows administrators to prevent users from transferring external calls to another external number. This parameter specifies values as True or False. Setting the parameter to True blocks external calls from being transferred to another external device. The default value specifies False. You can modify the Block External To External Transfer service parameter in the Service Parameters Configuration window.

International Dial Plan

Cisco CallManager International Dial Plan provides country-specific dialing functionality for countries outside the North American Numbering Plan (NANP). The international dial plan includes route pattern wildcards, special characters, calling party transformation settings, and called party transformation settings that non-NANP dial plans use. It also describes the Discard Digit Instructions (DDIs) and tags that dial plans of specific countries use. Cisco CallManager currently supports international dial plans for Japan, the Netherlands, and Portugal.

Where to Find More Information

•Cisco CallManager International Dial Plan Deployment Guide.

Calling Search Space Enhancements

Cisco CallManager 3.3(4) provides database enhancements for Calling Search Spaces, so you can make updates to Calling Search Spaces during regular business hours. Cisco removed the Restart Devices button from the Calling Search Space Configuration window in Cisco CallManager Administration because you do not need to restart the associated devices after you update a calling search space. To save your updates, remember to click Update after you make changes.

Default Trace Level Changed for Cisco Database Layer Monitor Service

In Cisco CallManager 3.3(4), the default trace level for the Cisco Database Layer Monitor service changed from Error to Significant.

If you change the default trace level before you upgrade the cluster to Cisco CallManager 3.3(4), your setting does not change after the upgrade. If you do not change the default trace level before the upgrade, the setting changes to Significant.

Important Notes

The following section contains important information that may not have been available in the initial release of documentation for Cisco CallManager Release 3.3(4).

Application Error During an Upgrade

When you upgrade to Cisco CallManager 3.3(4), you may encounter the following error message:

InsertCDR.exe - Application Error, The instruction at "0x10250fe7" referenced memory at "0x0000000". The memory could not be "read". Click OK to terminate program.

You should click OK to exit the dialog box and to continue with the installation of Cisco CallManager 3.3(4). Clicking OK does not terminate your installation; in fact, clicking OK will allow you to successfully upgrade your Cisco CallManager system.

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.

Using the Ping Command During Installation

The publisher database server serves as the master database for all servers in the cluster. All servers except the publishing database server maintain subscriber databases, which are copies of the publisher database server. If you are configuring a subscriber database server, make sure that the server that you are installing can connect to the publishing database server before the installation can continue. The installation process necessitates this connection, so the publisher database server can be copied to the local drive on the subscriber server. To make sure a good connection exists between the servers, issue a ping command from the subscriber server to the publisher database server before you try to authenticate to it. Use only a hostname (for example, `hostname.cisco.com') with the ping command. If the ping command is not successful, you must exit the installation program, fix the problem, and begin the installation process again.

The Installing Cisco CallManager Release 3.3(4) and Upgrading Cisco CallManager Release 3.3(4) documents incorrectly state to use a fully qualified domain name with the ping command.

Locale Installer for Cisco CallManager Release 3.3(4)

You can use Cisco IP Telephony Locale Installer version 3.3(3) with Cisco CallManager Release 3.3(4). Be aware that all phrases may not display in the desired locale when you install Locale Installer on a Cisco CallManager 3.3(4) system.

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

MLA for Cisco CallManager 3.3(4)

To maintain full multilevel administration access functionality in Cisco CallManager 3.3(4), you must use Cisco CallManager Multilevel Administration Access, Release 1.2(3). If you do not install Cisco MLA 1.2(3), you will only be able to log in to Cisco CallManager Administration with the administrator password.

Cisco CallManager Renamed After Restarting Services

If you deactivate the Cisco CallManager service in Cisco CallManager Serviceability, the Cisco CallManager where you deactivated the service no longer exists in the database. Hence, you cannot choose the Cisco CallManager for configuration operations in Cisco CallManager Administration because it will not display in the graphical user interface (GUI).

If you reactivate the Cisco CallManager service on the Cisco CallManager, the database creates a Cisco CallManager and adds a "CM_" prefix to the server name or IP address; for example, if you reactivate the Cisco CallManager service on a server with an IP address of 172.19.140.180, CM_172.19.140.180 displays in Cisco CallManager Administration. You can choose the new Cisco CallManager in Cisco CallManager Administration.

VirusScan on Cisco CallManager Servers

If you are using Microsoft Windows OS version 2000.2.4SR5 or 2000.2.5 with McAfee Netshield 2000 or McAfee VirusScan Enterprise Edition, you may encounter a problem authenticating to Cisco CallManager Administration or accessing some areas of Cisco CallManager Administration. Cisco CallManager displays an "HTTP Error 500-12 Application Restarting" error message.

To resolve this problem, you will need to upgrade McAfee Netshield and McAfee VirusScan to use VirusScan Engine Version 4.2.60 or later. You can obtain the latest Virus Scan updates from the Network Associates website.

Region Configuration

The Region Configuration window displays an Items per page drop-down list box that allows you to list 10, 20, 50, 100, or All configured regions. If you choose to display 100 or more regions, Cisco CallManager may experience performance degradation.

QSIG Support

Cisco offers support for Q.SIG basic call and ID services for selected MGCP-controlled gateways and for selected PBX. ID services support depends upon the PBX type. You can find a list of compatible gateways for which Cisco CallManager Release 3.3(4) has been tested at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/ccmcomp.htm

Supported Characters in the Directory

Caution Using non-ISO-Latin1 characters greater than 127 with DC Directory, Netscape Directory, or Active Directory can cause directory database errors. Cisco CallManager Release 3.3 supports all ISO-Latin1 (ISO-8859-1) characters and all non-ISO-Latin1 characters in the range 0-127 with any directory.

Cisco CallManager only supports ISO-Latin1 and ASCII characters in the User area of Cisco CallManager Administration.

After you download the locale installer, you can display field names in the User area of Cisco CallManager Administration in your chosen language. However, Cisco CallManager only supports ISO-Latin1 (ISO-8859-1) characters and non-ISO-Latin1 characters in the range 0-127 in the fields and in all user accounts and passwords that are needed to access these windows. If a user enters data that is not in the allowed character range, a dialog box displays and states that the user must enter data by using only ISO-Latin1 characters and non-ISO-Latin1 characters in the range 0-127.

CDR Analysis and Reporting (CAR) supports all ISO-Latin1 (ISO-8859-1) characters and non-ISO-Latin1 characters in the range 0-127.

Cisco CallManager Integration with Corporate Directories

If you have integrated Cisco CallManager with Active Directory or Netscape Directory, you must run the Cisco Customer Directory Configuration Plugin that is packaged with this release on all the Cisco CallManager servers in the cluster beginning with the publisher. You must complete this step after you have successful upgraded your Cisco CallManager server to Release 3.3(4). To ensure that Cisco CallManager can install the latest schema and new configuration information in the directory, you must enter a user, who has the rights to update the schema, in the Directory Administrator DN. For more information on installing the Cisco Customer Directory Configuration Plugin, refer to Installing the Cisco Customer Directory Configuration Plugin for Cisco CallManager Release 3.3.

Installing IPMA Assistant Console on Microsoft Windows XP

The installation for Assistant Console for IPMA service fails because Internet Explorer 6 on Windows XP does not include Microsoft Java Virtual Machine (JVM). This does not cause a problem if the system has Microsoft Windows XP Service Pack 1 installed. If the system does not have Microsoft Windows XP Service Pack 1, you can use Netscape browsers or install the Sun Java Virtual Machine plugin for Internet Explorer from http://java.sun.com/getjava/download.html.

After installing the Sun JVM plugin, continue the IPMA assistant console installation from http://<server>/ma/Install/IPMAConsoleInstallJar.jspl where <server> represents the IP address of the Cisco CallManager server.

Cisco VG248 Analog Phone Gateway (VG248) Support

When using the VG248 with Cisco CallManager 3.3, add the device as a Cisco VG248 gateway and configure each port as VGC phone model. This consolidates each of the 48 analog or SMDI ports onto a single device. However, you still must configure these ports in the VG248 interface, and you should not enter any values in the Port Specific fields of the Phone Configuration window. Because these fields are not operational when you are using the VG248 1.2(1) or earlier software, you must configure these settings locally on the VG248.

For details about using the VG248 with this and other Cisco CallManager versions, see the "Configuring VG248 Ports Using Cisco CallManager" in the Cisco VG248 Analog Phone Gateway Software Configuration Guide for details:

http://www.cisco.com/univercd/cc/td/doc/product/voice/c_access/apg/vg248/v1_2/sw_confg/index.htm

To view the latest compatibility information about the VG248 and Cisco CallManager, access the Cisco VG248 Analog Phone Gateway Version Release Notes on Cisco.com at the following location:

http://www.cisco.com/univercd/cc/td/doc/product/voice/c_access/apg/vg248/v1_2/rel_note/vg248rn6.htm

Changing User IDs

Cisco CallManager does not support changing an existing user ID in the directory. Some applications, such as Cisco IPMA and Extension Mobility, may not function properly when you change the user ID.

Settings Access on Cisco IP Phone 7940/7960

Users cannot access any button settings when you disable Settings Access for an individual Cisco IP Phone. This includes the settings to change ring type, volume level, and contrast level.

Cisco CallManager Attendant Console

Cisco CallManager Administration 3.3(4) provides the Cisco CallManager Attendant Console 1.2(1) plugin, although Cisco CallManager Administration Guide 3.3(4) and Cisco CallManager System Guide 3.3(4) support Cisco CallManager Attendant Console 1.1(3). To obtain documentation for attendant console 1.2(1), click the following URL: http://www.cisco.com/univercd/cc/td/doc/product/voice/attendnt/call_att/index.htm.

Upgrading Cisco CallManager Extension Mobility

If you run Cisco CallManager Extension Mobility and Cisco CallManager 3.1 or 3.2 before the upgrade, you must perform additional configuration tasks after the upgrade, so Cisco CallManager Extension Mobility runs as expected. For more information on configuration tasks, refer to the Cisco CallManager Extension Mobility upgrade section of the Cisco CallManager Features and Services Guide for 3.3.

End User Notes

The following section contains important information that affects the end user. Some features affect Cisco IP Phone end users but might not be included in model-specific documentation for the end user. Cisco suggests that you pass the information on to affected end users.

Attendant Console

Be aware that the attendant console user cannot drag a speed-dial entry onto a call in the Call Details pane.

Be aware that the attendant console user cannot rename a speed-dial group from the Edit menu.

Be aware that the Call Forward All to the voice mail icon and the Forward All to another directory number icon do not display in the Speed Dial window.

Ring Settings

The Ring Settings window, a new feature in the Cisco IP Phone User Options GUI, allows end users to assign distinctive ring tones to their phone line(s) from their computers. Users can access the Ring Settings window from the User Options main menu. The system administrator determines feature availability.

Cisco IPMA

Be aware that a Cisco IPMA assistant can support up to 33 proxy lines.

Be aware that a Cisco IPMA manager can have up to 10 assistants.

User Login Name and Password

Cisco CallManager supports only ISO-Latin1 (ISO-8859-1) characters and non-ISO-Latin1 characters in the range 0-127 in user login fields. This restriction affects services or applications that retrieve user login data from the Cisco CallManager database (such as the Cisco IP Phones, Cisco User Options, and the Cisco IPMA service).

If a user enters data that is not in the allowed character range, a dialog box displays and states that the user must enter data by using only ISO-Latin1 characters and non-ISO-Latin1 characters in the range 0-127. System administrators can advise end users who encounter this error message to enter a user name and/or password in only one of the following languages: Danish, Dutch, English, French, German, Italian, Norwegian, Portuguese, Spanish, Swedish, Hungarian, Polish, Greek, or Japanese.

Phone Hardening

Phone hardening options allow you to configure settings that restrict phone features and functionality for security purposes.

As part of phone hardening, you can disable user access to Cisco CallManager User Options and some phone settings (including those settings that are normally accessible via the Settings button). Because disabling access to these features will directly impact end users, you should advise affected users about the restrictions.

For more information about phone hardening, refer to the "Cisco IP Phone" chapter in Cisco CallManager System Guide.

End-user documentation mentions the possibility of restricted access to some settings; however, Cisco suggests that you provide more detailed information to users who are affected by phone hardening.

Note You configure phone hardening options in the Phone Configuration window of Cisco CallManager Administration. Phone hardening configuration options vary by phone model.

Resolved Caveats for Cisco CallManager - Release 3.3(4)

Table 1 lists and describes caveats that were resolved in Cisco CallManager Release 3.3(4).

Tip If you have an account with Cisco.com (Cisco Connection Online), you can use the Bug Toolkit to find caveats of any severity for any release.

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

Table 1 Resolved Caveats for Cisco CallManager Release 3.3(4) 

Identifier
Summary

CSCdv59928

Cisco CallManager does not remove a CTI device from an internal table when the CTI device unregisters.

CSCdv88850

Calls get disconnected when the calls are transferred across an intercluster trunk.

CSCdx00431

CTI ignores indicator and displays incoming number instead of displaying a message indicating that the call is private.

CSCdy88595

The configuration file for IOS MGCP Gateway does not get updated when the endpoints are deleted.

CSCdz04480

Updates to the Music on Hold (MOH) server do not occur until you reset the server.

CSCdz22424

Cisco Messaging Interface Service Parameters have incorrect definition.

CSCdz24796

Cisco CallManager does not set a default codec when you add a region in Cisco CallManager Administration.

CSCdz25060

Cisco CallManager only redirects calls for the first nine pickup groups.

CSCdz72286

The Voice Mail Port wizard throws a COM error when you enter a long pilot DN.

CSCea01730

Cisco CallManager displays a CDBLException Dump message when an administrator deletes a partition that is in use by a call park/call pickup/meetme number.

CSCea03795

The names and descriptions for IP Phone Service Parameters on the Cisco CallManager User pages do not display Russian characters.

CSCea11716

Cisco CallManager did not respond immediately to a clear MWI message.

CSCea13557

The Music on Hold (MOH) server displays the incorrect number of resources when a Cisco CallManager cluster is rebooted.

CSCea14510

DC directory replication fails when you upgrade a system that has a large database.

CSCea45346

WS-6608-E1 does not support mu-law pulse code modulation (PCM).

CSCea52428

The connection list displays a connection when it should be empty.

CSCea53538

Cisco CallManager displays an error message when you conduct a search of the subscriber global directory after adding a new user to the DC directory database.

CSCea54802

H.323 inbound faststart intercluster call fails.

CSCea55522

The art_log.ldf transaction log increases to 1 GB in size.

CSCea59099

An external PSTN call stays in the queue after an attendant console transfer.

CSCea59673

Java Telephony Application Programming Interface (JTAPI) does not send a CallCtlConnEstablished event for an unmonitored device after a blind transfer.

CSCea62899

Cisco CallManager upgrade fails when DC Directory does not terminate properly.

CSCea72465

Services hang when you reboot a server.

CSCea78545

Cisco CallManager sends an incorrect disconnect cause code for the calls to locations where bandwidth is not available.

CSCea82254

Cisco CallManager Administration displays a DBLE exception when a server is deleted.

CSCea83525

Call Detail Records (CDR) login fails when Cisco CallManager is integrated with Active Directory and Cisco CallManager Multilevel Administration Access.

CSCea84836

You cannot configure Authentication Proxy Rights on Cisco CallManager users page.

CSCea85171

The wrong event gets sent when you enable forward all on route points.

CSCea87355

Administrators get an error message when locations and CTI route points are added.

CSCea89916

The subscriber journal file can increase in size to over 1 GB.

CSCea90465

An "is empty" query on a translation pattern does not work.

CSCea92986

The audio translator does not work on files in a remote directory.

CSCeb00216

Administrators cannot set default values on clusterwide service parameters.

CSCeb00463

Some queries in the route plan report return incorrect results.

CSCeb02342

CDR Analysis and Reporting (CAR) Quality of Service (QoS) intermittently reports that data was not available for internal IP phone to IP phone calls.

CSCeb04068

You cannot enter SQL wildcard characters and bracketed expressions in the fields for a region search.

CSCeb09099

Cisco CallManager needs to update the object identifiers (OID) for labeledURI during the upgrade process.

CSCeb11140

You cannot add a MOH audio file with a single quote in the file name.

CSCeb11416

JTAPI sends a CallCtlConnNetworkReachedEv message before a call can be completed.

CSCeb13814

Cisco CallManager services restart when a H.323 trunk is reset.

CSCeb15723

Call gets dropped on an intercluster trunk when a call is transferred to a CTI route point.

CSCeb15742

Cisco CallManager does not update conference bridge resources properly.

CSCeb22383

A shared-line phone's ring state is not synchronized after a blind transfer call.

CSCeb23273

Cisco CallManager does not check and validate some CTI service parameters.

CSCeb23320

Cisco CallManager does not send a forward busy reason code for a call that is Call Forward Busy (CFB).

CSCeb23668

Cisco CallManager trace file reports an error on basic intercluster trunk calls.

CSCeb23944

Installation does not delete the temporary files after upgrading Cisco CallManager server.

CSCeb24227

Cisco CallManager Administration does not inform administrators that they need to reset or restart a device after an the Device Status Poll Interval service parameter is updated.

CSCeb24635

JTAPI sends the wrong callCtl_Cause code in the CallCtlConnAlertingEv message.

CSCeb24981

Cisco CallManager displays a CDBLException error message when you provide an entry with a missing quote character.

CSCeb25014

Cisco CallManager Administration allows you to use an invalid character in the description field in server configuration.

CSCeb25389

Cisco CallManager needs a new method to close connections for DirUser object.

CSCeb27289

CiscoIPPhoneExecute command fails to authenticate and execute with the proper credentials.

CSCeb27723

Cisco CallManager Serviceability treats the percent character (%) as wildcard in Q931 Translator Trace.

CSCeb27730

Cisco CallManager Administration displays a Javascript error when you enter a single quote in Alarm Details.

CSCeb27869

TSP locks up after completing a call with Microsoft Outlook auto-dial feature.

CSCeb28229

JTAPI did not send a CallCtlConnDisconnectedEv message.

CSCeb29036

The Call Detail Records (CDR) for Ad hoc conference (TP, Net Meeting) has incorrect values.

CSCeb30328

Cisco IPMA wizard stops when two entries exist for the same host—one entry has the hostname, and the other entry has the IP address

CSCeb30414

Cisco CallManager does not use ISO global ID in QSIG calling name.

CSCeb30508

Call Throttling fails on an H.225 intercluster trunk.

CSCeb30537

Event Viewer on Cisco CallManager shows a large number of transient connections for the Cisco IP Phone model 30 VIP.

CSCeb31088

Administrators get an application error message at the end of an installation on a publisher server.

CSCeb31499

Cisco CallManager Administration does not prompt you to restart a device when you update the default date time group settings.

CSCeb31503

Cisco CallManager Administration does not prompt you to restart a device when you update the media resources in a media resource group.

CSCeb31505

Cisco CallManager Administration does not prompt users to restart a device when you update the media resource group for a device.

CSCeb31562

Cisco CallManager sends an incorrect Redirecting Information Element identification for forwarded calls.

CSCeb31601

Changes to H.323 service parameter do not take affect until Cisco CallManager service is restarted.

CSCeb32022

Cisco CallManager Administration does not display the dependency records for a call pickup number.

CSCeb32294

Cisco CallManager Administration displays directory numbers of phones and voice mail port devices in the dependency records of calling search space.

CSCeb32323

Cisco CallManager Administration does not display Russian characters correctly.

CSCeb32402

Phone displays wrong call information for a third party when a call is answered after completing a conference.

CSCeb32712

Cisco CallManager does not validate the server name in syslog; syslog traces display the incorrect server name in the trace.

CSCeb32714

Cisco CallManager does not validate the host name that is entered in the update plugin URL field.

CSCeb32728

CDR Analysis and Reporting (CAR) does not display the QoS detail report correctly when special characters exist in the user ID field.

CSCeb32736

Users return to the same window when they click on the directory number (DN) on the dependency record link in the CTI route point window.

CSCeb32856

Cisco CallManager Administration displays a Javascript error when you attempt to add a non-gatekeeper controlled intercluster trunk by using an invalid server name.

CSCeb32886

Cisco CallManager Administration displays an undefined error message when you insert a quote character in the prefix DN field for a non-gatekeeper controlled ICT trunk.

CSCeb32915

CAR does not accept input that starts with a decimal point in the multiplication factor field.

CSCeb32923

Links in the Cisco IP Auto Attendant (AA) user preference window do not work when the name dialing value has a space

CSCeb34125

The Set Limits for Notification window does not display in Netscape Navigator when you click on the back button after receiving an error message.

CSCeb34131

CAR displays an error message when you enter a n multiplication factor of 999.999.

CSCeb34759

Cisco CallManager Administration does not display the pilot number in the dependency records for calling search space.

CSCeb35479

Cisco CallManager Administration displays an error message when you attempt to retrieve information for a phone button template with an invalid label.

CSCeb35496

Cisco CallManager displays an error message when you enter an invalid name in the phone button template window.

CSCeb35547

Cisco CallManager displays an error message when you enter a single quote in the description field while searching for a media termination point (MTP).

CSCeb35575

Cisco CallManager returns an incorrect description when you enter a space in the description field while searching for a MTP.

CSCeb35591

Cisco CallManager Administration does not allow you to use the slash (\) character in the search by description field.

CSCeb35719

Users cannot change user locale on Cisco CallManager User page.

CSCeb36091

Cisco IPMA Assistant Console does not display the Save and Cancel button for some non-English languages.

CSCeb36220

Some DC Directory default keys do not get enabled after Cisco CallManager is upgraded.

CSCeb36432

Call aborts when the agent conferences a gateway caller to Cisco Customer Response Solution (CRS) server.

CSCeb36706

A deleted Media Resource group appears in the Find and List window when the group has a dependent record.

CSCeb36921

Administrators get an error message when they delete a device that is a part of a Media Resource Group.

CSCeb36949

Deleting a user fails when the user ID field contains special characters.

CSCeb37599

Music on Hold server does not receive a registration ack message from the Cisco CallManager server.

CSCeb38185

You cannot update a directory number when you use a backslash in the display field.

CSCeb38251

Cisco CallManager Administration displays an undefined error when you use the double quote character in the gatekeeper configuration description field.

CSCeb38344

Cisco CallManager service does not start when the SDL trace file cannot be opened.

CSCeb38778

Cisco CallManager does not use the value in the Offhook to First Digit Timer field on a WS-6624 gateway.

CSCeb39111

Users in a conference call experience bad audio quality for a few seconds.

CSCeb40111

Administrators get a COM error when they delete a CTI route point that is used in a hunt group.

CSCeb40490

Cisco CallManager sends an incorrect response to a 510 error message from a Media Gateway Control Protocol (MGCP) gateway.

CSCeb40745

Cisco CallManager does not use the software media termination point as a transcoder resource between alaw and ulaw.

CSCeb40746

Cisco CallManager does not escape SQL wildcard characters and bracketed expressions in a Device Name Based Trace Monitoring query.

CSCeb40808

Cisco CallManager Serviceability displays the same results for gateways whether you enable or disable the search by trace field.

CSCeb41467

When a user has no associated device, BAT exports the MAC device entry for the previous user.

CSCeb41912

Cisco CallManager Administration displays an error message at the end of the Route Plan wizard when an administrator is using the Japanese locale.

CSCeb42012

Cisco CallManager Administration displays a misleading error message when you add a gateway without selecting a gateway type.

CSCeb42026

A phone that is attempting to barge in a call rings because a media path exists.

CSCeb42129

The upgrade assistant reports a domain check failure as an informational message.

CSCeb42197

CAR displays an incorrect key for the traffic summary report bar graph when the On Net box is not checked.

CSCeb42451

Cisco Agent Desktop (CAD) loses call control when a call is transferred to a extension that has Call Forward No Answer (CFNA) to voice-messaging enabled.

CSCeb43164

Entries in the CiCcp table do not get deleted during a redirect loop.

CSCeb43189

Cisco CallManager Administration displays a Javascript error in Trace Configuration when Cisco CTI Manager Service is stopped.

CSCeb43209

Cisco CallManager has high CPU usage when 3000 CTI users exist and a user attempts to open the CTI Enabled Users Report window.

CSCeb43285

Cisco CallManager reports incorrect values on park reversion calls in the Call Detail Record (CDR).

CSCeb44077

Redirected call fails when the call is redirected from Cisco IP Auto Attendant to another route point.

CSCeb44185

Administrators cannot run the backup utility by clicking on the backup utility link on the first CD.

CSCeb44465

You cannot disable a device level trace after reducing the trace parameter value.

CSCeb44608

The readme file in ServPrep has spelling errors.

CSCeb44800

Cisco CallManager Administration loads slowly when a large amount of calling search space exists.

CSCeb45432

Calls to phantom directory numbers that are forwarded to voice messaging fail.

CSCeb45857

Cisco CallManager Administration does not display an alert message when you use special characters.

CSCeb45871

Netscape Navigator does not clear the search criteria from the previous search in User Preferences.

CSCeb45905

Cisco CallManager Administration does not display the first page of Device Association when you choose the page link.

CSCeb45952

Third-party CTI application causes CTI manager process to stop.

CSCeb46547

Cisco IP Phone 7970 and Cisco IP Communicator does not close the service window when an extension mobility user logs in or logs out.

CSCeb46797

Region Configuration displays Video Call Bandwidth configuration parameters.

CSCeb47016

Netscape Navigator does not display the dependency records for route partition or automated alternate routing (AAR) groups when the route partition name contains a space.

CSCeb47032

Cisco CallManager Administration allows you to enter IP addresses.

CSCeb47066

Administrators get a Javascript error on Microsoft Internet Explorer when they add a pilot point without selecting a device pool.

CSCeb47114

Cisco CallManager Administration displays an error message when you enter a quote in the description field while adding a new voice-mail pilot number.

CSCeb47300

Cisco CallManager Administration fails to update associated lines when you update a device profile.

CSCeb47393

CTI Manager service stops when a route point has 256 lines.

CSCeb47435

User experiences one-way audio on calls that are transferred from PSTN to an analog phone across Cisco CallManager cluster.

CSCeb48385

Cisco CallManager does not immediately clear a call when a transcoder is not unavailable for an intercluster call.

CSCeb48454

Callback fails in a multiple callback scenario.

CSCeb49059

The ring tone cadence changes for inbound calls.

CSCeb49606

You cannot select the language locale in the Add/Delete Assistant window when an assistant has not been added.

CSCeb50331

Cisco CallManager Administration displays the exceed time limit error message when the session times out.

CSCeb50784

Cisco CallManager displays an error message when you search on voice mail by description.

CSCeb50787

Cisco CallManager returns incorrect results when you search with an empty CSS field in the Voice Mail Pilot page.

CSCeb50803

Cisco CallManager incorrectly shows that a phone is available for a callback.

CSCeb50805

Phone plays a false ringback when the ringing phone is not connected to the intercluster trunk.

CSCeb51155

Cisco CallManager displays a nondescript error message when user adds an already existing entry to the personal address book.

CSCeb51456

An error displays when user integrates Cisco CallManager server with a newly installed Netscape Directory server.

CSCeb52339

Cisco CallManager server displays a confusing message when you are replacing a server.

CSCeb52379

The upgrade assistant does not document how to contact technical support.

CSCeb52723

Cisco CallManager server upgrade fails when you upgrade a system that is using Microsoft Active Directory or Netscape Directory.

CSCeb53245

The CDR values for transfer and conference calls are incorrect.

CSCeb53318

Cisco CallManager does not check for valid characters in the host name/IP Address field in the gatekeeper configuration window.

CSCeb53374

You cannot increase the maximum number of hops for a multicast Music on Hold (MMOH) server beyond 15.

CSCeb53658

Cisco CallManager displays a GetVersion message during installation.

CSCeb53947

Cisco CallManager Release 3.3 installation fails if you cancelled a previous installation.

CSCeb54081

IP phone continues to ring when you choose callback.

CSCeb54528

Cisco CallManager displays a MohNoMoreResourcesAvailable error message when music on hold server is not configured.

CSCeb54623

Cisco CallManager trace files display errors for unassigned lines on a Cisco IP Phone Expansion Module 7914.

CSCeb54721

Filter active appears in English after you initiate a search on a device profile.

CSCeb54770

Users cannot log in after modifying the service parameter.

CSCeb54778

Cisco CallManager Serviceability does not display the CDR Analysis and Reporting tool.

CSCeb55405

Installation of a Cisco Customer Directory Configuration Plugin fails when the directory administrator password contains special characters.

CSCeb55470

A PBX or ISDN PRI switch restarts when the user-to-user information element (UUIE) is longer than the 260 octets that is defined in Q.931.

CSCeb55532

Administrators get a CDBL exception error when they add a server that is not on the network by using the hostname.

CSCeb55686

The updateServiceParameter request in AVVID XML Layer (AXL) fails to find some service parameters.

CSCeb56142

Cisco CallManager does not release the channel when a phone is disconnected.

CSCeb56524

Cisco CallManager installation displays an error message that states that it cannot find the existing Administrative Reporting Tool (ART) database version.

CSCeb56832

The information in Cisco CallManager management information base (MIB) appears out of order.

CSCeb57026

The callback key does not display when overlapping route patterns exist.

CSCeb57154

Cisco CallManager does not send the Idle state to Cisco Attendant Console at the end of a call.

CSCeb57852

MTP resources do not get released when the preexisting media connection of one endpoint fails to connect to another endpoint.

CSCeb58054

When Cisco CallManager server has overlap sending enabled, IP phone does not play the fast busy signal when a call disconnects.

CSCeb58118

Cisco CallManager uses a non-ISO standard for the facility information element.

CSCeb59294

IP phone does not display the dialed number after it receives a progress message.

CSCeb59427

Cisco CallManager does not immediately drop a call when it receives a H.225 release complete message.

CSCeb59743

Cisco CallManager subscriber servers have high CPU usage when a CTI route loop with Personal Assistant exists.

CSCeb60323

Cisco CallManager displays an incorrect message when you add conference bridge with the same name as pilot point.

CSCeb60440

Directory installation fails when the directory administrator password contains special characters.

CSCeb60593

Cisco CallManager server continues to route calls to a Primary Rate Interface (PRI) after the interface goes out of service.

CSCeb62505

Cisco CallManager has 100 percent CPU usage when you register phones with duplicate lines.

CSCeb63007

Callback to managers phone in Cisco IPMA does not work when a route point is defined as [xxx]xxx.

CSCeb63020

DC directory configuration fails when the administrator password has special character.

CSCeb63096

CDR Analysis and Reporting (CAR) does not display all users in a report.

CSCeb64249

Bandwidth does not get released and becomes oversubscribed when you resynchronize a music on hold server.

CSCeb65001

Incoming calls through Cisco Catalyst 6608 Primary Rate Interface (PRI) do not get cleared when the caller ends the call.

CSCeb65473

Cisco IP SoftPhone in an ad hoc conference call does not get released when the last party is dropped.

CSCeb65481

Call Detail Record (CDR) does not display the cause code for the last party dropped from a conference call.

CSCeb65498

CTI TSP stops while a user logs in and out of extension mobility.

CSCeb66123

Active Directory (AD) plugin installation displays Schema Update Failed error message.

CSCeb66149

Phone does not display a user name on a call between QSIG gateways.

CSCeb66617

The locale element in addUser method only works in the English locale.

CSCeb66884

Extension mobility user cannot log out on IP phone.

CSCeb67162

System users did not get created during an upgrade.

CSCeb67194

User gets a HTTP 500 error when accessing Cisco CallManager user.

CSCeb67247

The CPU usage spikes when you select the dependency records for a region.

CSCeb67383

The configuration window in Cisco CallManager Administration displays 10 regions at a time.

CSCeb68802

After a consult transfer call is received, the Cisco Agent Desktop (CAD) transfer button is grayed out.

CSCeb69344

The voice mail port wizard displays a JavaScript error message when you enter a backslash in the description or display field.

CSCeb69507

Cisco CallManager Administrator does not allow you to enter a maximum hop for multicast value between 100 and 127.

CSCeb69959

The patch.sql file did not get updated when Cisco CallManager was upgraded.

CSCeb70727

External route plan gets deleted even when a user chooses the cancel button.

CSCeb70825

Users get an error when they select a service parameter after changing the locale region setting to German.

CSCeb71025

Cisco CallManager displays an older version of JTAPI after an upgrade.

CSCeb71853

Cisco CallManager displays the media mixer on the dependency record for a media termination point.

CSCeb72096

DCD upgrades fail when the DCD password ends with a backslash.

<