Release Notes for Cisco Unified Communications Manager, Release 9.0(1)
Documentation Updates
Downloads: This chapterpdf (PDF - 1.54MB) The complete bookPDF (PDF - 3.01MB) | The complete bookePub (ePub - 340.0KB) | The complete bookMobi (Mobi - 654.0KB) | Feedback

Documentation Updates

Contents

Documentation Updates

This section contains information about errors, omissions, and changes for both the Cisco Unified Communications Manager and IM and Presence documentation and online help.

Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at

http:/​/​www.cisco.com/​en/​US/​docs/​general/​whatsnew/​whatsnew.html

Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop by using a reader application. Be aware that the RSS feeds are a free service, and Cisco currently supports RSS version 2.0.

General Documentation Updates

Document Restructure

In order to mirror the integration of Unified CM and the IM and Presence Service in release 9.0, the following documents have been restructured to include content from both documentation sets. The content has been divided into parts; the first part of each document pertains to Unified CM and the second part contains IM and Presence Service content.

  • Installing Cisco Unified Communications Manager, Release 9.0(1)
  • Upgrade Guide for Cisco Unified Communications Manager, Release 9.0(1)
  • Cisco Unified Serviceability Administration Guide, Release 9.0(1)
  • Cisco Unified Real-Time Monitoring Tool Administration Guide, Release 9.0(1)
  • Disaster Recovery System Administration Guide, Release 9.0(1)
  • Cisco Unified Communications Operating System Administration Guide, Release 9.0(1)
  • Cisco Unified Communications Manager TCP and UDP Port Usage Guide, Release 9.0(1)

The following documents have been merged in release 9.0. The restructuring of these documents differs from the preceding list of documents in that there are no parts; content from the related IM and Presence documents has been seamlessly merged with the existing Unified CM document.

  • Release Notes for Cisco Unified Communications Manager, Release 9.0(1)
  • Cisco Unified Communications Manager Documentation Guide, Release 9.0(1)
  • Command Line Interface Reference Guide for Cisco Unified Communications Solutions, Release 9.0(1)
  • Cisco Unified Reporting Administration Guide, Release 9.0(1)

Rebranding Impacts

Cisco Unified Presence as a product has been rebranded in this release to the IM and Presence Service. As such, all document, interface, and Online Help content now refers to this product as IM and Presence.


Note


In addition, references to User Group have been changed to Access Control Group throughout the documentation in this release:


The following table identifies the various GUI changes:

Table 1 GUI Rebranding

Pre-9.0

9.0 and later

Cisco Unified Presence Administration

Cisco Unified CM IM and Presence Administration

Cisco Unified Serviceability

Cisco Unified IM and Presence Serviceability

Cisco Unified OS Administration

Cisco Unified IM and Presence OS Administration

Cisco Unified Reporting

Cisco Unified IM and Presence Reporting

Disaster Recovery System

IM and Presence Disaster Recovery System

Cisco Unified Presence User Options

Cisco Unified CM IM and Presence User Options

User Profile Configuration Changes

The following user profile configuration options have been moved from IM and Presence to Unified CM:

  • Voicemail Profile
  • Voicemail Server
  • Application Listener
  • Application Profile
  • Audio Profile
  • Conferencing Profile
  • Conferencing Server
  • CTI Gateway Host
  • CTI Gateway Profile
  • LDAP Profile
  • LDAP Server
  • Mailstore
  • Licensing

IPPM Removal From IM and Presence

IP Phone Messenger content has been removed from the IM and Presence documentation set.

Cisco Intercompany Media Engine TCP and UDP Port Usage

Installing Cisco Unified Communications Manager

Add a New Node to an Existing Cluster

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

External NTP Server Requirements

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

Cisco Unified Communications Manager Administration Guide

The following sections and tables in the Cisco Unified Communications Manager Administration Guide were updated to describe the Call Queuing feature:

  • Announcement Configuration Settings section
  • Announcements in the Find and List Announcements Window section
  • Adding a Feature Announcement section
  • Uploading a Customized Announcement section
  • Hunt Pilot Configuration Settings table
  • Announcement Configuration Settings table

The following updates were made to describe the AS-SIP feature:

  • New AS-SIP chapter was added
  • End User Configuration Settings table was updated
  • SIP Profile Configuration Settings table was updated

The License Usage Report Configuration section was added to describe the UCM Licensing feature.

The EMCC and security mode for different cluster versions section was updated.

The following sections were added to describe consolidated administrative features, including the integration of user management configuration from IM and Presence:

  • UC Service setup
  • Service Profile setup
  • Universal Device Templates
  • Feature Group Templates
  • Quick User and Phone Addition
The following content was added to this document after the online help was released:
  • Hold Reversion Notification Interval interaction between SCCP and SIP phones (CSCsy57492)

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.

CSCuc10415 Tip for Naming a Server

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


Tip


To avoid errors, Cisco recommends 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.


CSCuc79185 Device Mobility Calling Search Space is Used When Device CSS is <none>

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.


CSCtw44980 Missing Exceptions for Voice-Mail Pilot

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

CSCud34740 Application User AXL Password Must Not Contain Special Characters

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 create an AXL password for an application user.


CSCue58074 Relabeling of Link Loss Type Field on the Region Configuration Page

On the System > Region configuration page, the Link Loss Type field has been re-labeled as the Audio Codec Preference List field.

CSCug28060 Connected Line ID Presentation Value Sets to Allowed

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.

CSCug52147 Relabel of Use Personal Preferences Field

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.

CSCug58742 Common Phone Profile Settings Secure Shell Information

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

CSCug63874 Call Stats Field Removed for SIP Profile Configuration

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

CSCue51184 End User Settings Need Correction

In the End user settings page, Primary User Device field content has been removed.

CSCuh62299 Service Name Cannot Be Localized If Customized Service URL Is Used

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.


CSCtw44786 Added Description for Option For Voice Mail Usage In Add Hunt List Procedure

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

Cisco Unified Communications Manager Bulk Administration Guide

The Cisco Unified Communications Manager Bulk Administration Guide was updated as follows to accommodate the integration of user management configuration from IM and Presence:

  • User Templates section was updated
  • User Settings table was updated
  • Fields and tasks were added for updating users using query

CSCui06050 Model Is Not a Valid Device Field When Generating Phone Reports

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

CSCug41922 Missing Note in Insert Phone Topic

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.


Cisco Unified Communications Manager Call Detail Records Administration Guide

CSCud20005 Missing CDR Field Descriptions

The following field descriptions are missing 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.

CSCul25436 Change Order of HuntPilotDN

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

The documented order for HuntPilotDN and HuntPilotPartition is interchanged to HuntPilotPartition and HuntPilotDN

CSCum60891 Missing CDR Field Descriptions for IMS Application Server

The following CDR field descriptions in the table below for IMS Application Server were missing.

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

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

Cisco Unified Communications Manager Documentation Guide

The following document listing was removed from the web version of the Cisco Unified Communications Manager Documentation Guide:

  • Installing Cisco Security Agent for Cisco Unified Communications Manager

Note


Removed document listings in the web version will still appear in the print edition of the Documentation Guide.


Cisco Unified Communications Manager Features and Services Guide

The Cisco Unified Communications Manager Features and Services Guide was updated as follows:

  • IM and Presence chapter was added to describe the IM and Presence Service and provide the steps to successfully configure this service.
  • Music on Hold chapter was updated to include information about the Call Queuing feature.
  • Licensing chapter was updated to reflect changes in licensing due to the Enterprise License Manager (ELM)
  • MLPP section was updated to include information about the AS-SIP feature.

The following features also impacted this document:

  • FCC over SIP trunks without Smart Client
  • HCS Anonymous Call Rejection ISC Trunks
  • HCS Supplementary Services for VoLTE IMS Mobile Device
  • Confirmed Answer and DVO VM Detection
  • NextGen mobile clients with QoE
The following content was added to this document after the online help was released:
  • Hold Reversion Notification Interval interaction between SCCP and SIP phones (CSCsy57492)

Format Changes

The structure of introductory topics were modified to remove duplication of hyperlinked subsection topic lists. Modifications were also made to correct the format of some tables and tasks, and misapplied cross-references to external documents were removed. These and other minor structural changes to improve the format are noticeable between the Online Help and the pdf and HTML versions of the document.

Incorrect Information on iDivert Feature

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.

Incorrect Information on User Control System Parameters

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.

Missing Information on Cisco Extension Mobility

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.

Missing Information About Early Media Cut-Through and Single Number Reach

The following information is missing 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.

Missing Information About Call Queuing Limitations

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

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

Missing Information About Call Mobility Limitations

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.

CSCue33154 SIP Phones Support CMC/FAC Tones

The following bullet in the interactions and restrictions section of the Client matter codes and forced authorization codes chapter was 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.

CSCue85258 Remove Play Continuously From MOH Settings Table

Removed play continuously from the Music On Hold audio source configuration settings table.

CSCue98877 Call Queuing Shared-Line Scenario Description

In the Call queuing operation considerations section, the paragraph describing shared-line deployments is modified 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.

CSCug36365 Call Park Display Timer Restriction

The interaction between the value that is entered for the Call Park Reversion Timer and the Cisco Call Park Display Timer is 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.

CSCue92900 Cisco Unified IP Phones That Support Call Pickup

Updated the table listing the Cisco Unified IP 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.

CSCue33160 Advance Features > EMCC > EMCC Remote Cluster Not In Cisco Unified Communications Manager

In the chapter Extension Mobility Cross cluster, step 20 of Configure EMCC, the following menu name is modified from Advance Features > EMCC > EMCC Remote Cluster to Advance Features > Cluster View.

CSCuh56102 Changes to Extension Mobility Equivalency

The following changes are made to 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

CSCui24499 Mobility Voicemail Policy Requires Enable Enterprise Feature Access to Be TRUE

The following note is missing 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.


CSCuj75419 Number of Allowed Hunt Pilots for One Call Queue

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.

CSCum47807 UCT Guide Should Mention That MGCP FXS Ports Do Not Consume Any Licenses

The following note is missing from Licensing- User and Device section.


Note


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

CSCup04321 Call Pickup group visual notification does not support localization

The following limitation is applicable to Call Pickup:

Localization support is not available for call pickup group visual notification, as it uses ASCII for alerting name.

CSCup44177- Configuring OpenAM Section

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.

    Cisco Unified Communications Manager 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 (<>).

    Cisco Unified Communications Manager System Guide

    The following content was added to the Cisco Unified Communications Manager System Guide after the online help was released:
    • Hold Reversion Notification Interval interaction between SCCP and SIP phones (CSCsy57492)

    The Cisco Unified Communications Manager System Guide references "user groups"; these references should be "access control groups."

    SMDI Voice Mail Integration

    This update applies to the SMDI Voice Mail Integration section in the Cisco Unified Communications Manager System Guide.

    To connect the EIA/TIA-232 cable to Cisco Unified Communications Manager, use a ATEN USB Serial Converter UC-232A adapter.

    For SMDI integration, the FXS port must be configured as a POTS line. If you are not able to configure it in the Route Group, follow the below configuration steps:

    1. Configure the Line Group with the FXS port. See "Line group setup" in Cisco Unified Communications Manager System Guide for more detailed information.
    2. Configure the Hunt List (With VoiceMail Usage selected). See "Hunt list setup" in Cisco Unified Communications Manager System Guide for more detailed information.
    3. Configure the Hunt Pilot with the voicemail number. See "Hunt pilot setup" in Cisco Unified Communications Manager System Guide for more detailed information.

    CSCue75498 Cisco Unified Communications Manager Trunk Types

    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

    Cisco Unified Communications Manager supports the imageattr line in the 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 800Kb/s and the imageattr[640 x 480] line in the SDP exists, then VGA is used.
    • If the session level bandwidth is greater than 800Kb/s 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 800Kb/s 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 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 w360p resolution was introduced at phone load 9.2(1).


    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.

    CSCuj60918 Updates to Section Phones That Support International Escape Character +

    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

    CSCuo13148 ATA 187 Not Compatible until Cisco Unified Communications Manager 8.0.3

    This update applies to the "Cisco ATA 187" chapter.

    The Cisco ATA 187 Analog Telephone Adaptor is compatible with Cisco Unified Communications Manager 8.0.3 and higher. For Cisco Unified Communications Manager 8.0.3, you must install the device pack cmterm-devicepack8.0.3.23038-1.cop.sgn for Cisco ATA 187 to be supported.

    Cisco Unified Communications Manager Security Guide

    CUMA Acronym

    In the Cisco Unified Communications Manager Security Guide, the expansion of the acronym CUMA is incorrect. The correct expansion is Cisco Unified Mobility Advantage.

    CSCud57169 CTL File Size Limit Should Be 64 Kilobytes

    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.

    CSCuf49157 SSL and TLS Support for HTTPS Web Communications

    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.

    CSCuf34403 Updated Note in Section Roll Back Cluster to a Pre-8.0 Release

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

    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.

    CSCuj71412 Secure Call Monitoring and Recording Update

    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.

    CSCul78860 BAT User Template Only Accepts Hexadecimal Characters for Digest Credentials

    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.

    CSCuo01831 Encryption protocols specifications missing for phone models

    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

    Cisco Unified Real-Time Monitoring Tool Administration Guide

    The following were added or updated to the Cisco Unified Real-Time Monitoring Tool Administration Guide were either added or updated to describe the :

    • Session Trace Enhancement feature:
      • Open from local disk section was added
      • Perform session trace section was updated
      • Trace calls section was updated
      • Monitor real-time data section was updated
    • Enhanced Location Call Admission Control:
      • Cisco LBM Service counters
      • Cisco Locations LBM counters
      • Cisco Locations RSVP counters
      • LocationOutOfResource alert

      Note


      The Enhanced Location Call Admission Control counters and alerts information does not appear in the Cisco Unified Communication Manager Release 9.0 online help but will be included in the Release 9.5 version of the online help.


    CSCui25367 Alert Removal

    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

    CSCul36067 Missing Content for Mailbox Sync Counters

    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.

    Cisco Unified Communications Operation System Administration Guide

    CSCul66341 ICSA Service Needs Restart After Ipsec Cert Is Regenerated

    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.

    Cisco Unified Serviceability Administration Guide

    The Cisco Unified Serviceability Administration Guide was updated as follows:

    • Locations chapter was added to describe the Enhanced Locations CAC feature
    • Configuring the Cisco syslog agent enterprise parameters procedure and Alarm configuration settings were updated for the Multisyslog Destination feature

    CSCua87708 Audit Log Severity Levels

    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

    CSCuf16874 Cisco Unified Communications Manager Administration User Options Logging

    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.

    CSCub37263 Audit Log Configuration Settings

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

    CSCup00956 Cisco AXL Web Service Requirement for ICSA HA

    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 Unified CM User Options Guide

    CSCuf57054 Fast Dial User Option Not Supported

    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.

    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.


    Deployment Guide for IM and Presence Service on Cisco Unified Communications Manager

    The Deployment Guide for IM and Presence Service on Cisco Unified Communications Manager was updated as follows:

    CSCug87105 Exceeding Maximum Contact List Settings During Contact List Import Is Supported

    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.

    Disaster Recovery System Administration Guide for Cisco Unified Communications Manager

    The Disaster Recovery System Administration Guide for Cisco Unified Communications Manager was updated as follows:

    CSCui75485 System Backup File Encryption

    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.

    CSCul28047 Updated Caution to Include DNS and Domain Name Prior To Restore

    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.

    Enterprise License Manager User Guide

    The Enterprise License Manager User Guide is a new document that describes how to use the Enterprise License Manager. Enterprise License Manager provides simplified, enterprise-wide management of user-based licensing, including license fulfillment. Enterprise License Manager handles licensing fulfillment, supports allocation and reconciliation of licenses across supported products, and provides enterprise-level reporting of usage and entitlement.

    Interdomain Federation for IM and Presence Service on Cisco Unified Communications Manager

    The Interdomain Federation for IM and Presence Service on Cisco Unified Communications Manager guide was updated as follows:

    The procedure titled Turn on email for XMPP federation was updated to specify that when you turn on IM and Presence Service to use the email address for XMPP federation, IM and Presence changes the JID of the local user to the email address of the contact.

    The procedure titled Configure static routes on IM and Presence for OCS servers was updated. You are no longer required to add static routes on IM and Presence Service for the following OCS entities to configure IM and Presence Service to use TCP when exchanging IM and Presence with a federated Microsoft OCS domain:
    • Each OCS Enterprise Edition front-end server or Standard Edition server FQDN
    • Each OCS pool FQDN (Enterprise Edition only)

    CSCui01368 Use TLS for Static Routes Between Microsoft Lync Servers and IM and Presence Service

    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.

    CSCui45519 FIPS Not a Requirement for Federated Connections with LYNC 2010 Servers

    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.

    Partitioned Intradomain Federation for IM and Presence Service on Cisco Unified Communications Manager

    The Partitioned Intradomain Federation for IM and Presence Service on Cisco Unified Communications Manager guide was updated as follows:

    CSCuh55035 MatchUri Set to IM and Presence Service Domain

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

    CSCui01368 Use TLS for Static Routes Between Microsoft Lync Servers and IM and Presence Service

    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.

    CSCui45519 FIPS Not a Requirement for Federated Connections with LYNC 2010 Servers

    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.

    PAWS Management Administration Guide

    The PAWS Management Administration Guide is a new document that describes an administrative platform for enterprise customers who want to perform and control the upgrades of their servers in a unified interface. PAWS-M allows you to:

    • configure your server inventory for the system
    • schedule and monitor upgrades of one or more servers across one or more clusters
    • schedule system restarts for one or more servers
    • switch versions between the active and inactive versions, for one or more servers

    TCP and UDP Port Usage Guide for Cisco Unified Communications Manager

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

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

    From (Sender)

    To (Listener)

    Protocol

    Transport Protocol

    Destination/ Listener

    Source/ Sender

    Remarks

    IM and Presence

    IM and Presence (Presence Engine)

    SIP

    UDP/TCP

    5080

    Ephemeral

    Default SIP UDP/TCP Listener port

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

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

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

    Table 5 Ports Between Cisco Unified Communications Manager and LDAP Directory

    From (Sender)

    To (Listener)

    Destination Port

    Purpose

    Unified Communications Manager

    External Directory

    389, 636, 3628, 3629 / TCP

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

    External Directory

    Unified Communications Manager

    Ephemeral

    Upgrade Guide for Cisco Unified Communications Manager

    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.

    Changing the IP Address and Hostname for Cisco Unified Communications Manager

    Change Hostname Using 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

    Cisco Unified Communications Manager Managed Service Guide

    The Cisco Unified Communications Manager Managed Service Guide was updated with the following sections:

    Preconfigured CallManager Alarm Notifications

    The following CallManager alarm notifications are deprecated from Release 8.x:

    • LowCallManagerHeartbeatRate
    • LowTFTPServerHeartbeatRate

    The following CallManager alarm notifications were added:

    Table 6 Configuration for the CARSchedulerJobFailed Alert

    Value

    Default Configuration

    Enable Alert

    Selected

    Severity

    Error

    Enable/Disable this alert on the following servers

    Enabled on listed servers

    Threshold

    Trigger alert when following condition met:

    CARSchedulerJobFailed event generated.

    Duration

    Trigger alert immediately

    Frequency

    Trigger alert on every poll

    Schedule

    24 hours daily

    Enable E-mail

    Selected

    Trigger Alert Action

    Default

    Table 7 Configuration for the CARIDSEngineCritical Alert

    Value

    Default Configuration

    Enable Alert

    Selected

    Severity

    Critical

    Enable/Disable this alert on the following servers

    Enabled on listed servers

    Threshold

    Trigger alert when following condition met:

    CARIDSEngineCritical event generated.

    Duration

    Trigger alert immediately

    Frequency

    Trigger alert on every poll

    Schedule

    24 hours daily

    Enable E-mail

    Selected

    Trigger Alert Action

    Default

    Table 8 Configuration for the CARIDSEngineFailure Alert

    Value

    Default Configuration

    Enable Alert

    Selected

    Severity

    Error

    Enable/Disable this alert on the following servers

    Enabled on listed servers

    Threshold

    Trigger alert when following condition met:

    CARIDSEngineFailure event generated.

    Duration

    Trigger alert immediately

    Frequency

    Trigger alert on every poll

    Schedule

    24 hours daily

    Enable E-mail

    Selected

    Trigger Alert Action

    Default

    Table 9 Configuration for the CallAttemptBlockedByPolicy Alert

    Value

    Default Configuration

    Enable Alert

    Selected

    Severity

    Warning

    Enable/Disable this alert on the following servers

    Enabled on listed servers

    Threshold

    Trigger alert when following condition met:

    CallAttemptBlockedByPolicy event(s) generated.

    Duration

    Trigger alert immediately

    Frequency

    Trigger up to 3 alert every 30 minutes

    Schedule

    24 hours daily

    Enable E-mail

    Selected

    Trigger Alert Action

    Default

    Table 10 Configuration for the EMCCFailedInLocalCluster Alert

    Value

    Default Configuration

    Enable Alert

    Selected

    Severity

    Error

    Enable/Disable this alert on the following servers

    Enabled on listed servers

    Threshold

    Trigger alert when following condition met:

    EMCCFailedInLocalCluster event(s) generated.

    Duration

    Trigger alert immediately

    Frequency

    Trigger up to 3 alert every 30 minutes

    Schedule

    24 hours daily

    Enable E-mail

    Selected

    Trigger Alert Action

    Default

    Table 11 Configuration for the EMCCFailedInRemoteCluster Alert

    Value

    Default Configuration

    Enable Alert

    Selected

    Severity

    Warning

    Enable/Disable this alert on the following servers

    Enabled on listed servers

    Threshold

    Trigger alert when following condition met:

    EMCCFailedInRemoteCluster event(s) generated.

    Duration

    Trigger alert immediately

    Frequency

    Trigger up to 3 alert every 30 minutes

    Schedule

    24 hours daily

    Enable E-mail

    Selected

    Trigger Alert Action

    Default

    Table 12 Configuration for the UserInputFailure Alert

    Value

    Default Configuration

    Enable Alert

    Selected

    Severity

    Warning

    Enable/Disable this alert on the following servers

    Enabled on listed servers

    Threshold

    Trigger alert when following condition met:

    UserInputFailure event(s) generated.

    Duration

    Trigger alert immediately

    Frequency

    Trigger up to 3 alert every 30 minutes

    Schedule

    24 hours daily

    Enable E-mail

    Selected

    Trigger Alert Action

    Default

    Table 13 Configuration for the CiscoElmNotConnected Alert

    Value

    Default Configuration

    Enable Alert

    Selected

    Severity

    Warning

    Enable/Disable this alert on the following servers

    Enabled on listed servers

    Threshold

    Trigger alert when following condition met:

    CiscoElmNotConnected event generated.

    Duration

    Trigger alert immediately

    Frequency

    Trigger alert on every poll

    Schedule

    24 hours daily

    Enable E-mail

    Selected

    Trigger Alert Action

    Default

    Table 14 Configuration for the CiscoNoProvisionTimeout Alert

    Value

    Default Configuration

    Enable Alert

    Selected

    Severity

    Error

    Enable/Disable this alert on the following servers

    Enabled on listed servers

    Threshold

    Trigger alert when following condition met:

    CiscoNoProvisionTimeout event generated.

    Duration

    Trigger alert immediately

    Frequency

    Trigger alert on every poll

    Schedule

    24 hours daily

    Enable E-mail

    Selected

    Trigger Alert Action

    Default

    Table 15 Configuration for the CiscoGraceTimeLeft Alert

    Value

    Default Configuration

    Enable Alert

    Selected

    Severity

    Informational

    Enable/Disable this alert on the following servers

    Enabled on listed servers

    Threshold

    Trigger alert when following condition met:

    CiscoGraceTimeLeft event generated.

    Duration

    Trigger alert immediately

    Frequency

    Trigger alert on every poll

    Schedule

    24 hours daily

    Enable E-mail

    Selected

    Trigger Alert Action

    Default

    Table 16 Configuration for the CiscoSystemInOverage Alert

    Value

    Default Configuration

    Enable Alert

    Selected

    Severity

    Warning

    Enable/Disable this alert on the following servers

    Enabled on listed servers

    Threshold

    Trigger alert when following condition met:

    CiscoSystemInOverage event generated.

    Duration

    Trigger alert immediately

    Frequency

    Trigger alert on every poll

    Schedule

    24 hours daily

    Enable E-mail

    Selected

    Trigger Alert Action

    Default

    Table 17 Configuration for the CiscoSystemSecurityMismatch Alert

    Value

    Default Configuration

    Enable Alert

    Selected

    Severity

    Warning

    Enable/Disable this alert on the following servers

    Enabled on listed servers

    Threshold

    Trigger alert when following condition met:

    CiscoSystemSecurityMismatch event generated.

    Duration

    Trigger alert immediately

    Frequency

    Trigger alert on every poll

    Schedule

    24 hours daily

    Enable E-mail

    Selected

    Trigger Alert Action

    Default

    Table 18 Configuration for the CiscoSystemInDemo Alert

    Value

    Default Configuration

    Enable Alert

    Selected

    Severity

    Warning

    Enable/Disable this alert on the following servers

    Enabled on listed servers

    Threshold

    Trigger alert when following condition met:

    CiscoSystemInDemo event generated.

    Duration

    Trigger alert immediately

    Frequency

    Trigger alert on every poll

    Schedule

    24 hours daily

    Enable E-mail

    Selected

    Trigger Alert Action

    Default

    Table 19 Configuration for the RTMTSessionsExceedsThreshold Alert

    Value

    Default Configuration

    Enable Alert

    Selected

    Severity

    Alert

    Enable/Disable this alert on the following servers

    Enabled on listed servers

    Threshold

    Trigger alert when following condition met:

    When number of ast session is more than 250.

    Duration

    Trigger alert immediately

    Frequency

    Trigger alert on every poll

    Schedule

    24 hours daily

    Enable E-mail

    Selected

    Trigger Alert Action

    Default

    Table 20 Configuration for the LocationOutOfResource Alert

    Value

    Default Configuration

    Enable Alert

    Selected

    Severity

    Warning

    Enable/Disable this alert on the following servers

    Enabled on listed servers

    Threshold

    Trigger alert when following condition met:

    LocationOutOfResource event generated.

    Duration

    Trigger alert immediately

    Frequency

    Trigger alert on every poll

    Schedule

    24 hours daily

    Enable E-mail

    Selected

    Trigger Alert Action

    Default

    Table 21 Default Configuration for the DBReplicationTableOutOfSync Alert

    Value

    Default Configuration

    Enable Alert

    Selected

    Severity

    Critical

    Enable/Disable this alert on the following servers

    Enabled on listed servers

    Threshold

    Trigger alert when following condition met:

    IDSReplicationFailure event with alarm number 888 generated.

    Duration

    Trigger alert immediately

    Frequency

    Trigger up to 1 alert within 60 minutes

    Schedule

    24 hours daily

    Enable E-mail

    Selected

    Trigger Alert Action

    Default