 Feedback
|
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
CSCtb31860 Transcoding G.711 to All Codecs Supported
CSCtw61986 Disable LRO on Cisco Unified Computing Systems running ESXi 4.1
CSCto57498 Upgrading to Cisco Unified Communications Manager Release 8.x from Release 7.x
CSCtd69640 Downtime when upgrading Publisher server until all Subscriber servers are updated
CSCte39796 Increase database replication timeout when upgrading large clusters
CSCsy57492 Hold Reversion Notification Interval for SCCP and SIP phones
New License Required when Replacing Motherboard (CSCtz12589 and CSCtz12651)
Limitations to Call Park Feature
CSCsz31137 Parked Call Gets Reverted When the Parkee is on
CSCsz35994 Incorrect Display for Park Monitoring Forward No Retrieve
CSCtb53159 Display Limitation in ConfList
CSCtg50662 Bridge Upgrade: Some Services Fail to Register with Disaster Recovery Framework
Node Licenses Missing After an Upgrade
CSCtd01766 Destination Port on Trunk Remains Unchanged After Upgrade
CSCte91815 Cisco Phone Designer Does Not Work with Phone
Do Not Run Unified CM 8.0(1) on a VMware Virtual Machine Server
Cisco Intercompany Media Engine is Not Available
CSCte53189 Changing More Than One Parameter at a Time on the CCD Requesting Service Causes Stale DN
CSCte36097 DRS Fails at Database Component
Disaster Recovery System Caution
CSCte47453 Installation Process Does Not Backup Component Files from Subscriber Server
EMCC Login Affects Settings in Product-Specific Configuration Layout of Phone Configuration Window
CSCtd94318 MCS-7845-I3 Server Locks Up After Integrated Management Module gets Restarted
CSCtj61834 MLPP Default Domain Name Displays MLPP ID Value
CSCtr40861 Incoming Calling Party Numbers should be up to 16 characters
CSCtr89029 URL Parameters for Secured Phones Repopulated After Restart
CSCto87262 Centralized TFTP with CUCM 8 SBD requires workaround
CSCte44108 Call Control Discovery Limitation
CSCtj37643 Installing Language Prompts for TAPS
CSCtx00678 Do not use Voicemail for Alerting Name or ASCII Alerting Name
CSCtx86215 Database Replication
CSCsu23100 Missing Information on Special Characters
CSCtx92282 Cisco Unified IP Phones 9951 and 9971 support SIP Dial Rules
CSCtr44481 Download Dial Plans for Cisco Unified Communications Manager Release 8.X
CSCtc71174 Call Park and Directed Call Park Restriction
CSCtg71595 Allowed characters for Cluster ID field
CSCtb58649 Sample query cannot list multiple users
CSCuc10415 Tip for Adding a New Server
CSCuc23992 Call Preservation support for SIP trunks
CSCuc79185 Device Mobility Calling Search Space is Used When Device CSS is <none>
CSCtw44980 Missing Exceptions for Voice-Mail Pilot
CSCud34740 Application User AXL Password Must Not Contain Special Characters
CSCud70447 Missing Etoken Recovery Steps in Troubleshooting Guide
CSCud95087 Limitation of SIP Forking on Trunk Not Documented
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)
Updated January 21, 2013
Because of CSCtg50662 Bridge Upgrade: Some Services Fail to Register with Disaster Recovery Framework, Cisco Unified Communications Manager Release 8.0(1) is deferred. Cisco recommends that you install/upgrade to Cisco Unified Communications Manager 8.0(2c).
Note
You can view release notes for Cisco Unified Communications Manager Business Edition at http://www.cisco.com/en/US/products/ps7273/prod_release_notes_list.html
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:
•
•
Before you install or upgrade Cisco Unified Communications Manager, Cisco recommends that you review the "Upgrading to Cisco Unified Communications Manager 8.0(1)" section, and the "Service Updates" section for information pertinent to installing or upgrading, and the "Important Notes" section for information about issues that may affect your system.
Introduction
Cisco Unified Communications Manager, the call-processing component of the Cisco Unified Communications System, extends enterprise telephony features and capabilities to IP phones, media processing devices, voice-over-IP (VoIP) gateways, mobile devices, and multimedia applications.
System Requirements
The following sections comprise the system requirements for this release of Cisco Unified CM.
Server Support
Make sure that you install and configure Cisco Unified CM on a Cisco Media Convergence Server (MCS) or a Cisco-approved HP server configuration or a Cisco-approved IBM server configuration.
To find which MCS are compatible with this release of Cisco Unified CM, refer to the Supported Servers for Cisco Unified Communications Manager Releases: http://www.cisco.com/en/US/prod/collateral/voicesw/ps6790/ps5748/ps378/prod_brochure0900aecd8062a4f9.html.
Note
Be aware that some servers that are listed in the Cisco Unified Communications Manager Software Compatibility Matrix may require additional hardware support for Cisco Unified CM Release 8.0(1). Make sure that your server meets the minimum hardware requirements, as indicated in the footnotes of the Cisco Unified Communications Manager Software Compatibility Matrix. Uninterruptible Power Supply
Cisco recommends that you connect each Cisco Unified Communications Manager server to an uninterruptible power supply (UPS) to provide backup power and protect your system against a power failure.
Note
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
Note
Upgrading to Cisco Unified Communications Manager 8.0(1)
The following sections contain information that is pertinent to upgrading to this release of Cisco Unified CM.
•
•
•
Before You Begin
1.
To do that, open Cisco Unified Communications Manager Administration. The following information displays:
–
–
2.
Note
Special Upgrade Information
Caution
The following sections include information that you must know before you begin the upgrade process.
•
•
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.
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
Upgrade Tasks
To successfully complete the upgrade, perform the upgrade tasks in the following order before you begin making configuration changes.
Note
Procedure
Step 1
Tip
Step 2
Step 3
Step 4
Step 5
Note
Step 6
•
•
–
–
–
–
–
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
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
Note
Step 2
Step 3
Step 4
The Software Installation/Upgrade window displays.
Step 5
Step 6
Step 7
Caution
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
Step 9
Step 10
Step 11
Step 12
a.
b.
The Upgrade Status window displays the Upgrade log.
c.
d.
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
Procedure
Step 1
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.
b.
Step 2
Step 3
The Software Installation/Upgrade window displays.
Step 4
Step 5
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
•
•
Step 6
Step 7
Step 8
Step 9
Step 10
Caution
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
Step 12
•
•
Step 13
Note
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
Step 15
a.
b.
The Upgrade Status window displays the Upgrade log.
c.
d.
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/public/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
Important Notes
The following section contains important information that may have been unavailable upon the initial release of documentation for Cisco Unified Communications Manager Release 8.0(1).
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
CSCtb31860 Transcoding G.711 to All Codecs Supported
The transcoder supports transcoding between G.711 and all codecs, including G.711, when functioning as a transcoder and when providing MTP/TRP functionality.
CSCtw61986 Disable LRO on Cisco Unified Computing Systems running ESXi 4.1
Disable Large Receive Offload (LRO) for deployments on Cisco Unified Computing System (UCS) servers running ESXi 4.1 to eliminate LRO-related network errors.
Step 1
Step 2
Step 3
Step 4
•
•
•
•
•
Step 5
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
Tip
Step 2
Cisco Unified Communications Manager Release 7.1(2)
•
•
Cisco Unified Communications Manager Release 7.1(3)
•
•
Note
Restart the Cisco TFTP Service on the TFTP Servers
Step 3
The Control Center - Feature Services window displays.
Step 4
Step 5
Reset all Cisco Unified IP Phones
Note
Step 6
The Enterprise Parameters Configuration window displays.
Step 7
Step 8
Back Up Your Cluster
Caution
Step 9
CSCtd69640 Downtime when upgrading Publisher server until all Subscriber servers are updated
When upgrading the publisher node, there will be a temporary server outage until all subscriber nodes get upgraded to the new software version.
CSCte39796 Increase database replication timeout when upgrading large clusters
Use the utils dbreplication setrepltimeout CLI command to increase the database replication timeout value when upgrading large clusters so that more subscriber servers have sufficient time to request replication. When the timer expires, the first subscriber server, plus all other subscriber servers that requested replication within that time period, begin a batch data replication with the publisher server. The default database replication timeout value is 300 (5 minutes). Restore the timeout to the default value after the entire cluster upgrades and the subscriber servers have successfully set up replication. For more information, see the Command Line Interface Guide for Cisco Unified Communications Solutions.
CSCsy57492 Hold Reversion Notification Interval for SCCP and SIP phones
SCCP phones support a minimum Hold Reversion Notification Interval (HRNI) of 5 seconds, whereas SIP phones support a minimum of 10 seconds. SCCP phones set for the minimum HRNI of 5 seconds may experience a Hold Reversion Notification ring delay of 10 seconds when handling calls involving SIP phones.
New License Required when Replacing Motherboard (CSCtz12589 and CSCtz12651)
A new license file is required if you are installing a replacement motherboard in publisher servers or single servers that are not part of a cluster.
Limitations to Call Park Feature
The Call Park feature has the following known limitations:
•
•
•
CSCsz18443 Cisco Unified IP Phone 8961, 9951, 9971 Registered to a Node may Use the Call Park Number Assigned to Another Node
Call Park numbers get configured on the nodes of a Cisco Unified Communications Manager cluster (first/subsequent). Call Park numbers are normally allocated from the node that initiates the call. If the Cisco Unified IP Phone 8961, 9951, 9971 that initiates the call is registered to the first node of the Cisco Unified Communications Manager cluster, then a Call Park number configured on the first node gets used to park the call. This is irrespective of the node to which the called party is registered, or which party (calling or called) invokes the Call Park feature.
For example, if a phone registered to the first node initiates a call to a phone registered to the second node, then regardless of which phone invokes the Call Park feature, a Call Park number configured on the first node is always used.
Similarly, if the Call Park feature gets invoked when a phone in the second node is the call initiator, then a Call Park number configured on the second node is used.
Note
CSCsz31137 Parked Call Gets Reverted When the Parkee is on
When an inter-cluster parked call connected by an Intercluster Trunk ( ICT) is put on hold, the call reverts when the Park Monitoring Reversion Timer and the Park Monitoring Forward No Retrieve Timer expire. Such a call reverts even though the parkee is on hold. This is a known limitation of inter-cluster calls connected via ICT that use the Call Park feature.
CSCsz35994 Incorrect Display for Park Monitoring Forward No Retrieve
For inter-cluster parked called connected by an ICT, after the Park Reversion Timer and Park Monitoring Forward No Retrieve Timer expire, the call gets forwarded to the Park Monitoring Forward No Retrieve destination. The display of the incoming call is incorrect on the destination device.
The display on the device is "From DN" instead of "Forwarded for DN". For example, if the initial call is an inter-cluster call via ICT from DN 1000 to DN 3000 and gets forwarded to DN 2000, the display on DN 2000 is "From 3000" instead of "Forwarded for 1000".
CSCtb53159 Display Limitation in ConfList
You can add as many conference participants as the conference bridge supports; however, ConfList only displays 16 participants. From the 17th participant onwards, the list displays only the latest 16 participants.
CSCtg50662 Bridge Upgrade: Some Services Fail to Register with Disaster Recovery Framework
Conditions
When you perform a bridge upgrade to Cisco Unified Communications Manager 8.0(1), services that are not activated before the upgrade do not register with Disaster Recovery Framework (DRF) and the associated data does not get backed up. When the restore completes on the new hardware, this situation becomes apparent.
Symptoms
Because data from one or more of the services listed in the Workaround (below) is missing, when the services get activated, the server behaves as if the services were not initialized and not used on the server earlier.
Workaround
Before you begin the bridge upgrade on the old hardware running pre-8.0 software, activate the following services (if they are not already activated) to ensure the associated data gets saved:
•
•
•
•
•
•
CSCtd09050 Service Parameter Name/Usage Change from CTIWildCardDNAsCalledParty to CTIWildCardDNInCallInfo
The service parameter "CTI Use Wildcard Pattern as calledPartyDN -" setting also applies to CTI call information fields CallingParty, OriginalCalledParty, and LastRedirectingParty, in addition to the CalledParty field.
The service parameter help text does not provide this information.
Node Licenses Missing After an Upgrade
If the node license file contains multiple features (for example: SW_FEATURE + CCM_NODE), after you upgrade to this release of Cisco Unified Communications Manager, the following licensing warnings might display:
•
•
For additional details and workaround, see CSCtf15332.
CSCtd01766 Destination Port on Trunk Remains Unchanged After Upgrade
During an upgrade to an unrestricted Cisco Unified CM release, the SIP trunk incoming port gets changed to 5060; however, the destination port on the trunk remains what it was before the upgrade.
CSCte91815 Cisco Phone Designer Does Not Work with Phone
If the HTTPS server configuration is set to "HTTPS only" and the phone has an LSC issued by Cisco Unified CM 8.0 or earlier, the Cisco Phone Designer does not save or preview wallpaper or ringtone to the phone.
Workaround
Step 1
Step 2
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:
•
•
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
This command lists all the components registered with DRS for backup on the specified subscriber server.
Step 2
Step 3
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.
2.
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:
•
•
•
•
You can enter up to 16 characters, which include digits, the international escape character (+), asterisk (*), or the pound sign (#).
CSCtr89029 URL Parameters for Secured Phones Repopulated After Restart
When you delete the Secured Phone URL Parameters in the Enterprise Parameter section of Cisco Unified Communications Manager Administrationand then reboot, the URL Parameters are re-populated by default. After you reboot go to the Secured Phone URL Parameters section and make the correct modifications to the URL and reboot the phones.
CSCto87262 Centralized TFTP with CUCM 8 SBD requires workaround
If you deploy a Centralized TFTP as described in Cisco Unified Communications Manager System Guide with a CUCM 8.X cluster using ITL files, you need to disable the ITL file on the IP Phones by running through the following workaround:
Workaround
Step 1
Step 2
Step 3
Step 4
CSCte44108 Call Control Discovery Limitation
The following information is missing from the "Call Control Discovery" chapter in the Cisco Unified Communications Manager Features and Services Guide.
CCD has a limitation with three clusters (A, B and C), when C learns the advertisements of A and B.
In this scenario, when two clusters (A and B) are present, both of them advertise the same pattern, and cluster B advertises later than cluster A. This behavior overwrites the PSTN failover rule for cluster A which cluster C adopts. If your IP connection is lost, calls from cluster C are always redirected to cluster B via PSTN.
After you delete the cluster B advertisement, the PSTN failover rule still points back to A. If your IP connection is lost, calls from cluster C are redirected to cluster A via PSTN.
CSCtj37643 Installing Language Prompts for TAPS
If you need to install language prompts other than English, you must install the Locale Installer on all nodes in your Cisco Unified CM cluster. After you install the Locale Installer, you must pull the locale specific AAR file that the Locale Installer saves to the Cisco Unified CM TFTP directory and install that file in Cisco Unified CCX.
Step 1
Step 2
Note
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
CSCtx00678 Do not use Voicemail for Alerting Name or ASCII Alerting Name
Do not use the word "Voicemail" anywhere in the Alerting Name or ASCII Alerting Name fields in the Directory Number Configuration window. If you use the word "Voicemail" Cisco Unity Connection may process the call as a direct Call, rather than as a forwarded call.
CSCtx86215 Database Replication
This section of the Cisco Unified Communications Manager System Issues chapter in the Troubleshooting Guide for Cisco Unified Communications Manager requires this addition:
Extension Mobility does not work when database replication breaks between the Unified CM node running Extension Mobility and the Unified CM node to which the phone is registered.
CSCsu23100 Missing Information on Special Characters
For information on special characters and how they can be used in a dial plan, refer to the Wildcards and Special Characters in Route Patterns and Hunt Pilots topic in the Understanding Route Plans chapter from the Cisco Unified Communications Manager System Guide.
CSCtx92282 Cisco Unified IP Phones 9951 and 9971 support SIP Dial Rules
The SIP Dial Rule Configuration Settings section of the Cisco Unified Communications Manager Administration Guide lists the phones that support SIP dial rules. However, the section omits the Cisco Unified IP Phones 9951 and 9971, both of which support SIP dial rules.
CSCtr44481 Download Dial Plans for Cisco Unified Communications Manager Release 8.X
You can download dial plans for Cisco Unified Communications Manager Release 8.X from the Downloads section of www.cisco.com. On the Cisco website, you can find the Cisco Option Package (COP) file that contains all the available dial plans that you can download, install, and integrate with Cisco Unified Communications Manager. For release 8.x, use the IDP v.3 cop files.
CSCtc71174 Call Park and Directed Call Park Restriction
The following call flow shows a limitation with the Call Park and Directed Call Park features.
1.
2.
3.
4.
5.
In this call flow, when you retrieve a parked call across an H323 ICT that is also on hold, the call fails. By the time phone C tries to retrieve the parked call, the parked party is on hold and Unified CM cannot cut through media.
CSCtg71595 Allowed characters for Cluster ID field
The Cluster ID field in the EMCC Remote Cluster configuration window supports only alphanumeric characters (a-z, A-Z, 0-9), periods (.), and dashes(-). If you enter another character, such as a space or percent sign, you will receive an http error when you click Update Remote Cluster.
CSCtb58649 Sample query cannot list multiple users
To retrieve multiple user queries in Extension Mobility (EM) Service, you must have EM Authentication Proxy Rights. If any other end user's credentials are used to query EM Service, only this end user's information will be retrieved.
CSCuc10415 Tip for Adding a New Server
The following tip needs to be added to the "Server settings" topic in the Cisco Unified Communications Manager Administration Guide.
Tip
CSCuc23992 Call Preservation support for SIP trunks
The Call Preservation feature in Cisco Unified Communications Manager also supports SIP trunks. Active calls that cross a SIP trunk do not get interrupted when a Cisco Unified Communications Manager node fails, or when communication between a device and its cluster node fails.
CSCuc79185 Device Mobility Calling Search Space is Used When Device CSS is <none>
The following note is missing from the "Phone Settings" topic in the Cisco Unified Communications Manager Administration Guide:
When set to <none>, Unified CM uses the device mobility calling search space, which is configured on the device pool.
CSCtw44980 Missing Exceptions for Voice-Mail Pilot
The following information is missing for the Voice Mail Pilot Name field description in the "Voice-Mail Pilot Settings" topic in the Cisco Unified Communications Manager Administration Guide:
Allowed characters are numeric (0-9), plus (+), asterisk (*), and pound (#).
CSCud34740 Application User AXL Password Must Not Contain Special Characters
The following note is missing from the Application User Settings topic in the Cisco Unified Communications Manager Administration Online Help:
Note
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
Step 1
file list tftp CTLFile.tlv
Step 2
file delete tftp CTLFile.tlv
Step 3
Step 4
Step 5
Tip
Step 6
Step 7
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:
•
•
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:
•
•
•
•
•
•
•
•
•
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
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:
•
•
You can search for problems by using the Cisco Software Bug Toolkit.
To access Bug Toolkit, you need the following items:
•
•
•
To use the Software Bug Toolkit, follow these steps:
Procedure
Step 1
Step 2
Step 3
Tip
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
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.
•
•
•
•
•
•
Note
Tip
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/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.
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)
