Release Notes for Cisco Unified Communications Manager, Release 9.1(1a)
Important Notes
Downloads: This chapterpdf (PDF - 1.37MB) The complete bookPDF (PDF - 2.88MB) | The complete bookePub (ePub - 401.0KB) | The complete bookMobi (Mobi - 687.0KB) | Feedback

Important Notes

Contents

Important Notes

Cisco Unified Mobility Disclaimer


Caution


The Cisco Mobility solution is verified with only Cisco equipment. This solution may also work with other third-party PSTN gateways and Session Border Controllers (SBCs), but each Cisco Mobility feature is not guaranteed to work as expected.

If you are using this solution with third-party PSTN gateways or SBCs, Cisco technical support may not be able to resolve problems that you encounter.


CSCuh70981 BFCP is Supported with TelePresence MCU

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.

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.

CSCui20806 Native Call Queuing Periodic Announcement Behavior

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.

CSCue14471 Change License Calculations for Extension Mobility

The Cisco Extension Mobility user feature consumes an essential license for Unified Communications Manager 9.0(1) through 9.1(1). With 9.1(1a) this is changed; a user configured with Extension Mobility (device profiles configured under Extension Mobility) only will no longer consume an Essential license. So, a user configured with Extension Mobility only, with no other devices assigned, will not consume an Essential license.

CSCue04792 EMCC Logout Limitation

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.

CSCum63324 Jabber Certificate Warnings with IM and Presence Service

When using the Cisco Jabber client, certificate warning messages can be encountered if the IP address is configured as the IM and Presence Service node name. To prevent Cisco Jabber from generating certificate warning messages, the FQDN should be used as the node name.

CSCue08776 Call Queuing Interaction with Hunt Groups and Hunt Pilots

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.

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

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.

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

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.


Caution


Be sure to back up 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 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.

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

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 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 Some Phones

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.

CSCud25228 Limitation for Mobility Voice Mail Avoidance

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.

Note


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.


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

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

Reduce Disk Space Utilization

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

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

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

    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.

    Note   

    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.


    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

    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.


    Note


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


    CSCuf57901 Video Resolution Support for SIP Phones

    Cisco Unified Communications Manager supports the imageattr line in the Session Description Protocol (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 800 Kbps and the imageattr[640 x 480] line in the SDP exists, then VGA is used.
    • If the session level bandwidth is greater than 800 Kbps 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 800 Kbps 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 Unified 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.

    CSCug52160 Do Not Change Hostname and IP Address Together

    You may need to change the IP address or hostname on a Cisco Unified Communications Manager server. For example, you may need to move the server from one segment to another or to resolve a duplicate IP address problem.

    If you change the IP address or the hostname of a server in a Cisco Unified Communications Manager cluster, ensure that you do not change both the IP address and the hostname at the same time. If you change both settings at the same time, the Cisco Unified Communications Manager database becomes inaccessible.

    CSCug89794 Error in Procedure for Changing Hostname

    In the document Changing the IP Address and Hostname for Cisco Unified Communications Manager, there is an error in the procedure "Changing the IP Address for Servers that are Defined by an IP Address."

    When you change the hostname for servers that are defined by an IP address, you must run the following command after you have changed the hostname and the server has rebooted:

    utils dbreplication dropadmindb

    CSCug77319 Database Replication After Hostname Change

    After you change the hostname of a Unified Communications Manager publisher or subscriber node, you must run a CLI command to set up database replication across the cluster.

    From the publisher server, run utils dbreplication rebuild all to set up replication across the whole cluster again.

    CSCuh27880 set network ip eth0 Requires Gateway Parameter

    In the document Changing the IP Address and Hostname for Cisco Unified Communications Manager, there is an error in the procedure "Changing the IP Address for Servers that are Defined by an IP Address."

    When you use a CLI command to change the IP address of the server, you must run the following command:

    set network ip eth0 <ip addr> <netmask> <gw>, where <ip_address> specifies the new server IP address, <netmask> specifies the new server network mask, and <gw> specifies the default gateway.

    CSCug39491 Configure Cygwin with DRS

    CSCuh70981 Presentation Sharing Supported with BFCP

    The Cisco Unified Communications Manager System Guide incorrectly states that Binary Floor Control Protocol (BFCP) is not supported when used between Cisco Unified Communications Manager and a Cisco TelePresence MCU conference bridge.

    Cisco Unified Communications Manager supports presentation sharing with BFCP between Unified Communications Manager and a Cisco TelePresence MCU.

    CSCug84842 Installation Fails with Unrecoverable Internal Error

    Application User Name and Password

    When you install Cisco Unified Communications Manager, you must enter an Application User name and password. You use the Application User name and password to access applications that are installed on the system, including the following areas:

    • Cisco Unified CM Administration
    • Cisco Unified Serviceability
    • Real Time Monitoring Tool
    • Cisco Unified Reporting

    To specify the Application User name and password, follow these guidelines:

    • Application User name - The Application User name must start with an alphabetic character and can contain alphanumeric characters, hyphens and underscores.
    • Application User password - The Application User password must be at least six characters long and can contain alphanumeric characters, hyphens, and underscores.

    Caution


    Do not use the system application name as the Application User name. Using a system application name causes the installation to fail with an unrecoverable error during the installation of the database

    System application names are:

    • CCMSysUser
    • WDSysUser
    • CCMQRTSysUser
    • IPMASysUser
    • WDSecureSysUser
    • CCMQRTSecureSysUser
    • IPMASecureSysUser
    • TabSyncSysUser
    • CUCService

    You can change the Application User name and password by using the command line interface. For more information, see the Command Line Interface Reference Guide for Cisco Unified Communications Solutions.

    CSCul38276 RTMT Update Is Required Upon Unified Communications Manager Upgrade

    When you perform an upgrade to Unified Communications Manager, an upgrade to the Cisco Unified Real Time Monitoring Tool (Unified RTMT) is required.

    Upgrade RTMT


    Tip


    To ensure compatibility, Cisco recommends that you upgrade RTMT after you complete the Cisco Unified Communications Manager upgrade on all servers in the cluster.


    RTMT saves user preferences and downloaded module jar files locally on the client machine. The system saves user-created profiles in the database, so you can access these items in Unified RTMT after you upgrade the tool.

    Before You Begin

    Before you upgrade to a newer version of RTMT, Cisco recommends that you uninstall the previous version.

    Procedure
      Step 1   From Cisco Unified CM Administration, choose Application > Plugins.
      Step 2   Click Find.
      Step 3   Perform one of the following actions:
      • To install the tool on a computer that is running the Microsoft Windows operating system, click the Download link for the Cisco Unified Real-Time Monitoring Tool - Windows.
      • To install the tool on a computer that is running the Linux operating system, click the Download link for the Cisco Unified Real-Time Monitoring Tool - Linux.
      Step 4   Download the installation file to your preferred location.
      Step 5   Locate and run the installation file. The extraction process begins.
      Step 6   In the RTMT welcome window, click Next.
      Step 7   Because you cannot change the installation location for upgrades, click Next. The Setup Status window appears; do not click Cancel.
      Step 8   In the Maintenance Complete window, click Finish.

      CSCul10528 License Mac References

      In Unified Communications Manager 9.x and later, the license mac is no longer used for licensing purposes; Enterprise License Manager handles licensing. Please ignore references to the license mac in the documentation.

      CSCuj24138 Bridge Upgrade Fails with Insufficient Disk Space

      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.

      Note


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

      ILS Troubleshooting Tips Corrections

      This documentation update resolves CSCun09203.

      The following information applies to the Command Line Interface Guide for Cisco Unified Communications Solutions.

      utils ils show peer info should be utils ils showpeerinfo.

      utils ils find route is an invalid command.

      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)

        X

        iDivert

        Cisco Unified IP Phone 7900 Series

        X

        iDivert

        Cisco Unified IP Phone 8900 Series

        X

        iDivert

        Cisco Unified IP Phone 9900 Series

        X

        iDivert

      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.

      Note


      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.

      Unified Communications Manager Alarms

      The Cisco Unified Communications Manager Managed Service Guide contains a list of system error alarm messages that may not be up to date.

      For a complete list of system error messages, see the System Error Messages document for your release at the following URL:

      http:/​/​www.cisco.com/​c/​en/​us/​support/​unified-communications/​unified-communications-manager-callmanager/​products-system-message-guides-list.html

      Configure LDAP Directory

      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 2000
      • Microsoft Active Directory 2003 R1 & R2 (32-bit)
      • Microsoft Active Directory 2008 R1 (32-bit) & R2 (64-bit)
      • Microsoft Active Directory Application Mode 2003 R1 & R2 (32-bit)
      • Microsoft Lightweight Directory Services 2008 R1 (32-bit) & R2 (64-bit)
      • Sun ONE Directory Server 5.2
      • Sun ONE Directory Server 6.x
      • Oracle Directory Server Enterprise Edition 11gR1
      • OpenLDAP 2.3.39
      • OpenLDAP 2.4

      CSCum01216 Serviceability XML API doc in error

      The following is implemented in Cisco Unified Communications Manager in Release 10.0(1):

      The SelectCmDevice API returns SIP trunk status and also returns the IP addresses and status of the peer devices.

      Hostnames in IPv4 and IPv6 Environments

      This documentation update resolves CSCun74975.

      The following information is omitted from the IPv6 Address (for dual IPv4/IPv6) field description under "Server Settings" in the Cisco Unified Communications Manager Administration Guide:

      You cannot use an IPv4 address as a hostname in a network environment with both IPv4 and IPv6 addresses.

      Music On Hold and Native Call Queuing Behavior

      The Announcements with Music On Hold document discusses Native Call Queuing and the added capabilities that are related to customized audio announcements and Music On Hold. Access this document at the following URL:

      http:/​/​www.cisco.com/​c/​en/​us/​support/​unified-communications/​unified-communications-manager-callmanager/​products-technical-reference-list.html

      Calling Party Normalization Restriction

      This documentation update resolves CSCuo56960.

      The following restriction is omitted from the Features and Services Guide for Cisco Unified Communications Manager:

      When calling or called party transformations are applied at the gateway or route list level, the calling number in the facility information element (IE) for QSIG calls is the post-transformation number. However, the called party in the facility IE is the pre-transformation called party number.

      The calling party that is sent after transformation through the gateway is typically localized and does not cause an issue with the display and routing. The called party is typically the dialed digits and is displayed on the calling phone, so the transformation is not relayed for called party transformations. Called party transformation is designed to send the information based on the gateway that the call is going through, regardless of how the number is dialed. Called party transformation is kept at the gateway level and not updated, whereas the calling party is updated.

      Maximum Hunt Timer Restriction

      This documentation update resolves CSCuo90637.

      The following note is omitted from the Cisco Unified Communications Manager Administration Guide and online help for Hunt Group configuration:


      Caution


      Do not specify the same value for the Maximum Hunt Timer and the RNA Reversion Timeout on the associated line group.


      Remote Destination and Auto Answer

      This documentation update resolves CSCtd43582.

      The following restriction is omitted from the "Cisco Mobility" chapter in the Features and Services Guide for Cisco Unified Communicatins Manager:

      A remote destination call does not work when Auto Answer is enabled.

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

      Platform

      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

      Cisco Certificate Change Notification Service

      This documentation update resolves CSCup84785.

      The following content is omitted from the Platform Services section of the "Services" chapter in the Cisco Unified Serviceability Administration Guide:

      Cisco Certificate Change Notification Service

      This service keeps certificates of components like Tomcat, CallManager, and XMPP automatically synchronized across all nodes in the cluster. When the service is stopped and you regenerate certificates, you have manually upload them to Certificate Trust on the other nodes.

      Secure and Nonsecure Indication Tone

      This documentation update resolves CSCuq04604.

      In the Cisco Unified Communications Manager Security Guide, the section about secure and nonsecure indication tones states that "Protected devices can call nonprotected devices that are either encrypted or nonencrypted. In such cases, the call specifies nonprotected and the nonsecure indication tone plays." This statement applies only if a protected phone calls a nonencrypted, nonprotected phone. If the call is encrypted for both parties, the indication tone plays the secure tone.

      Protected devices that call nonprotected devices that are encrypted play the secure tone, while protected devices that call nonprotected and nonencrypted devices play the nonsecure tone.

      Incorrect Default Value for LogPartitionLowWaterMarkExceeded Alert

      This documentation update resolves CSCuq39087.

      The default threshold value for LogPartitionLowWaterMarkExceeded alert is incorrectly described in the Cisco Unified Real-Time Monitoring Tool Administration Guide. The following table contains the correct value.

      Table 2 Default Configuration for the LogPartitionLowWaterMarkExceeded RTMT Alert

      Value

      Default Configuration

      Threshold

      Trigger alert when following condition met:

      Log Partition Used Disk Space Exceeds Low Water Mark (90%)

      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.

      Note


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