Table Of Contents
Release Notes for Cisco CallManager Release 4.1(2)
Contents
Introduction
System Requirements
Determining the Software Version
Compatibility Matrix and Supported Upgrades
Related Documentation
New and Changed Information
Cisco CallManager Installation, Upgrade, and Backup Enhancements
Installation and Upgrade
Backup
Operating System Installation Guidelines
Upgrading to Cisco CallManager Release 4.1(2)
Before Upgrading to Cisco CallManager 4.12
Requirement for Installation of Java Virtual Machine
JRE Installation
Cisco CallManager Administration Menu Changes
Call Coverage Enhancements
External Call Transfer Restrictions (Trunk-to-Trunk) Enhancements
Drop Ad Hoc Conference Enhancements
H.323 fastStart and T.38 Enhancements
MGCP BRI Endpoint Configuration
Time-of-Day Routing
Forced Authorization Codes/Client Matter Codes
Call Display Restrictions Enhancements
Multilevel Precedence and Preemption Enhancements
Cisco CallManager Attendant Console Enhancements
Cisco CallManager Extension Mobility Enhancements
Cisco IP Manager Assistant Enhancements
Directory Enhancements
Cisco Unity Voice-Mail Port Adjustments and Unity User Integration
Multilevel Administration Access Enhancements
QSIG Protocol Enhancements
Alerting Name
Annex M.1
Call Completion
Call Diversion
Compatibility with Older Versions of QSIG Protocol (ECMA)
Facility Selection and Reservation
Path Replacement
Video Calls Enhancements
Security Enhancements
CTI Super Provider
Bulk Administration Tool Enhancements
New BAT Features
External Call Transfer Restrictions (Trunk-to-Trunk Transfer)
Call Coverage
FAC/CMC
Call Display Restrictions
MLPP Enhancements
QSIG for Alerting Name
Video
Security
CTI Super Provider
CAPF Configuration
Tool for Autoregistered Phone Support Enhancements
Dialed Number Analyzer Enhancements
New and Updated Support for Cisco IP Phone Models 7940/7960
Support for Cisco IP Phone Model 7970
New and Changed Information for Cisco CallManager Serviceability
CDR Analysis and Reporting (CAR) Enhancements
Trace Collection Tool and RTMT Security Enhancements
Trace Configuration Tool
New and Changed Information for Third-Party and SDK Applications
JTAPI and TAPI Enhancements
Important Notes
CSCso79248 Do Not Run installxml.vbs in Unified CM Release 3.3 and Later
Adding Cisco CallManager Servers
Locale Installer for Cisco CallManager
Using the JTAPI Update Utility with CRS
Upgrade Requirements for CRS and Cisco CallManager 4.1
NetMeeting Calls Fail When T.38 is Advertised to NetMeeting
Cisco CallManager Installation Status Bar
CTI Route Point Considerations
Cisco CallManager Extension Mobility Scalability Update
Disabling IPSec for Cisco CallManager Upgrades
Disabling IPSec on the Cisco CallManager Server
Enabling IPSec on the Cisco CallManager Server
Resolved Caveats for Cisco CallManager - Release 4.1(2)
Bug Toolkit
Open Caveats for Cisco CallManager - Release 4.1(2)
Documentation Updates
Errors
Java Runtime Environment
Cisco CallManager Dialed Number Analyzer Service Startup Type
Barging into Encrypted Calls with the Cisco IP Phone Model 7970
Using Valid Characters in Cisco CallManager User IDs
Incorrect Reference in the Cisco CallManager Security Guide
Removing a Subscriber Server from Cisco CallManager
Using Script Files to Remove a Subscriber Server from Cisco CallManager
Changes
Associating H.323 Devices to Users
Omissions
? Icon Displays Incorrect Online Help for Region and Calling Search Space Pop p Windows
Name Change for the Cisco IAD 2400 Gateway Type in Cisco CallManager Administration
Route List Redundancy Configuration
Cisco IP Phone Models 7940/7960 Built-in Bridge and Device Security Considerations
CAPF Interaction When Cisco IP Phone Resets
Using Server Authentication, Third-Party CA Certificates
Using Shared Lines with Encrypted Devices
Reinstalling Dialed Number Analyzer after a Cisco CallManager Upgrade
Personal Directory
Support for the Cisco VG224 Gateway
Obtaining Documentation
Cisco.com
Ordering Documentation
Documentation Feedback
Obtaining Technical Assistance
Cisco Technical Support Website
Submitting a Service Request
Definitions of Service Request Severity
Obtaining Additional Publications and Information
Release Notes for Cisco CallManager Release 4.1(2)
Updated June 23, 2008
These release notes describe the new features and caveats for Cisco CallManager release 4.1(2).
Note 
To view the release notes for previous versions of Cisco CallManager, go to: http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/index.htm
Before you install Cisco CallManager, Cisco recommends that you review the "Important Notes" section for information about issues that may affect your system.
For a list of the open and resolved caveats for Cisco CallManager release 4.1(2), see the "Resolved Caveats for Cisco CallManager - Release 4.1(2)" section and the "Open Caveats for Cisco CallManager - Release 4.1(2)" section. Updates for these release notes occur with every maintenance release and major release.
To access the documentation suite for voice products, refer to the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/voice/
You can access the latest software upgrades and release notes for Cisco CallManager 4.0 on Cisco Connection Online (CCO) at the following URL:
http://www.cisco.com/public/sw-center/sw-voice.shtml
Contents
These release notes discuss the following topics:
•Introduction
•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.1(2)
•Open Caveats for Cisco CallManager - Release 4.1(2)
•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.1(2) 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.
Caution The installation does not complete if you do not have the exact configuration.
Access the correct Cisco-approved server configuration for an IBM server or an HP server at the following URL:
http://www.cisco.com/en/US/products/hw/voiceapp/ps378/prod_brochure_list.html
For system hardware component information and system requirements, refer to Installing Cisco CallManager Release 4.1(2).
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.1(2) and which previous release of Cisco CallManager has upgrade support by referring to the Cisco CallManager Compatibility Matrix at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/ccmcomp.htm
Note 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.1(2). 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.1 at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/4_1/doc_gd.
Along with the documents listed in the Cisco CallManager Document Guide, the following list specifies other related documents for Cisco CallManager release 4.1:
•Cisco CallManager Call Detail Record Definition
•Cisco IP Phone Services Application Development Notes
•Cisco JTAPI Installation Guide for Cisco CallManager 4.1(2)
•Cisco JTAPI Developer's Guide for Cisco CallManager 4.1(2)
•Cisco TAPI Installation Guide for Cisco CallManager 4.1(2)
•Cisco TAPI Developer's Guide for Cisco CallManager 4.1(2)
•Cisco CallManager Extension Mobility API Developer's Guide Release 4.1(2)
•Cisco CallManager 4.1(2) AXL Programming Guide
•Cisco CallManager 4.1(2) AXL Serviceability Programming Interface Guide
•Cisco CallManager Dialed Number Analyzer Guide
•Cisco WebDialer API Reference
•System Error Messages for Cisco CallManager 4.1
New and Changed Information
This following sections describe new features and changes that are pertinent to this release of Cisco CallManager. The sections include configuration tips for the administrator, information about users, and where to find more information.
•Cisco CallManager Installation, Upgrade, and Backup Enhancements
•Operating System Installation Guidelines
•Upgrading to Cisco CallManager Release 4.1(2)
•Requirement for Installation of Java Virtual Machine
•Cisco CallManager Administration Menu Changes
•Call Coverage Enhancements
•External Call Transfer Restrictions (Trunk-to-Trunk) Enhancements
•Drop Ad Hoc Conference Enhancements
•H.323 fastStart and T.38 Enhancements
•MGCP BRI Endpoint Configuration
•Time-of-Day Routing
•Forced Authorization Codes/Client Matter Codes
•Call Display Restrictions Enhancements
•Multilevel Precedence and Preemption Enhancements
•Cisco CallManager Attendant Console Enhancements
•Cisco CallManager Extension Mobility Enhancements
•Cisco IP Manager Assistant Enhancements
•Directory Enhancements
•Cisco Unity Voice-Mail Port Adjustments and Unity User Integration
•Multilevel Administration Access Enhancements
•QSIG Protocol Enhancements
•Video Calls Enhancements
•Security Enhancements
•CTI Super Provider
•Bulk Administration Tool Enhancements
•Tool for Autoregistered Phone Support Enhancements
•Dialed Number Analyzer Enhancements
•New and Updated Support for Cisco IP Phone Models 7940/7960
•Support for Cisco IP Phone Model 7970
•New and Changed Information for Cisco CallManager Serviceability
•New and Changed Information for Third-Party and SDK Applications
Cisco CallManager Installation, Upgrade, and Backup Enhancements
Cisco CallManager 4.1(2) implements the following changes for installation, upgrade, and backup procedures.
Installation and Upgrade
Installation and upgrade enhancements include the following:
•The enhanced Cisco CallManager upgrade process records the status of all running services and resets the services to an appropriate state for an upgrade to occur; the system automatically reboots and restarts the upgrade, as necessary.
•This enhancement applies to upgrades from Cisco CallManager release 3.3(x) and 4.0(x) to Cisco CallManager release 4.1(2).
•You must apply SQL 2000 SP3a before the upgrade from Cisco CallManager release 3.3(x).
•The upgrade process requires Cisco IP Telephony operating system (OS) version 2000.2.3 with OS upgrade 2000.2.6 or a fresh installation of OS version 2000.2.6 and the latest service release 2000.2-6-sr3 (or later).
Note This enhancement helps to ensure that the files the system needs are not in use and that the necessary services can be stopped, as required by the upgrade process.
Backup
Backup enhancements include the following:
•The Cisco IP Telephony Backup and Restore System (BARS) version 4.0(5) or later supports Cisco CallManager 4.1(2).
•Cisco CallManager release 3.3 and later no longer support Cisco IP Telephony Applications Backup Utility version 3.5.
Note Be sure to check the Cisco CallManager Compatibility Matrix for the latest information about supported compatibility combinations. See the "Compatibility Matrix and Supported Upgrades" section for more information.
Where to Find More Information
•Installing Cisco CallManager Release 4.1(2)
•Upgrading Cisco CallManager Release 4.1(2)
•Cisco IP Telephony Backup and Restore System (BARS)
Operating System Installation Guidelines
Cisco recommends that you install Cisco IP Telephony operating system version 2000.2.6 with the latest service release 2000.2-6-sr3 (or later) before you upgrade to Cisco CallManager release 4.1(2).
Where to Find More Information
•Installing the Operating System on the Cisco IP Telephony Applications Server, Version 2000.2.6
Upgrading to Cisco CallManager Release 4.1(2)
For detailed information about upgrading to Cisco CallManager 4.1(2), refer to Upgrading Cisco CallManager Release 4.1(2).
To verify which versions of Cisco CallManager are compatible for upgrade, refer to the Cisco CallManager Compatibility Matrix. To obtain the most recent version of this document, go to the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/ccmcomp.htm
•If your server runs Cisco CallManager release 4.0(2a), you can upgrade your server to release 4.1(2) by using the web download file that is available at http://www.cisco.com/public/sw-center/sw-voice.shtml.
•If your server runs a version of Cisco CallManager release 3.2 or earlier, you must use the Cisco CallManager software kit CD-ROM disks to first upgrade every server in the cluster to the latest version of Cisco CallManager release 3.3 or 4.0 before you can upgrade to a version of Cisco CallManager release 4.1.
Note For information about upgrading to Cisco CallManager release 3.3 or 4.0, refer to the appropriate version of the Upgrading Cisco CallManager document.
•You cannot upgrade directly from Cisco CallManager release 3.2 or earlier to Cisco CallManager release 4.1.
Tip Be sure to refer to the Cisco CallManager Compatibility Matrix for important information about the supported upgrade path for each Cisco CallManager release.
Before Upgrading to Cisco CallManager 4.12
Perform the following step on the voice-mail ports to ensure proper migration:
Important: Remove any call forwarding that is set on voice-mail ports that are used only for outbound calls and message waiting indication.
Requirement for Installation of Java Virtual Machine
The Microsoft Java Virtual Machine (MSJVM) technology allows Java applications to run on Microsoft Windows-based computers. Some versions of Microsoft Internet Explorer (a component of the Windows operating systems) included MSJVM, but Microsoft has since discontinued distribution of MSJVM in its software and announced end-of-life support for the product.
MSJVM was installed by default in all client workstation versions of the current Windows operating systems, except for the following versions:
•Windows XP Professional with SP1 slipstreamed into the installation
•Windows 2000 Server/Professional with SP4 slipstreamed into the installation
Note Because the Cisco CallManager Administration windows depend on remote scripts, which depend on the JVM for web interaction, Cisco CallManager requires the use of JVM on the client machine to ensure that the Cisco CallManager Administration windows display correctly.
•If your client machine runs MSJVM, you can continue to use the existing configuration to browse into the Cisco CallManager Administration windows and perform administration tasks.
•If you do not have MSJVM installed on your client machine (or if you receive an error message stating that Cisco CallManager cannot detect JVM on the client machine), and you need to perform Cisco CallManager Administration tasks, you must install and configure the Sun Microsystems Java Virtual Machine (JVM) on the client machine. (The Sun JVM comprises part of the Java 2 Runtime Environment—JRE.) In addition, you must configure the browser security to be Java-enabled. See the "JRE Installation" section for information about installing JRE on the client machine.
•If you are not sure whether MSJVM is installed on the client machine, you can install the Sun J2RE anyway. You would then have two Java Runtime Environments installed and running on your machine.
Tip If you run two separate JVM products (MSJVM and Sun J2RE) on your client machine, be sure to download and install patches and security updates for each JVM from the appropriate software vendor (Microsoft and Sun).
JRE Installation
As part of the Cisco CallManager installation, the system provides the Sun JRE client software in a zip file that is installed on the Cisco CallManager server.
Note Windows XP/XP Professional includes a built-in tool that handles zip files. If you use Windows 2000 as your operating system, you must obtain a separate compression utility (such as WinZip) to store and access zip files.
Tip Be sure you install Cisco IP Telephony operating system version 2000.2.6 with the latest service release 2000.2-6-sr3 (or later) before you upgrade to Cisco CallManager release 4.1(2).
To install the JRE software on the client PC, follow these steps:
Procedure
Step 1 From the Cisco CallManager server, navigate to the C:\utils\JRE directory and search for the J2RE_Client_<jre version>.zip file.
The following shows an example of the zip file name:
Note Only the Cisco CallManager Administrator can access the JRE software on the Cisco CallManager server; to enable access to other users, copy the J2RE_Client_<jre version>.zip file to a server that can be shared by all users.
Step 2 Right-click the J2RE_Client_<jre version>.zip file and click Copy to copy the file to your client PC.
Step 3 Double-click the J2RE_Client_<jre version>.zip file to unzip the Sun J2RE installation executable.
Step 4 Double-click the installation executable file on the client PC.
The following shows an example of the installation executable file name:
j2re-1_4_2_04-windows-i586-p.exe
Note The exact name of the installation executable file changes with each version as the new version number is incorporated into the name.
The JRE software installs in the C:\Program Files\Cisco\Java\JRE directory.
Cisco CallManager Administration Menu Changes
Cisco CallManager 4.1(2) contains the following Cisco CallManager Administration menu changes:
•The Route Plan menu contains a new submenu item, Class of Control. From the Cisco CallManager Administration window, navigate to Route Plan > Class of Control. Class of Control contains the following submenu items:
•Two new submenu items: Time Period and Time Schedule. (See the "Time-of-Day Routing" section for additional information about these submenus.)
•Two existing submenu items: Partition and Calling Search Space. (These submenu items moved from the Route Plan menu to the Class of Control submenu in this release.)
•This release separates and reorganizes Route and Hunt submenus under Route Plan (Route Plan > Route/Hunt).
•Two groups of three submenus—the routing submenus (Route Group, Route List, and Route Pattern) and the hunting submenus (Line Group, Hunt List, and Hunt Pilot)—replace the previous Route Plan > Route Pattern/Hunt Pilot submenu.
Note In Cisco CallManager release 4.0, route/hunt lists comprised line groups followed by route groups. In release 4.1, route lists comprise only route groups and hunts lists comprise only line groups. An existing route/hunt list that contains both line groups and route groups migrates to a hunt list that contains only line groups and a route list that contains only route groups.
•The Feature menu includes two new submenu items: Client Matter Code (Feature > Client Matter Code) and Forced Authorization Code (Feature > Forced Authorization Code).
•CAPF Report, a new Certificate Authority Proxy Function (CAPF) application submenu item, appears under Device.
•By navigating to Device >Device Settings >CAPF Report from the Cisco CallManager Administration window, you can generate a CAPF report to view the certificate operation status, the authentication strings, or the authentication mode for listed devices.
Note Refer to the Cisco CallManager Administration Guide for detailed information about the updated administration configuration windows.
Where to Find More Information
•Cisco CallManager Administration Guide
Call Coverage Enhancements
Cisco CallManager 4.1(2) now allows call forwarding on line directory numbers (DNs) to be configured (on Busy/No-answer) based on whether the caller DN is Internal (OnNet) or External (OffNet).
With this release, the system administrator can configure a forwarding point that acts as a personal forwarding point. A call that is placed to a phone can be set up for CFNA or CFB to a hunt group. If the call goes unanswered, it can be forwarded to the Call Forward no-coverage destination (for example, a voice-messaging system or another DN).
Cisco CallManager 4.1(2) allows Hunt Pilot DNs to be configured with forwarding capabilities on "Forward Hunt No Answer" or "Forward Hunt Busy." This change allows greater flexibility for inbound/outbound call hunting.
Note The Hunt Pilot and the Hunt List configuration is now separate from the Route Pattern and the Route List configuration, as described in the "Cisco CallManager Administration Menu Changes" section.
Configuration Tips (for Administrators)
•On call forward settings for line DNs, Gateway, Trunk, and Route Pattern settings of OnNet (internal) or OffNet (external), as defined in the "External Call Transfer Restrictions (Trunk-to-Trunk) Enhancements" section, determine the internal/external configuration.
•When configuring "Call forward no coverage" on a line DN, ensure that the Busy or No-answer settings for that line DN are configured to forward to a Hunt Pilot DN. Also, ensure that the Hunt Pilot DN is configured with the "Use Personal Preferences" check box enabled in the Forward Hunt Busy/No-answer settings.
•To configure a hunt list in Cisco CallManager release 4.1 so that the last resort of a hunt list specifies an external directory number, configure a hunt pilot that specifies the hunt list, and configure the hunt list so that the Forward Hunt No Answer and Forward Hunt Busy fields specify the external directory number.
How This Feature Affects the End User
•End users gain additional flexibility in handling call forwarding on internal or external calls.
•End users have more options for handling coverage to hunt groups by having calls that are not answered by the hunt group forward to a voice-messaging system or to another DN (such as a cell phone or another hunt group).
Where to Find More Information
•Route Group Configuration, Cisco CallManager Administration Guide
•Route List Configuration, Cisco CallManager Administration Guide
•Route Pattern Configuration, Cisco CallManager Administration Guide
•Line Group Configuration, Cisco CallManager Administration Guide
•Hunt List Configuration, Cisco CallManager Administration Guide
•Hunt Pilot Configuration, Cisco CallManager Administration Guide
•Cisco IP Phone Configuration, Cisco CallManager Administration Guide
•Understanding Route Plans, Cisco CallManager System Guide
External Call Transfer Restrictions (Trunk-to-Trunk) Enhancements
In previous releases, no configurable option existed to define a call as OnNet (internal) or OffNet (external). Cisco CallManager release 4.1(2) now provides that flexibility at the individual gateway, trunk, and route pattern levels. It also provides a global setting for gateways and trunks.
Cisco CallManager classifies incoming and outgoing calls on the basis of the following settings:
•An incoming call gets classified as OnNet or OffNet based on the setting that is configured on the gateway through which the call came into the network.
•An outgoing call gets classified as OnNet or OffNet based on the route pattern setting that is used to route the call out of the network.
Cisco CallManager 4.1(2) provides the ability to block OffNet to OffNet transfer that can be enabled by using a clusterwide service parameter, Block OffNet to OffNet Transfer; this field appears under the clusterwide service parameter (Feature - General) in the Service Parameters Configuration window. This new service parameter replaces the Block External to External Transfer service parameter. During upgrade to Cisco CallManager 4.1(2), the new parameter replaces the old service parameter, and the old value (true or false) gets set to the new parameter value.
Ad Hoc Conference Enhancements
Related to the concept of OnNet/OffNet, a new conference feature in this release includes the option to drop an active ad hoc conference when the conference controller drops out. An additional alternative allows you to drop an ad hoc conference when no OnNet parties remain in the conference. Choose the desired option by using the clusterwide service parameter, Drop Ad Hoc Conference. See the "Drop Ad Hoc Conference Enhancements" section and the Cisco CallManager System Guide for additional details.
Configuration Tips (for Administrators)
•Use the Call Classification field in the Cisco CallManager Administration Gateway Configuration window to configure H.323 and MGCP gateways with the option for OffNet, OnNet, or Use System Default.
•The default value for H.323 and MCGP gateways specifies OffNet.
•The default value for intercluster trunks (ICT), or trunks other than SIP trunks, specifies OnNet.
•In Cisco CallManager release 4.1, Call Classification replaces the H323 Network Location, MGCP Network Location, and MGCP Network Location OffNet for E1 and T1 service parameters.
•To configure trunks and gateways, the administrator can use the Call Classification clusterwide service parameter and choose the Use System Default option for the individual trunks and gateways.
•By default, the service parameter specifies OffNet.
•You can also configure trunks and gateways individually.
•The system considers FXS and phones to be OnNet; you cannot configure them.
•Use the setting on the Cisco CallManager Administration Gateway and Trunk Configuration windows to mark an incoming call as OnNet or OffNet.
•Use the Cisco CallManager Administration Route Pattern Configuration window to mark an outgoing call as OnNet or OffNet by configuring the following fields:
•Call Classification—Use this drop-down list box to classify the call that uses this route pattern as OffNet or OnNet.
•Allow Device Override—When you check this check box, the system uses the Call Classification setting of the trunk or gateway that is associated with the route pattern instead of the Call Classification setting on the Route Pattern Configuration window.
How This Feature Affects the End User
•If you enable this feature by using the service parameter, the end user cannot transfer an OffNet call to another OffNet call.
•The system allows transfer of an OnNet call to another OnNet/OffNet call, and an OffNet call may transfer to an OnNet destination.
•The "Cannot Complete Transfer" message displays on the phone when transfer is blocked.
Where to Find More Information
•External Call Transfer Restrictions, Cisco CallManager Features and Services Guide
Drop Ad Hoc Conference Enhancements
Cisco CallManager 4.1(2) makes available the option to drop an active ad hoc conference when the conference controller drops out. As an alternative, you can choose to drop an ad hoc conference when no OnNet parties remain in the conference. Choose the desired option by using the clusterwide service parameter, Drop Ad Hoc Conference. The Cisco CallManager System Guide documents this feature, which has been modified from Cisco CallManager release 3.3(x).
Configuration Tips (for Administrators)
•Use the setting on the Cisco CallManager Administration Route Pattern Configuration window to mark any call going through it as OnNet or OffNet.
•See the "External Call Transfer Restrictions (Trunk-to-Trunk) Enhancements" section for additional configuration tips.
How This Feature Affects the End User
•When you choose the option to drop an ad hoc conference when the conference creator leaves and the conference originator hangs up the call, the entire conference terminates.
•When the conference originator transfers/redirects or parks the call and another party retrieves the call, the party becomes a virtual controller. When this virtual controller hangs up, the entire conference terminates.
•When the option to drop an ad hoc conference when "No OnNet Parties Remain in the Conference" is selected and the last OnNet party moves out of the conference, the entire ad hoc conference terminates.
Where to Find More Information
•Conference Bridges, Cisco CallManager System Guide
H.323 fastStart and T.38 Enhancements
Cisco CallManager 4.1(2) provides support for the following enhancements to H.323 fastStart and T.38:
•H.323 outbound fastStart, including the following new parameters in the H.225 Trunk and H.323 Gateway Configuration windows:
•Enable Outbound fastStart
•Codec for Outbound fastStart
•Replacement of the H.323 fastStart Inbound service parameter with the Enable Inbound fastStart configuration field in the H.225 Trunk and H.323 Gateway Configuration windows.
•T.38 to allow switching from a voice call to a T.38 fax data call.
Where to Find More Information
•Understanding Cisco CallManager Voice Gateways, Cisco CallManager System Guide
•Gateway Configuration, Cisco CallManager Administration Guide
MGCP BRI Endpoint Configuration
Cisco CallManager 4.1(2) adds a basic rate interface (BRI) endpoint configuration window on the MGCP Gateway Configuration window. The new configuration window contains configurable BRI MGCP backhaul parameters and hardware-specific parameters that you may use to configure a BRI endpoint on the IOS gateway.
Configuration Tips (for Administrators)
•Cisco CallManager 4.1(2) includes support for new network modules. (Refer to the following documentation for additional information.)
•This release provides support only for ETSI BRI basic-net3 (user side only).
Where to Find More Information
•Understanding Cisco CallManager Voice Gateways, Cisco CallManager System Guide
•Gateway Configuration, Cisco CallManager Administration Guide
Time-of-Day Routing
The Time-of-Day feature routes calls to different locations based on the time of day when the call is made. For example, during business hours, calls could route to your office(s), and after hours, they could go directly to a voice-messaging system or to your home number.
Configuration Tips (for Administrators)
•The time-of-day feature comprises individual Time Periods that are grouped into Time Schedules. You can access these menus from Cisco CallManager Administration by navigating to Route Plan > Class of Control > Time Period (and Time Schedule).
•You can associate the Time Schedules with a Partition. (You can access the Partition Configuration window by navigating to Route Plan > Class of Control > Partition from Cisco CallManager Administration.) In the Partition Configuration window, you can choose either the originating device time zone or any specific time zone for the Time Schedule. The system checks the chosen time zone against the Time Schedule when a call is placed to directory numbers in this partition.
Tip Three new configuration windows support the time-of-day feature. These windows appear under the Route Plan > Class of Control submenu option. (The Calling Search Space and Partition Configuration windows also exist as part of this new submenu.)
How This Feature Affects the End User
•If the time-of-day feature is enforced, users cannot set certain CFwdAll numbers at certain times. For example, User A Calling Search Space for forwarding has a Time-of-Day configured partition that allows international calls from 8:00 am to 5:00 pm. User A wants to configure a CFwdAll number to an international number. User A can only set this number between the hours of 8:00 am to 5:00 pm because, outside of these hours, the international number will not be in the partitionSearchString that is used to validate the CFwdAll number.
•Users cannot reach directory numbers in some partitions that are configured with the time-of-day feature and are not active during the time of call depending upon the configuration of the partitions.
Where to Find More Information
•Route Plan Configuration, Cisco CallManager Administration Guide
•Time Period Configuration, Cisco CallManager Administration Guide
•Time Schedule Configuration, Cisco CallManager Administration Guide
•Partition Configuration, Cisco CallManager Administration Guide
•Calling Search Space Configuration, Cisco CallManager Administration Guide
•Partitions and Calling Search Spaces, Cisco CallManager System Guide
•Time of Day Routing, Cisco CallManager System Guide
Forced Authorization Codes/Client Matter Codes
Introduced in Cisco CallManager 3.3(4), Client Matter Codes (CMC) 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 (FAC) feature mandates that the user enter a valid authorization code before the call completes.
Tip In most cases, Cisco CallManager can alert a CTI, JTAPI, or TAPI application that the user must enter a code during a call. When a user places a call, creates an ad hoc conference, or performs a consult transfer through an FAC- or CMC-enabled route pattern, the user must enter a code after receiving the tone. When a user redirects or blind transfers a call through an FAC- or CMC-enabled route pattern, the user receives no tone, so the application must send the codes to Cisco CallManager. If Cisco CallManager receives the appropriate codes, the call connects to the intended party. If Cisco CallManager does not receive the appropriate codes, the system sends an error to the application that indicates which code is missing.
The system writes both the authorization information and the Client Matter Codes information to the Cisco CallManager Call Detail Record (CDR) database.
Configuration Tips (for Administrators)
•The Feature menu includes the Forced Authorization Code and the Client Matter Code submenus (Feature > Forced Authorization Code and Feature > Client Matter Code).
•The FAC feature requires that users enter an authorization code to reach certain dialed numbers; the CMC feature requires that users enter a client matter code to reach certain dialed numbers. As administrator, you can enable or disable the FAC/CMC feature by configuring the following attributes in the Route Pattern Configuration window:
•FAC—Require Forced Authorization Code check box and Authorization Level field—Check the check box to enable the FAC feature and enter a value in the authorization level field.
Authorization Level limits the range to 0-255 inclusive; the administrator defines the number of configured authorization levels.
•CMC—Require Client Matter Code check box—Check this box to enable the CMC feature.
When you enable these features, the user receives a prompting tone to enter an authorization code and/or a client matter code. Call processing collects digits until a number is entered or until the interdigit timeout expires. If the authorization level of the user authorization code is greater than or equal to the authorization level of the route pattern, the system processes the call; otherwise, the reorder tone plays. If the client matter code is valid, the system processes the call; otherwise, the reorder tone plays.
•In addition to CMC and FAC configuration in Cisco CallManager Administration, you must update route patterns and dial plan documents to reflect that you have enabled or disabled FAC and/or CMC for each route pattern.
•A route pattern can have both FAC and CMC enabled. In this case, the system collects the Authorization Code first and then collects the Client Matter Code.
•The system does not support FAC/CMC with overlap sending. When you check the Allow Overlap Sending check box, the FAC and CMC check boxes are disabled.
•The system writes the authorization description, authorization level, and the client matter code to the CDR to allow the CDR Analysis and Reporting Tool (CAR) to create reports for FAC/CMC calls. (For security purposes, the authorization code does not get written to the CDR.)
How These Features Affect the End User
•If the administrator enables and defines FAC/CMC codes and configures route patterns to use them, the user receives a prompt to enter a code when making a call.
•Users can press # on the phone to immediately route a call after entering the code.
•Users can start entering the code before the tone completes.
•The phone plays a reorder tone when the user enters an invalid code.
•After dialing the phone number, hearing-impaired users should wait 1 or 2 seconds before entering the authorization or client matter code.
•Cisco IP SoftPhone cannot play tones; however, after a Cisco SoftPhone user dials a directory number, the user can use CMC and FAC by waiting 1 or 2 seconds before entering the code.
•When a user presses the Redial softkey on the phone, the user must enter the authorization code or CMC when the dialed number is routed through an FAC- or CMC-enabled route pattern.
•The user cannot configure FAC or CMC for speed-dial buttons.
•Cisco WebDialer does not support FAC or CMC.
Note See the "CDR Analysis and Reporting (CAR) Enhancements" section for more information about the FAC/CMC reports that are available under the CAR Configuration window.
Where to Find More Information
•Understanding Route Plans, Cisco CallManager System Guide
•FAC/CMC, Cisco CallManager Features and Services Guide
Call Display Restrictions Enhancements
The Call Display Restrictions feature allows administrators to choose the information that displays for calling and/or connected lines, depending on the parties involved in the call. By using specific configurable Calling and Connected party restrictions on the Cisco CallManager Administration Translation Pattern Configuration window, call display information may be presented or restricted for each call.
Cisco CallManager 4.1(2) provides enhancements to this feature over Cisco CallManager 4.0. Specifically, the Phone Configuration window provides a new Ignore Presentation Indicators (internal calls only) check box that, when set, ignores presentation settings of the remote party for internal calls. For incoming external calls, the system respects the received presentation indicators even if the flag is set. The User Device Profile and Device Profile Default Configuration windows also provide this check box.
Configuration Tips (for Administrators)
•The basis for the functionality of the Call Display Restrictions feature relies on calls always being routed through different translation patterns before the calls are extended to the actual device. Configuring partitions and calling search spaces, along with translation patterns, make this possible. (In a hotel environment, this will ensure that, when two rooms are in a call, display information does not become visible across parties.)
•Configure partitions and calling search spaces before you add a translation pattern.
•Configure translation patterns with different levels of display restrictions.
•Check the Ignore Presentation Restriction (internal calls only) check box to ensure that the call information display for internal calls is always visible. (Phones that are used at hotel front desks usually require this characteristic.)
•Be aware that the translation pattern configuration at the terminating end can override the originating cluster settings for outgoing calls.
•Configure individual, associated translation patterns for each individual Call Park directory number to preserve the Call Display Restrictions feature; configuring a single translation pattern to cover a range of call park numbers does not work with Call Display Restrictions.
•For users who log in to phones that are enabled for Extension Mobility, configure the Ignore Presentation Indicators (internal calls only) setting from the Cisco CallManager Administration User Device Profile window as well as from the Phone Configuration window.
How This Feature Affects the End User
•This feature, which is well-suited to the hospitality industry, ensures that the display information is secured from public viewing (by the usage of translation patterns along with partitions and calling search spaces).
•The phones that have the Ignore Presentation Indicators (internal calls only) check box checked, however, always display the call information of the remote, internal party. Even when this flag is set, phones honor the call restrictions on external calls.
Where to Find More Information
•Call Display Restrictions, Cisco CallManager Features and Services Guide
•Phone Configuration, Cisco CallManager Administration Guide
•Device Profile Configuration, Cisco CallManager Administration Guide
•Translation Pattern Configuration, Cisco CallManager Administration Guide
Multilevel Precedence and Preemption Enhancements
Cisco CallManager 4.1(2) provides the following Multilevel Precedence and Preemption (MLPP) enhancements.
Defense Switched Network (DSN) Features
MLPP includes the following features for the DSN:
•Support for secure communication by using legacy BRI and analog secure endpoints (STE/STU) and support for IP-STE, including A, B, C, D digit dialing and V150 subset support.
•Support for missing certification requirements (Signal IE).
Defense Red Switched Network (DRSN) Features
MLPP includes the following features for the DRSN:
•Support for MLPP-enabled, UUIE-based PRI-4ESS interface.
•Support for Executive Override precedence level.
•Location-based MLPP through locations over intracluster and intercluster limited bandwidth WAN links for DRSN.
•Support for intercluster MLPP announcements.
Configuration Tips (for Administrators)
Cisco CallManager 4.1(2) includes the following configuration enhancements:
•Four new Cisco CallManager Service Parameters:
•Enable Location-based MLPP Feature
•Executive Override Call Preemptable
•H225 T305 Timer
•PRI 4ESS UUIE Device Type
•UUIE Configuration on MGCP PRI Gateway Configuration window for 4ESS protocol:
•Passing Precedence Level Through UUIE
•Security Access Level
•V150 (subset): Configuration on MGCP PRI/CAS Gateway Configuration window.
•MLPP Indication: Configuration on Intercluster and Gatekeeper controlled trunks on the Trunk Configuration window.
•IP-STE: New Skinny phone available.
•SCCP IOS GW Available: Configuration similar to MGCP Gateway configuration except endpoints are Skinny Analog and BRI phones:
•Five GW types, 269X, 26XX, 3725, 3745, and VG224, support the new SCCP protocol.
•In Add a New Gateway window, the system makes available both MGCP and SCCP protocols for five gateway types, 269X, 26XX, 3725, 3745, and VG224. (Choose gateway type and either MGCP or SCCP protocol type.)
•On the Translation Pattern and Route Pattern Configuration windows, the system makes highest precedence level Executive Override available.
•You can configure A, B, C, D digits and Transformation Masks on Route Pattern and Translation Pattern Configuration windows.
•CDR changes for Executive Override calls.
•Changes to the precedence level, as shown by the previously displayed/CDR display for precedence level:
(0) Flash Override/Executive Override
(1) Flash/Flash Override
(2) Immediate/Immediate
(3) Priority/Priority
(4) Routine/Routine
How This Feature Affects the End User
•Additional Executive Override precedence enables higher precedence than the existing Flash Override precedence.
•IP-STE may have limited features (especially in secure mode).
•IOS Skinny endpoints (BRI and analog) include very limited features, one call, one-line phones.
Where to Find More Information
•Multilevel Administration Access, Cisco CallManager Feature and Services Guide
•Route Pattern Configuration, Cisco CallManager Administration Guide
•Translation Pattern Configuration, Cisco CallManager Administration Guide
•Gateway Configuration, Cisco CallManager Administration Guide
•Trunk Configuration, Cisco CallManager Administration Guide
•Call Admission Control, Cisco CallManager System Guide
•Understanding Cisco CallManager Trunk Types, Cisco CallManager System Guide
•Understanding Cisco CallManager Voice Gateways, Cisco CallManager System Guide
•Cisco IP Phone Administration Guide for Appropriate phone model
Cisco CallManager Attendant Console Enhancements
Cisco CallManager 4.1(2) contains the following Attendant Console enhancements:
•Cisco CallManager Attendant Console 1.4(1) contains accessibility features, such as mouse-less operation (using only keyboard shortcuts), to assist visually impaired or blind attendants with using the attendant console.
•Cisco CallManager Attendant Console supports screen readers such as JAWS. The screen reader provides information about the status of the attendant console and about the text in various windows.
•Attendants can enable audible alerts to indicate various call events.
•Attendants can enable accessibility messages, so dialog boxes display information about the status of the attendant console, such as when call control goes up or down.
How This Feature Affects the User
•The default values for the keyboard shortcuts of some actions changed to avoid conflicts with JAWS shortcuts.
•The attendant can choose whether to enable audible alerts.
•The attendant can choose whether to enable accessibility messages.
•The attendant can choose whether to put calls on hold during a transfer, consult transfer, or conference.
Where to Find More Information
•Cisco CallManager Attendant Console User Guide
Cisco CallManager Extension Mobility Enhancements
Cisco CallManager 4.1(2) contains the following changes for Extension Mobility:
•Changes to comply with JTAPI.
•Changes for MSJVM removal.
•Support for the Call Display Restrictions feature.
Configuration Tips (for Administrators)
•To set up Call Display Restrictions, check the Ignore Presentation Indicators (internal calls only) check box on the User Device Profile Configuration window. For additional information, see the "Call Display Restrictions Enhancements" section.
Where to Find More Information
•Cisco CallManager Extension Mobility, Cisco CallManager Features and Services Guide
•Call Display Restrictions, Cisco CallManager Features and Services Guide
Cisco IP Manager Assistant Enhancements
Cisco CallManager 4.1(2) contains the following changes for Cisco IP Manager Assistant:
•Changes to comply with JTAPI.
•Changes for MSJVM removal.
•Support for the Time-of-Day routing feature.
Where to Find More Information
•Cisco CallManager Features and Services Guide
Directory Enhancements
Cisco CallManager 4.1(2) provides security automatically for the DC Directory. Microsoft Active Directory (AD) and the Netscape Directory require manual configuration for security. Providing LDAP at SSL (LDAPS) enables security. When security is set, the system "encrypts" certain data (such as user passwords and user IDs) when it passes through the network.
Configuration Tips (for Administrators)
•The administrator must run the Customer Directory Plugin if security is needed for Microsoft AD or for the Netscape Directory.
Where to Find More Information
•Directory, Cisco CallManager System Guide
•Installing the Cisco Customer Directory Configuration Plugin for Cisco CallManager
Cisco Unity Voice-Mail Port Adjustments and Unity User Integration
Cisco CallManager 4.1(2) includes a link to configure a Cisco Unity voice messaging subscriber number from the Directory Number Configuration window and from the User Configuration window (under "Add a New User"). Phones must associate with users for the link to appear on the User Configuration window.
Configuration Tips (for Administrators)
•The Unity administrator must perform certain configurations to make the link accessible, including copying an asp page to the Cisco CallManager server. This feature requires Unity 4.04 and additional configuration, as described in the Unity documentation.
Where to Find More Information
•Phone Configuration, Cisco CallManager Administration Guide
•Add a New User Configuration, Cisco CallManager Administration Guide
•Cisco Unity, Cisco CallManager System Guide
•Cisco CallManager 4.1 Integration Guide for Cisco Unity 4.0
Multilevel Administration Access Enhancements
Multilevel Administration Access (MLA) now supports UMX APIs for LDAP Directory access as a transparent change to the administrator. Previously, a custom Java code (MultilevelAdmin.dll) implemented the LDAP Directory access for Users and User Group. With this conversion, no dependency on the Microsoft JVM exists in future releases.
The Cisco CallManager Administration menu changes include MLA support for assigning access rights.
Where to Find More Information
•MLA, Cisco CallManager System Guide
•MLA Configuration, Cisco CallManager Administration Guide
QSIG Protocol Enhancements
Cisco CallManager release 4.1(2) includes the following QSIG enhancements:
•Alerting Name
•Annex M.1
•Call Completion
•Call Diversion
•Compatibility with Older Versions of QSIG Protocol (ECMA)
•Facility Selection and Reservation
•Path Replacement
Alerting Name
Cisco CallManager 4.1(2) supports "Alerting on ring" only to allow the QSIG Alerting Name that you configure to send and receive call name information while the phone rings. When two phones ring for the shared directory number, the name that you entered in the Alerting Name field displays on the phone of the called party at the terminating Private Integrated Services Network Exchange (PINX), unless translation pattern restrictions affect the information that displays. Route pattern restrictions may affect the information that displays on caller phone at the originating PINX. (In a QSIG network, a switch such as Cisco CallManager or other PBX represents a PINX.)
Configuration Tips (for Administrators)
•Configure the Alerting Name field for shared and nonshared directory numbers from the Cisco CallManager Administration Directory Number Configuration window.
•If you do not configure an Alerting Name, only the directory number displays on the calling party phone when alerting occurs.
•If you configure a Display Name for the called party, the Display Name displays on the calling party phone when the call connects.
•If you do not enter a Display Name or an Alerting Name, no name displays on the calling party phone during the call.
•Cisco CallManager does not provide support for Alerting Name with the following device types:
•PRI trunks
•FXS/FXO ports for MGCP gateways
•MGCP T1-CAS gateways
Annex M.1
The Annex M.1 feature uses intercluster trunks to transport (tunnel) non-H.323 protocol information in H.323 signaling messages between Cisco CallManagers. Annex M.1 supports QSIG calls and QSIG call independent signaling connections.
QSIG tunneling supports the Call Completion, Call Diversion, Call Transfer, Identification Services, Message Waiting Indication, and Path Replacement features.
Configuration Tips (for Administrators)
•In the Cisco CallManager Administration Trunk Configuration window, choose the QSIG option in the Tunneled Protocol drop-down list box and check the Path Replacement Support check box.
•After you configure the QSIG Tunneled Protocol option, the Path Replacement Support check box automatically becomes checked. If you do not require path replacement over Annex M.1 or QSIG-tunneled trunks, you can uncheck the Path Replacement Support check box.
•When you set the Tunneled Protocol field to None, Cisco CallManager automatically grays out the Path Replacement Support check box.
•When you set the Tunneled Protocol field to QSIG, the system does not allow configuration of the Redirecting Number IE Delivery (Inbound), Redirecting Number IE Delivery (Outbound), or Display IE Delivery options.
Tip If you use a gatekeeper, you must configure every gateway in the network for QSIG tunneling. If any gateway in the network does not support QSIG tunneling, calls drop at the intercluster trunk that is configured for QSIG tunneling.
Note Cisco CallManager does not support protocol profile 0x91 ROSE encoding with Annex M.1.
Call Completion
The Cisco Call Back feature allows you to receive call back notification on your Cisco IP Phone when a called party line becomes available. You can activate call back for a destination phone that is within the same Cisco CallManager cluster as your phone or
