Release Notes for Cisco Unified Communications Manager, Release 10.0(1)
Documentation Updates
Downloads: This chapterpdf (PDF - 1.38MB) The complete bookPDF (PDF - 2.27MB) | The complete bookePub (ePub - 212.0KB) | The complete bookMobi (Mobi - 370.0KB) | Feedback

Documentation Updates

Contents

Documentation Updates

Administration Guide

Directory Number Line Behavior in Cisco Unified Communications Manager

This documentation update resolves CSCuo74599.

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

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

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

Extension Mobility Now Supports Device Owners

This documentation update resolves CSCun04965.

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

Disable Early Media on 180 Correction

This documentation update resolves CSCup68350.

The "SIP Profile Settings" section in the Administration Guide contains incorrect information about the Disable Early Media on 180 check box. The description states that the setting applies to both the 180 and 183 responses, but the setting applies to only the 180 response.

Hostname and IP Address Field Can Contain a Fully Qualified Domain Name

This documentation update resolves CSCur62680.

The following information is omitted from the Host Name/IP Address field description, listed under the "Server Setup" chapter in the Administration Guide and the online help.

You can also enter a fully qualified domain name (FQDN) in this field—for example, cucmname.example.com.

Note


If Jabber clients are used, we recommend that you use an FQDN instead of a hostname so that the Jabber clients can resolve the Unified Communications Manager domain name.


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.

Incorrect Information about Deleting Route Patterns

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

The following information further explains the context:

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

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

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

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

The following is the corrected information:

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

Incorrect Note about User Locales

This documentation update resolves CSCuq42434.

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


Note


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


Line Group Deletion Correction

This documentation update resolves CSCuq26110.

The following is a correction to Line Group Deletion.

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


Tip


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


Maximum Hunt Timer Restriction

This documentation update resolves CSCuo90637.

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


Caution


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


Missing Information for Allow Multiple Codecs in Answer SDP

This documentation update resolves CSCup79162.

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

Configure Allow multiple codecs in answer SDP for the following:
  • Third-party SIP endpoints that support this capability

  • SIP trunks to third-party call controls servers that uniformly support this capability for all endpoints

Do not configure this capability for SIP intercluster trunks to Cisco SME or other Cisco Unified Communications Manager systems.

Time Is Not Manually Configurable

This information relates to CSCul67741.

The following note appears in the Cisco Unified OS Administration user interface in the Settings > Time menu and the Cisco Unified OS Administration Guide:


Note


Before you can manually configure the server time, you must delete any NTP servers that you have configured.


Because it is mandatory to have at least one NTP server, this note is inaccurate. The following is the correct note:


Note


You cannot configure time manually from the Time window, because you cannot delete all NTP servers and one NTP server is required.

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.

Insufficient Information about Call Control Agent Profile Fields

This documentation update resolves CSCuq11351.

The Call Control Agent Profile chapter in Cisco Unified Communications Manager Administration Guide contains insufficient information about the Call Control Agent Profile configuration fields. The following table contains the detailed information.

The following table describes the Call Control Agent Profile settings.

Table 1 Call Control Agent Profile Settings

Field

Description

Call Control Agent Profile Configuration

Call Control Agent Profile ID

Enter a unique ID for the Call Control Agent Profile. This ID is associated with the Directory Number. It is a mandatory field. The allowed values are alphanumeric (a-zA-Z0-9), period (.), dash (-), and space ( ).

Primary Softswitch ID

Enter the primary softswitch ID (prefix) of the directory number alias servers. It is a mandatory field. The allowed values are alphanumeric (a-zA-Z0-9), period (.), dash (-), and space ( ).

Secondary Softswitch ID

Enter the secondary softswitch ID (suffix) of the directory number alias servers. The allowed values for this field are alphanumeric (a-zA-Z0-9), period (.), dash (-), and space ( ).

Object Class

Enter the object class name for the directory numbers associated with the call control agent profile. It is a mandatory field. The allowed values are alphanumeric (a-zA-Z0-9), period (.), dash (-), and space ( ).

Subscriber Type

Enter the subscriber type of the directory numbers associated with the call control agent profile. The allowed values are alphanumeric (a-zA-Z0-9), period (.), dash (-), space ( ), and at (@).

SIP Alias Suffix

Enter the SIP alias suffix. The E.164 number that you specify for the directory number is appended to this suffix when mapping to the SIP Alias field in the LDAP directory. The allowed values are alphanumeric (a-zA-Z0-9), period (.), dash (-), space ( ), and at (@).

SIP User Name Suffix

Enter the SIP user name suffix. The E.164 number that you specify for the directory number is appended to this suffix when mapping to the SIP User Name field in the LDAP directory. The allowed values are alphanumeric (a-zA-Z0-9), period (.), dash (-), space ( ), and at (@).

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

Bulk Administration Character Length

This documentation update resolves CSCum94975.

The character length for the User Template Name field is incorrect in the Cisco Unified Communications Manager Bulk Administration Guide. The following table shows the correct description.

Field

Description

User Template Name

Enter a unique name, up to 132 alphanumeric characters, for the user template.

Call Detail Records Administration Guide

Call Recording Section of CDR Examples

The Call Recording section of the CDR Examples chapter in the Cisco Unified Communications Manager Call Detail Records Administration Guide contains two call recording scenarios. However, the CDR examples that accompany the scenarios are monitoring CDRs. Following are the 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

Changing IP Address and Hostname

Additional Prerequisite for IP and Hostname Change on IM and Presence Service

Item Added to Pre-Change Task List

This documentation update resolves CSCun73445.

For each cluster where the publisher/subscriber node being changed is an intercluster peer, remove the publisher’s/subscriber’s cluster from the list of intercluster peers.

For example, ClusterA, ClusterB and ClusterC are all intercluster peers. You want to change the hostname on the publisher node of ClusterA. You must first remove the ClusterA publisher node from the list of intercluster peers on both ClusterB and ClusterC.

CLI Reference Guide

Enable or Disable FIPS for IM and Presence Service

This documentation update resolves CSCuo56537.


Warning


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

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

set network domain Conflicting Information

This documentation update resolves CSCup03425.

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

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

Usage Guidelines:

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


Caution


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


Show perf query counter Command Output

This documentation update resolves CSCuo70238.

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

Note


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


Features and Services Guide

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.

Call Queuing Update

The Performance and Scalability topic in the Call Queuing chapter of the Cisco Unified Communications Manager Features and Services Guide contains a bullet that says that call queuing is not supported with broadcast algorithm hunt lists. This bullet point is incorrect and should be removed.

Gateway Recording Support

The System Requirements topic in the Monitoring and Recording chapter of the Cisco Unified Communications Manager Features and Services Guide contains a list of supported gateways for recording, including the ISR-G2 Gateways (29XX, 39XX) running release 15.3(3)M. It should say that release 15.3(3)M or later are supported.

Jabber Devices Count as Registered Devices

This documentation update resolves CSCur73944.

The following information is omitted from the Limitations section of the "Cisco Unified Mobility" chapter in the Features and Services Guide.

When initially configured, Jabber devices count as registered devices. These devices increase the count of registered devices in a node, set by the Maximum Number of Registered Devices service parameter.

MGCP FXS Ports Do Not Require a License

This documentation update resolves CSCum47807.

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


Note


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

Music On Hold and Native Call Queuing Behavior

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

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

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.

SAML SSO Authentication LDAP Attribute for User ID Setting

This documentation update resolves CSCuq44567.

The following note is missing from the "SAML Single Sign-On" chapter in Feature and Services Guide for Cisco Unified Communications Manager.


Note


Cisco Unified Communications Manager currently supports only sAMAccountName option as the LDAP attribute for user ID settings.

Installing Cisco Unified Communications Manager

Installation Warnings

This information applies to CSCug48896.

The following information applies when you install an IM and Presence Service cluster:


Note


Do not add a node in the Cisco Unified Communications Manager server list during the installation process.



Note


Complete the installation of the IM and Presence Service database publisher node and confirm that services are running before you begin to install IM and Presence Service subscriber nodes.


JTAPI Developers Guide

MeetMe: Unsupported JTAPI Feature

This documentation update resolves CSCum39340.

Applications that use JTAPI, including Unified Contact Center Express (UCCX), are unable to dial MeetMe conference numbers to begin a MeetMe conference or join an already started MeetMe conference. MeetMe is not a feature supported by JTAPI and therefor any application that uses JTAPI for call control is unable to perform actions on MeetMe conferences. For Unified Contact Center Express (UCCX), this prevents MeetMe conferences DN from being the destination of Place Call script steps.

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

OS Administration Guide

Time Is Not Manually Configurable

This information relates to CSCul67741.

The following note appears in the Cisco Unified OS Administration user interface in the Settings > Time menu and the Cisco Unified OS Administration Guide:


Note


Before you can manually configure the server time, you must delete any NTP servers that you have configured.


Because it is mandatory to have at least one NTP server, this note is inaccurate. The following is the correct note:


Note


You cannot configure time manually from the Time window, because you cannot delete all NTP servers and one NTP server is required.

Real-Time Monitoring Tool Guide

Analyze Call Path Tool does not Work with Non-English Language

This documentation update resolves CSCuq28511.

The following note is omitted from the "Cisco Unified Analysis Management" chapter in the Cisco Unified Real-Time Monitoring Tool Administration Guide.


Caution


The Analyze Call Path Tool might not work correctly if your computer is set to a language other than English.


Incorrect Default Value for LogPartitionLowWaterMarkExceeded Alert

This documentation update resolves CSCuq39087.

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

Table 2 Default Configuration for the LogPartitionLowWaterMarkExceeded RTMT Alert

Value

Default Configuration

Threshold

Trigger alert when following condition met:

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

Security Guide

BAT User Template Accepts Only Hexadecimal Characters

This documentation update resolves CSCul78860.

The table in the "End user digest credential settings" subsection of the "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.

IP Phone SSL VPN not Supported on Third Party Firewalls

This information applies to CSCun49156.

For IP Phones that use SSL VPN, third-party firewalls are not supported.

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.

Replace ASA Certificate on AnyConnect VPN Phone


Note


When you upload an updated certificate with the same Common Name (CN) to Phone-VPN-trust, you overwrite the old certificate. Upload the new certificate to the subscriber instead of the publisher. Phone-VPN-trust does not replicate to other servers but this process will still add the new certificate to the database for the Phone VPN Gateway configuration. Therefore, the old certificate will not be overwritten.


Procedure
    Step 1   Install the new ASA certificate on the ASA, but do not activate it.
    Step 2   Add the new ASA certificate to the trust store (Phone-VPN-trust).
    Step 3   Add the new ASA certificate to VPN Gateway Configuration. Select and add the new ASA certificate to "VPN certificates in this location."
    Step 4   Gather information about which VPN phones are registering and which VPN phones are not registering.
    Step 5   Apply the new configuration file to the phones from the Common Phone Profile Configuration window that is used for VPN phones or from the Device Pool Configuration window that used for VPN phones.
    Step 6   Reset the VPN phones.
    Step 7   Ensure that the phone received the updated configuration file or verify that the phone has the new ASA certificate hash information in its configuration file.

    For more information, see https:/​/​supportforums.cisco.com/​document/​33891/​ip-phone-ssl-vpn-asa-using-anyconnect.

    Step 8   Activate the new ASA certificate on the ASA.
    Step 9   Verify that the previously registered VPN phones are registering back to Unified Communications Manager.
    Step 10   Repeat Steps 4, 5, 6, and 8.
    Step 11   Remove the old ASA certificate from the VPN Gateway Configuration.

    Secure and Nonsecure Indication Tone

    This documentation update resolves CSCuq04604.

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

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

    CSCup54818 Support for CA Certificates in Mixed Mode

    If you run your system in mixed mode, some endpoints may not accept CA certificates with a key size of 4096 or longer. To use CA certificates in mixed mode, choose one of the following options:

    • use certificates with a certificate key size less than 4096

    • use self-signed certificates

    Serviceability Guide

    AXL Web Service Requirement for ICSA HA

    This documentation update resolves CSCup00956.

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

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

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

    Cisco CAR DB Service

    This documentation update resolves CSCup98304.

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

    Cisco CAR DB Service

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

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

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

    Cisco IP Phone Service Removed from CM Services

    This documentation update resolves CSCur03499.

    The Service groups and CM Services sections in Cisco Unified Serviceability Administration Guide mention Cisco IP Phone Service. This service has been removed from CM Services as IP Phone services is offered through the User Data Services (UDS) component starting Cisco Unified Communications Manager, Release 10.0(1).

    System Guide

    LDAP Directory Support

    The "Configure LDAP Directory" topic in the Cisco Unified Communications Manager System Guide, Release 10.0(1) contains a list of supported LDAP directories. However, this list should include Microsoft Active Directory 2012 and Microsoft Lightweight Directory Services 2012 R1/R2.

    The complete list of supported directories is as follows:
    • Microsoft Active Directory 2003 R1/R2
    • Microsoft Active Directory Application Mode (ADAM) 2003 R1/R2
    • Microsoft Active Directory 2008 R1/R2
    • Microsoft Lightweight Directory Services 2008 R1/R2
    • Microsoft Active Directory 2012 R1/R2
    • Microsoft Lightweight Directory Services 2012 R1/R2
    • Sun One 6.x
    • Sun Directory Services 7.0
    • Oracle Directory Services Enterprise Edition 11gR1 (v11.1.1.5.0)
    • OpenLDAP 2.3.39 & 2.4.x

    Upgrade Guide

    Disable or Postpone LDAP Synchronization During an Upgrade

    This document update resolves CSCuq07331.

    The following information is omitted from the "Preupgrade Tasks" chapter in the Upgrade Guide for

    It is recommended that you disable or postpone the LDAP synchronization on Unified Communications Manager during an upgrade. If the synchronization is scheduled in for a time period which falls after the Unified Communications Manager upgrade and before the IM and Presence Service upgrade, then the result can negatively affect the IM and Presence Service if user changes occurred in this timeframe.

    Unified CM 10.0 Upgrade Process Correction

    This documentation update resolves CSCup31306.

    In the Change Virtual Machine Configuration Specifications procedure, Step 6 ("Shut down the virtual machine") should be performed before Step 3 ("Change the configuration of the virtual machine").

    InterCluster Peer-User and Admin-CUMA Application User Roles Deprecated

    This document update resolves CSCur08490.

    The application user group roles InterCluster Peer-User and Admin-CUMA are deprecated from release 10.0(1). Any application users with these roles configured in releases 8.x or 9.x have the roles removed during an upgrade to any 10.x release. After the upgrade the administrator must configure appropriate roles for these users.


    Note


    For intercluster to function correctly, the AXL user defined on the IM and Presence Service user interface (Presence > Inter-Clustering ) must have a Standard AXL API Access role associated with it on the Cisco Unified Communications Manager application user page.