Table Of Contents
Release Notes for Cisco Unified Communications Manager Release 8.0(1)
Upgrading to Cisco Unified Communications Manager 8.0(1)
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)
Upgrading from a Remote Source
The Latest Software Upgrades for Unified CM 8.0 on Cisco.com
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
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
Open Caveats for Cisco Unified Communications Manager Release 8.0(1) As of February 23, 2010
Obtaining Documentation and Submitting a Service Request
Release Notes for Cisco Unified Communications Manager Release 8.0(1)
February 25, 2010
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:
•
Upgrading to Cisco Unified Communications Manager 8.0(1)
•
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.
Cisco Unified Communications Manager Business Edition (Unified CMBE) offers you the features and functionality of Cisco Unified Communications Manager (Unified CM) and Cisco Unity Connection on one appliance platform.
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 Business Edition server to an uninterruptible power supply (UPS) to provide backup power and protect your system against a power failure.
When Cisco Unified Communications Manager Business Edition runs on one of the servers that are listed in Table 1, 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 Business Edition 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 1 Supported Servers for Basic Integration
HP Servers IBM ServersMCS-7828-H3
MCS-7828-I3
MCS-7828-I4
![]()
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.
•
Upgrade Paths to Cisco Unified Communications Manager 8.0(1)
•
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.
Special Upgrade Information
The following sections include information that you must know before you begin the upgrade process.
•
Device Name of Cisco Unified Mobile Communicator Must Not Exceed 15 Characters Before 8.0(1) Upgrade
•
Important Upgrade Information
•
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 0Bus Interface: PCISlot: 0Cache Serial Number: P75B20C9SR642PRAID 6 (ADG) Status: DisabledController Status: OKChassis Slot:Hardware Revision: Rev BFirmware Version: 2.80Rebuild Priority: LowExpand Priority: LowSurface Scan Delay: 15 secCache Board Present: TrueCache Status: OKAccelerator Ratio: 50% Read / 50% WriteTotal Cache Size: 192 MBBattery Pack Count: 1Battery Status: OKSATA NCQ Supported: FalseThe 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 : OkayChannel description : SAS/SATAController Model : IBM ServeRAID 8kController Serial Number : 20ee0001Physical Slot : 0Copyback : DisabledData scrubbing : EnabledDefunct disk drive count : 0Logical 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 : OkayOver temperature : NoCapacity remaining : 100 percentTime remaining (at current draw) : 4 days, 18 hours, 40 minutes---------------------------------------------------Controller Vital Product Data---------------------------------------------------VPD Assigned# : 25R8075EC Version# : J85096Controller FRU# : 25R8076Battery FRU# : 25R8088----------------------------------------------------------------------Logical drive information----------------------------------------------------------------------Logical drive number 1Logical drive name : Logical Drive 1RAID level : 1Status of logical drive : OkaySize : 69900 MBRead-cache mode : EnabledWrite-cache mode : Enabled (write-back)Write-cache setting : Enabled (write-back) when protected by batteryNumber of chunks : 2Drive(s) (Channel,Device) : 0,0 0,1Logical drive number 2Logical drive name : Logical Drive 2RAID level : 1Status of logical drive : OkaySize : 69900 MBRead-cache mode : EnabledWrite-cache mode : Enabled (write-back)Write-cache setting : Enabled (write-back) when protected by batteryNumber of chunks : 2Drive(s) (Channel,Device) : 0,2 0,3Device 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.
Important Upgrade Information
Do not upgrade Cisco Unified CMBE at the same time that the Cisco Unity Connection task Upgrade Database Statistics is running. Because both processes are processor intensive, allowing them to run simultaneously may cause the system to stop functioning and force you to restart the server.
By default, the Upgrade Database Statistics task runs at 3:30 am daily. To determine whether the task schedule has been changed, whether the task is currently running, and how long the task has recently taken to complete, log on to Cisco Unity Connection Administration. Click Tools > Task Management > Update Database Statistics.
The Task Definition Basics window displays a history of when the task started and when it completed. If the Time Started column has a value and the Time Completed column does not, this indicates that the task is currently running.
If you must run the upgrade at a time that could overlap with the Upgrade Database Statistics task, reschedule the task to run before or after the upgrade. On the Task Definition Basics window for the task, click Edit > Task Schedule.
Do not reschedule the task to run during normal business hours. When the upgrade completes, reset the schedule to the default settings.
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.
![]()
CautionIf 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.htmlOrdering 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 are upgrading Cisco Unified Communications Manager Business Edition, skip to Step 2.
If you are adding a Cisco Unity Connection locale, stop the Connection Conversation Manager and Connection Mixer services:
a.
Start Cisco Unity Connection Serviceability.
b.
Navigate to Tools > Control Center - Feature Services.
c.
Under Critical Services, in the Connection Conversation Manager row, click Stop.
d.
Wait for the service to stop.
e.
Also under Critical Services, in the Connection Mixer row, click Stop.
f.
Wait for the service to stop.
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.
![]()
CautionAlthough 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 are upgrading Cisco Unified Communications Manager Business Edition, skip to Step 12.
If you are installing Cisco Unity Connection locales and want to install another locale, click Install Another, and return to Step 4.
If you do not want to install another locale, restart the Connection Conversation Manager and Connection Mixer services:
a.
Start Cisco Unity Connection Serviceability.
b.
Navigate to Tools > Control Center - Feature Services.
c.
Under Critical Services, in the Connection Conversation Manager row, click Start.
d.
Wait for the service to start.
e.
Also under Critical Services, in the Connection Mixer row, click Start.
f.
Wait for the service to start.
g.
Skip the rest of the procedure.
Step 12
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 13
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.
Step 2
If you are upgrading Cisco Unified Communications Manager Business Edition, skip to Step 3.
If you are adding a Cisco Unity Connection locale, stop the Connection Conversation Manager and Connection Mixer services:
a.
Start Cisco Unity Connection Serviceability.
b.
Navigate to Tools > Control Center - Feature Services.
c.
Under Critical Services, in the Connection Conversation Manager row, click Stop.
d.
Wait for the service to stop.
e.
Also under Critical Services, in the Connection Mixer row, click Stop.
f.
Wait for the service to stop.
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 Remote Filesystem.
Step 6
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
/patchesIf 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 7
In the Server field, enter the server name or IP address.
Step 8
In the User Name field, enter your user name on the remote server.
Step 9
In the User Password field, enter your password on the remote server.
Step 10
Select the transfer protocol from the Transfer Protocol field.
Step 11
To disable throttling, check the Disable I/O throttling check box.
![]()
CautionAlthough 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 12
To continue the upgrade process, click Next.
Step 13
Choose the upgrade version that you want to install and click Next.
Step 14
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 15
If you are installing upgrade software, skip to Step 16.
If you are installing Cisco Unity Connection locales and want to install another locale, click Install Another, and return to Step 4.
If you do not want to install another locale, restart the Connection Conversation Manager and Connection Mixer services:
a.
Start Cisco Unity Connection Serviceability.
b.
Navigate to Tools > Control Center - Feature Services.
c.
Under Critical Services, in the Connection Conversation Manager row, click Start.
d.
Wait for the service to start.
e.
Also under Critical Services, in the Connection Mixer row, click Start.
f.
Wait for the service to start.
g.
Skip the rest of the procedure.
Step 16
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 17
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).
•
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
•
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
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.
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/cucmbe/rel_notes/8_0_1/delta/nc-801-be.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.
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/cucmbe/rel_notes/8_0_1/80x_cucmbe_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.
CCDE, CCENT, CCSI, Cisco Eos, Cisco Explorer, Cisco HealthPresence, Cisco IronPort, the Cisco logo, Cisco Nurse Connect, Cisco Pulse, Cisco SensorBase, Cisco StackPower, Cisco StadiumVision, Cisco TelePresence, Cisco TrustSec, Cisco Unified Computing System, Cisco WebEx, DCE, Flip Channels, Flip for Good, Flip Mino, Flipshare (Design), Flip Ultra, Flip Video, Flip Video (Design), Instant Broadband, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn, Cisco Capital, Cisco Capital (Design), Cisco:Financed (Stylized), Cisco Store, Flip Gift Card, and One Million Acts of Green are service marks; and Access Registrar, Aironet, AllTouch, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Lumin, Cisco Nexus, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, Continuum, EtherFast, EtherSwitch, Event Center, Explorer, Follow Me Browsing, GainMaker, iLYNX, IOS, iPhone, IronPort, the IronPort logo, Laser Link, LightStream, Linksys, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, PCNow, PIX, PowerKEY, PowerPanels, PowerTV, PowerTV (Design), PowerVu, Prisma, ProConnect, ROSA, SenderBase, SMARTnet, Spectrum Expert, StackWise, WebEx, and the WebEx logo are registered trademarks of Cisco and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1002R)