Updates to Cisco Unified Communications Manager 8.0(x) Documentation

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.

Incorrect Description for Destination Number

This documentation update resolves CSCux74230.

The Remote Destination Configuration Settings field description in the Cisco Unified CM Administration

Online Help incorrectly states that you can “Enter the telephone number for the destination”. The correct

statement is “Enter the PSTN telephone number for the destination”.

Directory Number Field Description Updated

This documentation update resolves CSCuy28500.

The following note is omitted from the “Directory Number Settings” topic in the online help and “User Device

Profile Fields Descriptions in BAT Spreadsheet” topic in the Cisco Unified Communications Manager Bulk

Administration Guide:

Note The “Disable ” or “Flash only” setting options apply only for the handset. The led light on the phone button line will still flash.

Command Line Interface

This section contains updates for the Command Line Interface Reference Guide for Cisco Unifed Communications Solutions.

• Domain Name Changes

Domain Name Changes

Two commands, utils import config and s et network domain got updated with the following note:

Note If the new configuration has a different domain name than the original configuration you may have to manually regenerate certificates.

To ensure that you do not have to manually regenerate certificates, use a starting config or virtual machine template that has DNS disabled and then import a config with DNS parameters. Starting with a config without DNS and then importing a config with DNS parameters enables DNS and you will not need to manually regenerate certificates.

show perf query counter Command Output

This documentation update resolves CSCuo70238.

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

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

Installation, Upgrade, and Migration

This section contains updates for the installation, upgrade and migration documentation.

• Error Messages When Inserting or Removing a USB Drive
• Upgrading Server Hardware When Upgrading to Cisco Unified Communications Manager Release 8.0(3)
• Replacing the Publisher Node

Error Messages When Inserting or Removing a USB Drive

When you insert or remove a USB drive, you might see error messages on the console similar to “sdb: assuming drive cache: write through”. You can safely ignore these messages.

Upgrading Server Hardware When Upgrading to Cisco Unified Communications Manager Release 8.0(3)

The following sections contain information about upgrading server hardware When Upgrading to Cisco Unified Communications Manager Release 8.0(3):

• Memory Recommendations for Upgrading to Cisco Unified Communications Manager Release 8.5.1
• Upgrading Hard Drives When Upgrading to Cisco Unified Communications Manager Release 8.0(3)
• Replacing the Publisher Node

Memory Recommendations for Upgrading to Cisco Unified Communications Manager Release 8.5.1

It is strongly recommended that you run Cisco Unified Communications Manager Release 8.0(3) only on servers with at least 4 GB of memory.

Upgrading Hard Drives When Upgrading to Cisco Unified Communications Manager Release 8.0(3)

Follow this procedure to replace 72 GB hard drives with 146 GB hard drives when you upgrade to Cisco Unified Communications Manager Release 8.0(3):

Step 1 Reduce used disk space by following these steps:

a. Enter the CLI command show status.

If the active partition is 97% full or higher, seriously consider replacing the 72 GB drives with 146 GB drives. Use Real Time Monitoring Tool to monitor disk space usage.

b. If you are running Cisco Unified Communications Manager release 6.x or higher, reduce used disk space by performing these steps:

– Enter the CLI command utils diagnose module disk_files to identify files that you can delete.

– To delete files that you identified, use a Remote Account.

– Enter the CLI command show status to see the new disk space usage on the active partition.

Step 2 Back up the server using Disaster Recovery System.

Step 3 If you are running Cisco Unified Communications Manager release 5.x, upgrade the server to a 7.x release. If the upgrade fails, switch back to release 5.x and report the issue to Cisco Technical Support.

Step 4 Upgrade the server to release 8.0(3).

Step 5 If the upgrade to release 8.0(3) fails due to disk space shortage in /common, as reported by Real Time Monitoring Tool or in the upgrade log file (look for phrases with the word “space” in them, such as “Not enough space on partition to proceed” or “No space left on device”), perform the recommended workaround in “Workaround for /common: Adjust logging” section, then go to Step 4.

a. If the server originally was running Cisco Unified Communications Manager release 5.x, perform a fresh installation of the same 5.x release, then restore the data using Disaster Recovery System, then go to Step b .

b. If the server was originally not running Cisco Unified Communications Manager release 6.x or higher and the switchover to release 8.0(3) occurred, then clean up disk space using the procedure in Step 1, then switch back to the previous release.

c. Order 146 GB hard drives.

d. When the new hard drives are ready to be installed, perform these steps:

– Perform a backup of the existing Cisco Unified Communications Manager release using Disaster Recovery System.

– Install the new hard drives

– Perform a fresh installation of the existing Cisco Unified Communications Manager release.

– Restore data to the server using Disaster Recovery System.

– Go to Step 3.

Step 6 If the upgrade to release 8.0(3) fails for other reasons, contact Cisco Technical Support.

Step 7 If the upgrade to release 8.0(3) succeeds, be sure to run Real Time Monitoring Tool and monitor disk space usage, particularly if the active partition found in Step 1 was already over 97% disk usage.

Workaround for /common: Adjust logging

To change one of the values below, click the right mouse button on the attribute and select Set Alert/Properties. Once in the dialog box, click Next to open the dialog box for modifying the threshold values.

Before the upgrade:

Step 1 Launch Real Time Monitoring Tool.

Step 2 Select Alert Central, then perform the following tasks:

a. Select LogPartitionHighWaterMarkExceeded, note its value and change its threshold value to 60%.

b. Select LogPartitionLowWaterMarkExceeded, note its value and change its threshold value to 50%.

Polling occurs every 5 minutes, so wait for 5-10 minutes, then verify that the required disk space is available. If you want to free up more disk space in the common partition, change LogPartitionHighWaterMarkExceeded and LogPartitionLowWaterMarkExceeded thread values to lower values (for example, 30% and 20%) again.

After the upgrade finishes, change the threshold fields back their original values. The defaults are 95% for high water mark and 90% for low water mark.

Replacing the Publisher Node

This documentation contains an update to the Replacing the Publisher Node section of the document, Replacing a Single Server or Cluster for Cisco Unified Communications Manager 8.0(2).

Step 9 in the Replacing the Publisher Node Process Overview, should say to reboot all nodes in the cluster, starting with the subscriber nodes. After the subscriber nodes have finished rebooting, reboot the publisher node.

Currently, the documentation just says to reboot all cluster nodes. However, in order for the database replication process to work properly, the publisher node must not be rebooted until after all subscriber nodes have been rebooted.

Domain Name Change for Cisco Unified Communications Manager

This documentation update resolves CSCuw76028.

The following information is omitted from the “ Domain Name and Node Name Changes” chapter in the

Changing IP Address and Hostname for Cisco Unified Communications Manager and IM and Presence

Service Guide.

Update Domain Name for Cisco Unified Communications Manager

You can use the Command Line Interface (CLI) to change the domain name for Cisco Unified Communications

Manager. Update the DNS domain name on all applicable nodes using the CLI. The CLI command makes

the required domain name change on the node and triggers an automatic reboot for each node.

Before You Begin

• Perform all pre-change tasks and the applicable system health checks.
• Ensure to enable the DNS before changing the domain name.
• If the server table has an existing hostname entry, first change the hostname entry of the domain name.

Step 1 Log in to Command Line Interface.

Step 2 Enter run set network domain <new_domain_name>

Step 3 Click Yes to reboot the system.

Step 4 Enter the command show network eth0 to check if the new domain name is updated after the reboot.

Step 5 Repeat this procedure for all cluster nodes.

What to Do Next

For more information, see the “ Post-Change Tasks and Verification” chapter in the Changing IP Address and Hostname for Cisco Unified Communications Manager and IM and Presence Service guide.

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

• Correction in Software Conference Bridge Maximum Audio Streams
• Correction in Software Conference Bridge Maximum Audio Streams
• Incorrect Information in Trunk Configuration Setting for SIP Trunks
• Directory Lookup Dial Rule Configuration Settings Updates
• LDAP Configuration Restriction
• Enabling AAR for Hunt Pilots
• Circular Algorithm Description Is Incorrect
• Administrator Can Set User Credential Policy to Expire Without Making a Global Policy Change
• E & M Port Configuration Settings
• Removed field Call Stats from SIP Profile configuration
• Incorrect Information about Deleting Route Patterns
• Tip for Adding a New Server
• Incorrect Note about User Locales

Cisco Unified Communications Manager System Guide

• MDCX Sendonly Message Not Sent to MGCP Gateway
• DTMF Suppressed when G.Clear is Advertised

Cisco Unified Communications Manager Features and Services Guide

• Setting the Service Parameters for Cisco Unified Communications Manager Assistant
• Japanese Language and Unicode Font
• Setting the Service Parameters for Call Park
• Call Park Range
• 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
• Block Offnet to Offnet Transfer
• Call Control Discovery Limitation

Correction in Software Conference Bridge Maximum Audio Streams

This documentation update resolves CSCuu44805.

The maximum audio streams per software conference bridge is incorrectly listed as 128 in the

“Software Conference Devices” section of the Cisco Unified Communications Manager Administration Guide.The correct value is 256.

Hub_None Information

The “Location Configuration” chapter of the Cisco Unified Communications Manager Administration Guide omits the following information:

The location that is configured in a device pool takes precedence over the location configured in the device when the location in the device is set to Hub_None. If the device location is set to any other user-defined location, standard rules apply and the device parameter takes priority.

Incorrect Information in Trunk Configuration Setting for SIP Trunks

The Trunk Configuration Settings for SIP Trunks section of the “Trunk Configuration” chapter of the Cisco Unified Communications Manager Administration Guide contains incorrect information.

The Destination Address and the Destination Address IPv6 descriptions state that those addresses can comprise a hostname. That is incorrect. The destination address and the destination address IPv6 can be either a fully qualified domain name (FQDN) or a DNS SRV record only.

Directory Lookup Dial Rule Configuration Settings Updates

The Directory Lookup Dial Rule Configuration Settings section of the “Call Routing Configuration” chapter of the Cisco Unified Communications Manager Administration Guide requires the following update.

The Total Digits to be Removed cell should include this information:

Enter the number of digits that you want Cisco Unified Communications Manager to remove from directory numbers that apply to this dial rule. For example, if you enter 3, Cisco Unified Communications Manager removes 408 from directory numbers that include 4085556666.

Valid values for this field range from 1 to 100. The total digits to be removed cannot be more than the number of digits of the directory numbers that apply to this directory lookup dial rule.

The Prefix With Pattern cell should include this information:

Enter the pattern to prepend to directory numbers that apply to this directory lookup dial rule. Valid values include digits (0 through 9), plus (+), asterisk (*), and pound (#).

Note If a prefix pattern is defined, the digits to be removed can equal 0. If the prefix pattern is not defined, the digits to be removed must be greater than 0.

LDAP Configuration Restriction

The LDAP Authentication Configuration section of the “LDAP Authentication” chapter of the Cisco Unified Communications Manager Administration Guide omits the following information:

User accounts must be synchronized with Cisco Unified Communications Manager to use LDAP authentication. Administrators must enable LDAP synchronization and configure LDAP directory instance(s) to use the LDAP authentication mechanism.

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.

Clarification of Log Missed Calls Check Box

The description of the Log Missed Calls check box in the Directory Number Configuration chapter implies that the Log Missed Calls check box applies only to shared lines. However, the Log Missed Calls check box applies to both shared phone lines and non-shared phone lines.

If the Log Missed Calls check box is checked, Cisco Unified Communications Manager logs missed calls in the call history on the phone. If the check box is unchecked, Cisco Unified Communications Manager does not log missed calls. The default setting for this check box is checked.

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.

E & M Port Configuration Settings

The E & M Port Configurations section of the Gateway Configuration chapter in the Cisco Unified Communications Manager Administration Guide is missing the Unattended Port field description. Users should check the Unattended Port check box to indicate the device is attached to an unattended port, such as a voice mail port.

Removed field Call Stats from SIP Profile configuration

In the “SIP profile settings” section, the field “Call Stats” is not available under Device > Device Settings > SIP Profile on the Cisco Unified Communications Administration page. The Call Stats field is enabled, by default.

Incorrect Information about Deleting Route Patterns

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

The following information further explains the context:

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

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

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

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

The following is the corrected information:

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

Tip for Adding a New Server

This documentation update resolves CSCuc10415.

The following tip needs to be added to 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.

Incorrect Note about User Locales

This documentation update resolves CSCuq42434.

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

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

MDCX Sendonly Message Not Sent to MGCP Gateway

The Media Gateway Control Protocol section of the Understanding IP Telephony Chapter of the Cisco Unified Communications Manager System Guide does not mention that for all MGCP calls, Cisco Unified Communications Manager suppresses the media layer from sending any MDCX (M:sendonly) messages to the MGCP gateway. This is done to prevent one-way audio scenarios.

DTMF Suppressed when G.Clear is Advertised

The Support of G.Clear Codec for SIP Trunks section of the Understanding Session Initiation Protocol section of the Cisco Unified Communications Manager System Guide does not menation that Cisco Unified Communications Manager suppresses DTMF configuration settings for all calls on which G.Clear is advertised in the list of codecs, irrespective of whether G.Clear is chosen as the codec for the call.

Setting the Service Parameters for Cisco Unified Communications Manager Assistant

The Setting the Service Parameters for Cisco Unified Communications Manager Assistant section of the “Cisco Unified Communications Manager Assistant With Shared Line Support” and “Cisco Unified Communications Manager Assistant With Proxy Line Support” chapters of the Cisco Unified Communications Manager Features and Services Guide omits the following information.

Note Configure unique IP addresses for each pool so that the same Cisco IPMA server IP address does not appear in more than one pool.

Japanese Language and Unicode Font

The Configuring Web Dialer for the Local Language section of the “WebDialer” chapter of the Cisco Unified Communications Manager Features and Services Guide omits the following information:

If the Japanese language displays incorrectly when you use Microsoft Windows, ensure that the Unicode font is installed on your machine.

Setting the Service Parameters for Call Park

The Setting the Service Parameters for Call Park section of the “Call Park and Directed Call Park” chapter of the Cisco Unified Communications Manager Administration Guide omits some information about the call park reversion timer:

• When this timer expires, the parked call returns to the device that parked the call.

The last sentence in that section should say:

• When this timer expires, the parked call returns to the original called party. If a hunt group member parks a call that comes through a hunt pilot, the call goes back to the hunt pilot upon expiration of the Call Park Reversion Timer.

Call Park Range

The "Call Park and Directed Call Park" chapter of the Cisco Unified Communications Manager Features and Services Guide omits the following information:

The call park range is selected from the list of servers where the call originates.

For example, if Phone A (registered to node A) calls Phone B (registered to Node B) and the phone B user presses Park, Phone B requires a call park range in the CSS that resides on Node A.

In a multinode environment comprised of phones and gateways talking to various nodes, where calls originating from any server may need to be parked, the phones require a CSS that contains call park ranges from all servers.

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/sw/voicesw/ps556/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.

Block Offnet to Offnet Transfer

The following information is missing from the “External Call Transfer Restrictions” chapter in the Cisco Unified Communications Manager Features and Services Guide.

When you enable the service parameter Block Offnet to Offnet Transfer and make a blind transfer with Cisco Unity Connection, the Q.931 SETUP message which Cisco Unified Communications Manager sends to the PSTN gateway for an outbound PRI call still reaches the gateway. This transfer results in a dropped call.

Call Control Discovery Limitation

The following information is missing from the “Call Control Discovery” chapter in the Cisco Unified Communications Manager Features and Services Guide.

CCD has a limitation with three clusters (A, B and C), when C learns the advertisements of A and B.

In this scenario, when two clusters (A and B) are present, both of them advertise the same pattern, and cluster B advertises later than cluster A. This behavior overwrites the PSTN failover rule for cluster A which cluster C adopts. If your IP connection is lost, calls from cluster C are always redirected to cluster B via PSTN.

After you delete the cluster B advertisement, the PSTN failover rule still points back to A. If your IP connection is lost, calls from cluster C are redirected to cluster A via PSTN.

DoCoMo Phones Not Certified

The Remote Destination Configuration Settings section that appears in the “Cisco Unified Mobility” chapter of the Cisco Unified Communications Manager Features and Services Guide states that the Mobile Phone check box does not apply to dual-mode phones that are running SIP, such as DoCoMo N902iL and DoCoMo N906i. This information is correct. However, the DoCoMo phones should not be explicitly mentioned since neither phone has been certified with Cisco Unified Communications Manager.

Cisco Unified Communications Operating System

This section contains updates for the Cisco Unified Communications Operating System Administration Guide.

• Cisco Unified Communications Manager Attendant Console No Longer Available
• Regenerating a Certificate Update
• Note about IP Phone Firmware Update

Cisco Unified Communications Manager Attendant Console No Longer Available

The Pre-Upgrade Tasks section of the Cisco Unified Communications Operating System Administration Guide omits the following information:

Before you upgrade, delete Cisco Unified Communications Manager Attendant Console (CAC) devices and redirect numbering plans away from the CAC devices because CAC is not available in Cisco Unified Communications Manager 8.0 and later.

Regenerating a Certificate Update

This update applies to the Regenerating a Certificate procedure in Cisco Unified Communications Operating System Administration Guide.

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

Note about IP Phone Firmware Update

The Pre-Upgrade Tasks section of the Cisco Unified Communications Operating System Administration Guide omits the following information:

Note After you perform a switch version when you upgrade Unified CM, IP phones request a new configuration file. This request results in an automatic upgrade to the device firmware.

Cisco Unified Communication Manager Call Detail Records Administration

This section contains information on documentation omissions, errors, and updates for the Cisco Unified Communications Manager Call Detail Records Administration Guide.

• Incorrect CDR Field Description for destCallTerminationOnBehalfOf
• Incorrect Order of CDR and CMR Fields
• FAC and CMC Code is not Captured in CDR

Incorrect CDR Field Description for destCallTerminationOnBehalfOf

The description for the destCallTerminationOnBehalfOf field erroneously states “For example, if the originator of the call hangs up the phone, the OnBehalfOf code shows ‘12’ for Device. If the call terminates because of a transfer, the OnBehalfOf code shows ‘10’ for Transfer.” The term “originator” should read “destination.”

Incorrect Order of CDR and CMR Fields

Some CDR and CMR fields are in the wrong order. See the following tables for the order in the document and the corrected order:

Table 1 CDR Fields Order Corrections

Table 2 CMR Fields Order Corrections

FAC and CMC Code is not Captured in CDR

This documentation update resolves CSCus91749.

The following information about CDR entry for FAC and CMC calls is omitted in the Forced

authorization code (FAC) and Client Matter Code (CMC) topic in the Cisco Unified Communications Manager Call Detail Records Administration Guide.

FAC

CDR will now be written for a setup call leg for all the unanswered calls before the call is redirected to another caller if FAC is used to setup the call.

Note This call will not have any connect time since media is not connected for this call. The CDR will be logged regardless of the service parameter CdrLogCallsWithZeroDurationFlag if FAC is present in the call.

FAC Example 2

Blind conference using FAC:

Step 1 Call from 136201 to 136111.

Step 2 136111 answers and speaks for a few seconds.

Step 3 136201 presses the Conference softkey and dials 136203.

Step 4 The user is prompted to enter the FAC code and the user enters 124. FAC code 124 is configured as level 1 and given a name as Forward_FAC.

Step 5 While 136203 is ringing, 136201 presses the Conference softkey to complete the conference.

Step 6 136203 answers the call.

Step 7 The three members in the conference talk for sometime.

Step 8 136111 hangs up, leaving 136201 and 136203 in the conference. Since there are only two participants in

the conference, the conference feature will join these two directly together and they talk for a few seconds.

Note The setup call CDR for this example is generated even though it is of zero duration since FAC is used for this call.

CMC Example 2

Blind conference using CMC :

Step 1 Call from 136201 to 136111.

Step 2 136111 answers and speaks for a few seconds.

Step 3 136201 presses the Conference softkey and dials 136203.

Step 4 The user is prompted to enter the CMC code and the user enters 125. CMC code 125 is configured as level 1 and is given a name as Forward_CMC.

Step 5 While 136203 is ringing, 136201 presses the Conference softkey to complete the conference.

Step 6 136203 answers the call.

Step 7 The three members in the conference talk for sometime.

Step 8 136111 hangs sup, leaving 136201 and 136203 in the conference. Since there are only two participants in the conference, the conference feature will join these two directly together and they talk for a few seconds.

Note The setup call CDR for this example is generated even though it is of zero duration since CMC is used for this call.

Trace Compression

The Trace Configuration and Collection Checklist section of the “Understanding Trace” chapter of the Cisco Unified Serviceability Administration Guide contains incorrect information regarding trace compression. The correct information follows:

You cannot enable or disable trace compression from an enterprise parameter, the user interface (UI) or the command line interface (CLI).

Call Record Server and Trace File Server Renamed

The "Identifying and Adding Nodes to Cisco Unified Analysis Manager" chapter of the Cisco Unified Real Time Monitoring Tool Administration Guide includes incorrect terminology.

In Cisco Unified Communications Manager 8.0 and later, these changes exist:

• Call Record Server is renamed Call Record Repository
• Trace File Server is renamed Trace File Repository

Collect On Demand Renamed

The "Using the Cisco Unified Analysis Manager Tools" chapter of the Cisco Unified Real Time Monitoring Tool Administration Guide includes incorrect terminology.

In Cisco Unified Communications Manager 8.0 and later Collect On Demand is renamed Collect Traces Now.

CMR Records Do Not Get Generated for Call Legs That Involve IP Voice Media Streaming Application Components

The Feature Services section of the "Understanding Services" chapter in the Cisco Unified Serviceability Administration Guide omits this information:

The Cisco IP Voice Media Streaming Application service does not generate the Call Management Record (CMR) files for call legs that involve any IP Voice Media Streaming App components like conference, MOH, Annunciator or MTP.

Resend on Failure Field

In the Application Billing Server Parameter Settings section of the “Configuring CDR Repository Manager” chapter of the Cisco Unified Serviceability Administration Guide, the field description for Resend on Failure incorrectly states:

When you check the Resend on Failure box, this option informs CDRM not to send outdated CDR and CMR files to the billing server after the FTP or SFTP connection is restored.

That sentence should comprise:

When you check the Resend on Failure box, this option informs CDRM to send outdated CDR and CMR files to the billing server after the FTP or SFTP connection is restored.

Installing and Launching RTMT

The Installing RTMT section of the “Installing and Configuring 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.

Missing Information about the Platform Administrative Web Service

This documentation update resolves CSCup84833

The following information is omitted from the Platform Services Section of the Cisco Unified Serviceability Administration Guide :

The Platform Administrative Web Service is a Simple Object Access Protocol (SOAP) API that can be activated on Cisco Unified Communications Manager, IM and Presence Service, and Cisco Unity Connection systems to allow the PAWS-M server to upgrade the system.

Note Do not activate the Platform Administrative Web Service on the PAWS-M server.

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
• Alternative SFTP Servers
• DNS Information During Restore

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.

---

Alternative SFTP Servers

This update applies to the Disaster Recovery System Administration Guide for Cisco Unified Communications Manager. The System Requirements section contains out of date information about the Cisco Technology Developer Partner program (CTDP). This section should read as follows:

Cisco allows you to use any SFTP server product but recommends SFTP products that have been certified with Cisco Technology Partners. Technology partners, such as GlobalSCAPE, certify their products with specified versions of Cisco Unified Communications Manager. For information on which vendors have certified their products with your version of Cisco Unified Communications Manager, refer to the Solutions Catalog on the Cisco Developer Network. The Solutions Catalog is accessible at:

https://marketplace.cisco.com/catalog/search

Supported SFTP Servers

Note We recommend that you retest the DRS with your SFTP server after you upgrade your Unified Communications Manager, upgrade your SFTP server, or you switch to a different SFTP server. Perform this step to ensure that these components operate correctly together. As a best practice, perform a backup and restore on a standby or backup server.

Use the information in the following table to determine which SFTP server solution to use in your system.

DNS Information During Restore

DNS is not mentioned in the Disaster Recovery System Administration Guide. The guide should state that the DNS Configuration on the server prior to restore should be the same as the DNS Configuration when the backup was taken.

CDR Administration Guide

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

• Redirect Reason Codes

Redirect Reason Codes

The following entry is missing from the “Redirect Reason Codes” table.

Table 3 Redirect Reason Codes

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 CDR Analysis and Reporting 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 CDR Analysis and Reporting 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 CDR Analysis and Reporting 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

Cisco Unified IP Phone Services Application Development Notes

The IP Phone Service Configuration Settings table in the IP Phone Service Administration and Subscription of Cisco Unified IP Phone Services Applicaton Development Notes says that you can embed a special #DEVICENAME# substitution tag within a service URL. This tag works for either the Services or Messages buttons, but for the Directories button, the tag does not work on many older Cisco Unified IP phones.

Configure

This section contains updates for the Configuring Cisco Unified Communications Manager for the NovaTec TransNova S3 Voice Gateway, Cisco Unified Communications Manager Data Dictionary, Cisco Unified Communications Manager SIP Line Messaging Guide (Standard), Cisco Unified Communications Manager XML Developers Guide,. Cisco Unified IP Phone Service Application Development Notes for Cisco Unified Communications Manager, Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager.

• listDeviceByNameAndClass Is Not Supported in Cisco Unified Communications Manager 8.x

listDeviceByNameAndClass Is Not Supported in Cisco Unified Communications Manager 8.x

The “Administrative XMLAPI By Release” chapter in the Cisco Unified Communications Manager XML Developers Guide Release 8.0(1) incorrectly states that listDeviceByNameAndClass gets supported in Unified CM 8.x.

listDeviceByNameAndClass is not supported in Cisco Unified Communications Manager 8.x. Instead, you must use listPhone.

Troubleshooting Guide for Cisco Unified Communications Manager

In the “Performing Failed RAID Disk Replacement Without Restart” procedure in the Troubleshooting Guide for Cisco Unified Communications Manager, step 10 is incorrect. It should read as follows:

10. To check the RAID rebuild status, perform the following steps:

a. Check the LED on the disk. When the rebuild completes successfully, the LED changes from flashing amber to green.

b. Check the status of the physical disk by entering the show hardware CLI command.

A “State Optimal” message appears under the Logical Drives Information section.

c. Check a generated syslog. To generate a syslog, see the “Schedule trace collection” topic in the Cisco Unified Real-Time Monitoring Tool Administration Guide.

A “Rebuild complete” message appears.

Cisco Unified Communications Manager Features and Services Guide

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

• Early Media Cut-Through and Single Number Reach calls
• Call Park and Directed Call Park Restriction

Early Media Cut-Through and Single Number Reach calls

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.

Call Park and Directed Call Park Restriction

The following call flow shows a limitation with the Call Park and Directed Call Park features.

1. Phone A calls Phone B.

2. Phone B parks the call. Phone A is now connected to MOH.

3. Phone A presses Hold (Mutual Hold).

4. Phone C dials the parked number through a H323 Trunk.

5. No audio is produced and the call fails after 12 sec (MXTimeout).

In this call flow, when you retrieve a parked call across an H323 ICT that is also on hold, the call fails. By the time phone C tries to retrieve the parked call, the parked party is on hold and Unified CM cannot cut through media.

Cisco Unified Communications Manager Bulk Administration Guide

This section contains updates for the Cisco Unified Communications Manager Bulk Administration Guide :

CSCui06050 Model is Not a Valid Device Field When Generation a Phone Report

The Phone Reports section mentions Model as one of the fields. However, this field is not available in the Bulk Administration Tool GUI.

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.

Cisco Unified Real-Time Monitoring Tool Administration Guide

Incorrect Default Value for LogPartitionLowWaterMarkExceeded Alert

This documentation update resolves CSCuq39087

The default threshold value for LogPartitionLowWaterMarkExceeded alert is incorrectly described as 95% in the “Alerts” chapter. The following table contains the correct value.

Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at www.cisco.com/go/trademarks. Third party trademarks mentioned 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. (1005R)