Guest

Cisco Unified Communications Manager (CallManager)

Release Notes for Cisco Unified Communications Manager Release 8.0(2b) (Deferred)

  • Viewing Options

  • PDF (676.8 KB)
  • Feedback
Release Notes for Cisco Unified Communications Manager Release 8.0(2b)

Table Of Contents

Release Notes for Cisco Unified Communications Manager Release 8.0(2b)

Contents

Introduction

System Requirements

Upgrading to Cisco Unified Communications Manager 8.0(2b)

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(2b) Upgrade

Making Configuration Changes After an Upgrade

Upgrade Paths to Cisco Unified Communications Manager 8.0(2b)

Ordering the Upgrade Media

Upgrading to Unified CM 8.0(2b) by Using the UCSInstall File

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

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)

New and Changed Information for Cisco Unified Communications Manager 8.0(x)

CSCtg50662 Bridge Upgrade: Some Services Fail to Register with DRS

CSCtf96651 IME Call to Unregistered Phones Causes High Active Call Counter

CSCtf99430 IME Fallback Calls Cause High Active Call Counter

CSCtg20299 One-way Video Occurs on Cisco Unified IP Phone 9951/71 Using MeetingPlace via H323 Trunk

CSCtc32084 Cisco Unified IP Phones Cannot Register as SCCP

CSCtd09050 Service Parameter Name/Usage Change from CTIWildCardDNAsCalledParty to CTIWildCardDNInCallInfo

CSCtf46516 ClusterID PKID Changed During Unified CM Upgrade

CSCtd94578 Transfer Using E2E RSVP (SIP Preconditions) Fails

CSCte05285 IBM I3 Servers Automatic Server Restart (ASR) Default Specifies Disabled

Node Licenses Missing After an Upgrade

CSCtd01766 Destination Port on Trunk Remains Unchanged After Upgrade

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

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

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

CSCtx86215 Database Replication

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

CSCtc71174 Call Park and Directed Call Park Restriction

CSCuc10415 Tip for Adding a New Server

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

New and Changed Information

Caveats

Resolved Caveats

UsingBug Toolkit

Open Caveats

Open Caveats for Cisco Unified Communications Manager Release 8.0(2b) As of April 25, 2010

Documentation Updates

Obtaining Documentation and Submitting a Service Request


Release Notes for Cisco Unified Communications Manager Release 8.0(2b)


January 21, 2013

Because of CSCtg50662 Bridge Upgrade: Some Services Fail to Register with DRS, Cisco Unified Communications Manager Release 8.0(2b) 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


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

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.

Table 1 Updates to Release Notes for Cisco Unified Communications Manager 8.0(2b) Release Notes

Date
Change

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.

09-24-12

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

09-10-12

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

08-30-12

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

08-24-12

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

8-9-12

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

7-18-12

Added the CSCte39796 Increase database replication timeout when upgrading large clusters

7-12-12

Added the CSCsy57492 Hold Reversion Notification Interval for SCCP and SIP phones

6-23-12

Added the New License Required when Replacing Motherboard (CSCtz12589 and CSCtz12651)

5-6-10

Added the "CSCtg50662 Bridge Upgrade: Some Services Fail to Register with DRS" section


Contents

This document includes the following information:

Introduction

System Requirements

Upgrading to Cisco Unified Communications Manager 8.0(2b)

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(2b)" 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), a Cisco Unified Computing System (UCS) server, or a Cisco-approved HP server configuration or a Cisco-approved IBM server configuration.

To find which MCS and UCS servers 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(2b).



Note 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(2b). 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. For more information, see http://cisco.com/en/US/docs/voice_ip_comm/cucm/cucos/8_0_1/cucos/iptpch7.html#wp1058411


Table 2 Supported Servers for Basic Integration 

HP Servers
IBM Servers
UCS Servers

MCS-7816-H3

MCS-7815-I2

B200 M1 Blade Server

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(2b)

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(2b)

Ordering the Upgrade Media

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

Upgrading to Unified CM 8.0(2b) by Using the UCSInstall File

Before You Begin

1. Read "CSCtf46516 ClusterID PKID Changed During Unified CM Upgrade" section.

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

3. 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(2b) 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(2b) Upgrade

Before you upgrade to Cisco Unified Communications Manager 8.0(2b), 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(2b) 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(2b)

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(2b) from a release prior to 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 to Unified CM 8.0(2b) by Using the UCSInstall File

Because of its size, the UCSInstall iso file, UCOS_8.0.2.30000-1.sgn.iso, comprises two parts:

UCSInstall_UCOS_8.0.2.30000-1.sgn.iso_part1of2

UCSInstall_UCOS_8.0.2.30000-1.sgn.iso_part2of2

Procedure


Step 1 From the Software Download page on Cisco.com, download the two UCSInstall files.

Step 2 To combine the two files, execute one of the following commands.


Note Because the UCSInstall_UCOS_8.0.2.30000-1 build is a nonbootable ISO, it proves useful only for upgrades. You cannot use it for new installations.


a. If you have a Unix/Linux system, copy and paste the following command into the CLI:

cat UCSInstall_UCOS_8.0.2.30000-1.sgn.iso_part1of2 UCSInstall_UCOS_8.0.2.30000-1.sgn.iso_part2of2 > UCSInstall_UCOS_8.0.2.30000-1.sgn.iso


b. If you have a Windows system, copy and paste the following command into the command prompt (cmd.exe):

COPY /B UCSInstall_UCOS_8.0.2.30000-1.sgn.iso_part1of2+UCSInstall_UCOS_8.0.2.30000-1.sgn.iso_part2of2 UCSInstall_UCOS_8.0.2.30000-1.sgn.iso


Step 3 Use an md5sum utility to verify that the MD5 sum of the final file is correct.

35d1ee91f91565839a3e9523e28870b2 UCSInstall_UCOS_8.0.2.30000-1.sgn.iso

Step 4 Continue by following the instructions in the "Upgrading from a Local Source" section or the "Upgrading from a Remote Source" section.


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(2b) 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(2b). 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(2b).

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)

New and Changed Information for Cisco Unified Communications Manager 8.0(x)

CSCtg50662 Bridge Upgrade: Some Services Fail to Register with DRS

CSCtf96651 IME Call to Unregistered Phones Causes High Active Call Counter

CSCtf99430 IME Fallback Calls Cause High Active Call Counter

CSCtg20299 One-way Video Occurs on Cisco Unified IP Phone 9951/71 Using MeetingPlace via H323 Trunk

CSCtc32084 Cisco Unified IP Phones Cannot Register as SCCP

CSCtd09050 Service Parameter Name/Usage Change from CTIWildCardDNAsCalledParty to CTIWildCardDNInCallInfo

CSCtf46516 ClusterID PKID Changed During Unified CM Upgrade

CSCte05285 IBM I3 Servers Automatic Server Restart (ASR) Default Specifies Disabled

Node Licenses Missing After an Upgrade

CSCtd01766 Destination Port on Trunk Remains Unchanged After Upgrade

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, page 18

CSCte47453 Installation Process Does Not Backup Component Files from Subscriber Server

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

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

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

CSCtx86215 Database Replication

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

CSCtc71174 Call Park and Directed Call Park Restriction

CSCuc10415 Tip for Adding a New Server

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

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

New and Changed Information for Cisco Unified Communications Manager 8.0(x)


Note Information about the new and updated features that exist in Cisco Unified Communications Manager 8.0(x) is contained in a new document, New and Changed Information for Cisco Unified Communications Manager 8.0(x).


The New and Changed Information for Cisco Unified Communications Manager 8.0(x) provides information on what is new and changed for Release 8.0(x).

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

CSCtg50662 Bridge Upgrade: Some Services Fail to Register with DRS

Conditions

When you perform a bridge upgrade to Cisco Unified Communications Manager 8.0(2b), 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)

CSCtf96651 IME Call to Unregistered Phones Causes High Active Call Counter

In Cisco Unified Communications Manager Release 8.0(2), an IME call to unregistered phones caused high active call counter.

Cisco Unified Communications Manager Release 8.0(2b) resolves this defect.

CSCtf99430 IME Fallback Calls Cause High Active Call Counter

In Cisco Unified Communications Manager Release 8.0(2), users experienced high active call counter on IME fallback calls.

Cisco Unified Communications Manager Release 8.0(2b) resolves this defect.

CSCtg20299 One-way Video Occurs on Cisco Unified IP Phone 9951/71 Using MeetingPlace via H323 Trunk

When Cisco Unified IP Phone 9951/71 users dial into a MeetingPlace conference over H323 trunk (Cisco Unified Communications Manager Inter-Cluster), video does not display. This problem occurs intermittently.

Workaround

Hold and resume the call.

Deploy SIP trunk between Cisco Unified Communications Managers.

CSCtc32084 Cisco Unified IP Phones Cannot Register as SCCP

Previously configured Cisco Unified IP Phones 7940/60 attempt and fail to auto-register as SIP.

Sniffer traces show failed TFTP transfer of SEP<MAC>.cnf.xml , SIP and XMLDefault.cnf.xml error code 11.


Note Other second generation Cisco IP phones, such as the Cisco Unified IP 7902, 7905, 7910 and 7912 phones may be affected as well. These devices cannot register as SIP, so fail to register as SCCP.


Workaround

If the cluster has been upgraded to 8.0(1) or 8.0(2) and the Cisco Unified IP Phones 7940 or 7960 fail to register, modify the device defaults load for 7940 and 7960 "SIP" to utilize a SCCP phone load.


Note To avoid this issue, if you plan to upgrade to 8.0(1) or 8.0(2), apply the workaround after the publisher server gets upgraded, but before you upgrade subscriber servers where phones are registered.


Additional Information

For more information see CSCtc32084.

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.

CSCtf46516 ClusterID PKID Changed During Unified CM Upgrade

If you have SAF CCD service configured, after upgrading from release 8.0.(1) to release 8.0.(2x), the SAF CCD advertised routes (Directory Numbers) may be unroutable on the same cluster on which they originated. The error that Cisco Unified CM receives is "unallocated number" and users hear "This number has been disconnected".

Workaround

Administrator should reset Requesting Service on each cluster after the upgrade.

CSCtd94578 Transfer Using E2E RSVP (SIP Preconditions) Fails

When End-to-End RSVP gets enabled for a SIP trunk, an UPDATE message may erroneously contain a Session Description Protocol (SDP), causing blind transfers to fail. Although this issue may not adversely affect calls, you can avoid the problem by disabling End-to-End RSVP on the SIP trunk. To disable End-to-End RSVP, choose Local RSVP from the RSVP Over SIP field on the SIP Profile Configuration window (Device > Device Settings > SIP Profile).

CSCte05285 IBM I3 Servers Automatic Server Restart (ASR) Default Specifies Disabled

In the event of a system lockup, IBM I3 type servers do not automatically restart.

Under rare critical failures, such as a kernel panic, the IBM I3 type platforms do not automatically get restarted by the BIOS ASR functionality. The server remains unresponsive until it is rebooted manually.

Condition

In IMM Control > System Settings > Server Timeouts , the OS Watchdog timeout default specifies disabled.

Workaround

Before you perform the workaround make sure that the following conditions exist:

Cisco Unified CM install is complete and the system is operational

IMM remote management web interface is configured. (For details on how to configure IMM, refer to the hardware documentation.)

Procedure

To change the OS Watchdog configuration setting:

1. Log into the IMM remote management web interface.

2. From IMM Control > System Settings > Server Timeouts, change the OS Watchdog timeout value to 04:00. This configures the timeout to 4 minutes.


Caution Do not configure any other timeout duration.

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.

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, DNS configuration, version, and the deployment type values must match their values during the backup. DRS does not restore across different hostnames, IP addresses, DNS configurations, versions, 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.

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.

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.

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. Use of the word "Voicemail" can cause Cisco Unity Connection to 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.

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.

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.


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.

New and Changed Information


Note Information about the new and updated features that exist in Cisco Unified Communications Manager 8.0(x) is contained in a new document, New and Changed Information for Cisco Unified Communications Manager 8.0(x).


The New and Changed Information for Cisco Unified Communications Manager 8.0(x) provides information about what is new and changed for Release 8.0(x).

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(2b) As of April 25, 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(2b) As of April 25, 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(2b) As of April 25, 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(2b) As of April 25, 2010

The following information comprises unexpected behavior (as of April 25, 2010) that you may encounter in Release 8.0(2b) of Cisco Unified Communications Manager.

Table 3 Open Caveats for Cisco Unified Communications Manager Release 8.0(2b) as of April 25, 2010

Id

Component

Headline

CSCsz39371

ccm-serviceability

PSEC:Fails SNMP default requirement SEC-ACC-CRED.

CSCtg14800

ccmcip

Password with special characters causes ccmcip authentication failure.

CSCtg33030

cli

CLI does kill -11 when should be kill -6 for proc kill command.

CSCtg12030

cli

utils fior enable starts the fior module/service immediately.

CSCtg30822

cmcti

CER dialing default route pattern when first route pattern fails in list.

CSCtg40742

cmcti

getlinefetchinfo request failed for TSP8.0.2.3

CSCtg34450

cmui

EMCC URL cannot be configured in "Enterpise Parameter".

CSCtg31420

cmui

Cisco Unified CM user directory search causes memory allocation failure.

CSCtf62831

cmui

Cannot query Expires-on and Learned-on for IME learned route.

CSCtf28288

cmui

CUCM-SUNONE LDAP Sync change search scope (1 to 0) request.

CSCtg36018

cp-h323

Cisco Unified CM H323 removes calling party IE field if value is N/A or 00A3.

CSCtg20884

cp-ime-services

Need to remove number character (#) for IME to successfully learn route.

CSCte36991

cp-mediacontrol

Video lost on hairpin sTransfer call with multiple hold/resumes.

CSCtf64173

cp-mediacontrol

Race condition exists if two invites without SDP arrive and second leg media is not set up.

CSCtf99964

cp-mediacontrol

CP audio gets disconnected when video fails by dsp.

CSCtg16909

cp-mediacontrol

Call from H323 gateway to SIPT failed due to asymmetric codec.

CSCtf01379

cp-mediacontrol

Audio EP resumes RSVP call on SL and DSCP on orig RSVP-Agent are 136 136.

CSCte80568

cp-mediacontrol

Call drops on hold when SIP phone called via H323/225 trunk.

CSCtg18706

cp-mediacontrol

Call while in CUVC conference ends when transferred to CSF.

CSCtf25490

cp-mediacontrol

No video on 9951 phone when Tandberg calls it due to incorrect level.

CSCtf55088

cp-mediacontrol

9971 Pro Phone experiences audio cutthrough delay.

CSCte94447

cp-mobility

finalCalledPartyPartition is not correct in CDR for SNR call.

CSCtg28082

cp-mobility

NuRD not anchoring the call when calling MI-TCT device.

CSCtg26219

cp-sip-station

Active load is unknown when the phone is partial registered.

CSCtg36028

cp-sip-station

Cisco Unified CM sends 503 Unavailable error to TinCan Clients.

CSCtf77054

cp-sip-station

Issue exists with registration of third party device.

CSCtf98776

cp-sip-trunk

Cisco Unified CM changes port after session timer reinvite without hold-resume.

CSCtg04283

cp-sip-trunk

SIP trunk session refresh changes SDP direction.

CSCtg20449

cp-sip-trunk

SIP interface does not get created when Fake SDP is sent and Do invite.

CSCtg27573

cp-sip-trunk

DT: Number character (#) in route pattern does not get removed by the SIP trunk.

CSCtg01244

cp-ss-mwi

MWI using Enhanced MWI method (StationMwiNotification) across QSIG fails.

CSCtg24627

cp-subnotframework

BLF SD is not fully functional with partition.

CSCte73200

cp-subnotframework

SIP URI in BLF speed dial leads to malformed URL in Cisco Unified CM presence module.

CSCtg26431

cp-supplementaryservices

Conference remains active when CTIPort drops from the three-party conference.

CSCte41670

cpi-appinstall

TCP connection loss to CLI causes install to fail.

CSCtd88137

cpi-os

CLI command show memory modules results in error message.

CSCtg41510

cpi-os

IP Voice Media Streaming App service (IPVMS) can cause kernel panic.

CSCtd91156

database

dbmon core dump observed.

CSCtg31514

database

Audit log configuration db levels do not work.

CSCta20147

database-ids

dbscheduler - ph_alert/ph_task fills up rootdbs with repeated alarms.

CSCta25463

database-ids

PMR 73210 49R : errors 566, 116 and 7442 when out of memory.

CSCtc34902

database-ids

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

CSCtf04343

database-ids

PMR 29881 Assert fail in IDS.

CSCtg38516

database-ids

Assert fail "mtex.c Line: 491" occurs while "out of memory" testing runs.

CSCtg07458

database-ids

PMR 38677 DDR Block CDR delete server hangs.

CSCtg17491

database-ids

PMR 39366: onstat stuck in infinite loop.

CSCsz55537

ext-mobility

JPN:Katakana strings on Extension Mobility screens.

CSCtf71138

ime-risdc

IME Call Activity and Routing graph does not get refreshed in RTMT.

CSCtg18181

jtapisdk

Get primary call invalid after transfer to another hunt pilot.

CSCtg36857

jtapisdk

getTerminal() returns null on CiscoAddrRemovedEv

CSCtb36399

jtapisdk

VT: JTAPI client posts AddrOutOfService for all RP and ports

CSCta36165

licensing

License Manager causes a registration loop with Auto Registration.

CSCtg35049

qed

No field "Restrict Data Rates" in RT9971's Specific Configuration Layout.

CSCtg25081

rtmt

AnalysisManager should decode data in record details view.

CSCtg17493

rtmt

RTMT IOPS counters out of sync after running for long period of time.

CSCtf84767

rtmt-dp

"Refreshing Inventory updates, please wait" displays in Analyze Call Path.

CSCtg13272

sdl

sdl ssl connection does not allow multiple writes during handshake.

CSCtg20462

sdl

Cisco Unified CM coredump occurs due to SDL link failures in network with high packet loss.

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.

CSCtg22649

tftp

SCCP IP phones cannot download their config file SEP<mac>.cnf.xml.

CSCtf09981

voice-sipstack

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

CSCtf66290

voice-sipstack

Cannot route SIP INVITE with E.164 DN & "ext" attribute to GW/PSTN.

CSCtg08155

voice-sipstack

Call tranfer cases fail between SIP phones via ipip gateways.


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.