Table Of Contents
Release Notes for Cisco CallManager Release 5.0(1)
Contents
Introduction
System Requirements
Supported Platforms
Determining the Software Version
Upgrading System Software
Related Documentation
New and Changed Information
Installation, Upgrade, Migration, and Disaster Recovery
Installation Overview
Software Upgrades
Data Migration Assistant (DMA)
Disaster Recovery Enhancements
Where to Find More Information
Cisco IP Telephony Platform Administration
Overview
Browser Requirements
Platform Status and Configuration
Settings
Restart Options
Security Configuration
Software Upgrades
Services
Command Line Interface
Where to Find More Information
Cisco CallManager Administration
General Administration Enhancements
Navigating to IP Telephony Applications Within Cisco CallManager
Localizing Cisco CallManager Administration
Configuring Servers
Publisher and Subscriber Name Changes
Media Resources
Migration Tips
General Changes Made to Multiple Windows
Line and Phone Configuration Improvements
System Menu Changes
Call Routing Menu Changes (formerly Route Plan Menu)
Media Resources Menu
Voice Mail Menu
Device Menu Changes
Application Menu Changes
User Management Menu
Bulk Administration Menu
Service Parameter Changes
Where to Find More Information
Cisco CallManager Features
Call Forwarding Enhancements
Call Park
Call Pickup Group
CTI and CTI Super Provider
Dynamic Host Control Protocol (DHCP)
International Dial Plans
LDAP Directory Enhancements
Licensing
Personal Directory Enhancements
Phone NTP References for SIP Phones
Presence
Roles and User Groups
RSVP
Service Enhancements
SIP Line Side (Endpoints) Support
SIP Route Pattern
SIP Third-Party Phones
SIP Trunk Enhancements
TFTP Enhancements
URL Dialing
Video Telephony Enhancements
Voice Quality Metrics
Cisco CallManager User Options Web Pages
Addition of the Cisco Personal Communications Assistant Layer
Redesigned User Interface
Where to Find More Information
Cisco CallManager Applications
Cisco Call Back
Cisco CallManager Attendant Console
Cisco CallManager AutoAttendant
Cisco CallManager Extension Mobility
Cisco Dialed Number Analyzer
Cisco Emergency Responder 1.3(1)
Cisco IP Manager Assistant
Cisco Unity Voice Messaging
Cisco WebDialer
Client Matter Codes and Forced Application Codes
Multilevel Precedence and Preemption (MLPP)
Music On Hold
Quality Report Tool
Bulk Administration Tool Features
Installation Considerations
New and Changed Information for BAT
BAT Configuration Tips
Serviceability Considerations
Security Considerations
BAT Performance
TAPS Features
Installation Considerations
TAPS Configuration Tips
Serviceability Considerations
Security Considerations
Security Features
Cisco CallManager Administration Configuration Tips
Where to Find More Information
New and Changed Information for Cisco CallManager Serviceability
Serviceability Administration
Real-Time Monitoring Tool
Trace & Log Central
SysLog Viewer
CDR Analysis and Reporting (CAR)
Where to Find More Information
New and Changed Information for Cisco IP Phones
Cisco IP Phone Feature Differences by Protocol
Supported Cisco IP Phones Using the SIP Protocol
New Features Supported by Cisco CallManager Release 5.0(1)
Feature Support Listed by Phone Model and Protocol
New and Changed Information for Third-Party API
Cisco CallManager Developers Guide
CDR Definitions
Cisco IP Phone Service Application Development Notes for Cisco CallManager 5.0(1)
JTAPI Developers Guide
SCCP Messaging Guide
SIP Messaging Guide
TAPI Developers Guide
Installation Notes
Limitations and Restrictions
Important Notes
Using Call Park
Failover Time Using UDP Protocol on SIP Phones
Premature Certificate Generation Prevents Immediate Service Activation After a Fresh Installation
SIP Trunk Configuration
Unplugging a USB Cable
Cisco MCS-7845H-2.4-EVV1 and Cisco MCS-7835H-2.4-EVV2 Server May Not Recognize the USB-to-Serial Cable
Configuring Regions (Region Relationship) For SIP Devices with the MTP Required Option Enabled
Support for SIP WSM Connection
Caveats
Resolved Caveats
Using Bug Toolkit
Saving Bug Toolkit Queries
Open Caveats
Troubleshooting
Documentation Updates
Errors
Description of the Cisco IP phone proxy server
Definition of Originating Codec and Destination Codec
Name Correction for Cisco Database Service
Using the Command Line Interface to Stop/Start Services
Guidelines for the Cisco CallManager Application User
Password for Cisco CallManager Serviceability Administration
Changes
Perfmon Counter Name Changes
Ethernet Settings
Command Line Interface
Omissions
CTI Monitored Lines
Malicious Call Identification Restrictions
Call Control for Attendant Console
Destination Address for SIP Trunk Configuration
Music On Hold
Resource Reservation Protocol (RSVP)
NIC Teaming
Installing Device Packs and Phone Firmware Loads
Saving and Uploading Third-Party Security Certificates
Accessing Cisco Security Agent (CSA) Logs
Changing the IP Address on a Cisco CallManager Node
Obtaining a License File
Obtaining Documentation
Cisco.com
Product Documentation DVD
Ordering Documentation
Documentation Feedback
Cisco Product Security Overview
Reporting Security Problems in Cisco Products
Obtaining Technical Assistance
Cisco Technical Support & Documentation Website
Submitting a Service Request
Definitions of Service Request Severity
Obtaining Additional Publications and Information
Release Notes for Cisco CallManager Release 5.0(1)
Updated July 10, 2007
These release notes describe the new features and caveats for Cisco CallManager release 5.0(1).
To view the release notes for previous versions of Cisco CallManager, choose the Cisco CallManager version from the following URL: 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.
Note 
Cisco recommends that you check Cisco.com for the latest software updates to Cisco CallManager and its applications, and download and install the latest updates on your system before the deployment of your Cisco CallManager system. For a list of commonly used URLs, see the "Upgrading System Software" section.
Contents
These release notes discuss the following topics:
•Introduction
•System Requirements
•Related Documentation
•New and Changed Information
•Installation Notes
•Limitations and Restrictions
•Important Notes
•Caveats
•Troubleshooting
•Documentation Updates
•Obtaining Documentation
•Documentation Feedback
•Cisco Product Security Overview
•Obtaining Technical Assistance
•Obtaining Additional Publications and Information
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 5.0(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.
Cisco CallManager 5.0 requires a minimum of the following on the Cisco CallManager servers.
•2 GB of memory
•72 GB Disk Drive
•2 GHz processor
Cisco recommends that you connect each Cisco CallManager node to an Uniterruptible Power Supply (UPS) to provide backup power and protect your system against a power failure.
Supported Platforms
To find which servers support Cisco CallManager 5.0 releases, please refer to the Guide to Cisco CallManager Upgrades and Server Migrations at http://www.cisco.com/en/US/partner/products/hw/voiceapp/ps378/prod_brochure_list.html
Determining the Software Version
To determine the software version of Cisco CallManager, open Cisco CallManager Administration. The following information displays:
•Cisco CallManager System version
•Cisco CallManager Administration version
Upgrading System Software
You can access the latest software upgrades for Cisco CallManager 5.0 on Cisco.com. Table 1 lists the URLs where you access the software.
Related Documentation
Refer to the Cisco CallManager Document Guide for a list of documents that are related to Cisco CallManager release 5.0 at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/5_0/doc_gd/index.htm
New and Changed Information
The 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.
•Installation, Upgrade, Migration, and Disaster Recovery
•Cisco IP Telephony Platform Administration
•Cisco CallManager Administration
•Cisco CallManager Features
•Cisco CallManager User Options Web Pages
•Cisco CallManager Applications
•Bulk Administration Tool Features
•TAPS Features
•Security Features
•New and Changed Information for Cisco CallManager Serviceability
•New and Changed Information for Cisco IP Phones
•New and Changed Information for Third-Party API
Installation, Upgrade, Migration, and Disaster Recovery
This following sections describe the changes made to the installation, upgrade, and disaster recovery procedures in Cisco CallManager 5.0(1):
•Installation Overview
•Software Upgrades
•Data Migration Assistant (DMA)
•Disaster Recovery Enhancements
•Where to Find More Information
Installation Overview
Cisco CallManager 5.0(1) uses a different installation framework than previous releases. The installation process allows you to perform a basic installation, upgrade from Cisco CallManager 4.x to Cisco CallManager 5.0, and upgrade to a newer service release during the installation.
Note Although you do not need a license to install Cisco CallManager 5.0(1), you must have a Cisco CallManager server license to activate services on the server and you must have phone licenses to add phones to the Cisco CallManager database.
For a more detailed description of the different installation types, see Table 2.
Table 2 Installation Options
Installation Types
|
Description
|
Basic Install
|
This option represents the basic Cisco CallManager 5.0(1) installation, which installs the software from the installation disc and does not use any imported data.
|
Upgrade During Install
|
This option allows you to upgrade the software version contained on the installation disc with the latest service release. You can also choose Upgrade During Install followed by a Windows Upgrade and perform both during the installation process.
|
Windows Upgrade
|
This option allows you to import database information from a Cisco CallManager 4.x system using a file produced by the Data Migration Assistant (DMA) tool.
|
Software Upgrades
With Cisco CallManager 5.0, you can install software upgrades on your server while the system continues to operate. Multiple partitions exist on your system disk, including an active, bootable partition and an inactive, bootable partition. The system boots up on the partition that is marked as the active partition.
When you install the software upgrades by using the Cisco IP Telephony Platform interface, you install the software on the inactive partition. The system continues to function normally while you are installing the software. When you are ready, you activate the inactive partition and reboot the system with the new upgrade software. The current active partition will then get identified as the inactive partition when the system restarts. The current software remains in the inactive partition until the next upgrade.
You can also back out of an upgrade by restarting the system using the software version on the inactive partition. However, if you have made any configuration changes since you installed the upgrade, they get lost when you revert to the older version of the software.
Data Migration Assistant (DMA)
The Cisco DMA assists you with the first step in migrating Cisco CallManager 4.x data to Cisco CallManager 5.0 by backing up Cisco CallManager 4.x data in a format that Cisco CallManager 5.0 can read. Cisco CallManager 4.x runs in a Windows environment, and Cisco CallManager 5.0 runs in a Linux environment, so the Cisco DMA exports Windows-based data to a format that Cisco CallManager 5.0 can import. The Cisco CallManager 5.0 installation process converts the backed up data as needed for Cisco CallManager 5.0, which completes the data migration.
The Cisco DMA saves the data that it exports in a tape archive (tar) file in a location that you specify.
You must install and run the Cisco DMA on the Cisco CallManager publisher server before you upgrade to Cisco CallManager 5.0. If you make any Cisco CallManager configuration changes after running the the Cisco DMA, the system does not retain these changes when you upgrade.
In addition to exporting Cisco CallManager data, the Cisco DMA exports data for these related applications:
•Attendant Console (AC)
•Cisco CallManager Extension Mobility (EM). DMA does not export the last user logged in data.
•CDR Analysis and Reporting (CAR)
•Certificate Authority Proxy Function (CAPF)
•Certificate Trust List (CTL)
Note If you installed the CAPF utility 1.0(1) on a Cisco CallManager 4.0 subscriber server, you must copy the CAPF data to the 4.0 publisher database server before you upgrade to Cisco CallManager 5.0. Failing to perform this task causes a loss of CAPF data.
The Cisco DMA does not export this information:
•Custom Music on Hold (MOH) files—You must reapply these files after you upgrade to Cisco CallManager 5.0.
•TFTP phone load files—You must reapply these files after you upgrade to Cisco CallManager 5.0.
•Files on Cisco CallManager subscriber servers—Subscriber servers obtain required information from the publisher server as part of the Cisco CallManager upgrade process.
•Last Logged User in Extension Mobility—Extension mobility users will need to enter the user name and PIN to login the first time after the upgrade. The user does not need to enter the user name on subsequent logins.
•CDR database—If you want to preserve the historical data in the CDR database, you must back up the data in the CDR database. You can use the backup utility on Microsoft SQL server.
Disaster Recovery Enhancements
The Cisco Disaster Recovery System (DRS), accessed from the Cisco CallManager 5.0(1) Administration window, provides full data backup and restore capabilities for all servers in a Cisco CallManager cluster. Cisco DRS allows you to perform regularly scheduled automatic or manually initiated data backups and system restoration.
The Cisco Disaster Recovery System performs a cluster-level backup, which means that it collects backups from all servers in a Cisco CallManager cluster to a central location, then combines the backups into a single volume (or multiple volumes if necessary), and archives the backup data to a physical storage device.
When performing a system data restoration, you can choose which nodes and features in the cluster you want to restore.
The Cisco Disaster Recovery System features include:
•Graphical user interface for performing backup and restore tasks
•Command-line access to most Cisco DRS functions
•Scheduling engine to initiate tasks at user-specified times
•Archives backed up to a physical tape drive or to a remote server
Where to Find More Information
•Cisco IP Telephony Disaster Recovery System Administration Guide
•Cisco IP Telephony Data Migration Assistant 2.0 User Guide
•Upgrading Cisco CallManager Release 5.0(1)
•Installing Cisco CallManager Release 5.0(1)
•Cisco IP Telephony Platform Administration Guide, Release 5.0(1)
Cisco IP Telephony Platform Administration
For Cisco CallManager 5.0(1), you can perform many common system administration functions through the Cisco IP Telephony platform.
This chapter comprises the following topics:
•Overview
•Browser Requirements
•Platform Status and Configuration
•Restart Options
•Security Configuration
•Software Upgrades
•Services
•Command Line Interface
Overview
Cisco IP Telephony Platform Administration allows you to configure and manage the Cisco IP Telephony platform by doing these tasks:
•Check software and hardware status.
•Check and update IP addresses.
•Ping other network devices.
•Manage NTP servers.
•Upgrade system software and options.
•Restart the system.
The following sections describe each platform function in more detail.
Browser Requirements
You can access Cisco CallManager Administration, Cisco CallManager Serviceability, and Cisco IPT Administration by using the following browsers:
•Microsoft Internet Explorer version 6.0 or later
•Netscape Navigator version 7.1 or later
Note Cisco does not support or test other browsers, such as Mozilla Firefox.
Platform Status and Configuration
From the Show menu, you can check the status of various platform components, including:
•Cluster and nodes
•Hardware
•Network
•System
•Installed software and options
Settings
From the Settings menu, you can view and update the following platform settings:
•Ethernet—Updates the IP addresses and Dynamic Host Configuration Protocol (DHCP) settings that were entered when the application was installed.
•NTP Server settings—Configures the IP addresses of an external NTP server; add or delete an NTP server.
•SMTP settings—Configures the SMTP host that the platform will use for sending e-mail notifications.
Restart Options
From the Restart menu, you can choose from the following options for restarting or shutting down the system:
•Switch Versions—Switches the active and inactive disk partitions and restarts the system. You normally choose this option after the inactive partition has been updated and you want to start running a newer software version.
•Current Version—Restarts the system without switching partitions.
•Shutdown System—Stops all running software and shuts down the server.
Security Configuration
The platform security options enable you to manage security certificates and Secure Internet Protocol (IPSec). From the Security menu, you can choose the following security options:
•Certificate Management—Manages certificates, Certificate Trust Lists (CTL), and Certificate Signing Requests (CSR). You can display, upload, download, delete, and regenerate certificates. Through Certificate Management, you can also monitor the expiration dates of the certificates on the server.
•IPSEC Management—Displays or updates existing IPSEC policies; sets up new IPSEC policies and associations.
Software Upgrades
The software upgrade options enable you to upgrade the software version that is running on the platform or to install specific software options, including Cisco IP Telephony Locale Installers, dial plans, and TFTP server files.
From the Install/Upgrade menu option, you can upgrade system software from either a local disc or a remote server. The upgraded software gets installed on the inactive partition, and you can then restart the system and switch partitions, so the system starts running on the newer software version.
Note For Cisco CallManager 5.0, you must do all software installations and upgrades by using the Software Upgrades menu options. The system can upload and process only software that Cisco Systems approved. You cannot install or use third-party or Windows-based software applications that you may have been using with a previous version of Cisco CallManager with Cisco CallManager 5.0.
Services
The application provides the following platform utilities:
•Ping—Checks connectivity with other network devices.
•Remote Support—Sets up an account that Cisco support personnel can use to access the system. This account automatically expires after the number of days that you specify.
Command Line Interface
The command line interface, which you can access from the console or through a secure shell connection to the server, provides a subset of the platform functionality that is available through the platform user interface. Keep in mind that the command line interface is designed for system emergencies and not as a replacement for the user interface.
Where to Find More Information
•Cisco IP Telephony Platform Administration Guide
Cisco CallManager Administration
The Cisco CallManager 5.0 administration enhancements are described in the following sections:
•General Administration Enhancements
•Navigating to IP Telephony Applications Within Cisco CallManager
•Localizing Cisco CallManager Administration
•Configuring Servers
•Publisher and Subscriber Name Changes
•Media Resources
•Migration Tips
•General Changes Made to Multiple Windows
•Line and Phone Configuration Improvements
•System Menu Changes
•Call Routing Menu Changes (formerly Route Plan Menu)
•Media Resources Menu
•Voice Mail Menu
•Device Menu Changes
•Application Menu Changes
•User Management Menu
•Bulk Administration Menu
•Service Parameter Changes
•Where to Find More Information
General Administration Enhancements
Cisco CallManager Administration Release 5.0 supports JSPs, STRUTS framework, and Java. The following requirements apply to Cisco CallManager Administration:
•Tomcat 5.0.2
•Microsoft Internet Explorer (IE) 6.0 or higher
•Netscape 7.1 or higher
Note This release does not support Microsoft IE 5.5 and Netscape 7.0.
Navigating to IP Telephony Applications Within Cisco CallManager
Cisco CallManager Administration includes a navigation bar in the upper, right corner of the window that takes the administrator to the following Cisco IP Telephony applications:
•Cisco CallManager Administration
•Cisco CallManager Serviceability
•Disaster Recovery System
•Platform Administration
Note The Bulk Administration Tool (BAT) appears as a menu item on the Cisco CallManager Administration menu.
Localizing Cisco CallManager Administration
Cisco CallManager Release 5.0 incorporates the following localization capabilities:
•End User Configuration windows get localized. Other configuration windows that share the End User Configuration get localized.
•To see the localization, set the browser to the language that is required. If that language locale is loaded, the configuration windows will be localized.
Configuring Servers
Because of security requirements, you cannot add, copy, or delete the following types of server configurations:
•Cisco CallManager
•Music on Hold Server
•Annunciator
These servers automatically get created at Cisco CallManager installation.
Publisher and Subscriber Name Changes
Cisco CallManager Release 5.0 software and documentation use the following names of the publisher and subscribers interchangeably:
•Publisher specifies the first node
•Subscriber specifies the subsequent node
Media Resources
You cannot add, copy, reset, or delete the following types of devices to media resources:
•Media Termination Point—You cannot add or delete the Cisco Media Termination Point software.
•Conference Bridge—You cannot add or delete the Cisco Conference Bridge Software.
These entries automatically generate when a new server is added by using the Server Configuration window, and they get deleted when the server is deleted by using the Server Configuration window.
The following entry and server names automatically generate:
•Cisco CallManager—CM_<server name>
•Music On Hod Server—MOH_<count>
•Annunciator—ANN_<count>
•Media Termination Point Software—MTP_<count>
•Conference Bridge Software—CFB_<count>
where:
<count> specifies the number of entries for that device in the database.
Migration Tips
The following check boxes in Cisco CallManager Administration get migrated to user groups when you upgrade from Release 4.1 or 4.0 to Release 5.0.
Check Box Name in Releases Before 5.0
|
Functionality Migrated to This User Group
|
Enable Computer Telephony Integration (CTI) Application Use
|
Standard CTI Enabled
|
Enable CTI Super Provider
|
Standard CTI Allow Control of All Devices
|
Enable Calling Party Number Modification
|
Standard CTI Allow Calling Number Modification
|
Call Park Retrieval Allowed
|
Standard CTI Allow Call Park Monitoring
|
General Changes Made to Multiple Windows
You can find the following changes on multiple Cisco CallManager Administration windows:
•Search Within Results—Found on the Find/List windows, this check box performs a search within a search result. When the check box is checked, and the administrator clicks the Find button, the find request searches the records within the results that were returned from the previous query. When the administrator no longer wants to search within the results, uncheck the check box, and the next query will search as a new search.
•"i" button help changes—the question mark (?) icon replaces the "i" button on various Cisco CallManager Administration windows. The help information has not changed and still displays in a separate window.
Line and Phone Configuration Improvements
Cisco CallManager Administration includes the following usability enhancements to the Phone and Directory Number Configuration windows:
•Search Within Results (see the "General Changes Made to Multiple Windows" section)
•Copy with Lines
•Line improvements
•User/Phone Add
Copy With Lines
Administrators use this feature from the Find and List Phones window. If you check the phone and click the Copy w/Lines icon, the system copies all configured directory numbers, speed dials, Busy Lamp Field (BLF), speed dials, and service URLs, along with regularly copied items (for example, softkey template). The lines that get copied become shared lines between the original phone and the new phone.
Line Improvements
In addition to configured directory numbers, administrators can view additional settings such as speed dials, service URLs, and abbreviated dialing numbers on the Phone Configuration window. All this information displays in the Association Information pane. The administrator makes changes by clicking the link for the directory number (DN), for example.
The Unassigned Associated Items pane tracks the unassigned but associated DNs, speed dials, BLF speed dials, and service URLs.
The Modify Button Items button allows the administrator to configure, or reorder, the phone buttons without going to the Phone Button Template Configuration window. Administrators can move buttons to the Associated Items, Unassociated Items, and Disassociated Items boxes. When saved, these individual phone button templates display on the Find and List Phone Button Template window.
User/Phone Add
The User/Phone Add Configuration window combines the necessary steps to configure a new end user with a new phone. The window also allows association of the new end user and new phone with a new or existing DN. Access this window from the User Management menu.
Addition does not succeed if you try to use an existing end user or an existing phone in this window. After you add the new end user and new phone, you can continue to configure the new end user in the End User Configuration window, and you can configure more details about the phone in the Phone Configuration window and about the DN in the Directory Number Configuration window.
System Menu Changes
The following changes occurred in the System menu:
•Cisco CallManager—You no longer can add or delete a Cisco CallManager server. New fields for SIP phones.
•Phone NTP Reference (new)
•Date/Time Group—New list box to add Phone NTP References.
•Presence Group (new)
•Region—The audio codec and video call bandwidth support two new options: Keep Current Setting and Use System Default.
•Dynamic Host Configuration Protocol (DHCP) (new)
–DHCP Server
–DHCP Subnet
•Lightweight Directory Access Protocol (LDAP) (new)
–LDAP System
–LDAP Directory
–LDAP Authentication
•Location—New fields for RSVP settings.
•Survivable Remote Site Telephony (SRST)—New fields for SIP settings.
•Multilevel Precedence and Preemption (MLPP) Domain (new)
•Service Parameters (moved from Services menu). See the "Service Enhancements" section for more information.
•Security Profile (new)
–SIP Phone Security Profile
–SIP Trunk Security Profile
–SCCP Phone Security Profile
•Application Server (new)
–Application Server Type—Cisco Unity Voice Mail 4.x and Cisco Unity Connection 2.x
•Licensing (new)
–License Unit Report
–License Unit Calculator
–License File Upload
Call Routing Menu Changes (formerly Route Plan Menu)
The following changes occurred in the Call Routing menu:
•Dial Rules
–Application Dial Rules
–Directory Lookup Dial Rules (new)
–SIP Dial Rules (new)
•SIP Route Pattern (new)
•Client Matter Codes (moved from Feature > Client Matter Codes)
•Forced Authorization Code (moved from Feature > Forced Authorization Code)
•Call Park (moved from Feature > Call Park)
•Call Pickup Group (moved from Feature > Call Pickup)
•Directory Number (moved from Device > Phone > Add a New Phone)
–Can add a range of DNs
–Partition is now called Route Partition
–ASCII Alerting Name
–Associated Devices lists all devices that use this DN (shared line)
–Presence Group
–Secondary Calling Search Space for Call Forward All
–Forward on CTI Failure
–Related Links drop-down list box includes Create Cisco Unity Voice Mailbox
Note The Phone Directory Number Configuration window includes some DN settings; for example, Call Waiting and Ring Settings.
•Meet-Me Number/Pattern (moved from Feature > Meet-Me Number Pattern)
•Dial Plan Installer (new)
Media Resources Menu
Media Resources designates a new Cisco CallManager Administration menu item and combines the menu items that were previously under Service > Media Resource.
Voice Mail Menu
Voice Mail designates a new Cisco CallManager Administration menu item and combines the menu items that were previously under Feature > Voice Mail.
Device Menu Changes
The following changes occurred in the Device menu:
•Add a New Device got removed from the Device menu
•Trunk
–SIP WSM Connection will be used for a future product.
–SIP Trunk contains new fields.
•Gateway
–AS-2, AS-4, AS-8 no longer get supported.
–IAD 2420 no longer gets supported.
–Cisco 1880 gets supported.
•Phone
–Additional search options on the Find/List Phones window
–Removal of Allow Wildcards check box on Find and List Phone window
–Copy with Lines
–Additional Phone Models available
–SCCP and SIP protocol options
–Common Phone Profile
–Protocol Specific Information—Packet Capture Mode, Packet Capture Duration, Presence Group, SCCP or SIP Phone Security Profile, SUBSCRIBE Calling Search Space, Unattended Port, Require DTMF, RFC2833 Disabled, SIP Dial Rules, MTP Preferred Originating Codec, Rerouting Calling Search Space, SIP Profile, Digest User, Require DTMF Reception, Media Termination Point Required
–Changes to Certification Authority Proxy Function (CAPF)
–Secure Shell Information
–Association Information—Takes you to Directory Number Configuration window. Shared lines no longer display in red text; shared line information gets displayed in the Device Information area in the Update Shared Device Settings.
For more information about the changes that are on the Phone and Directory Number Configuration windows, see the "Line and Phone Configuration Improvements" section.
•Device > Device Settings
–Device Defaults (moved from System menu)
–Phone Services (moved from Feature menu)
–SIP Profile (new)
–Common Phone Profile (new)
–CAPF Report (removed)
Application Menu Changes
The following changes apply in the Application menu:
•Cisco IPMA Configuration Wizard (moved from Service menu)
•Cisco CM Attendant Console (moved from Service menu)
–Pilot Point—New fields: Location, Media Resource Group, Network Hold MOH Audio Source, and User Hold MOH Audio Source, Queuing Enable check box, Queue Size, and Queue Hold Time. Removed fields: Partition, Calling Search Space, Pilot Number (DirN)
–Cisco CM Attendant Console User (no change)
–Cisco CM Attendant Console User File Upload (new)
–Hunt Group (removed)
–Cisco CM Attendant Console Server (removed)
•Plugins (formerly Install Plugins)
•Update Plugin URL (removed)
•Cisco CallManager Serviceability (moved to Navigation bar; accessed by Go drop-down box)
•Bulk Administration Tool (BAT) (moved to Bulk Administration menu)
User Management Menu
User Management designates a new Cisco CallManager Administration menu item and combines the menu items that were previously under User.
•Application User (new)—The Related Links drop-down list box includes a link for User Privilege Report
•End User (formerly under User > Add a New User)
–The Related Links drop-down list box includes new links for IPMA Manager, IPMA Assistant, and User Privilege Report
–Application Profiles got removed, and devices and extension mobility get associated by using list boxes.
–Devices get associated by clicking on the Device Association button. Displaying all available devices changes from clicking the Select Device button to clicking Find from the User Device Association window.
–Extension Mobility provides several configuration options: profiles, presence group, SUBSCRIBE calling search space, and Allow Control of Device from CTI check box.
–Certificate Authority Proxy Function (CAPF) Information
–Permissions Information—Used for Roles and Groups
•Role (performs similar function as User > Access Rights)
•User Group (performs similar function as User > Access Rights > User Group)
–The Related Links drop-down list box includes links for Assign Role to User Group and Roles.
•User/Phone Add (new)
•Application User CAPF Profile (new)
•End User CAPF Profile (new)
•SIP Realm (new)
Bulk Administration Menu
Bulk Administration designates a new Cisco CallManager Administration menu item. Previously, BAT, which was installed as a plug-in, ran as a separate application within Cisco CallManager. Bulk Administration contains the following menu items:
•Upload/Download Files
•Phones
•Users
•Phones & Users
•Manager/Assistants
•User Device Profiles
•Gateways
•Forced Authorization Codes
•Client Matter Codes
•Call Pickup Group
•Job Scheduler
•Tool for Auto-Registered Phone Support (TAPS)
For more information about the BAT application, see Bulk Administration Tool Features.
Service Parameter Changes
Cisco CallManager 5.0 supports the following Bulk Administration related service parameter changes
•Default MTP Telephony Event Payload Type—This release removes this service parameter and adds it as a configuration option for SIP devices in the SIP Profile Configuration window. The default value equals 101 with range from 96 to 127.
•Max Simultaneous Cisco CallManager Initializations (new)—Use this parameter to limit the number of Cisco CallManager services that can initialize at the same time.
•Restart Cisco CallManager on Initialization Exception (new)—This parameter determines whether the Cisco CallManager service restarts if an error is encountered during initialization.
Cisco Messaging Interface (CMI)
Primary and backup CMI services—The Primary CMI gets specified in the CMI clusterwide service parameter, CallManager Name. The backup CMI service gets specified in the CMI clusterwide service parameter, Backup CallManager Name. Note that only the active CMI service handles the communication between CMI and Cisco CallManager as well as CMI the voice-messaging system.
Release 5.0 differs from Release 3.x and 4.x wherein the previous releases, the CMI residing on the node with the higher IP address is the Primary CMI.
Data Cable—In windows, CMI uses serial ports COM1 or COM2 for SMDI messages. The default value is COM1. In release 5.0, CMI uses the USB port that is connected through the USB-Serial adaptor for SMDI messages. The port name is USB0, which is configured by default.
GUI changes—The following parameters are now clusterwide:
•CallManager Name
•Backup CallManager Name
•Voice Mail DN
•Voice Mail Partition
•Alternate DN (new)
•Alternate DN Partition (new)
Where to Find More Information
•Presence Group Configuration, Cisco CallManager Administration Guide
•Presence, Cisco CallManager Features and Services Guide
•DHCP Server Configuration, Cisco CallManager Administration Guide
•DHCP Subnet Configuration, Cisco CallManager Administration Guide
•LDAP System Configuration, Cisco CallManager Administration Guide
•LDAP Directory Configuration, Cisco CallManager Administration Guide
•LDAP Authentication Configuration, Cisco CallManager Administration Guide
•Understanding the Directory, Cisco CallManager System Guide
•Application Users and End Users, Cisco CallManager System Guide
•MLPP Domain Configuration, Cisco CallManager Administration Guide
•Phone NTP Reference Configuration, Cisco CallManager Administration Guide
•SIP Phone Security Profile Configuration, Cisco CallManager Administration Guide
•SIP Trunk Security Profile Configuration, Cisco CallManager Administration Guide
•SCCP Phone Security Profile Configuration, Cisco CallManager Administration Guide
•Application Server Configuration, Cisco CallManager Administration Guide
•License Unit Report Configuration, Cisco CallManager Administration Guide
•License Unit Calculator Configuration, Cisco CallManager Administration Guide
•License File Upload Configuration, Cisco CallManager Administration Guide
•Directory Lookup Dial Rules Configuration, Cisco CallManager Administration Guide
•SIP Dial Rules Configuration, Cisco CallManager Administration Guide
•Dial Rules Overview, Cisco CallManager System Guide
•SIP Route Pattern Configuration, Cisco CallManager Administration Guide
•Directory Number Configuration, Cisco CallManager Administration Guide
•Directory Numbers, Cisco CallManager System Guide
•Installing Dial Plans Configuration, Cisco CallManager Administration Guide
•SIP Profile Configuration, Cisco CallManager Administration Guide
•Common Phone Profile Configuration, Cisco CallManager Administration Guide
•Application User Configuration, Cisco CallManager Administration Guide
•End User Configuration, Cisco CallManager Administration Guide
•Role Configuration, Cisco CallManager Administration Guide
•Roles and User Groups, Cisco CallManager System Guide
•User Group Configuration, Cisco CallManager Administration Guide
•User/Phone Add Configuration, Cisco CallManager Administration Guide
•Application User CAPF Profile Configuration, Cisco CallManager Administration Guide
•End User CAPF Profile Configuration, Cisco CallManager Administration Guide
•SIP Realm Configuration, Cisco CallManager Administration Guide
•Understanding Session Initiation Protocol, Cisco CallManager System Guide
•Understanding Cisco CallManager Trunk Types, Cisco CallManager System Guide
•Cisco IP Phones, Cisco CallManager System Guide
•Understanding Video Telephony, Cisco CallManager System Guide
•Cisco CallManager Bulk Administration Tool, Cisco CallManager Administration Guide
•Cisco CallManager Bulk Administration Guide
Cisco CallManager Features
The Cisco CallManager 5.0 feature enhancements are described in the following sections:
•Call Forwarding Enhancements
•Call Park
•Call Pickup Group
•CTI and CTI Super Provider
•Dynamic Host Control Protocol (DHCP)
•International Dial Plans
•LDAP Directory Enhancements
•Licensing
•Personal Directory Enhancements
•Phone NTP References for SIP Phones
•Presence
•Roles and User Groups
•RSVP
•Service Enhancements
•SIP Line Side (Endpoints) Support
•SIP Route Pattern
•SIP Third-Party Phones
•SIP Trunk Enhancements
•URL Dialing
•Video Telephony Enhancements
•Voice Quality Metrics
Call Forwarding Enhancements
The Call Forward All (CFA) enhancement introduces a secondary Calling Search Space (CSS) for the Call Forward All field. The secondary CSS for CFA combines with the existing CSS for CFA to allow the support of alternate CSS system configuration.
When CFA is activated, only the primary and secondary CSS for CFA gets used to validate the CFA destination and redirect the call to the CFA destination. If these fields are empty, then null CSS gets used. The combination of the line CSS and device CSS no longer gets used when CSS for CFA is None. Only CSS fields that are configured in the primary CSS for CFA and the secondary CSS for CFA fields get used.
For more information, refer to Cisco CallManager Features and Services Guide 5.0.
Cisco CallManager Administration Configuration Tips
•You must configure either primary Forward All Calling Search Space or Secondary Forward All Calling Search Space or both for Call Forward All to work properly. The system uses these concatenated fields (Primary CFA CSS + Secondary CFA CSS) to validate the CFA destination and forward the call to the CFA destination.
Note If the system is using partitions and calling search spaces, Cisco recommends that the other call forward calling search spaces are configured as well. When a call is forwarded or redirected to the call forward destination, the configured call forward calling search space gets used to forward the call. If the forward calling search space is None, the forward operation may fail if the system is using partitions and calling search spaces. For example, if the Forward Busy Destination is configured, the Forward Busy Calling Search Space should also be configured. If the Forward Busy Calling Search Space is not configured and the Forward Busy destination is in a partition, the forward operation will fail.
•When you forward calls by using the Cisco IP Phone User Options windows or the CFwdAll softkey on the phone, the automatic combination of the line CSS and device CSS does not get used. Only the configured Primary CFA CSS and Secondary CFA CSS gets used. If both of these fields are <None>, the combination results in two null partitions, which will cause the operation to fail.
•If you want to restrict users from forwarding calls on their phones, you must choose a restrictive calling search space from the Forward All Calling Search Space field.
•Migration automatically configures either one or both of these CSS for CFA fields based on the previous data.
•If CFA is activated from the phone, the CFA destination gets validated by using the CSS for CFA, and secondary CSS for CFA, and CFA destination gets written to the database.
•In previous releases, if the CSS for CFA is empty, the CFA destination got validated against the combination of the line CSS and device CSS of the phone. In Release 5.0, during CFA activation, the CFA destination always gets validated against the CSS for CFA and the secondary CSS for CFA.
GUI Changes
This release adds new drop-down list box to the Cisco CallManager Administration Directory Number Configuration window. This field provides a secondary CSS for CFA. The combination of the CSS for CFA and
