Guest

Cisco Unified Communications Manager (CallManager)

Release Notes for Cisco Unified CallManager Release 5.0(4c)

  • Viewing Options

  • PDF (1.6 MB)
  • Feedback
Release Notes for Cisco Unified CallManager Release 5.0(4c)

Table Of Contents

Release Notes for Cisco Unified CallManager Release 5.0(4c)

Contents

Introduction

System Requirements

Supported Platforms

Determining the Software Version

Upgrading System Software

Related Documentation

Installation Notes

Installation on Cisco MCS Servers MCS-7825-H1, MCS-7825-H2

Upgrade During Install Fails

TFTP Crash During Upgrade

Installation on IBM 8491-G2U

Limitations and Restrictions

Important Notes

Considerations for LDAP Port Configuration

USB Key Halts Installation of Cisco Unified CallManager on 7845-H2 Server

Migration of Cisco Unified CallManager 5.0 Locales

Using Call Park

Failover Time Using UDP on SIP Phones

Premature Certificate Generation Prevents Immediate Service Activation After a Fresh Installation

SIP Trunk Configuration

Unplugging a USB Cable

Cisco MCS-7845H-2.4-EVV1 and Cisco MCS-7835H-2.4-EVV2 Server May Not Recognize the USB-to-Serial Cable

Configuring Regions (Region Relationship) for SIP Devices with the MTP Required Option Enabled

Installed Software Options

Stalled Upgrades

Registering Cisco Catalyst WS-X6608, WS-6624 Gateways, and Other Media Devices

Limiting the Number of Records in a BAT Transaction

Using T.38 with Cisco IP Voice Media Streaming Application Service

Using IPSEC Within the Nodes of a Cluster

SIP Third-Party Phones Support AAR Calling Search Space

Configuration Tips for TFTP Servers in a Centralized TFTP Setting

Using FTP Servers

Customizing a Background Image on Cisco Unified IP Phones

Upgrading from Cisco Unified CallManager Release 5.0(1) to Release 5.0(2)

Backing up Hard Drives by Pulling them out on a Cisco MCS 7845

CSCtj61834 MLPP Default Domain Name Displays MLPP ID Value

New and Changed Information in Cisco Unified CallManager 5.0(4a)

Registration of Cisco IP Communicator

Installation on Cisco MCS Servers MCS-7825-H1, MCS-7825-H2

Upgrade During Install

TFTP Crash During Upgrade

Installation on IBM 8491-G2U

New and Changed Information in Cisco Unified CallManager 5.0(4)

IPMA on the Cisco Unified IP Phone

Cisco Unified CallManager Attendant Console

Cisco Unified CallManager Administration Configuration Tips

Service Parameter Changes

Online Help for Cisco Unified CallManager Attendant Console

Where to Find More Information

Cisco Unified CallManager Administration

System Menu Changes

LDAP Menu Changes

Enterprise Parameter Changes

Cisco Unified CallManager Features

Licensing

Cisco Unified CallManager Serviceability

Real-Time Monitoring Tool

Security Feature Changes

New and Changed Information in Cisco Unified CallManager 5.0(3)

Cisco Announces New Servers and Appliances

Firewall Support for Attendant Console

New and Changed Information in Cisco Unified CallManager 5.0(2)

New and Changed Information in Cisco Unified CallManager 5.0(1)

Installation, Upgrade, Migration, and Disaster Recovery

Installation Overview

Software Upgrades

Data Migration Assistant (DMA)

Disaster Recovery Enhancements

Where to Find More Information

Cisco Unified Communications Operating System Administration

Overview

Browser Requirements

Platform Status and Configuration

Settings

Restart Options

Security Configuration

Software Upgrades

Services

Command Line Interface

Where to Find More Information

Cisco Unified CallManager Administration

General Administration Enhancements

Navigating to IP Telephony Applications Within Cisco Unified CallManager

Localizing Cisco Unified CallManager Administration

Configuring Servers

Publisher and Subscriber Name Changes

Media Resources

Migration Tips

General Changes Made to Multiple Windows

Line and Phone Configuration Improvements

System Menu Changes

Call Routing Menu Changes (formerly Route Plan Menu)

Media Resources Menu

Voice Mail Menu

Device Menu Changes

Application Menu Changes

User Management Menu

Bulk Administration Menu

Service Parameter Changes

Where to Find More Information

Cisco Unified CallManager Features

Call Forwarding Enhancements

Call Park

Call Pickup Group

CTI and CTI Super Provider

Dynamic Host Control Protocol (DHCP)

International Dial Plans

LDAP Directory Enhancements

Licensing

Personal Directory Enhancements

Phone NTP References for SIP Phones

Presence

Roles and User Groups

RSVP

Service Enhancements

SIP Line Side (Endpoints) Support

SIP Route Pattern

SIP Third-Party Phones

SIP Trunk Enhancements

TFTP Enhancements

URL Dialing

Video Telephony Enhancements

Voice Quality Metrics

Cisco Unified CallManager User Options Web Pages

Addition of the Cisco Personal Communications Assistant Layer

Redesigned User Interface

Where to Find More Information

Cisco Unified CallManager Applications

Cisco Call Back

Cisco Unified CallManager Attendant Console

Cisco Unified CallManager AutoAttendant

Cisco Unified CallManager Extension Mobility

Cisco Dialed Number Analyzer

Cisco Emergency Responder 1.3(1)

Cisco Unified CallManager Assistant

Cisco Unity Voice Messaging

Cisco Web Dialer

Client Matter Codes and Forced Application Codes

Multilevel Precedence and Preemption (MLPP)

Music On Hold

Quality Report Tool

Cisco Unified CallManager Bulk Administration Features

Installation Considerations

New and Changed Information for BAT

BAT Configuration Tips

GUI Changes

Serviceability Considerations

Security Considerations

BAT Performance

Cisco Unified CallManager Auto-Register Phone Tool Features

Installation Considerations

TAPS Configuration Tips

Serviceability Considerations

Security Considerations

Security Features

Cisco Unified CallManager Administration Configuration Tips

Where to Find More Information

New and Changed Information for Cisco Unified CallManager Serviceability

Serviceability Administration

Real-Time Monitoring Tool

Trace & Log Central

SysLog Viewer

CDR Analysis and Reporting (CAR)

Where to Find More Information

New and Changed Information for Cisco Unified IP Phones

Cisco Unified IP Phone Feature Differences by Protocol

Supported Cisco Unified IP Phones Using SIP

New Features Supported by Cisco Unified CallManager Release 5.0(2)

Feature Support Listed by Phone and Protocol

New and Changed Information for Third-Party API

Cisco Unified CallManager Developers Guide

CDR Definitions

Cisco Unified IP Phone Service Application Development Notes for Cisco Unified CallManager 5.0(2)

JTAPI Developers Guide

SCCP Messaging Guide

SIP Messaging Guide

TAPI Developers Guide

Caveats

Resolved Caveats

Using Bug Toolkit

Open Caveats

Troubleshooting

Documentation Updates

Errors

Description of the Reset Button

Description of the Cisco Unified IP Phone Proxy Server

Definition of Originating Codec and Destination Codec

Name Correction for Cisco Database Service

Using the Command Line Interface to Stop/Start Services

Guidelines for the Cisco Unified CallManager Application User

Enabling the Super Provider Feature for Cisco Unified CallManager Attendant Console

SIP Profile Configuration

Web Dialer Service Parameters

Viewing Field Descriptions and Help for Product-Specific Configuration

Cisco Extension Mobility

Cisco CAR Web Service/Cisco CAR Scheduler Service

Real-Time Monitoring Tool

Device Authentication Application User

Launching Cisco Unified CallManager Attendant Console

Changes

Phone Security Profile Configuration Window

Ethernet Settings

Command Line Interface

TFTP Server File Upload

Deleting Files on the Inactive Partition

Forced Shutdown

Network Failover

Utils Network Tracert Command

Performing a Software Upgrade

Data Migration Assistant Installation File

CTIManager Connection Security Flag

Gatekeeper-controlled Intercluster Trunk Registers Incorrectly with Gatekeeper

RSVP Agent Configuration with Transcoder

Path Replacement Calling Search Space Service Parameter

H.323 Information Settings on a H.323 Client

Cisco Web Dialer Does Not Close All Windows After Dialing

User With Extension Mobility Authorization by Proxy Fails to Log In and Log Out Other Users

VD-2005-12-KE

H323 Redirecting Number IE is sent in UUIE by Cisco Unified CallManager

Extension Mobility Configuration Step is Missing

TS-6671 - Enabling Autoregistration

Music On Hold Configuration

BU-6666 - Cisco Web Dialer Servlet Service Parameter

Support of Third-Party CSRs for External CAs

Perfmon Counter Name Changes

Omissions

Setting the Cisco Unified Communications Manager MTU Size

Automated Alternate Routing (AAR) Limitation with Remote Gateways

Cisco 28xx Voice Gateways and H.323

Malicious Call Identification Restrictions

Call Control for Attendant Console

Destination Address for SIP Trunk Configuration

Music On Hold

Resource Reservation Protocol (RSVP)

Installing Device Packs and Phone Firmware Loads

Saving and Uploading Third-Party Security Certificates

Accessing Cisco Security Agent (CSA) Logs

Changing IP Address on a Cisco Unified CallManager Node

Obtaining a License File

BAT SCCP to SIP Phone Migration for Cisco Unified IP Phones 7940 and 7960

Upgrading CTL Client and CTL Files After Upgrading to Version 5.x

Tool for Auto-Registered Phone Support (TAPS)

Using Third-Party Certificate Authority Certificates

SDI Trace Settings

TFTP

Disaster Recovery CLI Commands

Searching for a Device in RTMT with the Any Status Option

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

License Capabilities Assignment Configuration

Corrections

Servers That Support Cisco Unified CallManager 5.0(3)

Cisco Emergency Responder 1.3(1a)

Obtaining Documentation, Obtaining Support, and Security Guidelines

Cisco Product Security Overview

Reporting Security Problems in Cisco Products


Release Notes for Cisco Unified CallManager Release 5.0(4c)


Updated August 8, 2011

This release of Cisco Unified CallManager adds support for the Hewlett-Packard 7845-H2 server only. This release adds no new features and no defects are resolved.

One Important Note exists for this release, "USB Key Halts Installation of Cisco Unified CallManager on 7845-H2 Server" section.

One document omission exists for this release, "Automated Alternate Routing (AAR) Limitation with Remote Gateways" section


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


Before you install Cisco Unified CallManager, Cisco recommends that you review the "Installation Notes" section and the "Important Notes" section for information about issues that may affect your system.


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



Caution Be aware that Cisco Unified CallManager Release 5.0(4c) is not an upgrade of Cisco Unified CallManager Release 5.0(4x). If you have successfully installed Cisco Unified CallManager Release 5.0(4) on a cluster and have not experienced problems, continue using that release. If you begin to experience problems with a successfully installed Cisco Unified CallManager Release 5.0(4x) cluster, report the problems through normal channels.

If you experience problems during the installation of a Cisco Unified CallManager Release 5.0(4x) cluster, you should install Cisco Unified CallManager Release 5.0(4c) on that cluster.

Ensure that all nodes in a cluster run the same Cisco Unified CallManager.5.0(4) release. Do not install Cisco Unified CallManager Release 5.0(4c) and Cisco Unified CallManager Release 5.0(4a) on the same cluster.

Contents

These release notes discuss the following topics:

Introduction

System Requirements

Related Documentation

Installation Notes

Limitations and Restrictions

Important Notes

New and Changed Information in Cisco Unified CallManager 5.0(4a)

New and Changed Information in Cisco Unified CallManager 5.0(4)

New and Changed Information in Cisco Unified CallManager 5.0(3)

New and Changed Information in Cisco Unified CallManager 5.0(2)

New and Changed Information in Cisco Unified CallManager 5.0(1)

New and Changed Information in Cisco Unified CallManager 5.0(1)

Caveats

Troubleshooting

Documentation Updates

Obtaining Documentation, Obtaining Support, and Security Guidelines

Cisco Product Security Overview

Introduction

Cisco Unified CallManager, a network business communication system, provides high-quality telephony over IP networks. Cisco Unified CallManager enables the conversion of conventional, proprietary, circuit-switched PBXs to multiservice, open LAN systems.

System Requirements

Make sure that you install and configure Cisco Unified CallManager release 5.0(4c) on any cluster that contains a Hewlett-Packard 7845-H2 server.

Cisco Unified CallManager 5.0(x) requires a minimum of the following items on supported servers.

2 GB of memory

72 GB disk drive

2 GHz processor

Supported Platforms

To find which servers support Cisco CallManager 5.0 releases, refer to the Guide to Cisco CallManager Upgrades and Server Migrations at http://www.cisco.com/en/US/partner/products/hw/voiceapp/ps378/prod_brochure_list.html

Determining the Software Version

To determine the software version of Cisco Unified CallManager, open Cisco Unified CallManager Administration. The following information displays:

Cisco Unified CallManager System version

Cisco Unified CallManager Administration version

Cisco recommends that you connect each Cisco Unified CallManager node to an Uninterruptible Power Supply (UPS) to provide backup power and protect your system against a power failure.

Upgrading System Software

You can access the latest software upgrades for Cisco Unified CallManager 5.0 on Cisco.com. Table 1 lists the URLs from which you download the software.


Related Documentation

The documentation that supports Cisco Unified CallManager Release 5.0(4x) comprises existing release 5.0(4) documentation that is listed in the Cisco Unified CallManager Release Documentation Guide.

Installation Notes

The following installation notes apply to Cisco Unified CallManager Release 5.0(4x):

Installation on Cisco MCS Servers MCS-7825-H1, MCS-7825-H2

Upgrade During Install Fails

TFTP Crash During Upgrade

Installation on IBM 8491-G2U

Installation on Cisco MCS Servers MCS-7825-H1, MCS-7825-H2

When you perform a fresh installation of Cisco Unified CallManager Release 5.0(4) on Cisco MCS of type MCS-7825-H1 or MCS-7825-H2 by using the Cisco Unified CallManager 5.0(4) Installation DVD, the installation process stops before completion and displays the following message: "Waiting for RAID to BUILD...".

Cisco Unified CallManager Release 5.0(4a) fixed this defect.

For more information about this issue, see the "Resolved Caveats" section.

Upgrade During Install Fails

When you perform an upgrade during install using the software that is contained on the Cisco Unified CallManager Release 5.0(4) installation disc with the latest service release, the installation fails.

Cisco Unified CallManager Release 5.0(4a) resolved this problem.

TFTP Crash During Upgrade

When you perform an upgrade to Cisco Unified CallManager Release 5.0(4), TFTP crashes. This problem resulted because of an imperfection in the TFTP code. Cisco Unified CallManager Release 5.0(4a) alters the code, and TFTP no longer crashes.

Installation on IBM 8491-G2U

When you perform a fresh installation of Cisco Unified CallManager Release 5.0(3a) on an IBM 8491-G2U by using the Cisco Unified CallManager 5.0(3a) Installation DVD, the installation process stops before completion and displays the following message: "HW type [Vendor/Product] NOT SUPPORTED...". The IBM 8491-G2 machines get supported, and Cisco Unified CallManager Release 5.0(4a) successfully resolved in this defect.

For More Information

For complete installation information, refer to the following documents:

Installing Cisco Unified CallManager Release 5.0(4)

Upgrading Cisco Unified CallManager Release 5.0(4)

Data Migration Assistant Administration Guide, Version 5.0(2a))

Limitations and Restrictions

You can find software release versions of both Cisco and third-party components that are used in the Cisco Unified Communications Release 5.0(2) at http://www.cisco.com/univercd/cc/td/doc/systems/unified/uc502/relnotes/rnipt502.htm#wp1355580

You can also find which application versions and third-party components are compatible with Contact Center products by referring to the System Release Notes for Contact Center: Cisco Unified Communications Release 5.0 at

http://www.cisco.com/univercd/cc/td/doc/systems/unified/uc502/relnotes/rnipc502.htm#wp1304584


Note Be aware that the release of Cisco IP telephony products does not always coincide with Cisco Unified CallManager releases. If a product does not meet the compatibility testing requirements with Cisco Unified CallManager, you need to wait until a compatible version of the product becomes available before you can upgrade to Cisco Unified CallManager Release 5.0(4c). 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


Caution Be aware that Cisco Unified CallManager Release 5.0(4c) does not constitute an upgrade of Cisco Unified CallManager Release 5.0(4x). If you have successfully installed Cisco Unified CallManager Release 5.0(4x) on a cluster and have not experienced problems, continue using that release. If you begin to experience problems with a successfully installed Cisco Unified CallManager Release 5.0(4x) cluster, report the problems through normal channels.

If you experience problems during the installation of a Cisco Unified CallManager Release 5.0(4x) cluster, you should install Cisco Unified CallManager Release 5.0(4c) on that cluster.

All nodes in a cluster must run the same Cisco Unified CallManager.5.0(4) release. Do not install Cisco Unified CallManager Release 5.0(4) and Cisco Unified CallManager Release 5.0(4a) or 5.0(4c) on the same cluster.

If you want to add or replace a node in a cluster that is running Cisco Unified CallManager Release 5.0(4) or 5.0(4) ES, install Cisco Unified CallManager Release 5.0(4c) on the new or replaced node and upgrade the entire cluster to Cisco Unified CallManager Release 5.0(4) ES.


The following section contains important information that may have been unavailable upon the initial release of documentation for Cisco Unified CallManager release 5.0(4x).

Important Note for Cisco Unified CallManager Release 5.0(4c)

USB Key Halts Installation of Cisco Unified CallManager on 7845-H2 Server

Important Notes for Cisco Unified CallManager Releases 5.0(4x)

Migration of Cisco Unified CallManager 5.0 Locales

Using Call Park

Failover Time Using UDP on SIP Phones

Premature Certificate Generation Prevents Immediate Service Activation After a Fresh Installation

SIP Trunk Configuration

Unplugging a USB Cable

Cisco MCS-7845H-2.4-EVV1 and Cisco MCS-7835H-2.4-EVV2 Server May Not Recognize the USB-to-Serial Cable

Configuring Regions (Region Relationship) for SIP Devices with the MTP Required Option Enabled

Installed Software Options

Stalled Upgrades

Registering Cisco Catalyst WS-X6608, WS-6624 Gateways, and Other Media Devices

Limiting the Number of Records in a BAT Transaction

Using T.38 with Cisco IP Voice Media Streaming Application Service

Using IPSEC Within the Nodes of a Cluster

SIP Third-Party Phones Support AAR Calling Search Space

Configuration Tips for TFTP Servers in a Centralized TFTP Setting

Using FTP Servers

Customizing a Background Image on Cisco Unified IP Phones

CSCtj61834 MLPP Default Domain Name Displays MLPP ID Value

Considerations for LDAP Port Configuration

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


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


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

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

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

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

3268—When SSL is not required.

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

USB Key Halts Installation of Cisco Unified CallManager on 7845-H2 Server

During installation of Cisco Unified CallManager Release 5.0(4c) with Answer File Generator stored on USB, you may get prompted for a media check and asked if the harddrive can be overwritten. Since the harddrive has nothing on it, you give permission and the configuration information gets picked up from the USB Answer File Generator. The installation begins and then the DVD gets ejected automatically.

The server should restart automatically, but it gets halted with this error:

Attempting boot from CD-ROM.
Attempting boot from USB drive key (c)
Disk error. press any key to restart. 

At this point, remove the USB key and manually restart the server and the installation completes successfully.

Migration of Cisco Unified CallManager 5.0 Locales

If you are upgrading Cisco Unified CallManager 5.0(1) to Cisco Unified CallManager 5.0(4a) and one or more locales other than the default English (United States) are installed on your system, you must install Cisco Unified CallManager Locale Installer 5.0.1.3-1, which replaces ALL non-default locales, PRIOR to upgrading each Cisco Unified CallManager server.

If you are upgrading Cisco Unified CallManager 5.0(2) to Cisco Unified CallManager 5.0(4a) and one or more locales other than the default English (United States) are installed on your system, you must install Cisco Unified CallManager Locale Installer 5.0.2.3-1, which replaces ALL non-default locales, PRIOR to upgrading each Cisco Unified CallManager server.

Access Cisco Unified CallManager Locale Installer 5.0 Downloads at the following URL:

http://www.cisco.com/cgi-bin/tablebuild.pl/callmgr-locale-50

Related defect ID:

CSCsb56021 Migration of Cisco Unified CallManager 5.0 Locales

Using Call Park

Consider the following information before you configure the call park feature in Cisco Unified CallManager:

Be sure to use Cisco Unified CallManager Dialed Number Analyzer tool to validate the call park number or ranges that you entered. Cisco Unified CallManager Administration does not validate the call numbers or range that you use to configure call park. Cisco Unified CallManager Dialed Number Analyzer can identify invalid numbers or ranges and potential range overlaps.

For more information, refer to CSCsc77968, CSCsc78450, and CSCsc78720.

Cisco Unified CallManager Administration does not check that the value that is entered for Call Park Reversion Timer is less than the value that is entered for the Call Park Display Timer. If you entered a Call Park Reversion Timer value that is less than the Call Park Display Timer, call park numbers will not display on the phone.

For more information, refer to CSCsc76797 and CSCsc76702.

When a user parks a call across a QSIG intercluster trunk or a QSIG gateway trunk, the caller who has been parked (the parkee) does not see the To parked number message. The phone continues to display the original connected number. The call has been parked, and the user who parked the call can retrieve it. When the call is retrieved from the parked state, the call continues, but the caller who was parked does not see the newly connected number.

Failover Time Using UDP on SIP Phones

This condition affects Cisco Unified IP Phones 7970G, 7971G-GE, 7941G, 7961G, 7941G-GE, 7961G-GE, and 7911that are using SIP.

When UDP is selected as the transport protocol, phones fail to connect to a Cisco Unified CallManager node after a failover. This occurs because phone failover time takes more than the 120 seconds that the phone waits to detect a Cisco Unified CallManager failure status. This condition affects Cisco Unified IP Phones 7970G, 7971G-GE, 7941G, 7961G, 7941G-GE, 7961G-GE, and 7911 that are using SIP. The workaround requires that you to configure the SIP phones to use the TCP protocol in the SIP Phone Security Profile.

Premature Certificate Generation Prevents Immediate Service Activation After a Fresh Installation

When you install Cisco Unified CallManager 5.0 on subscriber (subsequent) nodes and the time zone is a time zone that is ahead of the Pacific time zone (Mountain Time (GMT-8) through Auckland (GMT+12) time zone), the Tomcat certificate that is generated does not take effect until the time in the future equals to the number of hours that your time zone is ahead of the Pacific time zone. The certificates become valid only after this number of hours elapses and it affects all time zones that are ahead of the Pacific time zone. To enable immediate service activation on a subscriber, regenerate the certificates for your current time zone by performing the following steps:

Log in to Cisco Unified Communications Platform Administration on the subscriber node.

Choose Security > Certificate Mgmt > Delete/Regenerate Certificate in Cisco Unified Communications Platform Administration.

Activate the services on the subscriber node.

For more information, refer to CSCsc85288.

SIP Trunk Configuration

Consider the following restrictions when you configure SIP trunks on Cisco Unified CallManager because Cisco Unified CallManager does not perform validation on your configuration:

Cisco Unified CallManager does not support outbound MWI notification on a SIP trunk that is assigned to a Route List or a Route Group. If you want Cisco Unified CallManager to send outbound MWI notification on a SIP trunk, you must assign the SIP trunk directly to a route pattern.

Each SIP trunk must include a unique SIP routing configuration for SIP routing to work. Cisco Unified CallManager uses a combination of information from incoming SIP messages to route the SIP message to the correct SIP trunk. Consider SIP trunk routing configuration as unique if the following statements apply:

No other trunk gets configured with the same values for the Incoming Transport Protocol, Incoming Port, and Destination Address fields.

No other trunk gets configured with Transport Layer Security (TLS) selected as the Incoming Transport Protocol and the same values in the Incoming Port and X.509 Subject Name fields. The X.509 Subject Name parameter can comprise a list of names.

The Incoming Transport Protocol, Incoming Port, and X.509 Subject Name parameters get configured in SIP Trunk Security Profile Configuration in Cisco Unified CallManager Administration. Choose System > Security Profile > SIP Trunk Security Profile Configuration. This menu option yields the Find and List SIP Trunk Security Profile window. Use this window to search for existing SIP Trunk Security Profiles or click Add New to add a new profile.

The Destination Address and the selected SIP Trunk Security profile gets configured on the Trunk Configuration window in Cisco Unified CallManager. Choose Device-> Trunk. This menu option yields the Find and List Trunks window. Use this window to search for existing Trunks or click Add New to add a new trunk and choose SIP trunk as the Trunk Type.

The following example shows a valid configuration:

Trunk#1: Incoming Transport Protocol=TCP/UDP, Incoming Port=5060, Destination 
Address=10.10.10.1
Trunk#2: Incoming Transport Protocol=TCP/UDP, Incoming Port=5060, Destination 
Address=10.10.10.2
Trunk#3: Incoming Transport Protocol=TCP/UDP, Incoming Port=5080, Destination 
Address=10.10.10.1
Trunk#4: Incoming Transport Protocol=TLS, Incoming Port=5061, X.509 Subject 
Name=my_ccm1, my_ccm2
Trunk#5: Incoming Transport Protocol=TLS, Incoming Port=5061, X.509 Subject 
Name=my_ccm3
Trunk#6: Incoming Transport Protocol=TLS, Incoming Port=5081, X.509 Subject 
Name=my_ccm_1

The following example shows an invalid configuration:

Trunk#1: Incoming Transport Protocol=TCP/UDP, Incoming Port=5060, Destination 
Address=10.10.10.1
Trunk#2: Incoming Transport Protocol=TCP/UDP, Incoming Port=5060, Destination 
Address=10.10.10.1 
Trunk#3: Incoming Transport Protocol=TLS, Incoming Port=5061, X.509 Subject 
Name=my_ccm1, my_ccm2
Trunk#4: Incoming Transport Protocol=TLS, Incoming Port=5081, X.509 Subject 
Name=my_ccm2
Trunk#5: Incoming Transport Protocol=TLS, Incoming Port=5061, X.509 Subject 
Name=my_ccm2 
Trunk#6: Incoming Transport Protocol=TLS, Incoming Port=5081, X.509 Subject 
Name=my_ccm2 

Trunk #2 conflicts with Trunk #1 because the protocol, incoming port, and destination address are identical.

Trunk #5 conflicts with Trunk #3 because the protocol and incoming port are identical, and both trunks include my_ccm2 in their list of X.509 Subject Names.

Trunk #6 conflicts with Trunk #4 because the protocol, incoming port, and X.509 Subject Name are identical.

Unplugging a USB Cable

When you unplug the USB cable and then plug it back in, you must first stop the Cisco Message Interface (CMI) service if it is running on that Cisco Unified CallManager server. You can restart the CMI service after you plug the USB cable back in. If you do not stop the CMI service before you unplug and plug the USB cable back in and a phone call to the voice message pilot number occurs or a call gets forwarded to that pilot number, the OS stops, and you will need to reboot the server. For more information, refer to CSCsc58288.

Cisco MCS-7845H-2.4-EVV1 and Cisco MCS-7835H-2.4-EVV2 Server May Not Recognize the USB-to-Serial Cable

When you reboot a Cisco MCS-7845H-2.4-EVV1 or a Cisco MCS-7835H-2.4-EVV2 server, the USB controller may not recognize the existence of the USB-to-Serial cable and will not detect a device that is attached to it when the server is rebooted. As a workaround, install a USB hub with power or plug in the USB device after the system has booted up. This only occurs on a limited number of units.

To determine whether you have a good system board, use the show tech system CLI command. The show tech system command displays information about the USB modules that are loaded onto the system, devices that are connected to the PCI bus and their device driver, and other system-configured hardware. Look for the following entry in the output: "ATEN International Co., Ltd UC-232A".

If you do not see the line output and the server is under warranty, you can replace the system board in the server.

For more information, refer to CSCsc86874.

Configuring Regions (Region Relationship) for SIP Devices with the MTP Required Option Enabled

When you configure a region relationship, you must ensure that you choose an audio codec that has sufficient bandwidth for all the devices that will be used in a call. This includes configuring the codec for devices that will be in the same region as well as devices that are in different regions. When you configure a trunk or third-party phone to use SIP and Media Termination Point Required is enabled, Cisco Unified CallManager Administration only allows you to choose a G.711 codec in the MTP Preferred Originating Codec field. When you assign the SIP trunk or third-party SIP phone with the MTP Required option enabled to the device pool for that region, you must verify that the region relationship between the SIP device and the MTP device is configured to use a codec with equal or greater bandwidth (G.711 or wideband codec).

Installed Software Options

After installing upgrade software for Cisco Unified CallManager, Cisco IPT Platform Administration displays an incorrect list of Installed Software Options when you choose Show > Software. For more information, see CSCsd21585.

Stalled Upgrades

During the installation of upgrade software, the upgrade may appear to stall. The upgrade log stops displaying new log messages. When the upgrade stalls, you must cancel the upgrade, disable I/O throttling, and restart the upgrade procedure. When you successfully complete the upgrade, you do not need to reenable I/O throttling.

To disable I/O throttling, enter utils iothrottle disable on the command line interface.

To display the status of I/O throttling, enter utils iothrottle status on the command line interface.

To enable I/O throttling, enter utils iothrottle enable on the command line interface. By default, iothrottle stays enabled.


Note If the system does not respond to the cancellation, you must reboot the server, disable I/O throttling, and restart the upgrade process procedure.


Registering Cisco Catalyst WS-X6608, WS-6624 Gateways, and Other Media Devices

Cisco Catalyst WS-X6608, WS-X6624 gateways, and other media device with firmware loads that have 8-character filename cannot register with Cisco Unified CallManager, release 5.0. By default, many Cisco Catalyst WS-X6608 and WS-X6624 modules ship with 8-character firmware loads. Cisco Unified CallManager only supports 12-character firmware load files. Before you can register the gateway or device, you must upgrade each port to the new 12-character load.


Note If you have a gateway or a media device that is currently loaded with a 8-character firmware file, then you must upgrade the firmware load on your gateway or media device prior to upgrading to Cisco Unified CallManager Release 5.0.


To verify the firmware load on the gateway, you can use the CLI command, show ver <mod>, on the Cisco Catalyst 6000 supervisor or the Dick Tracy utility. The following examples show the outputs for a WS-X6608-T1 module with 12-character loads that are using the CLI command and using the Dick Tracy utility.

Using the CLI command on the Cat6K supervisor

nw100b-6506> (enable) sh ver 5
Mod Port Model               Serial #    Versions
--- ---- ------------------- ----------- --------------------------------------
5   8    WS-X6608-T1         SAD04320KZ7 Hw : 1.1
                                         Fw : 5.4(2)
                                         Sw : 8.1(2)
                                         HP1: (not online); DSP1: (not online)
                                         HP2: (not online); DSP2: (not online)
                                         HP3: D00404000022; DSP3: D0054322 (4.3.222)
                                         HP4: D00404000022; DSP4: D0054322 (4.3.222)
                                         HP5: D00404000021; DSP5: D0054322 (4.3.222)
                                         HP6: D00404000021; DSP6: D0054322 (4.3.222)
                                         HP7: M00103010007; DSP7: M002E031 (3.3.2)
                                         HP8: D00404000007; DSP8: D0054133 (4.1.33)

Using the Dick Tracy Utility, enter 0 sh ver on the Dick Tracy command window to see the firmware version that is running on the 6608

(GEN) Firmware Version Info
        Executing 860 image -----> D00404000022 Built Dec 22 2005 11:47:13
        TFTP 860 image file -----> D00404000022.bin
        TFTP DSP image file -----> D0054322.bin
        TFTP POST image file ----> D007C030.bin
        Flash ROM 860 image #1 --> D0040022
        Flash ROM 860 image #2 --> D0040022
        Flash ROM DSP image -----> D0054322
        Flash ROM POST image ----> D007C030
        TCP/IP Library ----------> TCPT030

To update the firmware load, you can connect the gateway or media device to a Cisco Unified CallManager Release 3.1 through release 4.2, and use Cisco Unified CallManager Administration to provision each port and upgrade the firmware load.

For more information, see CSCeg20715.

Limiting the Number of Records in a BAT Transaction

Cisco recommends that you limit the number of records when you perform a bulk transaction in Cisco Unified CallManager Bulk Administration to a maximum of 12,000 records. This applies when you insert, update, delete, or query any records using BAT.

If you have more than 12,000 records in your CSV file, your transaction fails. You must split the records into multiple CSV files, such that each CSV file contains less than 12,000 records.

If you have a query-based transaction, the transaction may not complete. You must refine your query to limit the number of records that Cisco Unified CallManager displays.

For more information, see CSCsd64029.

Using T.38 with Cisco IP Voice Media Streaming Application Service

Currently, Cisco IP Voice Media Streaming Application Service does not support T.38 data transmission. To prevent Cisco IP Voice Media Streaming Application Services from interfering with T.38 fax relay calls, ensure the Cisco IP Voice Media Streaming Application service is assigned to a Media Resource Group and that Media Resource Group does not get used in any gateways or trunks that are involved in T.38 calls.

Using IPSEC Within the Nodes of a Cluster

Do not configure Cisco Unified CallManager to use IPSEC between the nodes within a cluster. Doing so causes IP connectivity problems, and Cisco Unified CallManager applications may fail. This occurs because of a small amount of packet loss that occurs during the expiration and renegotiation of IPSec Security Associations (SA). You may use IPSEC between a Cisco Unified CallManager node and a gateway or between Cisco Unified CallManager nodes in different clusters because those SA lifetimes get generally configured with a much longer period, usually for several hours. For more information, refer to CSCsc27888 and CSCsd69723.

SIP Third-Party Phones Support AAR Calling Search Space

You can now configure an AAR Calling Search Space for Third-Party SIP Device (Basic) and Third-party SIP Device (Advanced) phones by using Phone Configuration.

For more information, refer to the "Phone Configuration Settings" table in the Cisco Unified CallManager Administration Guide and the "Automated Alternate Routing" section in the Cisco Unified CallManager System Guide.

Configuration Tips for TFTP Servers in a Centralized TFTP Setting

You must ensure that you list all your alternate servers before you have an empty parameter value. If the Cisco TFTP service parameter, First Alternate Cisco File Servers, contains an empty parameter value, TFTP will stop searching for alternate servers. For example, if Alternate Cisco File Servers 2 through 10 are configured, and Alternate Cisco file Server 1 remains empty, and TFTP searches for servers, it will not search for Alternate Cisco File Servers. For more information, refer to CSCsd48982.

Using FTP Servers

Some Cisco Unified CallManager services, such as CDR, DRF, and DMA, require a separate FTP or SFTP server. The following list shows FTP server programs that have been tested with Cisco Unified CallManager 5.0.

Openssh Server by Red Hat, Inc., Version 3.6.1p2, Release 33.30.4

Cygwin SFTP Server, Version 2.457.2.2 with cygwin.dll Version, 1.5.16

War FTP Daemon Version 1.82, by Jgaa's Freeware on Microsoft Windows server

FTP Publishing Service in Microsoft Internet Information Server 5.0, Version 1.0 on a Microsoft Windows 2000 Server

Customizing a Background Image on Cisco Unified IP Phones

You can display custom background images on the LCD screen on Cisco Unified IP Phones 7911, 7941, 7961, 7970, and 7971. Ensure these customized images are stored in specific subdirectories on the TFTP server. You must also copy the customized images and files to the other TFTP servers that the phone may contact to obtain these files.

To upload the images, you must choose Software Upgrades > Upload TFTP Server File in Cisco IPT Platform Administration. Upload the images to the following subdirectories:

For the Cisco Unified IP Phone 7970 series, the subdirectory specifies /Desktops/320x212x12

For the Cisco Unified IP Phone 7961/41, the subdirectory specifies /Desktops/320x196x4

For the Cisco Unified IP Phone 7911G, the subdirectory specifies /Desktops/95x34x1


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


For more information on how to configure custom background images, see the "Configuring a Background Image" section in the "Customizing the Cisco Unified IP Phone" chapter of the Cisco Unified IP Phone Administration Guide for Cisco Unified CallManager 5.0 (SCCP) or the Cisco Unified IP Phone Administration Guide for Cisco Unified CallManager 5.0 (SIP) for your phone.

For more information on uploading software, see the "Software Upgrades" chapter in the Cisco IP Telephony Platform Administration Guide.


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


Upgrading from Cisco Unified CallManager Release 5.0(1) to Release 5.0(2)

During the upgrade of Cisco Unified CallManager, the server experiences high disk I/O activity. This can adversely impact call processing. In the worst case, phones that are currently registered with that Cisco Unified CallManager server may failover to their backup server. We strongly recommend that you ensure that all trace levels are set to the default level on all servers in your cluster before you start the upgrade process.

Furthermore, if you have concerns that the upgrade may impact call processing service, we recommend that you perform the upgrade during off-peak hours. If you want to minimize the disruptions to the call-processing service, you may choose to stop the Cisco Unified CallManager service on the server before you start the upgrade process.

As always, follow standard best practices while performing a Cisco Unified CallManager upgrade.

Backing up Hard Drives by Pulling them out on a Cisco MCS 7845

Previous versions of Windows-based Cisco Unified CallManager require you to pull out one hard drive from the first RAID array.

For Cisco Unified CallManager, Release 5.0(2) and later, you MUST pull out one hard drive from each of the two RAID arrays on a Cisco MCS 7845. To ensure data consistency, shut down and power off the system before you remove the hard drive.

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.

New and Changed Information in Cisco Unified CallManager 5.0(4a)

Cisco Unified CallManager Release 5.0(4a) includes the following fixes:

Registration of Cisco IP Communicator

Installation on Cisco MCS Servers MCS-7825-H1, MCS-7825-H2

Upgrade During Install

TFTP Crash During Upgrade

Installation on IBM 8491-G2U

Registration of Cisco IP Communicator

You may experience difficulty registering Cisco IP Communicator on a cluster with security enabled after installing Cisco Unified CallManager Release 5.0(4). You may also see that centralized TFTP does not work. These problems existed because the internal buffer and code path that were used for HTTP were not the same as used for TFTP. Cisco Unified CallManager Release 5.0(4a) fixes this defect.

For more information about this issue, see the "Resolved Caveats" section

Installation on Cisco MCS Servers MCS-7825-H1, MCS-7825-H2

When you perform a fresh installation of Cisco Unified CallManager Release 5.0(4) on Cisco MCS of type MCS-7825-H1 or MCS-7825-H2 by using the Cisco Unified CallManager 5.0(4) Installation DVD, the installation process stops before completion and displays the following message: "Waiting for RAID to BUILD...".

Cisco Unified CallManager Release 5.0(4a) fixes this defect.

For more information about this issue, see the "Resolved Caveats" section.

Upgrade During Install

When you perform an upgrade during install by using the software that is contained on the Cisco Unified CallManager Release 5.0(4) installation disc with the latest service release, the installation fails.

Cisco Unified CallManager Release 5.0(4a) resolves this problem.

For more information about this issue, see the "Resolved Caveats" section.

TFTP Crash During Upgrade

When you perform an upgrade to Cisco Unified CallManager Release 5.0(4), TFTP crashes. This problem resulted because of a imperfection in the TFTP code. Cisco Unified CallManager Release 5.0(4a) alters the code and TFTP no longer crashes.

For more information about this issue, see the "Resolved Caveats" section.

Installation on IBM 8491-G2U

When you perform a fresh installation of Cisco Unified CallManager Release 5.0(3a) on an IBM 8491-G2U by using the Cisco Unified CallManager 5.0(3a) Installation DVD, the installation process stops before completion and displays the following message: "HW type [Vendor/Product] NOT SUPPORTED...". The IBM 8491-G2 machines get supported and Cisco Unified CallManager Release 5.0(4a) resolves this defect.

For more information about this issue, see the "Resolved Caveats" section.

For complete installation information, refer to the following documents:

Installing Cisco Unified CallManager Release 5.0(4)

Upgrading Cisco Unified CallManager Release 5.0(4)

Data Migration Assistant Administration Guide, Version 5.0(2a))

New and Changed Information in Cisco Unified CallManager 5.0(4)

Cisco Unified CallManager Release 5.0(4) includes the following new features:

IPMA on the Cisco Unified IP Phone

Cisco Unified CallManager Attendant Console

Migration of Cisco Unified CallManager 5.0 Locales

Cisco Unified CallManager Administration

Cisco Unified CallManager Features

Cisco Unified CallManager Serviceability

Security Feature Changes

IPMA on the Cisco Unified IP Phone

Cisco Unified CallManager includes enhancements for using the Cisco Unified CallManager Assistant on the assistant phone. This release includes the Assistant Phone Application, which enables the assistant to use the physical phone buttons and softkeys to perform most of the call-handling tasks that the assistant performs by using the Assistant Console application.

Cisco Unified CallManager Attendant Console

Cisco Unified CallManager Attendant Console, a client-server application, allows you to use a graphical user interface that contains speed-dial buttons and quick directory access to look up phone numbers, monitor line status, and direct calls.

For this release, administrators can implement a device security feature, so attendants can only use phones that are associated with a device authentication application user.

Cisco Unified CallManager Administration Configuration Tips

To implement device security, you must configure an attendant console device authorization application user and associate the attendant phones with this attendant console device authorization application user. If you do not configure and associate phones with this user, the attendant console cannot receive calls. To access the Application User Configuration window, choose User Management > Application User.

Make sure that the user ID that you use for the device authentication user is the same as the value in the Device Authentication Application Username field in the Service Parameters Configuration window for the Cisco CallManager Attendant Console Server service.

You do need to associate attendant phones and pilot points with the JTAPI (or "ac") user.

Service Parameter Changes

The following new service parameter supports Cisco Unified CallManager Attendant Console device security feature:

Device Authentication Application Username-Specifies the username that the Cisco CallManager Attendant Console Server uses to authenticate attendant phones. The default specifies ACDeviceAuthenticationUser. The value of this field must match the user ID of the device authentication application user that you create on the Application User Configuration window.

Online Help for Cisco Unified CallManager Attendant Console

The Cisco Unified CallManager Attendant Console 5.0(4) online help contains the Cisco Unified CallManager Attendant Console User Guide, Version 5.0(2). This version of the user guide applies to Cisco Unified CallManager Attendant Console 5.0(4), because no changes to the interface occurred for the 5.0(4) release.

If you would like a copy of the Cisco Unified CallManager Attendant Console User Guide, Version 5.0(4), go to http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/attendnt/call_att/index.htm.

Where to Find More Information

Cisco Unified CallManager Attendant Console, Cisco Unified CallManager Features and Services Guide

Cisco Unified CallManager Attendant Console User Guide, Version 5.0(4)

Cisco Unified CallManager Administration

System Menu Changes

The following change occurred in the System menu:

Licensing

Capabilities Assignment—This new menu item allows system administrators to enable the Cisco Unified Presence Server (CUPS) and Cisco Unified Personal Communicator (CUPC) capabilities for users. Ensure licenses for CUPS and CUPC are available (License > License File Upload).

LDAP Menu Changes

The following change occurred in the LDAP menu:

When you choose System > LDAP > LDAP System, you can choose Netscape or Sun ONE LDAP Server from the LDAP Server Type drop-down list box, so you can integrate the directory with the Sun Java System Directory Server.


Note Sun Microsystems rebranded Sun Open Net Environment (Sun ONE) Directory Server to Sun Java System Directory Server. Be aware that Cisco Unified CallManager has been tested with Sun Java System Directory Server 5.2. Refer to Sun Microsystems documentation for additional information.


Enterprise Parameter Changes

The default Phone URL Parameters on Enterprise Parameters Configuration changed since 4.x releases of Cisco Unified CallManager. The new default Phone URL Parameters (for 5.x releases) follow:

URL Authentication: http://serverName:8080/ccmcip/authenticate.jsp

URL Directories: http://serverName:8080/ccmcip/xmldirectory.jsp

URL Information: http://serverName:8080/ccmcip/GetTelecasterHelpTest.jsp

URL Services: http://serverName:8080/ccmcip/getservicesmenu.jsp

Although these default URLs should be populated automatically when upgrades occur, you also can access them in the online help by clicking the ? in the upper, right corner of the Enterprise Parameters Configuration window.


Note In releases prior to 5.0, these URLs had an extension of .asp instead of the new .jsp extension, and they were not case sensitive as they are now.


Cisco Unified CallManager Features

Licensing

The following sections describe the Capabilities Assignment functionality that is under the Licensing menu in Cisco Unified CallManager Administration.

Cisco Unified CallManager Configuration Tips

One CUPS license and one CUPC license each take one unit from the Phone Device License Pool.

Before assigning the CUPS and/or the CUPC license to users, you must first add the CUPS server(s) by using System > Application Server.

Activate the Cisco AXL Web Service from Serviceability, so the end user license information can get synchronized to CUPS.

Determine how many CUPS (servers and clients) and CUPC licenses are required for your system by choosing Licensing > License Unit Calculator.

Acquire the required licenses by using Licensing > License File Upload.

Verify the total licenses by using Licensing > License Unit Report.

Enable CUPS and CUPC for users by using Licensing > Capabilities Assignment.

Click the Find button to display the users in your system. The Find and List Capabilities Assignments window displays.

To enable CUPS and CUPC for an individual user, click the user. The Capabilities Assignment Configuration window displays.

To enable CUPS, check the Enable UPS (Unified Presence Server) check box. To enable CUPC, check the Enable UPC (Unified Personal Communicator) check box. You can enable both CUPS and CUPC; however, if you want CUPC, you will also need to enable CUPS. To save the information, click Save. To return to the Find and List Capabilities Assignment window, choose Back to Find/List from the Related Links drop-down list box and click Go. The user will have a check mark in the UPS and UPC column to indicate that they are enabled.

To enable CUPS and CUPC for a batch of users, check the check box by each user name or click the Select All button; click the Bulk Assignment button. The Capabilities AssignmentConfiguration window displays.

To batch enable CUPS, check the Enable UPS (Unified Presence Server) check box. To batch enable CUPC, check the Enable UPC (Unified Personal Communicator) check box. You can enable both CUPS and CUPC; however, if you want CUPC, you will also need to enable CUPS. To save the information, click Save; to save the information and return to the Find and List Capabilities Assignment window, click Save and then Close. The users will have a check mark in the UPS and UPC column to indicate that they are enabled.

GUI Changes

The following new menu option exists in Cisco Unified CallManager Administration:

Licensing > Capabilities Assignment

BAT Considerations

The Bulk Administration menu under CUPS now includes the following two items:

Update CUPS/CUPC Users — Bulk Administration>CUPS>Update CUPS/CUPC Users

Export CUPS/CUPC Users — Bulk Administration>CUPS>Export CUPS/CUPC Users

Update CUPS/CUPC Users

Use the following steps to add/change the license:

1. Use the Upload/Download Files window to upload the csv file. The csv file that you are updating must follow the rules that the sample file that is available on the Update CUPS window specifies.


Note You must ensure that you select the correct BAT target and transaction type while uploading the csv file.


2. Navigate to the Update CUPS window, select the csv file that is uploaded, and submit the job.


Note You can choose to run the job immediately or later by selecting the respective radio button. If you choose Run Later, you need to use the Job Scheduler window to schedule and activate this job.


3. To monitor the progress of the BAT job that is submitted, you can use the Export Users Query window.

Export CUPS/CUPC Users

You can use the Export Users Query window to obtain the current license information about all users for CUPS and CUPC.


Note Currently, no option exists to select a subset of CUPS users; all CUPS users in the system get exported to file.


Use the following steps to Export licenses:

1. Navigate to the Export Users Query window.

2. To view the basic user information and the license status, click Find.

3. To view the Export window for CUPS/CUPC, click Next.

4. Specify the file name to be exported and click Submit to start the BAT job.

5. To view the status of the BAT job that is submitted, go to the Job Scheduler window.


Note After the job is completed, you can go to the Upload/Download Files window to download the exported .csv file.


Where to Find More Information

Licensing Configuration, Cisco Unified CallManager Administration Guide

Cisco Unified CallManager Bulk Administration Guide

CUPS Administration Guide

Cisco Unified CallManager Serviceability

Cisco Unified CallManager Release 5.0(4a) provides the following enhancements to Serviceability:

Real-Time Monitoring Tool

Cisco Unified CallManager 5.0(4a) includes the following enhancements to the Real-time Monitoring Tool (RTMT):

RTMT allows you to log data from selected performance counters locally on your computer. From the Performance window, you can select the performance counter that you want to display. You can then choose to log all the counters that display or you can choose to log a specific performance counter.

RTMT includes a Performance Log Viewer that you can use to display data from the perfmon logs that you collected locally, or you can display the data from the Alert Manager and Collector (AMC) perfmon logs and Real-time Information Server Data Collection (RISDC) perfmon logs that are written on the server.

RTMT contains the following new performance counters:

Await Read Time—This counter represents the average time, measured in milliseconds, for Read requests that are issued to the device to be served.

This replaces the % Wait In Read counter.

Await Write Time—This counter represents the average time, measured in milliseconds, for write requests that are issued to the device to be served.

This replaces the % Wait In Write counter.

Security Feature Changes

To improve usability, prevent security configuration errors, and ensure that confidential user data is secure in phone downloads, release 5.0(4a) includes the following changes to Cisco Unified CallManager security configuration:

A new phone security profile, Phone Security Profile, replaces the SIP Phone Security Profile and SCCP Phone Security Profile. As administrator, you configure the Phone Security Profile parameters after you select a phone type and protocol. Cisco Unified CallManager displays only the security profile parameters that the phone type and protocol support in the Phone Security Profile Configuration window. Cisco Unified CallManager displays only the security profiles that the device type and protocol support in the Phone Configuration window.


Note Existing phone security profiles and settings migrate to the new database schema during upgrade.


Cisco Unified CallManager provides a set of predefined, nonsecure device profiles at installation for auto-registration for phones and the SIP trunk. To enable security features for a phone or a SIP trunk, you must configure a new, secure profile and apply it to the device.

Administrators can update CAPF settings in the security profile window or in the phone configuration window.

For voice-messaging service, you now configure a device security mode, not an SCCP security profile, for voice mail ports. The database predefines the security profiles that associate with the device security mode setting that you choose.

Cisco Unified CallManager uses reversible encryption to store all digest authentication credentials and SSH passwords in the database.

A new flag, Exclude Digest Credentials in Configuration File, on the Phone Security Profile allows administrators to simplify the process of downloading secure digest credentials to SIP phones.

The CTL client now displays mixed mode, not secure mode, to allow authenticated or encrypted Cisco Unified IP Phones and nonauthenticated modes Cisco Unified IP Phones to register with Cisco Unified CallManager. This represents a field name change only, which ensures consistency with other platforms.

This release adds third-party certificate support for external CAs with a new CSR mechanism that is accessible at the platform. Verification of the CSR mechanism occurred with these CAs: Keon, Microsoft, and Verisign.

Cisco Unified CallManager Administration Configuration Tips for Phone Security Profiles

Although Cisco Unified CallManager provides a set of predefined, nonsecure profiles for Cisco Unified IP Phones and the SIP trunk for auto-registration, you must still apply a security profile, including the nonsecure profile, to these devices in Cisco Unified CallManager Administration. You must also select a device security mode for the voice mail port to configure security settings for the voice mail ports. The default setting for the phone and SIP trunk security profile selection and the voice mail ports device security mode selection specifies Not Selected.

Cisco Unified CallManager displays only the security profile parameters that the phone type and protocol support in the Phone Security Profile Configuration window. If the phone device and protocol do not support security, only the nonsecure profile displays in the list.

The CAPF settings that are configured in the profile relate to the Certificate Authority Proxy Function settings that display in the Phone Configuration window. You must configure CAPF settings for certificate operations that involve manufacture-installed certificates (MICs) or locally significant certificates (LSC).

Consider the following information when you configure phone security profiles in Cisco Unified CallManager Administration:

When you configure phones, you must select a security profile in the Phone Configuration window. If the device does not support security, apply the nonsecure profile.

You cannot delete or change predefined, nonsecure profiles.

You cannot delete a security profile that is currently assigned to a device.

If you change the settings in a security profile that is already assigned to a phone, the reconfigured settings apply to all phones that are assigned that profile.

You can rename security files that are assigned to devices. The phones that are assigned the old profile name and settings assume the new profile name and settings.

The CAPF settings in the Phone Security Profile, authentication and key size, also display in the Phone Configuration window. You must configure CAPF settings for certificate operations that involve manufacture-installed certificates (MICs) or locally significant certificates (LSCs). You can update these fields directly in the Phone Configuration window.

If you update the CAPF settings in the security profile, the settings get updated in the Phone Configuration window.

If you update the CAPF settings in the Phone Configuration window and a matching profile is found, Cisco Unified CallManager applies the matching profile to the phone.

If you update the CAPF settings in the Phone Configuration window, and no matching profile is found, Cisco Unified CallManager creates a new profile and applies the new profile to the phone.

If you configured the device security mode prior to a Cisco Unified CallManager 5.0 or later upgrade, Cisco Unified CallManager creates a profile that is based on the model and protocol and applies the profile to the device.

Cisco Unified CallManager Administration Configuration Tips for TFTP Encrypted Configuration Files

Cisco recommends that you enable the TFTP Encrypted Config flag to secure confidential data in phone downloads. For phones that do not have PKI capabilities, you must also configure a symmetric key in Cisco Unified CallManager Administration and in the phone. If the symmetric key is missing from either the phone or Cisco Unified CallManager or if a mismatch occurs when the TFTP Encrypted Config flag is set, the phone cannot register.

Consider the following information when you configure encrypted configuration files in Cisco Unified CallManager Administration:

Only phones that support encrypted configuration files display the TFTP Encrypted Config flag in the phone security profile. You cannot configure encrypted configuration files for Cisco Unified IP SCCP Phones 7905, 7912, 7940, and 7960 because these phones do not receive confidential data in the configuration file download.

Only SIP phone security profiles display the Enable Digest Authentication flag and the TFTP Exclude Digest Credentials in Configuration File flag.

The default setting for TFTP Encrypted Config specifies false (not checked). If you apply the default, nonsecure profile to the phone, digest credentials and secured passwords get sent in the clear.

For Cisco Unified Phones that use public key encryption, Cisco Unified CallManager does not require you to set the Device Security Mode to authenticated or encrypted to enable encrypted configuration files. Cisco Unified CallManager uses the CAPF process for downloading its public key during registration.

You may choose to download unencrypted configuration files to phones if you know your environment is secure or to avoid manually configuring symmetric keys for phones that are not PKI-enabled; however, Cisco does not recommend using this method.

For Cisco Unified IP SIP Phones 7905, 7912, 7940, and 7960, Cisco Unified CallManager Administration provides a method of sending digest credentials to the phone that is easier, but less secure, than using an encrypted configuration file. This method, which is useful for initializing digest credentials because it does not require you to first configure a symmetric key and enter it on the phone, uses the TFTP Exclude Digest Credential in Configuration File setting.

With this method, you send the digest credentials to the phone in an unencrypted configuration file. After the credentials are in the phone, Cisco recommends that you keep the TFTP file encryption setting disabled and enable the TFTP Exclude Digest Credential in Configuration File flag on the corresponding security profile window, which will exclude digest credentials from future downloads.

After digest credentials exist in these phones and an incoming file does not contain digest credentials, the existing credentials remain in place. The digest credentials remain intact until the phone is factory reset or new credentials (including blanks) are received.

If you change digest credentials for a phone or end user, temporarily disable the Exclude Digest Credentials flag on the corresponding security profile window to download the new digest credentials to the phone.

Be aware that the TFTP Exclude Digest Credentials flag is valid for all Cisco Unified IP SIP Phone. If the TFTP Exclude Digest Credentials flag is set for these phones, Cisco Unified CallManager excludes the digest credentials, even when the TFTP Encrypted Config flag is set.


Note Be sure that the digest credentials are loaded on the phone at least once, or the phone may fail to register.


Cisco Unified CallManager Administration Configuration Tips for Voice Mail Ports

Consider the following information when you configure voice mail ports in Cisco Unified CallManager Administration:

You must run Cisco Unity 4.0(5) or later with this version of Cisco Unified CallManager.

You must perform security tasks for Cisco Unity by using the Cisco Unity Telephony Integration Manager; for information on how to perform these tasks, refer to the Cisco Unified CallManager 5.0 Integration Guide for Cisco Unity 4.x.

In addition to the procedures that are described in this section, you must use the certificate management feature in Cisco Unified Communications Operating System Administration to save the Cisco Unity certificate to the trusted store. For more information on this task, refer to the Cisco Unified Communications Operating System Administration Guide.

After you copy the certificate, you must restart the Cisco CallManager service on each server in cluster.

If Cisco Unity certificates expire or change for any reason, use the certificate management feature in the Cisco Unified Communications Operating System Administration to update the certificates in the trusted store. The TLS authentication fails when certificates do not match, and voice messaging does not work because it cannot register to Cisco Unified CallManager.

When configuring voice-mail server ports, you must select a device security mode.

The setting that you specify in the Cisco Unity Telephony Integration Manager must match the voice messaging port device security mode that is configured in Cisco Unified CallManager Administration. In Cisco Unified CallManager Administration, you apply the device security mode to the voice-messaging port in the Voice Mail Port Configuration window (or in the Voice Mail Port Wizard).


Tip If the device security mode settings do not match for Cisco Unified CallManager and Cisco Unity, the Cisco Unity ports fail to register with Cisco Unified CallManager, and Cisco Unity cannot accept calls on those ports.


Changing the device security mode for the port requires a reset of Cisco Unified CallManager devices and a restart of the Cisco Unity software. If you apply a different device security mode in Cisco Unified CallManager Administration, you must change the setting in Cisco Unity.

You cannot change the device security mode for existing voice-mail servers through the Voice Mail Port Wizard. If you add ports to an existing voice-mail server, the device security mode that is currently configured for the profile automatically applies to the new ports.

GUI Changes

The following GUI changes apply to security features in this release.

To access the new Phone Security Profile, choose System > Security Profile > Phone Security Profile.

The phone security profile asks for product type and device protocol before displaying the supported security profile parameters.

Cisco Unified CallManager displays only the security profiles that the device type and protocol support in the Phone Configuration window and the SIP Trunk Configuration window.

Cisco Unified CallManager provides a set of predefined, nonsecure device profiles at installation for auto-registration for phones and the SIP trunk.

In the Phone Security Profile CAPF Information section, the Phone Security Profile displays the message, "These fields are related to the CAPF Information settings on the Phone Configuration page.'

In the Certification Authority Proxy Function (CAPF) Information section, the Phone Configuration window displays the message, "Security Profile Contains Additional CAPF Settings."

The Cisco Voice Mail Port Configuration window and Cisco Voice Mail Port Wizard include a new setting, Device Security Mode, that replaces the device security profile setting. Cisco Unified CallManager stores the device security mode setting in a security profile in the database. Device Security Mode replaces Device Security Profile as a Find option.

The TFTP Encrypted Config check box now displays in the Phone Security Profile when phone device and protocol support encrypted configuration file downloads.

For SIP phones that support encrypted configuration file downloads, a new check box, Exclude Digest Credentials in Configuration File, displays in the phone security profile.

Some setting locations, such as the Certification Authority Proxy Function (CAPF) Information section, moved within a window to logically group related settings.

BAT Considerations

You can apply a security profile to phones in the BAT phone template.

Where to Find More Information

Cisco Unified CallManager Security Guide

New and Changed Information in Cisco Unified CallManager 5.0(3)

Cisco Unified CallManager Release 5.0(3) includes the following new features:

Cisco Announces New Servers and Appliances

Firewall Support for Attendant Console

Cisco Announces New Servers and Appliances

Cisco Unified CallManager supports a series of new Media Convergence Servers and Unified CallManager Appliances to continue to deliver converged voice, video, and data solutions. The system also supports two new Digital Audio Tape (DAT) drives by using USB 2.0 as the interface to the media convergence servers.

For more information on these servers, refer to http://www.cisco.com/en/US/products/hw/voiceapp/ps378/index.html

The following URL provides a list of supported servers:

http://www.cisco.com/en/US/products/hw/voiceapp/ps378/prod_brochure09186a0080174928.html

Firewall Support for Attendant Console

Cisco Unified CallManager 5.0(3) offers firewall support through Remote Method Indication (RMI).

Attendant console clients and attendant console servers communicate through Java RMI, which is also how attendant console servers communicate with each other. They only differ in that no firewall exists between servers.

The attendant console server uses a custom RMI socket to bind to specific TCP ports for sending the RMI response to the client. You can configure this by using Service Parameter RMI Bind Port.

RMI uses a TCP Callback Port to send callback messages to the attendant console client. You can configure the attendant console Client Callback Port by using Settings Dialog.


Tip You must make sure that the RMI ports are open in the firewall.


New and Changed Information in Cisco Unified CallManager 5.0(2)

Cisco Unified CallManager 5.0(2) supports the product name changes for the suite of Cisco Unified Communications system of voice, video, and IP communications products and applications. This name change updates all product and application names in the user interface with the exception of the following services and performance counter for Cisco Unified CallManager Serviceability:

Feature Services

Cisco CallManager service supports Cisco Unified CallManager.

Cisco CallManager Attendant Console Server service supports Cisco Unified CallManager Attendant Console.

Cisco IP Manager Assistant service supports Cisco Unified CallManager Assistant.

Cisco Dialed Number Analyzer service supports Cisco Unified CallManager Dialed Number Analyzer.

Network Services

The Cisco CallManager Admin service supports Cisco Unified CallManager Administration.

The Cisco CallManager Serviceability service supports Cisco Unified CallManager Serviceability.

The Cisco CallManager Serviceability RTMT service supports the Cisco Unified CallManager Real-Time Monitoring Tool (RTMT).

Perfmon

The Cisco CallManager object provides information about calls, applications, and devices that are registered with the Cisco Unified CallManager.

The Cisco CallManager Attendant Console (Cisco CallManager Attendant Console Server service) object provides information about the Cisco Unified CallManager Attendant Console.

The Cisco CallManager System Performance object provides system performance information about Cisco Unified CallManager. The Cisco IP Manager Assistant (IPMA) Service object provides information about the Cisco Unified CallManager Assistant application.

You can find more information on Cisco Unified Communications system of voice, video, and IP communications products and applications at www.cisco.com/go/unified.

New and Changed Information in Cisco Unified CallManager 5.0(1)

The following sections describe new features and changes that are pertinent to Cisco Unified CallManager, release 5.0(1) or later. The sections may include configuration tips for the administrator, information about users, and where to find more information.

Installation, Upgrade, Migration, and Disaster Recovery

Cisco Unified Communications Operating System Administration

Cisco Unified CallManager Administration

Cisco Unified CallManager Features

Cisco Unified CallManager User Options Web Pages

Cisco Unified CallManager Applications

Cisco Unified CallManager Bulk Administration Features

Cisco Unified CallManager Auto-Register Phone Tool Features

Security Features

New and Changed Information for Cisco Unified CallManager Serviceability

New and Changed Information for Cisco Unified IP Phones

New and Changed Information for Third-Party API

Installation, Upgrade, Migration, and Disaster Recovery

This following sections describe the changes that were made to the installation, upgrade, and disaster recovery procedures in Cisco Unified CallManager 5.0(2):

Installation Overview

Software Upgrades

Data Migration Assistant (DMA)

Disaster Recovery Enhancements

Where to Find More Information

Installation Overview

Cisco Unified CallManager 5.0(2) uses a different installation framework than previous releases. The installation process allows you to perform a basic installation, upgrade from Cisco Unified CallManager Release 4.0 or Release 4.1 to Cisco Unified CallManager 5.0, and upgrade to a newer service release during the installation.


Note Although you do not need a license to install Cisco Unified CallManager 5.0(2), you must have a Cisco Unified CallManager server license to activate services on the server, and you must have phone licenses to add phones to the Cisco Unified CallManager database.


For a more detailed description of the different installation types, see Table 2.

Table 2 Installation Options 

Installation Types
Description

Basic Install

This option represents the basic Cisco Unified CallManager 5.0(2) installation, which installs the software from the installation disc and does not use any imported data.

Upgrade During Install

This option allows you to upgrade the software version that the installation disc contains with the latest service release. You can also choose Upgrade During Install followed by a Windows Upgrade and perform both during the installation process.

Windows Upgrade

This option allows you to import database information from a Cisco Unified CallManager 4.0 or 4.1 system by using a file that the Data Migration Assistant (DMA) tool produces.


Software Upgrades

With Cisco Unified CallManager 5.0, you can install software upgrades on your server while the system continues to operate. Multiple partitions exist on your system disk, including an active, bootable partition and an inactive, bootable partition. The system boots up on the partition that is marked as the active partition.

When you install the software upgrades by using the Cisco Unified Communications Operating System interface, you install the software on the inactive partition. The system continues to function normally while you are installing the software. When you are ready, you activate the inactive partition and reboot the system with the new upgrade software. The current active partition will then get identified as the inactive partition when the system restarts. The current software remains in the inactive partition until the next upgrade.

You can also back out of an upgrade by restarting the system by using the software version on the inactive partition. However, if you have made any configuration changes since you installed the upgrade, they get lost when you revert to the older version of the software.

Data Migration Assistant (DMA)

The Cisco DMA assists you with the first step in migrating Cisco Unified CallManager 4.0 or 4.1 data to Cisco Unified CallManager 5.0 by backing up Cisco Unified CallManager 4.0 or 4.1 data in a format that Cisco Unified CallManager 5.0 can read. Cisco Unified CallManager 4.x runs in a Windows environment, and Cisco Unified CallManager 5.0 runs in a Linux environment, so the Cisco DMA exports Windows-based data to a format that Cisco Unified CallManager 5.0 can import. The Cisco Unified CallManager 5.0 installation process converts the backed-up data as needed for Cisco Unified CallManager 5.0, which completes the data migration.

The Cisco DMA saves the data that it exports in a tape archive (tar) file in a location that you specify.

You must install and run the Cisco DMA on the Cisco Unified CallManager publisher server before you upgrade to Cisco Unified CallManager 5.0. If you make any Cisco Unified CallManager configuration changes after running the Cisco DMA, the system does not retain these changes when you upgrade.

In addition to exporting Cisco Unified CallManager data, the Cisco DMA exports data for these related applications:

Attendant Console (AC)

Cisco Unified CallManager Extension Mobility (EM). DMA does not export the last user-logged-in data.

Cisco Unified CallManager CDR Analysis and Reporting (CAR)

Certificate Authority Proxy Function (CAPF)

Certificate Trust List (CTL)


Note If you installed the CAPF utility 1.0(1) on a Cisco Unified CallManager 4.0 subscriber server, you must copy the CAPF data to the 4.0 publisher database server before you upgrade to Cisco Unified CallManager 5.0. Failing to perform this task causes a loss of CAPF data.


The Cisco DMA does not export this information:

Custom Music on Hold (MOH) files—You must reapply these files after you upgrade to Cisco Unified CallManager 5.0.

TFTP phone load files—You must reapply these files after you upgrade to Cisco Unified CallManager 5.0.

Files on Cisco Unified CallManager subscriber servers—Subscriber servers obtain required information from the publisher server as part of the Cisco Unified CallManager upgrade process.

Last Logged User in Extension Mobility—Extension mobility users will need to enter the user name and PIN to log in the first time after the upgrade. The user does not need to enter the user name on subsequent logins.

CDR database—If you want to preserve the historical data in the CDR database, you must back up the data in the CDR database. You can use the backup utility on Microsoft SQL server.

Disaster Recovery Enhancements

The Cisco Disaster Recovery System (DRS), accessed from the Cisco Unified CallManager 5.0(2) Administration window, provides full data backup and restore capabilities for all servers in a Cisco Unified CallManager cluster. Cisco DRS allows you to perform regularly scheduled automatic or manually initiated data backups and system restoration.

The Cisco Disaster Recovery System performs a cluster-level backup, which means that it collects backups from all servers in a Cisco Unified CallManager cluster to a central location, then combines the backups into a single volume (or multiple volumes if necessary), and archives the backup data to a physical storage device.

When performing a system data restoration, you can choose which nodes and features in the cluster you want to restore.

The Cisco Disaster Recovery System features include

Graphical user interface for performing backup and restore tasks

Command-line access to most Cisco DRS functions

Scheduling engine to initiate tasks at user-specified times

Archives backed up to a physical tape drive or to a remote server

Where to Find More Information

Disaster Recovery System Administration Guide

Data Migration Assistant 2.0 User Guide

Upgrading Cisco Unified CallManager Release 5.0(2)

Installing Cisco Unified CallManager Release 5.0(2)

Cisco Unified CallManager Operating System Administration Guide, Release 5.0(2)

Cisco Unified Communications Operating System Administration

For Cisco Unified CallManager 5.0(2), you can perform many common system administration functions through the Cisco Unified Communications Operating System.

This section comprises the following topics:

Overview

Browser Requirements

Platform Status and Configuration

Restart Options

Security Configuration

Software Upgrades

Services

Command Line Interface

Overview

Cisco Unified Communications Operating System Administration allows you to configure and manage the Cisco Unified Communications Operating System by doing these tasks:

Check software and hardware status.

Check and update IP addresses.

Ping other network devices.

Manage NTP servers.

Upgrade system software and options.

Restart the system.

The following sections describe each platform function in more detail.

Browser Requirements

You can access Cisco Unified CallManager Administration, Cisco Unified CallManager Serviceability, and Cisco Unified Communications Operating System Administration by using the following browsers:

Microsoft Internet Explorer version 6.0 or later

Netscape Navigator version 7.1 or later


Note Cisco does not support or test other browsers, such as Mozilla Firefox.


Platform Status and Configuration

From the Show menu, you can check the status of various platform components, including

Cluster and nodes

Hardware

Network

System

Installed software and options

Settings

From the Settings menu, you can view and update the following platform settings

Ethernet—Updates the IP addresses and Dynamic Host Configuration Protocol (DHCP) settings that were entered when the application was installed.

NTP Server settings—Configure the IP addresses of an external NTP server; add or delete an NTP server.

SMTP settings—Configure the SMTP host that the platform will use for sending e-mail notifications.

Restart Options

From the Restart menu, you can choose from the following options for restarting or shutting down the system:

Switch Versions—Switches the active and inactive disk partitions and restarts the system. You normally choose this option after the inactive partition has been updated and you want to start running a newer software version.

Current Version—Restarts the system without switching partitions.

Shutdown System—Stops all running software and shuts down the server.

Security Configuration

The platform security options enable you to manage security certificates and Secure Internet Protocol (IPSec). From the Security menu, you can choose the following security options:

Certificate Management—Manages certificates, Certificate Trust Lists (CTL), and Certificate Signing Requests (CSR). You can display, upload, download, delete, and regenerate certificates. Through Certificate Management, you can also monitor the expiration dates of the certificates on the server.

IPSEC Management—Displays or updates existing IPSEC policies; sets up new IPSEC policies and associations.

Software Upgrades

The software upgrade options enable you to upgrade the software version that is running on the platform or to install specific software options, including Cisco Unified CallManager Locale Installers, dial plans, and TFTP server files.

From the Install/Upgrade menu option, you can upgrade system software from either a local disc or a remote server. The upgraded software gets installed on the inactive partition, and you can then restart the system and switch partitions, so the system starts running on the newer software version.


Note For Cisco Unified CallManager 5.0, you must do all software installations and upgrades by using the Software Upgrades menu options. The system can upload and process only software that Cisco Systems approved. You cannot install or use third-party or Windows-based software applications that you may have been using with a previous version of Cisco Unified CallManager with Cisco Unified CallManager 5.0.


Services

The application provides the following platform utilities:

Ping—Checks connectivity with other network devices.

Remote Support—Sets up an account that Cisco support personnel can use to access the system. This account automatically expires after the number of days that you specify.

Command Line Interface

The command line interface, which you can access from the console or through a secure shell connection to the server, provides a subset of the platform functionality that is available through the platform user interface. Keep in mind that the command line interface is designed for system emergencies and not as a replacement for the user interface.

Where to Find More Information

Cisco Unified Communications Operating System Administration Guide

Cisco Unified CallManager Administration

The following sections describe Cisco Unified CallManager 5.0 administration enhancements:

General Administration Enhancements

Navigating to IP Telephony Applications Within Cisco Unified CallManager

Localizing Cisco Unified CallManager Administration

Configuring Servers

Publisher and Subscriber Name Changes

Media Resources

Migration Tips

General Changes Made to Multiple Windows

Line and Phone Configuration Improvements

System Menu Changes

Call Routing Menu Changes (formerly Route Plan Menu)

Media Resources Menu

Voice Mail Menu

Device Menu Changes

Application Menu Changes

User Management Menu

Bulk Administration Menu

Service Parameter Changes

Where to Find More Information

General Administration Enhancements

Cisco Unified CallManager Administration Release 5.0 supports JSPs, STRUTS framework, and Java. The following requirements apply to Cisco Unified CallManager Administration:

Tomcat 5.0.2

Microsoft Internet Explorer (IE) 6.0 or higher

Netscape 7.1 or higher


Note This release does not support Microsoft IE 5.5 and Netscape 7.0.


Navigating to IP Telephony Applications Within Cisco Unified CallManager

Cisco Unified CallManager Administration includes a navigation bar in the upper, right corner of the window that takes the administrator to the following Cisco Unified Communications applications:

Cisco Unified CallManager Administration

Cisco Unified CallManager Serviceability

Disaster Recovery System

Cisco Unified Communications Operating System Administration


Note The Bulk Administration Tool (BAT) appears as a menu item on the Cisco Unified CallManager Administration menu.


Localizing Cisco Unified CallManager Administration

Cisco Unified CallManager Release 5.0 incorporates the following localization capabilities:

End User Configuration windows get localized. Other configuration windows that share the End User Configuration get localized.

To see the localization, set the browser to the language that is required. If that language locale is loaded, the configuration windows will be localized.

Configuring Servers

Because of security requirements, you cannot add, copy, or delete the following types of server configurations:

Cisco Unified CallManager

Music on Hold Server

Annunciator

These servers automatically get created at Cisco Unified CallManager installation.

Publisher and Subscriber Name Changes

Cisco Unified CallManager Release 5.0 software and documentation use the following names of the publisher servers and subscriber servers interchangeably:

Publisher specifies the first node

Subscriber specifies the subsequent node

Media Resources

You cannot add, copy, reset, or delete the following types of devices to media resources:

Media Termination Point—You cannot add or delete the Cisco Media Termination Point software.

Conference Bridge—You cannot add or delete the Cisco Unified CallManager Conference Bridge Software.

These entries automatically generate when a new server is added by using the Server Configuration window, and they get deleted when the server is deleted by using the Server Configuration window.

The following entry and server names automatically generate:

Cisco Unified CallManager—CM_<server name>

Music On Hod Server—MOH_<count>

Annunciator—ANN_<count>

Media Termination Point Software—MTP_<count>

Conference Bridge Software—CFB_<count>

where:

<count> specifies the number of entries for that device in the database.

Migration Tips

The following check boxes in Cisco Unified CallManager Administration get migrated to user groups when you upgrade from Release 4.1 or 4.0 to Release 5.0.

Check Box Name in Releases Before 5.0
Functionality Migrated to This User Group

Enable Computer Telephony Integration (CTI) Application Use

Standard CTI Enabled

Enable CTI Super Provider

Standard CTI Allow Control of All Devices

Enable Calling Party Number Modification

Standard CTI Allow Calling Number Modification

Call Park Retrieval Allowed

Standard CTI Allow Call Park Monitoring


General Changes Made to Multiple Windows

You can find the following changes on multiple Cisco Unified CallManager Administration windows:

Search Within Results—Found on the Find/List windows, this check box performs a search within a search result. When the check box is checked, and the administrator clicks the Find button, the find request searches the records within the results that were returned from the previous query. When the administrator no longer wants to search within the results, uncheck the check box, and the next query will search as a new search.

"i" button help changes—the question mark (?) icon replaces the "i" button on various Cisco Unified CallManager Administration windows. The help information did not change and still displays in a separate window.

Line and Phone Configuration Improvements

Cisco Unified CallManager Administration includes the following usability enhancements to the Phone and Directory Number Configuration windows:

Search Within Results (see the "General Changes Made to Multiple Windows" section)

Copy with Lines

Line Improvements

User/Phone Add

Copy With Lines

Administrators use this feature from the Find and List Phones window. If you check the phone and click the Copy w/Lines icon, the system copies all configured directory numbers, speed dials, Busy Lamp Field (BLF), speed dials, and service URLs, along with regularly copied items (for example, softkey template). The lines that get copied become shared lines between the original phone and the new phone.

Line Improvements

In addition to configured directory numbers, administrators can view additional settings such as speed dials, service URLs, and abbreviated dialing numbers on the Phone Configuration window. All this information displays in the Association Information pane. The administrator makes changes by clicking the link for the directory number (DN), for example.

The Unassigned Associated Items pane tracks the unassigned but associated DNs, speed dials, BLF speed dials, and service URLs.

The Modify Button Items button allows the administrator to configure, or reorder, the phone buttons without going to the Phone Button Template Configuration window. Administrators can move buttons to the Associated Items, Unassociated Items, and Disassociated Items boxes. When saved, these individual phone button templates display on the Find and List Phone Button Template window.

User/Phone Add

The User/Phone Add Configuration window combines the necessary steps to configure a new end user with a new phone. The window also allows association of the new end user and new phone with a new or existing DN. Access this window from the User Management menu.

Addition does not succeed if you try to use an existing end user or an existing phone in this window. After you add the new end user and new phone, you can continue to configure the new end user in the End User Configuration window, and you can configure more details about the phone in the Phone Configuration window and about the DN in the Directory Number Configuration window.

System Menu Changes

The following changes occurred in the System menu:

Cisco Unified CallManager—You no longer can add or delete a Cisco Unified CallManager server.

New fields for SIP phones.

Phone NTP Reference (new)

Date/Time Group—New list box to add Phone NTP References

Presence Group (new)

Region—The audio codec and video call bandwidth support two new options: Keep Current Setting and Use System Default.

Dynamic Host Configuration Protocol (DHCP) (new)

DHCP Server

DHCP Subnet

Lightweight Directory Access Protocol (LDAP) (new)

LDAP System

LDAP Directory

LDAP Authentication

Location—New fields for RSVP settings

Cisco Unified Survivable Remote Site Telephony (SRST)—New fields for SIP settings

Multilevel Precedence and Preemption (MLPP) Domain (new)

Service Parameters (moved from Services menu). See the "Service Enhancements" section for more information.

Security Profile (new)

SIP Phone Security Profile

SIP Trunk Security Profile

SCCP Phone Security Profile

Application Server (new)

Application Server Type—Cisco Unity Voice Mail 4.x and Cisco Unity Connection 2.x

Licensing (new)

License Unit Report

License Unit Calculator

License File Upload

Call Routing Menu Changes (formerly Route Plan Menu)

The following changes occurred in the Call Routing menu:

Dial Rules

Application Dial Rules

Directory Lookup Dial Rules (new)

SIP Dial Rules (new)

SIP Route Pattern (new)

Client Matter Codes (moved from Feature > Client Matter Codes)

Forced Authorization Code (moved from Feature > Forced Authorization Code)

Call Park (moved from Feature > Call Park)

Call Pickup Group (moved from Feature > Call Pickup)

Directory Number (moved from Device > Phone > Add a New Phone)

Can add a range of DNs

Partition is now called Route Partition.

ASCII Alerting Name

Associated Devices lists all devices that use this DN (shared line).

Presence Group

Secondary Calling Search Space for Call Forward All

Forward on CTI Failure

Related Links drop-down list box includes Create Cisco Unity Voice Mailbox.


Note The Phone Directory Number Configuration window includes some DN settings; for example, Call Waiting and Ring Settings.


Meet-Me Number/Pattern (moved from Feature > Meet-Me Number Pattern)

Dial Plan Installer (new)

Media Resources Menu

Media Resources designates a new Cisco Unified CallManager Administration menu item and combines the menu items that were previously under Service > Media Resource.

Voice Mail Menu

Voice Mail designates a new Cisco Unified CallManager Administration menu item and combines the menu items that were previously under Feature > Voice Mail.

Device Menu Changes

The following changes occurred in the Device menu:

The release removed Add a New Device from the Device menu.

Trunk

SIP WSM Connection will be used for a future product.

SIP Trunk contains new fields.

Gateway

AS-2, AS-4, AS-8 no longer get supported.

IAD 2420 no longer gets supported.

Cisco 1880 gets supported.

Phone

Additional search options on the Find/List Phones window

Removal of Allow Wildcards check box on Find and List Phone window

Copy with Lines

Additional Phones available

SCCP and SIP options

Common Phone Profile

Protocol Specific Information—Packet Capture Mode, Packet Capture Duration, Presence Group, SCCP or SIP Phone Security Profile, SUBSCRIBE Calling Search Space, Unattended Port, Require DTMF, RFC2833 Disabled, SIP Dial Rules, MTP Preferred Originating Codec, Rerouting Calling Search Space, SIP Profile, Digest User, Require DTMF Reception, Media Termination Point Required

Changes to Certification Authority Proxy Function (CAPF)

Secure Shell Information

Association Information—Takes you to Directory Number Configuration window. Shared lines no longer display in red text; shared line information displays in the Device Information area in the Update Shared Device Settings.

For more information about the changes that are on the Phone and Directory Number Configuration windows, see the "Line and Phone Configuration Improvements" section.

Device > Device Settings

Device Defaults (moved from System menu)

Phone Services (moved from Feature menu)

SIP Profile (new)

Common Phone Profile (new)

CAPF Report (removed)

Application Menu Changes

The following changes apply in the Application menu:

Cisco Unified CM Assistant Configuration Wizard (moved from Service menu)

Cisco Unified CM Attendant Console (moved from Service menu)

Pilot Point—New fields: Location, Media Resource Group, Network Hold MOH Audio Source, and User Hold MOH Audio Source, Queuing Enable check box, Queue Size, and Queue Hold Time. Removed fields: Partition, Calling Search Space, Pilot Number (DirN)

Cisco Unified CM Attendant Console User (no change)

Cisco Unified CM Attendant Console User File Upload (new)

Hunt Group (removed)

Cisco Unified CM Attendant Console Server (removed)

Plugins (formerly Install Plugins)

Update Plugin URL (removed)

Cisco Unified CallManager Serviceability (moved to Navigation bar; accessed by Go drop-down box)

Cisco Unified CallManager Bulk Administration (BAT) (moved to Bulk Administration menu)

User Management Menu

User Management designates a new Cisco Unified CallManager Administration menu item and combines the menu items that were previously under User.

Application User (new)—The Related Links drop-down list box includes a link for User Privilege Report.

End User (formerly under User > Add a New User)

The Related Links drop-down list box includes new links for Unified CM Assistant Manager, Unified CM Assistant, and User Privilege Report.

Application Profiles got removed, and devices and extension mobility get associated by using list boxes.

Devices get associated by clicking the Device Association button. Displaying all available devices changes from clicking the Select Device button to clicking Find from the User Device Association window.

Extension mobility provides several configuration options: profiles, presence group, SUBSCRIBE calling search space, and Allow Control of Device from CTI check box.

Certificate Authority Proxy Function (CAPF) Information

Permissions Information—Used for Roles and Groups

Role (performs similar function as User > Access Rights)

User Group (performs similar function as User > Access Rights > User Group)

The Related Links drop-down list box includes links for Assign Role to User Group and Roles.

User/Phone Add (new)

Application User CAPF Profile (new)

End User CAPF Profile (new)

SIP Realm (new)

Bulk Administration Menu

Bulk Administration designates a new Cisco Unified CallManager Administration menu item. Previously, BAT, which was installed as a plug-in, ran as a separate application within Cisco Unified CallManager. Bulk Administration contains the following menu items:

Upload/Download Files

Phones

Users

Phones & Users

Manager/Assistants

User Device Profiles

Gateways

Forced Authorization Codes

Client Matter Codes

Call Pickup Group

Job Scheduler

Tool for Auto-Registered Phone Support (TAPS)

For more information about the Bulk Administration application, see Cisco Unified CallManager Bulk Administration Features.

Service Parameter Changes

Cisco Unified CallManager 5.0 supports the following Bulk Administration related service parameter changes:

Default MTP Telephony Event Payload Type—This release removes this service parameter and adds it as a configuration option for SIP devices in the SIP Profile Configuration window. The default value equals 101 with range from 96 to 127.

Max Simultaneous Cisco CallManager Initializations (new)—Use this parameter to limit the number of Cisco CallManager services that can initialize at the same time.

Restart Cisco CallManager on Initialization Exception (new)—This parameter determines whether the Cisco CallManager service restarts if an error is encountered during initialization.

Cisco Messaging Interface (CMI)

Primary and backup CMI services—The Primary CMI gets specified in the CMI clusterwide service parameter, CallManager Name. The backup CMI service gets specified in the CMI clusterwide service parameter, Backup CallManager Name. Be aware that only the active CMI service handles the communication between CMI and Cisco Unified CallManager as well as CMI, and the voice-messaging system.

Release 5.0 differs from Release 3.x and 4.x where, in the previous releases, the CMI that resides on the node with the higher IP address represents the Primary CMI.

Data Cable—In windows, CMI uses serial ports COM1 or COM2 for SMDI messages. The default value specifies COM1. In release 5.0, CMI uses the USB port that connects through the USB-serial adapter for SMDI messages. The port name USB0 gets configured by default.

GUI changes—The following parameters now exist clusterwide:

CallManager Name

Backup CallManager Name

Voice Mail DN

Voice Mail Partition

Alternate DN (new)

Alternate DN Partition (new)

Where to Find More Information

Presence Group Configuration, Cisco Unified CallManager Administration Guide

Presence, Cisco Unified CallManager Features and Services Guide

DHCP Server Configuration, Cisco Unified CallManager Administration Guide

DHCP Subnet Configuration, Cisco Unified CallManager Administration Guide

LDAP System Configuration, Cisco Unified CallManager Administration Guide

LDAP Directory Configuration, Cisco Unified CallManager Administration Guide

LDAP Authentication Configuration, Cisco Unified CallManager Administration Guide

Understanding the Directory, Cisco Unified CallManager System Guide

Application Users and End Users, Cisco Unified CallManager System Guide

MLPP Domain Configuration, Cisco Unified CallManager Administration Guide

Phone NTP Reference Configuration, Cisco Unified CallManager Administration Guide

SIP Phone Security Profile Configuration, Cisco Unified CallManager Administration Guide

SIP Trunk Security Profile Configuration, Cisco Unified CallManager Administration Guide

SCCP Phone Security Profile Configuration, Cisco Unified CallManager Administration Guide

Application Server Configuration, Cisco Unified CallManager Administration Guide

License Unit Report Configuration, Cisco Unified CallManager Administration Guide

License Unit Calculator Configuration, Cisco Unified CallManager Administration Guide

License File Upload Configuration, Cisco Unified CallManager Administration Guide

Directory Lookup Dial Rules Configuration, Cisco Unified CallManager Administration Guide

SIP Dial Rules Configuration, Cisco Unified CallManager Administration Guide

Dial Rules Overview, Cisco Unified CallManager System Guide

SIP Route Pattern Configuration, Cisco Unified CallManager Administration Guide

Directory Number Configuration, Cisco Unified CallManager Administration Guide

Directory Numbers, Cisco Unified CallManager System Guide

Installing Dial Plans Configuration, Cisco Unified CallManager Administration Guide

SIP Profile Configuration, Cisco Unified CallManager Administration Guide

Common Phone Profile Configuration, Cisco Unified CallManager Administration Guide

Application User Configuration, Cisco Unified CallManager Administration Guide

End User Configuration, Cisco Unified CallManager Administration Guide

Role Configuration, Cisco Unified CallManager Administration Guide

Roles and User Groups, Cisco Unified CallManager System Guide

User Group Configuration, Cisco Unified CallManager Administration Guide

User/Phone Add Configuration, Cisco Unified CallManager Administration Guide

Application User CAPF Profile Configuration, Cisco Unified CallManager Administration Guide

End User CAPF Profile Configuration, Cisco Unified CallManager Administration Guide

SIP Realm Configuration, Cisco Unified CallManager Administration Guide

Understanding Session Initiation Protocol, Cisco Unified CallManager System Guide

Understanding Cisco Unified CallManager Trunk Types, Cisco Unified CallManager System Guide

Cisco Unified IP Phones, Cisco Unified CallManager System Guide

Understanding Video Telephony, Cisco Unified CallManager System Guide

Cisco Unified CallManager Bulk Administration Tool, Cisco Unified CallManager Administration Guide

Cisco Unified CallManager Bulk Administration Guide

Cisco Unified CallManager Features

The following sections describe the Cisco Unified CallManager 5.0 feature enhancements:

Call Forwarding Enhancements

Call Park

Call Pickup Group

CTI and CTI Super Provider

Dynamic Host Control Protocol (DHCP)

International Dial Plans

LDAP Directory Enhancements

Licensing

Personal Directory Enhancements

Phone NTP References for SIP Phones

Presence

Roles and User Groups

RSVP

Service Enhancements

SIP Line Side (Endpoints) Support

SIP Route Pattern

SIP Third-Party Phones

SIP Trunk Enhancements

URL Dialing

Video Telephony Enhancements

Voice Quality Metrics

Call Forwarding Enhancements

The Call Forward All (CFA) enhancement introduces a secondary Calling Search Space (CSS) for the Call Forward All field. The secondary CSS for CFA combines with the existing CSS for CFA to allow the support of alternate CSS system configuration.

When CFA is activated, only the primary and secondary CSS for CFA gets used to validate the CFA destination and redirect the call to the CFA destination. If these fields are empty, null CSS gets used. The combination of the line CSS and device CSS no longer gets used when CSS for CFA is None. Only CSS fields that are configured in the primary CSS for CFA and the secondary CSS for CFA fields get used.

For more information, refer to Cisco Unified CallManager Features and Services Guide 5.0.

Cisco Unified CallManager Administration Configuration Tips

You must configure either primary Forward All Calling Search Space or Secondary Forward All Calling Search Space or both for Call Forward All to work properly. The system uses these concatenated fields (Primary CFA CSS + Secondary CFA CSS) to validate the CFA destination and forward the call to the CFA destination.


Note If the system is using partitions and calling search spaces, Cisco recommends that the other call forward calling search spaces are configured as well. When a call is forwarded or redirected to the call forward destination, the configured call forward calling search space get used to forward the call. If the forward calling search space is None, the forward operation may fail if the system is using partitions and calling search spaces. For example, if the Forward Busy Destination is configured, the Forward Busy Calling Search Space should also be configured. If the Forward Busy Calling Search Space is not configured and the Forward Busy destination is in a partition, the forward operation will fail.


When you forward calls by using the Cisco Unified IP Phone User Options windows or the CFwdAll softkey on the phone, the automatic combination of the line CSS and device CSS does not get used. Only the configured Primary CFA CSS and Secondary CFA CSS gets used. If both of these fields are <None>, the combination results in two null partitions, which will cause the operation to fail.

If you want to restrict users from forwarding calls on their phones, you must choose a restrictive calling search space from the Forward All Calling Search Space field.

Migration automatically configures either one or both of these CSS for CFA fields based on the previous data.

If CFA is activated from the phone, the CFA destination gets validated by using the CSS for CFA, and secondary CSS for CFA, and CFA destination gets written to the database.

In previous releases, if the CSS for CFA is empty, the CFA destination got validated against the combination of the line CSS and device CSS of the phone. In Release 5.0, during CFA activation, the CFA destination always gets validated against the CSS for CFA and the secondary CSS for CFA.

GUI Changes

This release adds new drop-down list box to the Cisco Unified CallManager Administration Directory Number Configuration window. This field provides a secondary CSS for CFA. The combination of the CSS for CFA and secondary CSS for CFA gets used to activate and redirect a call to the CFA destination.

BAT Considerations

This release adds a new drop-down list box to Bulk Administration call forwarding and call pickup setting in Directory Number configuration window. This field provides a secondary CSS for CFA.

Where to Find More Information

Directory Number Configuration, Cisco Unified CallManager Administration Guide

Cisco Unified IP Phones, Cisco Unified CallManager System Guide

Call Park

Call Park provides the same functionality as in previous Cisco Unified CallManager releases.

Cisco Unified CallManager Administration Configuration Tips

Call Park now gets configured under the Call Routing menu. Additionally, this release removes the Allow Call Park Retrieval check box that was on the End User Configuration window and creates a new user group for Call Park users.

GUI Changes

Choose Call Routing > Call Park.

Add the users who will need access to Call Park to the Standard CTI Allow Call Park Monitoring user group. Choose User Management > User Group. Consider this a requirement for Attendant Console users.

Where to Find More Information

Call Park, Cisco Unified CallManager Features and Services Guide

User Group Configuration, Cisco Unified CallManager Administration Guide

Attendant Console Configuration, Cisco Unified CallManager Features and Services Guide

Call Pickup Group

Call Pickup Group provides the same functionality as Cisco Unified CallManager Release 4.1(3).

Cisco Unified CallManager Administration Configuration Tips

Call Pickup Group, which is now configured under the Call Routing menu, gets referred to as Call Pickup Group.

GUI Changes

Choose Call Routing > Call Pickup Group.

In Call Pickup Group Information section

Call Pickup Group Name (new field)

Call Pickup Group Number (changed: formerly Call Pickup Number)

In Associated Call Pickup Group Information, Find Pickup Numbers by Numbers/Partition section

This area allows you to search for associated call pickup groups by numbers and/or partitions of those groups. You can also add them to a list of associated call pickup groups.

In the Current Associated Call Pickup Groups section

You can change the order of the associated call pickup groups or remove them.

BAT Considerations

Bulk Administration provides Insert Call Pickup Groups and Delete Call Pickup Groups.

Where to Find More Information

Call Pickup Group, Cisco Unified CallManager Features and Services Guide

CTI and CTI Super Provider

The way devices and users get assigned to CTI applications changed. Administrators must add end users and application users to certain CTI user groups.

CTI supports Cisco Unified IP Phones 7911, 7941, 7961, 7970, and 7971 using SIP from the CTI interfaces JTAPI and TAPI, with some limited functionality. CTI applications control and monitor SIP phones in the same manner as CTI controlled/monitored SCCP phones.

Cisco Unified CallManager Administration Configuration Tips

Previous to Cisco Unified CallManager Release 5.0, two check boxes appeared on the User Configuration window. The check box, Enable CTI Application Use, provided users with access to CTI applications. The check box, Enable CTI Super Provider, provided CTI applications super provider capabilities to control all CTI-controllable devices.

Release 5.0 removed the check boxes and replaced them with user groups.

Administrators must use the following steps to correctly assign access for users and devices to CTI applications:

1. Add and configure an IP phone, CTI route points, or ports for each CTI application.

2. Configure the directory number for the CTI device.

3. Configure the end users and application users that will use CTI applications. Add the device that is used for CTI applications (for example, IP phone, CTI port) to the Controlled Devices lists that are on the End User and Application user Configuration windows.

4. Add the end users and application users to the Standard CTI Enabled user group.


Note All CTI users need to be in the Standard CTI Enabled user group, but they may also be in multiple CTI user groups.


5. If the application needs to control and monitor any CTI-controllable device, add that application user to the Standard CTI Allow Control of All Devices user group.

GUI Changes

The Enable CTI Application Use check box no longer appears on the User Configuration window.

The Enable CTI Super Provider check box no longer appears on the User Configuration window.

Use the Allow Control of Devices to CTI check box on the End User Configuration window for extension mobility. Check this check box to allow CTI to control devices that this end user owns. If the associated directory number specifies a shared line, ensure the check box is enabled as long as at least one associated device specifies a combination of device type and protocol that CTI supports.

End users and application users get access to CTI applications by being assigned to a CTI user group (User Management > User Group). The following CTI user groups exist in Release 5.0:

Standard CTI Allow Calling Number Modification—This user group allows an application to modify the calling party number in supported CTI applications.

Standard CTI Allow Control of All Devices—This user group allows an application to control or monitor any CTI-controllable device in the system (referred to as CTI super provider application).

Standard CTI Allow Reception of SRTP Key Material—This user group allows an application to receive information that is necessary to decrypt encrypted media streams. This group typically gets used for recording and monitoring purposes.

Standard CTI Enabled—This user group, which is required for all CTI applications, allows an application to connect to Cisco Unified CallManager to access CTI functionality.

Standard CTI Secure Connection—Inclusion into this group will require that the application have a secure (TLS) CTI connection to Cisco Unified CallManager if the Cisco Unified CallManager cluster security is enabled.

Standard CTI Allow Call Park Monitoring—This user group allows an application to receive notification when calls are parked/unparked to all Call Park directory numbers.


Note The CTI application must support the specified user group to which it gets assigned. Refer to the appropriate application documentation for more information.


Ensure CTI devices (such as IP phones and CTI ports) are associated with the user (User Management > End User).

CTI Considerations

See the "Migration Tips" section for information about CTI check boxes and user groups.

Where to Find More Information

Migration Tips

Computer Telephony Integration, Cisco Unified CallManager System Guide

Configuring Cisco Unified IP Phones, Cisco Unified CallManager Administration Guide

CTI Route Point Configuration, Cisco Unified CallManager Administration Guide

Application User Configuration, Cisco Unified CallManager Administration Guide

End User Configuration, Cisco Unified CallManager Administration Guide

User Group Configuration, Cisco Unified CallManager Administration Guide

Dynamic Host Control Protocol (DHCP)

Dynamic Host Configuration Protocol (DHCP) server enables Cisco Unified IP Phones, connected to either the customer data or voice Ethernet network, to dynamically obtain its IP address and configuration information. It uses Domain Name System (DNS) to resolve host names both within and outside the cluster.

You can configure one DHCP server for each node of each server, and multiple subnets can be configured for each server.

Cisco Unified CallManager Administration Configuration Tips

Because no migration is provided from Window 2000 based DHCP configuration to the DHCP configuration, the administrator needs to reconfigure the DHCP servers.

GUI Changes

Use the following new menu options in Cisco Unified CallManager Administration to configure DHCP servers and the DHCP subnets.

System > DHCP Server

System > DHCP Subnet

Serviceability Considerations

The following enhancements exist in Cisco Unified CallManager Serviceability for DHCP:

Serviceability provides an option to enable the DHCP functionality and to activate the DHCP Monitor Service on the node where the DHCP is enabled (Serviceability > Tools > Service Activation).

Serviceability provides an option to start and stop DHCP Monitor Service (Serviceability > Tools > Control Center - Feature Services).

Serviceability provides an option to change trace levels for DHCP monitor process (Serviceability > Trace > Configuration).

Serviceability provides an option to change alarm event level for DHCP (Serviceability > Alarm > Configuration).

Choose Serviceability > Alarm > Definitions to view new alarms that are defined for DHCP. This release adds two new alarms for DHCP:

CiscoDhcpdFailure

CiscoDhcpdRestarted

Where to Find More Information

DHCP Server Configuration, Cisco Unified CallManager Administration Guide

DHCP Subnet Configuration, Cisco Unified CallManager Administration Guide

Dynamic Host Configuration Protocol, Cisco Unified CallManager System Guide

International Dial Plans

Cisco Unified CallManager supports non-NANP. The following sections provide information on the installation and changes that are made to dial plans in release 5.0.

Cisco Unified CallManager Administration Configuration Tips

Use the Dial Plan Installer menu item to install dial plans that are available on Cisco Unified CallManager publisher server (Call Routing > Dial Plan Installer). For more details, see Cisco Unified CallManager Administration Guide and Cisco Unified CallManager Dial Plan Guide.

Installation Considerations

Before you install a dial plan on the server, you should download the equivalent dial plan COP (Cisco Option Package) file to the Cisco Unified CallManager server.

You can find COP files for all the available dial plans that you can download, install, and integrate with Cisco Unified CallManager systems at the following URL:

http://www.cisco.com/cgi-bin/tablebuild.pl/IDP

For details on installing a COP file, see Cisco CallManager International Dial Plans Deployment Guide

GUI Changes

This release adds a new menu item, Dial Plan Installer (Call Routing > Dial Plan Installer), to the Call Routing menu in Cisco Unified CallManager Administration.

Serviceability Considerations

You must restart Cisco CallManager service every time that the dial plans are installed, upgraded, or uninstalled.

Maximum length: 255. IDP uses Cisco RTMT Web Service for writing the trace files.

Where to Find More Information

Installing Dial Plans, Cisco Unified CallManager Administration Guide

Cisco CallManager International Dial Plans Deployment Guide

LDAP Directory Enhancements

The Lightweight Directory Access Protocol (LDAP) provides applications with a standard method for accessing and potentially modifying the information that is stored in the directory. This capability enables companies to centralize all user information in a single repository, available to several applications, with a reduction in maintenance costs through the ease of adds, moves, and changes.

Cisco Unified CallManager Administration documentation covers the main principles for synchronizing Cisco Unified CallManager with a corporate LDAP directory. The documentation also discusses the administrator choice not to synchronize with a corporate LDAP directory and the consequences of that choice of configuration. The documentation also summarizes considerations for providing Cisco Unified Communications endpoints, such as Cisco Unified IP Phones and Cisco IP SoftPhone, with access to a corporate LDAP directory.

The following list summarizes the changes in directory functionality from previous releases of Cisco Unified CallManager:

This release decoupled the directory component from Cisco Unified CallManager to ensure high Cisco Unified CallManager availability independent of the corporate directory.

Cisco Unified CallManager and related applications store all application data in the local database instead of in an embedded directory. The embedded directory gets removed, and Cisco Unified CallManager supports synchronization with the customer directory.

Cisco Unified CallManager Administration Configuration Tips

The following sections discuss the changes to Cisco Unified CallManager Administration that relate to changes in directory functionality.

You can only configure new end users if the synchronization from the LDAP server is disabled. To disable synchronization, choose the System > LDAP > LDAP System menu option and ensure that the Enable Synchronization from LDAP Server check box is unchecked.

The Cisco Unified CallManager Data Migration Assistant (DMA) provides conversion of Cisco Unified CallManager 4.x data to a format that is compatible with Cisco Unified CallManager 5.0. For details on obtaining, installing, and using DMA, refer to the Cisco Unified CallManager Data Migration Assistant 1.0 User Guide.

GUI Changes

This release eliminates the following menu options from previous releases of Cisco Unified CallManager Administration:

User > Add a New User

User > Global Directory

The following new menu options in this release of Cisco Unified CallManager Administration relate to configuration of directory information:

System > LDAP > LDAP System

System > LDAP > LDAP Directory

System > LDAP > LDAP Authentication

User Management > Application User

User Management > End User

The menu options allow the following basic functionality:

The System > LDAP > LDAP System menu option causes the LDAP System Configuration window to display. Use this window to enable or disable synchronization from the LDAP server and to configure the LDAP server type and the LDAP attribute for user ID.

The System > LDAP > LDAP Directory menu option causes the Find and List LDAP Directories window to display. Use this window to configure various attributes of LDAP directories.

The System > LDAP > LDAP Authentication menu option causes the LDAP Authentication window to display. Use this window to enable or disable LDAP authentication for end users as well as to provide LDAP server information.

The User Management > Application User menu option causes the Find and List Application Users window to display. Use this window to find application users or click Add New to add a new application user. On the Application User Configuration window, use the User Privilege Report link from the Related Links drop-down list box at right to view the user group, role, and resources that are associated with a specified application user.

The User Management > End User menu option causes the window to display. Use this window to find an end user or click Add New to add a new end user. On the End User Configuration window, use the User Privilege Report link from the Related Links drop-down list box at right to view the user group, role, and resources that are associated with a specified end user.

Service Parameter Changes

Changes to directory functionality affect the service parameters that are associated with the DirSync service.

Where to Find More Information

LDAP System Configuration, Cisco Unified CallManager Administration Guide

LDAP Directory Configuration, Cisco Unified CallManager Administration Guide

LDAP Authentication Configuration, Cisco Unified CallManager Administration Guide

Application User Configuration, Cisco Unified CallManager Administration Guide

End User Configuration, Cisco Unified CallManager Administration Guide

Understanding the Directory, Cisco Unified CallManager System Guide

Application Users and End Users, Cisco Unified CallManager System Guide

Cisco Unified CallManager Data Migration Assistant 1.0 User Guide

Licensing

Licensing in Cisco Unified CallManager Administration accurately tracks the number of devices that a customer has connected to Cisco Unified CallManager, including third-party SIP phones, and compares it with the number of unit licenses that have been purchased. License Configuration manages licenses for phones and nodes (Cisco Unified CallManager servers); it provides a calculator for determining how many and which types of devices are configured, and it includes a mechanism for uploading licenses files from a client PC.

Cisco Unified CallManager Administration Configuration Tips

Cisco Unified CallManager Administration provides a new system configuration option for licensing.

GUI Changes

The menu options in Cisco Unified CallManager Administration help determine the current license capacity and provide a tool to calculate the number of licenses that are required.

The following three menu options exist in Cisco Unified CallManager Administration:

System > Licensing > License Unit Report

System > Licensing > License Unit Calculator

System > Licensing > License File Upload

Serviceability Considerations

The following enhancements exist in Cisco Unified CallManager Serviceability for Licensing:

Serviceability provides an option to start and stop the Cisco License Manager service (Serviceability > Tools > Control Center - Network Services).

Serviceability provides an option to change trace levels for licensing (Serviceability > Trace Configuration).

Serviceability provides an option to change alarm event level for licensing (Serviceability > Alarm Configuration).

Choose Serviceability > Alarm > Definitions to view new alarms that are defined for licensing. Release 5.0 adds these new alarms in the Java Applications catalog for licensing:

CiscoLicenseManagerDown

CiscoLicenseOverDraft

CiscoLicenseRequestFailed

CiscoLicenseDataStoreError

CiscoLicenseInternalError

CiscoLicenseFileError

Security Considerations

Because the database tables that contain licensing-related data are secured, you cannot modify these tables by using AXL or any other SQL with regular user privileges.

Where to Find More Information

Licensing, Cisco Unified CallManager System Guide

License Unit Report, Cisco Unified CallManager Administration Guide

License Unit Calculator, Cisco Unified CallManager Administration Guide

License File Upload, Cisco Unified CallManager Administration Guide

Personal Directory Enhancements

Unlike previous releases of Cisco Unified CallManager, the Personal Directory feature in Cisco Unified CallManager Release 5.0(2) does not require special administrative configuration, and the end user does not need to subscribe to this service.

Cisco Unified IP Phones (SCCP) that support Personal Directory:

Cisco Unified IP Phone 7970G/7971G-GE

Cisco Unified IP Phone 7961G/7961G-GE and 7941G/7941G-GE

Cisco Unified IP Phone 7960G/7961G and 7940G

Cisco Unified IP Phone 7911G

Cisco Unified IP Phone 7905G and 7912G

Cisco Unified IP Phones (SIP) that support Personal Directory:

Cisco Unified IP Phone 7970G/7971G-GE

Cisco Unified IP Phone 7961G/7961G-GE and 7941G/7941G-GE

Cisco Unified IP Phone 7911G

Cisco Unified CallManager Administration Configuration Tips

The system administrator must activate the Personal Directory feature in Cisco Unified CallManager Serviceability: from the Navigation drop-down list box that is on the Cisco Unified CallManager 5.0(2) window, choose the Serviceability option and click Go; the Serviceability Application window displays. Administrators must also download the Address Book Synchronization Tool (TABSynch) from the Cisco Unified CallManager Plugins window and provide TABSynch to the user. After the system is configured, the system administrator provides the end users with the URL that is required to access the application from the User Options web pages:

http://server_name/CCMUser/

where server_name specifies the host on which the web server is installed.

GUI Changes

Administrator must download the Address Book Synchronization Tool (TABSynch) from the Cisco Unified CallManager Plugins window (Applications > Plugin).

User Tips

Users can access Personal Directory from

A web browser (Cisco Unified CallManager User Options)

A Cisco Unified IP Phone

Microsoft Windows application (assuming that the administrator provided the user with the TABSynch tool)

Using Personal Directory—Personal Address Book and Fast Dials

Users can access Personal Directory:

On the phone—Choose Directories > Personal Directory on the phone and log in with Cisco Unified CallManager user name and PIN.

On the Web—Log in to Cisco Unified CallManager User Options and choose User Options > Personal Address Book or User Options > Fast Dials.

From either interface, users can choose a PAB entry from search results, then dial, edit, delete, or assign a Fast Dial code to the entry. Users can also create new entries.

Users can also choose a Fast Dial entry from search results, then dial or delete the entry. Users can also create "raw" Fast Dial entries that are not associated with PAB entries.

Using the Address Book Synchronization Tool

Users can use the Address Book Synchronization Tool (TABSynch) to synchronize their existing Microsoft Windows Address Book (if applicable) with their Personal Address Book. Users can then access entries from the Microsoft Windows Address Book from the Cisco Unified IP Phone and Cisco Unified CallManager User Options.

You must make the TABSynch tool available to your users if you want them to access it (see the Providing Information to Your Users Via a Website section in the phone administration guides).

Serviceability Considerations

The system administrator must start and stop the Personal Directory feature by using Cisco Unified CallManager Serviceability.

Choose Tools > Control Center - Network Services.

Choose the server.

Under Unified CM Services, locate Cisco Unified CallManager Personal Directory.

From the Control Center - Network Services window, users can start and stop the Personal Directory.

Where to Find More Information

Providing Information to Your Users Via a Website section in the phone administration guides

Phone NTP References for SIP Phones

You can configure phone Network Time Protocol (NTP) references in Cisco Unified CallManager Administration to ensure that a Cisco  IP Phone that is using SIP gets its date and time from an NTP server.

Cisco Unified CallManager Administration Configuration Tips

Because you can configure several phone NTP references in Cisco Unified CallManager Administration, Cisco Unified CallManager Administration allows you to locate specific phone NTP references; if you want to do so, you can configure the IP address of an NTP server that exists outside of the Cisco Unified CallManager system (System > Phone NTP Reference).

After you add the phone NTP references to Cisco Unified CallManager Administration, you must add them to a date/time group (System > Date/Time Group). In the date/time group, you prioritize the phone NTP references.

The date/time group configuration gets specified in the device pool (System > Device Pool), and the phone receives the phone NTP reference configuration from the device pool.

GUI Changes

The following new and changed windows in Cisco Unified CallManager Administration contain NTP server-related configuration settings:

Phone NTP Reference window (new)—Contains Name and Description settings.

Date/Time Group window (changed)—Contains the Selected phone NTP references (in highest priority) setting.

Where to Find More Information

Phone NTP Reference Configuration, Cisco Unified CallManager Administration Guide

Presence

When you configure Presence in Cisco Unified CallManager Administration, an interested party, known as a watcher, can monitor the real-time status of a directory number or SIP URI, a presence entity, from the device of the watcher.

A watcher can monitor the status of the presence entity (called presentity) with the following options:

Busy Lamp Field (BLF)/Speed-Dial buttons

Missed call, placed call, or received call lists in the directories window

Shared directories, such as the corporate directory

Call lists and directories display the BLF status for existing entries. When you configure BLF/Speed-Dial buttons, the presence entity displays as a speed dial on the device of the watcher.


Note For presence-supported SIP phones, you can configure directory numbers or SIP URIs as BLF/Speed-Dial buttons. For presence-supported SCCP phones, you can only configure directory numbers as BLF/Speed Dial buttons. Configure BLF/Speed-Dial buttons for the phone, user device profile, or autogenerated device profile. The BLF value does not have to be on the cluster.


To view the status of a presence entity, watchers send presence requests to Cisco Unified CallManager. After administrators configure presence features, real-time status icons display on the watcher device to indicate whether the presence entity is on the phone, not on the phone, status unknown, and so on.

Extension mobility users can use presence features on phones with extension mobility support.

Presence group authorization ensures that only authorized watchers can access the presence status for a destination. Because the administrator ensures that the watcher is authorized to monitor the destination when a BLF/Speed Dial is configured, presence group authorization does not apply to BLF/Speed Dials.


Note For SIP phones, presence group authorization also does not apply to any directory number or SIP URI that is configured as a BLF/Speed Dial that appears in a call list.


To allow presence requests from outside the cluster, administrators must configure the system to accept presence requests from the external trunk or application. You can assign presence groups to trunks and applications outside the cluster to invoke presence group authorization.

The SUBSCRIBE Calling Search Space determines how Cisco Unified CallManager routes presence requests that come from the trunk or the phone. The SUBSCRIBE Calling Search Space that is associated with an end user gets used for extension mobility calls.

Cisco Unified CallManager Administration Configuration Tips

Administrators configure the phone features that are associated with presence: BLF/Speed Dials, call lists, or both. Administrators also configure the system to accept presence requests from outside the cluster and configure presence groups and permissions to use presence group authorization.

This section lists tips that you can use when you are configuring presence groups for presence authorization.

To allow a watcher to monitor a destination, make sure that the presence group that is applied to the watcher that is originating the request, including application users, has permission to monitor the group that is applied to the presence entity. End users for supported applications, for example, Unified CM Assistant end users, also serve as watchers because the user requests status about a presence entity that is configured on the application.

To allow Cisco Unified CallManager to receive and route presence requests from the SIP trunk application, make sure that the Accept Presence Subscription check box is checked in the Application User window to authorize incoming SUBSCRIBE requests. If no presence group is applied to the application user, Cisco Unified CallManager uses the presence group that is applied to the trunk.

If you check the Accept Presence Subscription check box for an application user, but do not check the Accept Presence Subscription check box in the SIP Trunk Security Profile that is applied to the trunk, a 403 message gets sent to the SIP user agent that is connected to the trunk.

If you check the Accept Presence Subscription check box for an application user, but do not check the Enable Application Level Authorization check box in the SIP Trunk Security Profile that is applied to the trunk, a 403 message gets sent to the SIP user agent that is connected to the trunk.

If digest authentication is not configured for the SIP trunk, you can configure the trunk to accept incoming subscriptions, but application-level authorization cannot be initiated, and Cisco Unified CallManager will accept all incoming requests before performing group authorization.

If the SIP trunk uses digest authentication, as configured in the SIP Trunk Security Profile, incoming presence requests require authentication of the credentials from the sending device. When digest authentication is used with application-level authorization, Cisco Unified CallManager also authenticates the credentials of the application that is sending the presence requests.

After authorization and authentication is successful for a SIP trunk application, Cisco Unified CallManager performs group authorization to verify the group permissions that are associated with the presence request before accepting the request.

When an administrator decides to add or change a BLF/Speed Dial button for a SIP URI, the administrator ensures that the watcher is authorized to monitor that destination. If the system uses a SIP trunk to reach a SIP URI BLF target, the presence group that is associated with the SIP trunk applies.

When configuring a SIP URI as BLF/Speed Dial button, make sure the routing patterns are appropriately configured. Refer to SIP Route Pattern Configuration in the Cisco Unified CallManager Administration Guide.

Cisco Unified IP Phones (SCCP) that Support Busy Lamp Field (BLF) -Speed Dial

Cisco Unified IP Phone 7970G/ 7971G-GE

Cisco Unified IP Phone 7961G/7961G-GE and 7941G/7941G-GE

Cisco Unified IP Phone 7960G/7940G

Cisco Unified IP Phone Expansion Module 7914

Cisco Unified IP Phones (SCCP) that Support Busy Lamp Field (BLF) -Call List

Cisco Unified IP Phone 7970G/7971G-GE

Cisco Unified IP Phone 7961G/7961G-GE and 7941G/7941G-GE

Cisco Unified IP Phones (SIP) that Support Busy Lamp Field (BLF) -Speed Dial

Cisco Unified IP Phone 7970G /7971G-GE

Cisco Unified IP Phone 7961G/7961G-GE and 7941G/7941G-GE

Cisco Unified IP Phones (SIP) that Support Busy Lamp Field (BLF) -Call List

Cisco Unified IP Phone 7970G/7971G-GE

Cisco Unified IP Phone 7961G/7961G-GE and 7941G/7941G-GE

GUI Changes

The following new and changed windows in Cisco Unified CallManager Administration contain presence-related configuration settings:

Presence Group Configuration window (new)—Contains Name, Description, Modify Relationship to Other Presence Groups, and Subscription Permission settings.

End User Configuration window (new)—Contains the Presence Group and SUBSCRIBE Calling Search Space settings.

Application User Configuration window (new)—Contains the Presence Group setting and Accept Presence Subscription check box.

SIP Trunk Security Profile Configuration window (new)—Contains the Accept Presence Subscription, Enable Application-Level Authorization, and Enable Digest Authentication check boxes.

SIP Trunk Configuration window (changed)—Contains the Presence Group and SUBSCRIBE Calling Search Space settings.

Phone Configuration window (changed)—Contains the Presence Group and SUBSCRIBE Calling Search Space settings; contains the Add a new BLF SD link.

Directory Number Configuration window (changed)—Contains the Presence Group setting.

Phone Button Template Configuration window (changed)—Contains the Speed Dial BLF option in the Features drop-down list boxes.

Device Profile Window (changed)—The autogenerated device profile contains the Presence Group and SUBSCRIBE Calling Search Space settings as well as the Add a new BLF SD link; the user device profile contains the Add a new BLF SD link.

Service and Enterprise Parameter Changes

The following new service and enterprise parameters support presence:

BLF for Call List—This enterprise parameter specifies the default Busy Lamp Field (BLF) behavior for phones (enabled or disabled). Restart all services for the changes to take effect.

Default Inter-Presence Group Subscription—Used with the Cisco CallManager service, this service parameter sets a system default value to allow or disallow a watcher in one presence group to request the status of a directory number or SIP URI that is assigned to another group when Use System Default is selected in the Presence Group Configuration window.

Presence Subscription Throttling Threshold—Used with the Cisco CallManager service, this service parameter specifies the number of external presence subscriptions that are allowed. When the number of subscriptions exceeds the value that this parameter specifies, Cisco Unified CallManager rejects additional call list busy lamp field (BLF) subscriptions as well as additional presence subscriptions via the SIP trunk. This parameter works with the Presence Subscription Resume Threshold parameter.

Presence Subscription Resume Threshold—Used with the Cisco CallManager service, this service parameter defines a percentage of the value that is specified in the Presence Subscription Throttling Threshold service parameter. When the number of external presence subscriptions decreases to below the percentage that this parameter specifies, Cisco Unified CallManager ceases throttling and resumes accepting call list BLF subscriptions as well as presence subscriptions via the SIP trunk. This parameter works with the Presence Subscription Throttling Threshold parameter.

User Tips

Users can use the Busy Lamp Field (BLF) to determine the state of another phone line that is associated with a speed-dial button, call list, or directory listing on their phone,

Using BLF-Speed Dials

To see the state of a speed-dial line, users can check icons and button light behavior next to the speed-dial line:

 

+

 

Line is in-use.

 

+

 

Line is idle.

 

BLF indicator unavailable for this line.



Note Users of the Cisco Unified IP Phone 7960G and the Cisco Unified IP Phone 7940G see the appropriate icon only.


Using BLF-Call Logs

To see the state of a line that is listed in a call list or directory, users can check for the following icons:

 

Line is in-use.

 

Line is idle.

 

BLF indicator unavailable for this line.


Serviceability Considerations

You must restart all services after you configure the BLF for Call List enterprise parameter.

BAT Considerations

You can configure BLF in the BAT phone template.

Where to Find More Information

Presence, Cisco Unified CallManager Features and Services Guide

Roles and User Groups

Roles and user groups replace the concept of functional groups and user groups that were found in previous versions of Cisco Unified CallManager Administration.

The Cisco CallManager Administration application and other applications use roles and user groups to provide varying levels of privilege (access). This technique permits granting only the required privileges for a selected group of users and limits the configuration functions that users in a particular user group can perform.

Roles and user groups provide multiple levels of security to Cisco Unified CallManager Administration and to other applications. The resources that are available to the Cisco Unified CallManager Administration application and to other applications get grouped into roles. Each application comes with standard, predefined roles. Administrators can configure additional roles for an application. A role contains, for a particular application, the list of resources that an application comprises. For each resource that a role comprises, the administrator defines the access privilege. For each resource in the Cisco Unified CallManager Administration application, the privileges include read and update. Other applications specify other privileges.

After configuration of roles for an application, administrators can configure user groups. User groups comprises groups of users that share a common list of assigned roles. User groups comprise both application users and end users.

Updates to roles and to user groups generate audit logs of user logins and access and modifications to Cisco CallManager configuration data.

Cisco Unified CallManager Administration Configuration Tips

This section describes the changes to Cisco Unified CallManager Administration that allow administrators to configure roles and user groups.

Standard, predefined roles and user groups exist within Cisco Unified CallManager Administration. Administrators cannot update these standard roles nor standard user groups. Administrators can, however, copy a standard role or standard user group and use the copy as the basis for creating a new role or new user group.

GUI Changes

Use the following Cisco Unified CallManager Administration menu options to configure roles and user groups:

User Management > Role—This menu option yields the Find and List Roles window. Use this window to search for existing roles or click Add New to add a new role.

User Management > User Group—This menu option yields the Find and List User Groups window. Use this window to search for existing user groups or click Add New to add a new user group.

The User Management > Role and User Management > User Group menu options replace the following menu options that existed in previous versions of Cisco Unified CallManager Administration:

User > Access Rights > Functional Group

User > Access Rights > User Group

User > Access Rights > Assign Privileges to User Group

User > Access Rights > Configure MLA Parameters

Enterprise Parameter Changes

Roles and user groups change the following enterprise parameters.

New Enterprise Parameters

The Effective Access Privileges For Overlapping User Groups and Roles enterprise parameter designates a new enterprise parameter under the User Management Parameters grouping.

Removed or Changed Enterprise Parameters

This release removed or changed the following enterprise parameters:

User Group Base (removed)

Administrative User Base (removed)

Debug Level (removed)

Effective Access Privileges For Overlapping User Groups (replaced) (See the New Enterprise Parameters for the replacement enterprise parameter.)

Effective Access Privileges For Overlapping Functional Groups (replaced) (See the New Enterprise Parameters for the replacement enterprise parameter.)

Enable MultiLevelAdmin (removed)

User Cache Flush Timeout (Minutes) (removed)

Serviceability Considerations

Updates to roles and to user groups generate audit logs of user logins and access and modifications to Cisco CallManager configuration data.

Where to Find More Information

Role Configuration, Cisco Unified CallManager Administration Guide

User Group Configuration, Cisco Unified CallManager Administration Guide

Roles and User Groups, Cisco Unified CallManager System Guide

RSVP

Resource Reservation Protocol (RSVP) designates a resource reservation signaling protocol for reserving resources in IP networks. RSVP messages travel along the same path as the media flow path. Because RSVP is unidirectional, flows get reserved in only one direction. Because RSVP is receiver-oriented, the receiver of the stream requests the reservation. (Two reservations, one for each direction, get made for each audio call.)

Previously, Cisco Unified CallManager used locations-based Call Admission Control (CAC) exclusively. RSVP provides an additional method of CAC. CAC preserves call quality by providing a method for rejecting an additional call that would degrade the quality of in-progress calls that are using a given set of resources.

RSVP provides guaranteed quality of service (QoS). RSVP preserves QoS and improves customer perception of IP voice calls. Network-aware RSVP can handle changes to routing or bandwidth, whereas location-based CAC cannot.

Location-based CAC supports only hub-and-spoke network topology. RSVP supports more complex network topologies, such as topologies that include the following entities:

Redundant links

More than three sites in a series

Multilevel hierarchies

Meshes

RSVP also supports the addition of video streams and their more complex bandwidth requirements to the resource reservation protocol. RSVP supports MLPP inherently.

Cisco Unified CallManager supports RSVP through an RSVP agent. RSVP supports all signaling protocols. RSVP works with all Cisco Unified CallManager supplementary services and features, such as Transfer, Conference, and Forwarding, to ensure that bandwidth reservation is correct after invocation of the feature or service.

RSVP does not support the following scenarios:

Reservations between clusters

RSVP-enabled endpoints

Device mobility

Cisco Unified CallManager Administration Configuration Tips

To configure RSVP, the administrator uses the Cisco Unified CallManager Administration Location and Service Parameter Configuration windows. See the following sections for more information.

GUI Changes

Use the following Cisco Unified CallManager Configuration windows to configure RSVP:

System > Location

RSVP Setting

System > Service Parameters

The following service parameters in the Clusterwide Parameters (System — RSVP) pane affect RSVP configuration:

Default Interlocation RSVP Policy

RSVP Retry Timer

Mandatory RSVP Mid-call Retry Counter

Mandatory RSVP mid call error handle option

RSVP Video Tspec Burst Size Factor

Other RSVP service parameters

Differentiated services code point (DSCP)-related service parameters

Administrators do not normally need to change the values of these service parameters.

Media Resources > Media Resource Group List

Assign a Media Resource Group List that includes RSVP Agent to the device or to the device pool that is associated with the device.

Service Parameter Changes

The following new service parameters support RSVP:

Clusterwide Parameters (System — QoS)

DSCP for audio calls when RSVP fails

DSCP for video calls when RSVP fails

Clusterwide Parameters (System — RSVP)

A variety of new service parameters

User Tips

Cisco does not recommend activating both location-based CAC and RSVP at the same time, except during the migration period from location-based CAC to RSVP.

During the RSVP deployment time period, devices in some Cisco Unified CallManager locations will have RSVP Agent resource configured, and devices in other locations will not have RSVP Agent configured. In cases where a call gets made from an RSVP location to a non-RSVP location, Cisco Unified CallManager will manage the call QoS by using both location-based CAC and RSVP.

Serviceability Considerations

Cisco Unified CallManager Serviceability provides location-based and node-based PerfMon counters for RSVP admission control. The PerfMon counters do not synchronize across nodes.

Cisco Unified CallManager Serviceability also provides PerfMon counters for RSVP Agent resources (media termination points and transcoders).

A new alarm indicates that no RSVP agent resource is available.

Cisco Unified CallManager RSVP Reservation Failure SDL and SDI traces get generated.

CAR/CDR Considerations

The QoS/RSVP Agent feature adds the following CDR fields:

origRSVPAudioStat

destRSVPAudioStat

origRSVPVideoStat

destRSVPVideoStat

These CDR fields reflect the status of RSVP bandwidth reservation per audio or video stream.

Where to Find More Information

Resource Reservation Protocol, Cisco Unified CallManager System Guide

Location Configuration, Cisco Unified CallManager Administration Guide

Service Parameter Configuration, Cisco Unified CallManager Administration Guide

Multilevel Precedence and Preemption, Cisco Unified CallManager Features and Services Guide

Cisco Unified CallManager Serviceability System Guide

Cisco Unified CallManager Serviceability Administration Guide

Service Enhancements

Cisco Unified CallManager Release 5.0 includes the following enhancements to Services:

Services get listed by type of service within Cisco Unified CallManager Serviceability. Main categories include Feature Services and Network Services.

Be aware that new services are available in Cisco Unified CallManager Serviceability for service activation and in Cisco Unified CallManager Service Parameter Configuration for setting and configuring parameters.

Feature Services—Unified CM Services

The following Services belong to the Unified CM Services group when Cisco Unified CallManager Serviceability is used:

Cisco Unified CallManager

Cisco TFTP

Cisco Messaging Interface

Cisco IP Voice Media Streaming App

Cisco CTIManager

Cisco CallManager Attendant Console Server (new)

Cisco Extension Mobility

Cisco Extended Functions

Cisco Unified CallManager Cisco Unified IP Phone Services (new)

Cisco Dialed Number Analyzer (new)

Cisco DHCP Monitor Service (new)

Feature Services—CTI Services

The following Services belong to the CTI Services group when Cisco Unified CallManager Serviceability is used:

Cisco IP Manager Assistant (IPMA) Service

Cisco Web Dialer Web Service

Feature Services—CDR Services

The following Services belong to the CDR Services group when Cisco Unified CallManager Serviceability is used:

Cisco SOAP - CDRonDemand Service (new)

Cisco CAR Scheduler (new)

Cisco CAR Web Service (new)

Feature Services—Database and Admin Services

The following Services belong to the Database and Admin Services group when Cisco Unified CallManager Serviceability is used:

Cisco AXL Web Service (new)

Cisco Bulk Provisioning Service (new)

Cisco Unified CallManager TAPS Service (new)

Feature Services—Performance and Monitoring Services

The following Services belong to the Performance and Monitoring Services group when Cisco Unified CallManager Serviceability is used:

Cisco Serviceability Reporter (new)

Cisco Unified CallManager SNMP Service (new)

Feature Services—Security Services

The following Services belong to the Security Services group when Cisco Unified CallManager Serviceability is used:

Cisco CTL Provider (new)

Cisco Certificate Authority Proxy Function

Feature services—Directory Services

Feature Services—Directory Services

The following Service belongs to the Directory Services group when Cisco Unified CallManager Serviceability is used:

Cisco DirSync (new)

Network Services—Platform Services

The following Services belong to the Platform Services group when Cisco Unified CallManager Serviceability is used:

A Cisco DB (new)

Cisco Tomcat

SNMP Master Agent (new)

MIB2 Agent (new)

Host Resources Agent (new)

Native Agent Adapter (new)

System Application Agent (new)

Cisco CDP Agent (new)

Cisco SysLog Agent (new)

Cisco Electronic Notification (new)

Cisco License Manager (new)

Cisco Certificate Expiry Monitor (new)

Network Services—DB Services

The following Service belongs to the DB Services group when Cisco Unified CallManager Serviceability is used:

Cisco Database Layer Monitor

Network Services—Unified CM Services

The following Services belong to the Unified CM Services group when Cisco Unified CallManager Serviceability is used:

Cisco Unified CallManager Admin (new)

Cisco Unified CallManager Serviceability (new)

Cisco Unified CallManager Personal Directory (new)

Cisco Log Partition Monitoring Tool (new)

Cisco CDP

Cisco Trace Collection Servlet

Cisco Trace Collection Service

Cisco RIS Data Collector

Cisco AMC Service (new)

Cisco Extension Mobility Application

Network Services—Performance and Monitoring Services

The following Services belong to the Performance and Monitoring Services group when Cisco Unified CallManager Serviceability is used:

Cisco Unified CallManager Serviceability RTMT

Cisco RTMT Reporter Servlet (new)

Cisco Tomcat Stats Servlet (new)

Network Services—SOAP Services

The following Services belong to the SOAP Services group when Cisco Unified CallManager Serviceability is used:

SOAP—Real-Time Service APIs (new)

SOAP—Performance Monitoring APIs (new)

SOAP—Log Collection APIs (new)

Network Services—Backup and Restore Services

The following Services belong to the Backup and Restore Services group when Cisco Unified CallManager Serviceability is used:

Cisco DRF Master (new)

Cisco DRF Local (new)

Network Services—CDR Services

The following Services belong to the CDR Services group when Cisco Unified CallManager Serviceability is used:

Cisco CDR Repository Manager (new)

Cisco CDR Agent (new)

Where to Find More Information

Cisco Unified CallManager Serviceability Administration Guide

Cisco Unified CallManager Serviceability System Guide

CDR Analysis and Reporting Administration Guide

Service Parameters Configuration, Cisco Unified CallManager Administration Guide

SIP Line Side (Endpoints) Support

The Cisco Unified IP Phones 7911, 7941, 7961, 7970, and 7971 for SIP deploy as a SIP endpoint in a Cisco Unified CallManager Back to Back User Agent (B2BUA) environment or in a SIP peer-to-peer network. SIP provides the primary interface between the phone and other network components. In addition to SIP, other protocols get used for various functions such as DHCP for IP address assignment, DNS SRV for domain name to address resolution, and TFTP for downloading image and configuration data.

The SIP line side feature affects Cisco Unified CallManager architecture, the TFTP server, and the Cisco Unified IP Phones. Because the SIP phone features are equivalent to the SCCP phone features, and they behave similarly, Cisco Unified IP Phones 7941/61/71/70/11 for SIP support all features. Cisco Unified IP Phones 7905/12/40/60 for SIP support a reduced feature set (for example, limited MOH and failover capabilities). SIP trunk side applications work for both SCCP and SIP phones.

Cisco Unified CallManager Administration Configuration Tips

To configure SIP line support, the administrator uses a variety of Cisco Unified CallManager Administration windows. See the following sections for detailed information.

Cisco SIP IP Phones Supported by Cisco Unified CallManager 5.0

Cisco Unified IP Phone 7905 (SIP)

Cisco Unified IP Phone 7912 (SIP)

Cisco Unified IP Phone 7940 (SIP)

Cisco Unified IP Phone 7960 (SIP)


Note The Cisco Unified IP Phones 7905, 7912, 7940, and 7960 for SIP have limited functionality in Cisco Unified CallManager. Refer to the appropriate SIP phone documentation for details.


Cisco Unified IP Phone 7911 (SIP)

Cisco Unified IP Phone 7941 (SIP)

Cisco Unified IP Phone 7961 (SIP)

Cisco Unified IP Phone 7970 (SIP)

Cisco Unified IP Phone 7971 (SIP)


Note The Cisco Unified IP Phones 7911, 7941, 7961, 7970, and 7971 for SIP have full functionality in Cisco Unified CallManager. Refer to the appropriate SIP phone documentation for details.


Configuration Similarities Between SCCP Phones and SIP Phones

Configure SIP and SCCP phones by using Cisco Unified CallManager Administration (Directory Number and Phone Configuration windows):

A majority of the fields on the Phone Configuration window stay the same for SIP and SCCP.

All fields on the Directory Number Configuration window stay the same for SIP and SCCP.

Protocol (SIP or SCCP) gets specified when a new phone type is added

You can reset and restart Cisco SIP and SCCP phones from the Cisco Unified CallManager Administration configuration windows

Configuration Differences Between SCCP Phones and SIP Phones

SCCP phones get device pool configuration from the TFTP server and get the rest of configuration information from the SCCP messages:

Includes Cisco Unified CallManager group (primary, secondary, tertiary), SRST, load info

SIP phones get all configuration from the TFTP server:

Device pool, line configuration, softkey, dial plan

SCCP phones do not have a local dial plan.

SIP phones can have a local dial plan:

If configured, the dial plan comprises either part of the configuration file or a separate file depending on the phone.

SCCP phones register by using TCP or TLS.

SIP phones register by using UDP, TCP, or TLS.

GUI Changes

Use the following Cisco Unified CallManager Configuration windows to configure SIP phones.

System > Cisco Unified CallManager Configuration

SIP Phone Port

SIP Phone Secure Port (used for Security)

Auto-Registration (if using)

Ensure the SIP auto registration enterprise parameter is set (System > Enterprise Parameters)

System > SRST Reference Configuration (optional)

SIP Network/IP Address

SIP Port

System > Phone NTP Reference Configuration (optional)

If configured, add NTP server to Date/Time configuration.

System > Presence Group (optional unless presence is needed)

System > Security Profile

SIP Phone Security Profile (Many default profiles from which to choose exist.)

Call Routing > Dial Rules > SIP Dial Rules Configuration (optional)

If configured, add to SIP IP Phone configuration.

Device > Device Settings > SIP Profile Configuration (A default profile exists.)

Add the SIP profile to the SIP IP Phone configuration.

Device > Phone Configuration:

Choose phone.

Choose SIP.

Choose the appropriate phone button template.

SIP dial rules (optional)

SIP Phone Security Profile

SIP Profile

Call Routing > Directory Number Configuration (can also be added from Phone Configuration)

Add to SIP Phone Configuration.

User Management > SIP Realm (optional unless security is needed)

Cisco Unified CallManager Configuration

The SIP Phone Port specifies the port number that Cisco Unified CallManager uses to ascertain SIP line registrations over TCP and UDP.

The SIP Phone Secure Port specifies the port number Cisco Unified CallManager uses to ascertain SIP line registrations over TLS.

Changes to either require the Cisco CallManager service to be restarted.

Use the default settings unless special requirements are needed.

SIP Phone Security Profile Configuration

Use the SIP Security Profile to specify transport type and port for registering SIP phones.

Transport Type field—This field represents the transport that Cisco Unified CallManager will accept. Only Cisco Unified IP Phones 7911, 7941, 7961, 7970, and 7971 for SIP will get configured with transport type. All other Cisco SIP phones only support UDP.

SIP Phone Port field—This field designates the signaling port that the phone listens on locally (voipControlPort). Difference exists from SIP Phone Port in Cisco Unified CallManager Configuration window.

SIP Dial Rules Configuration

With dial rules, a phone can send a SIP INVITE without the Dial softkey. Create one or more Dial Rules, each of which has one or more Patterns, and each of which has one or more Parameters. Configure the Dial Rule to a specific SIP phone. When the phone powers on or resets, it will upload its configuration and its dial rules based on MAC address.

When the SIP phone gets its configuration file from the TFTP server, that file will either contain the rules (Cisco Unified IP Phones 7905/7912) or that file will contain a pointer to another file that the phone will then upload from the TFTP server (Cisco Unified IP Phones 7940/7960, 7911, 7941, 7961, 7970, and 7971).

When a user makes a call, and if the digits the user dials match any pattern in the uploaded Dial Rules, the phone will send INVITE without waiting for the Dial softkey.

SIP Profile Configuration

Use SIP Profile parameters locally in the phone. In most cases, you can use the default values.

Add the SIP Profile (or use Default) to the SIP Phone configuration.

Phone Configuration (SIP Phone)

Choose Cisco phone that supports SIP:

Cisco Unified IP Phones 7905, 7911, 7912, 7940, 7941, 7960, 7961, 7970, 7971

Choose Third-party SIP Device (Basic) or Third-party SIP Device (Advanced) for third-party phone (if applicable).

Select SIP.

Although SIP phone configuration is similar to SCCP, differences exist in the Protocol Specific Information section:

Presence Group—Used for BLF, Missed/Placed calls

SIP Dial Rules—SIP dial plan downloaded to the phone.

SIP Profile

SIP Security Profile

Packet Capture Mode—Used for decrypting TLS packets

Digest User—Digest User needed for third-party phones.

Line configuration matches that of SCCP phone.

Device Defaults

Because device default entries for phones are protocol dependent, for example, you will see Cisco Unified IP Phone 7905 (SCCP) and Cisco Unified IP Phone 7905 (SIP) as device type and protocol.

New Service Parameters

SIP Station and Backup Server Keepalive Interval

SIP Station Keepalive Interval

SIP Station Realm

Clusterwide Parameters (Device - SIP)—Variety of new parameters

New Enterprise Parameter

Auto Registration Phone Protocol—Choose SCCP or SIP.

Removed or Changed Service Parameters

The SIP Profile includes the following service parameter:

Offhook to First Digit Timer

SCCP and SIP Phone Service Parameters Differences in Behavior

To achieve the same level of control that the Drop Ad Hoc Conference parameter settings provides for SCCP phone-initiated conference calls, the administrator can use a combination of the Conference Join Enabled SIP profile parameter and the Block OffNet to OffNet Transfer service parameter for conferences that are initiated on the SIP phone. (Because the SIP phone performs a transfer when it drops out of the conference call, the Block OffNet to OffNet Transfer can prevent toll fraud by not allowing two offnet phones to remain in the call.) For more information, see Conference Bridges in the Cisco Unified CallManager System Guide.

Call Rejection - When a call is made to SIP phone, the phone can choose to reject the call in which case, applications will see NewCallEvent followed by Disconnected call event for the line on SIP phone. This performs similar to RP rejecting the call.

For SIP phones, enbloc dialing is always used even if the user first goes off hook before dialing digits - the phone will wait until all the digits are collected before sending the digits to the Cisco Unified CallManager. This will result in new call event after enough digits are pressed on the phone to match one of the configured dialing patterns.

Applications should configure `out of band DTMF' on all devices to receive DTMF events.

Serviceability Considerations

Cisco Unified CallManager Serviceability provides the following Trace Configuration parameters for SIP line support:

Enable SIP Stack Trace

Enable SIP Call Processing Trace

BAT Considerations

The Bulk Administration Tool provides the following support for SIP endpoints:

Phones—Use the template to create SIP phones, use query to find SIP phones, and use Migrate Phones to migrate SCCP to SIP.

CAR/CDR Considerations

Cisco Unified CallManager generates two types of call statistics records: Call Detail Records (CDR) and Call Management Records (CMR).

Cisco Unified CallManager call control automatically generates Call Detail Records that are completely protocol independent.

Use the parameter, Call Diagnostics Enabled, for generating Call Management Records. These records contain the count of bytes that are sent and received, packets that are sent and received, jitter, latency, and lost packets. Unified CMRs sometimes get referred to as Diagnostics Records.

The SIP phone supports two proprietary headers for reporting of statistics. These headers get added to BYE messages and to the 200 response to a BYE message.

Security Considerations

Security affects SIP line support in a variety of ways. The following Cisco Unified CallManager Administration windows get used to configure security for SIP. For more information, see Security Features.

System > SIP Phone Security Profile

Device > Phone (add the SIP Phone Security Profile)

User Management > SIP Realm


Note Secure Survivable Remote Site Telephony (SRST) does not support SIP phones.


CTI Considerations


Note The CTI application registration state for SIP TNP phones with UDP transport may not be consistent with the actual registration state of the phone. This may happen when CTIManager determines that the Cisco Unified CallManager is down and shows the device is out of service, but because of the inherent delay in UDP to determine the lost connectivity, the phone may appear to be in service.


CTI functionality supports Cisco SIP IP Phones 7911, 7941, 7961, 7970, and 7971. CTI supports SIP phones from the existing CTI interfaces but supports the functionality that is needed by applications that are required to support SIP phones. The CTI interfaces (JTAPI, TAPI) remain unchanged but expose a new SIP phone device type to applications.

Existing applications do not get impacted if the SIP phones are not application-controlled via CTI, or if they are used, applications must ensure that they do not use any CTI functionality that is not supported for SIP phones.

SIP phones support the following Cisco CTI applications:

Contact Center (IPCC)

Media Services (Automated Attendant (AA), Interactive Voice Response (IVR), Cisco Unified Contact Center Express, Cisco Conference Connection (CCC))

Emergency Responder

Extension Mobility

Web Dialer

Quality Reporting Tool

Features that CTI does not support on SIP phones

The features that are not supported by CTI on SIP phones include

Set lamp mode

Display string

Device-based, application controlled softkeys

Play tone

Ringing notification

Device state notification - including

Keypad pressed - 0-9, *, #

Feature button pressed -

Lamp mode changed - Off/on/wink/flash/blink

Ring mode changed - Off/inside ring/outside ring/feature ring/flash only/precedence

Display changed - New text displayed

Onhook/off hook notification.

Call Park/Unpark - Request to park/unpark a specified call

CtiToneChangeNotify - Will not be supported other than for notification related to FAC/CMC.

Line Ringer Override - Overrides the current ringer setting for the specified line.

Ringing Notify - Provides notification that a line is ringing/unringing.


Note Cisco Unified IP Phones that use SIP that are configured to use User Datagram Protocol (UDP) as the transport mode (instead of TCP) will not support the device data pass-through functionality; for example, the Quality Reporting Tool (QRT) requires the data pass-through functionality, so it cannot be used with IP phones that are configured with UDP.


Where to Find More Information

Phone NTP Reference Configuration, Cisco Unified CallManager Administration Guide

SIP Phone Security Profile Configuration, Cisco Unified CallManager Administration Guide

Cisco Unified CallManager Configuration, Cisco Unified CallManager Administration Guide

SIP Dial Rules Configuration, Cisco Unified CallManager Administration Guide

Cisco Unified IP Phone Configuration, Cisco Unified CallManager Administration Guide

SIP Profile Configuration, Cisco Unified CallManager Administration Guide

Cisco TFTP, Cisco Unified CallManager System Guide

Dial Rules Overview, Cisco Unified CallManager System Guide

Cisco Unified IP Phones, Cisco Unified CallManager System Guide

Computer Telephony Integration, Cisco Unified CallManager System Guide

SIP Route Pattern

Cisco Unified CallManager uses SIP route patterns to route or block calls to foreign (with respect to this Cisco Unified CallManager node or cluster) hosts by using SIP trunks. SIP route patterns provide the mechanism to route SIP call-signaling messages on the basis of the host address information in the SIP URI.

The domain name or IP address provides the basis for routing. The administrator can add domains, IP addresses, and IP network (subnet) addresses and associate them to trunks (only). This method allows requests that are destined for these domains to be routed through particular SIP trunk interfaces.

The digit analysis infrastructure between release 4.x and 5.0 gets used extensively. The "match" logic that gets used in routing decisions for specific patterns remains exactly the same whether dealing with DNs, numeric route patterns, or new SIP route patterns. New pattern type values differentiate SIP route patterns from numeric (non-SIP) pattern types.

Similarities between (Numeric) Route Patterns and SIP Route Patterns

The following similarities between (Numeric) Route Patterns and SIP Route Patterns exist:

Both control the routing of calls.

Both have wildcard capabilities.

Differences between (Numeric) Route Patterns and SIP Route Patterns

The following differences between (Numeric) Route Patterns and SIP Route Patterns exist:

Formats significantly differ. Two different formats exist for SIP route patterns.

The system limits devices that are associated with SIP route patterns to SIP trunks only.

Meta characters and wildcard options differ.

Numeric route patterns have more configuration options.

SIP route patterns operate with respect to host address information. Numeric route patterns (in the case of SIP calls) operate with respect to user information.

You cannot route SCCP calls by using SIP route patterns. You can route SIP calls by using either SIP or numeric route patterns.

Cisco Unified CallManager Administration Configuration Tips

The following changes occurred in the GUI.

GUI Changes

Use the following Cisco Unified CallManager Administration configuration windows to configure SIP route patterns.

Call Routing > SIP Route Pattern allows you to create a new SIP route pattern.

The Find/List SIP Route Pattern window allows you to search for a SIP route pattern that has already been created, or you can click the Add button to add a new SIP route pattern.

The SIP Route Pattern Configuration window allows you to set up the new SIP route pattern. Two types of patterns exist: domain and IP address.

Sample domain pattern: cisco.com and *.com

Sample IP address pattern: 172.18.201.119 or 172.18.201.119/32 (includes explicit IP host address)

The SIP Route Pattern Configuration window includes a new field called Transformations:

Used to configure Calling Party and Connected Party

Works the same as before, but only on numeric User URI information

You must create a SIP trunk first, so it can be added to the SIP route pattern.

Enterprise Parameters

SIP route patterns support the following enterprise parameters, which are used to decide whether host address is local or foreign:

Organization Top Level Domain

Cluster Fully Qualified Domain Name

Serviceability Considerations

SIP route pattern supports new Trace messages:

Indication of the type of match operations that DA is performing

Indication of received host address being a foreign host

Where to Find More Information

SIP Route Pattern Configuration, Cisco Unified CallManager Administration Guide

SIP Trunk Configuration, Cisco Unified CallManager Administration Guide

Understanding Route Plans, Cisco Unified CallManager System Guide

Understanding Session Initiation Protocol (SIP), Cisco Unified CallManager System Guide

SIP Third-Party Phones

Cisco Unified CallManager Release 5.0 supports Cisco IP Phones that are using SIP as well as SIP phones that third-party companies design to work with Cisco Unified CallManager.

Cisco Unified CallManager Administration Configuration Tips

Administrators use the following Cisco Unified CallManager Administration windows to configure third-party SIP phones:

Directory Number Configuration

SIP Profile Configuration (optional; can use the default SIP profile)

SIP Phone Security Profile Configuration (optional)

End User Configuration

Associate the Third-party SIP Device (Basic) or Third-party SIP Device (Advanced) phone in the Controlled Devices box

Phone Configuration

Choose Third-party SIP Device (Basic) or Third-party SIP Device (Advanced) as the third-party phone type.

Choose a user for the Digest User field. You must select a user that is not associated with an existing phone; otherwise, the phone will not successfully register with Cisco Unified CallManager. Also, be sure to use the same user ID on the phone.

Configure the SIP Profile.

In the SIP Phone Security Profile field, use one of the predefined Non-Secure SIP Profiles, or the Standard SIP Profile for Autoregistration, or configure a SIP phone security profile. Enable digest authentication if required.


Note Third-party SIP Device (Basic) supports one line and consumes three license units, and Third-party SIP Device (Advanced) supports up to eight lines and video and consumes six license units.


GUI Changes

The Phone Configuration window includes two new phone types: Third-party SIP Device (Basic) and Third-party SIP Device (Advanced).

User Tips

The third-party vendor documentation provides all user information.

BAT Considerations

BAT provides a Third-party SIP Device (Basic) and Third-party SIP Device (Advanced) option on the Phone Template window.

Security Considerations

See Security Features.

Where to Find More Information

Configuring Non-Cisco SIP Phones, Cisco Unified CallManager Administration Guide

SIP Trunk Enhancements

SIP trunks interoperate with other SIP user agents such as SIP gateways and proxy servers.

Media Termination Points

You no longer need MTPs on the SIP trunk for DTMF events if the endpoints can negotiate the use of RFC2833 or out-of-band DTMF methods end to end. You can configure Cisco Unified CallManager SIP trunks and third-party SIP phones always to use an MTP, but you should not configure Cisco Unified IP phones that are using SIP always to use an MTP. Doing so can cause problems with Cisco Unified CallManager features such as Shared Line.

If the configuration parameters are set to not use an MTP (default case) Cisco Unified CallManager will dynamically allocate an MTP if the DTMF methods for the call are not compatible. Thus little or no benefit exists in checking the "MTP Required" box for Cisco Unified IP Phones that are using SIP.


Note Although this configuration option for Cisco Unified IP Phones that are running SIP may be removed in a future CallManager release. It will continue to be supported for generic third-party SIP phones.


Retry as Audio

Retry as Audio pertains to outgoing SIP trunk calls and does not impact incoming calls. By default, the system specifies that this device should immediately retry a video call as an audio call (if it cannot connect as a video call) prior to sending the call to call control for rerouting.

If the default is changed, a video call that fails to connect as video does not try to establish as an audio call. The call then fails to call control, and call control routes the call via Automatic Alternate Routing (AAR) and/or route/hunt list.

Support for REFER Primitive

The system uses support REFER Primitive for SIP-initiated transfer features and other advanced transfer-related features such as Web Transfer and Click-to-Dial. Cisco Unified CallManager supports in-dialog and out-of-dialog REFER (incoming only).

Support for Replaces Header

Use Replaces header to logically replace an existing SIP dialog with a new SIP dialog.

Support for SUBSCRIBE/NOTIFY Event Reporting

This feature currently supports the Presence event package and KPML (for out-of-band DTMF).

Message Waiting Indicator (MWI)

SIP trunk supports message waiting indicator from the SIP voice-messaging server (Unity).

Video

SIP trunk supports the use of one video channel per call.

Multiple SIP Trunks per Incoming Port Number

You can configure SIP trunk with the same incoming port (no longer needs to be unique port number).

Enhanced SIP Redirection 3XX Support

The system passes 3XX Redirect messages to Cisco Unified CallManager digit analysis, instead of this being done at the SIP stack level.

Security

SIP trunk supports connections over Transport Layer Security (TLS) in addition to UDP and TCP, and it supports digest for authentication and authorization.

Call Preservation

Active calls that exist within a Cisco Unified CallManager cluster do not get interrupted when a Cisco Unified CallManager node fails or when communication between a device and its Cisco Unified CallManager node fails.

T.38 Fax Relay

The system supports both Fax Relay and Fax Passthrough. SIP trunk supports calls that start as a voice call and then switch to T.38.

RPID Enhancements

Calling party information gets enhanced to update the screen indicator, the privacy indicator for conference connected number, and to handle the connected party number for conferencing.

Out-of-Band (OOB) DTMF Handling

SIP trunk supports two OOB DTMF methods (KPML and Unsolicited NOTIFY) to reduce per-call MTP allocations.

SIP Standards Compliancy

Cisco SIP trunk complies with the following SIP standards:

RFC2976 SIP INFO Method—Supported. INFO method gets used for video media channels such as Picture Fast Update and Picture Freeze.

RFC2833 RTP Payload for DTMF Digits—Supported.

RFC2782 DNS SRV—Supported.

RFC3261 SIP—Supported

RFC3262 SIP Reliability of Provisional Responses—Supported

RFC3264 Offer/Answer Model for SDP—Supported

RFC3265 Specific Event Notification—Supported. Packages that are supported include KPML, Presence, REFER.

RFC3311 SIP UPDATE Method—Supported

RFC3515 SIP REFER Method—Partially supported. SIP trunk accepts inbound REFERs (in-dialog and out-of-dialog). Release 5.0 supports method=INVITE in the Refer-To header. Cisco Unified CallManager does not support multiple REFER requests within the same dialog.

RFC3842 SIP MWI Package—Partially supported. SIP trunk supports unsolicited NOTIFY events; it does not Subscribe for MWI events notification.

RFC3856 SIP PRESENCE Event Package—Supported

RFC3891 SIP Replaces Header—Supported. INVITE with Replaces and REFER with Replaces.

RFC4028 Session Timers in the SIP—Supported. For outgoing Invites, SIP trunk indicates the support via Supported header. For incoming Invites, it accepts the Supported and Session-Expires headers.

Cisco Unified CallManager Administration Configuration Tips

The following configuration tips apply to Cisco Unified CallManager Administration:

You cannot use SIP trunks as intercluster trunks because SIP trunks do not provide the same feature parity as the existing H.323 ICT (for example, SIP trunks do not support Q.SIG tunneling and SRTP).

GUI Changes

The following GUI changes occurred:

Packet Capture Mode drop-down list box for TLS debugging

The Media Termination Point Required check box allows you to indicate whether an MTP should be allocated. Default specifies unchecked.

Retry Video Call as Audio check box allows you to indicate whether a video call, if not connected, should be retried as an audio-only call.

A new section, SIP Information, displays and contains the following fields:

Destination Address is an SRV Destination Port

MTP Preferred Originating Codec

Destination Presence Group

SIP Trunk Security Profile

Rerouting Calling Search Space (associated with the in-dialog and out-of-dialog Rerouting)

Out-of-Dialog Refer Calling Search Space (associated with the in-dialog and out-of-dialog REFER)

SUBSCRIBE Calling Search Space (associated with the in-dialog and out-of-dialog Presence)

SIP Profile

DTMF Signaling (To minimize MTP usage, Cisco recommends Best Effort, which is the default.)

Service Parameter Changes

This release removed the following Cisco Unified CallManager service parameter from the Service Parameter Configuration window and added it to the SIP Profile Configuration window:

SIP Default Telephony Event Payload Type—This field specifies the default payload type for RFC2833 telephony event. See RFC 2833 for more information. In most cases, the default value specifies the appropriate payload type. Be sure that you have a firm understanding of this parameter before changing it, as changes could result in DTMF tones not being received or generated through the SIP trunk. The default value specifies 101 with range from 96 to 127.

TFTP Enhancements

TFTP enhancements include support for SIP and for centralized TFTP in a multiple cluster environment.

SIP Support

When the SIP phone configuration gets changed, the Cisco Unified CallManager database notifies the TFTP server to rebuild some or all of the configuration files. The TFTP server retrieves information from the Cisco Unified CallManager database and converts it into the proper output format, according to the device type, and saves the output either in TFTP cache or on the disk.When the TFTP server gets a request, it searches either the cache or hard disk to serve the requested configuration file or default files.

The TFTP support for SIP phones builds and serves different formats of SIP configuration files from the Cisco Unified CallManager database for the following SIP IP phones:

Cisco Unified IP Phones 7970/71, 7961, 7941, and 7911 (These phones share the same SIP configuration file format.)

Cisco Unified IP Phones 7960 and 7940 (These phones share the same SIP configuration file format.)

Cisco Unified IP Phones 7905 and 7912

SIP dial plans on the preceding phones

Softkey templates on the preceding phones

Centralized TFTP in a Multiple Cluster Environment

A Centralized TFTP server supports multiple clusters within one large campus environment. The Centralized TFTP server allows phones to be moved from one building to another within a campus. It also supports a mixed OS multicluster environment.

Devices that are registered and configured in any cluster can home into a single TFTP server (Centralized TFTP server) that will then serve files to those devices.

Cisco Unified CallManager Administration Configuration Tips

The following changes occur in Cisco Unified CallManager Administration:

Changes to Alternate TFTP Path

Customizing and Modifying Configuration Files

Changes to Alternate TFTP Path

Similar to the Windows environment, Release 5.0 supports a different directory, but it must be on the same server where the TFTP service is running. Also, no mounted directory exists in 5.0.

Release 5.0 allows alternate path to now be a remote server. The syntax can follow either of the following examples:

host://<IP of the off-cluster TFTP server> (for example, host://10.89.134.24)

HOST://<IP of the off-cluster TFTP server> (for example, HOST://10.89.134.24)

The system does not allow any other syntax.

Customizing and Modifying Configuration Files

You can modify configuration files (for example, edit the xml files) and add customized files (for example, custom ring tones, callback tones, phone backgrounds) to the TFTP directory. You can modify files and/or add customized files to the TFTP directory in Cisco Unified Communications Platform Administration, from the TFTP Server File Upload window. Refer to the Cisco IP Telephony Platform Administration Guide for information on how to upload files to the TFTP folder on a Cisco Unified CallManager server.

Serviceability Considerations

The TFTP server provides counters in Cisco Unified CallManager Serviceability for troubleshooting purposes. See the Cisco Unified CallManager Serviceability System Guide and the Cisco Unified CallManager Serviceability Administration Guide for more information.

Where to Find More Information

Cisco TFTP, Cisco Unified CallManager System Guide

Cisco Unified CallManager Serviceability Administration Guide

Cisco Unified CallManager Serviceability System Guide

Cisco IP Telephony Platform Administration Guide

URL Dialing

The following Cisco Unified IP Phones (SIP) support URL dialing:

Cisco Unified IP Phones 7970G/7971G-GE

Cisco Unified IP Phones 7961G/7961G-GE and 7941G/7941G-GE

Cisco Unified IP Phones 7960G and 7940G

Cisco Unified IP Phones 7911G

Cisco Unified CallManager Administration Tips

You do not need to configure URL Dialing in Cisco Unified CallManager Administration.

User Tips

The following sections provide information on using URL dialing on Cisco Unified IP Phones.

Cisco Unified IP Phones 7970G/7971G-GE, 7961G/7961G-GE, 7941G/7941G-GE, and 7911G

To place a call from a URL entry in a call log on the Cisco Unified IP Phones 7970G/7971G-GE, 7961G/7961G-GE, 7941G/7941G-GE, and 7911G:

1. Choose > Missed Calls, Placed Calls, or Received Calls.

2. Highlight the URL entry that you want to dial.

3. If you need to edit the entry, press EditDial.

The icon appears and indicates that you can edit characters in the URL entry.

4. Press Dial.

For More Information

See "Using Call Logs" in the phone guides.

Cisco Unified IP Phones 7960G and 7940G

To place a call on the Cisco Unified IP Phones 7960G and 7940G by using alphanumeric strings containing letters, numbers, or symbols

1. Press NewCall > URL.

2. Enter the alphanumeric characters that you want to dial.

3. To make corrections to the entry, press <<, or to remove the entry completely, press Clear.

The icon appears and indicates that you can edit characters in the URL entry.

4. To complete the call, press Dial or press EndCall.

5. To return to standard dialing mode, press Number.

For More Information

See "URL Dialing" in the Cisco Unified IP Phone Guide for 7960G and 7940G for Cisco Unified CallManager 5.0 (SIP).

Video Telephony Enhancements

SIP video supports the following video calls by using the SIP Signaling Interface (SSI):

SIP to SIP

SIP to H.323

SIP to SCCP

SIP intercluster trunk

SIP video calls also provide media control functions for video conferencing.

Cisco Unified CallManager video supports the SIP, and both SIP trunks and lines support video signaling. SIP supports the H.261, H.263, and H.264 video codecs (it does not support the wideband video codec that the VTA uses).

Cisco Unified CallManager supports the use of H.264 codec within H.323 protocol.

The following table lists the types of audio codes that SIP interfaces support.

Codec
RTP Payload Type

G.711 mu-Law

0

GSM

3 (also referred to as GSM Full Rate)

G.723

4

G.711 a-Law

8

G.722

9

G.728

15

G.729

18 (support for combinations of AnnexA and AnnexB)


Some Media Termination Point (MTP) devices, which are used for RFC 2833, support multiple logical channels within a session. A logical channel could apply for audio or video. To support video channels, the MTP uses pass-through mode. Video pass-through gets enabled if the MTP supports both pass-through and multiple logical channels. Not all MTP devices support multiple logical channels and pass-through mode.

Cisco Unified CallManager Administration Configuration Tips

The following section describes the configuration that is needed for SIP devices to support video calls.

Configuring a SIP Trunk for Video Calls

Perform the following steps to enable video calls on a SIP trunk:

On the Trunk Configuration window in Cisco Unified CallManager Administration, ensure that the Retry Video Call as Audio check box is checked if you want the call to use audio when the video connection is not available.

Reset the trunk.

Service Parameter Changes

DSCP for video calls when RSVP fails

Intraregion Video Call Bandwidth Default

Interregion Video Call Bandwidth Default

RSVP Video Tspec Burst Size Factor

RSVP Video Application ID

Serviceability Considerations

This release makes the following serviceability performance monitoring counters available for the video enhancements:

Cisco SIP

VideoCallsCompleted

VideoCallsActive

Where to Find More Information

Understanding Video Telephony, Cisco Unified CallManager System Guide

Voice Quality Metrics

With Cisco Unified CallManager 5.0(2), system administrators can access a set of metrics to monitor voice quality and troubleshoot network problems. The Call Statistics screen on the phone displays counters, statistics, and voice quality metrics in the following ways:

During call—You can view the call information by rapidly pressing the question mark button twice.

After the call—You can view the call information that is captured during the last call by displaying the Call Statistics screen.


Note You can remotely view the call statistics information by using a web browser to access the Streaming Statistics.


To measure the voice quality of calls that are sent and received within the network, Cisco Unified IP Phones use statistical metrics that are based on concealment events.

Configuration Tips (for Administrators)

You can configure Cisco Unified IP Phones to collect call diagnostics and voice-quality metrics by setting a service parameter in Cisco Unified CallManager Administration as described in the following steps:

1. From Cisco Unified CallManager Administration, choose System > Service Parameters.

2. In Clusterwide Parameters (Device - General), locate the Call Diagnostics Enabled service parameter.

3. From the drop-down list box, choose one of the following states:

Enabled Only When CDR Enabled Flag is True

Enabled Regardless of CDR Enabled Flag

4. Click Save.

For more information about configuring service parameters in Cisco Unified CallManager Administration, refer to the Cisco Unified CallManager Administration Guide, the Cisco Unified CallManager System Guide, and the Cisco Unified IP Phone user and administration documentation.

How This Feature Affects the End User

When end users report poor voice quality on certain phone calls, administrators can use voice-quality metrics to assist with troubleshooting network problems.

Supported Phones

Cisco Unified IP Phones 7970G/7971G-GE (SCCP)

Cisco Unified IP Phones 7961G/7961G-GE (SCCP) and 7941G/7941G-GE (SCCP)

Cisco Unified IP Phones 7960G (SCCP) and 7940G (SCCP)

Cisco Unified IP Phone 7911G (SCCP)

Where to Find More Information

Cisco Unified IP Phone Administration Guides

Cisco Unified CallManager Administration Guide

Cisco Unified CallManager System Guide

Cisco Unified CallManager User Options Web Pages

Cisco Unified CallManager 5.0(2) provides the following changes to the Cisco Unified CallManager User Options window.

Addition of the Cisco Personal Communications Assistant Layer

End-users log in to the Cisco Personal Communications  Assistant and then choose User Options from the menu bar to navigate to User Options.

When logged in and viewing User Options, users access a User Guide, change the locale for the windows, and configure user-specific options such as Personal Address Book and Fast Dials.

To access phone-specific features, users must select a device after logging in (User Options > Device). When a device is selected, the user can access additional configuration options from the Related Links drop-down list, including speed dials, phone services, and line-specific options (call forwarding, message-waiting indicators, and ring patterns).

Redesigned User Interface

The redesigned Cisco Unified CallManager User Options windows have the same look-and-feel as Cisco Unified CallManager Administration. End users log in by using a Cisco Unified CallManager user ID and password.

To access User Settings, Directory features, a Personal Address Book, and Fast Dials, users choose User Options from the menu bar.

To access phone-specific features, users must choose a device after logging in (User Options > Device). When a device is chosen, users can access additional configuration options including speed dials, phone services, and line-specific options (such as call forwarding, message-waiting indicators, and ring patterns).

This release includes the following changes to the User Options functionality:

Users can create up to 500 Fast Dial entries and 500 Personal Address entries (previously limited to 99).

The system provides an ASCII Label field for phones that do not support double-byte character sets.

The Personal Address Book and Fast Dials features no longer get considered as services. Access these features directly on the phone from the Directory feature button, under the Personal Directory menu (see the "Personal Directory Enhancements" section).

Where to Find More Information

Cisco Unified IP Phone User Guides, Customizing Your Phone on the Web section (a separate guide, Customizing Your Cisco Unified IP Phone Guide on the Web, previously included this information).

Cisco Unified IP Phone Administration Guides, Providing Information to Users Via a Website section (now includes TABSynch instructions that you must provide to your users).

Cisco Unified CallManager Applications

The following sections describe the Cisco Unified CallManager 5.0 applications enhancements:

Cisco Call Back

Cisco Unified CallManager Attendant Console

Cisco Unified CallManager AutoAttendant

Cisco Unified CallManager Extension Mobility

Cisco Dialed Number Analyzer

Cisco Emergency Responder 1.3(1)

Cisco Unified CallManager Assistant

Cisco Unity Voice Messaging

Cisco Web Dialer

Client Matter Codes and Forced Application Codes

Multilevel Precedence and Preemption (MLPP)

Music On Hold

Quality Report Tool

Cisco Call Back

The Cisco Call Back feature allows you to receive call-back notification on your Cisco Unified IP Phone when a called party line becomes available.

User Tips

Release 5.0 of Cisco Unified CallManager supports the Cisco Call Back feature on the Session Initiation Protocol (SIP) Cisco Unified IP Phones 7970, 7971, 7961, and 7941.

The Cisco Unified IP Phones 7960 and 7940 do not support call back notification for on-hook/off-hook states.

Users receive call-back notification by pressing the Call Back softkey on a Cisco Unified IP  Phone 7970 that is using ,SIP phone in the same way as a Skinny Client Control Protocol (SCCP) phone. See the Cisco SIP IP Phone 7970 Guide for more information.

In previous releases, manually dialing a directory number (DN) on which Cisco Call Back notification had been activated would have the same effect as pressing the Dial softkey from the notification window. In Release 5.0, however, manually dialing a DN with Cisco Call Back notification on it has no effect on the call-back status.

Subscription Manager, a new component in Release 5.0, will replace the CTIManager service; therefore, you no longer require the CTIManager service for Cisco Call Back.

Suspend/Resume Feature Functionality

With Release 5.0, Cisco Call Back provides the ability to suspend the call-completion service if the user, who originated Cisco Call Back, is currently busy and receives call-back notification when the called party becomes available. When the originating user then becomes available, the call-completion service resumes for that user.

Where to Find More Information

Cisco Call Back, Cisco Unified CallManager Features and Services Guide

Cisco Unified CallManager Attendant Console

Cisco Unified CallManager Attendant Console, a client-server application, allows you to use a graphical user interface that contains speed-dial buttons and quick directory access to look up phone numbers, monitor line status, and direct calls.

For this release, new windows were added, and existing windows were modified, so administrators could configure features that they previously configured by editing files on the Cisco Unified CallManager server:

To configure functions that previously were supported by the Attendant Console Configuration Tool, including changing JTAPI Username and JTAPI password, entering queue size and queue hold time, and configuring circular and broadcast hunt groups, administrators configure new fields on the Cisco Unified CallManager Administration Pilot Point Configuration window and Cisco Unified CallManager Administration Service Parameter Configuration window.

To create dial rules and directory lookup rules, administrators use the Application Dial Rule Configuration window and the Directory Lookup Dial Rule Configuration window, respectively, rather than editing the DialRules.xml file.

To upload CorporateDirectory.txt files, Cisco Unified CallManager Administration contains a new Attendant Console User File upload window

Cisco Unified CallManager Administration Configuration Tips

The following sections describe the changes to Cisco Unified CallManager Administration windows and service parameters for Cisco Unified CallManager Attendant Console.

GUI Changes

The following new and changed windows support Cisco Unified CallManager Attendant Console:

Attendant Console User File Upload (new)—Allows users to upload CorporateDirectory.txt files if their user list is located on a directory server that is separate from the Cisco Unified CallManager server. To access, choose Application > Cisco Unified CM Attendant Console > Cisco Unified CM Attendant Console User File Upload.

Directory Lookup Dial Rule Configuration window (new)—Allows administrators to configure directory lookup rules rather than exiting an .xml file on the Cisco Unified CallManager server. This window resembles the Application Dial Rule Configuration window. To access, choose Call Routing > Dial Rules > Directory Lookup Dial Rules.

Pilot Point Configuration window (changed)—Contains the following new fields: Registration, IP Address, Description, Location, Media Resource Group List, Network Hold Audio Source, User Hold MOH Audio Source, Queuing Enable, Queue Size, and Queue Hold Time (seconds). In addition, the Route Calls drop-down list box contains Broadcast hunting and Circular hunting as new options. Many of these fields and options previously existed in the Attendant Console Configuration Tool. The Pilot Point Configuration window also contains a link to the Line Appearance Configuration window, so the administrator can choose a valid pilot point number rather than simply entering a number on the Pilot Point Configuration window itself.

Cisco Unified CallManager Service Parameter Configuration window (changed)—Contains JTAPI Username and JTAPI Password fields that previously existed in the Attendant Console Configuration Tool.

Add the ac user to the Standard CTI Enabled group and the Standard CTI Allow Call Park Monitoring group by using the User Group window (User Management > User Group.)

Make sure that you check the Allow Control of Device from CTI check box on the Phone Configuration window for each attendant phone. The system enables this field by default. If this check box is not checked for the attendant phone, call control does not come up for the attendant console.

Service Parameter Changes

The following new service parameter supports Cisco Unified CallManager Attendant Console:

JTAPI Username—Specifies the username that the Cisco Unified CallManager Attendant Console Server uses to log on to a CTI Device. The default specifies "ac." During an upgrade, Cisco Unified CallManager migrates the value for this field from the Attendant Console Configuration Tool.

User Tips

Consider the following information when setting up the Cisco Unified CallManager Attendant Console client application:

You cannot use SIP phones as attendant phones, but attendants can receive and handle calls from SIP phones.

The attendant console client displays the correct CFA status for all DNs. In previous releases, Cisco Unified CallManager Attendant Console could only display the correct CFA status in the Directory window if fewer than 10 search entries displayed in the window.

Users can import and export speed dials from the File menu on the client application.

If you are using a firewall, you can configure the Attendant Console Client CallBack Port field on the Basic tab of the Cisco Unified CallManager Attendant Console settings window to specify the port that the firewall should use to send callback messages to the attendant console client. To access this window, choose Edit > Settings from the application on the attendant PC.

CTI Considerations

You must associate the ac user to the Standard CTI Enabled users group (found on the Cisco Unified CallManager Administration User Group Configuration window). If you do not associate the ac user to this group, pilot points do not register, and the call control does not go up on the console.

Cisco Unified CallManager AutoAttendant

Cisco Unified CallManager AutoAttendant, a simple automated attendant, allows callers to locate people in your organization without talking to a receptionist. You can customize the prompts that are played for the caller, but you cannot customize how the software interacts with the customer.

Cisco Unified CallManager AutoAttendant comes bundled with Cisco Unified CallManager on the Cisco Unified CallManager 5-Agent Cisco Unified Contact Center Express bundle.

Cisco Unified CallManager Administration Configuration Tips

Cisco Unified CallManager AutoAttendant in CRS no longer exists as co-located on the server with Cisco Unified CallManager, and many associated functions that were performed on Cisco Unified CallManager now get performed on the CRS server. These functions include but are not limited to

Creating and updating CTI ports

Creating and updating CTI Route Points

Install Cisco Unified CallManager on an appliance-based system before you install Cisco Unified CallManager AutoAttendant on the CRS server.

Before you can use Cisco Unified CallManager AutoAttendant, you must configure Cisco Unified CallManager including configuring a Cisco Unified CallManager user for Cisco Unified CallManager AutoAttendant.

Where to Find More Information

Cisco Unified CallManager AutoAttendant, Cisco Unified CallManager Features and Services Guide

Cisco Unified CallManager Extension Mobility

The Cisco Unified CallManager Extension Mobility (EM) feature allows users to temporarily access their Cisco Unified IP Phone configuration such as line appearances, services, and speed dials from other Cisco Unified IP Phones.

Cisco Unified CallManager Administration Configuration Tips

The following sections comprise tips and information for configuring Cisco Extension Mobility.

URL Change

When creating the Cisco Extension Mobility IP phone service, you must enter a service URL. Release 5.0 makes a change in the URL with regards to the port number. Enter the following URL:

http://<IP Address of Extension Mobilityserver>:8080/emapp/EMAppServlet?device=#
DEVICENAME#

SIP Support for Extension Mobility

Cisco Extension Mobility supports only Cisco IP Phones 7911, 7941G, 7941G-GE, 7961G, 7961G-GE, and 7971 running SIP.

The following Cisco Unified IP Phones support Cisco Extension Mobility:

Cisco Unified IP Phones7970G/7971G

Cisco Unified IP Phone 7961G/41G and 7961GE/41GE (G = Non Gig; GE = Gig)

Change Notification Enhancements

This release provides change notification to the extension mobility application. When a change in activation or deactivation of the extension mobility service occurs, on any node, the database tables get updated with information that is required to build the service URLs. The database tables also get updated when extension mobility service parameters get modified. The EMApp service handles the change notification.

You no longer need to restart the Cisco Tomcat server after a change to extension mobility service parameters.

GUI Changes

Changes exist throughout Cisco Unified CallManager Administration, specifically to the add, update, insert, and continue buttons.

A new location exists for the Subscribe/Unsubscribe option. The option now appears in the upper, right corner of the window and is part of the Related Links drop-down list box. This option will become available after Cisco Extension Mobility is configured.

Cisco Extension Mobility now constitutes a deployable service.

Service Parameter Changes

A new service parameter, Clearing call logs, clears the call log (missed, received, placed) after every successful EM log in or log out. This action ensures privacy by preventing other users of the same phone from seeing the call logs of the previous user. Call logs get cleared only when you manually log in or log out, but no display shows that the login/logout was successful, as occurred in the previous release. Clearing call logs designates a clusterwide service parameter.

A change to the existing service parameter, Remember last logged in user, occurs with this release. When the field is set to True, all future logins will cause the user ID of the last successful logged-in user to automatically get filled in and remembered by Cisco Extension Mobility. You no longer need to restart the Cisco Tomcat server for a change to the service parameter value.


Note The last login user ID will not get migrated during an upgrade from Windows to Release 5.0.


User Tips

When a Cisco Unified CallManager Extension Mobility user logs out of a device, all Call Back services that are active on the Cisco Unified CallManager Extension Mobility user automatically cancel.

Serviceability Considerations

Cisco Unified CallManager Serviceability added four new performance counters. You can view them by using the RTMT tool:

EMAPP_ATTEMPTED_LOGIN_LOGOUT —This counter measures the total number of attempted login and logout requests and includes both successful and failed requests.

EMAPP_NO_OF_SUCCESS_LOGIN—This counter captures the successful login requests.

EMAPP_NO_OF_SUCCESS_LOGOUT—This counter captures the successful logout requests (No Autologouts).

EMAPP_NO_OF_THROTTLED_REQUESTS—This counter measures all throttled requests.

You must activate the following feature services from Cisco Unified CallManager Serviceability for EM to be enabled:

Cisco Extension Mobility

Cisco Unified CallManager

Cisco Unified IP Phone Services

You activate/deactivate these services from Cisco Unified CallManager Serviceability > Service Activation. Refer to the Cisco Unified CallManager Serviceability Administration Guide for more information.

Trace configuration for extension mobility changed in the new Log4j infrastructure, and the location of the trace files is not configurable. You should configure the trace settings from the Serviceability trace settings windows.

Where to Find More Information

Cisco Unified CallManager Extension Mobility, Cisco Unified CallManager Feature  and Services Guide

Cisco Dialed Number Analyzer

Dialed Number Analyzer (DNA) installs as a feature service along with Cisco Unified CallManager. The tool allows you to test a Cisco Unified CallManager dial plan configuration prior to deploying it. You can also use the tool to analyze dial plans after the dial plan is deployed. You can use Dialed Number Analyzer to test a dial plan by providing dialed digits as input. The tool analyzes the dialed digits and shows details of the calls. You can use these results to diagnose the dial plan, identify problems, if any, and tune the dial plan before it is deployed.

New and Changed Information for DNA

The following changes in DNA apply for Cisco Unified CallManager 5.0.

DNA supports Session Initiation Protocol (SIP) analysis for phones that support SIP and for SIP trunks.This release adds a new check box for SIP analysis to the Pattern Analysis field of the analyzer. Check the check box that corresponds to SIP Analysis, if applicable, and choose Domain Route or IP Route. If you want to perform a Session Initiation Protocol (SIP) analysis, make sure that you have configured a SIP Route Pattern in Cisco Unified CallManager Administration. For more details, refer to Cisco Unified CallManager Administration Guide.

Log files and trace files for DNA transactions get collected by using the trace and log central feature. The trace level (such as info, debug, error, and so on) information gets set by using Cisco Unified CallManager Serviceability for each service. Appropriate traces get written in the trace files based on the setting.

Logging on

You can access Dialed Number Analyzer by using Cisco Unified CallManager Serviceability and choosing Tools > Dialed Number Analyzer.

You can also access DNA from a remote PC by using a web browser (Internet Explorer 6.0 or later versions).

Use the following URL to access Dialed Number Analyzer:

https://<cm-machine>:8443/dna

where <cm-machine> specifies the node name or IP address on which Dialed Number Analyzer is installed.

Serviceability Considerations

The following enhancements exist in Serviceability for DNA:

Serviceability provides an option to activate/deactivate DNA Service (Serviceability > Tools > Service Activation).

Serviceability provides an option to start and stop DNA Service (Serviceability > Tools > Control Center - Feature Services).

Serviceability provides an option to change trace levels for DNA (Serviceability > Trace > Configuration).

Access DNA by using Cisco Unified CallManager Serviceability (Serviceability > Tools > Dialed Number Analyzer).

Where to Find More Information

Cisco Unified CallManager Dialed Number Analyzer Guide

Cisco Unified CallManager Administration Guide

Cisco Unified CallManager Serviceability Administration Guide

Cisco Unified CallManager Serviceability System Guide

Cisco Emergency Responder 1.3(1)

Cisco Emergency Responder (Cisco ER) 1.3(1) supports Cisco Unified CallManager 5.0(2) in addition to Cisco CallManager 3.3 and Cisco Unified CallManager 4.0, 4.1, and 4.2.

Ensure all Cisco ER servers are version 1.3(1). This allows Cisco ER to support multiple Cisco Unified CallManager 5.0(2) clusters. Cisco ER 1.3(1) will not work with previous versions of Cisco ER.

CER 1.3(1) supports upgrades from Cisco ER 1.2(1), Cisco ER 1.2(2), and Cisco ER 1.2(3).

Cisco ER 1.3(1) provides Windows-based support.

Where to Find More Information

Cisco Emergency Responder Administration Guide 1.3

Cisco Unified CallManager Assistant

Cisco Unified CallManager Assistant fully integrates into Cisco Unified CallManager Release 5.0.

Cisco Unified CallManager Administration Configuration Tips

Cisco Unified CallManager Release 5.0 Assistant features include the following configuration differences:

IIS no longer gets supported

Although Cisco Tomcat is still used, it does not represent an NT service.

Cisco Unified CallManager 5.0 supports one database, which also supports the directory information.

Cisco Unified CallManager Assistant supports Cisco Unified IP Phones 7940, 7941, 7960, 7961, 7970, and 7971, and Cisco IP Communicator.

Cisco Unified CallManager Assistant does not support SIP.

Partition Support—Cisco Unified CallManager Assistant supports the same line appearance (DN) in different partitions with the following configurations:

Lines with same DN but different partition gets treated as different lines.

Lines with same DN, same partition, and different devices gets treated as shared lines.

Lines with same DN and same partition on the same device do not get supported.

The Cisco Unified CallManager Assistant Manager Assistant configuration window displays the partition information next to the line number. The database stores this information.

Migration—When Cisco Unified CallManager is upgraded from a windows version, all Unified CM Assistant manager/assistant configuration migrate. The administrator must run the Data Migration Assistant (DMA) on the Windows platform prior to upgrading the platform to Release 5.0. It creates and exports a DMA tar ball of configuration data to be later installed onto the Release 5.0 platform during an upgrade.

For Cisco Unified CallManager Assistant in Proxy line mode, ensure the proxy line numbers on the assistant phone are unique, even though in different partitions.

For Cisco Unified CallManager Assistant in Proxy line mode, two managers cannot have the same Cisco Unified CallManager Assistant-controlled line number (DN), even though in different partitions.

GUI Changes

Cisco Unified CallManager Assistant supports the following GUI changes:

End User Configuration

Use to configure managers and assistants in Cisco Unified CallManager Assistant.

Cisco Unified IP Phone Service Configuration

The URL requires a port address:

http://

<server-ipaddress>:8080/ma/servlet/MAService?cmd=doPhoneService&Name=#DEVICENAME#

For example
http://123.45.67.89:8080/ma/servlet/MAService?cmd=doPhoneService&Name=#DEVICENAME#

Assistant Phone Configuration

Configure the assistant Cisco Unified IP Phones with the following settings:

Proxy lines for each configured manager with a voice-mail profile that is the same as the manager voice-mail profile

Cisco Unified CM Assistant Configuration Wizard

Choose Cisco Unified CallManager Assistant configuration wizard from Application > Cisco Unified CallManager Assistant Configuration Wizard.

Cisco Unified CallManager Assistant Configuration

Choose Cisco Unified CallManager Assistant Configuration from User Management > End User Configuration, as well as from the Cisco Unified CallManager Assistant Manager Configuration.

An optional configuration parameter exists on the Cisco Unified CallManager Assistant Manager configuration window: Primary Line. If configured, this line gets used as the default line to make external calls from the console.

New Service Parameters

See the "Security Considerations" section for more information.

User Tips

The Assistant Console application installation program supports Microsoft Internet Explorer (IE) 6.0 or later and Netscape 7.1 or later. The Manager Configuration application supports Microsoft IE 6.0 or later.

In Cisco Unified CallManager Assistant, the ImmDiv softkey on the manager phone causes behavior that differs from that of previous Cisco Unified CallManager Assistant versions.

With the Cisco Unified CallManager 5.0 release, if a manager who is using Cisco Unified CallManager Assistant receives an incoming call and presses the ImmDiv softkey, the call immediately gets diverted to a configured available assistant. However, if no assistant is available, the call gets diverted to the voice mailbox of the manager.

In previous versions of Cisco Unified CallManager Assistant, if a manager pressed the ImmDiv softkey and no configured assistant was available, the call did not get diverted to voice mailbox of the manager. Instead, the manager received a message that no configured assistant was available.

Installing the Assistant Console Application


Note When upgrading from Cisco Unified CallManager Release 4.0 or 4.1 to Release 5.0, you must reinstall the Assistant Console application.


Begin the installation by accessing the following URL:

https://<Cisco Unified CallManager Assistant server>:8443/ma/Install/ Cisco Unified CallManager AssistantConsoleInstall.jsp

where

Cisco Unified CallManager Assistant server specifies the IP address of the server that has the Cisco Unified CallManager Assistant service running on it.


Tip You can localize the installer (with the proper localization pack) by including the proper parameter on the URL; for example, for French, you would include the following parameter at the end of the URL:?locale=fr_FR.


Assistant Console Location

c:\Program Files\Cisco\Cisco Unified CallManager Assistant Console\

Manager Configuration URL

https://<server-name/ip>:8443/ma/desktop/maLogin.jsp

Cisco Unified CallManager Assistant Console

The console displays the partition information as a tool tip. Two lines with same directory number, but different partitions, appear as separate lines.

Serviceability Considerations

Cisco Unified CallManager Assistant supports the following capabilities for serviceability:

Cisco Unified CallManager Assistant_ChangeLog

The administrator can view a summary of changes that are made to the Manager or Assistant Configurations. A manager can change defaults by accessing the Manager Configuration from a URL.

An assistant can change the manager defaults from the assistant console.


Note Refer to the Cisco Unified CallManager Assistant User Guide for information about the URL and manager configuration.


When changes are made, the information gets sent to a log file that is called ipma_changeLogxxx.log. The log file resides on the server that runs the Cisco Unified CallManager Assistant service at the following location:

file get activelog tomcat/logs/ipma/log4j

The administrator can download this file from the server by using the trace and log central feature in the Serviceability Real-Time Monitoring Tool (RTMT). Refer to the Cisco Unified CallManager Serviceability Administration Guide for more information.

The log file fields remain the same.

Activating Cisco Unified CallManager Assistant

Use Serviceability Control Center Feature Service to stop and start the Cisco Unified CallManager Assistant service.

Trace Tool Settings

Configure trace settings from Cisco Unified CallManager Serviceability. Choose Cisco Unified CallManager Serviceability > Trace.

Download Cisco Unified CallManager Assistant traces from the Cisco Unified CallManager server by choosing Serviceability > Real Time Monitor Tool (RTMT) > Trace & Log Central.

Any errors that the configuration wizard generates get sent to the trace file.

Access this file by using the following CLI command:

file get activelog tomcat/logs/ccmadmin/log4j

Alarms and Perfmon Counters

Alarms get enabled from Serviceability. Use the Serviceability Real Time Monitor Tool (RTMT) to view the perfmon status and syslog (alarms).

BAT Considerations

Cisco Unified CallManager Assistant supports the following considerations for BAT, which is now integrated with Cisco Unified CallManager Administration.

Accessing BAT from Cisco Unified CallManager

To configure managers and assistants in Cisco Unified CallManager Assistant in BAT, choose Bulk Administration > Managers/Assistants. The following configuration windows display:

Insert Managers/Assistants

Delete Managers/Assistants

Delete Managers (Query and Custom File)

Delete Assistants (Query and Custom File)

Generate Cisco Unified CallManager Assistant Manager Reports

Generate Cisco Unified CallManager Assistant Reports

CAR/CDR Considerations

The CDR Analysis and Reporting Administration Guide documents CDR information for Cisco Unified CallManager Assistant.

Security Considerations

Cisco Unified CallManager Assistant supports security through the following service parameters and configuration windows:

Cisco Unified CallManager Assistant Service Parameters

CAPF Profile Instance ID for Secure Connection to CTI Manager—This node-specific service parameter specifies the Instance ID of the Application CAPF Profile for Application User Cisco Unified CallManager Assistant SecureSysUser that this Cisco Unified CallManager Assistant server will use to open a secure connection to CTI Manager. You must configure this parameter if CTI Manager Connection Security Flag is enabled.

CTI Manager Connection Security Flag—This clusterwide service parameter indicates whether security for Cisco Unified CallManager Assistant service CTI Manager connection is enabled or disabled. If enabled, Cisco Unified CallManager Assistant will open a secure connection to CTI Manager by using the Application CAPF profile that is configured in `Application CAPF Profile Instance ID for Secure Connection to CTI Manager' parameter.

Cluster Security Mode—You must also configure the security service parameter, Cluster Security Mode, from System > Enterprise Parameters in Cisco Unified CallManager Administration, to secure a TLS connection to CTI, giving it a value of 1. This value indicates secure mode. Because this parameter is read-only, to change the cluster security mode, you must run the CTL Client plug-in. You can do this from Application > Plugins in Cisco Unified CallManager Administration.

Secure Connection to CTI

Cisco Unified CallManager Assistant supports a secure connection to CTI (TLS connection).

The administrator must configure an Cisco Unified CallManager Assistant Secure Sys User for CAPF profile (one per Unified CM Assistant node) by choosing User Management > Application User CAPF Application Profile.

Where to Find More Information

Cisco Unified CallManager Assistant With Proxy Lines, Cisco Unified CallManager Features and Services Guide

Cisco Unified CallManager Assistant With Shared Lines, Cisco Unified CallManager Features and Services Guide

Cisco Unified CallManager Security Guide

Cisco Unified CallManager Administration Guide

Cisco Unified CallManager System Guide

Cisco Unity Voice Messaging

Cisco Unity comprises a communications solution that delivers voice messaging and unified messaging in a unified environment. This section comprises feature information for Cisco Unity and Cisco Unity Connection.

Cisco Unified CallManager Administration Configuration Tips

Enhancements exist to create individual Cisco Unity or Cisco Unity Connection voice mailboxes in Release 5.0. You can create Cisco Unity and Cisco Unity Connection user mailboxes from Cisco Unified CallManager Administration End User and Directory Number Configuration. For detailed information, refer to the Cisco Unified CallManager Administration Guide.


Note You must configure both Cisco Unity (or Cisco Unity Connection) and Cisco Unified CallManager Administration (for example, set up Cisco Unity voice mailbox templates, Cisco Unified CallManager dial plans) to enable this feature. To set up Cisco Unity, refer to the integration and installation guides for Cisco Unity and Cisco Unity Connection.


Cisco Unified CallManager SIP Integration to Cisco Unity now gets supported.

GUI Changes

When you save the configuration, Cisco Unity or Cisco Unity Connection adds the record in the Application Server Configuration in Cisco Unified CallManager Administration. Release 5.0 provides the Application Server windows.

You can create Cisco Unity voice mailboxes, if defined, in Cisco Unified CallManager Administration by choosing the Create Cisco Unity User link that displays in the Related Links drop-down list box in the upper, right corner of Cisco Unified CallManager Administration.


Note You must define a primary extension to create Cisco Unity voice mailboxes.


When the user is integrated with the Cisco Unified CallManager End User, you cannot edit the following fields in Cisco Unity windows:

Alias (User ID in Cisco Unified CallManager Administration)

First Name

Last Name

Extension (Primary Extension in Cisco Unified CallManager Administration)

Cisco Unity monitors the syncing of data from Cisco Unified CallManager. You can configure the sync time in Cisco Unity Administration.

Where to Find More Information

End User Configuration, Cisco Unified CallManager Administration Guide

Directory Number Configuration, Cisco Unified CallManager Administration Guide

Integration and installation documentation for Cisco Unity and Cisco Unity Connection

Cisco Web Dialer

Cisco Web Dialer, which is installed on a Cisco Unified CallManager server and used in conjunction with Cisco Unified CallManager, allows Cisco Unified IP Phone users to make calls from web and desktop applications. For example, Cisco Web Dialer uses hyperlinked telephone numbers in a company directory to allow users to make calls from a web page by clicking the telephone number of the person that they are trying to call.

Cisco Unified CallManager Administration Configuration Tips

The following section comprises the tips and information for configuring Cisco Web Dialer.

Application Dial Rule Change Notifications

You no longer need to restart Cisco Web Dialer after an application dial rule add, update, or delete. Dial rules will use change notification of data in the database, rather than the previous mechanism.

Redirector Servlet over HTTPS

The Redirector servlet now works over HTTPS, instead of HTTP. For example, you could access a URL similar to the following one:

https://<ccmIP address>:8443/webdialer/Redirector

SIP Support for Web Dialer

Cisco Web Dialer only supports Cisco Unified IP Phones 7941G, 7941G-GE, 7961G, 7961G-GE, and 7971 running SIP.

The following Cisco Unified IP Phones support Cisco Web Dialer:

Cisco Unified IP Phones 7970G/7971G

Cisco Unified IP Phones 7961G/41G and 7961GE/41GE (G = Non Gig; GE = Gig)

GUI Changes

The Cisco Web Dialer now supports partition information that JTAPI provides. The Cisco Web Dialer Preferences include information about the partition, as well as line information.

You can now launch Cisco Web Dialer from the Directory window, which is part of Cisco Unified CallManager User Options.

You can access Cisco Web Dialer from Cisco Unified CallManager User Options, under the Directory link. As an example, you could access a URL similar to the following one:

https://<ccmIP address>:8443/ccmuser

Service Parameter Changes

To configure Cisco Web Dialer service parameters, choose System >Service Parameters.

Two new security service parameters exist for enabling security for Cisco Web Dialer in Release 5.0:

CTI Manager Connection Security Flag—This clusterwide parameter indicates whether security for Cisco Web Dialer service CTI Manager connection gets enabled or disabled. If enabled, Cisco Web Dialer will open a secure connection to CTI Manager by using the Application CAPF profile that is configured in Application CAPF Profile instance ID for Secure Connection to CTI Manager parameter.

Application CAPF Profile Instance ID for Secure Connection to CTI Manager—This parameter specifies the Instance ID of the Application CAPF Profile for Application User WDSysUser that this Cisco Web Dialer server will use to open a secure connection to CTI Manager.


Note All changes to service parameters require a restart of the Cisco Web Dialer service for the changes to take effect.


Serviceability Considerations

The following sections comprise serviceability information for Cisco Web Dialer.

Trace Settings

You should configure the Cisco Web Dialer trace settings from the Serviceability trace settings windows. The same settings apply to both Cisco Web Dialer and Redirector.

Alarms and Performance Counters

Two new Cisco Web Dialer performance counters exist in Release 5.0:

RequestsCompleted

RequestsFailed

Security Considerations

Cisco Web Dialer now supports a secure (TLS) connection to CTI. A new application user, WDSecureSysUser, obtains the secure CTI connection. Release 5.0 makes two new application users available in Cisco Web Dialer:

WDSecureSysUser—Cisco Web Dialer uses this application user account to obtain a secure CTI connection.

WDSysUser—Cisco Web Dialer uses this application user account to open a non-secure CTI connection.

In Cisco Unified CallManager Administration, you must configure a CAPF profile in Application User CAPF Profile Configuration, that is configured for the instance ID for application user WDSecureSysUser. If you enable security from the service parameters window, Cisco Web Dialer will open a secure connection to CTI Manager by using the Application CAPF profile.

You must also configure the security service parameter, Cluster Security Mode, from System > Enterprise Parameters in Cisco Unified CallManager Administration, to secure a TLS connection to CTI, giving it a value of 1. This value indicates secure mode. Because this parameter is read only, to change the cluster security mode, you must run the CTL Client plug-in. You can do this from Application > Plugins in Cisco Unified CallManager Administration.

Where to Find More Information

Cisco Web Dialer, Cisco Unified CallManager Features and Services Guide

Cisco Unified CallManager Administration

Client Matter Codes and Forced Application Codes

Forced Authorization Codes (FAC) and Client Matter Codes (CMC) allow you to manage call access and accounting. CMC assists with call accounting and billing for billable clients, while Forced Authorization Codes regulate the types of calls that certain users can place.

Client Matter Codes force the user to enter a code to specify that the call relates to a specific client matter. You can assign client matter codes to customers, students, or other populations for call-accounting and billing purposes. The Forced Authorization Codes feature forces the user to enter a valid authorization code before the call completes.

The CMC and FAC features require that you make changes to route patterns and update your dial plan documents to reflect that you enabled or disabled FAC and/or CMC for each route pattern.

Cisco Unified CallManager Administration Configuration Tips

See the following section for GUI changes.

GUI Changes

CMC and FAC configuration moved from the Feature menu to the Call Routing menu in Release 5.0 of Cisco Unified CallManager Administration.

Where to Find More Information

Client Matter Codes and Forced Authorization Codes, Cisco Unified CallManager Features and Services Guide

Multilevel Precedence and Preemption (MLPP)

Resource Reservation Protocol (RSVP) signalling, using the RSVP Agent, includes a precedence level indicator for support of MLPP. RSVP supports only MLPP audio calls.

The Cisco Unified CallManager MLPP feature extends to RSVP reservations. Cisco Unified CallManager passes the caller precedence level information to RSVP Agent by means of SCCP Quality of Service (QoS) messages. An IOS router can preempt the call based on the precedence level. RSVP Agent needs to notify Cisco Unified CallManager about RSVP reservation failure reason including preemption cause. Cisco Unified CallManager notifies the preempted caller or callee about the preemption by using the existing MLPP method.

Cisco Unified CallManager passes the caller precedence level info to the RSVP Agent for both audio and video calls. The RSVP module in the router determines how to handle the precedence level information.

The system does not support MLPP for Session Initiation Protocol (SIP) phones.

Where to Find More Information

Multilevel Precedence and Preemption, Cisco Unified CallManager Features and Services Guide

Resource Reservation Protocol, Cisco Unified CallManager System Guide

Music On Hold

The Music On Hold (MOH) feature supports call admission control that Resource Reservation Protocol (RSVP) provides.

Cisco Unified CallManager supports RSVP for unicast MOH server. If RSVP policy is mandatory for the connection between an MOH server and the held party, Cisco Unified CallManager provides tone on hold when RSVP reservation fails.

Cisco Unified CallManager only allocates RSVP Agent for the calling/called devices, unicast MOH, and Annunciator. No RSVP Agent gets allocated for MTP or transcoder devices even if these devices are in different location from the endpoint. At most, one pair of RSVP agents per call exists.

Music On Hold interacts with RSVP by following the interlocation RSVP policy that was established for the location of the held party and the location of the MOH server.

This release includes the following enhancements to the MOH service:

MTP support for RFC2833 pass-through control by Cisco Unified CallManager with revised SCCP

Configuration settings for MTP RFC2833 DTMF duration and power

Configuration settings for MOH multicast RTP streams

This release includes the following enhancement to Cisco Unified CallManager:

Cisco Unified CallManager turns off Music on Hold streaming into a conference when a member of the conference puts the device on hold. This capability gets implemented on the SIP trunk for interoperability with Cisco Meeting Place.

Cisco Unified CallManager Administration Configuration Tips

In Release 5.0 of Cisco Unified CallManager, the Music On Hold (MOH) feature includes the following configuration differences:

The administrator must import the audio source file to the MOH server in each cluster prior to assigning an audio source number to the audio source file.

The Music On Hold Audio Source Configuration window uploads audio source files only to a particular server. The window does not provide for automatic copying of audio source files to any other servers. You must manually upload audio source files to subscriber servers by accessing the Cisco Unified CallManager application on each server.

The Music On Hold feature does not support the MP3 format.

In previous releases, Cisco Unified CallManager did not limit the amount of space that MOH files used. The MOH upload tool does not limit the number of uploaded files or the file size. The modified upload JSP pages check the disk usage of existing MOH files and only permit uploads if sufficient space is found.

Cisco Unified CallManager supports up to five MOH audio sources on 36- or 40-gigabyte disk-based systems. Systems with 72- or 80-gigabyte disks support the entire 50 audio streams. To increase the number of audio sources that Cisco Unified CallManager supports, install a larger disk during upgrade.

Administrators can neither add nor delete Music On Hold servers. Administrators can only modify MOH servers that get configured upon installation of Cisco Unified CallManager software.

The Media Resources menu includes the MOH Audio File Management menu option. Use this menu option to upload or delete Music On Hold audio source files.

GUI Changes

The Music On Hold configuration options moved from the Service > Media Resource menu to the Media Resources menu. Use the following menu options to configure the Music On Hold service:

Media Resources > Music On Hold Audio Source

Media Resources > Fixed MOH Audio Source

Media Resources > Music On Hold Server

Media Resources > MOH Audio File Management

User Tips

If an endpoint is connected to a multicast MOH server, no need for RSVP reservation exists.

Where to Find More Information

Music On Hold, Cisco Unified CallManager Features and Services Guide

Resource Reservation Protocol, Cisco Unified CallManager System Guide

Quality Report Tool

The Quality Report Tool (QRT), a voice-quality and general problem-reporting tool for Cisco Unified IP Phones, acts as a service that allows users to easily and accurately report audio and other general problems with their IP phone. QRT automatically loads with the Cisco Unified CallManager installation, and the Cisco Extended Functions (CEF) service supports it.

Cisco Unified CallManager Administration Configuration Tips

The following section comprises the tips and information for configuring QRT.

SIP Support for QRT

QRT supports Cisco Unified IP Phones 7911, 7941G, 7941G-GE, 7961G, 7961G-GE, and 7971 for SIP.

A SIP phone that is configured to use UDP as the transport, instead of TCP, will not support the device data pass-through functionality. QRT requires the pass-through functionality, so QRT does not support these UDP-configured SIP phones.

New QRT Report Fields

Two new fields exist in the QRT report:

sProtocol—This field represents the protocol for the source phones.

dProtocol—This field represents the protocol for the destination phones.

The actual names of the phones replace some phone names in the QRT report fields. For example, in previous releases, for the Source Model field, the description for an SCCP phone was 20. In Release 5.0, the actual corresponding SCCP phone name gets used.

This change affects the following report fields:

Source Model

Source Product

Destination Model

Destination Product

CallState

Security Considerations

QRT now supports a secure Transport Layer Security (TLS) connection to CTI. You can obtain the secure connection by using the CMQRTSecureSysUser application user.

If you enable security from the service parameters window, the QRT will open a secure connection to CTI Manager by using the Application CAPF profile. You should configure both the CTI Manager Connection Security Flag and the CAPF Profile Instance ID for Secure Connection to CTI Manager service parameters for the secure connection to succeed.

You must also configure the security service parameter, Cluster Security Mode, from System > Enterprise Parameters in Cisco Unified CallManager Administration, to secure a TLS connection to CTI, giving it a value of 1. This value indicates secure mode. Because this parameter is read only, to change the cluster security mode, you must run the CTL Client plug-in. You can do this from Application > Plugins in Cisco Unified CallManager Administration.

For more information, refer to the Cisco Unified CallManager Features and Services Guide and Cisco Unified CallManager Administration Guide.

Where to Find More Information

Cisco Unified CallManager Features and Services Guide

Cisco Unified CallManager Administration Guide

Cisco Unified CallManager System Guide

Cisco Unified CallManager Bulk Administration Features

Cisco Unified CallManager Bulk Administration (BAT), a web-based application, performs bulk transactions to the Cisco Unified CallManager database. This section introduces the changes to BAT for Cisco Unified CallManager 5.0.

Installation Considerations

BAT installs as part of Cisco Unified CallManager Administration. Refer to Cisco Unified CallManager Administration Guide for more details.

New and Changed Information for BAT

The menu structure in BAT changed to align with Cisco Unified CallManager Administration menu. Cisco Unified CallManager Administration includes Bulk Administration, a new menu.

See the "GUI Changes" section for more information.

The following changes in BAT apply for Cisco Unified CallManager 5.0:

BAT supports bulk provisioning of all phone data, including support for SIP features for phones. The migration script in BAT handles bulk provisioning for upgrade purposes.

Additions and changes to Cisco Unified CallManager administration and serviceability tools remain consistent with the existing look and feel of Cisco Unified CallManager Administration.

BAT accepts bulk provisioning data in a format that can be created and viewed by common enterprise desktop applications like Microsoft Excel.

The SCCP to SIP Phone Migration script in BAT allows you to select phones and update protocol from . To change the default values that are set during migration, use the Update Phones menu option in the Bulk Administration menu after migration. Values for the migration script in BAT from SCCP to SIP come from the phone template. Make sure that you reset the phones that you migrate from SCCP to SIP by using Bulk Administration > Phones > Reset/Restart Phones > Query. For more information about resetting phones, see Cisco Unified CallManager Bulk Administration Guide

BAT supports job scheduling to submit a job, like inserting phones, to the Bulk Provisioning Service (BPS). You can choose to run this job immediately or at a later time and date that you specify. This helps improve system performance during peak hours. Verify that the Bulk Provisioning Service is activated and running.

BAT provides a template for common user settings.

BAT provides a menu option to upload comma separated value (CSV) files from the client machine to Cisco Unified CallManager server with active BPS and to download reports, BAT Excel template, exported files, and log files that are generated through BAT from the server that is hosting the active BPS to the client machine.

Log files and trace files for BPS transactions get collected by using the trace and log central feature. The trace level (like info, debug, error, and so on) information gets set by using Cisco Unified CallManager Serviceability for each service including BPS. Appropriate traces get written in the trace files based on the setting.

BAT Configuration Tips

The Bulk Administration Tool installs with Cisco Unified CallManager, so requirement for plug-ins no longer exists.

GUI Changes

Cisco Unified CallManager Administration includes a menu item called Bulk Administration. The following menu items, which display under Bulk Administration, previously displayed under the Configure menu:

Phones

Users

Phones and Users (new)

Managers/Assistants

User Device Profiles

Gateways

Forced Authorization Codes

Client Matter Codes

Call Pickup Groups

Job Scheduler (new)

Upload/Download Files (new)

Service Parameter Changes

The following service parameters exist for the Bulk Provisioning Service (BPS) for BAT:

Stop Job Processing (Read-Only) — This required parameter, if set to true, stops bulk job processing. To start processing, change this value to false. You can set this value from Job Scheduling window from the Cisco Unified CallManager Bulk Administration Menu.

Default Job Processing Option—Default option for BPS Job processing. Select this option by default whenever you are ready to submit a job. You can change the selection for this required field before submitting the job.

Default Job Processing Time (HH.MM)—Default scheduled time for transactions goes in this optional required field.

Log File Location(Read-Only) —Location for Bulk Processing Log files. Log files for all jobs will get written here.

Serviceability Considerations

The following enhancements occur in Serviceability for BAT:

Serviceability provides an option to activate/deactivate BPS on a Cisco Unified CallManager server that is designated as the first node in cluster.

BAT transaction traces get stored with the traces for the other Cisco Unified CallManager applications. You can turn the traces on or off by using Cisco Unified CallManager Serviceability.

Security Considerations

BAT now implements Multilevel Administration. Restricted access to BAT administration windows occurs based on the permissions that are set for the users or groups of which users are part.

BAT Performance

Table 3 lists the performance values for various BAT transactions.


Note The following performance data occurs at laboratory conditions, and this data can change depending on Cisco Unified CallManager activity. Off-peak hour numbers only provide an approximate guidance to judge the overall time for transaction.


Table 3 BAT Performance Measures for Various Transactions 

Transaction
Records Processed/Minute

Forced Authorization Codes

Insert FAC

200

Delete FAC

500

Client Matter Codes

Insert CMC

250

Delete CMC

500

Call Pickup Groups

Insert CPG

200

Delete CPG

500

Phones/Users

Validate Phones/Users

100

Insert Phones/Users

15

Users

Insert Users

150

Update Users

65

Reset Password/PIN Query

500

Reset Password/PIN Custom

350

Generate User reports

500

Export Users - Specific

250

Export Users - All

200

Delete Users - Query

300

Delete Users - Custom

300

Manager Assistants

Manager/Assistant Insert

75

Manager/Assistant CSV-Based Delete

300

Manager/Assistant Query-Based Delete

300

Manager/Assistant Custom File-Based Delete

300

UDP Transactions

Validate UDP

300

Insert UDP Specific Details

65

Export All Details

50

Add lines UDP

75

Report UDP

125

Delete UDP

70

Phone Transactions

Validate Phones

250

Insert Specific Phones

45

Export All Details

75

Update Phones

150

Add lines for Phones

75

Reset/Restart Phones

500

Generate Phone Reports

300

Delete Phones (Query)

75


Cisco Unified CallManager Auto-Register Phone Tool Features

The Cisco Unified CallManager Auto-Register Phone Tool application enables phone users to call the TAPS directory number and download the preconfigured phone settings for the users directory number.

Installation Considerations

TAPS gets installed on Cisco Unified CallManager first node as part of Cisco Unified CallManager Administration installation. For more details, refer to Cisco Unified CallManager Administration Guide. For TAPS to function, you must enable auto-registration in Cisco Unified CallManager Serviceability.

You must install TAPS application on Cisco Customer Response Solutions (Cisco CRS) server that is running Microsoft Windows. You can download TAPS installable for the Cisco CRS by choosing Menu > Applications > Plugins from Cisco Unified CallManager Administration.

For more details about installing TAPS on Cisco CRS, refer to Cisco Unified CallManager Bulk Administration Guide.

TAPS Configuration Tips

TAPS requires the Cisco Unified IP Interactive Voice Response (IP-IVR) application that runs on the Cisco CRS server for the user interface and prompts.

GUI Changes

The TAPS submenu in Bulk Administration includes the following menu options.

Secure TAPS

User Locales for TAPS

View TAPS Log File

Service Parameter Changes

Two new service parameters exist for TAPS for Cisco Unified CallManager 5.0. For more information on service parameters and how to view and modify them, refer to Cisco Unified CallManager Administration Guide.

Auto-Registration Options for TAPS—Choose Allow Auto-Registered phones to reset with a profile with a dummy MAC address or Allow Auto-Registered phones with any profile.

Log File Location—Location for TAPS log files. Log files for all TAPS transactions will get written in this required field. Maximum length: 255.

Serviceability Considerations

The following enhancements exist in Serviceability for TAPS:

Serviceability provides an option to activate/deactivate Cisco TAPS service on a Cisco Unified CallManager server that is designated as the first node in cluster.

TAPS transaction traces get stored with the traces for the other Cisco Unified CallManager applications. You can turn the traces on or off by using Cisco Unified CallManager Serviceability.

Security Considerations

TAPS now implements Multilevel Administration. Restricted access to TAPS administration windows occurs based on the permissions that are assigned to the users or groups of which users are part.

Where to Find More Information

Cisco Unified CallManager Bulk Administration Guide

Cisco Unified CallManager Administration Guide

Cisco Unified CallManager Serviceability Administration Guide

Security Features

Cisco Unified CallManager 5.0 supports the following security features:

Security profiles—Cisco Unified CallManager Administration groups security-related settings into profiles, so you can apply all settings to a SIP phone, SIP trunk, or SCCP profile when you apply a profile to the device.

Encrypted phone configuration files—After you configure security-related settings, the phone configuration file contains sensitive configuration information, such as digest authentication passwords and phone administrator passwords. To ensure privacy of the configuration file during download, you must configure the configuration files for encryption.

H.323/H.245/H.225 gateway and trunk encryption—Cisco Unified CallManager 5.0 allows you to encrypt the media streams between Cisco Unified CallManager and the H.323/H.245/H.225 gateway and trunk.

Digest authentication—This process, which is used for SIP trunks and SIP phones, allows Cisco Unified CallManager to challenge the identity of the SIP user agent (UA) when the UA sends a request to Cisco Unified CallManager.

SIP trunk-based authorization—For SIP trunks, Cisco Unified CallManager provides authorization of Presence requests and certain non-INVITE SIP messages from the SIP trunk or SIP trunk application user; for example, out-of-dial REFER, unsolicited notification, and any SIP request with the replaces header.

Authorization occurs for the trunk first and then for the SIP trunk application user when you configure both the SIP trunk and the application for authorization in Cisco Unified CallManager Administration. Before authorization for the application can occur, Cisco Unified CallManager authenticates the application with digest authentication.

Presence group authorization—Cisco Unified CallManager allows you to configure presence groups to control the destinations that watchers can monitor. Refer to the "Presence" section for additional details.

JTAPI/TAPI/CTI application security—Cisco Unified CallManager 5.0 allows you to secure the signaling connections and media streams between CTIManager and CTI/JTAPI/TAPI applications.

Packet capture—Because third-party troubleshooting tools that sniff media and TCP packets do not work after you enable SRTP encryption, you must use Cisco Unified CallManager Administration to configure packet capturing.

Cisco Unified CallManager Administration Configuration Tips

Security operations rely on the creation of the Cisco CTL file. Before you perform the following tasks, create the Cisco CTL file and ensure that the cluster security mode equals secure mode.

Security Profiles

After you configure the security profile for the SIP trunk, SIP phone, or SCCP phone (System > Security Profile >...), you apply the profile to the device (Device > Phone or Device > Trunk).

All SIP phones, SCCP phones, and SIP trunks require that you apply a security profile. If the device does not support security, apply a nonsecure profile.

For SIP and SCCP phones, configure the CAPF settings in the profile in conjunction with the Certificate Authority Proxy Function settings that display in the Phone Configuration window.

If you configured the device security mode prior to the Cisco Unified CallManager 5.0 upgrade, Cisco Unified CallManager creates a profile that is based on the mode and applies the profile to the device.

If the device does not support the profile that you configure, Cisco Unified CallManager does not allow you to apply it to the device.

When you configure digest authentication for the SIP phone or SIP trunk, be sure to configure the digest credentials for the application user or end user and apply the end user with configured digest credentials to the phone.

The SCCP phone security profile supports the Cisco Voice Mail Port (Voice Mail > Cisco Voice Mail Port [or Cisco Voice Mail Port Wizard]). When you choose a profile, consider the device security mode and not the CAPF settings from the profile. Cisco Unified CallManager ignores the CAPF settings in the security profile because the settings do not apply to voice mail ports.

Encrypted Phone Configuration Files

In Cisco Unified CallManager Administration, enable the TFTP Encrypted Configuration enterprise parameter (System > Enterprise Parameters). If your phone supports manual key distribution, perform the manual key distribution tasks in Cisco Unified CallManager Administration (Device > Phone). If your phone supports the method, symmetric key encryption with phone public key, verify that a manufacture-installed certificate (MIC) or locally significant certificate (LSC) exists in the phone; reset the phone.

H.323/H.245/H.225 Gateway and Trunk Encryption

Configure IPSec in the network infrastructure or from Cisco Unified CallManager to the gateway/trunk. Check the SRTP Allowed check box in Cisco Unified CallManager Administration (Device > Gateway or Device > Trunk). To support IPSec and encryption on the gateway, perform the necessary tasks on the gateway, as described in the documentation that supports your gateway.


Caution If you do not configure IPSec but you check the SRTP Allowed check box in Cisco Unified CallManager Administration, the SRTP key material gets sent in the clear. Before you check the check box, ensure that you configured IPSec correctly.

SIP Trunk-Based Authorization

Configure the SIP trunk security profile (System > Security Profile > SIP Trunk Security Profile), and check any or all of the following check boxes: Accept Presence Subscription, Accept Out-of-Dialog Refer, Accept Unsolicited Notification, Accept Replaces Header.

If you want application-level authorization to occur after trunk-level authorization, check the Enable Application Level Authorization and Enable Digest Authentication check boxes.

After you configure the SIP trunk security profile, apply the profile to the trunk. Then, for application-level authorization, check the check boxes in the Application User Configuration window (User Management > Application User).

Make sure that you configure digest authentication for the trunk, as described in the "Digest Authentication for SIP Trunks and SIP Phones" section.

Presence Group Authorization

To use presence group authorization, configure presence groups and permissions (System > Presence Groups). For each presence group that you create, you apply the presence group to one or more of following items in Cisco Unified CallManager Administration: directory number, trunk, phone, application user, end user, and autogenerated device profiles.

Digest Authentication for SIP Trunks and SIP Phones

To configure digest authentication for the SIP phone, perform the following tasks:

Configure the digest credentials in the End User window (User Management > End User). Configure a SIP Phone Security Profile for digest authentication (System > Security Profile > SIP Phone Security Profile) and apply it to the phone (Device > Phone). In the Phone Configuration window, choose that end user from the Digest User drop-down list box. If you are configuring a third-party phone, you must enter the digest credentials on the phone.

To configure digest authentication for the SIP trunk, perform the following tasks:

Configure a SIP trunk security profile for digest authentication (System > Security Profile > SIP Trunk Security Profile) and apply it to the trunk (Device > Trunk).

When Cisco Unified CallManager acts as a UAS, configure the Cluster ID enterprise parameter (System > Enterprise Parameters). Configure the digest credentials in the Application User Configuration window (User Management > Application User).

When Cisco Unified CallManager acts as a UAC, configure the digest credentials in the SIP Realm window (User Management > SIP Realm).


Tip Digest authentication does not provide integrity or confidentiality. To ensure integrity and confidentiality for the device, configure the TLS protocol for the device if the device supports TLS. If the device supports encryption, configure the device security mode as encrypted. If the device supports encrypted phone configuration files, configure encryption for the files.


JTAPI/TAPI/CTI Application Security

To ensure that JTAPI/TAPI/CTI applications connect securely to the CTIManager, you must configure the Application User CAPF Profile (User Management > Application User CAPF Profile).

To ensure that applications connect securely to CTIManager, you must configure the Application or end user CAPF profile for each instance of the application that runs on a PC (User Management > End User CAPF Profile).

To ensure that application and end user supports secure connection (TLS) and media encryption (SRTP), you must add the user to the Standard CTI Secure Connection and the Standard CTI Allow Reception of SRTP Key Material user groups (User Management > User Group).


Tip Before the application and end user can use SRTP, verify that the user exists in the Standard CTI Enabled and Standard CTI Secure Connection user group, which serves as a baseline configuration for TLS and SRTP connections. After you add the user to this group, you can add the user to the Standard CTI Allow Reception of SRTP Key Material user group. The application and end user cannot use SRTP if it does not exist in these three groups.


Packet Capturing

In Cisco Unified CallManager Administration, configure the TLS packet capture service parameters for the Cisco CallManager service (System > Service Parameters) to capture packets for TLS connections between Cisco Unified CallManager and a device (Cisco Unified IP Phone, Cisco SIP IP Phone, SIP trunk, Cisco IOS MGCP gateway, H.323 gateway, or H.323/H.245/H.225 trunk). You then specify batch processing mode in the Packet Capture Mode field and the Packet Capture Duration in the device configuration window in Cisco Unified CallManager Administration.

GUI Changes

The following new and changed windows in Cisco Unified CallManager Administration contain security-related configuration settings:

SCCP Phone Security Profile Configuration window (new)—Contains the Device Security Mode, Authentication Mode (for CAPF), and the Key Size (for CAPF) settings.

SIP Phone Security Profile Configuration window (new)—Contains the Device Security Mode, Authentication Mode (for CAPF), the Key Size (for CAPF), Enable Digest Authentication, Nonce Validity Time, Transport Type, and SIP Phone Port settings.

SIP Trunk Security Profile Configuration window (new)—Contains the Incoming Transport Type, Outgoing Transport Type, Device Security Mode, Enable Digest Authentication, Nonce Validity Time, X.509 Subject Name, Incoming Port, Enable Application Level Authorization, Accept Presence Subscription, Accept Out-of-Dialog REFER, Accept Unsolicited Notification, and Accept Replaces Header settings.


Tip The Transport Type settings now display in the Security Profile window instead of the SIP Trunk window.


End User Configuration window (new)—Contains the following new settings for phone digest authentication: Digest Credentials and Confirm Digest Credentials.

Application User Configuration window (new)—Contains the Accept Presence Subscription, Accept Out-of-Dialog REFER, Accept Unsolicited Notification, Accept Replaces Header, and Associated CAPF settings, as well as the following new settings for application digest authentication: Digest Credentials and Confirm Digest Credentials.

User Group Configuration window (new)—Contains the following new settings for configuring TLS and encryption for JTAPI/TAPI/CTI applications: Standard CTI Secure Connection and Standard CTI Allow Reception of SRTP Key Material.

Application User CAPF Profile Configuration window (new)—Allows you to install and upgrade locally significant certificates for JTAPI/TAPI applications; all settings in this window relate to security.

End User CAPF Profile Configuration window (new)—Allows you to install and upgrade locally significant certificates for JTAPI/TAPI applications; all settings in this window relate to security.

SIP Realm window (new)—Supports SIP trunk digest authentication; all settings in this window relate to security.

Cisco Unified CallManager window (changed)—Contains the following new setting: SIP Phone Security Port. Update this setting only if the port number is in use, or if you use a firewall and you cannot use the port within the firewall.

Cisco Voice Mail Port window (changed)—Contains the SCCP Phone Security Profile setting where you can apply an authenticated, encrypted, or nonsecure security profile to the port.


Tip The Device Security Mode setting now displays in the SCCP Phone Security Profile window instead of the Cisco Voice Mail Port window and in the Cisco Voice Mail Port Wizard.


Cisco Voice Mail Port Wizard (changed)—Contains the SCCP Phone Security Profile setting where you can apply an authenticated, encrypted, or nonsecure security profile to the port.


Tip The Device Security Mode setting no longer displays in this window. You configure the Device Security Mode setting in the SCCP Phone Security Profile.


Phone Configuration window (changed)—Contains the following security-related settings:

SIP Phone Security Profile (or SCCP Phone Security Profile)—After you configure a security profile (System > Security Profile >...), you apply it to the device in this window.

Digest User, SIP phone only (new)—For this setting that is used for digest authentication, you choose the digest user, an end user, for a phone after you configure the digest credentials in the End User window. (Consider this field a required field for third-party SIP phones.)

Certificate Authority Proxy Function (not all phone types)—You configure the Certificate Operation, Authentication String, Generate String, Operation Completes By, and Certificate Operation Status settings in conjunction with the CAPF settings that display in the SIP Phone or SCCP Phone Security Profile windows.

Symmetric Key, Generate Symmetric Key, and Revert to Database Value (not all phone types)—These settings allow you to configure encrypted phone configuration files.

Packet Capture Mode and Packet Capture Duration—If the phone supports packet capturing, the Packet Capture Mode and Packet Capture Duration display to allow you to capture packets in batch mode.


Tip The Device Security Mode, Authentication Mode, and Key Size settings no longer display in the Phone Configuration window. You configure these settings in the SIP Phone or SCCP Phone Security Profile windows.


SIP Trunk Configuration window (changed)—Contains the SIP Trunk Security Profile setting where you choose a profile for the device and the Packet Capture Mode and Packet Capture Duration settings, which are used if you need to troubleshoot encryption for the trunk.

H.225 Trunk Configuration window (changed)—Contains the SRTP Allowed check box and the Packet Capture Mode and Packet Capture Duration settings, which are used if you need to troubleshoot encryption for the trunk.

Inter-Cluster Trunk Configuration (Gatekeeper-Controlled) window (changed)—Contains the SRTP Allowed check box and the Packet Capture Mode and Packet Capture Duration settings, which are used if you need to troubleshoot encryption for the trunk.

Inter-Cluster Trunk Configuration (Non Gatekeeper-Controlled) window (changed)—Contains the SRTP Allowed check box and the Packet Capture Mode and Packet Capture Duration settings, which are used if you need to troubleshoot encryption for the trunk.

H.323 Gateway Configuration window (changed)—Contains the SRTP Allowed check box and the Packet Capture Mode and Packet Capture Duration settings, which are used if you need to troubleshoot encryption for the trunk.

User Group Configuration window (changed)—Contains the Standard CTI Secure Connection, Standard CTI Allow Reception of SRTP Key Material, and Standard Packet Sniffer User groups that are provided by default; allows you to assign end users and applications users to these groups.

Role Configuration window (new)—Contains the Enable CTI Security and Enable CTI SRTP Key Distribution settings for a CTI application.

New Service and Enterprise Parameters

TFTP Encrypted Configuration—This enterprise parameter specifies whether encryption is enabled for TFTP download. Restart all services for the parameter change to take effect.

CAPF Profile Instance ID for Secure Connection to CTIManager—Used with the Cisco Web Dialer Web and Cisco Unified CallManager IP Manager Assistant services, this parameter specifies the instance ID of the application users, WDSecureSysUser and Cisco Unified CallManager Assistant SecureSysUser, that this Cisco Web Dialer or Cisco Unified CallManager Assistant server uses to open a connection to CTIManager. You must configure this parameter if you enable the CTI Manager Connection Security Flag parameter. You must restart the Cisco Unified CallManager Assistant or the Cisco Web Dialer service for the changes to this parameter to take effect.

CTIManager Connection Security Flag—The CTIManager Connection Security Flag service parameter indicates whether security is enabled for the CTIManager connection to the Cisco Unified CallManager Assistant or Cisco Web Dialer service. If enabled, Cisco Unified CallManager Assistant or Cisco Web Dialer opens a secure connection to CTIManager by using the Application CAPF profile that is configured for the instance ID for the application user. You must restart the Cisco Unified CallManager Assistant or the Cisco Web Dialer service for the changes to this parameter to take effect.

Cluster ID—This parameter provides a unique identifier for this cluster. This parameter serves as the realm in digest authentication when Cisco Unified CallManager challenges a trunk device. Because this parameter gets used in CDRs, you can trace collections of CDRs from multiple clusters to the source.

SIP Realm—This service parameter for Cisco Unified CallManager specifies the string that is used in the realm field when Cisco Unified CallManager responds to challenges from a trunk device in digest authentication.

SIP Station Realm—This service parameter for Cisco Unified CallManager specifies the string that is used in the realm field when Cisco Unified CallManager challenges a SIP phone in digest authentication.

Packet Capture Enable—This service parameter for Cisco Unified CallManager determines whether Cisco Unified CallManager captures packets that are sent or received over TLS connections.

Packet Capture Max File Size (MB)—This service parameter for Cisco Unified CallManager specifies the maximum size of each packet capture file that Cisco Unified CallManager creates for batch mode debugging.

Removed or Changed Service or Enterprise Parameters

The Device Security Mode enterprise parameter no longer exists. Instead, use the SCCP or SIP phone security profiles to configure and apply the device security mode to many devices at the same time.

Serviceability Considerations

After you configure the service parameters for JTAPI/TAPI/CTI security, you must restart the corresponding services.

Where to Find More Information

Cisco Unified CallManager Security Guide

New and Changed Information for Cisco Unified CallManager Serviceability

Cisco Unified CallManager Release 5.0 provides the following enhancements to Serviceability:

Serviceability Administration

Real-Time Monitoring Tool

Trace & Log Central

SysLog Viewer

CDR Analysis and Reporting (CAR)

Where to Find More Information

Serviceability Administration

The Cisco Unified CallManager Serviceability Administration windows allow you to perform such tasks as configuring trace parameters, configuring alarms, and activating, starting, and stopping services.

GUI Changes

The Cisco Unified CallManager Serviceability GUI contains the following changes for this release:

The system allows you to start and stop services on different Control Center windows, depending on the service type: features services and network services. Feature services allow you to use Cisco Unified CallManager related features. You can start and stop feature services on the Control Center-Feature services window. The system does not automatically activate these services when a new installation occurs. You must activate them on the Service Activation window. If you have upgraded your system, those services that you activated on the system prior to the upgrade automatically activate and start after the upgrade. You need network services for your system to function. Because these services are required for basic Cisco Unified CallManager functionality, you cannot activate them in the Service Activation window. You can start and stop these services in the Control Center-Network Services window.

Cisco Unified CallManager Serviceability contains a new SNMP Configuration menu that allows you to configure SNMP community strings, users, and notification destinations for SNMP versions 1, 2c, and 3. You can apply configurations to a single server or to all servers in the cluster. Previously, you had to configure SNMP in the Microsoft Windows SNMP service properties dialog box on each server in the cluster.

Cisco Unified CallManager Serviceability contains a new mechanism for managing and delivering call detail records (CDR) and call management records (CMR). The CDR Management Configuration window allows you to set the amount of disk space that is allocated to call detail record (CDR) and call management record (CMR) files, configure the number of days to preserve files before deletion, and configure up to three billing application server destinations for CDR delivery. The CDR repository manager service repeatedly attempts to deliver CDR and CMR files to the billing servers that you configure on the CDR Management Configuration window until it delivers the files successfully, until you change or delete the billing application server on the CDR Management Configuration window, or until the files fall outside the preservation window and are deleted. You must use the CDR Management feature to move CDR/CMR files to your billing server(s). To access, choose Tools > CDR Management.

The Alarm Configuration window (Alarm > Alarm Configuration) contains new check boxes: Local Syslog and Remote Syslog. The Local Syslog check box allows you to store syslog messages locally on Cisco Unified CallManager. You view the messages by using the SysLog viewer in RTMT or by using the CLI. The Remote Syslog check box allows you to send syslog messages to be stored on a Syslog server that you specify.

The trace output setting options on the Trace Configuration window (Trace > Configuration) changed. Available options include maximum number of files and maximum file size. The defaults for the options vary depending on the service.

Release 5.0 removes the Trace Analysis Configuration window. The system does not support XML tracing.

Release 5.0 deletes the Tools > RTMT menu option. To download the RTMT plug-in, use the Find and List Plugins window (Application > Plugins) in Cisco Unified CallManager Administration.

Release 5.0 makes the Q931 Translator obsolete and removes the Q931 Translator window from Cisco Unified CallManager Serviceability.

Release 5.0 removes the QRT viewer from Cisco Unified CallManager Serviceability and incorporates it into RTMT.

The Cisco Serviceability Reporter service generates a new report that is called the Performance Protection Report, which provides trend analysis information on default monitoring objects that allows you to track overall system health. The report includes information for the last seven days for each server. The report contains three graphs and one table. The three graphs contain data that the AMC service collects, and the report collects the table information from the Cisco Unified CallManager database.

The system contains new precanned alerts in Alert Central.

Administration Configuration Tips

If you are upgrading to Cisco Unified CallManager 5.0, you must enter SNMP configurations through the new SNMP Configuration menu in Cisco Unified CallManager Serviceability. The system does not migrate SNMP Configuration settings from the Microsoft Windows SNMP service properties dialog box.

Because the Serviceability Reporter service is CPU intensive, Cisco recommends that you activate the service on a non call-processing server.

When you change either the Maximum No. of Files or Maximum File Size field on the Trace Configuration window, the system deletes all the service log files except the current file if the service is running, or if the service has not been activated, the system will delete the files when the service initially gets activated. If you want to keep a record of the log files, make sure that you download and save the service log files to another server before changing the Maximum No. of Files field or the Maximum File Size field.

Real-Time Monitoring Tool

Cisco Unified CallManager 5.0(2) includes the following enhancements to the Real-time Monitoring Tool (RTMT).

Cisco provides RTMT versions that run on both Windows and Linux operating systems.

You can monitor the different processes that are running on the server.

RTMT includes updated performance monitor counters.

RTMT provides SIP activity information, such as a summary of SIP requests, SIP responses, total number of failed incoming responses (4xx, 5xx, and 6xx), total number of failed outgoing responses (4xx, 5xx, and 6xx), number of retry request, and number of retry responses.

RTMT provides Database summary information, such as change notification requests that are queued in the database, the change notification requests that are queued in memory, the total number of active client connections, and the number of devices that are queued for a device reset.

The phone summary will also provide information on the number of SIP phones and Partially Registered phones, as well as the number of Registered phones, SCCP phones, and the number of failed registration attempts.

You can initiate a trace download based on the occurrence of an event by checking the TCT Download check box in Alert properties for CriticalServiceDown and CodeYellow alerts.

With Cisco Unified CallManager 5.0(2), you can monitor the log partition disk space. The Log Partition Monitoring service starts automatically when you install Cisco Unified CallManager. You configure LogPartitionLowWaterMarkExceeded or LogPartitionHighWaterMarkExceeded setting in Alert Central in RTMT. You can configure Cisco Unified CallManager to send an alarm message to syslog or an alert message to alert central when disk space reaches either the LogPartitionLowWaterMarkExceeded or LogPartitionHighWaterMarkExceeded setting. When the disk space reaches the LogPartitionHighWaterMarkExceeded limit that you specify, the system begins deleting files until disk space reaches a configurable lower limit.

Release 5.0 integrates the Trace Collection Tool, which was a separate plug-in for previous releases, into RTMT and names it as Trace & Log Central. For more details, see the "Trace & Log Central" section.

Release 5.0 integrates the SysLog Viewer into RTMT. For more details, see the "SysLog Viewer" section.

With Cisco Unified CallManager 5.0(2), you can expand the functionality of RTMT by installing an application plug-in, such as the Voice Trace Log (VLT) application. You can download the latest plug-ins for the RTMT viewer from Cisco.com.

GUI Changes

New monitoring categories exist. To access, click the View tab in the Quick Launch Channel and use one of following paths:

Server > Process

Call Process > SIP Activity

Service > Database Summary

On the Select Phone to Monitor dialog box (Device > Open Device Search > Phone), a new option enables you to search by protocol: SCCP or SIP.

New trace options exist. To access, click the Tools tab in the Quick Launch Channel and choose Trace. For more details on these options, see the "Trace & Log Central" section.

Administration Configuration Tips

If the PC on which you are installing RTMT runs on a Linux operating system, make sure that you download the Cisco Unified CallManager Real-Time Monitoring Tool-Linux plug-in from the Find and List Plugins window in Cisco Unified CallManager Administration. If the PC runs Windows, make sure that you install the Cisco Unified CallManager Real-Time Monitoring Tool-Windows plug-in.

If you have previously installed RTMT for use with a Cisco Unified CallManager server that is running Microsoft Windows, you must install RTMT for Cisco Unified CallManager 5.0 in a different folder on your local computer.

For Log Partition Monitoring, configure the LogPartitionLowWaterMarkExceeded and LogPartitionHighWaterMarkExceeded settings in Alert Central.

To initiate a trace download based on the occurrence of an event, check the TCT Download check box in Alert properties for CriticalServiceDown and CodeYellow alerts.

Trace & Log Central

In previous releases, the trace collection tools represented a separate plug-in that was available from the Plugin Configuration window in Cisco Unified CallManager. The trace collection tool allowed you to collect, view, and zip various Cisco Unified CallManager service traces and/or other Cisco Unified CallManager log files. This release integrates the trace collection tool into the real-time monitoring tool (RTMT) client-side plug-in, and enhances it to include more trace collection options, and names it trace and log central.

GUI Changes

Administrators can access the trace collection option by installing RTMT on their PC and performing one of the following tasks:

In the Quick Launch Channel, click the Tools tab; then, click Trace and the Trace & Log Central icon.

Choose Tools > Trace Collection > Trace & Log Central.

The trace collection option contains the following new features:

Remote Browse—After the system generates trace files, you can view them on the server by using the viewers within the RTMT. You can also use the remote browse feature to download the traces to your PC.

Collect Files—This feature collects and downloads traces for services, applications, and system logs on one or more servers in the cluster for an absolute date and time range (such as between July 8, 2005 at 12:30 and August 8, 2005 at 12:30) or for a relative time (such as, within the last 30 minutes).

Query Wizard—This feature collects trace files for services, applications, and system logs for an absolute or relative time range that contains text strings that you specify. You can view the collected trace file and/or download the trace files to your PC. You can also save the trace collection query criteria for later use. If you save the query as a regular query, you can only run the query on the node on which it was created. If you save the query as a generic query, you can run it on any node in any cluster.

Schedule Collection—This feature schedules a recurring trace collection and allows users to perform a specified action, including run another query, generate a syslog, or download the trace files on a SFTP server.

Local Browse—After you collect trace files and download them to your PC, you can view them with a text editor that can handle UNIX variant line terminators such as WordPad on your PC, or you can view them by using the viewers within the RTMT.

Collect Crash Dump—This feature collects a crash dump file for one or more servers on your network.

Real Time Trace—This feature comprises two options: view real-time data and monitor user events. The view real-time data option allows you to view the current trace file that is being written on the server for an application. The monitor user event option enables the system to monitor real-time trace files and perform a specified action when a search string displays in the trace file. Actions include generating an alert, generating local or remote syslogs, or downloading trace files via SFTP.

Job Status—This feature allows you to view the status of the trace collection jobs that are running on the system as well as recently processed jobs and to delete currently running or pending jobs. To access, perform one of the following tasks:

In the Quick Launch Channel, click the Tools tab; then, click Trace and the Job Status icon.

Choose Tools > Trace Collection > Job Status.

Using the available collection methods, you can perform the following functions:

Collect trace files that contain text that you specify in the Search String field.

Delete the trace files on the server by checking the Delete Collected Log Files from the server check box.

Collect traces based on absolute or relative time.

Administration Configuration Tips

Consider the following tips when you are using the trace and log central option in RTMT:

If you collect traces for the same services in multiple clusters, you can create a generic query that you can run. You can only run regular queries on the node on which it was created.

You can automatically capture traces when a particular event occurs by checking the Enable trace collection Download check box in Set Alert/Properties for the CriticalServiceDown and CodeYellow alerts.

The system supports Log4j traces for Java applications.

SysLog Viewer

Release 5.0 integrates the SysLog Viewer into the RTMT and allows you to view messages in system logs, application logs, and security logs. It contains the following capabilities:

Sort messages in ascending or descending order.

Filter results based on a set of selected options.

Search for a particular string in the current log.

Save the currently selected log to your local computer.

GUI Changes

A new option in RTMT allows you to access the SysLog Viewer.

Administration Configuration Tips

Choose one of the following methods to access the SysLog Viewer:

In the Quick Launch Channel in RTMT, click the Tools tab; then, click SysLog Viewer and the SysLog Viewer icon.

In the RTMT menu, choose Tools > SysLog Viewer> Open SysLog Viewer.

CDR Analysis and Reporting (CAR)

The CDR Analysis and Reporting (CAR) application generates reports for calls on the basis of CDRs and CMRs. For this release, the following changes apply to CAR:

Administrators access CAR by activating CAR services rather than by installing a plug-in and grant administrator rights through the User Group Configuration window in Cisco Unified CallManager rather than through the Grant/Revoke CAR Admin Rights window in CAR. You must configure the CAR administrator as an end user, rather than as an application user.

CAR supports Internet Explorer 6.0 (and above) and Netscape 7.1 (and above). CAR reports support double-byte characters.

Because Cisco Unified CallManager stores CDRs in flat files rather than a CDR database in this release, the system loads the CAR database from CDR flat files. You can reload all CDRs into the CAR database by using a new option on the Manual Database Purge window. You can enable the system to delete CAR database records when the database size reaches the high water mark that you configure.

CAR reports support new features. This release removes some report options.

You can collect traces for CAR by using the trace and log central feature in RTMT.

CAR only migrates the first 2 million CDR that it finds in the old CAR database. CDR records beyond that will be lost. Be sure that you have less than 2 million CDRs by checking the number of CDRs in both tbl_billing_data and tbl_billling_error. If the number exceeds 2 million records, you must manually purge the number of CDRs until you have less than 2 million records.

GUI Changes

The CAR GUI contains the following changes for this release:

This release removes the following windows and reports: Grant/Revoke CAR Admin Rights window, Error Log window, CDR Database Alert window, Control Center window, and CTI Users report.

This release removes the CDR option from the Manual Purge window and Configure Automatic Purge window.

The CDR Search reports contain a new field to support the K factor feature.

This release adds the Reload All Call Detail Records to the Manual Database Purge window, so the administrator can delete the data in the CAR database and reload the CDRs from flat files into the database.

The CAR reports support double-byte languages.

Administration Configuration Tips

Use the following tips to configure and use CAR:

To activate CAR, activate the Cisco CAR Scheduler and Cisco CAR Web Service on the first node by using the Service Activation window in Cisco Unified CallManager Serviceability. You no longer install a plug-in as you did in previous releases. If you are using a third-party billing application that accesses CDR data via an HTTPS/SOAP interface, activate the Cisco SOAP-CDROnDemand service.

To grant administrative privileges for CAR, add users to the Standard CAR Admin Users group on the User Group Configuration window in Cisco Unified CallManager Administration (User Management > User Group). The Grant/Revoke CAR Admin Rights window no longer exists.

The CAR database can hold up to 6 gigabytes of data. You can control the amount of data in the CAR database by configuring a high water mark and low water mark on the Automatic Purge Configuration window (System > Database > Configure Automatic Purge). If you do not check the Disable CAR Purge check box, the system deletes records that are older than the number of days that you specify when the database size reaches the high water mark. The system continues to delete records until the database size reaches the low water mark. By default, the low water mark equals 80 percent, the high water mark equals 90 percent, and the deletion age equals 180 days. The system no longer deletes records based only on age.

You can delete the data in the CAR database and reload the CDRs from flat files into the database by clicking the Reload All Call Detail Records button on the Manual Database Purge window. You may want to reload the CAR database if you want to reclassify calls after dial-plan updates, user-device association changes, call rate changes, and so on. Performing this task may impact system performance. You can monitor the reload process by generating the CDR Load event log (System > Log Screens > Event Log).

The CAR database loads from CDR flat files. The CDR Export function exports data from the CAR database rather than the CDR database because the CDR database no longer exists.

The Call Type field in the CDR Search reports displays new call types to support SIP features: refer, replaces, pickups, and redirection.

CAR supports Log4j tracing, error logging, and Cisco CAR Scheduler logs. To set trace parameters for the Cisco CAR Web Service, use the Trace Configuration window in Cisco Unified CallManager Serviceability. To collect traces on the Cisco CAR Web Service, use the trace and log central feature of RTMT.

Where to Find More Information

CDR Analysis and Reporting Administration Guide

Cisco Unified CallManager Serviceability Administration Guide

Cisco Unified CallManager Serviceability System Guide

New and Changed Information for Cisco Unified IP Phones

The system supports these phones on Cisco Unified CallManager Release 5.0(2) with SCCP or SIP

Cisco Unified IP Phones 7970G and Cisco Unified IP Phone 7971G-GE

Cisco Unified IP Phones 7961G and Cisco Unified IP Phone 7961G-GE

Cisco Unified IP Phones 7941G and Cisco Unified IP Phone 7941G-GE

Cisco Unified IP Phones 7960G and Cisco Unified IP Phone 7940G

Cisco Unified IP Phones 7912G and Cisco Unified IP Phone 7905G

Cisco Unified IP Phones 7911G


Note The following phones operate with Cisco Unified CallManager 5.0(2); however, they do not support new Cisco Unified CallManager 5.0(2) features: Cisco Unified IP Phones 7985G, 7936, 7935, 7920, and 7902G, Cisco Gateway VG248, and Cisco ATA 186 and 188.


This section contains the following topics:

Cisco Unified IP Phone Feature Differences by Protocol

Supported Cisco Unified IP Phones Using SIP

New Features Supported by Cisco Unified CallManager Release 5.0(2)

Feature Support Listed by Phone and Protocol

Cisco Unified IP Phones 7911G, 7941G, 7941G-GE, 7961G, 7961G-GE, 7970G, and 7971G-GE

Cisco Unified IP Phones 7940G and 7960G

Cisco Unified IP Phones 7905G and 7912G

Cisco Unified IP Phone Feature Differences by Protocol

This section provides information about feature support for Cisco Unified IP Phones that support SCCP and SIP with Cisco Unified CallManager Release 5.0(2).


Note This does not constitute a complete list of the Cisco Unified IP Phones that are compatible with Cisco Unified CallManager Release 5.0(2). This information focuses solely on those phones that support SCCP and SIP with this release.


Supported Cisco Unified IP Phones Using SIP

New Features Supported by Cisco Unified CallManager Release 5.0(2)

Feature Support Listed by Phone and Protocol

Cisco Unified IP Phones 7911G, 7941G, 7941G-GE, 7961G, 7961G-GE, 7970G, and 7971G-GE

Cisco Unified IP Phones 7940G and 7960G

Cisco Unified IP Phones 7905G and 7912G

Supported Cisco Unified IP Phones Using SIP

In addition to existing SCCP support, Cisco Unified CallManager Release 5.0(2) introduces native SIP support for most Cisco Unified IP Phones. You can now choose the protocol with which these phones connect and interact with Cisco Unified CallManager.

Cisco Unified CallManager Release 5.0(2) with SCCP and SIP supports these phones with varying levels of feature support:

Cisco Unified IP Phones 7970G and 7971G-GE

Cisco Unified IP Phones 7961G and 7961G-GE

Cisco Unified IP Phones 7941G and 7941G-GE

Cisco Unified IP Phones 7960G and 7940G

Cisco Unified IP Phones 7912G and 7905G

Cisco Unified IP Phones 7911G

New Features Supported by Cisco Unified CallManager Release 5.0(2)

Cisco Unified CallManager Release 5.0(2) supports these new features:

Busy Lamp Field (BLF) Call Lists (Presence)

Busy Lamp Field (BLF) Speed Dial (Presence)

Do Not Disturb

Personal Directory Enhancements

Voice Quality Metrics

URL Dialing

Some of these new features require configuration changes on Cisco Unified CallManager while others only require new firmware updates to the phones. Be aware that not all these features are available on all phone platforms and protocols. For details about feature support per phone and protocol, see the "Feature Support Listed by Phone and Protocol" section.

Feature Support Listed by Phone and Protocol

Although Cisco Unified CallManager Release 5.0(2) provides native SIP support for many Cisco Unified IP Phones, the phones support different features depending on which protocol is implemented. These sections provide information about feature support differences between SCCP and SIP:

Cisco Unified IP Phones 7911G, 7941G, 7941G-GE, 7961G, 7961G-GE, 7970G, and 7971G-GE

Cisco Unified IP Phones 7940G and 7960G

Cisco Unified IP Phones 7905G and 7912G

These sections focus on end-user features. You can find descriptions of existing end-user features in the Cisco Unified IP Phone Features A - Z guide that is available online at

http://www.cisco.com/univercd/cc/td/doc/product/voice/c_ipphon/english/ipp7960/az_user.htm

For descriptions about the new end-user and administrative features (including security features), refer to the "Cisco Unified CallManager Administration" section and the "Security Features" section.

Cisco Unified IP Phones 7911G, 7941G, 7941G-GE, 7961G, 7961G-GE, 7970G, and 7971G-GE

In most cases, the Cisco Unified IP Phones 7911G, 7941G, 7941G-GE, 7961G, 7961G-GE, 7970G, and 7971G-GE support similar features whether on SCCP or SIP. Table 4 provides a high-level overview of calling features and their support by protocol. This table focuses primarily on end-user calling features, and it does not represent a comprehensive listing of all available phone features. For details about user interface differences and feature use, refer to the phone guide for your phone. The table references specific sections.

Table 4 Cisco Unified IP Phones 7911G, 7941G, 7941G-GE, 7961G, 7961G-GE, 7970G, and 7971G-GE Feature Support by Phone and Protocol 

Features
Cisco Unified IP Phones 7911G, 7941G, 7941G-GE, 7961G, 7961G-GE, 7970G, and 7971G-GE
For More Information
SCCP
SIP
Calling Features

Abbreviated Dialing

Supported

Supported

"Basic Call Handling—Placing a Call: Additional Options"

Answer Release

Supported

Supported

 

Auto Answer

Supported

Supported

"Using a Handset, Headset, and Speakerphone—Using Auto Answer"

Auto Dial

Supported

Supported

"Basic Call Handling—Placing a Call: Basic Options"

Barge (and cBarge)

Supported

Supported

"Advanced Call Handling—Using a Shared Line"

Busy Lamp Field (BLF) Call Lists

Supported
Not supported on 7911G

Supported
Not supported on 7911G

"Advanced Call Handling—Determining if Another Line is Busy or Idle"

Busy Lamp Field (BLF) Speed Dial

Supported
Not supported on 7911G

Supported
Not supported on 7911G

"Advanced Call Handling—Determining if Another Line is Busy or Idle"

Call Back

Supported

Supported

"Basic Call Handling—Placing a Call: Additional Options"

Call Forward All

Supported

Supported

"Basic Call Handling—Forwarding All Calls to Another Number"

Call Forward Busy

Supported

Supported

Users do not interact with this feature directly. It is configured on Cisco Unified CallManager

Call Forward No Answer

Supported

Supported

Users do not interact with this feature directly. It is configured on Cisco Unified CallManager

Call Park

Supported

Supported

"Advanced Call Handling—Storing and Receiving Parked Calls"

Call Pickup/Group Call Pickup

Supported

Supported

"Advanced Call Handling—Picking Up a Redirected Call on Your Phone"

Call Waiting

Supported

Supported

"Basic Call Handling—Answering a Call"

Caller ID

Supported

Supported

"An Overview of Your Phone—Understanding Touch Screen Features" or "An Overview of Your Phone—Understanding Phone Screen Features"

Client Matter Codes (CMC)

Supported

"Basic Call Handling—Placing a Call: Additional Options"

Conference

Supported

Supported

"Basic Call Handling—Making Conference Calls"

Conference List

Supported

Supported

"Basic Call Handling—Making Conference Calls"

Computer Telephony Integration (CTI) Applications

Supported

Limited Support

Users do not interact with this feature directly. It is configured on Cisco Unified CallManager

Do Not Disturb (DND)

Supported

"Basic Call Handling—Using Do Not Disturb"

Distinctive Ring

Supported

Supported

"Using Phone Settings—Customizing Rings and Message Indicators"

Extension Mobility

Supported

Supported

"Advanced Call Handling—Using Cisco Extension Mobility"

Fast Dial Service

Supported

Supported

"Advanced Call Handling—Speed Dialing"

Forced Authorization Codes (FAC)

Supported

"Basic Call Handling—Placing a Call: Additional Options"

Help System

Supported
Not supported on 7911G

Supported
Not supported on 7911G

"An Overview of Your Phone—Understanding Feature Buttons and Menus"

Hold/Resume

Supported

Supported

"Basic Call Handling—Using Hold and Resume"

Immediate Divert

Supported

Supported

"Basic Call Handling—Answering a Call"

Join/Select

Supported

"Basic Call Handling—Making Conference Calls"

Malicious Call ID

Supported

"Advanced Call Handling—Tracing Suspicious Calls"

Meet-Me Conference

Supported

Supported

"Basic Call Handling—Making Conference Calls"

Multilevel Precedence and Preemption (MLPP)

Supported

"Advanced Call Handling—Prioritizing Critical Calls"

Multiple Calls per Line Appearance

200
7911G supports up to 6

50
7911G supports up to 6

"An Overview of Your Phone—Understanding Lines vs. Calls"

Mute

Supported
Supported as Monitor feature on 7911G

Supported
Supported as Monitor feature on 7911G

"Basic Call Handling—Using Mute"

On-hook Dialing/Pre-Dial

Supported

Supported

"Basic Call Handling—Placing a Call: Basic Options"

Privacy

Supported

Supported

"Advanced Call Handling—Using a Shared Line"

Quality Reporting Tool (QRT)

Supported

Supported

"Troubleshooting—Using the Quality Reporting Tool"

Redial

Supported

Supported

"Basic Call Handling—Placing a Call: Basic Options"

Shared Line

Supported

Supported

"Advanced Call Handling—Using a Shared Line"

Speed Dialing

Supported

Supported

"Advanced Call Handling—Speed Dialing"

Transfer

Supported

Supported

"Basic Call Handling—Transferring Calls"

Transfer - Direct Transfer

Supported

"Basic Call Handling—Transferring Calls"

URL Dialing

Supported

"Using Call Logs and Directories—Using Call Logs"

Video Support

Supported
7911G does not support Cisco Unified Video Advantage

"Understanding Additional Configuration Options"

Voice Mail

Supported

Supported

"Accessing Voice Messages" section of the Phone Guide

Web Dialer

Supported

Supported

"Customizing Your Phone on the Web—Configuring Features and Services on the Web"

Settings

Call Statistics

Supported

Supported

"Troubleshooting Your Phone—Viewing Phone Administrative Data"

Voice Quality Metrics

Supported

"Troubleshooting Your Phone—Viewing Phone Administrative Data"

Services

SDK Compliance

4.0(1)

4.0(1)

Cisco Unified IP Phone Service Application Development Notes for Release 4.1(3) or later

Directories

Call Logs

Supported

Supported

"Using Call Logs and Directories—Directory Dialing"

Corporate Directories

Supported

Supported

"Using Call Logs and Directories—Directory Dialing"

Personal Directory Enhancements

Supported

Supported

"Using Call Logs and Directories—Directory Dialing"

Supplemental Features and Applications

Cisco Unified CallManager Assistant

Supported
Not supported on 7911G

Cisco Unified CallManager Assistant User Guide

Cisco Unified CallManager 
AutoAttendant

Supported

Cisco Unified CallManager Features and Services Guide

Cisco Unified CallManager Attendant Console

Supported

Cisco Unified CallManager Attendant Console User Guide

Cisco Unified IP Phone  Expansion Module 7914

Supported
7941G/7941G-GE and 7911G do not support

Cisco Unified IP Phone Expansion Module 7914 Guide

Cisco Unified Video Advantage

Supported
Not supported on 7911G

Cisco Unified Video Advantage User Guide


Cisco Unified IP Phones 7940G and 7960G

Cisco Unified CallManager Release 5.0(2) allows you to choose the protocol (SIP or SCCP) that you want to use to communicate with your Cisco Unified IP Phones 7940G and 7960G.

Feature use and availability depend on the protocol that you choose for your Cisco Unified IP Phone 7940G and 7960G. For information about feature use and availability by protocol, refer to the appropriate phone guide.

Table 5 provides a high-level overview of calling features and their support by protocol. This table focuses primarily on end-user calling features and it does not intend represent a comprehensive listing of all available phone features. For details about user interface differences and feature use, refer to the phone guide for your phone. The table references specific sections.

Table 5 Cisco Unified IP Phones 7940G and 7960G Feature Support by Phone and Protocol 

Features
Cisco Unified IP Phones 7940G and 7960G
For More Information
SCCP
SIP
Calling Features

Abbreviated Dialing

Supported

"Basic Call Handling—Placing a Call: Additional Options"

Answer Release

Supported

Supported

"Basic Call Handling—Answering a Call"

Auto Answer

Supported

Supported

"Basic Call Handling—Answering a Call"

Auto Dial

 

Barge (and cBarge)

Supported

"Advanced Call Handling—Using a Shared Line"

Busy Lamp Field (BLF) Call Lists

 

Busy Lamp Field (BLF) Speed Dial

Supported

"Advanced Call Handling—Determining if Another Line is Busy"

Call Back

Supported

"Basic Call Handling—Placing a Call: Additional Options"

Call Forward All

Supported

Supported

"Basic Call Handling—Forwarding All Calls to Another Number"

Call Forward Busy

Supported

Supported

Users do not interact with this feature directly. It is configured on Cisco Unified CallManager.

Call Forward No Answer

Supported

Supported

Users do not interact with this feature directly. It is configured on Cisco Unified CallManager.

Call Park

Supported

"Advanced Call Handling—Storing and Retrieving Parked Calls"

Call Pickup/Group Call Pickup

Supported

"Advanced Call Handling—Picking Up Redirected Calls"

Call Waiting

Supported

Supported

"Basic Call Handling—Answering a Call"

Caller ID

Supported

Supported

 

Client Matter Codes (CMC)

Supported

"Basic Call Handling—Placing a Call: Additional Options"

Conference

Supported

Supported

"Basic Call Handling—Making Conference Calls"

Conference List

Supported

"Basic Call Handling—Making Conference Calls"

Computer Telephony Integration (CTI) Applications

Supported

Users do not interact with this feature directly. It is configured on Cisco Unified CallManager.

Direct Transfer

Supported

"Basic Call Handling—Transferring Calls"

Distinctive Ring

Supported

"Using Phone Settings—Customizing Rings and Message Indicators"

Do Not Disturb

Supported

"Basic Call Handling—Using Do Not Disturb"

Extension Mobility

Supported

"Advanced Call Handling—Using Extension Mobility"

Fast Dial Service

Supported

"Advanced Call Handling—Speed Dialing"

Forced Authorization Codes (FAC)

Supported

"Basic Call Handling—Placing a Call: Additional Options"

Help System

Supported

Supported

"An Overview of Your Phone—Understanding Feature Buttons and Menus" section of the Phone Guide

Hold/Resume

Supported

Supported

"Basic Call Handling—Using Hold and Resume"

Immediate Divert

Supported

"Basic Call Handling—Answering a Call"

Join/Select

Supported

"Basic Call Handling—Making Conference Calls"

Malicious Call ID

Supported

"Advanced Call Handling—Tracing Suspicious Calls"

Meet-Me Conference

Supported

"Basic Call Handling—Making Conference Calls"

Multilevel Precedence and ambition (MLPP)

Supported

"Advanced Call Handling—Prioritizing Critical Calls"

Multiple Calls per Line Appearance

6

2 per line
7960G: maximum of 6 calls per phone
7940G: maximum of 4 calls per phone

"An Overview of Your Phone—Understanding Lines vs. Calls"

Mute

Supported

Supported

"Basic Call Handling—Using Mute"

On-hook Dialing/Pre-dial

Supported

"Basic Call Handling—Placing a Call: Basic Options"

Privacy

Supported

"Advanced Call Handling—Using a Shared Line"

Quality Reporting Tool (QRT)

Supported

"Troubleshooting Your Phone—Using the Quality Reporting Tool"

Redial

Supported

Supported

"Basic Call Handling—Placing a Call: Basic Options"

Shared Line

Supported

Limited Support

"Advanced Call Handling—Using a Shared Line"

Speed Dialing

Supported

Supported

"Advanced Call Handling—Speed Dialing"

Transfer

Supported

Supported

"Basic Call Handling—Transferring Calls"

Transfer - Direct Transfer

 

"Basic Call Handling—Transferring Calls"

URL Dialing

Supported

"Advanced Call Handling—URL Dialing"

Video Support

Supported

"Understanding Additional Configuration Options"

Voice Mail

Supported

Supported

"Accessing Voice Messaging

Web Dialer

Supported

"Customizing Your Phone on the Web—Configuring Features and Services on the Web"

Settings

Call Statistics

Supported

"Troubleshooting Your Phone—Viewing Phone Administrative Data"

Voice Quality Metrics

Supported

"Troubleshooting Your Phone—Viewing Phone Administrative Data"

Services

SDK Compliance

4.0(1)

3.0

Cisco Unified IP Phone Service Application Development Notes for Release 4.1(3)

Cisco Unified IP Phone Services Application Development Notes with Cisco CallManager 3.1

Directories

Call Logs

Supported

Supported

"Using Call Logs and Directories—Directory Dialing"

Corporate Directories

Supported

Supported

"Using Call Logs and Directories—Directory Dialing"

Personal Directory Enhancements

Supported

Supports SIP-only Personal Directory. Does not support new enhancements

"Using Call Logs and Directories"

Supplemental Features and Applications

Cisco Unified CallManager Assistant

Supported

Cisco Unified CallManager Assistant User Guide

Cisco Unified CallManager AutoAttendant

Supported

Cisco Unified CallManager Features and Services Guide

Cisco Unified CallManager Attendant Console

Supported

 

Cisco Unified IP Phone  Expansion Module 7914

Supported
7940G does not support.

Cisco Unified IP Phone Expansion Module 7914 Guide

Cisco Unified Video Advantage

Supported

Cisco Unified Video Advantage User Guide


Cisco Unified IP Phones 7905G and 7912G

Cisco Unified CallManager Release 5.0(2) allows you to choose which protocol (SIP or SCCP) that you want to use to communicate with your Cisco Unified IP Phones 7905G and 7912G.

Feature use and availability depend on the protocol that you choose for your Cisco Unified IP Phones 7905G and 7912G. For information about feature use and availability by protocol, refer to the appropriate phone guide.

Table 6 provides a high-level overview of calling features and their support by protocol for the Cisco Unified IP Phones 7905G and 7912G. This table focuses primarily on end-user calling features and it does not represent a comprehensive listing of all available phone features. For details about user interface differences and feature use, refer to the phone guide for your phone. The table references specific sections.

Table 6 Cisco Unified IP Phones 7905G and 7912G Feature Support by Phone and Protocol 

Features
Cisco Unified IP Phones 7905G and 7912G
For More Information
SCCP
SIP
Calling Features

Abbreviated Dialing

Supported

"Basic Call Handling—Placing a Call"

Answer Release

Supported

Supported

"Basic Call Handling—Answering a Call"

Auto Answer

Supported

"Basic Call Handling—Answering a Call"

Auto Dial

 

Barge (and cBarge)

Supports cBarge only

"Advanced Call Handling—Understanding Shared Lines"

Busy Lamp Field (BLF) Call Lists

 

Busy Lamp Field (BLF) Speed Dial

 

Call Back

Supported

"Basic Call Handling—Placing a Call"

Call Forward All

Supported

Supported

"Quick Reference—Using Call Forward"

Call Forward Busy

Supported

Supported

Users do not interact with this feature directly. It is configured on Cisco Unified CallManager

Call Forward No Answer

Supported

Supported

Users do not interact with this feature directly. It is configured on Cisco Unified CallManager

Call Park

Supported

"Advanced Call Handling—Storing and Retrieving Parked Calls"

Call Pickup/Group Call Pickup

Supported

"Advanced Call Handling—Picking Up a Redirected Call on Your Phone"

Call Waiting

Supported

Supported

"Basic Call Handling—Call Waiting"

Caller ID

Supported

Supported

 

Client Matter Codes (CMC)

Supported

"Basic Call Handling—Placing a Call"

Conference

Supported

Supported

"Quick Reference—Making Conference Calls"

Conference List

Supported

"Basic Call Handling—Making Conference Calls"

Computer Telephony Integration (CTI) Applications

Supported

Users do not interact with this feature directly. It is configured on Cisco Unified CallManager

Do Not Disturb (DND)

Supported

"Basic Call Handling—Additional Features Available from the Call Preferences Menu"

Distinctive Ring

 

Extension Mobility

Supported

"Advanced Call Handling—Using Cisco Extension Mobility"

Fast Dial Service

Supported

"Customizing Your Phone on the Web—Configuring Features and Services on the Web"

Forced Authorization Codes (FAC)

Supported

"Basic Call Handling—Placing a Call"

Help System

 

Hold/Resume

Supported

Supported

"Basic Call Handling—Using the Hold Button"

Immediate Divert

Supported

"Basic Call Handling—Answering a Call"

Join/Select

Supported

"Basic Call Handling—Making Conference Calls"

Malicious Call ID

Supported

"Advanced Call Handling—Tracing Suspicious Calls"

Meet-Me Conference

Supported

"Quick Reference—Making Conference Calls"

Multilevel Precedence and Preemption (MLPP)

Supported

"Advanced Call Handling—Prioritizing Critical Calls"

Multiple Calls per Line Appearance

6

2

"An Overview of Your Phone—Call Handling and Navigation Tips"

Mute

 

On-hook Dialing/Pre-Dial

Supported

Supported

"Basic Call Handling—Placing a Call"

Privacy

Supported

"Advanced Call Handling—Understanding Shared Lines"

Quality Reporting Tool (QRT)

Supported

"Troubleshooting Your Phone—Using the Quality Reporting Tool"

Redial

Supported

Supported

"Basic Call Handling—Placing a Call"

Shared Line

Supported

Limited Support

"Advanced Call Handling—Understanding Shared Lines"

Speed Dialing

Supported

Supported

"Quick Reference—Using Speed Dial"

Transfer

Supported

Supported

"Quick Reference—Transferring a Call"

Transfer - Direct Transfer

Supported

"Quick Reference—Transferring a Call"

URL Dialing

 

Video Support

 

Voice Mail

Supported

Supported

"Using Voice Messaging, Call Logs, and Directories"

Web Dialer

Supported

"Customizing Your Phone on the Web—Configuring Features and Services on the Web"

Settings

Voice Quality Metrics

 

Call Statistics

Supported

 
Services

SDK Compliance

4.1(3)

 
Directories

Call Logs

Supported

Supported

"Using Voice Messaging, Call Logs, and Directories"

Corporate Directories

Supported

 

Personal Directory Enhancements

Supported

 
Supplemental Features and Applications

Cisco Unified CallManager Assistant

Cisco Unified CallManager Assistant User Guide

Cisco Unified CallManager AutoAttendant

Supported

Cisco Unified CallManager Features and Services Guide

Cisco Unified CallManager Attendant Console

Supported

 

Cisco Unified IP Phone Expansion Module 7914

Cisco Unified IP Phone Expansion Module 7914 Guide

Cisco Unified Video Advantage

Cisco Unified Video Advantage User Guide


New and Changed Information for Third-Party API

This following sections describe new features and changes that are pertinent to this release of Cisco Unified CallManager and third-party APIs.

Cisco Unified CallManager Developers Guide

CDR Definitions

Cisco Unified IP Phone Service Application Development Notes for Cisco Unified CallManager 5.0(2)

JTAPI Developers Guide

SCCP Messaging Guide

SIP Messaging Guide

TAPI Developers Guide

Cisco Unified CallManager Developers Guide

The Cisco Unified CallManager Developers Guide, a new document, comprises four existing programming guides. This document describes the following Cisco Unified CallManager APIs:

AXL Programming

The following list describes the AXL API enhancements for Cisco Unified CallManager Release 5.0(2):

This release adds the following AXL APIs:

executeSQLUpdate

doAuthenticateUser

updateAppUser

addUserGroup

updateUserGroup

removeUserGroup

getUserGroup

This release modifies the following AXL API's:

addPhone

updatePhone

getPhone

addGatewayEndpoint

updateGatewayEndpoint

getGatewayEndpoint

addMGCPEndpoint

updateMGCP

addSIPTrunk

updateSIPTrunk

getSIPTrunk

addCallManager

updateCallManager

getCallManager

addCallPark

addRoutePattern

updateRoutePattern

updateTransPattern

updateHuntPilot

addHuntList

updateHuntList

getHuntList

addPilotPoint

updatePilotPoint

getPilotPoint

addH323Gateway

updateH323Gateway

updateH323Phone

getH323Gateway

getH323Trunk

addUser

updateUser

getUser

updateProcessNodeService

getProcessNodeService

listUserByName

updateServiceParameter

updateGatekeeper

updateConferenceBridge

updateAttendantConsoleHuntGroup

updateDeviceProfile

updateLine

updateLineGroup

addDevicePool

updateDevicePool

doDeviceReset

This release deprecates the following AXL APIs:

addDDI

updateDDI

removeDDI

addDialPlan

updateDialPlan

removeDialPlan

addDialPlanTag

updateDialPlanTag

removeDialPlanTag

Refer to the schema of these APIs for detailed information of the enhancements.

The following changes in AXL apply for Cisco Unified CallManager 5.0(2).

AXL gets deployed as a web application within Tomcat.

The URL for accessing AXL changes to https://server_name:8443/axl/

where server_name specifies the host on which AXL Web Service is running.

The system no longer supports some of the error codes in AXL. Users need to update their applications and modify their error handling to accommodate these changes.

For a user to access AXL, you must assign proper permission through the User Management menu under Cisco Unified CallManager Administration. Ensure the Application User is added to an existing or new User Group that has the AXL API Access role assigned to it.

AXL Serviceability Programming

The following list provides the new features or changes for the AXL Serviceability API in Cisco Unified CallManager Release 5.0(2):

Perfmon Data Collection Service—This service now gets exposed through a new framework called the Perfmon Infrastructure and System Information Library, which provides platform/OS counters. The APIs remain the same; however, the information that is provided through these APIs will be similar but not exactly the same. Windows performance counters will not be available.

Real-time and Perfmon WSDL interfaces get preserved, except the URL differs from previous releases for each SOAP service.

Real-Time Information (RisPort)—No changes occurred for this release.

Server Query Service—This service exports the following information from the Server Information SOAP interface:

Host Name

OS Name

OS Arch

OS Version

Java Runtime Version

Java Virtual Machine Vendor

CallManager Version

Service Interface—This service allows you to do Service Deploy, Service UnDeploy, and Get Service List and to perform service start and stop.

Log Collection Service—This service, a public SOAP/HTTPS interface, allows applications to retrieve lists of services and log files through the use of three APIs: listNodeServiceLogs, selectLogFiles, and getOneFile.

CDR on Demand Service—This service, a public SOAP/HTTPS interface, gets exposed to third-party billing applications or customers to allow them to query the Cisco Unified CallManager, specifically the CDR Repository Node, to retrieve CDR/CMR files on demand through the use of two APIs, get_file_list and get_file.

Disaster Recovery Framework Service—This release does not implement DRF API.

The following enhancements exist in Serviceability for AXL:

You can access AXL by using Cisco Unified CallManager Serviceability
(Serviceability > Tools AXL Web Service).

Serviceability provides an option to activate/deactivate AXL Web Service
(Serviceability > Tools > Service Activation).

Serviceability provides an option to start and stop AXL Web Service
(Serviceability > Tools > Control Center - Feature Services).

Serviceability provides an option to change trace levels for AXL
(Serviceability > Trace > Configuration).

Extension Mobility API

The following list describes the Extension Mobility API enhancements for Cisco Unified CallManager 5.0(2):

Dial Plan on Phone—SIP phones have dial plan information pushed to them via a Config file. This dial plan takes the form of an unordered list of dial maps. One dial plan corresponds to each CSS.

In the case of extension mobility, the effective list of CSSs for a phone comprises a combination of "Device CSS" and "Line CSS." Device CSS gets tied to the physical attributes of the phone like location, region, and so on, and does not change across login/logout of users. Line CSS gets tied to the lines and changes when users log in/log out.

DBL generates the appropriate list of dialmaps when login/logout operations are performed. Because each CSS has a dial map linked with it, the DBL module will extract dial map information for each line in the device profile. It will append this information to the dial map that corresponds to Device CSS. The resulting dial map list gets pushed to the configuration file.

SRST mode—In SRST mode, the extension mobility behavior remains the same as in previous releases. You cannot perform login and logout operations when a phone is in SRST mode. Call processing proceeds as normal, given that the SRST GW is configured appropriately.

Credentials for SIP Digest Authentication—Credentials for SIP digest authentication get configured in the "user directory" window. All the device profiles that associate with that user must use this set of credentials. For phones that read this information from the Config file, DBL populates the Config file with the appropriate credential set.

For phones that do not support Digest credentials in the Config file, digest authentication can break. For extension mobility, the SIP digest credentials will change when a user logs in and out. The user must enter the credentials when a call is placed.

Cisco Web Dialer Developers Guide

The following list describes the Cisco Web Dialer enhancements for Cisco Unified CallManager Release 5.0(2):

Modify logging mechanism to apply the changes to both Cisco Web Dialer and Redirector.

Make Redirector functional with HTTPS. This release has partial Redirector support for HTTPS.

Cisco Web Dialer subscribe for Dial Rule Change Notification.

Cisco Web Dialer support for enhancements in CTI and JTAPI.

Migration of dial rule data during an upgrade from Windows to Linux.

SIP support in Cisco Web Dialer.

Increase in thread count to 3.

CDR Definitions

The transition from an SQL database to flat files represents the major change in CDRs/CMRs in this release. If you upgrade from Cisco Unified CallManager 4.x, the CDRs in the CAR database get converted to CSV files, which the CDR repository stores.

The following list describes the CDR enhancements for Cisco Unified CallManager Release 5.0(2):

Cisco Unified CallManager will generate a special CDR/CMR to identify when these records are enabled or disabled.

A single sequence number now gets used for both CDR and CMR files.

This means that the CDR and the corresponding CMR will reside within a reasonable number of files and can more easily be correlated.

In addition to the existing voice quality data that the SCCP phone supports, this release adds new measurements in the new varVQMetrics field.

The QoS Support (RSVP) feature adds four new CDR fields to reflect the status of RSVP bandwidth reservation per audio or video stream for both the origin and destination.

This release adds a new CDR field per party to show what DTMF method is being used by that party for given call.

A new Call Secured Status field that is added to the CDR contains an indication of the highest level of security that is reached during the call.

This release includes three new SIP features (Refer, Replaces, and Redirection). Calls that involve these features will generate CDRs, but these features require no new CDR fields.

Depending on the features and the call scenario, the major difference means that the party fields may contain SIP URIs instead of numbers.

These new SIP features (Refer, Replaces, and Redirection) also include new onBehalfOf field values.

This release enhances and separates the Pickup feature from the Forwarding feature. Specifically, the pickup by redirect and monitoring of pickup groups move from the Forwarding feature to the Pickup feature.

The Q.931 call release cause codes remain the same; however, the Cisco-specific call release cause codes changed values, and this release adds several new codes. The release also adds a new table of SIP call release cause codes.

Refer to the CDR Definitions Guide for a complete description of these enhancements.

Cisco Unified IP Phone Service Application Development Notes for Cisco Unified CallManager 5.0(2)

This section provides the information that is needed for programmers and system administrators to develop and deploy new Cisco Unified IP Phone services with Cisco Unified CallManager 5.0, using eXtensible Markup Language (XML) objects and the Hyper Text Transfer Protocol (HTTP) with standard web servers. Cisco conforms as closely as possible to the XML and HTTP standards while providing maximum service functionality for Cisco Unified IP Phones.

JTAPI Developers Guide

The JTAPI Developers Guide now includes a chapter on installation of the JTAPI Client. Previously, the installation of JTAPI Client was supported only on Windows platforms. With this release, the JTAPIInstaller provides a unified installation/uninstallation process for the JTAPI Client for Linux, Windows, and Solaris.

For Linux and Solaris versions, the InstallShield MultiPlatform (ISMP) installer generates a binary file (.bin), and, for the Windows version, it generates an executable file (.exe), after the set of files that need to be installed is obtained.

The following list describes the JTAPI enhancements for Cisco Unified CallManager 5.0(2).

The basic changes for the end user of JTAPI applications follow:

JTAPI Applications users must migrate to JDK 1.4.

JTAPIPreferences will not work if users do not have JDK 1.4 installed.

JTAPI Applications that use jsafe.jar or log4j.jar may be impacted.

This release includes the following JTAPI enhancements:

Partition Support

Hairpin Support

QoS Support

Transport Layer Security

SIP Phone Support

Secure Real-Time Protocol (SRTP)

SIP REFER / REPLACES

SIP 3XX Redirection

Backward Compatibility

Address and Terminal Restriction

Unicode Support for JTAPI

Linux and Solaris Install

JDK 1.4 Migration

Network Alerting Change

SuperProvider Additional Functionality

Alternate Script Support

Half-Duplex Media Support

Refer to the JTAPI Developers Guide for a complete description of these enhancements.

SCCP Messaging Guide

The following list describes the SCCP messaging enhancements for Cisco Unified CallManager Release 5.0(2):

This release deprecates the following SCCP messages:

StationEnunciatorCommand

StationIpPortMessage

StationMediaPortListMessage

StationSetHkFDetectMessage

This release modifies the following SCCP messages:

StationCloseMultiMediaReceiveChannel

StationCloseReceiveChannelMessage

StationConnectionStatisticsResMessage

StationOpenMultiMediaReceiveChannel

StationOpenReceiveChannelMessage

StationRegisterMessage

StationStartMediaTransmissionMessage

StationStartMultiMediaTransmission

StationStopMediaTransmissionMessage

StationStopMultiMediaTransmission

This release adds the following SCCP messages:

StationMediaPathCapabilityMessage

StationMediaPathEventMessage

StationNotificationMessage

StationSubscriptionStatMessage

StationSubscriptionStatReqMessage

StationVideoDisplayCommandMessage

Refer to the SCCP Messaging Guide for a complete description of these enhancements.

SIP Messaging Guide

The SIP Messaging Guide, a new book for Cisco Unified CallManager Release 5.0(2), describes the external interface for the Cisco Unified CallManager SIP trunk device. It highlights the SIP primitives that are supported across the SIP trunk and basic call flow scenarios that can be used as a guide for technical support.

TAPI Developers Guide

The TAPI Developers Guide now includes a chapter on installation. No changes occurred to the TAPI installation for Cisco Unified CallManager Release 5.0(2).

The following list describes the TAPI enhancements for Cisco Unified CallManager Release 5.0(2):

QoS Support

Partition Support

Alternate Script Support

TLS Support

SRTP Support

Super Provider Support

Refer/Replaces Support

SIP URL Address Support

3XX Support

Refer to the TAPI Developers Guide for a complete description of these enhancements.

Caveats

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

Caveats describe unexpected behavior on a Cisco Unified CallManager 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 CallManager Release 5.0(4x) by using Bug Toolkit, which is an online tool that is available for customers to query defects according to their own needs.


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://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl.


This section includes the following topic:

Using Bug Toolkit

Using Bug Toolkit

Known problems (bugs) are 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 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.


Note For information about how to search for bugs, create saved searches, create bug groups, etc, click Help in the Bug Toolkit page.


Open Caveats

Table 7 describes possible unexpected behaviors in Cisco Unified CallManager Release 5.0(4x) sorted by component.


Tip For more information about an individual defect, click the associated Identifier in Table 7 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 CallManager interim versions in which the defect was fixed. These interim versions then get integrated into Cisco Unified CallManager 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 CallManager 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 CallManager release that includes that interim version. You can use these examples as guidance to better understand the presentation of information in these fields.

003.003(003.144) = Cisco CallManager Release 3.3(4)

004.000(000.123) = Cisco Unified CallManager Release 4.0(1)

004.000(001.008) = Cisco Unified CallManager Release 4.0(2)

004.001(002.201) = Cisco Unified CallManager Release 4.1(3)


Note Because defect status continually changes, be aware that Table 7 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.


.

Table 7 Open Caveats as of 9-23-07 

Identifier
Headline

Component: CLI

CSCsi64187

CLI becomes garbled. Text does not appear where expected, lines do not wrap at screen boundary.

CSCsc91158

The file tail command the CLI is slow which means that if you use the command to follow a Cisco Unified CallManager log, you do not get a real-time view of the data.

Component: Cisco Unified CallManager Documentation

CSCsh45275

Personal Address Book does not synchronize directly with Outlook contacts.

Component: CTI

CSCse21959

Memory corruption causes CTIManager crash.

CSCse40035

At TAPI application, wrong call information (LRP) is returned on transfer and forward scenarios through a QSIG gateway with path replacement.

CSCsh62050

CTI does not verify QBE versions.

CSCeg85332

Memory leak in StationInit when an open device unregisters.

CSCsi06589

CTI does not verify that the number of ConsultCalls is within the range of maximum consult calls.

CSCsd34080

At TAPI application, inconsistent call information is returned on QSIG scenarios.

Component: Call Processing

CSCsk07661

Huntlist: Hunt group logout impacts HL circular distribution.

CSCek47003

Media Control: Notify media about video reservation gets lost mid-call.

CSCef11657

Media Control: Remote video window goes blank when video bandwidth is insufficient.

CSCeg20136

Media Control: RSVP: Need to flow control video stream based on video bandwidth adjust outcome

CSCsd85096

SCCP: External phone number mask displays "Unknown" with X's before prefix.

CSCef09978

SCCP: Unnecessary messages sent from stationD to stationD during registration slows registration.

CSCsh36576

System: If the "DSCP for Cisco CallManager to Device Interface" enterprise parameter is set higher than CS4 (the default is CS3), the signaling packets from Cisco Unified CallManager will be tagged with DSCP 000000 instead of the configured DSCP.

Component: CPI

CSCsk18230

Data Migration Assistant: The need exists for DMA to provide more feedback when validation fails.

CSCse81663

Operating System: iLO firmware may be below minimum required version.

CSCsf26301

Operating System: Smart Array 5i requires harddrive firmware upgrade to avoid POST notification.

CSCsj58962

Operating System: HP Smart Array 6i firmware upgrade.

CSCse71185

Operating System: Some Hewlett-Packard Ultra320 SCSI harddrives may exhibit reduced performance and timeouts

CSCse71209

Operating System: Smart Array 6i requires harddrive firmware update to avoid POST notification.

CSCsk21776

Operating System: The need exists to support G0 stepping CPU for 7835/45 I2/H2/D2 servers.

CSCsk50525

Operating System: After upgrade, system displays a prompt to configure RAID controller.

CSCsi71874

Platform API: At times the administrative GUIs do not respond after a server restart or switch version command.

Component: Database

CSCsj40566

Non-ASCII characters used in Cisco Unified CallManager 4.x cannot be migrated or used in Cisco Unified CallManager 5.x and later.

CSCsh45042

Informix replication logs get written to the /tmp directory.

CSCsb71648

Upgrad requires excessive database migration time.

Component: Install Product

CSCsj56299

CDR Analysis and Reporting does not reflect Daylight Savings Time changes for New Zealand.

Component: JTAPI SDK

CSCsg03945

CiscoJTAPIClient-linux.bin does not install.

Component: TAPI SDK

CSCsb64096

Application stuck during RecordWave with Silence.


Troubleshooting

For troubleshooting information, refer to the Troubleshooting Guide for Cisco Unified CallManager, Release 5.0(4). This document provides troubleshooting procedures for Cisco Unified CallManager systems. The Troubleshooting Guide for Cisco Unified CallManager, Release 5.0(4) provides guidance for network administrators who are responsible for managing the Cisco Unified CallManager system, for enterprise managers, and for employees. This document does not cover every possible trouble event that might occur on a Cisco Unified CallManager system but instead focuses on those events that are frequently seen by the Cisco Technical Assistance Center (TAC) or frequently asked questions from newsgroups.

Documentation Updates

This section provides documentation changes that were unavailable when the Cisco Unified CallManager Release 5.0 documentation suite was released.

Errors

Changes

Omissions

Corrections

Errors

This section includes information about errors in the Cisco Unified CallManager Documentation suite:

Description of the Reset Button

Description of the Cisco Unified IP Phone Proxy Server

Definition of Originating Codec and Destination Codec

Name Correction for Cisco Database Service

Using the Command Line Interface to Stop/Start Services

Guidelines for the Cisco Unified CallManager Application User

Enabling the Super Provider Feature for Cisco Unified CallManager Attendant Console

SIP Profile Configuration

Web Dialer Service Parameters

Viewing Field Descriptions and Help for Product-Specific Configuration

Cisco Extension Mobility

Cisco CAR Web Service/Cisco CAR Scheduler Service

Real-Time Monitoring Tool

Device Authentication Application User

Launching Cisco Unified CallManager Attendant Console

Description of the Reset Button

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

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


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


Description of the Cisco Unified IP Phone Proxy Server

The Cisco Unified IP Phone Configuration chapter of the Cisco Unified CallManager Administration Guide incorrectly states the description of the Proxy Server. The following table provides the correct description.

Field
Description

External Data Locations Information

Proxy Server

Enter the host and port (for example, proxy.cisco.com:80) that are used to proxy HTTP requests for access to non-local host addresses from the phone HTTP client.

The rule contains two parts for when to use the proxy server parameter:

1. The hostname contains a "."

2. The hostname represents an IP address in any form.

If you do not configure this URL, the phone attempts to connect directly to the URL.

Leave this field blank to accept the default setting.


Definition of Originating Codec and Destination Codec

The CAR Report Results chapter of the CDR Analysis and Reporting Administration Guide incorrectly states the definition of the Orig. Codec and Dest. Codec fields in the Gateway Detail Report. The correct definitions follow:

Orig. Codec—The codec code (compression or payload code) that the call originator used on its sending side during this call. This code may differ from the codec code that was used on its receiving side.

Dest. Codec—The codec code (compression or payload code) that the destination used on its sending side during this call. This code may differ from the codec code that was used on its receiving side.

Name Correction for Cisco Database Service

The Command Line Interface chapter of the Cisco Unified Communications Administration Guide incorrectly names the Cisco Database service. The correct name specifies A Cisco DB. For example, to restart the database service by using the utils service command in the CLI, enter utils service restart A Cisco DB.

Using the Command Line Interface to Stop/Start Services

The Managing Services chapter of the Cisco Unified CallManager Serviceability Administration Guide does not list all the services that can be stopped or started by using the command line interface. The complete list of services follows:

System NTP

System SSH

Service Manager

A Cisco DB

Cisco Tomcat

Cisco Database Layer Monitor

Cisco Unified CallManager Serviceability

Guidelines for the Cisco Unified CallManager Application User

You do not have to create the Cisco Unified CallManager Attendant Console application user with the user ID of "ac" before changing the user ID as stated in the Cisco Unified CallManager Features and Services Guide. You can use any user ID, but the username of the application user must match the JTAPIUsername parameter that is configured in the service parameters for Attendant Console Server service.

Enabling the Super Provider Feature for Cisco Unified CallManager Attendant Console

You can enable Cisco Unified CallManager Attendant Console devices without associating each of the them with the Cisco Unified CallManager Attendant Console application user by enabling the super provider feature. To do this, add the Cisco Unified CallManager Attendant Console application user to the Standard CTI Allow Control of All Devices user group. After you enable the super provider feature, you do not have to associate pilot points and attendant phones to the Cisco Unified CallManager Attendant Console user.

During an upgrade from Cisco Unified CallManager Release 4.X, the system automatically converts the attendant console application user to a superprovider user and disassociates the devices that were previously associated to the application user.

SIP Profile Configuration

The SIP Profile Configuration chapter of the Cisco Unified CallManager Administration Guide and online help incorrectly include the description of the field, KPML, in the SIP Profile Configuration Settings table. Be aware that this field is no longer valid.

Web Dialer Service Parameters

The Setting Service Parameters for the Web Dialer Servlet section of the Cisco Web Dialer chapter that is in the Cisco Unified CallManager Features and Services Guide should be updated to the following.

To enter new values, enter the IP address of the Cisco Unified CallManager server and the port number on which Cisco Web Dialer is enabled.

Cisco Unified CallManager Administration 5.0 requires that you specify the port number; for example, "172.19.253.97:8443" with "8443" as the port number.

Viewing Field Descriptions and Help for Product-Specific Configuration

The Cisco Unified CallManager Bulk Administration Guide and the Cisco Unified CallManager Serviceability System Guide contain incorrect information on how to display the field descriptions and help for the product-specific configuration fields. It incorrectly states that you should click the "i" information icon to the right of the Product Specific Configuration heading to display help in a popup dialog box. It should state that you should click the "?" icon.

Cisco Extension Mobility

The Cisco Extension Mobility chapter of the Cisco Unified CallManager Features and Services Guide incorrectly states the maximum number of login and logout operations that Cisco Extension Mobility supports. The corrected document provides the following information:

Cisco Extension Mobility supports a maximum of 50 login and logout operations per minute (or 3000 operations per hour). Remember that these operations are sequential, not concurrent.

Cisco CAR Web Service/Cisco CAR Scheduler Service

The document, Cisco Unified CallManager Serviceability System Guide, incorrectly states that you must activate the Cisco CallManager service if you activate the Cisco CAR Web service or the Cisco CAR Scheduler service. In fact, you do not need to activate the Cisco CallManager service when you activate the CAR services. For CAR service activation recommendations, refer to the "Managing Services" chapter of the Cisco Unified CallManager Serviceability Administration Guide.

Real-Time Monitoring Tool

The "Real-Time Monitoring Tool" chapter in the Cisco Unified CallManager Serviceability System Guide provides the wrong Cisco Unified CallManager Administration path for accessing AMC service parameters. To access the AMC service parameters, choose System > Service Parameters. For more information on how to access service parameters, refer to the Cisco Unified CallManager Administration Guide.

Device Authentication Application User

The Cisco Unified CallManager Features and Services Guide indicates that administrators must create a device authentication application user and associate all attendant phones with that user. However, administrators should only create the device authentication application user and associate phones if they want to enable device security for Cisco Unified CallManager Attendant Console

Launching Cisco Unified CallManager Attendant Console

The Cisco Unified CallManager Attendant Console chapter of the Cisco Unified CallManager Features and Services Guide indicates that the Attendant Console plug-in can be installed in a location other than the default location; however, if the plug-in does not get installed in the default location, a possibility exists that the Cisco Unified CallManager Attendant Console will not launch.

Changes

This section contains changes that have occurred since the original release of the Cisco Unified CallManager Release 5.0 documentation:

Phone Security Profile Configuration Window

Ethernet Settings

Command Line Interface

TFTP Server File Upload

Deleting Files on the Inactive Partition

Forced Shutdown

Network Failover

Utils Network Tracert Command

Performing a Software Upgrade

CTIManager Connection Security Flag

Gatekeeper-controlled Intercluster Trunk Registers Incorrectly with Gatekeeper

RSVP Agent Configuration with Transcoder

Path Replacement Calling Search Space Service Parameter

H.323 Information Settings on a H.323 Client

Cisco Web Dialer Does Not Close All Windows After Dialing

User With Extension Mobility Authorization by Proxy Fails to Log In and Log Out Other Users

VD-2005-12-KE

H323 Redirecting Number IE is sent in UUIE by Cisco Unified CallManager

TS-6671 - Enabling Autoregistration

Extension Mobility Configuration Step is Missing

Music On Hold Configuration

BU-6666 - Cisco Web Dialer Servlet Service Parameter

Support of Third-Party CSRs for External CAs

Perfmon Counter Name Changes

Phone Security Profile Configuration Window

The TFTP Exclude Digest Credentials check box that displays for Cisco Unified IP Phones that are using SIP is only recommended for Cisco Unified IP Phones 7905, 7912, 7940, and 7960 because these phones use manual key distribution and can support this option properly. For other Cisco Unified IP Phones running SIP, check the TFTP Encrypted Config box to protect the configuration that is sent down from Cisco Unified CallManager to the Cisco Unified IP Phones.

Ethernet Settings

In the Cisco Unified Communications Operating System Administration Guide, all Ethernet settings only apply to Eth0. You cannot configure any settings for Eth1. Also, the Maximum Transmission Unit (MTU) on Eth0 defaults to 1500.

Command Line Interface

Appendix A of the Cisco Unified Communications Operating System Administration Guide requires the following changes:

File View command: Do not use this command to view binary files because this can corrupt the terminal session.

Show Hardware command: The command also displays the RAID controller status.

The command line interface (CLI) supports the following new command functions and options:

The show network eth0 command now displays DNS options, in addition to other DNS settings.

The show network failover command now displays DNS options, in addition to other DNS settings.

The utils network host command now supports the optional srv parameter, which you can use to fetch DNS SRV records.

The CLI now includes the set network dns options command, which is explained in the following table.

The CLI now includes the file check command, which is explained in the following table.

Command
Parameters
Description

file check

[detection-size-kb]

Where

detection-size-kb specifies the minimum file size change that is required for the command to display the file as changed.

Default minimum size: 100 KB

The command notifies you about a possible impact to system performance and asks you whether you want to continue.

Warning Because running this command can affect system performance, Cisco recommends that you run the command during off-peak hours.

Options

None

This command checks the /usr directory tree to see if any files or directories have been added, removed, or changed in size since the last fresh installation or upgrade and displays the results. The display includes both deleted and new files.


TFTP Server File Upload

In Chapter 7 of the Cisco Unified Communications Operating System Administration Guide, be aware that you can also specify the directory where you want to upload a TFTP server file.

Deleting Files on the Inactive Partition

In the Cisco Unified Communications Operating System Administration Guide, be aware that if you use the file delete inactivelog command to delete a TFTP data file on the inactive side, you may need to manually restore that file if you switch versions to the inactive side.

Forced Shutdown

In the Cisco Unified Communications Operating System Administration Guide, be aware that the utils system shutdown command has a 5-minute timeout. If the system does not shut down within 5 minutes, the command gives you the option of doing a forced shutdown.

Network Failover

In the Cisco Unified Communications Operating System Administration Guide, be aware of the following additional command parameters for setting up network fault tolerance (NFT):

set network failover {enable | disable}

show network failover [detail] [page]

NFT prevents network downtime by transferring the workload from a failed port to a working port.

Utils Network Tracert Command

In the Cisco Unified Communications Operating System Administration Guide, be aware the utils network tracert command does not accept any parameters.

Performing a Software Upgrade

If the upgrade file is located on a Linux or Unix server, you must enter a forward slash at the beginning of the directory path that you want to specify. For example, if the upgrade file is in the patches directory, you must enter /patches.

If the upgrade file is located on a Windows server, check with your system administrator for the correct directory path.

Data Migration Assistant Installation File

In the Data Migration Assistant User Guide, Release 5.0(2a), be aware that the filename for Data Migration Assistant installation file is explicitly referenced as DMASetup.exe. The naming convention for the DMA installation file uses the format DMASetup-x-y-z.exe, where x-y-z is the version.

CTIManager Connection Security Flag

The Cisco Unified CallManager Assistant (for proxy and shared lines) chapter needs to be updated for the following information about CTIManager Connection Security Flag.

The Cisco IP Manager Assistant service parameter, CTIManager Connection Security Flag, now has the following two options instead of True or False:

Nonsecure—The security mode specifies nonsecure.

Use Cluster Default—Cisco IP Manager Assistant service fetches the security mode for the cluster. If the cluster security mode is detected as mixed, Cisco Unified CallManager Assistant will open a secure connection to CTI Manager by using the Application CAPF profile. To make the secure connection succeed, configure both the "CTI Manager Connection Security Flag" and the "CAPF Profile Instance ID for Secure Connection to CTI Manager" parameters.

Gatekeeper-controlled Intercluster Trunk Registers Incorrectly with Gatekeeper

An update to the he Trunk Configuration chapter of the Cisco Unified CallManager Administration Guide provides an explanation of the Send Product ID and Version ID service parameter. You must set this service parameter to True for a gatekeeper-controlled intercluster trunk to register correctly with a gatekeeper. The "Trunk Configuration Settings" section contains the updated description in the [Gateway Information] Gatekeeper Name field.

RSVP Agent Configuration with Transcoder

The Resource Reservation Protocol chapter of the Cisco Unified CallManager System Guide provides a description of the special configuration that is necessary if you are using the RSVP Agent with a transcoder. The "Special Configuration With RSVP" section contains the new description.

Path Replacement Calling Search Space Service Parameter

An update to the Understanding IP Telephony Protocols chapter of the Cisco Unified CallManager System Guide revises the "Path Replacement" section. The section now contains the following text:

Cisco Unified CallManager provides the Path Replacement Calling Search Space service parameter, so you can configure the calling search space that the cooperating PINX uses to send the outbound SETUP message to the requesting PINX. If you do not specify a value for the Path Replacement Calling Search Space service parameter, the requesting PINX uses the calling search space of the end user that is involved in the call.

H.323 Information Settings on a H.323 Client

An update to the Cisco Unified IP Phone Configuration chapter of the Cisco Unified CallManager Administration Guide revises the "Phone Configuration Settings" section. The following fields now contain revised descriptions:

[H.323 Information] Outgoing Caller ID Pattern

[H.323 Information] Calling Party Selection

[H.323 Information] Calling Party Presentation

Cisco Web Dialer Does Not Close All Windows After Dialing

This issue required changes to the phone user documentation. The Cisco Web Dialer chapter of the Cisco Unified CallManager Features and Services Guide includes a reference to the pertinent phone user documentation in the "Related Topics" section.

User With Extension Mobility Authorization by Proxy Fails to Log In and Log Out Other Users

An update to the Cisco Extension Mobility chapter of the Cisco Unified CallManager Features and Services Guide provides an additional restriction that concerns Standard Extension Mobility (EM) Authentication Proxy. The "Restrictions" section contains the added restriction.

The Roles and User Groups chapter of the Cisco Unified CallManager System Guide also explains the restriction that concerns Standard Extension Mobility (EM) Authentication Proxy. The "Standard Roles and User Groups" topic provides the updated explanation.

VD-2005-12-KE

An update to the Gateway Configuration chapter of the Cisco Unified CallManager Administration Guide corrects omissions in the description of the PRI Protocol Type field in the Gateway Configuration window. An update to the Digital Access PRI Port Configuration Settings section also occurred.

H323 Redirecting Number IE is sent in UUIE by Cisco Unified CallManager

An update changed the field definition for all occurrences of the "Redirecting Number IE - Inbound" and "Redirecting Number IE - Outbound" fields in the Gateway Configuration chapter and Trunk Configuration chapter of the Cisco Unified CallManager Administration Guide.

Extension Mobility Configuration Step is Missing

An update to the Cisco Extension Mobility chapter of the Cisco Unified CallManager Features and Services Guide revises the configuration checklist for enabling Cisco Extension Mobility. The "Configuration Checklist for Cisco Extension Mobility" section provides the updated procedure.

TS-6671 - Enabling Autoregistration

An update to the Autoregistration Configuration chapter of the Cisco Unified CallManager Administration Guide provides a more detailed procedure for enabling autoregistration. The "Enabling Autoregistration" section provides the updated procedure.

Music On Hold Configuration

An update to the Music On Hold chapter of the Cisco Unified CallManager Features and Services Guide provides updated definitions for the following configuration parameters:

Maximum Half Duplex Streams

Maximum Multicast Connections

The "Music On Hold Server Configuration Settings" section provides the updated definitions.

BU-6666 - Cisco Web Dialer Servlet Service Parameter

An update to the Cisco Web Dialer chapter of the Cisco Unified CallManager Features and Services Guide provides an updated description in the "Setting Service Parameters for the Cisco Web Dialer Servlet" section.

Support of Third-Party CSRs for External CAs

Because Cisco Unified CallManager now supports third-party CSRs for external CAs, the Cisco Unified CallManager Security Guide requires the following updates:

Cisco Unified CallManager supports third-party, CA-signed certificates for Cisco Unified CallManager node, CAPF, HTTPS Tomcat, and IPSec with a new CSR mechanism that is accessible at the platform. You can use these certificates that are signed by external CAs, instead of the Cisco self-signed certificates that are provided at installation.

To obtain third-party, CA-signed certificates, see Using Third-Party Certificate Authority Certificates. Verification of the CSR mechanism occurred with these CAs: Keon, Microsoft, and Verisign. Verification of other external CAs that support CSRs did not occur. Be sure to run the CTL client after you upload a third-party CA-signed certificate to the platform to update the CTL file.

The Cisco Unified CallManager 5.0 installation creates a self-signed certificate on Cisco Unified CallManager and TFTP servers. You may also choose to use a third-party, CA-signed certificate for Cisco Unified CallManager instead of the self-signed certificate. After you configure the cluster for authentication, Cisco Unified CallManager uses the certificate to authenticate with supported Cisco Unified IP Phones. After a certificate exists on the Cisco Unified CallManager and TFTP servers, Cisco Unified CallManager does not reissue the certificates during each Cisco Unified CallManager upgrade. You must create a new CTL file with the new certificate entries.

To authenticate with the application, CTIManager uses the Cisco Unified CallManager certificate— either the self-signed certificate that installs automatically on the Cisco Unified CallManager server during the 5.0 installation or a third-party, CA-signed certificate that you uploaded to the platform. After you install the Cisco CTL client and generate the CTL file, this certificate gets added automatically to the CTL file. Before the application attempts to connect to CTIManager, the application downloads the CTL file from the TFTP server.

Perfmon Counter Name Changes

Table 8 lists the incorrect performance counter name as it appears in Cisco Unified CallManager Serviceability System Guide along with the correct counter name.

Table 8 Perfmon Counter Name Changes 

Incorrect Counter Name
Correct Counter Name

Cisco Extension Mobility Object

Successful Logins

LoginsSuccessful

Successful Logouts

LogoutsSuccessful


Omissions

This section lists new and additional information that the current version of the Cisco Unified CallManager documentation may not include:

Setting the Cisco Unified Communications Manager MTU Size

Automated Alternate Routing (AAR) Limitation with Remote Gateways

Cisco 28xx Voice Gateways and H.323

Malicious Call Identification Restrictions

Call Control for Attendant Console

Destination Address for SIP Trunk Configuration

Music On Hold

Resource Reservation Protocol (RSVP)

Installing Device Packs and Phone Firmware Loads

Saving and Uploading Third-Party Security Certificates

Accessing Cisco Security Agent (CSA) Logs

Changing IP Address on a Cisco Unified CallManager Node

Obtaining a License File

BAT SCCP to SIP Phone Migration for Cisco Unified IP Phones 7940 and 7960

Upgrading CTL Client and CTL Files After Upgrading to Version 5.x

Tool for Auto-Registered Phone Support (TAPS)

Using Third-Party Certificate Authority Certificates

SDI Trace Settings

TFTP

Disaster Recovery CLI Commands

Searching for a Device in RTMT with the Any Status Option

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

Setting the Cisco Unified Communications Manager MTU Size

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

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

Automated Alternate Routing (AAR) Limitation with Remote Gateways

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

Workaround Example

Use a specific partition for the TEHO in question.

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

Configure as follows:

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

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

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

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

5. Create a route pattern in the TehoBr1forHQPt partition.

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

Results

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

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

Cisco 28xx Voice Gateways and H.323

Table 39-1, Overview of Supported Voice Gateways, Protocols, Trunk Interfaces, and Ports, of the Cisco Unified CallManager System Guide for release 5.0(4) did not include H.323 in the list of gateway control protocols for the Cisco 2801, 2811, 2821, and the 2851 voice gateways.

Malicious Call Identification Restrictions

The Malicious Call Identification chapter of the Cisco Unified CallManager Features and Services Guide does not list SIP trunk as a restriction. MCID does not support SIP trunks.

Call Control for Attendant Console

The Attendant Console chapter of the Cisco Unified CallManager Features and Services Guide does not include the following information.

Make sure that you check the Allow Control of Device from CTI check box on the Phone Configuration window for each attendant phone. The system enables this field by default. If this check box is not checked for the attendant phone, call control does not come up for the attendant console.

Destination Address for SIP Trunk Configuration

The following information should be added to the Destination Address in the SIP Trunk Configuration Settings table.

Table 9 Trunk Configuration Settings for SIP Trunks

Field
Description
SIP Information

Destination Address

The Destination Address represents the remote SIP peer with which this trunk will communicate. The allowed values for this field comprise a valid V4 dotted IP address, fully qualified domain name (FQDN), or DNS SRV record only if the Destination Address is an SRV field that is checked.

Note SIP trunks only accept incoming requests from the configured Destination Address and the specified incoming port that is in the SIP Trunk Security Profile, which is associated with this trunk.

If the remote end is a Cisco Unified CallManager cluster, DNS SRV represents the recommended choice for this field. The DNS SRV record should include all Cisco Unified CallManagers within the cluster.

Destination Address is an SRV

This field specifies that the configured Destination Address is an SRV record.

The default value specifies unchecked.


Music On Hold

The Music On Hold chapter of the Cisco Unified CallManager Features and Services Guide does not include the following information.

The Media Resources > MOH Audio File Management menu option allows the administrator to perform the following functions:

Display a list of the MOH audio source files that are stored on the system. For each file, the window displays the file name, file length, and file status.

Upload new MOH audio source files. To do so, click the Upload File button and use the Upload File popup window that displays. For configuration details, refer to the description of the Upload File button in the Music On Hold Audio Source Configuration Settings table of the Music On Hold chapter in the Cisco Unified CallManager Features and Services Guide.

Select MOH audio source files for deletion. You cannot delete MOH audio source files that specify the In Use state.

Resource Reservation Protocol (RSVP)

The Resource Reservation Protocol chapter of the Cisco Unified CallManager System Guide does not include the following information.

In an RSVP session, special configuration applies if all of the following conditions exist:

One of the endpoint devices, such as Cisco IP Interactive Voice Response (IP IVR), has been configured to support only the G.711 codec.

RSVP has been configured for the call.

The interregion codec specifies G.729 between the calling RSVP Agent and the called RSVP Agent.

When the call is made, to achieve successful allocation and reservation of RSVP Agent resources and bandwidth, the administrator must configure the Media Termination Point (MTP)/RSVP Agent with the G.729 codec in addition to the pass-through codec. This configuration allows insertion of a transcoder between the RSVP Agent of the called side and the called device at the time of media connection. When codecs match, codec pass-through takes place; if codecs do not match, a transcoder is needed to allow the call to continue.

If configuration of the G.729 codec in the agent does not take place, the call will fail because Cisco Unified CallManager will not invoke a transcoder that is needed for the RSVP call.

The situation arises if either of the following conditions apply: the interregion codec is used between calling and called agents or between two endpoints that specify G.729. Two options exist to enable successful routing of this call:

Use RSVP Agent for IVR as a transcoder. In this case, the interregion codec between the transcoder/RSVP Agent and IVR needs to specify the G.711 codec.

Use software MTP as RSVP Agents and insert a transcoder between IVR and the RSVP Agent for IVR. In this case, the software MTP must configure the G.729 codec in addition to the pass-through codec.

Keep in mind that the RSVP Agent that has transcoding capability cannot perform G.729-to-G.729 transcoding. If you use a transcoder as an RSVP Agent, you must either use the pass-through codec or configure it, so one of the codecs that is used on both sides of the transcoder specifies G.711.

Installing Device Packs and Phone Firmware Loads

The Software Upgrades chapter of the Cisco Unified Communications Operating System Administration Guide does not include the following information.

You can also use the Software Upgrade and Installation procedure to upload and install device packs, phone firmware loads, and other COP files.

Saving and Uploading Third-Party Security Certificates

When you save certificates that you obtained from a third-party Certificate Authority (CA) to your PC, Cisco recommends that you use Notepad to open and save the certificate because this method maintains the certificate format.

After you save a certificate, see the Security chapter of the Cisco Unified Communications Operating System Administration Guide for information about how to upload it to the system.

Accessing Cisco Security Agent (CSA) Logs

Administrators can use the Trace & Log Central feature in the Real-Time Monitoring Tool (RTMT) to access Cisco Security Agent (CSA) logs. To collect CSA logs, check the Cisco Security Agent check box in the Select System Logs tab. To access user logs that provide information about users that are logging in and out, check the Security Logs check box in the Select System Logs tab. For more information on using RTMT, refer to the Cisco Unified CallManager Serviceability Administration Guide.

Changing IP Address on a Cisco Unified CallManager Node

If the IP address of the first Cisco Unified CallManager node gets changed while a subsequent node is offline, you may not be able to log in to Cisco Unified CallManager Administration on the subsequent node. If this occurs, follow this procedure:


Step 1 Log in directly to platform administration on the subsequent node by using the following IP address:

http://server-name/iptplatform

where server-name specifies the host name or IP address of the subsequent node.

Step 2 Enter your Administrator user name and password and click Submit.

Step 3 Navigate to Settings>IP>Publisher.

Step 4 Enter the new IP address for the publisher server and click Save.

Step 5 Restart the subsequent node.


Obtaining a License File

Use the following steps to obtain a license file for a new installation of Cisco CallManager 5.0 phones nodes and for updating the licenses when new phones are added.


Step 1 When you place an order for Cisco devices, Cisco provides a Product Authorization Key (PAK).

Step 2 Register the PAK with Cisco CallManager by using the License Registration tool at http://www.cisco.com/go/license.

Step 3 You must enter the MAC address of the Cisco CallManager server for which you are requesting the licenses and a valid e-mail ID. You must enter the number of nodes and phone units for which you want licenses.


Note You can determine the number of phone unit licenses that you will require for each phone type by using License Calculator in Cisco CallManager Administration. See the "Calculating License Units" section.


Step 4 CCO generates a license file with the number of unit licenses that you requested and sends it to you via e-mail by using the e-mail ID that you provided in Step 2.

Step 5 You must upload the license file to the server with the matching MAC address that you provided in Step 3. See the "Uploading a License file" section. This server then takes on the functionality of the license manager.



Note When you buy new phones and you want to update your licenses, go to the License Registration web tool at http://www.cisco.com/go/license and follow Step 3 through Step 5.


BAT SCCP to SIP Phone Migration for Cisco Unified IP Phones 7940 and 7960

After the request to migrate an SCCP phone to SIP through the Migrate Phones - SCCP TO SIP window is submitted, Cisco Unified IP Phones 7940 and 7960 continue to show up as SCCP phones. To solve this problem, power cycle (power off and on) individual phones after migration.


Note For Cisco Unified IP Phones 7905, 7911, 7912, 7941, 7961, 7970, and 7971, the migration activity works correctly, and the phones register as SIP after migration.


Upgrading CTL Client and CTL Files After Upgrading to Version 5.x

When you upgrade from a 4.1x release to a 5.x release and security is enabled on the cluster, you must perform the following tasks to enable security on the upgraded cluster. For information about performing these tasks and about Cisco Unified CallManager security, refer to the Cisco Unified CallManager Security Guide.

1. Uninstall the existing CTL client.

2. Install the new CTL client.

3. Run the CTL client by using at least one of the previously used USB keys.

4. Install the new CTL file on all nodes.

5. Restart all nodes.

Tool for Auto-Registered Phone Support (TAPS)

TAPS works with all phones that auto-register and have SEP, BAT, or ATA device name prefixes.

Using Third-Party Certificate Authority Certificates

In Cisco Unified Communications Operating System 5.0(4), the system supports certificates that a third party Certificate Authority (CA) issued with PKCS # 10 Certificate Signing Request (CSR). The following table provides an overview of this process, with references to additional documentation:

 
Task
For More Information

Step 1 

Generate a CSR on the server.

See the "Generating a Certificate Signing Request" section.

Step 2 

Download the CSR to your PC.

See the section "Download a Certificate Signing Request" in the Security chapter of the Cisco Unified Communications Operating System Administration Guide.

Step 3 

Use the CSR to obtain an application certificate from a CA.

Get information about obtaining application certificates from your CA. See "Obtaining Third-Party Certificate Authority (CA) Certificates" section for additional notes.

Step 4 

Obtain the CA root certificate.

Get information about obtaining a root certificate from your CA. See "Obtaining Third-Party Certificate Authority (CA) Certificates" section for additional notes.

Step 5 

Upload the Certificate Authority root certificate to the server.

See the "Uploading a Certificate or Certificate Trust List File" section.

Step 6 

Upload the application certificate to the server.

See the "Uploading a Certificate or Certificate Trust List File" section.

Step 7 

If you updated the certificate for CAPF or Cisco Unified CallManager, generate a new CTL file.

See the Cisco Unified CallManager Security Guide.

Step 8 

Restart the services that the new certificate affects.

For all certificate types, restart the corresponding service (for example, restart the Tomcat service if you updated the Tomcat certificate). In addition, if you updated the certificate for CAPF or Cisco Unified CallManager, restart the TFTP service.

See the Cisco Unified CallManager Serviceability Administration Guide for information about restarting services.

See the Cisco Unified CallManager Serviceability Administration Guide for information about restarting services.

Generating a Certificate Signing Request

To generate a Certificate Signing Request (CSR), follow these steps:

Procedure


Step 1 Navigate to Security>Certificate Management>Download/Generate CSR.

The Select Certificate type for CSR window displays.

Step 2 Choose the type of certificate to generate in the Existing Certificate Types area.

Step 3 Choose the Generate a new CSR radio button.

Step 4 Click Next.

The Cert/IPSEC Operation (CSR/Config/Assoc Create) Done window displays and states that the CSR successfully generated.


Obtaining Third-Party Certificate Authority (CA) Certificates

To use an application certificate that a third-party CA issued, you must obtain from the CA both the signed application certificate and the CA root certificate. Get information about obtaining these certificates from your CA. The process varies among CAs.

CAPF and Cisco Unified CallManager CSRs include extensions that you must include in your request for an application certificate from the CA. If your CA does not support the ExtensionRequest mechanism, you must enable the X.509 extensions that are listed on the final window of the CSR generation process.

Cisco Unified Communications Operating System generates certificates in DER and PEM encoding format and generates CSRs in PEM encoding format. It accepts certificates in DER and DER encoding formats.

Cisco verified third-party certificates that were obtained from Microsoft, Keon, and Verisign CAs. Certificates from other CAs might work but have not been verified.

Uploading a Certificate or Certificate Trust List File

This section replaces the "Upload a Certificate or Certificate Trust List" section in the Security chapter of the Cisco Unified Communications Operating System Administration Guide.


Caution Uploading a new certificate or certificate trust list (CTL) file can affect your system operations.


Note The system does not distribute trust certificates to other cluster nodes automatically. If you need to have the same certificate on more than one node, you must upload the certificate to each node individually.


To upload a CA root certificate, application certificate, or CTL file to the server, follow these steps:

Procedure


Step 1 Navigate to Security>Certificate Management>Upload Certificate/CTL.

The Select Certificate/CTL Upload window displays.

Step 2 Choose one of the radio buttons; then, click Next:

Upload Own Cert—To upload an application certificate that a third-party CA issued.

Upload Trust Cert—To upload a CA root certificate or a trusted application certificate.

Upload CTL File—To upload a CTL file.

The Certificate type for the upload including CTL window displays.

Step 3 Do the following in the Certificate type for the upload including CTL window:

a. Select the type of certificate or CTL from the Existing certificate types list.

b. If you are uploading an application certificate that a third-party CA issued, enter the name of the CA root certificate in the Root Cert Name (without any extensions) text box. If you are uploading a CA root certificate or CTL, leave this text box empty.

c. Click Next.

The Upload Certificate/CTL window displays.

Step 4 Do the following steps in the Upload Certificate/CTL window:

a. Select the file to upload by doing one of the following steps:

Enter the path to the file in the File Name for Upload text box.

Click the Browse button and navigate to the file; then, click Open.

b. To upload the file to the server, click the Upload button.

SDI Trace Settings

When setting the SDI trace level for the Cisco CallManager service to Detailed, you should uncheck the Enable SIP Stack Trace check box unless Cisco support representatives tell you to check the check box. If this check box is checked and a substantial amount of SIP traffic (either from SIP endpoints or SIP trunks) exists, the resulting logs could degrade performance of the Cisco Unified CallManager service.

TFTP

The Cisco TFTP chapter of the Cisco Unified CallManager System Guide does not include the following information about configuring the security CTL file when you are using the Centralized TFTP with Secure Clusters.

Centralized TFTP with Secure Clusters

All off-cluster servers that are operating in secure mode must add the Centralized TFTP server or servers IP address to the clusters CTL file. (Without this updated CTL file, phones that register to a cluster where security is enabled and that attempt to download their config files will fail.) After the CTL file is updated, reboot the servers, so they can participate in the secure multicluster centralized TFTP network.

To update the CTL file for the TFTP servers, download the CTL Client plug-in by using Application > Install Plugins from Cisco Unified CallManager Administration. For more information about the CTL client and how to configure TFTP for security, refer to the Cisco Unified CallManager Security Guide.

Disaster Recovery CLI Commands

The Cisco Unified Communications Operating System Administration Guide does not document the following CLI command:

Table 0-10 Utility Commands

Command
Parameters
Description

utils disaster_
recovery

configure_features features

Where features specifies one or more features to include in the disaster recovery backup. Separate feature names with commas (,).

Options

None

This command allows you to configure the features that the disaster recovery system backs up.

Use the command utils disaster_recovery show_registration to see a list of the features that are registered on the server.


Searching for a Device in RTMT with the Any Status Option

The Real-time Monitoring Tool chapter of the Cisco Unified CallManager Serviceability System Guide does not include the following information.

When you search for a device by choosing the any status option, RTMT does not display a snapshot of the matched device type, but rather it displays data for that device type from the RIS database for all specified Cisco Unified CallManager nodes for a period of time. As a result, you may see multiple entries of a device with multiple statuses (Registered, Unregistered, and so on) in RTMT. When you see multiple entries of a device, the current status of the device is the entry that has the latest timestamp. You can configure the time that information on unregistered or rejected device is kept in the RIS database by configuring the RIS Unused Cisco CallManager Device Store Period service parameter in Cisco RIS Data Collector service in Cisco Unified CallManager Administration. For more information on configuring service parameter, refer to the Cisco Unified CallManager Administration Guide.

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

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

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

Example:

Consider the following example:

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

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

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

License Capabilities Assignment Configuration

Capabilities Assignment allows system administrators to enable the Cisco Unified Presence Server (CUPS) and Cisco Unified Personal Communicator (CUPC) capabilities for users. Ensure licenses for CUPS and CUPC are available.

Before you begin configuring the capabilities assignments for users, determine how many CUPS (servers and clients) and CUPC licenses are required for your system by choosing Licensing > License UnitCalculator. Acquire the required licenses by using Licensing > License File Upload. Verify the total licenses by using Licensing > License Unit Report.

The following topics explain locations in more detail:

Finding a License Capabilities Assignment

Configuring the Capabilities Assignments For One User

Configuring the Capabilities Assignments For Multiple Users

License Capabilities Assignment Configuration Settings

Related Topics

Finding a License Capabilities Assignment

Because you might have several license capabilities assignments for users in your network, Cisco Unified CallManager Administration lets you locate specific capabilities assignments on the basis of specific criteria. Use the following procedure to find locations.


Note During your work in a browser session, Cisco Unified CallManager Administration retains your location search preferences. If you navigate to other menu items and return to this menu item, Cisco Unified CallManager Administration retains your location search preferences until you modify your search or close the browser.


Procedure


Step 1 Choose System > Licensing > Capabilities Assignment.

The Find and List Capabilities Assignment window displays. Use the two drop-down list boxes to search for a capabilities assignment.

Step 2 From the first Find capabilities assignment where drop-down list box, choose one of the following criteria:

User ID

Last Name

Manager

Department

From the second Find capabilities assignment where drop-down list box, choose one of the following criteria:

begins with

contains

ends with

is exactly

is empty

is not empty

Step 3 Specify the appropriate search text, if applicable, and click Find. You can also specify how many items per window to display.


Tip To find all entries that are available for capabilities assignment, click Find without entering any search text.


A list of discovered capabilities assignments displays by

User ID

Last Name

Manager

Department

UPS Enabled

UPC Enabled

Step 4 From the list of records, click the user name for whom you want to make capabilities assignments.

The Capabilities Assignments Configuration window displays


Additional Information

See the "Related Topics" section.

Configuring the Capabilities Assignments For One User

This section describes how to add or update a capabilities assignment for a user to the Cisco Unified CallManager database.

Before You Begin

Before configuring a capabilities assignment, you must obtain licenses from Cisco by using the License File Upload under the System menu.

Procedure


Step 1 Choose System > Licensing > Capabilities Assignment.

The Find and List Capabilities Assignment window displays

Step 2 To add a new capabilities assignment or update an existing capabilities assignment, locate the appropriate capabilities assignment as described in the "Finding a License Capabilities Assignment" section and continue with Step 3.

The Capabilities Assignments Configuration window displays.

Step 3 Check the appropriate check box as described in Table 1.

Step 4 To save the capabilities assignment information in the database, click Save.


Additional Information

See the "Related Topics" section.

Configuring the Capabilities Assignments For Multiple Users

This section describes how to add or update capabilities assignments for multiple users to the Cisco Unified CallManager database.

Before You Begin

Before configuring a capabilities assignment, you must obtain licenses from Cisco by using the License File Upload under the System menu.

Procedure


Step 1 Choose System > Licensing > Capabilities Assignment.

The Find and List Capabilities Assignment window displays.

Step 2 To add a new capabilities assignment or update an existing capabilities assignment, locate the appropriate capabilities assignment as described in the "Finding a License Capabilities Assignment" section and continue with Step 3.

Step 3 To enable a new capabilities assignment or to update an existing capabilities assignment for multiple users, check the check boxes next to the users or click the Select All button.

Step 4 Click the Bulk Assignment button.

The Capabilities Assignments Configuration window displays.

Step 5 Check the appropriate check box as described in Table 1.

Step 6 To save the capabilities assignment information in the database, click Save.

Additional Information

See the "Related Topics" section.

License Capabilities Assignment Configuration Settings

Table 11 describes the license capabilities assignment configuration settings. For related procedures, see the"Related Topics" section.

.

Table 11 License Capabilities Assignment Configuration Settings

Field

Description

User Information

User ID

Displays the name of the user to which you are enabling capabilities assignment.

Capabilities Assignment Information

Enable UPS (UnifiedPresence Server)

To enable CUPS for this user, check the Enable UPS (Unified PresenceServer) check box.

Enable UPC (UnifiedPersonal Communicator)

To enable CUPC for this user, check the Enable UPC (Unified PersonalCommunicator) check box. You can enable both CUPS and CUPC; however, if you want CUPC, you must also enable CUPS.


Related Topics

License Capabilities Assignment Configuration

Finding a License Capabilities Assignment

Configuring the Capabilities Assignments For One User

Configuring the Capabilities Assignments For Multiple Users

License Capabilities Assignment Configuration Settings

Corrections

This section lists corrected information that the current version of the Cisco Unified CallManager documentation may not include:

Servers That Support Cisco Unified CallManager 5.0(3)

Cisco Emergency Responder 1.3(1a)

Servers That Support Cisco Unified CallManager 5.0(3)

The document, Installing Cisco Unified CallManager 5.0(3) does not provide a complete list of servers that support Cisco Unified CallManager 5.0(3). For a list of servers that support Cisco Unified CallManager 5.0 releases, go to:

http://www.cisco.com/en/US/products/hw/voiceapp/ps378/prod_brochure09186a008174928.html

Cisco Emergency Responder 1.3(1a)

Cisco Emergency Responder (Cisco ER) 1.3(1a) supports Cisco Unified CallManager 5.0(2) and 5.0(3) in addition to Cisco Unified CallManager 3.3 and Cisco Unified CallManager 4.0, 4.1, and 4.2.


Note Cisco Unified CallManager 5.0(1) does not get supported with Cisco Emergency Responder 1.3(1a)


Ensure all Cisco ER servers are version 1.3(1a). This allows Cisco ER to support multiple Cisco Unified CallManager 5.0(2) or 5.0(3) clusters. Cisco ER 1.3(1a) will not work with previous versions of Cisco ER.

Cisco ER 1.3(1a) supports upgrades from Cisco ER 1.2(1), Cisco ER 1.2(2), and Cisco ER 1.2(3).

Cisco ER 1.3(1a) provides Windows-based support.

Obtaining Documentation, Obtaining Support, and Security Guidelines

For information on obtaining documentation, obtaining support, providing documentation feedback, security guidelines, and also recommended aliases and general Cisco documents, 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

Cisco Product Security Overview

Cisco provides a free online Security Vulnerability Policy portal at this URL:

http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html

From this site, you will find information about how to:

Report security vulnerabilities in Cisco products.

Obtain assistance with security incidents that involve Cisco products.

Register to receive security information from Cisco.

A current list of security advisories, security notices, and security responses for Cisco products is available at this URL:

http://www.cisco.com/go/psirt

To see security advisories, security notices, and security responses as they are updated in real time, you can subscribe to the Product Security Incident Response Team Really Simple Syndication (PSIRT RSS) feed. Information about how to subscribe to the PSIRT RSS feed is found at this URL:

http://www.cisco.com/en/US/products/products_psirt_rss_feed.html

Reporting Security Problems in Cisco Products

Cisco is committed to delivering secure products. We test our products internally before we release them, and we strive to correct all vulnerabilities quickly. If you think that you have identified a vulnerability in a Cisco product, contact PSIRT:

For Emergencies only — security-alert@cisco.com

An emergency is either a condition in which a system is under active attack or a condition for which a severe and urgent security vulnerability should be reported. All other conditions are considered nonemergencies.

For Nonemergencies — psirt@cisco.com

In an emergency, you can also reach PSIRT by telephone:

1 877 228-7302

1 408 525-6532


Tip We encourage you to use Pretty Good Privacy (PGP) or a compatible product (for example, GnuPG) to encrypt any sensitive information that you send to Cisco. PSIRT can work with information that has been encrypted with PGP versions 2.x through 9.x.

Never use a revoked or an expired encryption key. The correct public key to use in your correspondence with PSIRT is the one linked in the Contact Summary section of the Security Vulnerability Policy page at this URL:

http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html

The link on this page has the current PGP key ID in use.

If you do not have or use PGP, contact PSIRT at the aforementioned e-mail addresses or phone numbers before sending any sensitive material to find other means of encrypting the data.