Table Of Contents
Release Notes for Cisco Unified CallManager Release 5.0(4c)
Determining the Software Version
Installation on Cisco MCS Servers MCS-7825-H1, MCS-7825-H2
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
Failover Time Using UDP on SIP Phones
Premature Certificate Generation Prevents Immediate Service Activation After a Fresh Installation
Configuring Regions (Region Relationship) for SIP Devices with the MTP Required Option Enabled
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
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
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
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
Online Help for Cisco Unified CallManager Attendant Console
Where to Find More Information
Cisco Unified CallManager Administration
Cisco Unified CallManager Features
Cisco Unified CallManager Serviceability
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
Data Migration Assistant (DMA)
Disaster Recovery Enhancements
Where to Find More Information
Cisco Unified Communications Operating System Administration
Platform Status and Configuration
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
Publisher and Subscriber Name Changes
General Changes Made to Multiple Windows
Line and Phone Configuration Improvements
Call Routing Menu Changes (formerly Route Plan Menu)
Where to Find More Information
Cisco Unified CallManager Features
Dynamic Host Control Protocol (DHCP)
Personal Directory Enhancements
Phone NTP References for SIP Phones
SIP Line Side (Endpoints) Support
Cisco Unified CallManager User Options Web Pages
Addition of the Cisco Personal Communications Assistant Layer
Where to Find More Information
Cisco Unified CallManager Applications
Cisco Unified CallManager Attendant Console
Cisco Unified CallManager AutoAttendant
Cisco Unified CallManager Extension Mobility
Cisco Emergency Responder 1.3(1)
Cisco Unified CallManager Assistant
Client Matter Codes and Forced Application Codes
Multilevel Precedence and Preemption (MLPP)
Cisco Unified CallManager Bulk Administration Features
New and Changed Information for BAT
Cisco Unified CallManager Auto-Register Phone Tool Features
Cisco Unified CallManager Administration Configuration Tips
Where to Find More Information
New and Changed Information for Cisco Unified CallManager Serviceability
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
Cisco Unified IP Phone Service Application Development Notes for Cisco Unified CallManager 5.0(2)
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
Viewing Field Descriptions and Help for Product-Specific Configuration
Cisco CAR Web Service/Cisco CAR Scheduler Service
Device Authentication Application User
Launching Cisco Unified CallManager Attendant Console
Phone Security Profile Configuration Window
Deleting Files on the Inactive Partition
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
H323 Redirecting Number IE is sent in UUIE by Cisco Unified CallManager
Extension Mobility Configuration Step is Missing
TS-6671 - Enabling Autoregistration
BU-6666 - Cisco Web Dialer Servlet Service Parameter
Support of Third-Party CSRs for External CAs
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
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
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
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
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 July 16, 2009
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
Caution
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
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.
•
•
•
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 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.
Table 1 Download URLs for Software Upgrades
Cisco Unified CallManager 5.0
Locale installers
http://www.cisco.com/kobayashi/sw-center/telephony/callmgr/ locale-installer.shtm
Phone firmware
http://www.cisco.com/cgi-bin/tablebuild.pl/ip-7900ser
http://www.cisco.com/cgi-bin/tablebuild.pl/ip-7900ser-crypto
Cisco Security Agent (CSA)
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
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:
•
•
•
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
Important Notes
Caution
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)
•
•
Important Notes for Cisco Unified CallManager Releases 5.0(4x)
•
•
•
•
•
•
•
•
•
•
•
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
LDAP Port For When the LDAP Server Is Not a Global Catalog Server
•
•
LDAP Port For When the LDAP Server Is a Global Catalog Server
•
•
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:
•
For more information, refer to CSCsc77968, CSCsc78450, and CSCsc78720.
•
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:
•
•
•
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:
•
•
–
–
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.1Trunk#2: Incoming Transport Protocol=TCP/UDP, Incoming Port=5060, Destination Address=10.10.10.2Trunk#3: Incoming Transport Protocol=TCP/UDP, Incoming Port=5080, Destination Address=10.10.10.1Trunk#4: Incoming Transport Protocol=TLS, Incoming Port=5061, X.509 Subject Name=my_ccm1, my_ccm2Trunk#5: Incoming Transport Protocol=TLS, Incoming Port=5061, X.509 Subject Name=my_ccm3Trunk#6: Incoming Transport Protocol=TLS, Incoming Port=5081, X.509 Subject Name=my_ccm_1The following example shows an invalid configuration:
Trunk#1: Incoming Transport Protocol=TCP/UDP, Incoming Port=5060, Destination Address=10.10.10.1Trunk#2: Incoming Transport Protocol=TCP/UDP, Incoming Port=5060, Destination Address=10.10.10.1Trunk#3: Incoming Transport Protocol=TLS, Incoming Port=5061, X.509 Subject Name=my_ccm1, my_ccm2Trunk#4: Incoming Transport Protocol=TLS, Incoming Port=5081, X.509 Subject Name=my_ccm2Trunk#5: Incoming Transport Protocol=TLS, Incoming Port=5061, X.509 Subject Name=my_ccm2Trunk#6: Incoming Transport Protocol=TLS, Incoming Port=5081, X.509 Subject Name=my_ccm2Trunk #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
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
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 5Mod Port Model Serial # Versions--- ---- ------------------- ----------- --------------------------------------5 8 WS-X6608-T1 SAD04320KZ7 Hw : 1.1Fw : 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 InfoExecuting 860 image -----> D00404000022 Built Dec 22 2005 11:47:13TFTP 860 image file -----> D00404000022.binTFTP DSP image file -----> D0054322.binTFTP POST image file ----> D007C030.binFlash ROM 860 image #1 --> D0040022Flash ROM 860 image #2 --> D0040022Flash ROM DSP image -----> D0054322Flash ROM POST image ----> D007C030TCP/IP Library ----------> TCPT030To 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.
•
•
•
•
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:
•
•
•
Note
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
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.
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
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:
•
•
•
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 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 Administration
System Menu Changes
The following change occurred in the System menu:
•
–
LDAP Menu Changes
The following change occurred in the LDAP menu:
•
Note
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
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
•
•
•
•
•
•
•
–
–
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 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:
•
BAT Considerations
The Bulk Administration menu under CUPS now includes the following two items:
•
•
Update CUPS/CUPC Users
Use the following steps to add/change the license:
1.
Note
2.
Note
3.
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
Use the following steps to Export licenses:
1.
2.
3.
4.
5.
Note
Where to Find More Information
•
•
•
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):
•
•
•
–
This replaces the % Wait In Read counter.
–
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:
•
Note
•
•
•
•
•
•
•
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:
•
•
•
•
•
•
–
–
–
•
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:
•
•
•
•
•
•
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.•
Note
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:
•
•
•
After you copy the certificate, you must restart the Cisco CallManager service on each server in cluster.
•
•
•
Tip
•
•
GUI Changes
The following GUI changes apply to security features in this release.
•
•
•
•
•
•
•
•
•
•
BAT Considerations
You can apply a security profile to phones in the BAT phone template.
Where to Find More Information
•
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
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
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
•
•
•
•
Network Services
•
•
•
Perfmon
•
•
•
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
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
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
For a more detailed description of the different installation types, see Table 2.
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:
•
•
•
•
•
Note
The Cisco DMA does not export this information:
•
•
•
•
•
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
•
•
•
•
Where to Find More Information
•
•
•
•
•
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
Cisco Unified Communications Operating System Administration allows you to configure and manage the Cisco Unified Communications Operating System by doing these tasks:
•
•
•
•
•
•
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:
•
•
Note
Platform Status and Configuration
From the Show menu, you can check the status of various platform components, including
•
•
•
•
•
Settings
From the Settings menu, you can view and update the following platform settings
•
•
•
Restart Options
From the Restart menu, you can choose from the following options for restarting or shutting down the system:
•
•
•
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:
•
•
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
Services
The application provides the following platform utilities:
•
•
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 CallManager Administration
The following sections describe Cisco Unified CallManager 5.0 administration enhancements:
•
•
•
•
•
•
•
•
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:
•
•
•
Note
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:
•
•
•
•
Note
Localizing Cisco Unified CallManager Administration
Cisco Unified CallManager Release 5.0 incorporates the following localization capabilities:
•
•
Configuring Servers
Because of security requirements, you cannot add, copy, or delete the following types of server configurations:
•
•
•
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:
•
•
Media Resources
You cannot add, copy, reset, or delete the following types of devices to media resources:
•
•
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:
•
•
•
•
•
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.
General Changes Made to Multiple Windows
You can find the following changes on multiple Cisco Unified CallManager Administration windows:
•
•
Line and Phone Configuration Improvements
Cisco Unified CallManager Administration includes the following usability enhancements to the Phone and Directory Number Configuration windows:
•
•
•
•
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:
•
•
–
–
–
–
–
DHCP Server
DHCP Subnet
–
LDAP System
LDAP Directory
LDAP Authentication
–
–
–
–
–
SIP Phone Security Profile
SIP Trunk Security Profile
SCCP Phone Security Profile
–
Application Server Type—Cisco Unity Voice Mail 4.x and Cisco Unity Connection 2.x
–
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:
•
–
–
–
•
•
•
•
•
•
–
–
–
–
–
–
–
–
Note
•
•
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:
•
•
–
–
•
–
–
–
•
–
–
–
–
–
–
–
–
–
–
For more information about the changes that are on the Phone and Directory Number Configuration windows, see the "Line and Phone Configuration Improvements" section.
•
–
–
–
–
–
Application Menu Changes
The following changes apply in the Application 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.
•
•
–
–
–
–
–
–
•
•
–
•
•
•
•
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:
•
•
•
•
•
•
•
•
•
•
•
•
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:
•
•
•
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:
•
•
•
•
•
•
Where to Find More Information
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Cisco Unified CallManager Features
The following sections describe the Cisco Unified CallManager 5.0 feature enhancements:
•
•
•
•
•
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
•
Note
•
•
•
•
•
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
•
•
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
•
•
Where to Find More Information
•
•
•
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
•
•
–
–
•
–
•
–
BAT Considerations
Bulk Administration provides Insert Call Pickup Groups and Delete Call Pickup Groups.
Where to Find More Information
•
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.
2.
3.
4.
Note
5.
GUI Changes
•
•
•
•
–
–
–
–
–
–
Note
•
CTI Considerations
See the "Migration Tips" section for information about CTI check boxes and user groups.
Where to Find More Information
•
•
•
•
•
•
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.
•
•
Serviceability Considerations
The following enhancements exist in Cisco Unified CallManager Serviceability for DHCP:
•
•
•
•
•
–
–
Where to Find More Information
•
•
•
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
•
•
Where to Find More Information
•
•
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:
•
•
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:
•
•
The following new menu options in this release of Cisco Unified CallManager Administration relate to configuration of directory information:
•
•
•
•
•
The menu options allow the following basic functionality:
•
•
•
•
•
Service Parameter Changes
Changes to directory functionality affect the service parameters that are associated with the DirSync service.
Where to Find More Information
•
•
•
•
•
•
•
•
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:
•
•
•
Serviceability Considerations
The following enhancements exist in Cisco Unified CallManager Serviceability for Licensing:
•
•
•
•
–
–
–
–
–
–
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
•
•
•
•
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 Phones (SIP) that support Personal Directory:
•
•
•
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
•
•
•
Using Personal Directory—Personal Address Book and Fast Dials
Users can access Personal Directory:
•
•
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.
•
•
•
•
Where to Find More Information
•
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:
•
•
Where to Find More Information
•
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:
•
•
•
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
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
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.
•
•
•
•
•
•
•
•
•
Cisco Unified IP Phones (SCCP) that Support Busy Lamp Field (BLF) -Speed Dial
•
•
•
•
Cisco Unified IP Phones (SCCP) that Support Busy Lamp Field (BLF) -Call List
•
•
Cisco Unified IP Phones (SIP) that Support Busy Lamp Field (BLF) -Speed Dial
•
•
Cisco Unified IP Phones (SIP) that Support Busy Lamp Field (BLF) -Call List
•
•
GUI Changes
The following new and changed windows in Cisco Unified CallManager Administration contain presence-related configuration settings:
•
•
•
•
•
•
•
•
•
Service and Enterprise Parameter Changes
The following new service and enterprise parameters support presence:
•
•
•
•
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:
Note
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:
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
•
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:
•
•
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:
•
•
•
•
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:
•
•
•
•
•
•
•
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
•
•
•
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:
•
•
•
•
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:
•
•
•
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:
•
–
•
The following service parameters in the Clusterwide Parameters (System — RSVP) pane affect RSVP configuration:–
–
–
–
–
–
–
Administrators do not normally need to change the values of these service parameters.
•
–
Service Parameter Changes
The following new service parameters support RSVP:
•
–
–
•
–
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:
•
•
•
•
These CDR fields reflect the status of RSVP bandwidth reservation per audio or video stream.
Where to Find More Information
•
•
•
•
•
•
Service Enhancements
Cisco Unified CallManager Release 5.0 includes the following enhancements to Services:
•
•
Feature Services—Unified CM Services
The following Services belong to the Unified CM Services group when Cisco Unified CallManager Serviceability is used:
•
•
•
•
•
•
•
•
•
•
•
Feature Services—CTI Services
The following Services belong to the CTI Services group when Cisco Unified CallManager Serviceability is used:
•
•
Feature Services—CDR Services
The following Services belong to the CDR Services group when Cisco Unified CallManager Serviceability is used:
•
•
•
Feature Services—Database and Admin Services
The following Services belong to the Database and Admin Services group when Cisco Unified CallManager Serviceability is used:
•
•
•
Feature Services—Performance and Monitoring Services
The following Services belong to the Performance and Monitoring Services group when Cisco Unified CallManager Serviceability is used:
•
•
Feature Services—Security Services
The following Services belong to the Security Services group when Cisco Unified CallManager Serviceability is used:
•
•
•
Feature Services—Directory Services
The following Service belongs to the Directory Services group when Cisco Unified CallManager Serviceability is used:
•
Network Services—Platform Services
The following Services belong to the Platform Services group when Cisco Unified CallManager Serviceability is used:
•
•
•
•
•
•
•
•
•
•
•
•
Network Services—DB Services
The following Service belongs to the DB Services group when Cisco Unified CallManager Serviceability is used:
•
Network Services—Unified CM Services
The following Services belong to the Unified CM Services group when Cisco Unified CallManager Serviceability is used:
•
•
•
•
•
•
•
•
•
•
Network Services—Performance and Monitoring Services
The following Services belong to the Performance and Monitoring Services group when Cisco Unified CallManager Serviceability is used:
•
•
•
Network Services—SOAP Services
The following Services belong to the SOAP Services group when Cisco Unified CallManager Serviceability is used:
•
•
•
Network Services—Backup and Restore Services
The following Services belong to the Backup and Restore Services group when Cisco Unified CallManager Serviceability is used:
•
•
Network Services—CDR Services
The following Services belong to the CDR Services group when Cisco Unified CallManager Serviceability is used:
•
•
Where to Find More Information
•
•
•
•
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
•
•
•
•
Note
•
•
•
•
•
Note
Configuration Similarities Between SCCP Phones and SIP Phones
•
–
–
•
•
Configuration Differences Between SCCP Phones and SIP Phones
•
–
•
–
•
•
–
•
•
GUI Changes
Use the following Cisco Unified CallManager Configuration windows to configure SIP phones.
•
–
–
–
Ensure the SIP auto registration enterprise parameter is set (System > Enterprise Parameters)
•
–
–
•
–
•
•
–
•
–
•
–
•
–
–
–
–
–
–
•
–
•
Cisco Unified CallManager Configuration
•
•
•
•
SIP Phone Security Profile Configuration
•
•
•
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
•
•
Phone Configuration (SIP 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
•
•
•
•
New Enterprise Parameter
•
Removed or Changed Service Parameters
The SIP Profile includes the following service parameter:
•
SCCP and SIP Phone Service Parameters Differences in Behavior
•
•
•
•
Serviceability Considerations
Cisco Unified CallManager Serviceability provides the following Trace Configuration parameters for SIP line support:
•
•
BAT Considerations
The Bulk Administration Tool provides the following support for SIP endpoints:
•
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.
•
•
•
Note
CTI Considerations
Note
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:
•
•
•
•
•
•
Features that CTI does not support on SIP phones
The features that are not supported by CTI on SIP phones include
•
•
•
•
•
•
–
–
–
–
–
–
•
•
•
•
Note
Where to Find More Information
•
•
•
•
•
•
•
•
•
•
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:
•
•
Differences between (Numeric) Route Patterns and SIP Route Patterns
The following differences between (Numeric) Route Patterns and SIP Route Patterns exist:
•
•
•
•
•
•
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.
•
•
•
–
–
•
–
–
•
Enterprise Parameters
SIP route patterns support the following enterprise parameters, which are used to decide whether host address is local or foreign:
•
•
Serviceability Considerations
SIP route pattern supports new Trace messages:
•
•
Where to Find More Information
•
•
•
•
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:
•
•
•
•
–
•
–
–
–
–
Note
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
•
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
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:
•
•
•
•
•
•
•
•
•
•
•
•
•
Cisco Unified CallManager Administration Configuration Tips
The following configuration tips apply to Cisco Unified CallManager Administration:
•
GUI Changes
The following GUI changes occurred:
•
•
•
•
–
–
–
–
–
–
–
–
–
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:
•
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:
•
•
•
•
•
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
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:
•
•
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
•
•
•
•
URL Dialing
The following Cisco Unified IP Phones (SIP) support URL dialing:
•
•
•
•
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.
> Missed Calls, Placed Calls, or Received Calls.
2.
3.
The
icon appears and indicates that you can edit characters in the URL entry.
4.
For More Information
•
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.
2.
3.
The
4.
5.
For More Information
•
Video Telephony Enhancements
SIP video supports the following video calls by using the SIP Signaling Interface (SSI):
•
•
•
•
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.
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:
•
•
Service Parameter Changes
•
•
•
•
•
Serviceability Considerations
This release makes the following serviceability performance monitoring counters available for the video enhancements:
•
–
–
Where to Find More Information
•
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:
•
•
Note
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.
2.
3.
•
•
4.
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
•
•
•
•
Where to Find More Information
•
•
•
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:
•
•
•
Where to Find More Information
•
•
Cisco Unified CallManager Applications
The following sections describe the Cisco Unified CallManager 5.0 applications enhancements:
•
•
•
•
•
•
•
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 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:
•
•
•
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:
•
•
•
•
•
•
Service Parameter Changes
The following new service parameter supports Cisco Unified CallManager Attendant Console:
•
User Tips
Consider the following information when setting up the Cisco Unified CallManager Attendant Console client application:
•
•
•
•
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
•
•
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 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:
•
•
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
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:
•
•
•
•
You must activate the following feature services from Cisco Unified CallManager Serviceability for EM to be enabled:
•
•
•
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 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.
•
•
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:
•
•
•
•
Where to Find More Information
•
•
•
•
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.
•
•
•
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:
•
•
•
•
•
•
–
–
–
•
•
•
•
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:
•
Cisco Unified CM Assistant Configuration Wizard
•
Cisco Unified CallManager Assistant Configuration
•
•
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
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
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
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:
•
•
•
•
•
•
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
•
•
•
Secure Connection to CTI
•
•
Where to Find More Information
•
•
•
•
•
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
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
Guest
