Guest

Cisco Unified Communications Manager (CallManager)

Release Notes for Cisco Unified Communication Manager Release 6.1(3a)

  • Viewing Options

  • PDF (1.2 MB)
  • Feedback
Release Notes for Cisco Unified Communications Manager Release 6.1(3a)

Table Of Contents

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

Contents

Introduction

System Requirements

Installation Notes

Windows 2000 Users Must Download Windows Installer 3.0 Updates

Do Not Install 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(3x)

Before You Begin

Upgrade Paths To Cisco Unified Communications Manager 6.1(3x)

Upgrading to Unified CM 6.1(3x) From Unified CM 4.x and 5.x

Upgrading From an Engineering Special

Upgrading From Cisco Unified Communications Manager Release 6.1(1x) or higher to Release 6.1(3a) by Using the UCSInstall File

Related Documentation

Limitations and Restrictions

Important Notes

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

Caveats Resolved in Unified CM Release 6.1(3a)

SDI Trace Delete from User Interface May Cause High IO

Cisco Unified JTAPI

SFTP Server Products

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

Important Information About Delete Transaction 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

Deleting a Server and Adding a Deleted Server to a Cluster

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

CSCsq22385 Database Replication Setup Fails After You Add a New Subscriber to a Cluster

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

Out-of-Service Nodes and Cisco License Manager

Reset the Cluster After You Change the Security Password

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 Not Graceful

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

Configuring the Hostname/IP Address for the Cisco Unified Communications Manager Server

Serviceability Limitations When You Modify the IP Address

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

Online Help Was Not Updated for Cisco Unified Communications Manager, Release 6.1(3x)

CSCtj61834 MLPP Default Domain Name Displays MLPP ID Value

CSCtr84167 Block Offnet to Offnet Transfer

CSCtx86215 Database Replication

CSCuc10415 Tip for Adding a New Server

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

CSCtw44980 Missing Exceptions for Voice-Mail Pilot

CSCud34740 Application User AXL Password Must Not Contain Special Characters

CSCud70447 Missing Etoken Recovery Steps in Troubleshooting Guide

New and Changed Information in Cisco Unified Communications Manager 6.1(3x)

Installation, Upgrade, and Migration

Cisco Security Agent for Cisco Unified Communications Manager Log File

System History Log for Cisco Unified Communications Manager

Description

Data Migration Assistant (DMA) Enhancements

Command Line Interface

Spaces in File Names

Relative Paths

New Commands and Parameters

Cisco Unified Communications Manager Administration

New and Updated Enterprise and System Parameters

Menu Changes

Cisco Unified Communications Manager Features and Applications

Always Use Prime Line

Always Use Prime Line for Voice Message

Barge, cBarge, and Single Button Barge Support for PLAR

Cisco Unified Communications Manager Assistant

Cisco Web Dialer Configured in Application Server Window

Location-Based Call Admission Control Over Intercluster Trunk

Licensing Enhancements

Logging Missed Calls For Shared Lines

Multicast Music On Hold Over H.323/SIP Trunk

Party Entrance Tone

Table Out of Sync Detection

Transit Counter That is Implemented in Codeset5 for QSIG PRI Trunks

Unconfigured Device Registration Attempts Restricted

Viewing Held Calls on Shared Lines

Bulk Administration Tool

Support for Party Entrance Tone

Support for Log Missed Calls

Support for Always Use Prime Line

Support for VG202 and VG204 Gateways

Cisco Unified Serviceability

DBReplicationTableOutOfSync Alarm

Cisco UXL Web Service Added to Service Activation Window

Cisco Unified Real-Time Monitoring Tool

Quality Report Tool Reports

New Preconfigured Alert - DBReplicationTableOutOfSync

System History Log Displays in RTMT

Cisco Unified Communications Manager CDR Analysis and Reporting

Configuring Department Bills Reports

Reports That Are Unavailable to Administrator While CAR Database Gets Manually Purged or CDR Records Get Reloaded

SIP Call with URL as Extension Number Now Supported

CDR Search by User Extension Supports "+" and URLs for SIP Calls

Changes to Mail Server Configuration GUI

Change in Supported FTP/SFTP Versions for CAR Billing Servers

Effects on CAR Data When You Upgrade Cisco Unified Communications Manager by Using Data Migration Assistant

Ensure CAR Administrator Privileges Are Restored After Upgrade

Configuring CDR Error Reports

Event Log Report Status

New Error Message That Is Introduced If Data Present in Invalid or Remainder Partitions

Configuring Individual and Department Bills Reports

Cisco Unified Communications Manager Call Detail Records

Updated Information on Global Call ID CDR Field

CallingPartyNumber CDR Field Not Affected by Direct Calls

CMR Examples Provided

Video Conference Call CDR Example

Cisco Unified Reporting

Cisco and Third-Party APIs

Skinny Client Control Protocol (SCCP)

Administrative XML Interface

Cisco Web Dialer API

Cisco Unified IP Phones

Barge Tone Enhancements

Busy Lamp Field (BLF) Enhancements

Cisco Unified IP Phone Expansion Modules 7915 and 7916

Cisco Unified IP Phone Support HTTPS

Hold Status

Line Select

Missed Calls

Personal Directory and Fast Dial Service

Restrict Unconfigured Phone Registration

Web Dialer Enhancements

Cisco Unified CM User Options

Caveats

Resolved Caveats

Using Bug Toolkit

Open Caveats

Documentation Updates

Obtaining Documentation and Submitting a Service Request


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


Updated January 4, 2013


Caution Be aware that you can not upgrade directly from Unified CM 6.1(3x) to Unified CM 7.0

This document contains information pertinent to Cisco Unified Communications Manager Release 6.1(3x).

Before you install Cisco Unified Communications Manager, Cisco recommends that you review the "Upgrading to Cisco Unified Communications Manager 6.1(3x)" section for information about upgrading and the "Important Notes" 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.


Contents

These release notes discuss the following topics:

Introduction

System Requirements

Installation Notes

Upgrading to Cisco Unified Communications Manager 6.1(3x)

Related Documentation

Important Notes

Caveats Resolved in Unified CM Release 6.1(3a)

New and Changed Information in Cisco Unified Communications Manager 6.1(3x)

Caveats

Open Caveat as of February 12, 2009

Documentation Updates

Obtaining Documentation and Submitting a Service Request

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(3x) 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(3x), refer to the Supported Servers for Cisco Unified Communications Manager Releases: http://www.cisco.com/en/US/prod/collateral/voicesw/ps6790/ps5748/ps378/prod_brochure0900aecd8062a4f9.html.


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



Note Some servers that are listed in the Cisco Unified Communications Manager Software Compatibility Matrix may require additional hardware support for Cisco Unified Communications Manager Release 6.1(3a). Make sure that your server meets the minimum hardware requirements, as indicated in the footnotes of the Cisco Unified Communications Manager 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(3x).

Windows 2000 Users Must Download Windows Installer 3.0 Updates

Do Not Install 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 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(3x)

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

Before You Begin

Upgrade Paths To Cisco Unified Communications Manager 6.1(3x)

Upgrading to Unified CM 6.1(3x) From Unified CM 4.x and 5.x

Upgrading From an Engineering Special

Upgrading From Cisco Unified Communications Manager Release 6.1(1x) or higher to Release 6.1(3a) 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

Cisco Unified Communications Manager Administration version


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


Upgrade Paths To Cisco Unified Communications Manager 6.1(3x)

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 From Cisco Unified Communications Manager Release 6.1(1x) or higher to Release 6.1(3a) by Using the UCSInstall File" section for upgrades from 6.1(1x) and higher.

Upgrading to Unified CM 6.1(3x) 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.

Upgrading From an Engineering Special

if you want to upgrade to Cisco Unified CM 6.1(3a) 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 From Cisco Unified Communications Manager Release 6.1(1x) or higher to Release 6.1(3a) by Using the UCSInstall File

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

UCSInstall_UCOS_6.1.3.2000-1.sgn.iso_part1of2

UCSInstall_UCOS_6.1.3.2000-1.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.3.2000-1 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.3.2000-1.sgn.iso_part1of2 UCSInstall_UCOS_6.1.3.2000-1.sgn.iso_part2of2 UCSInstall_UCOS_6.1.3.2000-1.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.3.2000-1.sgn.iso_part1of2+UCSInstall_UCOS_6.1.3.2000-1.sgn.iso_part2of2 UCSInstall_UCOS_6.1.3.2000-1.sgn.iso


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

66fd64c2799d14db456cf589f1ed55be UCSInstall_UCOS_6.1.3.2000-1.sgn.iso

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

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 6.1(3x). 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.

Important Notes

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

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

Caveats Resolved in Unified CM Release 6.1(3a)

SDI Trace Delete from User Interface May Cause High IO

Cisco Unified JTAPI

SFTP Server Products

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

Important Information About Delete Transaction 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

Deleting a Server and Adding a Deleted Server to a Cluster

Viewing Privileges for Roles in Cisco Unified CM Administration

Basic Uninterruptible Power Supply (UPS) Integration

CSCsq22385 Database Replication Setup Fails After You Add a New Subscriber to a Cluster

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

Out-of-Service Nodes and Cisco License Manager

Reset the Cluster After You Change the Security Password

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 Not Graceful

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

Configuring the Hostname/IP Address for the Cisco Unified Communications Manager Server

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

Online Help Was Not Updated for Cisco Unified Communications Manager, Release 6.1(3x)

CSCtj61834 MLPP Default Domain Name Displays MLPP ID Value

CSCtr84167 Block Offnet to Offnet Transfer

CSCtx86215 Database Replication

CSCuc10415 Tip for Adding a New Server

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

CSCtw44980 Missing Exceptions for Voice-Mail Pilot

CSCud34740 Application User AXL Password Must Not Contain Special Characters

CSCud70447 Missing Etoken Recovery Steps in Troubleshooting Guide

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.

Caveats Resolved in Unified CM Release 6.1(3a)

The following information comprises unexpected behavior that is addressed by this Service Update of Cisco Unified Communications Manager.

------------------------------------------------------------------------------

Identifier: CSCsw93549

Component : phones

Headline : Error in IP phone rules file causes sidecar not to register to Unified CM.

------------------------------------------------------------------------------

Identifier: CSCsx35470

Component : call processing

Headline : SDL version change for Unified CM 613a.

------------------------------------------------------------------------------

Identifier: CSCsx16330

Component : cli

Headline : Nodatasync option on switchversion causes permanent data loss.

------------------------------------------------------------------------------

Identifier: CSCsw97038

Component : sip trunk

Headline : Unified CM sends incorrect codec in SDP of ACK for outgoing mobility call.

-----------------------------------------------------------------------------

Identifier: CSCsw76629

Component : mobility

Headline : Third-party SIP endpoint fails to register with digest authentication enabled.

-----------------------------------------------------------------------------

SDI Trace Delete from User Interface May Cause High IO

This caveat is resolved in Unified CM 6.1(2), but not in 6.1(3x).

In Unified CM 6.1(3x), when you change the number of SDI trace files, all existing trace files get deleted. If the number of trace files is extremely large, this can cause high IOWait problems and phones may unregister.

Workaround

Manually delete the excessive trace files during off hours.

Use the CLI to delete the files first and then use the Trace Configuration window to update the maximum number of files or the maximum file size settings.

Cisco recommends that you delete the files in batches of 500 files, or fewer, at a time.

Example

Since CLI support "wild card" characters, to delete trace files from ccm00000600.txt to ccm00000699.txt use following CLI:

file delete activelog cm/trace/ccm/sdi/ccm000006*.* noconfirm

The CLI command does not delete files that are currently open, so there will not be any interruption to the current ccm trace log.

Ensure that files that you intend to delete are of no value; otherwise, download them before deleting them.

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 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 Releases 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 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 htttp://developer.cisco.com/web/cdc/home. 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 (for Unix systems

Cygwin (refer to http://sshwindows.sourceforge.net/)

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


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

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.

Deleting a Server and Adding a Deleted Server to a Cluster

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


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


Before you delete a server, consider the following information:

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

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

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

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

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

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

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

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

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

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

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

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

Procedure


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

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


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

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

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


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

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


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 on each Cisco Unified Communications Manager in the cluster.

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 BAT, refer to the BAT documentation for Cisco Unified CM.

Basic Uninterruptible Power Supply (UPS) Integration

When Cisco Unified Communications Manager 6.0(1a) 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.

CSCsq22385 Database Replication Setup Fails After You Add a New Subscriber to a Cluster

Database replication failure alert displays after you add a new subscriber node to an existing cluster.
After the fresh install completes successfully, the following alert displays (date and time vary).

May 7 16:02:09 lg-pub-1 local7 2 : 116: May 07 20:02:09.491 UTC : 
%CCM_RTMT-RTMT-2-RTMT-ERROR-ALERT: RTMT Alert Name:DBReplicationFailure Detail: 
DBReplicationFailure occured. CallManager database replication errors, Reason code: 
Replication setup failed. The alert is generated on Wed May 07 16:02:09 EDT 2008 on node 
10.1.1.1. App ID:Cisco AMC Service Cluster ID: Node ID:xxx
 
   

The primary AMC server, which by default represents the publisher node, raises the DBReplicationFailure alert. You can observe this alert by using RTMT Alert Central or Summary view. You can also find the alerts in the EventViewer - Application Logs (CiscoSyslog) that you can access by using RTMT syslog viewer or platform CLI by using the file view activelog syslog/CiscoSyslog command.

Other Symptoms

The following list gives more symptoms of DBReplicationFailure that you may experience:

1. In the database replicator traces that are available on the publisher node. you may see the following error when you attempt to get the subscriber DB replication set up.

dbl_repl_cdr_define_lg_sub_8_ccm6_1_2_1000_13-2008_05_07_12_00_20.log
 
   
sucmd_err [su -c 'ulimit -c 0;cdr err --zap' - informix ]
Executing [su -c 'ulimit -c 0;cdr define server --connect=lg_sub_8_ccm6_1_2_1000_13 
--idle=0 --init --sync=g_lg_pub_1_ccm6_1_2_1000_13 g_lg_sub_8_ccm6_1_2_1000_13 
--ats=/var/log/active/cm/log/informix/ats --ris=/var/log/active/cm/log/informix/ris;' 
- informix]
We got exception in Cdr define
Exception from cdr define e.value[100] e.msg [Error executing [su -c 'ulimit -c 0;cdr 
define server --connect=lg_sub_8_ccm6_1_2_1000_13 --idle=0 --init 
--sync=g_lg_pub_1_ccm6_1_2_1000_13 g_lg_sub_8_ccm6_1_2_1000_13 
--ats=/var/log/active/cm/log/informix/ats --ris=/var/log/active/cm/log/informix/ris;' 
- informix] returned [25600]]
 
   

2. The subscriber node Cisco DB logs (ccm.log) may include the following error:

11:47:51 CDR GC: GC could not verify the local server identity in CDR catalog with 
that in sqlhost file during CDR recovery.
 
   

3. You cannot register any devices on the newly installed subscriber node because replication is not set up to the node.

By default, the publisher node DB replicator service continuously attempts to define the new server and generates a new log every 5 minutes.

Workaround for a Single Node

Use the following workaround for this caveat.


Caution Before you continue, identify the exact subscriber that is affected. To do that, look at the alert and confirm the node (IP) and the Node ID (hostname). In the preceding example alert, that information includes
node 10.1.1.1. App ID:Cisco AMC Service Cluster ID: Node ID:xxx


Step 1 Confirm that the reason for the DB replication failure is cdr define failure and then perform Step 2.

Step 2 From the platform CLI on the subscriber server, enter the following command:

utils dbreplication stop.


Caution This process can take 5 minutes or more to complete.

Wait for it to finish before you continue.

Step 3 From the platform CLI on the subscriber server, enter the following command:

utils dbreplication dropadmindb

Step 4 From the platform CLI on the publisher server, enter the following command.

utils dbreplication reset <subname> (<subname> equals the name of the subscriber server)


At the end of the command output, the following message displays:

admin:utils dbreplication reset nw104a-195
Repairing of replication is in progress.
Background repair of replication will continue after that for 30 minutes..
command failed -- Enterprise Replication not active  (62)
 
   

This output does not indicate a failure in the reset command. It serves as an informational message that got generated when you dropped the admindb on the subcriber server. The reset will complete successfully.

The reset command returns immediately, but the operation can take 30 minutes or more to finish.

Workaround for Multiple Nodes

The preceding instructions apply for single nodes, but multiple subscriber servers may experience this failure. If that occurs, for each subscriber node that is a fresh install and displays the DBReplicationFailure alert, repeat the preceding steps.

Verification

Be aware that replication is set correctly when the RTMT Replication counter "Replicate_State" equals 2 for both the publisher server and the subscriber server that you reset.

You can monitor the counter via the RTMT Database Summary window or via the platform CLI.

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


Out-of-Service Nodes and Cisco License Manager

Symptom

After an upgrade from Cisco Unified CallManager Release 5.1(x) to Cisco Unified Communications Manager 6.1(3x), apply the 6.x software license. Restart Unified CM services on all nodes. Cisco Unified Communications Manager and all services start, except Cisco License Manager. Attempts to manually restart Cisco License Manager do not succeed.

Workaround

If dummy nodes exist in the cluster, you should map the IP addresses of the dummy nodes to the hostnames in the DNS server. If you do not, Cisco Unified Communications Manager generates alarms to indicate that the License Manager service is down.

Reset the Cluster After You Change the Security Password

Servers in a cluster use the Security password to authenticate communication between servers.

To change the Security password, use the set password security CLI command or reset the password from the console.


Step 1 Change the security password on the publisher server (first node) and then reboot the server (node).

Step 2 Change the security password on all the subsequent servers/nodes to the password that was created in Step 1 and restart subsequent nodes, including application servers, to propagate the password change.



Note Cisco recommends that you restart each server after the password gets changed on that server.



Note Failure to reboot the servers (nodes) causes system service problems and problems with the Cisco Unified Communications Manager Administration windows on the subscriber servers.


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

Configuring the Hostname/IP Address for the Cisco Unified Communications Manager Server

Table 2 lists the locations where you can configure a host name for the Cisco Unified Communications Manager server, the allowed number of characters for the host name, and the recommended first and last characters for the host name. Be aware that, if you do not configure the host name correctly, some components in Cisco Unified Communications Manager, such as the operating system, database, installation, and so on, may not work as expected.


Caution Before you change the host name or IP address for any locations that are listed in Table 2, refer to Changing the IP Address and Host Name for Cisco Unified Communications Manager 5.x and 6.x Servers . Failing to update the host name or IP address correctly after it is configured may cause problems for Cisco Unified Communications Manager.

Table 2 Host Name Configuration in Cisco Unified Communications Manager

Host Name Location
Allowed Configuration
Allowed Number of Characters
Recommended First Character for Host Name
Recommended Last Character for Host Name

Host Name/ IP Address field

System > Server in Cisco Unified Communications Manager Administration

You can add or change the host name for any server in the cluster.

2-63

alphabetic

alphanumeric

Hostname field

Cisco Unified Communications Manager installation

You can add the host name for any server in the cluster.

1-63

alphabetic

alphanumeric

Hostname field

Settings > IP > Ethernet in Cisco Unified Communications Operating System

You can change, not add, the host name for any server in the cluster.

1-63

alphabetic

alphanumeric

set network hostname hostname

Command Line Interface

You can change, not add, the host name for any server in the cluster.

1-63

alphabetic

alphanumeric



Tip The host name must follow the rules for ARPANET host names. Between the first and last character of the host name, you can enter alphanumeric characters and hyphens.


Before you configure the host name in any of the locations in Table 2, review the following information:

The Host Name/IP Address field in the Server Configuration window, which supports device-to-server, application-to-server, and server-to-server communication, allows you to enter an IPv4 address in dotted decimal format or a host name.

After you install Cisco Unified Communications Manager on the publisher database server, the host name for the publisher automatically displays in this field. Before you install Cisco Unified Communications Manager on the subscriber server, enter either the IP address or the host name for the subscriber server in this field on the publisher database server.

In this field, only configure a host name if Cisco Unified Communications Manager can access the DNS server to resolve host names to IP addresses; make sure that you configure the Cisco Unified Communications Manager name and address information on the DNS server.


Tip In addition to configuring Cisco Unified Communications Manager information on the DNS server, you enter DNS information during the Cisco Unified Communications Manager installation.


During the Cisco Unified Communications Manager installation of the publisher database server, you enter the host name, which is mandatory, and IP address of the publisher server to configure network information; that is, if you want to use static networking.

During the Cisco Unified Communications Manager installation on the subscriber server, you enter the hostname and IP address of the publisher database server, so Cisco Unified Communications Manager can verify network connectivity and publisher-subscriber validation. Additionally, you must enter the host name and the IP address for the subscriber server. When the Cisco Unified Communications Manager installation prompts you for the host name of the subscriber server, enter the value that displays in the Server Configuration window in Cisco Unified Communications Manager Administration; that is, if you configured a host name for the subscriber server in the Host Name/IP Address field.

Related Topics

"Server Configuration" chapter, Cisco Unified Communications Manager Administration Guide

Installing Cisco Unified Communications Manager, Release 6.1(1)

Cisco Unified Communications Operating System Administration Guide

Command Line Interface Reference Guide for Cisco Unified Solutions

Changing the IP Address and Host Name for Cisco Unified Communications Manager 5.x and 6.x Servers

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

Online Help Was Not Updated for Cisco Unified Communications Manager, Release 6.1(3x)

When you view online help in Cisco Unified Communications Manager 6.1(3x), be aware that the online help did not get updated for 6.1(3x). 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)

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

CSCtj61834 MLPP Default Domain Name Displays MLPP ID Value

When you configure the MLPP Domain Name in Cisco Unified Communications Manager, the default name for MLPP Domain Name displays the MLPP ID value 000000 instead of Default as stated on the help page.

CSCtr84167 Block Offnet to Offnet Transfer

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

CSCtx86215 Database Replication

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

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

CSCuc10415 Tip for Adding a New Server

The following tip needs to be added to the "Server settings" topic in the Cisco Unified Communications Manager Administration Guide.

To avoid errors, Cisco recommends that you add a server to the system with a name that has less than 47 characters. Then, update the server name to the target length.

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

The following note is missing from the "Phone Settings" topic in the Cisco Unified Communications Manager Administration Guide:

When set to <none>, Unified CM uses the device mobility calling search space, which is configured on the device pool.

CSCtw44980 Missing Exceptions for Voice-Mail Pilot

The following information is missing for the Voice Mail Pilot Name field description in the "Voice-Mail Pilot Settings" topic in the Cisco Unified Communications Manager Administration Guide:

Allowed characters are numeric (0-9), plus (+), asterisk (*), and pound (#).

CSCud34740 Application User AXL Password Must Not Contain Special Characters

The following note is missing from the Application User Settings topic in the Cisco Unified Communications Manager Administration Online Help:


Note Do not use special characters when you create an AXL password for an application user.


CSCud70447 Missing Etoken Recovery Steps in Troubleshooting Guide

The Cisco Unified Communications Manager Troubleshooting Guide is missing the following procedure for troubleshooting if you lose all security tokens (etokens):

Perform the following procedure if you lose the security tokens and you need to update the CTL file.


Tip Perform the following procedure during a scheduled maintenance window, because you must reboot all servers in the cluster for the changes to take effect.



Step 1 On every Cisco Unified CallManager, Cisco TFTP, or alternate TFTP server, verify that CTLFile.tlv exists from the OS SSH command line.

file list tftp CTLFile.tlv

Step 2 Delete CTLFile.tlv.

file delete tftp CTLFile.tlv

Step 3 Repeat step 1 and step 2 for every Cisco Unified CallManager, Cisco TFTP, and alternate TFTP server.

Step 4 Obtain at least two new security tokens.

Step 5 By using the Cisco CTL client, create the CTL File, as described in "Installing the Cisco CTL Client" and "Configuring the Cisco CTL Client".


Tip If the clusterwide security mode is in mixed mode, the Cisco CTL client displays the message No CTL File exists on the server but the CallManager Cluster Security Mode is in Mixed Mode. For the system to function, you must create the CTL File and set CallManager Cluster to Mixed Mode. Click OK; then, choose Set CallManager Cluster to Mixed Mode and complete the CTL file configuration.


Step 6 Reboot all the servers in the cluster.

Step 7 After you create the CTL file on all the servers and reboot all servers in the cluster, delete the CTL file from the phone, as described in "Deleting the CTL File on the Cisco Unified IP Phone".

New and Changed Information in Cisco Unified Communications Manager 6.1(3x)

The following section describes new features and changes that are pertinent to Cisco Unified Communications Manager, Release 6.1(3x) or later. The sections may include configuration tips for the administrator, information about users, and information about where to find more information.

Installation, Upgrade, and Migration

Command Line Interface

Cisco Unified Communications Manager Administration

Bulk Administration Tool

Cisco Unified Serviceability

Cisco Unified Real-Time Monitoring Tool

Cisco Unified Communications Manager CDR Analysis and Reporting

Cisco Unified Communications Manager Call Detail Records

Cisco and Third-Party APIs

Cisco Unified IP Phones

Cisco Unified CM User Options

Installation, Upgrade, and Migration

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

Cisco Security Agent for Cisco Unified Communications Manager Log File

System History Log for Cisco Unified Communications Manager

Data Migration Assistant (DMA) Enhancements

Cisco Security Agent for Cisco Unified Communications Manager Log File

The CLI command that accesses the Cisco Security Agent file log changed to utils create report csa.

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.

Data Migration Assistant (DMA) Enhancements

Cisco Unified Communications Manager Release 6.1(3x) includes the following Data Migration Assistant (DMA) enhancements. For more details, refer to the documents Data Migration Assistant User Guide 6.1(3) and Upgrading to Cisco Unified Communications Manager Release 6.1(3) from Cisco Unified Communications Manager 4.x Releases:

The platformConfig.xml file that DMA generates supports upgrades for the first node (publisher database server) as well as for the subsequent nodes (subscribers). DMA provides a window where you can make detailed configuration specifications. Enter data at the DMA window Export > Answer File Generator.

DMA provides a window where users can customize the behavior of DMA by specifying which types of logs to include in the output file. Enter data at the DMA window Export > Custom Options

DMA explicitly lists the pre-DMA export tasks. DMA provides both information and the automation of pre-export tasks when possible to ensure that they know what tasks they need to complete before DMA is run. Enter data at the DMA window Export > Pre-Export Tasks.

DMA supports the generation of a license file upon successful DMA validation. The user can upload this license file to Cisco CCO to get the actual license file ready for use. Go to the DMA window Export > Storage Location and specify a local directory destination for the license file licupgrade.lic Specify the destination in the "Path Name" text box of the window's "Destination Option for License File" field.

For More Information

Effects on CAR Data When You Upgrade Cisco Unified Communications Manager by Using Data Migration Assistant

Ensure CAR Administrator Privileges Are Restored After Upgrade

Command Line Interface

This section contains information about the Command Line Interface (CLI).

Spaces in File Names

For Cisco Unified Communications Manager Release 6.1(3x), you can use CLI commands to directly work with file names that contain spaces. For example, you could use the file delete command to delete a log file with the name cisco test log in the Platform directory:

file delete activelog platform cisco test log

Relative Paths

When you download a file to your local computer with the file get command, the system prompts you to enter a download directory. For Cisco Unified Communications Manager Release 6.1(3x), you can specify a relative path for the download directory by using the ./ notation, as shown in the following example:

Download directory: ./RepStat

If you specify a download directory that does not exist on your local computer, the file get command creates it for you.

New Commands and Parameters

This section provides information about the following new CLI command for Cisco Unified Communications Manager Release 6.1(3x):

utils create report csa

This command collects all the files that are required for CSA diagnostics and assembles them into a single CSA diagnostics file. You can retrieve this file by using the file get command.

For more information about command syntax and parameters, see Appendix A of the Cisco Unified Communications Operating System Administration Guide and the Command Line Interface Reference Guide for Cisco Unified Solutions.

Cisco Unified Communications Manager Administration

This section contains information on the following topics:

Transit Counter That is Implemented in Codeset5 for QSIG PRI Trunks

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

No enterprise parameters updates occurred for Cisco Unified Communications Manager 6.1(3x).

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.

Party Entrance Tone—This parameter supports the Cisco CallManager service for the"Viewing Held Calls on Shared Lines" feature.

Always Use Prime Line—This parameter supports the Cisco CallManager service for the "Always Use Prime Line" feature.

Always Use Prime Line for Voice Message—This parameter supports the Cisco CallManager service for the "Always Use Prime Line for Voice Message" feature.

Table Out Of Sync—This parameter supports the Cisco CallManager service for the "Table Out of Sync Detection" feature.

Enable Transit Counter Processing on QSIG Trunks—This parameter supports the Cisco CallManager service for the "Transit Counter That is Implemented in Codeset5 for QSIG PRI Trunks" feature.

Send Multicast MOH in H.245 OLC Message—This parameter supports the Cisco CallManager service for the "Multicast Music On Hold Over H.323/SIP Trunk" feature.

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

After you log in to Cisco Unified Communications Manager Administration, messages may display that indicate the current state of licenses for Cisco Unified Communications Manager. For more information, see the "Licensing Enhancements" section.

System

The System menu contains the following changes:

System > Service Parameters —For information on new or updated service parameters, see the "New and Updated Enterprise and System Parameters" section.

System > Licensing > License File Upload—This window displays a message that uploading the license file removes the demo licenses for the feature. For more information, see the "Licensing Enhancements" section.

System > Licensing > License File Upload—This window displays the status of a license file. For example, the Status column for each license type may display Demo, Missing, or Uploaded. For more information, see the "Licensing Enhancements" section.

Call Routing

The Call Routing menu provides the following new and updated settings.

Call Routing > Directory Number—The Log Missed Calls check box displays, as described in the "Logging Missed Calls For Shared Lines" section.

Media Resources

No changes exist for the Media Resources menu.

Voice Mail

No changes exist for the Voice Mail menu.

Device

The Device menu displays the following new and updated settings.

Device > Phone—The Always Use Prime Line drop-down list box displays, as described in the "Always Use Prime Line" section. The Always Use Prime Line For Voice Mail drop-down list box displays, as described in the "Always Use Prime Line for Voice Message" section.

Device > Device Settings > Default Device Profile—The Always Use Prime Line drop-down list box displays, as described in the "Always Use Prime Line" section. The Always Use Prime Line For Voice Mail drop-down list box displays, as described in the "Always Use Prime Line for Voice Message" section.

Device > Device Settings > Device Profile—The Always Use Prime Line drop-down list box displays, as described in the "Always Use Prime Line" section. The Always Use Prime Line For Voice Mail drop-down list box displays, as described in the "Always Use Prime Line for Voice Message" section.

Device > Device Settings > Common Phone Profile—The Always Use Prime Line drop-down list box displays, as described in the "Always Use Prime Line" section. The Always Use Prime Line For Voice Mail drop-down list box displays, as described in the "Always Use Prime Line for Voice Message" section.

Application

No updates or new fields exist for this menu.

User Management

No changes exist for the User Management menu.

Bulk Administration

The Bulk Administration menu displays the following new and updated settings.

Bulk Administration > Phones > Phone Template—The Always Use Prime Line drop-down list box displays, as described in the "Always Use Prime Line" section. The Always Use Prime Line For Voice Mail drop-down list box displays, as described in the "Always Use Prime Line for Voice Message" section.

Bulk Administration > User Device Profile > UDP Template—The Always Use Prime Line drop-down list box displays, as described in the "Always Use Prime Line" section. The Always Use Prime Line For Voice Mail drop-down list box displays, as described in the "Always Use Prime Line for Voice Message" section.

Bulk Administration > Phones > Update Phones—The Always Use Prime Line drop-down list box displays, as described in the "Always Use Prime Line" section. The Always Use Prime Line For Voice Mail drop-down list box displays, as described in the "Always Use Prime Line for Voice Message" section.

Bulk Administration > Phones > Phone Template. Click Add New DN in the Associated Information Area—Log Missed Calls Check Box displays, as described in the "Logging Missed Calls For Shared Lines" section.

Bulk Administration > User Device Profile > UDP Template. Click Add New DN in the Associated Information Area—Log Missed Calls Check Box displays as described in the "Logging Missed Calls For Shared Lines" section.

Bulk Administration > Phones > Add/Update Lines > Update Lines—Log Missed Calls Check Box displays as described in the "Logging Missed Calls For Shared Lines" section.

Bulk Administration > User device Profiles > Add/Update Lines > Update Lines—Log Missed Calls Check Box displays as described in the "Logging Missed Calls For Shared Lines" section.

Bulk Administration > Phones > Phone Template Click Add New DN in the Associated Information Area—Party Entrance Tone drop-down list box displays, as described in the "Support for Party Entrance Tone" section.

Bulk Administration > User Device Profile > UDP Template Click Add New DN in the Associated Information Area—Party Entrance Tone drop-down list box displays, as described in the "Support for Party Entrance Tone" section.

Bulk Administration > Gateways > Gateway Template. Click Add New DN in the Associated Information Area—Party Entrance Tone drop-down list box displays, as described in the "Support for Party Entrance Tone" section.

Bulk Administration > Gateways > Gateway Template—VG202 and VG204 gateways now display in the Gateway Type drop-down list box, as described in the "Support for VG202 and VG204 Gateways" section.

Bulk Administration > Gateways > Insert Gateways—VG202 and VG204 gateways now display in the Gateway Type drop-down list box as described in the "Support for VG202 and VG204 Gateways" section.

Bulk Administration > Gateways > Insert Gateways. Select Gateway type and click next. The second Insert Gateways Configuration window displays—Sample insert gateways link now displays VG202 and VG204 sample files along with other BAT supported gateways, as described in the "Support for VG202 and VG204 Gateways" section.

Cisco Unified Communications Manager Features and Applications

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

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

Always Use Prime Line

Always Use Prime Line for Voice Message

Barge, cBarge, and Single Button Barge Support for PLAR

Cisco Unified Communications Manager Assistant

Cisco Web Dialer Configured in Application Server Window

Licensing Enhancements

Logging Missed Calls For Shared Lines

Multicast Music On Hold Over H.323/SIP Trunk

Party Entrance Tone

Table Out of Sync Detection

Transit Counter That is Implemented in Codeset5 for QSIG PRI Trunks

Unconfigured Device Registration Attempts Restricted

Viewing Held Calls on Shared Lines

Always Use Prime Line


Tip The information in this section does not exist in the online help for Cisco Unified Communications Manager Administration or in any other Cisco Unified Communications Manager 6.1(x) document besides the release notes.


Description

After you configure the Always Use Prime Line setting in Cisco Unified Communications Manager Administration, when the phone is idle (off hook) and receives a call on any line, the primary line gets chosen for the call.


Tip To configure the Always Use Prime Line feature in previous releases of Cisco Unified Communications Manager, you configured the Always Use Prime Line service parameter for the Cisco CallManager service, which applied to the entire cluster. In Cisco Unified Communications Manager 6.1(3x), you can configure the Always Use Prime Line setting for devices and device profiles.


Cisco Unified Communications Manager Administration Configuration Tips

When you configure this feature, going off hook makes only the first line active, even when a call rings on another line on the phone; that is, the call does not get answered on that line. In this case, the phone user must choose the other line to answer the call.

For more configuration considerations, see Table 3.

GUI Changes

The Always Use Prime Line for Voice Message setting displays in the following windows in Cisco Unified Communications Manager Administration.

System > Service Parameters (for Cisco CallManager service)

Device > Phone

Device > Common Phone Profile

Device > Device Settings > Default Device Profile

Device > Device Settings > Device Profile

For information on how the Always Use Prime Line setting works when a phone idle or busy, see Table 3.


Tip If you configure the Always Use Prime Line setting in the Service Parameter, Common Phone Profile, and in the Phone Configuration window, Cisco Unified Communications Manager uses the configuration from the Phone Configuration window.


Table 3 Always Use Prime Line for Voice Message Configuration

State of Phone
Configuration for Always Use Prime Line
How Feature Works

Idle

On

When the phone is idle (off hook) and receives a call on any line, the primary line gets chosen for the call. Calls on other lines continue to ring, and the phone user must select those other lines to answer these calls.

If you choose On for the Always Use Prime Line for Voice Message setting in the Device Profile or Default Device Profile Configuration window, a Cisco Extension Mobility user can use this feature after logging in to the device that supports Cisco Extension Mobility; that is, if you configure Cisco Extension Mobility correctly.

Idle

Off

When the phone is idle and receives a call on any line, the phone user answers the call from the line on which the call is received; that is, when the phone is off hook.

Idle

Default

If you choose Default for the Always Use Prime Line setting in the Common Phone Profile, the Device Profile, or the Default Device Profile Configuration windows, Cisco Unified Communications Manager uses the configuration from the Always Use Prime Line service parameter when determining whether a user, including a Cisco Extension Mobility user, can use this feature.

If you choose Default for the Always Use Prime Line setting in the Phone Configuration window, Cisco Unified Communications Manager uses the configuration from the common phone profile.

Busy

On

When the phone already has a call on a line, Cisco Unified Communications Manager uses the configuration for the Maximum Number of Calls and Busy Trigger settings to determine how to route the call.

Idle

On, but you also configured Auto Answer With Headset or Auto Answer with Speakerphone

If you choose the Auto Answer with Headset option or Auto Answer with Speakerphone option from the Auto Answer drop-down list box in Cisco Unified Communications Manager Administration, the Auto Answer configuration overrides the configuration for the Always Use Prime Line setting.


Service Parameter and Enterprise Parameter Changes

If you want to configure this feature via the clusterwide service parameter, Always Use Prime Line, which supports the Cisco CallManager service, choose System > Service Parameters in Cisco Unified Communications Manager Administration. Then, choose the server and the Cisco CallManager service. From the Always Use Prime Line drop-down list box, choose True.

Installation/Upgrade (Migration) Considerations

No special installation or upgrade considerations exist for this feature. After you install or upgrade to Cisco Unified Communications Manager 6.1(3x), you can configure this feature per device or per device profile.

Serviceability Considerations

This feature relies on the Cisco CallManager service, so activate the service by choosing Tools > Service Activation in Cisco Unified Serviceability. In addition, you can run SDI trace for the Cisco CallManager service. When you view the log in RTMT, you can see the configured value that is used by the device; for example, alwaysPrimeLine=1, which indicates that the device uses On for the configuration.

BAT Considerations

The Bulk Administration GUI has the following updates to support the Always Use Prime Line feature:

Always Use Prime Line drop-down list box—choose one of the following options:

Off

On

Default


Note For details of configuration options for the Always Use Prime Line feature, refer to Table 3.



Note The Always Use Prime Line drop-down list boxes displays on the Phone Template, UDP Template, and Update Phone windows.


Insert, Export, and Validate Details support for always use prime line—the following insert, export, and validate details features have support for the always use prime line feature:

Insert Phones Specific Details

Insert Phones All Details

Export Phones Specific Details

Export Phones All Details

Validate Phones All Details

Validate Phones Specific Details

Insert UDP All Details

Insert UDP Specific Details

Export UDP All Details

Export UDP Specific Details

Validate UDP All Details

Validate UDP Specific Details

Insert Phones/Users

Validate Phones/Users

UDP File Format—UDP File Format Configuration window lists the Always Use Prime Line and Always Use Prime Line for Voice Message drop-down list boxes in the device fields section.

Generate User Device Profile Report—The Generate User Device Profile Report Configuration window lists the Always Use Prime Line and Always Use Prime Line for Voice Message fields in the Device Fields section.

CAR/CDR Considerations

No CAR or CDR considerations exist for this feature.

Security Considerations

No security considerations exist for this feature.

AXL and CTI Considerations

No AXL or CTI considerations exist for this feature.

User Tips

For a list of phones that support this feature, see the "Line Select" section.

For More Information

Always Use Prime Line for Voice Message

Line Select

Always Use Prime Line for Voice Message


Tip The information in this section does not exist in the online help for Cisco Unified Communications Manager Administration or in any other Cisco Unified Communications Manager 6.1(x) document besides the release notes.


Description

After you configure the Always Use Prime Line for Voice Message setting in Cisco Unified Communications Manager Administration, the primary line on the phone becomes the active line for retrieving voice messages when the phone user presses the Messages button on the phone.


Tip To configure the Always Use Prime Line for Voice Message feature in previous releases of Cisco Unified Communications Manager, you configured the Always Use Prime Line service parameter for the Cisco CallManager service, which applied to the entire cluster. In Cisco Unified Communications Manager 6.1(3x), you can configure the Always Use Prime Line setting for devices and device profiles.


Cisco Unified Communications Manager Administration Configuration Tips

For configuration considerations, see Table 4.

GUI Changes

The Always Use Prime Line for Voice Message setting displays in the following windows in Cisco Unified Communications Manager Administration.

System > Service Parameters (for Cisco CallManager service)

Device > Phone

Device > Common Phone Profile

Device > Device Settings > Default Device Profile

Device > Device Settings > Device Profile

For information on how the Always Use Prime Line for Voice Message setting works when a phone is idle or busy, see Table 4.


Tip If you configure the Always Use Prime Line for Voice Message setting in the Service Parameter, Common Phone Profile, and in the Phone Configuration window, Cisco Unified Communications Manager uses the configuration from the Phone Configuration window.


Table 4 Always Use Prime Line for Voice Message Configuration

State of Phone
Configuration for Always Use Prime Line for Voice Message
How Feature Works

Idle

On

If the phone is idle, the primary line on the phone becomes the active line for retrieving voice messages when the phone user presses the Messages button on the phone.

If you choose On for the Always Use Prime Line for Voice Message setting in the Device Profile or Default Device Profile Configuration window, a Cisco Extension Mobility user can use this feature after logging in to the device that supports Cisco Extension Mobility; that is, if you configure Cisco Extension Mobility correctly.

Idle

Off

If the phone is idle, pressing the Messages button on the phone automatically dials the voice-messaging system from the line that has a voice message.Cisco Unified Communications Manager always selects the first line that has a voice message. If no line has a voice message, the primary line gets used when the phone user presses the Messages button.

Idle

Default

If you choose Default for the Always Use Prime Line for Voice Message setting in the Phone Configuration, the Common Phone Profile, the Device Profile, or the Default Device Profile Configuration windows, Cisco Unified Communications Manager uses the configuration from the Always Use Prime Line for Voice Message service parameter when it determines whether a user, including a Cisco Extension Mobility user, can use this feature.

If you choose Default for the Always Use Prime Line for Voice Message setting in the Phone Configuration window, Cisco Unified Communications Manager uses the configuration from the common phone profile.

Busy

On

If the device is busy, this feature does not work.


Service Parameter and Enterprise Parameter Changes

If you want to configure this feature via the clusterwide service parameter, Always Use Prime Line for Voice Message, which supports the Cisco CallManager service, choose System > Service Parameters in Cisco Unified Communications Manager Administration. Then, choose the server and the Cisco CallManager service. From the Always Use Prime Line for Voice Message drop-down list box, choose True.

Installation/Upgrade (Migration) Considerations

No special installation or upgrade considerations exist for this feature. After you install or upgrade to Cisco Unified Communications Manager 6.1(3x), you can configure this feature per device.

Serviceability Considerations

This feature relies on the Cisco CallManager service, so activate the service by choosing Tools > Service Activation in Cisco Unified Serviceability. In addition, you can run SDI trace for the Cisco CallManager service. When you view the log in RTMT, you can see the configured value that is used by the device; for example, alwaysUsePrimeLineForVM=2, which indicates that the device uses the default.

BAT Considerations

The Bulk Administration GUI has the following updates to support the Always Use Prime Line for Voice Mail feature:

Always Use Prime Line for Voice Message drop-down list box—choose one of the following options:

Off

On

Default


Note For details of configuration options for the Always Use Prime Line for Voice Mail feature, refer to Table 4.



Note The Always Use Prime Line for Voice Message drop-down list boxes display in the Phone Template, UDP Template, and Update Phone windows.


CAR/CDR Considerations

No CAR or CDR considerations exist for this feature.

Security Considerations

No security considerations exist for this feature.

AXL and CTI Considerations

No AXL or CTI considerations exist for this feature.

User Tips

For a list of phones that support this feature, see the "Line Select" section.

For More Information

Always Use Prime Line

Line Select

Barge, cBarge, and Single Button Barge Support for PLAR


Tip The information in this section does not exist in the online help for Cisco Unified Communications Manager Administration or in any other Cisco Unified Communications Manager 6.1(x) document besides the release notes.


Description

Barge, cBarge, or single-button barge allow a phone user to get added to a remotely active call that is on a shared line. Private Line Automatic Ringdown (PLAR) allows the phone user to dial a preconfigured number, and only this number, from the PLAR line. In Cisco Unified Communications Manager 6.1(3x), a barge, cBarge, or single-button barge initiator can barge into a call via a shared line that is configured for PLAR; that is, the initiator can barge into the call if the barge target uses the preconfigured number that is associated with the PLAR line while on the call.

In previous releases of Cisco Unified Communications Manager, Cisco Unified Communications Manager sent the cBarge invocation to the PLAR line before connecting the barge call. If the PLAR line was busy in previous releases, the initiator received a busy reorder tone. In Cisco Unified Communications Manager 6.1(3x), Cisco Unified Communications Manager does not send the barge invocation to the PLAR line before it connects the barge call, so the barge occurs no matter what the state of the PLAR destination.

Cisco Unified Communications Manager Administration Configuration Tips

To make barge, cBarge, or single-button barge work with PLAR, you must configure barge, cBarge, or single-button barge, as described in the "Barge and Privacy" chapter in the Cisco Unified Communications Manager Features and Services Guide. In addition, you must configure the PLAR destination, a directory number that is used specifically for PLAR. The following examples describe how to enable PLAR functionality for phones that are running SCCP and for phones that are running SIP.

A and A' represent shared-line devices that you configured for barge, cBarge, or single-button barge, and B1 represents the directory number for the PLAR destination. To enable PLAR functionality from A/A', which are running SIP, see the following example:


Tip Step 1 through Step 4 apply if you want to configure PLAR for phones that are running SCCP. For phones that are running SIP, you must perform Step 1 through Step 6.


Example for How to Configure PLAR


Step 1 Create a partition, for example, P1, and a calling search space, for example, CSS1, so CSS1 contains P1. (In Cisco Unified Communications Manager Administration, choose Call Routing > Class of Control > Partition or Calling Search Space.)

Step 2 Create a translation pattern, for example, TP1, which contains calling search space CSS1 and partition P1. Create a null pattern (blank pattern), but make sure that you enter the directory number for the B1 PLAR destination in the Called Party Transformation Mask field. (In Cisco Unified Communications Manager Administration, choose Call Routing > Translation Pattern.)

Step 3 Assign the calling search space, CS1, to either A or A'. (In Cisco Unified Communications Manager Administration, choose Device > Phone.)

Step 4 Assign the P1 partition to the directory number for B1, which is the PLAR destination. (In Cisco Unified Communications Manager Administration, choose Call Routing > Directory Number.)

Step 5 For phones that are running SIP, create a SIP dial rule. (In Cisco Unified Communications Manager Administration, choose Call Routing > Dial Rules > SIP Dial Rules. Choose 7940_7960_OTHER. Enter a name for the pattern; for example, PLAR1. Click Save; then, click Add Plar. Click Save.)

Step 6 For phones that are running SIP, assign the SIP dial rule configuration that you created for PLAR to the phones, which, in this example, are A and A'. ((In Cisco Unified Communications Manager Administration, choose Device > Phone. Choose the SIP dial rule configuration from the SIP Dial Rules drop-down list box.)


GUI Changes

No new configuration settings display in Cisco Unified Communications Manager Administration for this feature.

Service Parameter and Enterprise Parameter Changes

For parameters that you configure for barge, refer to the "Barge and Privacy" chapter in the Cisco Unified Communications Manager Features and Services Guide and the "Party Entrance Tone" section.

Installation/Upgrade (Migration) Considerations

You can use this feature after you install or upgrade to Cisco Unified Communications Manager 6.1(3x).

Serviceability Considerations

No special serviceability considerations exist for this feature.

BAT Considerations

No BAT considerations exist for this feature.

CAR/CDR Considerations

No CAR or CDR considerations exist for this feature.

Security Considerations

No security considerations exist for this feature.

AXL and CTI Considerations

No AXL or CTI considerations exist for this feature.

User Tips

By pressing the Barge, cBarge, or Single Button Barge softkey in the remote in use call state, the initiator gets added to the call with all parties, and all parties receive a barge beep tone (if configured).

For a list of phones that support this feature, see the "Barge Tone Enhancements" section.

For More Information

"Barge and Privacy," Cisco Unified Communications Manager Administration Guide, Release 6.1(1)

Party Entrance Tone

Barge Tone Enhancements

Cisco Unified Communications Manager Assistant


Tip The information in this section does not exist in the online help for Cisco Unified Communications Manager Administration or in any other Cisco Unified Communications Manager 6.1(x) document besides the release notes.


Cisco Unified Communications Manager Release 6.1(3x) supports numeric user ID login for Cisco Unified Communications Manager Assistants from their Cisco Unified IP Phones.

To configure numeric user ID login, perform the following steps:

Procedure


Step 1 When you add a Cisco Unified Communications Manager Assistant user (in Cisco Unified Communications Manager Administration, go to User Management -> End User), assign a User ID that is numeric only.

Step 2 In Cisco Unified Communications Manager Administration, go to the Service Parameters window (System> Service Parameters) then, select your server and select the Cisco IP Manager Assistant service.

In the section "Clusterwide Parameters (Parameters that apply to all servers)" set Alpha Numeric UserID to False.

Step 3 Restart the Cisco IP Manager Assistant service for this configuration change to take effect.


Cisco Web Dialer Configured in Application Server Window


Tip The information in this section does not exist in the online help for Cisco Unified Communications Manager Administration or in any other Cisco Unified Communications Manager 6.1(x) document besides the release notes.


Description

In previous releases of Cisco Unified Communications Manager, the List of WebDialers field in the Service Parameter window supported a maximum of 255 characters, which limited the scalability of the Redirector. In Cisco Unified Communications Manager 6.1(3x), you configure the Web Dialer servers in the Application Server Configuration window instead of the Service Parameters Configuration window.

Cisco Unified Communications Manager Administration Configuration Tips and GUI Changes

It is now possible for you to add a Cisco Web Dialer application server through the Application Server Configuration window. You access the Application Server Configuration window by choosing System > Application Server in Cisco Unified Communications Manager Administration. Cisco Web Dialer appears as one of the options in the Application Server Type drop-down list box.

If you add a Cisco Web Dialer application server in the Application Server Configuration window, the server displays in the List of WebDialers field in the Service Parameter Configuration window for the Cisco WebDialer Web Service.

Service Parameter and Enterprise Parameter Changes

In Cisco Unified Communications Manager 6.1(3x), you can configure either the List of WebDialers service parameter or the Cisco Web Dialer application server through the Application Server Configuration window. If you add a Cisco Web Dialer application server in the Application Server Configuration window, the server displays in the List of WebDialers field in the Service Parameter Configuration window for the Cisco WebDialer Web Service. You can access the Service Parameter Configuration window by choosing System > Service Parameters in Cisco Unified Communications Manager Administration.

Installation/Upgrade (Migration) Considerations

If you configured the List of WebDialers field in the Service Parameter Configuration window for the Cisco WebDialer Web Service before the upgrade to Cisco Unified Communications Manager 6.1(3x).

If you install Cisco Unified Communications Manager 6.1(3x) and plan to use Cisco Web Dialer, configure the Cisco Web Dialer application server in the Application Server Configuration window. You do not need to configure the List of WebDialers field in the Service Parameter Configuration window if you configure the application server in the Application Server Configuration window.

Serviceability Considerations

Cisco Web Dialer relies on the Cisco WebDialer Web Service. If you have not already done so, activate this service in the Service Activation window in Cisco Unified Serviceability.

BAT Considerations

No BAT considerations exist for this feature.

CAR/CDR Considerations

No CAR or CDR considerations exist for this feature.

Security Considerations

No security considerations exist for this feature.

AXL and CTI Considerations

See the "Cisco Web Dialer API" section.

User Tips

For user enhancements for Cisco Web Dialer, see the "Web Dialer Enhancements" section.

For More Information

"Cisco Web Dialer" chapter, Cisco Unified Communications Manager Features and Services Guide, Release 6.1(1)

Web Dialer Enhancements

Location-Based Call Admission Control Over Intercluster Trunk

Description

When a call is made across cluster through an intercluster trunk (ICT) and gets hairpinned back to the same location or site of the same cluster, although the media is exchanged between two endpoints in the same site or location, the current design of Cisco Unified Communications Manager location call admission control (CAC) deducts location bandwidth twice, once for the outbound call and again for the inbound call. The result does not correctly reflect the bandwidth consumption, which eventually causes denial of a new call to or from the site or location.

To resolve the bandwidth calculation problem, this feature enables Cisco Unified Communications Manager to pass location information, the primary key ID (PKID) of location record and location name, as a proprietary information element (IE) between the calling and called parties through an ICT, either in the H.323 protocol or SIP. Thus, either endpoint knows the true location information of the party/endpoint, not the location information of the ICT.

Currently, Cisco Unified Communications Manager has Hub_None as the default location that has unlimited bandwidth, plus any user-created location to which the user can assign a device and for which the user can configure bandwidth.

A new type of Cisco Unified Communications Manager location gets created specifically for the ICT for this application type. This new type of location, designated as the Phantom location, also has unlimited bandwidth. The locations server does not deduct bandwidth for a device that is assigned to the Phantom location. A device, such as the ICT, that is assigned to the Phantom location can use its own location or the true location of the connected device. Likewise, the outbound ICT can use its own location or the callee location, and the inbound ICT can use its own location or the caller location to deduct or adjust the bandwidth.

When the media connects, Cisco Unified Communications Manager adjusts the allocated location bandwidth according to the negotiated media codec. Cisco Unified Communications Manager can correctly readjust the location bandwidth based on received callee location information for the outbound call. This enhancement helps the outbound call, which has reserved bandwidth during call setup time, to adjust the bandwidth back to 0 if the call is hairpinned back to the same site or location.

Some supplementary services, such as transfer, can also hairpin the call back to the same site or location after the initial call setup process. Consider passing the location information of the final destination through the Notify signals (H.323) and re-INVITE signals (SIP) back to the calling cluster, so bandwidth can be adjusted to the right value as also required.

Because location record PKID is uniquely defined within the Cisco Unified Communications Manager enterprise environment, Cisco Unified Communications Manager uses location record PKID to identify whether the call over ICT has been looped back to the same cluster for the location-based CAC purpose. If other applications, like Cisco Voice Proxy (CVP), that do not have access to the Cisco Unified Communications Manager database for location record PKID information and also because PKID is a string of characters and digits, applications may need to rely on the location name information being passed around for the purpose of CAC. The same location name may exist for different locations with different location PKIDs in two different Cisco Unified Communications Manager clusters, which may cause confusion to the applications.

Cisco Unified Communications Manager Administration Configuration Tips

The Location Configuration window specifies the Phantom location as a location, besides the Hub_None location, that can get selected. Administrators cannot delete the Phantom location.

Administrators can create a new default location for the new Phantom location, similar to the Hub_None location. The Phantom location has unlimited audio and video bandwidth value, and the administrator cannot modify the audio and video bandwidth values. The user can assign a location-pair RSVP policy between this new location and other existing locations.


Caution If the ICT or H323 gateway is placed in a user defined location other than the Phantom location, this feature will not work. Also, if the ICT is connected to third-party system that does not recognize and pass the Cisco specific Location information in the SIP or H323 signals, this feature will not work

GUI Changes

This feature does not entail any new menu options or new fields in Cisco Unified Communications Manager Administration. The Phantom value is added for all entities that specify a location in the Location drop-down list box. Find the Location field on the Device Pool Configuration, Annunciator Configuration, Music On Hold (MOH) Server Configuration, Conference Bridge Configuration, Voice Mail Port Configuration, Voice Mail Port Wizard Configuration, CTI Route Point Configuration, Gateway Configuration, Phone Configuration, Trunk Configuration, and Pilot Point Configuration windows.

Service Parameter and Enterprise Parameter Changes

No service parameter nor enterprise parameter changes apply to this feature.

Installation/Upgrade (Migration) Considerations

Cisco Unified Communications Manager maintains the RSVP policy for the Phantom location during migration.

Serviceability Considerations

No serviceability considerations exist for this feature.

BAT Considerations

No BAT considerations exist for this feature.

CAR/CDR Considerations

No CAR nor CDR considerations exist for this feature.

Security Considerations

No security considerations exist for this feature.

AXL and CTI Considerations

No AXL nor CTI considerations exist for this feature.

User Tips

This feature does not entail user interaction.

For More Information

Call Admission Control, Cisco Unified Communications Manager System Guide, Release 6.1(1)

Resource Reservation Protocol, Cisco Unified Communications Manager System Guide, Release 6.1(1)

Understanding Cisco Unified Communications Manager Trunk Types, Cisco Unified Communications Manager System Guide, Release 6.1(1)

Location Configuration, Cisco Unified Communications Manager Administration Guide, Release 6.1(1)

Licensing Enhancements

Description

Cisco Unified Communications Manager 6.1(3x) identifies the state of a license; that is, if it is missing, if it represents a demo license, or if it represents an uploaded license. In addition, Cisco Unified Communications Manager Administration warns you whether Cisco Unified Communications Manager currently operates with demo licenses, with an insufficient number of licenses, or with an incorrect software feature license.

Cisco Unified Communications Manager Administration Configuration Tips

For information on how to configure licensing, refer to the licensing chapters in the Cisco Unified Communications Manager Administration Guide.

GUI Changes

The following windows display the state of licenses in Cisco Unified Communications Manager Administration:

Main Window—After you log in to Cisco Unified Communications Manager Administration, messages may display that indicate the current state of licenses for Cisco Unified Communications Manager. For example, Cisco Unified Communications Manager may identify the following situations:

Cisco Unified Communications Manager currently operates with demo licenses, so upload the appropriate license files.

Cisco Unified Communications Manager currently operates with an insufficient number of licenses, so upload additional license files.

Cisco Unified Communications Manager does not currently use the correct software feature license. In this case, the Cisco CallManager service stops and does not start until you upload the appropriate software version license and restart the Cisco CallManager service.

License File Upload (System > Licensing > License File Upload)—This window displays a message that uploading the license file removes the demo licenses for the feature.

License Unit Report (System > Licensing > License Unit Report)—This window displays the status of a license file. For example, the Status column for each license type may display Demo, Missing, or Uploaded.

Service Parameter and Enterprise Parameter Changes

No service parameters or enterprise parameters considerations exist for these licensing enhancements.

Installation/Upgrade (Migration) Considerations

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

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.

Immediately after you complete the upgrade to Cisco Unified Communications Manager 6.1(3x), upload the software feature license that is required for Cisco Unified Communications Manager 6.1(3x) 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 6.1(3x).

For more information, see Data Migration Assistant (DMA) Enhancements.

Serviceability Considerations

After you upload a license file, you must restart the Cisco CallManager service for the changes to take effect.

BAT Considerations

No BAT considerations exist for these licensing enhancements.

CAR/CDR Considerations

No CAR or CDR considerations exist for these licensing enhancements.

Security Considerations

No security considerations exist for these licensing enhancements.

AXL and CTI Considerations

No AXL or CTI considerations exist for these licensing enhancements.

User Tips

This feature does not impact the end user.

For More Information

"Licensing" chapter, Cisco Unified Communications Manager System Guide, Release 6.1(1)

Logging Missed Calls For Shared Lines


Tip The information in this section does not exist in the online help for Cisco Unified Communications Manager Administration or in any other Cisco Unified Communications Manager 6.1(x) document besides the release notes.


Description

With the missed call logging for shared lines feature, the administrator can configure Cisco Unified Communications Manager Administration, or the phone user can configure Cisco Unified CM User Options, so Cisco Unified Communications Manager logs missed calls in the call history to a specified shared line appearance on a phone.


Tip If configured correctly, this feature works if a phone user logs in to a phone via Cisco Extension Mobility.


The examples in Table 5, which use the following phones, describe how the missed call logging feature works for shared lines:

Phone A, which has directory number 1000 that is configured for the first line and directory number 2000 for the second line, which is shared with phone B.

Phone B, which has directory number 2000 that is configured as the first line, which is shared with phone A, and directory number 3000 that is configured as the second line.

Phone C, which places the calls.

Table 5 Example of How Logging Works for Missed Calls With Shared Lines 

Phone A
Phone B

Phone C calls directory number (DN) 1000.

Logged Missed Calls check box gets checked for DN 1000.

Missed calls get logged to DN 1000.

If the Logged Missed Calls check box is not checked, missed calls do not get logged to DN 1000.

Not applicable

Phone C calls directory number (DN) 2000.

Logged Missed Calls check box gets checked for DN 2000.

Missed calls get logged to DN 2000.

If the Logged Missed Calls check box is not checked, missed calls do not get logged to DN 2000.

Phone C calls DN 2000, which is a shared line appearance.

Logging displays for the shared line appearance on Phone B because the Logged Missed Calls check box is checked for DN 2000.


Cisco Unified Communications Manager Administration Configuration Tips

If this feature is not configured, the call history on the phone does not display missed calls for the specified line appearance.

GUI Changes

The Directory Number Configuration window in Cisco Unified Communications Manager Administration displays the Logged Missed Calls check box, which turns on or off this feature. If the check box displays as checked (turned on), which is the default for this setting, Cisco Unified Communications Manager logs missed calls in the call history for that shared line appearance on the phone. To access the check box, choose Call Routing > Directory Number. In the Directory Number Configuration window, highlight the associated device in the Associated Devices pane; then, click the Edit Line Appearance button.

In the Line Settings Configuration window in the Cisco Unified CM User Options, the phone user can check and uncheck the Log Missed Calls check box.

Service Parameter and Enterprise Parameter Changes

No new or updated parameters exist for this feature.

Installation/Upgrade (Migration) Considerations

Cisco Unified Communications Manager 6.1(3x) introduces this feature.

Serviceability Considerations

No serviceability considerations exist for this feature.

BAT Considerations

The Bulk Administration GUI has the following updates to support the Log Missed Calls feature:

Log Missed Calls Check Box— This check box allows you to turn this feature on or off. If the check box displays as checked (turned on), which is the default for this setting, Cisco Unified Communications Manager logs missed calls in the call history for that shared line appearance on the phone.


Note The Log Missed Calls Check Box exists on the Phone Line Template, UDP Line Template, Phone Update Line, and UDP Update Line windows.


Insert, Export, and Validate Details support for the log missed calls feature—the following insert, export, and validate details features have support for the log missed calls feature:

Insert Phones Specific Details

Insert Phones All Details

Export Phones Specific Details

Export Phones All Details

Validate Phones All Details

Validate Phones Specific Details

Insert UDP All Details

Insert UDP Specific Details

Export UDP All Details

Export UDP Specific Details

Validate UDP All Details

Validate UDP Specific Details

Insert Phones/Users

Validate Phones/Users

File Formats—the following file formats support the Log Missed Calls feature:

Phone File Format—Log Missed Calls field represents a part of the Line Fields section.

UDP File Format—Log Missed Calls field represents a part of the Line Fields section.

Generate User Device Profile Report—The Generate User Device Profile Report Configuration window lists the Log Missed Calls field in the Line Fields section.

CAR/CDR Considerations

No CAR or CDR considerations exist for this feature.

Security Considerations

No security considerations exist for this feature.

AXL and CTI Considerations

No AXL or CTI considerations exist for this feature.

User Tips


Tip If configured correctly, this feature works when a Cisco Extension Mobility user logs in to a phone via Cisco Extension Mobility.


For a list of phone models that support this feature, see the "Missed Calls" section.

For More Information

Missed Calls

Multicast Music On Hold Over H.323/SIP Trunk

Description

The Multicast Music on Hold (MOH) over H.323/SIP Trunk feature allows multicast MOH to work over H.323 and Session Initiation Protocol (SIP) intercluster trunks (ICTs). Prior to the implementation of this feature, multicast MOH used bandwidth for each unicast MOH over the same ICT, which wasted bandwidth.

Prior to the implementation of this feature, the H.323 Open Logical Channel (OLC) ACK message carried the IP address and port for multicast MOH. With the implementation of this feature, the H.323 OLC message now carries the IP address and port for multicast MOH, and Cisco Unified Communications Manager adds the mechanism to handle the information in the H.323 OLC message.

The new service parameter, Send Multicast MOH in H.245 OLC Message, controls the new feature. Both Cisco Unified Communications Manager nodes that are involved in the call must support single-transmitter multicast for the setting of this parameter to have any effect. This service parameter affects only the side of the party that places the call on hold and does not affect how the far end carries the multicast transport address. Even if this parameter is turned off, multicast MOH applies for the held-party side of the call as long as the held party has the capability to support single-transmitter multicast.

When a call connects over an intercluster trunk and one of the parties presses the Hold key, MOH will stream over the intercluster trunk. If multicast MOH is turned on and the holding party and trunk are configured to use the multicast MOH server, MOH streams with multicast. Only one multicast MOH stream streams over the trunk no matter how many calls get put on hold on this trunk.

Cisco Unified Communications Manager Administration Configuration Tips

Calls that connect over Cisco Unified Communications Manager intercluster trunks use this feature for multicast MOH. This feature does not work if any middle box between Cisco Unified Communications Managers does not pass the new fields in Terminal Capability Set (TCS) and OLC message.

No additional configuration exists for this new feature in addition to the normal configuration for setting up multicast MOH. This new feature only applies between Cisco Unified Communications Managers that support single-transmitter multicast.

You can turn this feature off by changing the default True value of the new Send Multicast MOH in H.245 OLC Message service parameter to False. You may need to do so if an interoperability issue arises.

GUI Changes

This feature does not entail any GUI changes to Cisco Unified Communications Manager Administration.

Service Parameter and Enterprise Parameter Changes

If you want to configure this feature via the clusterwide service parameter, Send Multicast MOH in H.245 OLC Message, which supports the Cisco CallManager service, choose System > Service Parameters in Cisco Unified Communications Manager Administration. Then, choose the server and the Cisco CallManager service. From the Send Multicast OH in H.245 OLC Message drop-down list box, choose True.

The new feature remains active by default. To turn off the feature, set the value of the Send Multicast MOH in H.245 OLC Message service parameter to False. Do so to resolve interoperability issues that the feature may cause.

The new service parameter governs the multicast MOH behavior on H.323 trunks and devices. The new service parameter does not control multicast MOH over SIP trunks, because multicast MOH over SIP trunks does not constitute a new behavior.

Installation/Upgrade (Migration) Considerations

No installation nor upgrade considerations exist for this feature. You may, however, turn off the feature if interoperability issues arise as a result of the feature. To do so, set the value of the Send Multicast MOH in H.245 OLC Message service parameter to False.

Serviceability Considerations

No serviceability considerations exist for this feature.

BAT Considerations

No BAT considerations exist for this feature.

CAR/CDR Considerations

No CAR nor CDR considerations exist for this feature.

Security Considerations

No security considerations exist for this feature.

AXL and CTI Considerations

No AXL considerations exist for this feature.

CTI-controlled phones work as before for multicast MOH. CTI-controlled applications such as CTI ports, and CTI route points do not perform multicast MOH, which is the same behavior as prior to the implementation of this feature.

User Tips

When multicast MOH gets turned on in Cisco Unified Communications Manager Administration, phone users receive MOH if the call connects through an intercluster trunk.

For More Information

Music on Hold, Cisco Unified Communications Manager Features and Services Guide, Release 6.1(1)

Party Entrance Tone


Tip The information in this section does not exist in the online help for Cisco Unified Communications Manager Administration or in any other Cisco Unified Communications Manager 6.1(x) document besides the release notes.


Description


Tip To configure the party entrance tone in previous releases of Cisco Unified Communications Manager, you configured the party entrance tone service parameter for the Cisco CallManager service, which applied to the entire cluster. In Cisco Unified Communications Manager 6.1(3x), you can configure the party entrance tone for directory numbers on a phone.


With the party entrance tone feature, a tone plays on the phone when a basic call changes to a mult-party call; that is, when a basic call changes to a barged call, cBarged call, ad hoc conference, meet-me conference, or a joined call. In addition, a different tone plays when a party leaves the multiparty call.

If the controlling device, that is, the originator of the multiparty call, has a built-in bridge, the tone gets played to all parties if you configured party tone entrance for the controlling device. When the controlling device leaves the call, Cisco Unified Communications Manager identifies whether another device on the call can play the tone; if another device on the call can play the tone, Cisco Unified Communications Manager plays the tone. If the controlling device cannot play the tone, Cisco Unified Communications Manager does not play the tone even if you enable the party entrance tone feature.

When a joined call or ad hoc conference begins, Cisco Unified Communications Manager uses the party entrance tone configuration from the conference controller. Cisco Unified Communications Manager uses this configuration until the conference ends.

If two ad hoc conferences are chained together and the controlling device for one conference has the party entrance tone set to True while the other controlling device for the other conference has a party entrance tone of False, Cisco Unified Communications Manager determines whether to plan the tone based on the conference to which the new party is added.

When a barge call gets created, the party entrance tone configuration of the barge target that shares the line with the barge initiator determines whether Cisco Unified Communications Manager plays the party entrance tone.

When a cBarge call gets created, the party entrance tone configuration of the cBarge target that shares the line with the cBarge initiator determines whether Cisco Unified Communications Manager plays the party entrance tone. However, if the target for the call is an existing ad hoc conference that is in the same cluster, the party entrance tone configuration for the ad hoc conference controller determines whether Cisco Unified Communications Manager plays the tone.

When a meet-me conference gets created, the party entrance tone configuration for the first party to enter the conference determines whether Cisco Unified Communications Manager plays the tone. Cisco Unified Communications Manager uses the configuration for the first party until the conference ends.

Cisco Unified Communications Manager Administration Configuration Tips and GUI Changes

To use the party entrance feature, ensure that you turned the privacy feature off for the devices and ensure that the controlling device for the multiparty call has a built-in bridge.

To configure the party entrance tone for a specific directory number, choose Call Routing > Directory Number in Cisco Unified Communications Manager Administration. From the Party Entrance Tone drop-down list box, choose one of the following options:

Default—Use the value that you configured in the Party Entrance Tone service parameter.

On—A tone plays on the phone when a basic call changes to a multiparty call; that is, a barge call, cBarge call, ad hoc conference, meet-me conference, or a joined call. In addition, a different tone plays when a party leaves the ad hoc call. If the controlling device, that is, the originator of the multiparty call has a built-in bridge, the tone gets played to all parties if you choose On for the controlling device. When the controlling device leaves the call, Cisco Unified Communications Manager identifies whether another device on the call can play the tone; if another device on the call can play the tone, Cisco Unified Communications Manager plays the tone. If the controlling device cannot play the tone, Cisco Unified Communications Manager does not play the tone even if you enable the party entrance tone feature.

Off—A tone does not play on the phone when a basic call changes to a ad hoc call.

Service Parameter and Enterprise Parameter Changes

For this location-based parameter, configure the Party Entrance Tone service parameter, which supports the Cisco CallManager service. To access this parameter, choose System > Service Parameters in Cisco Unified Communications Manager Administration; choose the server and the Cisco CallManager service. When the parameters display, locate the Party Entrance Tone service parameter. For more information on this parameter, click the name of the service parameter or the question-mark button in the Service Parameter Configuration window.

Installation/Upgrade (Migration) Considerations

Cisco Unified Communications Manager 6.1(3x) introduces this feature.

Serviceability Considerations

This feature relies on the Cisco CallManager service, so make sure that the service is activated in Cisco Unified Serviceability.

BAT Considerations

The Bulk Administration GUI has the following updates to support the party entrance tone feature:

Party Entrance Tone drop-down list box—Choose one of the following options:

Default—Use the value that you configured in the Party Entrance Tone service parameter.

On—A tone plays on the phone when a basic call changes to a ad hoc call; that is, a barge call, cBarge call, ad hoc conference, meet-me conference, or a joined call. In addition, a different tone plays when a party leaves the ad hoc call. If the controlling device, that is, the originator of the ad hoc call has a built-in bridge, the tone gets played to all parties if you choose On for the controlling device. When the controlling device leaves the call, Cisco Unified Communications Manager identifies whether another device on the call can play the tone; if another device on the call can play the tone, Cisco Unified Communications Manager plays the tone. If the controlling device cannot play the tone, Cisco Unified Communications Manager does not play the tone even if you enable the party entrance tone feature.

Off—A tone does not play on the phone when a basic call changes to a ad hoc call.


Note The Party Entrance Tone drop-down list box exists on the Phone Line Template, UDP Line Template, UDP Update Line, RDP Line Template, Phone Update Line, and UDP Update Line window.


For information regarding Insert, Export, and Validate Details support for party entrance tone "Support for Party Entrance Tone" section.

For more information on BAT, refer to the Bulk Administration Tool section of this document.

CAR/CDR Considerations

No CAR or CDR considerations exist for this feature.

Security Considerations

No security considerations exist for this feature.

AXL and CTI Considerations

No AXL or CTI considerations exist for this feature.

User Tips

For information on the phones that support this feature, see the "Barge Tone Enhancements" section.

For More Information

Barge Tone Enhancements

Table Out of Sync Detection


Note The information in this section does not exist in the online help for Cisco Unified Communications Manager Administration.


Description

When the Table Out Of Sync parameter is turned on, the Database Replication Status summary gets collected every day during the maintenance window. The system compares the output of three consecutive days to determine whether tables have been out of sync for all three days. If so, it triggers an alert.

This parameter, by default, gets set to Off and runs at the time that is specified in Maintenance Time parameter.

Cisco Unified Communications Manager Administration Configuration Tips and GUI Changes

To use the database table out of sync feature, ensure that you turn the parameter on.

To enable the database table out of sync feature, perform the following procedure:


Step 1 From Cisco Unified Communications Manager Administration, choose System > Service Parameter.

Step 2 From the Server drop-down list, select the server.

Step 3 From the Service drop-down list, select Cisco Database Layer Monitor.

Step 4 Set the Maintenance Time parameter value.

Step 5 Set the Maintenance Window parameter value.

Step 6 From the Table Out of Sync Detection drop-down list, choose On.

Step 7 From the MaintenanceTaskTrace drop-down list, choose On.

Step 8 Click Save.


Steps to Ensure That You Are Notified of Inconsistencies

To ensure that you will be notified if the databases on the publisher server and the subscriber servers are inconsistent, you should perform the following tasks:

Complete the steps that are described in "Cisco Unified Communications Manager Administration Configuration Tips and GUI Changes" section.

Enable the alert.

Configure the Alert in RTMT.

Enable the Alert

To enable Cisco Unified CM to alert you in case of out of sync conditions, perform the following steps from Cisco Unified Serviceability:


Step 1 From the Alarm menu, choose Configuration.

Step 2 From the server drop-down list, choose your server.

Step 3 From the Service Group drop-down list, choose Database and Admin Services and click Go.

Step 4 From the Service drop-down list, choose Cisco Database Monitor Layer Monitor and click Go.

Step 5 In the SDI Trace field, click Enable Alarm and set the Alarm Event Level to Error.

Step 6 Click Save.


Configure the Alert in RTMT

To configure the alert in RTMT, see the Setting Alert Properties in the Cisco Unified Real-time Monitoring Tool Guide.


Note You can configure RTMT to alert you via email.



Note Cisco recommends that you call TAC if this alert gets generated.


For More Information

Cisco Unified Real-time Monitoring Tool Guide

Transit Counter That is Implemented in Codeset5 for QSIG PRI Trunks

An IE that Q.931 supports, called Transit Counter, stops routing loops on PBXs.

The transit counter information element specifies a maximum length of 3 octets and may get included in the setup message. It indicates the number of private network transit exchanges that occur in a requested connection.

Cisco Unified CM parses a transit counter that is received in a setup message on a QSIG Trunk (as well as Annex M.1) when it is received in locking codeset5 and sends it to call control. If the subsequent leg of the call is QSIG , that leg increments the received transit counter and sends it outbound over QSIG (and Annex M.1) in locking codeset5.


Note Cisco Unified CM does not make route loop decisions that are based on transit counter information. It only transits and increments the counter.


A new service parameter, Enable Transit Counter Processing on QSIG Trunks, controls this implementation.

When the service parameter is set to false, the Unified CM

Behaves as it did in previous releases.

Does not send out the transit counter IE.

When the service parameter is set to true, the Unified CM

Only increments it in transit situations.

Never originates a transit counter.

Unconfigured Device Registration Attempts Restricted

Prior to Cisco Unified Communications Manager 6.1(3x), if a Cisco Unified IP Phone had not been added to the Cisco Unified Communications Manager database and did not have auto-registration enabled, the phone would repeatedly attempt to register (unsuccessfully) with Cisco Unified Communications Manager, thus wasting Cisco Unified Communications Manager with these repeated registration requests.

However, in Cisco Unified Communications Manager 6.1(3x), if auto-registration is not enabled and the phone has not been added to the Cisco Unified Communications Manager database, the phone will not attempt to register with Cisco Unified Communications Manager. The phone continues to display the Configuring IP message until auto-registration gets enabled or until the phone gets added to the Cisco Unified Communications Manager database.

Supported Devices

The following devices support this changed registration behavior:

IP Phone 7906G

IP Phone 7911G

IP Phone 7931G

IP Phone 7941G

IP Phone 7942G

IP Phone 7945G

IP Phone 7961G

IP Phone 7962G

IP Phone 7965G

IP Phone 7970G

IP Phone 7971G

IP Phone 7975G

Cisco Analog Telephone Adapter

VG248 Gateways

For more information, refer to the Cisco Unified IP Phone Administration Guide.

Cisco Unified Communications Manager Administration Configuration Tips

For information on configuring autoregistration, refer to the "Autoregistration" chapter in the Cisco Unified Communications Manager System Guide. For information on configuring a phone, refer to the "Phone Configuration" chapter in the Cisco Unified Communications Manager Administration Guide.

Before you configure a phone, consider the following information:

If the Cisco Unified Communications Manager database contains a real MAC address for a phone, not the dummy MAC address that is created via the Bulk Administration Tool (BAT), licensing immediately consumes device license units for the phone after the phone gets added to the database.

If the number of used device license units and number of pending device licensing units do not exceed the total number of device license units that are available for use, the phone with the real MAC address gets added to the database.

If the number of used device license units and number of pending device licensing units exceed the total number of device license units that are available for use, the phone with the real MAC address does not get added to the database.

Licensing uses the Is Active check box in the Phone Configuration window in Cisco Unified Communications Manager Administration to determine whether to consume device license units for the phone. In addition, Cisco Unified Communications Manager uses this check box to determine whether a phone should register with Cisco Unified Communications Manager.

For a phone that uses a real MAC address, not the dummy MAC address that is created via BAT, the check box displays as checked and disabled, which indicates that the phone uses device license units and can register with Cisco Unified Communications Manager.

For a phone that uses the dummy MAC address that is created via BAT, the Is Active check box displays as unchecked and enabled. If you manually convert the dummy MAC address to a real MAC address in the Phone Configuration window, check the Is Active check box, which ensures that the phone can register with Cisco Unified Communications Manager and that licensing consumes device license units for the phone.

Cisco Unified Communications Manager allows you to provision phones with dummy MAC addresses via BAT as long as the number of used device license units and the number of pending device license units do not exceed the total number of device license units that are available for use.

If you use the Cisco Unified Communications Manager Auto-Register Phone Tool (TAPS) to associate an auto-registered phone with the BAT dummy settings, the Cisco Unified Communications Manager Auto-Register Phone Tool deletes the auto-registered phone from the database, and licensing gives you credits for the device license units for the deleted phone. After the Cisco Unified Communications Manager Auto-Register Phone Tool applies the device name to the phone that uses the dummy MAC address, the Cisco Unified Communications Manager Auto-Register Phone Tool updates the Is Active check box to display as checked and disabled. Licensing consumes device license units for the phone, and the phone can register with Cisco Unified Communications Manager, unless the number of used device license units exceeds the total number of device license units that are available for use.

When a phone auto-registers for use with the Cisco Unified Communications Manager Auto-Register Phone Tool, it gets inserted into the database as long as the number of used device license units is less than the number of device license units that are available for use.

You can view the number of pending, used, and available device license units in the License Unit Report and the License Unit Calculator in Cisco Unified Communications Manager Administration.

GUI Changes

No new fields display in Cisco Unified Communications Manager Administration for this feature.

Service Parameter and Enterprise Parameter Changes

No parameter changes exist for this feature.

Installation/Upgrade (Migration) Considerations

After you install Cisco Unified Communications Manager 6.1(3x), if auto-registration is not enabled and the phone has not been added to the Cisco Unified Communications Manager database, the phone does not attempt to register with Cisco Unified Communications Manager.

Serviceability Considerations

The Real-Time Monitoring Tool and Cisco Unified Reporting can display information on registered and unregistered devices. For more information, refer to the Cisco Unified Communications Manager Real-Time Monitoring Tool Administration Guide and the Cisco Unified Reporting Administration Guide.

BAT Considerations

For information on adding devices through BAT, refer to the Cisco Unified Communications Manager Bulk Administration Guide.

CAR/CDR Considerations

No CAR or CDR considerations exist for this feature.

Security Considerations

No security considerations exist for this feature.

AXL and CTI Considerations

No AXL or CTI considerations exist for this feature.

User Tips

If the Configuring IP message displays on the phone, the phone user should contact the phone administrator.

Viewing Held Calls on Shared Lines


Tip The information in this section does not exist in the online help for Cisco Unified Communications Manager Administration or in any other Cisco Unified Communications Manager 6.1(x) document besides the release notes.


Description

With the held calls on shared lines feature, a phone user can determine whether the call was put on hold by the phone user locally at the primary device or by another party remotely on a shared device. How the held call displays on the devices depends on whether the primary device or shared device puts the call on hold. For information on how the held call displays on the devices, see the "Hold Status" section.

Cisco Unified Communications Manager Administration Configuration Tips and GUI Changes

This feature requires no configuration to work.

Service Parameter and Enterprise Parameter Changes

This feature requires no configuration to work.

Installation/Upgrade (Migration) Considerations

Cisco Unified Communications Manager 6.1(3x) introduces this feature.

Serviceability Considerations

No serviceability considerations exist for this feature.

BAT Considerations

No BAT considerations exist for this feature.

CAR/CDR Considerations

No CAR or CDR considerations exist for this feature.

Security Considerations

No security considerations exist for this feature.

AXL and CTI Considerations

No AXL or CTI considerations exist for this feature.

User Tips

For a list of phones that support this feature, see the "Hold Status" section.

For More Information

Hold Status

Bulk Administration Tool

This section contains information on the following topics:

Support for Party Entrance Tone

Support for Log Missed Calls

Support for Always Use Prime Line

Support for VG202 and VG204 Gateways

Support for Party Entrance Tone

The Bulk Administration GUI has the following updates to support the party entrance tone feature:

Party Entrance Tone drop-down list box—Choose one of the following options:

Default—Use the value that you configured in the Party Entrance Tone service parameter.

On—A tone plays on the phone when a basic call changes to a ad hoc call; that is, a barge call, cBarge call, ad hoc conference, meet-me conference, or a joined call. In addition, a different tone plays when a party leaves the ad hoc call. If the controlling device, that is, the originator of the ad hoc call has a built-in bridge, the tone gets played to all parties if you choose On for the controlling device. When the controlling device leaves the call, Cisco Unified Communications Manager identifies whether another device on the call can play the tone; if another device on the call can play the tone, Cisco Unified Communications Manager plays the tone. If the controlling device cannot play the tone, Cisco Unified Communications Manager does not play the tone even if you enable the party entrance tone feature.

Off—A tone does not play on the phone when a basic call changes to a ad hoc call.


Note The Party Entrance Tone drop-down list box exists on the Phone Line Template, UDP Line Template, RDP Line Template, Phone Update Line, UDP Update Line, and Gateway Line Template windows.


Insert, Export, and Validate Details support for party entrance tone—The following insert, export, and validate details features have support for the party entrance tone:

Insert Phones Specific Details

Insert Phones All Details

Export Phones Specific Details

Export Phones All Details

Validate Phones All Details

Validate Phones Specific Details

Insert UDP All Details

Insert UDP Specific Details

Export UDP All Details

Export UDP Specific Details

Validate UDP All Details

Validate UDP Specific Details

Insert Phones/Users

Validate Phones/Users

Insert Gateways

Insert Remote Destination Profiles

Export Remote Destination Profiles

Phone Add lines

Phone Update Lines

UDP Update Lines

UDP Add Lines

Generate Phone Report

Generate UDP Report

File Formats—The following file formats support the party entrance tone feature:

Phone File Format—Party Entrance Tone field represents a part of the Line Fields section.

UDP File Format—Party Entrance Tone field represents a part of the Line Fields section.

Remote Destination Profile File Format—Party Entrance Tone field represents a part of the Line Fields section.

Generate User Device Profile Report—The Generate User Device Profile Report Configuration page lists the Party Entrance Tone field in the Line Fields section.

Generate Phone Report—The Generate Phone Report Configuration page lists the Party Entrance Tone field in the Line Fields section.

Support for Log Missed Calls

The Bulk Administration GUI has the following updates to support the Log Missed Calls feature:

Log Missed Calls Check Box— This check box allows you to turn this feature on or off. If the check box displays as checked (turned on), which is the default for this setting, Cisco Unified Communications Manager logs missed calls in the call history for that shared line appearance on the phone.


Note The Log Missed Calls Check Box exists on the Phone Line Template, UDP Line Template, Phone Update Line, and UDP Update Line windows.


Insert, Export, and Validate Details support for the log missed calls feature—The following insert, export, and validate details features have support for the log missed calls feature:

Insert Phones Specific Details

Insert Phones All Details

Export Phones Specific Details

Export Phones All Details

Validate Phones All Details

Validate Phones Specific Details

Insert UDP All Details

Insert UDP Specific Details

Export UDP All Details

Export UDP Specific Details

Validate UDP All Details

Validate UDP Specific Details

Insert Phones/Users

Validate Phones/Users

Phone Add lines

Phone Update Lines

UDP Update Lines

UDP Add Lines

Generate Phone Report

Generate UDP Report

File Formats—The following file formats support the log missed calls feature:

Phone File Format—Log Missed Calls field represents a part of the Line Fields section.

UDP File Format—Log Missed Calls field represents a part of the Line Fields section.

Generate User Device Profile Report—The Generate User Device Profile Report Configuration page lists the Log Missed Calls field in the Line Fields section.

Generate Phone Report—The Generate Phone Report Configuration window lists the Log Missed Calls field in the Line Fields section.

Support for Always Use Prime Line

The Bulk Administration GUI has the following updates to support the Always Use Prime Line feature:

Always Use Prime Line drop-down list box—Choose one of the following options:

Off

On

Default

Always Use Prime Line for Voice Message drop-down list box—Choose one of the following options:

Off

On

Default


Note For details of configuration options for the Always Use Prime Line feature, refer to Table 3 and Table 4.



Note The Always Use Prime Line, and Always Use Prime Line for Voice Message drop-down list boxes exist on the Phone Template, UDP Template, and Update Phone windows.


Insert, Export, and Validate Details support for always use prime line—The following insert, export, and validate details features have support for the always use prime line feature:

Insert Phones Specific Details

Insert Phones All Details

Export Phones Specific Details

Export Phones All Details

Validate Phones All Details

Validate Phones Specific Details

Insert UDP All Details

Insert UDP Specific Details

Export UDP All Details

Export UDP Specific Details

Validate UDP All Details

Validate UDP Specific Details

Insert Phones/Users

Validate Phones/Users

Generate Phone Report

Generate UDP Report

Phone File Format—Phone File Format Configuration page lists the Always Use Prime Line, and Always Use Prime Line for Voice Message drop-down list boxes in the device fields section.

UDP File Format—UDP File Format Configuration window lists the Always Use Prime Line, and Always Use Prime Line for Voice Message drop-down list boxes in the device fields section.

Generate User Device Profile Report—The Generate User Device Profile Report Configuration window lists the Always Use Prime Line and Always Use Prime Line for Voice Message fields in the Device Fields section.

Generate Phone Report—The Generate Phone Report Configuration window lists the Always Use Prime Line and Always Use Prime Line for Voice Message fields in the Device Fields section.

Support for VG202 and VG204 Gateways

BAT now supports VG202 and VG204 gateways. The Bulk Administration Tool has the following updates to support VG202 and VG204 gateways:

Bulk Administration > Gateways > Gateway Template—VG202 and VG204 gateways now display in the Gateway Type drop-down list box.

Bulk Administration > Gateways > Insert Gateways—VG202 and VG204 gateways now display in the Gateway Type drop-down list box.

Bulk Administration > Gateways > Insert Gateways. Select Gateway type as VG202 or VG204 and click next. The second Insert Gateways Configuration page displays—The View Sample File link displays VG202 and VG204 sample files.

File Formats—the Create File Format and Add File Format gateway windows now support VG202 and VG204 gateways.

Generate Gateway Report—The Generate Gateway Report Configuration windows now lists all BAT supported gateways including VG202 and VG204.

Delete Gateway—The Delete Gateways Configuration window now lists all BAT supported gateways including VG202 and VG204.

BAT.XLT Support—BAT.XLT supports VG202 and VG204 gateways.

Cisco Unified Serviceability

The following sections comprise new and changed features in serviceability for Unified CM 6.1(3x).

DBReplicationTableOutOfSync Alarm

Cisco UXL Web Service Added to Service Activation Window

DBReplicationTableOutOfSync Alarm

In Cisco Unified Serviceability, you can configure the DBReplicationTableOutOfSync alarm, as described in the "New Preconfigured Alert - DBReplicationTableOutOfSync" section.

Cisco UXL Web Service Added to Service Activation Window

In most Cisco Unified Communications Manager releases, the TabSync client in Cisco IP Phone Address Book Synchronizer uses AXL for end-user queries to the Cisco Unified Communications Manager database. In Cisco Unified Communications Manager 6.1(3x), the TabSync client uses the Cisco UXL Web Service for queries to the Cisco Unified Communications Manager database, which ensures that Cisco IP Phone Address Book Synchronizer users have access only to end-user data that pertains to them.

In the Service Activation window in Cisco Unified Serviceability (Tools > Service Activation), you can activate the Cisco UXL Web Service, which performs the following functions:

Conducts authentication checks by verifying the end user name and password when an end user logs in to Cisco IP Phone Address Book Synchronizer.

Conducts a user authorization check by only allowing the user that is currently logged in to Cisco IP Phone Address Book Synchronizer to perform functions such as listing, retrieving, updating, removing, and adding contacts.

Cisco Unified Real-Time Monitoring Tool

This section contains information on the following topics:

Quality Report Tool Reports

New Preconfigured Alert - DBReplicationTableOutOfSync

System History Log Displays in RTMT

Quality Report Tool Reports

A change occurred in the Call State information that is collected from Cisco Unified Communications Manager/CTIManager and displayed in the Quality Report Tool (QRT) reports. Previously, the information included Connected, Connected Conference, Connected Transfer, and On Hook call state information. Now, the report only includes Connected and On Hook call state information.

New Preconfigured Alert - DBReplicationTableOutOfSync

For information on the DBReplicationTableOutofSync alert, see the "Table Out of Sync Detection" section.

System History Log Displays in RTMT

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

RTMT > Trace Log Collection

For more information on the system history log, see the "System History Log for Cisco Unified Communications Manager" section.

Cisco Unified Communications Manager CDR Analysis and Reporting

This section contains these subsections:

Configuring Department Bills Reports

Reports That Are Unavailable to Administrator While CAR Database Gets Manually Purged or CDR Records Get Reloaded

SIP Call with URL as Extension Number Now Supported

CDR Search by User Extension Supports "+" and URLs for SIP Calls

Changes to Mail Server Configuration GUI

Change in Supported FTP/SFTP Versions for CAR Billing Servers

Effects on CAR Data When You Upgrade Cisco Unified Communications Manager by Using Data Migration Assistant

Ensure CAR Administrator Privileges Are Restored After Upgrade

Configuring CDR Error Reports

Event Log Report Status

New Error Message That Is Introduced If Data Present in Invalid or Remainder Partitions

Configuring Individual and Department Bills Reports

Configuring Department Bills Reports

The following additional note applies to Step 6 of the Configuring Department Bills Reports procedure:

Click the Down radio button to view your direct reports. Use the Up and Down radio buttons to move up and down the report chain.

Reports That Are Unavailable to Administrator While CAR Database Gets Manually Purged or CDR Records Get Reloaded

A CAR administrator can no longer generate CAR reports when a manual purge of the CAR database is in process or CDR records are reloading. The following message displays when you try to run reports during these processes:

10023: Manual Purge/Reload is in process. Please run the reports once the Manual 
Purge/Reload is over.
 
   

Both the Purge button and the Reload All Call Detail Records button get disabled, and the following message displays on the Manual Purge window, when either a manual purge or CDR reload occurs:

Manual Purge/Reload is still running. User will not be allowed to run another instance of 
Manual Purge/Reload. So, both Purge and Reload All Call Detail Records buttons are 
disabled.
 
   

Before this enhancement, a CAR administrator could request CAR reports during the purge, but message 10012 displayed.

SIP Call with URL as Extension Number Now Supported

Because calling and called parties can have SIP calls where the extension number is a URL, you can use all printable ASCII characters in the extension number. No space gets allowed in the URL. For example, extension "1000 1001" does not get accepted as a valid URL. The following message displays:

30035 Invalid extension number.

Note Printable ASCII characters comprise characters with ASCII code (in decimal) 33 through 126.


CDR Search by User Extension Supports "+" and URLs for SIP Calls

When you use the CDR Search by User Extension feature, you may use the "+" in any position of the user extension number; however, in the current release of Cisco Unified Communications Manager and previous releases, the "+" cannot be used in any dial plan configurations.

When the user extension number is a SIP call with a URL, the system allows no space in the URL.

Changes to Mail Server Configuration GUI

You must now configure the mail ID, mail domain, and mail server name when you configure the mail server. Previously, you only had to configure the mail ID.

Procedure


Step 1 Choose System > System Parameters > Mail Parameters.

The Mail Parameters window displays.

Step 2 In the Mail ID field, enter the e-mail identifier that will be used in the From field when e-mails are sent (for example, smith1@abc.com, enter smith1 in the Mail ID field).


Note CAR does not support SMTP authentication. You must disable authentication on the SMTP mail server.


Step 3 The Password field and the Confirm Password field automatically get populated with the user password information.

Step 4 In the Mail Domain field, enter the domain name for the server that runs the e-mail system (that is, abc.com from the example in Step 2).

Step 5 In the Mail Server Name field, enter the mail server name or the IP address where the mail server runs (for example, 192.168.10.0)


Note You must provide entries in the Mail ID, Mail Domain, and Mail Server Name fields.


Step 6 To make the changes, click the Update button.


Change in Supported FTP/SFTP Versions for CAR Billing Servers

Cisco allows you to use any SFTP server product but Cisco recommends SFTP products that have been certified with Cisco through the Cisco Technology Developer Partner (CTDP) program.

CTDP partners, such as GlobalSCAPE, certify their products with a 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 htttp://developer.cisco.com/web/cdc/home. 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 these servers, but you must contact the vendor for support:

Open SSH (for Unix systems)

Cygwin (Refer to http://sshwindows.sourceforge.net/.)

Titan (Refer to http://www.titanftp.com/.)

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

Cisco has tested and will support the following versions of FTP or SFTP for CAR billing servers:

Linux/Unix

FTP: Unix (SunOS 5.6 Generic_105181-10) and Linux server (2.4.21-47.ELsmp and 2.6.9-42.7.ELsmp)

SFTP: Unix (SunOS 5.6 Generic_105181-10) and Linux server (2.4.21-47.ELsmp and 2.6.9-42.7.ELsmp)

Windows

FTP: Microsoft FTP service (Windows 2000 5.00.2195 sp4, IIS 5.0) and WAR FTP Daemon (1.82.0.10)

Effects on CAR Data When You Upgrade Cisco Unified Communications Manager by Using Data Migration Assistant

If you do not need to carry over your CAR data to Cisco Unified Communications Manager 6.1(3x), Cisco recommends that you purge the CAR data before you run the Data Migration Assistant (DMA). Purging the CDR data speeds up the migration process and decreases the size of the DMA TAR file.


Note Make sure that you purge any CAR records that are older than 180 days.


The Cisco Unified Communications Manager installation program limits the time in which CAR records migrate from the DMA TAR file to the CAR database on the upgraded system. The time limit that is allotted for the CAR component specifies 60 minutes. So, to facilitate migration of more data within the stipulated time, CAR uses the following logic:

Data migration starts with the migration of billing records from the tbl_billing_data CSV file into the tbl_billing_data table of the CAR database. Data migration starts from the latest record and proceeds toward the oldest record in the CSV file. The billing data migration stops when no more billing records remain to be migrated or the 60-minute time limit is reached, whichever occurs first.

After the billing data migration, if time remains in the preallotted 60-minutes, CAR proceeds with migration of error records from the tbl_billing_error CSV file into the tbl_billing_error table of the CAR database. Data migration starts from the latest record and proceeds toward the oldest record in the CSV file. For each error record that is migrated, CAR migrates the data that corresponds to the error_record_id that is present in the tbl_error_id_map CSV file into the tbl_error_id_map table of the CAR database. This action ensures that error record migration stays consistent with data in the tbl_error_id_map. The migration process continues until no more data remains to migrate or the 60-minute time limit gets reached, whichever occurs first.

Whenever the time limit gets reached, CAR data migration stops, and the tbl_system_preferences of the CAR database gets updated to reflect the data present in the upgraded system database.


Note If you upgrade from Cisco Unified Communications Manager 4.x, Cisco Unified Communications Manager saves the content of the Cisco Unified Communications Manager 4.x CAR database to CSV files. The Cisco Unified Communications Manager 4.x CAR database has part of the CDR information. The Cisco Unified Communications Manager 4.x CDR database stores the complete information about CDRs. This database does not migrate. The Data Migration Tool uses the CAR database CSV files to migrate the CAR database. The system stores the CSV files in the /common/download/windows/car directory. The system stores the pregenerated reports in the /common/download/windows/pregenerated database. Because no corresponding CDR database exists in Cisco Unified Communications Manager 5.x and later releases, the complete CDR data does not migrate to the Cisco Unified Communications Manager 5.x or 6.x system. The Cisco Unified Communications Manager 5.x and 6.x CAR database schema gets extended to contain complete CDR information, but only for the new CDRs that the Cisco Unified Communications Manager 5.x and 6.x system generates.


Ensure CAR Administrator Privileges Are Restored After Upgrade

When you use DMA to upgrade Cisco Unified Communications Manager, CAR users no longer have CAR administrator privileges after the upgrade and become standard end users. You must reset the CAR administrator privileges after the upgrade. Refer to the "Configuring CAR Administrators, Managers, and Users" section in the CDR Analysis and Reporting Administration Guide for more information on how to configure CAR administrators.

Configuring CDR Error Reports

To determine why the error records fail the CDR load, you must review the information in the tbl_error_id_map table.

Table 6 lists the CDR error codes and the definition of the error.

Table 6 CDR Error Codes 

Error Code
Definition

CDRs

31101

CDR globalCallID_callManagerId <= 0

31102

CDR globalCallID_callId <= 0

31103

CDR origLegCallIdentifier <= 0

31105

CDR dateTimeOrigination <= 0

31108

CDR destLegIdentifier <= 0

31110

CDR dateTimeConnect <= 0

31111

CDR dateTimeDisconnect <= 0

31119

CDR originalCalledPartyNumber is empty

31120

CDR finalCalledPartyNumber is empty

31122

CDR duration < 0

31137

CDR LDAP error while retrieving UserID or ManagerID

31139

CDR callingPartyNumber is empty

31147

CDR origDeviceName is empty

31148

CDR destDeviceName is empty

31151

CDR origCallTerminationOnBehalfOf < 0

31152

CDR destCallTerminationOnBehalfOf < 0

31153

CDR lastRedirectRedirectOnBehalfOf < 0

31155

CDR destConversationId < 0

31156

CDR globalCallId_ClusterID is empty

Orig CMR

31123

Orig CMR globalCallID_callManagerId <= 0

31124

Orig CMR globalCallID_callId <= 0

31125

Orig CMR numberPacketsSent < 0

31126

Orig CMR numberPacketsReceived < 0

31127

Orig CMR jitter < 0

31129

Orig CMR callIdentifier <= 0

31149

Orig CMR deviceName is empty

31157

Orig CMR globalCallId_ClusterID is empty

Dest CMR

31140

Dest CMR globalCallID_callManagerId <= 0

31141

Dest CMR globalCallID_callId <= 0

31142

Dest CMR numberPacketsSent < 0

31143

Dest CMR numberPacketsReceived < 0

31144

Dest CMR jitter < 0

31145

Dest CMR callIdentifier <= 0

31150

Dest CMR deviceName is empty

31158

Dest CMR globalCallId_ClusterID is empty


Event Log Report Status

A new field has been added to the Event Log report status: Scheduled—If this check box is checked, the event log report includes tasks that have been scheduled but have not yet started.

When the Scheduler restarts, all unfinished jobs with a status of Scheduled get deleted. Current jobs with the status of In Progress or Scheduled get changed to Unsuccessful.

New Error Message That Is Introduced If Data Present in Invalid or Remainder Partitions

A message gets logged in the CAR Scheduler traces if data is present in invalid and remainder partitions of the tbl_billing_data and tbl_billing_error files.

The LWM/HWM/2M e-mail alerts that get sent to the CAR administrator when CAR detects records in either the part_invalid or part_remainder partitions will contain the following information:

Data is present in invalid/remainder partition also, which cannot be removed by 
Automatic-Purge. Please delete these record(s) manually from Manual-Purge.

Configuring Individual and Department Bills Reports

Before you can configure the Individual Bills report, you must ensure that a device with an assigned Owner User ID exists in Cisco Unified Communications Manager Administration for each user that is included in the report. Use the following procedure to create the Owner User IDs:

Procedure for Adding Owner User ID to Individual Bills

In Cisco Unified Communications Manager Administration, choose Device > Phone > Add a New Phone > Phone Configuration.

Add the information for the device and the user.

Before you can configure the Department Bills report, you must ensure that a device with an assigned Owner User ID and Manager User ID exists in Cisco Unified Communications Manager Administration for each user that is included in the report. Use the following procedure to add the device, Owner User ID, and the associated Manager UserID for each user:

Procedure for Adding Owner User ID and Manager ID to Department Bills

In Cisco Unified Communications Manager Administration, choose Device > Phone > Add a New Phone > Phone Configuration.

Add the information for the device and the user.

In Cisco Unified Communications Manager Administration, choose User Management > End User > Add.

Add the Manager User ID information to the end user information.

For both individual bills and department bills, if the Extension Mobility feature is enabled on the device and the user logs in to the phone and places a call, the User ID that gets recorded in the CDRs represents the logged in User ID. If Cisco Extension Mobility is not enabled on the device, the User ID that gets recorded in the CDRs specifies the Owner User ID that is configured for the device. In the situation where neither the User ID or the Owner User ID is configured (that is, Cisco Extension Mobility is not enabled, and the Owner User ID is not configured), the User ID field in the CDRs gets recorded as blank. In this situation, CAR uses the default User ID of "_unspecified user" when it loads the CDRs, and the CDRs do not display in the Individual Bills User reports because no user by the name of "_unspecifieduser" exists in the Cisco Unified Communications Manager database. If you look for the reports for a particular end user in the directory, either the User ID for the particular end user must be configured as the Owner User ID for the device or the particular end user must have logged in to the device with the Cisco Extension Mobility feature enabled.

Cisco Unified Communications Manager Call Detail Records

This section contains these subsections:

CallingPartyNumber CDR Field Not Affected by Direct Calls

Video Conference Call CDR Example

Updated Information on Global Call ID CDR Field

Updated Information on Global Call ID CDR Field

For Cisco Unified Communications Manager Release 5.x and later releases, the value in the GlobalCallId CDR field survives over Cisco Unified Communications Manager restarts. In Release 4.x and earlier releases, even though the GlobalCallId field is time-based, the field gets reused under conditions of heavy traffic. Because of this behavior, problems can occur with customer billing applications and the ability of CAR to correlate CMRs with CDRs and to correlate conference call CDRs. For Release 5.x and later releases, GlobalCallId redesign ensures the field retains a unique value, at least for a certain number of days. Now, the last used globalCallId_callId value gets written to disk periodically (for every x number of calls). The value gets retrieved after a Cisco Unified Communications Manager restart, and the new globalCallId_callId value begins with this number plus x.

CallingPartyNumber CDR Field Not Affected by Direct Calls

When the Add Incoming Number Prefix to CDR service parameter gets set to True, type of number provides the basis for the prefixing digits that get configured. Setting this service parameter to True prefixes only the following prefixing (advanced) service parameters, based on the type of number for the incoming call:

Incoming calling party national number prefix.

Incoming calling party international number prefix.

Incoming calling party subscriber number prefix.

Incoming calling party unknown number prefix.


Note Setting the Add Incoming Number Prefix to CDR service parameter to True has no effect if translation occurs at the translation pattern level.


For normal calls, without any redirection or split/join in case of feature interaction, the CDR entry for the CallingPartyNumber field remains the same as the incoming number. But for pickup calls (one-touch), the CallingPartyNumber field in the CDR gets changed to the number after transformation at translation pattern level because the CallingPartyNumber field in the CDR gets updated every time a new call request or a split/join or redirection occurs. When an incoming call from a gateway occurs, the nontranslated number gets received for the CallingPartyNumber field in the CDR.

For a direct call, no split/join requests exist; therefore, the CallingPartyNumber field remains the nontranslated number. However, for a one-touch pickup call, upon pickup, the Cisco Unified Communications Manager splits the original call and the pickup call and then joins them together upon pickup. At this point, the translation pattern gets applied to the calling party, and the CDR uses the translated number for the calling party.

In the following examples, the number 89999999 has a calling party transform mask that gets entered as 0351441132. A call comes in from a PSTN from calling party 89999999 to an IP phone on the Cisco Unified Communications Manager.

CDR Example 1

The IP phone answers the call. The calling party transform mask does not get applied to the calling party number.

Field Names
CDR

globalCallID_callId

1

origLegCallIdentifier

100

destLegCallIdentifier

101

callingPartyNumber

89999999

originalCalledPartyNumber

2001

finalCalledPartyNumber

2001

origCause_Value

16

dest_CauseValue

0

duration

60


CDR Example 2

The call gets picked up by another IP phone that is using the one-touch pickup feature. The calling party transform mask gets applied to the calling party number.

Field Names
CDR

globalCallID_callId

22

origLegCallIdentifier

1

destLegCallIdentifier

2

callingPartyNumber

0351441132

originalCalledPartyNumber

2001

finalCalledPartyNumber

2002

lastRedirectDn

2001

origCause_Value

0

dest_CauseValue

16

origCalledPartyRedirectReason

0

lastRedirectRedirectReason

5

origCalledPartyRedirectOnBehalfOf

16

lastRedirectRedirectOnBehalfOf

16

duration

120


CMR Examples Provided

The following examples of CMRs get generated during a normal call (IP phone to IP phone). Normal calls log three records per call: one CDR and two CMRs (one for each endpoint).

These examples represent a call between directory number 1010 and 1014. To see a sample of the CDR that gets generated during a normal call, see the "Normal Calls" section of the latest release of the Cisco Unified Communications Manager Call Detail Records Administration Guide.

CMR Example

Field Names
AAC CDR

cdrRecordType

2

globalCallID_callManagerid

1

globalCallID_callId

96004

nodeId

1

callIdentifier

28141535

directoryNumber

1010

dateTimeStamp

1202412060

numberPacketsSent

358

numberOctetsSent

61576

numberPacketsReceived

351

numberOctetsReceived

60372

numberPacketsLost

1

jitter

0

latency

0

pkid

e95df5b1-2914-4a03-befb-0f58bf16392d

directoryNumberPartition

 

deviceName

SEP003094C39BE7

globalCallId_ClusterId

StandAloneCluster

varVQMetrics

MLQK=0.0000;MLQKav=0.0000;MLQKmn=0.0000;MLQKmx=0.0000;MLQKvr=0.95;CCR=0.0000;ICR=0.0000;ICRmx=0.0000;CS=0;SCS=0


Video Conference Call CDR Example

Calls that are part of a video conference have multiple records logged. The number of CDR records that get generated depends on the number of parties in the video conference. One CDR record exists for each party in the video conference: one for the original placed call, one for each setup call that was used to join other parties to the video conference, and one for the last two parties that are connected in the video conference.

Therefore, for a three-party ad hoc video conference, six CDR records exist:

1 record for the original call

3 records for the parties that connected to the conference

1 record for each setup call

1 record for the final two parties in the conference

Video Conference Call CDR Example

1. Call from 2001 to 2309; 2309 answers, and they talk for 60 seconds.

2. 2001 presses the conference softkey and dials 3071111.

3. 307111 answers and talks for 20 seconds; 2001 presses the conference softkey to complete the conference.

4. The three members of the conference talk for 360 seconds.

5. 3071111 hangs up; 2001 and 2309 stay in the conference. Because only two participants remain in the conference, the conference feature joins the two directly together, and they talk for another 55 seconds.


Note Each video conference call leg gets shown placing a call into the conference bridge. The call gets shown as a call into the bridge, regardless of the actual direction of the call.


FieldNames
Orig Call CDR
Setup Call CDR
Conference CDR 1
Conference CDR 2
Conference CDR 3
Final CDR

globalCallID_callId

1

2

1

1

 

1

origLegCallIdentifier

101

105

101

102

106

101

destLegCallIdentifier

102

106

115

116

117

102

callingPartyNumber

2001

2001

2001

2309

3071111

2001

originalCalledPartyNumber

2309

3071111

b0029901001

b0029901001

b0029901001

2309

finalCalledPartyNumber

2309

3071111

b0029901001

b0029901001

b0029901001

2309

lastRedirectDn

2001

3071111

b0029901001

b0029901001

b0029901001

b0029901001

origCause_Value

393216

0

16

393216

393216

16

dest_CauseValue

393216

0

393216

393216

393216

0

origVideoCap_Codec

103

103

103

103

103

103

origVideoCap_Bandwidth

320

320

320

320

320

320

origVideoCap_Resolution

0

0

0

0

0

0

origVideoTransportAddress_IP

552953152

552953152

552953152

-822647488

-945658560

552953152

origVideoTransportAddress_Port

5445

5445

5445

5445

5445

5445

destVideoCap_Codec

103

103

103

103

103

103

destVideoCap_Bandwidth

320

320

320

320

320

320

destVideoCap_Resolution

0

0

0

0

0

0

destVideoTransportAddress_IP

-822647488

-945658560

-666216182

-666216182

-666216182

-822647488

destVideoTransportAddress_Port

5445

10002

10000

10004

10001

5445

origCalledPartyRedirectReason

0

0

0

0

0

0

lastRedirectRedirectReason

0

0

0

0

0

98

origTerminationOnBehalfOf

4

4

12

12

4

12

destTerminationOnBehalfOf

4

4

0

0

4

4

origCalledRedirectOnBehalfOf

0

0

4

4

4

0

lastRedirectRedirectOnBehalfOf

0

0

4

4

4

4

joinOnBehalfOf

0

0

4

4

4

4

Conversation ID

0

1

 

1

1

0

duration

60

360

 

360

360

55


Comment

Orig Call CDR

 

Setup Call CDR

ConfControllerDn=2001;ConfControlerDeviceName=SEP0003E333FEBD

Conference CDR 1

ConfControllerDn=2001;ConfControlerDeviceName=SEP0003E333FEBD

Conference CDR 2

ConfControllerDn=2001;ConfControlerDeviceName=SEP0003E333FEBD

Conference CDR 3

ConfControllerDn=2001;ConfControlerDeviceName=SEP0003E333FEBD

Final CDR

 

Cisco Unified Reporting

Cisco Unified Reporting includes a new report that indicates the number of phones with no associated users, the number of users that are associated with only one phone, and the number of users that are associated with more than one phone.

For a complete description of reports that are available on your system and the data that gets captured in a report, access the Report Descriptions report, as described in the Cisco Unified Reporting Administration Guide.

Cisco and Third-Party APIs

The following sections describe new features and changes that are pertinent to this release of the Cisco Unified Communications Manager APIs and the Cisco extensions to third-party APIs.:

Skinny Client Control Protocol (SCCP)

Administrative XML Interface

Cisco Web Dialer API

Skinny Client Control Protocol (SCCP)

The following sections describe updates to the SCCP interface:

BLF Enhancements

I-Hold

Updated SCCP Messages

BLF Enhancements

This release supports the following variations of Busy Lamp Field (BLF):

Notification BLF Alerting—When a call arrives on a monitored line, an alerting indication notifies the monitoring stations. The alerting indication comprises a BLF icon, a flashing LED, an alerting icon, and an audible alert.

BLF Pickup—This enhancement allows a user to pick up a call from the monitoring station during the BLF Alerting state by pressing the corresponding BLF line button.

I-Hold

This feature provides visual distinction that shows which line placed a call on hold in a shared line configuration. With this enhancement, when a call is put on hold by the local line, the current LED behavior (flashing green) continues, and the remote line changes to a flashing red LED status.

Updated SCCP Messages

This release adds, modifies, or deletes the following SCCP messages:

New messages

StationFeatureStatV2Message—Sent from Cisco Unified Communications Manager

StationFeatureStatReqMessage—Sent from Cisco Unified Communications Manager

StationSetLampMessage—Sent from Cisco Unified Communications Manager

StationStimulusMessage—Sent to Cisco Unified Communications Manager

StationStartToneMessage—Sent from Cisco Unified Communications Manager

Modified message

StationCallStateMessage—Modified StationDCallState ENUM

Deleted messages

StationStartSessionTransmissionMessage

StationStopSessionTransmissionMessage

Administrative XML Interface

The Administrative XML (AXL) interface uses the Tomcat web service that is running on the Cisco Unified Communication Manager publisher server to return client data. Several other publisher server features share this service, including Cisco Unified Communication Administration, Cisco IP Manager Assistant, Cisco Web Dialer, Cisco Extension Mobility, and the Bulk Administration Tool. The Cisco Unified Communications Manager publisher server includes enhancements that ensure that no single application can consume all available Tomcat resources.

The AXL interface now includes a throttling mechanism that limits the amount of data that client can return. The limit for data that gets returned in any single request specifies 8 MB. The limit for concurrent data requests specifies 16 MB, which can be split over any number of concurrent requests (for example, 8 concurrent requests with each requiring 2 MB of data to be returned; 4 concurrent requests with each requiring 4 MB of data to be returned; or any other combination not exceeding 8 MB per request or 16 MB concurrently).

This feature

Prevents AXL request processing from making the Tomcat service unresponsive.

Allows critical applications such as the Cisco Unified Communications Manager Administration interface and logging in to and out of Cisco Extension Mobility to function even when heavy AXL queries are processed.

Allows client applications to obtain the information that is requested.

Maximizes interface throughput.

Minimizes required changes to existing applications.

AXL Data Throttling

The following AXL methods now include data throttling:

executeSQLQuery

listDeviceByNameAndClass

listDeviceByServiceName

listPhoneByDescription

listPhoneByName

listUserByName

With data throttling, the AXL interface now returns the following message when the 8-MB limit is reached: "Query request too large. Total rows matched: <Matched Rows>. Suggested row fetch: less than <Number of Rows>."

In addition, new <skip> and <first> tags for the List X methods allow developers to fetch the data requested.

Developers who use ExecuteSQLQuery should use standard SQL Skip and First tags in the request to retrieve the desired data set.

Interaction

This section describes how the interface responds in a variety of situations.

Example 1, Option 1: Client requests data that exceeds 8 MB

Server response: ProcessingConstraintException AXL error code 5011"Query request too large. Total rows matched: <Matched Rows>. Suggested row fetch: less than <Number of Rows>"

<Number of Rows> specifies the suggested number of rows that a single request can return to keep the data exchange under the 8-MB limit. Clients should use <Matched Rows> to determine the number of iterations that are required to retrieve the complete data set that a query tries to fetch.

Client response, Option 1:

1. Client logic analyzes the server response and obtains the value of <Row Fetch>.

2. Client stores the <Row Fetch> value in a constant that depicts Row Fetch Step Size. For this example, rowFetchStepSize represents the constant name.

3. Client logic generates the request in parts based on the <Row Fetch> value.

4. Client keeps track of the number of rows that were received in the previous request. For this example, this information exists in a variable that is named prevRows.

5. Client keeps track of the total number of rows that are fetched. For this example, this information exists in a variable that is named totalRowFetch.

6. Before sending the next request, client checks whether prevRows == <Row Fetch>.

7. If the check returns true, continue the request generation loop; otherwise, break from the loop.

Example 1, Option 2: Client requests data that exceeds 8 MB

Server response: ProcessingConstraintException AXL error code 5011 "Query request too large. Total rows matched: <Matched Rows>. Suggested row fetch: less than <Number of Rows>"

<Number of Rows> specifies the suggested number of rows that a single request can return to keep the data exchange under the 8-MB limit. Clients should use <Matched Rows> to determine the number of iterations that are required to retrieve the complete data set that a query tries to fetch.

Client response, Option 2:

1. Client logic analyzes the server response and obtains the value of <Row Fetch> and <totalRows>.

2. Client stores the <Row Fetch> and <totalRows> values in variables. For this example, the variable names comprise rowFetchStepSize and countOfRows.


Note Alternatively, the client can execute a query for count(*) to obtain the number of rows that can be fetched from the database.


3. Client logic calculates the number of iterations based on the values that are stored in rowFetchStepSize and countOfRows.

4. Client logic declares two variables: "skip" (with the initial value of 0) and "first" (with initial value set to rowFetchStepSize).

5. Client starts the iteration.

6. Client logic generates the request based on "skip" and "first" at every iteration.

7. Client modifies the value of "skip" and "first" at every iteration.

8. Client checks the response at every iteration.

9. If the response is a MemoryConstraintException, the client waits until the requests in progress completes, then continues the iteration.

If the response is not a MemoryConstraintException, the client continues the iteration.

10. Iterations continue until the <number Of Iterations> value is reached.

Example 2: Client sends single 8-MB request

Server responds with requested data.

Example 3: Client sends two 8-MB requests simultaneously

Server responds with requested data.

Example 4: Client sends more than two 8-MB requests simultaneously

The server processes the first two requests. Other concurrent requests that may be received generate this exception: MemoryConstraintException AXL error code 5009: "Maximum AXL Memory Allocation Consumed. Please retry once requests in progress have completed."

Client response:

1. Client waits for the requests that are being processed to complete and then sends the request again.

Cisco recommends that applications wait 2 to 3 minutes before resubmitting the request.

2. Client logic must track the requests that fail and send them again.

Example 5: Concurrent data requests reach 16-MB limit

This example applies to all AXL methods.

This situation returns MemoryConstraintException AXL error code 5009: "Maximum AXL Memory Allocation Consumed. Please retry once requests in progress have completed."

Cisco recommends that applications wait 2 to 3 minutes after receiving this message before resubmitting the request.

Using <skip> and <first> Tags in List APIs

The new <skip> and <first> tags provide additional functionality when data is retrieved by using the List methods. If a List Response exceeds 8 MB, the client can fetch data in sets of rows by using a combination of these tags. These tags provide navigation functionality. Be aware that they are not mandatory and have no default values.

In addition,

Negative values for the <skip> or <first> tags cause a SQL syntax error.

If the <skip> tag is not mentioned or is empty and the <first> tag is not mentioned or is empty, the default query or full query that pertains to the List API executes.

If the <skip> tag is not mentioned or is empty and the <first> tag has some positive value (for example, "m"), a query that skips the "zero" row and fetches the first "m" rows executes.

If the <skip> tag and <first> tag value are both positive (for example, "n" and "m," respectively), a query that skips "n" rows and fetches "m" rows executes.

The <skip> tag can only be used when the <first> tag is speficied and the <searchLimit> tag value is zero.

The <first> tag can be used when the <searchLimit> tag value is zero.

Suggested Use of <skip> and <first> Tags in List APIs

If a client request exceeds 8 MB of data, the server responds: "Total rows matched: <Matched Rows>. Suggested row fetch: less than <Number of Rows>."

<Number of Rows> specifies the suggested number of rows that a single request can return to keep the data exchange under the 8-MB limit. Clients should use <Matched Rows> to determine the number of iterations that are required to retrieve the complete data set that a query tries to fetch.

Client response:

1. Client logic analyzes the server response and obtains the value of <Row Fetch>.

2. Client stores the <Row Fetch> value in a constant that depicts Row Fetch Step Size. For this example, the constant name specifies rowFetchStepSize.

3. Client executes a query for count(*) to obtain the number of rows that can be fetched from database. (Consider this step as required only if you are not using the exception to exit the loop.)

a. Client modifies the tags <first> and <skip> in every iteration of the row fetch.

b. The first iteration starts with <skip>0<skip> and <first> rowFetchStepSize</first>.

c. Subsequent row fetch iteration have <skip>"first" tag value from previous iteration</skip> and <first>previous iteration "first" tag value + rowFetchStepSize</first>.

4. Before each iteration, client checks for the condition <skip> tag value < count(*) value. If <skip> tag value >= count(*) value, this indicates that the iteration is trying to fetch more rows than the existing number of rows in the database. In this case, break from the loop. Otherwise, the SQL Error (No Current Row) occurs, which you can use to break from loop.

Sample Code for Use of <skip> and <first> Tags in List APIs

Example 1

If the recommended RowFetch is X = 100 for ListPhoneByName, the client should use this logic:

StepSize = RowFetch (X = 9999)
//Two variables to store the skip and first values.
Int skip = 0;
Int first = StepSize;
//start the iteration 
While (1) 
{
 Try {
//A function to Modify the values of <first> and <skip> in the request with variables 
values defined above
modifyRequest(FilePath);
//Sending the modified request
Response = SendExecuteSQLQuery (select SKIP <SkipCount> First <StepSize> * from endusers;) 
//Modify the variables
Skip+ = StepSize;
First+= StepSize;
Check for fault_message from reply
//An SQL Exception from server while trying to fetch rows greater than that present in 
database 
If(fault_message .contains("No Current Row Found")){
Break;
}
Else{
Continue the loop;
}
} /* end of while*/

Example 2

#Declare variable for first and skip
long skip = 0;
long first = suggestiveRowFetch;
#Calculate number of iterations required
float precision = totalRowFetch/suggestiveRowFetch;
calculate the decimal point of variable precision
if decimal point == 0;
no. Of Iterations = totalRowFetch/suggestiveRowFetch;
if decimal point <5 
no. Of Iterations = Math.round(totalRowFetch/suggestiveRowFetch)+1;
if decimal point >5
no. Of Iterations = Math.round(totalRowFetch/suggestiveRowFetch);
****Here (no. Of Iterations = 15)********
#iterator
int iLoop = 1;
 
   
while( iLoop <=no. Of Iterations){
 
   
#modify the values of first and skip in the query
String mdSQLQuery = modifySQLQuery(skip,first); /* Its like select skip 0 first 2000 * 
from device for first loop*/
#send the request and get response
response = sendRequest(mdSQLQuery);
#update the skip and first variables
skip+=suggestiveRowFetch;
first+=suggestiveRowFetch;
#check for response
if(response contains MemoryConstraintException){
#undo the variable modification to get  attributes (i.e skip and first) of the query , 
that failed with an exception. 
skip - =suggestiveRowFetch;
first - =suggestiveRowFetch;
wait till the requests in Progress Gets Processed;
continue the loop;
 
   
}
else{
iLoop++;
}
}

Sample Code for ExecuteSQLQuery

Example 1

To obtain the first X rows and then next X rows, a client should send queries as described in this section. For example, the client should use the following logic if the recommended RowFetch is X = 9999 for the query "select * from endusers;":

StepSize = RowFetch (X = 9999)
SkipCount = 0
 While (1) 
{
 Try {
Response = SendExecuteSQLQuery (select SKIP <SkipCount> First <StepSize> * from endusers;) 
RowsReturned = Rowcount (Response);
If RowsReturned < StepSize
    Break;  /* All the rows have been fetched*/
Else
    SkipCount = SkipCount + StepSize /*Increase the SkipCount to get the next set of 
rows*/
} 
Catch for any exception 
{
    Take appropriate action based on Exception
    Break;
}
} /* end of while*/

Example 2

#sql query to be executed
sqlQuery = "select * from device";
#send the query to server
response = sendRequest(sqlQuery);
#what is in response?
processResponse();
**** Response contains an Exception: "Query request too large.Suggestive row fetch 2000 
rows.Total row fetch 30000" ****
#Declare two variables 
long suggestiveRowFetch = 0; /*contains Suggestive RowFetch Count*/
long totalRowFetch = 0;      /*contains Total RowFetch*/ 
#fetch the two values and store it into variables.
parseExceptionMessage();

Testing Suggestions

This section provides tests that you can run to check various operations.

Testing ListPhoneByDescription and ListPhoneByName Methods

To test the ListPhoneByDescription and ListPhoneByName AXL methods, follow these steps:


Step 1 Populate database fields (<name>, <tkproduct>, <tkmodel>) for devices/phones to the maximum field size, which is 15 characters each.

Step 2 Populate the database with more than 60,000 devices.

Step 3 Execute the ListPhoneByDescription and ListPhoneByName AXL methods. The resulting data set has a response that is greater than 8 MB.


Expected Results: The interface returns "<API name> API request exceeds Threshold Limit. Total rows matched: <Matched Rows>. Suggested row fetch: less than <Number of Rows>." <API name> specifies the name of the API method.

Testing listDeviceByNameAndClass and listDeviceByServiceName Methods

To test the listDeviceByNameAndClass and listDeviceByServiceName AXL methods, follow these steps:


Step 1 Populate database fields (<name>, <tkproduct>, <tkmodel>) for devices/phones to the maximum field size, which is 15 characters each.

Step 2 Populate the database with more than 75,000 devices.

Step 3 Execute the listDeviceByNameAndClass and listDeviceByServiceName AXL methods. The resulting data set has a response that is greater than 8 MB.


Expected Results: The interface returns "<API name> API request exceeds Threshold Limit. Total rows matched: <Matched Rows>. Suggested row fetch: less than <Number of Rows>." <API name> specifies the name of the API method.

Testing the ExecuteSQLQuery AXL Method

To test the ExecuteSQLQuery AXL method, follow these steps:


Step 1 Populate database fields (<name>, <tkproduct>, <tkmodel>) for devices/phones to the maximum field size, which is 15 characters each.

Step 2 Create a SQL Select statement that retrieves this data.

Step 3 When the exception occurs, pick up the recommended Row Fetch Count and send the modified executeSQLQuery (in loop) by using the recommended row fetch count.


Expected Results: Demonstrate that Row Fetch Count logic works and, at the end loop, client can retrieve the entire set of required data from Cisco Unified Communications Manager.

Verifying That Tomcat Resources Are Protected

To verify that Tomcat resources are protected (Publisher server continues to operate under heavy AXL load):


Step 1 Write a script that generates a load on the AXL interface. Run executeSQLQuery to generate a response slightly less than 8 MB.

Step 2 Client runs this executeSQLQuery in a loop as soon as the transaction completes (both passed and failed transactions) for 1 hour. The client also notes the time that the request was sent, time that the response was received, and whether the response passed or failed.

Step 3 Create four instances of this script and make them run simultaneously against the same Cisco Unified Communications Manager Publisher.

Step 4 During the 1-hour load test, monitor the Tomcat JVM-related RTMT counters. In addition, use the Cisco Unified Communications Manager Administration interface to check whether you can list the devices on the system.

Step 5 At the end of the test, document the request and response times of the four clients on a timescale and note whether they succeeded or failed.


This analysis indicates whether the total responses that are processed by the AXL interface are within 16 MB. Every third concurrent request should have been rejected. By looking at the JVM on the Tomcat server that was available during the test, you can determine whether enough JVM exits to allow other applications to function properly.

Cisco Web Dialer API

The following sections describe updates to the Cisco Web Dialer API:

User Interface Enhancements

Hidden Proxy User Credentials

Redirector Throttling

Configuration Changes

Update to Endcall SOAP Method

Internet Explorer 7 Support

User Interface Enhancements

The following enhancements apply to the Make Call window:

WebDialer Preferences moved to the Make Call window and show consolidated information.

The MAC address displays only when a user is associated with multiple devices of the same type.

Partition information does not display unless duplicate DNs are configured on the same device.

The Calling Line option displays only when the device has multiple lines.

The Extension Mobility option displays only when this feature is enabled for the user.

The following enhancements apply to the Hang Up window:

The Destination User Name displays if it is available.

Partition information does not display.

Hidden Proxy User Credentials

Credentials no longer display in clear text in a URL. For example, a URL that displayed as follows in previous versions

https://wdserver.com/webdialer/Webdialer?cmd=doSetProfile&destination=&loc=en-us&red=null&uid=wd&pwd=xyz

now displays as

https://wdserver.com/webdialer/Webdialer

As a result, developers who use the browser interface should use the HTTP POST method to pass the parameters. For example, this approach reduces the delay when Web Dialer converts GET parameters to POST:

<FORM action="https://42.88.86.1/webdialer/Webdialer" method="post">
    <P>
    <INPUT type="hidden" name="destination" value="+666">
    <INPUT type="submit" value="Send"> 
    </P>
 </FORM> 

Redirector Throttling

Redirector throttling supports up to 8 sessions/requests per second. The system throws the following error if it exceeds the throttle:

HTTP Status 503 - Service temporarily unavailable, please try again later

Configuration Changes

The following configuration changes occurred:

List of Web Dialers setting displays on the Application server window in Cisco Unified Communications Manager Administration.

Existing settings migrate automatically during an upgrade.

No restriction exists on the number of Cisco Web Dialer servers that you can add.

You can easily associate Cisco Web Dialers servers with Redirectors. To do so, take the following actions in the Application Server Configuration window in Cisco Unified Communications Manager Administration:

1. In the Hostname or IP Address field, enter the host name or the IP address of the Cisco Web Dialer Server. Include the port number, if applicable.

2. Assign the Cisco Web Dialer server to a particular Redirector Node. Choose Use None for a cluster-wide setting.

Update to Endcall SOAP Method

The SOAP method Endcall update means that it no longer drops all calls on a device. Endcall now ends an active call, but not a call on hold.

Internet Explorer 7 Support

When you exit Cisco Web Dialer when you run it with Internet Explorer 7, the pop-up window that prompts for confirmation no longer displays. This change does not affect the programming interface.

Cisco Unified IP Phones

This section provides the following information:

Barge Tone Enhancements

Busy Lamp Field (BLF) Enhancements

Cisco Unified IP Phone Expansion Modules 7915 and 7916

Cisco Unified IP Phone Support HTTPS

Hold Status

Line Select

Missed Calls

Personal Directory and Fast Dial Service

Restrict Unconfigured Phone Registration

Web Dialer Enhancements

See Table 7 for a listing of features and supported phone models.

Barge Tone Enhancements

The Party Entrance Tone configuration is available as a per-line setting, in addition to a service parameter setting for Cisco Unified CM administrators. The default value for the line setting specifies the service parameter setting. Because the Party Entrance Tone is configurable on a per-line basis, it is possible for one caller to hear a tone when he/she creates a conference, but if another caller has Party Entrance Tone set to No, then they do not hear the tone when that he/she creates another conference.

The Party Entrance Tone setting gets applied to Barge, cBarge, Join, Ad-hoc, and Meet Me conferences in the same manner as before.

Barge and cBarge support the interaction with Private Line Automatic Ringdown (PLAR). When a shared line has PLAR configured, a user can Barge or cBarge into a call that is connected on the shared PLAR line.

These Barge Tone enhancements gets supported on the following phones that are running SIP and SCCP:

Cisco Unified IP Phone 7975G

Cisco Unified IP Phone 7971G-GE

Cisco Unified IP Phone 7970G

Cisco Unified IP Phone 7965G

Cisco Unified IP Phone 7962G

Cisco Unified IP Phone 7961G

Cisco Unified IP Phone 7961G-GE

Cisco Unified IP Phone 7945G

Cisco Unified IP Phone 7942G

Cisco Unified IP Phone 7941G

Cisco Unified IP Phone 7941G-GE

Cisco Unified IP Phone 7931G (SCCP only)

Cisco Unified IP Phone 7911G

Cisco Unified IP Phone 7906G

Where to Find More Information

Cisco Unified IP Phone Guide

Busy Lamp Field (BLF) Enhancements

Cisco Unified Communications Manager 6.1(3x) introduces the following enhancements for the Busy Lamp Field (BLF) feature:

New "BLF alerting" state—If configured, a new BLF line state, "BLF alerting," notifies the monitoring phone user that the monitored line is in an Alerting state (ringing). An animated icon, LED appearance, and optional tone indicate BLF alerting.

New BLF Pickup action—If BLF alerting is configured and a call is ringing on the monitored phone, the monitoring user can press the BLF pickup button to pick up the call.

These BLF enhancements get supported on the following phones that are running SCCP:

Cisco Unified IP Phone 7975G

Cisco Unified IP Phone 7971G-GE

Cisco Unified IP Phone 7970G

Cisco Unified IP Phone 7965G

Cisco Unified IP Phone 7962G

Cisco Unified IP Phone 7961G

Cisco Unified IP Phone 7961G-GE

Cisco Unified IP Phone 7945G

Cisco Unified IP Phone 7942G

Cisco Unified IP Phone 7941G

Cisco Unified IP Phone 7941G-GE

Cisco Unified IP Phone 7931G

Where to Find More Information

Cisco Unified IP Phone Guide

Cisco Unified IP Phone Administration Guide

Cisco Unified IP Phone Expansion Modules 7915 and 7916

The Cisco Unified IP Phone Expansion Module 7915 (grayscale display) and Cisco Unified IP Phone Expansion Module 7916 (color display) attach to your Cisco Unified IP Phone 7962G, 7965G, or 7975G (SCCP or SIP). Each expansion module adds up to 24 extra line appearances or programmable buttons to your phone. You can attach up to two expansion modules to your Cisco Unified IP Phone for a total of 48 extra line appearances or programmable buttons.


Note If the phone is running SCCP, you can only configure a maximum of 42 lines on your phone. For example, if you configure two 24-line Cisco Unified IP Phone Expansion Modules on a Cisco Unified IP Phone, only the first 42 lines will be available for use, including the first 6 or 8 lines on the Cisco Unified IP Phone.


Where to Find More Information

Cisco Unified IP Phone Expansion 7915 Phone Guide

Cisco Unified IP Phone Expansion 7916 Phone Guide

Cisco Unified IP Phone Support HTTPS

Cisco Unified IP Phones can securely access the web with the use of a phone trust store called "phone-trust." Administrators can upload certificates to a phone-trust store by using the Cisco Unified Communications Manager Operating System GUI. The Cisco Unified IP Phone will display a menu option called "Application Server" for each phone-trust store whose certificates have been uploaded into Cisco Unified OS Administration and later downloaded into the Cisco Unified IP Phone CTL file.

The phone-trust certificates and secure HTTPS web access get supported on the following phones that are running SCCP and SIP:

Cisco Unified IP Phone 7906G

Cisco Unified IP Phone 7911G

Cisco Unified IP Phone 7931G (SCCP only)

Cisco Unified IP Phone 7941G

Cisco Unified IP Phone 7942G

Cisco Unified IP Phone 7945G

Cisco Unified IP Phone 7961G

Cisco Unified IP Phone 7962G

Cisco Unified IP Phone 7965G

Cisco Unified IP Phone 7970G

Cisco Unified IP Phone 7971G

Cisco Unified IP Phone 7975G

Where to Find More Information

Cisco Unified IP Phone Administration Guide

Cisco Unified Communications Operating System Administration Guide

Cisco Unified Communication Manager Security Guide

Hold Status

Cisco Unified Communications Manager 6.1(3x) introduces the following enhancements to hold status:

The Hold Status feature allows phones with a shared line to distinguish whether the local user placed the call on hold or a remote (shared line) user placed the call on hold.

If two phone users share a line and one user places a call on hold, that user phone displays the local hold icon while the other user phone displays the remote hold icon. In addition, on the Cisco Unified IP Phone 7906G and 7911G, the hold button shows solid red on the local and remote phone. On all other supported phones, the local phone LED flashes green and the remote phone user LED flashes green.

The hold status enhancement gets supported on the following phones that are running SCCP and SIP:

Cisco Unified IP Phone 7906G

Cisco Unified IP Phone 7911G

Cisco Unified IP Phone 7931G (SCCP only)

Cisco Unified IP Phone 7941G/GE

Cisco Unified IP Phone 7942G

Cisco Unified IP Phone 7945G

Cisco Unified IP Phone 7961G/GE

Cisco Unified IP Phone 7962G

Cisco Unified IP Phone 7965G

Cisco Unified IP Phone 7970G-GE

Cisco Unified IP Phone 7971G-GE

Cisco Unified IP Phone 7975G

Where to Find More Information

Cisco Unified IP Phone Guide

Cisco Unified IP Phone Administration Guide

Line Select

Cisco Unified Communications Manager 6.1(3x) introduces settings to determine whether the primary line is automatically selected when a call is answered, or when the Messages button is pressed. Be aware that these settings can be made for all phones in the system, or for a single phone.

Line Select: If this setting is disabled (default), the ringing line gets selected. When enabled, the primary line gets picked up even if a call is ringing on another line. The user must manually select the other line.

Line Select for Voice Messages: When this setting is disabled (default), pressing the Messages button selects the line that has a voice message. If more than one line has a voice message, the first available line gets selected. When this setting is enabled, the primary line always gets used to retrieve voice messages.


Note Be aware that the primary line settings are also available for phones that are using extension mobility.


These enhancements are supported on the following SIP and SCCP phones:

Cisco Unified IP Phone 7975G

Cisco Unified IP Phone 7971G-GE

Cisco Unified IP Phone 7970G

Cisco Unified IP Phone 7965G

Cisco Unified IP Phone 7962G

Cisco Unified IP Phone 7961G

Cisco Unified IP Phone 7961G-GE

Cisco Unified IP Phone 7945G

Cisco Unified IP Phone 7942G

Cisco Unified IP Phone 7941G

Cisco Unified IP Phone 7941G-GE

Cisco Unified IP Phone 7931G (SCCP only)

Where to Find More Information

Cisco Unified IP Phone Guide

Cisco Unified IP Phone Administration Guide

Cisco Unified Communications Manager Administration Guide

Missed Calls

The missed calls feature allows the phone administrator to specify whether missed calls will get logged in the missed calls directory for a given line appearance. The following properties apply to the missed calls feature:

The line can represent a directory number or shared line. The default behavior logs all missed calls on all lines.

Missed call logging operates on a line basis. The line can represent a directory number or a shared line.

If the phone administrator configures a line appearance (share or non-shared), so missed calls do not get logged, calls to that line never get logged in the missed call log directory, even if the calls eventually get forwarded due to no answer.

If more than one line key gets configured on a phone, logging missed calls depends on the missed call log setting for each line.

Missed call logging gets controlled by an on/off configuration parameter that is sent to the phone in the configuration file.

The Missed Calls Log configuration does not affect any existing or previous call log items.

Calls on lines that are not logged do not affect the New Missed Call status message.

If the phone administrator turns off the missed calls feature on the configured line appearance, the missed calls do not get listed in the missed call history on that line appearance.

In addition to these properties, the following properties continue to apply all calls:

All calls that are received on a phone appear in the Received Calls log, regardless of the line on which they were received.

All calls that are made from a phone appear in the Placed Calls log, regardless of whether they were placed from a shared or primary line.

The missed calls feature gets supported on the following phones that are running SCCP and SIP:

Cisco Unified IP Phone 7906G

Cisco Unified IP Phone 7911G

Cisco Unified IP Phone 7931G (SCCP only)

Cisco Unified IP Phone 7941G/GE

Cisco Unified IP Phone 7942G

Cisco Unified IP Phone 7945G

Cisco Unified IP Phone 7961G/GE

Cisco Unified IP Phone 7962G

Cisco Unified IP Phone 7965G

Cisco Unified IP Phone 7970G-GE

Cisco Unified IP Phone 7971G-GE

Cisco Unified IP Phone 7975G

Where to Find More Information

Cisco Unified IP Phone Guide

Cisco Unified IP Phone Administration Guide

Personal Directory and Fast Dial Service

Administrators can set up a service URL that allows users to access their Fast Dials and PAB as services without having to authenticate each time:

The administrator modifies a phone button template to associate a service URL and then assigns the phone button template to the user phone.

In Cisco Unified CM User Options, the user assigns the service URL to an existing line button on the phone. The user can then press the line button to access the PAB or Fast Dials without having to authenticate.

The personal directory and fast dial service get supported on the following phones that are running SCCP and SIP:

Cisco Unified IP Phone 7906G

Cisco Unified IP Phone 7911G

Cisco Unified IP Phone 7931G (SCCP only)

Cisco Unified IP Phone 7941G/GE

Cisco Unified IP Phone 7942G

Cisco Unified IP Phone 7945G

Cisco Unified IP Phone 7961G/GE

Cisco Unified IP Phone 7962G

Cisco Unified IP Phone 7965G

Cisco Unified IP Phone 7970G-GE

Cisco Unified IP Phone 7971G-GE

Cisco Unified IP Phone 7975G

Where to Find More Information

Cisco Unified IP Phone Guide

Cisco Unified IP Phone Administration Guide

Restrict Unconfigured Phone Registration

Prior to Cisco Unified Communications Manager 6.1(3x), if a Cisco Unified IP Phone had not been added to the Cisco Unified Communications Manager database and did not have auto-registration enabled, the phone would repeatedly attempt to register (unsuccessfully) with Cisco Unified Communications Manager, thus continually notifying Cisco Unified Communications Manager with these repeated registration requests.

With Cisco Unified Communications Manager 6.1(3x), if auto-registration is not enabled, and the phone has not been added to the Cisco Unified Communications Manager database, the phone will not attempt to register with Cisco Unified Communications Manager. The phone will continue to display the "Configuring IP" message until auto-registration has been enabled, or until the phone has been added to the Cisco Unified Communications Manager database.

The registration behavior is supported on the following phones and devices that are running SCCP and SIP:

Cisco Unified IP Phone 7906G

Cisco Unified IP Phone 7911G

Cisco Unified IP Phone 7931G (SCCP only)

Cisco Unified IP Phone 7941G

Cisco Unified IP Phone 7942G

Cisco Unified IP Phone 7945G

Cisco Unified IP Phone 7961G

Cisco Unified IP Phone 7962G

Cisco Unified IP Phone 7965G

Cisco Unified IP Phone 7970G

Cisco Unified IP Phone 7971G

Cisco Unified IP Phone 7975G

Cisco Analog Telephone Adapter

VG248 Gateways

Where to Find More Information

Cisco Unified IP Phone Administration Guide

Cisco Unified Communications Manager Administration Guide

Web Dialer Enhancements

Cisco Unified Communications Manager 6.1(3x) supports the following Web Dialer enhancements:

Changing the WebDialer database location—The list of WebDialers moves from the Service Parameter Configuration window in Cisco Unified Communications Manager to be node-specific on the Application Server Configuration window. The Application Server Configuration window gets updated to enable sorting by application server type and node.

Preferred Device menu name change—On the Cisco WebDialer Make Call window , the "Use permanent device" changes to display "Use preferred device." When only one preferred device is available, the MAC address will not display in the menu. MAC addresses will only display if two or more devices of the same type are assigned to the user.

Merging the Preferences and Make Call windows together—The Cisco WebDialer Preferences window options are now available from the Cisco WebDialer Make Call window.

Integration with Extension Mobility—If the user has an Extension Mobility profile, an option labeled "Use my Extension Mobility logged in device" will be available from the Preferred Device menu.

Dialog changes for Hang-Up UI—Changes the text on the Hang-Up UI to say

Calling <Username if available> at <dial-out number>

If authorization codes are required, enter them now

The Web Dialer enhancements get supported on the following phones that are running SCCP and SIP:

Cisco Unified IP Phone 7906G

Cisco Unified IP Phone 7911G

Cisco Unified IP Phone 7931G (SCCP only)

Cisco Unified IP Phone 7941G/GE

Cisco Unified IP Phone 7942G

Cisco Unified IP Phone 7945G

Cisco Unified IP Phone 7961G/GE

Cisco Unified IP Phone 7962G

Cisco Unified IP Phone 7965G

Cisco Unified IP Phone 7970G-GE

Cisco Unified IP Phone 7971G-GE

Cisco Unified IP Phone 7975G

Where to Find More Information

Cisco Unified IP Phone Guide

Table 7 lists Cisco Unified IP Phones that support the Cisco Unified Communications Manager 6.1(3x) features.

Table 7 Cisco Unified IP Phone Support for Cisco Unified Communications Manager 6.1(3x) Features 

Cisco Unified Communications Manager 6.1(3x) Feature
Cisco Unified IP Phone Support
For more information, see

Barge Tone Enhancements

SCCP and SIP
7975G
7971G-GE
7970G
7965G
7962G
7961G
7961G-GE
7945G
7942G
7941G
7941G-GE
7911G
7906G

SCCP only
7931G

Barge Tone Enhancements

Busy Lamp Field (BLF) Enhancements

SCCP and SIP
7975G
7971G-GE
7970G
7965G
7962G
7961G
7961G-GE
7945G
7942G
7941G
7941G-GE
7911G
7906G

SCCP only
7931G

Busy Lamp Field (BLF) Enhancements

Cisco Unified IP Phone Expansion Modules 7915 and 7916

SCCP and SIP:
7962G
7965G
7975G

Cisco Unified IP Phone Expansion Modules 7915 and 7916

Cisco Unified IP Phone Support HTTPS

SCCP and SIP
7975G
7971G-GE
7970G
7965G
7962G
7961G
7961G-GE
7945G
7942G
7941G
7941G-GE
7911G
7906G

SCCP only
7931G

Cisco Unified IP Phone Support HTTPS

Hold Status

SCCP and SIP
7975G
7971G-GE
7970G
7965G
7962G
7961G
7961G-GE
7945G
7942G
7941G
7941G-GE
7911G
7906G

SCCP only
7931G

Hold Status

Line Select

SCCP and SIP
7975G
7971G-GE
7970G
7965G
7962G
7961G
7961G-GE
7945G
7942G
7941G
7941G-GE
7911G
7906G

SCCP only
7931G

Line Select

Missed Calls

SCCP and SIP
7975G
7971G-GE
7970G
7965G
7962G
7961G
7961G-GE
7945G
7942G
7941G
7941G-GE
7911G
7906G

SCCP only
7931G

Missed Calls

Personal Directory and Fast Dial Service

SCCP and SIP
7975G
7971G-GE
7970G
7965G
7962G
7961G
7961G-GE
7945G
7942G
7941G
7941G-GE
7911G
7906G

SCCP only
7931G

Personal Directory and Fast Dial Service

Restrict Unconfigured Phone Registration

SCCP and SIP
7975G
7971G-GE
7970G
7965G
7962G
7961G
7961G-GE
7945G
7942G
7941G
7941G-GE
7911G
7906G

SCCP only
7931G

Restrict Unconfigured Phone Registration

WebDialer Enhancements

SCCP and SIP
7975G
7971G-GE
7970G
7965G
7962G
7961G
7961G-GE
7945G
7942G
7941G
7941G-GE
7911G
7906G

SCCP only
7931G

Web Dialer Enhancements


Cisco Unified CM User Options

See the following sections for enhancements to the Cisco Unified CM User Options:

Logging Missed Calls For Shared Lines

Web Dialer Enhancements

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(3x) 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 Caveat as of February 12, 2009" section describes possible unexpected behaviors, supported by component, in Cisco Unified Communications Manager Release 6.1(3x).


Tip For more information about an individual defect, click the associated Identifier in "Open Caveat as of February 12, 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)


Note Because defect status continually changes, be aware that Open Caveat as of February 12, 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 Caveat as of February 12, 2009

The following list contains the caveat that was open on February 12, 2009.

------------------------------------------------------------------------------

Identifier: CSCsu54695

Component : media

Headline : IPVMS generates syslog messages.

------------------------------------------------------------------------------

Documentation Updates

The Updates to Cisco Unified Communications Manager 6.1(1) Documentation document provides information about documentation omissions, errors, or updates that are not included in the documentation that supports the Unified CM 6.1(1) release train.To obtain this document, go to the following URL:

http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/rel_notes/6_1_1/cucm-doc_updates-611.html.

Obtaining Documentation and Submitting a Service Request

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

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

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