Guest

Cisco Unified Communications Manager (CallManager)

Release Notes for Cisco Unified Communications Manager Release 8.0(1) (Deferred)

  • Viewing Options

  • PDF (779.8 KB)
  • Feedback
Release Notes for Cisco Unified Communications Manager Release 8.0(1)

Table Of Contents

Release Notes for Cisco Unified Communications Manager Release 8.0(1)

Contents

Introduction

System Requirements

Upgrading to Cisco Unified Communications Manager 8.0(1)

Before You Begin

Special Upgrade Information

I/O Throttling

Write-Cache

Device Name of Cisco Unified Mobile Communicator Must Not Exceed 15 Characters Before 8.0(1) Upgrade

Making Configuration Changes After an Upgrade

Upgrade Paths to Cisco Unified Communications Manager 8.0(1)

Ordering the Upgrade Media

Upgrading from a Local Source

Upgrading from a Remote Source

The Latest Software Upgrades for Unified CM 8.0 on Cisco.com

Service Updates

Related Documentation

Limitations and Restrictions

Important Notes

CSCtb31860 Transcoding G.711 to All Codecs Supported

CSCtw61986 Disable LRO on Cisco Unified Computing Systems running ESXi 4.1

CSCto57498 Upgrading to Cisco Unified Communications Manager Release 8.x from Release 7.x

CSCtd69640 Downtime when upgrading Publisher server until all Subscriber servers are updated

CSCte39796 Increase database replication timeout when upgrading large clusters

CSCsy57492 Hold Reversion Notification Interval for SCCP and SIP phones

New License Required when Replacing Motherboard (CSCtz12589 and CSCtz12651)

Limitations to Call Park Feature

CSCsz18443 Cisco Unified IP Phone 8961, 9951, 9971 Registered to a Node may Use the Call Park Number Assigned to Another Node

CSCsz31137 Parked Call Gets Reverted When the Parkee is on

CSCsz35994 Incorrect Display for Park Monitoring Forward No Retrieve

CSCtb53159 Display Limitation in ConfList

CSCtg50662 Bridge Upgrade: Some Services Fail to Register with Disaster Recovery Framework

CSCtd09050 Service Parameter Name/Usage Change from CTIWildCardDNAsCalledParty to CTIWildCardDNInCallInfo

Node Licenses Missing After an Upgrade

CSCtd01766 Destination Port on Trunk Remains Unchanged After Upgrade

CSCte91815 Cisco Phone Designer Does Not Work with Phone

Do Not Run Unified CM 8.0(1) on a VMware Virtual Machine Server

Cisco Intercompany Media Engine is Not Available

CSCte49213 ChangeCredential: Non-ASCII Character Use Causes Question Marks to Display in Success Message

Two New Security Features

CSCte53189 Changing More Than One Parameter at a Time on the CCD Requesting Service Causes Stale DN

CSCte36097 DRS Fails at Database Component

Disaster Recovery System Caution

CSCte47453 Installation Process Does Not Backup Component Files from Subscriber Server

EMCC Login Affects Settings in Product-Specific Configuration Layout of Phone Configuration Window

CSCtd94318 MCS-7845-I3 Server Locks Up After Integrated Management Module gets Restarted

CSCtj61834 MLPP Default Domain Name Displays MLPP ID Value

CSCtr40861 Incoming Calling Party Numbers should be up to 16 characters

CSCtr89029 URL Parameters for Secured Phones Repopulated After Restart

CSCto87262 Centralized TFTP with CUCM 8 SBD requires workaround

CSCte44108 Call Control Discovery Limitation

CSCtj37643 Installing Language Prompts for TAPS

CSCtx00678 Do not use Voicemail for Alerting Name or ASCII Alerting Name

CSCtx86215 Database Replication

CSCsu23100 Missing Information on Special Characters

CSCtx92282 Cisco Unified IP Phones 9951 and 9971 support SIP Dial Rules

CSCtr44481 Download Dial Plans for Cisco Unified Communications Manager Release 8.X

CSCtc71174 Call Park and Directed Call Park Restriction

CSCtg71595 Allowed characters for Cluster ID field

CSCtb58649 Sample query cannot list multiple users

CSCuc10415 Tip for Adding a New Server

CSCuc23992 Call Preservation support for SIP trunks

CSCuc79185 Device Mobility Calling Search Space is Used When Device CSS is <none>

CSCtw44980 Missing Exceptions for Voice-Mail Pilot

CSCud34740 Application User AXL Password Must Not Contain Special Characters

CSCud70447 Missing Etoken Recovery Steps in Troubleshooting Guide

CSCud95087 Limitation of SIP Forking on Trunk Not Documented

CSCui20049 Restructure of Disaster Recovery Documentation for Restore Scenarios

Restore Scenarios

Restoring a Node or Cluster to a Last Known Good Configuration (No Rebuild)

Restoring the First Node only (Rebuilding the Publisher Alone)

Restoring the Entire Cluster

Restoring Subsequent Cluster Nodes (With or Without Rebuild)

New and Changed Information

Caveats

Resolved Caveats

UsingBug Toolkit

Open Caveats

Open Caveats for Cisco Unified Communications Manager Release 8.0(1) As of February 23, 2010

Documentation Updates

Obtaining Documentation and Submitting a Service Request


Release Notes for Cisco Unified Communications Manager Release 8.0(1)


Updated August 29, 2013

Because of CSCtg50662 Bridge Upgrade: Some Services Fail to Register with Disaster Recovery Framework, Cisco Unified Communications Manager Release 8.0(1) is deferred. Cisco recommends that you install/upgrade to Cisco Unified Communications Manager 8.0(2c).


Note You can view release notes for Cisco Unified Communications Manager Business Edition at http://www.cisco.com/en/US/products/ps7273/prod_release_notes_list.html


Table 1 Updates to Release Notes for Unified CM 8.0(1)

Date
Update

01-21-13

Added CSCud95087 Limitation of SIP Forking on Trunk Not Documented to Important Notes.

01-04-13

Added CSCud70447 Missing Etoken Recovery Steps in Troubleshooting Guide to Important Notes.

12-5-12

Added CSCud34740 Application User AXL Password Must Not Contain Special Characters to Important Notes.

10-31-12

Added CSCuc79185 Device Mobility Calling Search Space is Used When Device CSS is <none> and CSCtw44980 Missing Exceptions for Voice-Mail Pilot to Important Notes.

10-3-12

Added CSCtb31860 Transcoding G.711 to All Codecs Supported to Important Notes.

09-21-12

Added CSCuc10415 Tip for Adding a New Server to Important Notes.

09-10-12

Added a note about IP phone firmware to the Before You Begin of Upgrading to Cisco Unified Communications Manager 8.0(1).

09-07-12

Updated the "Important Notes" section (added CSCtw61986 Disable LRO on Cisco Unified Computing Systems running ESXi 4.1).

08-31-12

Updated the "Important Notes" section (added "CSCtc71174 Call Park and Directed Call Park Restriction" section).

08-24-12

Updated the "Important Notes" section (added CSCto57498 Upgrading to Cisco Unified Communications Manager Release 8.x from Release 7.x).

08-09-12

Updated the Important Notes, added CSCtd69640 Downtime when upgrading Publisher server until all Subscriber servers are updated).

7-18-12

Under Important Notes, added the CSCte39796 Increase database replication timeout when upgrading large clusters

7-12-12

Under Important Notes, added the CSCsy57492 Hold Reversion Notification Interval for SCCP and SIP phones

6-23-12

Under Important Notes, added the New License Required when Replacing Motherboard (CSCtz12589 and CSCtz12651)

10-19-10

Under Important Notes, added the "Limitations to Call Park Feature" section

5-5-10

Under Important Notes, added the "CSCtg50662 Bridge Upgrade: Some Services Fail to Register with Disaster Recovery Framework" section

4-4-10

Under Important Notes, added the "CSCtd09050 Service Parameter Name/Usage Change from CTIWildCardDNAsCalledParty to CTIWildCardDNInCallInfo" section

3-23-10

Under Important Notes, added the "Node Licenses Missing After an Upgrade" section


This document contains information pertinent to Cisco Unified Communications Manager Release 8.0(1).

To view the release notes for previous versions of Cisco Unified Communications Manager, choose the Cisco Unified Communications Manager version from the following URL: http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_release_notes_list.html.

Contents

This document includes the following information:

Introduction

System Requirements

Upgrading to Cisco Unified Communications Manager 8.0(1)

Service Updates

Related Documentation

Important Notes

New and Changed Information

Caveats

Documentation Updates

Obtaining Documentation and Submitting a Service Request

Before you install or upgrade Cisco Unified Communications Manager, Cisco recommends that you review the "Upgrading to Cisco Unified Communications Manager 8.0(1)" section, and the "Service Updates" section for information pertinent to installing or upgrading, and the "Important Notes" section for information about issues that may affect your system.

Introduction

Cisco Unified Communications Manager, the call-processing component of the Cisco Unified Communications System, extends enterprise telephony features and capabilities to IP phones, media processing devices, voice-over-IP (VoIP) gateways, mobile devices, and multimedia applications.

System Requirements

The following sections comprise the system requirements for this release of Cisco Unified CM.

Server Support

Make sure that you install and configure Cisco Unified CM on a Cisco Media Convergence Server (MCS) or a Cisco-approved HP server configuration or a Cisco-approved IBM server configuration.

To find which MCS are compatible with this release of Cisco Unified CM, refer to the Supported Servers for Cisco Unified Communications Manager Releases: http://www.cisco.com/en/US/prod/collateral/voicesw/ps6790/ps5748/ps378/prod_brochure0900aecd8062a4f9.html.


Note Make sure that the matrix shows that your server model supports Cisco Unified CM Release 8.0(1).


Be aware that some servers that are listed in the Cisco Unified Communications Manager Software Compatibility Matrix may require additional hardware support for Cisco Unified CM Release 8.0(1). Make sure that your server meets the minimum hardware requirements, as indicated in the footnotes of the Cisco Unified Communications Manager Software Compatibility Matrix. Uninterruptible Power Supply

Cisco recommends that you connect each Cisco Unified Communications Manager server to an uninterruptible power supply (UPS) to provide backup power and protect your system against a power failure.


Note You must connect MCS-7816 and MCS-7825 servers to a UPS to prevent file system corruption during power outages.


When Cisco Unified Communications Manager runs on one of the servers that are listed in Table 2, basic integration to the UPS model APC SmartUPS 1500VA USB and APC 750VA XL USB gets supported.

Integration occurs via a single point-to-point Universal Serial Bus (USB) connection. Serial and SNMP connectivity to UPS does not get supported, and the USB connection must be point-to-point (in other words, no USB hubs). Single- and dual-USB UPS models get supported with the APC SmartUPS 1500VA USB and APC 750VA XL USB. The feature activates automatically during bootup if a connected UPS gets detected.

Alternatively, you can execute the CLI command show ups status that shows the current status of the USB-connected APC smart-UPS device and starts the monitoring service if it is not already started. The CLI command also displays detected hardware, detected versions, current power draw, remaining battery runtime, and other relevant status information.

When the feature is activated, graceful shutdown will commence as soon as the low battery threshold is reached. Resumption or fluctuation of power will not interrupt or abort the shutdown, and administrators cannot stop the shutdown after the feature is activated.

For unsupported Cisco Unified Communications Manager releases, MCS models and/or UPS vendor/make/models, you can cause an external script to monitor the UPS. When low battery gets detected, you can log on to Cisco Unified Communications Manager by using Secure Shell (SSH), access the CLI, and execute the utils system shutdown command.


Note If your pre-8.0 Unified CM is running on a deprecated server, you can upgrade it by using the Bridge upgrade procedure.


Table 2 Supported Servers for Basic Integration 

HP Servers
IBM Servers

MCS-7816-H3

MCS-7815-I2

MCS-7825-H2

MCS-7816-I3

MCS-7825-H3

MCS-7816-I4

MCS-7825-H4

MCS-7825-I2

MCS-7828-H3

MCS-7825-I3

MCS-7835-H2

MCS-7825-I4

MCS-7845-H2

MCS-7828-I3

 

MCS-7828-I4

 

MCS-7835-I2

 

MCS-7845-I2

 

MCS-7835-I3

 

MCS-7845-I3



Note Be aware that the DL 380-G6 server is available only directly from HP; and there are no equivalent HP OEM MCS-7835-H3 or MCS-7845-H3 servers.


Upgrading to Cisco Unified Communications Manager 8.0(1)

The following sections contain information that is pertinent to upgrading to this release of Cisco Unified CM.

Before You Begin

Special Upgrade Information

Upgrade Paths to Cisco Unified Communications Manager 8.0(1)

Ordering the Upgrade Media

The Latest Software Upgrades for Unified CM 8.0 on Cisco.com

Upgrading from a Local Source

Before You Begin

1. Before you upgrade the software version of Cisco Unified Communications Manager, verify your current software version.

To do that, open Cisco Unified Communications Manager Administration. The following information displays:

Cisco Unified Communications Manager System version

Cisco Unified Communications Manager Administration version

2. Read the "Special Upgrade Information" section.


Note After you perform a switch version when you upgrade Unified CM, IP phones request a new configuration file. This request results in an automatic upgrade to the device firmware.


Special Upgrade Information



The following sections include information that you must know before you begin the upgrade process.

I/O Throttling

Write-Cache

Device Name of Cisco Unified Mobile Communicator Must Not Exceed 15 Characters Before 8.0(1) Upgrade

Making Configuration Changes After an Upgrade

I/O Throttling

The Disable I/O Throttling check box was introduced in the Cisco Unified CM 7.1(2) upgrade window. Do not check this box. It is no longer required when upgrading to this release.

Write-Cache

A disabled write-cache on the server also causes the upgrade process to run more slowly. Multiple factors, including dead batteries on older servers, can cause the write-cache to get disabled.

Before starting an upgrade, verify the status of the write-cache on the MCS-7828-H4 and MCS-7835/45 disk controllers. You do not need to verify the write-cache status on the MCS-7816, MCS-7825, or other MCS-7828 servers. To verify write-cache status, access the Cisco Unified Operating System Administration, and choose Show > Hardware.

If you determine that your write-cache is disabled because of a dead battery, you need to replace the hard disk controller cache battery. Follow your local support procedures to get this battery replaced.

See the following examples of output from the Show > Hardware menu for details on determining the battery and write-back cache status.

The following example shows write-cache enabled. The example indicates that 50 percent of the cache is reserved for write and 50 percent of the cache is reserved for read. If the write-cache was disabled, 100 percent of the cache would be reserved for read or the Cache Status would not equal "OK". Also, the battery count equals "1". If the controller battery was dead or missing, it would indicate "0".

Example 1 7835/45-H1, 7835/45-H2, 7828-H4 Servers with Write-Cache Enabled

-------------------------------
RAID Details      :
 
   
Smart Array 6i in Slot 0
   Bus Interface: PCI
   Slot: 0
   Cache Serial Number: P75B20C9SR642P
   RAID 6 (ADG) Status: Disabled
   Controller Status: OK
   Chassis Slot: 
   Hardware Revision: Rev B
   Firmware Version: 2.80
   Rebuild Priority: Low
   Expand Priority: Low
   Surface Scan Delay: 15 sec
   Cache Board Present: True
   Cache Status: OK
   Accelerator Ratio: 50% Read / 50% Write
   Total Cache Size: 192 MB
   Battery Pack Count: 1
   Battery Status: OK
   SATA NCQ Supported: False

The following example indicates that the battery status is enabled and that the the write-cache mode is enabled in (write-back) mode.

Example 2 7835/45-I2 Servers with Write-Cache Enabled

----------
RAID Details      :
Controllers found: 1
 
   
----------------------------------------------------------------------
Controller information
----------------------------------------------------------------------
   Controller Status                   : Okay
   Channel description                 : SAS/SATA
   Controller Model                    : IBM ServeRAID 8k    
   Controller Serial Number            : 20ee0001
   Physical Slot                       : 0
   Copyback                            : Disabled
   Data scrubbing                      : Enabled
   Defunct disk drive count            : 0
   Logical drives/Offline/Critical     : 2/0/0
   ---------------------------------------------------
   Controller Version Information
   ---------------------------------------------------
   BIOS                                : 5.2-0 (15421)
   Firmware                            : 5.2-0 (15421)
   Driver                              : 1.1-5 (2412)
   Boot Flash                          : 5.1-0 (15421)
   ---------------------------------------------------
   Controller Battery Information
   ---------------------------------------------------
   Status                              : Okay
   Over temperature                    : No
   Capacity remaining                  : 100 percent
   Time remaining (at current draw)    : 4 days, 18 hours, 40 minutes
   ---------------------------------------------------
   Controller Vital Product Data
   ---------------------------------------------------
   VPD Assigned#                       : 25R8075
   EC Version#                         : J85096
   Controller FRU#                     : 25R8076
   Battery FRU#                        : 25R8088
 
   
----------------------------------------------------------------------
Logical drive information
----------------------------------------------------------------------
Logical drive number 1
   Logical drive name                  : Logical Drive 1
   RAID level                          : 1
   Status of logical drive             : Okay
   Size                                : 69900 MB
   Read-cache mode                     : Enabled
   Write-cache mode                    : Enabled (write-back)
   Write-cache setting                 : Enabled (write-back) when protected by battery
   Number of chunks                    : 2
   Drive(s) (Channel,Device)           : 0,0 0,1 
Logical drive number 2
   Logical drive name                  : Logical Drive 2
   RAID level                          : 1
   Status of logical drive             : Okay
   Size                                : 69900 MB
   Read-cache mode                     : Enabled
   Write-cache mode                    : Enabled (write-back)
   Write-cache setting                 : Enabled (write-back) when protected by battery
   Number of chunks                    : 2
   Drive(s) (Channel,Device)           : 0,2 0,3 

Device Name of Cisco Unified Mobile Communicator Must Not Exceed 15 Characters Before 8.0(1) Upgrade

Before you upgrade to Cisco Unified Communications Manager 8.0(1), ensure that the device name of a Cisco Unified Mobile Communicator does not exceed 15 characters in Cisco Unified Communications Manager Administration. If the device name of a Cisco Unified Mobile Communicator exceeds 15 characters, migration of this device will fail when you upgrade to Cisco Unified Communications Manager 8.0(1) and the following error message gets written to the upgrade log:

InstallFull *ERROR* Name for Cisco Unified Mobile Communicator device(s) must be 15 or 
less, please correct and rerun upgrade.

If an existing Cisco Unified Mobile Communicator device name specifies a longer name, shorten the device name to 15 or fewer characters before the upgrade.

Making Configuration Changes After an Upgrade

The administrator must not make any configuration changes to Cisco Unified Communications Manager during an upgrade. Configuration changes include any changes that you make in Cisco Unified Communications Manager Administration, Cisco Unified Serviceability, and the User Option windows.

If you are upgrading your system, you must complete the upgrade tasks in this section before you perform any configuration tasks.


Caution If you fail to follow these recommendations, unexpected behavior may occur; for example, ports may not initialize as expected.

Upgrade Tasks

To successfully complete the upgrade, perform the upgrade tasks in the following order before you begin making configuration changes.


Note Cisco strongly recommends that you do not perform configuration tasks until the upgrade completes on all servers in the cluster, until you have switched the servers over to the upgraded partition, and until you have verified that database replication is functioning.


Procedure


Step 1 Stop all configuration tasks; that is, do not perform configuration tasks in the various Cisco Unified Communications Manager-related GUIs or the CLI (with the exception of performing the upgrade in the Cisco Unified Communications Operating System GUI).


Tip For detailed information about the upgrade process, see Chapter 7, "Software Upgrades", in the Cisco Unified Communications Operating System Administration Guide.


Step 2 Upgrade the first node in the cluster (the publisher node).

Step 3 Upgrade the subsequent nodes in the cluster (the subscriber nodes).

Step 4 Switch over the first node to the upgraded partition.

Step 5 Switch over subsequent nodes to the upgraded partition.


Note You can switch the subsequent nodes to the upgraded partition either all at once or one at a time, depending on your site requirements.


Step 6 Ensure that database replication is functioning between the first node and the subsequent nodes. You can check database replication status by using one of the following methods:

In Cisco Unified Reporting, access the Unified CM Database Status report. Before you proceed, ensure the report indicates that you have a good database replication status with no errors. For more information about using Cisco Unified Reporting, see the Cisco Unified Reporting Administration Guide.

In the Cisco Unified Real-Time Monitoring Tool, access the Database Summary service under the CallManager tab to monitor database replication status. The following list indicates the database replication status progress:

0— Initializing.

1—Replication setup script fired from this node.

2—Good replication.

3—Bad replication.

4—Replication setup did not succeed.

Before you proceed, ensure that you have a good database replication status. For more information about using the Cisco Unified Real-Time Monitoring Tool, see the Cisco Unified Real-Time Monitoring Tool Administration Guide.

Step 7 When all other upgrade tasks are complete, you can perform any needed configuration tasks as required.


Upgrade Paths to Cisco Unified Communications Manager 8.0(1)

For information about supported Cisco Unified CM upgrades, see the Cisco Unified Communications Manager Software Compatibility Matrix at the following URL:

http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/compat/ccmcompmatr.html

Ordering the Upgrade Media

To upgrade to Cisco Unified CM Release 8.0(1), use the Product Upgrade Tool (PUT) to obtain a media kit and license or to purchase the upgrade from Cisco Sales.

To use the PUT, you must enter your Cisco contract number (Smartnet, SASU or ESW) and request the DVD/DVD set. If you do not have a contract for Cisco Unified Communications Manager, you must purchase the upgrade from Cisco Sales.

For more information about supported Cisco Unified CM upgrades, see the Cisco Unified Communications Manager Software Compatibility Matrix at the following URL:

http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/compat/ccmcompmatr.html

See the "Software Upgrades" chapter of the Cisco Unified Communications Operating System Administration Guide.

Upgrading from a Local Source

To upgrade the software from local DVD, follow this procedure:

Procedure


Step 1 If you do not have a Cisco-provided upgrade disk, create an upgrade disk by burning the upgrade file that you downloaded onto a DVD as an ISO image.


Note Just copying the .iso file to the DVD will not work. Most commercial disk burning applications can create ISO image disks.


Step 2 Insert the new DVD into the disc drive on the local server that is to be upgraded.

Step 3 Log in to Cisco Unified Communications Operating System Administration.

Step 4 Navigate to Software Upgrades > Install/Upgrade.

The Software Installation/Upgrade window displays.

Step 5 From the Source list, choose DVD.

Step 6 Enter a slash (/) in the Directory field.

Step 7 To disable throttling, check the Disable I/O throttling check box.


Caution Although disabling throttling decreases the time it takes to perform the upgrade, it may degrade system performance. For more information about throttling and the causes of slow upgrades, see the "I/O Throttling" section.

If you want to reenable throttling after you start the upgrade, you must cancel the upgrade, reenable throttling, and then restart the upgrade.

Step 8 To continue the upgrade process, click Next.

Step 9 Choose the upgrade version that you want to install and click Next.

Step 10 In the next window, monitor the progress of the install.

Step 11 If you want to install the upgrade and automatically reboot to the upgraded partition, choose Reboot to upgraded partition. The system restarts and is running the upgraded software.

Step 12 If you want to install the upgrade and then manually reboot to the upgraded partition at a later time, do the following steps:

a. Choose Do not reboot after upgrade.

b. Click Next.

The Upgrade Status window displays the Upgrade log.

c. When the installation completes, click Finish.

d. To restart the system and activate the upgrade, choose Settings > Version; then, click Switch Version.

The system restarts running the upgraded software.


Upgrading from a Remote Source

To upgrade the software from a network location or remote server, use the following procedure.


Note Do not use the browser controls, such as Refresh/Reload, while you are accessing Cisco Unified Operating System Administration. Instead, use the navigation controls that are provided by the interface.


Procedure


Step 1 Put the upgrade file on an FTP or SFTP server that the server that you are upgrading can access.

If you are upgrading from a supported 5.1(x) release, the upgrade requires a set of files, called a patch set. Put the patch set files on the FTP or SFTP server by using one of these methods:

a. If you have a Cisco-provided upgrade disk, copy the contents of the disk to the remote server.

b. If you downloaded the upgrade files, copy the files you downloaded to the remote server.

Step 2 Log in to Cisco Unified Communications Operating System Administration.

Step 3 Navigate to Software Upgrades > Install/Upgrade.

The Software Installation/Upgrade window displays.

Step 4 From the Source list, choose Remote Filesystem.

Step 5 In the Directory field, enter the path to the directory that contains the patch file on the remote system.

If the upgrade file is located on a Linux or Unix server, you must enter a forward slash at the beginning of the directory path. For example, if the upgrade file is in the patches directory, you must enter /patches

If the upgrade file is located on a Windows server, remember that you are connecting to an FTP or SFTP server, so use the appropriate syntax, including

Begin the path with a forward slash (/) and use forward slashes throughout the path.

The path must start from the FTP or SFTP root directory on the server, so you cannot enter a Windows absolute path, which starts with a drive letter (for example, C:).

Step 6 In the Server field, enter the server name or IP address.

Step 7 In the User Name field, enter your user name on the remote server.

Step 8 In the User Password field, enter your password on the remote server.

Step 9 Select the transfer protocol from the Transfer Protocol field.

Step 10 To disable throttling, check the Disable I/O throttling check box.


Caution Although disabling throttling decreases the time it takes to perform the upgrade, it may degrade system performance. For more information about throttling and the causes of slow upgrades, see the "I/O Throttling" section.

If you want to reenable throttling after you start the upgrade, you must cancel the upgrade, reenable throttling, and then restart the upgrade.

Step 11 To continue the upgrade process, click Next.

Step 12 Choose the upgrade version that you want to install and click Next.

If you are upgrading from Cisco Unified Communications Manager Release 5.1(x), the upgrade requires a set of files that are called a patch set. Choose the upgrade version to install from the list. The upgrade version name does not include any file extensions, because it represents a patch set.

If you are upgrading from Cisco Unified Communications Manager Release 6.x or 7.x, the upgrade file has the extension sgn.iso.

Step 13 In the next window, monitor the progress of the download.


Note If you lose your connection with the server or close your browser during the upgrade process, you may see the following message when you try to access the Software Upgrades menu again:

Warning: Another session is installing software, click Assume Control to take over the installation.

If you are sure you want to take over the session, click Assume Control.

If Assume Control does not display, you can also monitor the upgrade with the Cisco Unified Real Time Monitoring Tool.


Step 14 If you want to install the upgrade and automatically reboot to the upgraded partition, choose Reboot to upgraded partition. The system restarts and runs the upgraded software.

Step 15 If you want to install the upgrade and then manually reboot to the upgraded partition at a later time, do the following steps:

a. Choose Do not reboot after upgrade.

b. Click Next.

The Upgrade Status window displays the Upgrade log.

c. When the installation completes, click Finish.

d. To restart the system and activate the upgrade, choose Settings > Version; then, click Switch Version.

The system restarts and is running the upgraded software.


The Latest Software Upgrades for Unified CM 8.0 on Cisco.com

You can access the latest software upgrades for this release of Unified CM from http://www.cisco.com/kobayashi/sw-center/sw-voice.shtml.

Service Updates

After you install or upgrade to this release of Cisco Unified Communications Manager, check to see if Cisco has released critical patches or Service Updates. Service Updates, or SUs, contain fixes that were unavailable at the time of the original release, and often include security fixes, firmware updates, or software fixes that could improve operation.

To check for updates, from www.Cisco.com, select Support > Download Software . Navigate to the "Voice and Unified Communications" section and select IP Telephony > Call Control > Cisco Unified Communications Manager (CallManager) > the appropriate version of Cisco Communications Manager for your deployment.

For continued notification of updates for your Cisco products, subscribe to the Cisco Notification Service at:

http://www.cisco.com/cisco/support/notifications.html

Related Documentation

You can view documentation that supports this release of Cisco Unified CM at http://www.cisco.com/en/US/products/sw/voicesw/ps556/tsd_products_support_series_home.html

Limitations and Restrictions

A list of compatible software releases represents a major deliverable of Cisco Unified Communications Manager 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 and contact center components that were tested for interoperability with Cisco Unified Communications Manager 8.0(1) as part of Cisco Unified Communications System Release 8.1 testing, see

http://www.cisco.com/go/unified-techinfo


Note Be aware that the release of Cisco IP telephony products does not always coincide with Cisco Unified Communications Manager releases. If a product does not meet the compatibility testing requirements with Cisco Unified CM, you need to wait until a compatible version of the product becomes available before you can upgrade to Cisco Unified CM Release 8.0(1). For the most current compatibility combinations and defects that are associated with other Cisco Unified CM products, refer to the documentation that is associated with those products.


Important Notes

The following section contains important information that may have been unavailable upon the initial release of documentation for Cisco Unified Communications Manager Release 8.0(1).

CSCtb31860 Transcoding G.711 to All Codecs Supported

CSCtw61986 Disable LRO on Cisco Unified Computing Systems running ESXi 4.1

CSCto57498 Upgrading to Cisco Unified Communications Manager Release 8.x from Release 7.x

CSCtd69640 Downtime when upgrading Publisher server until all Subscriber servers are updated

CSCte39796 Increase database replication timeout when upgrading large clusters

CSCsy57492 Hold Reversion Notification Interval for SCCP and SIP phones

New License Required when Replacing Motherboard (CSCtz12589 and CSCtz12651)

Limitations to Call Park Feature

CSCtg50662 Bridge Upgrade: Some Services Fail to Register with Disaster Recovery Framework

CSCtd09050 Service Parameter Name/Usage Change from CTIWildCardDNAsCalledParty to CTIWildCardDNInCallInfo

Node Licenses Missing After an Upgrade

CSCtd01766 Destination Port on Trunk Remains Unchanged After Upgrade

CSCte91815 Cisco Phone Designer Does Not Work with Phone

Do Not Run Unified CM 8.0(1) on a VMware Virtual Machine Server

Cisco Intercompany Media Engine is Not Available

CSCte49213 ChangeCredential: Non-ASCII Character Use Causes Question Marks to Display in Success Message

Two New Security Features

CSCte53189 Changing More Than One Parameter at a Time on the CCD Requesting Service Causes Stale DN

CSCte36097 DRS Fails at Database Component

Disaster Recovery System Caution

CSCte47453 Installation Process Does Not Backup Component Files from Subscriber Server

EMCC Login Affects Settings in Product-Specific Configuration Layout of Phone Configuration Window

CSCtd94318 MCS-7845-I3 Server Locks Up After Integrated Management Module gets Restarted

CSCtj61834 MLPP Default Domain Name Displays MLPP ID Value

CSCtr40861 Incoming Calling Party Numbers should be up to 16 characters

CSCtr89029 URL Parameters for Secured Phones Repopulated After Restart

CSCte44108 Call Control Discovery Limitation

CSCtj37643 Installing Language Prompts for TAPS

CSCtx00678 Do not use Voicemail for Alerting Name or ASCII Alerting Name

CSCtx86215 Database Replication

CSCsu23100 Missing Information on Special Characters

CSCtx92282 Cisco Unified IP Phones 9951 and 9971 support SIP Dial Rules

CSCtr44481 Download Dial Plans for Cisco Unified Communications Manager Release 8.X

"CSCtc71174 Call Park and Directed Call Park Restriction" section

"CSCtg71595 Allowed characters for Cluster ID field" section

CSCtb58649 Sample query cannot list multiple users

CSCuc10415 Tip for Adding a New Server

CSCuc23992 Call Preservation support for SIP trunks

CSCuc79185 Device Mobility Calling Search Space is Used When Device CSS is <none>

CSCuc79185 Missing Exceptions for Voice-Mail Pilot

CSCud34740 Application User AXL Password Must Not Contain Special Characters

CSCud70447 Missing Etoken Recovery Steps in Troubleshooting Guide

CSCud95087 Limitation of SIP Forking on Trunk Not Documented

CSCui20049 Restructure of Disaster Recovery Documentation for Restore Scenarios

CSCtb31860 Transcoding G.711 to All Codecs Supported

The transcoder supports transcoding between G.711 and all codecs, including G.711, when functioning as a transcoder and when providing MTP/TRP functionality.

CSCtw61986 Disable LRO on Cisco Unified Computing Systems running ESXi 4.1

Disable Large Receive Offload (LRO) for deployments on Cisco Unified Computing System (UCS) servers running ESXi 4.1 to eliminate LRO-related network errors.


Step 1 Log into the ESXi host or its vCenter with vSphere Client.

Step 2 Select the host, and then select Configuration > Software:Advanced Settings.

Step 3 Select Net and scroll down slightly more than half way.

Step 4 Set the following parameters from 1 to 0:

Net.VmxnetSwLROSL

Net.Vmxnet3SwLRO

Net.Vmxnet3HwLRO

Net.Vmxnet2SwLRO

Net.Vmxnet2HwLRO

Step 5 Reboot the ESXi host to activate these changes.

CSCto57498 Upgrading to Cisco Unified Communications Manager Release 8.x from Release 7.x

To upgrade your cluster from Release 7.x to Release 8.x, follow this procedure:

Procedure


Step 1 Follow the normal procedure for upgrading a cluster.


Tip After you finish upgrading all nodes in the cluster to Cisco Unified Communications Manager Release 8.x, you must also follow all the steps in this procedure to ensure that your Cisco Unified IP Phones register with the system.


Step 2 If you are running one of the following releases in mixed mode, you must run the CTL client:

Cisco Unified Communications Manager Release 7.1(2)

All regular releases of 7.1(2)

All ES releases of 712 prior to 007.001(002.32016.001)

Cisco Unified Communications Manager Release 7.1(3)

All regular releases of 713 prior to 007.001(003.21900.003) = 7.1(3a)su1a

All ES releases of 713 prior to 007.001(003.21005.001)


Note For more information about running the CTL client, see Chapter 4, "Configuring the CTL Client," in the Cisco Unified Communications Manager Security Guide.


Restart the Cisco TFTP Service on the TFTP Servers

Step 3 From Cisco Unified Serviceability, choose Tools > Control Center - Feature Services.

The Control Center - Feature Services window displays.

Step 4 Restart the Cisco TFTP service on each node on which it is active.

Step 5 Wait five minutes for TFTP to rebuild the files.

Reset all Cisco Unified IP Phones


Note You must reset all the Cisco Unified IP Phones in the cluster to ensure that the phones have the most current configuration.


Step 6 From Cisco Unified Communications Manager Administration, choose System > Enterprise Parameters.

The Enterprise Parameters Configuration window displays.

Step 7 Click Reset.

Step 8 Wait ten minutes for the Cisco Unified IP Phones to register with Cisco Unified Communications Manager.

Back Up Your Cluster


Caution You must back up your cluster using the Disaster Recovery System (DRS) to be able to recover the cluster.

Step 9 To backup your cluster using DRS, see the Disaster Recovery System Administration Guide.


CSCtd69640 Downtime when upgrading Publisher server until all Subscriber servers are updated

When upgrading the publisher node, there will be a temporary server outage until all subscriber nodes get upgraded to the new software version.

CSCte39796 Increase database replication timeout when upgrading large clusters

Use the utils dbreplication setrepltimeout CLI command to increase the database replication timeout value when upgrading large clusters so that more subscriber servers have sufficient time to request replication. When the timer expires, the first subscriber server, plus all other subscriber servers that requested replication within that time period, begin a batch data replication with the publisher server. The default database replication timeout value is 300 (5 minutes). Restore the timeout to the default value after the entire cluster upgrades and the subscriber servers have successfully set up replication. For more information, see the Command Line Interface Guide for Cisco Unified Communications Solutions.

CSCsy57492 Hold Reversion Notification Interval for SCCP and SIP phones

SCCP phones support a minimum Hold Reversion Notification Interval (HRNI) of 5 seconds, whereas SIP phones support a minimum of 10 seconds. SCCP phones set for the minimum HRNI of 5 seconds may experience a Hold Reversion Notification ring delay of 10 seconds when handling calls involving SIP phones.

New License Required when Replacing Motherboard (CSCtz12589 and CSCtz12651)

A new license file is required if you are installing a replacement motherboard in publisher servers or single servers that are not part of a cluster.

Limitations to Call Park Feature

The Call Park feature has the following known limitations:

CSCsz18443 Cisco Unified IP Phone 8961, 9951, 9971 Registered to a Node may Use the Call Park Number Assigned to Another Node

CSCsz31137 Parked Call Gets Reverted When the Parkee is on

CSCsz35994 Incorrect Display for Park Monitoring Forward No Retrieve

CSCtb53159 Display Limitation in ConfList

CSCsz18443 Cisco Unified IP Phone 8961, 9951, 9971 Registered to a Node may Use the Call Park Number Assigned to Another Node

Call Park numbers get configured on the nodes of a Cisco Unified Communications Manager cluster (first/subsequent). Call Park numbers are normally allocated from the node that initiates the call. If the Cisco Unified IP Phone 8961, 9951, 9971 that initiates the call is registered to the first node of the Cisco Unified Communications Manager cluster, then a Call Park number configured on the first node gets used to park the call. This is irrespective of the node to which the called party is registered, or which party (calling or called) invokes the Call Park feature.

For example, if a phone registered to the first node initiates a call to a phone registered to the second node, then regardless of which phone invokes the Call Park feature, a Call Park number configured on the first node is always used.

Similarly, if the Call Park feature gets invoked when a phone in the second node is the call initiator, then a Call Park number configured on the second node is used.


Note Be aware that you can restrict the Call Park feature only by using calling search space and partitions. Not configuring a Call Park number on a node will not ensure that the Call Park feature is not available to the phones in that node.


CSCsz31137 Parked Call Gets Reverted When the Parkee is on

When an inter-cluster parked call connected by an Intercluster Trunk ( ICT) is put on hold, the call reverts when the Park Monitoring Reversion Timer and the Park Monitoring Forward No Retrieve Timer expire. Such a call reverts even though the parkee is on hold. This is a known limitation of inter-cluster calls connected via ICT that use the Call Park feature.

CSCsz35994 Incorrect Display for Park Monitoring Forward No Retrieve

For inter-cluster parked called connected by an ICT, after the Park Reversion Timer and Park Monitoring Forward No Retrieve Timer expire, the call gets forwarded to the Park Monitoring Forward No Retrieve destination. The display of the incoming call is incorrect on the destination device.

The display on the device is "From DN" instead of "Forwarded for DN". For example, if the initial call is an inter-cluster call via ICT from DN 1000 to DN 3000 and gets forwarded to DN 2000, the display on DN 2000 is "From 3000" instead of "Forwarded for 1000".

CSCtb53159 Display Limitation in ConfList

You can add as many conference participants as the conference bridge supports; however, ConfList only displays 16 participants. From the 17th participant onwards, the list displays only the latest 16 participants.

CSCtg50662 Bridge Upgrade: Some Services Fail to Register with Disaster Recovery Framework

Conditions

When you perform a bridge upgrade to Cisco Unified Communications Manager 8.0(1), services that are not activated before the upgrade do not register with Disaster Recovery Framework (DRF) and the associated data does not get backed up. When the restore completes on the new hardware, this situation becomes apparent.

Symptoms

Because data from one or more of the services listed in the Workaround (below) is missing, when the services get activated, the server behaves as if the services were not initialized and not used on the server earlier.

Workaround

Before you begin the bridge upgrade on the old hardware running pre-8.0 software, activate the following services (if they are not already activated) to ensure the associated data gets saved:

Cisco Trace Collection (Network Service)

Cisco Tftp (Feature Service)

Cisco IP Voice Media Streaming App (Feature Service)

Cisco Serviceability Reporter (Feature Service)

Cisco Extended Functions (Feature Service)

Cisco Bulk Provisioning Service (Feature Service)

CSCtd09050 Service Parameter Name/Usage Change from CTIWildCardDNAsCalledParty to CTIWildCardDNInCallInfo

The service parameter "CTI Use Wildcard Pattern as calledPartyDN -" setting also applies to CTI call information fields CallingParty, OriginalCalledParty, and LastRedirectingParty, in addition to the CalledParty field.

The service parameter help text does not provide this information.

Node Licenses Missing After an Upgrade

If the node license file contains multiple features (for example: SW_FEATURE + CCM_NODE), after you upgrade to this release of Cisco Unified Communications Manager, the following licensing warnings might display:

System is operating on insufficient licenses.

Please upload additional license files.

For additional details and workaround, see CSCtf15332.

CSCtd01766 Destination Port on Trunk Remains Unchanged After Upgrade

During an upgrade to an unrestricted Cisco Unified CM release, the SIP trunk incoming port gets changed to 5060; however, the destination port on the trunk remains what it was before the upgrade.

CSCte91815 Cisco Phone Designer Does Not Work with Phone

If the HTTPS server configuration is set to "HTTPS only" and the phone has an LSC issued by Cisco Unified CM 8.0 or earlier, the Cisco Phone Designer does not save or preview wallpaper or ringtone to the phone.

Workaround


Step 1 Change the HTTPS server configuration to "HTTP and HTTPS enabled" which allows Phone Designer to fall back to HTTP if the certificate authentication fails.

Step 2 Remove the LSC certificate from the phone and try Phone Designer again.


Do Not Run Unified CM 8.0(1) on a VMware Virtual Machine Server

Cisco recommends that you do not run Cisco Unified Communications Manager Release 8.0(1) on a VMware virtual machine (VM) server (within a Cisco Unified Computing System, Cisco Media Convergence Server or any other hardware). While it is technically possible to license this configuration, Cisco does not support it.

Cisco Intercompany Media Engine is Not Available

The Cisco Intercompany Media Engine server will not be available until a later maintenance release.

CSCte49213 ChangeCredential: Non-ASCII Character Use Causes Question Marks to Display in Success Message

First Scenario

If you are logged into Extension Mobility or Change Credential and your locale allows special (non-ASCII) characters, when you change your PIN by using the SetPin button, question marks display when the PIN change succeeds.

If question marks display under the above conditions, it means that the PIN change succeeded.

Second Scenario

For Extension Mobility, if the PIN option "User Must Change at Next Login" is enabled, and you log into EM, you are redirected to the change PIN window. The redirect message displays as question marks.

If question marks display under the above condition, it indicates "PIN Change is required ..Redirecting Please wait".

Two New Security Features

Two security features exist in this release of Cisco Unified CM. Default for both specifies On.

For more information on these features, refer to:

Disaster Recovery System Administration Guide for Cisco Unified Communications Manager Business Edition Release 8.0(1)

Cisco Unified Communications Manager Security Guide, Release 8.0(1)

CSCte53189 Changing More Than One Parameter at a Time on the CCD Requesting Service Causes Stale DN

To avoid a race condition resulting in stale DN patterns, Cisco recommends that you change only one parameter at a time on the CCD Requesting Service.

However, if you see this problem as a result of attempting to change more than one parameter at a time, add an SAF trunk running on all nodes in the cluster to overwrite the stale DN patterns

CSCte36097 DRS Fails at Database Component

During a publisher server replacement, DRS fails at the database component for all subscriber servers.

Workaround

Contact Cisco TAC.

Disaster Recovery System Caution

When you restore your data, the hostname, server IP address, and the deployment type must be the same as it was during the backup. DRS does not restore across different hostnames, IP addresses and deployment types.

CSCte47453 Installation Process Does Not Backup Component Files from Subscriber Server

Occasionally, after an upgrade, some services are not registered to DRS.

Workaround


Step 1 During the maintenance window, log into the publisher server CLI and execute the utils disaster_recovery show_registration servername command.

This command lists all the components registered with DRS for backup on the specified subscriber server.

Step 2 Deactivate and reactivate any component that is not registered for backup from that server.

Step 3 Execute the utils disaster_recovery show_registration servername command again to verify the component is registered for backup.


EMCC Login Affects Settings in Product-Specific Configuration Layout of Phone Configuration Window

When a user uses a phone in a visiting cluster to log into the user Extension Mobility profile, the phone inherits the default provisioning, network, and security settings (specifically, the configuration in the Product Specific Configuration Layout section of the Phone Configuration window) from the home cluster. This behavior may override local security and network settings that are in place in the visiting cluster. Some of the parameters have firmware defaults that the system administrator cannot change until a fix is provided.

CSCtd94318 MCS-7845-I3 Server Locks Up After Integrated Management Module gets Restarted

The Cisco Unified CM MCS-7845-I3 server becomes unresponsive after the Integrated Management Module (IMM) module gets restarted.

Occassionally, the server becomes unresponsive if IMM gets restarted while the Unified CM OS is operational. Existing SSH sessions may remain connected for a period of time; however, no new connections get made. The CPU may spike to 100% with khubd or kipmi0 processes the top CPU consumers.

Tto recover a server in this unresponsive condition, reboot the server by using IMM.

Workaround

1. Configure IMM before you install Unified CM (For example, change HTTP to HTTPS, or perform necessary firmware updates through IMM).

2. If you need to restart IMM after Unified CM is installed, shut down Unified CM before restarting the IMM module.

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.

CSCtr40861 Incoming Calling Party Numbers should be up to 16 characters

When configuring the Incoming Calling Party Numbers setting, the number of characters you can enter is 16 not 8 for:

Incoming Calling Party National Number Prefix

Incoming Calling Party International Number Prefix

Incoming Calling Party Unknown Number Prefix

Incoming Calling Party Subscriber Number Prefix

You can enter up to 16 characters, which include digits, the international escape character (+), asterisk (*), or the pound sign (#).

CSCtr89029 URL Parameters for Secured Phones Repopulated After Restart

When you delete the Secured Phone URL Parameters in the Enterprise Parameter section of Cisco Unified Communications Manager Administrationand then reboot, the URL Parameters are re-populated by default. After you reboot go to the Secured Phone URL Parameters section and make the correct modifications to the URL and reboot the phones.

CSCto87262 Centralized TFTP with CUCM 8 SBD requires workaround

If you deploy a Centralized TFTP as described in Cisco Unified Communications Manager System Guide with a CUCM 8.X cluster using ITL files, you need to disable the ITL file on the IP Phones by running through the following workaround:

Workaround


Step 1 On the Central TFTP server enable the Enterprise Parameter "Prepare cluster for pre CM-8.0 rollback".

Step 2 Restart TVS and TFTP.

Step 3 Reset all phones to verify they download the new ITL file which disables ITL signature verification.

Step 4 Configure Enterprise Parameter Secure https URLs to use http instead of https.

CSCte44108 Call Control Discovery Limitation

The following information is missing from the "Call Control Discovery" chapter in the Cisco Unified Communications Manager Features and Services Guide.

CCD has a limitation with three clusters (A, B and C), when C learns the advertisements of A and B.

In this scenario, when two clusters (A and B) are present, both of them advertise the same pattern, and cluster B advertises later than cluster A. This behavior overwrites the PSTN failover rule for cluster A which cluster C adopts. If your IP connection is lost, calls from cluster C are always redirected to cluster B via PSTN.

After you delete the cluster B advertisement, the PSTN failover rule still points back to A. If your IP connection is lost, calls from cluster C are redirected to cluster A via PSTN.

CSCtj37643 Installing Language Prompts for TAPS

If you need to install language prompts other than English, you must install the Locale Installer on all nodes in your Cisco Unified CM cluster. After you install the Locale Installer, you must pull the locale specific AAR file that the Locale Installer saves to the Cisco Unified CM TFTP directory and install that file in Cisco Unified CCX.


Step 1 Download the Locale Installer that contains your language from cisco.com.

Step 2 Install the Locale Installer on each Cisco Unified CM cluster node.


Note For detailed installations on installing locales in Cisco Unified CM, see Software Upgrades in the Cisco Unified Communication Operating System Administration Guide.


Step 3 Restart each cluster node.

Step 4 Login to Cisco Unified Operating System Administration, and choose Software Upgrades > TFTP File Management.

Step 5 Search for the AAR file that the Locale Installer installed in Cisco Unified CM's TFTP directory.

Step 6 Login to Cisco Unified Operating System CLI.

Step 7 Use the file get tftp <AAR file name> CLI command to get the file from Cisco Unified CM's TFTP directory..

Step 8 Follow the procedures in Cisco Unified CCX Administration Guide to install and configure the AAR file in Cisco Unified CCX.

CSCtx00678 Do not use Voicemail for Alerting Name or ASCII Alerting Name

Do not use the word "Voicemail" anywhere in the Alerting Name or ASCII Alerting Name fields in the Directory Number Configuration window. If you use the word "Voicemail" Cisco Unity Connection may process the call as a direct Call, rather than as a forwarded call.

CSCtx86215 Database Replication

This section of the Cisco Unified Communications Manager System Issues chapter in the Troubleshooting Guide for Cisco Unified Communications Manager requires this addition:

Extension Mobility does not work when database replication breaks between the Unified CM node running Extension Mobility and the Unified CM node to which the phone is registered.

CSCsu23100 Missing Information on Special Characters

For information on special characters and how they can be used in a dial plan, refer to the Wildcards and Special Characters in Route Patterns and Hunt Pilots topic in the Understanding Route Plans chapter from the Cisco Unified Communications Manager System Guide.

CSCtx92282 Cisco Unified IP Phones 9951 and 9971 support SIP Dial Rules

The SIP Dial Rule Configuration Settings section of the Cisco Unified Communications Manager Administration Guide lists the phones that support SIP dial rules. However, the section omits the Cisco Unified IP Phones 9951 and 9971, both of which support SIP dial rules.

CSCtr44481 Download Dial Plans for Cisco Unified Communications Manager Release 8.X

You can download dial plans for Cisco Unified Communications Manager Release 8.X from the Downloads section of www.cisco.com. On the Cisco website, you can find the Cisco Option Package (COP) file that contains all the available dial plans that you can download, install, and integrate with Cisco Unified Communications Manager. For release 8.x, use the IDP v.3 cop files.

CSCtc71174 Call Park and Directed Call Park Restriction

The following call flow shows a limitation with the Call Park and Directed Call Park features.

1. Phone A calls Phone B.

2. Phone B parks the call. Phone A is now connected to MOH.

3. Phone A presses Hold (Mutual Hold).

4. Phone C dials the parked number through a H323 Trunk.

5. No audio is produced and the call fails after 12 sec (MXTimeout).

In this call flow, when you retrieve a parked call across an H323 ICT that is also on hold, the call fails. By the time phone C tries to retrieve the parked call, the parked party is on hold and Unified CM cannot cut through media.

CSCtg71595 Allowed characters for Cluster ID field

The Cluster ID field in the EMCC Remote Cluster configuration window supports only alphanumeric characters (a-z, A-Z, 0-9), periods (.), and dashes(-). If you enter another character, such as a space or percent sign, you will receive an http error when you click Update Remote Cluster.

CSCtb58649 Sample query cannot list multiple users

To retrieve multiple user queries in Extension Mobility (EM) Service, you must have EM Authentication Proxy Rights. If any other end user's credentials are used to query EM Service, only this end user's information will be retrieved.

CSCuc10415 Tip for Adding a New Server

The following tip needs to be added to the "Server settings" topic in the Cisco Unified Communications Manager Administration Guide.


Tip To avoid errors, Cisco recommends that you add a server to the system with a name that has less than 47 characters. Then, update the server name to the target length.


CSCuc23992 Call Preservation support for SIP trunks

The Call Preservation feature in Cisco Unified Communications Manager also supports SIP trunks. Active calls that cross a SIP trunk do not get interrupted when a Cisco Unified Communications Manager node fails, or when communication between a device and its cluster node fails.

CSCuc79185 Device Mobility Calling Search Space is Used When Device CSS is <none>

The following note is missing from the "Phone Settings" topic in the Cisco Unified Communications Manager Administration Guide:

When set to <none>, Unified CM uses the device mobility calling search space, which is configured on the device pool.

CSCtw44980 Missing Exceptions for Voice-Mail Pilot

The following information is missing for the Voice Mail Pilot Name field description in the "Voice-Mail Pilot Settings" topic in the Cisco Unified Communications Manager Administration Guide:

Allowed characters are numeric (0-9), plus (+), asterisk (*), and pound (#).

CSCud34740 Application User AXL Password Must Not Contain Special Characters

The following note is missing from the Application User Settings topic in the Cisco Unified Communications Manager Administration Online Help:


Note Do not use special characters when you create an AXL password for an application user.


CSCud70447 Missing Etoken Recovery Steps in Troubleshooting Guide

The Cisco Unified Communications Manager Troubleshooting Guide is missing the following procedure for troubleshooting if you lose all security tokens (etokens):

Perform the following procedure if you lose the security tokens and you need to update the CTL file.


Tip Perform the following procedure during a scheduled maintenance window, because you must reboot all servers in the cluster for the changes to take effect.



Step 1 On every Cisco Unified CallManager, Cisco TFTP, or alternate TFTP server, verify that CTLFile.tlv exists from the OS SSH command line.

file list tftp CTLFile.tlv

Step 2 Delete CTLFile.tlv.

file delete tftp CTLFile.tlv

Step 3 Repeat step 1 and step 2 for every Cisco Unified CallManager, Cisco TFTP, and alternate TFTP server.

Step 4 Obtain at least two new security tokens.

Step 5 By using the Cisco CTL client, create the CTL File, as described in "Installing the Cisco CTL Client" and "Configuring the Cisco CTL Client".


Tip If the clusterwide security mode is in mixed mode, the Cisco CTL client displays the message No CTL File exists on the server but the CallManager Cluster Security Mode is in Mixed Mode. For the system to function, you must create the CTL File and set CallManager Cluster to Mixed Mode. Click OK; then, choose Set CallManager Cluster to Mixed Mode and complete the CTL file configuration.


Step 6 Reboot all the servers in the cluster.

Step 7 After you create the CTL file on all the servers and reboot all servers in the cluster, delete the CTL file from the phone, as described in "Deleting the CTL File on the Cisco Unified IP Phone".

CSCud95087 Limitation of SIP Forking on Trunk Not Documented

The following information is missing from "Understanding Session Initiation Protocol" in the Cisco Unified Communications Manager System Guide:

Cisco Unified CallManager Release 4.x does not accept provisional responses (such as 180 Ringing) from more than five destinations. It does not accept a successful response (200 Ok) from any destination that is not among the first five to respond.

Cisco Unified CallManager Release 5.x and Cisco Unified Communications Manager Release 6.x do not accept provisional responses (such as 180 Ringing) from more than 20 destinations. They do not accept a successful response (200 Ok) from any destination that is not among the first 20 to respond.

CSCui20049 Restructure of Disaster Recovery Documentation for Restore Scenarios

Restore Scenarios


Caution Be aware that DRS encryption depends on the cluster security password. If you have changed the security password between the backup and this restore, DRS will ask for the old security password. Therefore, to use such old backups, you must remember the old security password or take a backup immediately after the security password change/reset.

You can restore Cisco Unified Communications Manager in the following scenarios:

Restoring a Node or Cluster to a Last Known Good Configuration (No Rebuild)

Restoring the First Node only (Rebuilding the Publisher Alone)

Restoring the Entire Cluster

Restoring Subsequent Cluster Nodes (With or Without Rebuild)

Restoring a Node or Cluster to a Last Known Good Configuration (No Rebuild)


Note Use this procedure only if you are restoring the node to a last known good configuration. Do not use this after a hard drive failure or other hardware failure. If you intend to rebuild the publisher server, read the "Restoring the First Node only (Rebuilding the Publisher Alone)" section. If you intend to rebuild the entire cluster, read the "Restoring the Entire Cluster" section.



Note Extension Mobility Cross Cluster users who logged in to a remote cluster at backup shall remain logged in after restore.



Caution Before you restore Cisco Unified Communications Manager, ensure that the Cisco Unified Communications Manager version that is installed on the server matches the version of the backup file that you want to restore. The Disaster Recovery System supports only matching versions of Cisco Unified Communications Manager for restore. For example, the Disaster Recovery System does not allow a restore from version 7.0( 1).1000-1 to version 7.1( 2).1000-1, or from version 7.1(2).1000- 1 to version 7.1(2).1000- 2. (The last parts of the version number change when you install a service release or an engineering special.) In essence, the product version needs to match, end-to-end, for the Disaster Recovery System to run a successful Cisco Unified Communications Manager database restore. Disaster Recovery System adheres to strict version checking and allows restore only between matching versions of Cisco Unified Communications Manager .


Caution Before you restore Cisco Unified Communications Manager , ensure that the hostname, IP address, and deployment type of the restore matches the hostname, IP address and deployment type of the backup file that you want to restore.

The Restore Wizard walks you through the steps that are required to restore a backup file. To perform a restore, use the procedure that follows.

Procedure


Step 1 Navigate to the Disaster Recovery System. Log in to Cisco Unified Communications Manager Administration, choose Disaster Recovery System from the Navigation menu in the upper, right corner of the Cisco Unified Communications Manager Administration window, and click Go.

The Disaster Recovery System Logon window displays.

Step 2 Log in to the Disaster Recovery System by using the same Administrator username and password that you use for Cisco Unified Communications Operating System Administration.

Step 3 Navigate to Restore > Restore Wizard. The Restore Wizard Step 1 window displays.

Step 4 Choose the backup device from which to restore in the Select Backup Device area. Then, click Next.

The Restore Wizard Step 2 window displays.

Step 5 Choose the backup file that you want to restore.


Note The backup filename indicates the date and time that the system created the backup file.


Step 6 Click Next. The Restore Wizard Step 3 window displays.

Step 7 Choose the features that you want to restore.


Note Only the features that were backed up to the file that you chose display.


Step 8 Click Next. The Restore Wizard Step 4 window displays.

Step 9 Select the Perform file integrity check using SHA1 Message Digest checkbox if you want to run a file integrity check.


Note The file integrity check is optional and is only required in the case of SFTP backups. You do not need to run a file integrity check when restoring from tape and local device backups.



Note Be aware that the file integrity check process consumes a significant amount of CPU and network bandwidth, which considerably slows down the restore process.


Step 10 When you get prompted to choose the node to restore, choose the appropriate node.

Step 11 If the node that you chose is a publisher node, from the Select Server Name drop-down list box, choose the subscriber node from which you want to restore the publisher database. The Disaster Recovery System restores all nondatabase information from the backup file and pulls the latest database from the chosen subscriber node.


Note This option appears only if the backup file that you selected includes the CCMDB database component and if the node that you chose is a publisher node.


Step 12 To start restoring the data, click Restore.


Note If you selected the Perform file integrity check using SHA1 Message Digest checkbox in Step 9, DRS runs a file integrity check on each file when you click Restore. If the system finds discrepancies in any .tar file during the check, the restore process will ERROR out the component that failed the integrity check and move to restore the next .tar file (that is, the next component).



Caution After you choose the node to which you want the data restored, any existing data on that server gets overwritten.


Note If you choose the first node to restore the data, DRS automatically restores the Cisco Unified Communications Manager database on the subsequent nodes. Read "Restoring the First Node only (Rebuilding the Publisher Alone)" section for more details.


Step 13 Your data gets restored on the node that you chose.

Step 14 When the restoration completes and the Percentage Complete field on the Restore Status window in the Disaster Recovery System shows 100 percent, Check the Replication Status value on all nodes by using the "utils dbreplication runtimestate" CLI command as described in the Command Line Interface Reference Guide for Cisco Unified Communications Solutions. The value on each node should be equal 2.


Note Database replication on the subsequent nodes may take enough time to complete depending on the size of the cluster.



Tip If replication does not set up properly, use the "utils dbreplication reset" CLI command as described in the Command Line Interface Reference Guide for Cisco Unified Communications Solutions.


Step 15 If the database replication status is 2, restart the server. For more information on restarting, see the Cisco Unified Communications Operating System Administration Guide.


Note If you are restoring only to the first node, you must restart all nodes in the cluster. Make sure that you restart the subsequent node(s) before you restart the first node.



Note When the subsequent node(s) has restarted and is running the restored version of Cisco Unified Communications Manager, restart the first node.



Restoring the First Node only (Rebuilding the Publisher Alone)

Follow this procedure to restore the first node or publisher server in the cluster.

Procedure


Note Cisco recommends that you perform a fresh installation of Cisco Unified Communications Manager on the first node. For more information on installing Cisco Unified Communications Manager, see Installing Cisco Unified Communications Manager.



Note Extension Mobility Cross Cluster users who logged in to a remote cluster at backup shall remain logged in after restore.



Caution Before you restore Cisco Unified Communications Manager, ensure that the Cisco Unified Communications Manager version that is installed on the server matches the version of the backup file that you want to restore. The Disaster Recovery System supports only matching versions of Cisco Unified Communications Manager for restore. For example, the Disaster Recovery System does not allow a restore from version 6.1.(1).1000-1 to version 6.1(2).1000-1, or from version 6.1.(2).1000-1 to version 6.1(2).1000-2.


Caution Before you restore Cisco Unified Communications Manager, ensure that the hostname, IP address, and deployment type of the restore matches the hostname, IP address and deployment type of the backup file that you want to restore.


Step 1 Navigate to the Disaster Recovery System. Log in to Cisco Unified Communications Manager Administration, choose Disaster Recovery System from the Navigation drop-down list box in the upper, right corner of the Cisco Unified Communications Manager Administration window, and click Go.

The Disaster Recovery System Logon window displays.

Step 2 Log in to the Disaster Recovery System by using the same Administrator username and password that you use for Cisco Unified Communications Operating System Administration.

Step 3 Configure the backup device.

Step 4 Navigate to Restore > Restore Wizard. The Restore Wizard Step 1 window displays.

Step 5 In the Select Backup Device area, choose the backup device from which to restore.

Step 6 Click Next. The Restore Wizard Step 2 window displays.

Step 7 Choose the backup file that you want to restore.


Note The backup filename indicates the date and time that the system created the backup file.


Step 8 Click Next. The Restore Wizard Step 3 window displays.

Step 9 Choose the features that you want to restore.


Note Only the features that were backed up to the file that you chose display.


Step 10 Click Next. The Restore Wizard Step 4 window displays.

Step 11 When you get prompted to choose the nodes to restore, choose only the first node (the publisher).


Caution Do not select the subsequent (subscriber) nodes in this condition as this will result in failure of the restore attempt.

Step 12 (Optional) From the Select Server Name drop-down list box, choose the subscriber node from which you want to restore the publisher database. The Disaster Recovery System restores all nondatabase information from the backup file and pulls the latest database from the chosen subscriber node.


Note This option appears only if the backup file that you selected includes the CCMDB database component. Initially, only the publisher node is fully restored, but when you perform Step 15 and restore the subsequent cluster nodes, the Disaster Recovery System performs database replication and fully synchronizes all cluster node databases. This ensures that all cluster nodes are using current data.



Note Make sure the subscriber node that you chose is up and connected to the cluster. A subscriber node can be added manually tothe cluster in Cisco Unified Communications Manager Administration (System > Server).


Step 13 To start restoring the data, click Restore.

Step 14 Your data gets restored on the publisher node.

Step 15 During the restore process, do not perform any tasks with Cisco Unified Communications Manager Administration or User Options.


Note Restoring the first node restores the whole Cisco Unified Communications Manager database to the cluster. This may take up to several hours based on number of nodes and size of database that is being restored.



Note Depending on the size of your database and the components that you choose to restore, the system can require a few hours to restore.


Step 16 When the restoration completes and the Percentage Complete field on the Restore Status window in the Disaster Recovery System shows 100 percent, Check the Replication Status value on all nodes by using the "utils dbreplication runtimestate" CLI command as described in the Command Line Interface Reference Guide for Cisco Unified Communications Solutions. The value on each node should be equal 2.


Note Database replication on the subsequent nodes may take enough time to complete depending on the size of the cluster.



Tip If replication does not set up properly, use the "utils dbreplication reset" CLI command as described in the Command Line Interface Reference Guide for Cisco Unified Communications Solutions.


Step 17 If the database replication status is 2, restart the server. For more information on restarting, see the Cisco Unified Communications Operating System Administration Guide.


Note If you are restoring only to the first node, you must restart all nodes in the cluster. Make sure that you restart the subsequent node(s) before you restart the first node.



Note When the subsequent node(s) has restarted and is running the restored version of Cisco Unified Communications Manager, restart the first node.



Restoring the Entire Cluster

If a major hard drive failure or upgrade occurs, or in the event of a hard drive migration, you may need to rebuild all nodes in the cluster. Follow these steps to restore an entire cluster:


Tip If you are doing most other types of hardware upgrades, such as replacing a network card or adding memory, you do not need to perform the following procedure.



Note You can restore the whole cluster as a single operation after you rebuild the publisher server and the subscriber servers, or to revert to a known good configuration. You do not need to restore the first node and the subsequent nodes in two separate operations.



Note Extension Mobility Cross Cluster users who logged in to a remote cluster at backup shall remain logged in after restore.



Note Before you restore a cluster, make sure that all nodes in the cluster are up and communicating with the first node. You must perform a fresh install for the nodes that are down or not communicating with first node at the time of the restore.


Procedure


Step 1 Navigate to the Disaster Recovery System. Log in to Cisco Unified Communications Manager Administration, choose Disaster Recovery System from the Navigation drop-down list box in the upper, right corner of the Cisco Unified Communications Manager Administration window, and click Go.

The Disaster Recovery System Logon window displays.

Step 2 Log in to the Disaster Recovery System by using the same Administrator username and password that you use for Cisco Unified Communications Operating System Administration.

Step 3 Configure the backup device.

Step 4 Navigate to Restore > Restore Wizard. The Restore Wizard Step 1 window displays.

Step 5 In the Select Backup Device area, choose the backup device from which to restore.

Step 6 Click Next. The Restore Wizard Step 2 window displays.

Step 7 Choose the backup file that you want to restore.


Note The backup filename indicates the date and time that the system created the backup file.


Step 8 Click Next. The Restore Wizard Step 3 window displays.

Step 9 Choose the features that you want to restore.


Note Only the features that were backed up to the file that you chose display.


Step 10 Click Next. The Restore Wizard Step 4 window displays.

Step 11 When you get prompted to choose the nodes to restore, choose all the nodes in the cluster.


Note The Disaster Recovery System restores the Cisco Unified Communications Manager database (CCMDB) on subsequent nodes automatically when you restore a first node. This may take up to several hours based on number of nodes and size of that database that is being restored.



Note If a subsequent node is down or not connected to the cluster during the cluster restore, the database component restore will skip that node and proceed with the next one. You must perform a fresh install of Cisco Unified Communications Manager on these subsequent nodes.


Step 12 Your data gets restored on all the nodes of the cluster.


Note During the restore process, do not perform any tasks with Cisco Unified Communications Manager Administration or User Options.



Note Depending on the size of your database and the components that you choose to restore, the system can require a few hours to restore.


Step 13 When the restoration completes and the Percentage Complete field on the Restore Status window in the Disaster Recovery System shows 100 percent, Check the Replication Status value on all nodes by using the "utils dbreplication runtimestate" CLI command as described in the Command Line Interface Reference Guide for Cisco Unified Communications Solutions. The value on each node should be equal 2.


Note Database replication on the subsequent nodes may take enough time to complete depending on the size of the cluster.



Tip If replication does not set up properly, use the "utils dbreplication reset" CLI command as described in the Command Line Interface Reference Guide for Cisco Unified Communications Solutions.


Step 14 If the database replication status is 2, restart the server. For more information on restarting, see the Cisco Unified Communications Operating System Administration Guide.


Note If you are restoring only to the first node, you must restart all nodes in the cluster. Make sure that you restart the subsequent node(s) before you restart the first node.



Note When the subsequent node(s) has restarted and is running the restored version of Cisco Unified Communications Manager, restart the first node.



Restoring Subsequent Cluster Nodes (With or Without Rebuild)

Follow this procedure to restore subsequent nodes in the cluster.


Note Extension Mobility Cross Cluster users who logged in to a remote cluster at backup shall remain logged in after restore.


Procedure


Caution Before you restore Cisco Unified Communications Manager, ensure that the Cisco Unified Communications Manager version that is installed on the server matches the version of the backup file that you want to restore. The Disaster Recovery System supports only matching versions of Cisco Unified Communications Manager for restore. For example, the Disaster Recovery System does not allow a restore from version 6.1.(1).1000-1 to version 6.1(2).1000-1, or from version 6.1.(2).1000-1 to version 6.1(2).1000-2.


Caution Before you restore Cisco Unified Communications Manager, ensure that the hostname, IP address, and deployment type of the restore matches the hostname, IP address and deployment type of the backup file that you want to restore.


Step 1 Navigate to the Disaster Recovery System. Log in to Cisco Unified Communications Manager Administration, choose Disaster Recovery System from the Navigation drop-down list box in the upper, right corner of the Cisco Unified Communications Manager Administration window, and click Go.

The Disaster Recovery System Logon window displays.

Step 2 Log in to the Disaster Recovery System by using the same Administrator username and password that you use for Cisco Unified Communications Operating System Administration.


Note If you are restoring the subsequent nodes after a rebuild, you must configure the backup device. For more information, see Managing Backup Devices, page 6.


Step 3 Navigate to Restore > Restore Wizard. The Restore Wizard Step 1window displays.

Step 4 In the Select Backup Device area, choose the backup device from which to restore.

Step 5 Click Next. The Restore Wizard Step 2 window displays.

Step 6 Choose the backup file that you want to restore.


Caution If you restored the first node earlier, you must choose the same backup file that you used to restore the first node to restore subsequent nodes in the cluster.

Step 7 Click Next. The Restore Wizard Step 3 window displays.

Step 8 Choose the features that you want to restore.


Note Only the features that were backed up to the file that you chose display.


Step 9 Click Next. The Restore Wizard Step 4 window displays.

Step 10 When you get prompted to choose the nodes to restore, choose only the subsequent nodes.

Step 11 To start restoring the data, click Restore. Your data gets restored on the subsequent nodes.


Note During the restore process, do not perform any tasks with Cisco Unified Communications Manager Administration or User Options.


Step 12 When the restoration completes and the Percentage Complete field on the Restore Status window in the Disaster Recovery System shows 100 percent, restart the server. For more information on restarting, see the Cisco Unified Communications Operating System Administration Guide.

New and Changed Information

The New and Changed Document for Cisco Unified Communications Manager 8.0(1) provides information on what is new and changed for Release 8.0(1). In this document, you can find new and changed information on the following topics:

Installation, Upgrade, Disaster Recovery System, and CLI

Cisco Unified Communications Operating System

Cisco Unified Communications Manager Administration; for example, menu changes and service and enterprise parameters

Cisco Unified Communications Manager features and applications

Bulk Administration Tool

Security

Cisco Unified Serviceability, Cisco Unified Real-Time Monitoring Tool, Cisco Unified Communications Manager CDR Analysis and Reporting, Call Detail Records, and Cisco Unified Reporting

Cisco Unified IP Phones

APIs

To obtain this document, go to the following URL:

http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/rel_notes/8_0_1/delta/nc-801-cm.html

Caveats

The following sections contain information on how to obtain the latest resolved caveat information and descriptions of open caveats of severity levels 1, 2, and 3.

Caveats describe unexpected behavior on a Cisco Unified Communications 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 Communications Manager Release 8.0 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://tools.cisco.com/Support/BugToolKit.


UsingBug Toolkit

The system grades known problems (bugs) according to severity level. These release notes contain descriptions of the following bug levels:

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 the Software Bug Toolkit, follow these steps:

Procedure


Step 1 Access the Bug Toolkit, http://tools.cisco.com/Support/BugToolKit.

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

Step 3 If you are looking for information about a specific problem, enter the bug ID number in the "Search for Bug ID" field, and click Go.



Tip Click Help on the Bug Toolkit page for information about how to search for bugs, create saved searches, create bug groups, and so on.


Open Caveats

Open Caveats for Cisco Unified Communications Manager Release 8.0(1) As of February 23, 2010 describe possible unexpected behaviors in Cisco Unified Communications Manager Release 7.1, which are sorted by component.


Tip For more information about an individual defect, click the associated Identifier in the "Open Caveats for Cisco Unified Communications Manager Release 8.0(1) As of February 23, 2010" section to access the online record for that defect, including workarounds.


Understanding the Fixed-in Version Field in the Online Defect Record

When you open the online record for a defect, you will see data in the "First Fixed-in Version" field. The information that displays in this field identifies the list of Cisco Unified Communications Manager interim versions in which the defect was fixed. These interim versions then get integrated into Cisco Unified Communications Manager 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 Communications Manager 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 Communications Manager release that includes that interim version. You can use these examples as guidance to better understand the presentation of information in these fields.

7.0(2.20000-x) = Cisco Unified Communications Manager Release 7.0(2a)

7.0(2.10000-x) = Cisco Unified Communications Manager Release 7.0(2)

6.1(3.3000-1) = Cisco Unified Communications Manager 6.1(3b)

6.1(3.2000-1) = Cisco Unified Communications Manager 6.1(3a)

6.1(3.1000-x) = Cisco Unified Communications Manager 6.1(3)

5.1(3.7000-x) = Cisco Unified Communications Manager 5.1(3f)


Note Because defect status continually changes, be aware that the "Open Caveats for Cisco Unified Communications Manager Release 8.0(1) As of February 23, 2010" section 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 "UsingBug 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://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl.


Open Caveats for Cisco Unified Communications Manager Release 8.0(1) As of February 23, 2010

The following information comprises unexpected behavior (as of February 23, 2010) that you may encounter in Release 8.0(1) of Cisco Unified Communications Manager.

Table 3 Cisco Unified Communications Manager Release 8.0(1) Open Caveats as of February 23, 2010 

Id

Component

Headline

CSCte93570

axl

TCT COP file / AXL issue exists.

CSCstb80964

cmcti

Race condition caused by Remote Access Connection not handled properly.

CSCte18855

cmui

Incomplete upgrade logging information displays in OS Admin window.

CSCte66048

cmui

Unmapped exceptionmessage displays.

CSCtf17766

cmui

Cannot add CKEM to RT phones.

CSCtd83214

cp-devicemanager

Abnormal reset/restart received during EMCC login/logout.

CSCtf14238

cp-h323

Unified CM sends a disconnect for a G.729 endpoint in H.323 deployment.

CSCte87629

cp-linecontrol

CUCM publish incorrect info to CUPS.

CSCtf04404

cp-linecontrol

Unable to drop held call from CUPC.

CSCtf01379

cp-mediacontrol

RSVPAgent DSCP does not get updated if call is de-escalated from video to audio call by remote cluster.

CSCte36991

cp-mediacontrol

Video gets lost on hairpin sTransfer call with multiple hold/resume.

CSCte84307

cp-mediacontrol

When ACF bandwidth is for audio only, OLC for video is still sent.

CSCte71728

cp-mediacontrol

Unified CM cores and clears calls with mixed bit rate video and H.235 H.239.

CSCtf01534

cp-mobility

User to Number Matching feature does not work )using a special gateway for SNR).

CSCte94447

cp-mobility

finalCalledPartyPartition is not correct in CDR for SNR call.

CSCtf04411

cp-mobility

RDNIS is populated in Calling Party on Mobility Connect calls.

CSCte80963

cp-sip-trunk

Transfer calls fail due to out-of-sequence SIP messages.

CSCtf09981

cp-sip-trunk

Unified CM does not attempt to re-establish the TCP connection when receiving RST.

CSCtf10011

cp-sip-trunk

CUCM -sip- PGW hold/resume fails in PGW VIP failure scenario with DNS

CSCtf10054

cp-sip-trunk

Unified CM sends UPDATE to wrong PGW VIP based on DNS responses.

CSCtf00718

cp-sip-trunk

Hold resume fails for a E2E RVSP call.

CSCte93290

cp-sip-trunk

T38 fax relay not working over SIP trunks.

CSCte73200

cp-subnotframework

SIP URI in BLF speed dial causes malformed URL in Unified CM presence module.

CSCte41670

cpi-appinstall

TCP connection loss to CLI causes install to fail.

CSCtd88137

cpi-os

show memory modules displays error message.

CSCte58231

cpi-os

Update iLO firmware to 1.81.

CSCtd14034

cpi-security

IMPORTANT TLS/SSL SECURITY UPDATE - RedHat OS

CSCte72234

cpi-security

When primary DNS is changed, cluster manager should restart automatically.

CSCte66893

curt

CURT shows hidden phone models in Unified CM Phone Feature List report.

CSCtc22869

database

Ctrl+C for show tech database dump causes the server to stop functioning.

CSCte17401

database

Out of memory test hits Assert fails: rslock.c Line 2617.

CSCtd91156

database

Dbmon core dump occurred.

CSCta25463

database-ids

Errors 566, 116 and 7442 occur insufficient memory exists.

CSCtd31951

database-ids

When you attempt a publisher server restore by using DRS, database replication does not complete.

CSCtc34902

database-ids

Lock table.overflow on large insert/update causes af on engine.

CSCta20147

database-ids

ph_alert/ph_task fills up rootdbs with repeated alarms.

CSCtf04343

database-ids

Assert fail in IDS version 11.50.UC5X9.

CSCte76132

database-ids

PMR 28758 assert fail while running "out of memory" test

CSCtb36399

jtapisdk

All CTI ports and route points go out of service.

CSCta36165

licensing

License Manager causes a registration loop with Auto Registration.

CSCtd14027

security

IMPORTANT TLS/SSL SECURITY UPDATE - JDK

CSCte67321

smdiservice

CMI requires server reboot to start.

CSCtb13891

tapisdk

TSP upgrade from 6.x to 7.x and then to 8.x fails with other language.

CSCte75390

tapisdk

NICE recording application (TSP/CTI integrated) cannot record calls going to certain users.

CSCtf01508

tapisdk

Phone unregisters.


Documentation Updates

The Updates to Cisco Unified Communications Manager 8.0(x) Documentation document provides information about documentation omissions, errors, or updates that are not included in the documentation that supports the Unified CM 8.0(x) release train.To obtain this document, go to the following URL:

http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/rel_notes/8_0_1/80x_cucm_doc-updates.html.

Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, submitting a service request, and gathering additional information, 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

Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop by using a reader application. Be aware that the RSS feeds are a free service, and Cisco currently supports RSS version 2.0.