Release Notes for Cisco Unified Communications Manager, Release 9.1(1a)
Documentation Updates
Downloads: This chapterpdf (PDF - 1.65MB) The complete bookPDF (PDF - 2.82MB) | The complete bookePub (ePub - 374.0KB) | The complete bookMobi (Mobi - 687.0KB) | Feedback

Documentation Updates

Contents

Documentation Updates

License Mac References

This documentation update resolves CSCul10528.

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.

Administration Guide

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.

Application User AXL Password Must Not Contain Special Characters

This documentation update resolves CSCud34740.

The following note is missing from the Application User Settings chapter in the Cisco Unified Communications Manager Administration Guide:


Note


Do not use special characters when you cwreate an AXL password for an application user.


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.

Call Stats Field Removed

This documentation update resolves CSCug63874.

On the Device > Device Settings > SIP Profile setup window, the Call Stats option has been removed.

Common Phone Profile Settings Secure Shell Information

This documentation update resolves CSCug58742.

In the Common phone profile settings, the Secure Shell Password field is incorrectly referred to as the Secure Shell User.

Connected Lined ID Presentation Value

This documentation update resolves CSCug28060.

Descriptions of the Connected Line ID Presentation parameter were updated to include the following statement:

If a call that originates from an IP phone on Cisco Unified Communications Manager encounters a device, such as a trunk, gateway, or route pattern, that has the Connected Line ID Presentation set to Default, the presentation value is automatically set to Allowed.

CTI Remote Device Name Cannot Contain Spaces

This documentation update resolve CSCue57419.

In the CTI remote device configuration settings window, you cannot add a space in the Device name field for CTI remote devices.

Directory Number Line Behavior in Cisco Unified Communications Manager

This documentation update resolves CSCuo74599.

The following information is omitted in the "Set Up Cisco Unified IP Phone" procedure in the Cisco Unified Communications Manager Administration Guide:

After you add a directory number to a phone and click Save, the following message appears:

Directory Number Configuration has refreshed due to a directory number change. Please click Save button to save the configuration.

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.

An ILS Restart is Required for Changes to Directory URI Catalogs

This documentation update resolves CSCur52619.

The following note is omitted from the "Intercluster Directory URI" chapter in the Administration Guide for Unified Communications Manager, Release 9.x:


Note


When ILS is configured and a route string is changed on an Imported Directory URI Catalog, a restart is required so that the hub can update this catalog and remove old cached entries when making a call with an ILS lookup.

The restart is only to update the hub and not the spoke clusters. The spoke clusters receive the update within the synchronization cluster time that is configured on the ILS Configuration window.


Incorrect Information about Deleting Route Patterns

The Cisco Unified Communications Manager Administration Guide and online help contain incorrect information about deleting route patterns such as route groups, hunt lists, and hunt pilots.

The following information further explains the context:

The association of any pattern or directory number (DN) to any device is separate from the devices and patterns themselves. As a result, you can delete a route list even if it is currently used for a route pattern. The same applies to hunt lists, hunt pilots, phones, and DNs.

As a best practice, whenever you remove a device, you must ensure that any associated pattern or DN is accounted for in your numbering plan. If you no longer need a pattern or DN, you must delete it separately from the device with which it was associated. Always check the configuration or dependency records before you delete a hunt list.

The following is an example of incorrect information in the guide:

Cisco Unified Communications Manager associates hunt lists with line groups and hunt pilots; however, deletion of line groups and hunt pilots does not occur when the hunt list is deleted. To find out which hunt pilots are using the hunt list, click the Dependency Records link from the Hunt List Configuration window. If dependency records are not enabled for the system, the dependency records summary window displays a message.

The following is the corrected information:

Cisco Unified Communications Manager associates hunt lists with line groups and hunt pilots. You can delete a hunt list even when it is associated with line groups and hunt pilots. To find out which hunt pilots are using the hunt list, click the Dependency Records link from the Hunt List Configuration window. If dependency records are not enabled for the system, the dependency records summary window displays a message.

Incorrect Note about User Locales

This documentation update resolves CSCuq42434.

The note about user locales in the Cisco Unified IP Phone settings section of the Administration Guide incorrectly states that Cisco Unified Communications Manager uses the user locale that is association with the device pool. The following is the correct note:


Note


If no user locale is specified, Cisco Unified Communications Manager uses the user locale that is associated with the common device configurations.


Line Group Deletion Correction

This documentation update resolves CSCuq26110.

The following is a correction to Line Group Deletion.

You can delete a line group that one or more route/hunt lists references. If you try to delete a line group that is in use, Cisco Unified Communications Manager displays an error message.


Tip


Dependency Records is not supported for line groups. As a best practice, always check the configuration before you delete a line group.


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.


Link Loss Type Field is Relabeled

This documentation update resolves CSCue58074.

On the System > Region configuration window, the Link Loss Type field has been relabeled as the Audio Codec Preference List field.

Option For Voicemail Usage Description

This documentation update resolves CSCtw44786.

The following description about For voice mail usage option has been added to the Add hunt list procedure in step 6.

"If you check the For Voice Mail Usage check box, the route list control process keeps a count of the setups that are being served to the hunt list, and will not allow more setups than the number of available devices. As a result, each device in the hunt list is treated as if it has a Busy Trigger and related Maximum Number of Calls of one".

"For example, if the hunt list contains five devices, and if busy trigger is two for each member, with the For Voice Mail Usage checkbox unchecked, it can process up to ten setups. For the same number of hunt list devices with a busy trigger of two for each member, with the For Voice Mail Usage checkbox checked, it can process only five setups and the next immediate setup after five gets rejected".

Service Name Cannot Be Localized

This documentation update resolves CSCuh62299.

The following note is added to the Service Name field under IP phone service settings table in the Cisco Unified Communications Manager Administration Guide.


Note


When the service URL points to an external customized URL, you cannot localize the service name as per the device locale of the phone. The service name gets displayed in English alphabets only.


Use Personal Preference Field is Relabeled

This documentation update resolves CSCug52147.

On the Call Routing > Route/Hunt > Hunt Pilot setup window, the Use Personal Preferences option has been renamed to Use Forward Settings of Line Group Member.

Bulk Administration Guide

Missing Note in Insert Phone Topic

This documentation update resolves CSCug41922.

The following note is missing from "Insert Phones in to Cisco Unified Communications Manager":


Note


BAT expects Directory Number URI fields for directory numbers in the following format:

URI 1 on Directory Number 1, URI 1 Route Partition on Directory Number 1, URI 1 is Primary on Directory Number 1.


Model Is Not a Valid Device Field When Generating Phone Reports

This documentation update resolves CSCui06050.

"Phone and IP telephony device reports" lists Model as a device field. However, this field is not an option in the Bulk Administration Tool.

Call Detail Records Administration Guide

Call Recording Samples in CDR Examples Chapter

The Call Recording section in the CDR Examples chapter of the Cisco Unified Communications Manager Call Detail Records Administration Guide contains descriptions of two call recording scenarios. However, the displayed CDR records are monitoring CDRs rather than recording CDRs. Following are the two examples with recording CDRs:

  1. The customer (9728134987) calls the agent (30000), and the agent answers. The Recorder's DN is 90000. The recording feature creates two recording calls to the recording device, which results in two additional CDRs: one for the agent voice, and another for the customer voice. The origConversationID from the recording CDRs matches the destLegCallIdentifier of the recorded CDR. In this scenario, the customer hangs up.

    Field Names

    Recorded Call CDR

    Recording Call CDR1

    Recording Call CDR2

    globalCallID_callId

    7

    10

    11

    origLegCallIdentifier

    16777110

    16777120

    16777122

    destLegCallIdentifier

    16777111

    16777121

    16777123

    callingPartyNumber

    9728134987

    BIB

    BIB

    originalCalledPartyNumber

    30000

    90000

    90000

    finalCalledPartyNumber

    30000

    90000

    90000

    lastRedirectDn

    30000

    90000

    90000

    origCause_Value

    16

    0

    0

    dest_CauseValue

    0

    0

    0

    origCalledPartyRedirectReason

    0

    354

    354

    lastRedirectRedirectOnBehalfOf

    0

    354

    354

    origCalledPartyRedirectOnBehalfOf

     

    27

    27

    lastRedirectRedirectOnBehalfOf

     

    27

    27

    origConversationID

    0

    16777111

    16777111

  2. The agent (30000) calls the customer (9728134987), and the customer answers. The Recorder's DN is 90000. The recording feature creates two recording calls to the recording device, which results in two additional CDRs: one for the agent voice, and another for the customer voice. The origConversationID field from the recording CDRs will match the origLegCallIdentifier field of the recorded CDR. In this scenario, the agent hangs up.

    Field Names

    Recorded Call CDR

    Recording Call CDR 1

    Recording Call CDR 2

    globalCallID_callId

    71

    100

    110

    origLegCallIdentifier

    16777113

    16777220

    16777222

    destLegCallIdentifier

    16777114

    16777221

    16777223

    callingPartyNumber

    30000

    BIB

    BIB

    originalCalledPartyNumber

    9728134987

    90000

    90000

    finalCalledPartyNumber

    9728134987

    90000

    90000

    lastRedirectDn

    9728134987

    90000

    90000

    origCause_Value

    16

    16

    16

    dest_CauseValue

    0

    0

    0

    origCalledPartyRedirectReason

    0

    354

    354

    lastRedirectRedirectOnBehalfOf

    0

    354

    354

    origCalledPartyRedirectOnBehalfOf

     

    27

    27

    lastRedirectRedirectOnBehalfOf

     

    27

    27

    origConversationID

    0

    16777113

    16777113

Change Order of HuntPilotDN

This documentation update resolves CSCul25436.

The following attributes order is incorrect in Cisco Unified Communications Manager Call Detail Records Administration Guide

The documented order for HuntPilotDN and HuntPilotPartition should be reversed to HuntPilotPartition and HuntPilotDN

FinalCalledPartyNumber Field Description Is Incorrect

This documentation update resolves CSCub12688.

The Cisco Unified Communications Manager Call Detail Records Administration Guide states that the FinalCalledPartyNumber record represents a numeric string of up to 48 characters that can be either digits or a SIP URL. This information is incorrect. The field does not have a 48 character limit and can be an alphanumeric string that can be either digits or a SIP URL.

Missing CDR Field Descriptions

This documentation update resolves CSCud20005.

The following field descriptions are omitted from the Cisco Unified Communications Manager Call Detail Records Administration Guide:
wasCallQueued

This field specifies whether the call has been put into a queue. A value of 0 means that the call is not put into any queue; 1 means the call has been put into a queue.

totalWaitTimeInQueue

This field specifies how long a caller has been in a queue. The value is specified in seconds. The value is 0 if the call was never put into any queue.

Missing CDR Field Descriptions for IMS Application Server

This documentation update resolves CSCum60891.

The following CDR field descriptions in the table below for IMS Application Server are omitted from the Call Detail Records Administration Guide.

Field Name

Range of Values

Description

incomingICID

Text String

Alphanumeric string up to 50 characters

This field is populated with the IMS Identifier(ICID) from the P-Charging Vector at the incoming call leg of the call.

This field will be empty when the call leg has no IMS or SIP trunk with P-Charging-Vector enabled.

Default = Empty String " "

incomingOrigIOI

Text String

Alphanumeric string up to 50 characters

This field is populated with the originating Interoperator Identifier(IOI) from the P-Charging Vector at the incoming call leg of the call.

This field will be empty when the call leg has no IMS or SIP trunk with P-Charging-Vector enabled.

Default = Empty String " "

incomingTermIOI

Text String

Alphanumeric string up to 50 characters

This field is populated with the terminating Interoperator Identifier(IOI) from the P-Charging Vector at the incoming call leg of the call.

This field will be empty when the call leg has no IMS or SIP trunk with P-Charging-Vector enabled.

Default = Empty String " "

outgoingICID

Text String

Alphanumeric string up to 50 characters

This field is populated with the IMS Identifier(ICID) from the P-Charging Vector at the outgoing call leg of the call.

This field will be empty when the call leg has no IMS or SIP trunk with P-Charging-Vector enabled.

Default = Empty String " "

outgoingOrigIOI

Text String

Alphanumeric string up to 50 characters

This field is populated with the originating Interoperator Identifier(IOI) from the P-Charging Vector at the outgoing call leg of the call.

This field will be empty when the call leg has no IMS or SIP trunk with P-Charging-Vector enabled.

Default = Empty String " "

outgoingTermIOI

Text String

Alphanumeric string up to 50 characters

This field is populated with the terminating Interoperator Identifier(IOI) from the P-Charging Vector at the outgoing call leg of the call.

This field will be empty when the call leg has no IMS or SIP trunk with P-Charging-Vector enabled.

Default = Empty String " "

outpulsedOriginalCalledPartyNumber

Text String

Alphanumeric string up to 50 characters

The Original called party number outpulsed from the device.

Default = Empty String " "

outpulsedLastRedirectingNumber

Text String

Alphanumeric string up to 50 characters

The Last Redirecting number outpulsed from the device.

Default = Empty String " "

Changing IP Address and Hostname

Change the Hostname Using the Unified Communications Operation System Administration GUI

In the procedure "Change hostname using Unified Communications Operation System Administration GUI," there is an error in the output displayed for step 5, which directs you to use the utils network host command to verify that the name-IP association has propagated to other nodes. When you use the command, the output should read as follows:

admin:utils network host sub-4

Hostname sub-4 resolves to 198.50.103.11

Database Replication After Hostname Change

This documentation update resolves CSCug77319.

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.

Do Not Change the Hostname and IP Address Together

This documentation update resolves CSCug52160.

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.

Error in the Procedure for Changing the Hostname

This documentation update resolves CSCug89794.

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

IP Address, Domain and Hostname for IM and Presence Service

The chapter titled "Modify the SIP Domain of an IM and Presence Cluster" has been removed and replaced with a new chapter titled "Modify Server Domain." Minor updates have been made to the remaining chapters to include instructions for when the node name is a Fully Qualified Domain Name (FQDN).

set network ip eth0 Requires Gateway Parameter

This documentation update resolves CSCuh27880.

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.

CLI Reference Guide

Enable or Disable FIPS for IM and Presence Service

This documentation update resolves CSCuo56537.


Warning


FIPS 140-2 mode for IM and Presence Service is pending certification at this time and is not supported until certification is complete.

Consider the following information before you enable or disable FIPS 140-2 mode for IM and Presence Service: After you enable or disable FIPS 140-2 mode for IM and Presence Service, the Tomcat certificate is regenerated and the node reboots. The Intercluster Sync Agent syncs the new Tomcat certificate across the cluster; this can take up to 30 minutes. Until the new Tomcat certificate is synced across the cluster, an IM and Presence Service subscriber node cannot access information from the IM and Presence Service database publisher node. For example, a user who is logged in to the Cisco Unified Serviceability GUI on a subscriber node cannot view services on the IM and Presence Service database publisher node. Users see the following error message until the synching is complete: Connection to server cannot be established (certificate exception)

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.

run cuc sysagent task Example is Incorrect

This documentation update resolves CSCum43072.

The example for the command run cuc sysagent task is incorrect. The command line should state the following: run cuc sysagent task Umss.CleanDeletedMessagesTask.

The following content is missing: For a list of Sysagent tasks, run the command show cuc sysagent task list (Cisco Unity Connection Only). Be aware that sysagent task names are case sensitive.

set network domain Conflicting Information

This documentation update resolves CSCup03425.

The set network domain command section of the Set Commands chapter in the Command Line Interface Guide for Cisco Unified Communications Solutions contains conflicting information about manual and automatic certificate regeneration of all Cisco Unified Communications Manager certificates. At present, only automatic regeneration of certificates is supported.

The content related to manual certificate regeneration has been removed from the Usage Guidelines section. The following is the final content of the Usage Guidelines section:

Usage Guidelines:

The system asks whether you want to continue to execute this command.


Caution


If you continue, this command causes a temporary loss of network connectivity.


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.


Deployment Guide for IM and Presence Service

Enhanced IM and Presence Deployment Support

The procedure to configure XMPP certificate settings has been removed from the "Security configuration on IM and Presence" chapter.

The following topics have been added to support the Enhanced IM and Presence Deployment Support feature:

  • DNS domain configuration

  • Presence domain configuration

  • Specify DNS domain associated with Cisco Unified Communications Manager cluster

The following topics have been updated to support the Enhanced IM and Presence Deployment Support feature:

  • Node name recommendations

  • Node name value for intercluster deployments

  • Presence domain value for intercluster deployments

The topic titled "Single Sign-On setup" has been updated to include support for the Cisco Client Profile Agent. This service is required for Cisco Jabber Single Sign-On (SSO) support.

Exceeding Maximum Contact List Settings During Contact List Import Is Supported

This documentation update resolves CSCug87105.

It is possible to exceed the maximum contact list size setting without losing data when importing user contact lists to IM and Presence Service using the Bulk Administration Tool; however, Cisco recommends temporarily increasing the Maximum Contact List Size setting or setting the value to Unlimited for the import. You can reset the maximum value after the import is complete.

Locale Installation Information Update

This documentation update resolves CSCue81331.

Removed the procedure to install Locale installer on Cisco Unified Communications Manager with instructions to see the Upgrade Guide for Cisco Unified Communications Manager for details about installing locales on the Cisco Unified Communications Manager.

Additional topics from the Upgrade Guide for Cisco Unified Communications Manager were added that cover the following:

  • Locale installation considerations and information to obtain the Locale Installer from www.cisco.com.

  • Locale file descriptions for Cisco Unified Communications Manager (cm-locale-language-country-version.cop), the Cisco Unified Communications Manager combined network locale file (cm-locale-combinednetworklocale-version.cop), and for IM and Presence Service (ps-locale-language_country-version.cop).

Disaster Recovery System Guide

System Backup File Encryption

This documentation update resolves CSCui75485.

A note was added to the topic describing how to view the backup history, which clarifies that the Cisco Unified Communications Manager and IM and Presence Service backup job files are encrypted and can be opened only by the system software.

Updated Caution to Include DNS and Domain Name Prior To Restore

This documentation update resolves CSCul28047.

The following caution is updated to include DNS and domain name prior to performing a restore:


Caution


Before you restore Cisco Unified Communications Manager, ensure that the hostname, IP address, DNS configuration, domain name, version, and deployment type of the restore matches the hostname, IP address, DNS configuration, domain name, version, and deployment type of the backup file that you want to restore.

Features and Services Guide

Call Mobility Missing Information

The following limitation is missing from the "Cisco Mobility" chapter in the Cisco Unified Communications Manager Features and Services Guide:

Cisco Unified Communications Manager does not support Unified Mobility with Call Queuing.

Call Park Display Timer Restriction

This documentation update resolves CSCug36365.

The interaction between the value that is entered for the Call Park Reversion Timer and the Cisco Call Park Display Timer must be updated in the Call Park restrictions section as follows:

If you entered a Call Park Reversion Timer value that is less than the Call Park Display Timer, Call Park numbers may not display on the phone.

Call Pickup Group Visual Notification Does Not Support Localization

This documentation bug resolves CSCup04321.

Localization support is not available for call pickup group visual notification, because this notification uses ASCII for the alerting name.

Call Pickup Phones Supported

This documentation update resolves CSCue92900.

The following information is omitted from the table that lists phones that support Call Pickup:

The Cisco Unified IP Phone series 7900, 8900, and 9900 support both softkey and button activated Call Pickup. For the 3500 Cisco Unified IP Phone, the Call Pickup feature is activated using the menu.

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.

Call Queuing Missing Information

The following limitation is missing from the "Call Queuing" chapter in the Cisco Unified Communications Manager Features and Services Guide:

Cisco Unified Communications Manager does not support Unified Mobility with Call Queuing.

Call Queuing Not Supported with Mobile Device Types

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

Call Queuing Shared Line Scenario Description

This documentation update resolves CSCue98877.

In the Call queuing operation considerations section, the paragraph describing shared-line deployments should read as follows:

For shared-line deployments, the availability of all devices with that shared-line are combined to provide a final status. If a shared-line device for one or members appears as on-hook, but all others are indicating off-hook, the final status for that line member remains off-hook.

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.

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.

Configuring OpenAM Section

This documentation update resolves CSCup44177.

The following content is missing from the "Configure OpenAM" section of "Single Sign-On" chapter:

After you install the OpenAM server, you must ensure that a default account is created so that you can enable and configure the SSO-based authentication successfully on Cisco Unified Communications Manager applications. The default account consists of a "demo" username and a password. To enable Agent Flow SSO on Unified Communications applications, the system uses this default account to validate the following that are provisioned on OpenAM:
  • Login module

  • J2EE agent

To verify if the "demo" user is configured or not, perform the following procedure:
Procedure
    Step 1   Log in to the OpenAM server. The OpenAM administration window appears.
    Step 2   Select the Access Control tab. A list of one or more access control realms appears.
    Step 3   Click Top Level Realm.
    Note    The top level realm appears in the list when you deploy the OpenAM server. This realm contains the OpenAM configuration data.
    An additional set of configuration tabs appears.
    Step 4   Select the Subjects tab.
    Step 5   Click New. A list of fields containing user details appears.
    Step 6   Enter data for the following fields:
    • ID: demo
    • First Name: demo
    • Last Name: demo
    • Full Name: demo
    • Password: changeit
    • Password (confirm): changeit
      Note   

      Do not change this default password.

    • User Status: Select the Active radio button.
    Step 7   Click OK. The system creates a "demo" user successfully.

    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

    EMCC Incorrect Limitation

    This documentation update resolves CSCum74529.

    The following Extension Mobility Cross Cluster limitation is incorrect:

    " Duplicate user ID does not get supported (for either the same or different PIN), because the behavior is unpredictable."

    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.

    EMCC Remote Cluster Menu

    This documentation update resolves CSCue33160.

    In the chapter Extension Mobility Cross cluster, step 20 of Configure EMCC, Advance Features > EMCC > EMCC Remote Cluster menu item should be Advance Features > Cluster View.

    EMCC Video Calling Override Common Settings

    This documentation update resolves CSCue66051.

    In the chapter "Extension Mobility Cross cluster," Step 12 of Configure EMCC reads as follows:

    In either window, set the Video Capabilities drop-down list box as Enabled. (This setting may be enabled by default per cluster.)

    This is incorrect. the corrected text is as follows:

    In either window, set the Video Capabilities drop-down list box as Enabled and check the Override Common Settings check box. (Although this setting may be enabled by default per cluster, it may be necessary to check the Override Common Settings check box and save the change)

    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.

    Enterprise Feature Access and User Control

    This documentation update resolves CSCui24499.

    The following note is omitted from the Remote Destination settings table for the Single Number Reach Voicemail Policy field:


    Note


    For User Control to work, you must set the Enable Enterprise Feature Access service parameter to TRUE.


    Extension Mobility Equivalency Changes

    This documentation update resolve CSCuh56102.

    The following information is omitted from the "Extension Mobility Equivalency" section:
    • All mentions of Feature Safe and Feature Safe Configuration are removed.

    • Added a new section "EM Equivalency during login" which mentions:

      Size safe phones use the template from the login profile and the template is applied as described in "Size Safe Feature" section. Non-size safe phones must use the template that is associated with the default device profile for the model and protocol that matches the phone that the user logs into.


      Note


      The device that the user logs into must support Size Safe on Phone Template for EM Equivalency. The capability of the EM Profile does not effect EM Equivalency during login.


    • Modified the below paragraph and listed the supported SCCP and SIP phones for EM Equivalency

      Cisco Unified Communications Manager enhances the existing Extension Mobility (EM) equivalency mechanism to work across both SCCP and SIP protocols on the following models:
      • Cisco 7906

      • Cisco 7941

      • Cisco 7941G-GE

      • Cisco 7942

      • Cisco 7945

      • Cisco 7961

      • Cisco 7961G-GE

      • Cisco 7962

      • Cisco 7965

      • Cisco 7970

      • Cisco 7971

      • Cisco 7975

      • Cisco IP Communicator

    Extension Mobility Now Supports Device Owners

    This documentation update resolves CSCun04965.

    You can now configure the Owner User ID in the Phone Settings interface if you are using Extension Mobility. Extension Mobility now supports device owners. A note indicating otherwise is listed in error in the Cisco Unified Communications Manager Administration Guide.

    Hunt Pilots Limit for a Call Queue

    This documentation update resolves CSCuj75419.

    The following note is missing from the Call Queuing operation section:


    Note


    You can configure a maximum of 25 hunt pilots per hunt list in Call Queuing. If you exceed this limit, the queue status will not be displayed.

    Licensing Usage Report Correction

    This documentation update resolves CSCud80834.

    The license type list in the "Licensing" chapter contains an incomplete list. The following is the corrected list:

    System > Licensing > License Usage Report

    This window displays the current license usage on the system.

    The License Type column lists the various types of licenses:

    • Essential

    • Basic

    • Enhanced

    • Advanced

    • Premium

    • Professional

    • TelePresence Room

    Locale Usage for Queue Announcements Clarification

    This documentation update resolves CSCuj05744.

    The following content is omitted from the Announcement Settings table in the Music On Hold chapter.

    • Periodic Announcement: MOH server always plays the periodic announcement regardless of other settings.
    • Initial announcements : 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 has begun to play may only hear a portion of the announcement.
    • Locale Announcement :
      • Prompts played by MOH will use the setting for Locale Announcement.
      • Prompts played by ANN will use the User Locale of the calling party.

    MGCP FXS Ports Do Not Require a License

    This documentation update resolves CSCum47807.

    The following note is missing from "Licensing" chapter in the Features and Services Guide:


    Note


    MGCP FXS ports do not require any license because they are not considered to be analog phones.

    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

    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.

    Play Continuously and Music On Hold

    This documentation update resolves CSCue85258.

    A reference to play continuously is listed in the Music On Hold audio source configuration settings table, but should be removed.

    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.

    SIP Phones Support CMC and FAC Tones

    This documentation update resolves CSCue33154.

    The following bullet in the interactions and restrictions section of the Client matter codes and forced authorization codes chapter should be updated to include SIP:
    • The FAC and CMC tones play only on Cisco Unified IP Phones that are running SCCP or SIP, TAPI/JTAPI ports, and MGCP FXS ports.

    IM and Presence Administration Online Help

    Microsoft Lync and FQDN Updates

    The following updates were made to the Cisco Unified CM IM and Presence Administration Online Help:

    • The Cluster Topology configuration topic has been updated to recommend that you specify the FQDN as the node name.

    • Minor changes to the following topics to include support for Microsoft Lync:

      • Bulk Administration Tool Configuration to Update Users' Contact Lists

      • Bulk Administration Tool Configuration to Upload and Download Files

      • Certificate Import Tool Configuration

      • IM and Presence Configuration

      • Microsoft RCC Troubleshooter Configuration

    Extension Mobility Now Supports Device Owners

    This documentation update resolves CSCun04965.

    You can now configure the Owner User ID in the Phone Settings interface if you are using Extension Mobility. Extension Mobility now supports device owners. A note indicating otherwise is listed in error in the Cisco Unified Communications Manager Administration Guide.

    XMPP Certificate Settings Section Missing

    This documentation update resolves CSCue50920.

    The XMPP Certification Settings content was removed in error from the Security Configuration topic. The information that was removed is contained in the following table.

    XMPP Certificate Settings

    Domain Name for XMPP Server-to-Server Certificate Subject Common name

    Enter a server-to-server domain name for this cluster. If you change this domain name value, you must regenerate affected XMPP S2S certificates before you restart the Cisco XCP Router service. The entry that you configure here will be visible on the associated XMPP certificates after you regenerate the certificates.

    Allowed Values: Alphanumeric (a-zA-Z), period (.), and dash (-), and asterisk (*).

    Example:

    Domain: cisco.com

    Use Domain Name for XMPP Certificate Subject Common Name

    Default Setting: Off

    Check this check box if you want the general XMPP certificate to use the same domain name as the XMPP server-to-server certificate. If you change this setting, you must regenerate the XMPP certificate before you restart the Cisco XCP Router service.

    Installing Cisco Unified Communications Manager

    Add a New Node to an Existing Cluster

    The procedure "Add a new node to an existing cluster" has been updated to indicate that after you install a new node in an existing cluster, all phones that are registered to the cluster are reset.

    Change the IM and Presence Node Name

    The procedure to change the IM and Presence node name to a resolvable value has been updated to specify that for non-DNS deployments you must change the IM and Presence node name to be the server's IP address after installation is complete.

    External NTP Server Requirements

    The procedure "Set up first node" has been updated to remove the requirement that the external NTP server be Stratum 5 or higher. When you configure the first node, Cisco recommends configuring the publisher to point to a Stratum 1, Stratum 2, or Stratum 3 NTP server to ensure that the cluster time is synchronized with an external time source.

    Installation Fails with Unrecoverable Internal Error

    This documentation update resolves CSCug84842.

    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.

    Interdomain Federation for IM and Presence Service

    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.

    FIPS Not a Requirement for Federated Connections with LYNC 2010 Servers

    This documentation update resolves CSCui45519.

    Federal Information Processing Standard (FIPS) is not required for federated connectivity over TLSv1 encrypted connections with Microsoft Lync 2010 servers. Content that was related to configuring FIPS for Lync servers have been removed from the guide.

    Microsoft Lync Support

    IM and Presence Service Release 9.1(1) supports Partitioned Intradomain Federation with Microsoft Lync. A new chapter titled Configuration of Microsoft Lync for Partitioned Intradomain Federation has been added. Several updates have also been made to other chapters to support Microsoft Lync.

    Use TLS for Static Routes

    This documentation update resolves CSCui01368.

    You must use TLS for static routes with Microsoft Lync servers. The TCP option for static routes between Microsoft Lync servers and IM and Presence Service was removed and some sections restructured.

    Managed Services Guide

    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

    Migration and Upgrade Guide

    Server Support

    This document contains information about the supported paths for direct upgrades. The section "Server support for direct to Release 9.0 upgrade path," incorrectly refers to Release 9.0; it should refer to Release 9.x.

    OS Administration Guide

    Client Profile Agent Update

    The chapter "Single Sign-On" has been updated to include the Cisco Client Profile Agent. This service is required for Cisco Jabber support for Single Sign-On (SSO).

    Documentation Update for Certificate Monitor Configuration

    This documentation update resolves CSCuo30610.

    The following information is omitted from the Certificate Monitor Field Descriptions table:

    You can enter multiple email addresses by separating the email addresses with a semicolon (;). Do not insert a space between the email addresses. For example, test@cisco.com;test1@cisco.com;test2@cisco.com, and so on.

    ICSA Service Needs Restart After Ipsec Cert Is Regenerated

    This documentation update resolves CSCul66341.

    The following information was omitted from the IM and Presence Service Regenerate certificate topic.

    If you regenerate an ipsec certificate, you must restart the Cisco Intercluster Sync Agent after you regenerate the certificate as follows:

    • When you regenerate an ipsec certificate on the IM and Presence Service database publisher node, you must restart the Cisco Intercluster Sync Agent on the publisher node and then restart the Cisco Intercluster Sync Agent on all IM and Presence Service subscriber nodes in the cluster.
    • When you regenerate an ipsec certificate on an IM and Presence Service subscriber node, you must restart the Cisco Intercluster Sync Agent service on that node, and then restart the Cisco Intercluster Sync Agent on all other nodes in the cluster.

    Partitioned Intradomain Federation for IM and Presence Service

    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.

    FIPS Not a Requirement for Federated Connections with LYNC 2010 Servers

    This documentation update resolves CSCui45519.

    Federal Information Processing Standard (FIPS) is not required for federated connectivity over TLSv1 encrypted connections with Microsoft Lync 2010 servers. Content that was related to configuring FIPS for Lync servers have been removed from the guide.

    MatchUri Set to IM and Presence Service Domain

    This documentation update resolves CSCuh55035.

    The definition for the MatchUri field was updated in the procedure titled Configure Lync static route to point to IM and Presence Service. The MatchUri value you enter must match the IM and Presence Service domain. This should also match the Line Server URI value that is specified for each user in the Lync Control Panel.

    The MatchUri value must be written in double quotation marks, for example: -MatchUri "my-domain.com".

    Use TLS for Static Routes

    This documentation update resolves CSCui01368.

    You must use TLS for static routes with Microsoft Lync servers. The TCP option for static routes between Microsoft Lync servers and IM and Presence Service was removed and some sections restructured.

    Real-Time Monitoring Tool Guide

    Alert Removal

    This documentation update resolves CSCui25367.

    The following alerts have been removed from Unified RTMT but are listed in the Cisco Unified Real-Time Monitoring Tool Administration Guide:

    LowAttendantConsoleServerHeartbeatRate

    LowCallManagerHeartbeatRate

    LowTFTPServerHeartbeatRate

    Audit Log Configuration Settings

    This documentation update resolves CSCub37263.

    A caution was added at the end of the Audit Log Configuration Settings table.


    Caution


    When enabled, database logging can generate large amounts of data in a short period, particularly if the debug audit level is set to Database Updates or Database Reads. This can result in a significant performance impact during heavy usage periods. In general, we recommend that you keep database logging disabled. If you do need to enable logging to track changes in the database, we recommend that you do so only for short periods of time, by using the Database Updates level. Similarly, administrative logging does impact on the overall performance of the web user interface, especially when polling database entries (for example, pulling up 250 devices from the database).

    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.

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

    Missing Content from Mailbox Sync Counters

    This documentation update resolves CSCul36067.

    The following counter information is missing:

    The following table contains information about Mailbox Sync counters.
    Counters Counter Description
    Active thread count

    Cisco Unity Connection maintains threads for synchronization of voicemail from Cisco Unity Connection to Exchange server and vice-versa. At any moment, this counter specifies the number of threads that are actively in use for voicemail synchronization.

    Background queue size

    Mailbox sync has three types of priority queues: Background, Normal, and Time-Sensitive. Background queue is the lowest priority queue. This queue has items that are scheduled because of background re-synchronization of each mailbox hourly.

    Normal queue size

    Normal queue has moderate priority. This queue has items that are scheduled because of messaging operation (such as message CREATE, READ, UNREAD, DELETE) performed by user or any configuration update by administrator on Unified Messaging page on Cisco Unity Connection Administration.

    Time sensitive queue size

    Time sensitive queue has highest priority. This queue has such items that are scheduled because of keep-alive message sent by Cisco Unity Connection to Exchange server to keep subscription alive. This is applicable for 2003 Exchange server only.

    Total connection errors

    It specifies the number of times the CuMbxSync process fails to retrieve or update some data from database.

    Total Mailbox Adds

    It specifies the number of times a user mailbox has been setup for subscription. Any communication error between Unity Connection and Exchange, results in user mailbox remove and re-add.

    Total Mailbox Removes

    It specifies the number of times a user mailbox has been setup for un-subscription. Any communication error between Unity Connection and Exchange, results in user mailbox remove and re-add.

    Total Resyncs

    It specifies the total number of times user mailbox is resynchronized with Exchange server. Cisco Unity Connection does background resynchronization for all the user mailboxes hourly.

    Total Retries

    Whenever there is a communication failure between Cisco Unity connection and Exchange server, Unity Connection does mailbox synchronization retry for particular user mailbox. This counter specifies the count of such occurrences.

    Total Work Items

    It specifies number of times any messaging operation, such as CREATE, READ, UNREAD, and DELETE, has been performed on any user mailbox.

    An RTMT Update Is Required When You Upgrade Unified CM

    This documentation update resolves CSCul38276.

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

    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.

      User Options Logging

      This documentation update resolves CSCuf16874.

      A section for User Options events logging was added.

      User logging (user login and user logout) events are logged for Cisco Unified Communications Manager User Options.

      Security Guide

      BAT User Template Only Accepts Hexadecimal Characters for Digest Credentials

      This documentation update resolves CSCul78860.

      The table in "End user digest credential settings" sub section of "Digest authentication for SIP phones setup" section states that Digest Credentials accepts alphanumeric characters, which is wrong. The Digest Credentials accepts only hexadecimal characters for BAT User Template.

      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.

      CTL File Size Limit Correction

      This documentation update resolves CSCud57169.

      The Cisco Unified Communications Manager Security Guide states the following: "The Cisco CTL Client limits the file size of a CTL file to 32 kilobytes because the phones cannot accept a larger CTL file." The file size limit should be 64 kilobytes.

      Encryption Protocols Specifications Missing for Phone Models

      This documentation update resolve CSCuo01831.

      You can encrypt the phone configuration file for the following Cisco Unified IP Phones:

      Phone Model and Protocol

      Encryption Method

      Cisco Unified IP Phone 7905G or 7912G (SIP only)

      Manual key distribution—Encryption algorithm: RC4Key size: 256 bits

      File signing support: No

      Cisco Unified IP Phone 7940G or 7960G (SIP only)

      Manual key distribution—Encryption algorithm: Advanced Encryption Standard (AES) 128Key size: 128 bits

      File signing support: These phones that are running SIP receive signed, encrypted configuration files but ignore the signing information.

      Cisco Unified IP Phone 6901, 6911, 6921, 6941, 6945, and 6961

      Cisco Unified IP Phone 7970G, 7971G, or 7975G; Cisco Unified IP Phone 7961G, 7962G, or 7965G;Cisco Unified IP Phone 7941G, 7942G, or 7945G;Cisco Unified IP Phone 7911G; Cisco Unified IP Phone 7906G

      Cisco Unified IP Phone 7971G-GE, 7961G-GE, 7941G-GE

      Cisco Unified IP Phone 7931G, 7921G, 7925G, 7926G (SCCP only)

      Cisco Unified IP Phone 8941 and 8945

      Cisco Unified IP Phone 8961, 9951, and 9971

      Symmetric key encryption with phone public key (PKI encryption)—Encryption algorithm: AES 128Key size: 128 bits

      File signing support: Yes

      Refresh Upgrade Update

      The following content is missing from the "Refresh upgrade from Cisco Unified Communications Manager Release 7.x to Release 8.6 or later" section:

      Once the publisher is up after the upgrade, do not reboot until the CAR migration completes. You are not allowed to switch to old version or perform a DRS backup in this phase. You can monitor the CAR migration status by navigating to Cisco Unified Serviceability > Tools > CDR Analysis and Reporting.

      Secure Call Monitoring and Recording Update

      This documentation update resolves CSCuj71412.

      The note in "About secure call monitoring and recording setup"section is updated to remove the word "Secure" as the system does not support recording on authenticated phones.


      Note


      The system does not support recording on authenticated phones.

      SSL and TLS Support

      This documentation update resolves CSCuf49157.

      Cisco Unified Communications Manager supports SSL and Transport Layer Security (TLS) for HTTPS connections. Cisco recommends using TLS for improved security if your web browser version supports TLS. Disable SSL on your web browser to use TLS for secure HTTPS communications.

      Updated Note for Rollback Cluster to Pre-8.0

      This documentation update resolves CSCuf34403.

      The note in step 1 of "Roll back cluster to a pre-8.0 release" section incorrectly states "pre-8.6". It is "pre-8.0".

      Serviceability Guide

      AXL Web Service Requirement for ICSA HA

      This documentation update resolves CSCup00956.

      Information regarding the Cisco AXL Web Service for interclustering on IM and Presence Service was updated as follows:

      • Turn on this service on the first node only if there is no intercluster communication configured.
      • If intercluster communication is configured, this service must be enabled on both nodes in the sub-cluster where remote peers are configured to sync from.

      • Failure to turn on this service causes the inability to update IM and Presence from client-based applications that use AXL.

      Cisco CAR DB Service

      This documentation update resolves CSCup98304.

      The following service is omitted from the "Services" chapter in the Cisco Unified Communications Manager Serviceability Guide and online help.

      Cisco CAR DB Service

      Cisco CAR DB manages the Informix instance for the CAR database, which allows Service Manager to start or stop this service and to bring up or shut down the CAR IDS instance respectively. This is similar to the Unified Communications Manager database that is used to maintain the CCM IDS instance.

      The Cisco CAR DB service is activated on the publisher by default. The CAR DB instances are installed and actively run on the publisher, to maintain the CAR database. This network service is used only on the publisher and is not available on the subscribers.

      Cisco SOAP-CallRecord Service

      This documentation update resolves CSCup98302.

      The following service is omitted from the "Services" chapter in the Cisco Unified Communications Manager Serviceability Guide and online help.

      Cisco SOAP-CallRecord Service

      The Cisco SOAP-CallRecord service runs by default on the publisher as a SOAP server, so that the client can connect to CAR database through the SOAP API. This connection happens through the use of the CAR connector (with a separate CAR IDS instance).

      SOAP-Diagnostic Portal Database Service

      This documentation update resolves CSCuq22399.

      The following service is omitted from the "Services" chapter in the Cisco Unified Communications Manager Serviceability Guide and online help.

      SOAP-Diagnostic Portal Database Service

      The Cisco Unified Real-Time Monitoring Tool (RTMT) uses the SOAP-Diagnostic Portal Database Service to access the RTMT Analysis Manager hosting database. RTMT gathers call records based on operator-defined filter selections. If this service is stopped, RTMT cannot collect the call records from the database.

      Platform Administrative Web Service

      This documentation update resolves CSCup84833.

      The following service is omitted from the "Cisco Unified CM Tools" chapter in the Cisco Unified Communications Manager Serviceability Guide and online help.

      Platform Administrative Web Service

      The Platform Administrative Web Service is a Simple Object Access Protocol (SOAP) API that can be activated on Cisco Unified Communications Manager, IM and Presence Service, and Cisco Unity Connection systems to allow the PAWS-M server to upgrade the system.

      Important:

      Do not activate the Platform Administrative Web Service on the PAWS-M server.

      System Guide

      Configure LDAP Directory

      The Configure LDAP Directory topic in the "Directory Overview" chapter contains an out-of-date list of supported directories. The list incorrectly states that Cisco Unified Communications Manager supports Microsoft Active Directory 2000 and iPlanet Directory Server 5.1. In addition, the list omits Sun One Directory Server 7.0 and Oracle Directory Server Enterprise Edition 11gR1, both of which Cisco Unified Communications Manager supports, from the list of supported directories.

      Connected Lined ID Presentation Value

      This documentation update resolves CSCug28060.

      Descriptions of the Connected Line ID Presentation parameter were updated to include the following statement:

      If a call that originates from an IP phone on Cisco Unified Communications Manager encounters a device, such as a trunk, gateway, or route pattern, that has the Connected Line ID Presentation set to Default, the presentation value is automatically set to Allowed.

      LDAP Synchronized and Local End Users

      This documentation update resolves CSCud14874.

      This update applies to the End Users section in the Cisco Unified Communications Manager System Guide.

      In the Cisco Unified Communications Manager, you can add end users in two ways:
      • Manually create them in the database

      • Automatically import them from the corporate LDAP directory

      When LDAP synchronization is enabled, the local users are still active and after performing a synchronization, users that are imported from the LDAP directory are also active.

      Phones that Support International Escape Character

      This documentation update resolves CSCuj60918.

      The up-to-date list of phones that support International Escape Character is as follows:
      • Cisco Unified SIP Phones 3900 Series (3905, 3911)
      • Cisco Unified IP Phones 6900 Series (6921, 6941, 6961, 6945)
      • Cisco Unified IP Phones 7900 Series (7942, 7945, 7962, 7965, 7975, 7931)
      • Cisco Unified IP Phones 8800 Series (8831)
      • Cisco Unified IP Phones 8900 Series (8941, 8945, 8961)
      • Cisco Unified IP Phones 9900 Series(9951, 9971)
      • EX60, EX90, MX200, MX300

      Phones That Support Private Line Automatic Ringdown

      This documentation update resolves CSCuf16795.

      The Private Line Automatic Ringdown (PLAR) topic in the "Dial Rules Overview" chapter incorrectly states that only Cisco Unified IP Phones 7940/41, 7960/61, and 7970/71 support PLAR for SIP. However, the following Cisco Unified IP Phones also support PLAR over SIP: 9971, 9951, 8961, and Cisco ATA 187.

      Presentation Sharing Supported with BFCP

      This documentation update resolves CSCuh70981.

      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.

      TFTP Cisco SIP Phones

      This documentation update resolves CSCud67724.

      The "Configure TFTP for Cisco Unified IP phones that run SIP" topic contains an out-of-date table that lists the configuration files that are generated based on the type of phone that is running SIP. The table is missing several Cisco Unified IP Phones. The following is the updated table:

      Model

      SIP IP Phone

      Dial Plan

      Softkey Template

      9971, 9951, 8961, 8945, 8941, 7975, 7971, 7970, 7961, 7941, 7911, Cisco Cius

      SEP<mac>.cnf.xml

      DR<dialplan>.xml

      SK<softkey_template>.xml

      Cisco TP 1000, Cisco TP 1100, Cisco TP 1300-47, Cisco TP 1300-65, Cisco TP 1310-65

      7960, 7940

      SIP<mac>.cnf

      <dialplan>.xml

      Not configurable

      7905

      Id<mac>

      Parameter in Id<mac>

      Not configurable

      7912

      gk<mac>

      Parameter in gk<mac>

      Not configurable

      Cisco IP Communicator

      <Device Name>.cnf.xml

      Parameter in <Device Name>.cnf.xml

      Parameter in <Device Name>.cnf.xml

      Cisco Jabber for Tablet

      TAB<Userid in Upper Case>.cnf.xml

      Not configurable

      SK<softkey_template>.xml

      Updates to Supported Cisco Unified IP Phones

      This documentation update resolves CSCue50755.

      The Supported Cisco Unified IP Phones topic omits the following supported phones.


      Note


      Phone models that are End of Software Maintenance will continue to be supported on the latest Unified Communications Manager releases, but they will not take advantage of any new Unified Communications Manager features or firmware features associated with that release. For more information on End of Sale phone models, reference the End of Sale announcement for that model for information on level of firmware and hardware support.


      Cisco Unified IP Phone Model

      Description

      Cisco Unified IP Phone 8945

      The Cisco Unified IP Phone 8945 delivers affordable, business-grade voice and video communication services to customers worldwide.

      The Cisco Unified IP Phone 8945 has the following features:

      • The phone delivers VGA presentation for calling, video calling, and applications, in addition to a 5-inch (10-cm) graphical TFT color display, 16-bit color depth, 640 x 480 effective pixel resolution, and backlighting. The display also supports localization requiring double-byte Unicode encoding for fonts

      • The phone supports four lines and four context-sensitive soft keys along with a high-definition voice, full-duplex speakerphone for a more productive and more flexible endpoint experience

      • Fixed keys for hold, transfer, redial, and conference; a tri-color LED line; and feature keys also make the endpoint simpler and easier to use.

      • The Cisco Unified IP Phone 8945 supports right-to-left language presentation on its display, addressing the language localization needs of global customers.

      Cisco Unified IP Phone 8941 supports SCCP and SIP.

      Cisco Unified IP Phone 8941

      The Cisco Unified IP Phone 8941 delivers affordable, business-grade voice and video communication services to customers worldwide.

      The Cisco Unified IP Phone 8941 has the following features:

      • The phone delivers VGA presentation for calling, video calling, and applications, in addition to a 5-inch (10-cm) graphical TFT color display, 16-bit color depth, 640 x 480 effective pixel resolution, and backlighting. The display also supports localization requiring double-byte Unicode encoding for fonts

      • The phone supports four lines and four context-sensitive soft keys along with a high-definition voice, full-duplex speakerphone for a more productive and more flexible endpoint experience

      • Fixed keys for hold, transfer, redial, and conference; a tri-color LED line; and feature keys also make the endpoint simpler and easier to use.

      • The Cisco Unified IP Phone 8941 supports right-to-left language presentation on its display, addressing the language localization needs of global customers.

      Cisco Unified IP Phone 8945 supports SCCP and SIP.

      Cisco Unified IP Phone 7961G-GE

      The new Cisco Unified IP Phone 7961G-GE delivers the latest technology and advancements in Gigabit Ethernet IP telephony. This phone not only offers enhanced functionality for managers that require advanced communications capabilities, it also brings network data and applications to users quickly with its Gigabit Ethernet port for integration to a PC or desktop server. The Cisco Unified IP Phone 7961G-GE is standards-based to deliver better interoperability and greater deployment flexibility. This state-of-the-art Gigabit Ethernet IP phone also offers the same features as the Cisco Unified IP Phone 7961G, including:

      • High-resolution, graphical 4-bit grayscale display (320 x 222) that supports double-byte characters and Unicode text to benefit Extensible Markup Language (XML) application developers [Note: This phone requires IEEE 802.3af inline power or the use of a local power cube]
      • A full-featured handset with six programmable line and feature buttons
      • Four interactive softkeys to help guide users through various call features and functions

      Cisco Unified IP Phone 7941G

      The new Cisco Unified IP Phone 7941G-GE delivers the latest technology and advancements in Gigabit Ethernet IP telephony. This phone not only offers enhanced functionality for businesses that require advanced communications capabilities, but also brings network data and applications to users quickly with its Gigabit Ethernet port for integration to a PC or desktop server. The Cisco Unified IP Phone 7941G-GE is standards-based to deliver better interoperability and greater deployment flexibility.

      This state-of-the-art Gigabit Ethernet IP phone offers the same features as the Cisco Unified IP Phone 7941G and includes:

      • High-resolution, graphical 4-bit grayscale display (320 x 222) that supports double-byte characters and Unicode text to benefit Extensible Markup Language (XML) application developers [Note: This phone requires IEEE 802.3af inline power or the use of a local power cube]
      • A full-featured handset that provides two programmable line and feature buttons
      • Four interactive softkeys to help guide users through various call features and functions

      Cisco Unified IP Phone 7926G

      Increase the responsiveness of your mobile workforce within the campus and reduce overall costs with the Cisco Unified Wireless IP Phone 7926G. This portable, wireless IP phone delivers Cisco Unified Communications, integrated bar-code scanning, and custom applications.

      Building on the capabilities of the Cisco Unified Wireless IP Phone, the 7926G includes:

      • Integrated EA11 2D bar-code scanner to track location, progress, and inventory
      • Ability to decode bar code symbologies; configure with Cisco Unified Communications Manager
      • Mobile Information Device Profile custom applications (MIDlets) for faster response
      • Specially designed holster and leather case

      Cisco Unified Wireless IP Phone 7925G EX

      The Cisco Unified Wireless IP Phone 7925G-EX delivers all of the capabilities of the Cisco Unified Wireless IP Phone 7925G with the ruggedness and resiliency that is certified for deployment in potentially explosive environments such as chemical and manufacturing plants, utilities, and oil refineries.

      Features include:

      • Atmospheres Explosibles (ATEX) Zone 2/Class 22 and Canadian Standards Association (CSA) Class I Division II certifications
      • IP64 rating for superior dust resistance with splashing water resistance adds resiliency.
      • Industry-standard yellow styling offers fast recognition in event of an emergency.
      • 802.11a/b/g standards for voice over WLAN (VoWLAN) communications support.
      • Supports third-party Bluetooth 2.0 headsets for added freedom
      • Large 2-inch color (176 x 220 pixel) display makes viewing easy.
      • Exceptional voice quality with high-definition voice (HD voice)
      • Built-in full-duplex speakerphone for high-quality hands-free communications.
      • Applications key provides direct access to XML applications such as push-to-talk and Lone Worker.
      • Extended-life batteries deliver a minimum of 13 hours talk time and up to 240 hours standby

      Cisco Unified SIP Phone 3911

      The Cisco Unified SIP Phone 3911 is a cost-effective, entry-level phone that addresses the needs of a lobby, laboratory, manufacturing floor, or hallway. This single-line phone with speakerphone and internal microphone can also fill the communication needs of cubicle, retail, classroom, or manufacturing workers or anyone with low to moderate telephone needs.

      The Cisco Unified SIP Phone 3911 provides:

      • Fixed feature keys that provide one-touch access to redial, transfer, conference, hold, line select, mute, speakerphone, and voicemail access features

      • A display that supports additional capabilities such as caller ID, call history, and phone configuration

      • Choice of IEEE 802.3af Power over Ethernet (PoE) or local power through an optional power adaptor

      Cisco Unified SIP Phone 3905

      Replace your existing analog and digital phone deployments with affordable IP communication endpoints using the Cisco Unified SIP Phone 3905.

      This phone also gives you access to the comprehensive suite of capabilities supported by Cisco Unified Communications Manager.

      The Cisco Unified SIP Phone 3905 includes interactive features such as:

      • Single-line IP phone with support for up to two concurrent calls

      • Graphical 128x32-pixel monochrome display with a two-way navigation button

      • Full duplex speakerphone for flexibility with hands-free communications

      • Fixed keys for common telephony features: hold, redial, transfer, and mute

      • Foldable, single-position display stand to simplify wall-mount deployments

      Video Resolution Support for SIP Phones

      This documentation update resolves CSCuf57901.

      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.

      TCP and UDP Port Usage Guide

      Destination Listener port value for IM and Presence

      In the section titled "Port Usage Information for the IM and Presence Service", the table listing the IM and Presence Service Ports for Presence Engine Requests was updated. The TCP/UDP Destination Listener port value for IM and Presence was updated to port 5080 as follows:

      Table 3 IM and Presence Service Release 9.x Ports - Presence Engine Requests

      From (Sender)

      To (Listener)

      Protocol

      Transport Protocol

      Destination/ Listener

      Source/ Sender

      Remarks

      IM and Presence

      IM and Presence (Presence Engine)

      SIP

      UDP/TCP

      5080

      Ephemeral

      Default SIP UDP/TCP Listener port

      Ports Between Unified CM and LDAP

      This documentation update resolves CSCul08363.

      This guide lists the destination port from Unified Communications Manager to External Directory as Ephemeral.

      Unified Communications Manager to External Directory is 389 LDAP, 636 for secure LDAP, or 3269 for global catalog. External Directory to Unified Communications Manager is Ephermeral.

      The following table shows the correct ports between Unified Communications Manager and LDAP directory.

      Table 4 Ports Between Cisco Unified Communications Manager and LDAP Directory

      From (Sender)

      To (Listener)

      Destination Port

      Purpose

      Unified Communications Manager

      External Directory

      389, 636, 3628, 3629 / TCP

      Lightweight Directory Access Protocol (LDAP) query to external directory (Active Directory, Netscape Directory)

      External Directory

      Unified Communications Manager

      Ephemeral

      User Options Guide

      The Fast Dial User Option is Not Supported

      This documentation update resolves CSCuf57054.

      The "Add Contact" procedure states that you can configure fast dial information while adding a contact. This statement is incorrect as Cisco Unified CM User Options supports speed dials, but not fast dials.

      Upgrade Guide

      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.

      Preupgrade Step to Check Connectivity

      This documentation update resolves CSCue26921.

      The pre-upgrade step to check the connectivity between the IM and Presence Service server and Cisco Unified Communications Manager was added to the Upgrade Guide for Cisco Unified Communications Manager.

      Problem    During an IM and Presence Service upgrade, the IM and Presence Service server generates the following error message, even though the upgrade path and file are valid.

      "The directory was located and searched but no valid options or upgrades were available. Note, a machine cannot be downgraded so option and upgrade files for previous releases were ignored"

      Solution    The upgrade manager checks for connectivity between IM and Presence Service and Cisco Unified Communications Manager to validate the version during the upgrade. If this fails, the IM and Presence Service server generates the error message even though the upgrade path and file are valid. Use a tool, such as the Cisco Unified CM IM and Presence Administration System Troubleshooter, to check that there is connectivity between IM and Presence Service and Cisco Unified Communications Manager before proceeding with the upgrade.

      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.


      Caution


      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.

      XML Developers Guide

      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.

      Serviceability XML API Doc in Error

      This documentation update resolves CSCum01216.

      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.