 Feedback
|
Table Of Contents
Release Notes for Cisco Unified CallManager Release 5.1(1c)
Determining the Software Version
Error Message Displays Post-Installation on IBM 7835-I2 and 7845-I2 Servers
Error Message Displays Post-Installation on the Dell PE2950 Server
CSCsh58558 BIOS Flash Not Forced
CSCsh50712 IBM 7835I2 Server BIOS Flash Files Corrupt
CSCsh50685 IBM BIOS MTM Change
CSCsh20023 Some Browsers and WinZip
Cisco Unified CallManager Release 5.1(1) Documents
Upgrading from Cisco Unified CallManager Release 5.0(4) to Release 5.1(1x)
MTP and Cisco Unified SIP IP Phones
Cisco Unified Communications Answer File Generator
Using SIP Trunks Between Release 4.x and 5.x Systems
Configuring SIP Phones With Same Directory Number
CSCtj61834 MLPP Default Domain Name Displays MLPP ID Value
New and Changed Information for Cisco Unified CallManager Release 5.1(1c)
New and Changed Information for Cisco Unified CallManager Release 5.1(1b)
New and Changed Information for Cisco Unified CallManager Administration
Cisco Unified CallManager Installation
General Administration Enhancements
Cisco Unified CallManager Administration Menu Updates
Third-Party SIP Phone Enhancements
Phone Configuration Enhancements
Phone Button Configuration Enhancements
License Capabilities Assignment
Phone Configuration—Product-Specific Configuration Changes
Additional Corporate Directory Support
New and Changed Information for Cisco Unified Communications Operating System Administration
New CLI Commands and Command Options
New and Changed Information for Cisco Unified CallManager Features
Arabic Language (right to left) Support
New and Changed Information for Cisco Unified CallManager Applications
DirSync Application Enhancements
New and Changed Information for Cisco Unified CallManager Bulk Administration Features
New and Changed Information for Cisco Unified CallManager Security Features
TFTP Exclude Digest Credentials Check Box Display
Upgrading Cisco Unified IP Phones to Authenticate with LSCs Not MICs
New and Changed Information for Cisco Unified CallManager Serviceability
Cisco Unified CallManager Serviceability Administration
Cisco Unified CallManager Real-Time Monitoring Tool (RTMT)
Cisco Unified CallManager Analysis and Reporting (CAR)
New and Changed Information for Third-Party API
New and Changed Information for Cisco Unified IP Phones
Setting the Cisco Unified Communications Manager MTU Size
Description of the Reset Button
Automated Alternate Routing (AAR) Limitation with Remote Gateways
Searching for a Device in RTMT with the Any Status Option
Planning Your Software MTP Configuration
Ad Hoc Conference Settings Restrictions for SIP Phones
Time-of-Day Routing Chapter Omits Information About Defined Time Periods
Servers That Support Cisco Unified CallManager 5.0(3)
Cisco Emergency Responder 1.3(1a)
Updated Voice Gateway Model Information
Obtaining Documentation, Obtaining Support, and Security Guidelines
Cisco Product Security Overview
Release Notes for Cisco Unified CallManager Release 5.1(1c)
Updated October 3, 2011
This release of Cisco Unified CallManager adds support for the IBM 7835-I2 and 7845-I2 servers only. This release adds no new features and no defects are resolved.
Two Important Notes exist for this release, "Error Message Displays Post-Installation on IBM 7835-I2 and 7845-I2 Servers" section and "Error Message Displays Post-Installation on the Dell PE2950 Server" section.
One document omission exists for this release, "Automated Alternate Routing (AAR) Limitation with Remote Gateways" section
Note
To view the release notes for previous versions of Cisco Unified CallManager, choose the Cisco Unified CallManager 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 CallManager, Cisco recommends that you review the "Important Notes" section for information about issues that may affect your system.
Caution
Ensure that all nodes in a cluster run the same Cisco Unified CallManager.5.1(1) release. Do not install Cisco Unified CallManager Release 5.1(1c) and Cisco Unified CallManager Release 5.1(1x) on the same cluster.
Note also that this release does not contain many of the fixes that are present in the 5.1(1x) Engineering Specials. If you have installed an ES in the past, you will lose many of the fixes contained in that ES by applying this patch.
Contents
These release notes discuss the following topics:
•
•
•
Introduction
Cisco Unified CallManager, a network business communication system, provides high-quality telephony over IP networks. Cisco Unified CallManager enables the conversion of conventional, proprietary, circuit-switched PBXs to multiservice, open LAN systems.
System Requirements
Following are the system requirements for Cisco Unified CallManager Release 5.1(1c).
•
•
•
Supported Platforms
To find which servers support the Cisco Unified CallManager 5.1(1x) release, refer to the Guide to Cisco CallManager Upgrades and Server Migrations at http://www.cisco.com/en/US/partner/products/hw/voiceapp/ps378/prod_brochure_list.html
Determining the Software Version
To determine the software version of Cisco Unified CallManager, open Cisco Unified CallManager Administration. The following information displays:
•
•
Cisco recommends that you connect each Cisco Unified CallManager node to an uninterruptible power supply (UPS) to provide backup power and protect your system against a power failure.
Upgrading System Software
You can access the latest software upgrades for Cisco Unified CallManager 5.1 on Cisco.com. Table 1 lists the URLs from which you download the software.
Table 1 Download URLs for Software Upgrades
Cisco Unified CallManager 5.1
Locale installers
http://www.cisco.com/kobayashi/sw-center/telephony/callmgr/ locale-installer.shtm
Phone firmware
http://www.cisco.com/pcgi-bin/tablebuild.pl/ip-7900ser
http://www.cisco.com/pcgi-bin/tablebuild.pl/ip-7900ser-crypto
Cisco Security Agent (CSA)
Upgrade Assistant
http://www.cisco.com/pcgi-bin/tablebuild.pl/callmgr-utilpage
Related Documentation
The documentation that supports Cisco Unified CallManager Release 5.1(1c) comprises existing release 5.0(4) documentation that is listed in the Cisco Unified CallManager Release 5.1(1) Documentation Guide, as well as the following new release 5.1(1) documents:
Cisco Unified CallManager New and Changed Information Guide, Release 5.1(1)
Release 5.1(1c) Release Notes for Cisco Unified CallManager
Upgrading Cisco Unified CallManager, Release 5.1(1)
Installing Cisco Unified CallManager, Release 5.1(1)
Data Migration Assistant Administration Guide, Release 5.1(1)
Cisco Unified Communications Operating System Administration Guide, Release 5.1(1)
Cisco Unified Communications Locale Installer Release Notes for Cisco Unified CallManager, Release 5.1
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 CallManager 5.1(1) as part of Unified Communications System Release 5.1(1) testing, see http://www.cisco.com/univercd/cc/td/doc/systems/unified/uc511/relnotes/rnipt511.htm
For a list of Software and Firmware versions of contact center components that were tested for interoperability with Cisco Unified CallManager 5.1(1) as part of Unified Communications System Release 5.1(1) testing, see http://www.cisco.com/univercd/cc/td/doc/systems/unified/uc511/relnotes/rnipc511.htm.
Note
Important Notes
The following section contains important information that may have been unavailable upon the initial release of documentation for Cisco Unified CallManager Release 5.1(1x).
Important Notes for Cisco Unified CallManager Release 5.1(1c)
•
•
Important Notes for Cisco Unified CallManager releases 5.1(1x)
•
•
•
•
•
•
•
•
•
•
•
Error Message Displays Post-Installation on IBM 7835-I2 and 7845-I2 Servers
During the POST installation process, if you see the following error message after you install this version of Cisco Unified CallManager on an IBM 7835-I2 or 7845-I2 server, you should download the BIOS flasher utility for IBM servers from cisco.com and flash the BIOS to the correct level after the installation.
The BIOS does not support the current stepping of Processor P0X
Error Message Displays Post-Installation on the Dell PE2950 Server
During the POST installation process, if you see the following error message after you install this version of Cisco Unified CallManager on a Dell PE2950 server, you should download the BIOS flasher utility for Dell servers from cisco.com and flash the BIOS to the correct level after the installation (it will be displayed during the POST screens):
Warning! No microcode update loaded for processor 1.
Warning! No microcode update loaded for processor 2.
CSCsh58558 BIOS Flash Not Forced
Hewlett Packard servers forced the BIOS flash during a fresh install if the BIOS version on the server did not match the Cisco Unified CallManager image version. This has been changed so that the BIOS does not get flashed when the server has a later (newer) BIOS than what exists on the Cisco Unified CallManager release.
CSCsh50712 IBM 7835I2 Server BIOS Flash Files Corrupt
On the Cisco 7835I2 server, in the case of a fresh software-only installation, if the server purchased from IBM has a newer BIOS version than the one bundled in Cisco Unified CallManager, the installation will fail.
Workaround
1.
2.
3.
4.
CSCsh50685 IBM BIOS MTM Change
Software only IBM servers (including 7815I2, 7825I2-2800, 7825I2-3400, 7835I1, 7835I2, 7845I1) purchased after IBM rolled out their Xcellator ordering process are impacted and the installation of Cisco Unified CallManager Release 5.1(1) will fail.
Workaround
Check with IBM about the new MTM strings of the server model you purchased, and the correct MTM string to set back for Cisco Unified CallManager installation to work.
Below is a list of what should be added for the AC1 models.
Note
To change the MTM:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
Step 10
Step 11
Step 12
Step 13
Step 14
Note
Step 15
Step 16
Step 17
CSCsh20023 Some Browsers and WinZip
When downloading the Cisco Unified CallManager upgrade patch file from cisco.com, some browsers may download files with the extension tar.gz.sgn as tar.gz.gz.
Workaround
After the patch file is downloaded, rename it with the extension.gz.sgn (in place of.gz.gz) and proceed with the install.
CSCsh50754 Do Not Install Cisco Unified CallManager Release 5.1(1) or 5.1(1a) on Hewlet Packard 78352 or 7845H2 Windmill Servers
If you install Cisco Unified CallManager Release 5.1(1) or 5.1(1a) on Hewlett Packard's 7835H2 or 7845H2 Windmill server, the server will become non-bootable.
Workaround
Do not install Cisco Unified CallManager Release 5.1(1) or 5.1(1a) on the new servers. You must install Cisco Unified CallManager Release 5.1(1b) instead.
Cisco Unified CallManager Release 5.1(1) Documents
The following Cisco Unified CallManager Release 5.1(1) books are applicable to Cisco Unified CallManager Release 5.1(1x).
•
•
•
•
•
Upgrading from Cisco Unified CallManager Release 5.0(4) to Release 5.1(1x)
During the upgrade of Cisco Unified CallManager, the server experiences high disk I/O activity. This can adversely impact call processing. In the worst case, phones that are currently registered with that Cisco Unified CallManager server may failover to their backup server. Cisco strongly recommends that you ensure that all trace levels are set to the default level on all servers in your cluster before you start the upgrade process.
Furthermore, if you have concerns that the upgrade may impact call-processing service, Cisco recommends that you perform the upgrade during off-peak hours. If you want to minimize the disruptions to the call processing service, you may choose to stop the Cisco Unified CallManager service on the server before you start the upgrade process.
As always, follow standard best practices while performing a Cisco Unified CallManager upgrade.
MTP and Cisco Unified SIP IP Phones
You can configure Cisco Unified CallManager SIP devices (lines and trunks) to always use an MTP. If the configuration parameters are set to not use an MTP (default case), Cisco Unified CallManager will attempt to dynamically allocate an MTP if the DTMF methods for the call are not compatible.
For example, SCCP phones support only out-of-band DTMF, and Cisco Unified SIP IP phones (7905, 7912, 7940, 7960) support RFC2833. Because the DTMF methods are not identical, Cisco Unified CallManager will dynamically allocate an MTP.
If, however, a SCCP phone that supports RFC2833 and out-of-band use, such as Cisco Unified IP Phone 7971, calls a Cisco Unified SIP IP Phone 7940, Cisco Unified CallManager will not allocate an MTP because both phones support RFC2833. Because the same type of DTMF method is supported on each phone, no need exists for an MTP.
Note
If you check the "MTP Required" check box you may experience problems with Cisco Unified CallManager features such as Shared Line.
When you leave this check box unchecked, Cisco Unified CallManager will still insert MTPs dynamically as needed, so you will experience no benefit from checking the "MTP Required" check box for Cisco Unified SIP IP Phones.
Although this configuration option for Cisco Unified SIP IP Phones may be removed in a future Cisco Unified CallManager release, Cisco will continue to support it for generic third-party SIP phones.
Rebuilding RAID Drives
A RAID drive may fail and may require manual intervention to rebuild one of the physical drives in a logical pair during normal Cisco Unified CallManager operation.
RAIDed disks, also termed RAID arrays, get arranged in logical pairs. A single logical pair comprises two physical drives. The system keeps the pair of drives in sync with the same data in real time to provide redundancy ultimately for data integrity and assurance. When one physical drive fails to synchronize or begins to experience read or write failures, you may need to rebuild the drive. Many things can cause the failure, but the main concern remains whether the data in a logical drive pair is compromised due to failures in one of the physical drives.
Monitoring software usually detects RAID failures, and failures get reported as a failed drive or a loss of drive redundancy. The procedure for rebuilding a failing drive follows and applies to all Cisco MCS model 7825, 7835, and 7845 servers.
First, check the status of the RAID array by using the CLI show hardware command and verify whether the Status field reads Ok or Okay. An example follows:
admin:show hardware
HW Platform : 7835I
Processors : 1
Type : Intel(R) Xeon(TM) CPU 3.06GHz
CPU Speed : 3066
Memory : 2048 MBytes
Object ID : 1.3.6.1.4.1.9.1.585
OS Version : UCOS 2.0.1.0-37
RAID Details :
Found 1 IBM ServeRAID controller(s).
Read configuration has been initiated for controller 1...
----------------------------------------------------------------------
Logical drive information
----------------------------------------------------------------------
Logical drive number 1
Status of logical drive : Okay (OKAY)
RAID level : 1
Size (in MB) : 70006
Write cache status : Temporary write through (TWT)
Number of chunks : 2
Stripe-unit size : 8 KB
Access blocked : No
Part of array : A
Array A stripe order (Channel/SCSI ID) : 1,0 1,1 Command completed successfully.
If the RAID array status field does not read Ok or Okay (for example, shows Degraded or Critical), perform the following steps:
1.
For information on how to access the console to perform CLI commands, see the Cisco Unified Communications Operating System Administration Guide.
2.
3.
4.
a.
1:ServeRAID-5i Slot 2, Logical drv=1, Firmware=7.12.07, Status=Fail
1 Drive(s) not responding or found at new location(s)
Press F2 Detailed information
F4 Retry the command
F5 Change the configuration and set the drive(s) defunct
F10 Continue without changing the configuration
b.
5.
6.
7.
8.
If the status does not read Ok or Okay, you may need to replace the physical drive.
Cisco Unified Communications Answer File Generator
Cisco Unified CallManager Release 5.1(1c) includes a web application that is called Cisco Unified Communications Answer File Generator that is used to generate answer files for unattended installations of Cisco Unified CallManager Release 5.0(1) and later. Individual answer files get copied to a USB key or a floppy diskette that accompanies the Cisco Unified CallManager DVD during the installation process.
The web application supports the following features:
•
•
•
The following usage requirements apply:
•
•
You can access the Cisco Unified Communications Answer File Generator at the following URL:
http://www.cisco.com/web/cuc_afg/index.html
The Cisco Unified Communications Answer File Generator supports Internet Explorer version 6.0 or higher and Mozilla version 1.5 or higher.
If a USB key is being used to perform an unattended installation of Cisco Unified CallManager, you may need to reformat the USB key to the FAT32 file system beforehand. You need to reformat especially in the case of USB keys with larger storage capacity (for example, 1 Gigabyte) that are formatted with the FAT file system.
You can use the Windows XP Disk Management Utility to reformat a USB key to the FAT32 file system as follows (you might need to be logged in as an administrator or a member of the Administrators group to perform these tasks):
1.
2.
3.
4.
5.
6.
7.
Using SIP Trunks Between Release 4.x and 5.x Systems
Cisco Unified CallManager Release 5.0 and later and Cisco Unified CallManager Release 4.0 and later support TCP and UDP as Transport Types when they are used with SIP trunks. However, release 4.x uses one TCP connection per SIP call; 5.x supports multiple SIP calls over the same TCP connection (referred to as TCP connection reuse).
The following Cisco products support TCP; however, not all support TCP Reuse (see Table 3 for more information):
•
•
•
•
•
•
•
Table 3 lists the SIP trunk connectivity that is supported between Cisco Unified CallManager Release 4.x and 5.x and the IOS gateway.
If a release 5.x system makes multiple calls over a TCP-based SIP trunk to a 4.x system, the 4.x system will only connect one call. The rest of the calls will not get connected.When using SIP trunks between 4.x and 5.x systems, you must configure both systems to use UDP as the Outgoing Transport Type, so calls between the release 4.x and 5.x systems will connect properly. (See Table 3.)
To configure UDP, use Cisco Unified CallManager Administration.
•
•
For more information about SIP trunks, see the Cisco Unified CallManager System Guide and the Cisco Unified CallManager Administration Guide.
Configuring SIP Phones With Same Directory Number
Cisco Unified SIP IP Phones 7906, 7911, 7941, 7961, 7970, and 7971 can support multiple lines with the same directory number in different partitions. However, configuring and using other Cisco Unified SIP IP Phones with multiple lines with the same directory number do not get supported.
CSCtj61834 MLPP Default Domain Name Displays MLPP ID Value
When you configure the MLPP Domain Name in Cisco Unified Communications Manager, the default name for MLPP Domain Name displays the MLPP ID value 000000 instead of Default as stated on the help page.
New and Changed Information for Cisco Unified CallManager Release 5.1(1c)
This release of Cisco Unified CallManager adds support for the IBM 7835-I2 and 7845-I2 servers only. This release adds no new features and no defects are resolved.
New and Changed Information for Cisco Unified CallManager Release 5.1(1b)
The following sections describe new features and changes that are pertinent to Cisco Unified CallManager, Release 5.1(1b) or later. The sections may include configuration tips for the administrator, information about users and where to find more information.
•
•
•
•
•
•
•
•
New and Changed Information for Cisco Unified CallManager Administration
The following sections describe the Cisco Unified CallManager 5.1 Administration enhancements:
•
•
•
•
•
•
•
•
Cisco Unified CallManager Installation
Cisco Unified CallManager 5.1 includes the following installation enhancements.
•
•
For more information
•
•
Data Migration Assistant (DMA) 5.1 includes the following enhancements:
•
•
For more information
•
General Administration Enhancements
The following requirements apply to Cisco Unified CallManager Administration:
•
•
Note
Service Parameter Changes
Cisco Unified CallManager 5.1 supports the following service parameter changes:
•
•
•
•
•
See the "Immediate Divert Enhancements" section for more information.
•
•
•
–
–
Cisco Unified CallManager Administration Menu Updates
The System menu in Cisco Unified CallManager Administration includes the License Capabilities option (System > Licensing > Capabilities Assignment).
Third-Party SIP Phone Enhancements
The following enhancements took place to third-party SIP phones in Release 5.1(1b):.
Third-Party SIP Phone Configuration Enhancements
The Basic and Advanced Third-Party SIP Phone Configuration windows include a check box that is called Require DTMF Reception.
Migrating from Cisco Unified CallManager Release 5.0(1), and Above, to Cisco Unified CallManager Release 5.1(1b)
In Cisco Unified CallManager Release 5.1(1b) and above, certain characteristics for Basic and Advanced Third-Party SIP Phones changed. These characteristics include changes to the Maximum Number of Calls per Device, Default Maximum Number of Calls per DN, and Default Busy Trigger per DN fields that display on the Directory Number Configuration window in Cisco Unified CallManager Administration. See the Cisco Unified CallManager New and Changed Information Guide for more information.
Phone Configuration Enhancements
Use the Phone Configuration window to configure the Cisco TelePresence and the Cisco Unified IP Phone 7906 devices. For more information on Cisco TelePresence and the Cisco Unified IP Phone 7906, see the Cisco Unified CallManager New and Changed Information Guide.
Phone Button Configuration Enhancements
Use the Phone Button Configuration window to configure the default phone button template for Cisco TelePresence and Cisco Unified IP Phone 7906 SIP and SCCP. For more information on Cisco TelePresence and the Cisco Unified IP Phone 7906, see the Cisco Unified CallManager New and Changed Information Guide.
License Capabilities Assignment
Capabilities Assignment allows system administrators to enable the Cisco Unified Presence Server (CUPS) and Cisco Unified Personal Communicator (CUPC) capabilities for users. You must ensure that licenses for CUPS and CUPC are available.
Make license capabilities assignments to existing users. Before you begin, ensure that users exist on your system by choosing User Management > End User and clicking Find.
Before you begin configuring the capabilities assignments for users, determine how many CUPS (servers and clients) and CUPC licenses are required for your system by choosing Licensing > License Unit Calculator. Acquire the required licenses by using Licensing > License File Upload. Verify the total licenses by using Licensing > License Unit Report.
Note
Call Forward Overriding
You can configure the behavior of this Cisco Unified CallManager feature via service parameter CFADestinationOverride. When the feature is enabled on Cisco Unified CallManager, it allows the CFA Target to reach the CFA Initiator for important calls. TSP application that monitors the CFA initiator will receive call as normal if the call is initiated from the CFA target.
No TSP interface change occurs for this Cisco Unified CallManager feature.
For More Information
•
•
•
•
•
•
Enterprise Parameter Changes
Cisco Unified CallManager Release 5.1 supports the following enterprise parameter changes:
•
Phone Configuration—Product-Specific Configuration Changes
The Product-Specific Configuration area of the Phone Configuration window supports a new parameter, Advertise G.722 Codec. Use this parameter to override the enterprise parameter (see Advertise G.722 Codec in the "Enterprise Parameter Changes" section) on an individual phone basis.
Use this parameter to override the enterprise parameter (see Advertise G.722 Codec in the "Enterprise Parameter Changes" section on page 1-1) on a per-phone basis
Note
Table 4 indicates how the phone responds to the configuration options.
Cisco Unified CallManager supports G.722, which is a wideband codec, as well as a propriety codec simply named Wideband. Both represent wideband codecs. For more information on wideband codec, see the "Wideband Codec" section.
How the Parameters Work with Regions
When you choose a G.711 or G.722 codec in Region Configuration you are choosing the bandwidth utilization. Choosing either codec produces the same affect. When you choose either G.711 or G.722, these codecs disallow selecting codecs that have a payload greater than 64 kbps, such as the G.722 wideband codec and Advanced Audio Codec (ACC) (when ACC uses more than one channel).
If you choose a region that is lower than G.711 or G.722, the Advertise G.722 Codec enterprise parameter gets ignored because the system does not allow G.722, G.711, AAC, and wideband.
Additional Corporate Directory Support
The DirSync application performs the synchronization of data in the Cisco Unified CallManager database with the customer LDAP directory information. DirSync allows Cisco Unified CallManager to synchronize the data from more corporate directories than with previous releases. DirSync allows synchronization from Microsoft Windows Server 2000 and Windows Server 2003 Active Directory (AD), Netscape/iPlanet Directory, Sun ONE Directory Server 5.1, and Sun Java System Directory Server 5.2 to the Cisco Unified CallManager database.
User Tips
When directory synchronization is enabled, Cisco Unified CallManager Administration cannot update any user information that is synchronized from the customer Corporate Directory.
For More Information
Cisco Unified CallManager New and Changed Information Guide, Release 5.1(1)
New and Changed Information for Cisco Unified Communications Operating System Administration
Cisco Unified Communications Operating System Administration includes the following enhancement:
•
New CLI Commands and Command Options
You now have the following new CLI commands and command options available.
–
–
–
–
–
–
–
–
–
–
–
–
–
–
•
For more information
•
New and Changed Information for Cisco Unified CallManager Features
The following sections describe the Cisco Unified CallManager 5.1 feature enhancements:
•
•
Immediate Divert Enhancements
Legacy iDivert allows diversion of a call to the voice mailbox of the party that invokes the iDivert feature. Enhanced iDivert allows diversion of a call to either the voice mailbox of the party that invokes the iDivert feature or to the voice mailbox of the original called party.
You can divert inbound calls that are in the call offering, call on hold, or call active states. You can divert outbound calls in the call active or call hold states. The diverted party receives the greeting of the voice-messaging system of the party to whom the call gets diverted.
When enhanced iDivert mode is active for incoming calls, the user to whom a call is presented can invoke Immediate Divert to divert the call either to the user voice mailbox or to the voice mailbox of the original called party. After the invoking user presses the iDivert softkey, a screen on the invoking user phone identifies both the original called party and the invoking user. The user selects one of the two names, and the call gets redirected to the voice mailbox of the selected party.
Cisco Unified CallManager Administration Configuration Tips
•
•
•
•
Service or Enterprise Parameter Changes
Immediate Divert includes the following new service parameters:
•
•
•
User Tips
Users can use iDivert to send an active, ringing, or on-hold call to their voice messaging system. Depending on the type of call and their phone configuration, users can also use iDivert to send the call to the voice-messaging system of another party.
•
•
See the Immediate Divert scenarios in the Cisco Unified CallManager New and Changed Information Guide for more information about using the enhanced Immediate Divert feature.
Cisco Unified IP Phone Support
•
•
•
•
•
•
•
•
•
•
Call Detail Records Considerations
Immediate Divert uses the Immediate Divert code number in the On behalf of fields (for example, join On behalf Of and lastRedirectRediectOnBehalfOf) in CDR.
For More Information
•
•
Call Forward All Override
The Call Forward All Override feature allows the administrator to override Call Forward All (CFA) when the target of the CFA calls the initiator of the CFA, so the CFA target can reach the initiator for important calls. In other words, when the user to whom calls are being forwarded (the target) calls the user whose calls are being forwarded (the initiator), the phone of the initiator rings instead of call forwarding back to the target. The override works whether the CFA target phone number is internal or external.
When the CFA Destination Override service parameter is set to False (the default value), no override occurs. See Service Parameters Configuration in the Cisco Unified CallManager Administration Guide for information about configuring service parameters.
Cisco Unified CallManager Administration Configuration Tips
Ensure the CFA Destination Override service parameter is set to True for CFA override to work. The default value specifies False.
Service or Enterprise Parameter Changes
The following new service parameter supports Call Forward All Override:
•
Cisco Unified IP Phone Support
•
•
•
•
•
•
•
•
•
For More Information
•
•
•
•
AAC Voice Codec Support
The Advanced Audio Codec (AAC) feature provides the following capabilities:
•
•
Cisco Unified CallManager Administration Configuration Tips
•
CAR/CDR Considerations
•
For More Information
•
Arabic Language (right to left) Support
Cisco Unified CallManager Release 5.1 supports Arabic locales on Cisco Unified CallManager user interfaces and Arabic text on phone screen displays for supported phones.
Cisco Unified IP Phones Supported
•
•
•
•
•
•
For More Information
•
New and Changed Information for Cisco Unified CallManager Applications
The following section describes the Cisco Unified CallManager 5.1 applications enhancements:
•
Music on Hold
The Music On Hold feature now supports the new service parameter, Multicast MOH Direction Attribute for SIP.
•
•
For More Information
•
DirSync Application Enhancements
The DirSync application performs the synchronization of data in the Cisco Unified CallManager database with the customer LDAP directory information. Cisco Unified CallManager administrators set up the DirSync service by first configuring the LDAP-directory-related Cisco Unified CallManager windows.
This release of Cisco Unified CallManager supports synchronization from more corporate directories than with previous releases. DirSync now allows Cisco Unified CallManager to synchronize the data from the following corporate directories to the Cisco Unified CallManager database:
•
•
•
•
For More Information
•
•
•
New and Changed Information for Cisco Unified CallManager Bulk Administration Features
Cisco Unified CallManager Bulk Administration (BAT), a web-based application, performs bulk transactions to the Cisco Unified CallManager database. This section introduces the changes to BAT for Cisco Unified CallManager Release 5.1.
Updating the Region Matrix
BAT now includes a new Region Matrix menu that allows you to populate or depopulate the region matrix. The region tables define physical locations, whereas the region matrix tables define available bandwidth within (intra) and between (inter) regions.
GUI Changes
Choose Bulk Administration>Region Matrix>Populate/Depopulate Region Matrix to update the Region Matrix.
For More Information
•
New and Changed Information for Cisco Unified CallManager Security Features
This section introduces the changes to security for Cisco Unified CallManager 5.1.
•
•
CTL Client Modifications
You can now secure a Cisco PIX Firewall as part of a secure Cisco Unified CallManager system. To secure a firewall, configure the firewall, which acts as a TLS proxy server, in the CTL client. After the firewall certificate gets added to the CTL client file, the firewall can inspect packets, detect threats, and perform NAT/Firewall transversal even on Cisco Unified CallManager systems with security enabled.
This release also adds CTL support for a Cisco Unified CallManager supercluster: sixteen call processing servers, one publisher, two TFTP servers, and up to nine media resource servers.
GUI Changes
The following changes to Cisco CTL client apply to secure firewall support:
To configure a PIX firewall in the CTL client, click the Add Firewall button in the CTL Entries window. After you enter the Hostname or IP Address, Port, Username, Password, and press Next, the CTL client authenticates the proxy server with the username and password before adding its certificate to the CTL file.
Cisco Unified CallManager Administration uses an etoken to authenticate the TLS connection between the Cisco CTL client and provider before sending the CTL file to the firewall server.
•
TFTP Exclude Digest Credentials Check Box Display
Only Cisco Unified IP SIP Phone 7905, 7912, 7940, and 7960 display the TFTP Exclude Digest Credentials in Configuration File check box in the phone security profile window. Only these phones fully support this option.
Use this option to exclude digest credentials from the configuration file that is sent to phones after the initial configuration. You may need to uncheck this check box to update the configuration file for changes to digest credentials.
Upgrading Cisco Unified IP Phones to Authenticate with LSCs Not MICs
Cisco supports LSCs to authenticate the TLS connection with Cisco Unified CallManager. Cisco recommends using manufacturer-installed certificates (MICs) for LSC installation only. Because MIC root certificates can be compromised, customers who configure phones to use MICs for TLS authentication or for any other purpose do so at their own risk. Cisco assumes no liability if MICs are compromised.
Cisco recommends upgrading Cisco Unified IP Phone 7906, 7911, 7941, 7961, 7970, and 7971 to use LSCs for TLS connection to Cisco Unified CallManager and removing MIC root certificates from the CallManager trust store to avoid possible future compatibility issues. Some phones that use MICs for TLS connection to Cisco Unified CallManager may not be able to register.
Administrators should remove the following MIC root certificates from the CallManager trust store: CAP-RTP-001
CAP-RTP-002
Cisco_Manufacturing_CA
Cisco_Root_CA_2048
MIC root certificates that stay in the CAPF trust store get used for certificate upgrades. For information on updating the Cisco Unified CallManager trust store and managing certificates, refer to the Cisco Unified Communications Operating System Administration Guide, Release 5.1(1).For More Information
•
•
•
New and Changed Information for Cisco Unified CallManager Serviceability
The following serviceability applications include updates for Cisco Unified CallManager Release 5.1(1b):
•
•
•
Cisco Unified CallManager Serviceability Administration
The Cisco Unified CallManager Serviceability GUI allows you to perform such tasks as configuring trace parameters, configuring alarms, and activating, starting, and stopping services.
GUI Changes
The Cisco Unified CallManager Serviceability GUI contains the following enhancements for Cisco Unified CallManager Release 5.1(1b):
•
–
–
–
–
–
–
Serviceability Administration Configuration Tips
Leaving Troubleshooting trace enabled for a long time increases the size of the trace files and may impact the performance of the services.
For More Information
•
•
Cisco Unified CallManager Real-Time Monitoring Tool (RTMT)
Cisco Unified CallManager includes the following enhancements for Cisco Unified CallManager Release 5.1(1b):
•
•
•
For More Information
•
•
Cisco Unified CallManager Analysis and Reporting (CAR)
Cisco Unified CallManager Analysis and Reporting (CAR), which is an application that allows you to run reports for Quality of Service (QoS), traffic, billing information, and so on, includes the following enhancements for Cisco Unified CallManager Release 5.1(1b):
•
•
CAR Configuration Tips
When you configure the time range for CDR Search, use Coordinated Universat Time (UTC). Likewise, when you configure the date and time range settings for CDR Search, configure the settings, so the number of CDR results do not exceed 15,000. If the results exceed 15,000, CDR search cannot occur, and a message displays that you must revise the settings.
For More Information
•
•
•
New and Changed Information for Third-Party API
This following sections describe new features and changes that are pertinent to this release of Cisco Unified CallManager and third-party APIs.
AXL Programming
AXL APIs
The following list provides AXL API calls that are new in Cisco Unified CallManager Release 5.1:
•
•
•
•
These APIs add and update credentials (passwordreserve) in siprealm.
New AXL Service Parameter
Cisco Unified CallManager Administration 5.1 release adds a new service parameter, Send Valid Namespace in AXL Response, under the Cisco Database Layer Monitor service. This parameter determines the namespace that gets sent in the AXL response from Cisco Unified CallManager.
When this parameter specifies True, Cisco Unified CallManager sends the valid namespace (that is, http://www.cisco.com/AXL/API/1.0) in the AXL response, so the namespace matches the AXL schema specification.
If the parameter specifies False, Cisco Unified CallManager sends an invalid namespace (that is, http://www.cisco.com/AXL/1.0) in the AXL response, which does not match the AXL schema specification.
The default service parameter value specifies False to maintain backward compatibility with the AXL response in the Cisco Unified CallManager 5.0 release. Cisco recommends that you set this parameter to True, so Cisco Unified CallManager sends the valid namespace.
WebDialer Requirements
Cisco Unified CallManager Release 5.1 includes the following change to Cisco Unified CallManager WebDialer:
•
Developers should format Redirector and WebDialer requests to use HTTPS. Cisco Unified CallManager requires the secured protocol to prevent unauthorized applications from reading user data.
For More Information
•
•
New and Changed Information for Cisco Unified IP Phones
The following section describes the enhancements for Cisco Unified IP Phones:
Wideband Codec
Wideband codecs such as G.722 provide a superior voice experience because wideband frequency response is 200 Hz to 7 kHz compared to narrowband frequency response of 300 Hz to 3.4 kHz. At 64 kbps, the G.722 codec offers conferencing performance and good music quality.
When users use a headset that supports wideband, they experience improved audio sensitivity when the wideband setting on their phones is enabled (it is disabled by default). To access the wideband headset setting on the phone, users choose the Settings icon > User Preferences > Audio Preferences > Wideband Headset. Users should check with their system administrator to be sure their phone system is configured to use G.722 or wideband. If the system is not configured for a wideband codec, they may not detect any additional audio sensitivity, even when they are using a wideband headset.
The following Cisco Unified IP Phones (both SCCP and SIP protocols) support the wideband codec G.722 for use with a wideband headset:
•
•
•
•
•
•
For more information about the administration settings for wideband codecs, see the "Enterprise Parameter Changes" section and the "Phone Configuration—Product-Specific Configuration Changes" section.
Caveats
The following sections contain information on how to obtain the latest resolved caveat information and descriptions of open caveats of severity level 1, 2, and 3.
Caveats describe unexpected behavior on a Cisco Unified CallManager server. Severity 1 caveats represent the most serious caveats, severity 2 caveats represent less serious caveats, and severity 3 caveats represent moderate caveats.
Resolved Caveats
You can find the latest resolved caveat information for Cisco Unified CallManager Release 5.1(1c) by using Bug Toolkit, which is an online tool that is available for customers to query defects according to their own needs.
Tip
To access the Bug Toolkit, log on to http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl.This section includes the following topics:
Using Bug Toolkit
Known problems (bugs) are graded according to severity level. These release notes contain descriptions of:
•
•
You can search for problems by using the Cisco Software Bug Toolkit.
To access Bug Toolkit, you need the following items:
•
•
•
To use Bug Toolkit, follow these steps:
Procedure
Step 1
Step 2
Step 3
Note
Open Caveats
Table 5 describes possible unexpected behaviors in Cisco Unified CallManager Release 5.1(1x), which are sorted by component.
Tip
Understanding the Fixed-in Version and the Integrated-in Fields in the Online Defect Record
When you open the online record for a defect, you may see data in the "First Fixed-in Version" or "Integrated-in" fields. The information that displays in these fields identifies the list of Cisco Unified CallManager interim versions in which the defect was fixed. These interim versions then get integrated into Cisco Unified CallManager releases.
Some more clearly defined versions include identification for Engineering Specials (ES) or Service Releases (SR); for example 03.3(04)ES29 and 04.0(02a)SR1. However, the version information that displays for the Cisco Unified CallManager maintenance releases may not be as clearly identified.
The following examples show how you can decode the maintenance release interim version information. These examples show you the format of the interim version along with the corresponding Cisco Unified CallManager release that includes that interim version. You can use these examples as guidance to better understand the presentation of information in these fields.
•
•
•
•
Note
Tip
.
Documentation Updates
This section provides documentation changes that were unavailable when the Cisco Unified CallManager release 5.1(1b) documentation suite was released.
Omissions
This section provides information that was not included in the Cisco Unified CallManager Release 5.1(1x) documentation.
•
•
•
•
•
•
•
Setting the Cisco Unified Communications Manager MTU Size
The maximum transmission unit (MTU) size that you configure for Cisco Unified Communications Manager must not exceed the lowest MTU size that is configured on any link in your network.
The default MTU size is 1500. You can configure the MTU size during product installation, or by using the CLI command set network mtu.
Call Park Range
The "Call Park and Directed Call Park" chapter of the Cisco Unified CallManager Features and Services Guide omits the following information:
The call park range is selected from the list of servers where the call originates.
For example, if Phone A (registered to node A) calls Phone B (registered to Node B) and the phone B user presses Park, Phone B requires a call park range in the CSS that resides on Node A.
In a multinode environment comprised of phones and gateways talking to various nodes, where calls originating from any server may need to be parked, the phones require a CSS that contains call park ranges from all servers.
Description of the Reset Button
The Cisco Unified Communications Manager Configuration Settings section of the "System Configuration" chapter of the Cisco Unified CallManager Administration Guide contains incomplete description of the Reset button. The description should comprise:
Click this button to reset all devices that belong to the same Cisco Unified CM Group as this Cisco Unified Communications Manager server.
Note
Automated Alternate Routing (AAR) Limitation with Remote Gateways
AAR exhibits the limitation that calls routed over a remote gateway during a high-bandwidth situation fail, and the calls cannot be routed over the local gateway when AAR is used. This functionality is important to customers who use Tail-End Hop Off (TEHO) for toll bypass.
Workaround Example
Use a specific partition for the TEHO in question.
In the following example, headquarters (HQ) has area code 408 and the Branch (BR1) has area code 919.
Configure as follows:
1.
2.
3.
4.
5.
6.
Results
In an out-of-bandwidth situation, after Cisco Unified CallManager tries to allocate the first route group for TEHO (BR1 route group), Cisco Unified CM retries the second route group, at which point the system strips the 91919 string and replaces it with the 1919 string, which is suitable for long-distance dialing. Because the string is configured for use by the local gateway, less rerouting takes place.
AAR works on a per-external-phone-number-mask basis and cannot be processed for an external PSTN number because the system does not know the phone number mask of the PSTN number. This workaround provides AAR functionality and improves network resiliency.
Searching for a Device in RTMT with the Any Status Option
The Real-time Monitoring Tool chapter of the Cisco Unified CallManager Serviceability System Guide does not include the following information.
When you search for a device by choosing the any status option, RTMT does not display a snapshot of the matched device type, but rather it displays data for that device type from the RIS database for all specified Cisco Unified CallManager nodes for a period of time. As a result, you may see multiple entries of a device with multiple status (Registered, Unregistered, and so on) in RTMT. When you see multiple entries of a device, the current status of the device appears as the entry that has the latest timestamp. You can configure the time that information on unregistered or rejected device is kept in the RIS database by configuring the RIS Unused Cisco CallManager Device Store Period service parameter in Cisco RIS Data Collector service in Cisco Unified CallManager Administration. For more information on configuring service parameter, refer to the Cisco Unified CallManager Administration Guide.
Planning Your Software MTP Configuration
The Cisco Unified CallManager System Guide, Media Termination Points chapter does not include the following information:
Consider the following information when you are planning your MTP configuration:
•
Ad Hoc Conference Settings Restrictions for SIP Phones
The Conferencing chapter of the Cisco Unified CallManager System Guide does not include the following information.
Even though Cisco SIP IP Phones (7911, 7941, 7961, 7970, 7971) can create an ad hoc conference, Cisco SIP IP Phone 7940/60 and third-party SIP phones can only be participants.
The following restrictions apply to all SIP phones when ad hoc conferencing is used:
•
Time-of-Day Routing Chapter Omits Information About Defined Time Periods
The "Time-of-Day Routing" chapter of the Cisco Unified Communications Manager System Guide omits the following information.
•
Example:
Consider the following example:
•
•
In this case, on December 31st, the afterofficehours period will not be considered because it gets overriden by the more specific newyearseve period.
Updates
This section provides information that has been updated since the release of the Cisco Unified CallManager Release 5.1(1x) documentation.
Name Change
Cisco Unified CallManager Analysis and Reporting Guide, Release 5.0(4), refers to Cisco IP Manager Assistant (IPMA) instead of Cisco Unified CallManager Assistant. For each instance of Cisco IP Manager Assistant (IPMA) in this guide, replace it with Cisco Unified CallManager Assistant. To run reports for Cisco Unified CallManager Assistant in Cisco Unified CallManager Analysis and Reporting (CAR), choose User Reports > Cisco Unified CallManager Assistant > Manager Call Usage (or Assistant Call Usage). For additional information on running these reports, refer to Cisco Unified CallManager Analysis and Reporting Guide, Release 5.0(4).
Corrections
This section lists corrected information that the current version of the Cisco Unified CallManager documentation may not include:
•
•
Servers That Support Cisco Unified CallManager 5.0(3)
The document, Installing Cisco Unified CallManager 5.0(3) does not provide a complete list of servers that support Cisco Unified CallManager 5.0(3). For a list of servers that support Cisco Unified CallManager 5.0 releases, click the following URL:
http://www.cisco.com/en/US/products/hw/voiceapp/ps378/
Cisco Emergency Responder 1.3(1a)
Cisco Emergency Responder (Cisco ER) 1.3(1a) supports Cisco Unified CallManager 5.0(2) and 5.0(3) in addition to Cisco Unified CallManager 3.3 and Cisco Unified CallManager 4.0, 4.1, and 4.2.
Note
•
•
•
Changes
This section lists changed information that the current version of the Cisco Unified CallManager documentation may not include:
Updated Voice Gateway Model Information
The Understanding Cisco Unified Voice Gateways chapter in the Cisco Unified CallManager Release 5.1(1) New and Changed Information Guide contains updated information on the supported voice gateways, protocols, trunk interfaces, and port types.
Obtaining Documentation, Obtaining Support, and Security Guidelines
For information on obtaining documentation, obtaining support, providing documentation feedback, security guidelines, and also recommended aliases and general Cisco documents, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Cisco Product Security Overview
This product contains cryptographic features and is subject to United States and local country laws governing import, export, transfer and use. Delivery of Cisco cryptographic products does not imply third-party authority to import, export, distribute or use encryption. Importers, exporters, distributors and users are responsible for compliance with U.S. and local country laws. By using this product you agree to comply with applicable laws and regulations. If you are unable to comply with U.S. and local laws, return this product immediately.
A summary of U.S. laws governing Cisco cryptographic products may be found at: http://www.cisco.com/wwl/export/crypto/tool/stqrg.html. If you require further assistance please contact us by sending email to export@cisco.com.
CCVP, the Cisco logo, and the Cisco Square Bridge logo are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn is a service mark of Cisco Systems, Inc.; and Access Registrar, Aironet, BPX, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, iQuick Study, LightStream, Linksys, MeetingPlace, MGX, Networking Academy, Network Registrar, PIX, ProConnect, ScriptShare, SMARTnet, StackWise, The Fastest Way to Increase Your Internet Quotient, and TransPath are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0708R)
