Table Of Contents
Release Notes for Cisco CallManager Release 4.0(2)
Determining the Software Version
Compatibility Matrix and Supported Upgrades
Upgrading to Cisco CallManager Release 4.0(2)
Cisco CallManager Extension Mobility Enhancements
System Enhancement for Route Group and Line Group Processing
Voice Mail Configuration Enhancements
Voice-Mail Pilot Configuration
Voice-Mail Profile Configuration
Cisco Unity Voice-Mail Port Adjustments
Route List Redundancy Configuration
Operating System Installation Guidelines
Disabling Cisco RIS Data Collector Prior to Upgrading to Cisco CallManager Release 4.0(2)
New and Updated Support for Cisco IP Phones
Support for Cisco VT Advantage
Changes to Type Specific Information in the Gateway Configuration Settings
Calling Search Space Enhancements
Attendant Console Enhancements
NM-HDV2 and NM-HD Support for Cisco CallManager
Using Immediate Divert with Hunt Lists
New and Changed Information for Cisco CallManager Serviceability
Cisco CallManager Renamed After Restarting Services
Cisco CallManager Trace Collection Tool
Real-Time Monitoring Tool as Standalone Plug-in
Serviceability Reports Archive
SNMP and Performance Counter Enhancements
CDR Analysis and Reporting (CAR) Enhancements
New and Changed Information for Third-Party and SDK Applications
CSCso79248 Do Not Run installxml.vbs in CallManager Release 3.3 and Later
Adding Cisco CallManager Servers
Installing IPMA Assistant Console on Microsoft Windows XP
Locale Installer for Cisco CallManager
Line Group/Route Group Support for MLPP-Enabled Devices
Using the JTAPI Update Utility with CRS
Resolved Caveats for Cisco CallManager - Release 4.0(2)
Open Caveats for Cisco CallManager - Release 4.0(2)
Deleting a Music On Hold Server
Deleting a Media Termination Point
System Requirements for Barge and Privacy
Configuring Maximum Calls and Busy Trigger Settings for Shared Line Appearances
Cisco CallManager Service Activation/Deactivation
Route Pattern Configuration Fields
Cisco IP Phone Configuration Fields
Translation Pattern Configuration
Calling Search Space Configuration
Configuring Digits in Configuration Fields
Cisco Call Back Synchronous Request Timeout Configuration
Cisco CallManager Dialed Number Analyzer Private Phrase Requirement
Cisco CallManager Extension Mobility Logout
Using Attendant Console and Shared Lines
Date/Time Configuration Changes
Adding and Deleting Users by Using Cisco CallManager Administration
IPMA Clusterwide Parameters for Softkey Templates
Meet-Me Conference Limitations
Quality Report Tool Configuration Settings
SRST Fallback Algorithm Enhancements
Defining the Quality of Service (QoS) Values
User Settings in Cisco CallManager Administration
Updated BAT Field Descriptions
Using Annunciator with Conference Bridges
Q.SIG Support with JTAPI and TAPI
Cisco Unity Voice-Mail Port Changes
Obtaining Technical Assistance
Cisco Technical Support Website
Definitions of Service Request Severity
Obtaining Additional Publications and Information
Release Notes for Cisco CallManager Release 4.0(2)
Updated June 23, 2008
These release notes describe the new features and caveats for Cisco CallManager release 4.0(2).
Note
To view the release notes for Cisco CallManager release 4.0(1), which contains information about prior release changes, go to the following URL: http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/4_0/rel_note/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.0(2), see the "Resolved Caveats for Cisco CallManager - Release 4.0(2)" section and the "Open Caveats for Cisco CallManager - Release 4.0(2)" 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 Cisco CallManager 4.0 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
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.0 on a Cisco Media Convergence Server (MCS).
For information about installing Cisco CallManager release 4.0 on a Cisco Integrated Communications System (ICS) 7750, go to http://www.cisco.com/kobayashi/sw-center/telephony/ics-7750/ics-compatibility.shtml.
You may also install Cisco CallManager on a Cisco-approved HP server configuration or a Cisco-approved IBM server configuration.
Caution
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 4.0.
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:
•
•
•
Compatibility Matrix and Supported Upgrades
You can find which application versions are compatible with Cisco CallManager release 4.0(2) 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
Related Documentation
Refer to the Cisco CallManager Document Guide for a list of documents that are related to Cisco CallManager release 4.0 at
http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/4_0/doc_gd.
Along with the documents listed in the Cisco CallManager Document Guide, the following list specifies other related documents for Cisco CallManager release 4.0:
•
•
•
•
•
•
•
•
•
•
•
•
New and Changed Information
This following sections describe new features and changes that are pertinent to this release of Cisco CallManager. The sections include configuration tips for the administrator, information about users, and where to find more information.
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Upgrading to Cisco CallManager Release 4.0(2)
If your server runs Cisco CallManager release 4.0(1), you can upgrade your server to release 4.0(2) by using the web download file that is available at http://www.cisco.com/kobayashi/sw-center/sw-voice.shtml.
If your server runs Cisco CallManager release 3.2 or 3.3, you must use the CD-ROM disks from the Cisco CallManager release 4.0(2) software kit to upgrade the Cisco CallManager software to version 4.0(2); you cannot use the version that is posted on CCO. For detailed instructions, refer to Upgrading Cisco CallManager Release 4.0(2).
Cisco CallManager Extension Mobility Enhancements
Cisco CallManager release 4.0(2) enhances extension mobility functionality by throttling login requests. When extension mobility is used with a large number of users, this system activity controls the number of concurrent extension mobility service requests to ensure optimal system performance.
For more information, refer to http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed28469.
Where to Find More Information
•
•
•
System Enhancement for Route Group and Line Group Processing
Cisco CallManager release 4.0(2) provides enhancements to route group functionality by modifying the default distribution algorithm of a new route group from "top down" to "circular." Cisco CallManager 4.0(2) also enhances new line group creation by setting the default distribution algorithm to "longest idle time."
The system defines these system changes, which enable increased performance for call setup; the user cannot configure them.
Where to Find More Information
•
•
Voice Mail Configuration Enhancements
Cisco CallManager release 4.0(2) provides the following voice messaging system configuration enhancements.
Voice-Mail Pilot Configuration
Starting with Cisco CallManager 4.0(2), you do not need to reset devices when you update a voice-mail pilot.
•
•
Voice-Mail Profile Configuration
Starting with Cisco CallManager 4.0(2), you do not need to restart devices when you update a voice-mail profile.
•
•
Where to Find More Information
•
•
Cisco Unity Voice-Mail Port Adjustments
Migration from Cisco CallManager 3.3(3) to Cisco CallManager 4.0(2) requires adjustments to the voice-mail port settings.
Where to Find More Information
•
Route List Redundancy Configuration
With Cisco CallManager release 4.0(2), route list handling and redundancy change to improve performance. Pre-4.0(2) implementations included route lists on every server in a cluster. After upgrade to release 4.0(2), 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), and if two or more primary CallManager servers exist in the cluster, the system creates new CallManager Group(s) with a default name of "RLCMG_<primary Cisco CallManager name>." The system creates one CallManager Group for each primary server and the secondary server in the CallManager Group, which is the dedicated backup server. Depending on the number of servers in the cluster, the system creates one or multiple CallManager Groups.
One instance of the active route list configuration then attaches to the primary Cisco CallManager server in the first CallManager Group. New CallManager Groups get assigned to the existing route list configuration by using a round-robin algorithm to ensure redundancy.
To complete the upgrade, you must perform the following tasks:
1.
2.
3.
4.
Caution
For more information, refer to http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCee30571.
Where to Find More Information
•
•
SRST Algorithm Enhancements
Implementation of Survivable Remote Site Telephony (SRST) algorithm enhancements resolves Wide Area Network (WAN) link flapping issues between Cisco CallManager and SRST, which can lead to IP phone instability. The system provides enhancement through an enterprise parameter and a device pool configuration setting, Connection Monitor Duration.
Connection Monitor Duration
An IP phone that is connected to SRST over a WAN reconnects itself to Cisco CallManager as soon as it can establish a connection with Cisco CallManager over the WAN link. However, if the WAN link is unstable, the IP phone switches back and forth between SRST and Cisco CallManager, which can cause temporary loss of phone service (no dial tone). These reconnect attempts, known as WAN link flapping issues, continue until the IP phone successfully reconnects itself to Cisco CallManager.
WAN link disruptions comprise two types: infrequent random outages that occur on an otherwise stable WAN, and sporadic, frequent disruptions that last a few minutes.
To resolve the WAN link flapping issues between Cisco CallManager and SRST, Cisco CallManager provides an enterprise parameter and a setting in the Device Pool Configuration window called Connection Monitor Duration. (Depending upon system requirements, the administrator decides which parameter to use.) The XML configuration file delivers the value of the parameter to the IP phone.
•
•
Where to Find More Information
•
•
Operating System Installation Guidelines
Cisco recommends that you install Cisco IP Telephony operating system version 2000.2.6 with the latest service release 2000.2-6-sr1 (or later) before you upgrade to Cisco CallManager release 4.0(2).
Disabling Cisco RIS Data Collector Prior to Upgrading to Cisco CallManager Release 4.0(2)
Before upgrading to Cisco CallManager release 4.0(2), Cisco recommends that the administrator disable the Cisco RIS Data Collector to minimize system problems and prevent false alerts. The following procedure describes how to disable the Cisco RIS Data Collector.
This procedure applies for upgrades from Cisco CallManager 3.3 to 4.0(2) and upgrades from Cisco CallManager 4.0(1) to 4.0(2).
Procedure
Step 1
The Service Parameters Configuration window displays.
Step 2
Step 3
Step 4
Step 5
You can now perform the upgrade to Cisco CallManager 4.0 and later.
Note
New and Updated Support for Cisco IP Phones
The following information describes new and updated phone support for Cisco CallManager release 4.0(2):
•
•
For more information, refer to the following URL for the appropriate
Cisco IP Phone guide for your model IP phone:
http://www.cisco.com/univercd/cc/td/doc/product/voice/c_ipphon/index.htm.Where to Find More Information
•
•
•
•
•
Support for Cisco VT Advantage
Cisco CallManager release 4.0(1)sr2, 4.0(2), and later provide support for Cisco VT Advantage. Cisco VT Advantage brings video telephony functionality to Cisco IP Phones, which provides users with the ability to add video to their communications experience.
Where to Find More Information
•
•
•
Dialed Number Analyzer
The Dialed Number Analyzer (DNA) tool, an installable plug-in for Cisco CallManager, 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. DNA runs as a service on the server.
Note
Where to Find More Information
•
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 the dial plans that specific countries use.
Cisco CallManager currently supports international dial plans for Australia, Japan, Netherlands, New Zealand, Portugal, Russia and Singapore.
Where to Find More Information
•
Changes to Type Specific Information in the Gateway Configuration Settings
After you install Cisco CallManager 4.0(2), the following check boxes in the Cisco CallManager Administration Gateway Configuration window are unchecked by default for some gateways:
•
•
•
The gateways that are affected include the following:
•
•
•
•
•
If you upgrade your server to Cisco CallManager 4.0(2) and you did not uncheck the check boxes before the upgrade, the check boxes remain checked after the upgrade. If you add an affected gateway after the upgrade, the check box is unchecked.
To determine when you should check the check box(es), refer to the guidelines specified in the Cisco CallManager Administration Guide.
Where to Find More Information
•
Calling Search Space Enhancements
Cisco CallManager provides database enhancements for Calling Search Spaces (CSS) that allow you to make updates to calling search spaces during normal 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.
Tip
Where to Find More Information
•
Conference Enhancements
Cisco CallManager release 4.0 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.
Note
Tip
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.Where to Find More Information
•
•
•
•
Attendant Console Enhancements
Cisco CallManager Attendant Console includes the following enhancements:
•
While the call is in the queue, the system places the call on hold, and music on hold plays to the caller. Cisco CallManager redirects the call to the next available hunt group member. When the call is in the queue for longer than the configured HoldTime, the call gets redirected to the "AlwaysRoute" member. If the "AlwaysRoute" member is not configured, no action gets taken. Attendants cannot see calls in the queue.
•
While the call is in the queue, the system places the call on hold, and music on hold plays to the caller. Cisco CallManager redirects the call to the attendant who answers the call.
•
•
•
•
Configuration Tips
•
•
•
How this Feature Affects the User
From the Broadcast Calls window in the Attendant Console application, users can view and answer calls.
Where to Find More Information
•
•
•
NM-HDV2 and NM-HD Support for Cisco CallManager
In Cisco CallManager release 4.0(2), 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:
Note
In addition to the preceding gateways, NM-HD supports the Cisco 3660.Per NM-HDV2:
•
•
•
•
Tip
•
•
Per NM-HD:
•
•
•
•
Tip
•
•
Note
Tip
Where to Find More Information
•
•
•
•
•
•
Security Enhancements
Cisco CallManager provides the following additional security implementation capabilities.
•
•
Configuration Tips
•
Tip
•
•
If CAPF requests certificates from Microsoft Certificate Services, you must enter the necessary configuration information, for example, the IP address or hostname, for this certificate authority in the applicable CAPF service parameter. In addition, you must install the SCEP addon on the server where you install Microsoft Certificate Services. To obtain the SCEP addon, contact the certificate authority vendor directly.
•
Where to Find More Information
•
•
•
Static Digit Analysis
Prior to Cisco CallManager release 4.0, unregistered devices without configured forwarding were removed from the digit analysis (DA) table and required dynamic digit analysis. Prior to release 4.0, when a phone unregistered, call processing allowed a call to pass to the next closest match in the CSS list. With the introduction of static DA in release 4.0, whether a phone is registered or not, the device remains in the DA table, and the directory number intercepts the call.
Configuration Tip
Administrators should note that the IPMA and PA applications can no longer use translation patterns for failover. Instead, administrators must set up Call Forward No Answer (CFNA) with the data that was in the translation pattern for all IPMA and PA failed route points, and these route points must be removed.
Where to Find More Information
Using Query to Delete Phones
You can delete phones by creating a query to locate the phone records by using the following procedure.
Procedure
Step 1
The Delete Phones window displays.
Caution
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Note
Step 8
Note
If you need to make a correction, click the Clear Query button to remove the query; then, return to Step 2 and restart.
Caution
Step 9
Note
Step 10
Step 11
The log file displays the number of phones that were deleted and the number of records that failed, including an error code.
Where to Find More Information
•
Using Immediate Divert with Hunt Lists
When you use a phone that is part of a line group in a hunt list and it has the iDivert softkey assigned to it, the iDivert softkey does not display when the phone receives a call from within the hunt list.
When the phone receives a call that is not associated with a hunt list, however, the iDivert softkey displays on the phone.
For more information, refer to http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCee84214 and http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCef15654.
Where to Find More Information
•
New and Changed Information for Cisco CallManager Serviceability
This section describes the following new serviceability features and changes that are pertinent to this release of Cisco CallManager:
•
•
•
•
•
•
•
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. Therefore, 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.
TroubleShooting Trace Setting
The TroubleShooting Trace Setting tool allows users to set/reset the troubleshooting traces for chosen services in the Cisco CallManager cluster from a single window, as well as set adequate trace (SDI and SDL) settings to troubleshoot Cisco CallManager services. Using this tool, users can choose the required services on different Cisco CallManager nodes in the cluster, so the trace settings of the chosen services get changed to reflect the predetermined trace settings.
Troubleshooting trace settings differ from the default trace settings. The development team for troubleshooting predetermines the troubleshooting trace settings for each Cisco CallManager service. While troubleshooting trace is set, most trace configuration parameters remain disabled in the trace configuration windows.
You can find the TroubleShooting Trace Setting tool in the Trace menu in Cisco CallManager Serviceability.
Cisco CallManager Trace Collection Tool
Release 4.0 removes trace collection for Cisco CallManager from the Trace menu of Cisco CallManager Serviceability Administration and installs as a Cisco CallManager client plugin tool that users can download from the Plug-ins page and install on a client machine. This tool collects traces for a Cisco CallManager cluster into a single zip file. The collection includes all traces for Cisco CallManager and logs, such as Event Viewer (Application, System, Security), Dr. Watson log, Cisco Update, Prog logs, RIS DC logs, SQL, and IIS logs.
The Trace Collection Tool collects traces from a remote machine for the following components on chosen servers in the Cisco CallManager cluster:
•
•
•
The Trace Collection Tool collects the traces and saves them in the form of a zip file (as a single file or split into multiple files) by using a different compression factor. You can collect traces for a chosen period or for all available traces.
You can install the Trace Collection Tool on Windows 2000, 98, or XP client.
Real-Time Monitoring Tool as Standalone Plug-in
Real-Time Monitoring Tool (RTMT) enhancements provide client-side functionality that did not exist in previous versions of Cisco CallManager. With the 4.0 version, RTMT monitors and reports on typical precanned (preconfigured) alerts. This type of monitoring allows the system administrator to have a comprehensive view of the entire Cisco CallManager cluster with little RTMT configuration. The precanned alerts allow the administrator to be alerted, via e-mail or e-mail pager, about typical Cisco CallManager server or service problems.The precanned reporting allows some minor trending as well as troubleshooting problems after they occur.
The new client-side RTMT plug-in continuously monitors real-time behavior of the components in a Cisco CallManager cluster. It uses HTTP and TCP to monitor system performance, critical services, call activity, device status, and CTI applications.
In addition to service parameter enhancements, the following list comprises the RTMT enhancements for Cisco CallManager release 4.0:
•
•
•
•
•
–
–
–
–
–
–
–
–
–
–
•
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
•
–
–
–
–
•
Note
Serviceability Reports Archive
The Cisco CallManager Serviceability Reports Archive allows users to view reports that the NT service Cisco CallManager Serviceability Reporter generates. Reporter generates five daily reports in Cisco CallManager Serviceability Administration: Device Statistics, Server Statistics, Service Statistics, Call Activities, and Alert. Each report provides a summary that comprises different charts that display the statistics for that particular report.
Users can view the reports by accessing Cisco CallManager Serviceability > Tools > Serviceability Reports Archive.
SNMP and Performance Counter Enhancements
Cisco CallManager SNMP for release 4.0 provides the following changes and enhancements:
•
–
–
•
•
•
•
The following SNMP traps, with associated trap objects, that were added alert the system administrator of a malicious call or quality report: ccmMaliciousCall and ccmQualityReport.
•
•
•
•
•
Release 4.0 adds several new performance objects and counters to support new Cisco CallManager features. Release 4.0 adds performance counters for the application-controlled bridge device, annunciator, security, video, hunt lists, SIP, transcoders, MTP, software conference bridge, and hardware conference bridge. The release also renamed and/or deleted some system performance counters.
Where to Find More Information
•
•
CDR Analysis and Reporting (CAR) Enhancements
In Cisco CallManager Release 4.0, the CDR Analysis and Reporting Tool (CAR) supports new hunting features, MLPP, Malicious Call ID, and new conference reports. This release enhances CDR management to export CDR records for date range and allows date-specific purging.
The following list describes the CAR enhancements for release 4.0:
•
–
–
–
•
–
–
•
–
–
•
–
–
–
•
–
–
–
Configuration Tip
The menu on the left side of the pane lists only the top 50 route patterns.
Where to Find More Information
•
•
New and Changed Information for Third-Party and SDK Applications
There are no new features and changes that are pertinent to this release of Cisco CallManager and third-party and SDK applications.
For information about third-party and SDK applications, refer to the Cisco CallManager 4.0 Developer Documents at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/voice/vpdd/cdd/4_0/
Important Notes
The following section contains important information that may have been unavailable upon the initial release of documentation for Cisco CallManager release 4.0(2).
•
•
•
•
•
•
CSCso79248 Do Not Run installxml.vbs in CallManager 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
Adding Cisco CallManager Servers
In Cisco CallManager Administration, make sure that you only add each server once on the Server Configuration window (System > Server). If you add a server using the host name and add the same server 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.
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 plug-in for Internet Explorer from http://java.sun.com/getjava/download.html.
After installing the Sun JVM plug-in, continue the IPMA assistant console installation from http://<server>/ma/Install/IPMAConsoleInstallJar.jspl where <server> represents the IP address of the Cisco CallManager server.
Locale Installer for Cisco CallManager
You can obtain locale specific versions of the Cisco IP Telephony Network Locale installer for Cisco CallManager 4.0 at the following URL:
http://www.cisco.com/kobayashi/sw-center/telephony/callmgr/locale-installer.shtml
Refer to the readme file that is posted next to the Cisco IP Telephony Locale Installer software for the complete list of supported languages and localized features.
Line Group/Route Group Support for MLPP-Enabled Devices
MLPP-enabled devices are not supported in line groups. As such, Cisco recommends the following guidelines:
•
•
Guest
