Release Notes for Cisco Unified Communications Manager, Release 9.0(1)
Documentation Updates
Downloads: This chapterpdf (PDF - 1.68MB) The complete bookPDF (PDF - 2.97MB) | The complete bookePub (ePub - 421.0KB) | The complete bookMobi (Mobi - 654.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.

Convert LDAP Synchronized User to Local User Check Box Field Description Is Missing

The End User configuration window contains a check box that allows you to convert an LDAP synchronized user to a local user. The description for this check box is missing from the Cisco Unified Communications Manager Administration Guide, as well as this troubleshooting information:

When an LDAP synchronized user is converted to a local user within a system enabled for LDAP authentication, after the conversion process completes, users experience sign-in failures from:

  • Cisco Unified CM IM and Presence Administration

  • Cisco Unified IM and Presence Serviceability Administration

  • Cisco Unified Personal Communicator

  • Cisco Jabber

  • Third Party XMPP Clients

  • All externally supported interface that requires user authentication (except PAWS API)

To resolve the sign-in problem, perform one of these actions:

  • Perform a manual synchronization from the System > LDAP > LDAP Directory menu. See "LDAP directory setup" in the Cisco Unified Communications Manager Administration Guide.

  • Resolve the problem during a scheduled synchronisation.

See "LDAP directory setup" in the Cisco Unified Communications Manager Administration Guide.

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.

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.

Default Device Pool May Not Be Chosen After Upgrades to 5.x or Later

This documentation update resolves CSCtw79487.

If you upgrade an existing system to 5.x or later and your system includes new device types, the Default Device Pool may not be selected for the new device types. After the upgrade, you must check to ensure that the Device Pool that you want is assigned.

Device Mobility Calling Search Space is Used When Device CSS is set to None

This documentation update resolves CSCuc79185.

The following note is missing from "Phone Settings" in the Cisco Unified Communications Manager Administration Guide:


Note


When set to <none>, Unified CM uses the device mobility calling search space, which is configured on the device pool.


End User Settings Correction

This documentation update resolves CSCue51184.

In the End User Configuration window, the Primary User Device field content has been removed.

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.


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.

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.


Missing Exceptions for Voicemail Pilot

This documentation update resolves CSCtw44980.

The following information is missing for the Voice Mail Pilot Name field description in "Voice-Mail Pilot Settings" in the Cisco Unified Communications Manager Administration Guide:

Allowed characters are numeric (0-9), plus (+), asterisk (*), and pound (#).

Missing Tip for Naming a Server

This documentation update resolves CSCuc10415.

The following tip is missing from the "Server settings" topic in the Cisco Unified Communications Manager Administration Guide.


Tip


To avoid errors, we recommend that you add a server to the system with a name that has less than 47 characters. Then, update the server name to the target length.


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

Route Class Configuration SIP Information

This documentation update resolves CSCub65671.

If the route pattern points to a SIP trunk supporting G.Clear, then specify Data or Hotline as the Route Class.

You can use non-default route class settings to translate an inbound T1 CAS route class digit into a Cisco Unified Communications Manager route class value (and strip off the digit). You should not need to assign a non-default route class setting to any other inbound calls that use pattern configuration.

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.


Transmit UTF8 for Calling Party Name Field Correction

This documentation update resolves CSCup45037.

The Cisco Unified Communications Manager Administrator Guide specifies that the SIP trunk field Transmit UTF-8 for Calling Party Name uses the user locale setting of the device pool to determine what to send in the Calling Party Name field. However, the device pool does not have a user locale field. It has a network locale field, and both the Common Device Configuration record, and the Phone record itself have user locale fields.

The following is the process that the SIP trunk uses to obtain the user locale:

If the Transmit UTF-8 for Calling Party Name is checked to obtain the locale, the SIP trunk attempts to obtain the locale from the device. If that attempt fails, the SIP trunk attempts to obtain the user locale from the Common Device Configuration, and if that attempt fails, the SIP trunk obtains the user locale that is used for the Enterprise Parameters.

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.

Directory Number Field Description Updated

This documentation update resolves CSCur86259.

The following information is omitted from the "Directory Number Settings" topic in the Cisco Unified Communications Manager Administration Guide and online help:

The Directory Number is a mandatory field.

Bulk Administration Guide

Cannot Disassociate Devices from End Users Using BAT

This documentation update resolves CSCuc30279.

The Bulk Administration Tool (BAT) cannot be used to disassociate devices that are already associated to an end user.

If you manually delete a controlled device from an exported end-user record and then insert the modified user record back in to the Cisco Unified Communications Manager database as a custom CSV data file, the insertion appears successful when you check the job results using Bulk Administration > Job Scheduler. However, the controlled device is still listed on the End User Configuration window in Cisco Unified Communications Manager Administration.

FindAndList Gateway Template Does Not Display the Templates

This documentation update resolves CSCtj43528.

FindAndList Gateway Template does not display templates with less than five characters. To display the list of templates, create a template with more than five characters.

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

Missing Step in Unified CM Hostname Update

This documentation update resolves CSCub59376.

There is a missing step in each of the procedures that describe how to change a server hostname in the Changing the IP Address and Hostname for Cisco Unified Communications Manager document. Immediately after you change the hostname of a Unified CM server and save your changes, the server reboots automatically. Immediately after the server reboots, you must bring up the Admin CLI for the server on which the hostname was changed and run the utils dbreplication dropadmin db command. This step applies to any procedure that involves a hostname change for Cisco Unified Communications Manager.

Command Line Interface Reference Guide

The following CLI commands were added to the Command Line Interface Reference Guide for Cisco Unified Communications Solutions, Release 9.0(1):

  • utils ntp server add

  • utils ntp server delete

To view the Command Line Interface Reference Guide for Cisco Unified Communications Solutions for your release, see the below URL.

CSCum43072 run cuc sysagent task Example Incorrect

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.

CSCuo56537 Enable Disable FIPS for IM and Presence Service

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 Servicee subscriber node cannot access information from the IM and Presence Service database publisher node. For example, a user who is logged into the Cisco Unified Serviceability GUI on a subscriber node will not be able to view services on theIM and Presence Service database publisher node. Users will see the following error message until the sync is complete: Connection to server cannot be established (certificate exception)

CSCup03425- CUCM 9.1 CLI guide has conflicting information for "set network domain"

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

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.


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.

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.


Trace Option for Show Media Streams CLI Command

This documentation update resolves CSCtt41576.

The trace option for the show media streams cli command activates extra trace from the media driver to the system log.


Note


Ignore any kernel messages that display on the console screen when show media streams trace is entered.


Deployment Guide for IM and Presence Service

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

Legacy Clients

When initially configuring your system for Cisco clients, use Cisco Unified CM IM and Presence Administration > Application > Legacy Clients to configure the settings below:

  • Proxy Listener

  • TFTP Servers

  • LDAP Client Attribute Mapping

  • Cisco CallManager Cisco IP Phone (CCMCIP) service


Note


In future releases of Jabber clients, some of these settings may no longer need to be configured.


For information about setting these values, see the Deployment Guide for IM and Presence Service on Cisco Unified Communications Manager, Release 9.0(1): http:/​/​www.cisco.com/​en/​US/​products/​sw/​voicesw/​ps556/​tsd_​products_​support_​configure.html.

Dialed Number Analyzer Guide

Find and List Phones in DNA Using Directory URI

This documentation update resolves CSCuc55921.

Dialed Number Analyzer (DNA) provides a Phones window where you can find and list phones by device name, description, directory number, Directory URI, calling search space device pool, device type, and call pickup group. You can find a phone and choose it as a calling device for the analysis that you want to perform. You can further choose a configured phone line (directory number) and use it as a calling party number.

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

Answer Too Late Timer

This documentation update resolves CSCtr78911.

In Cisco Unified Communications Manager Administration, use the Device > Remote Destination menu path to configure remote destinations.

Answer Too Late Timer

Enter the maximum time in milliseconds that Cisco Unified Communications Manager allows for the mobile phone to answer. If this value is reached, Cisco Unified Communications Manager stops ringing the mobile phone and pulls the call back to the enterprise.

Range: 0 and 10,000 - 300,000 milliseconds

Default: 19,000 milliseconds

If the value is set to zero, the timer is not started.

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

Call Waiting Behavior with MLPP Preemption Correction

This documentation update resolves CSCub10861.

When a Routine precedence call is offered to a destination station that already has active calls that are configured with call waiting, normal call waiting is activated if the existing call count is less than the busy trigger.

When a non-routine precedence call is offered to a destination station that already has an active call that is configured with call waiting, precedence call waiting is activated if the existing call count is less than the busy trigger and any of the following conditions exist:
  • The device supports visual call appearances and has an open appearance.

  • The device supports two non-visual call appearances and has an open appearance, and the precedence of the new call is equal to or lower than the existing call.

  • The device has an open appearance (visual or non-visual) and the device is non-preemptable.

When a non-routine precedence call is offered to a destination station that already has an active call that is configured with call waiting, an existing lower-precedence call is preempted if the existing call count is equal to or greater than the busy trigger.

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

    Early Media Cut-Through and Single Number Reach Missing Information

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

    Early Media cut-through is not supported for Single Number Reach (SNR) calls. SNR follows shared line behavior and does not function as desired with early media cut-through.

    For example, Phone A (DN 1000) calls Phone B (DN 1001) which has an Remote Destination Phone C(DN 1001), sharing line with Phone B . When you enable early media cut-through and place a call to Phone B, both shared lines do not ring, because with early media cut-through enabled, a device may signal a connect, causing the other device to stop ringing.

    To avoid this behavior, do not configure early media cut through on the outbound trunk or gateway for SNR.

    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.

    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.

    Enable Mobile Connect for IP Multimedia Subsystem

    This documentation update resolves CSCtz29138.

    For IP Multimedia Subsystem, ensure that the Mobile Connect feature is enabled in the Remote Destination Configuration window, or by using one of the other methods prescribed for enabling Mobile Connect, before implementing Intelligent Session Control call processing.

    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.


    Expansion Module Field Missing From Certain Device Profiles

    This documentation update resolves CSCuc39511.

    The expansion module field is not listed on the Device Profile Configuration window for Cisco Unified IP Phone models 8961, 9951, and 9971. No manual selection is required. The lines from the Phone Button Template are applied to the physical device no matter which expansion modules these phones use.

    Skip step 9 in the procedure to "Create the device profile for a user" as documented for Cisco Extension Mobility configuration in the Cisco Unified Communications Manager Features and Services Guide.

    Step..9

    If the phone type supports Cisco Unified IP Phone Expansion Modules, Cisco Unified Communications Manager displays expansion module field. At the Module 1 drop-down list box and at the Module 2 drop-down list box, choose the appropriate expansion module.

    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 Missing Information

    The following information is missing from the "Cisco Extension Mobility" chapter.

    The following table lists caveats and workarounds for using Cisco Extension Mobility during a node upgrade.

    Table 2 Cisco Extension Mobility Behavior During Node Upgrade

    Caveat

    Workaround

    When you perform an upgrade on the EM service node, the upgrade process increases the CPU load percentage. The CPU used during upgrade of the EM service node can increase to 80% and higher.

    Caution   

    Some EM logins may fail because of high CPU use threshold during an upgrade.

    • Sign in to another EM node to shift the CPU load from the upgraded node to another node.
    • Create another EM service that goes to another node that you are upgrading.

    When the EM service node finishes upgrade and then reboots, users cannot sign in or sign out using the EM service. However, they can sign in or sign out if they configured another EM service that points to another active node.

    If the phone performs a failover to a node on the old database, the user can still successfully sign in to and sign out of EM. But when the phone performs failback to the newly upgraded node that connects to the new database, the updates that occurred during the failover to the old database node do not appear on the phone until the failover node is successfully upgraded to the new version. In the meantime, the user needs to sign in or sign out of EM against the newly upgraded failback node.

    None.

    After you upgrade the TFTP node, it reboots and goes offline. If you sign in using EM and the EM service is not configured with TFTP and has a separate node, it signs in but does not load the new EM configuration to the phone.

    Create an alternative TFTP that loads the EM configuration from another node onto the phone.

    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.

    iDivert Feature Correction

    The Cisco Unified Communications Features and Services Guide states that the iDivert feature does not work in cases where the redirect signal must traverse a QSIG link. This statement is incorrect. The statement should read that the iDivert feature does not work in cases where the feature has been initiated via CTI and the redirect signal must traverse a QSIG link.

    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.

    MLPP Parameters

    In Cisco Unified Communications Manager Administration, you can use theDevice > Phone menu to configure the following MLPP parameters:

    • MLPP Domain

    • MLPP Preemption

    • MLPP Indication

    If you do not set the MLPP parameters on the Phone Configuration window, the system uses the settings configured in the common device configuration. If the MLPP paramaters are not configured in the common device configuration, then the settings from the enterprise parameters are used. MLPP parameters are not inherited from settings in the device pool.

    No Audio After Pressing Mobility Button

    This documentation update resolves CSCub51519.

    In Unified CM 9.0(1), the Cisco Unified Mobile Communicator must be enabled for a mobile phone on the Mobility Identity Configuration window.

    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.

    Queue Status PLK Supported Phone Models

    This documentation update resolves CSCuc63315.

    Queue status PLK is only supported with the following LCD display phones for both SCCP and SIP protocols:
    • 6921
    • 6941
    • 6945
    • 6961
    • 7911 G
    • 7931 G
    • 7942 G
    • 7945 G
    • 7962 G
    • 7965 G
    • 7975 G
    • 8961
    • 8945
    • 8941
    • 9951
    • 9971

    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.

    Remote Destination Single Number Reach and Enterprise Number Call Reroute

    This documentation update resolves CSCts83374.

    In Cisco Unified Communications Manager Administration, use the Device > Remote Destination menu path to configure remote destinations.

    Single Number Reach

    You can configure all of the Remote Destination Configuration Settings for Single Number Reach.

    Reroute Remote Destination Calls to Enterprise Number

    For the Reroute Remote Destination Calls to Enterprise Number, you can configure:

    • Answer Too Soon Timer

    • Answer Too Late Timer

    For the Reroute Remote Destination Calls to Enterprise Number, you can not configure:

    • Delay Before Ringing Timer

    • Enable Mobile Connect

    • Ring Schedule

    Secure Shell Password Maximum Length

    The maximum length of a secure shell password is 50 characters. It can include any alphanumeric or special characters.

    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.

    Support for Midcall Mobility Features with Cisco Unified Border Element

    This documentation update resolves CSCua75983

    Cisco Unified Mobility supports the Mobile Connect feature without mid-call features over SIP trunks with Cisco Unified Border Element (CUBE). To enable mid-call features, you must also configure an Enterprise Feature Access directory number and check the Send send-receive SDP in mid-call INVITE check box that appears in the SIP Profile Configuration window of the SIP profile that is assigned to the SIP trunk.

    User Control System Parameters Correction

    The Cisco Unified Communications Features and Services Guide states that the value you specify for the User Control Delayed Announcement Timer and User Control Confirmed Answer Indication Timer parameters is in seconds. This statement is incorrect. The value for these parameters is in milliseconds.

    Installing Cisco Unified Communications Manager

    Cisco Unified CM Installation on MCS 7825 H3 and 7828 H3 Server Models

    This documentation update resolves CSCtr49649.

    Note the following revision to step 5 of the Install software procedure in Installing Cisco Unified Communications Manager, Release 9.0(1).

    Step 5

    The system installer performs the following hardware checks to ensure that your system is correctly configured. If the installer makes any changes to your hardware configuration settings, you will get prompted to restart your system. Leave the DVD in the drive during the reboot:

    • First, the installation process checks for the correct drivers, and you may see the following warning:

      No hard drives have been found. You probably need to manually choose device drivers for 
      install to succeed. Would you like to select drivers now?

      To continue the installation, choose Yes.

    • The installation next checks to see whether you have a supported hardware platform. If your server does not meet the exact hardware requirements, the installation process fails with a critical error. If you think this is not correct, capture the error and report it Cisco support.

    • The installation process next verifies RAID configuration and BIOS settings.


      Note


      For MCS 7825 H3 and MCS 7828 H3 Server models, the installation process detects and disables the SATA RAID, if enabled. The System Rebooting Intermediately window appears with the message

      System is going to reboot for SATA RAID to be disabled in BIOS
      Press any key to continue

      This disables the SATA RAID and reboots the system. On reboot, the installation will continue and will activate the Linux SW RAID.



      Note


      If this step repeats, choose Yes again.


    • If the installation program must install a BIOS update, a notification appears telling you that the system must reboot. Press any key to continue with the installation.

    After the hardware checks complete, the Product Deployment Selection window displays.

    Disable ICH10 Onboard SATA Controller on EX/ESXi Servers During Unified CM Installation

    This documentation update resolves CSCtk68384.

    If the server is running VMware EX/ESXi and the motherboard has an ICH10 onboard SATA controller, you must disable the SATA controller in the BIOS. The ICH10 onboard SATA controller is not supported by EX/ESXi. Perform the following steps to disable the SATA controller in the BIOS as a pre-installation task when installing the Cisco Unified Communications Manager.

    1. Boot the server and press F2 when prompted during boot up.

    2. Select Advanced tab.

    3. Select Mass Storage Controllers Configuration.

    4. Set the Onboard SATA Controller to Disabled.

    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.

    Post-Installation Tasks

    Locales

    When you install the Cisco Unified Communications Manager on a server, the locale English_United_States installs automatically; however you can add new locales to the server if required. If you add new locales, add them only after you have installed Cisco Unified Communications Manager on all servers in the cluster, and have set up the database.

    COP Files

    Install COP enabler files for any custom device types that you want to use that do not ship with Cisco Unified Communications Manager. Perform this task only after you have completed the installation for the entire cluster, and set up the database.

    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.

    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

    Online Help

    404 Errors in Unified CM CDR Analysis and Reporting Online Help

    Some GUI menu items return broken links in the CDR Analysis and Reporting online help when you click Help > For this page.

    The following table lists paths to GUI menu items with broken online help links and the workaround to access the online help.

    Table 3 GUI Menu Items in CDR Analysis and Reporting

    GUI path

    Workaround

    • System Reports > QoS > Detail

    • System Reports > QoS > By Call Types

    1. Select Help > Contents and Index.

    2. Navigate to System reports > QoS system reports in the left-hand pane.

    • Device Reports > Gateway > Detail

    • Device Reports > Gateway > Utilization

    1. Select Help > Contents and Index.

    2. Navigate to Device reports > Gateway device reports in the left-hand pane.

    • Device Reports > Route Patterns/Hunt Pilots > Route and Line Group Utilization

    • Device Reports > Route Patterns/Hunt Pilots > Route/Hunt List Utilization

    • Device Reports > Route Patterns/Hunt Pilots > Route Pattern/Hunt Pilot Utilization

    1. Select Help > Contents and Index.

    2. Navigate Device reports > Route pattern and hunt pilot device reports in the left-hand pane.

    • Device Reports > Trunk > Utilization

    1. Select Help > Contents and Index.

    2. Navigate to Device reports > Trunk device reports in the left-hand pane.

    • System > Scheduler > Daily

    1. Select Help > Contents and Index.

    2. Navigate to System > CAR system scheduler in the left-hand pane.

    • System > Database > Configure Automatic Purge

    1. Select Help > Contents and Index.

    2. Navigate to System > CAR system database in the left-hand pane.

    • System > System Parameters > System Preference

    1. Select Help > Contents and Index.

    2. Navigate to System > CAR system parameters in the left-hand pane.

    • Report Config > Rating Engine > Voice Quality

    1. Select Help > Contents and Index.

    2. Navigate to Report configuration > CAR rating engine in the left-hand pane.

    Update Users Documentation Does Not Appear in Context-Sensitive Help

    From the Bulk Administration Tool, when you navigate to Users > Update Users > Query and click Help > This Page, the online help for this GUI menu item does not appear. The following workaround lets you access the documentation for this GUI menu item:

    1. Click Help > Contents.

    2. On the left-hand navigation menu, click Cisco Unified Communications Manager Batch Administration > Users > User Updates > User Update Settings

    Device Name and Description Fields Need to Be Updated

    In the Unified CM Administration menu Device > Trunk, the Device Name and Description fields should read as follows:

    Device Name

    Enter a unique identifier for the trunk. The device name can include up to 50 alphanumeric characters: A-Z, a-z, numbers, hyphens (-) and underscores (_) only.

    Description

    Enter a descriptive name for the trunk. The description can include up to 114 characters in any language, but it cannot include double-quotes ("), percentage sign (%), ampersand (&), back-slash (\), or angle brackets (<>).

    OS Administration Guide

    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.

    Regenerate Certificate

    This documentation update resolves CSCua63006 and CSCth80282.

    You can regenerate certificates from the Cisco Unified Communications Operating System as an operating system security function. For more information about regenerating certificates, see the Cisco Unified Communications Manager Security Guide.


    Caution


    Regenerating a certificate can affect your system operations. Regenerating a certificate overwrites the existing certificate including a third party signed certificate if one was uploaded.



    Note


    Certificate regeneration or upload of a third party signed certificate should be performed during maintenance.


    The following table describes the system security certificates you can regenerate from the Cisco Unified Communications Operating System and the related services that must be restarted. For information about regenerating the TFTP certificate, see the Cisco Unified Communications Manager Security Guide.

    Table 4 Certificate Names and Descriptions

    Name

    Description

    Related Services

    tomcat

    This self-signed root certificate is generated during installation for the HTTPS server.

    tomcat

    ipsec

    This self-signed root certificate is generated during installation for IPsec connections with MGCP and H.323 gateways.

    Cisco Disaster Recovery System (DRS) Local and Cisco DRF Master

    CallManager

    This self-signed root certificate is installed automatically when you install Cisco Unified Communications Manager. This certificate provides server identification, including the server name and the Global Unique Identifier (GUID).

    CallManager and CAPF

    CAPF

    The system copies this root certificate to your server or to all servers in the cluster after you complete the Cisco client configuration.

    CallManager and CAPF

    TVS

    This is a self-signed root certificate.

    TVS

    If you regenerated the certificate for Cisco Certificate Authority Proxy Function (CAPF) or Cisco Unified Communications Manager and a CTL client is configured, rerun the CTL client.

    After you regenerate certificates in the Cisco Unified Communications Operating System, you must perform a system backup so that the latest backup contains the regenerated certificates. If your backup does not contain the regenerated certificates and you perform a system restoration task, you must manually unlock each phone in your system so that the phone can register with Cisco Unified Communications Manager. For information about performing a backup, see the Disaster Recovery System Administration Guide.

    Procedure
      Step 1   Navigate to Security > Certificate Management.

      The Certificate List window displays.

      Step 2   Click Generate New.

      The Generate Certificate dialog box opens.

      Step 3   Choose a certificate name from the Certificate Name list. For details about certificate names, see the Certificate Names and Descriptions table.
      Step 4   Click Generate New.

      If intracluster communication is enabled using EMCC complete the following steps during certificate regeneration.

      Step 5   Navigate to Advanced Features > EMCC> Intercluster Service Profile and deactivate EMCC Service.
      Step 6   Logout all remotely logged in devices from Device > Related Link > Remotely Logged In Device.
      Step 7   Regenerate certificates.
      Step 8   Perform the Bulk Certification operation.
      Step 9   Activate the EMCC Service.

      What to Do Next

      Restart all services that are affected by the regenerated certificate as listed in the Certificate Names and Descriptions table.

      Rerun the CTL client (if configured) after you regenerate the CAPF or CallManager certificates.

      Perform a system backup to capture the newly regenerated certificates. For information about performing a backup, see the Disaster Recovery System Administration Guide.

      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

      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.

      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.

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

      RTMT Cannot Collect OPC Logs Under Default Settings

      This documentation update resolves CSCtw78204.

      If you are using Cisco Unified Real-Time Monitoring Tool (RTMT) to monitor Cisco Unified Contact Center Enterprise, RTMT cannot collect OPC logs under the default settings. This issue arises because the default timeout for RTMT log collection is 60 seconds, but the OPC log collection process takes longer.

      To resolve the issue, open the <RTMT_INSTALLATION_FOLDER_PATH>/conf/rtmt.xml file from the RTMT installation folder and change the value for ReadTimeout to 360. After you make the change, RTMT will be able to collect OPC logs.

      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

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

      Audit Log Severity Levels

      This documentation update resolves CSCua87708.

      The following table displays descriptions for the audit log severity level codes.

      Severity Code

      Description

      0

      Emergency: system is unusable

      1

      Alert: action must be taken immediately

      2

      Critical: critical conditions

      3

      Error: error conditions

      4

      Warning: warning conditions

      5

      Notice: normal but significant condition

      6

      Informational: informational messages

      7

      Debug: debug-level messages

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

      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.

      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.

      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.

      SIP Transparency and Normalization Developers Guide

      Cause Tag Required for convertHIToDiversion() API

      This documentation update resolves CSCub77698.

      If you are implementing the convertHIToDiversion() function with SIP Transparency and Normalization, a Diversion header will only be produced if the Histoy-Info header contains a “cause=” tag.

      System Guide

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

      This documentation update resolves CSCue58676.

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

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

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

      • DSCP for Audio Portion of Video Calls

      • DSCP for TelePresence Calls

      • · DSCP for Audio Portion of TelePresence Calls

      DSCP for ICCP Protocol Links is removed.

      Call Preservation Support for SIP Trunks

      This documentation update resolves CSCuc23992.

      The Call Preservation feature in Cisco Unified Communications Manager supports SIP trunks. Active calls that cross a SIP trunk do not get interrupted when a Cisco Unified Communications Manager node fails, or when communication between a device and its cluster node fails

      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

      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.

      SCCP Device Handles One Call in a Pending State

      This documentation update resolves CSCto78373.

      You can use the Computer Telephony Integration application, known as the CTI application, to control Cisco Unified IP Phones.

      For phones that are running SCCP, outbound dialing supports enbloc (the phone collects all digits before passing them to Cisco Unified Communications Manager for routing) or digit-by-digit collection. If dialing is done digit-by-digit, a CTI dialing call state notification gets sent to the phone when it goes off hook and the first digit is pressed for an outgoing call. For enbloc outbound dialing, the dialing call state notification gets delayed until the phone collects all the digits and sends them to Cisco Unified Communications Manager for routing.

      When an outbound call is pending on an SCCP device and is not yet connected, Cisco Unified Communications Manager does not process call setup requests for that device until the first call is connected. If you are using a CTI application for outbound dialing, Cisco recommends that you configure an interval between outbound calls to ensure that pending calls are connected before new call requests are initiated.

      SIP Redirect by Application Requires a SIP Route Pattern

      This documentation update resolves CSCub17607.

      If the Redirect by Application check box in the SIP Profile Configuration window is checked, Cisco Unified Communications Manager passes the Contact header of the redirection request through its routing engine and applies routing logic to forward the redirection request to the address in the Contact header. If the host portion of the Contact header is not a local Unified CM, a SIP route pattern may be required to map the host portion of the Contact header to an outgoing trunk or Unified CM will not be able to route the call.

      For detailed information on how Unified CM routes SIP requests, see "Routing of SIP Requests in Unified CM" in the Dial Plan chapter of the Cisco Unified Communications System SRND.

      Transcoding G.711 to All Codecs Supported

      This documentation update resolves CSCtb31860.

      The transcoder supports transcoding between G.711 and all codecs, including G.711, when functioning as a transcoder and when providing MTP/TRP functionality.

      Trunk Types

      This documentation update resolves CSCue75498.

      Step 14 of the Set up SIP trunk procedure in the Cisco Unified Communications Manager System Guide states "When you enable Send send-receive SDP in mid-call INVITE for an early offer SIP trunk in tandem mode, Cisco Unified Communications Manager inserts MTP to provide sendrecv SDP when a SIP device sends offer SDP with a=inactive or sendonly or recvonly in audio media line." This statement incorrectly qualifies the situation as occurring in tandem mode only. This situation can occur for all clusters.

      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

      Port Information for UDS

      This documentation update resolves CSCuc77135.

      The TCP and UDP Port Usage for Cisco Unified Communications Manager document does not mention port usage information for Cisco User Data Services. Endpoints can make a TCP connection to Cisco Unified Communications Manager port 8443 for Cisco User Data Services requests.

      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.

      Downtime When Upgrading Publisher Server Until All Subscriber Servers Are Updated

      This documentation update resolves CSCtd69640.

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

      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.

      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.

      XML Developers Guide

      MaxReturnedDevices in Serviceability XML

      This documentation update resolves CSCup71020.

      The Cisco Unified Communications Manager XML Developers Guide, Release 9.0(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.