Release Notes for Cisco Unified Communications Manager, Release 9.1(1a)
Important Notes
Download this chapter
Important NotesImportant Notes
Download the complete book
Release Notes for Cisco Unified Communications Manager, Release 9.1(1a)Release Notes for Cisco Unified Communications Manager, Release 9.1(1a) (PDF - 3 MB)
 Feedback

Contents

Important Notes

CSCue14471 Change license calculations for Extension Mobility

Extension Mobility currently consumes an essential license for Unified Communications Manager 9.1(1). This is an issue when one has Extension Mobility that is not assigned to a user. In this case, two licenses are consumed, instead of one just for the user. With this change, Extension Mobility will no longer consume an essential license. The Extension Mobility not assigned to a user scenario will only consume a single license.

CSCub12922: Adding a new subscriber causes device reset

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

CSCue04792 EMCC Logout Limitation

In the visiting cluster, the current Phone Configuration window has a Log Out button for intracluster EM. This button is also used by the visiting cluster administrator to logout an EMCC phone. Because the EMCC phone is not currently registered with the visiting Cisco Unified Communications Manager, this operation is equivalent to a DB 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.

CSCue08776 Call Queuing interaction with Hunt Groups and Hunt Pilots

The log off 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 enable for a hunt pilot.

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

Cannot install a server-client authentication certificate that is signed by a Microsoft 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.

You can perform the following procedure:

  1. Log on 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.

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

There is no upgrade path in VMware to upgrade from Cisco Unified Business Edition 5000 to Cisco Unified Communications Manager. A fresh installation is needed. After you perform the fresh installation, IM and Presence Service re-synchronizes 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 re-installed, all the pkid 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 backup your data before performing this procedure.

CSCto77824 Presence User Experiences Issues Obtaining Availability

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 toIM and Presence Service but experiences 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.

CSCud59343 Access Control Group Permissions Interactions

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

CSCtu18692 CallProcessingNodeCpuPegging alerts for VMware installations

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.

CSCud18710 Centralized Proxy TFTP File Signature Verification Failure

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 perform the bulk certificate export. To disable Security by Default, see the procedure to update the ITL file for IP Phones in the Cisco Unified Communications Manager Security Guide.

CSCud03278 Empty Far-End When Recording Call Park for RT Phones

CSCud25228 Limitation for Mobility Voice Mail Avoidance

A possible limitation was identified when fixing CSCud01434 where a corner scenario involved both Voice Mail Avoidance (VMA) and Call Forward No Answer (CFNA) interaction. The scenario is as follows:

CFNA Timer = 12s

Delay Before Ring Timer = 4s

Call Screening Timer = 4s

User Control Confirmed Answer Indication Timer = 10s

  1. 00:00 Phone A calls a 3G-registered dual-mode device configured with user control voicemail avoidance, 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 doesn't 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.

Note

While this is a corner case, it should be noted that it is possible. It was determined that it would be a better user experience to have a lengthened CFNA timer than to have the user pick up the call on their mobile identity with, for example, two seconds left on the CFNA timer. If the CFNA timer is not restarted and the user does not press a digit within two seconds, the call will suddenly be redirected to the CFNA destination, leaving the called user confused.

CSCuc63312 Upgrade to 9.1(1) Fails with Insufficient Disk Space

When upgrading Cisco Unified Communications Manager to 9.1(1) version, 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 cisco.com.

Reduce Disk Space Utilization

To reduce disk space utilization during an upgrade, follow this procedure.

Procedure
    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 is adjusted by changing the properties of the LogPartitionLowWaterMarkExceeded alert. The high watermark is adjusted 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.
    Note   

    Following 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 Cisco Connection Online under 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.

    Note   

    You must perform an upgrade after applying the COP file.

    Caution   

    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.

    Attention:

    If you are unable to perform the upgrade and continue to receive the error message even after applying this COP file, it means that the amount of data present on the running version does not leave adequate space for expanding and executing the upgrade. In such a case, more space may be recovered 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 further assistance is required.

    CSCue09155 Cisco Prime Unified Provisioning Manager Business Edition compatibility

    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

    As of Dec 2012, 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. Full phone support for this service parameter is expected with release 9.3(3), which is expected in May 2013. To ensure full support of this service parameter, please make sure that you install the latest phone builds.

    CSCuf57901 Video resolution support for SIP phones

    Cisco Unified Communications Manager supports the imageattr line in the SDP portion of the SIP header for higher resolution video calls. Cisco SIP phones that support w360p (640 x 360), such as the 9951, 9971, and 8961, automatically select the best resolution for video calls depending on the following criteria:
    • If the session level bandwidth is greater than 800Kb/s and the imageattr[640 x 480] line in the SDP exists, then VGA is used.
    • If the session level bandwidth is greater than 800Kb/s and the imageattr[640 x 480] line in the SDP does not exist, then w360p is used.
    • If the session level bandwidth is less than 800Kb/s but greater than 480 bits per second and the imageattr[640 x 480] line exists, then VGA 15 frames per second is used.

    Note

    If you currently have a Cisco IP Phone model 9951, 9971, or 8961 that supports w360p (640 x 360) video resolution and are upgrading to Cisco Unified Communications Manager release 8.5(1) or later, you may notice changes in the resolution of video calls.

    The following video call flow is between two 9951 phones (Phone A and Phone B) without imageattr line support (for example, using Cisco Unified Communications Manager releases 8.0(1) and earlier):
    1. Phone A sends a SIP message with an imageattr line in the SDP.
    2. Cisco Unified Communications Manager deletes the imageattr line in the SDP and then sends the modified SIP message to Phone B.
    3. Phone B attempts to send video with the w360p resolution because there is no imageattr line in the SDP portion of the SIP header.
    The following video call flow is between two 9951 phones (Phone A and Phone B) with imageattr line support (for example, using Cisco Unified Communications Manager releases 8.5(1) and later):
    1. Phone A sends a SIP message with the imageattr line in the SDP.
    2. Cisco Unified Communications Manager does not delete the imageattr line and sends the SIP message to Phone B unchanged.
    3. Phone B attempts to send video with the VGA resolution.