Table Of Contents
Release Notes for Cisco CallManager Release 4.1(3)
Determining the Software Version
Compatibility Matrix and Supported Upgrades
Cisco CallManager Installation, Upgrade, and Backup Guidelines
Operating System Installation Guidelines
Upgrading to Cisco CallManager Release 4.1(3)
Before Upgrading to Cisco CallManager 4.13
Call Pickup and Group Call Pickup Enhancements
Group Call Pickup Enhancements
Other Group Pickup Enhancements
New Feature Support with Cisco IP Manager Assistant
New Service Parameter to Enable Music On Hold and Annunciator Duplex Streaming
Updated Support for Cisco IP Phones
New Hunt Pilot Configuration Parameters for Automated Alternate Routing
Support for Annex M1 over H.225 Trunks and H.323 Gateways
Support for Secure Cisco IOS MGCP Gateway Troubleshooting
Configuring Security for Voice-Mail Ports
Bulk Administration Tool Enhancements
BAT Support for Call Pickup Groups
New Call Classification Field Description
Dialed Number Analyzer Enhancements
New and Changed Information for Cisco CallManager Serviceability
Call Type Update in the CDR Search Results
New and Changed Information for Third-Party and SDK Applications
CDR Records Update for Call Pickup Features
CSCso79248 Do Not Run installxml.vbs in Unified CM Release 3.3 and Later
Using Cisco Unity Consult Transfer with Cisco CallManager Onhook Call Transfer
Performing CAPF Operations on Cisco IP Phones via VPN Connection
Adding Cisco CallManager Servers
Locale Installer for Cisco CallManager Release 4.1(3)
Using the JTAPI Update Utility with CRS
Upgrade Requirements for CRS and Cisco CallManager 4.1
NetMeeting Calls Fail When T.38 is Advertised to NetMeeting
Cisco CallManager Installation Status Bar
CTI Route Point Considerations
Cisco CallManager Extension Mobility Scalability Update
Disabling IPSec for Cisco CallManager Upgrades
Disabling IPSec on the Cisco CallManager Server
Enabling IPSec on the Cisco CallManager Server
Support for Multicluster Integration with Active Directory
Requirement for Installation of Java Virtual Machine
Resolved Caveats for Cisco CallManager - Release 4.1(3)
Open Caveats for Cisco CallManager - Release 4.1(3)
Cisco CallManager Dialed Number Analyzer Service Startup Type
Barging into Encrypted Calls with the Cisco IP Phone Model 7970
Using Valid Characters in Cisco CallManager User IDs
Cisco CallManager Security Guide Corrections
Removing a Subscriber Server from Cisco CallManager
Using Script Files to Remove a Subscriber Server from Cisco CallManager
Clarification to MLPP Interaction with Call Transfer
Correction to Forward No Coverage Internal/External Configuration
Correction to the Procedure for Adding a Cisco CallManager
Cisco Call Back Supports Lines Not Devices
Associating H.323 Devices to Users
Meet-Me Conference Limitations
? Icon Displays Incorrect Online Help for Region and Calling Search Space Pop Up Windows
Name Change for the Cisco IAD 2400 Gateway Type in Cisco CallManager Administration
Route List Redundancy Configuration
Cisco IP Phone Models 7940/7960 Built-In Bridge and Device Security Considerations
CAPF Interaction When Cisco IP Phone Resets
Using Server Authentication, Third-Party CA Certificates
Using Shared Lines with Encrypted Devices
Reinstalling Dialed Number Analyzer After a Cisco CallManager Upgrade
Support for the Cisco VG224 Gateway
Call Back Feature Interactions with Call Forward, iDivert, and Voice-Mail System Features
Tool for Autoregistered Phone Support Information for End Users
Cisco Product Security Overview
Reporting Security Problems in Cisco Products
Obtaining Technical Assistance
Cisco Technical Support Website
Definitions of Service Request Severity
Obtaining Additional Publications and Information
Release Notes for Cisco CallManager Release 4.1(3)
Updated June 23, 2008
These release notes describe the new features and caveats for Cisco CallManager release 4.1(3).
Note
To view the release notes for previous versions of Cisco CallManager, go to: http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/index.htm
Before you install Cisco CallManager, Cisco recommends that you review the "Important Notes" section for information about issues that may affect your system.
For a list of the open and resolved caveats for Cisco CallManager release 4.1(3), see the "Resolved Caveats for Cisco CallManager - Release 4.1(3)" section and the "Open Caveats for Cisco CallManager - Release 4.1(3)" section. Updates for these release notes occur with every maintenance release and major release.
To access the documentation suite for voice products, refer to the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/voice/
You can access the latest software upgrades and release notes for all versions of Cisco CallManager on Cisco Connection Online (CCO) at the following URL:
http://www.cisco.com/public/sw-center/sw-voice.shtml
Contents
These release notes discuss the following topics:
•
•
•
•
•
•
Introduction
Cisco CallManager, a network business communication system, provides high-quality telephony over IP networks. Cisco CallManager enables the conversion of conventional, proprietary, circuit-switched PBXs to multiservice, open LAN systems.
System Requirements
Make sure that you install and configure Cisco CallManager release 4.1(3) on a Cisco Media Convergence Server (MCS).
You may also install Cisco CallManager on a Cisco-approved HP server configuration or a Cisco-approved IBM server configuration.
Note
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.1(3).
Determining the Software Version
To determine the software version of Cisco CallManager, open Cisco CallManager Administration; then, click Details on the main Cisco CallManager Administration window. The following information displays:
•
•
•
Compatibility Matrix and Supported Upgrades
You can find which application versions are compatible with Cisco CallManager release 4.1(3) and which previous release of Cisco CallManager has upgrade support by referring to the Cisco CallManager Compatibility Matrix at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/ccmcomp.htm
Note
Related Documentation
Refer to the Cisco CallManager Document Guide for a list of documents that are related to Cisco CallManager release 4.1 at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/4_1/doc_gd.
Along with the documents that are listed in the Cisco CallManager Document Guide, the following list specifies other related documents for Cisco CallManager release 4.1:
•
•
•
•
•
•
•
•
•
•
•
•
New and Changed Information
This following sections describe new features and changes that are pertinent to this release of Cisco CallManager. The sections may include configuration tips for the administrator, information about users, and where to find more information.
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Cisco CallManager Installation, Upgrade, and Backup Guidelines
This section includes information about the guidelines that apply to Cisco CallManager 4.1(3) installation, upgrade, and backup and restore procedures:
Installation and Upgrade
Cisco CallManager 4.1(3) implements the following installation and upgrade guidelines:
•
•
This section includes the following topics:
•
Upgraded Memory Requirement
The Cisco CallManager installation requires a minimum of 1 GB of memory on the Cisco CallManager publisher server. If the installation process detects less than 1 GB of memory, the installation aborts.
The installation process performs a similar check on the Cisco CallManager subscriber server; it may allow the installation to continue if it detects less than the minimum requirement.
Note
Adding Cisco CallManager Servers as Members of a Windows Domain
Cisco does not recommend adding Cisco CallManager servers as members of a Microsoft Windows domain. To prevent failures that may occur by the server being a member of a domain, Cisco CallManager 4.1(3) modifies the installation process to abort the installation and displays the following message if it detects that the server is in a Windows domain:
"The installation has detected that the server exists in a domain. When a server exists in a domain, authentication between servers may fail, or the non-default domain security policies may be too restrictive for the Cisco CallManager installation to build critical NT Accounts during an upgrade. Your server must be removed from the domain and added to a workgroup to reduce installation and upgrade errors, failures, or a total system failure, which would result in a loss of data and a complete reinstallation of Cisco CallManager. The installation will now abort."
Note
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.1(3) replaces previous versions of Cisco CallManager Upgrade Assistant Utility, release 3.3(5), 4.0(2a), and 4.1(2).
This updated release of Cisco CallManager Upgrade Assistant Utility adds support for multiple version upgrades; that is, you can use Cisco CallManager Upgrade Assistant Utility version 4.1(3) or later to detect the health of your servers before you upgrade to Cisco CallManager release 3.3(5), 4.0(2a), 4.1(2), or 4.1(3).
For additional information, refer to Using Cisco CallManager Upgrade Assistant Utility 4.1(3) at the following URL. http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/4_1/install/upgrade/index.htm
Backup and Restore
The following guidelines apply to Cisco CallManager backup and restore procedures:
•
•
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
Cisco recommends that you install Cisco IP Telephony operating system version 2000.2.7 with the latest service release 2000.2-7-sr(x) before you upgrade to Cisco CallManager release 4.1(3).
Tip
Note
Where to Find More Information
•
Upgrading to Cisco CallManager Release 4.1(3)
For detailed information about upgrading to Cisco CallManager 4.1(3), refer to Upgrading Cisco CallManager Release 4.1(3). For additional guidelines about Cisco CallManager installation and upgrades, see the "Cisco CallManager Installation, Upgrade, and Backup Guidelines" section.
Tip
•
•
•
Note
•
Tip
Before Upgrading to Cisco CallManager 4.13
Perform the following step on the voice-mail ports to ensure proper migration:
Important: Remove any call forwarding that is set on voice-mail ports that are used only for outbound calls and message waiting indication.
Call Pickup and Group Call Pickup Enhancements
Cisco CallManager 4.1(3) introduces the following enhancements to the Call Pickup and Group Call Pickup features:
•
•
Tip
To enable the OPickup softkey in the offhook state, follow the procedure to configure the softkey layout. Click the Off Hook call state. From the Unselected Softkeys list, choose the Other Pickup softkey and click the right arrow to move this softkey to the Selected Softkeys list.You can retrieve calls from a queue in your group by pressing one of the following pickup softkeys:
•
•
•
Note
•
•
•
True—Set this service parameter to True to enable the automatic, or one-touch, pickup functionality.
False—Set this service parameter to False to use the existing call pickup and group call pickup functionality.
The default value specifies False to retain backward compatibility with earlier versions of Cisco CallManager.
Note
•
The default value specifies 1 second.
Note
Refer to the Cisco CallManager Administration Guide for detailed information about these administration configuration windows.
Call Pickup Enhancements
Cisco CallManager 4.1(3) enhances the Call Pickup feature by allowing you to automatically answer a call that is ringing in your pickup group by pressing only the Pickup softkey. This enhancement streamlines call pickup functionality by removing the need to press the NewCall and Answer softkeys to complete a call pickup.
The administrator configures the pickup groups, and enables the automatic pickup functionality by configuring the Auto Call Pickup Enabled service parameter in the Cisco CallManager Administration Service Parameters Configuration window. The following valid configuration values apply:
•
•
You invoke the Call Pickup feature by pressing the Pickup softkey on the phone. The phone picks up the longest alerting call in the group.
1.
2.
3.
Group Call Pickup Enhancements
This release enhances the Group Call Pickup feature by allowing you to answer a call that is ringing at another device in another specified pickup group by pressing the GPickup softkey and then entering the Group Pickup number of the group that you want to pick up. When auto-pickup is enabled, the Group Pickup feature allows you to perform a call pickup by pressing a single softkey followed by the Group Pickup number.
Like the Call Pickup feature, the one-touch Group Pickup feature removes the need to press the NewCall and Answer softkeys to complete a group pickup.
To enable the automatic Group Pickup feature, the administrator configures the Auto Call Pickup Enabled service parameter in the Cisco CallManager Administration Service Parameters Configuration window. See the "Call Pickup Enhancements" section for additional information.
You invoke the Group Call Pickup feature by pressing the GPickup softkey on the phone. The phone picks up the longest alerting call in the group.
1.
2.
3.
4.
Note
Other Group Pickup Enhancements
Cisco CallManager 4.1(3) allows the administrator to provision other pickup groups for each pickup group. The OPickup softkey allows you to pick up calls in one of the associated groups that are configured as an other pickup group.
With auto-pickup enabled, the Other Pickup Group feature allows you to pick up calls in your group and in other associated groups that your administrator has configured, without the need to enter the group number. The phone will follow the sequence that the administrator configured to check each pickup group and will pick up the longest alerting call in the first group in which it finds calls.
The administrator defines the Other Group Pickup feature on the Cisco CallManager Administration Pickup Group Configuration window. The system supports up to 10 other pickup groups per pickup group.
You invoke the Other Group Pickup feature by pressing the OPickup softkey on the phone. The phone picks up the longest alerting call in the first group in which it finds calls.
1.
2.
3.
Note
Note
Where to Find More Information
•
•
•
•
•
Call Transfer Enhancements
Cisco CallManager 4.1(3) introduces the following enhancements to the Call Transfer feature:
•
•
•
True—Set this service parameter to True to enable the onhook call transfer functionality; this functionality allows the user to complete a call transfer by either going on hook or by pressing the Transfer softkey.
False—Set this service parameter to False to maintain the existing call transfer functionality; that is, the user completes the call transfer by pressing the Transfer key. The default value specifies False to preserve backward compatibility with earlier versions of Cisco CallManager.
Refer to the Cisco CallManager Administration Guide for detailed information about this administration configuration window.
•
•
•
•
Note
With Onhook Call Transfer enabled, you can invoke this feature by pressing the Transfer softkey. If you do not need to announce the caller who you are transferring, you can perform a regular call transfer by following these steps:
1.
2.
3.
To perform a consult transfer and announce the caller that you are transferring, follow these steps:
1.
2.
3.
Note
Where to Find More Information
•
•
•
New Feature Support with Cisco IP Manager Assistant
Cisco IP Manager Assistant (Cisco IPMA) does not provide support for the following feature enhancements in Cisco CallManager 4.1(3):
•
•
For additional information about Cisco IPMA, refer to the Cisco CallManager Features and Services Guide.
New Service Parameter to Enable Music On Hold and Annunciator Duplex Streaming
Cisco CallManager 4.1(3) includes a new service parameter, Duplex Streaming Enabled, for music on hold (MOH) and Annunciator. This service parameter determines whether MOH and Annunciator use duplex (two-way) or simplex (one-way) audio streams.
You can configure one of the following values for this service parameter:
•
•
Set the Duplex Streaming Enabled service parameter by using Cisco CallManager Administration to access the service parameters (Service > Service Parameters). Choose the server where the Cisco CallManager application resides. On the Cisco CallManager Administration Service Parameters Configuration window, scroll down to the Cluserwide Parameters (Service) section to configure the Duplex Streaming Enabled parameter.
For more information, refer to http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeg49352.
For detailed information about configuring service parameters, refer to the Cisco CallManager Administration Guide.
Updated Support for Cisco IP Phones
Cisco CallManager 4.1(3) updates support for the following Cisco IP Phones to include the call pickup and call transfer feature enhancements:
•
•
•
The following Cisco IP Phones do not provide support for the feature enhancements in this release:
•
•
•
For more information about Cisco IP Phones, refer to the following URL for the appropriate Cisco IP Phone guide for your model of Cisco IP Phone:
http://www.cisco.com/univercd/cc/td/doc/product/voice/c_ipphon/index.htm.Where to Find More Information
•
•
•
•
•
•
New Hunt Pilot Configuration Parameters for Automated Alternate Routing
Automated Alternate Routing (AAR) enables call reroute through the PSTN or other network by using an alternate number when Cisco CallManager blocks a call because of insufficient location bandwidth. Using AAR provides a benefit because the caller does not need to hang up and redial the called party.
Cisco CallManager 4.1(3) extends the Automated Alternate Routing functionality to include the hunt pilot number. (Cisco CallManager does not provide support for this enhanced functionality in Cisco CallManager version 4.x and earlier.)
In Cisco CallManager releases earlier than version 4.x, when a remote user tries to connect to the voice-messaging system in a central location and bandwidth is not available on the WAN link, Cisco CallManager could reroute the call through the PSTN gateway to the voice-messaging system.
Beginning with Cisco CallManager 4.0, AAR does not work with hunt pilots. Because the fully qualified directory number (DN) of the hunt pilot is unknown, AAR cannot initiate the reroute.
Hunt Pilot Configuration
To preserve the AAR functionality, Cisco CallManager 4.1(3) introduces the following new AAR Group Settings parameters on the Cisco CallManager Administration Hunt Pilot Configuration window:
•
•
Note
You can access the AAR Group Settings parameters on the Hunt Pilot Configuration window from Cisco CallManager Administration by navigating to Route Plan > Route/Hunt > Hunt Pilot. On the Cisco CallManager Administration Hunt Pilot Configuration window, scroll down to the AAR Group Settings section.
Service Parameter Configuration
In addition to configuring the AAR Group Settings, make sure that you configure the following service parameter to enable the proper function of AAR:
•
You can access the Automated Alternate Routing Enable parameter on the Service Parameters Configuration window from Cisco CallManager Administration by navigating to Service > Service Parameters. Choose the server where the Cisco CallManager application resides. On the Cisco CallManager Service Parameters Configuration window, scroll down to the Clusterwide Parameters (System - CCM Automated Alternate Routing) section to configure this parameter.
For additional information about AAR, refer to the Cisco CallManager Administration Guide and the Cisco CallManager System Guide.
Where to Find More Information
•
•
Support for Annex M1 over H.225 Trunks and H.323 Gateways
Cisco CallManager 4.1(3) extends its interoperability by adding support for QSIG tunneling via Annex M1 over H.225 trunks and H.323 gateways. With this enhancement, Cisco CallManager expands QSIG functionality by allowing you to configure tunneled protocol for H.225 trunks and H.323 gateways as you can currently configure for intercluster trunks.
Note
For information about other feature support and third-party interoperability with Cisco CallManager, refer to the Cisco Interoperability Portal at the following URL: http://www.cisco.com/go/interoperability.In this release, Cisco CallManager Administration updates enable configuration of tunneled protocol for H.225 trunks and H.323 gateways in the Cisco CallManager Administration Trunk Configuration and Gateway Configuration windows.
Trunk Configuration
From Cisco CallManager Administration, navigate to the Trunk Configuration window (Device > Trunk > Add a New Trunk) and configure the following fields:
•
•
Gateway Configuration
To complete the configuration, configure the same fields for H.323 gateways. From Cisco CallManager Administration, navigate to the Gateway Configuration (Device > Gateway > Add a New Gateway) and configure the following fields:
•
•
For additional information, refer to the Cisco CallManager Administration Guide and the Cisco CallManager System Guide.
Where to Find More Information
•
•
•
Security Enhancements
This section includes information about the following security enhancements in Cisco CallManager 4.1(3):
•
•
Support for Secure Cisco IOS MGCP Gateway Troubleshooting
Cisco CallManager 4.1(3) introduces support for secure Cisco IOS MGCP gateway troubleshooting. With this release, a new TAC debugging tool allows for the capture of encrypted MGCP messages and backhaul messages exchanged between Cisco CallManager and the secure Cisco IOS MGCP gateway. This troubleshooting tool diagnoses VoIP signaling and Real-Time Transport Protocol (RTP) streaming problems by analyzing the sniffed network traffic.
To successfully debug signaling problems, troubleshooting tools need to capture the plain text (decrypted) signaling packets that are sent to and received from the secure devices. To debug media problems, the tools need to capture the Secure Real-Time Transport Protocol (SRTP) encryption keys that are exchanged in MGCP signaling messages. Cisco CallManager 4.1(3) adds an interface to supply the plain text signaling packets for debugging Cisco IOS MGCP gateways. The gateway signaling packets include UDP-based MGCP messages and TCP-based backhaul messages.
The debugging tool establishes the encrypted Transport Layer Security (TLS) session with Cisco CallManager. Cisco CallManager and the troubleshooting tool authenticate each other by examining the certificate in the TLS session establishment. Cisco CallManager also determines whether the troubleshooting tool has administrative privileges to receive the secure signaling messages.
When a secure Cisco IOS MGCP gateway registers with Cisco CallManager, the system retrieves the configured Signal Packet Capture Mode and Packet Capture Duration settings for all devices on the gateway. When a device is configured for packet capturing, Cisco CallManager sends MGCP messages and backhaul messages for the gateway that is configured for real-time monitoring through the TLS connection. All the MGCP and backhaul messages that are sent to the debugging tool are nonencrypted in plain text format but are encrypted by a TLS session between Cisco CallManager and the troubleshooting tool.
Troubleshooting Tool Modes
The troubleshooting tool, which is configurable on a per-device basis, operates in two modes:
•
•
Configuring Packet Capturing in the MGCP Gateway Configuration Window
Cisco CallManager Administration supports the following Cisco IOS MGCP gateways with configurable settings for Packet Capture Mode and Packet Capture Duration on a per-port basis in the Gateway Configuration window:
•
•
•
•
•
•
•
•
The default value and range for Packet Capture Mode and Packet Capture Duration specify None (indicates that no packet capturing is occurring) and 60, respectively. Packet Capture Duration specifies the maximum number of minutes for one session of packet capturing. The default setting specifies 60; the allowable values range from 0 to 300 minutes.
Note
Troubleshooting Encryption for Cisco IP Phones and Cisco IOS MGCP Gateways
Because third-party troubleshooting tools that sniff media and TCP packets do not work after you enable encryption, you must use Cisco CallManager Administration to perform the following tasks if a problem occurs:
•
•
•
Configuration Tips (for Administrators)
•
•
•
•
•
•
•
Where to Find More Information
•
•
Configuring Security for Voice-Mail Ports
When you configure security for Cisco CallManager voice-mail ports and Cisco Unity SCCP devices, a TLS connection (handshake) opens for authenticated devices after each device accepts the other device's certificate. The system also sends SRTP streams between devices if you configure the devices for encryption.
•
•
Configuration Tips (for Administrator)
•
•
•
•
•
•
•
•
•
•
Where to Find More Information
•
•
Bulk Administration Tool Enhancements
The Bulk Administration Tool (BAT) version 5.1(4) supports Cisco CallManager release 4.1(3) and provides support for the following features and enhancements:
•
•
BAT Support for Call Pickup Groups
BAT 5.1(4) now provides support for call pickup groups. The following guidelines apply when you use BAT to configure call pickup groups:
•
•
•
For example, use the following format when you enter information for pickup groups:
(Pickup Group Name, Pickup Group Number, Partition, Other Pickup Group Name-Member1... Other Pickup Group Name-Member10)
Marketing,7815,Part1,Marketing,Managers,Training
•
•
•
•
•
New Call Classification Field Description
The BAT 5.1(4) web interface reflects a name change for the Device Destination field for non-FXS endpoints for a VG200 gateway to Call Classification. With this change, the Call Classification field replaces the Device Destination field in the gateway template.
You can use the following Call Classification field description when you are adding or updating values for the E&M ports for T1 CAS trunks on a Cisco VG200 gateway and when you are adding or updating values for T1 PRI or E1 PRI trunks on a Cisco VG200 gateway.
For additional information about BAT features and functionality, refer to the Bulk Administration Tool User Guide.
Where to Find More Information
•
•
•
Dialed Number Analyzer Enhancements
Dialed Number Analyzer (DNA) enables analysis of a configured Cisco CallManager dial plan (one pattern at a time) and provides details about the call flow of dialed digits. In the pre-deployment phase, you can use the tool to identify problems in a complex dial plan; in the post-deployment phase, you can use the tool to identify real-time problems in the call flow of dialed digits.
Cisco CallManager 4.1(3) updates DNA to support analysis of multiple dialed numbers by providing an interface to allow multiple analysis and dial plan bulk testing, along with generation of a corresponding bulk output report.
DNA Analysis by Using Multiple Analyzer
In this release of Cisco CallManager, DNA provides a Multiple Analyzer window that allows you to choose a CSV file that contains a list of data that is required for analysis. DNA then processes the CSV file and displays the bulk output results.
During DNA installation, the template, DNATemplate.zip, loads on the server. Use this template to create a CSV file that contains multiple sets of calling party numbers and corresponding dialed digits, calling search spaces, device time zones, time zones, and date and time information. You can upload or download these files by using the Multiple Analyzer window in DNA.
Note
Refer to the Cisco CallManager Dialed Number Analyzer Guide for additional information about Multiple Analyzer, include creating a CSV input file by using the DNA template, uploading or downloading the files, and viewing and analyzing the file contents.
Caution
Where to Find More Information
•
New and Changed Information for Cisco CallManager Serviceability
This section describes the following new serviceability features and changes that pertain to this release of Cisco CallManager:
•
Call Type Update in the CDR Search Results
Cisco CallManager 4.1(3) updates CDR Analysis and Reporting (CAR) by populating the Call Type field in the Cisco CallManager Call Detail Record (CDR) search results with "pickup" for automatic pickup, automatic group pickup, and automatic other pickup calls. CAR can distinguish between automatic pickup/group pickup calls and forwarded calls because the CDRs distinguish between these call types.
With this addition, the CDR search provides the following Call Type field descriptive information:
The type of call: simple, transfer, forward, pickup, or conference.
As in previous releases, CDRs still categorize pickup, group pickup, and other pickup calls as forwarded calls, and CAR populates the Call Type field for these call types with forward.
For additional information about CDR Analysis and Reporting (CAR), refer to the Cisco CallManager Serviceability Administration Guide. For more information about automatic pickup and automatic group pickup, see the "Call Pickup and Group Call Pickup Enhancements" section and refer to the Cisco CallManager Administration Guide and the Cisco CallManager System Guide.
Where to Find More Information
•
•
•
•
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:
Guest
