Table Of Contents
Release Notes for Cisco Unified Communications Manager Release 6.0(1b)
Contents
Introduction
System Requirements
Upgrading System Software
Upgrading to Cisco Unified Communications Manager 6.0(1x)
Cisco Upgrade Recommendations
Upgrade Paths To Cisco Unified Communications Manager 6.0(1x)
Upgrading from Unified CM 4.x and 5.x
Upgrading from Cisco Unified Communications Manager Release 6.0(1a) to Release 6.0(1x) Using the UCSInstall File
Related Documentation
Limitations and Restrictions
Important Notes
Unanswered Conference Call
Considerations for LDAP Port Configuration
CSCso96280 Unified CM and CTI May Terminate Unexpectedly
Cisco CallManager Service Stops After Upgrade to Cisco Unified Communications Manager 6.X
Important Information about Delete Transaction Using Custom File in BAT
Cisco Unified Communications Manager Does Not Support Recovery of Administration or Security Passwords
Deleting a Server and Adding a Deleted Server to a Cluster
Clarification for Call Park Configuration
Viewing Privileges for Roles in Cisco Unified Communications Manager Administration
TAPS Name Change in Bulk Administration Tool
CSCso94813: Subscriber Server Install Fails Due to 'hostname -i" Failing
Cisco Unified Communications Disaster Recovery Framework Command Execution
Voice Mailbox Mask Interacts with Diversion Header
Cisco Advisory for Cisco Unified Communications Manager Release 6.0(1a)
Cisco Security Agent (CSA) Drops Incoming TCP SYN Connection Attempts with No Logs
Do Not Upgrade from Cisco Unified CallManager 5.1(3) to Cisco Unified Communications Manager 6.x
CSCsi75567 MCS-7825H2-IPC1 Reboots Randomly
New Clustering Over WAN Requirements
Voice, Cisco Fax Relay and Fax Passthrough Calls Fail
Device Reset Speed
No Such Name Error Returned in the SNMP Response
Value of the Maximum Current Requests Service Parameter After Upgrade to Release 6.0
IP Phone Messenger (IPPM) User Does Not Have Callback Capability
Monitoring Call Gets Dropped When Agent Call Is Put on Hold
DVDROM Not Accessible After Upgrade
Deleting Then Adding Back a Server in Cisco Unified Communications Manager Administration
Call History Might Get Lost When AAR Routes Over QSIG Trunk
Extension Mobility Maximum Concurrent Requests Number Does Not Change After Upgrade
Cisco Unified Communications Manager Assistant Limitations with Cisco IP Communicator
Translation Pattern Support
Subscribe Calendar 500 Internal Error
Maximum Trace Settings
Disabling the Advertise G.722 Codec Enterprise Parameter When You Are Using System Features
Using FTP to Upgrade to Cisco Unified Communications Manager Release 6.0(1b)
Cisco Unified Personal Communicator LDAP Attribute Mappings
Terminal Server Causes RTMT to Display Repeating Syslog and Alert Messages
New and Changed Information in Cisco Unified Communications Manager Releases 6.0(1x)
Trace Compression Support
Basic Uninterruptible Power Supply (UPS) Integration
HP NC-Series Broadcom Firmware Updates Available for Supported NICs.
Smart Array 6i Requires HD Firmware Update to Avoid POST Notification
CSCsj72914 Conference Calls Experience Poor Audio Quality
CSCsj61395 Spurious Error Message Displays During Installation of Locale COP Files on a Subscriber Server
CSCsj55359 Installation Media Cannot Locate Available Patches
CSCsj42131 User with Incorrect Primary Extension in Directory Export
CSCsj22669 User and User Profile Association Issue in Directory Export
CSCsi71128 DMA Requires a Long Time to Run
CSCsi20684 CSS Call Forward All
Installation, Upgrade, Migration, and Disaster Recovery
Installation Overview
Software Upgrades
Disaster Recovery System
Where to Find More Information
Cisco Unified Communications Operating System Administration
Overview
Browser Requirements
Platform Status and Configuration Enhancements
Settings Enhancements
Restart Options Enhancements
Security Configuration Enhancements
Software Upgrades Enhancements
Command Line Interface Enhancements
Where to Find More Information
Cisco Unified Communications Manager Administration
System Architecture Changes
General Administration Enhancements
Navigating to IP Telephony Applications Within Cisco Unified Communications Manager Enhancements
Localizing Cisco Unified Communications Manager Administration
Migration Tips
General Changes That Were Made to Multiple Windows
Service Parameter Changes
Locations and Region Enhancements
System Menu Changes
Call Routing Menu Changes
Media Resources Menu
Voice Mail Menu
Device Menu Changes
Application Menu Changes
User Management Menu
Bulk Administration Menu
Where to Find More Information
Cisco Unified Communications Manager Features
AAC/iLBC Voice Codec Support
Advanced Ad Hoc Conference
Audible Message Waiting Indicator
Barge Enhancements
Call Diagnostics and Voice Quality Metrics
Call Forward Enhancements
Call Forward All Calling Search Space Backward Compatibility
Call Forward Overriding
Call Pickup Notification
Cisco Messaging Interface Enhancements
Cisco Unified Communications Manager T1 CAS Hookflash Transfer Support
Connected Number Display
Credential Policy and User Authentication
CTI Enhancements
Device Mobility
Directed Call Park
Do Not Disturb
Hold Reversion
Intercom
Licensing Enhancements
Log Out of Hunt Groups
MGCP T.38 Enhancements
Overlap Sending and Receiving for H.323 Gateways
Privacy on Hold
Programmable Line Keys
SCCP Optimization
SDL Traces
SIP Endpoints Support
Third-Party Phones Enhancements for Phones That Are Using SIP
SIP Trunk Enhancements
Cisco Unified Communications Manager Applications
Cisco Unified Communications Manager Extension Mobility
Cisco Unified Communications Manager Assistant
Cisco Unified Mobility
Migrating from Cisco Unified Mobility to Cisco Unified Communications Manager
Multilevel Precedence and Preemption (MLPP) Supplementary Services
Multilevel Precedence and Preemption Enhancements
Recording and Monitoring
Cisco Unified Communications Manager Bulk Administration Features
New and Changed Information for BAT
BAT Configuration Tips
GUI Changes
Cisco Unified Communications Manager Security Features
Secure Conferencing
Secure Conference Icon
Cisco Unified Serviceability
Serviceability Administration
Cisco Unified Real-Time Monitoring Tool
Cisco Unified Communications Manager CDR Analysis and Reporting
Call Detail Record Definitions
Cisco Dialed Number Analyzer
Cisco Unified Communications Manager User Options Menu
Cisco Unified IP Phones
Cisco Unified IP Phone 7975G
Cisco Unified IP Phone 7965G and 7945G
Cisco Unified IP Phone 7962G and 7942G
Cisco Unified IP Phone 7931G (SCCP Only)
Wideband Settings
Peer Firmware Sharing
Cisco Unified IP Phone Support for Cisco Unified Communications Manager 6.0 Features
Feature Support by Cisco Unified IP Phone and Protocol
Call Forward All Loop Prevention Message Changes
Cisco and Third-Party APIs
Cisco Unified Communications Manager Developers Guide
Cisco Unified Communications Manager Data Dictionary
Cisco Unified JTAPI Developers Guide
Cisco Unified TAPI Developers Guide
Cisco Unified TSP Enhancements for Release 4.2(1)
SCCP Messaging Guide for Cisco Unified Communications Manager 6.0(1)
SCCP Messaging Guide for Cisco Unified CallManager 5.0(4)
SCCP Messaging Guide for Cisco Unified CallManager 5.0(2)
SCCP Messaging Guide for Cisco Unified CallManager 5.0(1)
Caveats
Resolved Caveats
Using Bug Toolkit
Open Caveats
Documentation Updates
Omissions
Mobile Connect and Mobile Voice Access Chapter Omits Information About Configuring the Mobile Voice Access Media Resource
Trunk Chapter Omits Restrictions for H.323/H.225 Trunks
Clustering Chapter Omits Information about Subsequent (Subscriber) Node
Licensing Chapter Omits Information on Adjunct Licensing
Cisco TFTP Chapter Omits Configuration Tip on Centralized TFTP
For SIP Trunks Used with Multiple Device Pools, Configure an SRV Destination Port
Cisco Unified Communications Manager Does Not Support Recovery of Administration or Security Passwords
Characters Allowed in a Pre-Shared Key
LDAP Authentication Chapter Omits Information on SSL Certificates and IP Addresses/Hostnames
Enterprise Parameters and Service Parameters Chapters Omit Information on Set to Default Button
Information About Using an SRV Destination Port for the CUP Publish Trunk Service Parameter
Ephemeral Port Range
Trace Compression Support
Multicast Music On Hold and Media Termination Points
Cisco Unified IP Phones Supporting Cisco Call Back with PLKs
Intercom Configuration
Extension Mobility Redundancy
Serviceability Reports
CTI Monitored Lines
Call Throttling and the Code Yellow State
Call Throttling and Denial of Service (DOS) Attacks
Number of Login or Logout Operations that Cisco Extension Mobility Supports
Using the G.722 Codec
New Cisco Signaling Performance Object
Modifying HostName/IP Address Creates Inaccessible RTMT Profiles
Collecting Installation Logs with RTMT
Replication Status on Database Summary in RTMT
Creating an RTMT User
set network dhcp eth0 disable Command Parameters
Time-of-Day Routing Chapter Omits Information About Defined Time Periods
Errors
Mobile Connect and Mobile Voice Access Chapter Contains Incorrect Information About Configuring an H.323 Gateway for System Remote Access by Using PRI
Mobile Connect and Mobile Voice Access Chapter Contains Incorrect Information About Configuring an H.323 Gateway for System Remote Access by Using Hairpinning
Default Device Profile Chapter Incorrectly Includes Expansion Module Settings
AAR Group Chapter Includes Incorrect Description for Dial Prefix Field
Obtaining a License File
Default Device Profile Information
Call Admission Control Bandwidth Example Correction
Barge and Security
Barge Visual Indicator
Barge with Shared Conference Bridge
Serviceability Administration
Adding an Administrator User to Cisco Unity or Cisco Unity Connection
Number of Alphanumeric Characters Allowed in the Pickup Group Name Field
Updates
Information About Changing Region Bandwidth Settings When Video Calls Are Made
Hunt Pilot Chapter Needs Clarification of Maximum Hunt Timer Setting
Cisco Extension Mobility Supplemental Information
Cisco Unified IP Phones That Support Barge
Cisco Unified IP Phones That Support Cisco Call Back
Extension Mobility Successful Authentication Cache
Software Conference Bridge Not Supported
Throttling on SIP UDP Ports
Deleting a Server
Do Not Disturb Feature Priority
Security Icons and Encryption
Changes
Directory Numbers Chapter Includes Incorrect Example for Shared Lines and Call Forward Busy Trigger
Recommended Number of Devices in Device Pool
Devices Associated with the Attendant Console Application User
Number of Replicates Created and State of Replication
Credential Policy Settings
Support for Certificates from External CAs
CAPF System Interactions and Requirements
Peer-to-Peer Image Distribution
Cisco Product Security Overview
Reporting Security Problems in Cisco Products
Release Notes for Cisco Unified Communications Manager Release 6.0(1b)
Updated August 13, 2009
This document includes:
•
Information that was contained in the Release Notes for Cisco Unified CallManager Releases 6.0(1) and 6.0(1a).
•Information included in "Table 1 Information Added" section on page 1.
Table 1 Information Added
Date
|
Addition
|
August 13, 2009
|
Under Important Notes, added the "Unanswered Conference Call" section
|
July 16, 2009
|
Under Important Notes, added the "Considerations for LDAP Port Configuration" section
|
July 09, 2009
|
Under Documentation Updates > Omissions, added the"Time-of-Day Routing Chapter Omits Information About Defined Time Periods" section
|
October 20, 2008
|
Under Important Notes, added the "CSCso96280 Unified CM and CTI May Terminate Unexpectedly" section
|
September 16, 2008
|
Under Important Notes, updated the "Deleting a Server and Adding a Deleted Server to a Cluster" section.
|
September 8, 2008
|
Under Important Notes, added
•"Cisco CallManager Service Stops After Upgrade to Cisco Unified Communications Manager 6.X" section
•"Important Information about Delete Transaction Using Custom File in BAT" section
•"Cisco Unified Communications Manager Does Not Support Recovery of Administration or Security Passwords" section
•"Deleting a Server and Adding a Deleted Server to a Cluster" section
•"Clarification for Call Park Configuration" section
•"Viewing Privileges for Roles in Cisco Unified Communications Manager Administration" section
|
September 8, 2008
|
Under Documentation Updates > Errors, added the
•"AAR Group Chapter Includes Incorrect Description for Dial Prefix Field" section
•"Mobile Connect and Mobile Voice Access Chapter Contains Incorrect Information About Configuring an H.323 Gateway for System Remote Access by Using PRI" section
•"Mobile Connect and Mobile Voice Access Chapter Contains Incorrect Information About Configuring an H.323 Gateway for System Remote Access by Using Hairpinning" section
Under Documentation Updates > Updates, added the
•"Hunt Pilot Chapter Needs Clarification of Maximum Hunt Timer Setting" section
•"Information About Changing Region Bandwidth Settings When Video Calls Are Made" section
|
September 8, 2008
|
Under Documentation Updates > Omissions, added the
•"Clustering Chapter Omits Information about Subsequent (Subscriber) Node" section
•"Licensing Chapter Omits Information on Adjunct Licensing" section
•"Cisco TFTP Chapter Omits Configuration Tip on Centralized TFTP" section
•"Cisco Unified Communications Manager Does Not Support Recovery of Administration or Security Passwords" section
•"Characters Allowed in a Pre-Shared Key" section
•"LDAP Authentication Chapter Omits Information on SSL Certificates and IP Addresses/Hostnames" section
•"Enterprise Parameters and Service Parameters Chapters Omit Information on Set to Default Button" section
•"Information About Using an SRV Destination Port for the CUP Publish Trunk Service Parameter" section
•"For SIP Trunks Used with Multiple Device Pools, Configure an SRV Destination Port" section
•"Trunk Chapter Omits Restrictions for H.323/H.225 Trunks" section
•"Mobile Connect and Mobile Voice Access Chapter Omits Information About Configuring the Mobile Voice Access Media Resource" section
|
September 8, 2008
|
Under Documentation Updates > Changes, added the
•"Directory Numbers Chapter Includes Incorrect Example for Shared Lines and Call Forward Busy Trigger" section
|
August 20, 2008
|
•Under documentation Updates < Omissions, added the "Ephemeral Port Range" section
|
April 14, 2008
|
•Consolidated several sections about upgrading into the "Upgrading to Cisco Unified Communications Manager 6.0(1x)" section which includes:
–"Cisco Upgrade Recommendations" section
–"Upgrade Paths To Cisco Unified Communications Manager 6.0(1x)" section
–"Upgrading from Unified CM 4.x and 5.x" section
–"Upgrading from Cisco Unified Communications Manager Release 6.0(1a) to Release 6.0(1x) Using the UCSInstall File" section
•Added the "Summary of Cisco Unified Communications Manager Release 6.0(1b)" section
–Updated the information in "Table 8 Open Caveats as of April 14, 2008" section on page 123
|
|
|
April 14, 2008
|
•Added the "Upgrading from Cisco Unified Communications Manager Release 6.0(1a) to Release 6.0(1x) Using the UCSInstall File" section
Cisco Advisory for Cisco Unified Communications Manager Release 6.0(1a) got moved from page 1 to the "Important Notes for Cisco Unified Communications Manager Release 6.0(1a)" section
|
These release notes describe the caveats that release 6.0(1) and 6.0(1a) resolve, features and caveats for Cisco Unified Communications Manager Release 6.0(1b) and one Important Note for 6.0(1b). To view the release notes for previous versions of Cisco Unified Communications Manager, choose the Cisco Unified Communications Manager version from the following URL: http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_release_notes_list.html
Summary of Cisco Unified Communications Manager Release 6.0(1b)
The following non comprehensive list gives the caveats that were resolved in this release of Unified CM:
•CSCso53771 - According to Cisco Security, several products in the Cisco Unified Communications family of products contained a command execution vulnerability in the Disaster Recovery Framework (DRF) feature. A remote, unauthenticated user could exploit this vulnerability to execute arbitrary commands that may allow full administrative access to affected systems.
•CSCso45910 - Prior to this release, after an upgrade, the server would not boot to the new partition.
•CSCSk58101 - Prior to this release TabSync did not connect to Unified CM
•CSCsm47603 - The BIOS bundled with Cisco Unified Communications Manager Release 6.0(1a) does not support the E6400 processor that IBM includes in their 7825I3 servers. Because of this, Unified CM Release 6.0(1a) downrevs the BIOS to an unsupported version during installation or upgrade. Unfortunately, during start up, the system simply warns the user by displaying a warning message. The customer will not see this message if he is not constantly looking at the terminal. The system allows startup to continue in the unsupported state. The implications of running in this state remain unknown.
•CSCsj82405 - Prior to this release, DMA did not migrate some LDAP users due to spaces in the user profile.
•CSCsi71128 - Prior to this release, DMA required 28 hours to run on pre-4.1(3) system with many devices.
•CSCsk41261 - Prior to this release, DMA reported backup failure on Unified CM 4.1.3 to Unified CM 6.0.1 migration.
•CSCsk70423 - Prior to this release, an encrypted password displayed in plain text in DMA trace files.
•CSCso57947 - Prior to this release, no error displayed in GUI for COP file installation problem.
•CSCso67112 - Prior to this release, upgrade status specified running when upgrade was complete.
•CSCsj95364 - Prior to this release, DMA did not export users if the profileOwner and userId do not match.
•CSCsj94674 - Prior to this release, the need existed for DirExport to export users with an unambiguous numplan.
Contents
These release notes discuss the following topics:
•Introduction
•System Requirements
–Upgrade Paths To Cisco Unified Communications Manager 6.0(1x)
–Upgrading from Cisco Unified Communications Manager Release 6.0(1a) to Release 6.0(1x) Using the UCSInstall File
–Upgrading from Unified CM 4.x and 5.x
•Related Documentation
•Important Notes
•New and Changed Information in Cisco Unified Communications Manager Releases 6.0(1x)
•Caveats
–Open Caveats as of April 14, 2008
•Documentation Updates
•Cisco Product Security Overview
Introduction
Cisco Unified Communications Manager, the call-processing component of the Cisco Unified Communications System, extends enterprise telephony features and capabilities to IP phones, media processing devices, voice-over-IP (VoIP) gateways, mobile devices and multimedia applications.
System Requirements
Make sure that you install and configure Cisco Unified CM Release 6.0(1b) on a Cisco Media Convergence Server (MCS) or a Cisco-approved HP server configuration or a Cisco-approved IBM server configuration.
To find which MCS are compatible with Cisco Unified CM Release 6.0(1b), refer to the Supported Servers for Cisco Unified Communications Manager Releases: http://www.cisco.com/en/US/prod/collateral/voicesw/ps6790/ps5748/ps378/prod_brochure0900aecd80 62a4f9.html.
Note Make sure that the matrix indicates that your server model supports Cisco Unified Communications Manager Release 6.0(1b).
Note Some servers that are listed in the compatibility matrix may require additional hardware support for Cisco Unified Communications Manager Release 6.0(1b). Make sure that your server meets the minimum hardware requirements, as indicated in the footnotes of the compatibility matrix. Cisco Unified Communications Manager requires a minimum of 2 GB of memory, 72 GB disk drive, and 2 GHz processor.
Uninterruptible Power Supply
Ensure that you connect each Cisco Unified Communications Manager node to an uninterruptible power supply (UPS) to provide backup power and protect your system.
Caution If you do not connect the Cisco Unified Communication Manager nodes to a UPS damage to physical media may occur and a new installation of Cisco Unified Communications Manager may be required.
Upgrading System Software
Before you upgrade the software version of Cisco Unified Communications Manager, verify your current software version.
To do that, open Cisco Unified Communications Manager Administration. The following information displays:
•Cisco Unified Communications Manager System version
•Cisco Unified Communications Manager Administration version
Upgrading to Cisco Unified Communications Manager 6.0(1x)
The following sections contain information pertinent to upgrading to this release of Unified CM.
•Cisco Upgrade Recommendations
•Upgrade Paths To Cisco Unified Communications Manager 6.0(1x)
•Upgrading from Unified CM 4.x and 5.x
•Upgrading from Cisco Unified Communications Manager Release 6.0(1a) to Release 6.0(1x) Using the UCSInstall File
Cisco Upgrade Recommendations
Cisco offers the following recommendations.
Table 2 Cisco Recommendations
If you currently use
|
Do this
|
Unified CM 6.0(1) or 6.0(1a)
|
Upgrade to Unified CM 6.0(1b)
|
A Unified CM 6.01 or 6.0(1a) Engineering Special
|
Contact TAC to obtain the fixes that are included in Release 6.0(1b)
|
Upgrade Paths To Cisco Unified Communications Manager 6.0(1x)
For information about supported Cisco Unified CM upgrades, see the Cisco Unified Communications Manager Compatibility Matrix at the following URL:
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/compat/ccmcompmatr.html.
Upgrading from Unified CM 4.x and 5.x
If you are upgrading from 4.1.3, 4.2.3, 5.1.1, 5.1.2, or 5.1.3, use the Product Upgrade Tool (PUT) or the PUT for registered customers only to obtain a media kit and license or purchase the upgrade from Cisco Sales.
To use the PUT, you must enter your Cisco contract number (Smartnet, SASU or ESW) and request the CD/CD set. If you do not have a contract for Cisco Unified Communications Manager, you must purchase the upgrade from Cisco Sales.
For more information about supported Unified CM upgrades, see the Cisco Unified Communications Manager Software Compatibility Matrix at the following URL:
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/compat/ccmcompmatr.html
Upgrading from Cisco Unified Communications Manager Release 6.0(1a) to Release 6.0(1x) Using the UCSInstall File
Caution Do not use the following information to upgrade from any Unified CM release other than 6.0(1a).
Because of its size, the UCSInstall iso file, UCSInstall_UCOS_6.0.1.3000-7.sgn.iso, has been divided into two parts:
•UCSInstall_UCOS_6.0.1.3000-7.sgn.iso_part1of2
•UCSInstall_UCOS_6.0.1.3000-7.sgn.iso_part2of2
Procedure
Step 1 From www.cisco.com, download the two UCSInstall files.
Step 2 Execute one of the following commands to reunite the two parts of the file.
Note The 6.0.1.3000-7 build is a non-bootable ISO which is only useful for upgrades. It cannot be used for new installations.
a. If you have a Unix/Linux system, cut and paste the following command from this document into the CLI to combine the two parts:
b. If you have a Windows system, cut and paste the following command from this document into the command prompt (cmd.exe) to combine the two parts:
COPY /B UCSInstall_UCOS_6.0.1.3000-7.sgn.iso_part1of2+UCSInstall_UCOS_6.0.1.3000-7.sgn.iso_part2of2 UCSInstall_UCOS_6.0.1.3000-7.sgn.iso
|
Step 3 Use an md5sum utility to verify that the MD5 sum of the final file is correct.
58cb11e2025f5e688abfc53daf3bef27 UCSInstall_UCOS_6.0.1.3000-7.sgn.iso
Software Download URLs
You can access the latest software upgrades for Cisco Unified Communications Manager at http://tools.cisco.com/support/downloads/go/Redirect.x?mdfid=278875240
Related Documentation
The documentation that supports Cisco Unified Communications Manager Release 6.0(1x) resides at
http://www.cisco.com/en/US/products/sw/voicesw/ps556/tsd_products_support_series_home.html
Limitations and Restrictions
A recommendation of compatible software releases that have been verified by the test for customers represents a major deliverable of the Cisco Unified Communications System testing. The recommendations, which are not exclusive, represent an addition to interoperability recommendations for each individual voice application or voice infrastructure product.
For a list of software and firmware versions of IP telephony components that were tested for interoperability with Cisco Unified Communications Manager 6.0(1x) as part of Unified Communications System Release 6.0(1x) testing, see http://www.cisco.com/go/unified-techinfo.
For a list of software and firmware versions of contact center components that were tested for interoperability with Cisco Unified Communications Manager 6.0(1) as part of Unified Communications System Release 6.0(1x) testing, see http://tools.cisco.com/ITDIT/vtgsca/.
Be aware that the release of Cisco IP telephony products does not always coincide with Cisco Unified Communications Manager releases. If a product does not meet the compatibility testing requirements with Cisco Unified Communications Manager, you need to wait until a compatible version of the product becomes available before you can upgrade to Cisco Unified Communications Manager 6.0(1b). For the most current compatibility combinations and defects that are associated with other Cisco Unified Communications products, refer to the documentation that is associated with those products.
Important Notes
The following section contains important information that may have been unavailable upon the initial release of documentation for Cisco Unified Communications Manager Release 6.0(1).
Important Notes for Cisco Unified Communications Manager Release 6.0(1b)
•Unanswered Conference Call
•Considerations for LDAP Port Configuration
•CSCso96280 Unified CM and CTI May Terminate Unexpectedly
•Cisco CallManager Service Stops After Upgrade to Cisco Unified Communications Manager 6.X
•Important Information about Delete Transaction Using Custom File in BAT
•Cisco Unified Communications Manager Does Not Support Recovery of Administration or Security Passwords
•Deleting a Server and Adding a Deleted Server to a Cluster
•Clarification for Call Park Configuration
•Viewing Privileges for Roles in Cisco Unified Communications Manager Administration
•CSCso94813: Subscriber Server Install Fails Due to 'hostname -i" Failing
•Cisco Unified Communications Disaster Recovery Framework Command Execution
•Voice Mailbox Mask Interacts with Diversion Header
Important Notes for Cisco Unified Communications Manager Release 6.0(1a)
•Cisco Advisory for Cisco Unified Communications Manager Release 6.0(1a)
•Cisco Security Agent (CSA) Drops Incoming TCP SYN Connection Attempts with No Logs
•Do Not Upgrade from Cisco Unified CallManager 5.1(3) to Cisco Unified Communications Manager 6.x
•CSCsi75567 MCS-7825H2-IPC1 Reboots Randomly
Important Notes for Cisco Unified Communications Manager Release 6.0(1)
•New Clustering Over WAN Requirements
•Voice, Cisco Fax Relay and Fax Passthrough Calls Fail
•Device Reset Speed
•No Such Name Error Returned in the SNMP Response
•Value of the Maximum Current Requests Service Parameter After Upgrade to Release 6.0
•IP Phone Messenger (IPPM) User Does Not Have Callback Capability
•Monitoring Call Gets Dropped When Agent Call Is Put on Hold
•DVDROM Not Accessible After Upgrade
•Deleting Then Adding Back a Server in Cisco Unified Communications Manager Administration
•Call History Might Get Lost When AAR Routes Over QSIG Trunk
•Extension Mobility Maximum Concurrent Requests Number Does Not Change After Upgrade
•Cisco Unified Communications Manager Assistant Limitations with Cisco IP Communicator
•Translation Pattern Support
•Subscribe Calendar 500 Internal Error
•Maximum Trace Settings
•Disabling the Advertise G.722 Codec Enterprise Parameter When You Are Using System Features
•Using FTP to Upgrade to Cisco Unified Communications Manager Release 6.0(1b)
•Cisco Unified Personal Communicator LDAP Attribute Mappings
•Terminal Server Causes RTMT to Display Repeating Syslog and Alert Messages
Unanswered Conference Call
Be aware that an unanswered conference call that gets forwarded to voice-mail over QSIG PRI reaches the general greeting (open tree).
Considerations for LDAP Port Configuration
When you configure the LDAP Port field in the LDAP Authentication window in Cisco Unified CM Administration, you specify the port number that the corporate directory uses to receive LDAP requests. How your corporate directory is configured determines which port number to enter in this field. For example, before you configure the LDAP Port field, determine whether your LDAP server acts as a Global Catalog server and whether your configuration requires LDAP over SSL. Consider entering one of the following port numbers:
Tip Your configuration may require that you enter a different port number than the numbers that are listed in the following bullets. Before you configure the LDAP Port field, contact the administrator of your directory server to determine the correct port number to enter.
LDAP Port For When the LDAP Server Is Not a Global Catalog Server
•389—When SSL is not required. (This port number is the default that displays in the LDAP Port field.)
•636—When SSL is required. (If you enter this port number, make sure that you check the Use SSL check box.)
LDAP Port For When the LDAP Server Is a Global Catalog Server
•3268—When SSL is not required.
•3269—When SSL is required. (If you enter this port number, make sure that you check the Use SSL check box.)
CSCso96280 Unified CM and CTI May Terminate Unexpectedly
If your Unified CM and CTI service crash due to SdlTimer Services, it is recommended that you schedule a reboot of the affected nodes before 248 days of system uptime elapse (since the last reboot).
Note You must reboot the server to restart the timer to 248 days. Unified CM or Cisco CTIManager service individual restarts alone do not reset the timer.
To verify system uptime perform the show status CLI command on each cluster node.
See CSCso96280 for more information.
Cisco CallManager Service Stops After Upgrade to Cisco Unified Communications Manager 6.X
After you upgrade to Cisco Unified Communications Manager 6.X from a compatible Cisco Unified CM 5.X release, the Cisco CallManager service does not automatically run, even though Cisco Unified Serviceability shows that the Cisco CallManager service is activated.
Immediately after you complete the upgrade, upload the software feature license that is required for Cisco Unified Communications Manager 6.X in Cisco Unified Communications Manager Administration, and restart the Cisco CallManager service in Cisco Unified Serviceability. Until you perform these tasks, devices fail to register with Cisco Unified Communications Manager.
For more information on licensing, refer to the licensing chapters in the Cisco Unified Communications Manager Administration Guide and the Cisco Unified Communications Manager System Guide.
Important Information about Delete Transaction Using Custom File in BAT
Do not use the insert or export transaction files that are created with bat.xlt for the delete transaction. Instead, you must create a custom file with the details of the records that need to be deleted. Use only this file for the delete transaction. In this custom delete file, you do not need a header, and you can enter values for name, description, or user.
Cisco Unified Communications Manager Does Not Support Recovery of Administration or Security Passwords
Cisco Unified Communications Manager does not support recovery of administration or security passwords. If you lose these passwords, you must reset the passwords, as described in the Cisco Unified Communications Operating System Administration Guide.
The Cisco Unified Communications Operating System Administration Guide calls the section, "Recovering the Administrator or Security Passwords," instead of "Resetting the Administrator or Security Passwords." Access the "Recovering the Administrator or Security Passwords" section to reset the passwords.
Deleting a Server and Adding a Deleted Server to a Cluster
In Cisco Unified Communications Manager Administration, you cannot delete the first node of the cluster, but you can delete subsequent nodes. Before you delete a subsequent node in the Find and List Servers window, Cisco Unified Communications Manager Administration displays the following message: "You are about to permanently delete one or more servers. This action cannot be undone. Continue?". If you click OK, the server gets deleted from the Cisco Unified Communications Manager database and is not available for use.
Tip When you attempt to delete a server from the Server Configuration window, a message that is similar to the one in the preceding paragraph displays. If you click OK, the server gets deleted from the Cisco Unified Communications Manager database and is not available for use.
Before you delete a server, consider the following information:
•Cisco Unified Communications Manager Administration does not allow you to delete the first node in the cluster, but you can delete any subsequent node.
•Cisco recommends that you do not delete any node that has Cisco Unified Communications Manager running on it, especially if the node has devices, such as phones, registered with it.
•Although dependency records exist for the subsequent nodes, the records do not prevent you from deleting the node.
•If any call park numbers are configured for Cisco Unified Communications Manager on the node that is being deleted, the deletion fails. Before you can delete the node, you must delete the call park numbers in Cisco Unified Communications Manager Administration.
•If a configuration field in Cisco Unified Communications Manager Administration contains the IP address or host name for a server that you plan to delete, update the configuration before you delete the server. If you do not perform this task, features that rely on the configuration may not work after you delete the server; for example, if you enter the IP address or host name for a service parameter, enterprise parameter, service URL, directory URL, IP phone service, and so on, update this configuration before you delete the server.
•If an application GUI, for example, Cisco Unity, Cisco Unity Connection, and so on, contains the IP address or hostname for the server that you plan to delete, update the configuration in the corresponding GUIs before you delete the server. If you do not perform this task, features that rely on the configuration may not work after you delete the server.
•The system may automatically delete some devices, such as MOH servers, when you delete a server.
•Before you delete a node, Cisco recommends that you deactivate the services that are active on the subsequent node. Performing this task ensures that the services work after you delete the node.
•Changes to the server configuration do not take effect until you restart Cisco Unified Communications Manager. For information about restarting the Cisco CallManager service, refer to the Cisco Unified Serviceability Administration Guide.
•To ensure that database files get updated correctly, you must reboot the cluster after you delete a server.
•After you delete the node, access Cisco Unified Reporting to verify Cisco Unified Communications Manager removed the node from the cluster. In addition, access Cisco Unified Reporting, RTMT, or the CLI to verify that database replication is occurring between existing nodes; if necessary, repair database replication between the nodes.
If you delete a subsequent node (subscriber) from Cisco Unified Communications Manager Administration and you want to add it back to the cluster, perform the following procedure:
Procedure
Step 1 In Cisco Unified Communications Manager Administration, add the server by choosing System > Server.
Step 2 After you add the subsequent node to Cisco Unified Communications Manager Administration, perform an installation on the server by using the disk that Cisco provided in your software kit.
Tip For example, if you have a version 6.01(b) disk, perform a 6.0(1b) installation on the node. If you have a disk with a compatible version of 5.X on it, for example, use the disk to install Cisco Unified Communications Manager on the subsequent node; during the installation, choose the Upgrade During Install option when the installation displays the options.
Make sure that the version that you install on the subsequent node matches the version that runs on the first node (publisher) in the cluster.
If the first node in the cluster runs Cisco Unified Communications Manager 6.0(1b) version and a service release (or engineering special), you must choose the Upgrade During Install option when the installation displays the installation options; before you choose this option, ensure that you can access the service release (or engineering special) image on DVD or a remote server. For more information on how to perform an installation, refer toinstallation documentation that supports your version of Cisco Unified Communications Manager.
Step 3 After you install Cisco Unified Communications Manager, configure the subsequent node, as described in the installation documentation that supports your version of Cisco Unified Communications Manager.
Step 4 Access the Cisco Unified Reporting, RTMT, or the CLI to verify that database replication is occurring between existing nodes; if necessary, repair database replication between the nodes.
Clarification for Call Park Configuration
Consider the following information when you configure Call Park:
Call Park numbers cannot overlap between Cisco Unified Communications Manager servers. Ensure that each Cisco Unified Communications Manager server has its own unique number range.
Call Park numbers may have an associated partition that restricts access to the Call Park numbers and prevents retrieval of parked calls. If partitions are used to restrict access to Call Park numbers, you must define a unique call park number or range of call park extension numbers for each partition on each Cisco Unified Communications Manager in the cluster.
When the end user invokes Call Park, Cisco Unified Communications Manager attempts to find an available Call Park number from a Call Park partition that is currently accessible via the calling search space for the party that invoked Call Park.
Viewing Privileges for Roles in Cisco Unified Communications Manager Administration
The Role Configuration window in Cisco Unified Communications Manager Administration displays the privileges for each standard role. To access the Role Configuration window, find the role by choosing User Management > Role; when the Find and List Roles window displays, click Find. Click the link for the standard role that you want to view. After the Role Configuration window displays, you can view the privileges in the Resource Access Information pane.
TAPS Name Change in Bulk Administration Tool
Documentation refers to the Tool for Auto-Registered Phone Support (TAPS) as Cisco Unified Communications Manager Auto-Register Phone Tool in the Online Help for Bulk Administration. All references to 'Cisco Unified Communications Manager Auto-Register Phone Tool' in the Bulk Administration Tool Online Help should be read as 'Tool for Auto-Registered Phone Support (TAPS)'. This is in compliance with the Bulk Administration user interface.
For More Information
For information on configuring additional features in BAT, refer to the BAT documentation for Cisco Unified Communications Manager.
CSCso94813: Subscriber Server Install Fails Due to 'hostname -i" Failing
Ensure that the hostname of the publisher server and subscriber servers are distinctly different. Also ensure that the publisher server name does not appear as a substring of the subscriber server hostname.
If the names are not distinct, you will not be able to install the subscriber servers; and the install log file will indicate the following hostname failure: hostname: Host name lookup failure.
Example:The publisher server installs with a hostname of XXXX and a subscriber server gets
defined to the publisher server. The subscriber server hostname is XXXX-YYY. The
subscriber server hostname contains the publisher server hostname as a substring.In this
case, the subscriber server install fails.
Cisco Unified Communications Disaster Recovery Framework Command Execution
Several products in the Cisco Unified Communications family of products contain a command execution vulnerability in the Disaster Recovery Framework (DRF) feature. A remote, unauthenticated user could exploit this vulnerability to execute arbitrary commands that may allow full administrative access to affected systems. There is a workaround for this vulnerability.
Cisco has released free software updates that address this vulnerability.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20080403-drf.shtml.
Voice Mailbox Mask Interacts with Diversion Header
When a call gets redirected from a DN to a voice-mail server/service that is integrated with Unified CM using a SIP trunk, the voice mailbox mask on the voice-mail profile for the phone modifies the diverting number in the SIP diversion header. This behavior is expected because the diversion header gets used by the Unified CM server to choose a mailbox.
Cisco Advisory for Cisco Unified Communications Manager Release 6.0(1a)
A Cisco advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20070801-IOS-voice.shtml.
Summary
Cisco recommends that customers who run Cisco Unified Communications Manager Release 6.0(1) upgrade to release 6.0(1a). This recommendation applies because of the following information.
Cisco IOS software includes multiple voice-related vulnerabilities, one of which (malformed SIP packet) also gets shared with Cisco Unified Communications Manager.
SIP represents a protocol that is used to establish, modify, and terminate multimedia sessions. Most commonly, SIP gets used for Internet telephony. SIP call signaling can use UDP (User Datagram Protocol) or TCP (Transport Control Protocol) as an underlying transport protocol. In all cases processing a malformed SIP packet.can trigger vulnerabilities.
A malformed SIP packet can cause a vulnerable device to crash and can allow arbitrary code to be executed. The following Cisco Bug ID documents these vulnerabilities:
CSCsi80102 Cisco Unified Communications Manager crashes while processing malformed SIP packet.
Successful exploitation of the vulnerabilities that are listed as Cisco Bug ID CSCsi80102 can lead to remote code execution.
Successful exploitation of other SIP-related vulnerabilities that are listed in the Cisco Systems advisory can cause the affected device to crash. Repeated exploitation could result in a sustained denial of service (DoS) attack.
When considering software upgrades, also consult http://www.cisco.com/go/psirt and any subsequent advisories to determine exposure and a complete upgrade solution.
In all cases, you should exercise caution to be certain that the devices to be upgraded contain sufficient memory and that the new release will continue to support your current hardware and software configurations. If the information is not clear, contact the Cisco Technical Assistance Center (TAC) or your contracted maintenance provider for assistance.
No workarounds exist to mitigate the effects of any of the vulnerabilities apart from disabling the protocol or feature itself.
Obtaining Fixed Software
Cisco makes free software available to address these vulnerabilities. Prior to deploying software, customers should consult their maintenance provider or check the software for feature set compatibility and known issues that are specific to their environment.
Customers may only install and expect support for the feature sets that they have purchased. By installing, downloading, accessing, or otherwise using such software upgrades, customers agree to be bound by the terms of Cisco software license terms that are found at http://www.cisco.com/public/sw-license-agreement.html, or as otherwise set forth at Cisco.com Downloads at
http://www.cisco.com/public/sw-center/sw-usingswc.shtml.
These release notes describe updates and caveats for Cisco Unified Communications Manager Release 6.0(1a). To view the release notes for previous versions of Cisco Unified Communications Manager, choose the Cisco Unified Communications Manager version from the following URL: http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_release_notes_list.html
Before you install Cisco Unified Communications Manager, Cisco recommends that you review the "Important Notes" section for information about issues that may affect your system.
Note To ensure continuous operation and optimal performance of your Cisco Unified Communications Manager system, you must upgrade to Cisco Unified Communications Manager 6.0(1a).
Cisco recommends that you check Cisco.com for the latest software updates to Cisco Unified Communications Manager and its applications and download and install the latest updates on your system before the deployment of your Cisco Unified Communications Manager system. For a list of commonly used URLs, see the "Upgrading System Software" section.
Cisco Security Agent (CSA) Drops Incoming TCP SYN Connection Attempts with No Logs
Under heavy call volume, when a large number of H.323 gateways are utilized, as calls are answered and media gets established, severe delays may occur with the H.245 connection between the gateways and the Cisco Unified Communications Manager server.
This condition causes calls to not connect or to be dropped unexpectedly. This also may impact other incoming TCP connections, and unexpected failures or delays may occur.
If you have CSA enabled, no workaround exists; however, you can disable CSA by using the utils csa disable CLI command.
Note Disabling CSA requires restart of the Cisco Unified Communications Manager server.
Do Not Upgrade from Cisco Unified CallManager 5.1(3) to Cisco Unified Communications Manager 6.x
You cannot successfully upgrade from Cisco Unified CallManager Release 5.1(3) to Cisco Unified Communications Manager Release 6.x.
CSCsi75567 MCS-7825H2-IPC1 Reboots Randomly
Sporadic reboots of the 7825H2 servers get triggered during long system hangs. ASR functionality autorecovers the servers after 10 minutes of kernel unresponsiveness. Event timing ranges from once every 3 months to once every 3 days.
Workaround
See http://www.cisco.com/warp/public/770/fn62850.shtml.
New Clustering Over WAN Requirements
Every 10,000 busy hour call attempts (BHCA) between sites that are clustered over the WAN requires 900 Kb/s of bandwidth for Intracluster Communication Signalling (ICCS). This minimum bandwidth requirement exists for call control traffic and gets classified as priority traffic. You should allocate additional ICCS bandwidth at 900 Kb/s per 10,000 BHCA.
The minimum recommended bandwidth between sites that are clustered over the WAN equals 1.544 Mbps. This amount allows for the minimum of 900 Kb/s for ICCS and 644 Kb/s for database and other interserver traffic.
In prior versions of Cisco Unified Communications Manager, subscriber servers in the cluster use the publisher database for READ/WRITE access and only use the local database for READ access when the publisher database cannot be reached. With Cisco Unified Communications Manager Release 6.0, subscriber servers in the cluster READ the local database. DB WRITES happens in both the local database and the publisher database, depending on the type of data. DBMS (IDS) replication synchronizes the databases on the nodes of the cluster. When recovering from a failover conditions such as loss of WAN connectivity for an extended period of time, ensure that the Cisco Unified Communications Manager databases get synchronized with any changes that may occurred during the outage. This process happens automatically when database connectivity gets restored. This process may take longer over low bandwidth and/or higher delay links.
DB REPLICATION REPAIR/RESET:
At some point, you may need to reset or repair database replication between the Cisco Unified Communications Manager servers. To do this, use the utils dbreplication repair all or utils dbreplication reset all command at the command line interface (CLI).
When you repair or reset database replication using the CLI on remote subscribers over the WAN, all Cisco Unified Communications Manager databases in the cluster get resynchronized, which requires additional bandwidth above 1.544 Mbps. Database replication over lower bandwidths may take longer.
Note When you repair or reset database replication on multiple subscribers at the same remote location expect longer completion times. Cisco recommends that you repair or reset database replication of these remote subscribers one at a time.
You can repair or reset database replication on multiple subscribers at different remote locations simultaneously.
Voice, Cisco Fax Relay and Fax Passthrough Calls Fail
Voice, Cisco Fax Relay and Fax Passthrough calls fail when mgcp fax t38 inhibit command is configured.
Workaround
When you disable T.38 fax relay, you should also disable fxr-package (which is enabled by default) and reset the MGCP service.
Note If the gateway and call agent fail on the fax protocol negotiation, all calls get rejected, including voice calls.
Device Reset Speed
You might notice that phone device reset takes longer than in previous releases, especially in large-scale clusters.
Workaround
To mitigate the decrease in speed, Cisco recommends that customers with more than 1000 users on a system wait until the maintenance window to perform a device reset on the phones.
No Such Name Error Returned in the SNMP Response
If the getbulk/getnext/getmany request contains multiple OID variables in its request PDU and the subsequent tables appear empty in the CISCO-CCM MIB, the responses may include NO_SUCH_NAME, for SNMP v1 version or GENERIC_ERROR, for SNMP v2c or v3 version because the time that it takes to process the SNMP requests exceeds the MasterAgent timeout duration (currently set at 25 seconds).
Workaround
You can do many things to avoid this problem, including the following workaround:
•Use the available scalar variables (1.3.6.1.4.1.9.9.156.1.5) to determine the table size before you access the table or perform the get operation on the desired table first and then query the non-empty tables.
•Reduce the number of variables that are queried in a single request. For example, if the management application specifies timeout at 3 seconds for empty tables, Cisco recommends that you specify no more than 1 OID. For non-empty tables, it takes 1 second to retrieve one row of data.
•Increase the response timeout.
•Reduce the number of retries.
•Do not use getbulk SNMP API. Getbulk API gets the number of records that is specified by MaxRepitions. This means that, even if the next object goes outside the table or MIB, it gets those objects. So, if the Cisco Unified Communications Manager MIB has empty tables, it goes to next MIB and so will require more time to respond. When you know that the table is not empty, use getbulk API. Under these conditions, limit the maximum repetition counts to 5 to get a response within 5 seconds.
•Structure SNMP queries to reflect current limits.
Note The SNMP standard requires that getnext and getbulk APIs return the next available object even if the end of the table has been reached. In the case of empty tables, the CCMAgent keeps traversing the MIB tree until it finds data to return.
Value of the Maximum Current Requests Service Parameter After Upgrade to Release 6.0
The Cisco Extension Mobility service parameter, Maximum Concurrent Requests, does not change when you upgrade to Release 6.0 from an earlier release. This deliberate and intended situation allows you to retain the preexisting value even though Release 6.0 has a default value of 15 maximum concurrent requests. You can change this value on the Service Parameters Configuration window.
IP Phone Messenger (IPPM) User Does Not Have Callback Capability
An IPPM (IP Phone Messenger) user does not have callback capabilities if the user logs into IPPM on a phone where the user is not assigned to the line appearance. When a user logs in to the IPPM service on a Cisco Unified IP Phone and views the details of a MeetingPlace-based meeting on the phone screen, the Callback and Join softkeys do not display when the user is not associated with a line appearance. Although the user has associated himself with a device on the Cisco Unified Communication Manager Administration End User Configuration window, the line appearance on the device itself must get configured with an association to the user for the softkeys to display on the phone.
Workaround:
Associate the line appearance to the end user by using Cisco Unified Communications Manager Administration.
Step 1 From Cisco Unified Communications Manager administration, choose Device > Phone.
The Find and List Phones window displays.
Step 2 Locate the phone and click the device name of that phone.
The Phone Configuration window displays.
Step 3 Locate the line and click it.
Step 4 Associate the line to the end user (near bottom of the window).
Note You will not have callback capabilities if you log in to a phone where you are assigned on the line appearance.
Monitoring Call Gets Dropped When Agent Call Is Put on Hold
When the agent IP phone uses SIP and the supervisor IP phone uses SCCP, the monitoring call gets set up correctly; however. when the agent call is put on hold, the supervisor gets disconnected and receives a fast busy tone.
To avoid this problem, you can change the signaling protocol on either the agent or supervisor, so both phones use the same signaling protocol.
Note If you cannot apply that workaround, no way exists to prevent the disconnect; however, the supervisor can reinitiate a monitoring session from the CTI application, and a new monitoring call will get set up.
DVDROM Not Accessible After Upgrade
If you pull the DVD drive out or the DVD drive becomes not accessible during an upgrade, the grub.conf file may become corrupted.
If this happens, you may experience problems when you try to switch versions. For example, rebooting to the upgraded partition may fail, or the reboot may fail, or the reboot will result in a grub menu.
Workaround
You should open a TAC case.
Deleting Then Adding Back a Server in Cisco Unified Communications Manager Administration
In Cisco Unified Communications Manager Administration, you cannot delete the first node of the cluster, but you can delete subsequent nodes. Before you delete a subsequent node in the Find and List Servers window, Cisco Unified Communications Manager Administration displays the following message: "You are about to permanently delete one or more servers. This action cannot be undone. Continue?". If you click OK, the server gets deleted from the Cisco Unified Communications Manager database and is not available for use.
Tip When you attempt to delete a server from the Server Configuration window, a similar message as the one in the preceding paragraph displays. If you click OK, the server gets deleted from the Cisco Unified Communications Manager database and is not available for use.
If you delete a subsequent node (subscriber) from Cisco Unified Communications Manager Administration and you want to add it back to the cluster, perform the following procedure:
Tip Before you perform the procedure, review the information in the "Deleting a Server" section, which provides important considerations on deleting a server.
Procedure
Step 1 In Cisco Unified Communications Manager Administration, add the server, as described in the "Configuring a Server" section (Server Configuration chapter) in the Cisco Unified Communications Manager Administration Guide.
Step 2 After you add the subsequent node to Cisco Unified Communications Manager Administration, perform a 6.0(1) installation on it by using the 6.0(1) disk that Cisco provided in your software kit.
Tip Make sure that the version that you install on the subsequent node matches the version that runs on the first node (publisher) in the cluster.
If the first node in the cluster runs 6.0(1) and a service release (or engineering special), you must choose the Upgrade During Install option when the installation displays the installation options; before you choose this option, ensure that you can access the service release (or engineering special) image on DVD or a remote server. For more information on how to perform an installation, refer to Installing Cisco Unified Communications Manager 6.0(1).
After you install Cisco Unified Communications Manager, configure the subsequent node, as described in the "Configuring a Subsequent Node" section in the document, Installing Cisco Unified Communications Manager 6.0(1).
Call History Might Get Lost When AAR Routes Over QSIG Trunk
When a call is forwarded to another cluster over a trunk/gateway by using QSIG because of insufficient bandwidth (Call Forward No Bandwidth - CFNB), call history might get lost.
If Phone A calls Phone B, which is in a low-bandwidth location, with CFNR set to forward calls to Phone C, which is in a different cluster, and the QSIG protocol is used on the trunk/gateway, the original called party and the last redirecting party might not get passed to the destination party.
Extension Mobility Maximum Concurrent Requests Number Does Not Change After Upgrade
When you upgrade from Cisco Unified CallManager Release 4.x or 5.x to Cisco Unified Communications Manager Release 6,0(1), and you navigate to System-->Service Parameters-->Cisco Extension Mobility, you will see that the maximum concurrent requests value does not change after the upgrade. The value remains the same as it was for Cisco Unified CallManager Release 4.x or 5.x, even though the default value for the maximum concurrent requests for extension mobility in Cisco Unified Communications Manager Release 6.0(1b) is 15.
You can manually change this number to the system default of 15 or greater.
•
Cisco Unified Communications Manager Assistant Limitations with Cisco IP Communicator
Cisco IP Communicator does not support Cisco Unified Communications Manager Assistant Releases 5.1 and 6.0.
Translation Pattern Support
If a calling party transformation mask is configured for a translation pattern that is applied to a JTAPI application-controlled address, the application may see extra connections that are created and disconnected when both the calling and called party are observed. The system creates a connection for a transformed calling party instead of the actual calling party, and CiscoCall.getCurrentCallingParty() would return the transformed calling party, when only the called party is observed. In general, JTAPI might not be able to create the appropriate connection in the call and might not be able to provide correct information for currentCalling, currentCalled, calling, called, and lastRedirecting parties.
For example, consider a translation pattern X that is configured with a calling party transformation mask Y and calledparty transformation mask B. If A calls X, the call goes to B. In this scenario
If the application is observing only B, JTAPI creates a connection for Y and B, and CiscoCall.getCurrentCallingParty() would return Address Y.
If the application is observing both A and B, a connection for A and B gets created, a connection for Y gets temporarily created and dropped, and CiscoCall.getCurrentCallingParty() would return Address Y.
Other inconsistencies could occur in the calling information if further features get performed on a basic call. Cisco recommends that you not configure a calling party transformation mask for a translation pattern that might get applied to JTAPI application-controlled addresses.
Subscribe Calendar 500 Internal Error
A large number of Cisco Unified Presence Communicator users (for example 150 or more), each with 30 or more contacts with calendar enabled, that log in within a short time can compromise the ability of the Microsoft Exchange server to process the requests. The Microsoft Exchange 2003 server will begin to return "500 Internal Server Error" response to most, if not all, requests. The Microsoft Exchange server may or may not recover from the load.
Note The exact conditions may vary from server to server; however, login rates of more than one per second may cause the condition. In some instances, this behavior can get triggered at a rate of one login per 30 seconds.
Maximum Trace Settings
The maximum recommended Cisco Unified Communications Manager trace settings specifies 2,500 files of 2 MB each, for SDI and SDL traces, for a combined total of 5000 files. You can increase SDI traces to 5,000 files if SDL traces are disabled, but not vice versa. All other components should stay within 126 MB bucket (for example, 63 files of 2 MB). If you increase logs past the recommended limit, system performance gets reduced due to IOWAIT. After the system experiences IOWAIT related performance degradation, the only solution requires you to lower traces and use RTMT to remove all CCM/CTI SDI/SDL traces. For that reason, you should limit tracing to 5 GB for CCM and 5 GB for CTI.
Disabling the Advertise G.722 Codec Enterprise Parameter When You Are Using System Features
If you experience feature interoperability issues, and you have the Cisco Unified Communications Manager enterprise parameter Advertise G.722 Codec set to Enabled, change the setting to Disabled (the default setting specifies Enabled) and update the device pools for the phones. When this parameter specifies enabled, the enterprise parameter allows Cisco Unified IP Phones (such as 7971, 7970, 7941, 7961) to negotiate and use the G.722 codec when calls are within the same region.
If individual phone control and use of a specific codec type is required (for example, G.711), check the configuration of each phone (by using Phone Configuration) for the parameter Advertise G.722 Codec and change the setting to Disabled. Save and reset the device.
Note If the Advertise G.722 Codec enterprise parameter is set to Enabled, the administrator can override this setting by using the G722 Codec Enabled service parameter. This service parameter determines whether Cisco Unified Communications Manager supports G.722 negotiation for none, some, or all devices. Valid values specify Enabled for All Devices (support G.722 for all devices), Enabled for All Devices Except Recording-Enabled Devices (support G.722 for all devices except those that have call recording enabled), or Disabled (do not support G.722 codec).
For more information about the G.722 codec, see the "Using the G.722 Codec" section.
Using FTP to Upgrade to Cisco Unified Communications Manager Release 6.0(1b)
Even if enough disk space exists, if you upgrade to this release by using FTP, the upgrade might fail with an error message that states that not enough disk space exists to complete the upgrade.
If this happens, begin the upgrade again by using a different upgrade method (such as SFTP or LOCAL) or use different FTP server software.
Cisco Unified Personal Communicator LDAP Attribute Mappings
Be aware that Cisco Unified Personal Communicator LDAP attribute mappings are wrong for the Active Directory set of attribute mappings.
Before Cisco Unified Communications Manager Release 6.0(1), only one set of LDAP attribute mappings existed. In Cisco Unified Communications Manager Release 6.0(1), two sets of attribute mappings exist: for Netscape LDAP and for Active Directory LDAP. During an upgrade to this release, the default attribute mappings do not get correctly carried forward into the Cisco Unified Communications Manager Release 6.0(1) attribute mappings for Active Directory LDAP. (They correctly get carried forward for Netscape LDAP.)
This applies to default attribute mappings. Non-default attribute mappings (for example those explicitly specified by the user) properly get carried forward for both Netscape LDAP and Active Directory LDAP.
Before you upgrade to Cisco Unified Communications Manager Release 6.0(1b), make a note of the Cisco Unified Personal Communicator LDAP attribute mappings and enter the original values for the Active Directory set of attribute mappings
Terminal Server Causes RTMT to Display Repeating Syslog and Alert Messages
When a terminal server is connected to the serial port of a Cisco Unified Communications Manager server, the system generates a repeating alert message and corresponding syslog message similar to the following examples:
•Alert Message—SeverityMatch - Alert login(pam_unix)[12916]: check pass; user unknown
•Syslog Message—May 16 04:44:44 azo-cm-uc auth 5 mgetty[23127]: failed dev=ttyS0, pid=23127, login time out
This includes a router that is being used as a terminal server.
Cisco recommended that you configure no exec on the lines that are connected to the console of the other devices.
New and Changed Information in Cisco Unified Communications Manager Releases 6.0(1x)
The following sections describe new features and changes that are pertinent to Cisco Unified Communications Manager, Release 6.0(1a and below). The sections may include configuration tips for the administrator, information about users, and information about where to find more information.
No new and changed information exists specifically for Cisco Unified Communications Manager Release 6.0(1b).
•Trace Compression Support
•Basic Uninterruptible Power Supply (UPS) Integration
•HP NC-Series Broadcom Firmware Updates Available for Supported NICs.
•Smart Array 6i Requires HD Firmware Update to Avoid POST Notification
•CSCsj72914 Conference Calls Experience Poor Audio Quality
•CSCsj61395 Spurious Error Message Displays During Installation of Locale COP Files on a Subscriber Server
•CSCsj55359 Installation Media Cannot Locate Available Patches
•CSCsj42131 User with Incorrect Primary Extension in Directory Export
•CSCsj22669 User and User Profile Association Issue in Directory Export
•CSCsi71128 DMA Requires a Long Time to Run
•CSCsi20684 CSS Call Forward All
•Installation, Upgrade, Migration, and Disaster Recovery
•Cisco Unified Communications Operating System Administration
•Cisco Unified Communications Manager Administration
•Cisco Unified Communications Manager Features
•Cisco Unified Communications Manager Applications
•Cisco Unified Communications Manager Bulk Administration Features
•Cisco Unified Communications Manager Security Features
•Cisco Unified Serviceability
•Cisco Unified Communications Manager User Options Menu
•Cisco Unified IP Phones
•Cisco and Third-Party APIs
Trace Compression Support
This feature enables the ROS (Recoverable Outstream) library to support the compressed output of trace files. The files get compressed as they are being generated. The following benefits of trace file compression apply:
•Reduces the capacity that is required to store trace files.
•Reduces the disk head movement, which results in significantly improved call load. The CPU virtually never gets blocked due to trace file demands.
For more information, see Documentation Updates
Basic Uninterruptible Power Supply (UPS) Integration
When Cisco Unified Communications Manager 6.0(1a) runs on an MCS 7825H2 or MCS 7835H2, basic integration to the UPS model APC SmartUPS 1500VA USB and APC 750VA XL USB gets supported. Integration occurs via a single point-to-point Universal Serial Bus (USB) connection. Serial and SNMP connectivity to UPS does not get supported, and the USB connection must be point-to-point (in other words, no USB hubs). Single- and dual-USB UPS models get supported. The feature activates automatically during bootup if a connected UPS gets detected.
Alternatively, on MCS-7835H2, you can execute the show ups status CLI command to activate the feature (see "Command Line Interface Enhancements").
On supported servers, the CLI command also displays detected hardware, detected versions, current power draw, remaining battery runtime, and other relevant status information.
When the feature is activated, graceful shutdown will commence as soon as the low battery threshold is reached. Resumption or fluctuation of power will not interrupt or abort the shutdown.
For unsupported Cisco Unified Communications Manager releases, MCS models and/or UPS vendor/make/models, you can cause an external script to monitor the UPS. When low battery gets detected, you can log on to Cisco Unified Communications Manager by using Secure Shell (SSH), access the CLI, and execute the utils system shutdown command.
HP NC-Series Broadcom Firmware Updates Available for Supported NICs.
The upgrade includes
•iSCSI and UMP firmware upgrade support.
•An IPMI configuration command that allows IPMI to be enabled or disabled from the command line.
You can update firmware manually by downloading and booting from the HP Firmware Maintenance CD version 7.80 (10 May 07) that is located at http://h18023.www1.hp.com/support/files/server/us/download/27225.html
Smart Array 6i Requires HD Firmware Update to Avoid POST Notification
You should upgrade hard drive models that experience excessive SCSI command timeout. Failure to upgrade may result in the bus down-shifting from Ultra 320 to Ultra 3.
Upgrade following hard disk models to the specified versions:
Table 3 Recommended Firmware Upgrades
Hard Disk Model
|
Upgrade to
|
BF018863B8, BF036863B9, BF072863BA
|
HPB6 B (4 Jan 07
|
BD146863B3, BD072863B2, BD036863AC, BD03697633
|
HPB8 B (4 Jan 07
|
BD14686225, BD07286224, BD03686223, BD07296B44, BD03695CC8
|
HPB6 E (4 Jan 07)
|
BD009635CB, BD00973623, BD018635CC, BD01873624, BD03663622, BD03673625, BC072638A2
|
BDCB D (4 Jan 07)
|
BD01865CC4, BD01875CC7, BD00965CC3, BD00975CC6, BD00415CBC, BD00425CC2
|
HPB6 D (4 Jan 07)
|
BD0096349A, BD009734A3, BD0186349B, BD018734A4
|
3B15 D (4 Jan 07)
|
BD00962A66, BD00972A69, BD01862A67, BD01872A6A
|
B008 D (4 Jan 07)
|
BD00962373 BD00972374 BD01862376 BD01872377 and BC0367237A
|
BCJG D (4 Jan 07)
|
BD00912578 and BD01812579
|
BCJG D (18 Jan 07)
|
AD01836222, AD00935CCC, AD00435CCB
|
HPA6 C (16 Jan 07)
|
AD00933626 and AD01833627 drives version
|
ADCB D (4 Jan 07)
|
AD00932372 AD01832375 and AC03632378
|
ACJG D (4 Jan 07)
|
Workaround
You can update firmware manually by downloading and booting from the HP Firmware Maintenance CD version 7.80 (10 May 07) that is located at http://h18023.www1.hp.com/support/files/server/us/download/27225.html
CSCsj72914 Conference Calls Experience Poor Audio Quality
Conference calls that use the software media resources (MTP, MOH, and CFB) on a Cisco Unified CallManager 5.1(2) server experience poor audio quality when they traverse a WAN with QoS implemented.
Because the RTP that comes from Cisco Unified CallManager has a DSCP of 0x00, these packets get queued and/or dropped behind other voice signaling and RTP packets at the WAN router. Depending on network conditions for the WAN link, this can cause poor audio quality.
Current Condition
The release of Cisco Unified Communications Manager Release 6.0(1a) resolved this problem.
CSCsj61395 Spurious Error Message Displays During Installation of Locale COP Files on a Subscriber Server
Previously, when a user installed a locale COP file on a subscriber server, an error message displayed: "Status: Error Encountered."
Current Condition
The release of Cisco Unified Communications Manager Release 6.0(1a) resolved this problem.
CSCsj55359 Installation Media Cannot Locate Available Patches
The installation media does not find the available upgrade patches.
Workaround
The release of Cisco Unified Communications Manager Release 6.0(1a) resolved this problem.
CSCsj42131 User with Incorrect Primary Extension in Directory Export
Caveat
After migration from Cisco Unified CallManager Release 4.x to Cisco Unified CallManager Release 5.x, the user gets associated with the wrong primary extension.
Current Condition
The release of Data Migration Assistant 6.0(1a) and Cisco Unified Communications Manager resolved this problem.
CSCsj22669 User and User Profile Association Issue in Directory Export
Caveat
Multiple CNN-profiles per user exist in the Cisco Unified CallManager Release 4.x directory. After an upgrade to Cisco Unified Communications Manager 6.0(1), despite a clean DMA run, lost/missing/incorrect login profiles and device associations exist.
Current Condition
The release of Data Migration Assistant 6.0(1a) and Cisco Unified Communications Manager resolved this problem.
CSCsi71128 DMA Requires a Long Time to Run
Caveat
When users upgrade to Cisco Unified Communications Manager Release 6.x, from releases prior to release 4.1(3), DMA execution takes a very long time in the premigration phase. If this occurs, the users should wait for completion. A delay in this phase of up to 23 hours for 45,000 devices has occurred.
Current Condition
The release of Data Migration Assistant 6.0(1a) and Cisco Unified Communications Manager resolved this problem.
CSCsi20684 CSS Call Forward All
Caveat
DMA fails to validate when invalid contents exist in the CSSForCFA table:
Need exists for DMA processing to handle invalid CSS failures more efficiently.
Current Condition
The release of Data Migration Assistant 6.0(1a) and Cisco Unified Communications Manager resolved this problem.
Installation, Upgrade, Migration, and Disaster Recovery
The following sections describe the changes that were made to the installation, upgrade, and disaster recovery procedures in Cisco Unified Communications Manager 6.0(1):
•Installation Overview
•Software Upgrades
•Disaster Recovery System
•Where to Find More Information
Installation Overview
•In addition to installing Cisco Unified Communications Manager, the installation program supports installing Cisco Unity and Cisco Unified Communications Manager Business Edition.
•Now, you can specify the Application User account name during installation.
•You can generate preexisting configuration information that is required for an installation by using an online Answer File Generator (http://www.cisco.com/pcgi-bin/tablebuild.pl/callmgr-utilpage). You can use the resulting answer file rather than entering the configuration information manually during the installation procedure.
Software Upgrades
You can initiate and manage upgrades by using the utils system upgrade CLI command.
Disaster Recovery System
You can create up to 10 backup schedules. Each backup schedule has its own set of properties, including a schedule for automatic backups, the set of features to back up, and a storage location.
Where to Find More Information
•Disaster Recovery System Administration Guide
•Data Migration Assistant User Guide
•Upgrading Cisco Unified Communications Manager Release 6.0(1)
•Installing Cisco Unified Communications Manager Release 6.0(1)
•Cisco Unified Communications Operating System Administration Guide, Release 6.0(1)
Cisco Unified Communications Operating System Administration
For Cisco Unified Communications Manager 6.0(1), you can perform many common system administration functions through the Cisco Unified Communications Operating System.
This chapter comprises the following topics:
•Overview
•Browser Requirements
•Platform Status and Configuration Enhancements
•Restart Options Enhancements
•Security Configuration Enhancements
•Software Upgrades Enhancements
•Command Line Interface Enhancements
Overview
You cannot log in to Cisco Unified Communications Operating System and Cisco Unified Communications Manager Administration at the same time.
Browser Requirements
You can access Cisco Unified Communications Manager Administration, Cisco Unified Serviceability, and Cisco Unified Communications Operating System Administration by using the following browsers:
•Microsoft Internet Explorer version 6.x
•Netscape Navigator version 7.1
Note Cisco does not support or test other browsers, such as Mozilla Firefox.
Platform Status and Configuration Enhancements
This release removed the Logs item from the Show menu.
Settings Enhancements
This release added the Version item to the Settings menu.
Restart Options Enhancements
The system restart and version switching features moved from a System Restart menu to the Settings > Version window.
Security Configuration Enhancements
The reorganized security features and the Security menu moved all certificate management features to the Security > Certificate Management window. All IPSec management features moved to the Security > IPSec Management window.
Software Upgrades Enhancements
This release provides the following updates:
•You can initiate and manage upgrades by using the utils system upgrade CLI command.
•The upgrade file that you use to upgrade from a 6.x release to a later 6.x release now exists as an ISO image file. Previously, the upgrade file had a different file format.
•You can delete files from the TFTP server.
Command Line Interface Enhancements
This release adds the following CLI commands:
•utils system upgrade—Allows you to initiate and manage upgrade server upgrades.
•show tech dbstateinfo—Shows the state of the database.
•show tech dbintegrity—Shows the integrity of the database.
•show tech prefs—Displays database settings.
•utils fior—Monitors I/O on the server.
•show ups—Shows the current status of the USB-connected APC smart-UPS device and starts the monitoring service if it is not already started.
•show environment—Displays information about the server hardware.
•show memory—Displays information about the server memory.
Where to Find More Information
•Cisco Unified Communications Operating System Administration Guide
Cisco Unified Communications Manager Administration
The following sections describe the Cisco Unified Communications Manager Administration enhancements:
•System Architecture Changes
•General Administration Enhancements
•Navigating to IP Telephony Applications Within Cisco Unified Communications Manager Enhancements
•Localizing Cisco Unified Communications Manager Administration
•Migration Tips
•General Changes That Were Made to Multiple Windows
•Service Parameter Changes
•Enterprise Parameter Changes
•Locations and Region Enhancements
•System Menu Changes
•Call Routing Menu Changes
•Media Resources Menu
•Voice Mail Menu
•Device Menu Changes
•Application Menu Changes
•User Management Menu
•Bulk Administration Menu
•Where to Find More Information
System Architecture Changes
Cisco Unified Communications Manager Administration, Release 6.0 introduces the following changes to the way the database behaves during installation or upgrade:
•Enhancements to the database CLI command, show tech dbstateinfo, show active SQL statements and which process is executing them.
•The database no longer uses "CCMAdministrator" as a default super userid for administration during installation. Instead, the installation process asks for the user ID of the administrator. You should use this new userid when you are logging in to Cisco Unified Communications Manager Administration for the first time on fresh installations.
•Information from the installation framework to fit the topology that is being installed provides basis for the Cisco Unified Communications Manager database that is now conditionally sized. It provides four different sizes:
–Super cluster
–Normal (30K phones)
–Cisco Unified Communications Manager Business Edition (500 phones)
–Serviceability support (100 phones)—For standalone Unity Connection
•When a software upgrade from Cisco Unified Communications Operating System Administration from 5.x and beyond is performed, changes that are made during the upgrade for user-facing features will no longer get lost. This includes updates for the following features:
–Call Forward All (CFA)
–Message Waiting Indicator (MWI)
–Privacy Enable/Disable
–Do Not Disturb (DND) Enable/Disable
–Extension Mobility (EM) Login
–Log Out of Hunt Group
–Device Mobility
–CTI CAPF status for end users and application users
–Credential hacking and authentication
Note Upgrades from 4.x to 6.x require that the user log out and then log back in.
•Replication alarms and perfmon counters have meaning on subscribers servers as well as the publisher server.
•Loss of connectivity to the publisher server will not prohibit the setting of call-processing user-facing features such as call forward and message waiting indicator. This means that you can forward your phone or log in by using extension mobility even when the publisher server is not accessible.
Change notification will queue up as replication queues up and proceed as replication proceeds. This should alleviate previous anomalous behavior on subscriber servers that have experienced a time during which the publisher server was not available, and services on the subscriber servers did not receive one or more change notification events from the publisher server.
General Administration Enhancements
Cisco Unified Communications Manager Administration Release 6.0 supports JSPs, STRUTS framework, and Java. The following requirements apply to Cisco Unified Communications Manager Administration:
•Microsoft Internet Explorer (IE) 6.0
•Netscape 7.1
Note This release does not support Microsoft IE 5.5 and Netscape 7.0.
Navigating to IP Telephony Applications Within Cisco Unified Communications Manager Enhancements
After you log on, the main Cisco Unified Communications Manager Administration window redisplays. The window includes the drop-down list box, called Navigation, in the upper, right corner. To access the applications in the drop-down list box, choose the program that you want and click Go. The choices in the drop-down list box include the following Cisco Unified Communications Manager applications:
•Cisco Unified Communications Manager Administration—Shows the default when you access Cisco Unified Communications Manager. Use Cisco Unified Communications Manager Administration to configure system parameters, route plans, devices, and much more.
•Cisco Unified Serviceability—Takes you to the main Cisco Unified Serviceability window that is used to configure trace files and alarms and to activate and deactivate services.
•Cisco Unified OS Administration—Takes you to main Cisco Unified OS Administration window, so you can configure and administer the Cisco Unified Communications Manager platform. You must log off from any other application before you can log in to this application.
•Cisco Unity Connection Administration—Takes you to the main Cisco Unity Connection Administration window to configure voice messaging, integrated messaging, speech recognition capabilities, and call-routing rules. This menu option applies only to Cisco Unified Communications Manager Business Edition systems.
•Cisco Unity Connection Serviceability—Takes you to the main Cisco Unity Connection Serviceability window to configure trace files and alarms and to activate and deactivate services for Cisco Unity Connection. This menu option applies only to Cisco Unified Communications Manager Business Edition systems.
•Disaster Recovery System—Takes you to the Cisco Disaster Recovery System, a program that provides full data backup and restore capabilities for all servers in a Cisco Unified Communications Manager cluster. You must log off from any other application before you can log in to this application.
After you log in to Cisco Unified Communications Manager Administration, you can access all applications that display in the Navigation drop-down list box, except for the Cisco Unified Communications Operating System Administration and Disaster Recovery System, without having to log in to each application. You cannot access the Cisco Unified Communications Operating System Administration or Disaster Recovery System GUIs with the same username and password that you use to access Cisco Unified Communications Manager Administration. To access these applications from Cisco Unified Communications Manager Administration, you must first click the Logout button in the upper, right corner of the Cisco Unified Communications Manager Administration window; then, choose the application from the Navigation drop-down list box and click Go.
If you have already logged in to one of the applications that display in the Navigation drop-down list box (other than Cisco Unified Communications Operating System Administration or Disaster Recovery System), you can access Cisco Unified Communications Manager Administration without logging in. From the Navigation drop-down list box, choose Cisco Unified Communications Manager Administration and click Go.
Where to Find More Information
•Introduction, Cisco Unified CallManager Administration Guide
Localizing Cisco Unified Communications Manager Administration
Cisco Unified Communications Manager Release 6.0 incorporates the following localization capabilities:
•End User Configuration windows get localized. Other configuration windows that share the End User Configuration get localized.
•To see the localization, set the browser to the language that is required. If that language locale is loaded, the localized configuration windows will display.
Migration Tips
Cisco Unified Communications Manager Assistant
Cisco Unified Communications Manager supports up to 3500 managers and 3500 assistants for a total of 7000 users. To support 7000 users, the administrator must configure multiple active Cisco IP Manager Assistant servers by enabling and setting service parameters. Administrators can configure up to three active Cisco IP Manager Assistant servers, each managing up to 2500 managers and assistants. Each server can also have a backup server. Configure the Cisco IP Manager Assistant servers by using the Advanced Service Parameters, Enable Multiple Active Mode, Pool 2: Cisco IPMA Server, and Pool 3: Cisco IPMA Server. If you are migrating from a release prior to Cisco Unified Communications Manager Release 6.0(1), all managers and assistants will get migrated to Pool 1 (the default).
Check Box to User Group
The following check boxes in Cisco Unified Communications Manager Administration get migrated to user groups when you upgrade from Release 4.2 to Release 6.0.
Check Box Name in Releases Before 5.0
|
Functionality Migrated to This User Group
|
Enable Computer Telephony Integration (CTI) Application Use
|
Standard CTI Enabled
|
Enable CTI Super Provider
|
Standard CTI Allow Control of All Devices
|
Enable Calling Party Number Modification
|
Standard CTI Allow Calling Number Modification
|
Call Park Retrieval Allowed
|
Standard CTI Allow Call Park Monitoring
|
General Changes That Were Made to Multiple Windows
You can find the following changes on multiple Cisco Unified Communications Manager Administration windows:
•Clear Filter and + and - buttons—Found on the Find/List windows. To add additional search criteria click the + button. When you add criteria, the system searches for a record that matches all criteria that you specify. To remove criteria, click the - button to remove the last added criteria or click the Clear Filter button to remove all added search criteria.
•Device Pool—Used by many configuration windows for certain configuration details (for example, date/time group). Release 6.0 removed some fields from the device pool and added them to the common device configuration, so some configuration windows will need to include information about device pools and common device configurations for certain configuration details (for example, softkey templates).
•Common Device Configuration—A new configuration window that provides information about softkey templates, MOH, and MLPP. This common device configuration gets assigned to phones in the Phone Configuration window.
Service Parameter Changes
Cisco Unified Communications Manager 6.0 supports the following service parameter changes:
•Advance Ad Hoc Conference Enabled (introduced in Release 4.2(3))
•Nonlinear Ad Hoc Conference Linking Enabled (introduced in Release 4.2(3))
•Always Display Original Dialed Number (introduced in Release 4.2(3))
•Call Diagnostics Enabled (introduced in Release 4.2(1))
•Hold Reversion Duration Timer (introduced in Release 4.2(3))
•Hold Reversion Notification Interval (introduced in Release 4.2(3))
•Overlap Receiving Flag for H.323 (introduced in Release 4.2(1))
•Hunt Group Logoff Notification (introduced in Release 4.2(1))
•Enforce Privacy Setting on Held Calls (introduced in Release 4.2(1))
•Bundle Outbound SCCP Messages Timer (introduced in Release 4.2(3))
•Play Recording Notification Tone To Observed Target (introduced in Release 6.0(1))
•Play Recording Notification Tone To Observed Connected Parties (introduced in Release 6.0(1))
•Play Monitoring Notification Tone To Observed Target (introduced in Release 6.0(1)
•Play Monitoring Notification Tone To Observed Connected Parties (introduced in Release 6.0(1))
•Enable/Disable Multiple Active Mode
•Pool 2: Cisco IPMA Server (Primary) IP Address
•Pool 2: Cisco IPMA Server (Backup) IP Address
•Pool 3: Cisco IPMA Server (Primary) IP Address
•Pool 3: Cisco IPMA Server (Backup) IP Address
•CUP PUBLISH Trunk
•Default PUBLISH Expiration Timer
•Minimum PUBLISH Expiration Timer
•Retry Count for SIP Publish
•SIP Publish Timer
•BLF Status Depicts DND
•G722 Codec Enabled
•iLBC Codec Enabled
•Built-in Bridge Enable
•Maximum Concurrent Requests Now an Advanced Service Parameter
•Delay Before Ringing Cell Phone Timer
•Answer Too Late Timer (also known as Maximum Cell Phone Ring Timer)
•Answer Too Soon Timer (also known as Minimum Cell Phone Ring Timer)
•CFA CSS Activation Policy
•Maximum Number of Threads and Process
•SIP Station UDP Port Throttle Threshold
•SIP Trunk UDP Port Throttle Threshold
Enterprise Parameter Changes
Cisco Unified Communications Manager 6.0 supports the following enterprise parameter changes:
•Phone Personalization
•Enable Caching
Locations and Region Enhancements
Cisco Unified Communications Manager supports up to 1000 locations and up to 2000 regions. The following limitations and restrictions apply:
•Configure as many regions as possible to Use System Default for inter- intra-region audio codecs and video bandwidth.
•Configure as many locations as possible to Use System Default for the RSVP policy.
This enhancement requires an MCS 7845H1 or higher server.
System Menu Changes
The following changes occurred in the System menu:
•Device Pool—Field changes
•Device Mobility (New)—Submenus
–Device Mobility Group
–Device Mobility Info
•Physical Location (New)
•Application server—New fields
Call Routing Menu Changes
The following changes occurred in the Call Routing menu:
•Intercom (New)
–Intercom Route Partition
–Intercom Calling Search Space
–Intercom Directory Number
–Intercom Translation Pattern
•Directed Call Park (new)
•Directory Number
–New Calling Search Space Activation Policy field
•Meet-Me Number/Pattern
–Minimum Security Level (new field)
•Transformation Pattern (new)
•Mobility Configuration (new)
Media Resources Menu
The following changes occurred in the Media Resources menu:
•Mobile Voice Access (new)
•Conference Bridge
–Common Device Configuration (new field)
–Cisco IOS Enhanced Conference Bridge contains new field: Device Security Mode, which supports encrypted and nonsecure bridges.
Voice Mail Menu
No changes occurred to the Voice Mail menu.
Device Menu Changes
The following changes occurred in the Device menu:
•Phone
–New device types 7921, 7931, and 3951 (not available to North American and European markets)
–Common Device Configuration (new)
–Device Mobility Mode (new)
–Phone Personalization (new)
–Primary Phone (new)
–Logged Into Hunt Group (new)
–Remote Device (new)
–Do Not Disturb (new)
–Mobility User ID (Dual-mode phones only) (new)
–Outbound Call Rollover (new)
–Actively Logged in Device Report (new)—Access this window from the Related Links drop-down list box on the Find and List Phones window.
–Association Information Line configuration— Two new fields on the Directory Number Configuration window: Recording Option and Recording Profile
•Remote Destination (new)
•Device > Device Settings
–Common Device Configuration (new)
–Access List (new)
–Common Phone Profile (updated)—DND and Phone Personalization
–Remote Destination Profile (new)
–Recording Profile (new)
Application Menu Changes
No changes.
User Management Menu
The following changes occurred in the User Management menu:
•Credential Policy Default (new)
•Credential Policy (new)
•Application User
–Edit Credential (new field)
•End User Configuration
–Edit Credential (new field)
Bulk Administration Menu
Bulk Administration contains the following new menu items in Release 6.0:
•Phones > Add/Update Intercom (new)
•Users
–Line Appearance (new)
–Reset Password/PIN (new). Contains two menus for Query and Custom File.
•Gateways > Insert Gateways (now supports Cisco VG 224)
•Gateways > Gateway File Format (new)
•Mobility (new)
–Access List (new)
–Remote Destination (new)
–Remote Destination Profile (new)
•Config Tool (new)
For more information about the Bulk Administration application, see Cisco Unified Communications Manager Bulk Administration Features.
Where to Find More Information
•Cisco Unified Communications Manager Bulk Administration Guide
•Cisco Unified Communications Manager Administration Guide
•Cisco Unified Communications Manager Features and Services Guide
•Cisco Unified Communications Manager System Guide
•Cisco Unified Communications Manager Security Guide
Cisco Unified Communications Manager Features
The following sections describe the Cisco Unified Communications Manager 6.0 feature enhancements:
•AAC/iLBC Voice Codec Support
•Advanced Ad Hoc Conference
•Audible Message Waiting Indicator
•Barge Enhancements
•Call Diagnostics and Voice Quality Metrics
•Call Forward Enhancements
•Call Forward All Calling Search Space Backward Compatibility
•Call Forward Overriding
•Call Pickup Notification
•Cisco Messaging Interface Enhancements
•Cisco Unified Communications Manager T1 CAS Hookflash Transfer Support
•Connected Number Display
•Credential Policy and User Authentication
•CTI Enhancements
•Device Mobility
•Directed Call Park
•Do Not Disturb
•Hold Reversion
•Intercom
•Licensing Enhancements
•Log Out of Hunt Groups
•Overlap Sending and Receiving for H.323 Gateways
•MGCP T.38 Enhancements
•Privacy on Hold
•Programmable Line Keys
•SCCP Optimization
•SDL Traces
•SIP Endpoints Support
•Third-Party Phones Enhancements for Phones That Are Using SIP
•SIP Trunk Enhancements
AAC/iLBC Voice Codec Support
Release 5.1(1) of Cisco Unified CallManager added support for the Advanced Audio Codec (AAC) and the Internet Low Bit Rate Codec (iLBC), but without any changes to the user interface. Release 6.0(1) of Cisco Unified Communications Administration added the AAC and iLBC audio codecs to the user interface.
The Advanced Audio Codec (AAC) specifies a wideband voice codec that provides improved voice fidelity. This codec also provides equal or improved sound quality over older codecs with lower bit rates. SIP supports use of the AAC as an audio codec. Use the AAC audio codec for calls between phones that are running SIP.
The Internet Low Bit Rate Codec (iLBC) enables graceful speech quality degradation in a lossy network where frames get lost. Be aware that the iLBC is suitable for real-time communications, such as telephony and video conferencing, streaming audio, archival, and messaging.The iLBC has good error resilience character in a lossy network. When a link in the network has a high error rate, the administrator can configure the region pair as lossy, which in turn enables selection of iLBC for that link if iLBC is configured. SIP, SCCP, and MGCP support use of the iLBC as an audio codec.
When you assign the SIP trunk or third-party phone that is running SIP with the MTP Required option that is enabled to the device pool for that region, you must verify that the region relationship between the SIP device and the MTP device is configured to use a codec with equal or greater bandwidth (G.711 or Wideband/AAC codec). See the "Third-Party Phones Enhancements for Phones That Are Using SIP" section and the "SIP Trunk Enhancements" section for more information.
Cisco Unified Communications Manager Administration Configuration Tips
The following configuration tips apply to the AAC and iLBC audio codecs:
•To specify the AAC audio codec, configure the Wideband/AAC codec in the Region Configuration window of Cisco Unified Communications Manager Administration.
•To specify the iLBC audio codec, configure the G.728/iLBC codec in the Region Configuration window of Cisco Unified Communications Manager Administration.
GUI Changes
In Release 6.0(1) of Cisco Unified Communications Manager Administration, the Region Configuration window adds the AAC and iLBC audio codecs to the list of audio codecs that can be configured. In Release 5.1(1), the administrator needed to choose the G.728 codec (for iLBC) and Wideband codec (for AAC).
Where to Find More Information
•System-Level Configuration Settings, Cisco Unified Communications Manager System Guide
•Understanding Session Initiation Protocol (SIP), Cisco Unified Communications Manager System Guide
•Region Configuration, Cisco Unified Communications Manager Administration Guide
Advanced Ad Hoc Conference
Cisco Unified CallManager Release 4.2(3) made enhancements to the ad hoc conference feature and provided the following advanced capabilities in Release 6.0:
•A conference participant other than the controller can now add or remove participants.
•Conference participants can now chain multiple ad hoc conferences together in linear or nonlinear fashion.
•You can enable or disable these advanced capabilities by setting the value of two new service parameters (see Service Parameter Changes).
When multiple conferences are chained together, all the participants can hear and talk to each other; however, the ConfList softkey does not display a full list of all the participants in all the chained conferences. ConfList can only display the participants in its own conference and displays a linked conference as "Conference." The conferences do not get merged into a single conference.
Where to Find More Information
•Cisco Unified Communications Manager Administration Guide
•Cisco Unified Communications Manager System Guide
•Cisco Unified Communications Manager CDR Analysis and Reporting Administration Guide
•Cisco Unified IP Phone User Guides
•Release Notes for Cisco Unified CallManager Release 4.2(3)
Audible Message Waiting Indicator
Audible MWI, an accessibility feature, notifies visually impaired users of voice messages. When a voice message occurs on a line and the user goes off hook on that line, the phone plays a stutter dial tone to indicate the presence of voice message.
For non-visually impaired users, audible MWI provides a redundant indication of voice messages.
Cisco Unified Communications Manager Administration Configuration Tips
Use Directory Number Configuration to set the Audible Message Waiting Indicator Policy. This field configures an audible message waiting indicator policy for a line on the phone.
GUI Changes
New Audible Message Waiting Indicator Policy field displays on the Directory Number Configuration window. This field offers the following configurable settings:
•Off
•On—When this option is chosen, you will receive a stutter dial tone when you take the handset off hook.
•Default—When this option is chosen, the phone uses the default that was set from the Audible Message Waiting Indicator Policy clusterwide service parameter. This service parameter offers the following settings:
–Off
–On
BAT Considerations
The Line Template Configuration window in BAT contains the Audible Message Waiting Indicator Policy field.
Where to Find More Information
•Directory Number Configuration, Cisco Unified Communications Manager Administration Guide
•Cisco Unified IP Phone Configuration, Cisco Unified Communications Manager Administration Guide
•Cisco Unified IP Phone, Cisco Unified Communications Manager System Guide
Barge Enhancements
Nonsecure or authenticated Cisco Unified IP Phones that are running firmware release 8.3 or later can now barge encrypted calls.The security icon indicates the security status for the conference. (See the "Secure Conference Icon" section.)
•Due to bandwidth requirements, Cisco Unified IP Phones 7940 and 7960 do not support barge from an encrypted device on an active encrypted call. The barge attempt will fail. A tone plays on the initiator phone to indicate that the barge failed.
•Encrypted Cisco Unified IP Phones that are running firmware release 8.2 or earlier can only barge an active call as authenticated or nonsecure participants.
•If a caller barges a secure SCCP call, the system uses an internal tone-playing mechanism at the target device, and the status remains secure.
•If a caller barges a secure SIP call, the system provides tone-on-hold, and Cisco Unified Communications Manager classifies the call as nonsecure during the tone.
Cisco Unified Communications Manager Administration Configuration Tips
To secure conferences with barge, configure phones to use encrypted mode.
Where to Find More Information
•Barge and Privacy Release, Cisco Unified Communications Manager Features and Services Guide
•Cisco Unified Communications Manager Security Guide
•Cisco Unified Communications Manager Troubleshooting Guide
Call Diagnostics and Voice Quality Metrics
Cisco Unified CallManager Release 4.2(1) allowed you to configure Cisco Unified IP Phones to collect call diagnostics and voice quality metrics by setting the Call Diagnostics Enabled service parameter to True in Cisco Unified Communications Manager Administration. You can access the metrics to monitor voice quality and troubleshoot network problems. The Call Statistics screen on the phone displays counters, statistics, and voice quality metrics in the following ways:
•During call—You can view the call information by pressing the ? button twice rapidly.
•After the call—You can view the call information that was captured during the last call by displaying the Call Statistics screen
Note You can remotely view the call statistics information by using a web browser to access the Streaming Statistics window.
To measure the voice quality of calls that are sent and received within the network, Cisco Unified IP Phones use statistical metrics that are based on concealment events.
To use the metrics for monitoring voice quality, record the typical scores under normal conditions of zero packet loss and use the metrics as a baseline for comparison.
Where to Find More Information
•Troubleshooting Cisco Unified IP Phones, Cisco Unified IP Phone Administration Guides
•Cisco Unified IP Phones, Cisco Unified Communications Manager System Guide
•Release Notes for Cisco Unified CallManager Release 4.2(1)
Call Forward Enhancements
Cisco Unified CallManager Release 4.2(1) made the following enhancements to the forwarding and Automated Alternate Routing (AAR) logic to redirect calls that cannot be connected due to no bandwidth or an unregistered directory number:
•No Bandwidth
This enhancement applies AAR treatment to calls that are blocked due to insufficient bandwidth by using the AAR Settings fields (AAR Destination Mask, AAR Voicemail Enabled).
•Unregistered Phone
This enhancement forwards calls that are routed to a directory number with no registered devices.
Where to Find More Information
•Cisco Unified IP Phones, Cisco Unified Communications Manager System Guide
•Release Notes for Cisco Unified CallManager Release 4.2(1)
Call Forward All Calling Search Space Backward Compatibility
This enhancement allows Cisco Unified CallManager Release 4.x customers who are using device mobility and extension mobility to upgrade to Cisco Unified Communications Manager Release 6.0 without loss of functionality.
In the Directory Number Configuration window, in the Call Forward and Call Pickup Setting section, a new option specifies Calling Search Space Activation Policy.
Three possible values exist for this option:
•Use System Default
•With Configured CSS
•With Activating Device/Line CSS
If you select the With Configured CSS option, the Forward All Calling Search Space that is explicitly configured in the Directory Number Configuration window controls the forward all activation and call forwarding. If the Forward All Calling Search Space is set to None, no CSS gets configured for Forward All. A forward all activation attempt to any directory number with a partition will fail. No change in the Forward All Calling Search Space and Secondary Calling Search Space for Forward All occurs during the forward all activation.
If you prefer to utilize the combination of the Directory Number Calling Search Space and Device Calling Search Space without explicitly configuring a Forward All Calling Search Space, select With Activating Device/Line CSS for the Calling Search Space Activation Policy. With this option, when Forward All is activated from the phone, the Forward All Calling Search Space and Secondary Calling Search Space for Forward All automatically get populated with the Directory Number Calling Search Space and Device Calling Search Space for the activating device.
With this configuration (Calling Search Space Activation Policy set to With Activating Device/Line), if the Forward All Calling Search Space is set to None, when forward all is activated through the phone, the combination of Directory Number Calling Search Space and activating Device Calling Search Space gets used to verify the forward all attempt.
If you configure the Calling Search Space Activation Policy to Use System Default, the CFA CSS Activation Policy clusterwide service parameter determines which Forward All Calling Search space will be used. If the CFA CSS Activation Policy service parameter gets set to With Configured CSS, Forward All Calling Search Space and Secondary Calling Search Space for Forward All will get used for Call Forwarding. If CFA CSS Activation Policy service parameter gets set to With Activating Device/Line CSS, Forward All Calling Search Space and Secondary Calling Search Space for Forward All automatically will get populated with the Directory Number Calling Search Space and Device Calling Search Space for the activating device.
CFA CSS Activation Policy Service Parameter
The new service parameter (CFA CSS Activation Policy) supports this enhancement. In the Service Parameter Configuration window, this parameter displays in the Clusterwide Parameters (Feature - Forward) section:
•With Configured CSS (default)
•With Activating Device/Line CSS
When the Calling Search Space Activation Policy is set to Use System Default, the value of the CFA CSS Activation Policy service parameter determines the Call Forward All CSS.
When the option With Configured CSS is selected, the primary and secondary CFA Calling Search Space get used. When the option With Activating Device/Line CSS is selected, the primary and secondary CFA Calling Search Space get updated with primary line Calling Search Space and activating Device Calling Search Space.
By default, the system sets the value of the CFA CSS Activation Policy service parameter to With Configured CSS.
Roaming
When a device is roaming in the same device mobility group, Cisco Unified Communications Manager uses the Device Mobility CSS to reach the local gateway. If a user sets Call Forward All at the phone, the system sets CFA CSS to None, and the CFA CSS Activation Policy gets set to With Activating Device/Line CSS; then,
•The Device CSS and Line CSS get used as the CFA CSS when the device is in its home location.
•If the device is roaming within the same device mobility group, the Device Mobility CSS from the Roaming Device Pool and the Line CSS get used as the CFA CSS.
•If the device is roaming within a different device mobility group, the Device CSS and Line CSS get used as the CFA CSS.
For more information about configuration options for Call Forward All, see the Directory Number Configuration chapter in the Cisco Unified Communications Manager Administration Guide and the Understanding Directory Numbers chapter in the Cisco Unified Communications Manager System Guide.
Call Forward Overriding
Configure the behavior of this Cisco Unified Communications Manager feature, which was introduced in Release 4.2(3), by using the service parameter, CFA Destination Override. When the feature is enabled on Cisco Unified Communications Manager, it allows the CFA Target to reach the CFA Initiator for important calls. TSP applications that monitor the CFA initiator will receive calls as normal if the call is initiated from the CFA target.
No TSP interface change exists for this Cisco Unified Communications Manager feature.
Where to Find More Information
•Cisco Unified IP Phones, Cisco Unified Communications Manager System Guide
•Release Notes for Cisco Unified CallManager Release 4.2(3)
Call Pickup Notification
This feature allows users to receive an audio and/or visual alert when a call rings on a phone in pickup groups in which they are a member. For multiple line phones, the alert applies for pickup groups that are associated with the primary line only.
You can configure the following notification parameters in the Call Pickup Group Configuration window:
•Type of notification (audio, visual, both, or neither)
•Content of the visual notification message (called party identification, calling party identification, both, or neither)
•Number of seconds delay between the time the call comes into the original called party and the notification to the rest of the call pickup group members
You can configure the type of call pickup group audio notification that is provided for a line when a phone is idle or active by choosing the line in the Phone Configuration window.
Where to Find More Information
•Call Pickup Group, Cisco Unified Communications Manager Features and Services Guide
•Directory Number Configuration Settings, Cisco Unified Communications Manager Administration
•Advanced Call Handling, phone user guides
Cisco Messaging Interface Enhancements
The Cisco Messaging Interface (CMI) allows you to connect a simplified message desk interface (SMDI)-compliant external voice-messaging system with the Cisco Unified Communications Manager. The CMI service provides the communication between a voice-messaging system and Cisco Unified Communications Manager. The SMDI defines a way for a phone system to provide a voice-messaging system with the information that is needed to intelligently process incoming calls.
Introduced in Cisco Unified CallManager Release 4.2(1), you can now configure the CMI service parameters to define an alternate directory number and partition to be used when a non voice mail pilot number is dialed.
Note Users who have additional applications that are running on the voice-messaging system that require SMDI can configure the additional directory number (alternate DN). CMI will intercept all calls to this DN and generate an SMDI message over the serial cable to the server that is running the additional application. You make the partition for the alternate DN relevant online if you specify the alternate DN.
Where to Find More Information
•SMDI Voice Mail Integration, Cisco Unified Communications Manager System Guide
Cisco Unified Communications Manager T1 CAS Hookflash Transfer Support
Hookflash transfer defines a signaling procedure that allows a device, such as a voice-messaging system, to transfer a call to another destination. While the device is connected to Cisco Unified Communications Manager through a T1 CAS gateway, the device performs a hookflash procedure to perform the call transfer. Cisco Unified Communications Manager responds to the hookflash procedure by using a blind transfer to move the call. When the call transfer completes, the voice channel that connected the original call to the device gets released.
Cisco Unified CallManager Release 4.2(1) introduced the hookflash transfer on the T1 CAS ports of all Media Gateway Control Protocol (MGCP) gateways (both IOS and non-IOS gateways).
Where to Find More Information
•Understanding Cisco Unified Communications Manager Voice Gateways, Cisco Unified Communications Manager System Guide. (This chapter contains a summary of gateway model information. Every model that lists the T1 CAS port type supports hookflash transfer on those ports.)
Connected Number Display
When a call routes through a translation or route pattern, routes to a Call Forward All or Call Forward Busy destination, or gets redirected through a call transfer or CTI application, the connected number display updates to show the modified number or redirected number.
The Connected Number Display restriction restricts the connected line ID presentation to dialed digits only for the duration of the call.
Where to Find More Information
•Call Display Restrictions, Cisco Unified Communications Manager Features and Services Guide
•Release Notes for Cisco Unified CallManager Release 4.2(3)
Credential Policy and User Authentication
Cisco Unified Communications Manager authenticates user login credentials before allowing system access. To help secure user accounts, administrators can now specify settings for failed logon attempts, lockout durations, password expirations, and password requirements in Cisco Unified Communications Manager Administration. These authentication rules form a credential policy.
Credential policies apply to application users and end users. At installation, Cisco Unified Communications Manager assigns the system Default Credential Policy to end user passwords, end user PINS, and application user passwords.
Cisco Unified Communications Manager does not provide default credentials. At installation, the system applies the application password that you configured at installation to all application users.
•Upgrades from 5.x releases automatically migrate end user passwords and PINs.
•Upgrades from 4.x releases assign a default password and PIN to end users during installation
If you enable the trivial credential checks setting in the applied policy, the system disallows credentials that are easily hacked.
You can assign new credential policies and new credentials after installation for account groups or individual users. When you add a new user to the Cisco Unified Communications Manager database, the system assigns the default policy. You can change the assigned policy, user credentials, and manage user authentication events in Cisco Unified Communications Manager Administration.
Credential policies do not apply to OS users or CLI users. These administrators use standard password verification procedures that the OS supports.
Credential policy settings in Cisco Unified Communications Manager Administration do not apply if your system uses LDAP authentication.
The authentication function in Cisco Unified Communications Manager authenticates users, updates credential information, tracks and logs user events and errors, records credential change histories, and encodes/decodes or encrypts/decrypts user credentials for data storage.
Because Cisco Unified Communications Manager Java Telephony Applications Programming Interface (JTAPI) and Telephony Applications Programming Interface (TAPI) support the credential policies that are assigned to application users, developers must create applications that react to the password expiration, PIN expiration, and lockout return codes for credential policy enforcement.
Cisco Unified Communications Manager Administration Tips
The credential policy settings define the parameters that Cisco Unified Communications Manager uses during the authentication process:
•You define credential policies with the Credential Policy window (User Management > Credential Policy).
•You assign policies to groups in the Credential Policy Default window (User management > Credential Policy Default).
•You can change or view credential information for application and end users in the Credential Configuration window, which you access with the Edit Credential button in the user configuration window (User Management > End User and User Management > Application User).
Enterprise Parameter Changes
•To improve performance, administrators can configure the enterprise parameter "Enable Caching" to True. This eliminates the need for Cisco Unified Communications Manager to perform a database lookup or invoke a stored procedure for every single login request, thereby increasing system efficiency. An associated credential policy does not get enforced until the caching duration expires.
This setting applies to all Java applications that invoke user authentication. The system ignores this setting for LDAP authentication.
Where to Find More Information
•Credential Policy, Cisco Unified Communications Manager System Guide
•Application User Configuration, Cisco Unified Communications Manager Administration Guide
•Credential Policy Default Configuration, Cisco Unified Communications Manager Administration Guide
•Credential Policy Configuration, Cisco Unified Communications Manager Administration Guide
•End User Configuration, Cisco Unified Communications Manager Administration Guide
CTI Enhancements
CTI enhancements support new functionality in Release 6.0:
•New Standard CTI user groups for monitor and record
•Expanded SIP support (see the "SIP Endpoints Support" section). Line-side SIP includes CTI functionality, which allows CTI applications such as Cisco Unified Communications Manager Assistant to support SIP on Cisco Unified IP Phones (for example, Cisco Unified IP Phone 7961). Be aware that CTI capabilities on phones that are running SIP are equivalent to those on phones that are using SCCP with a few exceptions. Some CTI features that are supported on phones that are running SIP include display text, set lamp, play tone, call park, and privacy support.
•Support for mobility and device mobility
Cisco Unified Communications Manager Administration Configuration Tips
Following are Cisco Unified Communications Manager configuration tips.
•If a CTI application monitors calls, you must add the application to the Standard CTI Allow Call Monitoring user group. If the CTI application records calls, you must add the application to the Standard CTI Allow Call Recording user group.
•If a user will be call monitoring or call recording, you must add the end user to the Standard CTI Allow Call Monitoring and Standard CTI Allow Call Recording user groups.
•If you are using CTI ports with mobility or device mobility, configure the appropriate fields on the CTI Port Configuration window.
GUI Changes
The following comprise the GUI changes contained in this release.
•Standard CTI Allow Call Monitoring—This user group allows an application to monitor calls. Choose User Management > User Group and click Find.
•Standard CTI Allow Call Recording—This user group allows an application to record calls. Choose User Management > User Group and click Find.
•CTI Port—The CTI Port Configuration window includes new fields, check boxes, and Related Links:
–Common Device Configuration
–Device Mobility Mode
–Logged Into Hunt Group
–Remote Device
–Add a New Line Appearance
–Copy to Remote Destination Profile
–Add a new intercom
Where to Find More Information
•Computer Telephony Integration, Cisco Unified Communications Manager System Guide
•Understanding Session Initiation Protocol, Cisco Unified Communications Manager System Guide
•Cisco Unified Communications Manager Features and Services Guide
•Cisco Unified Communications Manager JTAPI Developer Guide
•Cisco Unified Communications Manager TAPI Developer Guide
Device Mobility
Cisco Unified Communications Manager uses IP subnets and device pools that contain location information to determine a device home location. By linking IP subnets to locations, the system can determine whether a device is at its home location or a remote location and register the device accordingly.
To support device mobility, modifications to the device pool structure separate the user information from the location and mobility information. Introduced in Cisco Unified CallManager Release 4.2(1), the device pool now contains the information that pertains to the device itself and to device mobility. An added common device profile allows you to configure all the user-related information. You must associate each device with the common device profile for user-based information.
Note Device pools that were already configured automatically migrate to the new structure as part of the upgrade to Cisco Unified Communications Manager Release 6.0(1).
In addition to the device pool and common device profile, device mobility uses device mobility groups, physical locations, and device mobility information to determine device identity and roaming properties and configuration.
Roaming
When a device is roaming in the same device mobility group, Cisco Unified Communications Manager uses the Device Mobility CSS to reach the local gateway. If a user sets Call Forward All at the phone, the CFA CSS gets set to None, and the CFA CSS Activation Policy gets set to With Activating Device/Line CSS, then:
•The Device CSS and Line CSS get used as the CFA CSS when the device is in its home location.
•If the device is roaming within the same device mobility group, the Device Mobility CSS from the Roaming Device Pool and the Line CSS get used as the CFA CSS.
•If the device is roaming within a different device mobility group, the Device CSS and Line CSS get used as the CFA CSS.
GUI Changes
The following comprise the changes that were made to the GUI in this release.
•In Release 6.0, access device mobility groups and device mobility information by using the System menu (System > Device Mobility > Device Mobility Group and System > Device Mobility > Device Mobility Information)
•The added Location Configuration window supports Device Mobility. Access this window by using the System menu (System > Location).
Where to Find More Information
•Cisco Unified Communications Manager Device Mobility, Cisco Unified Communications Manager Features and Services Guide
•Release Notes for Cisco Unified CallManager Release 4.2(1)
•For more information about configuration options for Call Forward All, see the Directory Number Configuration chapter in the Cisco Unified Communications Manager Administration Guide, and the Understanding Directory Numbers chapter in the Cisco Unified Communications Manager System Guide.
Directed Call Park
Directed Call Park, introduced in Cisco Unified CallManager Release 4.2(1), allows a user to transfer a call to an available user-selected directed call park number. Configure directed call park numbers in the Directed Call Park Configuration window. Configured directed call park numbers exist clusterwide. You can configure phones that support the directed call park Busy Lamp Field (BLF) button to monitor the busy/idle status of specific directed call park numbers. Users can also use the BLF button to speed dial a directed call park number.
A user can retrieve a parked call by dialing a configured retrieval prefix followed by the directed call park number where the call is parked.
Note Cisco recommends that you treat Call Park (a hold function) and Directed Call Park (a transfer function) as mutually exclusive: enable one or the other, but not both. If you do enable both, ensure that the numbers that are assigned to each are exclusive and do not overlap.
GUI Changes
In Release 6.0, access directed call park from the Call Routing menu (Call Routing > Directed Call Park).
Where to Find More Information
•Call Park and Directed Call Park, Cisco Unified Communications Manager Features and Services Guide
•Release Notes for Cisco Unified CallManager Release 4.2(1)
•Advanced Call Handling, phone user guides
Do Not Disturb
The Do Not Disturb (DND) feature allows you to turn off the ringer for an incoming call. When DND is enabled, you can also choose to have the Cisco Unified IP Phone beep or flash to indicate an incoming call. Users can configure DND directly from their Cisco Unified IP Phone or from the User Options.
With DND enabled, all new incoming calls with normal priority will honor the DND settings for the device. High-priority calls, such as Cisco Emergency Responder (CER) calls or calls with Multi-Level Precedence & Preemption (MLPP), will ring on the device. Also, when you enable DND, the Auto Answer feature gets disabled.
Although DND prevents most incoming calls from ringing a phone, the following features can override DND:
•Park reversion—For a locally parked call, park reversion overrides DND.
•Pickup—For locally placed pickup requests, pickup overrides DND.
•Hold reversion and intercom—Both hold reversion and intercom override DND, and the incoming call gets presented normally.
•MLPP and CER—Both MLPP and CER calls override DND and cause the phone to ring.
•Callback—Callback overrides DND, and callback notification still gets presented to the user.
•Pickup notification—When you enable DND Ringer Off, the user only receives visual pickup notification.
•Hunt list—When you enable DND on a phone in a hunt list, a call to the hunt list still gets presented to that phone.
Note Keep in mind that hunt list calls still get presented when DND Ringer Off is enabled by using DND alert settings. The hunt list call will not override DND.
Cisco Unified Communications Manager Administration Configuration Tips
To configure DND, complete the following tasks:
1. Configure DND service parameters (System > Service Parameters).
2. Configure DND softkeys (Device > Device Settings > Softkey Template).
3. Configure DND feature line keys (Device > Phone).
Note Depending on your system, you can configure either DND softkeys or DND feature line keys, or you can configure both.
4. Configure device-based DND parameters (Device > Phone).
5. Configure phone profile settings (Device > Device Settings > Common Phone Profile).
When you configure DND, keep the following configuration tips in mind:
•Be aware that Cisco Unified Communications Manager provides one systemwide service parameter for do not disturb: BLF Status Depicts DND. This parameter determines whether DND status is considered in the Busy Lamp Field (BLF) status calculation.
•You can configure DND on a per-device basis or in the common phone profile. If you do not set up DND at the device level, the common phone profile settings get used.
GUI Changes
For DND, Cisco Unified Communications Manager Administration includes one new service parameter, a DND softkey on the softkey template, as well as new fields on the Phone Configuration window and the Common Phone Profiles window.
To set the new service parameter, navigate to System > Service Parameters and choose the appropriate server and the Cisco CallManager service. You can specify either True or False for the BLF Status Depicts DND parameter.
To configure device parameters for DND, choose Device > Phone and configure the following parameters:
•Do Not Disturb
•DND Option
•DND Incoming Call Alert
To configure common phone profiles for DND, choose Device > Device Settings > Common Phone Profile and set the following parameters:
•DND Option
•DND Incoming Call Alert
To add a DND softkey, choose Device > Phone > Softkey Template. You can add a DND softkey for use in the following states:
•Connected
•Connected Conference
•Connected Transfer
•Off Hook
•Off Hook with Feature
•On Hold
•Remote In Use
•On Hook
To add a feature line key, choose Device > Device Settings > Phone Button Template and add Do Not Disturb in the Phone Button Template Configuration window.
Service Parameters
BLF Status Depicts DND—Specifies True or False.
User Tips
Users activate do not disturb (DND) by using any of the following options:
•Softkey
•Feature line key
•Cisco Unified Communications Manager User Options
After you activate DND, the phone status line displays Do not disturb is active, the DND line button icon becomes an empty circle, and the lamp turns amber if the DND feature line key is configured.
Cisco Unified Communications Manager 6.0.supports a subset of Do Not Disturb that is called Do Not Ring. Do Not Ring allows the user to toggle a Do Not Disturb state on/off for a device by using a feature key or softkey.
Note The feature key does not apply to the Cisco Unified IP Phone 7911G or 7906G.
Do Not Disturb disables all visual and audible notification of an incoming call during the ring-in state. Do Not Ring allows the user to turn off the audible ring only during the ringing-in state.
Supported Cisco Unified IP Phones (SCCP and SIP):
7971G-GE, 7970G, 7961G-GE, 7961G, 7941G-GE, 7941G, 7911G, 7906G
Supported Cisco Unified IP Phones (SCCP only):
7960G and 7940G (both softkey only) and 7931G
BAT Considerations
You can use the Bulk Administration Tool (BAT) to configure DND for groups of users. The BAT phone template includes the following DND fields:
•Do Not Disturb check box
•DND Incoming Call Alert
Where to Find More Information
•Do Not Disturb, Cisco Unified Communications Manager Features and Services Guide
•Common Phone Profile Configuration, Cisco Unified Communications Manager Administration Guide
•Cisco Unified IP Phone Configuration, Cisco Unified Communications Manager Administration Guide
•Softkey Template Configuration, Cisco Unified Communications Manager Administration Guide
•Phone Template, Cisco Unified Communications Manager Bulk Administration Guide
Hold Reversion
The Hold Reversion feature, which was introduced in Cisco Unified CallManager Release 4.2(3), alerts a phone user when a held call exceeds a configured time limit. When the held call duration exceeds the limit, Cisco Unified Communications Manager generates alerts, such as a ring or beep, at the phone to remind the user to handle the call. The held call becomes a reverted call when the hold duration exceeds the configured time limit.
For example, if you configure this feature to notify you when a call remains on hold past 30 seconds, Cisco Unified Communications Manager sends an alert, such as a ring or beep, to the phone after 30 seconds. You can also configure reminder alerts at configured intervals. A user can retrieve a reverted call on hold by going off hook, which deactivates the feature.
Where to Find More Information
•Hold Reversion, Cisco Unified Communications Manager Features and Services Guide
•Device Pool Configuration, Cisco Unified Communications Manager Administration Guide
•The Cisco Unified IP Phone administration guides for Cisco Unified IP Phones that support hold reversion and this version of Cisco Unified Communications Manager
•Cisco Unified IP Phone User Guides
•Release Notes for Cisco Unified CallManager Release 4.2(3)
Intercom
The Intercom feature allows a user to place a call to a predefined target (phone). The called destination auto-answers the call in speakerphone mode with mute activated. This sets up a one-way voice path between the initiator and the destination, so the initiator can deliver a short message, regardless of whether the called party is busy or idle.
To ensure that the voice of the called party does not get sent back to the caller when the intercom call is automatically answered, Cisco Unified Communications Manager implements whisper intercom. Whisper intercom provides only one-way audio from the caller to the called party. The called party must manually press a key to talk to the caller.
Note Intercom does not support Cisco Extension Mobility.
Cisco Unified Communications Manager Administration Configuration Tips
The following comprise configuration tips for Cisco Unified Communications Manager Administration.
1. Create intercom partition (Call Routing > Intercom > Intercom Route Partition). When you create an intercom partition, Cisco Unified Communications Manager Administration automatically generates a corresponding intercom calling search space with the same name and includes the intercom partition. See Intercom Partition Configuration in the Cisco Unified Communications Manager Administration Guide.
2. Create intercom calling search space (Call Routing > Intercom > Intercom Calling Search Space). When you create an intercom partition, Cisco Unified Communications Manager Administration automatically generates a corresponding intercom calling search space with the same name and includes the intercom partition. However, if you need to create an intercom calling search space other than the one that is generated automatically when you create the intercom partition, use these menus. See Intercom Calling Search Space Configuration in the Cisco Unified Communications Manager Administration Guide.
3. Create intercom translation pattern (Call Routing > Intercom > Intercom Translation Pattern). (Consider this step as optional.) See Intercom Calling Translation Pattern Configuration in the Cisco Unified Communications Manager Administration Guide.
4. Create intercom directory number (Call Routing > Intercom > Intercom Directory Number). See Intercom Directory Number Configuration in the Cisco Unified Communications Manager Administration Guide.
5. Add the intercom button to the appropriate phone button template (Device > Device Settings > Phone Button Template). See Phone Button Template Configuration in the Cisco Unified Communications Manager Administration Guide.
6. Assign intercom DN to a phone (Device > Phone > Add New). After completing the device information, click the line to which intercom gets configured. See Directory Number Configuration and Cisco Unified IP Phones Configuration in the Cisco Unified Communications Manager Administration Guide.
GUI Changes
The following comprise the changes that were made to the GUI for this release.
•You configure Intercom by using the four new Cisco Unified Communications Manager configuration windows that are provided from Call Routing > Intercom.
–Intercom Route Partition
–Intercom Calling Search Space
–Intercom Directory Number
–Intercom Translation Pattern
•System includes a new Intercom link on the Phone Configuration window, Association Information pane.
•System includes a new Intercom button on the Phone Button Template Configuration window.
User Tips
The system administrator configures Intercom in Cisco Unified Communications Manager Administration. The system administrator configures programmable buttons
•To dial an intercom line directly and/or
•To begin an intercom call, so the user can enter a specific intercom number to complete this call.
The intercom recipient can
•Listen to the intercom caller audio without answering
•End the call at any time by invoking the End Call softkey, or
•Press the intercom button to speak to the intercom caller.
Supported Cisco Unified IP Phones (SCCP and SIP):
7971G-GE, 7970G, 7961G-GE, 7961G, 7941G-GE, 7941G
Supported Cisco Unified IP Phones (SCCP only):
7931G, 7914 Expansion Module
BAT Considerations
The Cisco Unified Communications Manager administrator can use the Bulk Administration Tool (BAT) to add many intercom users at once instead of adding users individually. Refer to the Cisco Unified Communications Manager Bulk Administration Guide for more information.
Security Considerations
An intercom call represents a separate call and does not have media mixing to be played to third party. Basic call security should already cover all cases for intercom calls.
CTI Considerations
CTI supports both speakerphone and headset options for intercom as well as auto-answer settings for intercom lines.
Where to Find More Information
•Intercom Partition Configuration, Cisco Unified Communications Manager Administration Guide
•Intercom Directory Number Configuration, Cisco Unified Communications Manager Administration Guide
•Intercom Calling Search Space, Cisco Unified Communications Manager Administration Guide
•Intercom Translation Pattern Configuration, Cisco Unified Communications Manager Administration Guide
•Phone Button Template Configuration, Cisco Unified Communications Manager Administration Guide
•Cisco Unified IP Phone Configuration, Cisco Unified Communications Manager Administration Guide
•Cisco Unified Communications Manager Intercom, Cisco Unified Communications Manager Features and Services Guide
Licensing Enhancements
Use licensing in Cisco Unified Communications Manager Administration to accurately track the number of devices that are connected to Cisco Unified Communications Manager, including third-party phones that are running SIP, and compare it with the number of unit licenses that have been purchased.
Licensing helps manage Cisco Unified Communications Manager licenses and enforces the licenses for Cisco Unified Communications Manager applications and the number of IP phones. Using the Licensing Configuration window in Cisco Unified Communications Manager Administration, administrators can manage the phone and node licenses that get purchased and used.
The system generates licenses for requested Cisco Unified Communications Manager nodes (servers in a Cisco Unified Communications Manager cluster) and the phones that are associated with those nodes. Two types of licenses exist: production licenses and starter licenses. Production licenses for Cisco Unified Communications Manager represent licenses for phones and nodes that are purchased from Cisco. Starter licenses get replaced when a production license file is uploaded.
Cisco Unified Communications Manager keeps track of the software license version. Each time that the Cisco CallManager service restarts, this version check gets performed. If Cisco Unified Communications Manager fails to load (for example, because the license file is missing), the Service Manager tries to restart the Cisco CallManager service three times. At each attempt to restart, the license file check gets performed, and an alarm gets written to syslog.
The software license version displays in the License Unit Report window of Cisco Unified Communications Manager Administration. See License Unit Report, in the Cisco Unified Communications Manager Administration Guide.
Note For convenience, customers get an additional 5 percent of their total licenses when they receive their initial licenses.
Starter Licenses
Cisco Unified Communications Manager comes preinstalled with starter licenses, so the need does not exists for a file upload. Be aware that starter licenses, which have no expiration date, are available in limited quantities. Be aware that starter licenses are only available for fresh installations; they are not available for upgrades or migrations from previous releases. Starter licenses support only one Cisco Unified Communications Manager node and up to 50 device license units.
Starter license units get replaced when you purchase a production license.
Licenses for Primary Devices
Each phone type requires a fixed number of device license units. For example, Cisco Unified IP Wireless Phone 7920 requires four device license units, and Cisco Unified IP Phone 7970 requires five device license units. If you want licenses for four 7920 phones and four 7970 phones, you require 36 device license units. Additionally, certain types of applications, such as Cisco IP Communicator or mobility voice access, consume device license units.
Licenses for Adjunct Devices (Applications)
Certain types of applications, such as Cisco IP Communicator, Cisco Unified Mobile Communicator, and Cisco Unified Personal Communicator, consume device license units. For example, if IP communicator gets configured as a primary device to an end user, it consumes three device license units. If it gets configured as an adjunct device (by choice of a phone in the Primary Phone field in Phone Configuration), it consumes one device license unit, and the license unit calculator window displays the units that are consumed as Cisco IP Communicator (Adjunct).
Licenses for Mobility End User
When you configure an end user to have mobility functionality (check the Enable Mobility check box on the End User Configuration window), two device license units get consumed. When you uncheck the Enable Mobility check box, the two device license units get set back to zero.
To determine the number of units of licenses that are required for each phone and application, see Calculating License Units in the Cisco Unified Communications Manager Administration Guide.
Cisco Unified Communications Manager Administration Configuration Tips
See the following migration and upgrading configuration tips.
Migrating from Cisco Unified CallManager 4.2(3) to Cisco Unified Communications Manager 6.0(1)
When you migrate from Cisco Unified CallManager Release 4.2(3) to 6.0(1), the licenses that are required for existing phones and existing Cisco Unified Communications Manager nodes get calculated, and an intermediate file (XML file) that contains these license counts will get generated during the Cisco Unified Communications Manager migration process. Cisco gives these licenses free of cost because you are already using these phones for Cisco Unified CallManager Release 4.2(3). If you are adding new phones and nodes after migrating to Cisco Unified Communications Manager Release 6.0(1), you need to paste the intermediate license file in the License Registration window that is on CCO. See the Upgrading Cisco Unified Communications Manager and the Data Migration Assistant User Guide for more information.
Upgrading to Cisco Unified Communications Manager Release 6.0(1)
To successfully upgrade to Release 6.0(1), perform the following steps:
1. Obtain the license file for Release 6.0(1) (see Obtaining a License File, in the Cisco Unified Communications Manager Administration Guide).
2. Upgrade to Cisco Unified Communications Manager 6.0(1). (See the Upgrading Cisco Unified Communications Manager Release 6.0(1).)
Note The Cisco CallManager service will not activate due to lack of licenses. An alarm and alert get generated (see the Syslog for information).
3. After the upgrade, upload the appropriate license file (that you obtained in the previous step). See Uploading a License File, in the Cisco Unified Communications Manager Administration Guide for information on obtaining the appropriate license file.
4. Using Cisco Unified Serviceability, restart the Cisco CallManager service.
GUI Changes
The following comprise the changes that were made to the GUI for this release.
•Licensing > License Unit Report—Displays Software License Version
•Licensing > License Unit Calculator—New device types (phones, nodes, and applications)
Serviceability Considerations
The following comprise serviceability considerations for this release of Cisco Unified Communications Manager.
•If Cisco Unified Communications Manager does not have the appropriate license file, a Real-Time Monitoring Tool (RTMT) alert gets generated. See the Cisco Unified Serviceability Administration Guide for more information on alarms, and see the Cisco Unified Communications Manager Real-Time Monitoring Tool Administration Guide for more information on alerts.
•Cisco Unified Communications Manager keeps track of the software license version. Each time the Cisco CallManager service restarts, this version check gets performed. If Cisco Unified Communications Manager fails to load (for example, because the license file is missing), the Service Manager tries to restart the Cisco CallManager service three times. At each attempt to restart, the license file check gets performed, and an alarm is written to syslog.
Where to Find More Information
•Licensing, Cisco Unified Communications Manager System Guide
•License Unit Report, Cisco Unified Communications Manager Administration Guide
•License Unit Calculator, Cisco Unified Communications Manager Administration Guide
•License File Upload, Cisco Unified Communications Manager Administration Guide
•Licensing for Third-Party SIP Phones, Cisco Unified Communications Manager Administration Guide
•Cisco Unified Serviceability Administration Guide
•Cisco Unified Communications Manager Real-Time Monitoring Tool Administration Guide
Log Out of Hunt Groups
The Log Out of Hunt Groups feature, which was introduced in Cisco Unified CallManager Release 4.2(1), allows phone users to log out their phones from receiving calls that get routed to directory numbers that belong to line groups to which the phone lines are associated. Regardless of the phone status, the phone rings normally for incoming calls that are not calls to the line group(s) that are associated with the phone. The phone provides a visual status of the login state, so the user can determine by looking at the phone whether they are logged in to their line group(s).
Where to Find More Information
•Understanding Route Plans, Cisco Unified Communications Manager System Guide
•Softkey Template Configuration, Cisco Unified Communications Manager Administration Guide
•Advanced Call Handling, phone user guides
•Release Notes for Cisco Unified CallManager Release 4.2(1)
MGCP T.38 Enhancements
Introduced in Cisco Unified CallManager Release 4.2(3), T.38 fax relay added the following support (see Table 4):
•Cisco Unified Communications Manager supports CA-controlled MGCP T.38 fax relay.
•Fax calls use T.38 in CA-controlled mode if IOS enables T.38 (default).
•Fax calls use fax passthrough (or Cisco fax relay) if IOS disables T.38 (transparent to Cisco Unified Communications Manager).
•Both H.323 and MGCP (IOS only) support T.38 fax relay. For T.38 fax relay interworking between H.323 gateways and MGCP gateways, ensure MGCP gateways are configured to operate in CA-controlled mode.
Note Cisco Unified CallManager Release 5.0 does not include features from Release 4.2(3). Cisco Unified Communications Manager Release 6.0 includes those features.
In Release 5.0, T.38 fax relay introduced the following support:
•SIP support through the SIP trunk (configured by using SIP Trunk Configuration)
•H.323 and SIP T.38 interoperability
In Release 6.0, T.38 fax relay added the following support:
•T.38 interoperability support between SIP and MGCP
Table 4 T.38 Enhancements for Cisco Unified Communications Manager
T.38 Enhancement
|
Cisco Unified CallManager Release 4.1(1)
|
Cisco Unified CallManager Release 4.2(3)
|
Cisco Unified CallManager Release 5.0(1)
|
Cisco Unified Communications Manager Release 6.0(1)
|
T.38 supports H.323.
|
Yes
|
Yes
|
Yes
|
Yes
|
T.38 supports MGCP and H.323.
|
No
|
Yes
|
No
|
Yes
|
T.38 supports H.323 and SIP.
|
No
|
No
|
Yes
|
Yes
|
T.38 supports H.323, SIP, and MGCP.
|
No
|
No
|
No
|
Yes
|
Where to Find More Information
•Cisco Unified Communications Manager Administration Guide
•Cisco Unified Communications Manager System Guide
•Cisco IOS Fax and Modem Services over IP Application Guide
Overlap Sending and Receiving for H.323 Gateways
Introduced in Cisco Unified CallManager Release 4.2(1), support exists for overlap sending and receiving for H.323 gateways. H.323 module users do not need to dial all the digits for the setup message to be sent to an H.323 device. You can enable the overlap sending feature for the individual route pattern by using the Allow Overlap Sending check box on the Route Plan Configuration window. To enable the overlap receiving feature, you must set the Cisco CallManager service parameter, Overlap Receiving Flag for H.323, to True.
Where to Find More Information
•Client Matter Codes and Forced Authorization Codes, Cisco Unified Communications Manager Features and Services Guide
Privacy on Hold
With the privacy on hold feature, administrators can enable or disable the capability of users with phones that share the same line (DN) to view call status and retrieve calls on hold.
Administrators enable or disable privacy on hold for all phones in the cluster. To enable privacy on hold, the administrator must also enable the privacy feature for the phone or for all phones. Privacy on hold activates automatically on all private calls when privacy on hold is enabled.
To activate privacy on hold, users press the Hold softkey while on a private call. To return to the call, users press the Resume softkey. The phone that put the call on hold displays the status indicator for a held call; shared lines display the status indicators for a private and held call.
For more information about configuring and using privacy on hold, refer to the Barge and Privacy chapter in the Cisco Unified Communications Manager Features and Services Guide.
Programmable Line Keys
Cisco Unified IP Phones support line buttons (the buttons to the right of the display), which are used to initiate, answer, or switch to a call on a particular line. A limited number of features, such as speed dial, extension mobility, privacy, BLF speed dial, DND, and Service URLs, get assigned to these buttons.
The Programmable Line Key (PLK) feature expands the list of features that can be assigned to the line buttons to include features that are normally controlled by softkeys; for example, New Call, Call Back, End Call, and Forward All. When you configure these features on the line buttons, they always remain visible, so you can have a "hard" New Call key.
Cisco Unified Communications Manager Administration Configuration Tips
•Use the Phone Button Template Configuration window to assign programmable line keys.
•After configuring the phone button template, you must assign the phone button template to the phone by using Phone Configuration (reset is required).
GUI Changes
The following comprise the changes that were made to the GUI in this release.
•You can configure the following features on the phone buttons by using Phone Button Template Configuration:
–Redial (7931 uses existing line button)
–Speed Dial
–Hold (7931 uses existing line button)
–Transfer (7931 uses existing line button)
–Forward All
–Line
–Privacy
–Service URL
–Speed Dial BLF
–Call Park BLF
–Intercom
–Malicious Call ID
–Meet Me Conference
–Conference
–Call Park
–Call Pickup
–Group Call Pickup
–Mobility
–Do Not Disturb
–Conference List
–Remove Last Participant
–Quality Reporting Tool
–Call Back
–Other Pickup
–Video Mode
–New Call
–End Call
–Hunt Group Logout
–Settings (7971, 7970, 7961, 7941, and 7914 use existing button)
–Services (7971, 7970, 7961, 7941, and 7914 use existing button)
–Directories (7971, 7970, 7961, 7941, and 7914 use existing button)
–Messages (7971, 7970, 7961, 7941, and 7914 use existing button)
–Information (7971, 7970, 7961, 7941, and 7914 use existing button)
–Application Menu (7971, 7970, 7961, 7941, and 7914 use existing button)
–Headset (7971, 7970, 7961, 7941, and 7914 use existing button)
–None
User Tips
Programmable Line Keys supports Cisco Unified IP Phones 7971, 7970, 7961, 7941, 7931 (SCCP only), and 7914 (SCCP only)
BAT Considerations
The Phone Template supports Phone Button Template Configuration.
Where to Find More Information
•Cisco Unified IP Phone, Cisco Unified Communications Manager System Guide
•Phone Button Template Configuration, Cisco Unified Communications Manager Administration Guide
•Cisco Unified IP Phone Configuration, Cisco Unified Communications Manager Administration Guide
SCCP Optimization
Cisco Unified CallManager Release 4.2(3) introduced this feature. Because the feature consumes resources, ensure this feature gets enabled only when you experience signaling delays for phone that are using SCCP. Most users do not need this option.
Cisco Unified Communications Manager sends the bundled messages to the phone when the station buffer is full, as soon as it receives a media-related message, or when the Bundle Outbound SCCP Messages timer expires.
Note For Cisco Unified IP Phones 7960G and 7940G, the firmware version that supports improved SCCP messaging specifies 8.0(2).
In SCCP Version 9, SCCP message structures get altered to allow variable length messages instead of a fixed-length character array that consumes bandwidth.
Where to Find More Information
•Cisco Unified IP Phone Configuration, Cisco Unified Communications Manager Administration Guide
•Release Notes for Cisco Unified CallManager Release 4.2(3)
SDL Traces
Since it was introduced in Cisco Unified CallManager Release 4.2(1), you can use the Asynchronous SDL Logging Enabled parameter to determine whether Cisco Unified Communications Manager logs SDL traces in asynchronous mode. Asynchronous mode allows Cisco Unified Communications Manager to manage SDL trace data independently from other call-processing activities, which can improve Cisco Unified Communications Manager performance. This parameter setting does not affect SDL trace output; only the internal method data gathering is affected. In the event of a Cisco Unified Communications Manager exe crash, the SDL trace may not get fully logged. If asynchronous logging is enabled, an exception handler gets called to ensure that all the SDL trace data that were collected up until the time of crash get fully logged.
Where to Find More Information
•Trace, Cisco Unified Serviceability Administration Guide
SIP Endpoints Support
The following features support SIP endpoints in Release 6.0.
•Directed Call Park (see the "Directed Call Park" section)
•Log Out of Hunt Groups (see the "Log Out of Hunt Groups" section)
•Conference Chaining (for ad hoc conferences) (see the "Advanced Ad Hoc Conference" section)
•Voice Quality Metrics (see the "Call Diagnostics and Voice Quality Metrics" section)
•Call Pickup Group (see the "Call Pickup Notification" section)
•Hold Reversion (see the "Hold Reversion" section)
•Cisco Unified Communications Manager Assistant (see the "Cisco Unified Communications Manager Assistant" section)
•CTI enhancements (see the "CTI Enhancements" section)
•Call Select
•Privacy (see the "Privacy on Hold" section)
•Line-based Message Waiting Indicator
•Hunt Group CDR (see the "Call Detail Record Definitions" section)
Cisco Unified Communications Manager Administration Configuration Tips
The following comprise the administration configuration tips for this release.
•Directed Call Park—If reversion number is not configured, the call reverts to the parker (parking party) after the call park reversion timer expires. Directed Call Park for phones that are running SIP design incorporates busy lamp field (BLF) plus call transfer (to a park code). The transfer functionality remains the same as for phones that are running SCCP. Directed Call Park for phones that are running SIP includes the following limitations:
–Invoke directed call park by using the transfer softkey on Cisco Unified IP Phone Models 7940 and 7960 that are running SIP.
–The system does not support directed call park when the blind transfer softkey is used on Cisco Unified IP Phones 7940 and 7960 that are running SIP.
–The system does not support directed call park BLF on Cisco Unified IP Phones 7940 and 7960 that are running SIP and third-party phones that are running SIP.
–The following Cisco Unified IP Phones that are running SIP support directed call park BLF: 7941, 7961, 7970, and 7971.
•Conference Chaining—You can invoke ad hoc conference chaining for phones that are running SIP by using the Conference and Transfer functions. The system does not support Direct Transfer and Join. Supported Cisco Unified IP Phones include 7911, 7941, 7961, 7970, and 7971 that are running SIP.
•Log Out of Hunt Groups—This feature presents the following limitations:
–When Cisco Unified IP Phones 7906, 7911, 7941, 7961, 7970, and 7971 that are running SIP are logged in to hunt groups, and Call Forward All is activated, the call gets presented to the phone that is using SIP.
–When Cisco Unified IP Phones 7940 and 7960 that are running SIP are logged in to hunt groups, and Call Forward All is activated, the phone will get skipped, and the next phone in the line group will get rung.
–You can log Cisco Unified IP Phones 7940 and 7960 that are running SIP and third-party phones that are running SIP into/out of hunt groups by using the Phone Configuration window, but no softkey support exists.
–Cisco Unified IP Phones 7940 and 7960 that are running SIP and third-party phones that are running SIP will not show "Logged out of hunt groups" on the status line.
–Cisco Unified IP Phones 7940 and 7960 that are running SIP and third-party phones that are running SIP will not play the hunt group logoff notification tone regardless of whether the tone is configured.
•Voice Quality Metrics—Fully supported by Cisco Unified IP Phones 7911, 7941, 7961, 7970, and 7971 that are running SIP, support includes end-of-call reporting, mid-call reporting (for example, call hold, media disconnect), and voice quality metrics. Cisco Unified IP Phones 7905, 7912, 7940, and 7960 that are running SIP do not report voice quality metrics or mid-call reporting. To enable voice quality metrics on Cisco Unified IP Phones that are running SIP, check the Call Stats check box on the SIP Profile Configuration window.
•Call Pickup Group—This feature reflects the following limitations:
–Call pickup notification, audio, and visual alert support Cisco Unified IP Phones (SIP) 7911, 7941, 7961, 7970, and 7971.
–Call pickup notification, audio, and visual alert do not get supported on Cisco Unified IP Phones (SIP) 7905, 7912, 7940, and 7960.
–Call pickup notification, audio, and visual alert only supports licensed third-party phones that are running SIP.
•Hold Reversion—Call focus priority gets sent to the phone that is using SIP by its TFTP configuration file. The Cisco Unified IP Phones (SIP) 7906, 7911, 7941, 7961, 7970, and 7971 support the Hold Reversion feature. (This capability requires version 8.3(1) phone firmware.)
•Call Select and Privacy—Release 4.2 provides Call Select and Privacy enhancements for phones that are using SCCP that use shared lines. Releases 5.0 and 6.0 provide the same enhancements for phones that are running SIP that use shared lines. The system does not support Select and Privacy on nonshared lines for phones that are running SIP.
•Line-based Message Waiting Indicator—Release 6.0 provides line-based message waiting indicator for phones that are running SIP.
GUI Changes
See the individual features that this document lists for a list of GUI changes.
Serviceability Considerations
See the individual features that this document lists for a list of Serviceability changes.
BAT Considerations
See the individual features that this document lists for a list of BAT changes.
CAR/CDR Considerations
See the individual features that this document lists for a list of CAR changes.
Security Considerations
See the individual features that this document lists for a list of security changes.
CTI Considerations
See the individual features that this document lists for a list of CTI changes. Also see the "CTI Enhancements" section.
Features that CTI Does Support on Phones That Are Using SIP
CTI on phones that are running SIP supports the following features:
•Set lamp mode
•Display text on device
•Device-based, application-controlled softkeys
•Play device tone
•Ringing notification
•Call Park/Unpark - Request to park/unpark a specified call
•Call Park Reminder
•Call Privacy Change Notification
•Line Ringer Override - Overrides the current ringer setting for the specified line
Note Cisco Unified IP Phones (SIP) that are configured to use User Datagram Protocol (UDP) as the transport mode (instead of TCP) will not support the device data passthrough functionality; for example, the Quality Reporting Tool (QRT) requires the data passthrough functionality, so it cannot be used with IP phones that are configured with UDP.
Where to Find More Information
•Cisco Unified IP Phone Configuration, Cisco Unified Communications Manager Administration Guide
•SIP Profile Configuration, Cisco Unified Communications Manager Administration Guide
•Cisco Unified IP Phones, Cisco Unified Communications Manager System Guide
•Computer Telephony Integration, Cisco Unified Communications Manager System Guide
Third-Party Phones Enhancements for Phones That Are Using SIP
Cisco Unified Communications Manager Release 6.0 supports Cisco Unified IP Phones (SIP) in addition to phones that are running SIP that third-party companies design to work with Cisco Unified Communications Manager.
Licensing for Third-Party Phones That Are Using SIP
Third-party phones that are running SIP licensing enforces the following limitations:
•Third-party SIP Device (Basic)—Video calls do not get supported. Video enforcement occurs as part of the offer/answer process. If video-related media is provided as part of an offer or answer from a SIP device that is not permitted to negotiate video, only the non-video-related parts of the call get extended to the destination party. Similarly, a SIP endpoint that is not permitted to negotiate media will not receive any video-related media in the SDP that is sent from Cisco Unified Communications Manager.
•Third-party SIP Device (Advanced) and (Basic)—Cisco-specific SIP extensions do not get supported. Some Cisco-specific SIP extensions that do not get supported include service URIs, header extensions, dialog subscriptions, and remote call control proprietary mime types. Cisco Unified Communications Manager will reject any request from a phone that is using SIP that is not permitted to use an advanced feature that uses a service request URI (such as Call Pickup URI, Meet Me Service URI). The SIP profile specifies service URIs. The profile gets assigned to SIP devices. Cisco Unified Communications Manager will block features that require the use of Cisco-specific SIP extensions.
Note Be aware that any wireless third-party SIP client or device must be configured as a Third-Party SIP Device (Advanced) in conformance with Cisco Unified Communications Manager licensing policy.
Cisco Unified Communications Manager Administration Configuration Tips
Administrators use the following Cisco Unified Communications Manager Administration windows to configure third-party phones that are running SIP:
•To configure licensing for third-party phones that are running SIP, choose Licensing > License Unit Calculator and Licensing > License File Upload.
User Tips
The third-party vendor documentation provides all user information.
Where to Find More Information
•Configuring Non-Cisco SIP Phones, Cisco Unified Communications Manager Administration Guide
•License File Upload, Cisco Unified Communications Manager Administration Guide
•License Unit Calculator, Cisco Unified Communications Manager Administration Guide
•Licensing, Cisco Unified Communications Manager System Guide
•For more information about Cisco SIP Extensions, contact your Cisco representative.
SIP Trunk Enhancements
Cisco Unified Communications Manager Release 6.0 provides the following enhancements to SIP trunk:
•AAC/iLBC Voice Codec—See the "AAC/iLBC Voice Codec Support" section.
•SIP PUBLISH—This feature provides the preferred mechanism for Cisco Unified Communications Manager Release 6.0 to send IP phone presence information to Cisco Unified Presence Release 6.0 over a SIP trunk because it provides improved performance. PUBLISH also provides presence information on a line basis; for example, for do not disturb and mobility. Only outbound PUBLISH gets supported. (Cisco Unified Communications Manager Release 5.0 and 6.0 both support SUBSCRIBE/NOTIFY for presence. In addition, Cisco Unified Presence Release 6.0 supports Cisco Unified Communications Manager Releases 5.0 and 6.0.)
Cisco Unified Communications Manager Administration Configuration Tips for PUBLISH
The following configuration tips apply to Cisco Unified Communications Manager Administration when configuring a SIP trunk for PUBLISH:
•From the SIP Trunk Configuration window, configure a SIP trunk to access Cisco Unified Presence (destination address). In the destination port field, enter 5070 (preferred port for PUBLISH).
•From the Service Parameters Configuration window for the Cisco CallManager service, in the CUP PUBLISH Trunk field, choose the SIP trunk that you configured.
•Configure a Cisco Unified Presence end user (User Management > End User Configuration) and assign a licensing unit to the user (System > Licensing > Capabilities Assignment).
• Associate the end user with the line appearance (Device > Phone Configuration). From the Phone Configuration window, click the DN that the user will use to access Cisco Unified Presence. Click the Associated End Users button. From the Find and List Users window, choose an end user that will access Cisco Unified Presence.
•DND Support for SIP Trunk PUBLISH—Because DND is device based in Release 6.0, if a device is changed to the DND state, all Cisco Unified Presence-enabled line appearances that are associated with this device could get published. When a device gets changed to the DND state, DND as well as the busy/idle status will get published together to give Cisco Unified Presence more flexibility to process the data.
For Cisco Unified Presence users, consider DND an overall status of the person, rather than just a device setting; therefore, when DND is activated from a device, all line appearances that are associated with that device get published with the DND state, if the line appearances are associated with a Cisco Unified Presence user. As a result, DND will also get set on IP phone messenger (IPPM) and would block instant messages (IMs) on the IPPM device. It will also set DND on any other device that is associated with the user (unless a line appearance exists on that device that is associated with multiple users). The setting does not block Cisco Unified PresenceCommunicator IM or affect the display on Cisco Unified PresenceCommunicator in this release. For more information, see the Cisco Unified Presence documentation at cisco.com.
•Shared Lines—If Phone A and Phone B are sharing DN 1000, when a user picks up Phone A and makes a call on the line 1000, Cisco Unified Communications Manager notifies Cisco Unified Presence that line 1000 is busy. This information gives the watcher the illusion that all lines for DN 1000 are busy. This does not represent accurate information because line 1000 on Phone B remains idle. Cisco Unified Communications Manager tells Cisco Unified Presence that line 1000 on Phone A is busy. In Release 6.0, Cisco Unified Communications Manager publishes by line appearance. The system considers a line appearance a (DN, Device) pair.
•Multiple Partitions—When Cisco Unified Communications Manager publishes the presence status of a DN, it also shows the partition in which the DN is associated.
•Associating Username—With shared line and multiple partitions supported, Cisco Unified Presence cannot assume that it works only with one DN for each phone and also one partition across the whole Cisco Unified Communications Manager system. In Release 6.0, a line appearance can associate with an end user. SIP trunk will publish the status of the line appearance on behalf of the end user that is associated with that line appearance, which means that it can get used to identify Cisco Unified Presence-enabled lines. If a line appearance is associated with an end user, the systems consider it as Cisco Unified Presence -enabled; therefore, its presence information will get published.
Service Parameter Changes for PUBLISH
This release adds the following Cisco CallManager service parameters to the Service Parameter Configuration window:
•CUP PUBLISH Trunk
•Default PUBLISH Expiration Timer
•Minimum PUBLISH Expiration Timer
•Retry Count for SIP Publish
•SIP Publish Timer
Serviceability Considerations
Cisco Unified Serviceability collects and displays the following PUBLISH-related performance counters:
•SIP_StatsPublishIns
•SIP_StatsPublishOuts
•SIP_StatsRetryPublishOuts
•SIP_StatsRetryRequestsOut
The following performance counters exist in Cisco Unified Communications Manager Release 5.0, but the PUBLISH feature impacts their values:
•SIP_SummTotalOutReq
•SIP_SummTotalInRes
•SIP_StatsRetryRequestsOut
Security Considerations
RFC 3903 suggests the use of TLS and digest authentication against issues such as Access Control, Denial of Service Attacks, Replay Attacks, and Man in the Middle Attacks. Because Cisco Unified Communications Manager and Cisco Unified Presence support TLS and digest authentication, no changes occur in Release 6.0. The administrator can configure and enable TLS and digest authentication for Cisco Unified Communications Manager and Cisco Unified Presence. Additionally, IPSec can get used as an alternative to TLS.
BAT Considerations
The following comprise the BAT considerations for this release.
•BAT provides a tool that examines all Cisco Unified Presence licensed users and their primary extensions and associated device line appearances for users after Cisco Unified Communications Manager is upgraded from 5.x to 6.0. You need this tool during the upgrade/migration of Cisco Unified Presence when connecting to Cisco Unified Communications Manager Release 6.0 (because all the backend subscriptions get deleted and the new line appearance-based presence need to be available for Cisco Unified Presence users). To perform the migration, BAT uses the Export and Update functions. The export csv format specifies User ID, Device, Directory Number, Partition. The last three columns form a line appearance.
•To access the Export and Update windows, choose Bulk Administration > Users > Line Appearance > Export Line Appearance and Bulk Administration > Users > Line Appearance > Update Line Appearance.
•The Export and Update windows include a check box, Export Line Appearance for Cisco Unified Presence User Only (and Update Line Appearance for Cisco Unified Presence Users Only). When this check box gets checked, the export or update operation gets performed on the Cisco Unified Presence users. Non-Cisco Unified Presence users will not get exported or updated.
Where to Find More Information
•SIP Trunk Configuration, Cisco Unified Communications Manager Administration Guide
•End User Configuration, Cisco Unified Communications Manager Administration Guide
•Cisco Unified IP Phone Configuration, Cisco Unified Communications Manager Administration Guide
•Understanding Session Initiation Protocol, Cisco Unified Communications Manager System Guide
•Cisco Unified Communications Manager Bulk Administration Guide
Cisco Unified Communications Manager Applications
The following sections describe the Cisco Unified Communications Manager 6.0 applications enhancements:
•Cisco Unified Communications Manager Extension Mobility
•Cisco Unified Communications Manager Assistant
•Cisco Unified Mobility
•Migrating from Cisco Unified Mobility to Cisco Unified Communications Manager
•Multilevel Precedence and Preemption (MLPP) Supplementary Services
•Multilevel Precedence and Preemption Enhancements
•Recording and Monitoring
Cisco Unified Communications Manager Extension Mobility
The Cisco Extension Mobility (EM) equivalency enhancement that was introduced in Cisco Unified CallManager Release 4.2 eliminates the phone model dependency of phone button templates. The following factors determine the model equivalency among the various phones:
•Various features that the phone models support
•Number of buttons that the phone models support
The EM equivalency enhancement introduces the following support feature for the Cisco Unified IP Phones:
•Feature Safe on Phone Button Template
–Phones can use any phone button template that has the same number of buttons that the phone model supports.
–In Release 6.0 of Cisco Unified Communications Manager Administration, be aware that some Cisco Unified IP Phones (for example, 7970 and 7971) support Feature Safe.
Release 6.0 adds the following enhancements to Cisco Extension Mobility in Cisco Unified Communications Manager Release 6.0:
•After a user logs in to a phone, the Phone Configuration window for that device now reflects the Current End User Profile and Current Device Profile as well as links to the applicable End User Profile and Device Profile Configuration windows. This information displays in the Extension Information portion of the Phone Configuration window.
•When you subscribe Cisco Unified IP Phones to Cisco Extension Mobility, the options for Logout Profile in the Phone Configuration window have changed. You now have the option to select either Use Current Device Setting or any specific configured device profile that has a matching model and protocol type (the drop-down list box lists these device profiles). When total number of items in the drop-down list box exceeds 50, the drop-down list box changes to a search button.
•When you select the Use Current Device Setting option for Logout Profile, this no longer creates an autogenerated device profile. With the extension mobility rearchitecture, the internal implementation changed such that autogenerated device profiles no longer get used. During extension mobility login, the actual device record no longer changes. Instead, a mapping between the login device and the login profile gets created. If the logout profile is something other than Use Current Device Setting, during extension mobility logout, the mapping between the device and the logout profile remains. With the Use Current Device Setting option, no dynamic mapping occurs between the device and the device profile when the device is in the logout state.
•The line number for a phone does not change in the Phone Configuration window when a user logs in to a phone. It continues to display the line number that is associated with the phone when no user is logged in.
•The release makes New Find and List Actively Logged In Devices window available from the Actively Logged In Device Report link in the Related Links drop-down list box in the upper, right corner of the Phone Configuration window.
Service Parameter Changes
The reorganized Extension Mobility section of the Service Parameters Configuration window adds a new Advanced configuration button. Clicking Advanced displays the advanced Extension Mobility service parameters. The Maximum Concurrent Requests service parameter now represents an advanced service parameter. No new service parameters exist for extension mobility for this release.
Where to Find More Information
•Cisco Extension Mobility, Cisco Unified Communications Manager Features and Services Guide
Cisco Unified Communications Manager Assistant
Cisco Unified Communications Manager Assistant supports the following enhancements in Cisco Unified Communications Manager Release 6.0:
•Cisco Unified Communications Manager Assistant Configuration Wizard—The release adds the following windows to the configuration wizard:
–Secondary phone service
–Intercom partition
•The system provides BAT support for Cisco Unified IP Phones 7940, 7960, and 7970
•Cisco Unified Communications Manager Assistant on the Phone—The assistant can use the physical phone buttons and softkeys to perform most of the call-handling tasks that the assistant can perform by using the assistant console application. Cisco recommends that an assistant use the Cisco Unified Communications Manager Assistant-on-phone features only if that assistant supports no more than five managers.
•Assistant Console Layout—The assistant can customize the size and position of panels in the assistant console. Use the View menu to change the color scheme and font and to refresh initial default settings.
•Cisco Unified Communications Manager Do Not Disturb—Prior to Cisco Unified Communications Manager Release 6.0, Cisco Unified Communications Manager Assistant implemented DND at its layer. In Cisco Unified Communications Manager Release 6.0, DND represents a Cisco Unified Communications Manager feature, so Cisco Unified Communications Manager Assistant no longer uses the DND that it provided. (See the "Do Not Disturb" section.)
•Cisco Unified Communications Manager Intercom—Prior to Cisco Unified Communications Manager Release 6.0, Cisco Unified Communications Manager Assistant implemented intercom at its layer. In Cisco Unified Communications Manager Release 6.0, intercom represents a Cisco Unified Communications Manager feature, so Cisco Unified Communications Manager Assistant no longer uses its intercom feature for Cisco Unified IP Phones 7941, 7961, 7970, and 7971. (See the "Intercom" section.)
Note Cisco Unified IP Phones 7940 and 7960 do not support the Cisco Unified Communications Manager intercom feature. These phones must use the intercom feature that Cisco Unified Communications Manager Assistant provides.
•Alert Tone—Prior to Cisco Unified Communications Manager Release 6.0, the call detail that displayed on Status Window represented the only indication for assistant-handled calls on the manager phone. An alert tone helps a manager look at the display and intercept the call. Managers can turn alert tone On/Off from the IP Phone Service Menu on their phone. Assistants can turn alert tone On/Off for their managers from the manager configuration window in the assistant console and assistant phone. The assistant can also toggle the alert tone for their managers from the assistant console My Managers window.
•Support for phones that are running SIP—Managers and assistants can use Cisco Unified IP Phones 7941G, 7941G-GE, 7961G, 7961G-GE, 7970G, and 7971G-GE that are running SIP (session-initiated protocol).
•Scalability—This feature enhances the scalability numbers to 3500 managers and 3500 assistants (7000 users). Multiple active Cisco Unified Communications Manager Assistant instances run in the cluster, each managing 2500 users. Three such instances, each running on a separate server with a unique CTI Manager, can exist. To configure this feature, the release adds five new service parameters (see the "New Service Parameters" section).
•Redirect Softkey—Prior to Cisco Unified Communications Manager Release 6.0, the ImmDiv softkey appeared on the manager and assistant phones. In Cisco Unified Communications Manager Release 6.0, the ImmDiv softkey gets renamed to Redirect.
Cisco Unified Communications Manager Administration Configuration Tips
Cisco Unified Communications Manager Release 6.0 features include the following configuration differences:
•Cisco Unified Communications Manager Assistant Configuration Wizard—You use two windows to configure the Primary Phone Service Name and the Secondary Phone Service Name.
•Cisco Unified Communications Manager Assistant Configuration Wizard—Users use a new window to configure the Cisco Unified Communications Manager Intercom partition, which is required to use the intercom feature with Cisco Unified Communications Manager Assistant.
•The system provides BAT support for Cisco Unified IP Phones 7940, 7960, and 7970—The CSV file specifies these devices. (Prior to Cisco Unified CallManager Release 4.2, BAT would reject the record if the CSV file contained any non-7960 device.)
•Cisco Unified Communications Manager Do Not Disturb—This feature gets configured on the phone by using the Phone Configuration window. The phone gets associated to the manager by using the End User Configuration window.
•Cisco Unified Communications Manager Assistant supports the following intercom features:
–Cisco Unified Communications Manager Assistant intercom (used with Cisco Unified IP Phones 7940 and 7960). This intercom feature gets configured by using the DN configuration and end user (manager and assistant) configuration windows.
–Cisco Unified Communications Manager intercom (used with Cisco Unified IP Phones 7941, 7961, 7970, and 7971). This feature gets configured from the Call Routing menu by using the Intercom Route Partition, Intercom Calling Search Space, Intercom Directory Number, and Intercom Translation Pattern windows. The intercom directory number gets assigned to the device by using the Phone Configuration window. The phone gets associated to the manager or assistant by using the End User Configuration window. On the Assistant Configuration window, choose the incoming intercom line appearance for the assistant from the Intercom Line drop-down list box.
•Support for phones that are running SIP—Phones that are running SIP get configured in the Phone Configuration window. Phones that are running SIP can now be assigned to managers and assistants by using the End User Configuration window.
•Scalability—This enhancement gets configured by using Service Parameters Configuration and End User Configuration. When the service parameters are enabled and configured, the field, Assistant Pool, displays on the Manager Configuration window. From the drop-down list box, choose the applicable pool.
Note If you are migrating from a release previous to Cisco Unified Communications Manager Release 6.0(1), all managers and assistants will migrate to Pool 1 (the default).
•Migration—The following points apply to migration:
–When Cisco Unified Communications Manager is upgraded from a windows version, all Cisco Unified Communications Manager Assistant manager/assistant configurations migrate. The administrator must run the Data Migration Assistant (DMA) on the Windows platform prior to upgrading the platform to Release 6.0. It creates and exports a DMA tar ball of configuration data to be later installed onto the Release 6.0 platform during an upgrade.
–When upgrading and migrating from Cisco Unified CallManager Release 4.2, you must reinstall the Assistant Console application.
GUI Changes
Cisco Unified Communications Manager Assistant supports the following GUI changes:
•New windows in Cisco Unified Communications Manager Assistant Configuration Wizard for Phone Service Names and Intercom Partition.
•New field, Assistant Pool, on Manager Configuration window for scalability (up to 3500 managers and 3500 assistants).
•The Cisco Unified Communications Manager Assistant iDivert softkey renamed to Redirect (see the Softkey Template Configuration window).
New Service Parameters
•Enable/Disable Multiple Active Mode
•Pool 2: Cisco IPMA Server (Primary) IP Address
•Pool 2: Cisco IPMA Server (Backup) IP Address
•Pool 3: Cisco IPMA Server (Primary) IP Address
•Pool 3: Cisco IPMA Server (Backup) IP Address
User Tips
Cisco Unified Communications Manager Assistant suggests the following end user tips:
•Rename the Cisco Unified Communications Manager Assistant ImmDiv softkey to Redirect.
•Managers access Do Not Disturb from Cisco Unified Communications Manager softkeys.
•Managers and assistants who use the Cisco Unified IP Phones 7941, 7961, 7970, and 7971 access intercom from Cisco Unified Communications Manager softkeys.
•The assistant can use the physical phone buttons and softkeys to perform most of the call-handling tasks by using the assistant console application.
•The assistant can customize the size and position of panels in the assistant console. Use the View menu to change the color scheme and font and to refresh initial default settings.
•Managers can turn alert tone On/Off from the IP Phone Service Menu on their phones. Assistants can turn alert tone On/Off for their managers from the manager configuration window in the assistant console and assistant phone. The assistant can also toggle the alert tone for their managers from the assistant console My Managers window.
BAT Considerations
Cisco Unified Communications Manager Assistant supports the following considerations, which is now integrated with Cisco Unified Communications Manager Administration, for BAT.
•The system provides BAT support for Cisco Unified IP Phones 7940, 7960, and 7970
CAR/CDR Considerations
The Cisco Unified Communications Manager CDR Analysis and Reporting Administration Guide documents CDR information for Cisco Unified Communications Manager Assistant.
Where to Find More Information
•Cisco Unified Communications Manager Assistant With Proxy Lines, Cisco Unified Communications Manager Features and Services Guide
•Cisco Unified Communications Manager Assistant With Shared Lines, Cisco Unified Communications Manager Features and Services Guide
•Cisco Unified Communications Manager Security Guide
•Cisco Unified Communications Manager Administration Guide
•Cisco Unified Communications Manager System Guide
•Cisco Unified Communications Manager Bulk Administration Guide
Cisco Unified Mobility
Cisco Unified Communications Manager Release 6.0 integrates the Cisco Unified Mobility features, which include mobile connect and mobile voice access. Mobile connect enables users to manage business calls by using a single phone number and pick up in-progress calls on the desktop phone and cellular phone. Mobile voice access extends mobile connect capabilities by way of an integrated voice response (IVR) system that is used to initiate mobile connect calls and activate or deactivate mobile connect capabilities.
Mobile connect and mobile voice access enable flexible management of enterprise and cellular telephone communications and provide these features and benefits:
•Simultaneous desktop ringing—Incoming calls ring simultaneously on the IP phone extension and the designated mobile handset.When the user answers one line, the unanswered line automatically stops ringing. Users can choose the preferred device each time that a call comes in.
•Desktop call pickup—Users can switch between desktop phone and cellular phone during an active call without losing the connection. Based on the needs of the moment, they can take advantage of the reliability of the wired office phone or the mobility of the cellular phone.
•Single enterprise voice mailbox—The enterprise voice mailbox can serve as single, consolidated voice mailbox for all business, including calls to the desktop or configured remote devices. Incoming callers have a predictable means of contacting employees, and users need less time to check multiple voice-messaging systems.
•System remote access—A user cellular phone can initiate calls as if it were a local IP PBX extension. User-initiated calls can take advantage of local voice gateways and WAN trunking, and the enterprise can track employee call initiation.
•Allowed and blocked access lists—Users can restrict the set of callers that cause a designated remote destination to ring on an incoming call (allowed access list) or for which the remote destinations do not ring on an incoming call (blocked access list). Each remote destination presents a cellular or other phone that can be configured to accept transfers from the user desktop phone.
•Caller ID—Caller ID gets preserved and displayed on all calls. Users can take advantage of mobile connect capability with no loss of expected IP phone features.
•Remote on/off control—Users can turn their mobile connect features on or off from the cellular phone by using mobile voice access or from the End User Configuration window.
•Call tracing—Detailed mobile connect calls get logged, which provides information to help the enterprise optimize trunk usage and debug connection problems.
•Security and privacy for mobile connect calls—During an active mobile connect call, the associated desktop IP phone remains secured. Access to the call from the desktop gets eliminated as soon as the cellular connection becomes active, which precludes the possibility of an unauthorized person listening in on the call that is bridged to the cellular phone.
•Mid-call enterprise feature support—You can configure DTMF feature codes as Cisco Unified Communications Manager service parameters: Hold (default equals *81), exclusive hold (default equals *82), resume (default equals *83), transfer (default equals *84), and conference (default equals *85).
•Smartphone support—Users can use the enterprise hold, resume, transfer, conference softkeys on the smartphone in an active call. Users can also enable or disable mobile connect from a smartphone.
•Enterprise feature access for two-stage dialing—You can use enterprise features with two-stage dialing for smartphones. Two-stage dialing allows smartphones to make outgoing calls through Cisco Unified Communications Manager if the smartphone is in business mode. The smartphone dials the Enterprise Feature Access number for Cisco Unified Communications Manager and then dials the destination number.
•Manual handoff of calls on dual-mode phone—Dual-mode devices offer an option to manually hand off calls from the PSTN to WLAN and vice versa.
Cisco Unified Communications Manager Administration Configuration Tips
Cisco Unified Mobility supports the following configuration tips:
•To use mobile connect features, you must first disable the Auto Call Pickup feature.
•The Forced Authorization Code and Client Matter Code (FAC/CMC) feature does not work with mobile voice access. JAVA telephony programming interface (JTAPI) does not support the events that are required for FAC/CMC.
•To support different types of codecs, you must configure a transcoder in Cisco Unified Communications Manager for shared-line CTI ports.
•Mobile connect does not work with Multilevel Precedence and Preemption (MLPP). If a call is preempted with MLPP, the system disables mobile connect features for that call.
•Mobile connect services do not extend to video calls. The cellular phone cannot pick up a video call that is received at the desktop phone.
•Ensure remote destinations are Time Division Multiplex (TDM) devices.
•Be aware that mobile connect services are available only to directory numbers (DNs) that are in the same partition as the Shared Line CTI User. If the same DN is used in two different partitions, service only extends to the DN in the same partition as the Shared Line CTI User.
•The system does not make CDR Analysis and Reporting (CAR) support available.
•If two or more users share the same extension number, the parameters that are configured on the Line Appearances page correspond to the most recent update. Only one set of parameters gets stored for each extension, whether the extension is shared by multiple users or not.
•Users cannot access Meet-Me feature by using mobile voice access.
•QSIG (Q Signaling) path replacement does not get supported.
•When configuring CTI ports for outgoing calls, make sure the Media Resource group for the CTI Ports does not include Music-On-Hold (MOH) servers.
•When configuring a directory number that is associated with a remote destination profile, you must use ASCII characters only in the Display (Internal Caller ID) field on the Directory Number Configuration window.
•You do not need to configure settings for call forward unregistered if the end user has configured remote destinations. Appropriate call forwarding gets handled as part of the mobile connect process.
GUI Changes
The release adds new windows for Cisco Unified Mobility configuration:
•Call Routing > Mobility Configuration—Contains dual-mode phone handoff settings for call transfers between a user desktop phone and cellular phone.
•Media Resources > Mobile Voice Access—Contains settings for localized user IVR prompts.
•Device > Device Settings > Access Lists—Determines the phone numbers that are explicitly allowed or blocked for in-progress call transfers.
•Device > Device Settings > Remote Destination Profile—Contains the parameters that apply to all the remote destinations (cellular or other phones) that are available for in-progress call transfers and initiation of calls by way of mobile voice access.
•Device > Device Settings > Remote Destination—Specifies the cellular (or other phones) that can accept transfers from the user desktop phone and can be used to initiate calls by using mobile voice access.
The release updates the following window to support Cisco Unified Mobility configuration:
•User Management > End User—New Mobility Information section allows the user to choose remote destination profiles and access lists and enable mobile voice access.
New Service Parameters
These new service parameters support Cisco Unified Mobility:
•Delay before ringing cell phone timer
•Answer too late timer (also known as maximum cell phone ring timer)
•Answer too soon timer (also known as minimum cell phone ring timer)
User Tips
End users can configure mobility by using Cisco Unified Communications Manager User Options:
•Mobility Settings > Remote destinations—End users can add their own remote destinations.
•Mobility Settings > Access lists—End users can define their own access lists.
BAT Considerations
Cisco Unified Mobility supports BAT, which now integrates with Cisco Unified Communications Manager Administration. The system supports BAT for these functions:
•Users
•Access lists
•Remote destination profiles
•Remote destinations
CAR/CDR Considerations
Be aware that CDR Analysis and Reporting (CAR) support is not available.
Security Considerations
•Be aware that Mobility Voice Access is password-protected.
•During an active mobile connect call, the associated desktop IP phone remains secured. Access to the call from the desktop gets eliminated as soon as the cellular connection becomes active, which precludes the possibility of an unauthorized person listening in on the call that is bridged to the cellular phone.
Where to Find More Information
•Mobile Connect and Mobile Voice Access, Cisco Unified Communications Manager Features and Services Guide
•End User Configuration, Cisco Unified Communications Manager Administration Guide
•Cisco Unified Communications Manager Bulk Administration Guide
Migrating from Cisco Unified Mobility to Cisco Unified Communications Manager
This section provides guidelines for migrating Cisco Unified Mobility data to Cisco Unified Communications Manager 6.0.
Note Before performing the migration, verify that the user names that are configured for Cisco Unified Mobility are also configured in Cisco Unified Communications Manager. Specifically, if user1 is the Cisco Unified Mobility user whose data will be migrated to Cisco Unified Communications Manager, user1 must already exist in the Cisco Unified Communications Manager database.
Note Cisco Unified Communications Manager 6.0 does not allow remote destination numbers to be shared; therefore, you must remove any duplication during migration.
Note The remote destination number in Cisco Unified Mobility may have a 9 or 91 prefix access code. Confirm that these prefixes are consistent with the Cisco Unified Communications Manager 6.0 configuration during migration.
Migration Files
The data files that are listed in this section must be migrated to Cisco Unified Communications Manager.
CMMRDProfile.csv
This file contains the following fields:
REMOTE DESTINATION PROFILE NAME,DESCRIPTION,USER ID,DIRECTORY NUMBER 1,CSS,DEVICE POOL
REMOTE DESTINATION PROFILE NAME gets taken from the Mobile Voice Access User ID field in Cisco Unified Mobility. CSS and DEVICE POOL derive from an AXL query from Cisco Unified Communications Manager
In the DESCRIPTION field, the tool adds a default description, userID_RDP.
Example:
1681000RDP,johndoe_RDP,johndoe,1681000,everyonecss,Default
CMMAccessList.csv
This file contains the following fields:
ACCESS LIST NAME,ACCESS LIST DESCRIPTION,ACCESS LIST ALLOWED,ACCESS LIST OWNER,ACCESS LIST MEMBER 1
Example:
allow1,,t,johndoe,5551212
CMMRemoteDestination.csv
This file contains the following fields:
DESTINATION,NAME,DUAL MODE DEVICE,REMOTE DESTINATION PROFILE,ISMOBILEPHONE,ANSWER TOO SOON TIMER,ANSWER TOO LATE TIMER,DELAY BEFORE RINGING TIMER,ACCESS LIST ALLOWED,ACCESS LIST BLOCKED,SMART CLIENT INSTALLED,ENABLE MOBILE CONNECT,ASSOCIATED LINE NUMBER,PARTITION
In the DESTINATION NAME field, the tool adds a default name userID_RD.
Example:
95551212,johndoe_RD,f,1681000,t,1500,0,0,,,f,t,1681000,
CMMUserEnable.csv
This file contains the following fields:
USER ID,ENABLE MOBILITY,ENABLE MOBILE VOICE ACCESS
Example:
johndoe,t,t
CMMFeatureDataExport.log
This log contains warning messages.
Example:
Feature Data checking starts -----.
Remote Destination 95551212 has been associated with two users: 1681000RDP and 1682000RDP.
Feature Data checking ends -----.
Follow this process to migrate standalone Cisco Unified Mobility data to Cisco Unified Communications Manager Release 6.0(1):
Procedure
Step 1 Log in to Cisco Unified Mobility and export the configuration data files in CSV format:
•Use Export > Feature Data for CMMRDProfile.csv, CMMAccessList.csv, CMMRemoteDestination.csv, and CMMUserEnable.csv.
•Use Export > Log for CMMFeatureDataExport.log.
Step 2 Log in to Cisco Unified Communications Manager Administration Release 6.0(1). To upload the four CSV files, choose Bulk Administration > Upload/Download Files.
Step 3 To create a template and its associated line template, choose Bulk Administration> Mobility > Remote Destination Profile> Remote Destination Profile Template. In the Rerouting Calling Search Space field, enter the value that is taken from the Outgoing CTI port Calling Search Space in your old Cisco Unified Communications Manager system.
Step 4 Choose Bulk Administration > Mobility > Remote Destination Profile, and insert the file CMMRDProfile.csv. To verify that no error occurs, check the error log.
Step 5 Choose Bulk Administration > Mobility > Access List, and insert the file CMMAccessList.csv. To verify that no error occurs, check the error log.
Step 6 Choose Bulk Administration > Mobility > Remote Destination, and insert the file CMMRemoteDestination.csv.To verify that no error occurs, check the error log.
Step 7 Choose Bulk Administration > Users, and update the file CMMUserEnable.csv. To verify that no error occurs, check the error log.
Multilevel Precedence and Preemption (MLPP) Supplementary Services
Introduced in Cisco Unified CallManager Release 4.2(3), MLPP Supplementary Services support the following features:
•MLPP Support for Multiple Appearance Lines—The system currently supports MLPP support for multiple appearance lines.
•Call Forwarding—Ensure no precedence calls are forwarded to off-net endpoints (for example, cell phones). Additionally, ensure forwarded calls retain the original precedence across multiple forwarding hops.
–For CFA (Call Forward All) scenarios, precedence calls get routed to the AP target of the original called party immediately. The CFA target does not get used for MLPP calls.
–For CFB (Call Forward Busy) scenarios, precedence calls will get forwarded to the configured CFB destination, subject to the hop count limits that were previously described and the state of open appearances on the called party endpoint.
–For the CFNA (Call Forward No Answer) scenario, the system attempts a single forward attempt (hop) to the CFNA target of the original called party. If that endpoint does not answer prior to the no answer timer expiring, the call then gets sent to the MAP target of the original called party.
•Three-Way Calling—The three-way calling enhancement allows each connection of a three-way call to maintain its original precedence level. The phone that is performing the split operation of the three-way call uses the higher precedence level of the two calls when different precedence levels are used. This enhancement also supports preemption of conference bridge resources. If a conference bridge is saturated with calls, individual streams gets preempted when a new, higher precedence, three-way call gets set up.
•Transfer—When a call transfer is made at different precedence levels, the switch that initiates the transfer class marks the connection at the highest precedence level of the two segments.
This enhancement upgrades the precedence level of a call leg that is involved in a transfer operation. For example, party A calls party B at Priority. Party B then initiates a transfer to C and dials the Flash precedence digits when dialing. When the transfer completes, the precedence level of party A gets upgraded from Priority to Flash.
Note The precedence level upgrade does not work over ICT or PRI trunks.
•Call Pickup—This enhancement adds the criteria of highest precedence to the call pickup algorithm. The enhancement includes the following requirements:
–If a call pickup group has more than one party in an unanswered condition, and the unanswered parties are at different precedence levels, a call pickup attempt in that group will retrieve the highest precedence call first.
–If multiple calls of equal precedence are ringing simultaneously, a call pickup attempt in that group will retrieve the longest ringing call first.
–This release supports group pickup functionality for MLPP calls. Operation follows normal call pickup functionality.
–For MLPP calls, this release does not support Other Group Pickup.
•Hunt Pilot/Hunt List—Normal hunt algorithm logic occurs until all lines in the hunt group are busy. When all lines are busy, the lowest precedence call gets selected for preemption. When preemption occurs, normal line group `no answer' timer continues. When timer expires, next lowest precedence call in hunt group gets selected for preemption. MLPP enhancements support the following three hunt algorithms:
–Top down
–Longest idle time
–Circular
Cisco Unified Communications Manager allows multiple line groups to be configured for a hunt group.
Where to Find More Information
•Cisco Unified IP Phone User Guides
•MultiLevel Presence and Preemption, Cisco Unified Communications Manager Features and Services Guide
•Service Activation, Cisco Unified Serviceability Administration Guide
•Release Notes for Cisco Unified CallManager Release 4.2(3)
Multilevel Precedence and Preemption Enhancements
Introduced in Cisco Unified CallManager Release 4.2(1), MLPP includes the following additional features for the Defense Red Switched Network (DRSN):
•Support to map MLPP precedence levels to DSCP values in the TOS field of the IP header
•Support for MLPP-enabled, UUIE-based PRI-4ESS interface across intercluster trunks
•V150.1 Modem Relay support for Cisco Unified Communications Manager intercluster trunking configurations
Introduced in Cisco Unified CallManager Release 4.2(1), the following configuration enhancements to MLPP support these features:
•UUIE Configuration on H.225 and Intercluster Trunk Configuration window for 4ESS protocol:
–Passing Precedence Level Through UUIE
–Security Access Level
•You can map the following precedence levels to DSCP values in the Service Parameters window:
–Executive Override
–Flash Override
–Flash
–Immediate
–Priority
Tunneling of MLPP precedence level information can get carried in a PRI UUIE across an H.323 intercluster trunk via nonstandard control data within a H.225 UUIE.
DSCP marking creates multiple expedited forwarding classification levels that correspond to MLPP precedence levels.
Where to Find More Information
•Introducing MLPP, Cisco Unified Communications Manager Administration Guide
•Trunk Configuration, Cisco Unified Communications Manager Administration Guide
Recording and Monitoring
Cisco Unified Communications Manager supports silent call monitoring and call recording. Call centers need to be able to guarantee the quality of customer service that an agent in a call center provides. To protect themselves from legal liability, call centers need to be able to archive agent-customer conversations.
The Silent Call Monitoring feature allows a supervisor to eavesdrop on a conversation between an agent and a customer without allowing the agent to detect the monitoring session. (Other call monitoring modes include whisper call monitoring and active call monitoring, which the current release of Cisco Unified Communications Manager does not support.)
The Call Recording feature allows system administrators or authorized personnel to archive conversations between the agent and the customer.
Cisco Unified Communications Manager Administration Configuration Tips
Perform the following steps to configure monitoring and recording:
1. Turn on IP phone built-in bridge (BIB) to allow monitoring or recording.
2. Add user for monitoring or recording application.
3. Add user to groups that allow monitoring and recording.
4. Configure tones for monitoring or recording.
5. Configure DN for monitoring calling search space.
6. Enable recording for a line appearance.
7. Create recording profile.
8. Create a SIP trunk that points to the recorder.
9. Create a route pattern for the recorder.
10. Create recorder redundancy.
Refer to the Monitoring and Recording chapter of the Cisco Unified Communications Manager Features and Services Guide for configuration details.
GUI Changes
The following new and changed window supports recording and monitoring:
•Recording Profile Configuration (Device > Device Settings > Recording Profile)
Service Parameter Changes
The following new service parameters support recording and monitoring:
•Play Recording Notification Tone To Observed Target
•Play Recording Notification Tone To Observed Connected Parties
•Play Monitoring Notification Tone To Observed Target
•Play Monitoring Notification Tone To Observed Connected Parties
•G722 Codec Enabled
•iLBC Codec Enabled
•Built-in Bridge Enable
CTI Considerations
Computer Telephony Integration (CTI), Java Telephony API (JTAPI), and TSP support monitoring and recording of calls. Applications can use these interfaces to monitor or record calls in a Cisco Unified Communications Manager system. CTI provides the ability for applications to monitor calls on a per-call basis.
Call reference for the recorded call (agent-customer call) gets passed to the recorder. The recording application needs to get other relevant information through the CTI interface.
When invoking recording and monitoring or any other CTI features, delays and unexpected behavior can result if UDP transport is used for phones that are running SIP.
Security Considerations
To meet with the security requirements, the system allows call monitoring and call recording only when the monitoring calls or the recording calls can be established with the same or higher security levels as the security level of the call that is monitored or recorded. When such conditions cannot be met, the monitoring request or the recording request gets rejected with appropriate cause codes.
To implement the behavior in Cisco Unified Communications Manager that the security requirements for monitoring and recording dictate, the system uses a phased approach. In the first phase, the system permits monitoring or recording sessions only for an IP phone that does not have security enabled. When an application requests monitoring and recording sessions for a security-enabled phone, the request gets rejected with an appropriate cause code.
BAT Considerations
The monitoring and recording features interact with the Bulk Administration Tool (BAT).
Where to Find More Information
•Monitoring and Recording, Cisco Unified Communications Manager Features and Services Guide
•Cisco Unified IP Phone Configuration, Cisco Unified Communications Manager Administration Guide
•Application User Configuration, Cisco Unified Communications Manager Administration Guide
•User Group Configuration, Cisco Unified Communications Manager Administration Guide
•Service Parameters Configuration, Cisco Unified Communications Manager Administration Guide
•Directory Number Configuration, Cisco Unified Communications Manager Administration Guide
•Recording Profile Configuration, Cisco Unified Communications Manager Administration Guide
•Route Pattern Configuration, Cisco Unified Communications Manager Administration Guide
•Trunk Configuration, Cisco Unified Communications Manager Administration Guide
Cisco Unified Communications Manager Bulk Administration Features
Cisco Unified Communications Manager Bulk Administration Tool (BAT), a web-based application, performs bulk transactions to the Cisco Unified Communications Manager database. This section introduces the changes to BAT for Cisco Unified Communications Manager 6.0.
•New and Changed Information for BAT
•BAT Configuration Tips
•GUI Changes
New and Changed Information for BAT
The following changes in BAT apply for Cisco Unified Communications Manager Release 6.0:
•Adding and Updating Intercom DNs—You can use BAT to add and update intercom directory numbers in bulk. You access this feature from Bulk Administration > Phones > Add/Update Intercom.
•Updating and Exporting Line Appearances—You can use BAT to export and update information about line appearances. You access this feature from Bulk Administration > Users > Line Appearance.
•Inserting VG224 Gateways—You can use BAT to insert VG224 gateways in bulk. You can do this through Bulk Administration > Gateways > Insert Gateways.
•Creating and Adding Gateway File Formats—You can use BAT to configure gateway file formats. You access this feature from Bulk Administration > Gateways > Gateway File Format.
•Working with Mobility:
–Access Lists—You can use the Bulk Administration menu to insert, delete, and export access lists. You access this feature from Bulk Administration > Access List.
–Working with Remote Destinations—You can use BAT to insert, delete, and export remote destination details in bulk. Access this feature from Bulk Administration > Mobility > Remote Destination.
–Working with Remote Destination Profiles—You can use BAT to format, insert, delete, and export Remote Destination Profiles (RDPs) in batches. You access this feature from Bulk Administration > Mobility > Remote Destination Profile.
•Importing/Exporting Configuration—You can use the Import/Export menu in BAT to export or import all or a part of the Cisco Unified Communications Manager database to another server, or to the same server with modifications. You access this feature from Bulk Administration > Import/Export.
BAT Configuration Tips
Access all BAT configuration from the Cisco Unified Communications Manager Administration menu.
GUI Changes
Cisco Unified Communications Manager Administration includes a menu item called Bulk Administration. The following changes occurred in the GUI for BAT in Cisco Unified Communications Manager 6.0:
•Bulk Administration > Phones > Add/Update Intercom
–Update Intercom DNs
–Add Intercom DNs
•Bulk Administration > Users > Line Appearance
–Export Line Appearance
–Update Line Appearance
•Bulk Administration > Gateways > Gateway File Format
–Create File Format
–Add File Format
•Bulk Administration > Import Export
–Export
–Import
•Bulk Administration > Mobility
–Access List
–Remote Destination
–Remote Destination Profile
Where to Find More Information
•Cisco Unified Communications Manager Bulk Administration Guide
Cisco Unified Communications Manager Security Features
Cisco Unified Communications Manager 6.0 supports the following security features:
•Secure Conferencing
•Secure Conference Icon
Secure Conferencing
The Secure Conferencing feature provides authentication and encryption to secure a conference. Consider a conference as secure when all participating devices have encrypted signaling and media. The secure conference feature supports SRTP encryption over a secure TLS or IPSec connection.
The system provides a security icon for the entire conference, which is determined by the lowest security level of the participating devices. For example, a secure conference that includes two encrypted connections and one authenticated connection represents a conference security status of authenticated.
Conference status can change as participants enter and leave the conference. An encrypted conference session can revert to a security level of authenticated or nonsecure if an authenticated or nonsecure participant connects to the call. Likewise, the session status can upgrade if an authenticated or nonsecure participant drops off the call. A nonsecure participant that connects to a conference call renders the conference session nonsecure.
As administrator, you can specify a minimum security level for a conference when you configure a Meet-Me pattern or number as authenticated or encrypted. Participants must meet the minimum security requirement, or the system blocks the participant and drops the call.
To secure conferences with barge, configure phones to use encrypted mode. After the Barge key is pressed and if the device is authenticated or encrypted, Cisco Unified Communications Manager establishes a secure connection between the barging party and the built-in bridge at the target device. The system provides a conference security status for all connected parties in the barge call. See the "Barge Enhancements" section for secure conference considerations with barge.
Warning To obtain the full benefit of secure conference features, Cisco recommends upgrading Cisco Unified IP Phones to firmware release 8.3, which supports the encryption features in this release. Encrypted phones that run earlier releases do not fully support these new features. These phones can only participate in a secure conference as authenticated or nonsecure participants.
Cisco Unified IP Phones that are running firmware release 8.3 with an earlier release of Cisco Unified Communications Manager will display their connection security status during a conference call, not the conference security status, and do not support secure conference features like conference list.
Cisco Unified Communications Manager supports secure conference over licensed CTI devices.
Cisco Unified Communications Manager supports secure conference over intracluster trunks (ICTs), H.323 trunks/gateways, and MGCP gateways; however, encrypted phones that are running firmware release 8.2 or earlier will revert to RTP for ICT and H.323 calls, and the media does not get encrypted.
If a conference involves a SIP trunk, the secure conference status specifies nonsecure. In addition, SIP trunk signaling does not support secure conference notifications to off-cluster participants.
Cisco Unified Communications Manager Administration Configuration Tips
A conference bridge can register as a secure media resource when you add a hardware conference bridge to your network and you configure a secure conference bridge in Cisco Unified Communications Manager Administration.
Consider the following information before you configure secure conference bridge resources:
•Use localization if you want the phone to display custom text for secure conference messages. Refer to the Cisco Unified Communications Operating System Administration Guide for information about the Locale Installer.
•The conference or built-in bridge must support encryption to secure conference calls.
•To enable secure conference bridge registration, set the cluster security mode to mixed mode.
•Ensure the phone that initiates a conference is authenticated or encrypted to procure a secure conference bridge.
•To maintain conference integrity on shared lines, do not configure devices that share a line with different security modes; for example, do not configure an encrypted phone to share a line with an authenticated or nonsecure phone.
•Do not use SIP trunks as ICTs when you want to share conference security status between clusters.
•If you set the cluster security mode to mixed mode, the security mode that is configured for the DSP farm (nonsecure or encrypted) must match the conference bridge security mode in Cisco Unified Communications Manager Administration, or the conference bridge cannot register. The conference bridge registers as encrypted when both security modes specify encrypted; the conference bridge registers as nonsecure when both security modes specify nonsecure.
•If you set the cluster security mode to mixed mode, if the security profile that you applied to the conference bridge is encrypted, but the conference bridge security level is nonsecure, Cisco Unified Communications Manager rejects conference bridge registration.
•If you set the cluster security mode to nonsecure mode, configure the security mode at the DSP farm as nonsecure, so the conference bridge can register. The conference bridge registers as nonsecure even if the setting in Cisco Unified Communications Manager Administration specifies encrypted.
•During registration, the conference bridge must pass authentication. To pass authentication, the DSP farm must contain the Cisco Unified Communications Manager certificate, and Cisco Unified Communications Manager must contain certificates for the DSP farm system and the DSP connection. To ensure the conference bridge passes authentication, the X509 certification name must contain the conference bridge name.
•If conference bridge certificates expire or change for any reason, use the certificate management feature in the Cisco Unified Communications Operating System Administration to update the certificates in the trusted store. The TLS authentication fails when certificates do not match, and conference bridge does not work because it cannot register to Cisco Unified Communications Manager.
•The secure conference bridge registers to Cisco Unified Communications Manager through TLS connection at port 2443; a nonsecure conference bridge registers to Cisco Unified Communications Manager through TCP connection at port 2000.
•Changing the device security mode for the conference bridge requires a reset of Cisco Unified Communications Manager devices and a restart of the Cisco CallManager service.
•To configure packet capturing for a secure conference bridge, enable packet capturing in the Service Parameter Configuration window; then, set the packet capture mode to batch mode and capture tier to SRTP for the phone, gateway, or trunk in the device configuration window.
GUI Changes
The following new and changed windows in Cisco Unified Communications Manager Administration contain secure conferencing configuration settings:
•Media Resources > Conference Bridge Configuration
–Device Security Mode
Note You must select Cisco IOS Enhanced Conference Bridge as the conference bridge type.
•Call Routing > Meet-Me Number/Pattern
–Minimum Security Level
Removed or Changed Service or Enterprise Parameters
To keep a conference secure, if a participant in a secure ad hoc conference puts a call on hold or parks the call, the system does not play MOH, even if the Suppress MOH to Conference Bridge service parameter is set to False. The secure conference status does not change.
Serviceability Considerations
CDR data provides the security status of each call leg from the phone endpoint to the conference bridge as well as the security status of the conference itself. The two values use two different fields inside the CDR database.
CDR data provides termination cause code 58 (Bearer capability not presently available) when a Meet-Me conference rejects a join attempt that does not meet the minimum security level requirement.
This features includes no new performance objects, counters, or alarms.
User Tips
When users with secure phones initiate standard (ad hoc) conference calls or meet me conference calls, Cisco Unified Communications Manager assigns a secure conference bridge. An icon (lock or shield) displays next to "Conference" on the phone window to indicate the security level of the conference. If a participant with a nonsecure phone joins the conference, the icon changes to a "call in progress" icon to indicate that the conference is no longer secure.
Non-secure participants and non-secure conferences show the call state icon for "connected call."
Where to Find More Information
•Cisco Unified Communications Manager Security Guide
•Cisco Unified Communications Manager Troubleshooting Guide
Secure Conference Icon
Cisco Unified IP Phones display a conference security icon for the security level of the entire conference. These icons match the status icons for a secure, two-party call, as described in the user documentation for your phone.
For ad hoc and meet-me secure conferences, the security icon for the conference session displays next to the conference softkey in the phone screen for conference participants. The icon that displays depends on the security level of the conference bridge and all participants.
A conference list displays on participating phones when the ConfList softkey is pressed during a conference call. The conference list provides the conference status as well as the security status for each participant to identify participants that are not encrypted. Conference list displays these security icons: nonsecure, authenticated, encrypted, held. The conference initiator can use the conference list to eject participants with a low security status.
Note The Advanced Ad Hoc Conference Enabled service parameter determines whether conference participants other than the conference initiator can eject conference participants.
When a user presses Barge, the icon that displays next to the Barge softkey provides the security level for the barge conference. If the barging device and the barged device support encryption, the system encrypts the media between the two devices, but the barge conference status can be nonsecure, authenticated, or encrypted, depending on the security levels of the connected parties. See the "Barge Enhancements" section for secure conference icon considerations with barge.
During a packet capture session, the phone displays a nonsecure status for the conference, even if the media stream is encrypted.
Cisco Unified Communications Manager Administration Configuration Tips
Secure conference icons display when you configure a secure conference bridge in Cisco Unified Communications Manager Administration or barge secure phones.
Removed or Changed Service or Enterprise Parameters
If a participant in a secure ad hoc conference puts a call on hold or parks the call, the system does not play MOH, even if the Suppress MOH to Conference Bridge service parameter is set to False, to keep the conference secure. The secure conference status does not change.
Where to Find More Information
•Secure Conferencing
•Cisco Unified Communications Manager Security Guide
Cisco Unified Serviceability
Cisco Unified Communications Manager Release 6.0(1) provides the following enhancements to Serviceability:
•Serviceability Administration
•Cisco Unified Real-Time Monitoring Tool
•Cisco Unified Communications Manager CDR Analysis and Reporting
•Call Detail Record Definitions
•Cisco Dialed Number Analyzer
Tip In previous releases of Cisco Unified Communications Manager, the system generated the DBReplicationFailure alert based on the DBReplicationFailure alarm. In Cisco Unified Communications Manager 6.0(1), the DBReplicationFailure alert gets generated when the value for the Replication_State performance monitoring counter specifies 1, 3, or 4. No alert gets generated if the value specifies 0 or 2. For more information, see the "Number of Replicates Created and State of Replication" section.
Serviceability Administration
Cisco Unified Serviceability allows you to perform such tasks as configuring trace parameters, configuring alarms, and activating, starting, and stopping services for Cisco Unified Communications Manager.
GUI Changes
The Cisco Unified Serviceability GUI contains the following changes for this release:
•Serviceability Administration name change—The serviceability administration GUI name changed from Cisco Unified CallManager Serviceability to Cisco Unified Serviceability.
•System Alarm Catalog (new)—The System Alarm Catalog, which displays in the Alarms Messages Definition window (Alarms > Definitions), contains the following alarm catalogs: ClusterManagerAlarmCatalog, DBAlarmCatalog, DRFAlarmCatalog, GenericAlarmCatalog, JavaApplications, LoginAlarmCatalog, LpmTctCatalog, RTMTAlarmCatalog, SystemAccessCatalog, ServiceManagerAlarmCatalogs, TFTPAlarmCatalog, and TestAlarmCatalog.
The MLAAlarmCatalog, which was introduced in Release 4.2(3), no longer exists in Cisco Unified Serviceability. The LoginAlarmCatalog (new) replaces the MLAAlarmCatalog, and the AuthenticationFailed alarm replaces the MLAUserLoginFailed alarm. The LoginAlarmCatalog contains all login-related alarm definitions, including the AuthenticationFailed alarm. For information on this alarm, search for the alarm (Alarms > Definitions) and click the alarm name after it displays. In addition, the clusterwide precanned alert, AuthenticationFailed, now replaces MLAUserLoginFailed. AuthenticationFailed gets triggered when the alarm threshold is met, so the system sends an e-mail or page.
The ClusterManagerAlarmCatalog (new) contains all cluster manager alarm definitions that are related to the establishment of security associations between nodes in a cluster. The Service Manager Alarm Catalogs contains all service manager alarm definitions that are related to the activation, deactivation, starting, restarting, and stopping of services. The SystemAccess Catalog (new) contains all alarm definitions that are used for tracking whether SystemAccess provides all thread statistic counters together with all the process statistic counters. The Cisco Unified Serviceability Administration Guide describes all other preceding catalogs, which existed in previous releases.
CallManager Alarm Catalog (changed)—The CallManager Alarm Catalog, which displays in the Alarms Messages Definition window (Alarms > Definitions), contains the following alarm catalogs: CDRRepAlarm Catalog, CEFAlarmCatalog, CMIAlarmCatalog, CtiManagerAlarmCatalog, IpVmsAlarmCatalog, and TCDSRVAlarm Catalog. The Cisco Unified Serviceability Administration Guide describes all preceding catalogs, which existed in previous releases.
•Services Group drop-down list box (new)—This setting displays in the Alarm Configuration and Trace Configuration windows (Alarm > Configuration and Trace > Configuration). Cisco Unified Serviceability categorizes services into groups. Before you can configure a trace or alarm for a service, you must choose the service group for the service that you want to configure for trace or alarms. After you choose the service group, you can choose the service from the Service drop-down list box.
Refer to the "Configuring Alarms" and "Configuring Trace" chapters in the Cisco Unified Serviceability Administration Guide for a list of services that correspond to the service groups that are used in alarm and trace configuration.
•In the Control Center—Feature Services and Control Center—Network Services windows (Tools > Control Center...), the Start Time (new) and Up Time (new) columns display. The Start Column displays when the services last started, and the Up Time column displays the time that the service has been running.
•Check All Services check box (new)—If you want to activate all services that display in the Service Activation window (Tools > Service Activation), check this check box.
Administration Configuration Tips
The following comprise the administration configuration tips for this release.
•In Cisco Unified Communications Manager 6.0(1), you can log in directly to Cisco Unified Serviceability (without first logging in to Cisco Unified Communications Manager Administration). In Netscape 7.1 or Internet Explorer 6.0, enter https://<server name or IP address>:8443/ccmservice/, where server name or IP address equals the server where the Cisco Unified Serviceability service runs, and 8443 equals the port number for HTTPS.
After you log in to Cisco Unified Serviceability, you can access all applications that display in the Navigation drop-down list box, except the Cisco Unified Communications Operating System Administration or Disaster Recovery System, without having to log in to each application. You cannot access the Cisco Unified Communications Operating System or Disaster Recovery System GUIs with the same password that you use to log in to Cisco Unified Serviceability. To access these applications from Cisco Unified Serviceability, you must click the Logout link in the upper, right corner of the Cisco Unified Serviceability window; then, choose the application from the Navigation drop-down list box and click Go.
If you have already logged in to one of the applications that display in the Navigation drop-down list box (not Cisco Unified Communications Operating System Administration or Disaster Recovery System), you can access Cisco Unified Serviceability without logging in; from the Navigation drop-down list box, choose Cisco Unified Serviceability; then, click Go.
•In previous releases, two guides supported Cisco Unified Communications Manager Serviceability: the Cisco Unified CallManager Serviceability System Guide and the Cisco Unified CallManager Serviceability Administration Guide. In Cisco Unified Communications Manager 6.0(1), refer to the Cisco Unified Serviceability Administration Guide for descriptive and procedural information on how to configure Cisco Unified Serviceability.
The Cisco Unified Serviceability Administration Guide does not contain detailed information on the Real-Time Monitoring Tool (RTMT). For information on how to use RTMT, refer to the Cisco Unified Communications Manager Real-Time Monitoring Tool Administration Guide.
Service Enhancements
Cisco Unified Communications Manager Release 6.0(1) includes the following enhancements for services:
•The Cisco Unified Voice Access Service, a new feature service that exists under the CM Service group, starts the mobile voice access capability within Cisco Unified Mobility; mobile voice access, which is an integrated voice response (IVR) system, allows Cisco Unified Mobility users to perform the following tasks:
–Make calls from the cellular phone as if the call originated from the desk phone.
–Turn Cisco Unified Mobility on; turn Cisco Unified Mobility off.
For mobile voice access to work, you must activate the service, which you do on one server in the cluster after you configure the H.323 gateway to point to the first VXML page. In addition, make sure that the Cisco CallManager and the Cisco TFTP services run on one server in the cluster, not necessarily the same server where the Cisco Unified Voice Access Service runs.
•In the Control Center—Feature Services and Control Center—Network Services windows, the Start Time and Up Time columns display.
•Cisco Unified Serviceability displays the Service Groups drop-down list box, which is described in the "GUI Changes" section.
•For information on stopping and starting some services through the command line interface (CLI), refer to the Cisco Unified Communications Operating System Administration Guide.
New Service Parameters
This parameter specifies the maximum number of Processes and Threads that is allowed for SystemAccess to provide the complete Process and Thread statistics counters. If the total number of Processes/Threads exceeds this maximum number, SystemAccess only provides up to the maximum number of Processes statistics counters and ccm Thread (if running) statistics counters. The system provides no other Thread statistics counters.
To configure the maximum number of processes and threads, access the Maximum Number of Process and Threads service parameter for the Cisco RIS Data Collector service in Cisco Unified Communications Manager Administration. Click the hyperlink for the parameter name to display the question mark help, which contains more information on the parameter, including the default value.
AXL Considerations
For information on the AXL Serviceability API, refer to the Cisco Unified Communications Manager Developers Guide for Release 6.0.
Where to Find More Information
•Cisco Unified Serviceability Administration Guide
•Service Parameters Configuration, Cisco Unified Communications Manager Administration Guide
•Cisco Unified Communications Manager Developers Guide for Release 6.0
•Cisco Unified Communications Operating System Administration Guide
Cisco Unified Real-Time Monitoring Tool
Cisco Unified Communications Manager 6.0 includes the following changes to the Cisco Unified Communications Manager Real-Time Monitoring Tool (RTMT):
•Trace and Log Central added an option that allows you to collect installation and upgrade log files on your local computer.
•The new LogFileSearchStringFound alert replaces the TraceCollectionToolEvent alert. If you want to generate an alarm when the specified search string exists in a monitored trace file, enable the LogFileSearchStringFound alert.
•The new CpuPegging alert replaces the NonCallProcessingNodeCpuPegging alert. The existing threshold setting for NonCallProcessingNodeCpuPegging does not get preserved, but the default CPU threshold settings for CpuPegging will remain the same as the NonCallProcessingNodeCpuPegging alert.
•RTMT added the following performance objects:
–Cisco MGCP BRI Device—The Cisco Media Gateway Control Protocol (MGCP) Foreign Exchange Office (FXO) Device object includes performance counters with information about registered Cisco MGCP BRI devices.
–Cisco MobilityManager—The Cisco Mobility Manager object includes performance counters with information on registered Cisco Unified Mobility Manager devices.
–Cisco SIP Station—The Cisco SIP Station object includes performance counters with information about registered Cisco SIP Stations.
–Cisco Signaling Performance—The Cisco Signaling Performance object provides call signaling data on transport communications on Cisco Unified Communications Manager.
•RTMT added the following performance counters (object):
–SIPTrunkAuthorizationFailures (Cisco CallManager)
–SIPTrunkAuthorizations (Cisco CallManager)
–CallsRejectedDueToICTCallThrottling (Cisco H.323)
–CCBsAllocated (Cisco SIP Stack)
–PublishIns (Cisco SIP Stack)
–PublishOuts (Cisco SIP Stack)
–SCBsAllocated (Cisco SIP Stack)
–SIPHandlerSDLQueueSignalsPresent (Cisco SIP Stack)
–SIPGenericCounter1 through SIPGenericCounter4 (Cisco SIP Stack)
GUI Changes
The following comprise the GUI changes included in this release.
•The name of the Cisco Unified CallManager Real-Time Monitoring Tool changed to Cisco Unified Communications Manager Real-Time Monitoring Tool.
•The reorganized user interface for Cisco Unified Communications Manager Real-Time Monitoring Tool represents a directory tree under different tabs based on whether you are interested in monitoring the system and server object or whether you are monitoring objects that are related to Cisco Unified Communications Manager. You can access the following tabs by clicking on the quick launch channel on the left pane of the RTMT window.
–The System tab includes tools that help you monitor predefined system objects—System Summary, CPU and Memory Usage, Process, Disk Usage, Critical Services, Performance, Performance Log Viewer, Alert Central, Trace & Log Central (formerly known as Trace Collection Tools), and SysLog Viewer.
–The CallManager tab includes tools that help you monitor predefined Cisco Unified Communications Manager objects—Communications Manager Summary, Call Activity, Gateway Activity, Trunk Activity, SDL Queue, SIP Activity, Device summary, Device Search, Phone Summary, Cisco TFTP, Heartbeat, Database, Summary, CTI Manager, CTI search.
–RTMT adds icons to the directory trees for plug-ins, such as Voice Log Translator (VLT) application, that get installed on RTMT.
•Critical Services now comprise groups based on whether the service is a System service or Cisco Unified Communications Manager (CallManager) service. RTMT displays the status of each service in the window when you click the appropriate tab.
•Alerts now comprise groups based on whether the alert is a System alert, a Cisco Unified Communications Manager (CallManager) alert, or a user-defined alert. RTMT displays alert status in the window when you click the appropriate tab. User-defined alerts represents custom alerts.
•The System Summary window now includes an alert history table.
Administration Configuration Tips
The following comprise the administration configuration tips for this release.
•When you collect or view a trace file or dump file for a particular service in Trace and Log Central, you will find that the services are grouped based on whether the service is a system service or a Cisco CallManager service.
•When you select a trace file for viewing by using the Remote Browse feature in Trace and Log Central, you can now choose the RTMT, and you can choose the type of viewer that you would like to use to display the file.
•The local Browse feature in Trace and Log Central allows you to choose one of the Cisco-provided viewers, like the Cisco Generic Viewer or another program, as the default viewer of your choice for viewing the log files with that file extension.
Where to Find More Information
•Cisco Unified Communications Manager Real-Time Monitoring Tool Administration Guide
•Cisco Unified Serviceability Administration Guide
Cisco Unified Communications Manager CDR Analysis and Reporting
The Cisco Unified Communications Manager CDR Analysis and Reporting (CAR) application generates reports for calls on the basis of call detail records (CDRs) and call management records (CMRs). For this release, the following changes apply to CAR:
•When a logged-in Cisco Extension Mobility user makes a call, CAR uses the user ID that is configured for the Cisco Extension Mobility user in all reports that display a user ID. When the call is made by a non-Cisco Extension Mobility user (or logged-out Cisco Extension Mobility user) and when the call is made with a device that does not have a configured Owner User ID, CAR uses the default user ID, unspecifieduser, in the report.
•CDR Search includes several changes:
–Mobility and Silent Monitoring and Recording calls comprise additions as new call features. The resulting CDR Search report window will show the new call types in the CallType column.
–The origConversationID and callSecuredStatus fields display in the CDR detail reports.
•A Busy Hour Call Completion (BHCC) number with the percentage of traffic during the busy hour now displays in the header of the Traffic Summary (hour of day) report.
•Application users that have been added to the Standard CAR Administration group as a CAR Administrator can log in to CAR as an administrator with access to all CAR reports except the Individual Bill Report. If non-CAR Administrator application users try to log in, the following message displays: "Either the User Name or the Password entered is invalid. Ensure that you are logging into CAR as a CAR administrator or a regular End User."
•The CAR Loader feature redesign for Cisco Unified Communications Manager Release 6.0(1) improves the overall CAR loader performance. The loading rate of CDRs and CMRs into the CAR database improved. A new option exists to load only CDRs into the CAR database and not load the CMRs. The CAR Loader will now load all CDRs into the CAR database first, and those CDRs will get updated with the CMR information after all CDRs within the same date are loaded into the database. Also, a new Unfinished-Processing-File-Recovery capability allows the CAR Loader to recover loading unfinished-processing CDR/CMR flat files properly.
•When administrators configure phones from Cisco Unified Communications Manager Administration and do not specify the Owner User ID, the CAR Loader cannot determine the user_id that is associated with the device during load. For all these calls, CAR will assign the value of "unspecifieduser" to the user_id column of the CAR database. When you run a report, you will see a user that is called _unspecifieduser in the CAR reports.
•CAR now supports the new error codes that the Identity Management System (IMS) returns and the corresponding error messages. The user sees the appropriate error message on the CAR Invalid Logon window.
•New CAR report algorithms that have been implemented reduce the user-selected date and time range, so the number of records in the newly narrowed date and time range fall between 5000 and 10,000 records for PDF reports, between 20,000 and 30,000 records for CSV reports, and between 100 and 200 records for CDR Search reports. The narrowed date and time range that get returned from the algorithm provides the basis for report generation, and not the user-selected date and time range that users input.
•Under Device Reports, changes reduce the number of gateways that can be searched in the Gateway Utilization Report from 15 to 5. The manner of calculating the gateway utilization also changed. Gateway utilization now gets calculated based on the duration of calls instead of the number of calls.
•The method for configuring the H.323 Gateway Utilization report changed. The Cisco Unified Communications Manager database stores no port information for H.323 gateways. You must obtain the H.323 gateway port information from the Gateway Configuration window in CAR. Choose System > System Parameters > Gateway Configuration to configure the H.323 gateway ports.
•This change applies mainly to H.323 gateways and to any other gateways that have no port information available in the Cisco Unified Communications Manager database. The Cisco Unified Communications Manager database includes port information for most of the other types of gateways.
•When the Forced Authorization Code (FAC) feature is invoked, the authorizationCodeValue field gets written into the CDR. To display the authorizationCodeValue field information in the CDR, ensure the "Display FAC in CDR" service parameter is set to True. The default value of the parameter specifies False.
GUI Changes
The CAR GUI contains the following changes for this release:
•The CDR Search changed to select the date and time in Coordinated Universal Time (UTC) format (date and time in which the files were generated on the server) as opposed to prior releases that were based on local date and time.
•The CDR Search window adds Mobility and Silent Monitoring and Recording to the CallType column.
•The CAR Loader changed to add Mobility and Silent Monitoring and Recording to the call types.
•When the CAR administrator configures the CAR Loader through System > Scheduler > CDR Load, the administrator can use two new options that are available. The first option, Load CDR Only, allows the administrator to choose not to load the CMRs into the CAR database. The second option, Continuous Loading 24/7, allows the administrator to immediately start the CAR Loader and let it run continuously 24 hours a day, 7 days a week, to load CDR/CMR records in near real-time fashion.
•The Gateway Utilization Report found in the Device Reports changes the maximum number of gateways, route groups/line groups, route lists/hunt lists, route patterns/hunt pilots, and voice mail ports from 15 to 5.
Administration Configuration Tips
Use the following tip to configure and use CAR:
•When you configure the time range for CDR Search, use UTC. Likewise, when you configure the date and time range settings for CDR Search, configure the settings, so the number of CDR results does not exceed 15,000. If the results exceed 15,000, CDR search cannot occur, and a message displays that you must revise the settings.
Where to Find More Information
•Cisco Unified Communications Manager CDR Analysis and Reporting Administration Guide
•Cisco Unified Serviceability Administration Guide
Call Detail Record Definitions
This section describes the changes to the CDRs and CMRs with this release.
•With Cisco Unified CallManager Release 4.2(1), you can configure Cisco Unified CallManager to report the directory number (DN) of the hunt group member who answered a direct call to the hunt pilot number in the final called party number field in the CDR. Previously, Cisco Unified CallManager reported the hunt pilot DN in the final called party number field in the CDR.
•Cisco Unified CallManager Release 4.2(3) provides advanced ad hoc conference enhancements including the addition of the origConversationID field to the CDR.This field identifies the conference ID that is associated with the originating leg of the call. In most cases, this field equals 0. Default equals 0. The destConversationID field was added in previous releases. For conference chaining scenarios, the origConversationID and destConversationID fields identify which conferences are chained together.
The requestor party (party that requested the removal of a participant) appears in the CDR comment field to track the drop requestor because the requestor can be a participant other than the controller. The following tags apply for the originator information: ConfRequestorDn and ConfRequestorDeviceName. The tags for the drop requestor information include DropConfRequestorDn and DropConfRequestorDeviceName.
•Cisco Unified Communications Manager Release 6.0(1) eliminates CDR Configuration Enterprise Parameters that were available in previous releases. To locate the CDR Configuration Enterprise Parameters, open Cisco Unified CallManager Administration and choose System > Enterprise Parameters. The release eliminates the following parameters:
–Local CDR Path
–Primary CDR UNC Path
–CDR Format
–Primary CDR DSN
•Cisco Unified Communications Manager Release 6.0(1) supports the Call Monitoring and Call Recording features. No new CDR fields exist for these features. A CDR gets generated by using existing fields. For both monitoring and recording, the monitoring and recording calls have one-way media. The media fields remain empty for one side of the call for one-way media CDRs.
Two new redirect reasons exist:
–SS_RFR_RECORDING (value = 354)
–
