Guest

Support

Release Notes for Cisco Unified Communictaions Manager Release 6.1(4a)

  • Viewing Options

  • PDF (1.1 MB)
  • Feedback
Release Notes for Cisco Unified Communications Manager Release 6.1(4a)

Table Of Contents

Release Notes for Cisco Unified Communications Manager Release 6.1(4a)

Content

Introduction

System Requirements

Installation Notes

Windows 2000 Users Must Download Windows Installer 3.0 Updates

Do Not Install Cisco Unified CM in a Large Class A or Class B Subnet That Contains a Large Number of Devices

Upgrading to Cisco Unified Communications Manager 6.1(4a)

Before You Begin

Special Upgrade Considerations

Upgrade Paths to Cisco Unified Communications Manager 6.1(4a)

Upgrading to Unified CM 6.1(4a) from Unified CM 4.x and 5.x

Upgrading from an Engineering Special

Upgrading to Unified CM Release 6.1(4a) by Using the UCSInstall File

Related Documentation

Limitations and Restrictions

Software Download URLs

Important Notes for Cisco Unified Communications Manager 6.1(4a)

CSCta43460 BIOS Update Is Required for MCS 7825-I2 Servers

Important Notes for Cisco Unified Communications Manager 6.1(4)

Adding or Updating SIP Dial Rules Causes Cisco TFTP Service To Rebuild All Phone Configuration Files

CSCta10219 Unicast Music on Hold May Not Play

Workaround - Option 1

Workaround - Option 2

Alerts During Upgrades to Cisco Unified Communications Manager Business Edition 6.1(4)

Cisco Unified JTAPI

SFTP Server Products

CSCsu08609 Unanswered Conference Call or Blind Transfer Over QSIG Trunk Goes to Third-Party Voice Messaging System Instead of Called Party

Use Microsoft Outlook to Receive Cisco Unified Communications Manager Licenses

CSCsr80287 Cisco CallManager Service Stops After Upgrade to Cisco Unified Communications Manager 6.x

Important Information About Delete Transaction by Using Custom File in BAT

Partition Size Limitations When You Upgrade from a 5.x Release to a 6.x Release

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

Clarification for Call Park Configuration

Viewing Privileges for Roles in Cisco Unified CM Administration

TAPS Name Change in Bulk Administration Tool

Basic Uninterruptible Power Supply (UPS) Integration

Strict Version Checking

Serviceability Not Always Accessible from OS Administration

Voice Mailbox Mask Interacts with Diversion Header

CTL Client 5.0 Plug-In Installation Note

Best Practices for Assigning Roles to Serviceability Administrators

For Serviceability, the Administrator That Is Created During Installation Must Not Be Removed

Connecting to Third-Party Voice Messaging Systems

Database Replication When You Revert to an Older Product Release

User Account Control Pop-up Window Displays During Installation of RTMT

CiscoTSP Limitations on Windows Vista Platform

Time Required for Disk Mirroring

Cisco Unified Mobility Supports Nine Locales

Each Remote Destination Supports a Maximum of Two Active Calls

Changes to Cisco Extension Mobility After Upgrade

RTMT Requirement When Cisco Unified Communications Manager Is Upgraded

Serviceability Session Timeout is Not Graceful

Problem Configuring Mobility Identity for Nokia S60 Device in Cisco Unified Communications Manager Administration

Serviceability Limitations When You Modify the IP Address

SIP Network/IP Address Field that is Required for SIP Fallback to SRST Gateway

Network Time Protocol Version 4

New and Changed Information

Installation, Upgrade, and Migration

System History Log for Cisco Unified Communications Manager

Description

Documentation Changes

Command Line Interface

Cisco Unified Communications Manager Administration

New and Updated Enterprise and System Parameters

Menu Changes

Cisco Unified Communications Manager Features and Applications

IPMA Restart

Redirected Dialed Number Identification Service and Diversion Header

Bulk Administration Tool

Inserting User Device Profiles and Phones into Cisco Unified Communications Manager

Caveats

Resolved Caveats

Using Bug Toolkit

Open Caveats

Documentation Updates

CDR Analysis and Reporting

"Mailing a Report" Recipients

Cisco Unified Communications Operating System

Disk Space Before Upgrading

Cisco Unified Communications Manager Administration

Route Plan Report Description Omits Mention of Mobile Voice Access Numbers

End User Chapter Includes Incorrect Information for Manager User ID Field

For the Manager User ID field, enter the user ID of the end user manager ID..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

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 is Not Required for Cisco Unity Connection 2.x

Incorrect Documentation Exists 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

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

RSVP Reservation Teardown for Shared-Line Calls

Considerations for LDAP Port Configuration

RSVP Reservation Teardown for Shared-Line Calls

Application Server Configuration is 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

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

Information About Changing Region Bandwidth Settings When Video Calls Are Made

Intercom Calls Cannot Be Placed on Hold

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 does Not get 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

Security

Definition of Locally Significant Certificate

Support for Certificates from External CAs

CAPF System Interactions and Requirements

Security Icons and Encryption

Software Conference Bridge Not Supported

Bulk Administration Tool

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

Limitations in Validation of Phones and User Device Profiles

Fields Omitted in Search Results on the Update Phones Window

Insert / Update Users Credential Policy

Reset Password/PIN

Cisco Unified IP Phones

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)

Obtaining Documentation and Submitting a Service Request


Release Notes for Cisco Unified Communications Manager Release 6.1(4a)


Updated December 22, 2009


Caution Be aware that you cannot upgrade directly from Unified CM 6.1(4a) to Unified CM 7.0

See: http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/compat/ccmcompmatr.html

Table 1 Delta Between Unified CM Release 6.1(4) and Unified CM Release 6.1(4a)

Date

Change

December 22, 2009

Added the "Route Plan Report Description Omits Mention of Mobile Voice Access Numbers" section

September 18, 2009

Added the "CSCta43460 BIOS Update Is Required for MCS 7825-I2 Servers" section

Updated the Table 3 Open Caveats as of September 18, 2009, page 29


Content

This document contains information pertinent to Cisco Unified Communications Manager
Release 6.1(4a).

Introduction

System Requirements

Installation Notes

Windows 2000 Users Must Download Windows Installer 3.0 Updates

Do Not Install Cisco Unified CM in a Large Class A or Class B Subnet That Contains a Large Number of Devices

Upgrading to Cisco Unified Communications Manager 6.1(4a)

Related Documentation

Limitations and Restrictions

Software Download URLs

Important Notes for Cisco Unified Communications Manager 6.1(4a)

Important Notes for Cisco Unified Communications Manager 6.1(4)

New and Changed Information

Caveats

Resolved Caveats

Open Caveats

Documentation Updates

Obtaining Documentation and Submitting a Service Request

Before you install Cisco Unified Communications Manager, Cisco recommends that you review the "Upgrading to Cisco Unified Communications Manager 6.1(4a)" section for information about upgrading and the "Important Notes for Cisco Unified Communications Manager 6.1(4a)" section for information about issues that may affect your system.

To view the release notes for previous versions of Cisco Unified Communications Manager, choose the Cisco Unified Communications Manager version from the following URL: http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_release_notes_list.html


Note Cisco recommends that you check Cisco.com for the latest software updates to Cisco Unified Communications Manager and its applications and download and install the latest updates on your system before the deployment of your Cisco Unified Communications Manager system. For a list of commonly used URLs, see the "Before You Begin" section.


Introduction

Cisco Unified Communications Manager, the call-processing component of the Cisco Unified Communications System, extends enterprise telephony features and capabilities to IP phones, media processing devices, voice-over-IP (VOIP) gateways, mobile devices, and multimedia applications.

System Requirements

Server Support

Make sure that you install and configure Cisco Unified CM Release 6.1(4a) on a Cisco Media Convergence Server (MCS) or a Cisco-approved HP server configuration or a Cisco-approved IBM server configuration.

To find which MCS are compatible with Cisco Unified CM Release 6.1(4a), refer to the Supported Servers for Cisco Unified Communications Manager Releases, go here.


Note Make sure that the matrix indicates that your server model supports Cisco Unified Communications Manager Release 6.1(4a).



Note Some servers that are listed in the compatibility matrix may require additional hardware support for Cisco Unified Communications Manager Release 6.1(4a). Make sure that your server meets the minimum hardware requirements, as indicated in the footnotes of the compatibility matrix. Cisco Unified Communications Manager requires a minimum of 2 GB of memory, 72 GB disk drive, and
2 GHz processor.


Uninterruptible Power Supply

Ensure that you connect each Cisco Unified Communications Manager node to an uninterruptible power supply (UPS) to provide backup power and protect your system.


Caution Failure to connect the Cisco Unified Communication Manager nodes to a UPS may result in damage to physical media and require a new installation of Cisco Unified Communications Manager.

Installation Notes

The following sections comprise installation notes for Unified CM 6.1(4a).

Windows 2000 Users Must Download Windows Installer 3.0 Updates

Do Not Install Cisco Unified CM in a Large Class A or Class B Subnet That Contains a Large Number of Devices

Windows 2000 Users Must Download Windows Installer 3.0 Updates

If you are running Windows 2000 on your workstation or server, you must download Windows Installer 3.0 updates to correctly install CTL Client plug-ins. You can obtain Windows Installer 3.0 at the following URL:

http://www.microsoft.com/downloads/details.aspx?familyid=5FBC5470-B259-4733-A914-A956122E08E8&displaylang=en


Note Windows 2000 comes with Windows Installer 2.0.


Procedure


Step 1 Windows Installer 3.0 requires validation. Validate your PC by following the instructions.

Step 2 Install Windows Installer 3.0.

Step 3 Reboot your machine, if necessary.

Step 4 Proceed with CTL Client plug-ins installation.


Do Not Install Cisco Unified CM in a Large Class A or Class B Subnet That Contains a Large Number of Devices

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 experiences difficulty communicating with endpoints and cannot add more phones.

Upgrading to Cisco Unified Communications Manager 6.1(4a)

The following sections contain information pertinent to upgrading to this release of Unified CM.

Before You Begin

Special Upgrade Considerations

Upgrade Paths to Cisco Unified Communications Manager 6.1(4a)

Upgrading to Unified CM 6.1(4a) from Unified CM 4.x and 5.x

Upgrading from an Engineering Special

Upgrading to Unified CM Release 6.1(4a) by Using the UCSInstall File

Before You Begin

Before you upgrade the software version of Cisco Unified Communications Manager, verify your current software version.

To do that,

Open Cisco Unified Communications Manager Administration.

The following information displays:

Cisco Unified Communications Manager System version.

OR

Login to CLI.

Enter show version active CLI command.


Note If you get the error, GUI lost communication with the system during the upgrade, login again to OS Admin and assume that control to check the upgrade status. Otherwise, you need to use CLI command utlis system upgrade status to check the upgrade status.


Special Upgrade Considerations

Cisco only supports replacing failed hard drives. Cisco does not support drive pulling/swapping as a method of fast upgrade reversion, restore, or server recovery.

Upgrade Paths to Cisco Unified Communications Manager 6.1(4a)

For information about supported Cisco Unified CM upgrades, see the Cisco Unified Communications Manager Compatibility Matrix at the following URL:

http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/compat/ccmcompmatr.html.


Caution Use the ISO files that are mentioned in the "Upgrading to Unified CM Release 6.1(4a) by Using the UCSInstall File" section for upgrades from 6.1(1x) and later.

Upgrading to Unified CM 6.1(4a) from Unified CM 4.x and 5.x

If you are upgrading from 4.1.3, 4.2.3, 4.3(2), 5.1.2, or 5.1.3, use the Product Upgrade Tool (PUT) or the PUT for registered customers only to obtain a media kit and license or purchase the upgrade from Cisco Sales.

To use the PUT, you must enter your Cisco contract number (Smartnet, SASU, or ESW) and request the CD/CD set. If you do not have a contract for Cisco Unified Communications Manager, you must purchase the upgrade from Cisco Sales.


Note During an upgrade from a compatible Cisco Unified CM 5.1 version (see the Compatibility Matrix at http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/compat/ccmcompmatr.html) to Cisco Unified CM 6.1(4a) by using a DVD, in the Software Installation/Upgrade window, ignore the checksum step that tells you "To ensure the integrity of the installation file, verify the MD5 hash value against the Cisco Systems website." Click "Next".


Upgrading from an Engineering Special

If you want to upgrade to Cisco Unified CM 6.1(4a) and you are currently running an Engineering Special (ES), contact TAC to obtain the fixes that are included in the ES that you currently use.

Upgrading to Unified CM Release 6.1(4a) by Using the UCSInstall File

Because of its size, the UCSInstall iso file, UCOS_6.1.4.2000-2.sgn.iso, comprises two parts:

UCSInstall_UCOS_6.1.4.2000-2.sgn.iso_part1of2

UCSInstall_UCOS_6.1.4.2000-2.sgn.iso_part2of2

Procedure


Step 1 From www.cisco.com, download the two UCSInstall files.

Step 2 Execute one of the following commands to reunite the two parts of the file.


Note The 6.1.4.2000-2 build represents a non-bootable ISO that is only useful for upgrades. You cannot use it for new installations.


a. If you have a Unix/Linux system, cut and paste the following command from this document into the CLI to combine the two parts:

cat UCSInstall_UCOS_6.1.4.2000-2.sgn.iso_part1of2 UCSInstall_UCOS_6.1.4.2000-2.sgn.iso_part2of2 > UCSInstall_UCOS_6.1.4.2000-2.sgn.iso


b. If you have a Windows system, cut and paste the following command from this document into the command prompt (cmd.exe) to combine the two parts:

COPY /B UCSInstall_UCOS_6.1.4.2000-2.sgn.iso_part1of2+UCSInstall_UCOS_6.1.4.2000-2.sgn.iso_part2of2 UCSInstall_UCOS_6.1.4.2000-2.sgn.iso


Step 3 Use an md5sum utility to verify that the MD5 sum of the final file is correct.

f49782f2a28a21c75bf0e157caf2a965 UCSInstall_UCOS_6.1.4.2000-2.sgn.iso

Related Documentation

The documentation that supports Cisco Unified Communications Manager Release 6.1 resides at
http://www.cisco.com/en/US/products/sw/voicesw/ps556/tsd_products_support_series_home.html

Limitations and Restrictions

A recommendation of compatible software releases that have been verified by the test for customers represents a major deliverable of the Cisco Unified Communications System testing. The recommendations, which are not exclusive, represent an addition to interoperability recommendations for each individual voice application or voice infrastructure product.

For a list of software and firmware versions of IP telephony components that were tested for interoperability with Cisco Unified Communications Manager 6.1 as part of Unified Communications System Release 6.1 testing, see http://www.cisco.com/go/unified-techinfo.

For a list of software and firmware versions of contact center components that were tested for interoperability with Cisco Unified Communications Manager 6.1 as part of Unified Communications System Release 6.1 testing, see http://tools.cisco.com/ITDIT/vtgsca/.

Be aware that the release of Cisco IP telephony products does not always coincide with Cisco Unified Communications Manager releases. If a product does not meet the compatibility testing requirements with Cisco Unified Communications Manager, you need to wait until a compatible version of the product becomes available before you can upgrade to Cisco Unified Communications Manager Release 6.1(4a). For the most current compatibility combinations and defects that are associated with other Cisco Unified Communications products, refer to the documentation that is associated with those products.

Software Download URLs

You can access the latest software upgrades for Cisco Unified Communications Manager at http://tools.cisco.com/support/downloads/go/Redirect.x?mdfid=278875240

Important Notes for Cisco Unified Communications Manager 6.1(4a)

The following sections contains important information that may have been unavailable upon the initial release of documentation for Cisco Unified Communications Manager Release 6.1(4a).

CSCta43460 BIOS Update Is Required for MCS 7825-I2 Servers

CSCta43460 BIOS Update Is Required for MCS 7825-I2 Servers

After October 1, 2009, 7825-I2 servers will not start properly.

The critical BIOS update fix has been applied in Cisco Unified Communications Manager Release 6.1(4a).

If you are running any Cisco products on 7825-I2 servers, you must upgrade to Unified CM 6.1(4a) before October 1, 2009

Important Notes for Cisco Unified Communications Manager 6.1(4)

The following sections contains important information that may have been unavailable upon the initial release of documentation for Cisco Unified Communications Manager Release 6.1(4).

Adding or Updating SIP Dial Rules Causes Cisco TFTP Service To Rebuild All Phone Configuration Files

CSCta10219 Unicast Music on Hold May Not Play

Alerts During Upgrades to Cisco Unified Communications Manager Business Edition 6.1(4)

Cisco Unified JTAPI

SFTP Server Products

Windows 2000 Users Must Download Windows Installer 3.0 Updates

Do Not Install Cisco Unified CM in a Large Class A or Class B Subnet That Contains a Large Number of Devices

CSCsu08609 Unanswered Conference Call or Blind Transfer Over QSIG Trunk Goes to Third-Party Voice Messaging System Instead of Called Party

Use Microsoft Outlook to Receive Cisco Unified Communications Manager Licenses

CSCsr80287 Cisco CallManager Service Stops After Upgrade to Cisco Unified Communications Manager 6.x

Important Information About Delete Transaction by Using Custom File in BAT

Partition Size Limitations When You Upgrade from a 5.x Release to a 6.x Release

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

Viewing Privileges for Roles in Cisco Unified CM Administration

TAPS Name Change in Bulk Administration Tool

Basic Uninterruptible Power Supply (UPS) Integration

Strict Version Checking

Serviceability Not Always Accessible from OS Administration

Voice Mailbox Mask Interacts with Diversion Header

CTL Client 5.0 Plug-In Installation Note

Best Practices for Assigning Roles to Serviceability Administrators

For Serviceability, the Administrator That Is Created During Installation Must Not Be Removed

Connecting to Third-Party Voice Messaging Systems

Database Replication When You Revert to an Older Product Release

User Account Control Pop-up Window Displays During Installation of RTMT

CiscoTSP Limitations on Windows Vista Platform

Time Required for Disk Mirroring

Cisco Unified Mobility Supports Nine Locales

Each Remote Destination Supports a Maximum of Two Active Calls

Changes to Cisco Extension Mobility After Upgrade

RTMT Requirement When Cisco Unified Communications Manager Is Upgraded

Serviceability Session Timeout is Not Graceful

Problem Configuring Mobility Identity for Nokia S60 Device in Cisco Unified Communications Manager Administration

Serviceability Limitations When You Modify the IP Address

SIP Network/IP Address Field that is Required for SIP Fallback to SRST Gateway

Network Time Protocol Version 4

Adding or Updating SIP Dial Rules Causes Cisco TFTP Service To Rebuild All Phone Configuration Files

When you add or update a SIP dial rule in Cisco Unified Communications Manager Administration, be aware that the Cisco TFTP service rebuilds all phone configuration files, which may cause CPU to spike on the server where the Cisco TFTP service runs, especially if you have a large system with many phones. To ensure that CPU does not spike, add or update the SIP dial rule during a maintenance window or temporarily stop the Cisco TFTP service in Cisco Unified Serviceability before you make the configuration change. If you stop the Cisco TFTP service, remember to restart the service in Cisco Unified Serviceability after you add or update the SIP dial rule.

CSCta10219 Unicast Music on Hold May Not Play

After you invoke music on hold (MOH) several times, unicast MOH may not play. MOH can be invoked by using hold, transfer, conference, park, and so on.

Workaround - Option 1

Upgrade to a version of Cisco Unified Communications Manager that contains a fix for this issue.

Workaround - Option 2

Configure the MOH servers to send out multicast MOH and unicast MOH on the same MOH resources.

Procedure


Step 1 Configure each MOH audio source ID for multicast.

Step 2 Configure each MOH server to multicast.

Step 3 Make sure that Media Resource Groups (if any are defined) do not have multicast enabled.

Be aware that no network (router) changes to forward multicast MOH packets are required if Media Resource Groups (MRG) are not configured to enable multicast MOH.


Note The MOH servers transmit multicast streams for each MOH source and MOH codec, so network traffic to the local network may increase. The multicast streams will remain continuous and run at all times.

The MOH servers send the multicast streams to the local router; but, if the rounter is not configured to forward the MOH multicast packets, impact to the LAN traffic will be minimal. By default, routers do not forward multicast MOH packets.


Alerts During Upgrades to Cisco Unified Communications Manager Business Edition 6.1(4)

During an upgrade to Cisco Unified Communications Manager Business Edition, users may experience following alerts in the Cisco Unified Real-Time Monitoring Tool. Users may disregard these alerts during the upgrade process:

NumberOfRegisteredPhonesDropped

NumberOfRegisteredMediaDevicesDecreased

NumberOfRegisteredMediaDevicesIncreased

NumberOfRegisteredGatewayDecreased

NumberOfRegisteredGatewayIncreased

Cisco Unified JTAPI

In Cisco Unified Communications Manager Releases 6.x and 5.x, if an application tries to conference two or more addresses on the same terminal, based on the order of participants in the request, an application may receive CiscoJtapiException.CONFERENCE_INVALID_PARTICIPANT for the conference request. The conference might then start successfully with some of the participants. In such cases, no guarantees exist about which application joins the conference. The system creates the conference with only one of the addresses on a terminal. It ignores the other addresses.

This situation occurs in the following scenarios.

Scenario 1

Assume that B1 and B2 represent different addresses on the same terminal, TB.

A -> B1 - GC1

A -> B2 - GC2

A -> C - GC3

Assume that an application issues a conference request GC1.conference(GC2,GC3).

In Cisco Unified Communications Manager Releases 6.x and 5.x, the application receives CiscoJtapiException.CONFERENCE_INVALID_PARTICIPANT; however, A, B1, and C join into conference, and the following normal set of events in a conference scenario occur:

GC1 CiscoConferenceStartEv
 
GC2 TermConnDroppedEv TB
GC2 CallCtlTermConnDroppedEv TB
GC2 ConnDisconnectedEv B1
GC2 CallCtlConnDisconnectedEv B1
GC1 CallCtlTermConnTalkingEv TB
GC2 CiscoCallChangedEv
 
GC1 ConnCreatedEv C
GC1 ConnConnectedEv C
GC1 CallCtlConnEstablishedEv C
GC1 TermConnCreatedEv TC
GC1 TermConnActiveEv TC
GC1 CallCtlTermConnTalkingEv TC
 
GC2 TermConnDroppedEv TC
GC2 CallCtlTermConnDroppedEv TC
GC2 ConnDisconnectedEv C
GC2 CallCtlConnDisconnectedEv C
GC2 CallInvalidEv
GC1 CiscoConferenceEndEv

Scenario 2

Assume that B1 and B2 represent different addresses on the same terminal, TB.

A -> B1 - GC1

A -> B2 - GC2

A -> C - GC3

Assume that an application issues a conference request GC3.conference(GC1,GC2).

In Cisco Unified Communications Manager Release 5.x, the application does not receive an exception, and the request processes successfully. A, C, and B1 join the conference with the regular set of conference events.

In Cisco Unified Communications Manager Releases 5.x and 6.x, the application receives CiscoJtapiException.CONFERENCE_INVALID_PARTICIPANT; however, A, C, B1 join conference, and the normal set of conference events occurs.

SFTP Server Products

Cisco allows you to use any SFTP server product with applications that require SFTP access but recommends SFTP products that have been certified with Cisco through the Cisco Technology Developer Partner program (CTDP). CTDP partners, such as GlobalSCAPE, certify their products with specified version of Cisco Unified Communications Manager. For information on which vendors have certified their products with your version of Cisco Unified Communications Manager, refer to http://www.cisco.com/pcgi-bin/ctdp/Search.pl. For information on using GlobalSCAPE with supported Cisco Unified Communications versions, refer to http://www.globalscape.com/gsftps/cisco.aspx. Cisco uses the following servers for internal testing. You may use one of the servers, but you must contact the vendor for support:

Open SSH (refer to http://sshwindows.sourceforge.net/)

Cygwin (refer to http://www.cygwin.com/)

Titan (refer http://www.titanftp.com/)


Note For issues with third-party products that have not been certified through the CTDP process, contact the third-party vendor for support.


CSCsu08609 Unanswered Conference Call or Blind Transfer Over QSIG Trunk Goes to Third-Party Voice Messaging System Instead of Called Party

A blind transfer or an unanswered conference call that is forwarded to an Avaya system over a QSIG PRI trunk causes the call to go to the third-party voice messaging system instead of the called party. No workaround exists for this issue.

Use Microsoft Outlook to Receive Cisco Unified Communications Manager Licenses

When you obtain a license file from the Product License Registration window on www.cisco.com, the system sends the license file(s) to you via e-mail by using the e-mail ID that you provided. When you receive license files from e-mail clients other than Microsoft Outlook, for example, Microsoft Entourage, additional characters may exist in the license file, which can prevent you from being able to upload the license file in Cisco Unified Communications Manager Administration. To avoid this issue, Cisco recommends that you use Microsoft Outlook when you receive license files for Cisco Unified Communications Manager.

If you obtained a license file with additional characters in it, perform the following procedure:

Procedure


Step 1 Use the CLI to delete the license file from the Cisco Unified Communications Manager server. In the CLI, run the command, file delete license <name of license file>.

Step 2 Restart the Cisco License Manager service in Cisco Unified Serviceability.

Step 3 To save the received license file, use Microsoft Outlook.

Step 4 In Cisco Unified Communications Manager Administration, upload the saved license file, as described in the "Uploading a License File" section of the Cisco Unified Communications Manager Administration Guide.


For More Information

"Licensing" chapter, Cisco Unified Communications Manager System Guide

CSCsr80287 Cisco CallManager Service Stops After Upgrade to Cisco Unified Communications Manager 6.x

After you upgrade to Cisco Unified Communications Manager 6.X from a compatible Cisco Unified CM 5.X release, the Cisco CallManager service does not automatically run, even though Cisco Unified Serviceability shows that the Cisco CallManager service is activated.

Immediately after you complete the upgrade, upload the software feature license that is required for Cisco Unified Communications Manager 6.X in Cisco Unified Communications Manager Administration and restart the Cisco CallManager service in Cisco Unified Serviceability. Until you perform these tasks, devices fail to register with Cisco Unified Communications Manager.

For more information on licensing, refer to the licensing chapters in the Cisco Unified Communications Manager Administration Guide and the Cisco Unified Communications Manager System Guide.

Important Information About Delete Transaction by Using Custom File in BAT

Do not use the insert or export transaction files that are created with bat.xlt for the delete transaction. Instead, you must create a custom file with the details of the records that need to be deleted. Use only this file for the delete transaction. In this custom delete file, you do not need a header, and you can enter values for name, description, or user.

Partition Size Limitations When You Upgrade from a 5.x Release to a 6.x Release

Cisco Unified Communications Manager 5.x releases create disk partitions of a fixed size. If you install a 5.x release on a server with more disk space than is required by the fixed partitions, the partitions still get created at the fixed size.

When you upgrade such a server from a 5.x release to a 6.x release, the disk partitions remain at the fixed size. If you perform a fresh installation of a 6.x release, the disk partitions get created as percentages of the available disk space, so your server will use all the available disk space effectively.


Note Likelihood of getting low active partition disk space alerts, if upgrading from 5.x to 6.1(4) with lots of locales, is low because of improvements made in 6.1(4)


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

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

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.

Clarification for Call Park Configuration

Consider the following information when you configure Call Park:

Call Park numbers cannot overlap between Cisco Unified CM servers. Ensure that each Cisco Unified CM server has its own unique number range.

Call Park numbers may have an associated partition that restricts access to the Call Park numbers and prevents retrieval of parked calls. If partitions are used to restrict access to Call Park numbers, you must define a unique call park number or range of call park extension numbers for each partition in Cisco Unified Communications Manager Administration.

When the end user invokes Call Park, Cisco Unified Communications Manager attempts to find an available Call Park number from a Call Park partition that is currently accessible via the calling search space for the party that invoked Call Park.

Viewing Privileges for Roles in Cisco Unified CM Administration

The Role Configuration window in Cisco Unified CM Administration displays the privileges for each standard role. To access the Role Configuration window, find the role by choosing User Management > Role; when the Find and List Roles window displays, click Find. Click the link for the standard role that you want to view. After the Role Configuration window displays, you can view the privileges in the Resource Access Information pane.

TAPS Name Change in Bulk Administration Tool

Documentation refers to the Tool for Auto-Registered Phone Support (TAPS) as Cisco Unified Communications Manager Auto-Register Phone Tool in the Online Help for Bulk Administration. All references to 'Cisco Unified Communications Manager Auto-Register Phone Tool' in the Bulk Administration Tool Online Help should be read as 'Tool for Auto-Registered Phone Support (TAPS)'. This makes the terminology compliant with the Bulk Administration user interface.

For More Information

For information on configuring additional features in Bulk Administration Tool, refer to the BAT documentation for Cisco Unified CM.

Basic Uninterruptible Power Supply (UPS) Integration

When Cisco Unified Communications Manager 6.1(4) runs on an MCS 7825H2 or MCS 7835H2, basic integration to the UPS model APC SmartUPS 1500VA USB and APC 750VA XL USB gets supported. Integration occurs via a single point-to-point Universal Serial Bus (USB) connection. Serial and SNMP connectivity to UPS does not get supported, and the USB connection must be point-to-point (in other words, no USB hubs). Single- and dual-USB UPS models get supported. The feature activates automatically during bootup if a connected UPS gets detected.

Alternatively, on MCS-7835H2, you can execute the show ups CLI command that shows the current status of the USB-connected APC smart-UPS device and starts the monitoring service if it is not already started.

On supported servers, the CLI command also displays detected hardware, detected versions, current power draw, remaining battery runtime, and other relevant status information.

When the feature is activated, graceful shutdown will commence as soon as the low battery threshold is reached. Resumption or fluctuation of power will not interrupt or abort the shutdown.

For unsupported Cisco Unified Communications Manager releases, MCS models and/or UPS vendor/make/models, you can cause an external script to monitor the UPS. When low battery gets detected, you can log on to Cisco Unified Communications Manager by using Secure Shell (SSH), access the CLI, and execute the utils system shutdown command.

Strict Version Checking

Disaster Recovery System adheres to strict version checking and allows restore only between matching versions of Cisco Unified Communications Manager.


Note Make sure that the restore runs on the same Cisco Unified Communications Manager version as the backup. The Disaster Recovery System supports only matching versions of Cisco Unified Communications Manager for restore.


Consider the following examples of restore to understand strict version checking:

Table 2 Restore Examples

From version
To version
Allowed / Not allowed

6.1.(1).1000-1

6.1(2).1000-1

Not allowed

6.1.(2).1000-1

6.1(2).1000-2

Not allowed

6.1.(2).1000-1

6.1(2).2000-1

Not allowed

6.1.(2).1000-1

6.1(2).1000-1

Allowed


In essence, the product version needs to match, end-to-end, for the Disaster Recovery System to run a successful Cisco Unified Communications Manager database restore.

Serviceability Not Always Accessible from OS Administration

In some scenarios, you cannot access Cisco Unified Serviceability from Cisco Unified OS Administration. The window displays a "Loading, please wait" message indefinitely.

If the redirect fails, log out from Cisco Unified OS Administration, select Cisco Unified Serviceability from the navigation menu, and log in to Cisco Unified Serviceability.

Voice Mailbox Mask Interacts with Diversion Header

When a call gets redirected from a DN to a voice-messaging server/service that is integrated with Unified CM by using a SIP trunk, the voice mailbox mask on the voice-mail profile for the phone modifies the diverting number in the SIP diversion header. Be aware that this behavior is expected because the Unified CM server uses the diversion header to choose a mailbox.

CTL Client 5.0 Plug-In Installation Note

If you are upgrading to the CTL Client 5.0 plug-in, you first need to remove eToken Run Time Environment 3.00 by performing the following steps:

Procedure


Step 1 Download Windows Installer Cleanup Utility at the following URL:

http://support.microsoft.com/kb/290301

Step 2 Install the utility on your PC.

Step 3 Run the utility.

Step 4 Find eToken rte3.0 in the list of programs and remove it.

Step 5 Proceed with CTL Client installation.


Best Practices for Assigning Roles to Serviceability Administrators

Cisco recommends that you configure application users, rather than end users, to access remote nodes to perform such tasks as starting and stopping services. Starting and stopping services requires that the Standard Serviceability Administration and Standard RealtimeAndTraceCollection roles be assigned.

For Serviceability, the Administrator That Is Created During Installation Must Not Be Removed

Removing the Administrator that is created during installation or upgrade can cause communication with remote nodes via Serviceability Administration to fail.

Connecting to Third-Party Voice Messaging Systems

Administrators can connect third-party voice-messaging systems to Cisco Unified Communications Manager. Ensure the voice-messaging system has a simplified message desk interface (SMDI) that is accessible with a null-modem EIA/TIA-232 cable (and an available serial port). To connect the EIA/TIA-232 cable to Cisco Unified Communications Manager Release 5.0 or later, use a Cisco certified serial-to-USB adapter with the part number USB-SERIAL-CA=.

Database Replication When You Revert to an Older Product Release

If you revert the servers in a cluster to run an older product release, you must manually reset database replication within the cluster. To reset database replication after you revert all the cluster servers to the older product release, enter the CLI command utils dbreplication reset all on the publisher server.

When you switch versions by using Cisco Unified Communications Operating System Administration or the CLI, you get a message that reminds you about the requirement to reset database replication if you are reverting to an older product release. The caveats CSCsl57629 and CSCsl57655 also document this behavior.

For information about the utils dbreplication clusterreset, utils dbreplication dropadmindb, and utils dbreplication forcedatasyncsub commands, see the Command Line Interface Reference Guide for Cisco Unified Communications Solutions Release 7.0(1) document at http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/cli_ref/7_0_1/cli_ref.html.

User Account Control Pop-up Window Displays During Installation of RTMT

When you install RTMT on the Microsoft Vista platform, the system displays the User Account Control pop-up window to indicate that an unidentified program wants access to your computer. This occurs because of a limitation in the InstallAnywhere software. This one-time pop-up displays only when you are installing RTMT. To continue, select Allow.

CiscoTSP Limitations on Windows Vista Platform

Always perform the first-time installation of the CiscoTSP and Cisco Unified Communications Manager TSP Wave Driver on a Vista machine as a fresh install.

If secure connection to Cisco Unified Communications Manager is to be used, turn off the Windows firewall.

If Cisco Unified Communications Manager TSP Wave Driver is used for inbound audio streaming, turn off the Windows firewall.

If Cisco Unified Communications Manager TSP Wave Driver is used for audio streaming, disable all other devices in the "Sound, video and game controllers" group.

Time Required for Disk Mirroring

Disk mirroring on server model 7825 I3 with 160 GB SATA disk drives takes approximately 3 hours.

Disk mirroring on server model 7828 I3 with 250 GB SATA disk drives takes approximately 4 hours.

Cisco Unified Mobility Supports Nine Locales

Cisco Unified Mobility (Mobile Connect and Mobile Voice Access) support a maximum of nine locales, so Cisco Unified Communications Manager Administration blocks you from configuring 10 or more locales for Cisco Unified Mobility. In the Mobility Configuration window, more than nine locales can display in the Available Locales pane if they are installed for Cisco Unified Communications Manager, but you can only save nine locales in the Selected Locales pane. If you attempt to configure more than nine locales for Cisco Unified Mobility, the following message displays: "Update failed. Check constraint (informix.cc_ivruserlocale_orderindex) failed."

Each Remote Destination Supports a Maximum of Two Active Calls

For Cisco Unified Mobility, each remote destination supports a maximum of two active calls via Cisco Unified Communications Manager. Using the enterprise feature access directory number (DID number) to transfer or conference with DTMF counts as one call. When a Cisco Unified Mobility user receives a call while the user has two active calls for the remote destination or while the user is using DTMF to transfer/conference a call from the remote destination, the received call does not reach the remote destination and instead goes to the enterprise voice mail; that is, if Call Forward No Answer (CFNA) is configured or if the call is not answered on a shared line.

Changes to Cisco Extension Mobility After Upgrade

If you chose a user-created profile from the Log Out Profile drop-down list on the Phone Configuration window and checked the Enable Extension Mobility check box, the settings in that profile become the permanent settings on the phone after an upgrade from Cisco Unified CallManager 4.x or Cisco Unified Communications Manager 5.x to Cisco Unified Communications Manager 6.1(1a).

RTMT Requirement When Cisco Unified Communications Manager Is Upgraded

If you are running the Cisco Unified Communications Real-Time Monitoring Tool (RTMT) client and monitoring performance counters during a Cisco Unified Communications Manager upgrade, the performance counters will not update during and after the upgrade. To continue monitoring performance counters accurately after the upgrade completes, you must either reload the RTMT profile or restart the RTMT client.

Serviceability Session Timeout is Not Graceful

When a session has been idle for more than 30 minutes, the Cisco Unified Serviceability user interface allows you to make changes before it indicates that the session timed out and redirects you to the login window. After you log in again, you may need to repeat those changes. This behavior occurs in the Alarm, Trace, Service Activation, Control Center, and SNMP windows.

Workaround

If you know that the session has been idle for more than 30 minutes, log out by using the Logout button before making any changes in the user interface.

Problem Configuring Mobility Identity for Nokia S60 Device in Cisco Unified Communications Manager Administration

The following message may display in the Phone Configuration window in Cisco Unified Communications Manager Administration when you try to configure Mobility Identity for the Nokia S60 device: "Add failed. [10102] Check the type of device specified in fkDevice_DualMode. Remote Destinations other than Dual Mode must use fkDevice_RemoteDestinationTemplate."

The error occurs under one of the following circumstances:

Circumstance 1—You provisioned Nokia S60 devices by using the pre-6.1(1a) Nokia S60 .cop file before or after you upgraded to Cisco Unified Communications Manager 6.1(1a). After you installed the latest 6.1(1a) compatible Nokia S60 .cop file, you tried to configure Mobility Identity for an existing Nokia S60 device in the Phone Configuration window in Cisco Unified Communications Manager Administration.

Circumstance 2—Previously, you provisioned Nokia S60 devices by using the pre-6.1(1a) Nokia S60 .cop file. Then, you installed the latest 6.1(1a) compatible Nokia S60 .cop file. After the latest .cop file was installed, you tried to configure Mobility Identity for an existing Nokia S60 device in the Phone Configuration window in Cisco Unified Communications Manager Administration.

If the message displays, you can perform the following tasks to ensure that you can configure Mobility Identity for the Nokia S60 device:

1. In Cisco Unified Communications Manager Administration 6.1, disable auto-registration.

2. In the Find/List Phone window in Cisco Unified Communications Manager Administration, delete all Nokia S60 records.


Tip In case of large number of existing Nokia devices, Cisco recommends that you delete the Nokia S60 records by using the Bulk Administration Tool by choosing Bulk Administration > Phones > Delete Phones


3. In Cisco Unified Communications Manager Administration, configure all Nokia S60 devices by choosing Device > Phone > Add New > Nokia S60.


Tip For a large number of Nokia S60 devices, you can provision the devices in the Bulk Administration Tool by choosing Bulk Administration > Phones > Insert Phones.


4. Reset all Nokia S60 devices.

Serviceability Limitations When You Modify the IP Address

When you modify the IP Address field, you cannot access the RTMT profiles, custom counters, custom alerts, and generic queries for Trace & Log Collection Tool (TLC) for that server.

You should manually remove any RTMT profiles, custom counters, custom alerts, and generic queries for Trace and Log Collection Tool (TLC) that were set for the old IP Address. When you modify the IP Address field, you will need to re-create the RTMT profile, custom counters, custom alerts, and generic queries for TLC the next time that you log in to the server on RTMT.

Cisco AMC Service includes two user-configurable service parameters, Primary Collector and Failover Collector. These service parameters use Host Name/IP Address to designate the primary and failover AMC server. If you change the IP address of the AMC primary collector or failover collector, you should check these service parameters and update them accordingly.

Cisco Serviceability Reporter service includes one user-configurable service parameter, RTMT Reporter Designated Node. This service parameter uses Host Name/IP Address to designate the node on which RTMTReporter runs. If you changed the IP address of the RTMT Reporter Designated Node, you should check this service parameter and update it accordingly.

SIP Network/IP Address Field that is Required for SIP Fallback to SRST Gateway

Although Cisco Unified Communications Manager Administration does not list the SIP Network/IP Address field as a required setting, you must configure the SIP Network/IP Address field and the SIP Port field in the SRST Reference Configuration window for a SIP device to fall back to the SRST-enabled gateway. For more information on these fields and SRST references, refer to the Cisco Unified Communications Manager Administration Guide.

Network Time Protocol 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).

New and Changed Information

This section contains information on the following topics:

Installation, Upgrade, and Migration

Documentation Changes

Command Line Interface

Cisco Unified Communications Manager Administration

Cisco Unified Communications Manager Features and Applications

Bulk Administration Tool

Installation, Upgrade, and Migration

The following sections describe the changes for installation, upgrade, and migration in Cisco Unified Communications Manager 6.1(4):

System History Log for Cisco Unified Communications Manager

System History Log for Cisco Unified Communications Manager

This system history log provides a central location for getting a quick overview of the initial system install, system upgrades, Cisco option installations, DRS backups and DRS restores, as well as switch version and reboot history.

Description

This section provides a description of the system history log feature.

Overview

The system history log exists as a simple ASCII file, system-history.log, and the data does not get maintained in the database. Because it does not get excessively large, the system history file does not get rotated.

The system history log provides the following functions:

Logs the initial software installation on a server.

Logs the success and failure or cancellation of every software upgrade (Cisco option files and patches).

Logs every DRS backup and restore that is performed.

Logs every invocation of Switch Version that is issued through either the CLI or the GUI.

Logs every invocation of Restart and Shutdown that is issued through either the CLI or the GUI.

Logs every boot of the system. If not correlated with a restart or shutdown entry, the boot results from a manual reboot, power cycle, or kernal panic.

Maintains a single file that contains the system history, since initial installation or since feature availability.

Exists in the install folder. Access the log from the CLI by using the file commands and by using the Real-Time Monitoring Tool (RTMT).

System History Log Fields

Each system history log entry contains the following fields:

<timestamp> <userid> <action> <description> <start>

The log also displays a common header which contains information about product name, product version and kernel image.

=======================================

Product Name - Cisco Unified Communications Manager

Product Version - 7.1.0.39000-9023

Kernel Image - 2.6.9-67.EL

=======================================

The system history log fields can contain the following values:

timestamp—Displays the local time and date on the server with the format mm/dd/yyyy hh:mm:ss.

userid—Displays the user name of the user who invokes the action.

action—Displays one of the following actions:

Install

Windows Upgrade

Upgrade During Install

Upgrade

Cisco Option Install

Switch Version

System Restart

Shutdown

Boot

DRS Backup

DRS Restore

description—Displays one of the following messages:

Version: Displays for the Install, Windows Upgrade, Upgrade During Install, Upgrade, and ServerPak Install actions.

Cisco Option file name: Displays for the Cisco Option Install action.

Timestamp: Displays for the DRS Backup and DRS Restore actions.

Active version to inactive version: Displays for the Switch Version action.

Active version: Displays for the System Restart, Shutdown, and Boot actions.

result—Displays the following results:

Start

Success or Failure

Cancel

Example

Example 1 shows a sample of the system history log.

Example 1 System History Log

admin:file dump install system-history.log
=======================================
Product Name -    Cisco Unified Communications Manager
Product Version - 6.1.2.9901-117
Kernel Image -    2.4.21-47.EL.cs.3BOOT
=======================================
07/25/2008 14:20:06 | root: Install 6.1.2.9901-117 Start 
07/25/2008 14:50:38 | root: Boot 6.1.2.9901-117 Start
07/25/2008 15:05:37 | root: Install 6.1.2.9901-117 Success 
07/25/2008 15:05:38 | root: Boot 6.1.2.9901-117 Start 
07/30/2008 10:08:56 | root: Upgrade 6.1.2.9901-126 Start 
07/30/2008 10:46:31 | root: Upgrade 6.1.2.9901-126 Success 
07/30/2008 10:46:43 | root: Switch Version 6.1.2.9901-117 to 6.1.2.9901-126 Start 
07/30/2008 10:48:39 | root: Switch Version 6.1.2.9901-117 to 6.1.2.9901-126 Success 
07/30/2008 10:48:39 | root: Restart 6.1.2.9901-126 Start 
07/30/2008 10:51:27 | root: Boot 6.1.2.9901-126 Start 
08/01/2008 16:29:31 | root: Restart 6.1.2.9901-126 Start 
08/01/2008 16:32:31 | root: Boot 6.1.2.9901-126 Start 

CLI Considerations

You can access the system history log by using the CLI file command; for example:

file view install system-history.log

file get install system-history.log

Cisco Unified Communications Manager Administration Configuration Tips

No Cisco Unified Communications Manager Administration configuration tips exist for this feature.

GUI Changes

No GUI changes exist for this feature.

Service Parameter and Enterprise Parameter Changes

No service parameter and enterprise parameter changes exist for this feature.

Installation/Upgrade (Migration) Considerations

No installation or upgrade consideration exist for this feature.

Serviceability Considerations

To access the system history log in RTMT, navigate to RTMT Trace Collection:

RTMT > Trace Log Collection

BAT Considerations

No BAT considerations exist for this feature.

CAR/CDR Considerations

No CAR/CDR considerations exist for this feature.

Security Considerations

No security considerations exist for this feature.

AXL and CTI Considerations

No AXL and CTI considerations exist for this feature.

User Tips

No user tips exist for this feature.

For More Information

For more information about using the CLI, see the Cisco Unified Communications Operating System Administration Guide or the Command Line Interface Reference Guide for Cisco Unified Solutions.

For more information about RTMT, see the Cisco Unified Communications Manager Real-Time Monitoring Tool Administration Guide.

Documentation Changes

This section highlights some documentation changes for the 6.1(4) release. This section does not contain all the documentation updates for the 6.1(4) release. Use this section in conjunction with the information in the "New and Changed Information" section and the "Documentation Updates" section.

For information on features that are introduced in Cisco Unified Communications Manager Business Edition 6.1(4), see the Release Notes for Cisco Unified Communications Manager Business Edition, Release 6.1(4). For a list of documents that are updated for Cisco Unified Communications Manager Business Edition 6.1(4), refer to the Cisco Unified Communications Manager Business Edition Documentation Guide for Release 6.1(4).

When you view online help in Cisco Unified Communications Manager 6.1(4), be aware that the online help did not get updated for 6.1(4). The following graphical user interfaces (GUIs) contain online help:

Cisco Unified Communications Manager Administration, which displays online help from 6.1(1)

Cisco Unified Reporting, which displays online help from 6.1(1)

Cisco Unified Serviceability, which displays online help from 6.1(1)

Cisco Unified Communications Operating System Administration, which displays online help from 6.1(1)

Cisco Unity Connection Serviceability, which displays online help from 6.1(1)

Cisco Unity Connection Administration, which displays online help from 6.1(1)

Command Line Interface

The Command Line Interface Reference Guide for Cisco Unified Communications Solutions Release 6.1(3) does not contain updated information for the show memory command. Use the following updated information.

show memory

This command displays information about the server memory.

Command Syntax

show memory

count

modules

size

Options

count—Displays the number of memory modules on the system.

modules—Displays detailed information about all the memory modules.

size—Displays the total amount of memory.

Parameters

None

Cisco Unified Communications Manager Administration

This section contains information on the following topics:

New and Updated Enterprise and System Parameters

Menu Changes

Cisco Unified Communications Manager Features and Applications

New and Updated Enterprise and System Parameters

The following sections contain information on new and updated enterprise and service parameters:

Enterprise Parameters

Service Parameters

Enterprise Parameters

To access the enterprise parameters in Cisco Unified Communications Manager Administration, choose System > Enterprise Parameters. To display the help for the service parameter, click the name of the enterprise parameter in the window.

Cisco Unified Communications Manager 6.1(4) does not contain any new enterprise parameters.

Service Parameters

To access the service parameters in Cisco Unified Communications Manager Administration, choose System > Service Parameters. Choose the server and the service name that the parameter supports. For some parameters, you may need to click Advanced to display the service parameter. To display the help for the service parameter, click the name of the service parameter in the window.

The SIP Interoperability Enabled service parameter, which supports the Cisco CallManager service, determines whether Cisco Unified Communications Manager supports Session Initiation Protocol (SIP) for SIP stations and SIP trunks. Devices that run SIP, for example, phones and trunks, require that you set this parameter to True; when you set this parameter to False, Cisco Unified Communications Manager ignores SIP messages, and SIP devices do not function; that is, phones that run SIP cannot register with Cisco Unified Communications Manager and SIP trunks cannot interact with Cisco Unified Communications Manager. The default value specifies True. You must restart the Cisco CallManager service if you change the value of this parameter.

Menu Changes

This section contains information on the following menus in Cisco Unified Communications Manager Administration:

Main Window

System

Call Routing

Media Resources

Voice Mail

Device

Application

User Management

Bulk Administration

Main Window

No changes exist for the main window.

System

No changes exist for the System menu.

Call Routing

No changes exist for the Call Routing menu.

Media Resources

No changes exist for the Media Resources menu.

Voice Mail

No changes exist for the Voice Mail menu.

Device

No changes exist for the Device menu.

Application

No updates or new fields exist for this menu.

User Management

No updates or new fields exist for this menu.

Bulk Administration

No changes exist for the Bulk Administration.

Cisco Unified Communications Manager Features and Applications

This section contains information on the following Cisco Unified Communications Manager Administration features and applications:

IPMA Restart

Redirected Dialed Number Identification Service and Diversion Header

IPMA Restart

As of Release 6.1(4), if the system administrator changes a user username, preferred location, or password (assistants), that user does not get logged off. For user-ID changes, neither the manager nor his or her assistant gets logged off when that manager user ID is changed; however, an assistant gets logged off the assistant phone and the Assistant Console when that assistant user ID is changed.

Redirected Dialed Number Identification Service and Diversion Header

Release 6.1(4) adds the Redirected Dialed Number Identification Service (RDNIS) and diversion header capability for certain calls that use the Cisco Unified Mobility Mobile Connect feature.

The RDNIS/diversion header for Mobile Connect enhances this Cisco Unified Mobility feature to include the RDNIS or diversion header information on the forked call to the mobile device. Service providers and customers use the RDNIS for correct billing of end users who make Cisco Unified Mobility Mobile Connect calls.

For Mobile Connect calls, the Service Providers use the RDNIS/diversion header to authorize and allow calls to originate from the enterprise, even if the caller ID does not belong to the enterprise Direct Inward Dial (DID) range.

Example Use Case

Consider a user that has the following setup:

Desk phone number specifies 89012345.

Enterprise number specifies 4089012345.

Remote destination number specifies 4088810001.

User gets a call on desk phone number (89012345) that causes the remote destination (4088810001) to ring as well.

If the user gets a call from a nonenterprise number (5101234567) on the enterprise number (4089012345), the user desk phone (89012345) rings, and the call gets extended to the remote destination (4088810001) as well.

Prior to the implementation of the RDNIS/diversion header capability, the fields populated as follows:

Calling Party Number (From header in case of SIP): 5101234567

Called Party Number (To header in case of SIP): 4088810001

After implementation of the RDNIS/diversion header capability, the Calling Party Number and Called Party Number fields populate as before, but the following additional field gets populated as specified:

Redirect Party Number (Diversion Header in case of SIP): 4089012345

Thus, the RDNIS/diversion header specifies the enterprise number that is associated with the remote destination.

Configuration in Cisco Unified Communications Manager Administration

To enable the RDNIS/diversion header capability for Mobile Connect calls, ensure the following configuration takes place in Cisco Unified Communications Manager Administration:

All gateways and trunks must specify that the Redirecting Number IE Delivery — Outbound check box gets checked.

In Cisco Unified Communications Manager Administration, you can find this check box by following the following menu paths:

For H.323 and MGCP gateways, execute Device > Gateway and find the gateway that you need to configure. In the Call Routing Information - Outbound calls pane, ensure that the Redirecting Number IE Delivery - Outbound check box gets checked. For T1/E1 gateways, check the Redirecting Number IE Delivery - Outbound check box in the PRI Protocol Type Information pane.

For SIP trunks, execute Device > Trunk and find the SIP trunk that you need to configure. In the Outbound Calls pane, ensure that the Redirecting Diversion Header Delivery - Outbound check box gets checked.

Bulk Administration Tool

This section contains information on the following topic:

Inserting User Device Profiles and Phones into Cisco Unified Communications Manager

Inserting User Device Profiles and Phones into Cisco Unified Communications Manager

While you insert user device profiles for user devices and inserting phones into Cisco Unified Communications Manager, the following check boxes get enabled for selection after you have checked the Override the existing configuration check box.

Delete all existing speed dials before adding new speed dials.

Delete all existing BLF Speed Dials before adding new BLF Speed Dials.

Delete all existing Subscribed Services before adding new services.


Note Check the check box(es) to delete all existing Speed Dials, BLF Speed Dials, or Subscribed Services records and add new records. Leave the check box(es) unchecked if you want to append these to existing records.


Caveats

The following sections contain information on how to obtain the latest resolved caveat information and descriptions of open caveats of severity level 1, 2, and 3.

Caveats describe unexpected behavior on a Cisco Unified Communications Manager server. Severity 1 caveats represent the most serious caveats, severity 2 caveats represent less serious caveats, and severity 3 caveats represent moderate caveats.

Resolved Caveats

You can find the latest resolved caveat information for Cisco Unified Communications Manager Release 6.1(4) by using Bug Toolkit, which is an online tool that is available for customers to query defects according to their own needs.

Procedure

From http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs perform the following:


Step 1 In the Select Product Category list, double-click Voice and Unified Communications.

Step 2 In the Select Product list, double-click Cisco Unified Communications Manager (CallManager).

Step 3 From the Version drop-down list, select the Unified CM version train for which you want to see defects (for example, for Unified CM Release 6.1(3x), select 6.1.).

Step 4 Under Advanced Options, select Use custom settings for severity, status, and others.

Step 5 In the options that display, click the Open check box to deselect that option.

Now, the only option that will get acted upon is the Fixed option.

Step 6 Click Search.



Tip You need an account with Cisco.com (Cisco Connection Online) to use the Bug Toolkit to find open and resolved caveats of any severity for any release.

To access the Bug Toolkit, log on to http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs.


Using Bug Toolkit

Known problems (bugs) get graded according to severity level. These release notes contain descriptions of

All severity level 1 or 2 bugs.

Significant severity level 3 bugs.

You can search for problems by using the Cisco Software Bug Toolkit.

To access Bug Toolkit, you need the following items:

Internet connection

Web browser

Cisco.com user ID and password

To use the Software Bug Toolkit, follow these steps:

Procedure


Step 1 To access the Bug Toolkit, go to http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs.

Step 2 Log in with your Cisco.com user ID and password.

Step 3 To look for information about a specific problem, enter the bug ID number in the "Search for Bug ID" field; then, click Go.

For information about how to search for bugs, create saved searches, create bug groups, and so on, click Help in the Bug Toolkit window.

Open Caveats

The "Open Caveats as of September 18, 2009" section describes possible unexpected behaviors, supported by component, in Cisco Unified Communications Manager Release 6.1(4).


Tip For more information about an individual defect, click the associated Identifier in "Open Caveats as of September 18, 2009" section to access the online record for that defect, including workarounds.


Understanding the Fixed-in Version and the Integrated-in Fields in the Online Defect Record

When you open the online record for a defect, you may see data in the "First Fixed-in Version" or "Integrated-in" fields. The information that displays in these fields identifies the list of Cisco Unified Communications Manager interim versions in which the defect was fixed. These interim versions then get integrated into Cisco Unified Communications Manager releases.

Some more clearly defined versions include identification for Engineering Specials (ES) or Service Releases (SR); for example 03.3(04)ES29 and 04.0(02a)SR1. However, the version information that displays for the Cisco Unified Communications Manager maintenance releases may not be as clearly identified.

The following examples show how you can decode the maintenance release interim version information. These examples show you the format of the interim version along with the corresponding Cisco Unified Communications Manager release that includes that interim version. You can use these examples as guidance to better understand the presentation of information in these fields.

005.000(000.123) = Cisco Unified Communications Manager Release 5.0(1)

005.000(001.008) = Cisco Unified Communications Manager Release 5.0(2)

005.001(002.201) = Cisco Unified Communications Manager Release 5.1(3)

006.000(000.123) = Cisco Unified Communications Manager Release 6.0(1)

006.001(003.150) = Cisco Unified Communications Manager Release 6.1(4)


Note Because defect status continually changes, be aware that Open Caveats as of September 18, 2009 reflects a snapshot of the defects that were open at the time this report was compiled. For an updated view of open defects, access Bug Toolkit and follow the instructions as described in the "Using Bug Toolkit" section.



Tip Bug Toolkit requires that you have an account with Cisco.com (Cisco Connection Online). By using the Bug Toolkit, you can find caveats of any severity for any release. Bug Toolkit may also provide a more current listing than this document provides. To access the Bug Toolkit, log on to http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs.


Open Caveats as of September 18, 2009

Table 3Table 3 contains the open caveats that existed on September 18, 2009.

Table 3 Open Caveats as of September 18, 2009 

CSCtc02687

bat

After user saves the UDP file format configuration, the Selected Device Field disappears.

CSCtb51714

cmcti

Number Of Active CMLinks does not match the actual number of active CM service.

CSCtc05360

cmcti

ProcessForwardManager DmPidRes is incorrect because of race condition.

CSCtc03241

cmui

Adding a Timeout, Button, User parameter to a previously defined SIP Dial Rule pattern with multiple patterns causes the that parameter to be added to second pattern.

CSCtb68090

cp-cac

Race condition leads to locations bandwidth leak in cdcc.

CSCtb92379

cp-huntlist

User receives calls twice when member is logged out of hunt group.

CSCta96039

cp-mediacontrol

Fax fails if faxserver sends reinvite for T38 before voice call gets established.

CSCtb41812

cp-mediacontrol

Unified CM mid-call H.323 capabilities renegotiation exposes race condition.

CSCtb52833

cp-sip-trunk

Unnecessary MTP inserted for DTMF after call has been transfered.

CSCtb52363

cp-supplementaryservices

Transfer from CAD leaves agent in hung state.

CSCta75630

cp-supplementaryservices

Forward No Call Answer External to internal extension does not work.

CSCta29539

cpi-os

Default net-snmp logrotate configuration causes weekly agent restart.

CSCsw14030

cpi-security

User cannot specify two IPSEC policies to the same endpoint in Unified CM.

CSCtc01467

curt

The need exists to change the code to use StringBuffer instead of String in RunCmd.java.

CSCso35247

database

The need exists for database replication setup to occur more quickly.

CSCtb65083

database

The need exists for Unified CM DBL JDBC connector to auto-discard failed connectors from pool.

CSCsv95745

rtmt

RTMT: Create directory button displays disabled.

CSCtb80964

tapisdk

Race condition caused by incorrectly handled remote access connection.


Documentation Updates

This section contains information on documentation omissions, errors, and updates for the following Release 6.1(4) documentation:

CDR Analysis and Reporting

Cisco Unified Communications Operating System

Cisco Unified Communications Manager Administration

Security

Bulk Administration Tool

Cisco Unified IP Phones

CDR Analysis and Reporting

This section contains information on documentation omissions, errors and updates for the Cisco Unified Communications Manager CDR Analysis and Reporting Administration Guide.

"Mailing a Report" Recipients

"Mailing a Report" Recipients

The "Mailing a Report" chapter in the CDR Analysis and Reporting Administration Guide omits this information:

When the Mailing option gets enabled, End users receive the individual billing summary.

Cisco Unified Communications Operating System

This section contains information on documentation ommissions, errors, and updates for the Cisco Unified Communications Operation System Administration Guide

Disk Space Before Upgrading

Disk Space Before Upgrading

Before you upgrade to Cisco Unified Communications Manager from supported appliance releases, make sure that you have enough disk space on the common partition to perform the upgrade. To ensure that you have enough disk space, determine the size of the ISO file on your DVD or on Cisco.com. If you are upgrading from a local source (DVD), you need the same amount of disk space as the size of the ISO file. If you are upgrading from a network source, you need twice the amount of disk space as the size of the combined ISO file.

To verify the disk space on the common partition, do one of the following tasks:

Use the show status CLI command and note the information that displays under the Disk/logging heading.

From Cisco Unified Communications Operating System, choose Show > System.

From Cisco Unified Real-Time Monitoring Tool, choose System > Server > Disk Usage. Choose the server from the Disk Usage at Host drop-down list box and view the Used Space (MB) for the Common partition.

If you do not have enough disk space, use Cisco Unified Real-Time Monitoring Tool to collect core and trace files and delete them from the server. For more information on collecting files, refer to the Cisco Unified Real-Time Monitoring Tool Administration Guide.

You can also use the log partition monitoring service or the command line interface (CLI) to delete files on your server; however, Cisco does not recommend using these tools to delete files during regular business hours, as they can impact system performance. For more information on configuring log partition monitoring, see the Cisco Unified Real-Time Monitoring Tool Administration Guide. For more information on the CLI, see the Command Line Interface Reference Guide for Cisco Unified Communications Solutions.


Note In order to prevent disk usage issues due to large numbers of trace files in the future, you should review your trace configuration settings in Cisco Unified Serviceability (Trace > Configuration). You can reduce the maximum number of trace files for your services or set the trace settings to the default values.


Cisco Unified Communications Manager Administration

This section contains information on documentation omissions, errors, and updates for the Cisco Unified Communications Manager Administration Guide, Cisco Unified Communications Manager Features and Services Guide, and the Cisco Unified Communications Manager System Guide.

Cisco Unified Communications Manager Administration Guide

Route Plan Report Description Omits Mention of Mobile Voice Access Numbers

End User Chapter Includes Incorrect Information for Manager User ID Field

For the Manager User ID field, enter the user ID of the end user manager ID..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

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 is Not Required for Cisco Unity Connection 2.x

Incorrect Documentation Exists 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

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

Cisco Unified Communications Manager System Guide

Considerations for LDAP Port Configuration

RSVP Reservation Teardown for Shared-Line Calls

Application Server Configuration is 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

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

Cisco Unified Communications Manager Features and Services Guide

Intercom Calls Cannot Be Placed on Hold

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 does Not get 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

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

You cannot delete the server where you install Cisco Unified Communications Manager Business Edition. Disregard all information on deleting a server in the Cisco Unified Communications Manager Administration Guide for Cisco Unified Communications Manager Business Edition and Cisco Unified Communications Manager System Guide for Cisco Unified Communications Manager Business Edition.

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

Application Server Configuration is 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 Exists 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(4) 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(4).

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.

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

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.

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 represents 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 is 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 by 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 4 describes the configurable threshold values:

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

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

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

Intercom Calls Cannot Be Placed on Hold

The Restrictions section of the "Intercom" chapter in the Cisco Unified Communications Manager Features and Services Guide incorrectly indicates that an intercom call can be placed on hold. Actually, you cannot place an intercom call on hold.

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

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) (and later 6.x releases), 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 following information.

Correct Information

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.


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 does Not get 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, as well as an additional (final) step that was omitted in previous versions.

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 Publisher IP Addr>:8080/ccmivr/pages/IVRMainpage.vxml

Sample configuration before IOS Version 12.3(12)

call application voice Unified CCM

http://<Unified CM 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 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

Step 5 On the Cisco Unified Communications Manager, create a new route pattern to redirect the incoming MVA number to the H.323 gateway that has the vxml script loaded. Ensure that the Incoming CSS of the gateway can access the partition in which the new route pattern gets created.


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 Publisher IP Addr>:8080/ccmivr/pages/IVRMainpage.vxml

Sample configuration before IOS Version 12.3(12)

call application voice Unified CCM

http://<Unified CM 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 symbols * (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.

Security

This section contains information on documentation omissions, errors, and updates for the Cisco Unified Communications Manager Security Guide.

Definition of Locally Significant Certificate

Support for Certificates from External CAs

CAPF System Interactions and Requirements

Security Icons and Encryption

Software Conference Bridge Not Supported

Definition of Locally Significant Certificate

The definition of Locally Significant Certificate (LSC) in the Cisco Unified Communications Manager Security Guide needs correction. A third-party certificate authority (CA), cannot issue an LSC. An LSC represents a digital X.509v3 certificate that CAPF issues. It gets installed on a phone or JTAPI/TAPI/CTI application.

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 Cisco Unified Communications Manager server, 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 back to an encrypted phone that is configured on the same server as the phone that transferred the call, the call does not get encrypted, and the lock icon does not display even though the encrypted phones are configured on the same server.

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.

Bulk Administration Tool

This section contains information on documentation omissions, errors, and updates for the Cisco Unified Communications Manager 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)—Phone Template Configuration Window in BAT

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

Limitations in Validation of Phones and User Device Profiles

Fields Omitted in Search Results on the Update Phones Window

Insert / Update Users Credential Policy

Reset Password/PIN

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

Limitations in Validation of Phones and User Device Profiles

The validation of phones and user device profiles has the following limitations:

The validation process only checks for the number of lines that are configured on the template; it does not check the line numbers that are configured on the template. After running the Validate phones - specific details or the Validate UDP - specific details job, the administrator sees the following message in the log when the CSV date file contains more lines than are supported by the phone template: "WARNING: CSV contains more number of lines than are supported by the phone template." If blank Directory Numbers and/or blank Speed dials and/or blank Busy Lamp Field Speed Dials exist, this indicates that the warning message that is displayed in the summary log file may be inaccurate.

The validate process does not check whether mandatory fields are specified in the CSV file.

If IP phone service parameters are specified in the phone text file, the validate process only checks whether a parameter exists with a name that is specified in the CSV on Cisco Unified Communications Manager. It does not check whether the parameter that is specified is configured on the IP phone service.

Export Phones/Export UDPs - All details in BAT exports all the fields, even if a particular product does not support some fields. The validate process will display errors for some fields. Such fields will have default values in the exported files, and the insert job will not fail. The administrator can ignore such errors on the Validate Phones Configuration/ Validate UDP Configuration window.

Fields Omitted in Search Results on the Update Phones Window

On the Update Phones window, certain fields may not display if the search results include devices of multiple types and protocols. Make sure that you have the phones of same type and protocol for all the fields to display.

For example, Product Specific Configuration will display only if devices of same type and protocol are selected in the Find and List window.

Insert / Update Users Credential Policy

While you are inserting/updating users, the Credential policy settings get taken from the Default Credential Policy.

Reset Password/PIN

The credential settings that display on the Reset Users window reset the settings for password as well as PIN.

Cisco Unified IP Phones

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

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.