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):
•
–
–
–
–
•
•
–
–
–
–
•
Guest
