Release Notes for Cisco Unified Communications Manager and IM and Presence Service, Release 9.1(1)
Important Notes
Downloads: This chapterpdf (PDF - 1.29 MB) The complete bookPDF (PDF - 2.98 MB) | The complete bookePub (ePub - 398.0 KB) | The complete bookMobi (Mobi - 720.0 KB) | Feedback

Important Notes


Important Notes

BFCP is Supported with TelePresence MCU

This documentation update resolves CSCuh70981.

The section "Conference Bridge Types in Cisco Unified Communications Manager Administration" incorrectly states that Binary Floor Control Protocol (BFCP) is not supported between Cisco Unified Communications Manager and a Cisco TelePresence Multipoint Control Units (MCU).

The system supports presentation sharing with the BFCP between Unified Communications Manager and a TelePresence MCU.

Native Call Queuing Periodic Announcement Behavior

This documentation update resolves CSCui20806.

The following information is omitted from the "Call Queuing" and "Music On Hold" chapters in the Features and Services Guide:

Initial announcements are always simulcast to each new caller. Periodic announcements are multicast to queued callers at the specified time interval. Callers who join the queue after the periodic announcement begins to play may only hear a portion of the announcement.

Disable Empty TLS Fragments

This documentation update resolves CSCuh39611.

To support TLS encryption between IM and Presence Service and Microsoft Lync/OCS/LCS, you must modify the Peer Authentication TLS Context configuration on IM and Presence Service using the Cisco Unified CM IM and Presence Administration GUI. Ensure that you disable empty TLS fragments when you modify the Peer Authentication TLS Context on IM and Presence Service before integrating with Microsoft Lync/OCS/LCS for Partitioned Intradomain Federation.

Adding a New Subscriber Causes Device Reset

This documentation update resolves CSCub12922.

After you install a new node in an existing cluster, all phones that are registered to the cluster are reset.

EMCC Logout Limitation

This documentation update resolves CSCue04792.

In the visiting cluster, the current Phone Configuration window has a Log Out button for intracluster Extension Mobility (EM). This button is also used by the visiting cluster administrator to log out an Extension Mobility Cross Cluster (EMCC) phone. Because the EMCC phone is not currently registered with the visiting Cisco Unified Communications Manager, this operation is equivalent to a database cleanup in the visiting cluster. The EMCC phone will remain registered with the home Cisco Unified Communications Manager until it comes back to the visiting cluster due to a reset or a logout from the home cluster by other means.

Call Queuing Interaction with Hunt Groups and Hunt Pilots

This documentation update resolves CSCue08776.

The logoff notification functionality for hunt groups changes when Call Queuing is enabled for a hunt pilot. The Hunt Group Logoff Notification does not play when a user logs out of a hunt group, or is logged off because they missed their turn in the queue, if Call Queuing is enabled for a hunt pilot.

Bandwidth Management Sections of Video Telephony in the 9.x System Guide

This documentation update resolves CSCue58676.

In the Differentiated Services Code Point (DSCP) packet marking, the following characteristic is added:

Video streams and associated audio streams in immersive video calls default to CS4 is added.

The following service parameter settings affect DSCP packet marking for media RTP streams are added:

  • DSCP for Audio Portion of Video Calls

  • DSCP for TelePresence Calls

  • · DSCP for Audio Portion of TelePresence Calls

DSCP for ICCP Protocol Links is removed.

Cannot Install Signed Microsoft CA Server-Client Authentication Certificate on Microsoft OCS 2008

This documentation update resolves CSCtw47643.

You cannot install a server-client authentication certificate that is signed by a Microsoft certificate authority (CA) into the local computer store of a Microsoft Office Communications Server (OCS) running Windows 2008. Attempting to copy the certificate from the current user store to the local computer store fails with the error message that the private key is missing.

To resolve this issue, perform the following procedure:

  1. Log on to the OCS as a local user.

  2. Create the certificate.

  3. Approve the certificate from the CA server.

  4. While logged on to the OCS, export the certificate to a file and ensure that the private key is exported.

  5. Log off the OCS (Local Computer).

  6. Log on to the OCS again, but this time log on to the OCS domain as a domain user.

  7. Use the Certificate Wizard to import the certificate file. The certificate is installed in the local computer store. You can now select the certificate in the OCS certificate tab.

Presence Data Loss After Upgrade From Cisco Business Edition 5000 to Cisco Unified Communications Manager

This documentation update resolves CSCts65285.

There is no upgrade path in VMware to upgrade from Cisco Business Edition 5000 to Cisco Unified Communications Manager. A fresh installation is needed. After you perform the fresh installation, IM and Presence Service resynchronizes data with the new Cisco Unified Communications Manager. The Syncagent uses the primary key (pkid) as a comparison field for the synchronization. When the Cisco Unified Communications Manager is reinstalled, all the pkids on Cisco Unified Communications Manager are changed. As such, any existing data on IM and Presence Service is cleaned up and the Syncagent deletes the old data.


Be sure to back up your data before performing this procedure.

Presence User Experiences Issues Obtaining Availability

This documentation update resolves CSCto77824.

After an IM and Presence Service server upgrade, when all activated feature services and network services are started, a user experiences inconsistent presence availability. The user can log in to IM and Presence Service but will experience issues obtaining availability information, mainly from SIP-based clients.

This issue is caused when users are provisioned while IM and Presence Service is being upgraded. You must unassign and then reassign the user.

Access Control Group Permissions Interactions

This documentation update resolves CSCud59343.

Users can belong to multiple access control groups. When adding a new access control group to existing users, an unexpected reduction in the current level of privileges for some preexisting access control groups may be experienced if the new access control group has the "Effective Access Privileges for Overlapping User Groups and Roles" Enterprise parameter set to Minimum.

Access privilege reduction can occur inadvertently, for example, during an upgrade of Cisco Unified Communications Manager Administration. If the upgrade version supports the Standard RealTimeAndTrace Collection user group, which has the "Effective Access Privileges for Overlapping User Groups and Roles" Enterprise parameter set to Minimum, all users are automatically added to that user group during the upgrade. To resolve the permissions issue in this example, you can remove users from the Standard RealTimeAndTrace Collection user group.

CallProcessingNodeCpuPegging Alerts for VMware Installations

This documentation update resolves CSCtu18692.

Cisco Unified Communications Manager VMware installations can experience high CPU usage spikes while performing tasks such as DRF backups and Bulk Administration Tool exports. The processes that are commonly responsible for CPU usage spikes are gzip and DRFLocal.

If your system is generating CallProcessingNodeCpuPegging alarms, add an additional vCPU for the support of 7500 Cisco Unified Communications Manager users following the Open Virtualization Archives (OVA) template specifications for your system.

The CallProcessingNodeCpuPegging alert is generated during CPU usage spikes. Other alarms that may also be issued during these CPU usage spikes include CoreDumpFound, CriticalServiceDown, SDLLinkOutOfService, and NumberOfRegisteredPhonesDropped alarms.

Centralized Proxy TFTP File Signature Verification Failure

This documentation update resolves CSCud18710.

When a phone requests a common file from a central or proxy TFTP server and that file has a common name such as ringlist.xml.sgn or is a locale file, the TFTP server sends its own local copy of the file instead of the file from the home cluster of the phone. The phone rejects the file due to a signature verification failure because the file has the signature of the TFTP server's local cluster, which does not match the Initial Trust List (ITL) of the phone. To resolve this issue, you can either disable Security By Default (SBD) for the phone or perform the bulk certificate export procedure to make the Trust Verification System (TVS) return a success when the phone verifies a signature from a different cluster. See the procedure in the "Default Security Setup" section of the Cisco Unified Communications Manager Security Guide for performing a bulk certificate export when migrating IP phones between clusters. To disable Security by Default, see the procedure to update the ITL file for IP Phones in the Cisco Unified Communications Manager Security Guide.

Empty Far-End When Recording Call Park for Some Phones

This documentation update resolves CSCud03278.

In the current Call Park implementation, the far-end or X-Refci may be empty when recording Call Park for phone models such as 997X, 995X and 896X.

Limitation for Mobility Voice Mail Avoidance

This information applies to CSCud25228.

A possible limitation involves both Voice Mail Avoidance (VMA) and Call Forward No Answer (CFNA) interaction. The scenario is as follows:

CFNA Timer = 12 seconds

Delay Before Ring Timer = 4 seconds

Call Screening Timer = 4 seconds

User Control Confirmed Answer Indication Timer = 10 seconds

  1. 00:00 Phone A calls a 3G-registered dual-mode device configured with user control voicemail avoidance, dual-mode B (DM B). This dual-mode has a shared line, Phone C.

  2. 00:00 Phone A hears a ringback tone. The CFNA and Delay Before Ring timers start. Phone C rings.

  3. 00:04 The Delay Before Ring timer pops. The mobility layer attempts to establish the 3G data channel before extending the call over the PSTN network. The SIP Progress timer (Call Screening timer) starts.

  4. 00:08 The Call Screening timer pops. Due to 3G network errors or delays, the mobility layer never received a SIP Progress from the dual-mode mobile client. To make up for this, the CFNA timer is restarted. The call to the mobile identity of DM B is extended over the PSTN network.

  5. 00:18 User answers the call on the mobile identity of DM B. The CFNA timer is restarted again. The user does not hear the prompt to "press any digit to be connected."

  6. 00:28 The User Control Confirmed Answer Indication Timer fires. Mobility tears down the call and sends a CcRejInd. However, LineCdpc holds onto this CcRejInd because it has not heard from all other shared lines, including Phone C.

  7. 00:30 The CFNA timer fires and Phone A is redirected to the voicemail/CFNA destination of DM B/Phone C.


Though unlikely, this scenario is possible. Cisco determined that it is preferable for users to have a lengthened CFNA timer than to have users pick up the call on their mobile identity with, for example, 2 seconds left on the CFNA timer. If the CFNA timer is not restarted and the user does not press a digit within 2 seconds, the call will suddenly be redirected to the CFNA destination, leaving the called user confused.

Upgrade to 9.1(1) Fails with Insufficient Disk Space

This information applies to CSCuc63312.

When upgrading Cisco Unified Communications Manager to Version 9.1(1), the upgrade may fail due to insufficient disk space. You will see the following error message:

There is not enough disk space in the common partition to perform the upgrade. For steps to resolve this condition please refer to the Cisco Unified Communications Manager 9.1(1) Release Notes or view defect CSCuc63312 in Bug Toolkit on

Reduce Disk Space Utilization

Follow this procedure to reduce disk space utilization during an upgrade.

    Step 1   Reduce the amount of traces on the system by lowering the low and high watermarks in the Cisco Log Partition Monitoring Tool. The low watermark adjusts by changing the properties of the LogPartitionLowWaterMarkExceeded alert. The high watermark adjusts by changing the properties of the LogPartitionHighWaterMarkExceeded alert. For more information about the Cisco Log Partition Monitoring Tool, see the Cisco Unified Real-Time Monitoring Tool Administration Guide.

    After the upgrade, you must restore the high and low watermarks to their original values in order to avoid premature purging of traces. The default value for the high watermark is 85. The default value for the low watermark is 80.

    Step 2   If you still get the error message, install the COP file named ciscocm.free_common_space_v1.0.cop.sgn that you can find on at Cisco Unified Communications Manager Version 9.1 > Unified Communications Manager/ CallManager/ Cisco Unity Connection Utilities > COP-Files.

    This COP file frees disk space to allow the upgrade to proceed.


    You must perform an upgrade after applying the COP file.


    You will not be able to switch to the previous version after the COP file is installed. For example, if you are upgrading from Cisco Unified Communications Manager 9.0(1) to Cisco Unified Communications Manager 9.1(1) and the previous version is Cisco Unified Communications Manager 8.6, the COP file clears the space by removing the 8.6 version data that resides in the common partition. So after you apply the COP file, you will not be able to switch to the 8.6 version.


    If you are unable to perform the upgrade and continue to receive the error message after applying this COP file, the amount of data present on the running version does not leave adequate space for expanding and executing the upgrade. In this case, you can recover more space by removing unused device firmware from the TFTP path. In some cases, having sufficient space for an upgrade will require that you take a backup, reinstall to a larger capacity disk or larger sized Open Virtual Appliance (OVA), and restore. Contact Cisco Technical Assistance Center (TAC) if you require further assistance.

    Cisco Prime Unified Provisioning Manager Business Edition Compatibility

    This information applies to CSCue09155.

    Cisco Unified Communications Manager 9.1(1) is not compatible with Cisco Prime Unified Provisioning Manager Business Edition 9.0(1).

    Phone Support for URI Dialing Display Preference Service Parameter

    Most Cisco Unified IP Phones do not support the URI Dialing Display Preference service parameter. Regardless of how you configure the service parameter, the phone displays a directory URI, if one is available. To ensure full support of this service parameter, make sure that you install the latest phone builds. This service parameter is fully functional system-wide only after the phone firmware implements the changes.


    The default value of URI Dialing Display Preference has been changed from "URI" to "DN."

    Call Queuing Not Supported with Mobile Device Types

    Cisco Unified Communications Manager does not support Call Queuing with mobile device types.

    CSCug39491 Configure Cygwin with DRS

    CSCui95074 The Release Note for RTMT Does Not Mention Win7 as Supported Platform

    You can install Cisco Unified Real-Time Monitoring Tool (Unified RTMT) on a computer running Windows 7.


    To create a Unified RTMT certificate store on a Windows 7 platform, you must have a username with full administrative privileges.

    Bridge Upgrade Fails with Insufficient Disk Space

    This information applies to CSCuj24138.

    Bridge upgrades may fail due to insufficient disk space on servers that have 72GB hard drives, such as the MCS-7835-H2 or the MCS-7835-I2. When this failure occurs, the install.log file displays a message indicating that there is no more space left on the partition.

    This failure may occur when you are upgrading a large cluster, when the database is large, or when the server contains a large amount of TFTP data. If a failure occurs when you upgrade from Cisco Unified Communications Manager Release 7.x to Release 9.1(1), perform one or more of the following actions to create more disk space on the partition:

    • Move log files to other machines.
    • Install the ciscocm.free_common_space_<latest_version>.cop.sgn file; this COP file removes the inactive side in the common partition to increase available disk space.


    If you install the COP file, you will not be able to switch back to the inactive version.

    Corrections for the Immediate Divert Feature

    Configure Immediate Divert

    This documentation update resolves CSCun20448.

    Steps 6 and 7 are incorrect for the "Configure Immediate Divert" procedure in the Features and Services Guide. The following are the corrected steps.

    Step 6

    Standard User or Standard Feature softkey is copied to a new template and then the template is used to assign iDivert softkey. Assign the softkey in the Connected, On Hold, and Ring In states. Divert softkey in Cisco Unified IP Phones 8900 series gets enabled using the softkey template and for the 9900 series the Divsert softkey feature gets enabled using feature control policy template.

    Step 7

    In the Phone Configuration window, assign the newly configured softkey template which has iDivert enabled, to each device that has immediate divert access.

    System requirements for Immediate Divert

    The following table lists the phones that use the Divert or iDivert softkey. The 8900 and 9900 series contain system requirement changes:
    • Cisco Unified Communications Manager 6.0 or later
    • Table 1 Cisco Unified IP Phones That Use iDivert or Divert Softkeys

      Cisco Unified IP Phone Model

      Divert Softkey

      iDivert Softkey

      What to configure in softkey template

      Cisco Unified IP Phone 6900 Series (except 6901 and 6911)



      Cisco Unified IP Phone 7900 Series



      Cisco Unified IP Phone 8900 Series



      Cisco Unified IP Phone 9900 Series



    Bulk Certificate Import Can Cause Phones to Restart

    This documentation update resolves CSCun32117.

    The following note is omitted from the "Bulk Certificate Export" section in the Cisco Unified Communications Manager Security Guide and the "Configure EMCC Section" in the Cisco Unified Communications Manager Features and Services Guide.


    When you use the Bulk Certificate Management tool to import certificates, it causes an automatic restart of the phones on the cluster on which you imported the certificates.

    CSCup71020 MaxReturnedDevices in Serviceability XML

    The Cisco Unified Communications Manager XML Developers Guide, Release 9.1(1) incorrectly specifies the maximum number of devices (MaxReturnedDevices) for which information can be returned in a search as 1000. The correct maximum number of devices is 200.

    Browser Support for Cisco Unified CM User Options

    The following table displays the list of supported browsers for Cisco Unified CM User Options Release 9.1(1).


    Windows XP

    Windows 7

    Windows 8

    Supported Browser

    Internet Explorer 8

    Firefox 8, 9

    Chrome 25

    Internet Explorer 9

    Firefox 8, 9

    Chrome 25

    Internet Explorer 8, 9

    Firefox 8, 9

    Chrome 25

    Show perf query counter Command Output

    This documentation update resolves CSCuo70238.

    The following note is omitted from the show perf query counter command section in the Cisco Unified Communications Command Line Interface Guide.


    The output that this command returns depends on the number of endpoints that is configured in the Route Groups in Cisco Unified Communications Manager.