Guest

Cisco Unified Communications Manager (CallManager)

Release Notes for Cisco Unified Communications Manager Release 8.0(3a)

  • Viewing Options

  • PDF (752.7 KB)
  • EPUB (81.2 KB)
  • MOBI (125.1 KB)
  • Feedback

Table of Contents

Release Notes for Cisco Unified Communications Manager Release 8.0(3a)

Contents

Introduction

System Requirements

Upgrading to Cisco Unified Communications Manager 8.0(3x)

Before You Begin

Special Upgrade Information

Device Name of Cisco Unified Mobile Communicator Must Not Exceed 15 Characters Before Upgrade

Do Not Make Configuration Changes During an Upgrade

Upgrade Paths

Ordering the Upgrade Media

Upgrading to Unified CM 8.0(3a) by Using the UCSInstall File

Upgrading from a Local Source

Upgrading from a Remote Source

Upgrading From an Engineering Special

The Latest Software Upgrades for UnifiedCM8.0 on Cisco.com

Service Updates

Related Documentation

Limitations and Restrictions

Important Notes

CSCtb31860 Transcoding G.711 to All Codecs Supported

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

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

CSCte39796 Increase database replication timeout when upgrading large clusters

CSCsy57492 Hold Reversion Notification Interval for SCCP and SIP phones

New License Required when Replacing Motherboard (CSCtz12589 and CSCtz12651)

Limitations to Call Park Feature

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

CSCsz31137 Parked Call Gets Reverted When the Parkee is on

CSCsz35994 Incorrect Display for Park Monitoring Forward No Retrieve

CSCtb53159 Display Limitation in ConfList

CSCth53322 Rebuild Server After You Use the Recovery Disk

Verify IPv6 Networking on Servers Before Upgrade

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

CSCtd01766 Destination Port on Trunk Remains Unchanged After Upgrade

Disaster Recovery System Caution

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

CSCtr84167 Block Offnet to Offnet Transfer

CSCtr21486 Troubleshooting Guide Update to Switch Version

Certificate Regeneration During Domain Name Change

CSCtx86215 Database Replication

CSCtc71174 Call Park and Directed Call Park Restriction

CSCte94072 Phone has blank screen after switching forward to 8.X (EMCC logged in)

CSCtb58649 Sample query cannot list multiple users

CSCtf84350 cm tftp build all cnf does not work

CSCuc10415 Tip for Adding a New Server

Release Notes for Cisco Unified Communications Manager Release 8.0(3a)

June 3, 2014


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



Note Because of CSCti25567, Cisco is releasing Cisco Unified Communications Manager 8.0(3a).


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

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(3x)” 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(3a).



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(3a). 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 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 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 Servers
UCS Servers

MCS-7816-H3

MCS-7815-I2

B200 M1 Blade Server

MCS-7825-H2

MCS-7816-I3

C210 M1 Rack Server

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(3x)

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

Before You Begin


Note Follow the install instructions located here:

http://www.cisco.com/en/US/customer/docs/voice_ip_comm/cucm/install/8_0_2/install/cmins802.html


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

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

Cisco Unified Communications Manager System version

Cisco Unified Communications Manager Administration version

2. Read the “Special Upgrade Information” section.


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


Special Upgrade Information

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

Device Name of Cisco Unified Mobile Communicator Must Not Exceed 15 Characters Before Upgrade

Before you upgrade to Cisco Unified Communications Manager 8.0(3a), 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 Manager8.0(3a) 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.

Do Not Make Configuration Changes During an Upgrade

Do 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, 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, you have switched the servers over to the upgraded partition, and 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 the first node to the upgraded partition.

Step 5 Switch 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 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 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 configuration tasks.


 

Upgrade Paths

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(3a) from a release prior to 8.0(1), use the Product Upgrade Tool (PUT) to obtain a media kit and license or 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(3a) by Using the UCSInstall File

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

  • UCSInstall_UCOS_8.0.3.20000-2.sgn.iso_part1of2
  • UCSInstall_UCOS_8.0.3.20000-2.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.

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

 
cat UCSInstall_UCOS_8.0.3.20000-2.sgn.iso_part1of2 UCSInstall_UCOS_8.0.3.20000-2.sgn.iso_part2of2 > UCSInstall_UCOS_8.0.3.20000-2.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.3.20000-2.sgn.iso_part1of2+UCSInstall_UCOS_8.0.3.20000-2.sgn.iso_part2of2 UCSInstall_UCOS_8.0.3.20000-2.sgn.iso

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

eb2126b16c8ff5912fa0ebd0f8802d42 UCSInstall_UCOS_8.0.3.20000-2.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.

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.

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.

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


 

Upgrading From an Engineering Special

If you are currently running an Engineering Special (ES), and want the fixes included in Cisco Unified Communications Manager 8.0(3a), contact TAC to obtain an ES that contains:

  • the fixes that are included in Cisco Unified Communications Manager 8.0(3a)
  • the fixes that are included in the ES that you currently use

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 Communications Manager at http://www.cisco.com/en/US/products/sw/voicesw/ps556/tsd_products_support_series_home.html

For information about the Cisco Intercompany Media Engine server, see the Release Notes for Cisco Intercompany Media Engine Release 8.0(3) at http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/ime/8_0_3/rel_notes/ime-rel_notes-803.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(3x) as part of Cisco Unified Communications System Release 8.x 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(3a). 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 that supports Cisco Unified Communications Manager Release 8.0(3a).

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.

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

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

Procedure


Step 1 Follow the normal procedure for upgrading a cluster.


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


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

Cisco Unified Communications Manager Release 7.1(2)

  • All regular releases of 7.1(2)
  • All ES releases of 712 prior to 007.001(002.32016.001)

Cisco Unified Communications Manager Release 7.1(3)

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

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


Restart the Cisco TFTP Service on the TFTP Servers

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

The Control Center - Feature Services window displays.

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

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

Reset all Cisco Unified IP Phones


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


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

The Enterprise Parameters Configuration window displays.

Step 7 Click Reset.

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

Back Up Your Cluster


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

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


 

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

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

CSCte39796 Increase database replication timeout when upgrading large clusters

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

CSCsy57492 Hold Reversion Notification Interval for SCCP and SIP phones

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

New License Required when Replacing Motherboard (CSCtz12589 and CSCtz12651)

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

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

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

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

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


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


CSCsz31137 Parked Call Gets Reverted When the Parkee is on

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

CSCsz35994 Incorrect Display for Park Monitoring Forward No Retrieve

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

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

CSCtb53159 Display Limitation in ConfList

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

CSCth53322 Rebuild Server After You Use the Recovery Disk

After you use the recovery disk to bring a server with a corrupted file system into a bootable and semi-functional state, Cisco recommends that you rebuild the server.


Note If you do not rebuild the server, you may notice missing directories, lost permissions, or corrupted softlinks.


Verify IPv6 Networking on Servers Before Upgrade

Before you upgrade a cluster, execute the utils network ipv6 ping CLI command to verify IPv6 networking on the publisher and subscriber servers. If IPv6 is configured incorrectly on the subscriber server, load detection may take 20 minutes.

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.

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.

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.

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.

CSCtr84167 Block Offnet to Offnet Transfer

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

CSCtr21486 Troubleshooting Guide Update to Switch Version

When there is a version mismatch between a subscriber server and publisher server, the Cisco Unified Communications Manager history file does not log a switch version entry.

Certificate Regeneration During Domain Name Change

Using the set network domain CLI command to change the domain name triggers an automatic regeneration of all Cisco Unified Communications Manager certificates, including any third party signed certificates that have been uploaded. After the server reboots automatically, phones running in secure (mixed) mode cannot connect to the server until after the CTL client updates the new CTL file to the phones.

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.

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.

CSCte94072 Phone has blank screen after switching forward to 8.X (EMCC logged in)

When you have upgraded from 7.(x) to 8.(x), you must log out of all EMCC phones prior to switching back to 7.(x).

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.

CSCtf84350 cm tftp build all cnf does not work

CNF file download is not supported by TFTP for 7940/7960. Setting the build CNF files service parameter to "build all" will not build the cnf files in the format SEP<MAC>.CNF.

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.

CSCuo13148 Cisco ATA 187 Analog Telephone Adaptor Compatibility

The Cisco ATA 187 Analog Telephone Adaptor is compatible with Cisco Unified Communications Manager 8.0(3) and higher. For Cisco Unified Communications Manager 8.0(3), you must install the device pack cmterm-devicepack8.0.3.23038-1.cop.sgn for Cisco ATA 187 to be supported.

CSCuo10697 Updated List of LDAP Supported Directories

You can add users from your corporate directory to the Cisco Unified Communications Manager database by synchronizing the user data to the database. Cisco Unified Communications Manager allows synchronization from the following directories to the database:


Note This is an updated list for this release.


  • Microsoft Active Directory 2003 R1 & R2 (32-bit)
  • Microsoft Active Directory 2008 R1 (32-bit)
  • Microsoft Active Directory Application Mode 2003 R1 & R2 (32-bit)
  • Microsoft Lightweight Directory Services 2008 R1 (32-bit)
  • Planet 5.1 & Sun ONE Directory Server 5.2
  • Sun ONE Directory Server 6.x
  • Sun Directory Services 7.0
  • Oracle Directory Server Enterprise Edition 11gR1 (v11.1.1.5.0)
  • OpenLDAP 2.3.39
  • OpenLDAP 2.4

CSCup04321 Call Pickup Group Visual Notification does not Support Localization

The following limitation is applicable to Call Pickup:

Localization support is not available for call pickup group visual notification, as it uses ASCII for alerting name.

New and Changed Information

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.


Using Bug 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(3x) As of August 18, 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(3x) As of August 18, 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.

  • 8.0(2.40000-x) = Cisco Unified Communications Manager 8.0(2c)
  • 7.1(5.10000-x) = Cisco Unified Communications Manager 7.1(5)
  • 7.1(3.30000-x) = Cisco Unified Communications Manager 7.1(3b)
  • 7.1(3.20000-x) = Cisco Unified Communications Manager 7.1(3a)
  • 7.1(3.10000-x) = Cisco Unified Communications Manager 7.1(3)
  • 7.1(2.30000-x) = Cisco Unified Communications Manager 7.1(2b)
  • 7.1(2.20000-x )= Cisco Unified Communications Manager 7.1(2a)
  • 7.1(2.10000-x) = Cisco Unified Communications Manager 7.1(2)

Note Because defect status continually changes, be aware that the “Open Caveats for Cisco Unified Communications Manager Release 8.0(3x) As of August 18, 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 “Using Bug Toolkit” section.



Tip Bug Toolkit requires that you have an account with Cisco.com (Cisco Connection Online). By using the Bug Toolkit, you can find caveats of any severity for any release. Bug Toolkit may also provide a more current listing than this document provides. To access the Bug Toolkit, log on to http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl.


Open Caveats for Cisco Unified Communications Manager Release 8.0(3x) As of August 18, 2010

The following information comprises unexpected behavior (as of August 18, 2010) that you may encounter in Release 8.0(3x) of Cisco Unified Communications Manager.

 

Table 2 Open Caveats for Cisco Unified Communications Manager 8.0(3x) as of August 18, 2010

Id

Component

Headline

CSCtc20906

axl

AXL addRemoteDestination will not associate lines with Cisco Unified Communications Manager.

CSCth54303

cmcti

Application receives time out response but monitoring session is created.

CSCtf37698

cmcti

Incorrect reason code in ExistingCallEvent for supervisor.

CSCtf28288

cmui

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

CSCth20779

cmui

Certificate page contains empty filled mandatory parameter.

CSCti23225

cp-h323

Call using tunneled ICT getting unallocated number causes Cisco Unified Communications Manager core.

CSCti32919

cp-huntlist

Hunt Pilot Alerting Name does not display on called phone.

CSCtg88510

cp-mediacontrol

The X-cisco-media SDP attribute for MOH/MMOH issues over a SIP ICT.

CSCth34693

cp-mediacontrol

200 OK to INVITE for resuming media does not have SDP.

CSCth48527

cp-mediacontrol

IT stopper:H.263+ OMMRC payload type negotiation error.

CSCth58139

cp-mediacontrol

sRTP:E2E-No Audio after simultaneuos resume.

CSCtc87894

cp-mediacontrol

Video: UCM sends sendRecv instead of recvOnly for video call over ICT.

CSCti03257

cp-mediacontrol

Resume fails (SIP <-> h.323)

CSCti22603

cp-mediacontrol

Support video backward comatibility between 8.0 and 8.5

CSCtg71460

cp-mediacontrol

No video in CUVA for call between CUVA and TB across SIP trunk after Hold/Resume.

CSCth96670

cp-sccp

Rranscoder does not get inserted when phone codec is locked for recording.

CSCth89840

cp-sip-station

Multicast MOH does not operate as expected in encrypted mode.

CSCtg26431

cp-supplementaryservices

Conferences remains active when CTIPort drops from the 3-party conference.

CSCte41670

cpi-appinstall

TCP connection loss to CLI causes install to fail.

CSCth51118

cpi-os

System log file is more permissive than 640.

CSCte05285

cpi-os

IBM I3 servers Automatic Server Restart (ASR) does not get enabled by default.

CSCth51032

cpi-os

Unowned files exist.

CSCth68063

cpi-os

Slow memory leak due to dirsnmp.

CSCta25463

database-ids

Errors 566, 116 and 7442 occur when out of memory

CSCtc34902

database-ids

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

CSCtb36399

jtapisdk

JTAPI client posts AddrOutOfService for all RP and ports.

CSCtg17493

risdc

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

CSCtg79013

security

TVS core when publisher server/subscriber 1 switch back to old load after subscriber 2install on new.

CSCth63321

security

Incomplete ITL built after subscriber server gets upgraded-TFTP service running on subscriber server.

CSCth74101

security

Certificate with signature longer than 256 character does not get recognized by CTL client.

CSCtc38788

tapisdk

TAPI application stuck - cannot start.

CSCth75213

webdialer-service

Click-to-Call failed randomly with CTI error: Device is not acquired.

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.