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
CSCtj61834 MLPP Default Domain Name Displays MLPP ID Value
Caveats
Resolved Caveats
Using Bug Toolkit
Saving Bug Toolkit Queries
Open Caveats
Troubleshooting
Documentation Updates
Errors
Description of the Reset Button
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
Setting the Cisco Unified Communications Manager MTU Size
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
Time-of-Day Routing Chapter Omits Information About Defined Time Periods
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 October 3, 2011
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 secondary CSS for CFA gets used to activate and redirect a call to the CFA destination.
BAT Considerations
This release adds a new drop-down list box to Bulk Administration call forwarding and call pickup setting in Directory Number configuration window. This field provides a secondary CSS for CFA.
Where to Find More Information
•Directory Number Configuration, Cisco CallManager Administration Guide
•Cisco IP Phones, Cisco CallManager System Guide
Call Park
Call Park provides the same functionality as in previous Cisco CallManager releases.
Cisco CallManager Administration Configuration Tips
Call Park now gets configured under the Call Routing menu. Additionally, this release removes the Allow Call Park Retrieval check box that was on the End User Configuration window and creates a new user group for Call Park users.
GUI Changes
•Choose Call Routing > Call Park.
•Add the users who will need access to Call Park to the Standard CTI Allow Call Park Monitoring user group. Choose User Management > User Group. Consider this a requirement for Attendant Console users.
Where to Find More Information
•Call Park, Cisco CallManager Features and Services Guide
•User Group Configuration, Cisco CallManager Administration Guide
•Attendant Console Configuration, Cisco CallManager Features and Services Guide
Call Pickup Group
Call Pickup Group provides the same functionality as Cisco CallManager Release 4.1(3).
Cisco CallManager Administration Configuration Tips
Call Pickup Group, which is now configured under the Call Routing menu, gets referred to as Call Pickup Group.
GUI Changes
•Choose Call Routing > Call Pickup Group.
•In Call Pickup Group Information section:
–Call Pickup Group Name (new field)
–Call Pickup Group Number (changed: formerly Call Pickup Number)
•In Associated Call Pickup Group Information, Find Pickup Numbers by Numbers/Partition section:
–This area allows you to search for associated call pickup groups by numbers and/or partitions of those groups. You can also add them to a list of associated call pickup groups.
•In the Current Associated Call Pickup Groups section:
–You can change the order of the associated call pickup groups or remove them.
BAT Considerations
Bulk Administration provides Insert Call Pickup Groups and Delete Call Pickup Groups.
Where to Find More Information
•Call Pickup Group, Cisco CallManager Features and Services Guide
CTI and CTI Super Provider
The way devices and users get assigned to CTI applications changed. Administrators must add end users and application users to certain CTI user groups.
CTI supports Cisco SIP IP Phones (models 7911, 7941, 7961, 7970, and 7971) from the CTI interfaces JTAPI and TAPI, with some limited functionality. CTI applications control and monitor SIP phones in the same manner as CTI-controlled/monitored SCCP phones.
Cisco CallManager Administration Configuration Tips
Previous to Cisco CallManager Release 5.0, two check boxes appeared on the User Configuration window. The check box, Enable CTI Application Use, provided users with access to CTI applications. The check box, Enable CTI Super Provider, provided CTI applications super provider capabilities to control all CTI-controllable devices.
Release 5.0 removed the check boxes and replaced them with user groups.
Administrators must use the following steps to correctly assign users and devices access to CTI applications:
1. Add and configure an IP phone, CTI route points, or ports for each CTI application.
2. Configure the directory number for the CTI device.
3. Configure the end users and application users that will use CTI applications. Add the device that is used for CTI applications (for example, IP phone, CTI port) to the Controlled Devices list that is on the End User Configuration window.
4. Add the end users and application users to the Standard CTI Enabled user group.
Note All CTI users need to be in the Standard CTI Enabled user group, but they may also be in multiple CTI user groups.
5. If the application needs to control and monitor any CTI-controllable device, add that application user to the Standard CTI Allow Control of All Devices user group.
GUI Changes
•The Enable CTI Application Use check box no longer appears on the User Configuration window.
•The Enable CTI Super Provider check box no longer appears on the User Configuration window.
•Use the Allow Control of Devices to CTI check box on the End User Configuration window for extension mobility. Check this check box to allow CTI to control devices that this end user owns. If the associated directory number specifies a shared line, ensure the check box is enabled as long as at least one associated device specifies a combination of device type and protocol that CTI supports.
•End users and application users get access to CTI applications by being assigned to a CTI user group (User Management > User Group). The following CTI user groups exist in Release 5.0:
–Standard CTI Allow Calling Number Modification—This user group allows an application to modify the calling party number in supported CTI applications.
–Standard CTI Allow Control of All Devices—This user group allows an application to control or monitor any CTI-controllable device in the system (referred to as CTI super provider application).
–Standard CTI Allow Reception of SRTP Key Material—This user group allows an application to receive information that is necessary to decrypt encrypted media streams. This group typically gets used for recording and monitoring purposes.
–Standard CTI Enabled—This user group, which is required for all CTI applications, allows an application to connect to Cisco CallManager to access CTI functionality.
–Standard CTI Secure Connection—Inclusion into this group will require that the application have a secure (TLS) CTI connection to Cisco CallManager if the Cisco CallManager cluster security is enabled.
–Standard CTI Allow Call Park Monitoring—This user group allows an application to receive notification when calls are parked/unparked to all Call Park directory numbers.
Note The CTI application must support the specified user group to which it gets assigned. Refer to the appropriate application documentation for more information.
•CTI devices (such as IP phones and CTI ports) must be associated with the user (User Management > End User).
CTI Considerations
See the "Migration Tips" section for information about CTI check boxes and user groups.
Where to Find More Information
•Migration Tips
•Computer Telephony Integration, Cisco CallManager System Guide
•Configuring Cisco IP Phones, Cisco CallManager Administration Guide
•CTI Route Point Configuration, Cisco CallManager Administration Guide
•Application User Configuration, Cisco CallManager Administration Guide
•End User Configuration, Cisco CallManager Administration Guide
•User Group Configuration, Cisco CallManager Administration Guide
Dynamic Host Control Protocol (DHCP)
Dynamic Host Configuration Protocol (DHCP) server enables Cisco IP phones, connected to either the customer's data or voice Ethernet network, to dynamically obtain its IP address and configuration information. It uses Domain Name System (DNS) to resolve host names both within and outside the cluster.
You can configure one DHCP server for each node of each server, and multiple subnets can be configured for each server.
Cisco CallManager Administration Configuration Tips
Because no migration is provided from Window 2000 based DHCP configuration to the DHCP configuration, the administrator needs to reconfigure the DHCP servers.
GUI Changes
Use the following new menu options in Cisco CallManager Administration to configure DHCP servers and the DHCP subnets.
•System > DHCP Server
•System > DHCP Subnet
Serviceability Considerations
The following enhancements exist in Cisco CallManager Serviceability for DHCP:
•Serviceability provides an option to enable the DHCP functionality and to activate the DHCP Monitor Service on the node where the DHCP is enabled (Serviceability > Tools > Service Activation).
•Serviceability provides an option to start and stop DHCP Monitor Service (Serviceability > Tools > Control Center - Feature Services).
•Serviceability provides an option to change trace levels for DHCP monitor process (Serviceability > Trace > Configuration).
•Serviceability provides an option to change alarm event level for DHCP (Serviceability > Alarm > Configuration).
•Choose Serviceability > Alarm > Definitions to view new alarms that are defined for DHCP. This release adds two new alarms for DHCP:
–CiscoDhcpdFailure
–CiscoDhcpdRestarted
Where to Find More Information
•DHCP Server Configuration, Cisco CallManager Administration Guide
•DHCP Subnet Configuration, Cisco CallManager Administration Guide
•Dynamic Host Configuration Protocol, Cisco CallManager System Guide
International Dial Plans
Cisco CallManager supports non-NANP. The following sections provide information on the installation and changes made to dial plans in release 5.0.
Cisco CallManager Administration Configuration Tips
Use the Dial Plan Installer menu item to install dial plans that are available on Cisco CallManager publisher server (Call Routing > Dial Plan Installer). For more details, see Cisco CallManager Administration Guide and Cisco CallManager International Dial Plan Deployment Guide.
Installation Considerations
Before you install a dial plan on the server, you should download the equivalent dial plan COP (Cisco Option Package) file to the Cisco CallManager server.
You can find COP files for all the available dial plans that you can download, install, and integrate with Cisco CallManager systems at the following URL:
http://www.cisco.com/pcgi-bin/tablebuild.pl/IDP
For details on installing a COP file, see Cisco CallManager International Dial Plans Deployment Guide
GUI Changes
This release adds a new menu item, Dial Plan Installer (Call Routing > Dial Plan Installer), to the Call Routing menu in Cisco CallManager Administration.
Serviceability Considerations
•You must restart Cisco CallManager service every time the dial plans are installed, upgraded, or uninstalled.
•Maximum length: 255. IDP uses Cisco RTMT Web Service for writing the trace files.
Where to Find More Information
•Installing Dial Plans, Cisco CallManager Administration Guide
•Cisco CallManager International Dial Plans Deployment Guide
LDAP Directory Enhancements
The Lightweight Directory Access Protocol (LDAP) provides applications with a standard method for accessing and potentially modifying the information that is stored in the directory. This capability enables companies to centralize all user information in a single repository, available to several applications, with a reduction in maintenance costs through the ease of adds, moves, and changes.
Cisco CallManager Administration documentation covers the main principles for synchronizing Cisco CallManager with a corporate LDAP directory. The documentation also discusses the administrator's choice not to synchronize with a corporate LDAP directory and the consequences of that choice of configuration. The documentation also summarizes considerations for providing Cisco IP Telephony endpoints, such as Cisco IP Phones and Cisco IP SoftPhone, with access to a corporate LDAP directory.
The following list summarizes the changes in directory functionality from previous releases of Cisco CallManager:
•The directory component has been decoupled from Cisco CallManager to ensure high Cisco CallManager availability independent of the corporate directory.
•Cisco CallManager and related applications store all application data in the local database instead of in an embedded directory. The embedded directory gets removed, and Cisco CallManager supports synchronization with the customer directory.
Cisco CallManager Administration Configuration Tips
The following sections discuss the changes to Cisco CallManager Administration that relate to changes in directory functionality.
You can only configure new end users if the synchronization from the LDAP server is disabled. To disable synchronization, choose the System > LDAP > LDAP System menu option and ensure that the Enable Synchronization from LDAP Server check box is unchecked.
The Cisco CallManager Data Migration Assistant (DMA) provides conversion of Cisco CallManager 4.x data to a format that is compatible with Cisco CallManager 5.0. For details on obtaining, installing, and using DMA, refer to the Cisco CallManager Data Migration Assistant 1.0 User Guide.
GUI Changes
This release eliminates the following menu options from previous releases of Cisco CallManager Administration:
•User > Add a New User
•User > Global Directory
The following new menu options in this release of Cisco CallManager Administration relate to configuration of directory information:
•System > LDAP > LDAP System
•System > LDAP > LDAP Directory
•System > LDAP > LDAP Authentication
•User Management > Application User
•User Management > End User
The menu options allow the following basic functionality:
•The System > LDAP > LDAP System menu option causes the LDAP System Configuration window to display. Use this window to enable or disable synchronization from the LDAP server and to configure the LDAP server type and the LDAP attribute for user ID.
•The System > LDAP > LDAP Directory menu option causes the Find and List LDAP Directories window to display. Use this window configure various attributes of LDAP directories.
•The System > LDAP > LDAP Authentication menu option causes the LDAP Authentication window to display. Use this window to enable or disable LDAP authentication for end users, as well as to provide LDAP server information.
•The User Management > Application User menu option causes the Find and List Application Users window to display. Use this window to find application users or click Add New to add a new application user. On the Application User Configuration window, use the User Privilege Report link from the Related Links drop-down list box at right to view the user group, role, and resources that are associated with a specified application user.
•The User Management > End User menu option causes the window to display. Use this window to find an end user or click Add New to add a new end user. On the End User Configuration window, use the User Privilege Report link from the Related Links drop-down list box at right to view the user group, role, and resources that are associated with a specified end user.
Service Parameter Changes
Changes to directory functionality affect the service parameters that are associated with the DirSync service.
Where to Find More Information
•LDAP System Configuration, Cisco CallManager Administration Guide
•LDAP Directory Configuration, Cisco CallManager Administration Guide
•LDAP Authentication Configuration, Cisco CallManager Administration Guide
•Application User Configuration, Cisco CallManager Administration Guide
•End User Configuration, Cisco CallManager Administration Guide
•Understanding the Directory, Cisco CallManager System Guide
•Application Users and End Users, Cisco CallManager System Guide
•Cisco CallManager Data Migration Assistant 1.0 User Guide
Licensing
Licensing in Cisco CallManager Administration accurately tracks the number of devices that a customer has connected to Cisco CallManager, including third-party SIP phones, and compares it with the number of unit licenses that have been purchased. License Configuration manages licenses for phones and nodes (Cisco CallManager servers), it provides a calculator for determining how many and what types of devices are configured, and it includes a mechanism for uploading licenses files from a client PC.
Cisco CallManager Administration Configuration Tips
Licensing is a new system configuration option in Cisco CallManager Administration.
GUI Changes
The menu options in Cisco CallManager Administration help determine the current license capacity and provide a tool to calculate the number of licenses that are required.
The following three menu options exist in Cisco CallManager Administration:
•System > Licensing > License Unit Report
•System > Licensing > License Unit Calculator
•System > Licensing > License File Upload
Serviceability Considerations
The following enhancements exist in Cisco CallManager Serviceability for Licensing:
•Serviceability provides an option to start and stop the Cisco License Manager service (Serviceability > Tools > Control Center - Network Services).
•Serviceability provides an option to change trace levels for licensing (Serviceability > Trace Configuration).
•Serviceability provides an option to change alarm event level for licensing (Serviceability > Alarm Configuration).
•Choose Serviceability > Alarm > Definitions to view new alarms that are defined for licensing. Release 5.0 adds these new alarms in the Java Applications catalog for licensing:
–CiscoLicenseManagerDown
–CiscoLicenseOverDraft
–CiscoLicenseRequestFailed
–CiscoLicenseDataStoreError
–CiscoLicenseInternalError
–CiscoLicenseFileError
Security Considerations
Because the database tables that contain licensing-related data are secured, you cannot modify these tables by using AXL or any other SQL with regular user privileges.
Where to Find More Information
•Licensing, Cisco CallManager System Guide
•License Unit Report, Cisco CallManager Administration Guide
•License Unit Calculator, Cisco CallManager Administration Guide
•License File Upload, Cisco CallManager Administration Guide
Personal Directory Enhancements
Unlike previous releases of Cisco CallManager, the Personal Directory feature in Cisco CallManager Release 5.0(1) does not require special administrative configuration, and the end user does not need to subscribe to this service.
Cisco IP Phones (SCCP) that support Personal Directory:
•Cisco IP Phone 7970G/7971G-GE
•Cisco IP Phone 7961G/7961G-GE and 7941G/7941G-GE
•Cisco IP Phone 7960G/7961G and 7940G
•Cisco IP Phone 7911G
•Cisco IP Phone 7905G and 7912G
Cisco IP Phones (SIP) that support Personal Directory:
•Cisco IP Phone 7970G/7971G-GE
•Cisco IP Phone 7961G/7961G-GE and 7941G/7941G-GE
•Cisco IP Phone 7911G
Cisco CallManager Administration Configuration Tips
The system administrator must activate the Personal Directory feature in Cisco CallManager Serviceability: from the Navigation drop-down list box that is on the Cisco CallManager 5.0(1) window, choose the Serviceability option and click Go; the Serviceability Application window displays. Administrators must also download the Address Book Synchronization Tool (TABSynch) from the Cisco CallManager Plugins window and provide TABSynch to the user. After the system is configured, the system administrator provides the end users with the following information about the User Options web pages:
•The URL required to access the application:
http://server_name/CCMUser/
where server_name is the host on which the web server is installed.
GUI Changes
Administrator must download the Address Book Synchronization Tool (TABSynch) from the Cisco CallManager Plugins window (Applications > Plugin).
User Tips
Users can access Personal Directory from:
•A web browser (Cisco CallManager User Options)
•A Cisco IP Phone
•Microsoft Windows application (assuming that the administrator provided the user with the TABSynch tool)
Using Personal Directory—Personal Address Book and Fast Dials
Users can access Personal Directory:
•On the phone—Choose Directories > Personal Directory on the phone and log in with Cisco CallManager user name and PIN.
•On the Web—Log in to Cisco CallManager User Options and choose User Options > Personal Address Book or User Options > Fast Dials.
From either interface, users can choose a PAB entry from search results, then dial, edit, delete, or assign a Fast Dial code to the entry. Users can also create new entries.
Users can also choose a Fast Dial entry from search results, then dial or delete the entry. Users can also create "raw" Fast Dial entries that are not associated with PAB entries.
Using the Address Book Synchronization Tool
Users can use the Address Book Synchronization Tool (TABSynch) to synchronize their existing Microsoft Windows Address Book (if applicable) with their Personal Address Book. Users can then access entries from the Microsoft Windows Address Book from the Cisco IP Phone and Cisco CallManager User Options.
You must make the TABSynch tool available to your users if you want them to access it (see the Providing Information to Your Users Via a Website section in the phone administration guides).
Serviceability Considerations
The system administrator must start and stop the Personal Directory feature by using Cisco CallManager Serviceability.
•Choose Tools > Control Center - Network Services.
•Choose the server.
•Under CM Services, locate Cisco CallManager Personal Directory.
•From the Control Center - Network Services window, users can start and stop the Personal Directory.
Where to Find More Information
•Providing Information to Your Users Via a Website section in the phone administration guides
Phone NTP References for SIP Phones
You can configure phone Network Time Protocol (NTP) references in Cisco CallManager Administration to ensure that a Cisco SIP IP Phone gets its date and time from an NTP server.
Cisco CallManager Administration Configuration Tips
Because you can configure several phone NTP references in Cisco CallManager Administration, Cisco CallManager Administration allows you to locate specific phone NTP references; if you want to do so, you can configure the IP address of an NTP server that exists outside of the Cisco CallManager system (System > Phone NTP Reference).
After you add the phone NTP references to Cisco CallManager Administration, you must add them to a date/time group (System > Date/Time Group). In the date/time group, you prioritize the phone NTP references.
The date/time group configuration gets specified in the device pool (System > Device Pool), and the phone receives the phone NTP reference configuration from the device pool.
GUI Changes
The following new and changed windows in Cisco CallManager Administration contain NTP server-related configuration settings:
•Phone NTP Reference window (new)—Contains Name and Description settings.
•Date/Time Group window (changed)—Contains the Selected phone NTP references (in highest priority) setting.
Where to Find More Information
•Phone NTP Reference Configuration, Cisco CallManager Administration Guide
Presence
When you configure Presence in Cisco CallManager Administration, an interested party, known as a watcher, can monitor the real-time status of a directory number or SIP URI, a presence entity, from the device of the watcher.
A watcher can monitor the status of the presence entity (called presentity) with the following options:
•Busy Lamp Field (BLF)/Speed-Dial buttons
•Missed call, placed call, or received call lists in the directories window
•Shared directories, such as the corporate directory
Call lists and directories display the BLF status for existing entries. When you configure BLF/Speed-Dial buttons, the presence entity displays as a speed dial on the device of the watcher.
Note For presence-supported SIP phones, you can configure directory numbers or SIP URIs as BLF/Speed-Dial buttons. For presence-supported SCCP phones, you can only configure directory numbers as BLF/Speed Dial buttons. Configure BLF/Speed-Dial buttons for the phone, user device profile, or autogenerated device profile. The BLF value does not have to be on the cluster.
To view the status of a presence entity, watchers send presence requests to Cisco CallManager. After administrators configure presence features, real-time status icons display on the watcher device to indicate whether the presence entity is on the phone, not on the phone, status unknown, and so on.
Extension mobility users can use presence features on phones with extension mobility support.
Presence group authorization ensures that only authorized watchers can access the presence status for a destination. Because the administrator ensures that the watcher is authorized to monitor the destination when a BLF/Speed Dial is configured, presence group authorization does not apply to BLF/Speed Dials.
Note For SIP phones, presence group authorization also does not apply to any directory number or SIP URI that is configured as a BLF/Speed Dial that appears in a call list.
To allow presence requests from outside the cluster, administrators must configure the system to accept presence requests from the external trunk or application. You can assign presence groups to trunks and applications outside the cluster to invoke presence group authorization.
The SUBSCRIBE Calling Search Space determines how Cisco CallManager routes presence requests that come from the trunk or the phone. The SUBSCRIBE Calling Search Space that is associated with an end user gets used for extension mobility calls.
Cisco CallManager Administration Configuration Tips
Administrators configure the phone features that are associated with presence: BLF/Speed Dials, call lists, or both. Administrators also configure the system to accept presence requests from outside the cluster and configure presence groups and permissions to use presence group authorization.
This section lists tips that you can use when you are configuring presence groups for presence authorization.
•To allow a watcher to monitor a destination, make sure that the presence group that is applied to the watcher that is originating the request, including application users, has permission to monitor the group that is applied to the presence entity. End users for supported applications, for example, IPMA end users, also serve as watchers because the user requests status about a presence entity that is configured on the application.
•To allow Cisco CallManager to receive and route presence requests from the SIP trunk application, make sure that the Accept Presence Subscription check box is checked in the Application User window to authorize incoming SUBSCRIBE requests. If no presence group is applied to the application user, Cisco CallManager uses the presence group that is applied to the trunk.
•If you check the Accept Presence Subscription check box for an application user, but do not check the Accept Presence Subscription check box in the SIP Trunk Security Profile that is applied to the trunk, a 403 error message gets sent to the SIP user agent that is connected to the trunk.
•If you check the Accept Presence Subscription check box for an application user, but do not check the Enable Application Level Authorization check box in the SIP Trunk Security Profile that is applied to the trunk, a 403 error message gets sent to the SIP user agent that is connected to the trunk.
•If digest authentication is not configured for the SIP trunk, you can configure the trunk to accept incoming subscriptions, but application-level authorization cannot be initiated, and Cisco CallManager will accept all incoming requests before performing group authorization.
•If the SIP trunk uses digest authentication, as configured in the SIP Trunk Security Profile, incoming presence requests require authentication of the credentials from the sending device. When digest authentication is used with application-level authorization, Cisco CallManager also authenticates the credentials of the application that is sending the presence requests.
•After authorization and authentication is successful for a SIP trunk application, Cisco CallManager performs group authorization to verify the group permissions that are associated with the presence request before accepting the request.
•When an administrator decides to add or change a BLF/Speed Dial button for a SIP URI, the administrator ensures that the watcher is authorized to monitor that destination. If the system uses a SIP trunk to reach a SIP URI BLF target, the presence group that is associated with the SIP trunk applies.
•When configuring a SIP URI as BLF/Speed Dial button, make sure the routing patterns are appropriately configured. Refer to SIP Route Pattern Configuration in the Cisco CallManager Administration Guide for more information.
Cisco IP Phones (SCCP) that Support Busy Lamp Field (BLF) -Speed Dial
•Cisco IP Phone 7970G/ 7971G-GE
•Cisco IP Phone 7961G/7961G-GE and 7941G/7941G-GE
•Cisco IP Phone 7960G/7940G
•Cisco IP Phone Expansion Module 7914
Cisco IP Phones (SCCP) that Support Busy Lamp Field (BLF) -Call List
•Cisco IP Phone 7970G/7971G-GE
•Cisco IP Phone 7961G/7961G-GE and 7941G/7941G-GE
Cisco IP Phones (SIP) that Support Busy Lamp Field (BLF) -Speed Dial
•Cisco IP Phone 7970G /7971G-GE
•Cisco IP Phone 7961G/7961G-GE and 7941G/7941G-GE
Cisco IP Phones (SIP) that Support Busy Lamp Field (BLF) -Call List
•Cisco IP Phone 7970G/7971G-GE
•Cisco IP Phone 7961G/7961G-GE and 7941G/7941G-GE
GUI Changes
The following new and changed windows in Cisco CallManager Administration contain presence-related configuration settings:
•Presence Group Configuration window (new)—Contains Name, Description, Modify Relationship to Other Presence Groups, and Subscription Permission settings.
•End User Configuration window (new)—Contains the Presence Group and SUBSCRIBE Calling Search Space settings.
•Application User Configuration window (new)—Contains the Presence Group setting and Accept Presence Subscription check box.
•SIP Trunk Security Profile Configuration window (new)—Contains the Accept Presence Subscription, Enable Application-Level Authorization, and Enable Digest Authentication check boxes.
•SIP Trunk Configuration window (changed)—Contains the Presence Group and SUBSCRIBE Calling Search Space settings.
•Phone Configuration window (changed)—Contains the Presence Group and SUBSCRIBE Calling Search Space settings; contains the Add a new BLF SD link.
•Directory Number Configuration window (changed)—Contains the Presence Group setting.
•Phone Button Template Configuration window (changed)—Contains the Speed Dial BLF option in the Features drop-down list boxes.
•Device Profile Window (changed)—The autogenerated device profile contains the Presence Group and SUBSCRIBE Calling Search Space settings as well as the Add a new BLF SD link; the user device profile contains the Add a new BLF SD link.
Service and Enterprise Parameter Changes
The following new service and enterprise parameters support presence:
•BLF for Call List—This enterprise parameter specifies the default Busy Lamp Field (BLF) behavior for phones (enabled or disabled). Restart all services for the changes to take effect.
•Default Inter-Presence Group Subscription—Used with the Cisco CallManager service, this service parameter sets a system default value to allow or disallow a watcher in one presence group to request the status of a directory number or SIP URI that is assigned to another group when the Use System Default is selected in the Presence Group Configuration window.
•Presence Subscription Throttling Threshold—Used with the Cisco CallManager service, this service parameter specifies the number of external presence subscriptions that are allowed. When the number of subscriptions exceeds the value that this parameter specifies, Cisco CallManager rejects additional call list busy lamp field (BLF) subscriptions as well as additional presence subscriptions via the SIP trunk. This parameter works with the Presence Subscription Resume Threshold parameter.
•Presence Subscription Resume Threshold—Used with the Cisco CallManager service, this service parameter defines a percentage of the value that is specified in the Presence Subscription Throttling Threshold service parameter. When the number of external presence subscriptions decreases to below the percentage that this parameter specifies, Cisco CallManager ceases throttling and resumes accepting call list BLF subscriptions as well as presence subscriptions via the SIP trunk. This parameter works with the Presence Subscription Throttling Threshold parameter.
User Tips
Users can use the Busy Lamp Field (BLF) to determine the state of another phone line that is associated with a speed-dial button, call list, or directory listing on their phone,
Using BLF-Speed Dials
To see the state of a speed-dial line, users can check icons and button light behavior next to the speed-dial line:
Line is in-use.
Line is idle.
BLF indicator unavailable for this line.
Note Users of the Cisco IP Phone 7960G and the Cisco IP Phone 7940G see the appropriate icon only.
Using BLF-Call Logs
To see the state of a line that is listed in a call list or directory, users can check for the following icons:
Line is in-use.Line is idle.
BLF indicator unavailable for this line.
Serviceability Considerations
You must restart all services after you configure the BLF for Call List enterprise parameter.
BAT Considerations
You can configure BLF in the BAT phone template.
Where to Find More Information
•Presence, Cisco CallManager Features and Services Guide
Roles and User Groups
Roles and user groups replace the concept of functional groups and user groups that were found in previous versions of Cisco CallManager Administration.
The Cisco CallManager Administration application and other applications use roles and user groups to provide varying levels of privilege (access). This technique permits granting only the required privileges for a selected group of users and limits the configuration functions that users in a particular user group can perform.
Roles and user groups provide multiple levels of security to Cisco CallManager Administration and to other applications. The resources that are available to the Cisco CallManager Administration application and to other applications get grouped into roles. Each application comes with standard, predefined roles. Administrators can configure additional roles for an application. A role contains, for a particular application, the list of resources that an application comprises. For each resource that a role comprises, the administrator defines the access privilege. For each resource in the Cisco CallManager Administration application, the privileges include read and update. Other applications specify other privileges.
After configuration of roles for an application, administrators can configure user groups. User groups defines groups of users that share a common list of assigned roles. User groups comprise both application users and end users.
Updates to roles and to user groups generate audit logs of user logins and access and modifications to Cisco CallManager configuration data.
Cisco CallManager Administration Configuration Tips
This section describes the changes to Cisco CallManager Administration that allow administrators to configure roles and user groups.
Standard, predefined roles and user groups exist within Cisco CallManager Administration. Administrators cannot update these standard roles nor standard user groups. Administrators can, however, copy a standard role or standard user group and use the copy as the basis for creating a new role or new user group.
GUI Changes
Use the following Cisco CallManager Administration menu options to configure roles and user groups:
•User Management > Role—This menu option yields the Find and List Roles window. Use this window to search for existing roles or click Add New to add a new role.
•User Management > User Group—This menu option yields the Find and List User Groups window. Use this window to search for existing user groups or click Add New to add a new user group.
The User Management > Role and User Management > User Group menu options replace the following menu options that existed in previous versions of Cisco CallManager Administration:
•User > Access Rights > Functional Group
•User > Access Rights > User Group
•User > Access Rights > Assign Privileges to User Group
•User > Access Rights > Configure MLA Parameters
Enterprise Parameter Changes
Roles and user groups change the following enterprise parameters.
New Enterprise Parameters
The Effective Access Privileges For Overlapping User Groups and Roles enterprise parameter designates a new enterprise parameter under the User Management Parameters grouping.
Removed or Changed Enterprise Parameters
This release removed or changed the following enterprise parameters:
•User Group Base (removed)
•Administrative User Base (removed)
•Debug Level (removed)
•Effective Access Privileges For Overlapping User Groups (replaced) (See the New Enterprise Parameters for the replacement enterprise parameter.)
•Effective Access Privileges For Overlapping Functional Groups (replaced) (See the New Enterprise Parameters for the replacement enterprise parameter.)
•Enable MultiLevelAdmin (removed)
•User Cache Flush Timeout (Minutes) (removed)
Serviceability Considerations
Updates to roles and to user groups generate audit logs of user logins and access and modifications to Cisco CallManager configuration data.
Where to Find More Information
•Role Configuration, Cisco CallManager Administration Guide
•User Group Configuration, Cisco CallManager Administration Guide
•Roles and User Groups, Cisco CallManager System Guide
RSVP
Resource Reservation Protocol (RSVP) designates a resource reservation signaling protocol for reserving resources in IP networks. RSVP messages travel along the same path as the media flow path. Because RSVP is unidirectional, flows get reserved in only one direction. Because RSVP is receiver-oriented, the receiver of the stream requests the reservation. (Two reservations, one for each direction, get made for each audio call.)
Previously, Cisco CallManager used locations-based Call Admission Control (CAC) exclusively. RSVP provides an additional method of CAC. CAC preserves call quality by providing a method for rejecting an additional call that would degrade the quality of in-progress calls that are using a given set of resources.
RSVP provides guaranteed quality of service (QoS). RSVP preserves QoS and improves customer perception of IP voice calls. Network-aware RSVP can handle changes to routing or bandwidth, whereas location-based CAC cannot.
Location-based CAC supports only hub-and-spoke network topology. RSVP supports more complex network topologies, such as topologies that include the following entities:
•Redundant links
•More than three sites in a series
•Multilevel hierarchies
•Meshes
RSVP also supports the addition of video streams and their more complex bandwidth requirements to the resource reservation protocol. RSVP supports MLPP inherently.
Cisco CallManager supports RSVP through an RSVP agent. RSVP supports all signaling protocols. RSVP works with all Cisco CallManager supplementary services and features, such as Transfer, Conference, and Forwarding, to ensure that bandwidth reservation is correct after invocation of the feature or service.
RSVP does not support the following scenarios:
•Reservations between clusters
•RSVP-enabled endpoints
•Device mobility
Cisco CallManager Administration Configuration Tips
To configure RSVP, the administrator uses the Cisco CallManager Administration Location and Service Parameter Configuration windows. See the following sections for more information.
GUI Changes
Use the following Cisco CallManager Configuration windows to configure RSVP:
•System > Location
–RSVP Setting
•System > Service Parameters
The following service parameters in the Clusterwide Parameters (System — RSVP) pane affect RSVP configuration:
–Default Interlocation RSVP Policy
–RSVP Retry Timer
–Mandatory RSVP Mid-call Retry Counter
–Mandatory RSVP mid call error handle option
–RSVP Video Tspec Burst Size Factor
–Other RSVP service parameters
–Differentiated services code point (DSCP)-related service parameters
Administrators do not normally need to change the values of these service parameters.
•Media Resources > Media Resource Group List
–Assign a Media Resource Group List that includes RSVP Agent to the device or to the device pool that is associated with the device.
Service Parameter Changes
The following new service parameters support RSVP:
•Clusterwide Parameters (System — QoS)
–DSCP for audio calls when RSVP fails
–DSCP for video calls when RSVP fails
•Clusterwide Parameters (System — RSVP)
–A variety of new service parameters
User Tips
Cisco does not recommend activating both location-based CAC and RSVP at the same time, except during the migration period from location-based CAC to RSVP.
During the RSVP deployment time period, devices in some Cisco CallManager locations will have RSVP Agent resource configured, and devices in other locations will not have RSVP Agent configured. In cases where a call gets made from an RSVP location to a non-RSVP location, Cisco CallManager will manage the call QoS by using both location-based CAC and RSVP.
Serviceability Considerations
Cisco CallManager Serviceability provides location-based and node-based PerfMon counters for RSVP admission control. The PerfMon counters do not synchronize across nodes.
Cisco CallManager Serviceability also provides PerfMon counters for RSVP Agent resources (media termination points and transcoders).
A new alarm indicates that no RSVP agent resource is available.
Cisco CallManager RSVP Reservation Failure SDL and SDI traces get generated.
CAR/CDR Considerations
The QoS/RSVP Agent feature adds the following CDR fields:
•origRSVPAudioStat
•destRSVPAudioStat
•origRSVPVideoStat
•destRSVPVideoStat
These CDR fields reflect the status of RSVP bandwidth reservation per audio or video stream.
Where to Find More Information
•Resource Reservation Protocol, Cisco CallManager System Guide
•Location Configuration, Cisco CallManager Administration Guide
•Service Parameter Configuration, Cisco CallManager Administration Guide
•Multilevel Precedence and Preemption, Cisco CallManager Features and Services Guide
•Cisco CallManager Serviceability System Guide
•Cisco CallManager Serviceability Administration Guide
Service Enhancements
Cisco CallManager Release 5.0 includes the following enhancements to Services:
•Services get listed by type of service within Cisco CallManager Serviceability. Main categories include Feature Services and Network Services.
•Be aware that new services are available in Cisco CallManager Serviceability for service activation and in Cisco CallManager Service Parameter Configuration for setting and configuring parameters.
Feature Services—CM Services
The following Services belong to the CM Services group when using Cisco CallManager Serviceability:
•Cisco CallManager
•Cisco TFTP
•Cisco Messaging Interface
•Cisco IP Voice Media Streaming App
•Cisco CTIManager
•Cisco CallManager Attendant Console Server (new)
•Cisco Extension Mobility
•Cisco Extended Functions
•Cisco CallManager Cisco IP Phone Services (new)
•Cisco Dialed Number Analyzer (new)
•Cisco DHCP Monitor Service (new)
Feature Services—CTI Services
The following Services belong to the CTI Services group when using Cisco CallManager Serviceability:
•Cisco IP Manager Assistant
•Cisco WebDialer Web Service
Feature Services—CDR Services
The following Services belong to the CDR Services group when using Cisco CallManager Serviceability:
•Cisco SOAP - CDRonDemand Service (new)
•Cisco CAR Scheduler (new)
•Cisco CAR Web Service (new)
Feature Services—Database and Admin Services
The following Services belong to the Database and Admin Services group when using Cisco CallManager Serviceability:
•Cisco AXL Web Service (new)
•Cisco Bulk Provisioning Service (new)
•Cisco TAPS Service (new)
Feature Services—Performance and Monitoring Services
The following Services belong to the Performance and Monitoring Services group when using Cisco CallManager Serviceability:
•Cisco Serviceability Reporter (new)
•Cisco CallManager SNMP Service (new)
Feature Services—Security Services
The following Services belong to the Security Services group when using Cisco CallManager Serviceability:
•Cisco CTL Provider (new)
•Cisco Certificate Authority Proxy Function
•Feature services—Directory Services
Feature Services—Directory Services
The following Service belongs to the Directory Services group when using Cisco CallManager Serviceability:
•Cisco DirSync (new)
Network Services—Platform Services
The following Services belong to the Platform Services group when using Cisco CallManager Serviceability:
•A Cisco DB (new)
•Cisco Tomcat
•SNMP Master Agent (new)
•MIB2 Agent (new)
•Host Resources Agent (new)
•Native Agent Adapter (new)
•System Application Agent (new)
•Cisco CDP Agent (new)
•Cisco SysLog Agent (new)
•Cisco Electronic Notification (new)
•Cisco License Manager (new)
•Cisco Certificate Expiry Monitor (new)
Network Services—DB Services
The following Service belongs to the DB Services group when using Cisco CallManager Serviceability:
•Cisco Database Layer Monitor
Network Services—CM Services
The following Services belong to the CM Services group when using Cisco CallManager Serviceability:
•Cisco CallManager Admin (new)
•Cisco CallManager Serviceability (new)
•Cisco CallManager Personal Directory (new)
•Cisco Log Partition Monitoring Tool (new)
•Cisco CDP
•Cisco Trace Collection Servlet
•Cisco Trace Collection Service
•Cisco RIS Data Collector
•Cisco AMC Service (new)
•Cisco Extension Mobility Application
Network Services—Performance and Monitoring Services
The following Services belong to the Performance and Monitoring Services group when using Cisco CallManager Serviceability:
•Cisco CallManager Serviceability RTMT
•Cisco RTMT Reporter Servlet (new)
•Cisco Tomcat Stats Servlet (new)
Network Services—SOAP Services
The following Services belong to the SOAP Services group when using Cisco CallManager Serviceability:
•SOAP—Real-Time Service APIs (new)
•SOAP—Performance Monitoring APIs (new)
•SOAP—Log Collection APIs (new)
Network Services—Backup and Restore Services
The following Services belong to the Backup and Restore Services group when using Cisco CallManager Serviceability:
•Cisco DRF Master (new)
•Cisco DRF Local (new)
Network Services—CDR Services
The following Services belong to the CDR Services group when using Cisco CallManager Serviceability:
•Cisco CDR Repository Manager (new)
•Cisco CDR Agent (new)
Where to Find More Information
•Cisco CallManager Serviceability Administration Guide
•Cisco CallManager Serviceability System Guide
•CDR Analysis and Reporting Administration Guide
•Service Parameters Configuration, Cisco CallManager Administration Guide
SIP Line Side (Endpoints) Support
The Cisco IP Phones 7911, 7941, 7961, 7970, and 7971 for SIP, deploy as a SIP endpoint in a Cisco CallManager Back to Back User Agent (B2BUA) environment or in a SIP peer-to-peer network. The SIP protocol provides the primary interface between the phone and other network components. In addition to SIP, other protocols get used for various functions such as DHCP for IP address assignment, DNS SRV for domain name to address resolution, and TFTP for downloading image and configuration data.
The SIP line side feature affects Cisco CallManager architecture, the TFTP server, and the Cisco IP Phones. Because the SIP phone features are equivalent to the SCCP phone features, and they behave similarly. Cisco IP Phones 7941/61/71/70/11 for SIP, support all features. Cisco IP phones 7905/12/40/60 for SIP, support a reduced feature set (for example, limited MOH and failover capabilities). SIP trunk side applications work for both SCCP and SIP phones.
Cisco CallManager Administration Configuration Tips
To configure SIP line support, the administrator uses a variety of Cisco CallManager Administration windows. See the following sections for detailed information.
Cisco SIP IP Phones Supported by Cisco CallManager 5.0
•Cisco IP Phone 7905 (SIP)
•Cisco IP Phone 7912 (SIP)
•Cisco IP Phone 7940 (SIP)
•Cisco IP Phone 7960 (SIP)
Note The Cisco IP Phones 7905, 7912, 7940, and 7960 for SIP, have limited functionality in Cisco CallManager. Refer to the appropriate SIP phone documentation for details.
•Cisco IP Phone 7911 (SIP)
•Cisco IP Phone 7941 (SIP)
•Cisco IP Phone 7961 (SIP)
•Cisco IP Phone 7970 (SIP)
•Cisco IP Phone 7971 (SIP)
Note The Cisco IP Phones 7911, 7941, 7961, 7970, and 7971, for SIP have full functionality in Cisco CallManager. Refer to the appropriate SIP phone documentation for details.
Configuration Similarities Between SCCP Phones and SIP Phones
•Configure SIP and SCCP phones by using Cisco CallManager Administration (Directory Number and Phone Configuration windows):
–A majority of the fields on the Phone Configuration window are the same for SIP and SCCP.
–All fields on the Directory Number Configuration window are the same for SIP and SCCP.
•Protocol (SIP or SCCP) gets specified when a new phone type is added
•Cisco SIP and SCCP phones can be reset and restarted from the Cisco CallManager Administration configuration windows
Configuration Differences Between SCCP Phones and SIP Phones
•SCCP phones get device pool configuration from the TFTP server and get the rest of configuration information from the SCCP messages:
–Includes Cisco CallManager group (primary, secondary, tertiary), SRST, load info
•SIP phones get all configuration from the TFTP server:
–Device pool, line configuration, softkey, dial plan
•SCCP phones do not have a local dial plan.
•SIP phones can have a local dial plan:
–If configured, the dial plan is either part of the configuration file or a separate file depending on the phone model.
•SCCP phones register by using TCP or TLS.
•SIP phones register by using UDP, TCP, or TLS.
GUI Changes
Use the following Cisco CallManager Configuration windows to configure SIP phones.
•System > Cisco CallManager Configuration
–SIP Phone Port
–SIP Phone Secure Port (used for Security)
–Auto-Registration (if using)
The SIP auto registration enterprise parameter must be set (System > Enterprise Parameters)
•System > SRST Reference Configuration (optional)
–SIP Network/IP Address
–SIP Port
•System > Phone NTP Reference Configuration (optional)
–If configured, add NTP server to Date/Time configuration.
•System > Presence Group (optional unless presence is needed)
•System > Security Profile
–SIP Phone Security Profile (Many default profiles from which to choose exist.)
•Call Routing > Dial Rules > SIP Dial Rules Configuration (optional)
–If configured, add to SIP IP Phone configuration.
•Device > Device Settings > SIP Profile Configuration (A default profile is provided.)
–Add the SIP profile to the SIP IP Phone configuration.
•Device > Phone Configuration:
–Choose phone model.
–Choose SIP protocol.
–Choose the appropriate phone button template.
–SIP dial rules (optional)
–SIP Phone Security Profile
–SIP Profile
•Call Routing > Directory Number Configuration (can also be added from Phone Configuration)
–Add to SIP Phone Configuration.
•User Management > SIP Realm (optional unless security is needed)
Cisco CallManager Configuration
•The SIP Phone Port specifies the port number that Cisco CallManager uses to ascertain SIP line registrations over TCP and UDP.
•The SIP Phone Secure Port specifies the port number Cisco CallManager uses to ascertain SIP line registrations over TLS.
•Changes to either require the Cisco CallManager service to be restarted.
•Use the default settings unless special requirements are needed.
SIP Phone Security Profile Configuration
•Use the SIP Security Profile to specify transport type and port for registering SIP phones.
•Transport Type field—This represents the transport that Cisco CallManager will accept. Only Cisco IP Phones 7911, 7941, 7961, 7970, and 7971, for SIP will get configured with transport type. All other Cisco SIP phones only support UDP.
•SIP Phone Port field—This designates the signaling port that the phone listens on locally (voipControlPort). Difference exists from SIP Phone Port in Cisco CallManager Configuration window.
SIP Dial Rules Configuration
With dial rules, a phone can send a SIP INVITE without the Dial softkey. Create one or more Dial Rules, each of which has one or more Patterns, and each of which has one or more Parameters. Configure the Dial Rule to a specific SIP phone. When the phone powers on or resets, it will upload its configuration and its dial rules based on MAC address.
When the SIP phone gets its configuration file from the TFTP server, that file will either contain the rules (Cisco IP Phones 7905/7912) or that file will contain a pointer to another file that the phone will then upload from the TFTP server (Cisco IP Phones 7940/7960, 7911, 7941, 7961, 7970, and 7971).
When a user makes a call, and if the digits the user dials match any pattern in the uploaded Dial Rules, the phone will send INVITE without waiting for the Dial softkey.
SIP Profile Configuration
•Use SIP Profile parameters locally in the phone. In most cases, you can use the default values.
•Add the SIP Profile (or use Default) to the SIP Phone configuration.
Phone Configuration (SIP Phone)
•Choose Cisco phone model that supports SIP:
–Cisco IP Phones 7905, 7911, 7912, 7940, 7941, 7960, 7961, 7970, 7971
–Choose Third-party SIP Device (Basic) or Third-party SIP Device (Advanced) for third-party phone (if applicable).
•Select SIP Protocol.
•Although SIP phone configuration is similar to SCCP, differences exist in the Protocol Specific Information section:
–Presence Group—Used for BLF, Missed/Placed calls
–SIP Dial Rules—SIP dial plan downloaded to the phone.
–SIP Profile
–SIP Security Profile
–Packet Capture Mode—Used for decrypting TLS packets
–Digest User—Digest User needed for third-party phones.
•Line configuration matches that of SCCP phone.
Device Defaults
Because device default entries for phones are protocol dependent, for example, you will see Cisco IP Phone 7905 (SCCP) and Cisco IP Phone 7905 (SIP) as device type and protocol.
New Service Parameters
•SIP Station and Backup Server Keepalive Interval
•SIP Station Keepalive Interval
•SIP Station Realm
•Clusterwide Parameters (Device - SIP)—Variety of new parameters
New Enterprise Parameter
•Auto Registration Phone Protocol—Choose SCCP or SIP.
Removed or Changed Service Parameters
The SIP Profile includes the following service parameter:
•Off-hook to First Digit Timer
SCCP and SIP Phone Service Parameters Differences in Behavior
•To achieve the same level of control that the Drop Ad Hoc Conference parameter settings provides for SCCP phone-initiated conference calls, the administrator can use a combination of the Conference Join Enabled SIP profile parameter and the Block OffNet to OffNet Transfer service parameter for conferences that are initiated on the SIP phone. (Because the SIP phone performs a transfer when it drops out of the conference call, the Block OffNet to OffNet Transfer can prevent toll fraud by not allowing two offnet phones to remain in the call.) For more information, see Conference Bridges in the Cisco CallManager System Guide.
Serviceability Considerations
Cisco CallManager Serviceability provides the following Trace Configuration parameters for SIP line support:
•Enable SIP Stack Trace
•Enable SIP Call Processing Trace
BAT Considerations
The Bulk Administration Tool provides the following support for SIP endpoints:
•Phones—Use the template to create SIP phones, use query to find SIP phones, and use Migrate Phones to migrate SCCP to SIP.
CAR/CDR Considerations
Cisco CallManager generates two types of call statistics records: Call Detail Records (CDR) and Call Management Records (CMR).
Cisco CallManager call control automatically generates Call Detail Records that are completely protocol independent.
Use the parameter, Call Diagnostics Enabled, for generating Call Management Records. These records contain the count of bytes that are sent and received, packets that are sent and received, jitter, latency, and lost packets. CMRs sometimes get referred to as Diagnostics Records.
The SIP phone supports two proprietary headers for reporting of statistics. These headers get added to BYE messages and to the 200 response to a BYE message.
Security Considerations
Security affects SIP line support in a variety of ways. The following Cisco CallManager Administration windows get used to configure security for SIP. For more information, see Security Features.
•System > SIP Phone Security Profile
•Device > Phone (add the SIP Phone Security Profile)
•User Management > SIP Realm
Note Secure Survivable Remote Site Telephony (SRST) does not support SIP phones.
CTI Considerations
CTI functionality supports Cisco SIP IP Phones model 7911, 7941, 7961, 7970, and 7971. CTI supports SIP phones from the existing CTI interfaces, but supports the functionality that is needed by applications that are required to support SIP phones. The CTI interfaces (JTAPI, TAPI) remain unchanged but expose a new SIP phone device type to applications.
Existing applications do not get impacted if the SIP phones are not application-controlled via CTI, or if they are used, applications must ensure that they do not use any CTI functionality that is not supported for SIP phones.
SIP phones support the following Cisco CTI applications:
•Contact Center (IPCC)
•Media Services (Automated Attendant (AA), Interactive Voice Response (IVR), Cisco IP Contact Center (IPCC) Express, Cisco Conference Connection (CCC))
•Emergency Responder
•Extension Mobility
•WebDialer
•Quality Reporting Tool
Note CTI does not support the Call Park/Unpark feature on the SIP phone.
Note Cisco SIP IP Phones that are configured to use User Datagram Protocol (UDP) as the transport mode (instead of TCP) will not support the device data pass-through functionality; for example, the Quality Reporting Tool (QRT) requires the data pass-through functionality, so it cannot be used with IP phones that are configured with UDP.
Where to Find More Information
•Phone NTP Reference Configuration, Cisco CallManager Administration Guide
•SIP Phone Security Profile Configuration, Cisco CallManager Administration Guide
•Cisco CallManager Configuration, Cisco CallManager Administration Guide
•SIP Dial Rules Configuration, Cisco CallManager Administration Guide
•Cisco IP Phone Configuration, Cisco CallManager Administration Guide
•SIP Profile Configuration, Cisco CallManager Administration Guide
•Cisco TFTP, Cisco CallManager System Guide
•Dial Rules Overview, Cisco CallManager System Guide
•Cisco IP Phones, Cisco CallManager System Guide
•Computer Telephony Integration, Cisco CallManager System Guide
SIP Route Pattern
Cisco CallManager uses SIP route patterns to route or block calls to foreign (with respect to this Cisco CallManager node or cluster) hosts by using SIP trunks. SIP route patterns provide the mechanism to route SIP call signaling messages based on the host address information in the SIP URI.
The domain name or IP address provides the basis for routing. The administrator can add domains, IP addresses, and IP network (subnet) addresses and associate them to trunks (only). This method allows requests that are destined for these domains to be routed through particular SIP trunk interfaces.
The digit analysis infrastructure between release 4.x and 5.0 is used extensively. The "match" logic that is used in routing decisions for specific patterns remain exactly the same whether dealing with DNs, numeric route patterns, or new SIP route patterns. New pattern type values differentiate SIP route patterns from numeric (non-SIP) pattern types.
Similarities between (Numeric) Route Patterns and SIP Route Patterns
The similarities between (Numeric) Route Patterns and SIP Route Patterns are:
•Both control the routing of calls.
•Both have wildcard capabilities.
Differences between (Numeric) Route Patterns and SIP Route Patterns
The differences between (Numeric) Route Patterns and SIP Route Patterns are:
•Formats significantly differ. Two different formats exist for SIP route patterns.
•The system limits devices that are associated with SIP route patterns to SIP trunks only.
•Meta characters and wildcard options differ.
•Numeric route patterns have more configuration options.
•SIP route patterns operate with respect to host address information. Numeric route patterns (in the case of SIP calls) operate with respect to user information.
•You cannot route SCCP calls by using SIP route patterns. You can route SIP calls by using either SIP or numeric route patterns.
Cisco CallManager Administration Configuration Tips
The following changes occurred in the GUI.
GUI Changes
Use the following Cisco CallManager Administration configuration windows to configure SIP route patterns.
•Call Routing > SIP Route Pattern allows you to create a new SIP route pattern.
•The Find/List SIP Route Pattern window allows you to search for a SIP route pattern that has already been created, or you can click the Add button to add a new SIP route pattern.
•The SIP Route Pattern Configuration window allows you to set up the new SIP route pattern. Two types of patterns exist: domain and IP address.
–Sample domain pattern: cisco.com and *.com
–Sample IP address pattern: 172.18.201.119 or 172.18.201.119/32 (includes explicit IP host address)
•The SIP Route Pattern Configuration window includes a new field called Transformations:
–Used to configure Calling Party and Connected Party
–Works the same as before, but only on numeric User URI information
•You must create a SIP trunk first, so it can be added to the SIP route pattern.
Enterprise Parameters
SIP route patterns support the following enterprise parameters, which are used to decide whether host address is local or foreign:
•Organization Top Level Domain
•Cluster Fully Qualified Domain Name
Serviceability Considerations
SIP route pattern supports new Trace messages:
•Indication of the type of match operations that DA is performing
•Indication of received host address being a foreign host
Where to Find More Information
•SIP Route Pattern Configuration, Cisco CallManager Administration Guide
•SIP Trunk Configuration, Cisco CallManager Administration Guide
•Understanding Route Plans, Cisco CallManager System Guide
•Understanding Session Initiation Protocol (SIP), Cisco CallManager System Guide
SIP Third-Party Phones
Cisco CallManager Release 5.0 supports Cisco SIP IP Phones as well as SIP phones that third-party companies design to work with Cisco CallManager.
Cisco CallManager Administration Configuration Tips
Administrators use the following Cisco CallManager Administration windows to configure third-party SIP phones:
•Directory Number Configuration
•SIP Profile Configuration (optional; can use the default SIP profile)
•SIP Phone Security Profile Configuration (optional)
•End User Configuration
–Associate the Third-party SIP Device (Basic) or Third-party SIP Device (Advanced) phone in the Controlled Devices box
•Phone Configuration
–Choose Third-party SIP Device (Basic) or Third-party SIP Device (Advanced) as the third-party phone type.
–Choose a user for the Digest User field. You must select a user that is not associated with an existing phone; otherwise the phone will not successfully register with Cisco CallManager. Also, be sure to use the same user ID on the phone.
–Configure the SIP Profile.
–In the SIP Phone Security Profile field, use one of the predefined Non-Secure SIP Profiles, or the Standard SIP Profile for Autoregistration or configure a SIP phone security profile. Enable digest authentication if required.
Note Third-party SIP Device (Basic) supports one line and consumes three license units, and Third-party SIP Device (Advanced) supports up to eight lines and video and consumes six license units.
GUI Changes
The Phone Configuration window includes two new phone types: Third-party SIP Device (Basic) and Third-party SIP Device (Advanced).
User Tips
The third-party vendor documentation provides all user information.
BAT Considerations
BAT provides a Third-party SIP Device (Basic) and Third-party SIP Device (Advanced) option on the Phone Template window.
Security Considerations
See Security Features.
Where to Find More Information
•Configuring Non-Cisco SIP Phones, Cisco CallManager Administration Guide
SIP Trunk Enhancements
SIP trunks interoperate with other SIP user agents such as SIP gateways and proxy servers.
Media Termination Points
You no longer need MTPs on the SIP trunk for DTMF events if the endpoints can negotiate the use of RFC2833 or out-of-band DTMF methods end-to-end. You can configure Cisco CallManager SIP devices (lines and trunks) to always use an MTP. If the configuration parameters are set to not use an MTP (default case) Cisco CallManager will attempt to dynamically allocate an MTP if the DTMF methods for the call are not compatible.
Retry as Audio
Retry as Audio pertains to outgoing SIP trunk calls and does not impact incoming calls. By default, the system specifies that this device should immediately retry a video call as an audio call (if it cannot connect as a video call) prior to sending the call to call control for rerouting.
If the default is changed, a video call that fails to connect as video does not try to establish as an audio call. The call then fails to call control, and call control routes the call via Automatic Alternate Routing (AAR) and/or route/hunt list.
Support for REFER Primitive
The system uses support REFER Primitive for SIP-initiated transfer features and other advanced transfer-related features such as Web Transfer and Click-to-Dial. Cisco CallManager supports in-dialog and out-of-dialog REFER (incoming only).
Support for Replaces Header
Use Replaces header to logically replace an existing SIP dialog with a new SIP dialog.
Support for SUBSCRIBE/NOTIFY Event Reporting
This feature currently supports the Presence event package and KPML (for out-of-band DTMF).
Message Waiting Indicator (MWI)
SIP trunk supports message waiting indicator from the SIP voice messaging server (Unity).
Video
SIP trunk supports the use of one video channel per call.
Multiple SIP Trunks per Incoming Port Number
You can configure SIP trunk with the same incoming port (no longer needs to be unique port number).
Enhanced SIP Redirection 3XX Support
The system passes 3XX Redirect messages to Cisco CallManager digit analysis, instead of this being done at the SIP stack level.
Security
SIP trunk supports connections over Transport Layer Security (TLS) in addition to UDP and TCP, and it supports digest for authentication and authorization.
Call Preservation
Active calls that exist within a Cisco CallManager cluster do not get interrupted when a Cisco CallManager node fails or when communication between a device and its Cisco CallManager node fails.
T.38 Fax Relay
The system supports both Fax Relay and Fax Passthrough. SIP trunk supports calls that start as a voice call and then switch to T.38.
RPID Enhancements
Calling party information gets enhanced to update the screen indicator, the privacy indicator for conference connected number, and to handle the connected party number for conferencing.
Out-of-Band (OOB) DTMF Handling
SIP trunk supports two OOB DTMF methods (KPML and Unsolicited NOTIFY) to reduce per-call MTP allocations.
SIP Standards Compliancy
Cisco SIP trunk complies with the following SIP standards:
•RFC2976 SIP INFO Method—Supported. INFO method gets used for video media channels such as Picture Fast Update and Picture Freeze.
•RFC2833 RTP Payload for DTMF Digits—Supported.
•RFC2782 DNS SRV—Supported.
•RFC3261 SIP—Supported
•RFC3262 SIP Reliability of Provisional Responses—Supported
•RFC3264 Offer/Answer Model for SDP—Supported
•RFC3265 Specific Event Notification—Supported. Packages supported include KPML, Presence, REFER.
•RFC3311 SIP UPDATE Method—Supported
•RFC3515 SIP REFER Method—Partially supported. SIP trunk accepts inbound REFERs (in-dialog and out-of-dialog). Release 5.0 supports method=INVITE in the Refer-To header. Cisco CallManager does not support multiple REFER requests within the same dialog.
•RFC3842 SIP MWI Package—Partially supported. SIP trunk supports unsolicited NOTIFY events; it does not Subscribe for MWI events notification.
•RFC3856 SIP PRESENCE Event Package—Supported
•RFC3891 SIP Replaces Header—Supported. INVITE with Replaces and REFER with Replaces.
•RFC4028 Session Timers in the SIP—Supported. For outgoing Invites, SIP trunk indicates the support via Supported header. For incoming Invites, it accepts the Supported and Session-Expires headers.
Cisco CallManager Administration Configuration Tips
The following configuration tips apply to Cisco CallManager Administration:
•You cannot use SIP trunks as intercluster trunks because SIP trunks do not provide the same feature parity as the existing H.323 ICT (for example, SIP trunks do not support Q.SIG tunneling and SRTP).
GUI Changes
The following GUI changes have occurred:
•Packet Capture Mode drop-down list box for TLS debugging.
•The Media Termination Point Required check box allows you to indicate whether an MTP should be allocated. Default specifies unchecked.
•Retry Video Call as Audio check box allows you to indicate whether a video call, if not connected, should be retried as an audio only call.
•A new section, SIP Information, displays and contains the following fields:
–Destination Address is an SRV Destination Port
–MTP Preferred Originating Codec
–Destination Presence Group
–SIP Trunk Security Profile
–Rerouting Calling Search Space (associated with the in-dialog and out-of-dialog ReRouting)
–Out-of-Dialog Refer Calling Search Space (associated with the in-dialog and out-of-dialog REFER)
–SUBSCRIBE Calling Search Space (associated with the in-dialog and out-of-dialog Presence)
–SIP Profile
–DTMF Signaling (To minimize MTP usage, Cisco recommends Best Effort, which is the default.)
Service Parameter Changes
This release removed the following Cisco CallManager service parameter from the Service Parameter Configuration window and added it to the SIP Profile Configuration window:
•SIP Default Telephony Event Payload Type—This field specifies the default payload type for RFC2833 telephony event. See RFC 2833 for more information. In most cases, the default value specifies the appropriate payload type. Be sure that you have a firm understanding of this parameter before changing it, as changes could result in DTMF tones not being received or generated through the SIP trunk. The default value specifies 101 with range from 96 to 127.
TFTP Enhancements
TFTP enhancements include support for SIP and for centralized TFTP in a multiple cluster environment.
SIP Support
When the SIP phone configuration gets changed, the Cisco CallManager database notifies the TFTP server to rebuild some or all of the configuration files. The TFTP server retrieves information from the Cisco CallManager database and converts it into the proper output format, according to the device type, and saves the output either in TFTP cache or on the disk.When the TFTP server gets a request, it searches either the cache or hard disk to serve the requested configuration file or default files.
The TFTP support for SIP phones builds and serves different formats of SIP configuration files from the Cisco CallManager database for the following SIP IP Phones:
•Cisco IP Phone 7970/71, 7961, 7941, and 7911 (These phones share the same SIP configuration file format.)
•Cisco IP Phone 7960 and 7940 (These phones share the same SIP configuration file format.)
•Cisco IP Phone 7905 and 7912
•SIP dial plans on the preceding phone models
•Softkey templates on the preceding phone models
Centralized TFTP in a Multiple Cluster Environment
A Centralized TFTP server supports multiple clusters within one large campus environment. The Centralized TFTP server allows phones to be moved from one building to another within a campus. It also supports a mixed OS multicluster environment.
Devices that are registered and configured in any cluster can home into a single TFTP server (Centralized TFTP server) that will then serve files to those devices.
Cisco CallManager Administration Configuration Tips
The following changes occur in Cisco CallManager Administration:
•Changes to Alternate TFTP Path
•Customizing and Modifying Configuration Files
Changes to Alternate TFTP Path
Similar to the Windows environment, Release 5.0 supports a different directory, but it must be on the same server where the TFTP service is running. Also, no mounted directory exists in 5.0.
Release 5.0 allows alternate path to now be a remote server. The syntax can be either of the following examples:
•host://<IP of the off-cluster TFTP server> (for example, host://10.89.134.24)
•HOST://<IP of the off-cluster TFTP server> (for example, HOST://10.89.134.24)
The system does not allow any other syntax.
Customizing and Modifying Configuration Files
You can modify configuration files (for example, edit the xml files) and add customized files (for example, custom ring tones, call back tones, phone backgrounds) to the TFTP directory. You can modify files and/or add customized files to the TFTP directory in Cisco IPT Platform Administration, from the TFTP Server File Upload page. Refer to the Cisco IP Telephony Platform Administration Guide for information on how to upload files to the TFTP folder on a Cisco CallManager server.
Serviceability Considerations
The TFTP server provides counters in Cisco CallManager Serviceability for troubleshooting purposes. See the Cisco CallManager Serviceability System Guide and the Cisco CallManager Serviceability Administration Guide for more information.
Where to Find More Information
•Cisco TFTP, Cisco CallManager System Guide
•Cisco CallManager Serviceability Administration Guide
•Cisco CallManager Serviceability System Guide
•Cisco IP Telephony Platform Administration Guide
URL Dialing
The following Cisco IP Phones (SIP) support URL dialing:
•Cisco IP Phone 7970G/7971G-GE
•Cisco IP Phone 7961G/7961G-GE and 7941G/7941G-GE
•Cisco IP Phone 7960G and 7940G
•Cisco IP Phone 7911G
Cisco CallManager Administration Tips
You do not need to configure URL Dialing in Cisco CallManager Administration.
User Tips
The following sections provide information on using URL dialing on Cisco IP Phones.
Cisco IP Phone 7970G/7971G-GE, 7961G/7961G-GE, 7941G/7941G-GE, and 7911G
To place a call from a URL entry in a call log on the Cisco IP Phone 7970G/7971G-GE, 7961G/7961G-GE, 7941G/7941G-GE, and 7911G:
1. Choose 
> Missed Calls, Placed Calls, or Received Calls.
2. Highlight the URL entry you want to dial.
3. If you need to edit the entry, press EditDial.
The 
icon appears and indicates that you can edit characters in the URL entry.
4. Press Dial.
For More Information
•See "Using Call Logs" in the phone guides.
Cisco IP Phone 7960G and 7940G
To place a call on the Cisco IP Phone 7960G and 7940G by using alphanumeric strings containing letters, numbers, or symbols:
1. Press NewCall > URL.
2. Enter the alphanumeric characters that you want to dial.
3. To make corrections to the entry, press <<. Or, to remove the entry completely, press Clear.
The icon appears and indicates that you can edit characters in the URL entry.
4. Press Dial to complete the call, or, press EndCall.
5. To return to standard dialing mode, press Number.
For More Information
•See "URL Dialing" in the Cisco IP Phone Guide for 7960G and 7940G for Cisco CallManager 5.0 (SIP).
Video Telephony Enhancements
SIP video supports the following video calls by using the SIP Signaling Interface (SSI):
•SIP to SIP
•SIP to H.323
•SIP to SCCP
•SIP intercluster trunk
SIP video calls also provide media control functions for video conferencing.
Cisco CallManager video supports the SIP protocol, and both SIP trunks and lines support video signaling. SIP supports the H.261, H.263, and H.264 video codecs (it does not support the wideband video codec that the VTA uses).
Cisco CallManager supports the use of H.264 codec within H.323 protocol.
The following table lists the type of audio codes that SIP interfaces support.
Codec
|
RTP Payload Type
|
G.711 mu-Law
|
0
|
GSM
|
3 (also referred to as GSM Full Rate)
|
G.723
|
4
|
G.711 a-Law
|
8
|
G.722
|
9
|
G.728
|
15
|
G.729
|
18 (support for combinations of AnnexA and AnnexB)
|
Some Media Termination Point (MTP), which is used for RFC 2833, supports multiple logical channels within a session. A logical channel could apply for audio or video. To support video channels, the MTP uses pass-through mode. Video pass-through gets enabled if the MTP supports both pass-through and multiple logical channels. Not all MTP devices support multiple logical channels and pass-through mode.
Cisco CallManager Administration Configuration Tips
The following section describes the configuration that is needed for SIP devices to support video calls.
Configuring a SIP Trunk for Video Calls
Perform the following steps to enable video calls on a SIP trunk:
•On the Trunk Configuration window in Cisco CallManager Administration, ensure that the Retry Video Call as Audio check box is checked if you want the call to use audio when the video connection is not available.
•Reset the trunk.
Service Parameter Changes
•DSCP for video calls when RSVP fails
•Intraregion Video Call Bandwidth Default
•Interregion Video Call Bandwidth Default
•RSVP Video Tspec Burst Size Factor
•RSVP Video Application ID
Serviceability Considerations
The following serviceability performance monitoring counters are available for the video enhancements:
•Cisco SIP
–VideoCallsCompleted
–VideoCallsActive
Where to Find More Information
•Understanding Video Telephony, Cisco CallManager System Guide
Voice Quality Metrics
With Cisco CallManager 5.0(1), system administrators can access a set of 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:
•During call—You can view the call information by rapidly pressing the question mark button twice.
•After the call—You can view the call information that is captured during the last call by displaying the Call Statistics screen.
Note You can remotely view the call statistics information by using a web browser to access the Streaming Statistics.
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.
Configuration Tips (for Administrators)
You can configure Cisco IP Phones to collect call diagnostics and voice-quality metrics by setting a service parameter in Cisco CallManager Administration as described in the following steps:
1. From Cisco CallManager Administration, choose System > Service Parameters.
2. In Clusterwide Parameters (Device - General), locate the Call Diagnostics Enabled service parameter.
3. From the drop-down list box, choose one of the following states:
•Enabled Only When CDR Enabled Flag is True
•Enabled Regardless of CDR Enabled Flag
4. Click Save.
For more information about configuring service parameters in Cisco CallManager Administration, refer to the Cisco CallManager Administration Guide, the Cisco CallManager System Guide, and the Cisco IP Phone user and administration documentation.
How This Feature Affects the End User
When end users report poor voice quality on certain phone calls, administrators can use voice quality metrics to assist with troubleshooting network problems.
Supported Phones
•Cisco IP Phone 7970G/7971G-GE (SCCP)
•Cisco IP Phone 7961G/7961G-GE (SCCP) and 7941G/7941G-GE (SCCP)
•Cisco IP Phone 7960G (SCCP) and 7940G (SCCP)
•Cisco IP Phone 7911G (SCCP)
Where to Find More Information
•Cisco IP Phone Administration Guides
•Cisco CallManager Administration Guide
•Cisco CallManager System Guide
Cisco CallManager User Options Web Pages
Cisco CallManager 5.0(1) provides the following changes to the Cisco CallManager User Options web pages.
Addition of the Cisco Personal Communications Assistant Layer
End-users log in to the Cisco Personal Communications Assistant and then choose User Options from the menu bar to navigate to User Options.
When logged in and viewing User Options, users access a User Guide, change the locale for the web pages, and configure user-specific options such as Personal Address Book and Fast Dials.
To access phone-specific features, users must select a device after logging in (User Options > Device). When a device is selected, the user can access additional configuration options from the Related Links drop-down list, including speed dials, phone services, and line-specific options (call forwarding, message-waiting indicators, and ring patterns).
Redesigned User Interface
The redesigned Cisco CallManager User Options web pages have the same look-and-feel as Cisco CallManager Administration. End users log in by using a Cisco CallManager user ID and password.
To access User Settings, Directory features, a Personal Address Book, and Fast Dials, users choose User Options from the menu bar.
To access phone-specific features, users must choose a device after logging in (User Options > Device). When a device is chosen, users can access additional configuration options including speed dials, phone services, and line-specific options (such as call forwarding, message waiting indicators, and ring patterns).
This release includes the following changes to the User Options functionality:
•Users can create up to 500 Fast Dial entries and 500 Personal Address entries (previously limited to 99).
•The system provides an ASCII Label field for phones that do not support double-byte character sets.
•The Personal Address Book and Fast Dials features no longer get considered as services. Access these features directly on the phone from the Directory feature button, under the Personal Directory menu (see the "Personal Directory Enhancements" section).
Where to Find More Information
•Cisco IP Phone User Guides, Customizing Your Phone on the Web section (a separate guide, Customizing Your Cisco IP Phone Guide on the Web, previously included this information).
•Cisco IP Phone Administration Guides, Providing Information to Users Via a Website section (now includes TABSynch instructions that you must provide to your users.
Cisco CallManager Applications
The Cisco CallManager 5.0 applications enhancements are described in the following sections:
•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
Cisco Call Back
The Cisco Call Back feature allows you to receive call-back notification on your Cisco IP Phone when a called party line becomes available.
User Tips
Release 5.0 of Cisco CallManager supports the Cisco Call Back feature on the Session Initiation Protocol (SIP) Cisco IP Phones 7970, 7971, 7961, and 7941.
The Cisco IP Phones 7960 and 7940 do not support call back notification for on-hook/off-hook states.
Users receive call- back notification by pressing the Call Back softkey on a Cisco IP Phones 7970 SIP phone in the same way as a Skinny Client Control Protocol (SCCP) phone. See the Cisco SIP IP Phone 7970 Guide for more information.
In previous releases, manually dialing a directory number (DN) on which Cisco Call Back notification had been activated would have the same effect as pressing the Dial softkey from the notification screen. In Release 5.0, however, manually dialing a DN with Cisco Call Back notification on it has no effect on the call-back status.
Subscription Manager, a new component in Release 5.0, will replace the CTIManager service; therefore, you no longer require the CTIManager service for Cisco Call Back.
Suspend/Resume Feature Functionality
With Release 5.0, Cisco Call Back provides the ability to suspend the call-completion service if the user, who originated Cisco Call Back, is currently busy and receives call-back notification when the called party becomes available. When the originating user then becomes available, the call-completion service resumes for that user.
Where to Find More Information
•Cisco Call Back, Cisco CallManager Features and Services Guide
Cisco CallManager Attendant Console
Cisco CallManager Attendant Console, a client-server application, allows you to use a graphical user interface that contains speed-dial buttons and quick directory access to look up phone numbers, monitor line status, and direct calls.
For this release, new windows were added, and existing windows were modified, so administrators could configure features that they previously configured by editing files on the Cisco CallManager server:
•To configure functions that previously were supported by the Attendant Console Configuration Tool including changing JTAPI Username and JTAPI password, entering queue size and queue hold time, and configuring circular and broadcast hunt groups, administrators configure new fields on the Cisco CallManager Administration Pilot Point Configuration window and Cisco CallManager Administration Service Parameter Configuration window.
•To create dial rules and directory lookup rules, administrators use the Application Dial Rule Configuration window and the Directory Lookup Dial Rule Configuration window, respectively, rather than editing the DialRules.xml file.
•To upload CorporateDirectory.txt files, Cisco CallManager Administration contains a new Attendant Console User File upload window
Cisco CallManager Administration Configuration Tips
The following sections describe the changes to Cisco CallManager Administration windows and service parameters for Cisco CallManager Attendant Console.
GUI Changes
The following new and changed windows support Cisco CallManager Attendant Console:
•Attendant Console User File Upload (new)—Allows users to upload CorporateDirectory.txt files if their user lists is located on a directory server that is separate from the Cisco CallManager server. To access, choose Application > Cisco CM Attendant Console > Cisco CM Attendant Console User File Upload.
•Directory Lookup Dial Rule Configuration window (new)—Allows administrators to configure directory lookup rules rather than exiting an .xml file on the Cisco CallManager server. This window resembles the Application Dial Rule Configuration window. To access, choose Call Routing > Dial Rules > Directory Lookup Dial Rules.
•Pilot Point Configuration window (changed)—Contains the following new fields: Registration, IP Address, Description, Location, Media Resource Group List, Network Hold Audio Source, User Hold MOH Audio Source, Queuing Enable, Queue Size, and Queue Hold Time (seconds). In addition, the Route Calls drop-down list box contains Broadcast hunting and Circular hunting as new options. Many of these fields and options previously existed in the Attendant Console Configuration Tool. The Pilot Point Configuration window also contains a link to the Line Appearance Configuration window, so the administrator can choose a valid pilot point number rather than simply entering a number on the Pilot Point Configuration window itself.
•Cisco CallManager Service Parameter Configuration window (changed)—Contains JTAPI Username and JTAPI Password fields that previously existed in the Attendant Console Configuration Tool.
•Add the ac user to the Standard CTI Enabled group and the Standard CTI Allow Call Park Monitoring group by using the User Group window (User Management > User Group.)
•Make sure that you check the Allow Control of Device from CTI check box on the Phone Configuration window for each attendant phone. The system enables this field by default. If this check box is not checked for the attendant phone, call control does not come up for the attendant console.
Service Parameter Changes
The following new service parameter supports Cisco CallManager Attendant Console:
•JTAPI Username—Specifies the username that the Cisco CallManager Attendant Console Server uses to log on to a CTI Device. The default specifies "ac." During an upgrade, Cisco CallManager migrates the value for this field from the Attendant Console Configuration Tool.
User Tips
Consider the following information when setting up the Cisco CallManager Attendant Console client application:
•You cannot use SIP phones as attendant phones, but attendants can receive and handle calls from SIP phones.
•The attendant console client displays the correct CFA status for all DNs. In previous releases, Cisco CallManager Attendant Console could only display the correct CFA status in the Directory window if fewer than 10 search entries displayed in the window.
•Users can import and export speed dials from the File menu on the client application.
•If you are using a firewall, you can configure the Attendant Console Client CallBack Port field on the Basic tab of the Cisco CallManager Attendant Console settings window to specify the port that the firewall should use to send callback messages to the attendant console client. To access this window, choose Edit > Settings from the application on the attendant PC.
CTI Considerations
You must associate the ac user to the Standard CTI Enabled users group (found on the Cisco CallManager Administration User Group Configuration window). If you do not associate the ac user to this group, pilot points do not register, and the call control does not go up on the console.
Cisco CallManager AutoAttendant
Cisco CallManager AutoAttendant, a simple automated attendant, allows callers to locate people in your organization without talking to a receptionist. You can customize the prompts that are played for the caller, but you cannot customize how the software interacts with the customer.
Cisco CallManager AutoAttendant comes bundled with Cisco CallManager on the Cisco CallManager 5-Agent IPCC Express bundle.
Cisco CallManager Administration Configuration Tips
Cisco AutoAttendant in CRS is no longer co-located on the server with Cisco CallManager, and many associated functions that were performed on Cisco CallManager are now performed on the CRS server. These functions include but are not limited to:
•Creating and updating CTI ports
•Creating and updating CTI Route Points
Install Cisco CallManager on an appliance-based system before you install Cisco CallManager AutoAttendant on the CRS server.
Before you can use Cisco CallManager AutoAttendant, you must configure Cisco CallManager including configuring a Cisco CallManager user for Cisco CallManager AutoAttendant.
Where to Find More Information
•Cisco AutoAttendant, Cisco CallManager Features and Services Guide
Cisco CallManager Extension Mobility
The Cisco CallManager Extension Mobility (EM) feature allows users to temporarily access their Cisco IP Phone configuration such as line appearances, services, and speed dials from other Cisco IP Phones.
Cisco CallManager Administration Configuration Tips
The following sections comprise tips and information for configuring Cisco Extension Mobility.
URL Change
When creating the Cisco Extension Mobility IP phone service, you must enter a service URL. Release 5.0 makes a change in the URL with regards to the port number. Enter the following URL:
http://<IP Address of Extension Mobilityserver>:8080/emapp/EMAppServlet?device=#
DEVICENAME#
SIP Support for Extension Mobility
Cisco Extension Mobility supports only Cisco IP phones 7911, 7941G, 7941G-GE, 7961G, 7961G-GE, and 7971 (SIP).
The following Cisco IP Phones support Cisco Extension Mobility:
•Cisco IP Phones 7970G/7971G
•Cisco IP Phones7961G/41G and 7961GE/41GE (G = Non Gig; GE = Gig)
Change Notification Enhancements
This release provides change notification to the extension mobility application. When a change in activation or deactivation of the extension mobility service occurs, on any node, the database tables get updated with information that is required to build the service URLs. The database tables also get updated when extension mobility service parameters get modified. The EMApp service handles the change notification.
You no longer need to restart the Cisco Tomcat server after a change to extension mobility service parameters.
GUI Changes
Changes exist throughout Cisco CallManager Administration, specifically to the add, update, insert and continue buttons.
A new location exists for the Subscribe/Unsubscribe option. The option now appears in the upper, right corner of the window and is part of the Related Links drop-down list box. This option will become available after Cisco Extension Mobility is configured.
Cisco Extension Mobility now constitutes a deployable service.
Service Parameter Changes
A new service parameter, Clearing call logs, clears the call log (missed, received, placed) after every successful EM login or logout. This action ensures privacy by preventing other users of the same phone from seeing the call logs of the previous user. Call logs get cleared only when you manually login or logout, but no display shows that the login/logout was successful, as occurred in the previous release. Clearing call logs designates a clusterwide service parameter.
A change to the existing service parameter, Remember last logged in user, occurs with this release. When the field is set to True, all future logins will cause the user ID of the last successful logged-in user to automatically get filled in and remembered by Cisco Extension Mobility. You no longer need to restart the Cisco Tomcat server for a change to the service parameter value.
Note The last login user ID will not get migrated during an upgrade from Windows to Release 5.0.
User Tips
When a Cisco CallManager Extension Mobility user logs out of a device, all Call Back services that are active on the Cisco CallManager Extension Mobility user automatically cancel.
Serviceability Considerations
Cisco CallManager Serviceability added four new performance counters. You can view them by using the RTMT tool:
•EMAPP_ATTEMPTED_LOGIN_LOGOUT —This counter measures the total number of attempted login and logout requests and includes both successful and failed requests.
•EMAPP_NO_OF_SUCCESS_LOGIN—This counter captures the successful login requests.
•EMAPP_NO_OF_SUCCESS_LOGOUT—This counter captures the successful logout requests (No Autologouts).
•EMAPP_NO_OF_THROTTLED_REQUESTS—This counter measures all throttled requests.
You must activate the following feature services from Cisco CallManager Serviceability for EM to be enabled:
•Cisco Extension Mobility
•Cisco CallManager Cisco IP Phone Services
You activate/deactivate these services from Cisco CallManager Serviceability > Service Activation. Refer to the Cisco CallManager Serviceability Administration Guide for more information.
Trace configuration for extension mobility has changed in the new Log4j infrastructure and the location of the trace files is not configurable. You should configure the trace settings from the Serviceability trace settings windows.
Where to Find More Information
•Cisco CallManager Extension Mobility, Cisco CallManager Feature and Services Guide
Cisco Dialed Number Analyzer
Dialed Number Analyzer (DNA) installs as a feature service along with Cisco CallManager. The tool allows you to test a Cisco CallManager dial plan configuration prior to deploying it. You can also use the tool to analyze dial plans after the dial plan is deployed. You can use Dialed Number Analyzer 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.
New and Changed Information for DNA
The following changes in DNA apply for Cisco CallManager 5.0.
•DNA supports Session Initiation Protocol (SIP) analysis for phones that support SIP and for SIP trunks.This release adds a new check box for SIP analysis to the Pattern Analysis field of the analyzer. Check the check box that corresponds to SIP Analysis, if applicable, and choose Domain Route or IP Route. If you want to perform a Session Initiation Protocol (SIP) analysis, make sure that you have configured a SIP Route Pattern in Cisco CallManager Administration. For more details, refer to Cisco CallManager Administration Guide.
•Log files and trace files for DNA transactions get collected by using the trace and log central feature. The trace level (such as info, debug, error, and so on) information gets set by using Cisco CallManager Serviceability for each service. Appropriate traces get written in the trace files based on the setting.
Logging on
You can access Dialed Number Analyzer by using Cisco CallManager Serviceability and choosing Tools > Dialed Number Analyzer.
You can also access DNA from a remote PC by using a web browser (Internet Explorer 6.0 or later versions).
Use the following URL to access Dialed Number Analyzer:
https://<cm-machine>:8443/dna
where <cm-machine> specifies the node name or IP address on which Dialed Number Analyzer is installed.
Serviceability Considerations
The following enhancements exist in Serviceability for DNA:
•Serviceability provides an option to activate/deactivate DNA Service (Serviceability > Tools > Service Activation).
•Serviceability provides an option to start and stop DNA Service (Serviceability > Tools > Control Center - Feature Services).
•Serviceability provides an option to change trace levels for DNA (Serviceability > Trace > Configuration).
•Access DNA by using Cisco CallManager Serviceability (Serviceability > Tools > Dialed Number Analyzer).
Where to Find More Information
•Cisco Dialed Number Analyzer Guide
•Cisco CallManager Administration Guide
•Cisco CallManager Serviceability Administration Guide
•Cisco CallManager Serviceability System Guide
Cisco Emergency Responder 1.3(1)
Cisco Emergency Responder (Cisco ER) 1.3(1) supports Cisco CallManager 5.0(1), in addition to Cisco CallManager 3.3, 4.0, 4.1 and 4.2.
•All Cisco ER servers must be version 1.3(1). This allows Cisco ER to support multiple Cisco CallManager 5.0(1) clusters. Cisco ER 1.3(1) will not work with previous versions of Cisco ER.
•CER 1.3(1) supports upgrades from Cisco ER 1.2(1), Cisco ER 1.2(2), and Cisco ER 1.2(3).
•Cisco ER 1.3(1) is Windows-based.
Where to Find More Information
Cisco Emergency Responder Administration Guide 1.3
Cisco IP Manager Assistant
Cisco IPMA fully integrates into Cisco CallManager Release 5.0.
Cisco CallManager Administration Configuration Tips
Cisco CallManager Release 5.0 IPMA feature includes the following configuration differences:
•IIS no longer gets supported
•Although Cisco Tomcat is still used, it does not represent an NT service.
•Cisco CallManager 5.0 supports one database, which also supports the directory information.
•Cisco IPMA supports Cisco IP Phones model 7940, 7941, 7960, 7961, 7970, 7971, and Cisco IP Communicator.
•Cisco IPMA does not support the SIP protocol.
•Partition Support—Cisco CallManager 5.0 IPMA supports the same line appearance (DN) in different partitions with the following configurations:
–Lines with same DN, different partition will be treated as different lines.
–Lines with same DN, same partition and different devices will be treated as shared lines.
–Lines with same DN, same partition on the same device do not get supported.
•The IPMA Manager and Assistant configuration window displays the partition information next to the line number. The database stores this information.
•Migration—When Cisco CallManager is upgraded from a windows version, all IPMA manager/assistant configuration migrate. The administrator must run the Data Migration Assistant (DMA) on the Windows platform prior to upgrading the platform to Release 5.0. It creates and exports a DMA tar ball of configuration data to be later installed onto the Release 5.0 platform during an upgrade.
•For IPMA in Proxy line mode, ensure the proxy line numbers on the assistant phone are unique, even though in different partitions.
•For IPMA in Proxy line mode, two managers cannot have the same IPMA-controlled line number (DN), even though in different partitions.
GUI Changes
Cisco IPMA supports the following GUI changes:
End User Configuration
Use to configure Cisco IPMA managers and assistants.
Cisco IP Phone Service Configuration
The URL requires a port address:
http://<server-ipaddress>:8080/ma/servlet/MAService?cmd=doPhoneService&Name=#DEVICENAME#
For example
http://123.45.67.89:8080/ma/servlet/MAService?cmd=doPhoneService&Name=#DEVICENAME#
Assistant Phone Configuration
Configure the assistant Cisco IP Phones with the following settings:
•Proxy lines for each configured manager with a voice-mail profile that is the same as the manager voice-mail profile
Cisco IPMA Configuration Wizard
•Choose IPMA configuration wizard from Application > Cisco IPMA Configuration Wizard.
Cisco IPMA Assistant Configuration
•Choose IPMA Assistant Configuration from User Management > End User Configuration, as well as from the IPMA Manager Configuration.
•An optional configuration parameter exists on the IPMA assistant configuration window: Primary Line. If configured, this line will get used as the default line to make external calls from the console.
New Service Parameters
See the "Security Considerations" section for more information.
User Tips
The Assistant Console application installation program supports Microsoft Internet Explorer (IE) 6.0 or later and Netscape 7.1 or later. The Manager Configuration application supports Microsoft IE 6.0 or later.
In Cisco IP Manager Assistant, the ImmDiv softkey on the manager phone causes behavior that differs from that of previous IPMA versions.
With the Cisco CallManager 5.0 release, if a manager who is using IPMA receives an incoming call and presses the ImmDiv softkey, the call immediately gets diverted to a configured available assistant. However, if no assistant is available, the call gets diverted to the voice mailbox of the manager.
In previous versions of IPMA, if a manager pressed the ImmDiv softkey and no configured assistant was available, the call did not get diverted to voice mailbox of the manager. Instead, the manager received a message that no configured assistant was available.
Installing the Assistant Console Application
Note When upgrading from Cisco CallManager Release 4.0 or 4.1 to Release 5.0, you must reinstall the Assistant Console application.
Begin the installation by accessing the following URL:
https://<IPMA server>:8443/ma/Install/IPMAConsoleInstall.jsp
where
IPMA server specifies the IP address of the server that has the IPMA service running on it.
Tip You can localize the installer (with the proper localization pack) by including the proper parameter on the URL; for example, for French, you would include the following parameter at the end of the URL:?locale=fr_FR.
Assistant Console Location
c:\Program Files\Cisco\IPMA Assistant Console\
Manager Configuration URL
https://<server-name/ip>:8443/ma/desktop/maLogin.jsp
IPMA Console
The console displays the partition information as a tool tip. Two lines with same directory number, but different partitions appear as separate lines.
Serviceability Considerations
Cisco IPMA supports the following for Serviceability:
IPMA_ChangeLog
The administrator can view a summary of changes that are made to the Manager or Assistant Configurations. A manager can change defaults by accessing the Manager Configuration from a URL.
An assistant can change the manager defaults from the Assistant Console.
Note Refer to the Cisco IP Manager Assistant User Guide for information about the URL and Manager Configuration.
When changes are made, the information gets sent to a log file that is called ipma_changeLogxxx.log. The log file resides on the server that runs the IPMA service at the following location:
file get activelog tomcat/logs/ipma/log4j
The administrator can download this file from the server by using the trace and log central feature in the Serviceability Real-Time Monitoring Tool (RTMT). Refer to the Cisco CallManager Serviceability Administration Guide for more information.
The log file fields remain the same.
Activating Cisco IPMA
Use Serviceability Control Center Feature Service to stop and start the Cisco IPMA service.
Trace Tool Settings
Configure trace settings from Cisco CallManager Serviceability. Choose Cisco CallManager Serviceability > Trace.
Download IPMA traces from the Cisco CallManager server by choosing Serviceability > Real Time Monitor Tool (RTMT) > Trace & Log Central.
Any errors that the configuration wizard generates get sent to the trace file.
Access this file can by using the following CLI command:
file get activelog tomcat/logs/ccmadmin/log4j
Alarms and Perfmon Counters
Alarms get enabled from Serviceability. Use the Serviceability Real Time Monitor Tool (RTMT) to view the perfmon status and syslog (alarms).
BAT Considerations
Cisco IPMA supports the following considerations for BAT, which is now integrated with Cisco CallManager Administration.
Accessing BAT from Cisco CallManager
To configure Cisco IPMA Managers and Assistants in BAT, choose Bulk Administration > Managers/Assistants. The following configuration windows display:
•Insert Managers/Assistants
•Delete Managers/Assistants
•Delete Managers (Query and Custom File)
•Delete Assistants (Query and Custom File)
•Generate IPMA Manager Reports
•Generate IPMA Assistant Reports
CAR/CDR Considerations
The CDR Analysis and Reporting Administration Guide documents CDR information for IPMA.
Security Considerations
IPMA supports security through the following service parameters and configuration windows:
Cisco IPMA Service Parameters
•CAPF Profile Instance Id for Secure Connection to CTI Manager—This node-specific service parameter specifies the Instance Id of the Application CAPF Profile for Application User IPMASecureSysUser that this Cisco IPMA server will use to open a secure connection to CTI Manager. You must configure this parameter if CTI Manager Connection Security Flag is enabled.
•CTI Manager Connection Security Flag—This clusterwide service parameter indicates whether security for Cisco IPMA service CTI Manager connection is enabled or disabled. If enabled, Cisco IPMA will open a secure connection to CTI Manager by using the Application CAPF profile that is configured in `Application CAPF Profile Instance Id for Secure Connection to CTI Manager' parameter.
•Cluster Security Mode—You must also configure the security service parameter Cluster Security Mode, from System > Enterprise Parameters in Cisco CallManager Administration, to secure a TLS connection to CTI, giving it a value of 1. This value indicates secure mode. Because this parameter is read-only, to change the cluster security mode, you must run the CTL Client plugin. You can do this from Application > Plugins in Cisco CallManager Administration.
Secure Connection to CTI
•IPMA supports a secure connection to CTI (TLS connection).
•The administrator must configure an IPMA Secure Sys User for CAPF profile (one per IPMA node) by choosing User Management > Application User CAPF Application Profile.
Where to Find More Information
•Cisco IPMA With Proxy Lines, Cisco CallManager Features and Services Guide
•Cisco IPMA With Shared Lines, Cisco CallManager Features and Services Guide
•Cisco CallManager Security Guide
•Cisco CallManager Administration Guide
•Cisco CallManager System Guide
Cisco Unity Voice Messaging
Cisco Unity comprises a communications solution that delivers voice messaging and unified messaging in a unified environment. This section comprises feature delta information for Cisco Unity and Cisco Unity Connection.
Cisco CallManager Administration Configuration Tips
Enhancements exist to create individual Cisco Unity or Cisco Unity Connection Voice Mailboxes in Release 5.0. You can create Cisco Unity and Cisco Unity Connection user mailboxes from Cisco CallManager Administration End User and Directory Number Configuration. For detailed information, refer to the Cisco CallManager Administration Guide.
Note You must configure both Cisco Unity (or Cisco Unity Connection) and Cisco CallManager Administration (for example, set up Cisco Unity voice mailbox templates, Cisco CallManager dial plans) to enable this feature. To set up Cisco Unity, refer to the integration and installation guides for Cisco Unity and Cisco Unity Connection.
Cisco CallManager SIP Integration to Cisco Unity now gets supported.
GUI Changes
When you save the configuration, Cisco Unity or Cisco Unity Connection adds the record in the Application Server Configuration in Cisco CallManager Administration. The Application Server windows get provided for Release 5.0.
You can create Cisco Unity voice mailboxes, if defined, in Cisco CallManager Administration by choosing the Create Cisco Unity User link that displays in the Related Links drop-down list box in the upper, right corner of Cisco CallManager Administration.
Note You must define a primary extension to create Cisco Unity voice mailboxes.
When the user is integrated with the Cisco CallManager End User, you cannot edit the following fields in Cisco Unity windows:
•Alias (User ID in Cisco CallManager Administration)
•First Name
•Last Name
•Extension (Primary Extension in Cisco CallManager Administration)
Cisco Unity monitors the syncing of data from Cisco CallManager. You can configure the sync time in Cisco Unity Administration.
Where to Find More Information
•End User Configuration, Cisco CallManager Administration Guide
•Directory Number Configuration, Cisco CallManager Administration Guide
•Integration and installation documentation for Cisco Unity and Cisco Unity Connection
Cisco WebDialer
Cisco WebDialer, which is installed on a Cisco CallManager server and used in conjunction with Cisco CallManager, allows Cisco IP Phone users to make calls from web and desktop applications. For example, Cisco WebDialer uses hyperlinked telephone numbers in a company directory to allow users to make calls from a web page by clicking the telephone number of the person that they are trying to call.
Cisco CallManager Administration Configuration Tips
The following section comprises the tips and information for configuring Cisco WebDialer.
Application Dial Rule Change Notifications
You no longer need to restart Cisco WebDialer after an application dial rule add, update, or delete. Dial rules will use change notification of data in the database, rather than the previous mechanism.
Redirector Servlet over HTTPS
The Redirector servlet now works over HTTPS, instead of HTTP. For example, you could access a URL similar to the following one:
https://<ccmIP address>:8443/webdialer/Redirector
SIP Support for WebDialer
Cisco WebDialer only supports Cisco IP Phones 7941G, 7941G-GE, 7961G, 7961G-GE, and 7971 for SIP.
The following Cisco IP Phones support Cisco WebDialer:
•Cisco IP Phones 7970G/7971G
•Cisco IP Phones 7961G/41G and 7961GE/41GE (G = Non Gig; GE = Gig)
GUI Changes
The Cisco WebDialer now supports partition information that JTAPI provides. The Cisco WebDialer Preferences include information about the partition, as well as line information.
You can now launch Cisco WebDialer from the Directory window, which is part of Cisco CallManager User Options.
You can access Cisco WebDialer from Cisco CallManager User Options, under the Directory link. As an example, you could access a URL similar to the following one:
https://<ccmIP address>:8443/ccmuser
Service Parameter Changes
To configure Cisco WebDialer service parameters, choose System >Service Parameters.
Two new security service parameters exist for enabling security for Cisco WebDialer in Release 5.0:
•CTI Manager Connection Security Flag—This clusterwide parameter indicates whether security for Cisco WebDialer service CTI Manager connection gets enabled or disabled. If enabled, Cisco WebDialer will open a secure connection to CTI Manager by using the Application CAPF profile that is configured in Application CAPF Profile instance ID for Secure Connection to CTI Manager parameter.
•Application CAPF Profile Instance Id for Secure Connection to CTI Manager—This parameter specifies the Instance Id of the Application CAPF Profile for Application User WDSysUser that this Cisco WebDialer server will use to open a secure connection to CTI Manager.
Note All changes to service parameters require a restart of the Cisco WebDialer service for the changes to take effect.
Serviceability Considerations
The following sections comprise Serviceability information for Cisco WebDialer.
Trace Settings
You should configure the Cisco WebDialer trace settings from the Serviceability trace settings windows. The same settings apply to both Cisco WebDialer and Redirector.
Alarms and Performance Counters
Two new Cisco WebDialer performance counters exist in Release 5.0:
•RequestsCompleted
•RequestsFailed
Security Considerations
Cisco WebDialer now supports a secure (TLS) connection to CTI. A new application user, WDSecureSysUser, obtains the secure CTI connection. Release 5.0 makes two new application users available in Cisco WebDialer:
•WDSecureSysUser—Cisco WebDialer uses this application user account to obtain a secure CTI connection.
•WDSysUser—Cisco WebDialer uses this application user account to open a non-secure CTI connection.
You must configure a CAPF profile in Application User CAPF Profile Configuration in Cisco CallManager Administration, that is configured for the instance ID for application user WDSecureSysUser. If you enable security from the service parameters window, Cisco WebDialer will open a secure connection to CTI Manager by using the Application CAPF profile.
You must also configure the security service parameter Cluster Security Mode, from System > Enterprise Parameters in Cisco CallManager Administration, to secure a TLS connection to CTI, giving it a value of 1. This value indicates secure mode. Because this parameter is read-only, to change the cluster security mode, you must run the CTL Client plugin. You can do this from Application > Plugins in Cisco CallManager Administration.
Where to Find More Information
•Cisco WebDialer, Cisco CallManager Features and Services Guide
•Cisco CallManager Administration
Client Matter Codes and Forced Application Codes
Forced Authorization Codes (FAC) and Client Matter Codes (CMC) allow you to manage call access and accounting. CMC assists with call accounting and billing for billable clients, while Forced Authorization Codes regulate the types of calls that certain users can place.
Client Matter Codes force the user to enter a code to specify that the call relates to a specific client matter. You can assign client matter codes to customers, students, or other populations for call-accounting and billing purposes. The Forced Authorization Codes feature forces the user to enter a valid authorization code before the call completes.
The CMC and FAC features require that you make changes to route patterns and update your dial plan documents to reflect that you enabled or disabled FAC and/or CMC for each route pattern.
Cisco CallManager Administration Configuration Tips
See the following section for GUI changes.
GUI Changes
CMC and FAC configuration moved from the Feature menu to the Call Routing menu in Release 5.0 of Cisco CallManager Administration.
Where to Find More Information
•Client Matter Codes and Forced Authorization Codes, Cisco CallManager Features and Services Guide
Multilevel Precedence and Preemption (MLPP)
Resource Reservation Protocol (RSVP) signalling, using the RSVP Agent, includes a precedence level indicator for support of MLPP. RSVP supports only MLPP audio calls.
The Cisco CallManager MLPP feature extends to RSVP reservations. Cisco CallManager passes the caller precedence level information to RSVP Agent by means of SCCP Quality of Service (QoS) messages. An IOS router can preempt the call based on the precedence level. RSVP Agent needs to notify Cisco CallManager about RSVP reservation failure reason including preemption cause. Cisco CallManager notifies the preempted caller or callee about the preemption by using the existing MLPP method.
Cisco CallManager passes the caller precedence level info to the RSVP Agent for both audio and video calls. The RSVP module in the router determines how to handle the precedence level information.
The system does not support MLPP for Session Initiation Protocol (SIP) phones.
Where to Find More Information
•Multilevel Precedence and Preemption, Cisco CallManager Features and Services Guide
•Resource Reservation Protocol, Cisco CallManager System Guide
Music On Hold
The Music On Hold (MOH) feature supports call admission control that Resource Reservation Protocol (RSVP) provides.
Cisco CallManager supports RSVP for unicast MOH server. If RSVP policy is mandatory for the connection between an MOH server and the held party, Cisco CallManager provides tone on hold when RSVP reservation fails.
Cisco CallManager only allocates RSVP Agent for the calling/called devices, unicast MOH, and Annunciator. No RSVP Agent gets allocated for MTP or transcoder devices even if these devices are in the difference location from the endpoint. At most, one pair of RSVP agents per call exists.
Music On Hold interacts with RSVP by following the interlocation RSVP policy that was established for the location of the held party and the location of the MOH server.
This release includes the following enhancements to the Media Streaming Application service:
•MTP support for RFC2833 pass through control by Cisco CallManager with revised SCCP
•Configuration settings for MTP RFC2833 DTMF duration and power
•Configuration settings for MOH multicast RTP streams
This release includes the following enhancement to Cisco CallManager:
Cisco CallManager turns off Music on Hold streaming into a conference when a member of the conference puts the device on hold. This capability gets implemented on the SIP trunk for interoperability with Cisco Meeting Place.
Cisco CallManager Administration Configuration Tips
In Release 5.0 of Cisco CallManager, the Music On Hold (MOH) feature includes the following configuration differences:
•The administrator must import the audio source file to the MOH server in each cluster prior to assigning an audio source number to the audio source file.
•The Music On Hold Audio Source Configuration window uploads audio source files only to a particular server. The window does not provide for automatic copying of audio source files to any other servers. You must manually upload audio source files to subscriber servers by accessing the Cisco CallManager application on each server.
•The Music On Hold feature does not support the MP3 format.
•In previous releases, Cisco CallManager did not limit the amount of space that MOH files used. The MOH upload tool does not limit the number of uploaded files or the file size. The modified upload JSP pages check the disk usage of existing MOH files and only permit uploads if sufficient space is found.
•Cisco CallManager supports up to five MOH audio sources on 36- or 40-gigabyte disk-based systems. Systems with 72- or 80-gigabyte disks support the entire 50 audio streams. To increase the number of audio sources that Cisco CallManager supports, install a larger disk during upgrade.
•Administrators can neither add nor delete Music On Hold servers. Administrators can only modify MOH servers that get configured upon installation of Cisco CallManager software.
•The Media Resources menu includes the MOH Audio File Management menu option. Use this menu option to upload or delete Music On Hold audio source files.
GUI Changes
The Music On Hold configuration options moved from the Service > Media Resource menu to the Media Resources menu. Use the following menu options to configure the Music On Hold service:
•Media Resources > Music On Hold Audio Source
•Media Resources > Fixed MOH Audio Source
•Media Resources > Music On Hold Server
•Media Resources > MOH Audio File Management
User Tips
If an endpoint is connected to a multicast MOH server, no need for RSVP reservation exists.
Where to Find More Information
•Music On Hold, Cisco CallManager Features and Services Guide
•Resource Reservation Protocol, Cisco CallManager System Guide
Quality Report Tool
The Quality Report Tool (QRT), a voice-quality and general problem-reporting tool for Cisco IP Phones, acts as a service that allows users to easily and accurately report audio and other general problems with their IP phone. QRT automatically loads with the Cisco CallManager installation, and the Cisco Extended Functions (CEF) service supports it.
Cisco CallManager Administration Configuration Tips
The following section comprises the tips and information for configuring QRT.
SIP Support for QRT
QRT supports Cisco IP Phones 7911, 7941G, 7941G-GE, 7961G, 7961G-GE, and 7971 for SIP.
A SIP phone that is configured to use UDP as the transport, instead of TCP, will not support the device data pass-through functionality. QRT requires the pass-through functionality, so QRT does not support these UDP-configured SIP phones.
New QRT Report Fields
Two new fields exist in the QRT report:
•sProtocol—This field represents the protocol for the source phones.
•dProtocol—This field represents the protocol for the destination phones.
The actual names of the phone models replace some phone model names in the QRT report fields. For example, in previous releases, for the Source Model field, the description for an SCCP phone model was 20. In Release 5.0, the actual corresponding model name SCCP Phone is used.
This change affects the following report fields:
•Source Model
•Source Product
•Destination Model
•Destination Product
•CallState
Security Considerations
QRT now supports a secure Transport Layer Security (TLS) connection to CTI. You can obtain the secure connection by using the CCMQRTSecureSysUser application user.
If you enable security from the service parameters window, the QRT will open a secure connection to CTI Manager by using the Application CAPF profile. You should configure both the CTI Manager Connection Security Flag and the CAPF Profile Instance Id for Secure Connection to CTI Manager service parameters for the secure connection to succeed.
You must also configure the security service parameter Cluster Security Mode, from System > Enterprise Parameters in Cisco CallManager Administration, to secure a TLS connection to CTI, giving it a value of 1. This value indicates secure mode. Because this parameter is read-only, to change the cluster security mode, you must run the CTL Client plugin. You can do this from Application > Plugins in Cisco CallManager Administration.
Refer to the Cisco CallManager Features and Services Guide and Cisco CallManager Administration Guide for more information.
Where to Find More Information
•Cisco CallManager Features and Services Guide
•Cisco CallManager Administration Guide
•Cisco CallManager System Guide
Bulk Administration Tool Features
Cisco CallManager Bulk Administration (BAT), a web-based application, performs bulk transactions to the Cisco CallManager database. This section introduces the changes to BAT for Cisco CallManager 5.0.
Installation Considerations
BAT installs as part of Cisco CallManager Administration. Refer to Cisco CallManager Administration Guide for more details.
New and Changed Information for BAT
The menu structure in BAT changed to align with Cisco CallManager Administration menu. Cisco CallManager Administration includes Bulk Administration, a new menu.
See the "GUI Changes" section, for more information.
The following changes in BAT apply for Cisco CallManager 5.0.
•BAT supports bulk provisioning of all phone data, including support for SIP features for phones. The migration tool handles bulk provisioning for upgrade purposes.
•Additions and changes to Cisco CallManager administration and serviceability tools remain consistent with the existing look and feel of Cisco CallManager Administration.
•BAT accepts bulk provisioning data in a format that can be created and viewed by common enterprise desktop applications like Microsoft Excel.
•The SCCP to SIP Phone Migration Tool allows you to select phones, and update protocol from . To change the default values that are set during migration, use the Update Phones menu option in the Bulk Administration menu, after migration. Values for the migration tool in BAT from SCCP to SIP come from the phone template. Make sure that you reset the phones that you migrate from SCCP to SIP by using Bulk Administration > Phones > Reset/Restart Phones > Query. For more information about resetting phones, see Cisco CallManager Bulk Administration Guide
•BAT supports job scheduling to submit a job, like inserting phones, to the Bulk Provisioning Service (BPS). You can choose to run this job immediately or at a later time and date that you specify. This helps improve system performance during peak hours.
•BAT provides a template for common user settings.
•BAT provides a menu option to upload comma separated value (CSV) files from the client machine to Cisco CallManager server with active BPS and to download reports, bat excel template, exported files, and log files that are generated through BAT from the server hosting the active BPS to the client machine.
•Log files and trace files for BPS transactions get collected using the trace and log central feature. The trace level (like info, debug, error, and so on) information gets set by using the Cisco CallManager Serviceability for each service including BPS. Appropriate traces get written in the trace files based on the setting.
BAT Configuration Tips
The Bulk Administration Tool installs with Cisco CallManager, so requirement for plugins no longer exists.
GUI Changes
Cisco CallManager Administration includes a menu item called Bulk Administration. The following menu items, which display under Bulk Administration, previously displayed under the Configure menu:
•Phones
•Users
•Phones and Users (new)
•Managers/Assistants
•User Device Profiles
•Gateways
•Forced Authorization Codes
•Client Matter Codes
•Call Pickup Groups
•Job Scheduler (new)
•Upload/Download Files (new)
Service Parameter Changes
The following two service parameters exist for the Bulk Provisioning Service (BPS) for BAT:
•Stop Job Processing(Read-Only) — This required parameter, if set to true, stops bulk job processing. To start processing, change this value to false. You can set this value from Job Scheduling window from the Cisco CallManager Bulk Administration Menu.
•Default Job Processing Option—Default option for BPS Job processing. Select this option by default whenever you are ready to submit a job. You can change the selection for this required filed before submitting the job.
•Default Job Processing Time (HH.MM)—Default scheduled time for transactions. This is not a required field.
•Log File Location(Read-Only) —Location for Bulk Processing Log files. Log files for all jobs will be written here.
Serviceability Considerations
The following enhancements occur in Serviceability for BAT:
•Serviceability provides an option to activate/deactivate BPS on a Cisco CallManager server that is designated as the first node in cluster.
•BAT transaction traces get stored with the traces for the other Cisco CallManager applications. You can turn the traces on or off using Cisco CallManager Serviceability.
Security Considerations
BAT now implements Multilevel Administration. Restricted access to BAT administration windows occurs based on the permissions to the users or groups of which they are part.
BAT Performance
Table 3 lists the performance values for various BAT transactions.
Note The following performance data occurs at laboratory conditions, and this data can change depending on Cisco CallManager activity. These are off-peak hour numbers and only provide an approximate guidance to judge the overall time for transaction.
Table 3 BAT Performance Measures for Various Transactions
Transaction
|
Records Processed/Minute
|
Forced Authorization Codes
|
Insert FAC
|
200
|
Delete FAC
|
500
|
Client Matter Codes
|
Insert CMC
|
250
|
Delete CMC
|
500
|
Call Pickup Groups
|
Insert CPG
|
200
|
Delete CPG
|
500
|
Phones/Users
|
Validate Phones/Users
|
100
|
Insert Phones/Users
|
15
|
Users
|
Insert Users
|
150
|
Update Users
|
65
|
Reset Password/PIN query
|
500
|
Reset Password/PIN Custom
|
350
|
Generate User reports
|
500
|
Export Users - Specific
|
250
|
Export Users - All
|
200
|
Delete Users - Query
|
300
|
Delete Users - Custom
|
300
|
Manager Assistants
|
Manager/Assistant Insert
|
75
|
Manager/Assistant CSV Based Delete
|
300
|
Manager/Assistant Query based Delete
|
300
|
Manager/Assistant Custom file based delete
|
300
|
UDP Transactions
|
Validate UDP
|
300
|
Insert UDP specific details
|
65
|
Export All Details
|
50
|
Add lines UDP
|
75
|
Report UDP
|
125
|
Delete UDP
|
70
|
Phone Transactions
|
Validate Phones
|
250
|
Insert Specific Phones
|
45
|
Export All Details
|
75
|
Update Phones
|
150
|
Add lines for Phones
|
75
|
Reset/Restart Phones
|
500
|
Generate Phone Reports
|
300
|
Delete Phones (Query)
|
75
|
TAPS Features
The Tool for Auto-Registered Phone Support (TAPS) application enables phone users to call the TAPS directory number and download the preconfigured phone settings for the users directory number.
Installation Considerations
TAPS gets installed on Cisco CallManager first node, as part of Cisco CallManager Administration installation. For more details, refer to Cisco CallManager Administration Guide. For TAPS to function, you must enable auto-registration in Cisco CallManager Serviceability.
You must install TAPS application on Cisco Customer Response Solutions (Cisco CRS) server. You can download TAPS installable for the Cisco CRS by choosing Menu > Applications > Plugins from Cisco CallManager Administration.
For more details about installing TAPS on Cisco CRS, refer to Cisco CallManager Bulk Administration Guide.
TAPS Configuration Tips
TAPS requires the Cisco IP Interactive Voice Response (IP IVR) application that runs on the Cisco CRS server for the user interface and prompts.
GUI Changes
The TAPS submenu in Bulk Administration includes the following menu options.
•Secure TAPS
•User Locales for TAPS
•View TAPS Log File
Service Parameter Changes
Two new service parameters exist for TAPS for Cisco CallManager 5.0. For more information on service parameters and how to view and modify them, refer to Cisco CallManager Administration Guide.
•Auto-Registration Options for TAPS—Choose Allow Auto-Registered phones to reset with a profile with a dummy MAC address or Allow Auto-Registered phones with any profile.
•Log File Location—Location for TAPS log files. Log files for all TAPS transactions will be written in this required field. Maximum length: 255.
Serviceability Considerations
The following enhancements exist in Serviceability for TAPS:
•Serviceability provides an option to activate/deactivate Cisco TAPS service on a Cisco CallManager server that is designated as the first node in cluster.
•TAP transaction traces get stored with the traces for the other Cisco CallManager applications. You can turn the traces on or off by using Cisco CallManager Serviceability.
Security Considerations
TAPS now implements Multilevel Administration. Restricted access to TAPS administration windows occurs based on the permissions to the users or groups of which they are part.
Where to Find More Information
•Cisco CallManager Bulk Administration Guide
•Cisco CallManager Administration Guide
•Cisco CallManager Serviceability Administration Guide 5.0
Security Features
Cisco CallManager 5.0 supports the following security features:
•Security profiles—Cisco CallManager Administration groups security-related settings into profiles, so you can apply all settings to a SIP phone, SIP trunk, or SCCP profile when you apply a profile to the device.
•Encrypted phone configuration files—After you configure security-related settings, the phone configuration file contains sensitive configuration information, such as digest authentication passwords and phone administrator passwords. To ensure privacy of the configuration file during download, you must configure the configuration files for encryption.
•H.323/H.245/H.225 gateway and trunk encryption—Cisco CallManager 5.0 allows you to encrypt the media streams between Cisco CallManager and the H.323/H.245/H.225 gateway and trunk.
•Digest authentication—This process, which is used for SIP trunks and SIP phones, allows Cisco CallManager to challenge the identity of the SIP user agent (UA) when the UA sends a request to Cisco CallManager.
•SIP trunk-based authorization—For SIP trunks, Cisco CallManager provides authorization of Presence requests and certain non-INVITE SIP messages from the SIP trunk or SIP trunk application user; for example, out-of-dial REFER, unsolicited notification, and any SIP request with the replaces header.
Authorization occurs for the trunk first and then for the SIP trunk application user when you configure both the SIP trunk and the application for authorization in Cisco CallManager Administration. Before authorization for the application can occur, Cisco CallManager authenticates the application with digest authentication.
•Presence group authorization—Cisco CallManager allows you to configure presence groups to control the destinations that watchers can monitor. Refer to the "Presence" section for additional details.
•JTAPI/TAPI/CTI application security—Cisco CallManager 5.0 allows you to secure the signaling connections and media streams between CTIManager and CTI/JTAPI/TAPI applications.
•Packet capture—Because third-party troubleshooting tools that sniff media and TCP packets do not work after you enable SRTP encryption, you must use Cisco CallManager Administration to configure packet capturing.
Cisco CallManager Administration Configuration Tips
Security operations rely on the creation of the Cisco CTL file. Before you perform the following tasks, create the Cisco CTL file and ensure that the cluster security mode equals secure mode.
Security Profiles
After you configure the security profile for the SIP trunk, SIP phone, or SCCP phone (System > Security Profile >...), you apply the profile to the device (Device > Phone or Device > Trunk).
All SIP phones, SCCP phones, and SIP trunks require that you apply a security profile. If the device does not support security, apply a nonsecure profile.
For SIP and SCCP phones, configure the CAPF settings in the profile in conjunction with the Certificate Authority Proxy Function settings that display in the Phone Configuration window.
If you configured the device security mode prior to the Cisco CallManager 5.0 upgrade, Cisco CallManager creates a profile that is based on the mode and applies the profile to the device.
If the device does not support the profile that you configure, Cisco CallManager does not allow you to apply it to the device.
When you configure digest authentication for the SIP phone or SIP trunk, be sure to configure the digest credentials for the application user or end user and apply the end user with configured digest credentials to the phone.
The SCCP phone security profile supports the Cisco Voice Mail Port (Voice Mail > Cisco Voice Mail Port [or Cisco Voice Mail Port Wizard]). When you choose a profile, consider the device security mode and not the CAPF settings from the profile. Cisco CallManager ignores the CAPF settings in the security profile because the settings do not apply to voice mail ports.
Encrypted Phone Configuration Files
In Cisco CallManager Administration, enable the TFTP Encrypted Configuration enterprise parameter (System > Enterprise Parameters). If your phone supports manual key distribution, perform the manual key distribution tasks in Cisco CallManager Administration (Device > Phone). If your phone supports the method, symmetric key encryption with phone public key, verify that a manufacture-installed certificate (MIC) or locally significant certificate (LSC) exists in the phone; reset the phone.
H.323/H.245/H.225 Gateway and Trunk Encryption
Configure IPSec in the network infrastructure or from Cisco CallManager to the gateway/trunk. Check the SRTP Allowed check box in Cisco CallManager Administration (Device > Gateway or Device > Trunk). To support IPSec and encryption on the gateway, perform the necessary tasks on the gateway, as described in the documentation that supports your gateway.
Caution If you do not configure IPSec but you check the SRTP Allowed check box in Cisco CallManager Administration, the SRTP key material gets sent in the clear. Before you check the check box, ensure that you configured IPSec correctly.
SIP Trunk-Based Authorization
Configure the SIP trunk security profile (System > Security Profile > SIP Trunk Security Profile), and check any or all of the following check boxes: Accept Presence Subscription, Accept Out-of-Dialog Refer, Accept Unsolicited Notification, Accept Replaces Header.
If you want application-level authorization to occur after trunk-level authorization, check the Enable Application Level Authorization and Enable Digest Authentication check boxes.
After you configure the SIP trunk security profile, apply the profile to the trunk. Then, for application-level authorization, check the check boxes in the Application User Configuration window (User Management > Application User).
Make sure that you configure digest authentication for the trunk, as described in the "Digest Authentication for SIP Trunks and SIP Phones" section.
Presence Group Authorization
To use presence group authorization, configure presence groups and permissions (System > Presence Groups). For each presence group that you create, you apply the presence group to one or more of following items in Cisco CallManager Administration: directory number, trunk, phone, application user, end user, and autogenerated device profiles.
Digest Authentication for SIP Trunks and SIP Phones
To configure digest authentication for the SIP phone, perform the following tasks:
•Configure the digest credentials in the End User window (User Management > End User). Configure a SIP Phone Security Profile for digest authentication (System > Security Profile > SIP Phone Security Profile) and apply it to the phone (Device > Phone). In the Phone Configuration window, choose that end user from the Digest User drop-down list box. If you are configuring a third-party phone, you must enter the digest credentials on the phone.
To configure digest authentication for the SIP trunk, perform the following tasks:
•Configure a SIP trunk security profile for digest authentication (System > Security Profile > SIP Trunk Security Profile) and apply it to the trunk (Device > Trunk).
•When Cisco CallManager acts as a UAS, configure the Cluster ID enterprise parameter (System > Enterprise Parameters). Configure the digest credentials in the Application User Configuration window (User Management > Application User).
•When Cisco CallManager acts as a UAC, configure the digest credentials in the SIP Realm window (User Management > SIP Realm).
Tip Digest authentication does not provide integrity or confidentiality. To ensure integrity and confidentiality for the device, configure the TLS protocol for the device if the device supports TLS. If the device supports encryption, configure the device security mode as encrypted. If the device supports encrypted phone configuration files, configure encryption for the files.
JTAPI/TAPI/CTI Application Security
To ensure that JTAPI/TAPI/CTI applications connect securely to the CTIManager, you must configure the Application User CAPF Profile (User Management > Application User CAPF Profile).
To ensure that a service connects securely to the client, you must configure the End User CAPF Profile for each instance of the application that runs on a PC (User Management > End User CAPF Profile).
To ensure that an application or end user supports authentication and media encryption (SRTP), you must add the user to the Standard CTI Secure Connection and the Standard CTI Allow Reception of SRTP Key Material user groups (User Management > User Group).
Tip Before the application and end user can use SRTP, verify that the user exists in the Standard CTI Enabled and Standard CTI Secure Connection user group, which serves as a baseline configuration for TLS and SRTP connections. After you add the user to this group, you can add the user to the Standard CTI Allow Reception of SRTP Key Material user group. The application and end user cannot use SRTP if it does not exist in these three groups.
Packet Capturing
In Cisco CallManager Administration, configure the TLS packet capture service parameters for the Cisco CallManager service (System > Service Parameters) to capture packets for TLS connections between Cisco CallManager and a device (Cisco IP Phone, Cisco SIP IP Phone, SIP trunk, Cisco IOS MGCP gateway, H.323 gateway, or H.323/H.245/H.225 trunk). You then specify batch processing mode in the Packet Capture Mode field and the Packet Capture Duration in the device's configuration window in Cisco CallManager Administration.
GUI Changes
The following new and changed windows in Cisco CallManager Administration contain security-related configuration settings:
•SCCP Phone Security Profile Configuration window (new)—Contains the Device Security Mode, Authentication Mode (for CAPF), and the Key Size (for CAPF) settings.
•SIP Phone Security Profile Configuration window (new)—Contains the Device Security Mode, Authentication Mode (for CAPF), the Key Size (for CAPF), Enable Digest Authentication, Nonce Validity Time, Transport Type, and SIP Phone Port settings.
•SIP Trunk Security Profile Configuration window (new)—Contains the Incoming Transport Type, Outgoing Transport Type, Device Security Mode, Enable Digest Authentication, Nonce Validity Time, X.509 Subject Name, Incoming Port, Enable Application Level Authorization, Accept Presence Subscription, Accept Out-of-Dialog REFER, Accept Unsolicited Notification, and Accept Replaces Header settings.
Tip The Transport Type settings now display in the Security Profile window instead of the SIP Trunk window.
•End User Configuration window (new)—Contains the following new settings for phone digest authentication: Digest Credentials and Confirm Digest Credentials.
•Application User Configuration window (new)—Contains the Accept Presence Subscription, Accept Out-of-Dialog REFER, Accept Unsolicited Notification, Accept Replaces Header, and Associated CAPF settings, as well as the following new settings for application digest authentication: Digest Credentials and Confirm Digest Credentials.
•User Group Configuration window (new)—Contains the following new settings for configuring TLS and encryption for JTAPI/TAPI/CTI applications: Standard CTI Secure Connection and Standard CTI Allow Reception of SRTP Key Material.
•Application User CAPF Profile Configuration window (new)—Allows you to install and upgrade locally significant certificates for JTAPI/TAPI applications; all settings in this window relate to security.
•End User CAPF Profile Configuration window (new)—Allows you to install and upgrade locally significant certificates for JTAPI/TAPI applications; all settings in this window relate to security.
•SIP Realm window (new)—Supports SIP trunk digest authentication; all settings in this window relate to security.
•Cisco CallManager window (changed)—Contains the following new setting: SIP Phone Security Port. Update this setting only if the port number is in use, or if you use a firewall and you cannot use the port within the firewall.
•Cisco Voice Mail Port window (changed)—Contains the SCCP Phone Security Profile setting where you can apply an authenticated, encrypted, or nonsecure security profile to the port.
Tip The Device Security Mode setting now displays in the SCCP Phone Security Profile window instead of the Cisco Voice Mail Port window and in the Cisco Voice Mail Port Wizard.
•Cisco Voice Mail Port Wizard (changed)—Contains the SCCP Phone Security Profile setting where you can apply an authenticated, encrypted, or nonsecure security profile to the port.
Tip The Device Security Mode setting no longer displays in this window. You configure the Device Security Mode setting in the SCCP Phone Security Profile.
•Phone Configuration window (changed)—Contains the following security-related settings:
–SIP Phone Security Profile (or SCCP Phone Security Profile)—After you configure a security profile (System > Security Profile >...), you apply it to the device in this window.
–Digest User, SIP phone only (new)—For this setting that is used for digest authentication, you choose the digest user, an end user, for a phone after you configure the digest credentials in the End User window. (Consider this field a required field for third-party SIP phones.)
–Certificate Authority Proxy Function (not all phone types)—You configure the Certificate Operation, Authentication String, Generate String, Operation Completes By, and Certificate Operation Status settings in conjunction with the CAPF settings that display in the SIP Phone or SCCP Phone Security Profile windows.
–Symmetric Key, Generate Symmetric Key, and Revert to Database Value (not all phone types)—These settings allow you to configure encrypted phone configuration files.
–Packet Capture Mode and Packet Capture Duration—If the phone supports packet capturing, the Packet Capture Mode and Packet Capture Duration display to allow you to capture packets in batch mode.
Tip The Device Security Mode, Authentication Mode, and Key Size settings no longer display in the Phone Configuration window. You configure these settings in the SIP Phone or SCCP Phone Security Profile windows.
•SIP Trunk Configuration window (changed)—Contains the SIP Trunk Security Profile setting where you choose a profile for the device and the Packet Capture Mode and Packet Capture Duration settings, which are used if you need to troubleshoot encryption for the trunk.
•H.225 Trunk Configuration window (changed)—Contains the SRTP Allowed check box and the Packet Capture Mode and Packet Capture Duration settings, which are used if you need to troubleshoot encryption for the trunk.
•Inter-Cluster Trunk Configuration (Gatekeeper-Controlled) window (changed)—Contains the SRTP Allowed check box and the Packet Capture Mode and Packet Capture Duration settings, which are used if you need to troubleshoot encryption for the trunk.
•Inter-Cluster Trunk Configuration (Non Gatekeeper-Controlled) window (changed)—Contains the SRTP Allowed check box and the Packet Capture Mode and Packet Capture Duration settings, which are used if you need to troubleshoot encryption for the trunk.
•H.323 Gateway Configuration window (changed)—Contains the SRTP Allowed check box and the Packet Capture Mode and Packet Capture Duration settings, which are used if you need to troubleshoot encryption for the trunk.
•User Group Configuration window (changed)—Contains the Standard CTI Secure Connection, Standard CTI Allow Reception of SRTP Key Material, and Standard Packet Sniffer User groups that are provided by default; allows you to assign end users and applications users to these groups.
•Role Configuration window (new)—Contains the Enable CTI Security and Enable CTI SRTP Key Distribution settings for a CTI application.
New Service and Enterprise Parameters
•TFTP Encrypted Configuration—This enterprise parameter specifies whether encryption is enabled for TFTP download. Restart all services for the parameter change to take effect.
•CAPF Profile Instance ID for Secure Connection to CTIManager—Used with the Cisco WebDialer Web and Cisco IP Manager Assistant (IPMA) services, this parameter specifies the Instance ID of the application users, WDSecureSysUser and IPMASecureSysUser, that this Cisco WebDialer or Cisco IPMA server uses to open a connection to CTIManager. You must configure this parameter if you enable the CTI Manager Connection Security Flag parameter. You must restart the Cisco IPMA or the Cisco WebDialer service for the changes to this parameter to take effect.
•CTIManager Connection Security Flag—The CTIManager Connection Security Flag service parameter indicates whether security is enabled for the CTIManager connection to the Cisco IPMA or Cisco WebDialer service. If enabled, Cisco IPMA or Cisco WebDialer opens a secure connection to CTIManager by using the Application CAPF profile that is configured for the Instance ID for the application user. You must restart the Cisco IPMA or the Cisco WebDialer service for the changes to this parameter to take effect.
•Cluster ID—This parameter provides a unique identifier for this cluster. This parameter serves as the realm in digest authentication when Cisco CallManager challenges a trunk device. Because this parameter gets used in CDRs, you can trace collections of CDRs from multiple clusters to the source.
•SIP Realm—This service parameter for Cisco CallManager specifies the string that is used in the realm field when Cisco CallManager responds to challenges from a trunk device in digest authentication.
•SIP Station Realm—This service parameter for Cisco CallManager specifies the string that is used in the realm field when Cisco CallManager challenges a SIP phone in digest authentication.
•Packet Capture Enable—This service parameter for Cisco CallManager determines whether Cisco CallManager captures packets that are sent or received over TLS connections.
•Packet Capture Max File Size (MB)—This service parameter for Cisco CallManager specifies the maximum size of each packet capture file created by Cisco CallManager for batch mode debugging.
Removed or Changed Service or Enterprise Parameters
The Device Security Mode enterprise parameter no longer exists. Instead, use the SCCP or SIP phone security profiles to configure and apply the device security mode to many devices at the same time.
Serviceability Considerations
After you configure the service parameters for JTAPI/TAPI/CTI security, you must restart the corresponding services.
Where to Find More Information
•Cisco CallManager Security Guide
New and Changed Information for Cisco CallManager Serviceability
Cisco CallManager Release 5.0 provides the following enhancements to Serviceability:
•Serviceability Administration
•Real-Time Monitoring Tool
•Trace & Log Central
•SysLog Viewer
•CDR Analysis and Reporting (CAR)
•Where to Find More Information
Serviceability Administration
The Cisco CallManager Serviceability Administration windows allow you to perform such tasks as configuring trace parameters, configuring alarms, and activating, starting, and stopping services.
GUI Changes
The Cisco CallManager Serviceability GUI contains the following changes for this release:
•The system allows you to start and stop services on different Control Center windows, depending on the service type: features services and network services. Feature services allow you to use Cisco CallManager related features. You can start and stop feature services on the Control Center-Feature services window. The system does not automatically activate these services when a new installation occurs. You must activate them on the Service Activation window. If you have upgraded your system, those services that you activated on the system prior to the upgrade automatically activate and start after the upgrade. You need network services for your system to function. Because these services are required for basic Cisco CallManager functionality, you cannot activate them in the Service Activation window. You can start and stop these services in the Control Center-Network Services window.
•Cisco CallManager Serviceability contains a new SNMP Configuration menu that allows you to configure SNMP community strings, users, and notification destinations for SNMP versions 1, 2c, and 3. You can apply configurations to a single server or to all servers in the cluster. Previously, you had to configure SNMP in the Microsoft Windows SNMP service properties dialog box on each server in the cluster.
•Cisco CallManager Serviceability contains a new mechanism for managing and delivering call detail records (CDR) and call management records (CMR). The CDR Management Configuration window allows you to set the amount of disk space allocated to call detail record (CDR) and call management record (CMR) files, configure the number of days to preserve files before deletion, and configure up to three billing application server destinations for CDR delivery. The CDR repository manager service repeatedly attempts to deliver CDR and CMR files to the billing servers that you configure on the CDR Management Configuration window until it delivers the files successfully, until you change or delete the billing application server on the CDR Management Configuration window, or until the files fall outside the preservation window and are deleted. You must use the CDR Management feature to move CDR/CMR files to your billing server(s). To access, choose Tools > CDR Management.
•The Alarm Configuration window (Alarm > Alarm Configuration) contains new check boxes: Local Syslog and Remote Syslog. The Local Syslog check box allows you to store syslog messages locally on Cisco CallManager. You view the messages by using the SysLog viewer in RTMT or by using the CLI. The Remote Syslog check box allows you to send syslog messages to be stored on a Syslog server that you specify.
•The trace output setting options on the Trace Configuration window (Trace > Configuration) have changed. Available options include maximum number of files and maximum file size. The defaults for the options vary depending on the service.
•The Trace Analysis Configuration window has been removed. The system does not support XML tracing.
•The Tools > RTMT menu option has been deleted. To download the RTMT plug-in, use the Find and List Plugins window (Application > Plugins) in Cisco CallManager Administration.
•The Q931 Translator is obsolete and the Q931 Translator window has been removed from Cisco CallManager Serviceability.
•The QRT viewer has been removed from Cisco CallManager Serviceability and incorporated into RTMT.
•The Cisco Serviceability Reporter service generates a new report that is called the Performance Protection Report, which provides trend analysis information on default monitoring objects that allows you to track overall system health. The report includes information for the for the last 7 days for each server. The report contains three graphs and one table. The three graphs contain data that the AMC service collects, and the report collects the table information from the Cisco CallManager database.
•The system contains new precanned alerts in Alert Central.
Administration Configuration Tips
•If you are upgrading to Cisco CallManager 5.0, you must enter SNMP configurations through the new SNMP Configuration menu in Cisco CallManager Serviceability. The system does not migrate SNMP Configuration settings from the Microsoft Windows SNMP service properties dialog box.
•Because the Serviceability Reporter service is CPU intensive, Cisco recommends that you activate the service on a non call-processing server.
•When you change either the Maximum No. of Files or Maximum File Size field on the Trace Configuration window, the system deletes all the service log files except the current file if the service is running, or if the service has not been activated, the system will delete the files when the service is initially activated. If you want to keep a record of the log files, make sure that you download and save the service log files to another server before changing the Maximum No. of Files field or the Maximum File Size field.
Real-Time Monitoring Tool
Cisco CallManager 5.0(1) includes the following enhancements to the Real-time Monitoring Tool (RTMT).
•Cisco provides RTMT versions that run on both Windows and Linux operating systems.
•You can monitor the different processes that are running on the server.
•RTMT includes updated performance monitor counters.
•RTMT provides SIP activity information, such as a summary of SIP requests, SIP responses, total number of failed incoming responses (4xx, 5xx, and 6xx), total number of failed outgoing responses (4xx, 5xx, and 6xx), number of retry request, and number of retry responses.
•RTMT provides Database summary information, such as change notification requests that are queued in the database, the change notification requests that are queued in memory, the total number of active client connections, and the number of devices that are queued for a device reset.
•The phone summary will also provide information on the number of SIP phones and Partially Registered phones, as well as the number of Registered phones, SCCP phones, and the number of failed registration attempts.
•You can initiate a trace download based on the occurrence of an event by checking the TCT Download check box in Alert properties for CriticalServiceDown and CodeYellow alerts.
•With Cisco CallManager 5.0(1), you can monitor the log partition disk space. The Log Partition Monitoring service starts automatically when you install Cisco CallManager. You configure LogPartitionLowWaterMarkExceeded or LogPartitionHighWaterMarkExceeded setting in Alert Central in RTMT. You can configure Cisco CallManager to send an alarm message to syslog or an alert message to alert central when disk space reaches either the LogPartitionLowWaterMarkExceeded or LogPartitionHighWaterMarkExceeded setting. When the disk space reaches the LogPartitionHighWaterMarkExceeded limit that you specify, the system begins deleting files until disk space reaches a configurable lower limit.
•The Trace Collection Tool, which was a separate plug-in for previous releases, has been integrated into RTMT and named Trace & Log Central. For more details, see the "Trace & Log Central" section.
•The SysLog Viewer has been integrated into RTMT. For more details, see the "SysLog Viewer" section.
•With Cisco CallManager 5.0(1), you can expand the functionality of RTMT by installing an application plug-in, such as the Voice Trace Log (VLT) application. You can download the latest plug-ins for the RTMT viewer from Cisco.com.
GUI Changes
•New monitoring categories exist. To access, click the View tab in the Quick Launch Channel and use one of following paths:
–Server > Process
–Call Process > SIP Activity
–Service > Database Summary
•On the Select Phone to Monitor dialog box (Device > Open Device Search > Phone), a new option enables you to search by protocol: SCCP or SIP.
•New trace options exist. To access, click the Tools tab in the Quick Launch Channel and choose Trace. For more details on these options, see the "Trace & Log Central" section.
Administration Configuration Tips
•If the PC on which you are installing RTMT runs on a Linux operating system, make sure that you download the Cisco CM Real-Time Monitoring Tool-Linux plug-in from the Find and List Plugins window in Cisco CallManager Administration. If the PC runs Windows, make sure that you install the Cisco CM Real-Time Monitoring Tool-Windows plug-in.
•If you have previously installed RTMT for use with a Cisco CallManager server that is running Microsoft Windows, you must install RTMT for Cisco CallManager 5.0 in a different folder on your local computer.
•For Log Partition Monitoring, configure the LogPartitionLowWaterMarkExceeded and LogPartitionHighWaterMarkExceeded settings in Alert Central.
•To initiate a trace download based on the occurrence of an event, check the TCT Download check box in Alert properties for CriticalServiceDown and CodeYellow alerts.
Trace & Log Central
In previous releases, the trace collection tools represented a separate plug-in that was available from the Plugin Configuration window in Cisco CallManager. The trace collection tool allowed you to collect, view, and zip various Cisco CallManager service traces and/or other Cisco CallManager log files. In this release, the trace collection tool was integrated into the real-time monitoring tool (RTMT) client-side plug-in, enhanced to include more trace collection options, and named trace and log central.
GUI Changes
Administrators can access the trace collection option by installing RTMT on their PC and performing one of the following tasks:
•In the Quick Launch Channel, click the Tools tab; then, click Trace and the Trace & Log Central icon.
•Choose Tools > Trace Collection > Trace & Log Central.
The trace collection option contains the following new features:
•Remote Browse—After the system generates trace files, you can view them on the server by using the viewers within the RTMT. You can also use the remote browse feature to download the traces to your PC.
•Collect Files—This feature collects and downloads traces for services, applications, and system logs on one or more servers in the cluster for an absolute date and time range (such as between July 8, 2005 at 12:30 and August 8, 2005 at 12:30) or for a relative time (such as, within the last 30 minutes).
•Query Wizard—This feature collects trace files for services, applications, and system logs for an absolute or relative time range that contains text strings that you specify. You can view the collected trace file and/or download the trace files to your PC. You can also save the trace collection query criteria for later use. If you save the query as a regular query, you can only run the query on the node on which it was created. If you save the query as a generic query, you can run it on any node in any cluster.
•Schedule Collection—This feature schedules a recurring trace collection and allows users to perform a specified action, including run another query, generate a syslog, or download the trace files on a SFTP server.
•Local Browse—After you collect trace files and download them to your PC, you can view them with a text editor that can handle UNIX variant line terminators such as WordPad on your PC, or you can view them by using the viewers within the RTMT.
•Collect Crash Dump—This feature collects a crash dump file for one or more servers on your network.
•Real Time Trace—This feature comprises two options: view real-time data and monitor user events. The view real-time data option allows you to view the current trace file that is being written on the server for an application. The monitor user event option enables the system to monitor real-time trace files and perform a specified action when a search string displays in the trace file. Actions include generating an alert, generating local or remote syslogs, or downloading trace files via SFTP.
•Job Status—This feature allows you to view the status of the trace collection jobs that are running on the system as well as recently processed jobs and to delete currently running or pending jobs. To access, perform one of the following tasks:
–In the Quick Launch Channel, click the Tools tab; then, click Trace and the Job Status icon.
–Choose Tools > Trace Collection > Job Status.
Using the available collection methods, you can perform the following functions:
•Collect trace files that contain text that you specify in the Search String field.
•Delete the trace files on the server by checking the Delete Collected Log Files from the server check box.
•Collect traces based on absolute or relative time.
Administration Configuration Tips
Consider the following tips when you are using the trace and log central option in RTMT:
•If you collect traces for the same services in multiple clusters, you can create a generic query that you can run. You can only run regular queries on the node on which it was created.
•You can automatically capture traces when a particular event occurs by checking the Enable trace collection Download check box in Set Alert/Properties for the CriticalServiceDown and CodeYellow alerts.
•The system supports Log4j traces for Java applications.
SysLog Viewer
The SysLog Viewer has been integrated into the RTMT and allows you to view messages in system logs, application logs, and security logs. It contains the following capabilities:
•Sort messages in ascending or descending order.
•Filter results based on a set of selected options.
•Search for a particular string in the current log.
•Save the currently selected log to your local computer.
GUI Changes
A new option in RTMT allows you to access the SysLog Viewer.
Administration Configuration Tips
Choose one of the following methods to access the SysLog Viewer:
•In the Quick Launch Channel in RTMT, click the Tools tab; then, click SysLog Viewer and the SysLog Viewer icon.
•In the RTMT menu, choose Tools > SysLog Viewer> Open SysLog Viewer.
CDR Analysis and Reporting (CAR)
The CDR Analysis and Reporting (CAR) application generates reports for calls on the basis of CDRs and CMRs. For this release, the following changes apply to CAR:
•Administrators access CAR by activating CAR services rather than by installing a plug-in and grant administrator rights through the User Group Configuration window in Cisco CallManager rather than through the Grant/Revoke CAR Admin Rights window in CAR. You must configure the CAR administrator as an end user, rather than as an application user.
•CAR supports Internet Explorer 6.0 (and above) and Netscape 7.1 (and above). CAR reports support double-byte characters.
•Because Cisco CallManager stores CDRs in flat files rather than a CDR database in this release, the system loads the CAR database from CDR flat files. You can reload all CDRs into the CAR database by using a new option on the Manual Database Purge window. You can enable the system to delete CAR database records when the database size reaches the high water mark that you configure.
•CAR reports support new features. Some report options have been removed.
•You can collect traces for CAR by using the trace and log central feature in RTMT.
•CAR only migrates the first 2 million CDR that it finds in the old CAR database. CDR records beyond that will be lost. Be sure that you have less than 2 million CDRs by checking the number of CDRs in both tbl_billing_data and tbl_billling_error. If it exceeds 2 million records, then you must manually purge the number of CDRs until you have less than 2 million records.
GUI Changes
The CAR GUI contains the following changes for this release:
•The following windows and reports have been removed: Grant/Revoke CAR Admin Rights window, Error Log window, CDR Database Alert window, Control Center window, and CTI Users report.
•The CDR option has been removed from the Manual Purge window and Configure Automatic Purge window.
•The CDR Search reports contain a new field to support the K factor feature.
•The Reload All Call Detail Records has been added to the Manual Database Purge window so that the administrator can delete the data in the CAR database and reload the CDRs from flat files into the database.
•The CAR reports support double byte languages.
Administration Configuration Tips
Use the following tips to configure and use CAR:
•To activate CAR, activate the Cisco CAR Scheduler and Cisco CAR Web Service on the first node by using the Service Activation window in Cisco CallManager Serviceability. You no longer install a plug-in as you did in previous releases. If you are using a third-party billing application that accesses CDR data via an HTTPS/SOAP interface, activate the Cisco SOAP-CDROnDemand service.
•To grant administrative privileges for CAR, add users to the Standard CAR Admin Users group on the User Group Configuration window in Cisco CallManager Administration (User Management > User Group). The Grant/Revoke CAR Admin Rights window no longer exists.
•The CAR database can hold up to 6 gigabytes of data. You can control the amount of data in the CAR database by configuring a high water mark and low water mark on the Automatic Purge Configuration window (System > Database > Configure Automatic Purge). If you do not check the Disable CAR Purge check box, the system deletes records that are older than the number of days that you specify when the database size reaches the high water mark. The system continues to delete records until the database size reaches the low water mark. By default, the low water mark equals 80 percent, the high water mark equals 90 percent, and the deletion age equals 180 days. The system no longer deletes records based only on age.
•You can delete the data in the CAR database and reload the CDRs from flat files into the database by clicking the Reload All Call Detail Records button on the Manual Database Purge window. You may want to reload the CAR database if you want to reclassify calls after dial-plan updates, user-device association changes, call rate changes, and so on. Performing this task may impact system performance. You can monitor the reload process by generating the CDR Load event log (System > Log Screens > Event Log).
•The CAR database loads from CDR flat files. The CDR Export function exports data from the CAR database rather than the CDR database, because the CDR database no longer exists.
•The Call Type field in the CDR Search reports displays new call types to support SIP features: refer, replaces, pickups, and redirection.
•CAR supports Log4j tracing, error logging, and Cisco CAR Scheduler logs. To set trace parameters for the Cisco CAR Web Service, use the Trace Configuration window in Cisco CallManager Serviceability. To collect traces on the Cisco CAR Web Service, use the trace and log central feature of RTMT.
Where to Find More Information
•CDR Analysis and Reporting Administration Guide
•Cisco CallManager Serviceability Administration Guide
•Cisco CallManager Serviceability System Guide
New and Changed Information for Cisco IP Phones
These phone models are supported on Cisco CallManager Release 5.0(1) with SCCP or SIP protocols:
•Cisco IP Phones 7970G and Cisco IP Phone 7971G-GE
•Cisco IP Phones 7961G and Cisco IP Phone 7961G-GE
•Cisco IP Phones 7941G and Cisco IP Phone 7941G-GE
•Cisco IP Phones 7960G and Cisco IP Phone 7940G
•Cisco IP Phones 7912G and Cisco IP Phone 7905G
•Cisco IP Phones 7911G
Note The following phones operate with Cisco CallManager 5.0(1); however, they do not support new Cisco CallManager 5.0(1) features: Cisco IP Phones 7985G, 7936, 7935, 7920, 7902G, Cisco Gateway VG248, and Cisco ATA 186 and 188.
This section contains the following topics:
•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
•Cisco IP Phones 7911G, 7941G, 7941G-GE, 7961G, 7961G-GE, 7970G, 7971G-GE
•Cisco IP Phones 7940G and 7960G
•Cisco IP Phones 7905G and 7912G
Cisco IP Phone Feature Differences by Protocol
This section provides information about feature support for Cisco IP Phones that support SCCP and SIP with Cisco CallManager Release 5.0(1).
Note This is not a complete list of the Cisco IP Phones that are compatible with Cisco CallManager Release 5.0(1). This information focuses solely on those phones that support SCCP and SIP with this release.
•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
–Cisco IP Phones 7911G, 7941G, 7941G-GE, 7961G, 7961G-GE, 7970G, 7971G-GE
–Cisco IP Phones 7940G and 7960G
–Cisco IP Phones 7905G and 7912G
Supported Cisco IP Phones Using the SIP Protocol
In addition to existing SCCP support, Cisco CallManager Release 5.0(1) introduces native SIP support for most Cisco IP Phone models. You can now choose the protocol with which these phones connect and interact with Cisco CallManager.
These phone models are supported on Cisco CallManager Release 5.0(1) with SCCP and SIP protocols and with varying levels of feature support:
•Cisco IP Phones 7970G and Cisco IP Phone 7971G-GE
•Cisco IP Phones 7961G and Cisco IP Phone 7961G-GE
•Cisco IP Phones 7941G and Cisco IP Phone 7941G-GE
•Cisco IP Phones 7960G and Cisco IP Phone 7940G
•Cisco IP Phones 7912G and Cisco IP Phone 7905G
•Cisco IP Phones 7911G
New Features Supported by Cisco CallManager Release 5.0(1)
Cisco CallManager Release 5.0(1) supports these new features:
•Busy Lamp Field (BLF) Call Lists (Presence)
•Busy Lamp Field (BLF) Speed Dial (Presence)
•Do Not Disturb
•Personal Directory Enhancements
•Voice Quality Metrics
•URL Dialing
Some of these new features require configuration changes on Cisco CallManager while others only require new firmware updates to the phones. Not all of these features are available on all phone platforms and protocols. For details about feature support per phone model and protocol, see the "Feature Support Listed by Phone Model and Protocol" section.
Feature Support Listed by Phone Model and Protocol
Although Cisco CallManager Release 5.0(1) provides native SIP support for many Cisco IP Phone models, the phones support different features depending on which protocol is implemented. These sections provide information about feature support differences between SCCP and SIP:
•Cisco IP Phones 7911G, 7941G, 7941G-GE, 7961G, 7961G-GE, 7970G, 7971G-GE
•Cisco IP Phones 7940G and 7960G
•Cisco IP Phones 7905G and 7912G
These sections focus on end-user features. Descriptions of existing end-user features are available in the Cisco IP Phone Features A - Z guide which is available online at:
http://www.cisco.com/univercd/cc/td/doc/product/voice/c_ipphon/english/ipp7960/az_user.htm
For descriptions about the new end-user and administrative features (including security features), refer to the "Cisco CallManager Administration" section, and the "Security Features" section.
Cisco IP Phones 7911G, 7941G, 7941G-GE, 7961G, 7961G-GE, 7970G, 7971G-GE
In most cases, the Cisco IP Phones 7911G, 7941G, 7941G-GE, 7961G, 7961G-GE, 7970G, 7971G-GE support similar features whether on SCCP or SIP. Table 4 provides a high-level overview of calling features and their support by protocol. This table focuses primarily on end-user calling features and is not intended to represent a comprehensive listing of all available phone features. For details about user interface differences and feature use, refer to the phone guide for your phone model. Specific sections are referenced in the table.
Table 4 Cisco IP Phones 7911G, 7941G, 7941G-GE, 7961G, 7961G-GE, 7970G, 7971G-GE Feature Support by Phone Model and Protocol
Features
|
Cisco IP Phones 7911G, 7941G, 7941G-GE, 7961G, 7961G-GE, 7970G, 7971G-GE
|
For More Information
|
SCCP
|
SIP
|
Calling Features
|
Abbreviated Dialing
|
Supported
|
Supported
|
"Basic Call Handling—Placing a Call: Additional Options"
|
Answer Release
|
Supported
|
Supported
|
|
Auto Answer
|
Supported
|
Supported
|
"Using a Handset, Headset, and Speakerphone—Using Auto Answer"
|
Auto Dial
|
Supported
|
Supported
|
"Basic Call Handling—Placing a Call: Basic Options"
|
Barge (and cBarge)
|
Supported
|
Supported
|
"Advanced Call Handling—Using a Shared Line"
|
Busy Lamp Field (BLF) Call Lists
|
Supported
Not supported on 7911G
|
Supported
Not supported on 7911G
|
"Advanced Call Handling—Determining if Another Line is Busy or Idle"
|
Busy Lamp Field (BLF) Speed Dial
|
Supported
Not supported on 7911G
|
Supported
Not supported on 7911G
|
"Advanced Call Handling—Determining if Another Line is Busy or Idle"
|
Call Back
|
Supported
|
Supported
|
"Basic Call Handling—Placing a Call: Additional Options"
|
Call Forward All
|
Supported
|
Supported
|
"Basic Call Handling—Forwarding All Calls to Another Number"
|
Call Forward Busy
|
Supported
|
Supported
|
Users do not interact with this feature directly. It is configured on Cisco CallManager
|
Call Forward No Answer
|
Supported
|
Supported
|
Users do not interact with this feature directly. It is configured on Cisco CallManager
|
Call Park
|
Supported
|
Supported
|
"Advanced Call Handling—Storing and Receiving Parked Calls"
|
Call Pickup/Group Call Pickup
|
Supported
|
Supported
|
"Advanced Call Handling—Picking Up a Redirected Call on Your Phone"
|
Call Waiting
|
Supported
|
Supported
|
"Basic Call Handling—Answering a Call"
|
Caller ID
|
Supported
|
Supported
|
"An Overview of Your Phone—Understanding Touch Screen Features" or "An Overview of Your Phone—Understanding Phone Screen Features"
|
Client Matter Codes (CMC)
|
Supported
|
—
|
"Basic Call Handling—Placing a Call: Additional Options"
|
Conference
|
Supported
|
Supported
|
"Basic Call Handling—Making Conference Calls"
|
Conference List
|
Supported
|
Supported
|
"Basic Call Handling—Making Conference Calls"
|
Computer Telephony Integration (CTI) Applications
|
Supported
|
Limited Support
|
Users do not interact with this feature directly. It is configured on Cisco CallManager
|
Do Not Disturb (DND)
|
—
|
Supported
|
"Basic Call Handling—Using Do Not Disturb"
|
Distinctive Ring
|
Supported
|
Supported
|
"Using Phone Settings—Customizing Rings and Message Indicators"
|
Extension Mobility
|
Supported
|
Supported
|
"Advanced Call Handling—Using Cisco Extension Mobility"
|
Fast Dial Service
|
Supported
|
Supported
|
"Advanced Call Handling—Speed Dialing"
|
Forced Authorization Codes (FAC)
|
Supported
|
—
|
"Basic Call Handling—Placing a Call: Additional Options"
|
Help System
|
Supported
Not supported on 7911G
|
Supported
Not supported on 7911G
|
"An Overview of Your Phone—Understanding Feature Buttons and Menus"
|
Hold/Resume
|
Supported
|
Supported
|
"Basic Call Handling—Using Hold and Resume"
|
Immediate Divert
|
Supported
|
Supported
|
"Basic Call Handling—Answering a Call"
|
Join/Select
|
Supported
|
—
|
"Basic Call Handling—Making Conference Calls"
|
Malicious Call ID
|
Supported
|
—
|
"Advanced Call Handling—Tracing Suspicious Calls"
|
Meet-Me Conference
|
Supported
|
Supported
|
"Basic Call Handling—Making Conference Calls"
|
Multilevel Precedence and Preemption (MLPP)
|
Supported
|
—
|
"Advanced Call Handling—Prioritizing Critical Calls"
|
Multiple Calls per Line Appearance
|
200
7911G supports up to 6
|
50
7911G supports up to 6
|
"An Overview of Your Phone—Understanding Lines vs. Calls"
|
Mute
|
Supported
Supported as Monitor feature on 7911G
|
Supported
Supported as Monitor feature on 7911G
|
"Basic Call Handling—Using Mute"
|
On-hook Dialing/Pre-Dial
|
Supported
|
Supported
|
"Basic Call Handling—Placing a Call: Basic Options"
|
Privacy
|
Supported
|
Supported
|
"Advanced Call Handling—Using a Shared Line"
|
Quality Reporting Tool (QRT)
|
Supported
|
Supported
|
"Troubleshooting—Using the Quality Reporting Tool"
|
Redial
|
Supported
|
Supported
|
"Basic Call Handling—Placing a Call: Basic Options"
|
Shared Line
|
Supported
|
Supported
|
"Advanced Call Handling—Using a Shared Line"
|
Speed Dialing
|
Supported
|
Supported
|
"Advanced Call Handling—Speed Dialing"
|
Transfer
|
Supported
|
Supported
|
"Basic Call Handling—Transferring Calls"
|
Transfer - Direct Transfer
|
Supported
|
—
|
"Basic Call Handling—Transferring Calls"
|
URL Dialing
|
—
|
Supported
|
"Using Call Logs and Directories—Using Call Logs"
|
Video Support
|
Supported
7911G does not support Cisco VT Advantage
|
—
|
"Understanding Additional Configuration Options"
|
Voice Mail
|
Supported
|
Supported
|
"Accessing Voice Messages" section of the Phone Guide
|
WebDialer
|
Supported
|
Supported
|
"Customizing Your Phone on the Web—Configuring Features and Services on the Web"
|
Settings
|
Call Statistics
|
Supported
|
Supported
|
"Troubleshooting Your Phone—Viewing Phone Administrative Data"
|
Voice Quality Metrics
|
Supported
|
—
|
"Troubleshooting Your Phone—Viewing Phone Administrative Data"
|
Services
|
SDK Compliance
|
4.0(1)
|
4.0(1)
|
Cisco IP Phone Service Application Development Notes for Release 4.1(3) or later
|
Directories
|
Call Logs
|
Supported
|
Supported
|
"Using Call Logs and Directories—Directory Dialing"
|
Corporate Directories
|
Supported
|
Supported
|
"Using Call Logs and Directories—Directory Dialing"
|
Personal Directory Enhancements
|
Supported
|
Supported
|
"Using Call Logs and Directories—Directory Dialing"
|
Supplemental Features and Applications
|
Cisco IP Manager Assistant
|
Supported
Not supported on 7911G
|
—
|
Cisco IPMA User Guide
|
Cisco CallManager
AutoAttendant
|
Supported
|
—
|
Cisco CallManager Features and Services Guide
|
Cisco CallManager Attendant Console
|
Supported
|
—
|
Cisco CallManager Attendant Console User Guide
|
Cisco IP Phone Expansion Module 7914
|
Supported
7941G/7941G-GE and 7911G do not support
|
—
|
Cisco IP Phone Expansion Module 7914 Guide
|
Cisco VT Advantage
|
Supported
Not supported on 7911G
|
—
|
Cisco VT Advantage User Guide
|
Cisco IP Phones 7940G and 7960G
Cisco CallManager Release 5.0(1) allows you to choose which protocol (SIP or SCCP) you want to use to communicate with your Cisco IP Phone 7940G and Cisco IP Phone 7960G.
Feature use and availability are dependent on the protocol you choose for you Cisco IP Phones 7940G and 7960G. For information about feature use and availability by protocol, refer to the appropriate phone guide for your phone model.
Table 5 provides a high-level overview of calling features and their support by protocol. This table focuses primarily on end-user calling features and is not intended to represent a comprehensive listing of all available phone features. For details about user interface differences and feature use, refer to the phone guide for your phone model. Specific sections are referenced in the table.
Table 5 Cisco IP Phone 7940G and Cisco IP Phone 7960G Feature Support by Phone Model and Protocol
Features
|
Cisco IP Phones 7940G and 7960G
|
For More Information
|
SCCP
|
SIP
|
Calling Features
|
Abbreviated Dialing
|
Supported
|
—
|
"Basic Call Handling—Placing a Call: Additional Options"
|
Answer Release
|
Supported
|
Supported
|
"Basic Call Handling—Answering a Call"
|
Auto Answer
|
Supported
|
Supported
|
"Basic Call Handling—Answering a Call"
|
Auto Dial
|
—
|
—
|
|
Barge (and cBarge)
|
Supported
|
—
|
"Advanced Call Handling—Using a Shared Line"
|
Busy Lamp Field (BLF) Call Lists
|
—
|
—
|
|
Busy Lamp Field (BLF) Speed Dial
|
Supported
|
—
|
"Advanced Call Handling—Determining if Another Line is Busy"
|
Call Back
|
Supported
|
—
|
"Basic Call Handling—Placing a Call: Additional Options"
|
Call Forward All
|
Supported
|
Supported
|
"Basic Call Handling—Forwarding All Calls to Another Number"
|
Call Forward Busy
|
Supported
|
Supported
|
Users do not interact with this feature directly. It is configured on Cisco CallManager.
|
Call Forward No Answer
|
Supported
|
Supported
|
Users do not interact with this feature directly. It is configured on Cisco CallManager.
|
Call Park
|
Supported
|
—
|
"Advanced Call Handling—Storing and Retrieving Parked Calls"
|
Call Pickup/Group Call Pickup
|
Supported
|
—
|
"Advanced Call Handling—Picking Up Redirected Calls"
|
Call Waiting
|
Supported
|
Supported
|
"Basic Call Handling—Answering a Call"
|
Caller ID
|
Supported
|
Supported
|
|
Client Matter Codes (CMC)
|
Supported
|
—
|
"Basic Call Handling—Placing a Call: Additional Options"
|
Conference
|
Supported
|
Supported
|
"Basic Call Handling—Making Conference Calls"
|
Conference List
|
Supported
|
—
|
"Basic Call Handling—Making Conference Calls"
|
Computer Telephony Integration (CTI) Applications
|
Supported
|
—
|
Users do not interact with this feature directly. It is configured on Cisco CallManager.
|
Direct Transfer
|
Supported
|
—
|
"Basic Call Handling—Transferring Calls"
|
Distinctive Ring
|
Supported
|
—
|
"Using Phone Settings—Customizing Rings and Message Indicators"
|
Do Not Disturb
|
—
|
Supported
|
"Basic Call Handling—Using Do Not Disturb"
|
Extension Mobility
|
Supported
|
—
|
"Advanced Call Handling—Using Extension Mobility"
|
Fast Dial Service
|
Supported
|
—
|
"Advanced Call Handling—Speed Dialing"
|
Forced Authorization Codes (FAC)
|
Supported
|
—
|
"Basic Call Handling—Placing a Call: Additional Options"
|
Help System
|
Supported
|
Supported
|
"An Overview of Your Phone—Understanding Feature Buttons and Menus" section of the Phone Guide
|
Hold/Resume
|
Supported
|
Supported
|
"Basic Call Handling—Using Hold and Resume"
|
Immediate Divert
|
Supported
|
—
|
"Basic Call Handling—Answering a Call"
|
Join/Select
|
Supported
|
—
|
"Basic Call Handling—Making Conference Calls"
|
Malicious Call ID
|
Supported
|
—
|
"Advanced Call Handling—Tracing Suspicious Calls"
|
Meet-Me Conference
|
Supported
|
—
|
"Basic Call Handling—Making Conference Calls"
|
Multilevel Precedence and ambition (MLPP)
|
Supported
|
—
|
"Advanced Call Handling—Prioritizing Critical Calls"
|
Multiple Calls per Line Appearance
|
6
|
2 per line
7960G: maximum of 6 calls per phone
7940G: maximum of 4 calls per phone
|
"An Overview of Your Phone—Understanding Lines vs. Calls"
|
Mute
|
Supported
|
Supported
|
"Basic Call Handling—Using Mute"
|
On-hook Dialing/Pre-dial
|
Supported
|
—
|
"Basic Call Handling—Placing a Call: Basic Options"
|
Privacy
|
Supported
|
—
|
"Advanced Call Handling—Using a Shared Line"
|
Quality Reporting Tool (QRT)
|
Supported
|
—
|
"Troubleshooting Your Phone—Using the Quality Reporting Tool"
|
Redial
|
Supported
|
Supported
|
"Basic Call Handling—Placing a Call: Basic Options"
|
Shared Line
|
Supported
|
Limited Support
|
"Advanced Call Handling—Using a Shared Line"
|
Speed Dialing
|
Supported
|
Supported
|
"Advanced Call Handling—Speed Dialing"
|
Transfer
|
Supported
|
Supported
|
"Basic Call Handling—Transferring Calls"
|
Transfer - Direct Transfer
|
|
—
|
"Basic Call Handling—Transferring Calls"
|
URL Dialing
|
—
|
Supported
|
"Advanced Call Handling—URL Dialing"
|
Video Support
|
Supported
|
—
|
"Understanding Additional Configuration Options"
|
Voice Mail
|
Supported
|
Supported
|
"Accessing Voice Messaging
|
WebDialer
|
Supported
|
—
|
"Customizing Your Phone on the Web—Configuring Features and Services on the Web"
|
Settings
|
Call Statistics
|
Supported
|
—
|
"Troubleshooting Your Phone—Viewing Phone Administrative Data"
|
Voice Quality Metrics
|
Supported
|
—
|
"Troubleshooting Your Phone—Viewing Phone Administrative Data"
|
Services
|
SDK Compliance
|
4.0(1)
|
3.0
|
Cisco IP Phone Service Application Development Notes for Release 4.1(3)
Cisco IP Phone Services Application Development Notes with Cisco CallManager 3.1
|
Directories
|
Call Logs
|
Supported
|
Supported
|
"Using Call Logs and Directories—Directory Dialing"
|
Corporate Directories
|
Supported
|
Supported
|
"Using Call Logs and Directories—Directory Dialing"
|
Personal Directory Enhancements
|
Supported
|
Supports SIP-only Personal Directory. Does not support new enhancements
|
"Using Call Logs and Directories"
|
Supplemental Features and Applications
|
Cisco IP Manager Assistant
|
Supported
|
—
|
Cisco IPMA User Guide
|
Cisco CallManager AutoAttendant
|
Supported
|
—
|
Cisco CallManager Features and Services Guide
|
Cisco CallManager Attendant Console
|
Supported
|
—
|
|
Cisco IP Phone Expansion Module 7914
|
Supported
7940G does not support.
|
—
|
Cisco IP Phone Expansion Module 7914 Guide
|
Cisco VT Advantage
|
Supported
|
—
|
Cisco VT Advantage User Guide
|
Cisco IP Phones 7905G and 7912G
Cisco CallManager Release 5.0(1) allows you to choose which protocol (SIP or SCCP) you want to use to communicate with your Cisco IP Phone 7905G and Cisco IP Phone 7912G.
Feature use and availability are dependent on the protocol you choose for you Cisco IP Phones 7905G and 7912G. For information about feature use and availability by protocol, refer to the appropriate phone guide for your phone model.
Table 6 provides a high-level overview of calling features and their support by protocol for the Cisco IP Phones 7905G and 7912G. This table focuses primarily on end-user calling features and is not intended to represent a comprehensive listing of all available phone features. For details about user interface differences and feature use, refer to the phone guide for your phone model. Specific sections are referenced in the table.
Table 6 Cisco IP Phone 7905G and Cisco IP Phone 7912G Feature Support by Phone Model and Protocol
Features
|
Cisco IP Phones 7905G and 7912G
|
For More Information
|
SCCP
|
SIP
|
Calling Features
|
Abbreviated Dialing
|
Supported
|
—
|
"Basic Call Handling—Placing a Call"
|
Answer Release
|
Supported
|
Supported
|
"Basic Call Handling—Answering a Call"
|
Auto Answer
|
Supported
|
—
|
"Basic Call Handling—Answering a Call"
|
Auto Dial
|
—
|
—
|
|
Barge (and cBarge)
|
Supports cBarge only
|
—
|
"Advanced Call Handling—Understanding Shared Lines"
|
Busy Lamp Field (BLF) Call Lists
|
—
|
—
|
|
Busy Lamp Field (BLF) Speed Dial
|
—
|
—
|
|
Call Back
|
Supported
|
—
|
"Basic Call Handling—Placing a Call"
|
Call Forward All
|
Supported
|
Supported
|
"Quick Reference—Using Call Forward"
|
Call Forward Busy
|
Supported
|
Supported
|
Users do not interact with this feature directly. It is configured on Cisco CallManager
|
Call Forward No Answer
|
Supported
|
Supported
|
Users do not interact with this feature directly. It is configured on Cisco CallManager
|
Call Park
|
Supported
|
—
|
"Advanced Call Handling—Storing and Retrieving Parked Calls"
|
Call Pickup/Group Call Pickup
|
Supported
|
—
|
"Advanced Call Handling—Picking Up a Redirected Call on Your Phone"
|
Call Waiting
|
Supported
|
Supported
|
"Basic Call Handling—Call Waiting"
|
Caller ID
|
Supported
|
Supported
|
|
Client Matter Codes (CMC)
|
Supported
|
—
|
"Basic Call Handling—Placing a Call"
|
Conference
|
Supported
|
Supported
|
"Quick Reference—Making Conference Calls"
|
Conference List
|
Supported
|
—
|
"Basic Call Handling—Making Conference Calls"
|
Computer Telephony Integration (CTI) Applications
|
Supported
|
—
|
Users do not interact with this feature directly. It is configured on Cisco CallManager
|
Do Not Disturb (DND)
|
—
|
Supported
|
"Basic Call Handling—Additional Features Available from the Call Preferences Menu"
|
Distinctive Ring
|
—
|
—
|
|
Extension Mobility
|
Supported
|
—
|
"Advanced Call Handling—Using Cisco Extension Mobility"
|
Fast Dial Service
|
Supported
|
|
"Customizing Your Phone on the Web—Configuring Features and Services on the Web"
|
Forced Authorization Codes (FAC)
|
Supported
|
|
"Basic Call Handling—Placing a Call"
|
Help System
|
—
|
—
|
|
Hold/Resume
|
Supported
|
Supported
|
"Basic Call Handling—Using the Hold Button"
|
Immediate Divert
|
Supported
|
—
|
"Basic Call Handling—Answering a Call"
|
Join/Select
|
Supported
|
—
|
"Basic Call Handling—Making Conference Calls"
|
Malicious Call ID
|
Supported
|
—
|
"Advanced Call Handling—Tracing Suspicious Calls"
|
Meet-Me Conference
|
Supported
|
—
|
"Quick Reference—Making Conference Calls"
|
Multilevel Precedence and Preemption (MLPP)
|
Supported
|
—
|
"Advanced Call Handling—Prioritizing Critical Calls"
|
Multiple Calls per Line Appearance
|
6
|
2
|
"An Overview of Your Phone—Call Handling and Navigation Tips"
|
Mute
|
—
|
—
|
|
On-hook Dialing/Pre-Dial
|
Supported
|
Supported
|
"Basic Call Handling—Placing a Call"
|
Privacy
|
Supported
|
—
|
"Advanced Call Handling—Understanding Shared Lines"
|
Quality Reporting Tool (QRT)
|
Supported
|
—
|
"Troubleshooting Your Phone—Using the Quality Reporting Tool"
|
Redial
|
Supported
|
Supported
|
"Basic Call Handling—Placing a Call"
|
Shared Line
|
Supported
|
Limited Support
|
"Advanced Call Handling—Understanding Shared Lines"
|
Speed Dialing
|
Supported
|
Supported
|
"Quick Reference—Using Speed Dial"
|
Transfer
|
Supported
|
Supported
|
"Quick Reference—Transferring a Call"
|
Transfer - Direct Transfer
|
Supported
|
—
|
"Quick Reference—Transferring a Call"
|
URL Dialing
|
—
|
—
|
|
Video Support
|
—
|
—
|
|
Voice Mail
|
Supported
|
Supported
|
"Using Voice Messaging, Call Logs, and Directories"
|
WebDialer
|
Supported
|
—
|
"Customizing Your Phone on the Web—Configuring Features and Services on the Web"
|
Settings
|
Voice Quality Metrics
|
—
|
—
|
|
Call Statistics
|
—
|
Supported
|
|
Services
|
SDK Compliance
|
4.1(3)
|
—
|
|
Directories
|
Call Logs
|
Supported
|
Supported
|
"Using Voice Messaging, Call Logs, and Directories"
|
Corporate Directories
|
Supported
|
—
|
|
Personal Directory Enhancements
|
Supported
|
—
|
|
Supplemental Features and Applications
|
Cisco IP Manager Assistant
|
—
|
—
|
Cisco IPMA User Guide
|
Cisco CallManager AutoAttendant
|
Supported
|
—
|
Cisco CallManager Features and Services Guide
|
Cisco CallManager Attendant Console
|
Supported
|
—
|
|
Cisco IP Phone Expansion Module 7914
|
—
|
—
|
Cisco IP Phone Expansion Module 7914 Guide
|
Cisco VT Advantage
|
—
|
—
|
Cisco VT Advantage User Guide
|
New and Changed Information for Third-Party API
This following sections describe new features and changes that are pertinent to this release of Cisco CallManager and third-party APIs.
•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
Cisco CallManager Developers Guide
The Cisco CallManager Developers Guide, a new document, comprises four existing programming guides. This document describes the following Cisco CallManager APIs:
AXL Programming
The following list describes the AXL API enhancements for Cisco CallManager Release 5.0(1):
This release adds the following AXL API's:
•executeSQLUpdate
•doAuthenticateUser
•updateAppUser
•addUserGroup
•updateUserGroup
•removeUserGroup
•getUserGroup
The following AXL API's are modified in this release:
•addPhone
•updatePhone
•getPhone
•addGatewayEndpoint
•updateGatewayEndpoint
•getGatewayEndpoint
•addMGCPEndpoint
•updateMGCP
•addSIPTrunk
•updateSIPTrunk
•getSIPTrunk
•addCallManager
•updateCallManager
•getCallManager
•addCallPark
•addRoutePattern
•updateRoutePattern
•updateTransPattern
•updateHuntPilot
•addHuntList
•updateHuntList
•getHuntList
•addPilotPoint
•updatePilotPoint
•getPilotPoint
•addH323Gateway
•updateH323Gateway
•updateH323Phone
•getH323Gateway
•getH323Trunk
•addUser
•updateUser
•getUser
•updateProcessNodeService
•getProcessNodeService
•listUserByName
•updateServiceParameter
•updateGatekeeper
•updateConferenceBridge
•updateAttendantConsoleHuntGroup
•updateDeviceProfile
•updateLine
•updateLineGroup
•addDevicePool
•updateDevicePool
•doDeviceReset
The following AXL API's are deprecated in this release:
•addDDI
•updateDDI
•removeDDI
•addDialPlan
•updateDialPlan
•removeDialPlan
•addDialPlanTag
•updateDialPlanTag
•removeDialPlanTag
Refer to the schema of these API's for detailed information of the enhancements.
The following changes in AXL apply for Cisco CallManager 5.0(1).
•AXL is deployed as a web application within Tomcat.
•The URL for accessing AXL is changed to https://server_name:8443/axl/
where server_name is the host on which AXL Web Service is running.
•Some of the error codes are no longer supported in AXL. Users need to update their applications and modify their error handling to accommodate these changes.
•For a User to access AXL, proper permissions need to be assigned through the User Management menu under the Cisco CallManager Administration pages. The Application User needs to be added to an existing or new User Group that has the AXL API Access role assigned to it.
AXL Serviceability Programming
The following list provides the new features or changes for the AXL Serviceability API in Cisco CallManager Release 5.0(1):
•Perfmon Data Collection Service—This service now gets exposed through a new framework called the Perfmon Infrastructure and System Information Library, which provides platform/OS counters. The APIs remain the same; however, the information that is provided through these APIs will be similar but not exactly the same. Windows performance counters will not be available.
Real-time and Perfmon WSDL interfaces are preserved, except the URL will differ from previous releases for each SOAP service.
•Real-Time Information (RisPort)—No changes occurred for this release.
•Server Query Service—This service exports the following information from the Server Information SOAP interface:
–Host Name
–OS Name
–OS Arch
–OS Version
–Java Runtime Version
–Java Virtual Machine Vendor
–CallManager Version
•Service Interface—This service allows you to do Service Deploy, Service UnDeploy, and Get Service List and to perform service start and stop.
•Log Collection Service—This service, a public SOAP/HTTPS interface, allows applications to retrieve lists of services and log files through the use of three APIs: listNodeServiceLogs, selectLogFiles, and getOneFile.
•CDR on Demand Service—This service, a public SOAP/HTTPS interface, gets exposed to third-party billing applications or customers to allow them to query the Cisco CallManager, specifically the CDR Repository Node, to retrieve CDR/CMR files on demand through the use of two APIs, get_file_list and get_file.
•Disaster Recovery Framework Service—The DRF API is not implemented in this release.
The following enhancements exist in Serviceability for AXL:
•You can access AXL by using Cisco CallManager Serviceability
(Serviceability > Tools AXL Web Service).
•Serviceability provides an option to activate/deactivate AXL Web Service
(Serviceability > Tools > Service Activation).
•Serviceability provides an option to start and stop AXL Web Service
(Serviceability > Tools > Control Center - Feature Services).
•Serviceability provides an option to change trace levels for AXL
(Serviceability > Trace > Configuration).
Extension Mobility API
The following list describes the Extension Mobility API enhancements for Cisco CallManager 5.0(1):
•Dial Plan on Phone—SIP phones will have dial plan information pushed to them via a Config file. This dial plan takes the form of an unordered list of dial maps. One dial plan corresponds to each CSS.
In the case of extension mobility, the effective list of CSSs for a phone is a combination of "Device CSS" and "Line CSS." Device CSS gets tied to the physical attributes of the phone like location, region, and so on, and does not change across login/logout of users. Line CSS gets tied to the lines and changes when users login/logout.
DBL generates the appropriate list of dialmaps when login/logout operations are performed. Because each CSS has a dial map linked with it, the DBL module will extract dial map information for each line in the device profile. It will append this information to the dial map that corresponds to Device CSS. The resulting dial map list gets pushed to the configuration file.
•SRST mode—In SRST mode, the extension mobility behavior remains the same as in previous releases. You cannot perform login and logout operations when a phone is in SRST mode. Call processing proceeds as normal, given that the SRST GW is configured appropriately.
•Credentials for SIP Digest Authentication—Credentials for SIP Digest authentication are configured in the "user directory" page. All the device profiles that associate with that user must use this set of credentials. For phones that read this information from the Config file, DBL populates the Config file with the appropriate credential set.
For phones that do not support Digest credentials in the Config file, Digest authentication can break. For extension mobility, the SIP Digest credentials will change when a user logs in and out. The user must enter the credentials when placing a call.
WebDialer Developers Guide
The following list describes the WebDialer enhancements for Cisco CallManager Release 5.0(1):
•Modify logging mechanism to apply the changes to both WebDialer and Redirector.
•Make Redirector functional with HTTPS. Redirector support for HTTPS is only partial.
•WebDialer subscribe for Dial Rule Change Notification.
•WebDialer support for enhancements in CTI and JTAPI.
•Migration of Dial Rule data during an upgrade from Windows to Linux.
•SIP support in WebDialer.
•Increase in thread count to 3.
CDR Definitions
The transition from an SQL database to flat files represents the major change in CDRs/CMRs in this release. If you upgrade from Cisco CallManager 4.x, the CDRs in the CAR database are converted to CSV files, which are stored in the CDR Repository.
The following list describes the CDR enhancements for Cisco CallManager Release 5.0(1):
•Cisco CallManager will generate a special CDR/CMR to identify when these records are enabled or disabled.
•A single sequence number is now used for both CDR and CMR files.
This means the CDR and the corresponding CMR will reside within a reasonable number of files and can more easily be correlated.
•In addition to the existing voice quality data that the SCCP phone supports, new measurements are added in the new varVQMetrics field.
•The QoS Support (RSVP) feature adds four new CDR fields to reflect the status of RSVP bandwidth reservation per audio or video stream for both the origin and destination.
•A new CDR field is added per party to show what DTMF method is being used by that party for given call.
•A new Call Secured Status field that is added to the CDR contains an indication of the highest level of security that is reached during the call.
•This release includes three new SIP features (Refer, Replaces, and Redirection). Calls that involve these features will generate CDRs, but no new CDR fields are required for these features.
Depending on the features and the call scenario, the major difference means that the party fields may contain SIP URIs instead of numbers.
These new SIP features (Refer, Replaces, and Redirection) also have new onBehalfOf field values.
•The Pickup feature is enhanced and separated from the Forwarding feature. Specifically, the pickup by redirect and monitoring of pickup groups move from the Forwarding feature to the Pickup feature.
•The Q.931 call release cause codes remain the same; however, the Cisco-specific call release cause codes changed values, and several new codes have been added. The release also adds a new table of SIP call release cause codes.
Refer to the CDR Definitions Guide for a complete description of these enhancements.
Cisco IP Phone Service Application Development Notes for Cisco CallManager 5.0(1)
This document provides the information needed for programmers and system administrators to develop and deploy new Cisco IP Phone services with Cisco CallManager 5.0, using eXtensible Markup Language (XML) objects and the Hyper Text Transfer Protocol (HTTP) with standard web servers. Cisco conforms as closely as possible to the XML and HTTP standards while providing maximum service functionality for Cisco IP Phones.
JTAPI Developers Guide
The JTAPI Developers Guide now includes a chapter on installation of the JTAPI Client. Previously, the installation of JTAPI Client was supported only on Windows platforms. With this release, the JTAPIInstaller provides a unified installation/uninstallation process for the JTAPI Client for Linux, Windows, and Solaris.
For Linux and Solaris versions, the InstallShield MultiPlatform (ISMP) installer generates a binary file (.bin), and, for the Windows version, it generates an executable file (.exe), after the set of files that need to be installed are obtained.
The following list describes the JTAPI enhancements for Cisco CallManager 5.0(1).
The basic changes for the end user of JTAPI applications follow:
•JTAPI Applications users must migrate to JDK 1.4.
•JTAPIPreferences will not work if users do not have JDK 1.4 installed.
•JTAPI Applications that use jsafe.jar or log4j.jar may be impacted.
This release includes the following JTAPI enhancements:
•Partition Support
•Hairpin Support
•QoS Support
•Transport Layer Security
•SIP Phone Support
•Secure Real Time Protocol (SRTP)
•SIP REFER / REPLACES
•SIP 3XX Redirection
•Backward Compatibility
•Address and Terminal Restriction
•Unicode Support for JTAPI
•Linux and Solaris Install
•JDK 1.4 Migration
•Network Alerting Change
•SuperProvider Additional Functionality
•Alternate Script Support
•Half Duplex Media Support
Refer to the JTAPI Developers Guide for a complete description of these enhancements.
SCCP Messaging Guide
The following list describes the SCCP messaging enhancements for Cisco CallManager Release 5.0(1):
•The following SCCP messages are deprecated in this release:
–StationEnunciatorCommand
–StationIpPortMessage
–StationMediaPortListMessage
–StationSetHkFDetectMessage
•The following SCCP messages are modified in this release:
–StationCloseMultiMediaReceiveChannel
–StationCloseReceiveChannelMessage
–StationConnectionStatisticsResMessage
–StationOpenMultiMediaReceiveChannel
–StationOpenReceiveChannelMessage
–StationRegisterMessage
–StationStartMediaTransmissionMessage
–StationStartMultiMediaTransmission
–StationStopMediaTransmissionMessage
–StationStopMultiMediaTransmission
•This release adds the following SCCP messages:
–StationMediaPathCapabilityMessage
–StationMediaPathEventMessage
–StationNotificationMessage
–StationSubscriptionStatMessage
–StationSubscriptionStatReqMessage
–StationVideoDisplayCommandMessage
Refer to the SCCP Messaging Guide for a complete description of these enhancements.
SIP Messaging Guide
The SIP Messaging Guide, a new book for Cisco CallManager Release 5.0(1), describes the external interface for the Cisco CallManager SIP trunk device. It highlights the SIP primitives that are supported across the SIP trunk and basic call flow scenarios that can be used as a guide for technical support.
TAPI Developers Guide
The TAPI Developers Guide now includes a chapter on installation. No changes occurred to the TAPI installation for Cisco CallManager Release 5.0(1).
The following list describes the TAPI enhancements for Cisco CallManager Release 5.0(1):
•QoS Support
•Partition Support
•Alternate Script Support
•TLS Support
•SRTP Support
•Super Provider Support
•Refer/Replaces Support
•SIP URL Address Support
•3XX Support
Refer to the TAPI Developers Guide for a complete description of these enhancements.
Installation Notes
For installation information, refer to the following documents:
•Installing Cisco CallManager Release 5.0(1)
•Upgrading Cisco CallManager Release 5.0(1)
•Cisco IP Telephony Data Migration Assistant Administration Guide, Version 2.0(1)
Limitations and Restrictions
You can find which application versions are compatible with Cisco CallManager release 5.0(1)and which previous release of Cisco CallManager has upgrade support by referring to the Cisco CallManager Software Compatibility Matrix at this location: http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_device_support_tables_list.html
Note Be aware that the release of Cisco IP telephony products does not always coincide with Cisco CallManager releases. If a product does not meet the compatibility testing requirements with Cisco CallManager, you need to wait until a compatible version of the product becomes available before you can upgrade to Cisco CallManager release 5.0(1). For the most current compatibility combinations and defects, refer to the documentation that is distributed with the Cisco IP telephony products.
Important Notes
The following section contains important information that may have been unavailable upon the initial release of documentation for Cisco CallManager release 5.0(1).
•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
•CSCtj61834 MLPP Default Domain Name Displays MLPP ID Value
Using Call Park
Consider the following information before you configure the call park feature in Cisco CallManager,
•Be sure to use Cisco Dialed Number Analyzer tool to validate the call park number or ranges that you entered. Cisco CallManager Administration does not validate the call numbers or range that you use to configure call park. Cisco Dialed Number Analyzer can identify invalid numbers or ranges, and potential range overlaps.
For more information, refer to CSCsc77968, CSCsc78450, and CSCsc78720.
•Cisco CallManager Administration does not check that the value entered for Call Park Reversion Timer is less than the valued entered for the Callpark Display Timer. If you entered a Call Park Reversion Timer value that is less than the Call Park Display Timer, call park numbers will not display on the phone.
For more information, refer to CSCsc76797 and CSCsc76702.
When a user parks a call across a QSIG intercluster trunk or a QSIG gateway trunk, the caller who has been parked (the parkee) does not see the To parked number message. The phone continues to display the original connected number. The call has been parked and can be retrieved by the user who parked the call. When the call is retrieved from the parked state, the call continues but the caller who was parked does not see the newly connected number.
Failover Time Using UDP Protocol on SIP Phones
This condition affects Cisco IP Phone models 7970G, 7971G-GE, 7941G, 7961G, 7941G-GE, 7961G-GE, and 7911 using the SIP Protocol.
When UDP is selected as the transport protocol, phones fail to connect to a Cisco CallManager node after a failover. This occurs because phone failover time takes more than the 120 seconds that the phone waits to detect a Cisco CallManager failure status. This condition affects Cisco IP Phone models 7970G, 7971G-GE, 7941G, 7961G, 7941G-GE, 7961G-GE, and 7911 that are using the SIP Protocol. The workaround is to configure the SIP phones to use the TCP protocol in the SIP Phone Security Profile.
Premature Certificate Generation Prevents Immediate Service Activation After a Fresh Installation
When you install Cisco CallManager 5.0 on subscriber (subsequent) nodes and the time zone is a time zone that is ahead of the Pacific time zone (Mountain Time (GMT-8) through Auckland (GMT+12) time zone), the Tomcat certificate that is generated does not take affect until the time in the future equal to the number of hours your time zone is ahead of the Pacific time zone. The certificates become valid only after this number of hours has elapsed and it affects all time zones that are ahead of the Pacific time zone. To enable immediate service activation on a subscriber, regenerate the certificates for your current time zone by performing the following:
•Login to Cisco IPT Platform Administration on the subscriber node.
•Choose Security > Certificate Mgmt > Delete/Regenerate Certificate in Cisco IPT Platform Administration.
•Activate the services on the subscriber node.
For more information, refer to CSCsc85288.
SIP Trunk Configuration
Consider the following restrictions when you configure SIP trunks on Cisco CallManager since Cisco CallManager does not perform validation on your configuration:
•Cisco CallManager does not support outbound MWI notification on a SIP Trunk that is assigned to a Route List or a Route Group. If you want Cisco CallManager to send outbound MWI notification on a SIP Trunk, you must assign the SIP trunk directly to a route pattern.
•Each SIP trunk must have a unique SIP routing configuration in order for SIP routing to work. Cisco CallManager uses a combination of information from incoming SIP messages to route the SIP message to the correct SIP trunk. A SIP trunk's routing configuration is unique if:
–No other trunk is configured with the same values for the Incoming Transport Protocol, Incoming Port, and Destination Address fields.
–No other trunk is configured with Transport Layer Security (TLS) selected as the Incoming Transport Protocol and the same values in the Incoming Port and X.509 Subject Name fields. The X.509 Subject Name parameter can consist of a list of names.
The Incoming Transport Protocol, Incoming Port, and X.509 Subject Name parameters are configured in SIP Trunk Security Profile Configuration in Cisco CallManager Administration. Choose System > Security Profile > SIP Trunk Security Profile Configuration. This menu option yields the Find and List SIP Trunk Security Profile window. Use this window to search for existing SIP Trunk Security Profiles or click Add New to add a new profile.
The Destination Address and the selected SIP Trunk Security profile are configured on the Trunk Configuration page in Cisco CallManager. Choose Device-> Trunk. This menu option yields the Find and List Trunks window. Use this window to search for existing Trunks or click Add New to add a new trunk and choose SIP trunk as the Trunk Type.
The following is an example of a valid configuration:
Trunk#1: Incoming Transport Protocol=TCP/UDP, Incoming Port=5060, Destination
Address=10.10.10.1
Trunk#2: Incoming Transport Protocol=TCP/UDP, Incoming Port=5060, Destination
Address=10.10.10.2
Trunk#3: Incoming Transport Protocol=TCP/UDP, Incoming Port=5080, Destination
Address=10.10.10.1
Trunk#4: Incoming Transport Protocol=TLS, Incoming Port=5061, X.509 Subject
Name=my_ccm1, my_ccm2
Trunk#5: Incoming Transport Protocol=TLS, Incoming Port=5061, X.509 Subject
Name=my_ccm3
Trunk#6: Incoming Transport Protocol=TLS, Incoming Port=5081, X.509 Subject
Name=my_ccm_1
The following is an example of an invalid configuration:
Trunk#1: Incoming Transport Protocol=TCP/UDP, Incoming Port=5060, Destination
Address=10.10.10.1
Trunk#2: Incoming Transport Protocol=TCP/UDP, Incoming Port=5060, Destination
Address=10.10.10.1
Trunk#3: Incoming Transport Protocol=TLS, Incoming Port=5061, X.509 Subject
Name=my_ccm1, my_ccm2
Trunk#4: Incoming Transport Protocol=TLS, Incoming Port=5081, X.509 Subject
Name=my_ccm2
Trunk#5: Incoming Transport Protocol=TLS, Incoming Port=5061, X.509 Subject
Name=my_ccm2
Trunk#6: Incoming Transport Protocol=TLS, Incoming Port=5081, X.509 Subject
Name=my_ccm2
Trunk #2 conflicts with Trunk #1 because the protocol, incoming port, and destination address are identical.
Trunk #5 conflicts with Trunk #3 because the protocol and incoming port are identical and both trunks include my_ccm2 in their list of X.509 Subject Names.
Trunk #6 conflicts with Trunk #4 because the protocol, incoming port, and X.509 Subject Name are identical.
Unplugging a USB Cable
When you unplug the USB cable and then plug it back in, you must first stop the Cisco Message Interface (CMI) service if it is running on that Cisco CallManager server. You can restart the CMI service after you plug back in the USB cable. If you do not stop the CMI service before you unplug and plug back in the USB cable and there is a phone call to the voicemail pilot number or a call gets forwarded to that pilot number, the OS stops and you will need to reboot the server. For more information, refer to CSCsc58288.
Cisco MCS-7845H-2.4-EVV1 and Cisco MCS-7835H-2.4-EVV2 Server May Not Recognize the USB-to-Serial Cable
When you reboot a Cisco MCS-7845H-2.4-EVV1 or a Cisco MCS-7835H-2.4-EVV2 server, the USB controller may not recognize the existence of the USB-to-Serial cable and will not detect a device that is attached to it when the server is rebooted. This only occurs on a limited number of units. If the server is under warranty, you can replace the system board in the server. For more information, refer to CSCsc86874.
Configuring Regions (Region Relationship) For SIP Devices with the MTP Required Option Enabled
When you configure a region relationship, you must ensure that you choose an audio codec that has sufficient bandwidth for all the devices that will be used in a call. This includes configuring the codec for devices that will be in the same region as well as devices that are in different regions. When you configure a trunk or third-party phone to use the SIP protocol and Media Termination Point Required is enabled, Cisco CallManager Administration only allows you to choose a G.711 codec in the MTP Preferred Originating Codec field. When you assign the SIP trunk or third-party SIP phone with the MTP Required option enabled to the device pool for that region, you must verify that the region relationship between the SIP device and the MTP device is configured to use a codec with equal or greater bandwidth (G.711 or Wideband codec).
Support for SIP WSM Connection
Cisco CallManager Administration 5.0(1) does not support the SIP WSM Connection or the Motorola CN622.
CSCtj61834 MLPP Default Domain Name Displays MLPP ID Value
When you configure the MLPP Domain Name in Cisco Unified Communications Manager, the default name for MLPP Domain Name displays the MLPP ID value 000000 instead of Default as stated on the help page.
Caveats
The following sections contain information on how to obtain the latest resolved caveat information and descriptions of open caveats of severity level 1, 2 and 3.
Caveats describe unexpected behavior on a Cisco CallManager server. Severity 1 caveats are the most serious caveats; severity 2 caveats are less serious. Severity 3 caveats are moderate caveats, and only select severity 3 caveats are included in this section.
Resolved Caveats
You can find the latest resolved caveat information for Cisco CallManager release 5.0(1) by using Bug Toolkit, which is an online tool that is available for customers to query defects according to their own needs.
Tip You need an account with Cisco.com (Cisco Connection Online) to use the Bug Toolkit to find open and resolved caveats of any severity for any release.
To access the Bug Toolkit, log on to http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl.
This section includes the following topics:
•Using Bug Toolkit
•Saving Bug Toolkit Queries
Using Bug Toolkit
To access Bug Toolkit, you need the following items:
•Internet connection
•Web browser
•Cisco.com user ID and password
To use Bug Toolkit, follow this procedure.
Procedure
Step 1 To access the Bug Toolkit, go to http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl.
Log on with your Cisco.com user ID and password.
Step 2 Click the Launch Bug Toolkit hyperlink.
Step 3 If you are looking for information about a specific caveat, enter the ID number in the "Enter known bug ID:" field.
To view all caveats for Cisco CallManager, go to the "Search for bugs in other Cisco software and hardware products" section, and enter Cisco CallManager in the Product Name field. Alternatively, you can scroll through the product name list and click Cisco CallManager.
Step 4 Click Next. The Cisco CallManager search window displays.
Step 5 Choose the filters to query for caveats. You can choose any or all of the available options:
a. Choose the Cisco CallManager version:
•Choose the major version for the major releases (such as, 5.0, 4.1, 4.0).
A major release contains significant new features, enhancements, architectural changes, and/or defect fixes.
•Choose the revision for more specific information; for example, choosing major version 5.0 and revision version 3 queries for release 5.0(1) caveats.
A revision (maintenance) release primarily contains defect fixes to address specific problems, but it may also include new features and/or enhancements.
b. Choose the Features or Components to query; make your selection from the "Available" list and click Add to place your selection in the "Limit search to" list.
•To query for all Cisco CallManager caveats for a specified release, choose "All Features" in the left window pane.
Note The default value specifies "All Features" and includes all of the items in the left window pane.
•To query only for Cisco CallManager-related caveats, choose "ciscocm" and then click Add.
•To query only for phone caveats, choose "ciscocm-phone" and then click Add.
•To query only for gateway caveats, choose "voice-gateway" and then click Add.
c. Enter keywords to search for a caveat title and description, if desired.
Note To make queries less specific, use the All wildcard for the major version/revision, features/components, and keyword options.
d. Choose the Set Advanced Options, including the following items:
•Bug Severity level—The default specifies 1-3.
•Bug Status Group—Check the Fixed check box for resolved caveats.
•Release Note Enclosure—The default specifies Valid Release Note Enclosure.
e. Click Next.
Bug Toolkit returns the list of caveats on the basis of your query.
•You can modify your results by submitting another query and using different criteria.
•You can save your query for future use. See the "Saving Bug Toolkit Queries" section.
Note For detailed online help with Bug Toolkit, click Help on any Bug Toolkit window.
Saving Bug Toolkit Queries
Bug Toolkit allows you to create and then save your queries to monitor a specific defect or network situation. You can edit a saved search at any time to change the alert conditions, the defects being watched, or the network profile.
Follow this procedure to save your Bug Toolkit queries.
Procedure
Step 1 Perform your search for caveats, as described in the "Using Bug Toolkit" section.
Step 2 In the search result window, click the This Search Criteria button that displays at the bottom of the window.
A new window displays.
Step 3 In the Name of saved search field, enter a name for the saved search.
Step 4 Under My Bug Groups, use one of the following options to save your defects in a bug group:
•Click the Existing group radio button and choose an existing group name from the drop-down list box.
•Click the Create new group named: radio button and enter a group name to create a new group for this saved search.
Note This bug group will contain the bugs that are identified by using the search criteria that you have saved. Each time that a new bug meets the search criteria, the system adds it to the group that you chose.
Bug Toolkit saves your bugs and searches, and makes them available through the My Stuff window. (The My Stuff window allows you to view, create, and/or modify existing bug groups or saved searches. Choose the My Stuff link to see a list of all your bug groups.)
Step 5 Under Email Update Options, you can choose to set optional e-mail notification preferences if you want to receive automatic updates of a bug status change. Bug Toolkit provides the following options:
•Do NOT send me any email updates—If you choose this default setting, Bug Toolkit does not send e-mail notifications.
•Send my updates to:—Click the radio button to choose this option to send e-mail notifications to the user ID that you enter in this field. Additional notification options include
•Updates as they occur—Bug Toolkit provides updates that are based on status change.
•Weekly summaries—Bug Toolkit provides weekly summary updates.
•Apply these email update options to all of my saved searches—Check this check box to use these e-mail update options for all of your saved searches.
Step 6 To save your changes, click Save.
Step 7 A window displays the bug group(s) that you have saved. From this window, you can click a bug group name to see the bugs and the saved searches; you can also edit the search criteria.
Note For complete Cisco IP Phone firmware release note information, refer to the applicable firmware release notes for your specific model IP phone at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_ipphon/english/.
Open Caveats
Table 1 describes possible unexpected behaviors in Cisco CallManager release 5.0(1) and are sorted by component.
Tip For more information about an individual defect, click the associated Identifier in Table 1 to access the online record for that defect, including workarounds.
Understanding the Fixed-in Version and the Integrated-in Fields in the Online Defect Record
When you open the online record for a defect, you may see data in the "First Fixed-in Version" or "Integrated-in" fields. The information that displays in these fields identifies the list of Cisco CallManager interim versions in which the defect was fixed. These interim versions then get integrated into Cisco CallManager releases.
Some more clearly defined versions include identification for Engineering Specials (ES) or Service Releases (SR); for example 03.3(04)ES29 and 04.0(02a)SR1. However, the version information that displays for the Cisco CallManager maintenance releases may not be as clearly identified.
The following examples show how you can decode the maintenance release interim version information. These examples show you the format of the interim version along with the corresponding Cisco CallManager release that includes that interim version. You can use these examples as guidance to better understand the presentation of information in these fields.
•003.003(003.144) = Cisco CallManager release 3.3(4)
•004.000(000.123) = Cisco CallManager release 4.0(1)
•004.000(001.008) = Cisco CallManager release 4.0(2)
•004.001(002.201) = Cisco CallManager release 4.1(3)
Note Because defect status continually changes, be aware that Table 1 reflects a snapshot of the defects that were open at the time this report was compiled. For an updated view of open defects, access Bug Toolkit and follow the instructions as described in the "Using Bug Toolkit" section.
Tip Bug Toolkit requires that you have an account with Cisco.com (Cisco Connection Online). By using the Bug Toolkit, you can find caveats of any severity for any release. Bug Toolkit may also provide a more current listing than this document provides. To access the Bug Toolkit, log on to http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl.
.
Table 7 Open Caveats
Identifier
|
Headline
|
Component: Alert-coll-report
|
CSCsc91225
|
Cisco AMC service should adjust the local collector's polling adjustment time.
|
CSCsd06310
|
The AMC log files that are generated every 5 minutes contain the same data.
|
Component: Attendant Console
|
CSCsc67399
|
After upgrading Cisco CallManager from Microsoft Windows OS, The attendant console password does not work.
|
CSCsd16948
|
Attendant Console cannot locate the Russian locale files.
|
Component: AXL
|
CSCsc68072
|
AXL does not support the add user to a user-group feature.
|
CSCsc73685
|
The update Device Profile request returns a SQL exception error.
|
CSCsc76665
|
The getphone request fails when you enter braces {} around the phoneID value.
|
CSCsc96599
|
The user authentication response to SNR takes a minimum of 18 seconds.
|
CSCsd14344
|
SIP device profile insertion fails.
|
Component: Backup-restore
|
CSCsc64967
|
The backup of feature components failed because of the permission settings on the server.
|
CSCsc99865
|
Disaster Recovery Framework does not send alarms to indicate problems with the backup process for all errors.
|
Component: BAT
|
CSCsb59649
|
BAT overwrites previously generated report when a recurring job is scheduled to generate the report.
|
CSCsc72956
|
User Template Configuration accepts invalid entries in the password or PIN field.
|
CSCsc74503
|
BAT does not generate a log when the TAPS service stops in between transactions.
|
CSCsc84439
|
Users get an exception error when they submit a bulk job with the Run Later option.
|
CSCsc88874
|
BAT incorrectly reports that jobs have failed when the jobs run successfully.
|
CSCsc89013
|
BAT cannot process more than 5000 records when validating phones.
|
CSCsc89091
|
Inserting a phone in BAT fails when the busy lamp field is configured.
|
CSCsc90536
|
The toolbar on the delete pickup group page in BAT displays additional icons.
|
CSCsc90571
|
The job result details and log file link does not work when you export users.
|
CSCsc90575
|
Bat does not validate the MAC Address and DN correctly when it validates phone.
|
CSCsc90629
|
Inserting a phone in BAT fails when the SIP phone template has digest user information.
|
CSCsc90894
|
The Secure TAPS DN Configuration page displays a java.lang.IndexOutOfBoundsException error.
|
CSCsc90901
|
The TAPS view log file page displays a Can't insert page error.
|
CSCsc93716
|
Bulk Provision Service (BPS) has poor performance when inserting phones-users.
|
CSCsc93750
|
The Upload/Download FindList page does not list the logfiles in the results.
|
CSCsc93765
|
BAT inserts a record when you submit an insert a client matter code (CMC) job with the override option selected.
|
CSCsc96061
|
When you select the all data option, the export user report does not contain any data.
|
CSCsd00461
|
System displays a number that is entered in the Line Template Name field as a shared line.
|
CSCsd02672
|
BAT allows the administrator to enter a password phrase that Cisco CallManager Administration does not allow.
|
CSCsd08702
|
When you delete a secure DN using TAPS, it also deletes the line from the database.
|
CSCsd22945
|
BAT does not configure the call pickup group value when the phone is inserted into the database.
|
CSCsd24256
|
BAT does not configure the expansion module and BLF parameters when the phone is inserted into the database.
|
Component: CAR
|
CSCsb56188
|
System does not display cluster information.
|
CSCsc86276
|
CDR Error Report displays incorrect values.
|
CSCsc86310
|
Manual purge times out when there is a large number of records in the tbl_billing_error table.
|
CSCsc94626
|
IPMA manager usage report displays incorrect values.
|
CSCsc94638
|
System displays database error when you generate a Voice Messaging Utilization Report.
|
CSCsc96698
|
QOS Reports fails for reports dated after December 31, 2005.
|
CSCsd02733
|
The Route/Hunt and Gateway Utilization reports display incorrect data.
|
CSCsd05862
|
CAR stops working after you change the domain name.
|
CSCsd21432
|
System performance gets impacted when the CAR scheduler is loading CDRs.
|
Component: CCM Serviceability
|
CSCsd04966
|
Browser displays an error message when a service is deactivated.
|
Component: CLI
|
CSCsc78726
|
The CLI does not provide the capability to display the tail end of a file in real time.
|
CSCsc87198
|
Remote Account becomes inaccessible after deleting an administrator's account with the same name as the remote account.
|
CSCsc93648
|
The CLI utils system shutdown and reboot command should display a warning for administrators to wait for the broadcast shutdown/reboot message before shutting down SSH connection.
|
CSCsc99870
|
Administrators cannot change the network interface MTU size from the default size of 1500 bytes.
|
CSCsc99876
|
System Status command does not display all critical information.
|
CSCsc99879
|
The show network details command does not display collision information.
|
CSCsc99885
|
System does not allow administrators to change the path MTU discovery configuration.
|
CSCsd00609
|
When you regenerate certificates, the system does not prompt you to restart services.
|
CSCsd01121
|
The CLI search command does not display a clear message when no files matching the search are found.
|
CSCsd03786
|
The show tech table command throws a java exception.
|
CSCsd08009
|
You cannot register a phone by using DNS if the DNS client is not configured during installation.
|
CSCsd12375
|
The command line interface does not display the last logged on user.
|
Component: CMCTI
|
CSCeg85332
|
Memory leak occurs when an open device unregisters.
|
CSCsb26613
|
LastRedirectedParty and OriginalCalledParty fields do not get set when a call is parked.
|
CSCsc29276
|
System displays incorrect OriginalPartyName in barged call.
|
CSCsc53189
|
System does not send dwRedirectingID on a InviteW_Replaces call.
|
CSCsc70420
|
Incorrect call information gets displayed in a transferred call that used a translation pattern.
|
CSCsc79231
|
Call disconnects for an outbound option agent in preview mode when the CTI encounters a timeout error code.
|
CSCsc98522
|
CTI fails on a DeviceInfoFetchRequest when a user has 2500 controlled devices.
|
CSCsd08537
|
SIP phones receive extra RTP events in a conference call.
|
CSCsd11122
|
If the first CtiRequest_LineCallInitiateReq times out, subsequent request for the same line also fails.
|
CSCsd23641
|
Devices fail when provide open times out.
|
CSCsd24819
|
CTI does not send the ProviderUserChangedEvent when the SuperProvider property is disabled.
|
Component: CM Documentation
|
CSCsc96394
|
When RSVP Agent is enabled, Cisco CallManager does not use the transcoder for a call.
|
CSCsd48982
|
TFTP process stops searching for files in the off clusters when the alternative file location is empty.
|
CSCtr84167
|
When you enable the service parameter Block Offnet to Offnet Transfer and make a blind transfer with Cisco Unity Connection, the Q.931 SETUP message which Cisco CallManager sends to the PSTN gateway for an outbound PRI call still reaches the gateway. This transfer results in a dropped call.
|
Component: Call Processing
|
CSCsc88296
|
Call Control: QSIG path replacement kicks in even though there is not enough bandwidth in a location.
|
CSCsc48113
|
Call Control: Phone fails to resume a call and user continues to hear MOH.
|
CSCsc93000
|
Call Control: Cisco CallManager does not send the ring back tone on a blind transfer call scenario.
|
CSCsd08726
|
Call Control: Phone redirects a call with incorrect FAC code.
|
CSCsc82184
|
Change Notify: You cannot change the SIP security profile on a phone.
|
CSCsc81681
|
Database: DN changes on extension mobility (EM) phones can take a long time.
|
CSCsc71873
|
Device Manager: IP phones cannot registered after being reset. The logs display a Number of registered devices exceeded message.
|
CSCsc92504
|
Device Manager: Rebooting a secondary Cisco CallManager node causes phones to unregister on the primary Cisco CallManager node.
|
CSCsc14412
|
H323: Cisco CallManager sets the H225BearerCapability field to 98 98 when the call is redirected through CTI.
|
CSCsc92381
|
H323: Calls failed at the terminal agent when the consult transfer load exceeds 1.5 calls per second.
|
CSCsc97807
|
H323: Cisco CallManager dropped a gateway call while the call was being transferred.
|
CSCsd03212
|
H323: Cisco CallManager stops generating a ring-back tone when the H.245 logical channel opens.
|
CSCsa80120
|
Hunt List: Cisco CallManager service terminates unexpectedly when there is over 5000 calls to the voice messaging system.
|
CSCsc62073
|
Hunt List: Calls from a location that has no bandwidth causes Cisco Unity to failover
|
CSCsc95849
|
Line Control: To improve performance, Cisco CallManager needs to reduce the number of traces that are collected.
|
CSCef85737
|
Media Control: For RSVP calls, the video for Cisco VT Advantage (CVTA) fails when CVTA is started just prior to picking up the call.
|
CSCef88433
|
Media Control: Media manager can not handle two saved connections on a RSVP call.
|
CSCeg20136
|
Media Control: Cisco CallManager needs to adjust flow control based on video bandwidth reservation negotiation.
|
CSCsc17961
|
Media Control: SIP video pass thru fails when MTP is dynamically allocated.
|
CSCsc63298
|
Media Control: SIP call to H.323 Fax gateway fails when using T.38.
|
CSCsc81024
|
Media Control: SIP call through a H.323 ICT fails to resume when H.323 ICT has asymmetric region configured.
|
CSCsc87293
|
Media Control: The voice path between SIP Phones no longer exists after a QSIG Path Replacement that is triggered by multiple blind transfers.
|
CSCsc88318
|
Media Control: Call fails when INVITE w/T38 Session Description Protocol (SDP) is not forwarded to the next cluster.
|
CSCsc88625
|
Media Control: When Cisco CallManager receives an OLC ACK message from H.323 MOH, it does not need to generate a Sendonly offer.
|
CSCsc95963
|
Media Control: Video calls using H.264 between SIP and non-SIP endpoints fail.
|
CSCsc97011
|
Media Control: SIP video calls fail when the video region is set for greater than 768 Kbps and one of the endpoints is using H.261.
|
CSCsd00951
|
Media Control: SIP endpoint call to a MGCP GW fails after negotiating a G.729 with annex codec.
|
CSCsd07995
|
Media Control: Cisco CallManager process crash when there is a T.38 fax call on a SIP to H.323 intercluster trunk.
|
CSCsd09808
|
Media Control: SIP pass-through call has video failure.
|
CSCsd13361
|
Media Control: Video call fails when the a SCCP phone shares a line with a SIP phone and RSVP is enabled.
|
CSCsd17117
|
Media Control: Calls fail when the call goes through a IOS MGCP gateway to a third-party SIP phones and vice versa.
|
CSCsd17456
|
Media Control: Video call from H.323 intercluster trunk to a H.323 endpoint fails when RSVP is enabled and the call is placed on hold.
|
CSCsd19183
|
Media Control: You cannot switch to video in the middle of a audio call.
|
CSCsd24796
|
Media Control: Cisco CallManager does not allow an IPVC PSTN call to be setup using G.722.
|
CSCsc97583
|
MGCP: Hookflash transfer fails when Cisco CallManager does not receive a Progress or Alert message from the Telco.
|
CSCsc83684
|
QSIG: Calls across a QSIG ICT fail when the call is transferred by a Cisco IP Softphone.
|
CSCsd17222
|
PRI: Call from PSTN to Cisco SIP phone fails.
|
CSCsa79452
|
RSVP Agent: Non-RSVP call ties up reserved RSVP resources.
|
CSCsd06601
|
RSVP Agent: SIP phones that are registered with Cisco CallManager consume extra RSVP resources during the ring state.
|
CSCsd09096
|
RSVP Agent: Call to a shared DN on a SCCP and SIP phones consumes 3 RSVP resources.
|
CSCef09978
|
SCCP: StationD process sends unnecessary signals during registration and during a call.
|
CSCsc86632
|
SCCP: Phone does not update the connected number that is displayed when a call is parked over a QSIG trunk.
|
CSCsd05774
|
SCCP: Cisco CallManager behaves inconsistently on a callback that was activated through a forwarded call over a trunk that was enabled with a Forced Activation Code (FAC).
|
CSCsd14697
|
SCCP: Phone does not display the service buttons after Cisco CallManager is restarted.
|
CSCsd02045
|
SIP: Cisco CallManager ignores some H.264 video parameters.
|
CSCsd04350
|
SIP: Cisco CallManager does not use session level Secure Device Provisioning (SDP) Mode.
|
CSCsb82854
|
SIP Station: Phones display the DN of SIP phones in the Line Group Members (LGMs) on a call to Hunt Pilot.
|
CSCsb85007
|
SIP Station: Cisco IP phones 7940/7960 fail to register with blank credentials.
|
CSCsc18476
|
SIP Station: Caller hears a ringback, but the phone does not actually ring when the call is forwarded through a SIP trunk to a phone on another cluster.
|
CSCsc35502
|
SIP Station: Cisco CallManager has missing consult call events in the CiscoTransferStart event.
|
CSCsc56226
|
SIP Station: Call information is missing on a referred call.
|
CSCsc64288
|
SIP Station: RFC3261 compliant phone cannot make calls when HTTP digest is enable.
|
CSCsc70787
|
SIP Station: SIP phones do not support the hospitality feature.
|
CSCsc99957
|
SIP Station: Phone does not display the forwarded call information hen the call comes over JTAPI using a CTI route point from Cisco Emergency Responder.
|
CSCsd03158
|
SIP Station: Cisco CallManager does not send a device unregistered message when a multi-line phone is reset.
|
CSCsd05260
|
SIP Station: Cisco CallManager does not automatically insert the international prefix 000 and the national 00 prefix numbers.
|
CSCsd12929
|
SIP Station: Secure SIP phone models 7970G/7971G-GE, 7941G/7961G, and 7941G-GE/7961G-GE, and 7911 reset following a failover.
|
CSCsd13874
|
SIP Station: SIP phones has a 4 second delay for interdigit timeout.
|
CSCsd20511
|
SIP Station: Cisco CallManager sends an unsolicited MWI notify message to third-party SIP phones.
|
CSCsd22172
|
SIP Station: Third-party phone received a 404 response for an Invite message.
|
CSCsd24382
|
SIP Station: Calls in progress counter shows that there are hung calls even when there are no calls in the system.
|
CSCsc78467
|
SIP Trunk: Cisco CallManager does not attempt to contact other DNS servers when the first server is unavailable.
|
CSCsc91350
|
SIP Trunk: Cisco CallManager does not process all SIP packets that arrive at the interface.
|
CSCsc92167
|
SIP Trunk: Cisco CallManager transmits 180 and 183 messages with a Remote Party ID that contains the connected Names after it receives a of 200-OK message.
|
CSCsc96384
|
SIP Trunk: Phones do not receive a ringback tone when MTP is disabled on the SIP trunk.
|
CSCsd01708
|
SIP Trunk: Cisco CallManager reject s a call when the second INV message arrives before the 4xx ACK to the first INV message.
|
CSCsd05892
|
SIP Trunk: Call transfer between an agent and an IVR route point fails when it is redirected and transferred between two clusters.
|
CSCsd06441
|
SIP Trunk: Phones receive the reorder tone for calls that go through a SIP ICT trunk that is using Transport Layer Security (TLS).
|
CSCsd25114
|
SIP Trunk: Voice messaging on some phones do not work when the SIP trunk between Cisco CallManager and Cisco Unity has MTP disabled.
|
CSCsc87699
|
SS Callback: Callback does not get cancelled on a monitored phone when the DN is removed.
|
CSCsc89639
|
SS Callback: Call does not get released at the originating phone on a callback over Annex M.1QSIG ICT trunk.
|
CSCsc95093
|
SS Callback: Phone does not use the full translation pattern to dial a number after a callback notification.
|
CSCsc76702
|
SS CallPark: Cisco CallManager Administration does not verify that the value entered for call park display timer field is equal to or greater than the Call Park Reversion Timer
|
CSCsc76797
|
SS Callpark: Cisco CallManager Administration does not verify that the call park reversion timer is less than the call park display timer.
|
CSCsc78450
|
SS Callpark: The Call Park Configuration Settings Help page incorrectly states that call park numbers cannot overlap between Cisco CallManager servers.
|
CSCsc41435
|
SS MCID: Cisco CallManager does not send a Malicious Call Identification (MCID) request on an E1 QSIG trunk.
|
CSCsc79463
|
Subnotframework: Authorization fails when the presence group permission option is set to Use System Default.
|
CSCsd10419
|
Subnotframework: Cisco CallManager has high CPU usage during a SIP Presence line subscription stress test.
|
CSCsc36348
|
System: Device Pool reset s take much longer on a Cisco CallManager 5.0 system.
|
CSCsc45124
|
System: Initialization times for a Cisco CallManager 5.0 system are much longer.
|
CSCsc62081
|
System: Cisco Unity fails when the SDL links between nodes go out of service and then go back in service.
|
CSCsc65526
|
System: The default value for code yellow entry latency timer should be 60msec.
|
CSCsd03545
|
Unknown: Cisco CallManager Administration uses GMT time instead of the selected time zone when you select the Use Originating Device Time Zone option for the time of day feature while configure the originating device.
|
CSCsd07209
|
Unknown: The CallsInProgress counter display calls in progress when there are no calls.
|
Component: CPI-Appinstall
|
CSCsc71932
|
Cisco CallManager installation displays misleading error message during an upgrade.
|
CSCsc85288
|
Incorrect certificates are created after installing Cisco CallManager on a subscriber node. This results in inactive services on the subscriber.
|
CSCsc96465
|
Installation program does not clean up the /etc/hosts file when you install on subsequent nodes.
|
CSCsc97261
|
Cisco Mobility Manager does not notify you when you use a duplicate IP address.
|
CSCsd15299
|
Cisco CallManager outputs PAM authentication messages to the console.
|
Component: CPI-Cert-Mgmt
|
CSCsc75021
|
Certificate management requires a privacy enhanced mail (PEM) file.
|
CSCsc75033
|
Cisco CallManager and CAPF certificates cannot be displayed because certificate management requires a partial certificate name in the XML file.
|
CSCsc98200
|
Certificate management does not completely delete a trust certificate.
|
CSCsc99747
|
On a certificate regeneration, certificate management displays error message because it calls the certificate management backend multiple times.
|
CSCsd00137
|
The system does not log certificate management messages in the certm.log file.
|
Component: CPI- DMA
|
CSCsc37545
|
DMA status window does not display in the foreground when DMA is launched.
|
CSCsc83455
|
DMA validation fails when there is a large database.
|
CSCsd12267
|
Cisco CallManager does not automatically activate the AXL service when you upgrade from Cisco CallManager 4.1 to Cisco CallManager 5.0.
|
CSCsd15536
|
The progress indicator does not display the status during all phases.
|
Component: CPI-OS
|
CSCsa69619
|
The system does not save diagnostic information in the trace when there is a kernel panic.
|
CSCsb24327
|
Phones unregister when yon upgrade the system.
|
CSCsb81155
|
Administrators with no root access cannot fix corrupted partitions.
|
CSCsb81161
|
After rebooting Cisco CallManager, the installation menu for a new sound card displayed.
|
CSCsb99789
|
Cisco Messaging Interface (CMI) does not start when you reboot because the OS does not detect a Aten USB device.
|
CSCsc00895
|
MCS server displays a different shutdown and power off behavior on a Cisco CallManager 5.0 system.
|
CSCsc34687
|
You cannot set the network interface card for 1 GB speed by using the set network CLI command.
|
CSCsc37662
|
An upgrade stalls as a result of a database lockup
|
CSCsc68429
|
Cisco CallManger 5.0 does not support NIC teaming in fault tolerant mode.
|
CSCsc78315
|
Cisco CallManager can not boot up from a mirrored drive after a power outage.
|
CSCsc89865
|
Cisco CallManager 5.0(1) does not automatically enable Cisco Security Agent.
|
CSCsc95581
|
Under load, phones fail to register to Cisco CallManager.
|
CSCsc96018
|
You cannot use numerals in the name field when you create a remote account.
|
CSCsd11449
|
When you upgrade Cisco CallManager, the BIOS does not get upgraded.
|
Component: CPI- Security
|
CSCsc27888
|
Cisco CallManager system encounters TCP Send errors when IPSec is enabled.
|
CSCsc37096
|
Cisco CallManager does not restrict SFTP access.
|
CSCsd00153
|
Ping utility fails when the Validate IPSec flag is enabled.
|
CSCsd15426
|
Cisco Security Agent rules fail to load correctly.
|
Component: CPI -Service-Mgr
|
CSCsc70230
|
There are no options to stop the Cisco CallManager service from restarting automatically after a crash.
|
CSCsc88204
|
The Service Manager process does needs provide details when it encounters an error.
|
CSCsd01578
|
After restoring the backup data with Disaster Recovery Framework, some services do not restart automatically.
|
CSCsd19290
|
After upgrading Cisco CallManager, Cisco CallManager Serviceability and CLI report that some services are not running.
|
Component: CPI-UI
|
CSCsc83951
|
Software Installation/Upgrade Status does not always display the installation completed message.
|
CSCsc88915
|
When you change the IP address of a node, Cisco CallManager Administration does not prompt the user to reboot the other nodes.
|
CSCsc98923
|
You cannot delete files from the TFTP directory from the Platform page.
|
Component: Database
|
CSCei37242
|
Cisco CallManager service terminates while searching for available voice mail in a hunt list.
|
CSCsa88961
|
Cisco CallManager does not support the GMT+2 (Israel) timezone.
|
CSCsb70554
|
The display name gets copied to alerting name field in dialing number configuration.
|
CSCsb88240
|
RTMT does not display correct instances of the subscribed Table list.
|
CSCsb91158
|
Upgrade from Microsoft Windows platform fail when there is no reverse DNS entry setup for the subscriber servers.
|
CSCsc08482
|
Administrators cannot run the CLI command set trace.
|
CSCsc19293
|
The dbmon process cored dumped when the system is restarted.
|
CSCsc42572
|
Upgrade of a publisher server failed when an IP address is added to the server list.
|
CSCsc44076
|
Cisco CallManager SIP sends multiple Restart Notify messages to a phone during the extension mobility login.
|
CSCsc44976
|
Cisco CallManager does not reinitialize database replication in a cluster when there is a failure.
|
CSCsc57349
|
Cisco CallManager does not display details on Data Source Name (DSN).
|
CSCsc70780
|
RTMT fails to display ReplicationQueueDepth for Enterprise Replication Perfmon Counter.
|
CSCsc74763
|
The run sql CLI command does not support all SQL stored procedures.
|
CSCsc78720
|
Cisco CallManager Administration does not validate for overlapping range entries.
|
CSCsc86656
|
The Device Reset Queued DB perfmon counter has an incorrect value.
|
CSCsc88165
|
After updating the VG248 gateway using Bulk Administration, the database response to an application can take up to 30 seconds.
|
CSCsc91096
|
Discard digits instruction (DDI) gets disabled on Route Pattern page for patterns without "@ "and in non-dotted patterns
|
CSCsc94627
|
Cisco CallManager Administration displays a SQL exception error when you adding Phone NTP references in the Date/Time group Configuration page.
|
CSCsc97177
|
DBMON process cored with NcsTcpConnectionServer:svc() *ERROR* Connection message.
|
CSCsc98918
|
After upgrading the server, the database replication on Cisco CallManager 5.0(1) failed while restoring the data.
|
CSCsc99206
|
Subscriber reboot causes an Informix process panic and af and shmem stack trace to be written in the core directory.
|
CSCsc99443
|
Database monitor does not send an IDSReplicationFailure alarm when failure occurs.
|
CSCsc99525
|
DBAlarmCatalog does not have alarms for replication status.
|
CSCsd00062
|
Attendant console and pilot point failovers take more than 5 minutes when the publisher node is down.
|
CSCsd00422
|
Cisco CallManager Java-based service trace configuration changes do not take effect unless you restart the service.
|
CSCsd01119
|
Administrators cannot reset some user password from Cisco CallManager Administration.
|
CSCsd03145
|
Cisco CallManager 5.0(1) publisher database get stuck in read-only mode when the Disaster Recovery Framework (DRF) backup is interrupted.
|
CSCsd08209
|
The value in the device pool parameter in the Device Default web page does not get assigned to the phone.
|
CSCsd09072
|
You cannot remove a standard application user from a standard user group.
|
CSCsd09231
|
DBMon process core dumped after upgrading a subscriber server.
|
CSCsd10825
|
SIP Realm Configuration allows users to enter 64 characters in the digest credential field.
|
CSCsd11509
|
The Cisco CallManager process restarts during startup because of a database error.
|
CSCsd12294
|
Ports became unassociated when the user group for CTI ports and route points changed after upgrading to Cisco CallManager 5.0.
|
CSCsd14073
|
Services do not start immediately following the switch to a new partition because of a delay in the database.
|
CSCsd15099
|
DMA returns a SQL error when you try to upgrade from Cisco CallManager 4.0(2).
|
CSCsd16487
|
Database monitor process core dumped when ODBC failed to pass a connection string.
|
CSCsd17836
|
The database monitor process has a core dump on the subscriber server when connectivity to the publisher server is lost.
|
CSCsd17913
|
After upgrading to Cisco CallManager 5.0, database replication fails between the first node and the subsequent node.
|
CSCsd18572
|
Users can add duplicate records in mgcpslotconfig.
|
CSCsd21768
|
RTMT gets stuck because of MLA authentication.
|
Component: Database Administration
|
CSCsb66052
|
The end users dependency records get corrupted in Cisco CallManager Administration.
|
CSCsb80238
|
Cisco CallManager User does not warn users that the primary line label can not be changed.
|
CSCsc68721
|
CPU usage goes to 99 percent when you try to display route lists.
|
CSCsc77968
|
Cisco CallManager Administration allows an administration to enter a park range pattern [^1-8]. This allows a user to park a call with alphabetic characters, but will not allow a user to retrieve the call.
|
CSCsc82418
|
Cisco CallManager Administration for Cisco CallManager 5.0 has the wrong port numbering scheme for SCCP gateways.
|
CSCsc85024
|
Deleting a SIP dial rule causes a Java exception error.
|
CSCsc85225
|
Active user gets logged out of a session after 3-5 hours.
|
CSCsc90134
|
The gateway registration status does not display all MGCP gateways.
|
CSCsc92779
|
You cannot update the default device profile for Cisco IP Communicator.
|
CSCsc93995
|
The music-on-hold audio file management page does not display the delete or upload button.
|
CSCsc94541
|
Cisco Personal Communications Assistant page displays some text in english when you are using the Japanese locale.
|
CSCsc94933
|
Cisco CallManager Administration does not save the Block this pattern option in the translation pattern configuration.
|
CSCsc95025
|
Call Pickup Group Configuration status never changes from the ready state.
|
CSCsc96036
|
Calling Search Space Configuration takes a long time to display.
|
CSCsc96335
|
Busy Lamp Field Speed Dial configuration takes up to 10 minutes to display.
|
CSCsc98581
|
When you upload a license file on a Cisco CallManager system with Japanese locale, the message box display corrupted text.
|
CSCsc98733
|
SIP Realm Configuration displays Could not perform unpadding: invalid pad byte error message.
|
CSCsc98963
|
The find and list phones query stops working when you change the rows per page setting.
|
CSCsc99037
|
Find and List phones maintain the page number that you are on even if you execute a new query.
|
CSCsd00279
|
Find and List Fast Dial Phone Books in Cisco CallManager User is confusing.
|
CSCsd00803
|
Adding new services from the User pages fail.
|
CSCsd02244
|
Phone fails to reset/restart when you choose the reset/restart button in User Administration.
|
CSCsd03552
|
Changing only DN in Directory Number Configuration causes unwanted side-effects in devices.
|
CSCsd04902
|
Line settings do not get propagated when one of the shared line is connected to a Cisco IP Phone 7960 using SIP.
|
CSCsd16957
|
Cisco CallManager does not display the phones that are part of the dependency records of a device pool.
|
Component: Dialed Number Analyzer
|
CSCsc80363
|
The Dialed Number Analyzer (DNA) application displays the Help > Contents menu tag.
|
CSCsc80373
|
The Next Page link does not work properly when you view the results of a device search in DNA.
|
CSCsc91062
|
The Dialed Number Analyzer (DNA) application does not display the proper phone and gateway icons.
|
CSCsc94632
|
The SIP hostname analysis is case sensitive and the Wireless LAN Services Module (WSM) trunk analysis does not work properly in the DNA application.
|
CSCsd02687
|
When you do a Search by Phrases with the ALT Key in Cisco Dialed Number Analyzer (DNA), you get an unmapped exception error.
|
CSCsd19759
|
DNA tracing mechanism does not support the Trace Levels Setting option.
|
CSCsd37566
|
DNA does not capture call forwarding information when there are no partitions configured on the system.
|
Component: Directory
|
CSCsb66633
|
The User ID field accepts more than 30 characters.
|
CSCsd05409
|
Directory synchronization on Active Directory 2003 takes a long time.
|
Component: Extension Mobility
|
CSCsd01543
|
Cisco IP Phone 7905 and 7912 display Japanese characters as ? in the extension mobility screens.
|
CSCsd19357
|
Cisco IP Phone 7971 does not display user created softkey template.
|
Component: IPMA Service
|
CSCsd08490
|
After upgrading Cisco CallManager from Microsoft Windows, Cisco IPMA managers configuration page list assistants twice.
|
CSCsd02580
|
The Cisco IPMA Assistant Console does not track reorder calls when the assistant logs off and logs back in.
|
Component: JTAPI SDK
|
CSCsd12240
|
Application cannot update the certificate from the JTAPI Preference user interface.
|
CSCsd23842
|
Phone displays an incorrect modified address in a QSIG scenario.
|
Component: Licensing
|
CSCsc78429
|
After uploading license file, Cisco CallManager service failed to stop.
|
CSCsd07896
|
License manager displays a deletion 4911 error message when requests to provision devices fail.
|
CSCsd11245
|
License manager charges 5 units for low-end phones.
|
Component: QED
|
CSCsc98970
|
You cannot add BRI card to IOS GW 3640 using Cisco CallManager Administration.
|
CSCsc99075
|
Gateway configuration displays SPID1 and SPID2 field when adding BRI to a gateway.
|
CSCsc99083
|
Gateway configuration displays the auto detect field under MGCP BRI gateway page.
|
CSCsc99087
|
Gateway configuration displays the upwait field in the MGCP BRI gateway page.
|
CSCsd02417
|
Cisco CallManager displays a mismatch SCCP MAC address and description.
|
Component:RIS DC
|
CSCsc89694
|
The SelectCmDevice SOAP API returns duplicated devices.
|
CSCsd03678
|
Process Virtual Image counter is obsolete.
|
CSCsd03701
|
Cisco CallManager should provide actual memory and virtual memory usage counters.
|
Component: Rootless
|
CSCsc84528
|
Users gets a validation error message when they enter a valid date.
|
CSCsd00747
|
You can not run gdb, less, etc. remotely.
|
Component: RTMT
|
CSCsc10210
|
RTMT does not have proper error handling when there is a delayed/lost response from the server.
|
CSCsc88227
|
View Real Time Data does not display the list of services in alphabetical order
|
CSCsc93786
|
RTMT cannot support Cisco CallManager log files that are greater than 50 MB in size.
|
CSCsc94067
|
RTMT Device Search returns a DeviceReply failed error message.
|
CSCsc96003
|
Real Time Monitoring Tool Trace and Log Central has slow download performance over a wide area network (WAN).
|
CSCsc98335
|
RTMT display many counters with an error value in the Cisco CallManager Cluster Info dialog.
|
CSCsc98454
|
Saved queries in the RTMT Query Wizard do not display all the nodes in the cluster.
|
CSCsd03317
|
Error always occur when you open the Prog Logs log4j file in View Real-time Data.
|
CSCsd04454
|
User gets an insufficient disk space error while downloading trace files with RTMT.
|
CSCsd08561
|
RTMT displays empty gateway port/channel status.
|
CSCsd11807
|
You cannot install RTMT on a computer that is running the German version of Microsoft XP.
|
CSCsd12426
|
RTMT does not display the correct number of clients when a subscriber is rebooted.
|
CSCsd15552
|
RTMT does not save profiles with updated performance counters.
|
Component: SDL
|
CSCsc89311
|
The SDL start process signal degrade system performance.
|
Component: Security
|
CSCsb10317
|
CAPF does not work when you select Microsoft CA as the Certificate Generation Method.
|
CSCsb61935
|
Phones cannot install certificate when Keon CA is selected as the Certificate Generation Method.
|
CSCsc67671
|
The .passphrase file is missing.
|
CSCsc96805
|
IOS gateways cannot process a Cisco CallManager certificate.
|
CSCsc98482
|
Bundled CTL Client does not detect migrated CTL file.
|
CSCsd02393
|
Certificate manager does not support certificate signing request (CSR).
|
CSCsd07910
|
You cannot change the certificate trust list (CTL) provider port number on a Cisco CallManager.
|
CSCsd08403
|
Cisco CallManager does not display message prompt to restart CTL Provider services when the port number is changed.
|
CSCsd11355
|
You cannot export a CAPF certificate from the CertMgr GUI.
|
Component: Serv-Soap
|
CSCsd01628
|
The collectSessionData call returns status=ok for non-existent counters.
|
Component: SMDI Service
|
CSCsc58288
|
Cisco CallManager stops when the USB cable gets unplugged and plugged back in.
|
Component: SNMP Research Agent
|
CSCsc83214
|
Host Agent, Mib2 Agent and System Appl Agent cannot connect to the master agent when the SNMP master agent is restarted.
|
CSCsc91997
|
TCP-MIB snmp queries increase soft IRQs and impact system performance.
|
Component: TAPI SDK
|
CSCsb64096
|
Application gets stuck during RecordWave().
|
CSCsc20794
|
Application gets stuck during Provider Open for a secure user.
|
Component: TFTP
|
CSCsb75268
|
The CTFTP server should provide header content to identify whether a e file requested is cacheable or not for HTTP requests.
|
CSCsc93286
|
The TFTP process core dump because of libCryptoUtil.so lib issue.
|
CSCsd01761
|
MGCP BRI Gateway configuration does not set the correct compand type for the BRI interface.
|
CSCsd11029
|
TFTP server failed to send configuration files to the off-cluster phone devices.
|
CSCsd13832
|
You cannot add new third-party SIP phone models.
|
Component: WebDialer Service
|
CSCsc65614
|
WebDialer does not work when the publisher node is down.
|
The following firmware caveats apply to this release.
|
CSCsb79445
|
XML API:Phone displays a 503 error after shutting down extension mobility service on a multi-homed host and logging back in.
|
CSCsd51603
|
Calls fail whan the SIP phones are connected behind a firewall.
|
Troubleshooting
For troubleshooting information, refer to the Troubleshooting Guide for Cisco CallManager, Release 5.0(1). This document provides troubleshooting procedures for Cisco CallManager systems. The Troubleshooting Guide for Cisco CallManager, Release 5.0(1) provides guidance for network administrators responsible for managing the Cisco CallManager system, for enterprise managers, and for employees. This document does not cover every possible trouble event that might occur on a Cisco CallManager system but instead focuses on those events that are frequently seen by the Cisco Technical Assistance Center (TAC) or frequently asked questions from newsgroups.
Documentation Updates
This section provides documentation changes that were unavailable when the Cisco CallManager release 5.0 documentation suite was released.
•Errors
•Changes
•Omissions
Errors
This section includes information about errors in the Cisco CallManager Documentation suite.
•Description of the Reset Button
•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
Description of the Reset Button
The Cisco Unified Communications Manager Configuration Settings section of the "System Configuration" chapter of the Cisco CallManager Administration Guide contains incomplete description of the Reset button. The description should comprise:
Click this button to reset all devices that belong to the same Cisco Unified CM Group as this Cisco Unified Communications Manager server.
Note All devices in the Cisco Unified CM Group of which this server is a member get reset, not just those devices that are registered with this server.
Description of the Cisco IP phone proxy server
The Cisco IP Phone Configuration chapter of the Cisco CallManager Administration Guide incorrectly states the description of the Proxy Server. The following table provides the correct description.
Field
|
Description
|
External Data Locations Information
|
Proxy Server
|
Enter the host and port (for example, proxy.cisco.com:80) that are used to proxy HTTP requests for access to non-local host addresses from the phone HTTP client.
The rule contains two parts for when to use the proxy server parameter:
1. The hostname contains a "."
2. The hostname is an IP address in any form
If you do not configure this URL, the phone attempts to connect directly to the URL.
Leave this field blank to accept the default setting.
|
Definition of Originating Codec and Destination Codec
The CAR Report Results chapter of the CDR Analysis and Reporting Administration Guide incorrectly states the definition of the Orig. Codec and Dest. Codec fields in the Gateway Detail Report. The correct definitions are as follows:
•Orig. Codec--The codec code (compression or payload code) that the call originator used on its sending side during this call. This code may differ from the codec code that was used on its receiving side.
•Dest. Codec--The codec code (compression or payload code) that the destination used on its sending side during this call. This code may differ from the codec code that was used on its receiving side.
Name Correction for Cisco Database Service
The Command Line Interface chapter of the Cisco IP Telephony Administration Guide incorrectly names the Cisco Database service. The correct name is A Cisco DB. For example, to restart the database service using the utils service in the CLI, enter utils service restart A Cisco DB.
Using the Command Line Interface to Stop/Start Services
The Managing Services chapter of the Cisco CallManager Serviceability Administration Guide does not list all the services that can be stopped or started by using the command line interface. The complete list of services includes:
•System NTP
•System SSH
•Service Manager
•A Cisco DB
•Cisco Tomcat
•Cisco Database Layer Monitor
•Cisco CallManager Serviceability
Guidelines for the Cisco CallManager Application User
You do not have to create the Cisco CallManager Attendant Console application user with the user ID of "ac" before changing the user ID as stated in the Cisco CallManager Features and Services Guide. You can use any user ID, but the username of the application user must match the JTAPIUsername parameter configured in the service parameters for Attendant Console Server service.
Password for Cisco CallManager Serviceability Administration
The Cisco CallManager Serviceability Administration Guide incorrectly states that administrators should enter ciscocisco as the password for Cisco CallManager Serviceability Admininstration.
Changes
This section contains changes that have occurred since the original release of the Cisco CallManager release 5.0 documentation.
•Perfmon Counter Name Changes
•Ethernet Settings
•Command Line Interface
Perfmon Counter Name Changes
Table 8 lists the incorrect performance counter name as it appears in Cisco CallManager Serviceability System Guide along with the correct counter name.
Table 8 Perfmon Counter Name Changes
Incorrect Counter Name
|
Correct Counter Name
|
Cisco Dual-Mode Mobility Object
|
Hand Out Aborted
|
HandOutAborted
|
Hand Out In Progress
|
HandOutInProgress
|
Hand Out Aborted
|
HandOutAborted
|
Cisco Extension Mobility Object
|
Successful Logins
|
LoginsSuccessful
|
Successful Logouts
|
LogoutsSuccessful
|
Total Attempted Login/Logout Requests
|
Login/LogoutRequestsAttempted
|
Requests Throttled
|
RequestsThrottled
|
Cisco Tomcat JVM Object
|
KBytes Memory Free
|
KBytesMemoryFree
|
KBytes Memory Max
|
KBytesMemoryMax
|
KBytes Memory Total
|
KBytesMemoryTotal
|
Cisco Tomcat Web Application Object
|
Sessions Active
|
SessionsActive
|
Cisco Video Conference Bridge Device Object
|
ConferenceActive
|
ConferencesActive
|
ConferenceAvailable
|
ConferencesAvailable
|
ConferenceCompleted
|
ConferencesCompleted
|
ConferenceTotal
|
ConferencesTotal
|
Ethernet Settings
In the Cisco IP Telephony Platform Administration Guide, all Ethernet settings only apply to Eth0. You cannot configure any settings for Eth1. Also the Maximum Transmission Unit (MTU) on Eth0 defaults to 1500.
Command Line Interface
Appendix A of the Cisco IP Telephony Platform Administration Guide requires the following changes:
•File View command: Do not use this command to view binary files, because this can corrupt the terminal session.
•Show Hardware command: The command also displays the RAID controller status.
Omissions
This section lists new and additional information that the current version of the Cisco CallManager documentation may not include.
•Setting the Cisco Unified Communications Manager MTU Size
•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
•Time-of-Day Routing Chapter Omits Information About Defined Time Periods
•
Setting the Cisco Unified Communications Manager MTU Size
The maximum transmission unit (MTU) size that you configure for Cisco Unified Communications Manager must not exceed the lowest MTU size that is configured on any link in your network.
The default MTU size is 1500. You can configure the MTU size during product installation, or by using the CLI command set network mtu.
CTI Monitored Lines
To calculate the number of CTI monitored lines in a system, use the following formula:
number of pilot point DNs + (number of clients open * number of directory numbers per phone) + (number of parked directory numbers * number of open clients) = CTI Monitored Lines
Malicious Call Identification Restrictions
The Malicious Call Identification chapter of the Cisco CallManager Features and Services Guide does not list SIP trunk as a restriction. MCID does not support SIP trunks.
Call Control for Attendant Console
The Attendant Console chapter of the Cisco CallManager Features and Services Guide does not include the following information.
Make sure that you check the Allow Control of Device from CTI checkbox on the Phone Configuration window for each attendant phone. The system enables this field by default. If this checkbox is not checked for the attendant phone, call control does not come up for the attendant console.
Destination Address for SIP Trunk Configuration
The following information should be added to the Destination Address in the SIP Trunk Configuration Settings table.
Table 9 Trunk Configuration Settings for SIP Trunks
Field
|
Description
|
SIP Information
|
Destination Address
|
The Destination Address represents the remote SIP peer with which this trunk will communicate, the allowed values for this field are a valid V4 dotted IP address, fully qualified domain name (FQDN), or DNS SRV record only if the Destination Address is an SRV filed is checked.
Note SIP trunks only accept incoming requests from the configured Destination Address and the specified incoming port that is in the SIP Trunk Security Profile, which is associated with this trunk.
If the remote end is a Cisco CallManager cluster, DNS SRV represents the recommended choice for this field. The DNS SRV record should include all Cisco CallManagers within the cluster.
|
Destination Address is an SRV
|
This field specifies that the configured Destination Address is an SRV record.
The default value unchecked.
|
Music On Hold
The Music On Hold chapter of the Cisco CallManager Features and Services Guide does not include the following information.
The Media Resources > MOH Audio File Management menu option allows the administrator to perform the following functions:
•Display a list of the MOH audio source files that are stored on the system. For each file, the window displays the file name, file length, and file status.
•Upload new MOH audio source files. To do so, click the Upload File button and use the Upload File popup window that displays. For configuration details, refer to the description of the Upload File button in the Music On Hold Audio Source Configuration Settings table of the Music On Hold chapter in the Cisco CallManager Features and Services Guide.
•Select MOH audio source files for deletion. You cannot delete MOH audio source files that specify the In Use state.
Resource Reservation Protocol (RSVP)
The Resource Reservation Protocol chapter of the Cisco CallManager System Guide does not include the following information.
In an RSVP session, special configuration applies if all of the following conditions exist:
•One of the end point devices, such as Cisco IP Interactive Voice Response (IP IVR), has been configured to support only the G.711 codec.
•RSVP has been configured for the call.
•The inter-region codec specifies G.729 between the calling RSVP Agent and the called RSVP Agent.
When the call is made, in order to achieve successful allocation and reservation of RSVP Agent resources and bandwidth, the administrator must configure the Media Termination Point (MTP)/RSVP Agent with the G.729 codec in addition to the pass-through codec. This configuration allows insertion of a transcoder between the RSVP Agent of the called side and the called device at the time of media connection. When codecs match, codec pass-through takes place; if codecs do not match, a transcoder is needed to allow the call to continue.
If configuration of the G.729 codec in the agent does not take place, the call will fail because Cisco CallManager will not invoke a transcoder that is needed for the RSVP call.
The situation arises if either of the following conditions apply: the inter-region codec is used between calling and called agents, or between two endpoints that specify G.729. Two options exist to enable successful routing of this call:
•Use RSVP Agent for IVR as a transcoder. In this case, the inter-region codec between the transcoder/RSVP Agent and IVR needs to specify the G.711 codec.
•Use software MTP as RSVP Agents and insert a transcoder between IVR and the RSVP Agent for IVR. In this case, the software MTP has to configure the G.729 codec in addition to the pass-through codec.
Keep in mind that the RSVP Agent that has transcoding capability cannot perform G.729-to-G.729 transcoding. If you use a transcoder as an RSVP Agent, you must either use the pass-through codec or configure so that one of the codecs used on both sides of the transcoder specifies G.711.
NIC Teaming
The Cisco IP Telephony Platform Administration Guide does not include the following information.
Cisco CallManager 5.0(1) does not support NIC teaming. Be aware that if you were using NIC teaming with a Windows-based version of Cisco CallManager, you will not be able to use it after you upgrade to Cisco CallManager 5.0(1).
Installing Device Packs and Phone Firmware Loads
The Software Upgrades chapter of the Cisco IP Telephony Platform Administration Guide does not include the following information.
You can also use the Software Upgrade and Installation procedure to upload and install device packs, phone firmware loads, and other COP files.
Saving and Uploading Third-Party Security Certificates
When you save certificates that you obtained from a third-party Certificate Authority (CA) to your PC, Cisco recommends that you use Notepad to open and save the certificate, because this maintains the certificate format.
After you save a certificate, see the Security chapter of the Cisco IP Telephony Platform Administration Guide for information about how to upload it to the system.
Accessing Cisco Security Agent (CSA) Logs
Administrators can use the Trace & Log Central feature in the Real-Time Monitoring Tool (RTMT) to access Cisco Security Agent (CSA) logs. To collect CSA logs, choose the Cisco Security Agent check box in the Select System Logs tab. To access user logs that provide information about users logging in and out, choose the Security Logs check box in the Select System Logs tab. For more information on using RTMT, refer to the Cisco CallManager Serviceability Administration Guide.
Changing the IP Address on a Cisco CallManager Node
If the IP address of the first Cisco CallManager node gets changed while a subsequent node is offline, you may not be able to log in to Cisco CallManager administration on the subsequent node. If this occurs, follow this procedure:
Step 1 Log in directly to platform administration on the subsequent node using the following IP address:
http://server-name/iptplatform
where server-name is the host name or IP address of the subsequent node.
Step 2 Enter your Administrator user name and password and click Submit.
Step 3 Navigate to Settings>IP>Publisher.
Step 4 Enter the new IP address for the publisher and click Save.
Step 5 Restart the subsequent node.
Obtaining a License File
Use the following steps to obtain a license file for a new installation of Cisco CallManager 5.0 phones nodes and for updating the licenses when new phones are added.
Step 1 When you place an order for Cisco devices, Cisco provides a Product Authorization Key (PAK).
Step 2 Register the PAK with Cisco CallManager using the License Registration web tool that is provided on CCO.
Step 3 You must enter the MAC address of the Cisco CallManager server that you are requesting the licenses for, and a valid E-mail Id. You must enter the number of nodes and phone units that you want licenses for.
Note You can determine the number of phone unit licenses that you will require for each phone type using License Calculator in Cisco CallManager Administration. See the "Calculating License Units" section.
Step 4 CCO generates a license file with the number of unit licenses that you requested and sends it you via E-mail using the E-mail ID that you provided in Step 2 .
Step 5 You must upload the license file to the server with the matching MAC address that you provided in Step 3. See the "Uploading a License file" section. This server then takes on the functionality of the license manager.
Note When you buy new phones and you want to update your licenses, go to the License Registration web tool that is provided on CCO and follow Step 3 through Step 5.
Time-of-Day Routing Chapter Omits Information About Defined Time Periods
The "Time-of-Day Routing" chapter of the Cisco Unified Communications Manager System Guide omits the following information.
•If you defined a time period with a specific date, on that specified date, that period overrides other periods that are defined on a weekly basis.
Example:
Consider the following example:
•A time period, afterofficehours, that is defined as 00:00 to 08:00 from Monday to Friday exists.
•A time period, newyearseve, that is defined as 14:00 to 17:00 on December 31st exists.
In this case, on December 31st, the afterofficehours period will not be considered because it gets overriden by the more specific newyearseve period.
Obtaining Documentation
Cisco documentation and additional literature are available on Cisco.com. Cisco also provides several ways to obtain technical assistance and other technical resources. These sections explain how to obtain technical information from Cisco Systems.
Cisco.com
You can access the most current Cisco documentation at this URL:
http://www.cisco.com/techsupport
You can access the Cisco website at this URL:
http://www.cisco.com
You can access international Cisco websites at this URL:
http://www.cisco.com/public/countries_languages.shtml
Product Documentation DVD
The Product Documentation DVD is a comprehensive library of technical product documentation on a portable medium. The DVD enables you to access multiple versions of installation, configuration, and command guides for Cisco hardware and software products. With the DVD, you have access to the same HTML documentation that is found on the Cisco website without being connected to the Internet. Certain products also have .PDF versions of the documentation available.
The Product Documentation DVD is available as a single unit or as a subscription. Registered Cisco.com users (Cisco direct customers) can order a Product Documentation DVD (product number DOC-DOCDVD= or DOC-DOCDVD=SUB) from Cisco Marketplace at this URL:
http://www.cisco.com/go/marketplace/
Ordering Documentation
Registered Cisco.com users may order Cisco documentation at the Product Documentation Store in the Cisco Marketplace at this URL:
http://www.cisco.com/go/marketplace/
Nonregistered Cisco.com users can order technical documentation from 8:00 a.m. to 5:00 p.m. (0800 to 1700) PDT by calling 1 866 463-3487 in the United States and Canada, or elsewhere by calling 011 408 519-5055. You can also order documentation by e-mail at tech-doc-store-mkpl@external.cisco.com or by fax at 1 408 519-5001 in the United States and Canada, or elsewhere at 011 408 519-5001.
Documentation Feedback
You can rate and provide feedback about Cisco technical documents by completing the online feedback form that appears with the technical documents on Cisco.com.
You can submit comments about Cisco documentation by using the response card (if present) behind the front cover of your document or by writing to the following address:
Cisco Systems
Attn: Customer Document Ordering
170 West Tasman Drive
San Jose, CA 95134-9883
We appreciate your comments.
Cisco Product Security Overview
Cisco provides a free online Security Vulnerability Policy portal at this URL:
http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html
From this site, you will find information about how to:
•Report security vulnerabilities in Cisco products.
•Obtain assistance with security incidents that involve Cisco products.
•Register to receive security information from Cisco.
A current list of security advisories, security notices, and security responses for Cisco products is available at this URL:
http://www.cisco.com/go/psirt
To see security advisories, security notices, and security responses as they are updated in real time, you can subscribe to the Product Security Incident Response Team Really Simple Syndication (PSIRT RSS) feed. Information about how to subscribe to the PSIRT RSS feed is found at this URL:
http://www.cisco.com/en/US/products/products_psirt_rss_feed.html
Reporting Security Problems in Cisco Products
Cisco is committed to delivering secure products. We test our products internally before we release them, and we strive to correct all vulnerabilities quickly. If you think that you have identified a vulnerability in a Cisco product, contact PSIRT:
•For Emergencies only — security-alert@cisco.com
An emergency is either a condition in which a system is under active attack or a condition for which a severe and urgent security vulnerability should be reported. All other conditions are considered nonemergencies.
•For Nonemergencies — psirt@cisco.com
In an emergency, you can also reach PSIRT by telephone:
•1 877 228-7302
•1 408 525-6532
Tip We encourage you to use Pretty Good Privacy (PGP) or a compatible product (for example, GnuPG) to encrypt any sensitive information that you send to Cisco. PSIRT can work with information that has been encrypted with PGP versions 2.x through 9.x.
Never use a revoked or an expired encryption key. The correct public key to use in your correspondence with PSIRT is the one linked in the Contact Summary section of the Security Vulnerability Policy page at this URL:
http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html
The link on this page has the current PGP key ID in use.
If you do not have or use PGP, contact PSIRT at the aforementioned e-mail addresses or phone numbers before sending any sensitive material to find other means of encrypting the data.
Obtaining Technical Assistance
Cisco Technical Support provides 24-hour-a-day award-winning technical assistance. The Cisco Technical Support & Documentation website on Cisco.com features extensive online support resources. In addition, if you have a valid Cisco service contract, Cisco Technical Assistance Center (TAC) engineers provide telephone support. If you do not have a valid Cisco service contract, contact your reseller.
Cisco Technical Support & Documentation Website
The Cisco Technical Support & Documentation website provides online documents and tools for troubleshooting and resolving technical issues with Cisco products and technologies. The website is available 24 hours a day, at this URL:
http://www.cisco.com/techsupport
Access to all tools on the Cisco Technical Support & Documentation website requires a Cisco.com user ID and password. If you have a valid service contract but do not have a user ID or password, you can register at this URL:
http://tools.cisco.com/RPF/register/register.do
Note Use the Cisco Product Identification (CPI) tool to locate your product serial number before submitting a web or phone request for service. You can access the CPI tool from the Cisco Technical Support & Documentation website by clicking the Tools & Resources link under Documentation & Tools. Choose Cisco Product Identification Tool from the Alphabetical Index drop-down list, or click the Cisco Product Identification Tool link under Alerts & RMAs. The CPI tool offers three search options: by product ID or model name; by tree view; or for certain products, by copying and pasting show command output. Search results show an illustration of your product with the serial number label location highlighted. Locate the serial number label on your product and record the information before placing a service call.
Submitting a Service Request
Using the online TAC Service Request Tool is the fastest way to open S3 and S4 service requests. (S3 and S4 service requests are those in which your network is minimally impaired or for which you require product information.) After you describe your situation, the TAC Service Request Tool provides recommended solutions. If your issue is not resolved using the recommended resources, your service request is assigned to a Cisco engineer. The TAC Service Request Tool is located at this URL:
http://www.cisco.com/techsupport/servicerequest
For S1 or S2 service requests, or if you do not have Internet access, contact the Cisco TAC by telephone. (S1 or S2 service requests are those in which your production network is down or severely degraded.) Cisco engineers are assigned immediately to S1 and S2 service requests to help keep your business operations running smoothly.
To open a service request by telephone, use one of the following numbers:
Asia-Pacific: +61 2 8446 7411 (Australia: 1 800 805 227)
EMEA: +32 2 704 55 55
USA: 1 800 553-2447
For a complete list of Cisco TAC contacts, go to this URL:
http://www.cisco.com/techsupport/contacts
Definitions of Service Request Severity
To ensure that all service requests are reported in a standard format, Cisco has established severity definitions.
Severity 1 (S1)—An existing network is down, or there is a critical impact to your business operations. You and Cisco will commit all necessary resources around the clock to resolve the situation.
Severity 2 (S2)—Operation of an existing network is severely degraded, or significant aspects of your business operations are negatively affected by inadequate performance of Cisco products. You and Cisco will commit full-time resources during normal business hours to resolve the situation.
Severity 3 (S3)—Operational performance of the network is impaired, while most business operations remain functional. You and Cisco will commit resources during normal business hours to restore service to satisfactory levels.
Severity 4 (S4)—You require information or assistance with Cisco product capabilities, installation, or configuration. There is little or no effect on your business operations.
Obtaining Additional Publications and Information
Information about Cisco products, technologies, and network solutions is available from various online and printed sources.
•The Cisco Product Quick Reference Guide is a handy, compact reference tool that includes brief product overviews, key features, sample part numbers, and abbreviated technical specifications for many Cisco products that are sold through channel partners. It is updated twice a year and includes the latest Cisco offerings. To order and find out more about the Cisco Product Quick Reference Guide, go to this URL:
http://www.cisco.com/go/guide
•Cisco Marketplace provides a variety of Cisco books, reference guides, documentation, and logo merchandise. Visit Cisco Marketplace, the company store, at this URL:
http://www.cisco.com/go/marketplace/
•Cisco Press publishes a wide range of general networking, training and certification titles. Both new and experienced users will benefit from these publications. For current Cisco Press titles and other information, go to Cisco Press at this URL:
http://www.ciscopress.com
•Packet magazine is the Cisco Systems technical user magazine for maximizing Internet and networking investments. Each quarter, Packet delivers coverage of the latest industry trends, technology breakthroughs, and Cisco products and solutions, as well as network deployment and troubleshooting tips, configuration examples, customer case studies, certification and training information, and links to scores of in-depth online resources. You can access Packet magazine at this URL:
http://www.cisco.com/packet
•iQ Magazine is the quarterly publication from Cisco Systems designed to help growing companies learn how they can use technology to increase revenue, streamline their business, and expand services. The publication identifies the challenges facing these companies and the technologies to help solve them, using real-world case studies and business strategies to help readers make sound technology investment decisions. You can access iQ Magazine at this URL:
http://www.cisco.com/go/iqmagazine
or view the digital edition at this URL:
http://ciscoiq.texterity.com/ciscoiq/sample/
•Internet Protocol Journal is a quarterly journal published by Cisco Systems for engineering professionals involved in designing, developing, and operating public and private internets and intranets. You can access the Internet Protocol Journal at this URL:
http://www.cisco.com/ipj
•Networking products offered by Cisco Systems, as well as customer support services, can be obtained at this URL:
http://www.cisco.com/en/US/products/index.html
•Networking Professionals Connection is an interactive website for networking professionals to share questions, suggestions, and information about networking products and technologies with Cisco experts and other networking professionals. Join a discussion at this URL:
http://www.cisco.com/discuss/networking
•World-class networking training is available from Cisco. You can view current offerings at this URL:
http://www.cisco.com/en/US/learning/index.html
This document is to be used in conjunction with the documents listed in the "Obtaining Documentation" section.
CCSP, CCVP, the Cisco Square Bridge logo, Follow Me Browsing, and StackWise are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, and iQuick Study are service marks of Cisco Systems, Inc.; and Access Registrar, Aironet, BPX, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step, FormShare, GigaDrive, GigaStack, HomeLink, Internet Quotient, IOS, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, LightStream, Linksys, MeetingPlace, MGX, the Networkers logo, Networking Academy, Network Registrar, Packet, PIX, Post-Routing, Pre-Routing, ProConnect, RateMUX, ScriptShare, SlideCast, SMARTnet, The Fastest Way to Increase Your Internet Quotient, and TransPath are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0601R)
© 2006 Cisco Systems, Inc. All rights reserved.
Feedback
