Guest

Support

Updates to Cisco Unified Communications Manager 6.1(x) Documentation

  • Viewing Options

  • PDF (868.8 KB)
  • Feedback
Updates to Cisco Unified CallManager 6.1(1) Documentation

Table Of Contents

Updates to Cisco Unified CallManager 6.1(1) Documentation

Installation, Upgrade, and Migration

Setting the Cisco Unified Communications Manager MTU Size

Cisco Unified Communications Manager CDR Analysis and Reporting Administration Guide

Add Incoming Number Prefix to CDR Update

Cisco Unified Communications Manager Administration Guide

Directory Lookup Dial Rule Configuration Settings Updates

Description of the Reset Button

Route Plan Report Description Omits Mention of Mobile Voice Access Numbers

End User Chapter Includes Incorrect Information for Manager User ID Field

Device Pool Chapter Contains Incomplete Description for Device Pool Name Field

Credential Policy Configuration Settings Display Description is Incorrect

Incorrect Information Exists in the Meet-Me Number/Pattern Configuration

Considerations for LDAP Port Configuration

Software Feature License

Incorrect Description for User ID Field in Application User Window

Logging In To the Web Interface When the Firewall Is Disabled

Credential Policy Settings

Deleting a Server

Unclear Documentation on Called Party Name Presentation

Misleading Documentation About Creating Cisco Unity and Cisco Unity Connection Voice Mailboxes

Barge Visual Indicator

Adding an Administrator User to Cisco Unity or Cisco Unity Connection

Documentation Does Not Include the Latest List of Supported Phone Models

Upgrade Procedure Contains Incorrect Information

Application Server Configuration Not Required for Cisco Unity Connection 2.x

Incorrect Documentation on How to Delete Parameter for Phone Service

Default Device Profile Chapter Incorrectly Includes Expansion Module Settings

Hunt Pilot Chapter Needs Clarification of Maximum Hunt Timer Setting

Annunciator Chapter Contains Incorrect Information on Description Field

Gateway Configuration Chapter Contains Incorrect Information on Domain Name Field

AAR Group Chapter Includes Incorrect Description for Dial Prefix Field

Dual Phone Mode Support

Generating a License File from DMA

Uploading a License File

LDAP Authentication Chapter Omits Information on SSL Certificates and IP Addresses/Host Names

Enterprise Parameters and Service Parameters Chapters Omit Information on Set to Default Button

Information About Using an SRV Destination Port for the CUP Publish Trunk Service Parameter

For SIP Trunks Used with Multiple Device Pools, Configure an SRV Destination Port

Information About Changing Region Bandwidth Settings When Video Calls Are Made

Information Omitted for Reroute Incoming Request to New Trunk Based on Setting

Do Not Begin Starting and Ending Directory Numbers with a Zero (0)

Time-of-Day Routing Chapter Omits Information About Defined Time Periods

Cisco Unified Communications Manager System Guide

RSVP Reservation Teardown for Shared-Line Calls

Considerations for LDAP Port Configuration

RSVP Reservation Teardown for Shared-Line Calls

Application Server Configuration Not Required for Cisco Unity Connection 2.x

Unclear Documentation on Called Party Name Presentation

Automated Alternate Routing (AAR) Limitation with Remote Gateways

Documentation Does Not State That Line Group With No Members Is Not Supported for Routing Calls

Peer-to-Peer Image Distribution

Recommended Number of Devices in Device Pool

Throttling on SIP UDP Ports

Call Admission Control Bandwidth Example Correction

Directory Numbers Chapter Includes Incorrect Example for Shared Lines and Call Forward Busy Trigger

Clustering Chapter Omits Information about Subsequent (Subscriber) Node

Licensing Chapter Omits Information on Adjunct Licensing

Cisco TFTP Chapter Omits Configuration Tip on Centralized TFTP

Information About Changing Region Bandwidth Settings When Video Calls Are Made

Trunk Chapter Omits Restrictions for H.323/H.225 Trunks

Voice-Messaging Chapters Omits Fact That Cisco Messaging Interface Service Parameters Must Be Configured Per Node

Information About Changing Region Bandwidth Settings When Video Calls Are Made

Cisco Unified Communications Manager Features and Services Guide

Setting the Service Parameters for Cisco Unified Communications Manager Assistant

Call Park Range

Supported Call States

CTI and Attendant Console Chapters Omit Information on CTI Monitored Lines

Incorrect Information on How to Install Assistant Console Application

Do Not Disturb Feature Priority

Extension Mobility Successful Authentication Cache

Devices Associated with the Attendant Console Application User

CTI Devices Do Not Support Multicast Music on Hold (MOH)

Attendant Console Phones Do Not Support the Intercom Feature

Unclear Documentation on How Locales Work for Mobile Voice Access

Mobile Connect and Mobile Voice Access Chapter Omits Information About Configuring the Mobile Voice Access Media Resource

cBarge Chapter Omits Information on Shared Line Restriction for Conferences

Cisco Unified IP Phones Supporting Call Back with PLKs

Intercom Configuration

Extension Mobility Redundancy

Number of Login or Logout Operations That Cisco Extension Mobility Supports

None Option Not Documented for DND Incoming Call Alert Setting

Mobile Connect and Mobile Voice Access Chapter Contains Incorrect Information About Configuring an H.323 Gateway for System Remote Access by Using Hairpinning

Mobile Connect and Mobile Voice Access Chapter Contains Incorrect Information About Configuring an H.323 Gateway for System Remote Access by Using PRI

Cisco Extension Mobility Chapter Error

Barge and Security

Barge with Shared Conference Bridge

Number of Alphanumeric Characters That Are Allowed in the Pickup Group Name Field

Documentation Does Not Include the Latest List of Supported Phone Models

Do Not Disturb Documentation Provides Incorrect Information About Phone Tone

Destination Number in Remote Destination Configuration Window

Cisco Extension Mobility Supplemental Information

Cisco Unified IP Phones Supporting Barge

Cisco Unified IP Phones Supporting Call Back

Cisco Unified Communications Manager Security Guide

Support for Certificates from External CAs

CAPF System Interactions and Requirements

Security Icons and Encryption

Software Conference Bridge Not Supported

Cisco Unified Communications Manager XML Developers Guide for Release 6.0(1)

Cisco Unified Serviceability Administration Guide

DNS Required for RTMT Alerts by E-mail

Warning Displays When SIP Stack Trace Is Enabled

Missing MIB Changes

SNMP Traps and Informs Correction

Cisco Unified Communications Manager Assistant User Guide

Cisco Unified Communications Manager Assistant User Guide for Cisco Unified Communications Manager 6.0

Online Help Notes for Hebrew and Arabic

Cisco Unified Communications Manager Assistant

Directory Search Correction

Creating Filter Lists for a Manager

Cisco Unified IP Phone Documentation

Cisco Unified IP Phone User Guide (7906, 7911, 7931, 7945, 7965, 7975)

Cisco Unified IP Phone Administration Guides (7905G, 7912G, 7921G)

Cisco Unified Wireless IP Phone Guide 7920 for Cisco Unified CallManager 5.0 (SCCP)

Cisco Unified Wireless IP Phone Guide (7975, 7971, 7965, 7945, 7962, 7942, 7941, 7931, 7911, 7906)

Cisco Unified CallManager Bulk Administration Guide

Description for Phone Personalization Is Incorrect in Documentation

Incorrect Path Is Documented for Add File Format Window

Primary User Device Field on the Update Users Window in BAT

Single Button Barge (new field)—Phone Template Configuration Window in BAT

Join Across Lines (new field)—Phone Template Configuration Window in BAT

Single Button Barge (new field)—UDP Template configuration Window in BAT

Join Across Lines (new field)—UDP Template configuration Window in BAT

Cisco Unified Communications Manager Real-Time Monitoring Tool Administration Guide

RTMT Trace and Log Central Disk IO and CPU Throttling

Trace Compression Support

Path for Accessing Cisco Unified Reporting

Perfmon Log File—Maximum File Size Default Value

Path for Accessing Cisco Unified Reporting

DNS Required for RTMT Alerts by E-mail

Minimum Memory Requirement for RTMT Client

Cisco Unified Communications Operating System Administration Guide

COP File Installation

NTP Version 4

Support for NIC Teaming

Install New COP Files Before You Upgrade Cisco Unified Communications Manager

Digital Certificate Key Length Restrictions

Parallel Upgrades from Unified CM Releases 5.x and 6.x to Unified CM Release 6.1(3x)

set network dhcp eth0 disable Command Parameters

Remote Support Account Duration

System Generates a DBReplicationFailure Alert

Information On ARP Cache Limits Omitted from Operating System Administration Guide

Third-Party Certificate Authority Verification

Recovering Administrator and Security Passwords

Software Feature License Information Omitted from Operating System Administration Guide

Cisco Unified Communications Manager Does Not Support Recovery of Administration or Security Passwords

Characters Allowed in a Pre-Shared Key

IP Phones Automatically Upgrade Firmware After Switch Version

Troubleshooting Guide for Cisco Unified Communications Manager

Automated Alternate Routing (AAR) Limitation with Remote Gateways

Cisco Unified Mobility User Hangs Up Mobile Phone But Cannot Resume Call on Desktop Phone

Netdump Utility

Database Replication

Cisco Unified Communications Manager 6.1 TCP and UDP Port Usage

Ephemeral Port Range

Disaster Recovery System Administration Guide

Upgrading to Cisco Unified Communications Manager from 4.x Releases Guide

Obtaining Documentation and Submitting a Service Request


Updates to Cisco Unified CallManager 6.1(1) Documentation


Updated February 28, 2012

This document provides documentation changes that were unavailable when the Cisco Unified Communications Manager Release 6.1(1) documentation suite was released.

Cisco Unified Communications Manager CDR Analysis and Reporting Administration Guide

Cisco Unified Communications Manager Administration Guide

Cisco Unified Communications Manager System Guide

Cisco Unified Communications Manager Features and Services Guide

Cisco Unified Communications Manager XML Developers Guide for Release 6.0(1)

Cisco Unified Serviceability Administration Guide

Cisco Unified Communications Manager Assistant User Guide

Cisco Unified IP Phone Documentation

Cisco Unified CallManager Bulk Administration Guide

Cisco Unified Communications Manager Real-Time Monitoring Tool Administration Guide

Cisco Unified Communications Operating System Administration Guide

Troubleshooting Guide for Cisco Unified Communications Manager

Cisco Unified Communications Manager 6.1 TCP and UDP Port Usage

Disaster Recovery System Administration Guide

Upgrading to Cisco Unified Communications Manager from 4.x Releases Guide

Installation, Upgrade, and Migration

This section comprises documentation updates to documentation that supports installation, upgrade and migration of Cisco Unified CM.

Setting the Cisco Unified Communications Manager MTU Size

Setting the Cisco Unified Communications Manager MTU Size

The maximum transmission unit (MTU) size that you configure for Cisco Unified Communications Manager must not exceed the lowest MTU size that is configured on any link in your network.

The default MTU size is 1500. You can configure the MTU size during product installation, or by using the CLI command set network mtu.

Cisco Unified Communications Manager CDR Analysis and Reporting Administration Guide

The following section comprises documentation updates for the Cisco Unified Communications Manager CDR Analysis and Reporting Administration Guide.

Add Incoming Number Prefix to CDR Update

Add Incoming Number Prefix to CDR Update

The Configuring CDR Service Parameters section of the "Configuring the CDR Analysis and Reporting Tool" chapter of the Cisco Unified Communications Manager CDR Analysis and Reporting Administration Guide for Release 6.1(1) contains information that needs to be updated as follows:

Add Incoming Number Prefix to CDR —This parameter determines whether Cisco Unified Communications Manager adds the incoming prefix (as specified in the National Number Prefix, International Number Prefix, Subscriber Number Prefix, and Unknown Number Prefix service parameters) to the calling party number in the CDRs for that call. If the prefix is applied on the inbound side of the call, it always will be added to the calling party number in the CDRs for that call, even if this parameter is set to False. If the prefix is applied on the outbound side, the prefix will be added to the calling party number in the CDR(s) for that call, only if this parameter is set to True. If the destination of the call is a gateway, Cisco Unified Communications Manager will not add the prefix to the CDRs even if this parameter is enabled. This parameter applies cluster wide. The default value for this required field specifies False.

Cisco Unified Communications Manager Administration Guide

The following sections comprise documentation updates for the Cisco Unified Communications Manager Administration Guide.

Directory Lookup Dial Rule Configuration Settings Updates

Description of the Reset Button

Route Plan Report Description Omits Mention of Mobile Voice Access Numbers

End User Chapter Includes Incorrect Information for Manager User ID Field

Device Pool Chapter Contains Incomplete Description for Device Pool Name Field

Credential Policy Configuration Settings Display Description is Incorrect

Incorrect Information Exists in the Meet-Me Number/Pattern Configuration

Considerations for LDAP Port Configuration

Software Feature License

Incorrect Description for User ID Field in Application User Window

Logging In To the Web Interface When the Firewall Is Disabled

Credential Policy Settings

Deleting a Server

Unclear Documentation on Called Party Name Presentation

Misleading Documentation About Creating Cisco Unity and Cisco Unity Connection Voice Mailboxes

Barge Visual Indicator

Adding an Administrator User to Cisco Unity or Cisco Unity Connection

Documentation Does Not Include the Latest List of Supported Phone Models

Upgrade Procedure Contains Incorrect Information

Application Server Configuration Not Required for Cisco Unity Connection 2.x

Incorrect Documentation on How to Delete Parameter for Phone Service

Default Device Profile Chapter Incorrectly Includes Expansion Module Settings

Hunt Pilot Chapter Needs Clarification of Maximum Hunt Timer Setting

Annunciator Chapter Contains Incorrect Information on Description Field

Gateway Configuration Chapter Contains Incorrect Information on Domain Name Field

AAR Group Chapter Includes Incorrect Description for Dial Prefix Field

Dual Phone Mode Support

Generating a License File from DMA

Uploading a License File

LDAP Authentication Chapter Omits Information on SSL Certificates and IP Addresses/Host Names

Enterprise Parameters and Service Parameters Chapters Omit Information on Set to Default Button

Information About Using an SRV Destination Port for the CUP Publish Trunk Service Parameter

Information About Changing Region Bandwidth Settings When Video Calls Are Made

Information Omitted for Reroute Incoming Request to New Trunk Based on Setting

Do Not Begin Starting and Ending Directory Numbers with a Zero (0)

Time-of-Day Routing Chapter Omits Information About Defined Time Periods

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.


Description of the Reset Button

The Cisco Unified Communications Manager Configuration Settings section of the "System Configuration" chapter of the Cisco Unified Communications Manager Administration Guide contains incomplete description of the Reset button. The description should comprise:

Click this button to reset all devices that belong to the same Cisco Unified CM Group as this Cisco Unified Communications Manager server.


Note All devices in the Cisco Unified CM Group of which this server is a member get reset, not just those devices that are registered with this server.


Route Plan Report Description Omits Mention of Mobile Voice Access Numbers

The first paragraph of the "Route Plan Report" chapter in the Cisco Unified Communications Manager Administration Guide omits mention of the Mobile Voice Access number as one of the numbers that the route plan report provides. The text that follows replaces the first paragraph of the chapter.

The route plan report lists all of the following types of directory and other numbers in the system:

Unassigned directory numbers (DN)

Call park numbers

Conference numbers

Directory numbers (DN)

Calling party transformation patterns

Called party transformation patterns

Translation patterns

Call pickup group numbers

Route patterns

Message-waiting indicators

Voice-mail ports

Attendant console

Domain routing

IP routing

Hunt pilots

Directed call park numbers

Intercom directory numbers

Intercom translation patterns

Mobile Voice Access numbers (configured in the Service Parameters window [System > Service Parameters])

The route plan report allows you to view either a partial or full list and to go directly to the associated configuration windows by clicking the entry in the Pattern/Directory Number, Partition, or Route Detail columns of the report.

End User Chapter Includes Incorrect Information for Manager User ID Field

The "End User Configuration" chapter in the Cisco Unified Communications Manager Administration Guide incorrectly describes the Manager User ID field.

Incorrect Description

For the Manager User ID field, enter the user ID of the end user manager ID. The manager user ID that you enter must already exist in the directory as an end user.

Correct Description

For the Manager User ID field, enter the user ID of the end user manager ID. The manager user ID that you enter does not have to exist in the same cluster as the end user; therefore, Cisco Unified Communications Manager does not require that you enter a user ID that already exists in the database.

Device Pool Chapter Contains Incomplete Description for Device Pool Name Field

The "Device Pool Configuration" chapter in the Cisco Unified Communications Manager Administration Guide does not contain the supported characters that you can enter in the Device Pool Name field. In this field, you can enter alphanumeric characters, period (.), hyphen (-), underscore (_), or a blank space. You can enter up to 50 characters.

Credential Policy Configuration Settings Display Description is Incorrect

The Credential Policy Configuration Settings section of the User Management Chapter of the Cisco Unified Communications Manager Administration Guide contains an incorrect description of the Display field. The correct information follows:

Specify the credential policy name. Enter up to 64 characters, except for quotation marks (""). Do not enter tab.

Incorrect Information Exists in the Meet-Me Number/Pattern Configuration

The Description field in the Meet-Me Number/Pattern Configuration Settings table incorrectly states that you can enter up to 30 alphanumeric characters as a description of the meet-me number/pattern.

The description should state that you can enter up to 50 characters in the description field.

Considerations for LDAP Port Configuration


Tip The following information does not display in the LDAP chapters in the Cisco Unified Communications Manager Administration Guide and Cisco Unified Communications Manager System Guide.


When you configure the LDAP Port field in the LDAP Authentication window in Cisco Unified Communications Manager Administration, you specify the port number that the corporate directory uses to receive LDAP requests. How your corporate directory is configured determines which port number to enter in this field. For example, before you configure the LDAP Port field, determine whether your LDAP server acts as a Global Catalog server and whether your configuration requires LDAP over SSL. Consider entering one of the following port numbers:


Tip Your configuration may require that you enter a different port number than the numbers that are listed in the following bullets. Before you configure the LDAP Port field, contact the administrator of your directory server to determine the correct port number to enter.


LDAP Port For When the LDAP Server Is Not a Global Catalog Server

389—When SSL is not required. (This port number is the default that displays in the LDAP Port field.)

636—When SSL is required. (If you enter this port number, make sure that you check the Use SSL check box.)

LDAP Port For When the LDAP Server Is a Global Catalog Server

3268—When SSL is not required.

3269—When SSL is required. (If you enter this port number, make sure that you check the Use SSL check box.)

Software Feature License

When you upgrade from any supported release of Cisco Unified Communications Manager to Release 6.1(3x), you must download and install a software feature license to activate the new features. The Cisco Unified Communication Administration Guide indicates that you must install a software feature license only if you are upgrading from 5.x or 6.x releases. You also need a license if you are upgrading from supported 4.x releases. For instructions about how to obtain and install a software feature license, see the "License File Upload" chapter in the Cisco Unified Communications Manager Administration Guide.

Incorrect Description for User ID Field in Application User Window

The "Application User Configuration" chapter in the Cisco Unified Communications Manager Administration Guide incorrectly states that you can enter quotation marks (") in the User ID field in the Application User Configuration window in Cisco Unified Communications Manager Administration. In the User ID field, you can enter the following characters: alphanumeric (a-zA-Z0-9), dash(-), underscore(_), or space( ).

Logging In To the Web Interface When the Firewall Is Disabled

When the firewall is disabled, you must enter the URL of the Cisco Unified Communications Manager server in the following format to log in to the web interface:

https://server:8443/
 
   

where server specifies the servername or IP address of the server.


Note Cisco does not recommend disabling the firewall.


Credential Policy Settings

The Credential Policy Configuration Settings (table) in the "Credential Policy" chapter of the Cisco Unified Communications Manager Administration Guide requires the following changes:

Change 1-10 to 1-100 in the Description column for the Failed Logon/No Limit for Failed Logons field.

Change 1-120 to 1-1440 in the Description column for the Lockout Duration/Administrator Must Unlock field.

Deleting a Server

The Cisco Unified Communications Manager Administration Guide does not provide the messages that display when you attempt to delete a server. Disregard the entire section, Deleting a Server, in the "System-Level Configuration Settings" chapter in the Cisco Unified Communications Manager System Guide. Instead, refer to the following:

Deleting a Server and Adding a Deleted Server to a Cluster

In Cisco Unified Communications Manager Administration, you cannot delete the first node of the cluster, but you can delete subsequent nodes. Before you delete a subsequent node in the Find and List Servers window, Cisco Unified CM Administration displays the following message: "You are about to permanently delete one or more servers. This action cannot be undone. Continue?". If you click OK, the server gets deleted from the Cisco Unified CM database and is not available for use.


Tip When you attempt to delete a server from the Server Configuration window, a message that is similar to the one in the preceding paragraph displays. If you click OK, the server gets deleted from the Cisco Unified CM database and is not available for use.


Before you delete a server, consider the following information:

Cisco Unified CM Administration does not allow you to delete the first node in the cluster, but you can delete any subsequent node.

Cisco recommends that you do not delete any node that has Cisco Unified CM running on it, especially if the node has devices, such as phones, registered with it.

Although dependency records exist for the subsequent nodes, the records do not prevent you from deleting the node.

If any call park numbers are configured for Cisco Unified CM on the node that is being deleted, the deletion fails. Before you can delete the node, you must delete the call park numbers in Cisco Unified CM Administration.

If a configuration field in Cisco Unified CM Administration contains the IP address or host name for a server that you plan to delete, update the configuration before you delete the server. If you do not perform this task, features that rely on the configuration may not work after you delete the server; for example, if you enter the IP address or host name for a service parameter, enterprise parameter, service URL, directory URL, IP phone service, and so on, update this configuration before you delete the server.

If an application GUI, for example, Cisco Unity, Cisco Unity Connection, and so on, contains the IP address or hostname for the server that you plan to delete, update the configuration in the corresponding GUIs before you delete the server. If you do not perform this task, features that rely on the configuration may not work after you delete the server.

The system may automatically delete some devices, such as MOH servers, when you delete a server.

Before you delete a node, Cisco recommends that you deactivate the services that are active on the subsequent node. Performing this task ensures that the services work after you delete the node.

Changes to the server configuration do not take effect until you restart Cisco Unified CM. For information about restarting the Cisco CallManager service, refer to the serviceability documentation for Cisco Unified CM.

To ensure that database files get updated correctly, you must reboot the cluster after you delete a server.

After you delete the node, access Cisco Unified Reporting to verify Cisco Unified CM removed the node from the cluster. In addition, access Cisco Unified Reporting, RTMT, or the CLI to verify that database replication is occurring between existing nodes; if necessary, repair database replication between the nodes.

If you delete a subsequent node (subscriber) from Cisco Unified CM Administration and you want to add it back to the cluster, perform the following procedure:

Procedure


Step 1 In Cisco Unified CM Administration, add the server by choosing System > Server.

Step 2 After you add the subsequent node to Cisco Unified CM Administration, perform an installation on the server by using the disk that Cisco provided in your software kit.


Tip For example, if you have a version 6.1(4) disk, perform a 6.1(4) installation on the node. If you have a disk with a compatible version of 5.X on it, for example, use the disk to install Cisco Unified CM on the subsequent node; during the installation, choose the Upgrade During Install option when the installation displays the options.

Make sure that the version that you install on the subsequent node matches the version that runs on the first node (publisher) in the cluster.

If the first node in the cluster runs Cisco Unified Communications Manager 6.1(4) version and a service release (or engineering special), you must choose the Upgrade During Install option when the installation displays the installation options; before you choose this option, ensure that you can access the service release (or engineering special) image on DVD or a remote server. For more information on how to perform an installation, refer to installation documentation that supports your version of Unified CM.


Step 3 After you install Unified CM, configure the subsequent node, as described in the installation documentation that supports your version of Unified CM.

Step 4 Access the Cisco Unified Reporting, RTMT, or the CLI to verify that database replication is occurring between existing nodes; if necessary, repair database replication between the nodes.


Unclear Documentation on Called Party Name Presentation

The Cisco Unified Communications Manager Administration Guide provides unclear information about called party name presentation.

The Cisco Unified Communications System Guide states that when the Always Display Original Dialed Number service parameter is set to True, the originating phone displays only the dialed digits for the duration of the call. To clarify the documentation, if you set the Cisco CallManager service parameter to True, the name of the called party does not display on the phone of the calling party.

The Cisco Unified Communications Manager Administration Guide does not state that setting the Always Display Original Dialed Number service parameter to True impacts the configuration for the Alerting Name field. If you set the service parameter to True, the alerting name does not display on the calling phone; only the original dialed number displays.

Misleading Documentation About Creating Cisco Unity and Cisco Unity Connection Voice Mailboxes

The Cisco Unified Communications Manager Administration Guide contains misleading information about creating Cisco Unity and Cisco Unity Connection voice mailboxes. Consider the following information when you configure the voice mailboxes:

You can disregard the following statement in the Cisco Unified Communications Manager Administration Guide: "Ensure Cisco Unity Cisco Unified Communications Manager Integrated Voice Mailbox Configuration is enabled on the Cisco Unity or Cisco Unity Connection server."

If you are integrating Cisco Unified Communications Manager 6.x with Cisco Unity Connection 2.x, you can use the import feature that is available in Cisco Unity Connection 2.x instead of performing the procedure that is described in the Creating a Cisco Unity or Cisco Unity Connection Voice Mailbox section in the Cisco Unified Communications Manager Administration Guide. For information on how to use the import feature, refer to the User Moves, Adds, and Changes Guide for Cisco Unity Connection 2.x.

Barge Visual Indicator

The "Cisco Unified IP Phone Configuration" chapter in the Cisco Unified Communications Manager Administration Guide incorrectly states that a spinning circle on the phone display indicates that a barge is taking place. Only an audible indicator occurs.

Adding an Administrator User to Cisco Unity or Cisco Unity Connection

The "Application User" chapter of the Cisco Unified Communications Manager Administration Guide incorrectly states that you can use the Create Cisco Unity Application User link in the Related Links drop-down list box to create an application user voice mailbox in Cisco Unity or Cisco Unity Connection. You use this link to add an administrator user to Cisco Unity or Cisco Unity Connection.

1. Correct the Next Steps portion in the Configuring an Application User section to read as follows:

Next Steps

If you want to associate devices with this application user, continue with the "Associating Devices to an Application User" procedure.

To manage credentials for this application user, continue with the "Managing Application User Credential Information" procedure.

To add this administrator user to Cisco Unity or Cisco Unity Connection, continue with the procedure in "Adding an Administrator User to Cisco Unity or Cisco Unity Connection" section.

2. Correct the section header "Creating a Cisco Unity or Cisco Unity Connection Voice Mailbox" to "Adding an Administrator User to Cisco Unity of Cisco Unity Connection" and correct the content as follows:

Adding an Administrator User to Cisco Unity or Cisco Unity Connection

The Create Cisco Unity Application User link on the Application Configuration window allows you to add this user as an administrator user to Cisco Unity or Cisco Unity Connection. With this method, you configure the application user in Cisco Unified Communications Manager Administration; then, configure any additional settings for the user in Cisco Unity or Cisco Unity Connection Administration

You can also use the import tool in Cisco Unity or Cisco Unity Connection to import application users as administrative users. To import users, refer to the Cisco Unity or Cisco Unity Connection documentation. (The system does not support the import feature for Cisco Unity Connection 1.1 or 1.2.)

The Create Cisco Unity User link displays only if the Cisco Unity administrator installed and configured the appropriate software. Refer to the applicable Cisco Unified Communications Manager Integration Guide for Cisco Unity or the applicable Cisco Unified Communications Manager SCCP Integration Guide for Cisco Unity Connection.

Before You Begin

Ensure that you have defined an appropriate template for the user that you plan to push to Cisco Unity or Cisco Unity Connection. For Connection users, refer to the applicable User Moves, Adds, and Changes Guide for Cisco Unity Connection. For Cisco Unity users, refer to the Cisco Unity System Administration Guide.

Procedure


Step 1 Find the application user, as described in the Finding an Application User section.

Step 2 From the Related Links drop-down list box, in the upper, right corner of the window, choose the Create Cisco Unity Application User link and click Go.

The Add Cisco Unity User dialog box displays.

Step 3 From the Application Server drop-down list box, choose the Cisco Unity or Cisco Unity Connection server on which you want to create a Cisco Unity or Cisco Unity Connection user and click Next.

Step 4 From the Application User Template drop-down list box, choose the template that you want to use.

Step 5 Click Save.

The administrator account gets created in Cisco Unity or Cisco Unity Connection. The link in Related Links changes to Edit Cisco Unity User in the Application User Configuration window. You can now view the user that you created in Cisco Unity Administration or Cisco Unity Connection Administration.



Note When the Cisco Unity or Cisco Unity Connection user is integrated with the Cisco Unified Communications Manager Application User, you cannot edit fields such as Alias (User ID in Cisco Unified Communications Manager Administration), First Name, Last Name, Extension (Primary Extension in Cisco Unified Communications Manager Administration), and so on, in Cisco Unity Administration or Cisco Unity Connection Administration. You can only update these fields in Cisco Unified Communications Manager Administration.



Note Cisco Unity and Cisco Unity Connection monitor the synchronization of data from Cisco Unified Communications Manager. You can configure the sync time in Cisco Unity Administration or Cisco Unity Connection Administration at the Tools menu. For Cisco Unity Connection, refer to the User Moves, Adds, and Changes Guide for Cisco Unity Connection for more information. For Cisco Unity, refer to the Cisco Unity System Administration Guide.


Documentation Does Not Include the Latest List of Supported Phone Models

The Cisco Unified Communications Manager Administration Guide, Cisco Unified Communications Manager System Guide, and Cisco Unified Communications Manager Features and Services Guide may not contain the latest list of supported Cisco Unified IP Phones. To identify whether the phone supports a feature, refer to the phone documentation that supports this version of Cisco Unified Communications Manager and the phone model.

Upgrade Procedure Contains Incorrect Information

In the Upgrading From Cisco Unified CallManager 4.x Releases section of the Cisco Unified Communications Administration Guide, the procedure indicates that a pop-up window displays when the user chooses an existing license file and chooses the View File button. The license actually displays in the main window after the screen refreshes

Application Server Configuration Not Required for Cisco Unity Connection 2.x

The Cisco Unified Communications Manager Administration Guide suggests that you must configure a Cisco Unity Connection 2.x server in the Application Server Configuration window in Cisco Unified Communications Manager Administration to maintain an association with the Cisco Unity Connection 2.x server. In fact, configuring a Cisco Unity Connection 2.x server in Cisco Unified Communications Manager Administration creates a blank list of user templates for Cisco Unity Connection in Cisco Unified Communications Manager. Instead of configuring the application server in Cisco Unified Communications Manager Administration, create an AXL connection via Unity Connection 2.x, as described in the System Administration Guide for Cisco Unity Connection. Creating the AXL connection via Cisco Unity Connection 2.x pushes a list of valid user templates for Cisco Unity Connection 2.x to Cisco Unified Communications Manager.

Incorrect Documentation on How to Delete Parameter for Phone Service

The Cisco Unified Communications Manager Administration Guide incorrectly states how to delete a service parameter in the IP Phone Services Configuration window in Cisco Unified Communications Manager Administration. To delete a parameter for an IP phone service, click the Delete Parameter button; after the deletion message displays, click OK.

To delete an IP phone service, click the Delete button in the IP Phone Services Configuration window or check the IP phone service check box in the Find and List Phone Services window and click Delete Selected.

Default Device Profile Chapter Incorrectly Includes Expansion Module Settings

The "Default Device Profile" chapter in the Cisco Unified Communications Manager Administration Guide includes descriptions for the following settings, which you cannot configure in the Default Device Profile Configuration window in Cisco Unified CM Administration: Module 1 and Module 2. Ignore these descriptions in this chapter.

Hunt Pilot Chapter Needs Clarification of Maximum Hunt Timer Setting

The "Hunt Pilot Configuration" chapter in the Cisco Unified Communications Manager Administration Guide provides the following description for the Maximum Hunt Timer setting:

Enter a value (in seconds) that specifies the maximum time for hunting. Valid values specify 1 to 3600. The default value specifies 1800 seconds (30 minutes).

This timer cancels if either a hunt member answers the call or if the hunt list gets exhausted before the timer expires. If you do not specify a value for this timer, hunting continues until a hunt member answers or hunting exhausts. If neither event takes place, hunting continues for 30 minutes, after which the call gets taken for final treatment.


Tip If hunting exceeds the number of hops that the Forward Maximum Hop Count service parameter specifies, hunting expires before the 30-minute maximum hunt timer value, and the caller receives a reorder tone.


In addition, the description should state that Cisco Unified CM only uses the configuration for the Maximum Hunt Timer setting if you configure the Hunt Forward settings in the Hunt Pilot Configuration window.

Annunciator Chapter Contains Incorrect Information on Description Field

The "Annunciator Configuration" chapter in the Cisco Unified Communications Manager Administration Guide states that you can configure up to 54 characters in the Description field. Actually, you can configure up to 128 characters.

Gateway Configuration Chapter Contains Incorrect Information on Domain Name Field

The "Gateway Configuration" chapter in the Cisco Unified Communications Manager Administration Guide incorrectly states that you can enter 50 characters in the Domain Name field in the MGCP gateway configuration window. Actually, you can enter up to 64 characters in the Domain Name field for MGCP gateways.

AAR Group Chapter Includes Incorrect Description for Dial Prefix Field

The "Automated Alternate Routing Group Configuration" chapter in the Cisco Unified Communications Manager Administration Guide includes incorrect entries for the Dial Prefix field.

Incorrect Information

Dial Prefix field—Enter the prefix characters and symbols to use for automated alternate routing within this AAR group. Valid entries include the following digits: [ ^ 0 1 2 3 4 5 6 7 8 9 - ] + ? ! X * # . @

Correct Information

Dial Prefix field—Enter the prefix digits to use for automated alternate routing within this AAR group. Valid entries include numeric characters (0-9), alpha characters (A-D), asterisk (*), and pound (#).

Dual Phone Mode Support

The "Cisco Unified IP Phone Configuration" chapter of the Cisco Unified Communications Manager Administration Guide omitted this information.

To support Mobile Connect and Mobile Voice Access for dual-mode phones, the following field displays on the Phone Configuration window:

Mobility User ID (dual-mode phones only) - From the drop-down list box, choose the user ID of the person to whom this dual-mode phone is assigned.


Note The Owner User ID and Mobility User ID can differ.


Generating a License File from DMA

The "License File Upload" chapter of the Cisco Unified Communications Manager Administration Guide for Release 6.1(3x) does not describe that there is an alternate method to obtain a product license. In this method, the user generates the product license from Data Migration Assistant (DMA). Data Migration Assistant User Guide Release 6.1(3x) describes how to use this method to generate the file.

Upgrading to Cisco Unified Communications Manager Release 6.1(3) from Cisco Unified Communications  Manager 4.x Releases describes how to upload the file to Cisco Unified Communications Manager Release 6.1(3x).

Uploading a License File

The Uploading a License File section of the Cisco Unified Communications Manager Administration Guide does not instruct administrators to restart the Cisco CallManager service after uploading the license file. Administrators must restart the service for the license changes to take effect.

LDAP Authentication Chapter Omits Information on SSL Certificates and IP Addresses/Host Names

The "LDAP Authentication" chapter in the Cisco Unified Communications Manager Administration Guide does not contain the following information:

If you check the Use SSL check box in the LDAP Authentication window in Cisco Unified CM Administration, enter the IP address or the hostname that exists in the corporate directory SSL certificate in the Host Name or IP Address for Server field, which displays in the same window. If the certificate contains an IP address, enter the IP address. If the certificate contains the hostname, enter the hostname. If you do not enter the IP address or hostname exactly as it exists in the certificate, problems may occur for some applications; for example, applications that use CTIManager.


Tip You must upload the corporate directory SSL certificate into Cisco Unified CM by using the Cisco Unified Communications Operating System. For information on how to perform this task, refer to the Cisco Unified Communications Operating System Administration Guide.


Enterprise Parameters and Service Parameters Chapters Omit Information on Set to Default Button

The "Enterprise Parameters Configuration" and the "Service Parameters Configuration" chapters in the Cisco Unified Communications Manager Administration Guide do not contain information on the Set to Default button. Clicking the Set to Default button in either the Enterprise Parameters Configuration window or Service Parameter Configuration window updates all parameters to the suggested value, which is the default that displays on the right side of the parameter. If a parameter does not have a suggested value, Cisco Unified CM does not update the value when you click the Set to Default button; for example, the Phone URL Parameters in the Enterprise Parameters Configuration window do not display a suggested value, so clicking the Set to Default button does not change the parameter that you configured.

A warning message displays after you click the Set to Default button. If you click OK in the dialog box, Cisco Unified CM updates all parameters in the configuration window to the suggested value; that is, if the parameter has a suggested value.

Information About Using an SRV Destination Port for the CUP Publish Trunk Service Parameter

The "Service Parameters Configuration" chapter in the Cisco Unified Communications Manager Administration Guide omits the following information.

You can configure a SIP trunk to use a DNS SRV port on a Cisco Unified Presenceserver as a destination. If you use a SIP trunk with a DNS SRV destination to configure the CUP Publish Trunk service parameter and then modify the DNS record, you must restart all devices (phones) that previously published, so they point to the correct Cisco Unified Presenceserver destination.

To configure the CUP Publish Trunk parameter, navigate to System Service Parameters and choose Cisco CallManager service for the server that you want to configure.

For an overview of configuring Cisco Unified Presence with Cisco Unified CM, see "Cisco Unified Communications Manager and Cisco Unified Presence High-Level Architecture Overview" in the Cisco Unified Communications Manager System Guide.

For SIP Trunks Used with Multiple Device Pools, Configure an SRV Destination Port

The "Trunk Configuration" chapter in the Cisco Unified Communications Manager Administration Guide omits the following information.

For configuring SIP trunks when you have multiple device pools in a cluster, you must configure a destination address that is a DNS SRV destination port.

From Cisco Unified CM Administration, choose Device > Trunk. Click Find to choose the SIP trunk that you want to edit or click Add New to create a new trunk.

When the Trunk Configuration window displays, enter the name of a DNS SRV port for the Destination Address and check the Destination Address is an SRV Destination Port check box.

Information About Changing Region Bandwidth Settings When Video Calls Are Made

The following informational reference will get added to the Cisco Unified Communications Manager administration documentation:

Refer to the "Regions" subtopic under the "Administration Considerations" topic of the "IP Video Telephony" chapter of the Cisco Unified Communications Solution Reference Network Design (SRND) for the current release, which provides recommendations as to how the video bandwidth should be set for regions and locations, so the video portion of video calls will succeed, and the video calls will not get rejected nor set up as audio-only calls.

The reference will get added to the following topics of the Cisco Unified CM Administration documentation:

document: Cisco Unified Communications Manager Administration Guide
chapter: Location Configuration
topic: list of restrictions at the beginning of the chapter

document: Cisco Unified Communications Manager Administration Guide
chapter: Region Configuration
topic: list of limitations and restrictions at the beginning of the chapter

Information Omitted for Reroute Incoming Request to New Trunk Based on Setting

Instead of using the information for the Reroute Incoming Request to New Trunk Based on Setting in the "SIP Profile Configuration" chapter in the Cisco Unified Communications Manager Administration Guide/online help, use the following information when you configure the Reroute Incoming Request to New Trunk Based on Setting in the SIP Profile Configuration window in Cisco Unified Communications Manager Administration.

Cisco Unified Communications Manager only accepts calls from the SIP device whose IP address matches the destination address of the configured SIP trunk. In addition, the port on which the SIP message arrives must match the one that is configured on the SIP trunk. After Cisco Unified Communications Manager accepts the call, Cisco Unified Communications Manager uses the configuration for this setting to determine whether the call should get rerouted to another trunk.

From the drop-down list box, choose the method that Cisco Unified Communications Manager uses to identify the SIP trunk where the call gets rerouted:

Never— If the SIP trunk matches the IP address of the originating device, choose this option, which equals the default setting. Cisco Unified Communications Manager, which identifies the trunk by using the source IP address of the incoming packet and the signaling port number, does not route the call to a different (new) SIP trunk. The call occurs on the SIP trunk on which the call arrived.

Contact Info Header—If the SIP trunk uses a SIP proxy, choose this option. Cisco Unified Communications Manager parses the contact header in the incoming request and uses the IP address or domain name and signaling port number that is specified in the header to reroute the call to the SIP trunk that uses the IP address and port. If no SIP trunk is identified, the call occurs on the trunk on which the call arrived.

Call-Info Header with purpose=x-cisco-origIP—If the SIP trunk uses a Customer Voice Portal (CVP) or a Back-to-Back User Agent (B2BUA), choose this option. When the incoming request is received, Cisco Unified Communications Manager parses the Call-Info header, looks for the parameter, purpose=x-cisco-origIP, and uses the IP address or domain name and the signaling port number that is specified in the header to reroute the call to the SIP trunk that uses the IP address and port. If the parameter does not exist in the header or no SIP trunk is identified, the call occurs on the SIP trunk on which the call arrived.


Tip This setting does not work for SIP trunks that are connected to a Cisco Unified Presence proxy server or SIP trunks that are connected to originating gateways in different Cisco Unified CM groups.


Do Not Begin Starting and Ending Directory Numbers with a Zero (0)

In Table 3 of the "Cisco Unified Communications Manager Configuration" chapter, under Auto-registration Information, the descriptions of Starting Directory Number and Ending Directory Number omit the information that neither number should begin with a zero (0).

Time-of-Day Routing Chapter Omits Information About Defined Time Periods

The "Time-of-Day Routing" chapter of the Cisco Unified Communications Manager System Guide omits the following information.

If you defined a time period with a specific date, on that specified date, that period overrides other periods that are defined on a weekly basis.

Example:

Consider the following example:

A time period, afterofficehours, that is defined as 00:00 to 08:00 from Monday to Friday exists.

A time period, newyearseve, that is defined as 14:00 to 17:00 on December 31st exists.

In this case, on December 31st, the afterofficehours period will not be considered because it gets overriden by the more specific newyearseve period.

Cisco Unified Communications Manager System Guide

The following sections comprise documentation updates for the Cisco Unified Communications Manager System Guide.

Considerations for LDAP Port Configuration

RSVP Reservation Teardown for Shared-Line Calls

Application Server Configuration Not Required for Cisco Unity Connection 2.x

Unclear Documentation on Called Party Name Presentation

Automated Alternate Routing (AAR) Limitation with Remote Gateways

Documentation Does Not State That Line Group With No Members Is Not Supported for Routing Calls

Peer-to-Peer Image Distribution

Recommended Number of Devices in Device Pool

Throttling on SIP UDP Ports

Call Admission Control Bandwidth Example Correction

Directory Numbers Chapter Includes Incorrect Example for Shared Lines and Call Forward Busy Trigger

Clustering Chapter Omits Information about Subsequent (Subscriber) Node

Licensing Chapter Omits Information on Adjunct Licensing

Cisco TFTP Chapter Omits Configuration Tip on Centralized TFTP

Information About Changing Region Bandwidth Settings When Video Calls Are Made

Trunk Chapter Omits Restrictions for H.323/H.225 Trunks

Voice-Messaging Chapters Omits Fact That Cisco Messaging Interface Service Parameters Must Be Configured Per Node

RSVP Reservation Teardown for Shared-Line Calls

The Cisco Unified Communications Manager System Guide incorrectly documents the teardown of RSVP reservations that takes place when a shared-line call gets answered. The RSVP and Shared-Line Calls section of the "Resource Reservation Protocol" chapter provides an example that includes the following erroneous statement to describe the reservation teardown:

After phone B2 (in location 3) answers the shared-line call, the RSVP reservation between location 1 and location 3, as well as the reservation between location 1 and location 4, get torn down.

The correct information follows:

After phone B2 (in location 3) answers the shared-line call, the RSVP reservation between location 1 and location 2, as well as the reservation between location 1 and location 4, get torn down. Only the RSVP reservation between location 1 and location 3 remains established.

Considerations for LDAP Port Configuration


Tip The following information does not display in the LDAP chapters in the Cisco Unified Communications Manager Administration Guide and Cisco Unified Communications Manager System Guide.


When you configure the LDAP Port field in the LDAP Authentication window in Cisco Unified Communications Manager Administration, you specify the port number that the corporate directory uses to receive LDAP requests. How your corporate directory is configured determines which port number to enter in this field. For example, before you configure the LDAP Port field, determine whether your LDAP server acts as a Global Catalog server and whether your configuration requires LDAP over SSL. Consider entering one of the following port numbers:


Tip Your configuration may require that you enter a different port number than the numbers that are listed in the following bullets. Before you configure the LDAP Port field, contact the administrator of your directory server to determine the correct port number to enter.


LDAP Port For When the LDAP Server Is Not a Global Catalog Server

389—When SSL is not required. (This port number is the default that displays in the LDAP Port field.)

636—When SSL is required. (If you enter this port number, make sure that you check the Use SSL check box.)

LDAP Port For When the LDAP Server Is a Global Catalog Server

3268—When SSL is not required.

3269—When SSL is required. (If you enter this port number, make sure that you check the Use SSL check box.)

RSVP Reservation Teardown for Shared-Line Calls

The Cisco Unified Communications Manager System Guide incorrectly documents the teardown of RSVP reservations that takes place when a shared-line call gets answered. The RSVP and Shared-Line Calls section of the "Resource Reservation Protocol" chapter provides an example that includes the following erroneous statement to describe the reservation teardown:

After phone B2 (in location 3) answers the shared-line call, the RSVP reservation between location 1 and location 3, as well as the reservation between location 1 and location 4, get torn down.

The correct information follows:

After phone B2 (in location 3) answers the shared-line call, the RSVP reservation between location 1 and location 2, as well as the reservation between location 1 and location 4, get torn down. Only the RSVP reservation between location 1 and location 3 remains established.

Application Server Configuration Not Required for Cisco Unity Connection 2.x

The Cisco Unified Communications Manager System Guide suggests that you must configure a Cisco Unity Connection 2.x server in the Application Server Configuration window in Cisco Unified Communications Manager Administration to maintain an association with the Cisco Unity Connection 2.x server. In fact, configuring a Cisco Unity Connection 2.x server in Cisco Unified Communications Manager Administration creates a blank list of user templates for Cisco Unity Connection in Cisco Unified Communications Manager. Instead of configuring the application server in Cisco Unified Communications Manager Administration, create an AXL connection via Unity Connection 2.x, as described in the System Administration Guide for Cisco Unity Connection. Creating the AXL connection via Cisco Unity Connection 2.x pushes a list of valid user templates for Cisco Unity Connection 2.x to Cisco Unified Communications Manager.

Unclear Documentation on Called Party Name Presentation

The Cisco Unified Communications Manager System Guide provides unclear information about called party name presentation.

The Cisco Unified Communications System Guide states that when the Always Display Original Dialed Number service parameter is set to True, the originating phone displays only the dialed digits for the duration of the call. To clarify the documentation, if you set the Cisco CallManager service parameter to True, the name of the called party does not display on the phone of the calling party.

The Cisco Unified Communications Manager Administration Guide does not state that setting the Always Display Original Dialed Number service parameter to True impacts the configuration for the Alerting Name field. If you set the service parameter to True, the alerting name does not display on the calling phone; only the original dialed number displays.

Automated Alternate Routing (AAR) Limitation with Remote Gateways

AAR exhibits the limitation that calls that are routed over a remote gateway during a high-bandwidth situation fail, and the calls cannot be routed over the local gateway when AAR is used. This functionality proves to be important to customers who use Tail-End Hop Off (TEHO) for toll bypass.

Workaround Example

Use a specific partition for the TEHO in question.

In the following example, headquarters (HQ) has area code 408 and the Branch (BR1) has area code 919.

Configure as follows:

1. Create theTehoBr1forHQPt partition and assign this partition to the calling search space (CSS) of the HQ devices with a higher priority than the regular PSTN access uses.

2. Create the TehoBr1forHQRL route list and add the BR1 gateway route group to this route list as the first option and the HQ gateway as the second option.

3. Apply called party modification within the route list. In this case, apply predot called party modification for the BR1 route group, and apply predot and prefix 1919 called party modification for the HQ route group.

4. Ensure that the gateway does not perform called party modification.

5. Create a route pattern in the TehoBr1forHQPt partition.

6. Ensure that no called party modifications are applied in the route pattern.

Results

In an out-of-bandwidth situation, after Cisco Unified Communications Manager tries to allocate the first route group for TEHO (BR1 route group), Cisco Unified CM retries the second route group, at which point the system strips the 91919 string and replaces it with the 1919 string, which is suitable for long-distance dialing. Because the string is configured for use by the local gateway, less rerouting takes place.

AAR works on a per-external-phone-number-mask basis and cannot be processed for an external PSTN number because the system does not know the phone number mask of the PSTN number. This workaround provides AAR functionality and improves network resiliency.

Documentation Does Not State That Line Group With No Members Is Not Supported for Routing Calls

The Cisco Unified Communications Manager documentation does not state that you can configure an empty line group with no members (directory numbers) in Cisco Unified Communications Manager Administration. Although you can configure an empty line group with no members, Cisco Unified Communications Manager does not support this configuration for routing calls. If the line group contains no members, the hunt list stops hunting when the call gets routed to the empty line group. To avoid this situation, make sure that you configure at least one member in the line group.

Peer-to-Peer Image Distribution

Use the following information from the Cisco Unified Communications Manager System Guide, "Cisco Unified IP Phones" chapter, to replace the first paragraph of the Peer to Peer Image Distribution section.

The Peer Firmware Sharing feature provides these advantages in high-speed campus LAN settings:

Limits congestion on TFTP transfers to centralized TFTP servers.

Eliminates the need to manually control firmware upgrades.

Reduces phone downtime during upgrades when large numbers of devices are reset simultaneously.

In most conditions, the Peer Firmware Sharing feature optimizes firmware upgrades in branch deployment scenarios over bandwidth-limited WAN links.

When the feature is enabled, it allows the phone to discover like phones on the subnet that are requesting the files that make up the firmware image and to automatically assemble transfer hierarchies on a per-file basis. The individual files that make up the firmware image get retrieved from the TFTP server by only the root phone in the hierarchy and are then rapidly transferred down the transfer hierarchy to the other phones on the subnet using TCP connections.

For more information, see the applicable Cisco Unified IP Phone administration guide.

Recommended Number of Devices in Device Pool

The following information from the Cisco Unified Communications Manager System Guide, "Redundancy" chapter, needs clarification.

You associate devices with a Cisco Unified Communications Manager group by using device pools. You can assign each device to one device pool and associate each device pool with one Cisco Unified Communications Manager group. You can combine the groups and device pools in various ways to achieve the desired level of redundancy.


Note A server can exist in a single device pool and can support up to 7500 devices (high-end servers only). See your Cisco representative for information on the types of servers that Cisco Unified Communications Manager supports.


Throttling on SIP UDP Ports

The "SIP and Cisco Unified Communications Manager" chapter in the Cisco Unified Communications Manager System Guide requires this update for SIP UDP port throttling.

SIP UDP port throttle thresholds help prevent Denial of Service (DOS) attacks from SIP trunks and SIP stations. When the incoming packet rate exceeds the configured threshold for a SIP station or SIP trunk UDP port, Cisco Unified Communications Manager throttles (drops) the packets that exceed the threshold.

The SIP Service Parameters section of this chapter does not include the following parameters for SIP UDP throttling.

SIP UDP Port Throttling Thresholds

These throttle thresholds apply only to SIP UDP ports and do not affect SIP TCP or TLS ports.


Tip Be aware that the enterprise parameter Denial-of-Service Protection Flag must be set to True for these parameter values to take effect.


Table 1 describes the configurable threshold values:

Table 1 SIP UDP Port Throttling Thresholds

Service Parameter
Default Value
Range
Definition

SIP Station UDP Port Throttle Threshold

50

10-500

The SIP Station UDP Port Throttle Threshold parameter defines the maximum incoming packets per second that Cisco Unified Communications Manager can receive from a single (unique) IP address that is directed at the SIP station UDP port.

When the threshold is exceeded, Cisco Unified Communications Manager throttles (drops) the packets that exceed the threshold.

SIP Trunk UDP Port Throttle Threshold

200

10-500

The SIP Trunk UDP Port Throttle Threshold defines the maximum incoming packets per second that a SIP trunk can receive from a single (unique) IP address that is directed at the SIP trunk UDP port.

When the threshold is exceeded, Cisco Unified Communications Manager throttles (drops) the packets that exceed the threshold.


The Incoming Port description in Table 15-1 in the Cisco Unified Communications Manager Security Guide requires this addition for SIP UDP Port Throttling:


Tip If the incoming packet rate on a SIP trunk UDP port from a single IP address exceeds the configured SIP Trunk UDP Port Throttle Threshold during normal traffic, reconfigure the threshold. When a SIP trunk and SIP station share the same incoming UDP port, Cisco Unified Communications Manager throttles packets based on the higher of the two service parameter values. You must restart the Cisco CallManager service for changes to this parameter to take effect.


Call Admission Control Bandwidth Example Correction

The "Call Admission Control" chapter of the Cisco Unified Communications Manager System Guide incorrectly describes the amount of bandwidth that is consumed in an example locations-type call admission control scenario.

Original explanation:

Cisco Unified Communications Manager continues to admit new calls to a link as long as sufficient bandwidth is still available. Thus, if the link to the Austin location in the example has 160 kb/s of available bandwidth, that link can support one G.711 call at 80 kb/s (in each direction), three G.723 or G.729 calls at 24 kb/s each (in each direction), or two GSM calls at 29 kb/s each (in each direction). If any additional calls try to exceed the bandwidth limit, the system rejects them, the calling party receives reorder tone, and a text message displays on the phone.

Correct explanation:

Cisco Unified Communications Manager continues to admit new calls to a link as long as sufficient bandwidth is still available. Thus, if the link to the Austin location in the example has 160 kb/s of available bandwidth, that link can support two G.711 calls at 80 kb/s each, six G.723 or G.729 calls at 24 kb/s each, or five GSM calls at 29 kb/s each. If any additional calls try to exceed the bandwidth limit, the system rejects them, the calling party receives reorder tone, and a text message displays on the phone

Directory Numbers Chapter Includes Incorrect Example for Shared Lines and Call Forward Busy Trigger

The "Understanding Directory Numbers" chapter in the Cisco Unified Communications Manager System Guide includes incorrect example for shared lines and call forward busy trigger. Use the following information instead of the information in the guide:

Devices with shared-line appearance support the Call Forward Busy Trigger and the Maximum Number of Calls settings. You can configure Call Forward Busy Trigger per line appearance, but the configuration cannot exceed the maximum number call setting for that directory number.

The following example demonstrates how three Cisco Unified IP Phones with the same shared-line appearance, directory number 2000, use Call Forward Busy Trigger and Maximum Number of Calls settings. This example assumes that two calls occur. The following values configuration applies for the devices:

Cisco Unified IP Phone 1—Configured for a maximum call value of 1 and busy trigger value of 1

Cisco Unified IP Phone 2—Configured for a maximum call value of 1 and busy trigger value of 1

Cisco Unified IP Phone 3—Configured a for maximum call value of 2 and busy trigger value of 2

When Cisco Unified IP Phone User 1 dials directory number 2000 for the first call, all three devices ring. The user for Cisco Unified IP Phone 3 picks up the call, and Cisco Unified IP Phones 1 and 2 go to remote in use. When the user for Cisco Unified IP Phone 3 puts the call on hold, user can retrieve the call from the Cisco Unified IP Phone 1 or Cisco Unified IP Phone 2. When User 2 dials directory number 2000 for the second call, only Cisco Unified IP Phone 3 rings.

Clustering Chapter Omits Information about Subsequent (Subscriber) Node

The "Clustering" chapter in the Cisco Unified Communications Manager System Guide does not state that Cisco Unified CM uses the subsequent (subscriber) node for database replication; that is, after you install Cisco Unified CM on the subsequent node, the node contains a replicate of the database that exists on the first node (publisher).


Tip To ensure that the subsequent node replicates the database of the first node, you must add the subsequent node to the Server Configuration window in Cisco Unified CM Administration on the first node before you install Cisco Unified CM on the server.


You can also use the subsequent node for call-processing redundancy and for load balancing. For information on how to configure call-processing redundancy and load balancing in Cisco Unified CM Administration, refer to the Cisco Unified Communications Manager Administration Guide and the Cisco Unified Communications Manager System Guide.

Licensing Chapter Omits Information on Adjunct Licensing

The "Licensing" chapter in the Cisco Unified Communications Manager System Guide omits the fact that an error occurs when you configure an application, for example, Cisco IP Communicator, as the adjunct device, and the adjunct device requires more device license units (DLUs) than the primary device; for example, the Cisco Unified IP Phone 7906.

With adjunct licensing, fewer device license units (DLUs) get consumed for adjunct (secondary) devices, such as Cisco IP Communicator, Cisco Unified Personal Communicator, and Cisco Unified Mobile Communicator, when these applications get used with a Cisco Unified IP Phone 79xx, which serves as the primary device. For adjunct licensing to work, the adjunct device must consume fewer or the same number of DLUs as the primary device.

For example, if you configure Cisco IP Communicator as a secondary device for the Cisco Unified IP Phone 7970, Cisco IP Communicator consumes only 1 DLU. Adjunct licensing works because the Cisco Unified IP Phone 7970 consumes 5 DLUs, and Cisco IP Communicator consumes 3 DLUs.

In another example, if you configure Cisco IP Communicator as a secondary device for the Cisco Unified IP Phone 7906, adjunct licensing fails because the Cisco Unified IP Phone 7906 consumes 2 DLUs, and Cisco IP Communicator consumes 3 DLUs.

To ensure that Cisco Unified Communications Manager treats Cisco IP Communicator, Cisco Unified Personal Communicator, and Cisco Unified Mobile Communicator as adjunct (secondary) devices, configure the Primary Phone setting in the Phone Configuration window for Cisco IP Communicator, Cisco Unified Personal Communicator, and Cisco Unified Mobile Communicator, as described in the "Phone Configuration" chapter in the Cisco Unified Communications Manager Administration Guide.

Cisco TFTP Chapter Omits Configuration Tip on Centralized TFTP

The "Cisco TFTP" chapter in the Cisco Unified Communications Manager System Guide does not contain the following information on configuring centralized TFTP:

For centralized TFTP configurations, ensure that the main TFTP server exists in the cluster that runs the highest version of Cisco Unified Communications Manager; for example, if you are using a centralized TFTP server between a compatible Cisco Unified CallManager 4.X cluster and a Cisco Unified Communications Manager 6.X cluster, ensure that your main TFTP server exists in the Cisco Unified Communications Manager 6.X cluster. If the main TFTP server exists in the cluster that runs the lower version of Cisco Unified Communications Manager, the phones use the locale files from the lower version of Cisco Unified Communications Manager, which can cause issues with the phone; for example, the phone displays Undefined or ??? for the Do Not Disturb feature instead of displaying that DND is active. These errors display on the phone because the locale files that are served to the phones from the main cluster do not include the localized phrases.

Information About Changing Region Bandwidth Settings When Video Calls Are Made

The following informational reference will get added to the Cisco Unified Communications Manager administration documentation:

Refer to the Regions subtopic under the Administration Considerations topic of the "IP Video Telephony" chapter of the Cisco Unified Communications Solution Reference Network Design (SRND) for the current release, which provides recommendations as to how the video bandwidth should be set for regions and locations, so the video portion of video calls will succeed, and the video calls will not get rejected nor set up as audio-only calls.

The reference will get added to the following topics of the Cisco Unified CM Administration documentation:

document: Cisco Unified Communications Manager System Guide
chapter: Understanding Video Telephony
topic: Bandwidth Management

document: Cisco Unified Communications Manager System Guide
chapter: Call Admission Control
topic: Bandwidth Calculations

Trunk Chapter Omits Restrictions for H.323/H.225 Trunks

The "Understanding Cisco Unified Communications Manager Trunks Types" chapter in the Cisco Unified Communications Manager System Guide does not contain the following restriction for H.323/H.225 trunks.

You cannot configure more than one H.323 trunk of any type (gatekeeper- or non-gatekeeper-controlled) between the same clusters. Configuring more than one H.323 trunk can break inbound calls because Cisco Unified Communications Manager uses the received IP address to choose which trunk handles the call. If you configure more than one H.323 trunk between the same clusters, Cisco Unified Communications Manager may choose the wrong trunk device when a call gets processed. To avoid this issue, Cisco Unified Communications Manager checks the following configuration:

Whether the remote Cisco Unified Communications Manager IP address that is configured for the trunk is the same as another remote Cisco Unified Communications Manager IP address for a configured trunk.

Whether a remote Cisco Unified Communications Manager hostname for a configured trunk is the same as another remote Cisco Unified Communications Manager hostname for a configured trunk.

If you configure one trunk with an IP address, and you configure another trunk with a hostname that resolves to the same IP address, Cisco Unified Communications Manager does not detect this configuration, which causes duplicate trunk configuration and problems with call processing.

Cisco Unified Communications Manager cannot detect the configuration of a gatekeeper-controlled trunk and a non-gatekeeper-controlled trunk or the configuration of multiple gatekeeper-controlled trunks between the same Cisco Unified Communications Manager clusters. Additionally, Cisco Unified Communications Manager cannot detect the configuration of a gatekeeper-controlled H.323 trunk with the configuration of an H.323 gateway that is accessible from that same gatekeeper-controlled H.323 trunk. These configurations can cause problems for call processing, so carefully configure your trunks in Cisco Unified Communications Manager to avoid these issues.

Voice-Messaging Chapters Omits Fact That Cisco Messaging Interface Service Parameters Must Be Configured Per Node

The voice-messaging chapters in the Cisco Unified Communications Manager System Guide do not state that you must configure the following Cisco Messaging Interface service parameters per node if you use the CMI service to deploy multiple third-party voice-messaging systems in the same Cisco Unified Communications Manager cluster.

CallManager Name

Backup CallManager Name

Voice Mail DN

Voice Mail Partition

Alternate DN

Alternate DN Partition

After you configure these parameters in the Service Parameters Configuration window, a message displays that warns that you must configure the value on each node in the cluster to achieve clusterwide support.

Information About Changing Region Bandwidth Settings When Video Calls Are Made

The following informational reference will get added to the Cisco Unified Communications Manager administration documentation:

Refer to the Regions subtopic under the Administration Considerations topic of the "IP Video Telephony" chapter of the Cisco Unified Communications Solution Reference Network Design (SRND) for the current release, which provides recommendations as to how the video bandwidth should be set for regions and locations, so the video portion of video calls will succeed, and the video calls will not get rejected nor set up as audio-only calls.

The reference will get added to the following topics of the Cisco Unified CM Administration documentation:

document: Cisco Unified Communications Manager System Guide
chapter: Understanding Video Telephony
topic: Bandwidth Management

document: Cisco Unified Communications Manager System Guide
chapter: Call Admission Control
topic: Bandwidth Calculations

Cisco Unified Communications Manager Features and Services Guide

The following sections comprise documentation updates for the Cisco Unified Communications Manager Features and Services Guide.

Setting the Service Parameters for Cisco Unified Communications Manager Assistant

Call Park Range

Supported Call States

CTI and Attendant Console Chapters Omit Information on CTI Monitored Lines

Incorrect Information on How to Install Assistant Console Application

Do Not Disturb Feature Priority

Extension Mobility Successful Authentication Cache

Devices Associated with the Attendant Console Application User

CTI Devices Do Not Support Multicast Music on Hold (MOH)

Attendant Console Phones Do Not Support the Intercom Feature

Unclear Documentation on How Locales Work for Mobile Voice Access

Mobile Connect and Mobile Voice Access Chapter Omits Information About Configuring the Mobile Voice Access Media Resource

cBarge Chapter Omits Information on Shared Line Restriction for Conferences

Cisco Unified IP Phones Supporting Call Back with PLKs

Intercom Configuration

Extension Mobility Redundancy

Number of Login or Logout Operations That Cisco Extension Mobility Supports

None Option Not Documented for DND Incoming Call Alert Setting

Mobile Connect and Mobile Voice Access Chapter Contains Incorrect Information About Configuring an H.323 Gateway for System Remote Access by Using Hairpinning

Mobile Connect and Mobile Voice Access Chapter Contains Incorrect Information About Configuring an H.323 Gateway for System Remote Access by Using PRI

Cisco Extension Mobility Chapter Error

Barge and Security

Barge with Shared Conference Bridge

Number of Alphanumeric Characters That Are Allowed in the Pickup Group Name Field

Incorrect Information on How to Install Assistant Console Application

Documentation Does Not Include the Latest List of Supported Phone Models

Do Not Disturb Documentation Provides Incorrect Information About Phone Tone

Destination Number in Remote Destination Configuration Window

Cisco Extension Mobility Supplemental Information

Cisco Unified IP Phones Supporting Barge

Cisco Unified IP Phones Supporting Call Back

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.


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.

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

CTI and Attendant Console Chapters Omit Information on CTI Monitored Lines

To calculate the number of CTI monitored lines in a system, use the following formula:

number of pilot point DNs + (number of clients open * number of directory numbers per phone) + (number of parked directory numbers * number of open clients) = CTI Monitored Lines

Incorrect Information on How to Install Assistant Console Application

The Cisco Unified Communications Manager Features and Services Guide incorrectly describes how to obtain the assistant console application for Cisco Unified Communications Manager Assistant. In release 6.1(1a), the assistant no longer obtains the assistant console application via the URL that is listed in the guide. Instead, the assistant must download the Cisco Unified Communications Manager Assistant plug-in from Cisco Unified Communications Manager Administration (choose Applications > Plugins), as described in the "Cisco Unified Communications Manager Assistant User Guide" section.

The Cisco Unified Communications Manager Features and Services Guide does not state that the assistant console application supports Windows Vista.

Disregard the entire Assistant Console Dialog Options section in the Cisco Unified Communications Manager Features and Services Guide. Instead, use the information in the "Cisco Unified Communications Manager Assistant User Guide" section.

Do Not Disturb Feature Priority

On Cisco Unified IP Phones, the text message that indicates the Do Not Disturb (DND) feature is active takes priority over the text message that indicates the user has new voicemail messages, which allows the user to know when DND is active. However, the text message that indicates the Call Forward All feature is active has a higher priority than DND.

Extension Mobility Successful Authentication Cache

The Extension Mobility application maintains a cache of all logged on user information for 2 minutes. If a request comes to extension mobility regarding a user who is represented in the cache, the user gets validated with information from the cache. This means that, if a user changes the password, logs out, and then logs back in within 2 minutes, both the old and new passwords get recognized.

Devices Associated with the Attendant Console Application User

You must always enable the superprovider feature by associating the ac application user with the user group "Standard CTI Allow Control of All Devices" and must not associate any devices with the Cisco Unified Communications Manager Attendant Console ac application user.


Caution System instability can occur if you associate devices to the Cisco Unified Communications Manager Attendant Console application user.

CTI Devices Do Not Support Multicast Music on Hold (MOH)

CTI devices do not support the multicast Music on Hold feature. If a CTI device is configured with a multicast MOH device in the media resource group list of the CTI device, call control issues may result. CTI devices do not support multicast media streaming.

Attendant Console Phones Do Not Support the Intercom Feature

The Cisco Unified Communications Manager Attendant Console does not support the intercom feature. The attendant console GUI shows intercom and other lines but does not display the hunt group member line when the intercom feature is configured on a phone that is a member of a hunt group.

Unclear Documentation on How Locales Work for Mobile Voice Access

The Cisco Unified Communications Manager Features and Services Guide does not address how locales work for mobile voice access. Mobile voice access uses the first locale that displays in the Selected Locales pane in the Mobile Voice Access window in Cisco Unified Communications Manager Administration (Media Resources > Mobile Voice Access) when the IVR is used. For example, if English United States displays first in the Selected Locales pane, the Cisco Unified Mobility user receives English when the IVR is used during a call.

Mobile Connect and Mobile Voice Access Chapter Omits Information About Configuring the Mobile Voice Access Media Resource

The "Mobile Connect and Mobile Voice Access" chapter in the Cisco Unified Communications Manager Features and Services Guide omits the following information about configuring the mobile voice access media resource:

Be aware that this configuration is required for making calls with the Mobile Voice Access feature. After the gateway collects the required digits from the user to make a call, the call gets transferred to the DN that is configured in this window. This DN can represent an internal DN to Cisco Unified Communications Manager, and the end user does not need to know the DN. The administrator must configure a dial-peer, so the MVA service can transfer the call from the gateway to this DN. Also, ensure this DN is placed in a partition where the inbound calling search space (CSS) of the gateway or the remote destination profile CSS can reach the DN, as configured in the Inbound Calling Search Space for Remote Destination service parameter in the Clusterwide Parameters (System - Mobility) pane.

cBarge Chapter Omits Information on Shared Line Restriction for Conferences

The "Barge and Privacy" chapter in the Cisco Unified Communications Manager Features and Services Guide does not contain the following cBarge restriction for shared lines and conferences:

If the number of shared-line users in the conference is equal to or greater than the configuration for the Maximum Number of Calls setting for the device from which you are attempting to barge, the phone displays the message, Error Past Limit.


Note The "Understanding Directory Numbers" chapter in the Cisco Unified Communications Manager System Guide does not contain the previous information in the shared lines section.


Cisco Unified IP Phones Supporting Call Back with PLKs

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

Many Cisco Unified IP Phone support the Cisco Call Back feature by using the programmable line key (PLK). The following URL lists the phone documentation that is available for the various Cisco Unified IP Phones:

http://www.cisco.com/en/US/products/hw/phones/ps379/tsd_products_support_series_home.html

Intercom Configuration

The "Intercom" chapter in the Cisco Unified Communications Manager Features and Services Guide omits the following steps that should be taken to successfully install the intercom feature.

Procedure


Step 1 From Cisco Unified Communications Manager Administration, click Call Routing > Intercom.

a. Create the intercom partition.


Note When you add a new intercom partition, Cisco Unified Communications Manager automatically adds a new intercom calling search space that contains only the new partition. You can modify the new intercom calling search space later.


b. Create the intercom directory number.


Note Be aware that intercom partition and calling search space cannot be mixed with partition and calling search space for regular lines.


Step 2 Click Device > Device Settings > Phone Button Template and add the intercom line to an existing phone button template or create new template.


Note Be aware that the intercom line cannot be configured as the primary line.


Step 3 Click Device -> Phone and assign an intercom directory number to the intercom line.

Step 4 Configure the intercom directory number and set up intercom speed dial, if desired.


Note You can configure the intercom line with a predefined destination (speed dial) to allow fast access.



Where to Find More Information

The "Intercom" chapter of the Cisco Unified Communications Manager Features and Services Guide Release 6.1(1)

The "Intercom Directory Number Configuration" chapter of the Cisco Unified Communications Manager Administration Guide Release 6.1(1)

The "Intercom Calling Search Space Configuration" chapter of the Cisco Unified Communications Manager Administration Guide Release 6.1(1)

The "Intercom Partition Configuration" chapter of the Cisco Unified Communications Manager Administration Guide Release 6.1(1)

The "Phone Button Template Configuration" chapter of the Cisco Unified Communications Manager Administration Guide Release 6.1(1)

Extension Mobility Redundancy

The "Extension Mobility" chapter in the Cisco Unified Communications Manager Features and Services Guide omits the following statement:

For information on extension mobility redundancy, see the "Cisco Unified Communications Manager Applications" chapter of the latest Cisco Unified Communications SRND that is located at http://www.cisco.com/go/srnd.

Number of Login or Logout Operations That Cisco Extension Mobility Supports

The Cisco Unified Communications Manager Features and Services Guide omits the maximum number of login or logout operations that Cisco Extension Mobility supports for Cisco Unified Communications Manager Release 6.1(1a). The correct guideline follows:

Cisco Extension Mobility supports a maximum of 250 login or logout operations per minute (or 15,000 operations per hour). Remember that these operations are sequential, not concurrent. (Some devices may support more login or logout operations per hour.)

None Option Not Documented for DND Incoming Call Alert Setting

The Cisco Unified Communications Manager Administration Guide and Cisco Unified Communications Manager Features and Services Guide ("Do Not Disturb" chapter) do not describe the None option that displays in the DND Incoming Call Alert drop-down list box.


Tip The DND Incoming Call Alert drop-down list box displays in the Phone Configuration, Default Device Profile Configuration, and the Device Profile Configuration windows in Cisco Unified Communications Manager Administration.


The following information describes the DND Incoming Call Alert drop-down list box:

When you enable the DND Ringer Off option, this parameter specifies how a call displays on a phone. From the drop-down list, choose one of the following options:

None—For an incoming call, the device uses the settings that are defined in the common phone profile.

Disable—This option disables both beep and flash notification of a call, but incoming call information still gets displayed.

Beep Only—For an incoming call, this option causes the phone to play a beep tone only.

Flash Only—For an incoming call, this option causes the phone to display a flash alert only.

Mobile Connect and Mobile Voice Access Chapter Contains Incorrect Information About Configuring an H.323 Gateway for System Remote Access by Using Hairpinning

In the "Mobile Connect and Mobile Voice Access" chapter in the Cisco Unified Communications Manager Features and Services Guide, the procedure for configuring an H.323 gateway for system remote access by using hairpinning contains minor errors. The following procedure contains the corrected steps.

Procedure


Step 1 Load the VXML application from the Cisco Unified Communications Manager server (Publisher).

Sample configuration for IOS Version 12.3 (13) and later

application service CCM

http://<Unified CM cluster Publisher IP Addr>:8080/ccmivr/pages/IVRMainpage.vxml

Sample configuration before IOS Version 12.3(12)

call application voice Unified CCM

http://<Unified CM cluster Publisher IP Addr>:8080/ccmivr/pages/IVRMainpage.vxml


Note Although VXML was added in Version 12.2(11), Versions 12.3(8), 12.3(9), 12.3(14)T1, and 12.2(15) have VXML issues, and you should not use them.


Step 2 Configure the dial-peer to associate mobile connect application with system remote access.

Sample configuration for IOS 12.3(13) and later

dial-peer voice 1234567 voip

service CCM

incoming called-number 1234567

codec g711u

session target ipv4:<ip_address of call manager>

Sample configuration for IOS 12.3(12) and earlier

dial-peer voice 1234567 voip

application CCM

incoming called-number 1234567

codec g711u

session target ipv4:<ip_address of call manager>

Step 3 Add a dial-peer for transferring calls to the Mobile Voice Access DN that is configured in the Configuring Mobile Voice Access Media Resources section of the "Mobile Connect and Mobile Voice Access" chapter of the Cisco Unified Communications Manager Features and Services Guide.

Sample configuration for primary Cisco Communications Manager

dial-peer voice 101 voip

preference 1

destination-pattern <Mobile Voice Access DN>


Note This step specifies the Mobile Voice Access DN that is configured with the Media Resources > Mobile Voice Access menu option. If a generic dial-peer is already configured to terminate the calls and is consistent with the Mobile Voice Access DN, you do not need to perform this step.


session target ipv4:10.1.30.3

voice-class h323 1

codec g711ulaw

dtmf-relay h245-alphanumeric

no vad

Sample configuration for secondary Cisco Communications Manager (if needed):

dial-peer voice 102 voip

preference 2

destination-pattern <Mobile Voice Access DN>


Note This step specifies the Mobile Voice Access DN that is configured with the Media Resources > Mobile Voice Access menu option. If a generic dial-peer is already configured to terminate the calls and is consistent with the Mobile Voice Access DN, you do not need to perform this step.


session target ipv4:10.1.30.4

voice-class h323 1

codec g711ulaw

dtmf-relay h245-alphanumeric

no vad

Step 4 Configure hairpin.

voice service voip

allow-connections h323 to h323


Mobile Connect and Mobile Voice Access Chapter Contains Incorrect Information About Configuring an H.323 Gateway for System Remote Access by Using PRI

In the "Mobile Connect and Mobile Voice Access" chapter in the Cisco Unified Communications Manager Features and Services Guide, the procedure for configuring an H.323 gateway for system remote access by using PRI contains minor errors. The following procedure contains the corrected steps.

Procedure


Step 1 Configure the T1/E1 controller for PRI from PSTN.

Sample configuration

controller T1 1/0

framing esf

linecode b8zs

pri-group timeslots 1-24

Step 2 Configure the serial interface for the PRI (T1/E1).

Sample configuration

interface Serial 1/0:23

ip address none

logging event link-status none

isdn switch-type primary 4ess

isdn incoming-voice voice

isdn bchan-number-order ascending

no cdp enable

Step 3 Load the VXML application from the Cisco Unified Communications Manager server (Publisher).

Sample configuration for IOS Version 12.3 (13) and later

application service CCM

http://<Unified CM cluster Publisher IP Addr>:8080/ccmivr/pages/IVRMainpage.vxml

Sample configuration before IOS Version 12.3(12)

call application voice Unified CCM

http://<Unified CM cluster Publisher IP Addr>:8080/ccmivr/pages/IVRMainpage.vxml


Note Although VXML was added in Version 12.2(11), Versions 12.3(8), 12.3(9), 12.3(14)T1, and 12.2(15) have VXML issues, and you should not use them.


Step 4 Configure the dial peer to associate Mobile Connect application with system remote access.

Sample configuration for IOS 12.3(13) and later

dial-peer voice 58888 pots

service CCM (Mobile Connect VXML application)

incoming called-number 58888

no digit-strip

Sample configuration for IOS 12.3(12) and earlier

dial-peer voice 100 pots

application CCM (Mobile Connect VXML application)

incoming called-number 58888 (where 58888 represents the Mobile Voice Access number)

no digit-strip

Step 5 Add a dial-peer to transfer the calls to the Mobile Voice Access DN that is configured in the Configuring Mobile Voice Access Media Resources section of the Mobile Connect and Mobile Voice Access chapter of the Cisco Unified Communications Manager Features and Services Guide.

Sample configuration for primary Cisco Unified Communications Manager

dial-peer voice 101 voip

preference 1

destination-pattern <Mobile Voice Access DN>


Note This step specifies the Mobile Voice Access DN that is configured with the Media Resources > Mobile Voice Access menu option. If a generic dial-peer is already configured to terminate the calls and is consistent with the Mobile Voice Access DN, you do not need to perform this step.


session target ipv4:10.1.30.3

codec g711ulaw

dtmf-relay h245-alphanumeric

no vad

Sample configuration for secondary Cisco Unified Communications Manager (if needed)

dial-peer voice 102 voip

preference 2

destination-pattern <Mobile Voice Access DN>


Note This step specifies the Mobile Voice Access DN that is configured with the Media Resources > Mobile Voice Access menu option. If a generic dial-peer is already configured to terminate the calls and is consistent with the Mobile Voice Access DN, you do not need to perform this step.


session target ipv4:10.1.30.4

codec g711ulaw

dtmf-relay h245-alphanumeric

no vad


Cisco Extension Mobility Chapter Error

The "Cisco Extension Mobility" chapter in the Cisco Unified Communications Manager Features and Services Guide states that you can configure the Module 1 and Module 2 drop-down list boxes in the Default Device Profile Configuration window, which is not true.

Barge and Security

The Restrictions section of the "Barge and Privacy" chapter in the Cisco Unified Communications Manager Features and Services Guide misstates the capabilities of encrypted phones to accept barge requests from unencrypted phones or from calls with a lower security level in Cisco Unified Communications Manager Release 6.1(1a).

The correct information follows:

Any phone can barge in to any existing call regardless of security level. An icon on the phone indicates the lowest security level of all participants:

A shield icon represents the authenticated security level

A lock icon represents the encrypted security level

If no icon exists, that means that the call has no security level

Barge with Shared Conference Bridge

The "Barge and Privacy" chapter in the Cisco Unified Communications Manager Features and Services Guide does not correctly describe the process for configuration of the Barge with Shared Conference Bridge feature. The Standard User and Standard Feature softkey templates do not support cBarge and cannot be modified. The following corrections apply to the Barge with Shared Conference Bridge (cBarge) Configuration Checklist (table).

Replace Step 1 with the following information:

To create a softkey template that includes cBarge, make a copy of the Standard Feature softkey template. Modify this user-named copy to add the Conference Barge (cBarge) softkey to the Selected Softkeys in the Remote in Use call state. See the Adding Non-Standard Softkey Templates section in the "Device Configuration" chapter of the Cisco Unified Communications Manager Administration Guide for more information on creating copies of standard softkey templates.

After Step 3, insert the following sentence:

Disable privacy on phones to allow cBarge.

Number of Alphanumeric Characters That Are Allowed in the Pickup Group Name Field

The Cisco Unified Communications Manager Features and Services Guide incorrectly states that you can enter up to 30 alphanumeric characters in the Pickup Group Name field in the Call Pickup Group Configuration window. The guide should state that you can enter up to 100 characters in the Pickup Group Name field.

Documentation Does Not Include the Latest List of Supported Phone Models

The Cisco Unified Communications Manager Features and Services Guide may not contain the latest list of supported Cisco Unified IP Phones. To identify whether the phone supports a feature, refer to the phone documentation that supports this version of Cisco Unified Communications Manager and the phone model.

Do Not Disturb Documentation Provides Incorrect Information About Phone Tone

The "Do Not Disturb" chapter in the Cisco Unified Communications Manager Features and Services Guide states that the phone periodically plays a tone to remind you that DND is active. The phone does not play a tone to remind you that DND is active. Instead, the status on the phone displays Do Not Disturb is active.

Destination Number in Remote Destination Configuration Window

The "Mobile Connect and Mobile Voice Access" chapter of the Cisco Unified Communications Manager Features and Services Guide incorrectly documents the Destination Number field of the Remote Destination Configuration window. In the Remote Destination Configuration Settings section, the following statements in the Destination Number description require correction:

The maximum number of digits that are allowed in the Destination Number specifies 24, not 20 as stated.

The current release does not support the digits A through D.

This field supports the digits * (asterisk) and # (pound sign).

Cisco Extension Mobility Supplemental Information

Consider the following information as supplementary to the information that is provided in the "Cisco Extension Mobility" chapter of the Cisco Unified Communications Manager Features and Services Guide:

When you subscribe devices to the Extension Mobility IP Phone Service (Device > Device Settings > Phone Services), an error results if you click Update Subscriptions more than once. When you update many phones, it can take some time for the changes to propagate to all devices. You must click Update Subscriptions only once and wait for this propagation to complete.

Cisco Unified IP Phones Supporting Barge

Replace the following out-of-date statement in the "Barge and Privacy" chapter of the Cisco Unified Communications Manager Features and Services Guide:

Original statement:

Some Cisco Unified IP Phones (such as 7940 and 7960) have the built-in conference bridge capability, which barge uses.

Updated information:

Most Cisco Unified IP Phones include the built-in conference bridge capability, which barge uses.

Cisco Unified IP Phones Supporting Call Back

The Interactions and Restrictions section in the "Cisco Call Back" chapter of the Cisco Unified Communications Manager Features and Services Guide did not get updated with regard to the specific Cisco Unified Communications Manager IP Phones that support Cisco Call Back.

The following URL lists the phone documentation that is available for the various Cisco Unified IP Phones:

http://www.cisco.com/en/US/products/hw/phones/ps379/tsd_products_support_series_home.html

To check which phones support Cisco Call Back, refer to the phone administration guide that supports the phone and refer to the Telephony Features for the Cisco Unified IP Phone table.

To check which phones also support Cisco Call Back with PLKs, refer to the phone user guide that supports the phone and refer to the Understanding Feature Availability section.

Cisco Unified Communications Manager Security Guide

The following sections comprise documentation updates for the Cisco Unified Communications Manager Security Guide.

Support for Certificates from External CAs

CAPF System Interactions and Requirements

Security Icons and Encryption

Software Conference Bridge Not Supported

Support for Certificates from External CAs

This section in the "Security Overview" chapter of the Cisco Unified Communications Manager Security Guide updates the existing sentence to include IPSec and Tomcat, as follows: Customers who currently use third-party CAs should use the CSR mechanism to issue certificates for Communications Manager, CAPF, IPSec, and Tomcat.

CAPF System Interactions and Requirements

This section in the "Using the Certificate Authority Proxy Function" chapter of the Cisco Unified Communications Manager Security Guide requires this new item:

If a secure phone gets moved to another cluster, the Cisco Unified Communications Manager will not trust the LSC certificate that the phone sends because it was issued by another CAPF whose certificate is not in the CTL file. To enable the secure phone to register, delete the existing CTL file by using the Deleting the CTL File on the Cisco Unified IP Phone procedure in the Cisco Unified Communications Manager Security Guide. You can then use the Upgrade/Install option to install a new LSC certificate with the new CAPF and reset the phone for the new CTL file (or use the MIC). Use the Delete option in the CAPF section on the Phone Configuration window to delete the existing LSC before the phones are moved.

Security Icons and Encryption

This subsection of the Restrictions section in the "Security Overview" chapter in the Cisco Unified Communications Manager Security Guide requires this addition:

If a call from an encrypted phone over a SIP trunk gets transferred to an encrypted phone in its own cluster, the call does not get encrypted, and the lock icon does not display even though the encrypted phones exist in the same secure cluster.

Software Conference Bridge Not Supported

The "Configuring Secure Conference Resources" chapter in the Cisco Unified Communications Manager Security Guide requires this addition: Due to the performance impact to Cisco Unified Communications Manager processing, secure conferencing does not get supported on software conference bridge.

Cisco Unified Communications Manager XML Developers Guide for Release 6.0(1)

The information in Cisco Unified Communications Manager XML Developers Guide for Release 6.0(1) applies to Release 6.1(1a), with the following updates:

In the AXL Versioning Support section, the sample AXL request that carries version information now displays as follows:

POST /axl/ HTTP/1.0
Host:10.77.31.194:8443
Authorization: Basic Q0NNQWRtaW5pc3RyYXRvcjpjaXNjb19jaXNjbw==
Accept: text/*
Content-type: text/xml
SOAPAction: "CUCM:DB ver=6.1"
Content-length: 427
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
					xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
					xmlns:xsd="http://www.w3.org/2001/XMLSchema"> 
<SOAP-ENV:Body> 
<axl:getUser xmlns:axl=http://www.cisco.com/AXL/API/6.1         
xsi:schemaLocation="http://www.cisco.com/AXL/API/6.1 
http://ccmserver/schema/axlsoap.xsd" 
sequence="1234"> <userid>tttt</userid> </axl:getUser> 
</SOAP-ENV:Body> 
</SOAP-ENV:Envelope>
 
   

In the AXL Versioning Support section, the sample AXL response now displays as follows:

HTTP/1.1 200 OK
Server: Apache-Coyote/1.1
Set-Cookie: JSESSIONIDSSO=950805DE5E10F32C5788AE164EEC4955; Path=/
Set-Cookie: JSESSIONID=151CF94ACF20728B1D47CC5C3BECC401; Path=/axl; Secure
SOAPAction: "CUCM:DB ver=6.1"
Content-Type: text/xml;charset=utf-8
Content-Length: 728
Date: Mon, 22 Jan 2007 06:51:42 GMT
Connection: close

Cisco Unified Serviceability Administration Guide

The following sections comprise documentation updates for the Cisco Unified Serviceability Administration Guide.

DNS Required for RTMT Alerts by E-mail

Warning Displays When SIP Stack Trace Is Enabled

Missing MIB Changes

SNMP Traps and Informs Correction

DNS Required for RTMT Alerts by E-mail

The Cisco Unified Serviceability Administration Guide does not explain that to configure RTMT to send alerts via e-mail, you must configure DNS. For information on configuring the primary and secondary DNS IP addresses and the domain name in Cisco Unified Communications Manager Server Configuration, see the "DHCP Server Configuration" chapter in the Cisco Unified Communications Manager Administration Guide.

Warning Displays When SIP Stack Trace Is Enabled

In the Trace Configuration window in Cisco Unified Serviceability, Enable SIP Stack Trace represents one of the trace filter settings that are available. If you enable this log, you may experience severe performance degradation; so, when you click the Enable SIP Stack Trace check box, the following warning displays:

Enabling SIP Stack Trace can cause extreme performance degradation especially during high 
traffic hours.

Missing MIB Changes

The Cisco Unified Serviceability Administration Guide requires updates for these MIB changes:

Addition to Table 15-1 in the section Access Privileges (for V1 and V2): ReadNotifyOnly—The community string can read values of MIB objects and also send the values for trap and inform messages. To change the trap configuration parameters, you need to configure a community string with NotifyOnly, ReadNotifyOnly, or ReadWriteNotify privileges.

Addition to Table 16- 1 in the section Access Privileges (for V3): ReadNotifyOnly—The user can read values of MIB objects and also send the values for trap and inform messages. To change the trap configuration parameters, you need to configure a user with NotifyOnly, ReadNotifyOnly, or ReadWriteNotify privileges.

SNMP Traps and Informs Correction

The Cisco Unified Serviceability Administration Guide requires the deletion of this sentence from the SNMP Traps and Informs section: For some alarms, if the routing list in the alarm definition displays SNMP traps, the CCMAgent receives alarm notifications from the alarms. The notifications are received as XML messages which are parsed and traps are sent. In the case of Phone Failed and Phone Status events, the Phone Failed and Phone Status MMFs are populated.

Cisco Unified Communications Manager Assistant User Guide

The following sections comprise documentation updates for the Cisco Unified Communications Manager Assistant User Guide.

Cisco Unified Communications Manager Assistant User Guide for Cisco Unified Communications Manager 6.0

Online Help Notes for Hebrew and Arabic

Cisco Unified Communications Manager Assistant

Directory Search Correction

Creating Filter Lists for a Manager

Cisco Unified Communications Manager Assistant User Guide for Cisco Unified Communications Manager 6.0

Consider the following note.


Note If the Assistant is configured with the Unified CM Intercom line, the speed dial on that line will initially point to the first Manager and then eventually to the last Manager that was called from the Intercom line.


Online Help Notes for Hebrew and Arabic

In the Cisco Unified Communications Manager Assistant User Guide, the chapter called "Introduction to Cisco Unified Communications Manager Assistant" does not contain the following information that Hebrew and Arabic users may need to know: Beginning in Cisco Unified Communications Manager Release 6.1 release, Cisco provides PDF versions of the Cisco Unified Communications Manager Assistant User Guide in Hebrew and Arabic as online help on the client PC that is running Cisco Unified Communications Manager Assistant. Therefore, this client must have Adobe Reader installed.

Cisco Unified Communications Manager Assistant

The assistant no longer obtains the assistant console application via a URL that the administrator provides; instead, a plug-in from Cisco Unified Communications Manager Administration gets downloaded and installed on the assistant PC.

The assistant console application installation supports Netscape 7.1 (or later) and Microsoft Internet Explorer 6 (or later). You can install the application on a PC that runs Windows 2000, Windows XP, or Windows Vista [new support for 5.1(3) and later].

A previous 5.x or 6.x version of the assistant console application works with Cisco Unified Communications Manager 6.1(1a), but if you decide to install the 6.1(1a) plug-in, you must uninstall the previous 5.x or 6.x version of the assistant console application before you install the plug-in.

Previous versions of the assistant console application do not work with Windows Vista. If the PC runs Windows Vista, install the plug-in.

After you upgrade from Cisco Unified CallManager Release 4.x to Cisco Unified Communications Manager 6.1(1a), you must install the assistant console plug-in. Before you install the plug-in, uninstall the 4.x version of the assistant console application.

To uninstall previous versions of the assistant console application (6.0(1), 4.x, or any 5.x version before 5.1(3)), choose Start> ...Programs > Cisco Unified CallManager Assistant > Uninstall Assistant Console.

To uninstall 5.1(3) (or later) attendant console application, go to the Control Panel and remove it.


Tip The assistant console application requires that JRE1.4.2_05 exist in C:\Program Files\Cisco\Cisco Unified Communications Manager.


To install the assistant console application, perform the following procedure:

Procedure


Step 1 From the PC where you want to install the assistant console application, browse into Cisco Unified Communications Manager Administration and choose Application > Plugins.

Step 2 For the Cisco Unified Communications Manager Assistant plug-in, click the Download link; save the executable to a location that you will remember.

Step 3 Locate the executable and run it.


Tip If you install the application on a Windows Vista PC, a security window may display. Allow the installation to continue.


The installation wizard displays.

Step 4 In the Welcome window, click Next.

Step 5 Accept the license agreement and click Next.

Step 6 Choose the location where you want the application to install. After you choose the location for the installation, click Next.


Tip By default, the application installs in C:\Program Files\Cisco\ Unified Communications Manager Assistant Console.


Step 7 To install the application, click Next.

The installation begins.

Step 8 After the installation completes, click Finish.



Tip To launch the assistant console, click the desktop icon or choose Cisco Unified Communications Manager Assistant > Assistant Console in the Start...Programs menu.

Before the assistant logs in to the console, give the assistant the port number and the IP address or hostname of the Cisco Unified Communications Manager server where the Cisco IP Manager Assistant service is activated. The first time that the assistant logs in to the console, the assistant must enter the information in the Cisco Unified Communications Manager Assistant Server Port and the Cisco Unified Communications Manager Assistant Server Hostname or IP Address fields.

Before the assistant logs in to the console, give the assistant the user name and password that is required to log in to the console.

The Advanced tab in the Cisco Unified Communications Manager Assistant Settings window allows you to enable trace for the assistant console.


Directory Search Correction

In the Cisco Unified Communications Manager Assistant User Guide, "Getting Started" chapter, the Using the Directory section, the following sentence exists:

To search for a coworker, enter any portion of the person's first and/or last name in the search fields and click Search. The directory displays a list of all users that match your search string.

Replace the preceding information with the following information:

To search in the directory, enter the first letter of the first name or the first letter of the last name, followed by the trailing letters in the first or last name (whichever name that you are entering), and click Search. The results that match the search string display.

The following wildcards do not get supported:

*

#

+

Creating Filter Lists for a Manager

In the "How to Configure Manager Features" chapter of the Cisco Unified Communications Manager Assistant User Guide, in the How to Create Filter Lists for a Manager section, the following information now applies:

Be aware that the + character is allowed in inclusive/exclusive filter configurations for managers via the browser-based configuration window for managers or the PC assistant console application. The + character signifies an international directory number that an end user may see (as a globalized number) in either the Cisco Unified Communications Manager directory or on the Cisco Unified IP Phone (under Call Details > History).

The + character gets evaluated on an incoming call. For an incoming call to a manager, Cisco Unified Communications Manager Assistant will evaluate both localized and globalized numbers while performing filter pattern matching.

Cisco Unified IP Phone Documentation

The following sections comprise the documentation updates for the Cisco Unified IP Phone Administration Guide.

Cisco Unified IP Phone User Guide (7906, 7911, 7931, 7945, 7965, 7975)

Cisco Unified IP Phone Administration Guides (7905G, 7912G, 7921G)

Cisco Unified Wireless IP Phone Guide 7920 for Cisco Unified CallManager 5.0 (SCCP)

Cisco Unified Wireless IP Phone Guide (7975, 7971, 7965, 7945, 7962, 7942, 7941, 7931, 7911, 7906)

Cisco Unified CallManager Bulk Administration Guide

Cisco Unified IP Phone User Guide (7906, 7911, 7931, 7945, 7965, 7975)

The following information on extension mobility needs updating in the Cisco Unified IP Phone Guide (7906, 7911, 7931, 7945, 7965, 7975).

Using Cisco Extension Mobility

Cisco Extension Mobility (EM) allows you to temporarily configure a Cisco Unified IP Phone as your own. After you log in to EM, the phone adopts your user profile, including your phone lines, features, established services, and web-based settings. Your system administrator must configure EM for you.

Tips

EM automatically logs you out after a certain time. Your system administrator establishes this time limit.

Changes that you make to your EM profile from your User Options window take effect immediately if you are logged in to EM on the phone; otherwise, changes take effect the next time that you log in.

Changes that you make to the phone from your User Options window take effect immediately if you are logged out of EM; otherwise, changes take effect after you log out.

Local settings that are controlled by the phone do not get maintained in your EM profile.

Extension Mobility Successful Authentication Cache

The extension mobility application maintains a cache of all logged on user information for 2 minutes. If a request comes to extension mobility regarding a user who is represented in the cache, the user gets validated with information from the cache. This means that, if a user changes the password, logs out, and then logs back in within 2 minutes, both the old and new passwords get recognized.

Do Not Disturb Feature Priority

On Cisco Unified IP Phones, the text message that indicates the Do Not Disturb (DND) feature is active takes priority over the text message that indicates the user has new voicemail messages, which allows the user to know when DND is active. However, the text message that indicates the Call Forward All feature is active has a higher priority than DND.

Cisco Unified IP Phone Administration Guides (7905G, 7912G, 7921G)

The following information on Configuring a Custom Background Image needs updating in the Cisco Unified IP Phone Administration Guide (7905G, 7912G, 7921G).

Use the following procedure if you need to do the following types of updates to your IP phone:

Change your logo, for which you will need the configuration file.

Update your configuration file when the phone is in a locale other than "United States."


Tip For more information, see the Cisco Unified Communications Locale Installer 5.1.1.2000-1 Readme file.


Configuring a Custom Background Image

To configure custom background images for the Cisco Unified IP Phone, follow these steps:

Procedure


Step 1 Open a command window and enter the following command:

bmp2logo imageID image.bmp image.logo

where:

imageID specifies a unique identifier for the new graphic. This identifier must comprise a number from 0 through 4294967296 and must differ from the identifier of the graphic that is currently on the phone.

image specifies the base file name of the image that you previously created and saved with the graphics program.


Note The imageID of the image that comes with the phone specifies 1.


For example, if the image identifier is 10 and the base name of your image file is mylogo, enter this command:

bmp2logo 10 mylogo.bmp mylogo.log

Step 2 Copy the image.logo file to the following directory in the TFTP server for the Cisco Unified Communications Manager:

/usr/local/cm/tftp/<country>/

where:

<country> is the country of your locale installer (for example, Greece for Greek).


Note Be aware that the file name and subdirectory parameters are case sensitive. Be sure to use the forward slash "/" when you specify the subdirectory path.


Step 3 Add the following line to the Cisco Unified IP Phone profile file:

upgradelogo:imageID,TFTPServerID,image.logo

where:

imageID specifies the same unique identifier that you specified in Step 1.

TFTPServerID specifies the IP address of the TFTP server on which the image.logo file gets stored. If the image.logo file is stored on the same TFTP server as the Cisco Unified IP Phone configuration file, replace TFTPServerID with the numeral 0.

image specifies the base file name of the image file.

For example, if the image identifier is 10, the converted file gets stored on the same TFTP server as the Cisco Unified IP Phone configuration file, and the base name of the converted image file specifies mylogo, add the following line to the configuration file:

upgradelogo:10,0,mylogo.logo


Note For detailed information about using profile files, see Appendix A, "Additional Configuration Methods and Parameters."


Step 4 Use the cfgfmt.exe tool to generate a binary profile file from the text file.

Step 5 Upload the new binary file that you created to the following directory in the TFTP server for the Cisco Unified Communications Manager:

//usr/local/cm/tftp/<lowercase country name>/


Note Be aware that the file name and directory parameters are case sensitive. Be sure to use the forward slash "/" when you specify the directory path.


To upload the files, choose Software Upgrades > Upload TFTP Server File in Cisco Unified OS Administration.

For more information, see the "Software Upgrades" chapter in Cisco Unified Communications Operating System Administration Guide.

You must also copy the customized binary files to the other TFTP servers that the phone may contact to obtain these files.


Note Cisco recommends that you also store backup copies of custom binary files in another location. You can use these backup copies if the customized files are overwritten when you upgrade Cisco Unified Communications Manager.


Step 6 Power cycle the phone.

The new graphic displays when the phone restarts.


Cisco Unified Wireless IP Phone Guide 7920 for Cisco Unified CallManager 5.0 (SCCP)

The Using Personal Directory on Your Phone section incorrectly states that you access the personal address book from the Services button on the Cisco Unified Wireless IP Phone 7920. The following section provides the correct procedure.

Using Personal Directory on Your Phone

The Personal Directory feature set contains your Personal Address Book (PAB) and Fast Dials. This section describes how to set up and use Personal Directory on your phone.

If you want to ...
Then ...

Access Personal Directory (for PAB and Fast Dial codes)

1. Choose Menu > Directory > Corporate Directory > Personal Directory.

2. Enter your Cisco Unified Communications Manager user ID and PIN; then, press Submit.


Cisco Unified Wireless IP Phone Guide (7975, 7971, 7965, 7945, 7962, 7942, 7941, 7931, 7911, 7906)

The information for Cisco Web Dialer for Cisco Unified Communications Manager 6.1(2) was updated in the Cisco Unified IP Phone Guide for Cisco Unified Communications Manager 6.1(3).

Using Cisco Web Dialer

On the Preferences page (Make Call page in release 6.1(3x)), the default device for an Extension Mobility only user changed from Use EM Profile to Permanent Device. In release 6.1(3x), the default for EM only user changes back to Use EM Profile.

Cisco Unified CallManager Bulk Administration Guide

The following sections comprise documentation updates to the Cisco Unified CallManager Bulk Administration Guide.

Description for Phone Personalization Is Incorrect in Documentation

Incorrect Path Is Documented for Add File Format Window

Primary User Device Field on the Update Users Window in BAT

Single Button Barge (new field)—Phone Template Configuration Window in BAT

Join Across Lines (new field)—Phone Template Configuration Window in BAT

Single Button Barge (new field)—UDP Template configuration Window in BAT

Join Across Lines (new field)—UDP Template configuration Window in BAT

Description for Phone Personalization Is Incorrect in Documentation

The Cisco Unified Communications Manager Bulk Administration Guide, Cisco Unified Communications Manager System Guide, and Cisco Unified Communications Manager Administration Guide contain incorrect information on phone personalization. If you plan to configure the Phone Personalization setting in Cisco Unified Communications Manager Administration, use the following information:

The Phone Personalization setting allows you to enable a Cisco Unified IP Phone, so it works with Phone Designer, a Cisco Unified Communications widget that allows a phone user to customize the wallpaper and ring tones on the phone. You can enable phone personalization in the Enterprise Parameter Configuration window, the Phone Configuration window, the Common Phone Profile Configuration window, or the Phone Template window in Cisco Unified Communications Manager Administration.


Tip To enable phone personalization via the Phone Personalization enterprise parameter, which supports all phones in the cluster that work with Phone Designer, choose System > Enterprise Parameter in Cisco Unified Communications Manager Administration, enter 1 in the Value Parameter field, and click Save in the Enterprise Parameter Configuration window.


If you configure phone personalization in the Phone Configuration window (Device > Phone), Common Phone Profile Configuration window (Device > Device Settings > Common Phone Profile), or the Phone Template window (Bulk Administration > Phones > Phone Template), choose one of the following options from the Phone Personalization drop-down list box:

Disabled-The user cannot customize the Cisco Unified IP Phone by using Phone Designer.

Enabled-The user can use Phone Designer to customize the phone.

Default-The phone uses the configuration from the Phone Personalization enterprise parameter if you choose Default in both the Phone Configuration and Common Phone Profile Configuration windows. If you choose Default in the Common Phone Profile Configuration window but not in the Phone Configuration window, the phone uses the configuration that you specify in the Phone Configuration window.

You must install and configure Phone Designer, so the phone user can customize the phone. Before you install and configure Phone Designer, identify which Cisco Unified IP Phone models work with Phone Designer, as described in the Phone Designer release notes. To obtain the Phone Designer documentation, go to the following URL:

http://www.cisco.com/en/US/products/ps9829/tsd_products_support_series_home.html

Incorrect Path Is Documented for Add File Format Window

The "Phones and User File Format" chapter in the Cisco Unified Communications Manager Bulk Administration Guide includes an incorrect path to the Add File Format window. The Adding Phones/User File Formats section incorrectly states that you choose Bulk Administration > Phones and Users> Phones & Users File Format > Assign File Format to access the Add File Format window. Disregard the path in the BAT documentation and choose the following path to access the Add File Format window: Bulk Administration > Phones and Users > Phones & Users File Format > Add File Format.

Primary User Device Field on the Update Users Window in BAT

The Cisco Unified CallManager Bulk Administration Guide omitted this information. A new field called Primary User Device displays in the Mobility Information section of the End User Configuration window. This field controls the number of device license units that are consumed for adjunct devices for mobile connect and works in conjunction with the Enable Mobility check box in the End User Configuration window.You can access this window through Users > Update Users.

Single Button Barge (new field)—Phone Template Configuration Window in BAT

The Cisco Unified CallManager Bulk Administration Guide omitted this information. Single Button Barge (new field)—This new field displays in the Phone Template Configuration window, and when you add a new phone configuration for a phone that is running SCCP, a new row exists for Single Button Barge/cBarge. You can set the Single Button Barge/cBarge feature Off, Barge. cBarge, or Default. If it is set to Default, the phone inherits the Single Button Barge/cBarge setting from the service parameter and device pool settings.

Join Across Lines (new field)—Phone Template Configuration Window in BAT

The Cisco Unified CallManager Bulk Administration Guide omitted this information. Join Across Lines (new field)—This new field displays in the Phone Template Configuration window. When you add a new phone configuration for a phone that is running SCCP, a new row exists for Join Across Lines. You can set the Join Across Lines feature to Off, On, or Default. If it is set to Default, the phone inherits the Join Across Lines setting from the service parameter and device pool settings.

Single Button Barge (new field)—UDP Template configuration Window in BAT

The Cisco Unified CallManager Bulk Administration Guide omitted this information. Single Button Barge (new field)—This new field displays in the UDP Template configuration window. When you add a new device profile configuration for a phone that is running SCCP, a new row exists for Single Button Barge/cBarge. You can set the Single Button Barge/cBarge feature to Off, Barge, cBarge, or Default. If it is set to Default, the phone inherits the Single Button Barge/cBarge setting from the service parameter and device pool settings.

Join Across Lines (new field)—UDP Template configuration Window in BAT

The Cisco Unified CallManager Bulk Administration Guide omitted this information. Join Across Lines (new field)—This new field displays inthe UDP Template configuration window. When you add a new device profile configuration for a phone that is running SCCP, a new row exists for Join Across Lines. You can set the Join Across Lines feature to Off, On, or Default. If it is set to Default, the phone inherits the Join Across Lines setting from the service parameter and device pool settings.

Cisco Unified Communications Manager Real-Time Monitoring Tool Administration Guide

The following sections comprise the documentaiton updates for the Cisco Unified Communications Manager Real-Time Monitoring Tool Administration Guide.

RTMT Trace and Log Central Disk IO and CPU Throttling

Trace Compression Support

Incorrect Description for User ID Field in Application User Window

Path for Accessing Cisco Unified Reporting

Perfmon Log File—Maximum File Size Default Value

Path for Accessing Cisco Unified Reporting

DNS Required for RTMT Alerts by E-mail

Minimum Memory Requirement for RTMT Client

RTMT Trace and Log Central Disk IO and CPU Throttling

RTMT now supports the throttling of critical Trace and Log Central operations and jobs, whether they are running on demand, scheduled, or automatic. The throttling slows down the operations when IO utilization is in high demand for call processing, so call processing can take precedence.

When a user makes a request for an on-demand operation when the call processing node is running under high IO conditions, the system now displays a warning, which gives the user the opportunity to abort the operation. You can configure the IO rate threshold values that control when the warning displays with the following new service parameters:

TLC Throttling CPU Goal

TLC Throttling IOWait Goal

The system compares the values of these parameters against the system actual CPU and IOWait values. If the goal (the value of the service parameter) is lower than the actual value, the system issues the warning.

For More Information

"Service Parameters Configuration" chapter, Cisco Unified Communications Manager Administration Guide

Trace Compression Support

The following information provides an updated version of what appears in the Cisco Unified Communications Manager Real-Time Monitoring Tool Administration Guide.

This feature enables the ROS (Recoverable Outstream) library to support the compressed output of tracefiles. The files get compressed as they are being generated. The benefits of tracefile compression include

Reduces the capacity required to store tracefiles.

Reduces the disk head movement, which results in significantly improved disk I/O wait. This may prove to be of value when tracefile demand is high.

Use the new enterprise parameter, Trace Compression, to enable or disable trace compression. The default value for this parameter specifies Disabled. For information on setting the values of enterprise parameters, see the "Enterprise Parameters Configuration" chapter in the Cisco Unified Communications Manager Administration Guide.


Caution Compressing files adds additional CPU cycles. Enabling the Trace Compression enterprise parameter can negatively impact overall call throughput by as much as 10 percent.

You can recognize compressed files by their .gz extension (.gzo if the file is still being written to). To open a compressed file, double click the file name, and the file opens in the log viewer.

For More Information

"Enterprise Parameters Configuration" chapter, Cisco Unified Communications Manager Administration Guide

Path for Accessing Cisco Unified Reporting

In both the Cisco Unified Communications Manager Real-Time Monitoring Tool Administration Guide ("Installing and Configuring Real-Time Monitoring Tool" chapter) and the Cisco Unified Serviceability Administration Guide ("Understanding Cisco Unified Serviceability" chapter), the RTMT menu path for accessing Cisco Unified Reporting is incorrect. The correct path follows: File>Cisco Unified Reporting.

Perfmon Log File—Maximum File Size Default Value

Chapters 4 and 5 ("Understanding Performance Monitoring" and "Configuring and Displaying Performance Counters") in the Cisco Unified Communications Manager Real-Time Monitoring Tool Administration Guide incorrectly specify the default value of the Maximum File Size perfmon data-logging parameter as 2 megabytes. The correct default value equals 5 megabytes.

Path for Accessing Cisco Unified Reporting

Both the Cisco Unified Communications Manager Real-Time Monitoring Tool Administration Guide ("Installing and Configuring Real-Time Monitoring Tool" chapter) and the Cisco Unified Serviceability Administration Guide ("Understanding Cisco Unified Serviceability" chapter) show an incorrect RTMT menu path for accessing Cisco Unified Reporting. The correct path follows: File>Cisco Unified Reporting.

DNS Required for RTMT Alerts by E-mail

The Cisco Unified Communications Manager Real-Time Monitoring Tool Administration Guide do not explain that to configure RTMT to send alerts via Email, you must configure DNS. For information on configuring the primary and secondary DNS IP addresses and the domain name in Cisco Unified Communications Manager Server Configuration, see the "DHCP Server Configuration" chapter in the Cisco Unified Communications Manager Administration Guide.

Minimum Memory Requirement for RTMT Client

Chapter 2, "Installing and Configuring Real-Time Monitoring Tool (RTMT)" in the Cisco Unified Communications Manager Real-Time Monitoring Tool Administration Guide does not include the minimum memory requirement for running the RTMT client on a Windows OS machine. The minimum memory requirement equals 128 MB.

Cisco Unified Communications Operating System Administration Guide

The following sections comprise documentation updates for the Cisco Unified Communications Operating System Administration Guide.

COP File Installation

NTP Version 4

Support for NIC Teaming

Install New COP Files Before You Upgrade Cisco Unified Communications Manager

Digital Certificate Key Length Restrictions

Parallel Upgrades from Unified CM Releases 5.x and 6.x to Unified CM Release 6.1(3x)

set network dhcp eth0 disable Command Parameters

Remote Support Account Duration

System Generates a DBReplicationFailure Alert

Information On ARP Cache Limits Omitted from Operating System Administration Guide

Third-Party Certificate Authority Verification

Recovering Administrator and Security Passwords

Software Feature License Information Omitted from Operating System Administration Guide

Cisco Unified Communications Manager Does Not Support Recovery of Administration or Security Passwords

Characters Allowed in a Pre-Shared Key

COP File Installation

Before you begin the upgrade, install any new COP files that apply to the release you plan to install.


Tip Cisco recommends that you always install new COP files before you upgrade to a new release.


NTP Version 4

To avoid potential compatibility, accuracy, and network jitter problems, the external NTP servers that you specify for the primary node should be NTP v4 (version 4).

Support for NIC Teaming

The Cisco Unified Communications Operating System Administration Guide does not indicate the appropriate support for NIC teaming. Server platforms with dual Ethernet network interface cards (NICs) can support NIC teaming for network fault tolerance with Cisco Unified Communications Manager . Cisco began support of NIC teaming on HP servers in the 5.0(1) release and began support on IBM servers in the 6.1(2) release. This feature allows a server to be connected to the Ethernet via two NICs and, hence, two cables. NIC teaming prevents network downtime by transferring the workload from the failed port to the working port. NIC teaming cannot be used for load balancing or increasing the interface speed.

Install New COP Files Before You Upgrade Cisco Unified Communications Manager

If you have new .cop files for your devices, be sure you install them before you upgrade Cisco Unified Communications Manager to a newer build. If you do not install the new .cop file before you upgrade, your devices might not function correctly after the upgrade.

Digital Certificate Key Length Restrictions

In 5.x releases of Cisco Unified Communications Manager you must use digital certificates with a key length of 2048 bits or less. Cisco Unified Communications Operating System in these releases does not support digital certificates with a key length larger than 2048 bits.

Parallel Upgrades from Unified CM Releases 5.x and 6.x to Unified CM Release 6.1(3x)

When you upgrade a cluster that is running a supported version of Cisco Unified Communications Manager 5.x or 6.x to Cisco Unified Communications Manager 6.1(3x), begin upgrading the first node first. You can begin upgrading subsequent nodes in parallel after the first node has reached a specified point in the upgrade.

During the upgrade of the first node, view the installation log, install_log_<date+time>.log, by using the Software Installation/Upgrade window in Cisco Unified Communications Operating System Administration or the command line interface (CLI). You can begin the upgrade of the subsequent nodes after the following information displays in the log.

PRODUCT_TARGET is <product target id>

PRODUCT_NAME is <product name>

PRODUCT_VERSION is <product version to which you are upgrading, such as 6.1(2)>

You can also use the CLI to search for the relevant information in the install log by following this procedure:

Procedure


Step 1 List the install logs; for example:

file list install install_* date
 
   
install_log_2008-10-01.09.41.57.log     install_log_2008-10-08.12.59.29.log
install_log_2008-10-14.09.31.06.log     
dir count = 0, file count = 3
 
   

Step 2 Search the most recent install log for the string PRODUCT_VERSION; for example:

file search install install_log_2008-10-14.09.31.06.log PRODUCT_VERSION
 
   
Searching path: /var/log/install/install_log_2008-10-14.09.31.06.log
Searching file: /var/log/install/install_log_2008-10-14.09.31.06.log
10/14/2008 09:52:14 upgrade_os.sh|PRODUCT_VERSION is 7.1.0.39000-97|<LVL::Info>
 
   
Search completed
 
   

Step 3 When the file search command finds the PRODUCT_VERSION string in the install log, you can start the upgrade of the subsequent nodes.



Caution If you want to upgrade the subsequent nodes in parallel with the first node, do not choose the Reboot to upgraded partition on either first node or subsequent nodes while you are configuring the upgrade options. If selected, the first node may complete its upgrade and reboot while the subsequent nodes are upgrading, which causes the upgrade of the subsequent nodes to fail.

set network dhcp eth0 disable Command Parameters

The set network dhcp eth0 disable command now requires the following parameters:

ip—The new static IP address

mask—The new network mask

gateway ip—The new gateway IP address

Remote Support Account Duration

When you create a remote support account in Cisco Unified Communications Operating System Administration, you must enter the duration for which the account will be active in the Account Duration field. Enter a number of days between 1 and 30. The remote support account will automatically expire after the number of days that you enter. The default account duration specifies 30 days.

System Generates a DBReplicationFailure Alert

During supported upgrades from Cisco Unified Communications Manager 5.x or 6.x to Cisco Unified Communications Manager 6.1(x), the system may generate a DBReplicationFailure alert while the system transitions to the new software release. Administrators can disregard this alert until all servers in the cluster have been upgraded and are running Cisco Unified Communications Manager 6.1(x).

For more information on viewing alerts, refer to the Cisco Unified Communications Manager Real-Time Monitoring Tool Administration Guide.

Information On ARP Cache Limits Omitted from Operating System Administration Guide

Do not install Cisco Unified Communications Manager in a large Class A or Class B subnet that contains a large number of devices. When you install Cisco Unified Communications Manager in a large subnet with a large number devices in that subnet, the Address Resolution Protocol (ARP) table can fill up quickly (maximum 1024 entries, by default). When the ARP table gets full, Cisco Unified Communications Manager can have difficulty talking to endpoints and cannot add more phones.

Third-Party Certificate Authority Verification

The Cisco Unified Communications Operating System Administration Guide, Release 6.0(1) states that Cisco has verified Verisign as a source for third party certificates. Be aware that this is no longer correct, and Verisign is not a verified CA.

Recovering Administrator and Security Passwords

This section replaces the section Recovering the Administrator Password in the "Log In to Cisco Unified Communications Operating System Administration" chapter" of the Cisco Unified Communications Operating System Administration Guide for releases 5.0(4), 5.1(1), 6.0(1), and 6.1(1a).

If you lose the administrator password or security password, use the following procedure to reset these passwords.


Note During this procedure, you must remove and then insert a valid CD or DVD in the disk drive to prove that you have physical access to the system.


Procedure


Step 1 Log in to the system with the following username and password:

Username: pwrecovery

Password: pwreset

The Welcome to platform password reset window displays.

Step 2 Press any key to continue.

Step 3 If you have a CD or DVD in the disk drive, remove it now.

Step 4 To continue, press any key.

The system tests to ensure that you have removed the CD or DVD from the disk drive.

Step 5 Insert a valid CD or DVD into the disk drive.

The system tests to ensure that you have inserted the disk.

Step 6 After the system verifies that you have inserted the disk, you get prompted to enter one of the following options to continue:

To reset the administrator password, enter a.

To reset the security password, enter s.

To quit, enter q.

Step 7 Enter a new password of the type that you chose.

Step 8 Reenter the new password.

The password must contain at least 6 characters. The system checks the new password for strength. If the password does not pass the strength check, you get prompted to enter a new password.

Step 9 After the system verifies the strength of the new password, the password gets reset, and you get prompted to press any key to exit the password reset utility.


Caution The security password on all nodes in a cluster must match. Change the security password on all machines, or the cluster nodes will not communicate.

Software Feature License Information Omitted from Operating System Administration Guide

The "Software Upgrades" chapter of the Cisco Unified Communications Operating System Administration Guide omits the following information:

You must obtain a software feature license if you are upgrading from Cisco Unified Communications Manager 5.x. A software feature license activates features on your system for the specified license version. To use 5.0 device licenses with Cisco Unified Communications Manager 6.(x) or later, make sure that you obtain the software feature license for the Cisco Unified Communications Manager version that is running on your system.

For more information on obtaining and installing licenses, see the "License File Upload" chapter in the Cisco Unified Communications Manager Administration Guide.

Cisco Unified Communications Manager Does Not Support Recovery of Administration or Security Passwords

Chapter 2 of the Cisco Unified Communications Operating System Administration Guide does not contain the following information.

Cisco Unified CM does not support recovery of administration or security passwords. If you lose these passwords, you must reset the passwords, as described in the Cisco Unified Communications Operating System Administration Guide.


Tip The Cisco Unified Communications Operating System Administration Guide calls the section Recovering the Administrator or Security Passwords, instead of Resetting the Administrator or Security Passwords. Access the Recovering the Administrator or Security Passwords section to reset the passwords.


Characters Allowed in a Pre-Shared Key

Chapter 6 of the Cisco Unified Communications Operating System Administration Guide does not contain the following information.

Pre-shared IPSec keys can contain alphanumeric characters and hyphens only, not white spaces or any other characters. If you are migrating from a Windows-based version of Cisco Unified CM, you may need to change the name of your pre-shared IPSec keys, so they are compatible with current versions of Cisco Unified CM.

IP Phones Automatically Upgrade Firmware After Switch Version

The following note is missing from the Cisco Unified Communications Operating System Administration Guide.


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.


Troubleshooting Guide for Cisco Unified Communications Manager

The following section comprises documentation updates for the Troubleshooting Guide.

Automated Alternate Routing (AAR) Limitation with Remote Gateways

Cisco Unified Mobility User Hangs Up Mobile Phone But Cannot Resume Call on Desktop Phone

Netdump Utility

Database Replication

Automated Alternate Routing (AAR) Limitation with Remote Gateways

AAR exhibits the limitation that calls routed over a remote gateway during a high-bandwidth situation fail, and the calls cannot get routed over the local gateway when AAR is used. Be aware that this functionality is important to customers who use Tail-End Hop Off (TEHO) for toll bypass.

Workaround Example

Use a specific partition for the TEHO in question.

In the following example, headquarters (HQ) has area code 408, and the Branch (BR1) has area code 919.

Configure as follows:

1. Create theTehoBr1forHQPt partition and assign this partition to the calling search space (CSS) of the HQ devices with a higher priority than the regular PSTN access uses.

2. Create the TehoBr1forHQRL route list and add the BR1 gateway route group to this route list as the first option and the HQ gateway as the second option.

3. Apply called party modification within the route list. In this case, apply predot called party modification for the BR1 route group, and apply predot and prefix 1919 called party modification for the HQ route group.

4. Ensure that the gateway does not perform called party modification.

5. Create a route pattern in the TehoBr1forHQPt partition.

6. Ensure that no called party modifications are applied in the route pattern.

Results

In an out-of-bandwidth situation, after Cisco Unified Communications Manager tries to allocate the first route group for TEHO (BR1 route group), Cisco Unified CM retries the second route group, at which point the system strips the 91919 string and replaces it with the 1919 string, which is suitable for long-distance dialing. Because the string is configured for use by the local gateway, less rerouting takes place.

AAR works on a per-external-phone-number-mask basis and cannot be processed for an external PSTN number because the system does not know the phone number mask of the PSTN number. This workaround provides AAR functionality and improves network resiliency.

Cisco Unified Mobility User Hangs Up Mobile Phone But Cannot Resume Call on Desktop Phone

Symptom

When a remote destination (mobile phone) is not a smart phone and a call to this mobile phone is anchored through Cisco Unified CM, the user can hang up the mobile phone and expect to see a Resume softkey on the user desktop phone to resume the call. The user cannot resume this call on the user desktop phone.

Possible Cause

If the calling party receives busy/reorder/disconnect tone when the mobile phone hangs up, the mobile phone provider probably did not disconnect the media. Cisco Unified CM cannot recognize this circumstance because no disconnect signals came from the provider. To verify whether this is the case, let the calling party wait for 45 seconds, when service provider will time out and send disconnect signals, upon which Cisco Unified CM can provide a Resume softkey to resume the call.

Recommended Action

Perform the following actions:

Add the following command to the gateway:

voice call disc-pi-off

For the Cisco CallManager service, set the Retain Media on Disconnect with PI for Active Call service parameter to False.

Netdump Utility

The netdump utility allows you to send data and memory crash dump logs from one server on the network to another. Servers that are configured as netdump clients send the crash logs to the server that is configured as the netdump server. The log file gets sent to the crash directory of the netdump server.

In a Cisco Unified Communications Manager cluster, you must configure at least two nodes as netdump servers, so the first node and subsequent nodes can send crash dump longs to each other.

For example, if your cluster contains three servers (one primary/first node and two subsequent nodes), you can configure the first node and subsequent node #1 as the netdump servers. Then, you can configure the first node as a netdump client of the subsequent node #1 and configure all of the subsequent nodes as netdump clients of the first node. If the first node crashes, it sends the netdump to subsequent node #1. If any subsequent node crashes, it sends the netdump to the first node.

You can use an external netdump server rather than configuring a Cisco Unified Communications Manager server as a netdump server. For information on configuring an external netdump server, contact TAC.


Note Cisco recommends that you configure the netdump utility after you install Cisco Unified Communications Manager to assist in troubleshooting. If you have not already done so, configure the netdump utility before you upgrade Cisco Unified Communications Manager from supported appliance releases.


To configure the netdump servers and clients, use the command line interface (CLI) that is available for the Cisco Unified Communications Operating System as described in the following sections:

Configuring a Netdump Server

Configuring a Netdump Client

Working with Files That Are Collected by the Netdump Server

Monitoring Netdump Status

Configuring a Netdump Server

To configure a node as a netdump server, use the following procedure:

Procedure


Step 1 On the node that you want to configure as the netdump server, start a CLI session as described in the Cisco Unified Communications Operating System Administration Guide.

Step 2 Execute the utils netdump server start command.

Step 3 To view the status of the netdump server, execute the utils netdump server status command.

Step 4 Configure the netdump clients, as described in the "Configuring a Netdump Client" section.


Configuring a Netdump Client

To configure a node as a netdump client, use the following procedure:

Procedure


Step 1 On the node that you want to configure as the netdump client, start a CLI session as described in the Cisco Unified Communications Operating System Administration Guide.

Step 2 Execute the utils netdump client start ip-address-of-netdump-server command.

Step 3 Execute the utils netdump server add-client ip-address-of-netdump-client. Repeat this command for each node that you want to configure as a netdump client.


Note Make sure that you enter the correct IP addresses. The CLI does not validate the IP addresses.


Step 4 To view the status of the netdump client, execute the utils netdump client status command.


Working with Files That Are Collected by the Netdump Server

To view the crash information from the netdump server, use the Real-Time Monitoring Tool or the command line interface (CLI). To collect the netdump logs by using the Real-Time Monitoring Tool, choose the Collect Files option from Trace & Log Central. From the Select System Services/Applications tab, choose the Netdump logs check box. For more information on collecting files by using Real-Time Monitoring Tool, see the Cisco Unified Communications Manager Real-Time Monitoring Tool Administration Guide.

To use the CLI to collect the netdump logs, use the "file" CLI commands on the files in the crash directory. The log filenames begin with the IP address of the netdump client and end with the date that the file gets created. For information on the file commands, refer to the Cisco Unified Communications Operating System Administration Guide.

Monitoring Netdump Status

You can monitor the netdump status by configuring SyslogSearchStringFound alerts in the Real-Time Monitoring Tool. Use the following procedure to configure the appropriate alerts:

Procedure


Step 1 From the quick launch channel in Real-Time Monitoring Tool, choose Tools > Alert Central.

Step 2 Right-click the SyslogStringMatchFound alert and choose Set Alert/Properties.

Step 3 Click Next three times.

Step 4 On the SysLog Alert window, click the Add button. When the Add Search String dialog box displays, enter netdump: failed and click Add. Then, click Next.


Note Make sure that the case and syntax match exactly.


Step 5 On the Email Notification window, choose the appropriate trigger alert action, enter any user-defined e-mail text, and click Save.

Database Replication

This section of the Cisco Unified Communications Manager System Issues chapter in the Troubleshooting Guide for Cisco Unified Communications Manager requires this addition:

Extension Mobility does not work when database replication breaks between the Unified CM node running Extension Mobility and the Unified CM node to which the phone is registered.

Cisco Unified Communications Manager 6.1 TCP and UDP Port Usage

The following section comprises the documentation updates for the Cisco Unified Communications Manager 6.1 TCP and UDP Port Usage documentation.

Ephemeral Port Range

Ephemeral Port Range

The Cisco Unified Communications Manager 6.1 TCP and UDP Port Usage document requires the following update:

The Ephemeral port range for the system equals 32768 - 61000.

Disaster Recovery System Administration Guide

The topic "Restoring the Entire Cluster" in the Disaster Recovery System Administration Guide currently includes the following information:

If a major failure or a hardware upgrade occurs, or in the event of a hardware migration, you may need to rebuild all nodes in the cluster.

Correct this section to include the following information and to add the following tip:

If a major hard drive failure or upgrade occurs, or in the event of a hard drive migration, you may need to rebuild all nodes in the cluster.


Tip If you are doing most other types of hardware upgrades, such as replacing a network card or adding memory, you do not need to perform the following procedure.


Upgrading to Cisco Unified Communications Manager from 4.x Releases Guide

The Upgrading to Cisco Unified Communications Manager from 4.x Releases Guide should include the following information :

If you change the Servername during the upgrade, the original Servername—rather than the changed Servername— displays in the Cisco Unified Communications Manager Administration window.

If you want to change the Servername from what displays in the Cisco Unified Communications Manager Administration window, so it matches the name that you assigned during the upgrade, you can do so after the upgrade. Be aware, however, that this step is not required.

For more information on how to make this change, refer to the Changing the IP Address and Host Name for Cisco Unified Communications Manager document at the following URL:

http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_maintenance_guides_list.html.

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 using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0.