Table Of Contents
Release Notes for Cisco CallManager Release 4.0(1)
Contents
Introduction
System Requirements
Determining the Software Version
Compatibility Matrix and Supported Upgrades
Related Documentation
New and Changed Information
Installation and Backup Enhancements
Disabling RIS Data Collector Prior to Upgrading to Cisco CallManager Release 4.0 and Above
Support for New Cisco IP Phones
Menu Changes
Multiple Calls on Directory Numbers (lines)
Shared-Line Enhancements
Unassigned Directory Numbers
Phone Button Template Consolidation for Cisco IP Phone Model 7960 and Cisco Expansion Module Model 7914
Conference and Transfer Enhancements
Configurable Call Forward Information Displayed
Abbreviated Dialing
Configuring Service URL on Phone Buttons
Immediate Divert
Barge and Privacy Enhancements
Barge and cBarge
Privacy
Malicious Call Identification
Annunciator
Multilevel Precedence and Preemption
Attendant Console Enhancements
Cisco CallManager Extension Mobility Enhancements
Cisco IP Manager Assistant (IPMA) Enhancement
Static Digit Analysis
Directory Enhancements
Routing Enhancements
Cisco Unity Voice-Mail Port Adjustments
Additional Media Resources Support
Multilevel Administration Access Enhancements
QSIG Protocol
Session Initiation Protocol (SIP) Trunk
Support for Video Calls
H.323 Enhancements
Removing a Deleted Subscriber
Security
Bulk Administration Tool Enhancements
Tool for Auto-Registered Phone Support Enhancements
CDR Analysis and Reporting (CAR) Enhancements
Tomcat Web Server
New and Changed Information for Cisco CallManager Serviceability
TroubleShooting Trace Setting
Cisco CallManager Trace Collection Tool
Real-Time Monitoring Tool (RTMT) as Standalone Plugin
Serviceability Reports Archive
SNMP and Performance Counter Enhancements
New and Changed Information for Third-Party and SDK Applications
Cisco CallManager Call Detail Record Definition
Cisco CallManager Extension Mobility API Developer Guide Release 4.0(1)
Cisco IP Phone Services Application Development Notes
Cisco JTAPI Developer Guide for Cisco CallManager 4.0(1)
Cisco JTAPI Installation Guide for Cisco CallManager 4.0(1)
Cisco TAPI Developer and Installation Guides for Cisco CallManager 4.0(1)
Changes From CiscoTSP 3.3 to CiscoTSP 4.0
Important Notes
CSCso79248 Do Not Run installxml.vbs in Unified CM Release 3.3 and Later
Uninstall CDR Analysis and Reporting Plugin Before Upgrading to Cisco CallManager 4.0(1)
Locale Installer for Cisco CallManager
Using TAPS to Configure Shared-line Phones
Survivable Remote Site Telephony (SRST) Support
Uninstalling Backup and Restore (BARS) Version 4.0(1)
Adding Cisco CallManager Servers
Softkey Support for Cisco IP Phone Models 7905 and 7912
Resolved Caveats for Cisco CallManager - Release 4.0(1)
Open Caveats for Cisco CallManager - Release 4.0(1)
Documentation Updates
Errors
Installation and Upgrade Document References Incorrect Version of Backup and Restore (BARS)
Cisco Video Link Codec
Cisco IP Communicator
Malicious Call Identification
Changes
Route Pattern/Hunt Pilot Configuration
Troubleshooting Security
Omissions
Fax and Modem Connectivity with Cisco CallManager
Cisco Unity Voice-Mail Port Changes
Static Digit Analysis
Obtaining Documentation
Cisco.com
Ordering Documentation
Documentation Feedback
Obtaining Technical Assistance
Cisco TAC Website
Opening a TAC Case
TAC Case Priority Definitions
Obtaining Additional Publications and Information
Release Notes for Cisco CallManager Release 4.0(1)
Updated June 23, 2008
These release notes describe the new features and caveats for Cisco CallManager Release 4.0(1).
Before you install Cisco CallManager, we recommend that you review the "Important Notes" section for information on issues that may affect your system.
For a list of the open and resolved caveats for Cisco CallManager Release 4.0(1), see "Resolved Caveats for Cisco CallManager - Release 4.0(1)" section and "Open Caveats for Cisco CallManager - Release 4.0(1)" section. Updates for these release notes occur with every maintenance and major release.
To access the documentation suite for voice products, refer to
http://www.cisco.com/univercd/cc/td/doc/product/voice/
Access the latest software upgrades and release notes for Cisco CallManager 4.0 on Cisco Connection Online (CCO) at
http://www.cisco.com/public/sw-center/sw-voice.shtml
Contents
These release notes discuss the following topics:
•
Introduction
•System Requirements
•Compatibility Matrix and Supported Upgrades
•Related Documentation
•New and Changed Information
•New and Changed Information for Cisco CallManager Serviceability
•New and Changed Information for Third-Party and SDK Applications
•Important Notes
•Resolved Caveats for Cisco CallManager - Release 4.0(1)
•Open Caveats for Cisco CallManager - Release 4.0(1)
•Documentation Updates
•Obtaining Documentation
•Obtaining Technical Assistance
Introduction
Cisco CallManager, a network business communication system, provides high-quality telephony over IP networks. Cisco CallManager enables the conversion of conventional, proprietary, circuit-switched PBXs to multiservice, open LAN systems.
System Requirements
Make sure that you install and configure Cisco CallManager Release 4.0 on a Cisco Media Convergence Server (MCS). For information about installing Cisco CallManager Release 4.0 on a Cisco Integrated Communications System (ICS) 7750, go to http://www.cisco.com/public/sw-center/telephony/ics-7750/ics-compatibility.shtml
You may also install Cisco CallManager on a Cisco-approved HP server configuration or a Cisco-approved IBM server configuration.
Caution The installation does not complete if you do not have the exact configuration.
Access the correct Cisco-approved server configuration for IBM server or HP server at
http://www.cisco.com/en/US/products/hw/voiceapp/ps378/prod_brochure_list.html
For system hardware component information and system requirements, refer to Installing Cisco CallManager Release 4.0.
Determining the Software Version
To determine the software version of Cisco CallManager, open Cisco CallManager Administration; then, click Details on the main Cisco CallManager Administration window. The following information displays:
•Cisco CallManager System version
•Cisco CallManager Administration version
•Database information and database DLL versions
Compatibility Matrix and Supported Upgrades
You can find which application versions are compatible with Cisco CallManager Release 4.0(1) and which previous release of Cisco CallManager has upgrade support at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/ccmcomp.htm
Note Be aware that the release of Cisco IP telephony products does not always coincide with Cisco CallManager releases. If a product proves to be incompatible with Cisco CallManager, you need to wait until a compatible version of the product becomes available before you upgrade to Cisco CallManager Release 4.0(1). For the most current compatibility combinations and defects, refer to the documentation that is distributed with the Cisco IP telephony products.
Related Documentation
Refer to the Cisco CallManager Document Guide for a list of documents that are related to Cisco CallManager Release 4.0 at
http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/4_0/doc_gd
Along with the documents listed in the Cisco CallManager Document Guide, the following list gives other related documents for Cisco CallManager Release 4.0.
•Skinny Client Control Protocol Messaging Guide
•Cisco CallManager Call Detail Record Definition
•Cisco IP Phone Services Application Development Notes
•Cisco JTAPI Installation Guide for Cisco CallManager 4.0(1)
•Cisco JTAPI Developer's Guide for Cisco CallManager 4.0(1)
•Cisco TAPI Installation Guide for Cisco CallManager 4.0(1
•Cisco TAPI Developer's Guide for Cisco CallManager 4.0(1)
•Cisco CallManager Extension Mobility API Developer's Guide Release 4.0(1)
•System Error Message
•Cisco CallManager 4.0(1) AXL Programming Guide
•Cisco CallManager 4.0(1) AXL Serviceability Programming Interface Guide
•Cisco CallManager Dialed Number Analyzer Guide
•Cisco WebDialer API Reference
New and Changed Information
This following sections describe new features and changes that are pertinent to this release of Cisco CallManager. The sections include configuration tips for the administrator, information about users, and where to find more information.
•Installation and Backup Enhancements
•Disabling RIS Data Collector Prior to Upgrading to Cisco CallManager Release 4.0 and Above
•Support for New Cisco IP Phones
•Menu Changes
•Multiple Calls on Directory Numbers (lines)
•Shared-Line Enhancements
•Unassigned Directory Numbers
•Phone Button Template Consolidation for Cisco IP Phone Model 7960 and Cisco Expansion Module Model 7914
•Conference and Transfer Enhancements
•Configurable Call Forward Information Displayed
•Abbreviated Dialing
•Configuring Service URL on Phone Buttons
•Immediate Divert
•Barge and Privacy Enhancements
•Malicious Call Identification
•Annunciator
•Multilevel Precedence and Preemption
•Attendant Console Enhancements
•Cisco CallManager Extension Mobility Enhancements
•Cisco IP Manager Assistant (IPMA) Enhancement
•Static Digit Analysis
•Directory Enhancements
•Routing Enhancements
•Cisco Unity Voice-Mail Port Adjustments
•Additional Media Resources Support
•Multilevel Administration Access Enhancements
•QSIG Protocol
•Session Initiation Protocol (SIP) Trunk
•Support for Video Calls
•H.323 Enhancements
•Removing a Deleted Subscriber
•Security
•Bulk Administration Tool Enhancements
•Tool for Auto-Registered Phone Support Enhancements
•CDR Analysis and Reporting (CAR) Enhancements
•Tomcat Web Server
•New and Changed Information for Cisco CallManager Serviceability
•New and Changed Information for Third-Party and SDK Applications
Installation and Backup Enhancements
Cisco implemented the following changes for Cisco CallManager 4.0(1) release.
Backup Changes
Cisco provides two backup utilities:
•Cisco IP Telephony Backup Utility
•Cisco IP Telephony Backup Restore System (BARS)
You use the Cisco IP Telephony Backup utility version 3.5.53 (or later) for servers that are running Cisco CallManager 3.2(x). You use BARS 4.0(2) or later for servers that are running Cisco CallManager 3.3(x) or later.
Both backup utilities support CER 1.2(1) or later and all CRA/CRS and Cisco CAR releases that are compatible with Cisco CallManager.
Changes That Apply to Cisco CallManager 4.0(1) Installations and Upgrades
The following changes apply to all Cisco CallManager 4.0(1) installations and upgrades:
•Cisco CallManager 4.0(1) requires Cisco-provided operating system version 2000.2.5 (or later) and the service release 2000-2-5sr2 (or later.)
•Cisco CallManager 4.0(1) uses two installation disks:
–Cisco CallManager 4.0(1) Installation, Upgrade, and Recovery Disk 1
–Cisco CallManager 4.0(1) Installation, Upgrade, and Recovery Disk 2
You are prompted to insert the appropriate disk during the installation process.
•The Cisco CallManager installation contains additional and more meaningful error messages.
New Installation Changes
The following changes apply to all Cisco CallManager 4.0(1) installations:
•The installation program requires that you have 2.0 gigabytes of available disk space on your server.
•SQL 2000 SP3a installs automatically during the Cisco CallManager installation.
•To back up your system, install and configure the Cisco IP Telephony Backup and Restore System (BARS), version 4.0(2) or later. For more information, refer to the Cisco IP Telephony Backup and Restore System (BARS) Administration Guide, Version 4.0(2) (or later). To obtain the most recent version of this document, go to http://www.cisco.com/univercd/cc/td/doc/product/voice/backup/index.htm.
Important Notes Regarding Upgrades from Cisco CallManager 3.2(x)
The following important notes apply to upgrades from Cisco CallManager 3.2(x) to Cisco CallManager 4.0(1):
•The upgrade program requires that you have 3.0 gigabytes of available disk space on your server.
•You must use Cisco IP Telephony Backup utility version 3.5.53 (or later) to back up your system before you upgrade.
•Cisco CallManager 4.0(1) requires Cisco-provided operating system version 2000.2.5 (or later) and the service release 2000-2-5sr2 (or later.) You must install OS version 2000.2.4 (or later) by using the Same Server Recovery method, upgrade to OS version 2000.2.5 (or later), and then upgrade to the latest service release.
Important Notes Regarding Upgrades from Cisco CallManager 3.3(x)
The following important notes apply to upgrades from Cisco CallManager 3.2(x) to Cisco CallManager 4.0(1):
•The upgrade program requires that you have 3.0 gigabytes of available disk space on your server
•Cisco CallManager 4.0(1) requires Cisco-provided operating system version 2000.2.5 (or later) and the service release 2000-2-5sr2 (or later.) You can upgrade the operating system from version 2000.2.3 (or later.)
•You must install Microsoft SQL Server 2000 Service Pack 3a (or later) before you upgrade to Cisco CallManager 4.0(1).
To back up your system, install and configure the Cisco IP Telephony Backup and Restore System (BARS), version 4.0(2) or later. For more information, refer to the Cisco IP Telephony Backup and Restore System (BARS) Administration Guide, Version 4.0(2) (or later). To obtain the most recent version of this document, go to http://www.cisco.com/univercd/cc/td/doc/product/voice/backup/index.htm.
Upgrade Tips
Clicking the Cancel button during the Cisco CallManager installation/upgrade process causes Cisco CallManager to become nonfunctional. If you click Cancel during the installation process, you must restart the installation from the beginning before you can use Cisco CallManager.
You can increase the system performance on servers with four drives by configuring a drive to collect trace files. The Cisco CallManager documentation instructs you to configure the F: drive to collect trace files; however, you need to configure the drive that is labeled Trace. To determine which drive is labeled Trace, log in to the system by using the local Administrator account and double-click My Computer on the system Desktop. Note the drive letter of the drive that is labeled Trace. Use this drive letter when configuring a drive to collect trace files.
Disabling RIS Data Collector Prior to Upgrading to Cisco CallManager Release 4.0 and Above
Before upgrading to Cisco CallManager Release 4.0 and above, Cisco recommends that the administrator disables the RIS Data Collector to minimize system problems and prevent false alerts. The following procedure describes how to disable the RIS Data Collector.
Procedure
Step 1 From Cisco CallManager Administration, choose Service > Service Parameters.
The Service Parameters Configuration window displays.
Step 2 From the Server pull-down menu, choose any server.
Step 3 From the Service pull-down menu, choose RIS Data Collector.
Step 4 In the Data Collection Enabled field, choose False.
Step 5 Click Update.
You can now perform the upgrade to Cisco CallManager 4.0 and above.
Note After you complete the Cisco CallManager upgrade, be sure to reset the parameter to "True" in the Data Collection Enabled field from the Service Parameters Configuration window to enable RIS data collection.
Related Documentation
•Cisco CallManager Serviceability System Guide
•Cisco CallManager Serviceability Administration Guide
Support for New Cisco IP Phones
Cisco CallManager Release 4.0(1) includes support for Cisco Wireless IP Phone model 7920, the Cisco IP Conference Station 7936, and the Cisco IP Phone model 7970.
Where to Find More Information
•Cisco Wireless IP Phone 7920 Administration Guide
•Cisco IP Conference Station 7936 Administration Guide
•Cisco IP Phone 7970 Administration Guide for Cisco CallManager
Menu Changes
In Cisco CallManager Release 4.0(1), the Automated Alternate Routing (AAR) Group menu option moves from the System menu to the Route Plan menu.
Where to Find More Information
•"Automated Alternate Routing Group Configuration," Cisco CallManager Administration Guide
Multiple Calls on Directory Numbers (lines)
In previous releases of Cisco CallManager, a maximum of 2 calls could exist on a single line (one active and one on hold). In Cisco CallManager release 4.0, multiple calls can exist on the same line. (Depending on the phone model, some phones can display up to 200 calls on a single line. The user scrolls to view each call.) This capability eliminates the need to create multiple instances of the same directory number in different partitions to allow users to share a line and still be able to receive and place multiple calls out of the same line. To easily manage more than one call on the line and to view calling name and number of the calls on the line, a new user-interaction model exists on the phone display.
You can configure up to 200 calls for a line on a device in a cluster, with the limiting factor being the device. As you configure the number of calls for one line, the calls that are available for another line decrease. Cisco IP Phones that support the multicall display (such as a Cisco IP Phone 7960) support up to 200 calls per DN and 2 calls per DN for non-multicall display devices (such as Cisco IP Phone 7905).
Phones that are capable of supporting multiple calls display information for all concurrent calls. For each call, the phone displays a unique call identifier, the selected call status, call information, and the call state.
Note Only the Cisco IP Phone models 7940 and 7960 support multiple calls on directory numbers in release 4.0(1).
Configuration Tips
Using Directory Number Configuration, administrators configure the following multiple call/call waiting line parameters on each phone that is capable of supporting multiple calls:
•No Answer Ring Duration—Used in conjunction with Call Forward No Answer Destination, this field sets the timer for how long the phone will ring before it gets forwarded. Leave this setting blank to use the value that is set in the Cisco CallManager service parameter, Forward No Answer Timer.
•Maximum Number of Calls—You can configure up to 200 calls for a line on a device, with the limiting factor being the total number of calls that are configured on the device. As you configure the number of calls for one line, the calls that are available for another line decrease.
•Call Forward No Answer—This field forwards calls when the phone is not answered after the configured no answer ring duration.
•Busy Trigger—This setting, which works in conjunction with Maximum Number of Calls and Call Forward Busy, determines the maximum number of calls that can be presented at the line.
Example
Max number of calls = 50
Busy trigger = 40
If no calls are present on the line, this line can receive a maximum of 40 calls. If this line originated 40 calls, the line can originate 10 more calls but cannot receive any additional calls. The following formula decides the number of calls that this line can receive: Busy Trigger minus the number of calls that are currently present on this line. So, with 40 calls present on this line, new incoming call 41 gets rejected with a busy cause (and will get forwarded if Call Forward Busy is set). If this line is shared, all the lines must be busy before the incoming calls get rejected. The call initiates alerts on all lines with that DN until the configured No Answer Ring Duration timer value is exceeded. Once the timer value is exceeded, the call diverts to the configured Call Forward No Answer target. To disable call waiting, set the busy trigger to 1. If this line is shared and you want to disable call waiting, set the busy trigger to 1 on all shared DNs.
Configuration Comparisons
Table 1 illustrates the multicall display line configuration differences between Cisco CallManager release 4.0 and release 3.3.
Table 1 Line Configuration Differences for Multicall Display Phones
Feature
|
Release 3.3
|
Release 4.0
|
Maximum number of calls for each line
|
2
|
Up to 200, default specifies 4.
|
Call waiting
|
If call forward busy trigger is set to 1, Call Waiting is disabled. If call forward busy trigger is set to 2, Call Waiting is enabled
|
Set the Busy Trigger to be less than or equal to the Maximum Number of Calls per DN. Default specifies 2.
|
Table 2 illustrates the single line display configuration differences between Cisco CallManager release 4.0 and release 3.3.
Table 2 Line Configuration Differences for Single-Line Display Phones
Feature
|
Release 3.3
|
Release 4.0
|
Maximum number of calls for each line
|
2
|
Default specifies 2.
|
Call waiting
|
If call forward busy trigger is set to 1, Call Waiting is disabled. If call forward busy trigger is set to 2, Call Waiting is enabled.
|
If call forward busy trigger is set to 1, Call Waiting is disabled. If call forward busy trigger is set to 2, Call Waiting is enabled.
|
How this Feature Affects the User
•In previous releases, the user could have only two calls on the same line. Improved display text provides information for managing multiple calls on the same line. The display shows whether a call is holding, alerting or connected. The user can select a call to connect with by navigating between calls in the list.
Where to Find More Information
•"Cisco IP Phone Configuration," Cisco CallManager Administration Guide
•"Cisco IP Phones," Cisco CallManager System Guide
Shared-Line Enhancements
Cisco CallManager supports the following enhancements to shared lines:
•Administrators can now configure devices that are sharing a line to support multiple calls. This allows users on shared-line phones to make or receive a call while the remote phone is in use.
•Call information (such as calling party or called party) displays on all devices that are sharing a line. If the Privacy feature is turned on by one of the devices, other devices that are sharing the line will not see outbound calls made from the device that turned privacy on. All devices will still see inbound calls to the shared line.
•Devices with shared-line appearance support the Call Forward Busy Trigger and the Maximum Number of Calls settings. You can configure Call Forward Busy Trigger per line appearance, but the configuration cannot exceed the maximum number call setting for that directory number.
•Cisco IPMA with shared-line support allows managers and assistants to share lines (refer to the Cisco CallManager Features and Services Guide).
Configuration Tip
•Cisco IP Phones without pixel-based displays (such as the Cisco IP Phone model 7910) cannot manage more than two calls (one inbound, one outbound) per line.
How this Feature Affects the User
•Users that have shared lines can manage multiple calls for the same line appearance. For example, when one user answers a call for the shared line appearance, another user can answer the next incoming for that line appearance. New call display information helps users manage calls on shared lines.
Where to Find More Information
•"Cisco IP Phone Configuration," Cisco CallManager Administration Guide
•"Cisco IP Phones," Cisco CallManager System Guide
Unassigned Directory Numbers
Directory numbers get associated with devices such as phones, route points, CTI ports, and H.323 clients. Administrators manage directory numbers from the Directory Number Configuration and Route Plan Report windows in Cisco CallManager Administration.
When you remove a directory number from a phone, the number still exists within Cisco CallManager. To see a list of directory numbers that are not associated with phones, use the Route Plan Report menu option.
Unassigned DNs allow customers to continue forwarding to voice messaging or another destination for DNs that are no longer assigned to devices. This can happen when employees are reassigned or terminated.
Previous to release 4.0, the system automatically deleted directory numbers when a device was deleted. Because line group support is a feature of release 4.0, you must now keep unassigned DNs.
Configuration Tips
To permanently remove a directory number, you must perform a two-step procedure:
1. Use the Directory Number Configuration window to add, update, and remove directory numbers from a device, route point, or port.
2. Use the Route Plan Report window to delete or update unassigned directory numbers from Cisco CallManager database.
Where to Find More Information
•"Cisco IP Phone Configuration," Cisco CallManager Administration Guide
•"Route Plan Report," Cisco CallManager Administration Guide
•"Line Group Configuration," Cisco CallManager Administration Guide
Phone Button Template Consolidation for Cisco IP Phone Model 7960 and Cisco Expansion Module Model 7914
The standard phone button template for the Cisco IP Phone Model 7960, which supports the Cisco IP Phone Model 7914 Expansion Module, includes buttons for both devices (up to 34 buttons). The template uses buttons 1 and 2 for lines and assigns buttons 3 through 34 as speed dials or lines or for the features privacy and service URL.
If you are upgrading from an earlier release of Cisco CallManager and you have separate templates for the Cisco IP Phone Expansion Module model 7914 and Cisco IP Phone model 7960, Cisco CallManager automatically creates a consolidated phone button template.
The following reasons explain why the Cisco IP Phone model 7960 and Cisco Expansion Module model 7914 phone button templates were updated in release 4.0:
•Make all phone button templates for a model dependent on the maximum number of buttons that are possible for base plus expansion modules.
•Remove the phone button template for the expansion module
•Limit the appearance of features across the base and expansion modules
Configuration Tips
•To create a consolidated phone button template for new users, use the following procedure:
–From the Phone Button Template Configuration window, choose a standard 7960 phone button template.
–Copy the 7960 phone button template, rename it; for example, 7960 with expansion buttons, and click Update. The new phone button template displays with all 34 buttons available for configuring features such as speed dial, service URL, and Privacy.
–Make the applicable feature configurations and click Update.
–Find the phone button template that is available for all Cisco IP Phone models 7960 in the Phone Configuration window, phone button template field.
•After an upgrade to Cisco CallManager release 4.0(1), verify the following phone configuration:
–The field, Phone Button Template, should contain the information, ConsolidatedPhoneTemplate_x, where x is a number that Cisco CallManager assigns.
–The field, Module 1 (and Module 2, if applicable), should contain the information, 7914 14-Button Expansion Module.
How This Feature Affects the User
•Users will now see up to 99 speed dials on the User Options page. To view the speed dials, the user chooses the Add/Update Your Speed Dials link.
Where to Find More Information
•"Cisco IP Phone Configuration," Cisco CallManager Administration Guide
•"Phone Button Template Configuration," Cisco CallManager Administration Guide
•"Cisco IP Phones," Cisco CallManager System Guide
•Customizing Your Cisco IP Phone on the Web
•Cisco IP Phone Guide
Conference and Transfer Enhancements
Cisco CallManager release 4.0 supports several conference and transfer enhancements. The system tears down ad hoc conferences when only two conference participants remain in the conference. This release supports Call Join (join multiple parties on a line into an ad hoc conference) and Direct Transfer (directly transfer two parties on a line to each other without joining the user invoking the Direct Transfer). Participants in an ad hoc conference can list the participants of the conference call, and the originator can selectively drop any participant.
Cisco CallManager supports the following conference call enhancements:
•Join—Using the Join softkey, a user can join up to 15 established calls (for a total of 16) to create an ad hoc conference call.
•Direct Transfer—This enhancement allows a user to transfer two callers on the same line to each other.
•Ad hoc conference—Ad hoc conferences now support multiple concurrent conferences on the same device. When only two participants remain in a conference, Cisco CallManager frees up conference resources and reconnects the two participants in a point-point call.
Note This release does not support Conference bridge chaining for ad hoc conference and barged calls that are created within the cluster.
•Conference List—The conference list feature provides a list of participant directory numbers that are in an ad hoc conference. The name of the participant displays if it is configured in Cisco CallManager Administration. Any participant can invoke the conference list feature on the phone by pressing the ConfList softkey and can view the participants. The conference controller can invoke the conference list feature and can view and remove any participant in the conference by using the Remove softkey.
Note Only the conference initiator can drop any conference party. Any participant in the ad hoc conference can display the list of conference participants if their IP phone has display capabilities. When the ConfList softkey gets pressed, the list of conference participants remains static. The user must press the Update softkey to get the latest list. The list does not update automatically if any participant ends the call or a new participant is added.
Configuration Tips
•To make the conference features available for the user, perform the following procedures:
–Add the Join, RmConf, and Select softkeys by using the Softkey Configuration window.
–Assign the softkey template to the user phone by using the Phone Configuration window.
•Using the Join operation requires conference bridge resources. This release does not support Join across different lines. The total number of participants in the joined call must be less than the configured setting in the Maximum Ad-hoc Conference service parameter. You can configure the number from a default of 4 calls to a maximum of 64 calls depending on the number of calls that the network conference resource can support.
How this Feature Affects the User
•Direct Transfer—When a user has two calls on the same line, the user can transfer the callers to each other. The user highlights the two calls and presses the Select softkey, or when already connected to one call, selects the other call. A check mark appears adjacent to selected calls. After selecting only two calls, the user presses the DirTrfr softkey. The two callers then connect and the user that initiated the direct transfer gets dropped.
•Join—Users can easily join several calls in an ad hoc conference call. With all calls holding on the same line, the user chooses each call for the conference by highlighting the call and pressing the Select softkey. After choosing all calls for the conference, the user presses the Join softkey to establish the ad hoc conference call. A check mark appears adjacent to selected calls. The ad hoc conference remains connected until only two parties remain, and then the conference call reverts to a two-party call.
•List of Conference Participants—Ad hoc conference members can see a list of conference participants by pressing the ConfList softkey. The conference initiator can select a conference participant in the conference list and press Remove to drop the participant from the conference.
Where to Find More Information
•Cisco IP Phones, Cisco CallManager System Guide
•"Softkey Template Configuration," Cisco CallManager Administration Guide
•"Cisco IP Phone Configuration," Cisco CallManager Administration Guide
•Cisco IP Phone Guide
Configurable Call Forward Information Displayed
An administrator can now configure each line on a phone to display the following information for a forwarded call:
•Original Dialed Number (ODN)—This feature, which is enabled by default, causes the original dialed number to display upon call forward.
•Redirected Dialed Number (RDN)—This feature, which is disabled by default, causes the number that was redirected to display upon call forward.
•Calling Line ID (CLID)—This feature, which is enabled by default, causes the caller number to display upon call forward.
•Calling Name ID (CNID)—This feature, which is disabled by default, causes the caller name to display upon call forward.
Configuration Tip
•Configure these fields in the Directory Number Configuration window.
How This Feature Affects the User
•Incoming Call Displays—The Cisco IP Phone can now display both the name and number of the calling party. In addition, if the incoming call was forwarded from a another phone, the phone can display the original called number.
•Outgoing Call Displays—When a user dials a number on the network, the Cisco IP Phone can now display both the called party name and number. If an outgoing call forwards to another phone, the display can provide the "forwarded to" information.
Information might not display for all calls because some network facilities do not support calling and called party displays. Administrators can restrict the use of display information for some calls.
Where to Find More Information
•"Cisco IP Phone Configuration," Cisco CallManager Administration Guide.
Abbreviated Dialing
Abbreviated dialing allows users to quickly access up to 99 speed-dial numbers. While the phone is onhook, users can access the additional speed-dial numbers that are not assigned to speed-dial buttons by using the AbbrDial softkey and an index number.
Configuration Tip
•Administrators configure speed-dial numbers for users in the Phone Configuration window by using the Add/Update Speed Dial link.
How This Feature Affects the User
•Users configure their own speed-dial list by accessing the User Options Menu web page and choosing the Add/Update Your Speed Dials link.
•The user can assign some speed-dial numbers to unused line buttons. The remaining speed dials get assigned to index numbers. Assign these numbers by using the Add/Update Your Speed Dials link in the section called "Speed dials not associated with a phone button."
•To access these speed-dial numbers, the user dials the index number with the phone on-hook and then presses the AbbrDial softkey. The system receives the speed-dial index and dials the associated number.
Where to Find More Information
•"Cisco IP Phone Configuration," Cisco CallManager Administration Guide
•"Cisco IP Phones," Cisco CallManager System Guide
•Cisco IP Phone Guide
Configuring Service URL on Phone Buttons
You can now program phone buttons that are used for lines or speed dial for access to phone services. Use Cisco CallManager Administration to configure the programmable buttons as Service URL buttons for the users phone.
Configuration Tips
•Creating Service URL buttons requires a six-step process:
1. Create an IP Phone service.
2. Create a phone button template to include the service.
3. Add the new phone button template to all phones that require access to the Service URL.
4. Subscribe to the service.
5. Add the Service URL button.
6. Notify users to use the Add/Update Your Service URL Button link on the User Options Menu web page.
How This Feature Affects the User
•Users can program special phone buttons to access a service URL such as FastDials or a weather service. The user accesses the Cisco CallManager User Options Menu web page to subscribe to the phone service and then assigns the service to a Service URL button on the phone.
Where to Find More Information
•"Cisco IP Phones," Cisco CallManager System Guide
•Customizing Your Cisco IP Phone on the Web
Immediate Divert
The Immediate Divert feature immediately diverts a call to a voice-messaging system. Managers and assistants, or anyone who shares lines, use this feature. When the call gets diverted, the line becomes available to make or receive new calls. Both the caller and the called party can use Immediate Divert.
Important Configuration Tips
•Configure this softkey by using the Softkey Template Configuration window of Cisco CallManager Administration.
•The softkey template gets assigned to phones that are in the Cisco CallManager system.
•Feature interaction with route/hunt lists: all calls distributed by a line group will not be diverted to voice messaging.
•No support for immediate divert for inbound calls extended through a Q.SIG trunk.
•No support for immediate divert invocation at hunt list members when the original call is received directly from other than the hunt list.
How This Feature Affects the User
•Users access the Immediate Divert feature by using the iDivert softkey.
•When an incoming call displays on the users phone, the user can choose to answer the call or press the iDivert softkey to send the incoming call to a voice messaging system mail box.
•The called party can divert the incoming call while the call is ringing, after answering the call, or when the call is on hold.
•The calling party can also divert the call to a voice messaging system mail box after the call is connected or when the call is on hold.
Where to Find More Information
•"Immediate Divert," Cisco CallManager Features and Services Guide
Barge and Privacy Enhancements
The Barge and Privacy features work together. Both features work with shared lines only.
Barge and cBarge
Barge adds a user to a call that is in progress. Pressing the Barge or cBarge softkey automatically adds the user (initiator) to the shared-line call (target), and the users currently on the call receive a tone.
Phones support Barge in two conference modes:
•Built-in conference bridge at the target device (the phone that is being barged). This mode uses the Barge softkey.
•Shared (network) conference bridge. This mode uses the cBarge softkey.
Barge supports the following features:
•Three-way barge maximum
•G.711 only
•When the barge target hangs up, the call reverts to a two-way call between the original connected caller and barge initiator, and Cisco CallManager releases the barge resources on the targeted phone.
cBarge includes the following features:
•Creates an ad hoc conference by using network conference resources.
•Maximum number of parties that is supported is based on the Maximum AdHoc Conference service parameter and the maximum number of conference participants that conference bridge resources support.
•Supports all codecs that are available on the conference bridge.
•The conference controller acts as the barge target.
•When two parties are left, Cisco CallManager releases networked conference resources, and the call reverts to a two-party call.
Configuration Tips
•System administrators should not configure both the Barge and cBarge softkeys on one phone.
•cBarge requires availability of network conferencing resource (DSP resource card for bridging media streams during the barge).
•The Party Entrance Tone service parameter has a global effect on Barge, cBarge, Conference, Join, and Meet-Me conference.
•JTAPI and TSP applications do not support barge.
How This Feature Affects the User
•Barge—Users can enter a two-party call on a shared line by pressing the Barge softkey. A party entrance tone alerts the barge targets that a user entered the call.
•Conference Barge—Users can enter a call on a shared line by pressing the cBarge softkey to establish an ad hoc conference call.
Privacy
Privacy lets a user allow or disallow other users of shared-line devices to view its call information or to allow another user to barge into its active calls.
Administrators enable privacy for each device that is sharing a line. Users toggle the Privacy button to enable or disable privacy on their phone. When privacy is enabled, the remote phone that is sharing the line does not display the calling name and number, and remote users cannot barge into a call. Default specifies that Privacy is disabled.
Configuration Tips
•Privacy does not affect call history (missed, placed, received) display on phones with shared-line appearances. If privacy is enabled on phone A and user at phone A places a call on the shared-line appearance, the real-time call information will not display on the other phones; however, the placed call history will show call information on the other phones.
•Cisco CallManager APIs such as JTAP and TSP do not support privacy.
How This Feature Affects the User
•Users can place the phone in privacy mode.
•Users that share lines with a phone in privacy mode cannot barge in to a call.
•Calling name and number do not display on other shared-line phones.
•The administrator assigns the Privacy feature button to a phone, and this affects all lines on the phone. To enable the feature, press the Privacy button. A privacy status icon displays next to the Privacy button and indicates that the Privacy feature is enabled. When Privacy feature is enabled, the user can press Privacy again to disable the feature.
Where to Find More Information
•"Barge and Privacy," Cisco CallManager Features and Services Guide.
Malicious Call Identification
System administrators enable malicious call identification (MCID) service, so a user can identify a suspicious call. While the malicious call is in progress, the user presses the MCID softkey to start the following sequence of events:
•Immediately notifies the Cisco CallManager system administrator by setting an alarm.
•Flags the Cisco CallManager cluster CDR as a malicious call.
•Notifies off-net resources such as the Public Switched Telephone Network (PSTN) of the malicious call, so off-net resources can to take action.
The following devices and features support MCID:
•All SCCP gateways
•MGCP PRI-Backhaul network interface for E1(ETSI) and standard T1(NI2)
•H.323 trunks and gateways
•Extension Mobility
•Conference calls
The system sends notifications of malicious calls through facility information element (IE) messages by using the following protocol standards:
•Q.932-Digital Subscriber Signaling System 1 (DSS 1)—Generic Procedures for the Control of ISDN Supplementary Services
•Q.951.7—Stage 3 description for number identification supplementary service using DSS 1: Malicious Call Identification (MCID)
•EN 300 130-1—ISDN Malicious Call Identification (MCID)
Configuration Tips
•To configure MCID, the administrator must set a service parameter, configure an alarm, add a softkey to a template, and assign the softkey template to the user phone.
•Because QSIG has no standard for MCID the feature does not work on a QSIG connection.
•Intercluster trunks do not support MCID because Cisco CallManager does not support the MCID-T component. MCID-T, a terminating function, accepts an MCID invocation and responds with a success or failure to perform the action.
How This Feature Affects the User
•When the user has access to the MCID feature and is connected to a suspicious call, the user presses the MCID softkey and receives a tone and display (if a display is available) to confirm the action. This action alerts the administrator by setting an alarm and by creating a special CDR record.
Where to Find More Information
•"Malicious Call Identification," Cisco CallManager Features and Services Guide
Annunciator
An annunciator, a Skinny Client Control Protocol (SCCP) device that uses the Cisco IP Voice Media Streaming Application service, enables Cisco CallManager to play prerecorded announcements (.wav files) and tones to Cisco IP Phones, gateways, and other configurable devices. The annunciator, which works with Cisco CallManager Multilevel Precedence Preemption (MLPP), enables Cisco CallManager to alert callers as to why the call fails. Annunciator can also play tones for some transferred calls and some conferences.
Annunciator includes the following features:
•You can use up to two recorded audio WAV files for an announcement.
•Announcements can play once or can repeat at regular intervals.
•The annunciator.xml defines announcements and tones.
•The annunciator device reads the database for service parameters, device settings, user locales, and network (country) locales.
•Annunciator supports Wideband, G.711 mu-law, G.711 a-law, and G.729a codecs.
•Annunciator supports multiple user locales and multiple network (country) locales.
•Annunciator supports up to 400 simultaneous announcements, depending on your network configuration and server capability. The default setting equals 48.
•A single annunciator device gets inserted into the database when you activate Cisco IP Voice Media Streaming Application service in Cisco CallManager Administration.
Where to Find More Information
•"Annunciator," Cisco CallManager System Guide
•"Annunciator Configuration," Cisco CallManager Administration Guide
Multilevel Precedence and Preemption
The Multilevel Precedence and Preemption (MLPP) service, introduced in Cisco CallManager 4.0, allows properly validated users to complete higher-priority calls by preempting lower-priority calls. Higher-priority calls take precedence over lower-priority calls. MLPP complies with ANSI T1.619/T1.619a and Generic Switching Center Requirements (GSCR).
MLPP plays a tone to indicate to users on an IP-to-IP phone call that their call is being preempted. A user with higher precedence can also preempt a call with lower precedence that is made through a gateway. MLPP also provides Alternate Party Diversion (APD), which allows Cisco CallManager to route the priority call to a different phone if the target party does not answer the call.
The following terms pertain to MLPP service:
•Precedence—Priority level that is associated with a call
•Preemption—Process of terminating lower-precedence calls that are currently using the target device such that a call of higher precedence can be extended to or through the device.
•Domain—Subscription option of the originating user determines the domain. Only higher-precedence calls in the same domain can preempt connections that calls in one domain are using.
Administrators configure the MLPP indication, preemption, and domain ID at the device and device pool level. Administrators can configure five precedence levels: Flash Override (highest), Flash, Immediate, Priority, and Routine (lowest). Administrators configure precedence patterns within route patterns and translation patterns.
Users can only preempt lower-priority calls on devices that are in the same domain ID. Predefined audio tones and announcement messages that are sent by the annunciator device notify users of the higher-precedence call.
The following devices currently support MLPP: Cisco IP Phone models 7905, 7912, 7940, and 7960,7970, Cisco IP SoftPhone that uses SCCP, and MGCP-controlled TDM trunks that are using PRI/CAS.
MLPP service exhibits the following features:
•PRI signals MLPP messages. T1-CAS signals via DTMF tones.
•Calling search spaces (CSS) control user permissions to dial a precedence pattern.
•MLPP service does not restrict the construction of route patterns. Typically, a route pattern or translation pattern contains a precedence digit.
•Alternate party target and Ring No Answer (RNA) timer can be configured per line.
•MLPP settings can be configured by using the Bulk Administration Tool (BAT).
From Cisco IP Phone to Cisco IP Phone, a user initiates a precedence call by dialing a well-known route pattern or translation pattern with embedded precedence selectors as part of the pattern. The device's calling search space determines whether the user is authorized for the specified precedence. If the precedence is not authorized, the call does not get extended.
The target of the precedence call receives appropriate visual and/or audible notification of a precedence call, depending upon the relative precedence of the existing calls in progress. If the target user acknowledges the precedence call attempt, the precedence call gets extended to the target.
Provision exists for optional configuration of precedence alternate party diversion target in the event that the target does not acknowledge the precedence call request. If no alternate party target is defined, normal Call Forward No Answer (CFNA) and Call Forward Busy (CFB) paths get followed. Preempted parties on Cisco IP Phones receive a tone until they hang up. Gateway parties simply get disconnected. The system does not permit modifying the precedence level of a call in midcall.
From Cisco IP Phone to trunk, MLPP service first authenticates precedence call setup through an MLPP-enabled gateway that is configured in the Cisco CallManager cluster. If the target gateway is fully subscribed (that is, all DS0s are in use), the precedence of other calls on the route group gets sampled for precedence level. A call with lower precedence gets selected, all participants in the call receive audible notification of the imminent call preemption, and the selected lower-precedence call gets terminated. The selected channel gets reserved, and a precedence call gets extended across the trunk to the destination. Precedence level gets passed over a gateway trunk, but not the domain ID, which should be configured on the trunk.
Configuration Tips
•No support exists for precedence and preemption of ad hoc conference calls.
•MLPP supports single-site deployments. No provision exists for extending a precedence calls and preempting existing calls across an IP trunk.
•MLPP does not support the Lookahead For Busy (LFB) option.
•Annunciator supports only MLPP announcements. The annunciator is not available as a general-purpose annunciator.
How This Feature Affects the User
•When the administrator enables MLPP for a phone, users can perform the following tasks:
–Users can choose a priority (precedence) level for an outgoing call.
–Users can make a priority call.
–Users can receive a priority call.
–Users can accept a higher priority call (preemption).
•When a user makes or receives an MLPP-enabled call, special ring tones, call waiting tones, and icons identify the type of call.
Where to Find More Information
•"Multilevel Precedence and Preemption," Cisco CallManager Features and Services Guide
•"Device Pool Configuration," Cisco CallManager Administration Guide
•"Enterprise Parameters Configuration," Cisco CallManager Administration Guide
•"Associated Alternate Routing Group Configuration," Cisco CallManager Administration Guide
•"Partition Configuration," Cisco CallManager Administration Guide
•"Calling Search Space Configuration," Cisco CallManager Administration Guide
•"Route Pattern/Hunt Pilot Configuration," Cisco CallManager Administration Guide
•"Translation Pattern Configuration," Cisco CallManager Administration Guide
•"Annunciator," Cisco CallManager System Guide
•"Annunciator Configuration," Cisco CallManager Administration Guide
•"Gateway Configuration," Cisco CallManager Administration Guide
•"Cisco IP Phone Configuration," Cisco CallManager Administration Guide
•"Device Profile Configuration," Cisco CallManager Administration Guide
•"Device Profile Defaults Configuration," Cisco CallManager Administration Guide
•Cisco IP Phone administration guide that matches your phone model
•Firmware release notes for your phone model
Attendant Console Enhancements
Cisco CallManager Attendant Console, Release 1.3(1) is compatible with Cisco CallManager, Release 4.0(1). The following list gives Cisco CallManager Attendant Console enhancements:
•Support for Call Queuing—When a call comes in to a pilot point and all hunt groups members are busy, Cisco CallManager answers the call and inserts it into the queue when the queue is not full. If the queue is full, the call gets redirected to "AlwaysRoute" member. If the "AlwaysRoute" member is not configured, the call gets dropped. While the call is in the queue, the call gets put on hold, and MOH plays to the caller. Cisco CallManager redirects the call to the next available hunt group member. When the call is in the queue for longer than the configured HoldTime, the call gets redirected to the "AlwaysRoute" member. If the "AlwaysRoute" member is not configured, no action gets taken. Attendants cannot see calls in the queue.
•Support for broadcast calls—When a call arrives at the broadcast hunting pilot point, Cisco CallManager answers the call and inserts it into the queue if the queue is not full. Cisco CallManager Attendant Console broadcasts the call to all available attendants. If the queue is full, the call gets redirected to "AlwaysRoute" member. If the "AlwaysRoute" member is not configured, the call gets dropped. While the call is in the queue, the call gets put on hold and MOH plays to the caller. Cisco CallManager redirects the call to the attendant who answers the call.
•Support for shared lines—Calls to a pilot point get routed to a shared-line phone only when the shared line is not in use on another remote phone. Attendant phones can share lines with other attendants or non-attendants.
•Multiple calls on a single line—Cisco CallManager Attendant Console supports multiple calls on a single line based on the line setting configuration in Cisco CallManager Administration.
•Support for direct transfer and Join—Direct transfer merges two independent calls into one single call. Join merges a group of calls, including the attendant, into a conference call.
•A configuration tool that enables you to set the JTAPI user name and password, set directory values, enable call queuing for a pilot point, set the queue parameters (such as the queue size and hold time), and configure circular hunt groups and broadcast hunt groups.
Configuration Tips
•You enable queuing for a pilot point by using the Attendant Console Configuration Tool.
•You enable queuing for a pilot point by using the Attendant Console Configuration Tool.
•To configure the number of calls on a line, enter the appropriate value in the Maximum Number of Calls on the Directory Number Configuration window.
•This release reimplements Transfer to Voicemail with JTAPI support. Administrators no longer need to edit the VoiceMailProfiles.xml property file to enable users to access voice messaging system from the Cisco CallManager Attendant Console.
How this Feature Affects the User
•From the Broadcast Calls window in the Attendant Console application, users can view and answer calls.
Where to Find More Information
•"Cisco CallManager Attendant Console," Cisco CallManager System Guide
•"Cisco CallManager Attendant Console Configuration," Cisco CallManager Administration Guide
•"Configuring IP Phones," Cisco CallManager Administration Guide
