Updates to Cisco Unified Communications Manager 8.0(x) Documentation

Table Of Contents

Updates to Cisco Unified Communications Manager 8.0(x) Documentation

Documentation Updates

Cisco Unified Communications Manager "?" Help

Cisco Unified Communications Manager Administration

Enabling AAR for Hunt Pilots

Circular Algorithm Description Is Incorrect

Administrator Can Set User Credential Policy to Expire Without Making a Global Policy Change

Calling Party Transformation CSS of the Roaming Device Pool

Codec Consideration During Monitoring or Recording

Max Hops Value Range Is Incorrect

Supported Call States

Video Is Not Supported With Intercom

IP Phones That Work With Mobile Connect and Mobile Voice Access

Updates to the Configuration Checklist for Cisco Extension Mobility

Interaction of Single Number Reach and Privacy

User Hold and Network Hold MOH Audio Source ID Cannot Be Defined Under Device Pool

Route Patterns that Require FAC or CMC Causes Calls to Fail

Configuring the CTIManager (Primary) IP Address Service Parameter

Mobility SIP Extensions Content Does Not Apply

Secure Extension Mobility

Cisco Unified Serviceability

Installing and Launching RTMT

Authentication Type Column Description

Disaster Recovery

DRS Does Not Restore Across Different Hostnames, IP Addresses and Deployment Types

CDR Analysis and Reporting Administration

Automatic Database Purge Configuration Step Removed

The 2M or HWM Limit

New Dashboard Exists in CAR

Obtaining Documentation and Submitting a Service Request

Updates to Cisco Unified Communications Manager 8.0(x) Documentation

---

Updated March 14, 2011

This document contains information pertinent toCisco Unified Communications Manager Release 8.0(x) documentation.

Documentation Updates

The Updates to Cisco Unified Communications Manager 8.0(x) Documentation document provides information about documentation omissions, errors, or updates that are not included in the documentation that supports the Unified CM 8.0(x) release train.

•Cisco Unified Communications Manager "?" Help

•Cisco Unified Communications Manager Administration

•Cisco Unified Serviceability

•Disaster Recovery

•CDR Analysis and Reporting Administration

Cisco Unified Communications Manager "?" Help

From the Service Parameters Configuration window [System > Service Parameters > Cisco CallManager (Active)], after you click Advanced, the Help that displays when you click "?" omits this information:

The CTI Use Wildcard Pattern as calledPartyDN service parameter applies to the following CTI information fields: OriginalCalledParty, and LastRedirectingParty.

Cisco Unified Communications Manager Administration

This section contains updates for the Cisco Unified Communications Manager Administration Guide, Cisco Unified Communications Manager Features and Services Guide, and the Cisco Unified Communications Manager System Guide.

Cisco Unified Communications Manager Administration Guide

•Enabling AAR for Hunt Pilots

•Circular Algorithm Description Is Incorrect

•Administrator Can Set User Credential Policy to Expire Without Making a Global Policy Change

Cisco Unified Communications Manager Features and Services Guide

•Calling Party Transformation CSS of the Roaming Device Pool

•Codec Consideration During Monitoring or Recording

•Max Hops Value Range Is Incorrect

•Supported Call States

•Video Is Not Supported With Intercom

•IP Phones That Work With Mobile Connect and Mobile Voice Access

•Updates to the Configuration Checklist for Cisco Extension Mobility

•Interaction of Single Number Reach and Privacy

•User Hold and Network Hold MOH Audio Source ID Cannot Be Defined Under Device Pool

•Route Patterns that Require FAC or CMC Causes Calls to Fail

•Configuring the CTIManager (Primary) IP Address Service Parameter

•Mobility SIP Extensions Content Does Not Apply

•Secure Extension Mobility

Enabling AAR for Hunt Pilots

The AAR Group field in the Hunt Pilot Configuration table in the "Hunt Pilot Configuration" chapter of the Cisco Unified Communications Manager Administration Guide incorrectly includes this note:

You can enable AAR for this hunt pilot only if all members of the line group are in the same location.

That is incorrect. You can configure hunt pilots pointing to hunt lists that have line group members in different locations.

Circular Algorithm Description Is Incorrect

The Line Group Configuration Settings table in the "Line Group Configuration" chapter of the Cisco Unified Communications Manager Administration Guide contains this description of the Circular Algorithm:

Circular-If you choose this distribution algorithm, Cisco Unified Communications Manager distributes a call to idle or available members starting from the (n+1)th member of a route group, where the nth member is the member to which Cisco Unified Communications Manager most recently extended a call. If the nth member is the last member of a route group, Cisco Unified Communications Manager distributes a call starting from the top of the route group.

The description should say:

Circular-If you choose this distribution algorithm, Cisco Unified Communications Manager distributes a call to idle or available members starting from the (n+1)th member of a route group, where the nth member is the next sequential member in the list who is either idle or busy but not "down". If the nth member is the last member of a route group, Cisco Unified Communications Manager distributes a call starting from the top of the route group.

Administrator Can Set User Credential Policy to Expire Without Making a Global Policy Change

The Credential Settings and Fields section of the "End User Configuration" chapter in the Cisco Unified Communications Manager Administration Guide incorrectly includes the following information:

For example, if the policy has the Never Expires check box checked, you cannot uncheck and save the Does Not Expire check box in the user Credential Configuration window. You can, however, set a different credential expiration for the user, including Does Not Expire, if the Never Expires policy setting is not checked; the user setting overrides the policy setting.

And, again, regarding the Does Not Expire checkbox:

You cannot uncheck this check box if the policy setting specifies Never Expires.

For releases above 6.1(3), this is not true. An administrator can set a user credential policy to expire without making a global policy change.

Calling Party Transformation CSS of the Roaming Device Pool

The Interactions, Device Mobility section of the Calling Party Normalization chapter in the Cisco Unified Communications Manager Features and Services Guide omits the following information:

The Calling Party Transformation CSS of the roaming device pool overrides the device level configuration of the phone roaming within same DMG, even when the Use Device Pool Calling Party Transformation CSS check box in the phone configuration window remains unchecked.

Codec Consideration During Monitoring or Recording

The Interactions and Restrictions section of the "Monitoring and Recording" chapter of the Cisco Unified Communications Manager Features and Services Guide does not include the following information.

The codec of the call-leg originating from the IP phone that is being monitored or recorded must remain the same throughout the call.

Max Hops Value Range Is Incorrect

The Music On Hold Server Configuration Settings table in the "Music On Hold" chapter of the Cisco Unified Communications Manager Features and Services Guide contains incorrect information.

The Max Hops value range in the document specifies 1 - 15.

The correct value range is 1 - 127.

Supported Call States

The "Quality Report Tool" chapter of the the Cisco Unified Communications Manager Features and Services Guide mentions four supported call states: Connected, On Hook, Connected Conference and Connected Transfer.

Only two states are supported: Connected and On Hook

Video Is Not Supported With Intercom

The Interaction and Restrictions section of the "Intercom" chapter in the Cisco Unified Communications Manager Features and Services Guide does not mention that video is not supported with Intercom.

IP Phones That Work With Mobile Connect and Mobile Voice Access

The System Requirements section of the "Cisco Unified Mobility" chapter of the Cisco Unified Communications Manager Features and Services Guide includes this information:

Mobile Connect works with Cisco Unified IP Phones 7906, 7911, 7941/61, 7962/42, 7970/71, 7975 that are running SIP or SCCP.

Replace that sentence with the following information:

To see which IP phones work with Mobile Connect and Mobile Voice Access, see the applicable Cisco Unifed IP Phone Administration Guide and Cisco Unified IP Phone User Guide.

Updates to the Configuration Checklist for Cisco Extension Mobility

The information below comprises updates to the Configuration Checklist for Cisco Extension Mobility table of the "Cisco Extension Mobility" chapter of the Cisco Unified Communications Manager Features and Services Guide.

Step 5 omits the following information:

To subscribe the device profile to Cisco Extension Mobility, on the Device Profile Configuration Window, from the related links drop-down list (in the upper right corner of the window), choose "Subscribe/Unsubscribe Services" and click Go.

---

Note Subscribe the directory number and the device profile the same Extension Mobility service.

---

Step 2 updates:

The second bullet specifies:

•Select values for Service Category and Service Type.

The second bullet should specify:

•Select values for Service Category and Service Type.

–For Service Category select "XML Service".

–For Service Type, select "Standard IP Phone Service".

Interaction of Single Number Reach and Privacy

The Privacy section of the Remote Destination Profile Configuration Settings table in the "Cisco Unified Mobility" chapter of the Cisco Unified Communications Manager Features and Services Guide omits the following information:

---

Note You cannot transfer a call from a cell phone to a desk phone if the RDP Privacy is On, and the "Enforce Privacy Setting on Held Calls" service parameter is set to True.

---

User Hold and Network Hold MOH Audio Source ID Cannot Be Defined Under Device Pool

The Music On Hold Definitions section of the "Music On Hold" chapter in the Cisco Unified Communications Manager Features and Services Guide in correctly states:

If no level four nor level three audio source IDs are selected, the system selects audio source IDs that are defined in level two, which is DevicePool-based.

As of Cisco Unified Communications Manager 6.x, that should read:

If no level four nor level three audio source IDs are selected, the system selects audio source IDs that are defined in level two, which is Common Device Configuration-based

Route Patterns that Require FAC or CMC Causes Calls to Fail

The Interactions and Restrictions section of the "Client Matter Codes and Forced Authorization Codes" chapter of the Cisco Unified Communications Manager Features and Services Guide omits the following information:

•Because no method exists to play the FAC or CMC tone over a trunk, calls that originate from a SIP trunk, H323, or MGCP gateway fail if they encounter a route pattern that requires FAC or CMC.

Configuring the CTIManager (Primary) IP Address Service Parameter

The "Cisco Unified Communications Manager Assistant With Proxy Line Support" and the "Cisco Unified Communications Manager Assistant With Proxy Line Support" chapters of the Cisco Unified Communications Manager Features and Services Guide omit the following information:

To avoid potential high CPU usage, enter the address of the local CTIManager server where the IPMA process is running when you configure the Cisco IP Manager Assistant CTIManager (Primary) IP Address service parameter.

Mobility SIP Extensions Content Does Not Apply

In the online help that is provided with Release 8.0(1) of Cisco Unified Communications Manager Administration, the following chapters of the Cisco Unified Communications Manager Features and Services Guide contain information about Mobility SIP Extensions:

•Cisco Unified Mobility

•Cisco Unified Mobility Advantage and Cisco Unified Mobile Communicator Integration

The information about Mobility SIP Extensions does not apply to Release 8.0(1) of Cisco Unified Communications Manager.

The website versions of these chapters on http://www.cisco.com/en/US/products/ps7273/prod_maintenance_guides_list.html do not erroneously contain the information about Mobility SIP Extensions.

Secure Extension Mobility

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

The Extension Mobility HTTPS Support feature ensures that when communications are exchanged between a Cisco Unified IP Phone service and other applications, that the communications use the HTTPS protocol to ensure that the communications are secure. Users must log into the Cisco Unified CM applications by providing their authentication information. Their credentials are encrypted after the communication protocol changes to HTTPS.

When a visiting Extension Mobility (EM) application fails to locate a user's identification in the local database, the following occurs:

1. Cisco Extension Mobility Cross Cluster (EMCC) sends a request to the local EM service to determine the home cluster of that user (the cluster which owns the user's identification, and which can handle the EM login).

2. The visiting EM service sends a user identification message over HTTPS to all the remote clusters added in the local database.

3. The visiting EM service then parses the response received from the home cluster to get the list of device profiles associated with that user.

–All further communication between the visiting EM service and home EM service takes place over HTTPS.

–Similarly, visiting logout requests are also sent from the home EM service to the visiting EM service over HTTPS.

The Extension Mobility HTTPS Support feature is supported on the following IP phones (SIP):

•Cisco Unified IP Phone 8961

•Cisco Unified IP Phone 9951

•Cisco Unified IP Phone 9971

---

Note Configure Cisco Extension Mobility on Cisco Unified IP Phones before configuring EMCC.

---

Cisco Unified Serviceability

This section contains updates for the Cisco Unified Serviceability Administration Guide, Cisco Unified Real-Time Monitoring Tool Administration Guide, Cisco Unified Communications Manager Call Detail Records Administration Guide, and CDR Analysis and Reporting Administration Guide.

•Installing and Launching RTMT

•Authentication Type Column Description

Installing and Launching RTMT

The Installing RTMT section of the "Installing and Configuring Cisco Unified Real-Time Monitoring Tool" chapter of the Cisco Unified Real-Time Monitoring Tool Administration Guide omits the following information:

•When you launch RTMT, log into the same product type from which you downloaded the RTMT client application. If you log into a different product type, RTMT will not launch/work properly.

•RTMT requires a miniumu of 300 MB of disk space to run on a Windows / Linux OS platform.

Authentication Type Column Description

In the "Monitoring Predefined Cisco Unified Communications Manager Objects" chapter of the Cisco Unified Real-Time Monitoring Tool Administration Guide, the description for the Authentication Type column is missing in Table 5-6, Data from SAF Forwarder Report.

Authentication Type - Indicates that Cisco Unified Communications Manager used digest authentication to connect to the SAF forwarder.

Disaster Recovery

This section contains updates for the Disaster Recovery System Administration Guide.

•DRS Does Not Restore Across Different Hostnames, IP Addresses and Deployment Types

DRS Does Not Restore Across Different Hostnames, IP Addresses and Deployment Types

The What is the Disaster Recovery System, the Restoring a Node or Cluster to a Last Known Good Configuration (No Rebuild), the Restoring the First Node only (Rebuilding the Publisher Alone) and the Restoring Subsequent Cluster nodes (With or Without Rebuild) sections of the Disaster Recovery System Administration Guide omit the following caution.

---

Caution When you restore your data, the hostname, server IP address, and the deployment type must be the same as it was during the backup. DRS does not restore across different hostnames, IP addresses and deployment types.

---

CDR Analysis and Reporting Administration

This section contains updates for the Cisco Unified Communications Manager Call Detail Records Administration Guide.

•Automatic Database Purge Configuration Step Removed

•The 2M or HWM Limit

•New Dashboard Exists in CAR

Automatic Database Purge Configuration Step Removed

In the Configuring Automatic Database Purge section of the "Configuring the CAR System Database" chapter in the Cisco Unified Communications Manager Call Detail Records Administration Guide, step 4 mentions the Min Age of Call Detail Records field. Because that field no longer exists, that step is no longer applicable.

The 2M or HWM Limit

The following information is missing from the Configuring Automatic Database Purge section of the "Configuring the CAR System Database" chapter in the Cisco Unified Communications Manager Call Detail Records Administration Guide:

When the 2M or HWM limit is breached:

1. CAR deletes the database partitions one by one, starting from the oldest partition.

2. CAR stops purging under one of the following conditions:

–When the record count falls below the 2M or HWM limit.

–When only two days data exists in the billing tables.

In cases where a large number of CDRs exist in the billing tables, and the deletion of the partitions does not bring the record count below the 2M or HWM limit, CAR holds at least two days data in the database.

When the record count in the database reaches the 2M or HWM limit:

1. CAR loader stops processing new records.

2. CAR starts purging the records from the oldest partition until the record count reaches 2M or HWM limit.

If the record count does not fall below the 2M or HWM limit after the records get deleted, CAR holds at least two days records and stops the CAR loader. Also, CAR sends an e-mail notification to the CAR administrator to proceed with a manual purge.

New Dashboard Exists in CAR

The following information is missing from the Logging On to CAR section of the "Configuring the CDR Analysis and Reporting Tool" chapter in the Cisco Unified Communications Manager Call Detail Records Administration Guide.

A new dashboard that displays warning messages and notices exists in Cisco Unified Communications Manager CDR Analysis and Reporting.

Warning Messages

When you log in to CAR, warning messages regarding the following scenarios display on the new dashboard:

•If nodes exist on which CallManager service is activated, but the CDR Enabled parameter specifies disabled, a list of those nodes displays. CDRs do not get generated on the listed nodes.

•If the Call Diagnostics Enabled cluster wide parameter specifies disabled, that information displays If this parameter specifies disabled, QoS information does not get generated on calls.

•If the CAR Scheduler Service or the Cisco Repository Manager Service are stopped on the publisher server, that status displays.

•If either the2M limit or HWM get breached, the breach status displays.

•The status of CDR loader displays.

–If the loader is disabled, the message specifies that the loader is disabled.

–If the loader is enabled, the last load status of the CDR loader displays. If the last load status specifies "failed", this information dislays and the customer gets advised to check the CAR scheduler logs.

•If any of the Tbl_System_Preferences table columns does not contain expected values, the exceptions and a Restore Defaults button display. You can click the Restore Defaults button to populate the Tbl_System_Preferences table with default values required for the smooth functioning of CAR loader and reports.

Notices

When appropriate, notices regarding the following display on the dashboard:

•If the CDR Log Calls with Zero Duration flag is activiated, that information displays indicating that a large number of CDRs of zero duration may get generated. In this situation, billing tables may get filled quickly and cause the 2M or HWM limit to be breached.

•Loader schedule displays.

•If the CDR Load Only option is selected in the CDR Load window, a notice displays indicating that CMRs do not get loaded into the CAR database.

•If the mail parameters remain unconfigured, the notice includes that information and provides the path for configuring the mail parameters.

•If the Mail ID of the CAR Administrator remains unconfigured, a notice displays.

•The following information regarding billing tables displays:

–Number of records present in Tbl_Billing_Data

–Number of records present in Tbl_Billing_Error

–Maximum and minimum date of Tbl_Billing_Data and Tbl_Billing_Error tables

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.

---

CCDE, CCENT, CCSI, Cisco Eos, Cisco Explorer, Cisco HealthPresence, Cisco IronPort, the Cisco logo, Cisco Nurse Connect, Cisco Pulse, Cisco SensorBase, Cisco StackPower, Cisco StadiumVision, Cisco TelePresence, Cisco TrustSec, Cisco Unified Computing System, Cisco WebEx, DCE, Flip Channels, Flip for Good, Flip Mino, Flipshare (Design), Flip Ultra, Flip Video, Flip Video (Design), Instant Broadband, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn, Cisco Capital, Cisco Capital (Design), Cisco:Financed (Stylized), Cisco Store, Flip Gift Card, and One Million Acts of Green are service marks; and Access Registrar, Aironet, AllTouch, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Lumin, Cisco Nexus, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, Continuum, EtherFast, EtherSwitch, Event Center, Explorer, Follow Me Browsing, GainMaker, iLYNX, IOS, iPhone, IronPort, the IronPort logo, Laser Link, LightStream, Linksys, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, PCNow, PIX, PowerKEY, PowerPanels, PowerTV, PowerTV (Design), PowerVu, Prisma, ProConnect, ROSA, SenderBase, SMARTnet, Spectrum Expert, StackWise, WebEx, and the WebEx logo are registered trademarks of Cisco and/or its affiliates in the United States and certain other countries.

All other trademarks mentioned in this document or website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1002R)