Release Notes for Cisco Unified Communications Manager, Release 10.0(1)
Documentation Updates
Downloads: This chapterpdf (PDF - 1.23MB) The complete bookPDF (PDF - 2.23MB) | The complete bookePub (ePub - 188.0KB) | The complete bookMobi (Mobi - 327.0KB) | Feedback

Documentation Updates

Contents

Documentation Updates

Administration Guide

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.

Call Detail Records Administration Guide

Call Recording Section of CDR Examples Chapter

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

Command Line Interface Guide for Cisco Unified Communications Solutions

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.

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


Cisco Unified Serviceability Administration Guide

CSCup00956 Cisco AXL Web Service Requirement for ICSA HA

Following installation, Cisco AXL Web Service is enabled by default on all cluster nodes. Cisco recommends that you always leave the service activated on the IM and Presence database publisher node. This ensures that you are able to configure products that are dependent on AXL. 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. If this service is not enabled on both nodes presence and IM capabilities will be lost in failover scenarios.

Cisco CAR DB Service

This documentation update resolves CSCup98304.

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

Cisco CAR DB Service

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

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

Cisco SOAP-CallRecord Service

This documentation update resolves CSCup98302.

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

Cisco SOAP-CallRecord Service

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

SOAP-Diagnostic Portal Database Service

This documentation update resolves CSCuq22399.

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

SOAP-Diagnostic Portal Database Service

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

Cisco Unified Communications Manager Security Guide

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

CLI Reference Guide

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.


Installing Cisco Unified Communications Manager

CSCug48896 Installation Warnings

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.

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.


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.