 Feedback
|
Table Of Contents
Release Notes for Cisco CallManager Release 4.2(1)
Determining the Software Version
Compatibility Matrix and Supported Upgrades
Cisco CallManager 4.2(1) Installation and Upgrade Guidelines
Operating System Installation Guidelines
Upgrading to Cisco CallManager Release 4.2(1)
New and Changed Information for Cisco CallManager Features
Multilevel Precedence and Preemption Enhancements
Cisco CallManager Attendant Console and Call Pickup Limitation
Cisco Messaging Interface Enhancements
Voice-Mail-Related Changes to Hunt List and Hunt Pilot
New MLPP Service Lockout Enterprise Parameter
Call Diagnostics and Voice Quality Metrics
Overlap Sending and Receiving for H.323 Gateways
Cisco CallManager T1 CAS Hookflash Transfer Support
New and Changed Information for Cisco IP Phones
New and Changed Information for Cisco Emergency Responder 1.3(1)
New and Changed Information for Bulk Administration Tool
New and Changed Information for Cisco CallManager Dialed Number Analyzer
New and Changed Information for Cisco Personal Assistant 1.4(5)
New and Changed Information for Third-Party and SDK Applications
Show Line Group Member DN in finalCalledPartyNumber CDR Field Service Parameter
Cisco CallManager 4.2(1) AXL Programming
Cisco CallManager 4.2(1) Call Detail Record Definition
CSCso79248 Do Not Run installxml.vbs in Unified CM Release 3.3 and Later
Configuring Regions (Region Relationship) For SIP Devices with the MTP Required Option Enabled
Resolved Caveats for Cisco CallManager - Release 4.2(1)
Open Caveats for Cisco CallManager - Release 4.2(1)
Bulk Administration Tool User Guide Title Error
Device Mobility Info Configuration Window
Device Pool Configuration Window
Malicious Call Identification Restrictions
TAPS Installation Procedure for CCM4.1(3)SR2 and Subsequent Releases
Cisco Product Security Overview
Reporting Security Problems in Cisco Products
Obtaining Technical Assistance
Cisco Technical Support & Documentation Website
Definitions of Service Request Severity
Obtaining Additional Publications and Information
Release Notes for Cisco CallManager Release 4.2(1)
Updated June 23, 2008
Table 1 Modification History
June 23, 2008
Under Important Notes, added "CSCso79248 Do Not Run installxml.vbs in Unified CM Release 3.3 and Later" section
November 16, 2007
Corrected "Upgraded Memory Requirement" section
These release notes describe the new features and caveats for Cisco CallManager release 4.2(1).
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/4_2/rel_note/index.htm
Before you install Cisco CallManager, Cisco recommends that you review the "Caveats" section for information about issues that may affect your system.
For a list of the open and resolved caveats for Cisco CallManager release 4.2(1), see the "Resolved Caveats for Cisco CallManager - Release 4.2(1)" section and the "Open Caveats for Cisco CallManager - Release 4.2(1)" 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
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.2(1) 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
Caution
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.2(1).
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.2(1) and which previous releases of Cisco CallManager have 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.2 at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/4_2/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.2:
•
•
•
•
•
•
•
•
•
•
•
•
•
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 4.2(1) Installation and Upgrade Guidelines
This section includes information about the guidelines that apply to Cisco CallManager 4.2(1) installation and upgrade procedures:
Installation and Upgrade
Cisco CallManager 4.2(1) implements the following installation and upgrade guidelines:
•
•
This section includes the following topics:
•
Upgraded Memory Requirement
The Cisco CallManager installation requires a minimum of 2 GB of memory on the Cisco CallManager publisher server. If the installation process detects less than 2 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
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) modified the installation process to abort the installation and display 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
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
Note
Follow this procedure to disable the Cisco-installed NTP software on a server:
Procedure
Step 1
Step 2
Step 3
Step 4
Step 5
Caution
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.2(1) replaces previous versions.
This release of Cisco CallManager Upgrade Assistant Utility supports multiple version upgrades; that is, you can use Cisco CallManager Upgrade Assistant Utility version 4.2(1) or later to detect the health of your servers before you upgrade to Cisco CallManager release 3.3(5), 4.0(2a), 4.1(3), or 4.2(1)
For additional information, refer to Using Cisco CallManager Upgrade Assistant Utility 4.2(1) at the following URL: http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/4_2/install/upgrade/index.htm
Backup and Restore
The following guidelines apply to Cisco CallManager backup and restore procedures:
•
•
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
Where to Find More Information
•
•
Operating System Installation Guidelines
Before you upgrade to Cisco CallManager release 4.2(1), you must install the Cisco IP Telephony operating system version 2000.4.2 with the latest service release 2000.4-2-sr(x). While the upgrade process may not check for the installation of the latest service release, Cisco recommends that you install it to avoid Windows security issues.
Tip
Note
Where to Find More Information
•
Upgrading to Cisco CallManager Release 4.2(1)
For detailed information about upgrading to Cisco CallManager 4.2(1), refer to Upgrading Cisco CallManager Release 4.2(1). For additional guidelines about Cisco CallManager installation and upgrades, see the "Cisco CallManager 4.2(1) Installation and Upgrade Guidelines" section.
Tip
The following guidelines apply to upgrading to Cisco CallManager 4.2(1):
Note
•
•
•
Note
•
Tip
New and Changed Information for Cisco CallManager Features
The following sections describe new and changed information related to Cisco CallManager features:
•
•
•
•
•
•
•
•
Multilevel Precedence and Preemption Enhancements
MLPP includes the following additional features for the Defense Red Switched Network (DRSN):
•
•
•
Cisco CallManager 4.2(1) includes the following configuration enhancements to support these features:
•
–
–
•
–
–
–
–
–
Tunneling of MLPP precedence level information can be carried in a PRI UUIE across an H.323 inter-cluster trunk via non-standard control data within a H.225 UUIE.
DSCP marking creates multiple expedited forwarding classification levels that correspond to MLPP precedence levels.
Where to Find More Information
•
•
Device Mobility
Cisco CallManager uses IP subnets and device pools that contain location information to determine a device home location. By linking IP subnets to locations, the system can determine whether a device is at its home location or a remote location and register the device accordingly.
To support device mobility, modifications to the device pool structure separate the user information from the location and mobility information. Beginning with Cisco CallManager release 4.2(1), the device pool now contains the information that pertains to the device itself and to device mobility. An added common profile allows you to configure all the user-related information. You must associate each device with the common profile for user based information.
Note
In addition to the device pool and common profile, device mobility uses device mobility groups, physical locations, and device mobility information to determine device identity and roaming properties and configuration. The following sections provide additional details:
•
Device Pool and Common Profile
Parameters that previously were included in the device pool include parameters that pertain to the device itself and device mobility and the set that pertain to the user.
The Device Pool window contains these parameters:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
The Common Profile window now includes these parameters that were formerly included in the device pool:
•
–
–
–
–
–
•
–
–
–
Device Mobility Design
To design an efficient device mobility structure, you must first determine how to divide the network into hierarchical groupings with distinct device mobility properties and make the proper associations among the groupings. This is done using device mobility groups, physical locations, device pools, and subnet-based device mobility information.
Device Mobility Groups
Device mobility groups represent the highest level geographic entities in your network. Depending upon the network size and scope, your device mobility groups could represent countries, regions, states or provinces, cities, or other entities. For example, an enterprise with a worldwide network might choose device mobility groups that represent individual countries, whereas an enterprise with a national or regional network might define device mobility groups that represent states, provinces, or cities.
Movement of a device from one device mobility group to another represents the highest level movement that Cisco CallManager recognizes.
Physical Location
Physical location represents the next division below that of device mobility group. Physical locations provide a means of distinguishing the parameters that relate to a specific geographical location from other parameters. For example, a Music on Hold (MOH) server may serve a specific office or campus within the enterprise. When a device roams to another office or campus and reregisters with Cisco CallManager, having the device served by the MOH server at the roaming location represents best practice. By defining the physical location according to availability of services such as MOH, you can assure efficient and cost-effective reassignment of services as devices move from one physical location to another. Depending upon the network structure and allocation of services, you can define physical locations based upon city, enterprise campus, or building.
Device Pools
After the device mobility groups and physical locations are identified, you can associate them with device pools. Each device pool contains the set of parameters that apply to devices, and adding the device mobility group and physical location ties the device pool to those entities.
Device Mobility Information
In the final step in designing a device mobility structure, you associate subnets with the device pools that contain the device mobility group and physical location information. When a phone registers and obtains an IP address, the system compares the address to device mobility subnets that are associated with one or more device pools. The matching subnet becomes the device home subnet for the purpose of device mobility.
Phone Configuration
After the device mobility structure is in place, you can turn device mobility on for IP phones that are provisioned to be mobile.
Where to Find More Information
•
•
•
Cisco CallManager Attendant Console and Call Pickup Limitation
Cisco CallManager Attendant console does not work with call pickup. The attendant console user interface cannot appropriately handle calls coming from or made to phones that belong to a call pickup group due to Cisco Java Telephony Applications Programming Interface (JTAPI) and computer telephony integration (CTI) limitations.
Where to Find More Information
Call Pickup, Cisco CallManager System Guide
Call Pickup Notification
This new feature allows users to receive an audio and/or visual alert when a call rings on a phone in pickup groups in which they are a member. For multiple line phones, the alert is available for pickup groups associated with the primary line only.
You can configure the following notification parameters in the Call Pickup Group Configuration window:
•
•
•
You can configure the type of audio notification that is provided when a phone is idle or in use in the Directory Number Configuration window.
Supported Cisco IP Phones
•
•
•
•
•
•
Where to Find More Information
•
•
•
Directed Call Park
Directed Call Park allows a user to transfer a parked call to an available user-selected directed call park number. Configure directed call park numbers in the new Cisco CallManager Directed Call Park Configuration window. Configured directed call park numbers exist cluster wide. You can configure phones that support the directed call park Busy Lamp Field (BLF) button to monitor the busy/idle status of specific directed call park numbers. Users can also use the BLF button to speed dial a directed call park number.
A user can retrieve a parked call by dialing a configured retrieval prefix followed by the directed call park number where the call is parked.
Note
Supported Cisco IP Phones
•
•
•
•
•
With the directed call park Busy Lamp Field (BLF) button, users can determine when a directed call park number is available or occupied as follows:
•
or Occupied Park Number
.
•
or occupied
.
Where to Find More Information
•
•
IPMA Enhancements
The following enhancements have been added for Cisco IP Manager Assistant (IPMA):
•
•
In addition, Cisco IP Manager Assistant for Cisco CallManager 4.2 includes enhancements for using Cisco IPMA on the assistant phone. With this release, the assistant can use the physical phone buttons and softkeys to perform most of the call-handling tasks that the assistant can perform using the IPMA Assistant Console application.
Cisco recommends that an assistant use the Cisco IPMA-on-phone features only if that assistant supports no more than five people.
Supported Cisco IP Phones
The following Cisco IP Phone models support the Cisco IPMA on-phone features:
•
•
•
•
•
•
Where to Find More Information
•
•
Cisco Messaging Interface Enhancements
The Cisco Messaging Interface (CMI) allows you to connect a simplified message desk interface (SMDI)-compliant external voice-messaging system with the Cisco CallManager. The CMI service provides the communication between a voice-messaging system and Cisco CallManager. The SMDI defines a way for a phone system to provide a voice-messaging system with the information that is needed to intelligently process incoming calls.
With this release, you can now configure the CMI service parameters to define an alternate directory number and partition to be used when a non voice mail pilot number is dialed.
Note
Where to Find More Information
•
Call Forwarding Enhancements
Cisco CallManager 4.2(1) provides the following enhancements to the forwarding and Automated Alternate Routing (AAR) logic to redirect calls that cannot be connected due to no bandwidth or an unregistered directory number:
•
This enhancement applies AAR treatment to calls that are blocked due to insufficient bandwidth using the new AAR Settings fields (AAR Destination Mask, AAR Voicemail Enabled).•
This enhancement forwards calls that are routed to a directory number with no registered devices.See the "Cisco TSP Enhancements" section for full descriptions of these Call Forwarding enhancements.
Where to Find More Information
•
Password Management Features
The following enterprise directories can provide password management features after they are integrated with the Cisco CallManager:
•
•
•
Note
You can configure password management features for Cisco CallManager (LDAP) users, and, if MLA is enabled, for administrative users. You can configure the following password management features:
•
•
•
Refer to your enterprise directory documentation for password management configuration procedures.
Note
Caution
User Cache Flush Timeout (Minutes) Enterprise Parameter
The new User Cache Flush Timeout enterprise parameter designates the interval (in minutes) between flushes of the MLA cache that contains user credentials, and is therefore a factor in periodic password expiration. Every time that MLA flushes the cache, it synchronizes itself with the latest user credentials information from the integrated enterprise directory server.
The lower the value of this parameter, the higher the potential for performance degradation in outside polling applications such as the Real Time Monitoring Tool (RTMT). The higher the value of this parameter, the higher the risk that a user is inappropriately authenticated based on cached credentials that are no longer valid.
You can set this enterprise parameter to any of the following values: No Caching, 5, 10, 20, 30, 45, or 60. The User Cache Flush Timeout enterprise parameter specifies the default value of 5 minutes.
Supported Cisco IP Phones
•
•
•
•
•
•
Where to Find More Information
•
•
•
•
Log Out of Hunt Groups
The Log Out of Hunt Groups feature allows phone users to log their phones out from receiving calls that get routed to directory numbers that belong to line groups to which the phone lines are associated. Regardless of the phone status, the phone rings normally for incoming calls that are not calls to the line group(s) that are associated with the phone. The phone provides a visual status of the login state, so the user can determine by looking at the phone whether they are logged in to their line group(s).
The Log Out of Hunt Groups feature also comprises the following components:
•
•
The Log Out of Hunt Groups feature, which is device-based, operates differently for non-shared lines and for shared lines.
Supported Cisco IP Phones
•
•
•
•
•
•
Where to Find More Information
•
•
•
Voice-Mail-Related Changes to Hunt List and Hunt Pilot
Several modifications to Cisco CallManager Administration address the problem of voice-mail calls that get rejected when hunt list use reaches a maximum because all voice-mail ports are in use.
If you intend to use a hunt list for voice messaging, check the new For Voice Mail Usage check box in the Hunt List Configuration window. Also, if you intend to use a hunt list for voice messaging, all members of the line group(s) that you assign (add) to the hunt list must be voice-mail ports.
For details of the changes to hunt list configuration, refer to the "Adding a Hunt List" and "Adding Line Groups to a Hunt List" sections of the "Hunt List Configuration" chapter in the Cisco CallManager Administration Guide.
The description of the Hunt List field in the Hunt Pilot Configuration Settings table reminds you to check whether the hunt list that you choose for the voice-mail hunt pilot specifies a hunt list that has the For Voice Mail Usage check box checked.
For details of the changes to hunt pilot configuration, refer to the "Hunt Pilot Configuration Settings" section of the "Hunt Pilot Configuration" chapter in the Cisco CallManager Administration Guide.
Where to Find More Information
•
•
New MLPP Service Lockout Enterprise Parameter
Release 4.2(1) adds a new enterprise parameter that affects Multilevel Precedence and Preemption (MLPP) configuration. The new enterprise parameter, MLPP Service Lockout, determines whether to override the max calls setting for a line to prevent supplementary services from conflicting with MLPP.
Where to Find More Information
•
Phone Button Template
You can create the Cisco IP Phone Expansion Module 7914 phone button template by renaming the phone button template used for the Cisco IP Phone 7960.
Where to Find More Information
•
Call Diagnostics and Voice Quality Metrics
You can configure Cisco IP Phones to collect call diagnostics and voice quality metrics by setting the Call Diagnostics Enabled service parameter to True in Cisco CallManager Administration. You can access the metrics to monitor voice quality and troubleshoot network problems. The Call Statistics screen on the phone displays counters, statistics, and voice quality metrics in the following ways:
•
•
Note
To measure the voice quality of calls that are sent and received within the network, Cisco IP Phones use statistical metrics that are based on concealment events.
To use the metrics for monitoring voice quality, record the typical scores under normal conditions of zero packet loss, and use the metrics as a baseline for comparison.
Supported Cisco IP Phones
•
•
•
•
•
Where to Find More Information
•
•
Overlap Sending and Receiving for H.323 Gateways
Support is provided for overlap sending and receiving for H.323 gateways. It is not necessary for H.323 module users to dial all the digits for the setup message to be sent to an H.323 device. You can enable the overlap sending feature for the individual route pattern by using the Allow Overlap Sending checkbox on the Route Plan Configuration window. To enable the overlap receiving feature, you must set the CallManager Overlap Receiving Flag for H.323 service parameter.
Where to Find More Information
•
SDL Traces
You can use the Asynchronous SDL Logging Enabled parameter to determine whether Cisco CallManager logs SDL traces in asynchronous mode. Asynchronous mode allows Cisco CallManager to manage SDL trace data independently from other call processing activities, which can improve Cisco CallManager performance. SDL trace output is not affected by this parameter setting; only the internal method data gathering is affected. In the event of a Cisco CallManager exe crash, it is possible that the SDL trace may not get fully logged. If asynchronous logging is enabled, an exception handler is called to ensure that all the SDL trace data collected up until the time of crash are fully logged.
Where to Find More Information
•
Cisco CallManager T1 CAS Hookflash Transfer Support
Hookflash transfer defines a signaling procedure that allows a device, such as a voice-messaging system, to transfer a call to another destination. While the device is connected to Cisco CallManager through a T1 CAS gateway, the device performs a hookflash procedure to perform the call transfer. Cisco CallManager responds to the hookflash procedure by using a blind transfer to move the call. When the call transfer completes, the voice channel that connected the original call to the device gets released.
Cisco CallManager supports hookflash transfer on the T1 CAS ports of all Media Gateway Control Protocol (MGCP) gateways (both IOS and non-IOS gateways).
Where to Find More Information
•
New and Changed Information for Cisco IP Phones
Table 1 lists Cisco IP Phones that support new Cisco CallManager 4.2 features.
Note
Table 2 Cisco IP Phone Support for Cisco CallManager 4.2 Features
Call Pickup Notification
Cisco IP Phone 7970G/7971G
Cisco IP Phone 7961GE/7941GE
Cisco IP Phone 7961G/7941G
Cisco IP Phone 7960G/7940G
Cisco IP Phone 7911G
Cisco IP Phone 7905G/7912GSee the "Call Pickup Notification" section.
Directed Call Park
Cisco IP Phone 7970G/7971G
Cisco IP Phone 7961GE/7941GE
Cisco IP Phone 7961G/7941G
Cisco IP Phone 7960G/7940G
Cisco IP Phone Expansion Module 7914See the "Directed Call Park" section.
Logging out of Hunt Groups
Cisco IP Phone 7970G/7971G
Cisco IP Phone 7961GE/7941GE
Cisco IP Phone 7961G/7941G
Cisco IP Phone 7960G/7940G
Cisco IP Phone 7905G/7912G
Cisco IP Phone 7911GSee the "Log Out of Hunt Groups" section.
Password Management
Cisco IP Phone 7970G/7971G
Cisco IP Phone 7961GE/7941GE
Cisco IP Phone 7961G/7941G
Cisco IP Phone 7960G/7940G
Cisco IP Phone 7905G/7912G
Cisco IP Phone 7911GVoice Quality Metrics
Cisco IP Phone 7970G/7971G
Cisco IP Phone 7961GE/7941GE
Cisco IP Phone 7961G/7941G
Cisco IP Phone 7960G/7940G
Cisco IP Phone 7911GSee the "Call Diagnostics and Voice Quality Metrics" section.
New and Changed Information for Cisco Emergency Responder 1.3(1)
Cisco Emergency Responder (Cisco ER) 1.3(1) supports Cisco CallManager 4.2(1) in addition to Cisco CallManager 3.3, 4.0, and 4.1.
•
•
Where to Find More Information
•
New and Changed Information for Bulk Administration Tool
Bulk Administration Tool (BAT), a web-based application, performs bulk transactions to the Cisco CallManager database. This section introduces the changes to BAT for Cisco CallManager 4.2:
•
•
•
–
–
–
–
•
–
–
•
–
–
–
–
•
–
–
–
•
–
–
•
–
–
–
•
–
–
–
Where to Find More Information
•
•
•
New and Changed Information for Cisco CallManager Dialed Number Analyzer
Cisco CallManager Dialed Number Analyzer 4.2(1) is a feature service that installs along with Cisco CallManager. The tool allows you to test a Cisco CallManager dial plan configuration prior to and after deploying the dial plan. You can use Dialed Number Analyzer (DNA) to test a dial plan by providing dialed digits as input. The tool analyzes the dialed digits and shows details of the calls. You can use these results to diagnose the dial plan, identify problems if any, and tune the dial plan before it is deployed.
The following changes in DNA apply to Cisco CallManager 4.2(1):
•
–
–
–
–
•
•
–
–
–
–
•
Where to Find More Information
•
•
•
New and Changed Information for Cisco Personal Assistant 1.4(5)
Cisco Personal Assistant 1.4(5) has been qualified for use with Cisco CallManager 4.2. For Personal Assistant 1.4(5) to work with the Cisco CallManager 4.2 release, you must update the JTAPI files on each Personal Assistant server.
Note
Perform the following procedure to update the JTAPI files:
Step 1
•
•
•
•
•
•
Step 2
Step 3
Step 4
Step 5
Where to Find More Information
For more information about Cisco Personal Assistant, refer to the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/voice/assist/index.htm
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
The following list describes the changes to Cisco JTAPI for Cisco CallManager 4.2(1):
•
If you downgrade Cisco CallManager 4.2 to version 4.1, you must also downgrade Cisco JTAPI from version 2.2 to version 2.1(x).
•
–
–
•
When a call is transferred to a directed call park DN (dparked), the application sees a connection created for directed call park DN and the call control connection state is CallControlConnection.QUEUED. CiscoTransferstart and end events are delivered. An application can use the new interface on CiscoConnection to get the prefix code needed to unpark the call.
•
•
Where to Find More Information
For information about third-party and SDK applications, refer to the Cisco JTAPI Developer Guide for Cisco CallManager 4.2(1) at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/voice/vpdd/cdd/4_2/
Cisco TSP Enhancements
This section describes the Cisco TSP enhancements for Cisco CallManager 4.2(1) in the following sections:
•
Cisco CallManager Version Compatibility
It is not necessary to upgrade Cisco TSP when upgrading to Cisco CallManager 4.2(1), unless you want to use features that are new for the 4.2(1) release. Previously, it was required to upgrade Cisco TSP when upgrading Cisco CallManager.
Windows 2003 Support
Cisco TSP is now supported on Windows 2003.
Call Forwarding
Cisco CallManager 4.2(1) provides enhancements to the forwarding and Automated Alternate Routing (AAR) logic to redirect calls that cannot be connected due to no bandwidth or an unregistered directory number.
No Bandwidth
In this scenario a call comes in from a gateway at the central site (Centralized Call Manager Configuration) for a phone at a remote site. Previously, if AAR was enabled, and there was insufficient bandwidth to deliver the call to the remote site, Cisco CallManager rerouted the call through PSTN or other network by using an alternate number. The alternate number is derived from the external phone number mask. The AAR cannot redirect the call to an alternate destination (for example, a cell phone or voice mail).
Now you can configure an alternate call destination or direct the call to voicemail. No bandwidth calls are handled by AAR and are rerouted to the AAR Destination Mask or to voice mail.
TAPI applications receive the LINECALLREASON_FWDBUSY call reason in this scenario.
Unregistered Phone
In this scenario, a call is placed to a DN that is unregistered. Previously, that call was handled by the CFNA (Call Forward No Answer) forwarding logic.
Now Cisco CallManager can determine if the call is not answered or if the target DN is unregistered. This feature adds a new call forwarding type CFUR (Call Forward Unregistered) to handle the calls which are targeted to an unregistered DN.
TAPI applications receive the LINECALLREASON_FWDNOANSWER call reason in this scenario.
Privacy on Hold
A shared line cannot retrieve a held call on which privacy is enabled. However, a shared line can retrieve the call if its privacy mode is disabled.
When a privacy enabled call is put on hold, Cisco TSP reports the call state as CONNECTED INACTIVE for calls on shared lines.
Directed Call Park
This feature allows you to select a park code at which to park a call. Previously you could not select the park code; it was assigned automatically.
Cisco TSP sends the prefix code to the application as part of dwConnectedIDName in the format "Park Number:<PrefixCode><DParkDN>". Applications can use <PrefixCode> and <DParkDN> to unpark a parked call.
When the call is parked, unparked or reverted for the directed call park, the call reasons reported by Cisco TSP are the same as for the normal park cases:
•
•
Where to Find More Information
For information about third-party and SDK applications, refer to the Cisco TAPI Developer Guide for Cisco CallManager 4.2(1) at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/voice/vpdd/cdd/4_2/
Show Line Group Member DN in finalCalledPartyNumber CDR Field Service Parameter
This service parameter for the Cisco CallManager service allows you to specify either the line group directory number (DN) that picks up a call to a hunt pilot number or the hunt pilot number as the final called party number in the Call Detail Record (CDR).
Where to Find More Information
•
Cisco CallManager 4.2(1) AXL Programming
The AXL SOAP API is updated with new APIs and changes to existing APIs. Refer to the Cisco CallManager 4.2(1) AXL Programming Guide for more information.
Where to Find More Information
For information about third-party and SDK applications, refer to the Cisco CallManager 4.2(1) AXL Programming Guide at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/voice/vpdd/cdd/4_2/
Cisco CallManager 4.2(1) Call Detail Record Definition
You can configure Cisco CallManager to report the directory number (DN) of the hunt group member who answered a direct call to the hunt pilot number in the final called party number field in the CDR. Previously, Cisco CallManager reported the hunt pilot DN in the final called party number field in the CDR.
Where to Find More Information
For information about third-party and SDK applications, refer to Cisco CallManager 4.2(1) Call Detail Record Definition at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/voice/vpdd/cdd/4_2/
Installation Notes
For complete installation information, refer to the following document:
•
For installation information specific to Cisco CallManager release 4.2(1), see the following sections:
•
•
•
Limitations and Restrictions
You can find which application versions are compatible with Cisco CallManager release 4.2(1) 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
Important Notes
The following section contains important information that may have been unavailable upon the initial release of documentation for Cisco CallManager release 4.2(1).
•
•
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
Configuring Regions (Region Relationship) For SIP Devices with the MTP Required Option Enabled
When you configure a region relationship, you must ensure that you choose an audio codec that has sufficient bandwidth for all the devices that will be used in a call. This includes configuring the codec for devices that will be in the same region as well as devices that are in different regions. When you configure a trunk or third-party phone to use the SIP protocol and Media Termination Point Required is enabled, Cisco CallManager Administration only allows you to choose a G.711 codec in the MTP Preferred Originating Codec field. When you assign the SIP trunk or third-party SIP phone with the MTP Required option enabled to the device pool for that region, you must verify that the region relationship between the SIP device and the MTP device is configured to use a codec with equal or greater bandwidth (G.711 or Wideband codec).
Caveats
This section contains information about resolved and open caveats for Cisco CallManager, Release 4.2(1), and instructions for using the online tools that will help you monitor the current status of caveats in the following sections:
•
•
Resolved Caveats for Cisco CallManager - Release 4.2(1)
You can find the latest resolved caveat information for Cisco CallManager release 4.2(1) by using Bug Toolkit, which is an online tool that is available for customers to query defects according to their own needs.
Tip
To access Bug Toolkit, log on to the following URL:
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.plThis section includes the following topics:
Using Bug Toolkit
To access Bug Toolkit, you need the following items:
•
•
•
To use Bug Toolkit, follow this procedure.
Procedure
Step 1
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.plLog on with your Cisco.com user ID and password.
Step 2
Step 3
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
Step 5
a.
•
A major release contains significant new features, enhancements, architectural changes, and/or defect fixes.
•
A revision (maintenance) release primarily contains defect fixes to address specific problems, but it may also include new features and/or enhancements.
b.
•
Note
•
•
•
c.
Note
d.
•
•
•
e.
Bug Toolkit returns the list of caveats on the basis of your query.
•
•
Note
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
Step 2
A new window displays.
Step 3
Step 4
•
•
Note
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
•
•
–
–
•
Step 6
Step 7
Note
http://www.cisco.com/univercd/cc/td/doc/product/voice/c_ipphon/english/
Open Caveats for Cisco CallManager - Release 4.2(1)
Table 3 describes possible unexpected behaviors by Cisco CallManager release 4.2(1), sorted by component. Unless otherwise noted, these caveats apply to all Cisco CallManager 4.x releases up to and including Cisco CallManager release 4.2(1).
Tip
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.
•
•
•
•
•
Note
Tip
Note
http://www.cisco.com/univercd/cc/td/doc/product/voice/c_ipphon/english/
Troubleshooting
For troubleshooting information, refer to the Troubleshooting Guide for Cisco CallManager, Release 4.2(1). This document provides troubleshooting procedures for Cisco CallManager systems. The Troubleshooting Guide for Cisco CallManager provides guidance for network administrators responsible for managing the Cisco CallManager system, for enterprise managers, and for employees. This document does not cover every possible trouble event that might occur on a Cisco CallManager system but instead focuses on those events that are frequently seen by the Cisco Technical Assistance Center (TAC) and frequently asked questions from newsgroups.
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
This section includes information about errors in the Cisco CallManager Documentation suite:
•
Bulk Administration Tool User Guide Title Error
The Bulk Administration Tool User Guide is incorrectly named the Cisco CallManager Bulk Administration Guide in the following documents:
•
•
•
Changes
This section contains changes that have occurred since the original release of the Cisco CallManager release 4.2 documentation. These changes may not appear in the current documentation or the online help for the Cisco CallManager application:
•
•
•
Device Mobility Info Configuration Window
The subnet and subnet mask fields on the Device Mobility Info Configuration Window have been combined into one field in the format: [Network Address]/[Network Prefix Length].
Device Pool Configuration Window
The fields on the Device Pool Configuration window have been rearranged into groups: Device Pool Settings, Roaming Sensitive Settings, and Device Mobility Related Information settings. The Device Mobility Related Information settings overwrite device level settings when the device is roaming in the same device mobility group.
Behavior Enhancements to Join
The following information documents the enhancements made to the Join feature that is described in Cisco IP Phones, Cisco CallManager System Guide.
Join does not create a consultation call and does not put the active call on hold. To implement Join, choose at least two calls and then press the Join softkey on one of the calls. Join can include more than two calls, which results in a call with three or more parties. Join supports up to 16 participants in a call. To choose an active or held call, highlight the call and press the Select softkey. A selected call has a checked indicator shown next to it on the phone.
The call that initiates the Join gets automatically included, even if not selected. The active call gets included even if not selected.
If all the calls in the join are a basic call, then the call that initiated the join is the primary call. If any call in the join is a conference call (that is, it was in a conference before being joined), then that call is the primary call.
The selected status of the final call after the join depends on the selected status of the primary call before the join. If the primary call was selected, then after the join, the final call remains selected. If the primary call was not selected, then after the join, the final call remains unselected.
Note
Omissions
This section lists new and additional information that the current version of the Cisco CallManager documentation may not include:
•
•
Malicious Call Identification Restrictions
The Malicious Call Identification chapter of the Cisco CallManager Features and Services Guide does not list SIP trunk as a restriction. Malicious Call Identification (MCID) does not support SIP trunks.
TAPS Installation Procedure for CCM4.1(3)SR2 and Subsequent Releases
There is a new procedure for installing and configuring Cisco Tool for Auto-Registered Phone Support (TAPS) in IPCCx 4.0 as follows:
Step 1
Step 2
Step 3
Step 4
Step 5
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:
You can access international Cisco web sites at this URL:
http://www.cisco.com/public/countries_languages.shtml
Documentation DVD
Cisco documentation and additional literature are available in the Product Documentation DVD package, which may have shipped with your product. The Product Documentation DVD is updated regularly and may be more current than printed documentation.
The Product Documentation DVD is a comprehensive library of technical product documentation on portable media. The DVD enables you to access multiple versions of hardware and software installation, configuration, and command guides for Cisco products and to view technical documentation in HTML. With the DVD, you have access to the same documentation that is found on the Cisco webbiest without being connected to the Internet. Certain products also have PDF versions of the documentation available.
The Product Documentation DVD is available as a single unit or as a subscription. Registered Cisco.com users (Cisco direct customers) can order a Product Documentation DVD (product number DOC-DOCDVD=) from Cisco Marketplace at this URL:
http://www.cisco.com/go/marketplace/
Ordering Documentation
Beginning June 30, 2005, registered Cisco.com users may order Cisco documentation at the Product Documentation Store in the Cisco Marketplace at this URL:
http://www.cisco.com/go/marketplace/
Nonregistered Cisco.com users can order technical documentation from 8:00 a.m. to 5:00 p.m. (0800 to 1700) PDT by calling 1 866 463-3487 in the United States and Canada, or elsewhere by calling 011 408 519-5055. You can also order documentation by e-mail at tech-doc-store-mkpl@external.cisco.com or by fax at 1 408 519-5001 in the United States and Canada, or elsewhere at 011 408 519-5001.
Documentation Feedback
You can rate and provide feedback about Cisco technical documents by completing the online feedback form that appears with the technical documents on Cisco.com.
You can send comments about Cisco 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-9883We 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:
•
•
•
A current list of security advisories and notices for Cisco products is available at this URL:
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
This product contains cryptographic features and is subject to United States and local country laws governing import, export, transfer and use. Delivery of Cisco cryptographic products does not imply third-party authority to import, export, distribute or use encryption. Importers, exporters, distributors and users are responsible for compliance with U.S. and local country laws. By using this product you agree to comply with applicable laws and regulations. If you are unable to comply with U.S. and local laws, return this product immediately.
A summary of U.S. laws governing Cisco cryptographic products may be found at: http://www.cisco.com/wwl/export/crypto/tool/stqrg.html. If you require further assistance please contact us by sending email to export@cisco.com.
See the "Reporting Security Problems in Cisco Products" section for additional information.
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:
•
An emergency is either a condition in which a system is under active attack or a condition for which a severe and urgent security vulnerability should be reported. All other conditions are considered nonemergencies.
•
In an emergency, you can also reach PSIRT by telephone:
•
•
Tip
Never use a revoked or an expired encryption key. The correct public key to use in your correspondence with PSIRT is the one linked in the Contact Summary section of the Security Vulnerability Policy page at this URL:
http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html
The link on this page has the current PGP key ID in use.
Obtaining Technical Assistance
Cisco Technical Support provides 24-hour-a-day award-winning technical assistance. The Cisco Technical Support & Documentation website on Cisco.com features extensive online support resources. In addition, if you have a valid Cisco service contract, Cisco Technical Assistance Center (TAC) engineers provide telephone support. If you do not have a valid Cisco service contract, contact your reseller.
See the following sections for additional information:
•
•
Cisco Technical Support & Documentation Website
The Cisco Technical Support & Documentation 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, at this URL:
http://www.cisco.com/techsupport
Access to all tools on the Cisco Technical Support & Documentation 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
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 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 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-2447For 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.
•
http://www.cisco.com/go/marketplace/
•
•
•
http://www.cisco.com/go/iqmagazine
or view the digital edition at this URL:
http://ciscoiq.texterity.com/ciscoiq/sample/
•
•
http://www.cisco.com/en/US/products/index.html
•
http://www.cisco.com/discuss/networking
•
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, 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, 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, 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. (0601R)
© 2006 Cisco Systems, Inc. All rights reserved.
