Guest

Release Notes for Cisco Unified CallManager Release 5.1(1c)

  • Viewing Options

  • PDF (692.9 KB)
  • Feedback
Release Notes for Cisco Unified CallManager Release 5.1(1c)

Table Of Contents

Release Notes for Cisco Unified CallManager Release 5.1(1c)

Contents

Introduction

System Requirements

Supported Platforms

Determining the Software Version

Upgrading System Software

Related Documentation

Limitations and Restrictions

Important Notes

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

CSCsh50754 Do Not Install Cisco Unified CallManager Release 5.1(1) or 5.1(1a) on Hewlet Packard 78352 or 7845H2 Windmill Servers

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

Rebuilding RAID Drives

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

Service Parameter Changes

Cisco Unified CallManager Administration Menu Updates

Third-Party SIP Phone Enhancements

Phone Configuration Enhancements

Phone Button Configuration Enhancements

License Capabilities Assignment

Call Forward Overriding

Enterprise Parameter Changes

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

Immediate Divert Enhancements

Call Forward All Override

AAC Voice Codec Support

Arabic Language (right to left) Support

New and Changed Information for Cisco Unified CallManager Applications

Music on Hold

DirSync Application Enhancements

New and Changed Information for Cisco Unified CallManager Bulk Administration Features

New and Changed Information for Cisco Unified CallManager Security Features

CTL Client Modifications

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

AXL Programming

WebDialer Requirements

New and Changed Information for Cisco Unified IP Phones

Wideband Codec

Caveats

Resolved Caveats

Using Bug Toolkit

Open Caveats

Documentation Updates

Omissions

Setting the Cisco Unified Communications Manager MTU Size

Call Park Range

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

Updates

Name Change

Corrections

Servers That Support Cisco Unified CallManager 5.0(3)

Cisco Emergency Responder 1.3(1a)

Changes

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 Be aware that Cisco Unified CallManager Release 5.1(1c) is not an upgrade of Cisco Unified CallManager Release 5.1(1x). If you have successfully installed Cisco Unified CallManager Release 5.1(1x) on a cluster and have not experienced problems, continue using that release. If you begin to experience problems with a successfully installed Cisco Unified CallManager Release 5.1(1x) cluster, report the problems through normal channels.

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

System Requirements

Related Documentation

Important Notes

New and Changed Information for Cisco Unified CallManager Release 5.1(1c)

New and Changed Information for Cisco Unified CallManager Release 5.1(1b)

Caveats

Documentation Updates

Obtaining Documentation, Obtaining Support, and Security Guidelines

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).

2 GB of memory

72 GB disk drive

2 GHz processor

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 Unified CallManager System version

Cisco Unified CallManager Administration version

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.


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 Be aware that the release of Cisco IP telephony products does not always coincide with Cisco Unified CallManager releases. If a product does not meet the compatibility testing requirements with Cisco Unified CallManager, you need to wait until a compatible version of the product becomes available before you can upgrade to Cisco Unified CallManager release 5.1(1x). 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 CallManager Release 5.1(1x).

Important Notes for Cisco Unified CallManager Release 5.1(1c)

Error Message Displays Post-Installation on IBM 7835-I2 and 7845-I2 Servers

Error Message Displays Post-Installation on the Dell PE2950 Server

Important Notes for Cisco Unified CallManager releases 5.1(1x)

CSCsh58558 BIOS Flash Not Forced

CSCsh50712 IBM 7835I2 Server BIOS Flash Files Corrupt

CSCsh50685 IBM BIOS MTM Change

CSCsh20023 Some Browsers and WinZip

CSCsh50754 Do Not Install Cisco Unified CallManager Release 5.1(1) or 5.1(1a) on Hewlet Packard 78352 or 7845H2 Windmill Servers

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

Rebuilding RAID Drives

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

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. Download the newer BIOS version 1.03 file (ibm_fw_bios_gge123a_linux_intel32.sh) from http://www-304.ibm.com/jct01004c/systems/support/supportsite.wss/docdisplay?lndocid=MIGR-64527&brandind=5000008.

2. Copy that shell script file to the 7835I2 server and set "-x" execute permission.

3. Run the shell script file with "-s" option (for example: /ibm_fw_bios_gge123a_linux_intel32.sh -s). This will flash the BIOS to version 1.03.

4. Now you can install Cisco Unified CallManager Release 5.1(1b) and it should flash the BIOS to 1.01.

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.

Table 2 MTM Strings to add for ACl Models

Description
Current
Add

7815-I2 x206m, 1yr.

8485-7AY

8485-AC1

7815-I2 x206m, 1yr.

8485-7AY

8485-AC1

7815-I2 x206m, 3yr.

8490-7AY

8490-AC1

7825-I2 x306m (P920), 1 yr.

8849-G2Y

8849-AC1

7825-I2 x306m (P920), 1 yr.

8849-G2Y

8849-AC1

7825-I2 x306m (P920), 3 yr.

8491-G2Y

8491-AC1

7825-I2 x306m (P920), 3 yr.

8491-G2Y

8491-AC1

7825-I2 x306m (P950), 1 yr.

8849-K2Y

8849-AC1

7825-I2 x306m (P950), 3 yr.

8491-K2Y

8491-AC1

7835-I1 x346 (RoHS)

8840-3RY

8840-AC1

7845-I1 x346 (RoHS)

8840-3RY

8840-AC1

7835-I2 x3650

7979-5AY

7979-AC1



Note You must contact IBM field support or manually change the MTM string on existing servers to avoid this issue.


To change the MTM:


Step 1 Run the installation DVD.

Step 2 When the system stops with an error message regarding invalid BIOS version, press alt F2.

Step 3 A root prompt will display.

Step 4 Enter dmidecode | more and press Enter.

Step 5 Write down the Version and Release Date values.

Step 6 Enter q to exit the more command.

Step 7 Enter cd /mnt/source/Cisco/vendor/IBM/data/BIOS-Updates/<server> and press Enter.

Step 8 Enter mkdir /tmp/t and press Enter.

Step 9 Enter cp flashit.sh /tmp and press Enter.

Step 10 Enter cd /tmp and press Enter.

Step 11 Enter chmod a+x flashit.sh and press Enter.

Step 12 Enter ./flashit.sh -x /tmp/t and press Enter.

Step 13 Enter cd /tmp/t and press Enter.

Step 14 Enter ./lflash -m 8849G2U and press Enter.


Note This will change the model number on the IBM server to 8849-G2U.


Step 15 Press alt F1

Step 16 This will return you to the installation window.

Step 17 Click Cancel installation or whatever option you have to make the system shutdown. If nothing is available, then it is safe to manually shut down the server.

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).

Cisco Unified CallManager New and Changed Information Guide, Release 5.1(1)

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)

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 Cisco Unified CallManager 5.0 and later provides an "MTP Required" check box for Cisco Unified SIP IP Phones, but you should not check this check box for Cisco Unified SIP IP Phones.

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. Log in to console and enter the CLI command, utils system shutdown.

For information on how to access the console to perform CLI commands, see the Cisco Unified Communications Operating System Administration Guide.

2. When you get prompted to power off the server, press the power off button.

3. Extract the failed disk drive.

4. Power up the server (press power on button).

a. If the server is an IBM server (for example, a 7825I, 7835I, or 7845I), the following menu will display during system reboot:

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. Press F5

5. After the login prompt appears in the console window, log in and check the status of the RAID array by using the CLI show hardware command; the Status field should read Degraded or Critical.

6. Insert the failed disk drive into the original slot; be sure to lock it properly in place.

7. Check the status of the RAID array by using the CLI show hardware command; the Status field will read Rebuilding or Critical.

8. After an hour, recheck the status of the RAID array by using the CLI show hardware command and verify that the Status field reads Ok or Okay.

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:

Allows simultaneous generation and saving of answer files for unattended installs on the publisher server and all subscriber servers.

Provides syntactical validation of data entries

Provides online help and documentation

The following usage requirements apply:

The web application supports only fresh installs (for example, it does not include upgrades).

If DHCP client is being used on the publisher server, and subscriber server answer files are also being generated, you must specify the publisher server IP address.

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. Insert the USB key into a USB slot on the Windows XP PC.

2. Choose Start > Control Panel > Administrative Tools and then double-click Computer Management.

3. Expand the Storage tree and click Disk Management.

4. Right-click the Removable Disk icon and click Format. You may be asked whether you are sure that you want to format this partition; click Yes.

5. Click the File System: pull down and select FAT32.

6. Click OK. When prompted to format the volume, click OK again.

7. The Removable Disk icon text should now show the file system format as FAT32.

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):

Cisco Unified CallManager Release 4.1 - No TCP Connection Reuse

Cisco Unified CallManager Release 4.2 - No TCP Connection Reuse

Cisco Unified CallManager Release 5.0(2) - TCP Connection Reuse

Cisco Unified CallManager Release 5.0(4) - TCP Connection Reuse

Cisco Unified CallManager Release 5.1(1) - TCP Connection Reuse

Cisco IOS 12.3(8)T and above - TCP Reuse

Cisco IOS 12.3(8)T and below - No TCP Reuse

Table 3 lists the SIP trunk connectivity that is supported between Cisco Unified CallManager Release 4.x and 5.x and the IOS gateway.

Table 3  SIP Trunk Compatibility Matrix 

 
Cisco Unified CallManager Release 4.x
Cisco Unified CallManager Release 5.x
IOS 12.3(8)T
IOS 12.3(8)T Below

Cisco Unified CallManager Release 4.x

UDP/TCP

UDP only

UDP only

UDP/TCP

Cisco Unified CallManager Release 5.x

UDP only

UDP/TCP

UDP/TCP

UDP only

IOS 12.3(8)T

UDP only

UDP/TCP

UDP/TCP

UDP only

IOS 12.3(8)T Below

UDP/TCP

UDP only

UDP only

UDP/TCP


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 Cisco Unified CallManager release 5.0 and later that is connecting to a Release 4.x system, choose UDP as the Outgoing Transport Type from the SIP Trunk Security Profile Configuration window.

For Cisco Unified CallManager release 4.0 and later that is connecting to a Release 5.x system, choose UDP as the Outgoing Transport Type from the Trunk Configuration window.

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

New and Changed Information for Cisco Unified Communications Operating System Administration

New and Changed Information for Cisco Unified CallManager Features

New and Changed Information for Cisco Unified CallManager Applications

New and Changed Information for Cisco Unified CallManager Bulk Administration Features

New and Changed Information for Cisco Unified CallManager Serviceability

New and Changed Information for Third-Party API

New and Changed Information for Cisco Unified IP Phones

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

General Administration Enhancements

Service Parameter Changes

Cisco Unified CallManager Administration Menu Updates

Third-Party SIP Phone Enhancements

Phone Configuration Enhancements

Phone Button Configuration Enhancements

License Capabilities Assignment

Call Forward Overriding

Enterprise Parameter Changes

Additional Corporate Directory Support

Cisco Unified CallManager Installation

Cisco Unified CallManager 5.1 includes the following installation enhancements.

New network connectivity checking—The installation program checks for network connectivity. If the network is not accessible, you have several options for how to proceed with the installation.

New hostname and IP assignment during upgrade—The upgrade installation program now allows you to use a different hostname or IP address on the upgraded system.

For more information

Installing Cisco Unified CallManager Release 5.1(1)

Upgrading Cisco Unified CallManager Release 5.1(1)

Data Migration Assistant (DMA) 5.1 includes the following enhancements:

DMA migrates data for upgrades of Cisco Emergency Responder (CER) 1.3.

Enhanced interaction between DMA and Cisco Security Agent for Cisco Unified CallManager (CSA) occurs. Depending on the versions of DMA and CSA that you are using, you may possibly leave CSA enabled while DMA runs. In other cases, DMA automatically disables CSA while it is running, and in some cases you must disable CSA manually while you are running DMA.

For more information

Data Migration Assistant User Guide Release 5.1(1).

General Administration Enhancements

The following requirements apply to Cisco Unified CallManager Administration:

Microsoft Internet Explorer (IE) 6.0

Netscape 7.1 or higher


Note This release does not support Microsoft IE 5.5 and 7.0 or Netscape 7.0.


Service Parameter Changes

Cisco Unified CallManager 5.1 supports the following service parameter changes:

The TFTP Service Parameter no longer includes the Enable Caching of Configuration Files option.

Immediate Divert (iDivert) includes the following new service parameters:

Use Legacy iDivert

Allow QSIG During iDivert

iDivert User Response Timer

See the "Immediate Divert Enhancements" section for more information.

The Cisco Database Layer Monitor service includes a new service parameter, "Send Valid Namespace in AXL Response." See the "New AXL Service Parameter" section for more information.

Cisco Unified CallManager provides a new service parameter, CFA Destination Override, that 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. See the "Call Forward All Override" section for more information.

Two Cisco Unified CallManager service parameters relate to the Enhanced iDivert feature:

Use Legacy Immediate Divert-This clusterwide service parameter defines whether the legacy iDivert behavior is maintained or the new Enhanced iDivert behavior is adopted. If the Use Legacy iDivert service parameter is set to True, the user can divert an incoming call only to the voice mailbox of the user.

Allow QSIG during iDivert-IDivert diverts calls to voice-messaging systems that can be reached over QSIG, SIP and QSIG-enabled H.323 devices if the clusterwide service parameter is set to True.

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 Cisco Unified CallManager, Release 5.0(4) introduced License Capabilities Assignment.Cisco Unified CallManager New and Changed Information Guide, Release 5.1(1) fully documents it.


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

License Capabilities Configuration, Cisco Unified CallManager New and Changed Information Guide, Release 5.1(1)

Configuring Non-Cisco SIP IP Phones, Cisco Unified CallManager New and Changed Information Guide, Release 5.1(1)

Cisco TFTP, Cisco Unified CallManager New and Changed Information Guide, Release 5.1(1)

Immediate Divert, Cisco Unified CallManager New and Changed Information Guide, Release 5.1(1)

Cisco Unified IP Phones, Cisco Unified CallManager New and Changed Information Guide, Release 5.1(1)

AXL Programming, Cisco Unified CallManager New and Changed Information Guide, Release 5.1(1)

Enterprise Parameter Changes

Cisco Unified CallManager Release 5.1 supports the following enterprise parameter changes:

Advertise G.722 Codec—This parameter determines whether Cisco Unified IP Phones will advertise the G.722 codec to Cisco Unified CallManager. Codec negotiation involves two steps. First, the phone must advertise the supported codec(s) to Cisco Unified CallManager (not all phones support the same set of codecs). Second, when Cisco Unified CallManager gets the list of supported codecs from all phones that are involved in the call attempt, it chooses a commonly supported codec based on various factors, including the region pair setting. This parameter only applies to Cisco Unified IP Phone 7941G, 7941G-GE, 7961G, 7961G-GE, 7970G, and 7971G-GE. Valid values specify True (the specified Cisco Unified IP Phones advertise G.722 to Cisco Unified CallManager) or False (the specified Cisco Unified IP Phones do not advertise G.722 to Cisco Unified CallManager). For more information, see the "Phone Configuration—Product-Specific Configuration Changes" section.

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 The default for the Advertise G.722 Codec enterprise parameter enables G.722 on all phones in the cluster. The default value of the phone configuration Advertise G.722 Codec Product-Specific parameter uses the value that the enterprise parameter setting specifies.


Table 4 indicates how the phone responds to the configuration options.

Table 4 How Phone Responds to Configuration Settings

Enterprise Parameter Setting
Phone (Product-Specific) Parameter Setting
Phone Advertises G.722

Advertise G.722 Codec Enabled (True)

Use System Default

Yes

Advertise G.722 Codec Enabled (True)

Enabled

Yes

Advertise G.722 Codec Enabled (True)

Disabled

No

Advertise G.722 Codec Disabled (False)

Use System Default

No

Advertise G.722 Codec Disabled (False)

Enabled

Yes

Advertise G.722 Codec Disabled (False)

Disabled

No


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

New CLI Commands and Command Options

You now have the following new CLI commands and command options available.

show ipsec status

show logins

show network max_ip_conntrack

show open

set commandcount

set network mtu

set network max_ip_conntrack

set network pmtud

unset network dns options

utils core

utils dbreplication

utils iothrottle

utils reset_ui_administrator_password

utils sftp

After uploading a file to the TFTP server, you must restart the TFTP service to access the file.

For more information

Cisco Unified Communications Operating System Administration Guide Release 5.1(1).

New and Changed Information for Cisco Unified CallManager Features

The following sections describe the Cisco Unified CallManager 5.1 feature enhancements:

Immediate Divert Enhancements

Call Forward All Override

AAC Voice Codec Support

Arabic Language (right to left) Support

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

Configure appropriate service parameters.

Configure the iDivert softkey.

If using hunt lists and line groups, refer to the Limitations and Restrictions section of the Immediate Divert chapter in the Cisco Unified CallManager New and Changed Information Guide.

If using QSIG trunks, refer to the Limitations and Restrictions section of the Immediate Divert chapter in the Cisco Unified CallManager New and Changed Information Guide.

Service or Enterprise Parameter Changes

Immediate Divert includes the following new service parameters:

Use Legacy Immediate Divert

Allow QSIG During iDivert

Immediate Divert User Response Timer

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.

If a call originally gets sent to the phone of someone else, iDivert allows the user to redirect the call either to the voice-messaging system or to the original called party voice-messaging system. The system administrator must make this option available.

If a call gets sent to the user directly (not transferred or forwarded to the user) or if the user phone does not support the described option, using iDivert redirects the call to the voice-messaging system of the user.

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

Cisco Unified IP Phone 7906G (SCCP and SIP)

Cisco Unified IP Phone 7911G (SCCP and SIP)

Cisco Unified IP Phone 7961G-GE (SCCP and SIP)

Cisco Unified IP Phone 7941G-GE (SCCP and SIP)

Cisco Unified IP Phone 7970G (SCCP and SIP)

Cisco Unified IP Phone 7971G-GE (SCCP and SIP)

Cisco Unified IP Phone 7905G (SCCP and SIP)

Cisco Unified IP Phone 7912G (SCCP and SIP)

Cisco Unified IP Phone 7960G (SCCP and SIP)

Cisco Unified IP Phone 7940G (SCCP and SIP)

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

Immediate Divert, Cisco Unified CallManager New and Changed Information Guide, Release 5.1(1)

Cisco Unified IP Phone User Guide For Your Phone

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:

CFA Destination Override

Cisco Unified IP Phone Support

Cisco Unified IP Phone 7971G (SCCP and SIP)

Cisco Unified IP Phone 7971G-GE (SCCP and SIP)

Cisco Unified IP Phone 7970G (SCCP and SIP)

Cisco Unified IP Phone 7961G-GE (SCCP and SIP)

Cisco Unified IP Phone 7960G (SCCP and SIP)

Cisco Unified IP Phone 7941G-GE (SCCP and SIP)

Cisco Unified IP Phone 7940G (SCCP and SIP)

Cisco Unified IP Phone 7911G (SCCP and SIP)

Cisco Unified IP Phone 7906G (SCCP and SIP)

For More Information

Understanding Directory Numbers, Cisco Unified CallManager System Guide

Cisco Unified IP Phones, Cisco Unified CallManager System Guide

Service Parameters Configuration, Cisco Unified CallManager Administration Guide

Cisco Unified CallManager New and Changed Information Guide, Release 5.1(1)

AAC Voice Codec Support

The Advanced Audio Codec (AAC) feature provides the following capabilities:

Advanced Audio Codec (AAC) specifies a wideband voice codec that provides improved voice fidelity and equal or better sound quality over older codecs.

When configuring a region, use the wideband audio codec if you want to configure the AAC for calls between SIP phones. The Cisco Unified IP Phone 7900 series phone supports wideband, a high-quality, high-bandwidth audio codec for IP-phone to IP-phone calls.

Cisco Unified CallManager Administration Configuration Tips

When configuring a region, use the wideband audio codec if you want to configure the AAC for calls between SIP phones.

CAR/CDR Considerations

The table of the AAC codec types includes the table of supported codec types.

For More Information

Cisco Unified CallManager New and Changed Information Guide, Release 5.1(1)

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

Cisco Unified IP Phone 7906G

Cisco Unified IP Phone 7911G

Cisco Unified IP Phone 7961G-GE

Cisco Unified IP Phone 7941G-GE

Cisco Unified IP Phone 7970G

Cisco Unified IP Phone 7971G-GE

For More Information

Cisco Unified IP Phone Configuration, Cisco Unified CallManager Administration Guide

New and Changed Information for Cisco Unified CallManager Applications

The following section describes the Cisco Unified CallManager 5.1 applications enhancements:

Music on Hold

DirSync Application Enhancements

Music on Hold

The Music On Hold feature now supports the new service parameter, Multicast MOH Direction Attribute for SIP.

The Multicast MOH Direction Attribute for SIP service parameter determines whether Cisco Unified CallManager sets the direction attribute of the Session Description Protocol (SDP) in its multicast Music on Hold (MOH) INVITE message to sendOnly or recvOnly.

If your deployment uses SIP phone loads 8.4 and earlier for Cisco Unified IP Phone 7940 and 7960, or SIP phone loads 8.1(x) and earlier for Cisco Unified IP Phone 7906, 7911, 7941, 7961, 7970, and 7971, set this parameter to sendOnly. Otherwise, leave this parameter set to the default value, recvOnly.

For More Information

Cisco Unified CallManager New and Changed Information Guide, Release 5.1(1)

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:

Microsoft Windows Server 2000 and Windows Server 2003 Active Directory (AD)

Netscape/iPlanet Directory

Sun ONE Directory Server 5.1

Sun Java System Directory Server 5.2

For More Information

Understanding the Directory, Cisco Unified CallManager System Guide

Cisco Unified CallManager Serviceability System Guide

Cisco Unified CallManager Serviceability Administration Guide.

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

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

Cisco Unified CallManager Release 5.1(1) New and Changed Information Guide

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

TFTP Exclude Digest Credentials Check Box Display

Upgrading Cisco Unified IP Phones to Authenticate with LSCs Not MICs

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.

The Cisco CTL client displays the firewall certificate as a "CCM" certificate

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

Configuring the Cisco CTL Client, Cisco Unified CallManager New and Changed Information Guide, Release 5.1(1)

Configuring Encrypted Phone Configuration Files, Cisco Unified CallManager New and Changed Information Guide, Release 5.1(1)

Cisco Unified CallManager 5.1 TCP and UDP Port Usage

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

Cisco Unified CallManager Real-Time Monitoring Tool (RTMT)

Cisco Unified CallManager Analysis and Reporting (CAR)

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):

The Troubleshooting Trace Setting window, which allows you to choose the services in Cisco Unified CallManager for which you want to set predetermined troubleshooting trace settings, contains the following updates:

The Server drop-down list box—Applies the troubleshooting trace settings to the server that you specify.

Check All Services check box—Automatically checks all check boxes for the services on the current node that you chose in the Server drop-down list box.

Check Selected Services on All Nodes check box—Allows you to check specific service check boxes in the Troubleshooting Trace Settings window. This setting applies for all nodes in the cluster where the service is activated.

Check All Services on All Nodes check box—Automatically checks all check boxes for all services for all nodes in the cluster. When you check this check box, the Check All Services and Check Selected Services on All Nodes check boxes automatically get checked.

Reset Troubleshooting Traces—Restores the original trace settings for the services on the node that you chose in the Server drop-down list box; also displays as an icon that you can click.

Reset Troubleshooting Traces On All Nodes—Restores the original trace settings for the services on all nodes in the cluster.

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

Troubleshooting Trace Settings Configuration, Cisco Unified CallManager New and Changed Information Guide, Release 5.1(1)

Trace, Cisco Unified CallManager New and Changed Information Guide, Release 5.1(1)

Cisco Unified CallManager Real-Time Monitoring Tool (RTMT)

Cisco Unified CallManager includes the following enhancements for Cisco Unified CallManager Release 5.1(1b):

RTMT allows you to zoom in and zoom back out on the monitor of a predefined object. To zoom in on the monitor of a predefined object, click and drag the left mouse button over the area of the chart in which you are interested. To zoom out and reset the monitor to the initial default view, press the "R" key.

RTMT contains a new counter. The Cisco Tomcat Connector ThreadsBusy counter represents the connector current number of busy/in-use request processing threads.

The description for the Process Status counter value of 4 changed from traced to stopped.

For More Information

Real-time Monitoring Configuration, Cisco Unified CallManager New and Changed Information Guide, Release 5.1(1)

Performance Objects and Counters, Cisco Unified CallManager New and Changed Information Guide, Release 5.1(1)

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):

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.

In all CDR Search reports, the system only displays the oldest 100 records that fall into the time and date range that you configure.

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

CAR Report Results, Cisco Unified CallManager New and Changed Information Guide, Release 5.1(1)

CDR Analysis and Reporting Overview, Cisco Unified CallManager New and Changed Information Guide, Release 5.1(1)

CDR Search Configuration, Cisco Unified CallManager New and Changed Information Guide, Release 5.1(1)

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

WebDialer Requirements

AXL Programming

AXL APIs

The following list provides AXL API calls that are new in Cisco Unified CallManager Release 5.1:

addSIPRealm

updateSIPRealm

getSIPRealm

removeSIPRealm

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:

WebDialer and Redirector now require HTTPS.

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

AXL Programming, Cisco Unified CallManager New and Changed Information Guide, Release 5.1(1)

WebDialer API Programmming, Cisco Unified CallManager New and Changed Information Guide, Release 5.1(1)

New and Changed Information for Cisco Unified IP Phones

The following section describes the enhancements for Cisco Unified IP Phones:

Wideband Codec

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:

Cisco Unified IP Phone 7971G-GE

Cisco Unified IP Phone 7970G

Cisco Unified IP Phone 7961G-GE

Cisco Unified IP Phone 7961G

Cisco Unified IP Phone 7941G-GE

Cisco Unified IP Phone 7941G

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 You need an account with Cisco.com (Cisco Connection Online) to use the Bug Toolkit to find open and resolved caveats of any severity for any release.

To access the Bug Toolkit, log on to http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl.


This section includes the following topics:

Using Bug Toolkit

Using Bug Toolkit

Known problems (bugs) are graded according to severity level. These release notes contain descriptions of:

All severity level 1 or 2 bugs.

Significant severity level 3 bugs.

You can search for problems by using the Cisco Software Bug Toolkit.

To access Bug Toolkit, you need the following items:

Internet connection

Web browser

Cisco.com user ID and password

To use Bug Toolkit, follow these steps:

Procedure


Step 1 To access the Bug Toolkit, go to http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs.

Step 2 Log in with your Cisco.com user ID and password.

Step 3 To look for information about a specific problem, enter the bug ID number in the "Search for Bug ID" field, then click Go.


Note For information about how to search for bugs, create saved searches, create bug groups, etc, click Help in the Bug Toolkit page.


Open Caveats

Table 5 describes possible unexpected behaviors in Cisco Unified CallManager Release 5.1(1x), which are sorted by component.


Tip For more information about an individual defect, click the associated Identifier in Table 5 to access the online record for that defect, including workarounds.


Understanding the Fixed-in Version and the Integrated-in Fields in the Online Defect Record

When you open the online record for a defect, you may see data in the "First Fixed-in Version" or "Integrated-in" fields. The information that displays in these fields identifies the list of Cisco 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.

003.003(003.144) = Cisco CallManager Release 3.3(4)

005.000(000.123) = Cisco Unified CallManager Release 5.0(1)

005.000(001.008) = Cisco Unified CallManager Release 5.0(2)

005.001(002.9901.062) = Cisco Unified CallManager Release 5.1(3)


Note Because defect status continually changes, be aware that Table 5 reflects a snapshot of the defects that were open at the time this report was compiled. For an updated view of open defects, access Bug Toolkit and follow the instructions as described in the "Using Bug Toolkit" section.



Tip Bug Toolkit requires that you have an account with Cisco.com (Cisco Connection Online). By using the Bug Toolkit, you can find caveats of any severity for any release. Bug Toolkit may also provide a more current listing than this document provides. To access the Bug Toolkit, log on to http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs.


.

Table 5 Open Caveats as of 9-25-07 

Identifier
Headline

Component: Alert-Coll_Report

CSCsk23265

The need exists for an RTMT precanned alert for NumDevRegExceeded alarm.

Component: Attendant Console

CSCsk53501

Attendant Console InterServer Race Conditions exist when agents are split on publisher and subscriber servers.

CSCsj76444

"General SQL failure" and Java exception error messages get printed to the upgrade log file.

Component: AXL

CSCsj71916

AXIS Java exception.

CSCsk14345

Remove failed for Line, CallPickup, CSS, RouteParition, Time Schedule.

CSCsk28959

Change notification database space fills up due to phone inserts taking place via AXL interface.

Component: Backup and Restore (BAR)

CSCsj31456

RTMT received a CallProcessingNodeCpuPegging alert during a DRF backup.

Component: Cisco Unified CallManager MIB Agent

CSCsi85520

When the getbulk/getnext/getmany request has multiple OIDs in its request PDU and the subsequent tables are empty in the CISCO-CCM MIB, the responses may be NO_SUCH_NAME, for SNMP v1 version or GENERIC_ERROR, for SNMP v2c or v3 version.

CSCsk59462

ccmPhoneProductTypeIndex retuns a 0 value.

Component: Cisco Unified CallManager CTI

CSCsk13172

Wrong remote-in-use value for shared line when conference/transfer gets initiated on a cbarge/barge scenario.

CSCsk48801

CTIManager does not update partition information when part name gets changed.

CSCsi06589

System not verifying number of ConsultCalls is in range of maximum consult calls.

Component: Call Processing

CSCsj77506

CAC: Location based CAC bandwidth does not get released intermittently.

CSCsk54103

H323: Cisco Unified CallManager shows increased memory utilization and handle count over time when processing H.323 calls.

CSCsk52316

Huntlist: Basic SCCP Calls over SIP trunks does not display Alerting Name.

CSCsk07661

Huntlist: Logout of the hunt group changes circular line group distribution.

CSCsk18634

Mediacontrol: In a video conference involving two video endpoints and a polycom, the two video endpoints cannot see video from polycom.

CSCsi13130

Mediacontrol: Location bandwidth does not get deducted correctly for SIP ICT.

CSCsg29976

Mediacontrol: Video RSVP call to CUPC endpoint takes three RSVP resources.

CSCeg64769

QSIG: An erroneous APDU is sent from the rerouting PINX to the servedUser PINX.

CSCsk40448

QSIG: Callback over QSIG fails if call forward is enabled.

CSCsh64270

SCCP: Missed conference calls do not display..

CSCsh97800

SCCP: Call transfer does not complete on a phone which answers an incoming call before the transfer gets completed.

CSCsj13962

SCCP: For users with Cisco Unified IP Phone model 7961 with one or more 7914 side cars, intermittently when user is on an active call on a line on the 7914 and another call comes in on another line on the 7914, the phone does not ring, it just flashes.

CSCsi99786

SCCP: Phone reregister while the subscriber server on which it's already registered is still up.

CSCsj78900

SCCP: Cisco Unified CallManager cannot disconnect a preserved call.

CSCsk07094

SS Transfer: Call transfer loop occurs on SCCP phones.

CSCsk27418

System: Enabling trace compression decreases call throughput.

CSCsh36576

System: If the "DSCP for Cisco CallManager to Device Interface" Enterprise Parameter is set to something higher than CS4 (the default is CS3), the signaling packets from CallManager will be tagged with DSCP 000000 instead of the configured DSCP, such as DSCP CS5 101000.

CSCsj20653

System: Large number of phone unregistrations leads to critical alarms dropped.

Component: Cisco Customer Performance Indicators (CPI) Appinstall

CSCsk56707

Subscriber server upgrade has inconsistent publisher version requirements.

Component: Cisco Customer Performance Indicators (CPI) Data Migration Assistant (DMA)

CSCsk18230

The need exists for DMA to provide more feedback when validation fails.

CSCsg92930

The DMA backup page does not get refreshed automatically, so the user must close the page and reopen it manually.

Component: Cisco Customer Performance Indicators (CPI) OS

CSCsk48990

The need exists for updated BIOS firmware to support Woodcrest CPU changes for G0 stepping.

CSCse71209

Smart Array 6i v2.68 requires HD firmware update to avoid POST notification.

CSCsf26301

Smart Array 5i requires HD firmware update to avoid POST notification.

CSCsi02536

BIOS flash failure during new installation.

CSCsj74466

The following error is displayed on the console: init: ID "SD0" respawning too fast: disabled for 5 minutes.

CSCsk18417

"grubby fatal errors" in the install log, but no ther symptoms.

CSCsk21776

A new CPU with G0 stepping will get used on 7835 and 7845 H2/I2/D2 platforms. This requires new BIOS from vendors and for some Cisco Unified CallManager 5.x releases we down rev the BIOS and it causes issues on the servers with the new CPU.

CSCsk26020

MCS-7825-I2 servers report SNMP RAID events as kernel notification events. These are not reported as IBM-SYSTEM-RAID-MIB events with an IBM OID as expected.

CSCsk27561

Use of CLI comand "utils core list" shows a modprobe core file.

CSCsk44741

If the writeCache setting gets enabled and the checked, it still shows disabled.

Component: Cisco Customer Performance Indicators (CPI) User Interface

CSCsk16329

CriticalServiceDown alerts get raised after an upgrade and switchover.

Component: Database

CSCsk41452

In Cisco Unified CallManager 5.0 and 5.1 systems it is possible that 1024 (which is the limit) of incomplete connections gets reached due to incorrect handling of resources. This results in the user being unable to access the Cisco Unified CallManager Administration window among other things.

CSCsg06024

Tomcat server down because of database engine DDR block.

CSCsj90196

The need exists for a change to the DRS process so that the subscriber server does not require rebuild/restore.

CSCsj40566

Non-ASCII characters entered in some fields in Windows Cisco Unified CallManager cannot be migrated or used in Cisco Unified CallManager 5.x and later. Fields include Descriptions which allowed accented characters used by languages other than English. In 5.0 and later releases only plain characters (ASCII characters with values less than 127) are allowed in these fields.

CSCsb71648

Migration takes over fifteen hours.

CSCsh45042

Informix replication logs get written to the /tmp directory.

ComponentL Directory

CSCsj24600

When the directory export is exporting directory data, there is no progress indication provided to DMA.

CSCsk19222

DirSync starts a full synchronization when the scheduled time gets changed.

Component: Documentation

CSCsj32442

Upgrade documentation should give more specific licensing reference.

CSCsj34278

Obtaining license file documentation not applicable to upgrade.

CSCtr84167

When you enable the service parameter "Block Offnet to Offnet Transfer" and make a blind transfer with Cisco Unity Connection, the Q.931 SETUP message which Cisco Unified CallManager sends to the PSTN gateway for an outbound PRI call still reaches the gateway. This transfer results in a dropped call.

Component: Install Product

CSCsj56299

CDR Analysis and Reporting does not reflect DST changes for New Zealand.

Component: Java Telephony API (JTAPI) Software Development Toolkit (SDK)

CSCsg03945

CiscoJTAPIClient-linux.bin fails to install.

Component: Media Storage Application

CSCsk61129

MOH file upload fails due to lack of disk space.

Component: QED

CSCsj18895

When an 8.3 7970 is talking to a pre-6.0 Cisco Unified CallManager, Programmable Line Keys (PLKs) such as Redial, Conference, and others work, but their labels show as "???".

Component: Security

CSCsk03132

Remove CTL upload from certificate management window and document it.

CSCsk11229

The need exists for better handling to prevent CTLClient from accessing the subscriber server directly.

CSCsk33511

CTL client operation fails on Vista.

Component: TAPI SDK

CSCsg23468

The first playwave operation gets delayed by a few seconds before the destination hears it.

CSCsg23990

TSP svchost pegging 99% CPU usage during TLS connection.

CSCsb64096

Application stuck during RecordWave with Silence.


Documentation Updates

This section provides documentation changes that were unavailable when the Cisco Unified CallManager release 5.1(1b) documentation suite was released.

Omissions

Updates

Changes

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

Call Park Range

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

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 All devices in the Cisco Unified CM Group of which this server is a member get reset, not just those devices that are registered with this server.


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. Create theTehoBr1forHQPt partition and assign this partition to the calling search space (CSS) of the HQ devices with a higher priority than the regular PSTN access uses.

2. Create the TehoBr1forHQRL route list and add the BR1 gateway route group to this route list as the first option and the HQ gateway as the second option.

3. Apply called party modification within the route list. In this case, apply predot called party modification for the BR1 route group, and apply predot and prefix 1919 called party modification for the HQ route group.

4. Ensure that the gateway does not perform called party modification.

5. Create a route pattern in the TehoBr1forHQPt partition.

6. Ensure that no called party modifications are applied in the route pattern.

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:

To optimize performance of DTMF signaling, use Cisco IOS Release 12.4(11)T or later. This Cisco IOS release supports RFC 2833 DTMF MTP Pass through of digits.

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:

Cisco Unified CallManager uses "beep" and "beep beep" tones when a new party is added, and when the new party drops from the ad hoc conference, respectively. When a party is added to an ad hoc conference, a user on a SIP Phone may or may not hear the beep; when a participant drops from the ad hoc conference, a user on a SIP Phone may not hear the beep beep. The beeps may not be heard because of the time it takes to re-establish connections for the conference.

Time-of-Day Routing Chapter Omits Information About Defined Time Periods

The "Time-of-Day Routing" chapter of the Cisco Unified Communications Manager System Guide omits the following information.

If you defined a time period with a specific date, on that specified date, that period overrides other periods that are defined on a weekly basis.

Example:

Consider the following example:

A time period, afterofficehours, that is defined as 00:00 to 08:00 from Monday to Friday exists.

A time period, newyearseve, that is defined as 14:00 to 17:00 on December 31st exists.

In this case, on December 31st, the afterofficehours period will not be considered because it gets overriden by the more specific newyearseve period.

Updates

This section provides information that has been updated since the release of the Cisco Unified CallManager Release 5.1(1x) documentation.

Name Change

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)

Cisco Emergency Responder 1.3(1a)

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 Cisco Unified CallManager 5.0(1) does not get supported with Cisco Emergency Responder 1.3(1a).


Ensure all Cisco ER servers are version 1.3(1a). This allows Cisco ER to support multiple Cisco Unified CallManager 5.0(2) or 5.0(3) clusters. Cisco ER 1.3(1a) will not work with previous versions of Cisco ER.

Cisco ER 1.3(1a) supports upgrades from Cisco ER 1.2(1), Cisco ER 1.2(2), and Cisco ER 1.2(3).

Cisco ER 1.3(1a) provides Windows-based support.

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.