Release Notes for Cisco Unified Communications Manager Release 7.1(2a)
Available Languages
Table Of Contents
Release Notes for Cisco Unified Communications Manager Release 7.1(2a)
Upgrading to Cisco Unified Communications Manager 7.1(2a)
Making Configuration Changes After an Upgrade
Upgrade Paths to Cisco Unified Communications Manager 7.1(2a)
Upgrading from Cisco Unified Communications Manager Release 5.1(3e) to 7.1(x) Releases
Upgrading to Unified CM 7.1(2a) by Using the UCSInstall File
Upgrading From an Engineering Special
The Latest Software Upgrades for Unified CM 7.1 on Cisco.com
Context-Sensitive Help Does Not Display for Some Windows
Deleting Unassigned Directory Numbers
CSCta09513 Switch Version Does Not Complete
CSCta12062 Null Value in NetworkLocale Caused Database Exception
CSCsy92863 Intercom Route Partition Online Help Is Incorrect
Admin Password Gets Corrupted If Correction is Made During Password Reset
Password Too Short or Password in Dictionary
CSCsz33878 IPMA Wizard Constraint
CSCsz21235 Core Dump File Gets Generated During the Cisco Security Agent Shutdown Process
Creating a Custom Help Desk Role and Custom Help Desk User Group
Use Microsoft Outlook to Receive Cisco Unified Communications Manager Licenses
Multiple Tenant MWI Modes Service Parameter
Considerations for LDAP Port Configuration
Installation, Upgrade, and Migration
System History Log for Cisco Unified Communications Manager
Device Name of Cisco Unified Mobile Communicator Must Not Exceed 15 Characters Before 7.1(2) Upgrade
Cisco Unified Communications Operating System Administration
Ethernet IPv6 Configuration Settings
Cisco Unified Communications Manager Administration
New and Updated Enterprise and System Parameters
Cisco Unified Communications Manager Features and Applications
Always Use Prime Line for Voice Message
Barge, cBarge, and Single Button Barge Support for PLAR
Calling Party Normalization Enhancements
Cisco Unified Communications Manager Assistant Enhancements for Numeric User ID Login
Cisco Unified Communications Manager Attendant Console Support in 7.1(2)
Cisco Web Dialer Configured in Application Server Window
G.Clear Codec Support on SIP Trunks
Geolocations and Geolocation Filters
H.329—Extended Video Channel Support
Internet Protocol Version 6 (IPv6)
Location-Based Call Admission Control Over Intercluster Trunk
Logging Missed Calls for Shared Lines
Multicast Music On Hold Over H.323 Intercluster Trunks
OpenLDAP 2.3.41 Can Synchronize with Cisco Unified Communications Manager Database
Phone Migration in Cisco Unified Communications Manager Administration
QSIG Variant Configuration for a Gateway or Trunk
Standard Audit Log Administration Role
Standard Audit Users User Group
Synchronization of Configuration Settings
Unconfigured Device Registration Attempts Restricted
Viewing Held Calls on Shared Lines
CAPF Interaction with IPv6 Addressing
SSH Credentials in the Common Device Profile window
Accessing Cisco Security Agent Logs
Support for Party Entrance Tone
Support for Always Use Prime Line
Support for VG202 and VG204 Gateways
Support for Geolocations and Logical Partitioning
New fields That Are Supported for Export by Import/Export
Support for Seamless Integration (Apply Config)
Cisco Unified Cisco Unified Real-Time Monitoring Tool
Performance Monitoring Counters
Cisco Unified Communications Manager CDR Analysis and Reporting
Audit Events Get Logged for CAR
Ensure CAR Administrator Privileges Are Restored After Upgrade
Cisco Unified Communications Manager Call Detail Records
New Call Termination Cause Codes
SIP Calls with URL in callingPartyNumber Field
GlobalCallId Survives Over Cisco Unified Communications Manager Restarts
Cisco Unified TAPI Service Provider (TSP)
Skinny Client Control Protocol (SCCP)
Administrative XML (AXL) Programming
Serviceability XML Programming
Cisco Unified IP Phone 6900 Series
Enterprise Phone Configuration Window
Join and Direct Transfer Policy Configuration Parameter
Cisco Unified IP Phone Support HTTPS
Internet Protocol Version 6 on the Cisco Unified IP Phone
Restrict Unconfigured Phone Registration
Open Caveats for Cisco Unified Communications Manager Release 7.1(2) As of May 27, 2009
Cisco Unified Communication Manager CDR Analysis and Reporting
Purpose of Cisco Unified Communications Manager CDR Analysis and Reporting
Cisco Unified Communications Manager Security
Definition of Locally Significant Certificate
Using Certificates Issued by a Third-Party Certificate Authority
Cisco Unified Communications Operating System
Guidelines for Installing COP Files
Pre-Upgrade Task Is Omitted From Software Upgrades Chapter
Cisco Unified Communications Manager Administration
Administrator Can Set User Credential Policy to Expire Without Making a Global Policy Change
Number of Digits Field Description is Incorrect
Number of Locations and Regions That Cisco Unified Communications Manager Supports
Intercom Route Partition Configuration Settings Description Field Information Is Incorrect
Mobile Connect Support Restrictions
Configuring an H.323 Gateway for System Remote Access by Using Hairpinning
Enterprise Feature Access Two-Stage Dialing
Valid Characters in Name Field of Access List Configuration Window
Valid Characters in Name Field of Role Configuration Window
Valid Characters in Name and Description Fields of Remote Destination Profile Window
Valid Characters in Name Field of Geolocation Filter Configuration Window
Valid Characters in Name Field of Geolocation Configuration Window
Directory Number Chapter Includes Incorrect Information on Alerting Name and Display Name Fields
End User Chapter Includes Incorrect Information for Manager User ID Field
Trunk Configuration Chapter Does Not State That You Can Enter Hostname in Destination Address Field
Licensing Chapter Does Not State That You Should Use Microsoft Outlook to Receive Licenses
Device Name of Cisco Unified Mobile Communicator Must Not Exceed 15 Characters
Mobile Voice Access Directory Number Field Description
Recording Destination Address Field Description
OpenLDAP Version 2.3.41 Not Listed in LDAP Synchronization Documentation
Do Not Begin Starting and Ending Directory Numbers with a Zero (0)
Time-of-Day Routing Chapter Omits Information About Defined Time Periods
Changed Values of Mobility Cell Pick
Obtaining Documentation and Submitting a Service Request
Release Notes for Cisco Unified Communications Manager Release 7.1(2a)
Updated April 22, 2010
This document contains information pertinent to Cisco Unified Communications Manager Release 7.1(2) (which got deferred) as well as information specific to Cisco Unified CM 7.1(2a).
Updates to Cisco Unified CM 7.1(2a):
•
August 27, 2009—Added the note under the "Upgrading from Cisco Unified Communications Manager Release 5.1(3e) to 7.1(x) Releases" section
•
•
•
•
To view the release notes for previous versions of Cisco Unified Communications Manager, choose the Cisco Unified Communications Manager version from the following URL: http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_release_notes_list.html.
Before you install Cisco Unified Communications Manager, Cisco recommends that you review the "Important Notes" section for information about issues that may affect your system.
Note
Cisco recommends that you check Cisco.com for the latest software updates to Cisco Unified Communications Manager and its applications and download and install the latest updates on your system before the deployment of your Cisco Unified Communications Manager system. For a list of commonly used URLs, see the "The Latest Software Upgrades for Unified CM 7.1 on Cisco.com" section.
Introduction
Cisco Unified Communications Manager, the call-processing component of the Cisco Unified Communications System, extends enterprise telephony features and capabilities to IP phones, media processing devices, voice-over-IP (VoIP) gateways, mobile devices, and multimedia applications.
Cisco Unified Communications Manager Business Edition (Unified CMBE) offers you the features and functionality of Cisco Unified Communications Manager (Unified CM) and Cisco Unity Connection on one appliance platform.
System Requirements
The following sections comprise the system requirements for this release of Cisco Unified CM.
Server Support
Make sure that you install and configure Cisco Unified CM on a Cisco Media Convergence Server (MCS) or a Cisco-approved HP server configuration or a Cisco-approved IBM server configuration.
To find which MCS are compatible with this release of Cisco Unified CM, refer to the Supported Servers for Cisco Unified Communications Manager Releases: http://www.cisco.com/en/US/prod/collateral/voicesw/ps6790/ps5748/ps378/prod_brochure0900aecd8062a4f9.html.
Note
Note
Uninterruptible Power Supply
Cisco recommends that you connect each Cisco Unified Communications Manager Business Edition server to an uninterruptible power supply (UPS) to provide backup power and protect your system against a power failure.
When Cisco Unified Communications Manager Business Edition runs on one of the servers listed in Table 1, basic integration to the UPS model APC SmartUPS 1500VA USB and APC 750VA XL USB gets supported.
Integration occurs via a single point-to-point Universal Serial Bus (USB) connection. Serial and SNMP connectivity to UPS does not get supported, and the USB connection must be point-to-point (in other words, no USB hubs). Single- and dual-USB UPS models get supported with the APC SmartUPS 1500VA USB and APC 750VA XL USB. The feature activates automatically during bootup if a connected UPS gets detected.
Alternatively, you can execute the show ups status CLI command which shows the current status of the USB-connected APC smart-UPS device and starts the monitoring service if it is not already started. The CLI command also displays detected hardware, detected versions, current power draw, remaining battery runtime, and other relevant status information.
When the feature is activated, graceful shutdown will commence as soon as the low battery threshold is reached. Resumption or fluctuation of power will not interrupt or abort the shutdown, and administrators cannot stop the shutdown once the feature is activated.
For unsupported Cisco Unified Communications Manager Business Edition releases, MCS models and/or UPS vendor/make/models, you can cause an external script to monitor the UPS. When low battery gets detected, you can log on to Cisco Unified Communications Manager by using Secure Shell (SSH), access the CLI, and execute the utils system shutdown command.
Table 1 Supported Servers for Basic Integration
MCS-7828-H3
MCS-7828-I3
MCS-7828-H4
MCS-7828-I4
MCS-7828-I4
Upgrading to Cisco Unified Communications Manager 7.1(2a)
The following sections contain information pertinent to upgrading to this release of Cisco Unified CM.
•
•
•
•
•
Before You Begin
1.
To do that, open Cisco Unified Communications Manager Administration. The following information displays:
–
–
2.
Special Upgrade Information
The following sections include information that you must know before you begin the upgrade process.
•
•
I/O Throttling
This section describes how I/O throttling affects the upgrade process, identifies possible causes of slow or stalled upgrades, and provides actions you can take to speed up the upgrade.
I/O Throttling Overview
I/O throttling prevents call processing degradation during the upgrade but may cause the upgrade to take longer. I/O throttling, which is necessary if you perform the upgrade during normal business hours, gets enabled by default. If you disable throttling during normal business hours or other high-traffic hours, this may cause a core dump in Cisco Unified Communications Manager. Be aware that the higher the call processing load on the system during the upgrade, the longer the upgrade takes.
Disabling I/O throttling
If you can perform the upgrade during a maintenance window, you can disable I/O throttling to decrease the time that it takes for the upgrade to complete.
To disable I/O throttling, use one of the following methods before you start the upgrade:
•
•
Note
Note
Server Models
The server model that you have also impacts the upgrade speed. Upgrades on servers that have SATA hard drives, such as MCS-7816, MCS-7825, MCS-7828, take longer than servers with SAS/SCSI hard drives, such as MCS-7835 and MCS-7845.
Write-Cache
A disabled write-cache on the server also causes the upgrade process to run more slowly. Multiple factors can cause the write-cache to get disabled, including dead batteries on older servers.
Before starting an upgrade, verify the status of the write-cache on the MCS-7828-H4 and MCS-7835/45 disk controllers. You do not need to verify the write-cache status on the MCS-7816, MCS-7825, or other MCS-7828 servers. To verify write-cache status, access the Cisco Unified Operating System Administration, and choose Show > Hardware.
If you determine that your write-cache is disabled because of a dead battery, you need to replace the hard disk controller cache battery. Follow your local support procedures to get this battery replaced.
See the following examples of output from the Show > Hardware menu for details on determining the battery and write-back cache status.
The following example shows write-cache enabled. The example indicates that 50 percent of the cache is reserved for write and 50 percent of the cache is reserved for read. If the write-cache was disabled, 100 percent of the cache would be reserved for read or the Cache Status would not equal "OK". Also, the battery count equals "1". If the controller battery was dead or missing, it would indicate "0".
Example 1-1 7835/45-H1, 7835/45-H2, 7828-H4 Servers with Write-Cache Enabled
-------------------------------RAID Details :Smart Array 6i in Slot 0Bus Interface: PCISlot: 0Cache Serial Number: P75B20C9SR642PRAID 6 (ADG) Status: DisabledController Status: OKChassis Slot:Hardware Revision: Rev BFirmware Version: 2.80Rebuild Priority: LowExpand Priority: LowSurface Scan Delay: 15 secCache Board Present: TrueCache Status: OKAccelerator Ratio: 50% Read / 50% WriteTotal Cache Size: 192 MBBattery Pack Count: 1Battery Status: OKSATA NCQ Supported: FalseThe following example indicates that the battery status is enabled and that the the write-cache mode is enabled in (write-back) mode.
Example 1-2 7835/45-I2 Servers with Write-Cache Enabled
----------RAID Details :Controllers found: 1----------------------------------------------------------------------Controller information----------------------------------------------------------------------Controller Status : OkayChannel description : SAS/SATAController Model : IBM ServeRAID 8kController Serial Number : 20ee0001Physical Slot : 0Copyback : DisabledData scrubbing : EnabledDefunct disk drive count : 0Logical drives/Offline/Critical : 2/0/0---------------------------------------------------Controller Version Information---------------------------------------------------BIOS : 5.2-0 (15421)Firmware : 5.2-0 (15421)Driver : 1.1-5 (2412)Boot Flash : 5.1-0 (15421)---------------------------------------------------Controller Battery Information---------------------------------------------------Status : OkayOver temperature : NoCapacity remaining : 100 percentTime remaining (at current draw) : 4 days, 18 hours, 40 minutes---------------------------------------------------Controller Vital Product Data---------------------------------------------------VPD Assigned# : 25R8075EC Version# : J85096Controller FRU# : 25R8076Battery FRU# : 25R8088----------------------------------------------------------------------Logical drive information----------------------------------------------------------------------Logical drive number 1Logical drive name : Logical Drive 1RAID level : 1Status of logical drive : OkaySize : 69900 MBRead-cache mode : EnabledWrite-cache mode : Enabled (write-back)Write-cache setting : Enabled (write-back) when protected by batteryNumber of chunks : 2Drive(s) (Channel,Device) : 0,0 0,1Logical drive number 2Logical drive name : Logical Drive 2RAID level : 1Status of logical drive : OkaySize : 69900 MBRead-cache mode : EnabledWrite-cache mode : Enabled (write-back)Write-cache setting : Enabled (write-back) when protected by batteryNumber of chunks : 2Drive(s) (Channel,Device) : 0,2 0,3Device Name of Cisco Unified Mobile Communicator Must Not Exceed 15 Characters Before 7.1(2a) Upgrade
Before you upgrade to Cisco Unified Communications Manager 7.1(2a), ensure that the device name of a Cisco Unified Mobile Communicator does not exceed 15 characters in Cisco Unified Communications Manager Administration. If the device name of a Cisco Unified Mobile Communicator exceeds 15 characters, migration of this device will fail when you upgrade to Cisco Unified Communications Manager 7.1(2a) and the following error message gets written to the upgrade log:
InstallFull *ERROR* Name for Cisco Unified Mobile Communicator device(s) must be 15 or less, please correct and rerun upgrade.If an existing Cisco Unified Mobile Communicator device name specifies a longer name, shorten the device name to 15 or fewer characters before the upgrade.
Important Upgrade Information
Do not upgrade Cisco Unified CMBE at the same time that the Cisco Unity Connection task Upgrade Database Statistics is running. Because both processes are processor intensive, allowing them to run simultaneously may cause the system to stop functioning and force you to restart the server.
By default, the Upgrade Database Statistics task runs at 3:30 am daily. To determine whether the task schedule has been changed, whether the task is currently running, and how long the task has recently taken to complete, log on to Cisco Unity Connection Administration. Click Tools > Task Management > Update Database Statistics.
The Task Definition Basics window displays a history of when the task started and when it completed. If the Time Started column has a value and the Time Completed column does not, this indicates that the task is currently running.
If you must run the upgrade at a time that could overlap with the Upgrade Database Statistics task, reschedule the task to run before or after the upgrade. On the Task Definition Basics window for the task, click Edit > Task Schedule.
Do not reschedule the task to run during normal business hours. When the upgrade completes, reset the schedule to the default settings.
Making Configuration Changes After an Upgrade
The administrator must not make any configuration changes to Cisco Unified Communications Manager during an upgrade. Configuration changes include any changes that you make in Cisco Unified Communications Manager Administration, Cisco Unified Serviceability, and the User Option windows.
If you are upgrading your system, you must complete the upgrade tasks in this section before you perform any configuration tasks.
Caution
Upgrade Tasks
To successfully complete the upgrade, perform the upgrade tasks in the following order before you begin making configuration changes.
Note
Procedure
Step 1
Tip
Step 2
Step 3
Step 4
Step 5
Note
Step 6
•
•
–
–
–
–
–
Before you proceed, ensure that you have a good database replication status. For more information about using the Cisco Unified Real-Time Monitoring Tool, see the Cisco Unified Cisco Unified Real-Time Monitoring Tool Administration Guide.
Step 7
Upgrade Paths to Cisco Unified Communications Manager 7.1(2a)
For information about supported Cisco Unified CM upgrades, see the Cisco Unified Communications Manager Software Compatibility Matrix at the following URL:
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/compat/ccmcompmatr.htmlOrdering the Upgrade Media
To upgrade to Cisco Unified CM Release 7.1(2a), use the Product Upgrade Tool (PUT) to obtain a media kit and license or to purchase the upgrade from Cisco Sales.
To use the PUT, you must enter your Cisco contract number (Smartnet, SASU or ESW) and request the DVD/DVD set. If you do not have a contract for Cisco Unified Communications Manager, you must purchase the upgrade from Cisco Sales.
For more information about supported Cisco Unified CM upgrades, see the Cisco Unified Communications Manager Software Compatibility Matrix at the following URL:
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/compat/ccmcompmatr.html
See the "Software Upgrades" chapter of the Cisco Unified Communications Operating System Administration Guide.
Upgrading from Cisco Unified Communications Manager Release 5.1(3e) to 7.1(x) Releases
This information applies when you upgrade from any of the following releases to any 7.1.x release:
•
•
–
–
–
Before you upgrade, you must install the COP file ciscocm.513e_upgrade.cop.sgn on the server. This COP file is available from the following URL:
http://tools.cisco.com/support/downloads/go/ImageList.x?relVer=COP-Files&mdfid=280735907&sftType=Unified+Communications+Manager%2FCallManager+Utilities&optPlat=&nodecount=2&edesignator=null&modelName=Cisco+Unified+Communications+Manager+Version+5.1&treeMdfId
For information about installing this COP file, follow the installation instructions included with the COP file.
Note
Upgrading to Unified CM 7.1(2a) by Using the UCSInstall File
Because of its size, the UCSInstall iso file, UCOS_7.1.2.20000-2.sgn.iso, comprises two parts:
•
•
Procedure
Step 1
Step 2
Note
a.
cat UCSInstall_UCOS_7.1.2.20000-2.sgn.iso_part1of2 UCSInstall_UCOS_7.1.2.20000-2.sgn.iso_part2of2 > UCSInstall_UCOS_7.1.2.20000-2.sgn.iso
b.
COPY /B UCSInstall_UCOS_7.1.2.20000-2.sgn.iso_part1of2+UCSInstall_UCOS_7.1.2.20000-2.sgn.iso_part2of2 UCSInstall_UCOS_7.1.2.20000-2.sgn.iso
Step 3
4b9836cd8c29d02c90dd5f9bd8863f16 UCSInstall_UCOS_7.1.2.20000-2.sgn.iso
Step 4
Consider the following:
•
•
•
Step 5
Upgrading From an Engineering Special
If you want to upgrade to Cisco Unified CM 7.1(2a) and you are currently running an Engineering Special (ES), contact TAC to obtain the fixes that are included in the ES that you currently use.
The Latest Software Upgrades for Unified CM 7.1 on Cisco.com
You can access the latest software upgrades for Unified CM 7.1 from http://www.cisco.com/kobayashi/sw-center/sw-voice.shtml.
Related Documentation
The view documentation that supports Cisco Unified CM Release 7.1(2a), go to http://www.cisco.com/en/US/products/sw/voicesw/ps556/tsd_products_support_series_home.html
Limitations and Restrictions
A list of compatible software releases represents a major deliverable of Cisco Unified Communications Manager System testing. The recommendations, which are not exclusive, represent an addition to interoperability recommendations for each individual voice application or voice infrastructure product.
For a list of software and firmware versions of IP telephony components and contact center components that were tested for interoperability with Cisco Unified Communications Manager 7.1(2a) as part of Cisco Unified Communications System Release 7.1 testing, see
http://www.cisco.com/go/unified-techinfo
Note
Important Notes
The following section contains important information that may have been unavailable upon the initial release of documentation for Cisco Unified Communications Manager Release 7.1(2a).
•
•
•
•
•
•
•
•
•
•
•
Context-Sensitive Help Does Not Display for Some Windows
Context-sensitive help (Help > This Page) does not display for the Network Configuration window in the Cisco Unified Communications Operating System (Show > Network). To access the online help for this page, choose Help > Contents. After the online help displays, choose Status and Configuration > Network Configuration.
Context-sensitive help (Help > This Page) does not display for the following windows in the Bulk Administration Tool.
•
To access the online help for this page, click Help > Contents. After the online elp displays, choose Cisco Unified CM Bulk Administration Guide > Mobility > Access List > Exporting Access Lists.
•
To access the online help for this page, click Help > Contents. After the online help displays, choose Cisco Unified CM Bulk Administration Guide > Mobility > Remote Destination Profile > Exporting Remote Destination Profile > Using Remote Destination Profile Export.
•
See the following section for information on this window:
Deleting Unassigned Directory Numbers
Use the following procedure to delete unassigned directory numbers by creating a query to locate the phone records.
Procedure
Step 1
The Delete Unassigned Directory Numbers window displays.
Step 2
•
•
•
From the second Delete Bulk Unassigned Directory Number where drop-down list box, choose one of the following criteria:
•
•
•
•
•
•
Step 3
Step 4
A list of discovered phones displays by
•
•
•
Tip
Step 5
The default description is Delete Unassigned DN - Query
Step 6
Step 7
Note
Step 8
CSCta09513 Switch Version Does Not Complete
Prior to the release of Cisco Unified Communications Manager Release 7.1(2a), if your servers were running Cisco Unity Connection 2.x and you attempt to upgrade to Cisco Unified CM 7.1(2), the switch version task did not complete to make the new version software the active partition.
The release of Cisco Unified CM 7.1(2a) resolves this problem.
CSCta12062 Null Value in NetworkLocale Caused Database Exception
Prior to Cisco Unified Communications Manager Release 7.1(2), AXL did not allow a tkField to get updated to NULL. When an EMPTY value was sent in tags (for example, <networkLocale></networkLocale> in the UpdatePhone API), the EMPTY value was ignored.
Cisco Unified CM 7.1(2) included a change to this behavior. EMPTY values did not get ignored. They updated the database with a NULL value.
This behavioral change caused applications that send EMPTY values in ENUM tags in their insert operations to fail.
The release of Cisco Unified CM Release 7.1(2a) restores the original behavior. EMPTY tkFields get ignored.
CSCsz91530 Logical Partitioning Feature Does Not Work Correctly in Conference Scenario When Multiple H.323 Gateways Are Configured in a Route Group
The logical partitioning feature does not work as defined in the Cisco Unified Communication Manager Administration Guide under the following conditions:
Conditions
•
•
or
A route group gets configured with an H.323 gateway in combination with another MGCP port/SIP trunk device.
Effect
Be aware that, under these conditions, when a call gets routed to the H.323 gateway, the geolocation that corresponds to the call is not available for logical partitioning policy matching.
Workaround
To ensure that you do not encounter this caveat, either
•
•
For more information see CSCsz91530.
CSCsy92863 Intercom Route Partition Online Help Is Incorrect
The Intercom Route Partition Configuration Settings description field in the Configuring Intercom chapter of the Cisco Unified Communications Manager Administration Guide omits a complete list of the non-alphanumeric characters that are not allowed in the description. The unacceptable characters comprise double-quotes ("), angle brackets (<>), square bracket ([ ]), ampersand (&), percentage sign (%).
Admin Password Gets Corrupted If Correction is Made During Password Reset
When you use the Pwrecovery tool to reset your password, if the new password is unacceptable, one of the following messages displays.
•
This message displays if, when you attempted to change the password, you did not enter exactly the same word when you confirmed the new password.
•
This message displays if the password that you entered is fewer than 6 characters.
•
This message displays if the password that you entered already exists in the dictionary or is based on a word that already exists in the dictionary.
If you continue by entering an acceptable password, the system seems to accept the reset password; however, that password cannot be used and attempts to use pwrecovery do not work. GUI log in still works, but you cannot log into the platform GUI or CLI.
Workarounds
•
Passwords Do Not Match
Log in as pwrecovery to relaunch the pwrecovery tool and follow normal procedure.
Password Too Short or Password in Dictionary
Contact TAC to reset the admin password.
Removing Hard Drives
Cisco only supports replacing failed hard drives. Cisco does not support drive pulling/swapping as a method of fast upgrade reversion, restore, or server recovery.
CSCsz33878 IPMA Wizard Constraint
Be aware that you can run the IPMA Wizard only once. Attempts to run it more than once will fail.
CSCsz21235 Core Dump File Gets Generated During the Cisco Security Agent Shutdown Process
Intermittently, your system may experience a core dump during the Cisco Security Agent for Unified Communications Manager shutdown process.
Cause
Causes of the core dump include
•
•
–
–
–
–
•
Workaround
No workaround exists. You initiated an action that required Security Agent for Unified CM to shut down. Security Agent for Unified CM will shut down properly, but might leave a core file as a result of the shutdown operation.
The core file gets generated infrequently. This defect does not introduce any security concern and does not impact call processing as it is only encountered after a user-initiated action that requires Security Agent for Unified CM to be shut down.
Creating a Custom Help Desk Role and Custom Help Desk User Group
Some companies want their help desk personnel to have privileges to be able to perform certain tasks, such as adding a phone, adding an end user, or adding an end user to a user group in Cisco Unified Communications Manager Administration.
Performing the steps in the following example allows help desk personnel to add a phone, add an end user, and add the end user to the Standard CCM End Users user group, which allows an end user to access and update the Cisco Unified CM User Options.
Example—Allows Help Desk Personnel to Add Phone, Add End User, and Add End User to User Group
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
a.
b.
Step 7
a.
b.
c.
d.
e.
f.
Next Steps
In Cisco Unified Communications Manager Administration, the help desk personnel can add the phone, add the user, and add the end user to the user group.
•
•
•
Tip
Use Microsoft Outlook to Receive Cisco Unified Communications Manager Licenses
When you obtain a license file from the Product License Registration window on www.cisco.com, the system sends the license file(s) to you via e-mail by using the e-mail ID that you provided. When you receive license files from e-mail clients other than Microsoft Outlook, for example, Microsoft Entourage, additional characters may exist in the license file, which can prevent you from being able to upload the license file in Cisco Unified Communications Manager Administration. To avoid this issue, Cisco recommends that you use Microsoft Outlook when you receive license files for Cisco Unified Communications Manager.
If you obtained a license file with additional characters in it, perform the following procedure:
Procedure
Step 1
Step 2
Step 3
Step 4
For More Information
•
Multiple Tenant MWI Modes Service Parameter
The Multiple Tenant MWI Modes service parameter, which supports the Cisco CallManager service, specifies whether to apply translation patterns to voice-message mailbox numbers. Valid values specify True, which means that Cisco Unified Communications Manager uses translation patterns to convert voice-message mailbox numbers into directory numbers when your voice-messaging system issues a command to set a message waiting indicator, or False, which means that Cisco Unified Communications Manager does not translate the voice-message mailbox numbers that it receives from your voice-messaging system.
Be aware that this service parameter supports Cisco Unified Communications Manager integrations with Cisco Unity Connection. If your voice-mail extensions require translation in Cisco Unified Communications Manager, set the Multiple Tenant MWI Modes service parameter to True after you install or upgrade to Cisco Unified Communications Manager 7.1(2).
Considerations for LDAP Port Configuration
When you configure the LDAP Port field in Cisco Unified Communications Manager Administration, you specify the port number that the corporate directory uses to receive LDAP requests. How your corporate directory is configured determines which port number to enter in this field. For example, before you configure the LDAP Port field, determine whether your LDAP server acts as a Global Catalog server and whether your configuration requires LDAP over SSL. Consider entering one of the following port numbers:
Your configuration may require that you enter a different port number than the numbers that are listed in the following bullets. Before you configure the LDAP Port field, contact the administrator of your directory server to determine the correct port number to enter.
LDAP Port For When the LDAP Server Is Not a Global Catalog Server
•
•
LDAP Port For When the LDAP Server Is a Global Catalog Server
•
•
New and Changed Information
This section contains information on the following topics:
•
•
•
•
•
•
•
•
•
Documentation Changes
This section highlights some documentation changes for the 7.1(2) release; for example, this section highlights new documents, new chapters in guides, and information that moved from one document to another document. This section does not contain all the documentation updates for the 7.1(2) release. Use this section in conjunction with the information in the "New and Changed Information" section and the "Documentation Updates" section.
Cisco Unified Communications Manager Administration Updates
•
•
•
Troubleshooting information for intercom now exists in the Troubleshooting Guide for Cisco Unified Communications Manager, instead of in the "Intercom" chapter of the Cisco Unified Communications Manager Features and Services Guide.
•
•
•
•
The Release 7.1(2) version of the "Cisco Unified Mobility" chapter of the Cisco Unified Communications Manager Features and Services Guide includes only the Cisco Unified Mobility features and capabilities that are native to Cisco Unified Communications Manager.
The Cisco Unified Mobility features and capabilities that require configuration of Cisco Unified Mobility Advantage and Cisco Unified Mobile Communicator now get documented in the new chapter, "Cisco Unified Mobility Advantage and Cisco Unified Mobile Communicator Integration," of the Cisco Unified Communications Manager Features and Services Guide. The "Cisco Unified Mobility Advantage and Cisco Unified Mobile Communicator Integration" chapter discusses the following topics:
–
–
–
–
–
–
Serviceability Updates
•
•
•
–
–
–
–
–
–
–
–
Installation, Upgrade, and Migration
This following sections describe the changes for installation, upgrade, and migration in Cisco Unified Communications Manager 7.1(2):
•
•
System History Log for Cisco Unified Communications Manager
This system history log provides a central location for getting a quick overview of the initial system install, system upgrades, Cisco option installations, DRS backups and DRS restores, as well as switch version and reboot history.
Description
This section provides a description of the system history log feature.
Overview
The system history log exists as a simple ASCII file, system-history.log, and the data does not get maintained in the database. Because it does not get excessively large, the system history file does not get rotated.
The system history log provides the following functions:
•
•
•
•
•
•
•
•
System History Log Fields
Each system history log entry contains the following fields:
•
The system history log fields can contain the following values:
•
•
•
–
–
–
–
–
–
–
–
–
–
–
•
–
–
–
–
–
•
–
–
–
Example
Example 3 shows a sample of the system history log.
Example 3 System History Log
admin:file dump install system-history.log=======================================Product Name - Cisco Unified Communications ManagerProduct Version - 6.1.2.9901-117Kernel Image - 2.4.21-47.EL.cs.3BOOT=======================================07/25/2008 14:20:06 | root: Install 6.1.2.9901-117 Start07/25/2008 15:05:37 | root: Install 6.1.2.9901-117 Success07/25/2008 15:05:38 | root: Boot 6.1.2.9901-117 Start07/30/2008 10:08:56 | root: Upgrade 6.1.2.9901-126 Start07/30/2008 10:46:31 | root: Upgrade 6.1.2.9901-126 Success07/30/2008 10:46:43 | root: Switch Version 6.1.2.9901-117 to 6.1.2.9901-126 Start07/30/2008 10:48:39 | root: Switch Version 6.1.2.9901-117 to 6.1.2.9901-126 Success07/30/2008 10:48:39 | root: Restart 6.1.2.9901-126 Start07/30/2008 10:51:27 | root: Boot 6.1.2.9901-126 Start08/01/2008 16:29:31 | root: Restart 6.1.2.9901-126 Start08/01/2008 16:32:31 | root: Boot 6.1.2.9901-126 StartCLI Considerations
You can access the system history log by using the CLI file command; for example:
•
•
Cisco Unified Communications Manager Administration Configuration Tips
No Cisco Unified Communications Manager Administration configuration tips exist for this feature.
GUI Changes
No GUI changes exist for this feature.
Service Parameter and Enterprise Parameter Changes
No service parameter and enterprise parameter changes exist for this feature.
Installation/Upgrade (Migration) Considerations
No installation or upgrade considerations exist for this feature.
Serviceability Considerations
To access the system history log in RTMT, navigate to RTMT Trace Collection:
RTMT > Trace Log Collection
BAT Considerations
No BAT considerations exist for this feature.
CAR/CDR Considerations
No CAR/CDR considerations exist for this feature.
Security Considerations
No security considerations exist for this feature.
AXL and CTI Considerations
No AXL and CTI considerations exist for this feature.
User Tips
No user tips exist for this feature.
For More Information
For more information about using the CLI, see the Cisco Unified Communications Operating System Administration Guide or the Command Line Interface Reference Guide for Cisco Unified Solutions.
For more information about RTMT, see the Cisco Unified Real-Time Monitoring Tool Administration Guide.
Device Name of Cisco Unified Mobile Communicator Must Not Exceed 15 Characters Before 7.1(2) Upgrade
For information on this topic, see the "Device Name of Cisco Unified Mobile Communicator Must Not Exceed 15 Characters Before 7.1(2a) Upgrade" section.
Cisco Unified Communications Operating System Administration
This section describes changes to the Cisco Unified Communications Operating System Administration GUI.
•
Customized Log-on Message
You can upload a text file that contains a customized log-on message that appears in Cisco Unified Communications Operating System Administration, Cisco Unified Communications Manager Administration, and the command line interface.
To upload a customized log-on message, follow this procedure:
Procedure
Step 1
The Customized Logon Message window displays.
Step 2
Step 3
Note
When you next log in to the system, the customized log-on message displays.
Step 4
Your customized log-on message gets deleted, and the system displays the default log-on message.
Ethernet IPv6 Configuration Settings
Cisco Unified Communications Manager Business Edition does not support IPv6, so you cannot configure the settings in the Ethernet IPv6 Configuration window.
For More Information
•
Command Line Interface
This section contains information about the Command Line Interface (CLI).
show memory
The Command Line Interface Reference Guide for Cisco Unified Communications Solutions Release 6.1(3) does not contain updated information for the show memory command. Use the following updated information.
Command Syntax
show memory
count
modules
size
Options
•
•
•
Parameters
None
Spaces in File Names
You can use CLI commands to directly work with file names that contain spaces. For example, you could use the file delete command to delete a log file with the name cisco test log in the Platform directory:
file delete activelog platform cisco test log
Relative Paths
When you download a file to your local computer with the file get command, the system prompts you to enter a download directory. You can specify a relative path for the download directory by using the ./ notation, as shown in the following example:
Download directory: ./RepStat
If you specify a download directory that does not exist on your local computer, the file get command creates it for you.
New Commands and Parameters
This section provides information about the new CLI commands for Cisco Unified Communications Manager Release 7.1(2).
For more information about command syntax and parameters, see the Command Line Interface Reference Guide for Cisco Unified Solutions.
•
This command enables, disables, and provides the status of audit logging. When audit logging is enabled, the system monitors and records user actions in both Cisco Unified Communications Manager and Cisco Unified Serviceability.
You can also use the CLI file commands to manipulate the audit log, including the following commands:
–
–
–
–
–
Note
•
This command collects all the files that are required for CSA diagnostics and assembles them into a single CSA diagnostics file. You can retrieve this file by using the file get command.
•
Use this command to enable password complexity rules for the type of characters in a password.
When you enable password complexity, you must follow these guidelines when you assign a password:
–
–
–
–
–
•
Note
Use this command to modify the value for the minimum password length for Cisco Unified Communications Operating System accounts.
Acceptable values must be equal-to or greater-than 6.
•
Use this command to modify the value for maximum password age, in days, for Cisco Unified Communications Operating System accounts.
Be aware that acceptable values must be equal-to or greater-than 90 days.
Note
Cisco Unified Communications Manager Administration
This section contains information on the following topics:
•
•
New and Updated Enterprise and System Parameters
The following sections contain information on new and updated enterprise and service parameters:
Enterprise Parameters
To access the enterprise parameters in Cisco Unified Communications Manager Administration, choose System > Enterprise Parameters. To display the help for the service parameter, click the name of the enterprise parameter in the window.
•
•
•
•
•
•
•
•
Service Parameters
To access the service parameters in Cisco Unified Communications Manager Administration, choose System > Service Parameters. Choose the server and the service name that the parameter supports. For some parameters, you may need to click Advanced to display the service parameter. To display the help for the service parameter, click the name of the service parameter in the window.
•
•
•
•
•
•
•
•
•
•
Menu Changes
This section contains information on the following menus in Cisco Unified Communications Manager Administration:
Main Window
The main window contains the following changes:
•
•
•
System
The System menu contains the following changes:
•
•
•
•
•
•
•
•
•
Call Routing
The Call Routing menu provides the following new and updated settings.
•
•
•
Media Resources
No changes exist for the Media Resources menu.
Voice Mail
No changes exist for the Voice Mail menu.
Device
•
•
•
•
•
•
•
•
•
Application
No updates or new fields exist for this menu.
User Management
The User Management menu displays the following new settings:
•
•
Bulk Administration
The Bulk Administration menu displays the following new and updated settings.
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Cisco Unified Communications Manager Features and Applications
This section contains information on the following Cisco Unified Communications Manager Administration features and applications:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Always Use Prime Line
Tip
Description
After you configure the Always Use Prime Line setting in Cisco Unified Communications Manager Administration, when the phone is idle (off hook) and receives a call on any line, the primary line gets chosen for the call.
Tip
Cisco Unified Communications Manager Administration Configuration Tips
When you configure this feature, going off hook makes only the first line active, even when a call rings on another line on the phone; that is, the call does not get answered on that line. In this case, the phone user must choose the other line to answer the call.
For more configuration considerations, see Table 2.
GUI Changes
The Always Use Prime Line setting displays in the following windows in Cisco Unified Communications Manager Administration.
•
•
•
•
•
For information on how the Always Use Prime Line setting works when a phone idle or busy, see Table 2.
Tip
Service Parameter and Enterprise Parameter Changes
If you want to configure this feature via the clusterwide service parameter, Always Use Prime Line, which supports the Cisco CallManager service, choose System > Service Parameters in Cisco Unified Communications Manager Administration. Then, choose the server and the Cisco CallManager service. From the Always Use Prime Line drop-down list box, choose True.
Installation/Upgrade (Migration) Considerations
No special installation or upgrade considerations exist for this feature. After you install or upgrade to Cisco Unified Communications Manager 7.1(2), you can configure this feature per device or per device profile.
Serviceability Considerations
This feature relies on the Cisco CallManager service, so activate the service by choosing Tools > Service Activation in Cisco Unified Serviceability. In addition, you can run SDI trace for the Cisco CallManager service. When you view the log in RTMT, you can see the configured value that is used by the device; for example, alwaysPrimeLine=1, which indicates that the device uses On for the configuration.
BAT Considerations
The Bulk Administration GUI includes the following updates to support the Always Use Prime Line feature: Always Use Prime Line drop-down list box—choose one of the following options:
•
•
•
Note
Note
•
–
–
–
–
–
–
–
–
–
–
–
–
–
–
•
•
CAR/CDR Considerations
No CAR or CDR considerations exist for this feature.
Security Considerations
No security considerations exist for this feature.
AXL and CTI Considerations
See the "Always Use Prime Line" section.
User Tips
For a list of phones that support this feature, see the "Line Select" section.
For More Information
•
Always Use Prime Line for Voice Message
Tip
Description
After you configure the Always Use Prime Line for Voice Message setting in Cisco Unified Communications Manager Administration, the primary line on the phone becomes the active line for retrieving voice messages when the phone user presses the Messages button on the phone.
Tip
Cisco Unified Communications Manager Administration Configuration Tips
For configuration considerations, see Table 3.
GUI Changes
The Always Use Prime Line for Voice Message setting displays in the following windows in Cisco Unified Communications Manager Administration.
•
•
•
•
•
For information on how the Always Use Prime Line for Voice Message setting works when a phone is idle or busy, see Table 3.
Tip
Service Parameter and Enterprise Parameter Changes
If you want to configure this feature via the clusterwide service parameter, Always Use Prime Line for Voice Message, which supports the Cisco CallManager service, choose System > Service Parameters in Cisco Unified Communications Manager Administration. Then, choose the server and the Cisco CallManager service. From the Always Use Prime Line for Voice Message drop-down list box, choose True.
Installation/Upgrade (Migration) Considerations
No special installation or upgrade considerations exist for this feature. After you install or upgrade to Cisco Unified Communications Manager 7.1(2), you can configure this feature per device.
Serviceability Considerations
This feature relies on the Cisco CallManager service, so activate the service by choosing Tools > Service Activation in Cisco Unified Serviceability. In addition, you can run SDI trace for the Cisco CallManager service. When you view the log in RTMT, you can see the configured value that is used by the device; for example, alwaysUsePrimeLineForVM=2, which indicates that the device uses the default.
BAT Considerations
The Bulk Administration GUI includes the following updates to support the Always Use Prime Line for Voice Mail feature:
Always Use Prime Line for Voice Message drop-down list box—Choose one of the following options:
•
•
•
Note
Note
CAR/CDR Considerations
No CAR or CDR considerations exist for this feature.
Security Considerations
No security considerations exist for this feature.
AXL and CTI Considerations
See the "Always Use Prime Line" section.
User Tips
For a list of phones that support this feature, see the "Line Select" section.
For More Information
Barge, cBarge, and Single Button Barge Support for PLAR
Tip
Description
Barge, cBarge, or single-button barge allow a phone user to get added to a remotely active call that is on a shared line. Private Line Automatic Ringdown (PLAR) allows the phone user to dial a preconfigured number, and only this number, from the PLAR line. In Cisco Unified Communications Manager 7.1(2), a barge, cBarge, or single-button barge initiator can barge into a call via a shared line that is configured for PLAR; that is, the initiator can barge into the call if the barge target uses the preconfigured number that is associated with the PLAR line while on the call.
In previous releases of Cisco Unified Communications Manager [except for 6.1(3)], Cisco Unified Communications Manager sent the cBarge invocation to the PLAR line before it connected the barge call. If the PLAR line was busy in previous releases, the initiator received a busy reorder tone. In Cisco Unified Communications Manager 7.1(2) and 6.1(3) [and later 6.1(x) releases], Cisco Unified Communications Manager does not send the barge invocation to the PLAR line before it connects the barge call, so the barge occurs no matter what the state of the PLAR destination is.
Cisco Unified Communications Manager Administration Configuration Tips
To make barge, cBarge, or single-button barge work with PLAR, you must configure barge, cBarge, or single-button barge as described in the "Barge and Privacy" chapter in the Cisco Unified Communications Manager Features and Services Guide. In addition, you must configure the PLAR destination, a directory number that is used specifically for PLAR. The following examples describe how to enable PLAR functionality for phones that are running SCCP and for phones that are running SIP.
A and A' represent shared-line devices that you configured for barge, cBarge, or single-button barge, and B1 represents the directory number for the PLAR destination. To enable PLAR functionality from A/A', which are running SIP, see the following example:
Tip
Example for How to Configure PLAR
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
GUI Changes
No new configuration settings display in Cisco Unified Communications Manager Administration for this feature.
Service Parameter and Enterprise Parameter Changes
For parameters that you configure for barge, refer to the "Barge and Privacy" chapter in the Cisco Unified Communications Manager Features and Services Guide and the "Party Entrance Tone" section.
Installation/Upgrade (Migration) Considerations
You can use this feature after you install or upgrade to Cisco Unified Communications Manager 7.1(2).
Serviceability Considerations
No special serviceability considerations exist for this feature.
BAT Considerations
No BAT considerations exist for this feature.
CAR/CDR Considerations
No CAR or CDR considerations exist for this feature.
Security Considerations
No security considerations exist for this feature.
AXL and CTI Considerations
No AXL or CTI considerations exist for this feature.
User Tips
By pressing the Barge, cBarge, or Single Button Barge softkey in the remote in use call state, the initiator gets added to the call with all parties, and all parties receive a barge beep tone (if configured).
For a list of phones that support this feature, see the "Barge Tone Enhancements" section.
For More Information
•
Calling Party Normalization Enhancements
Description
In Cisco Unified Communications Manager 7.1(2), the names of the Incoming Calling Party settings changed in the Device Pool, Gateway, and Trunk Configuration windows, as shown in Table 4. For information on how Cisco Unified Communications Manager 7.0(x) configuration works after an upgrade to Cisco Unified Communications Manager 7.1(2), see the "Installation/Upgrade (Migration) Considerations" section.
Cisco Unified Communications Manager Administration Configuration Tips
This section contains information on the following topics:
•
•
Considerations for Configuring the Prefix Field
Before you configure the prefix fields, consider the following information.
•
•
•
•
•
•
•
Considerations for Configuring the Strip Digits Field
If your service provider prepends leading digits (for example, a zero) to the calling party number and you want to strip these digits before prepending other digits (for example, if the leading digits are not part of the E.164 number and you want to transform the calling party number to the E.164 format), you can configure the Strip Digits fields to ensure that Cisco Unified Communications Manager strips the leading digits before applying the prefixes to an incoming calling party number.
Before you configure the number of leading digits that Cisco Unified Communications Manager must strip from the calling party number, consider the following information.
•
•
•
•
•
•
•
•
GUI Changes
The settings in Table 4 display in the following windows in Cisco Unified Communications Manager Administration:
•
•
•
Tip
For configuration procedures for each configuration window, refer to the following sections:
•
•
•
Service Parameter and Enterprise Parameter Changes
No service or enterprise parameters changes occurred for this feature in 7.1(2).
Tip
If your service provider prepends leading digits (for example, a zero) to the calling party number and you want to strip these digits before prepending other digits (for example, if the leading digits are not part of the E.164 number and you want to transform the calling party number to the E.164 format), you can enter a colon (:) followed by the number of digits that you want to strip in the Incoming Calling Party National Number Prefix, Incoming Calling Party International Number Prefix, Incoming Calling Party Unknown Number Prefix, and/or Incoming Calling Party Subscriber Number Prefix service parameters to ensure that Cisco Unified Communications Manager strips the leading digits before applying the prefixes to an incoming calling party number. The value that you configure before the colon (:) represents the prefix; the value that you configure after the colon (:) specifies the number of digits that you want Cisco Unified Communications Manager to strip from the calling party number before it applies the prefix.
For example, you configure +:1 in the incoming prefix service parameters, which alerts Cisco Unified Communications Manager to strip the first digit from the calling party number and then apply the international escape character +. If an incoming call arrives as 04423452345, Cisco Unified Communications Manager strips the first digit, in this case, zero, from the calling party number and prefixes the international escape character + to the calling party number. As a result, the calling party number gets transformed to +4423452345.
To strip digits without prefixing anything, you can configure the colon (:) in the incoming prefix service parameters without configuring a prefix. If you do not enter a prefix before the colon (:), Cisco Unified Communications Manager strips the number of leading digits that you specify and does not apply a prefix to the calling party number. For example, if you configure :2, Cisco Unified Communications Manager strips 2 leading digits without applying a prefix.
If you want Cisco Unified Communications Manager to strip a certain number of leading digits, and the entire number of digits for the calling party number equals or specifies less than the value that you configure, Cisco Unified Communications Manager strips all digits but still applies the prefix; that is, if you configure a prefix. For example, if you enter +1:6 in the incoming prefix fields, and the calling party number contains 6 or fewer digits, Cisco Unified Communications Manager strips all digits and applies the prefix +1.
If you configure Cisco Unified Communications Manager to strip more digits than exist in the calling party number, Cisco Unified Communications Manager clears the calling party number (makes it blank).
If you do not configure a colon (:) in the incoming prefix service parameters, Cisco Unified Communications Manager does not strip any digits from the calling party number; that is, unless you configure the Strip Digit fields that are listed in Table 4, which support the configuration at the device level.
If you configure a prefix but the calling party number that arrives is empty, Cisco Unified Communications Manager does not apply the prefix.
Cisco Unified Communications Manager can strip up to 24 digits from the calling party number. If you enter :26 in the incoming prefix service parameters, Cisco Unified Communications Manager Administration displays a message and does not allow the configuration.
If an error occurs when Cisco Unified Communications Manager attempts to strip the digits and apply the prefix to the calling party number, Cisco Unified Communications Manager does not manipulate the digits or apply the prefixes; instead, Cisco Unified Communications Manager uses the calling party number that arrived for the call.
Tip
•
•
•
•
Tip
•
•
•
•
Tip
•
Installation/Upgrade (Migration) Considerations
If you upgrade from Cisco Unified Communications Manager 7.0(1) to 7.1(2), be aware that Cisco Unified Communications Manager moves the numbers of digits that you want stripped from the Incoming Prefix 7.0 fields in the Device Pool, Trunk, or Gateway Configuration windows to the Strip Digits fields in the same windows in Cisco Unified Communications Manager Administration 7.1(2). For example, if you configured :12 in the Incoming Calling Party International Number Prefix field in the Trunk Configuration window in 7.0(1), 12 displays in the Strip Digits field for the International Number in the Trunk Configuration window after you upgrade to 7.1(2).
If you configured the Incoming Prefix service parameters in 7.0(1) so Cisco Unified Communications Manager strips leading digits, Cisco Unified Communications Manager 7.1(2) does not change the configuration; that is, Cisco Unified Communications Manager 7.1(2) uses the value, including the : (colon), that you configured in 7.0(1).
Serviceability Considerations
This feature relies on the Cisco CallManager service, so make sure that this service is activated in Cisco Unified Serviceability.
Security Considerations
No security considerations exist for this feature.
AXL and CTI Considerations
See the "Enhancements to Calling Party Number Transformations" section.
User Tips
Depending on your configuration, a phone user may not need to edit the call log directory entry on the phone before placing a call. Depending on your configuration, the phone user may see the international escape character, +, in the call log directories on the phone.
For More Information
•
Cisco Unified Communications Manager Assistant Enhancements for Numeric User ID Login
Tip
Cisco Unified Communications Manager supports numeric user ID login for Cisco Unified Communications Manager Assistants from their Cisco Unified IP Phones.
To configure numeric user ID login, perform the following steps:
Procedure
Step 1
Step 2
In the section "Clusterwide Parameters (Parameters that apply to all servers)" set Alpha Numeric UserID to False.
Step 3
Cisco Unified Communications Manager Attendant Console Support in 7.1(2)
If you are upgrading from a compatible Cisco CallManager 4.X release or a compatible Cisco Unified Communications Manager 5.X, 6.X, or 7.X release to Cisco Unified Communications Manager Release 7.1(2), you can continue to use the Cisco Unified Communications Manager Attendant Console. As automated within the Cisco Unified Communications Manager upgrade process, the Cisco Unified Communications Manager Attendant Console plug-in will remain viewable from the Find and List Plugins window in Cisco Unified Communications Manager Administration 7.1(2).
Be aware, however, that Cisco no longer supports the Cisco Unified Communications Manager Attendant Console with new installations of Cisco Unified Communications Manager 7.X. For new installations, the Cisco Unified Communications Manager Attendant Console plug-in does not display in the Find and List Plugins window in Cisco Unified Communications Manager Administration.
If you previously obtained the Cisco Unified Communications Manager Attendant Console 7.0(x) plug-in from the Cisco software download site, you can use that plug-in with Cisco Unified Communications Manager 7.1(x) but only for upgrades of a compatible Cisco Unified Communications Manager 5.X, 6.X, or 7.X release to Cisco Unified Communications Manager Release 7.1(x). Cisco Systems does not authorize the use of the Cisco Unified Communications Manager Attendant Console 7.0(x) plug-in with new Cisco Unified Communications Manager 7.X installations, and its use does not get supported by the Cisco Technical Assistance Center.
If you need attendant console functionality after a Cisco Unified Communications Manager 7.X installation/upgrade, Cisco recommends that you use the Cisco Unified Business Attendant Console, Cisco Unified Enterprise Attendant Console, or the Cisco Unified Department Attendant Console.
For More Information
•
•
•
To obtain the documentation for Cisco Unified Business Attendant Console, Cisco Unified Enterprise Attendant Console, or Cisco Unified Department Attendant Console, click the Release Notes link or the Maintain and Operate link after you go to the preceding URL.
•
Cisco Web Dialer Configured in Application Server Window
Tip
Description
In previous releases of Cisco Unified Communications Manager [except for 6.1(3)], the List of WebDialers field in the Service Parameter window supported a maximum of 255 characters, which limited the scalability of the Redirector. In Cisco Unified Communications Manager 7.1(2) and 6.1(3), you configure the WebDialer servers in the Application Server Configuration window instead of the Service Parameters Configuration window.
Cisco Unified Communications Manager Administration Configuration Tips and GUI Changes
You can add a Cisco Web Dialer application server through the Application Server Configuration window. You access the Application Server Configuration window by choosing System > Application Server in Cisco Unified Communications Manager Administration. Cisco Web Dialer displays as one of the options in the Application Server Type drop-down list box.
If you add a Cisco Web Dialer application server in the Application Server Configuration window, the server displays in the List of Web Dialers field in the Service Parameter Configuration window for the Cisco WebDialer Web Service.
Service Parameter and Enterprise Parameter Changes
In Cisco Unified Communications Manager 7.1(2), you can configure either the List of WebDialers service parameter or the Cisco Web Dialer application server through the Application Server Configuration window. If you add a Cisco Web Dialer application server in the Application Server Configuration window, the server displays in the List of WebDialers field in the Service Parameter Configuration window for the Cisco WebDialer Web Service. You can access the Service Parameter Configuration window by choosing System > Service Parameters in Cisco Unified Communications Manager Administration.
Installation/Upgrade (Migration) Considerations
If you install Cisco Unified Communications Manager 7.1(2) and plan to use Cisco Web Dialer, configure the Cisco Web Dialer application server in the Application Server Configuration window. You do not need to configure the List of WebDialers field in the Service Parameter Configuration window if you configure the application server in the Application Server Configuration window.
Serviceability Considerations
Cisco Web Dialer relies on the Cisco WebDialer Web Service. If you have not already done so, activate this service in the Service Activation window in Cisco Unified Serviceability.
BAT Considerations
No BAT considerations exist for this feature.
CAR/CDR Considerations
No CAR or CDR considerations exist for this feature.
Security Considerations
No security considerations exist for this feature.
User Tips
For user enhancements for Cisco Web Dialer, see the "Cisco Web Dialer Enhancements" section.
For More Information
•
•
G.Clear Codec Support on SIP Trunks
Cisco Unified Communications Manager supports limited early offer for G.Clear data calls (also known as clear channel). The Early Offer for G.Clear Calls feature provides support for third-party SIP user agents that can do early offer to negotiate data calls without using a Media Termination Point. MTPs do not support the G.Clear codec.
If you enable both Media Termination Point Required and Early Offer for G.Clear Calls for a SIP device, the system does not allocate the MTP if the G.Clear codec in present in the offer. The system only allocates the MTP if the call is not G.Clear, and the MTP is required.
The Early Offer for G.Clear Calls feature supports both standards-based G.Clear (CLEARMODE) and proprietary Cisco Session Description Protocols (SDP), including CCD, G.nX64, and X-CCD.
To enable or disable Early Offer for G.Clear Calls, navigate to the SIP Profile Configuration window in Cisco Unified Communications Manager Administration (Device Device Settings > SIP Profile) and choose one of the following options for the Early Offer for G.Clear Calls parameter:
•
•
•
•
•
AXL and CTI Considerations
See the "Enhanced Clear Channel (G.clear) Support" section.
Geolocations and Geolocation Filters
This section, which describes support of geolocations and geolocation filters for Cisco Unified Communications Manager Business Edition 7.1(2), contains information on the following topics:
–
•
•
•
•
•
•
•
Description for Geolocations
Geographical location information, or geolocation, describes a physical position in the world that may correspond to the past, present, or future location of a person, event, or device.
Cisco Unified Communications Manager Administration allows you to specify a geolocation for every device.
The Request for Comments (RFC) 4119 standard provides the basis for geolocations. Geolocations use the civic location format that specifies the following fields: country, A1, A2, A3, A4, A5, A6, PRD, POD, STS, HNO, HNS, LMK, LOC, FLR, NAM, and PC.
In Cisco Unified Communications Manager Administration, geolocations get configured manually.
Tip
Configuration of geolocations entails provisioning the following elements:
•
–
–
–
Cisco Unified Communications Manager administrators must define the following item:
•
Cisco Unified Communications Manager administrators then assign geolocations to devices.
The following entities in a Cisco Unified Communications Manager system can have geolocation and geolocation filter values that are assigned:
•
•
•
•
Note
•
•
•
•
You do not need to associate media devices, such as media termination points (MTP), conference bridges (CFB), annunciators, and music on hold (MOH) servers, with geolocations.
Internally, the device layer of Cisco Unified Communications Manager associates with geolocation values that call processing uses. The following sequence takes place:
1.
2.
3.
The following logic determines the geolocation value:
1.
2.
3.
4.
5.
The standard record for a geolocation specifies Unspecified. Use this value when no geolocation needs to associate with a device. In such scenarios, any features that are based on geolocations do not execute.
Be aware that the Default Geolocation enterprise parameter can be configured from drop-down list boxes on the Enterprise Parameters Configuration window.
Geolocation Usage for Shared Lines and Route Lists
When the called party specifies a group device, a different geolocation can apply for each device in a group. For the early attended scenarios, you do not know the actual connected device until the device gets answered. Thus, the Geolocation information gets aggregated until the device answers.
•
•
Geolocation Examples
Table 5 specifies examples of geolocations.
Geolocation Identifiers
Geolocation identifiers get constructed from a combination of geolocations, geolocation filters, and device types of Cisco Unified Communications Manager devices.
Geolocation filters allow selection of specific fields from the 17 geolocation fields. Use the System > Geolocation Filter menu option in Cisco Unified Communications Manager Administration to configure geolocation filters manually. Specific Cisco Unified Communications Manager features associate the geolocation filters by using drop-down list boxes in the configuration windows of the devices that get configured for a particular feature.
The Cisco Unified Communications Manager device type of a device specifies one of the following values:
•
•
Refer to Table 10 in the "Logical Partitioning" section for a detailed listing of the Cisco Unified Communications Manager devices that associate with the Border and Interior device types.
The following object specifies an example geolocation identifier:
{geolocPkid=9dc76052-3a37-78c2-639a-1c02e8f5d3a2, filterPkid=d5bdda76-6a86-56c5-b5fd-6dff82b37493, geolocVal=, devType=8}
where:
The geolocVal field gets used in cases where the Cisco Unified Communications Manager database does not reference the geolocation record but data for a geolocation comes from another source.
In such cases, Cisco Unified Communications Manager constructs the name value pair for the geolocation fields.
Example: "country=US:A1=Texas:A3=Richardson:LOC=Building 6" where the value gets communicated through the geolocVal field.
Note
The following string specifies the logical representation of a geolocation identifier:
"Border:country=US:A1=Texas:A3=Richardson:LOC=Building 6"
Note
Description for Geolocation Filters
Cisco Unified Communications Manager administrators define the following item:
•
Cisco Unified Communications Manager administrators then assign geolocation filters to devices.
The following logic determines the geolocation filter value:
1.
2.
3.
4.
Geolocation Filter Examples
Table 6 specifies examples of geolocation filters.
Geolocation Configuration Tips
Use the System > Geolocation Configuration menu option in Cisco Unified Communications Manager Administration to configure geolocations.
Table 7 provides a checklist for configuring geolocations.
Geolocation Filter Configuration Tips
Use the System > Geolocation Filter menu option in Cisco Unified Communications Manager Administration to configure geolocation filters.
Table 8 provides a checklist for configuring geolocation filters.
GUI Changes for Geolocations and Geolocation Filters
Use the following new menu options in Cisco Unified Communications Manager Administration to configure the geolocations and geolocation filters:
•
•
The following existing Cisco Unified Communications Manager Administration windows contain new fields for configuring geolocations and geolocation filters:
•
•
•
•
•
Service Parameter and Enterprise Parameter Changes for Geolocations and Geolocation Filters
The following new enterprise parameter affects the configuration of geolocations:
•
Installation/Upgrade (Migration) Considerations for Geolocations and Geolocation Filters
The following migration considerations that affect the dial plan exist for geolocations and geolocation filters when you are migrating from releases of Cisco Unified Communications Manager that are earlier than Release 7.1(2):
•
–
–
–
–
–
During upgrade of Cisco Unified Communications Manager Release 7.1(x) or later from an earlier release, the following values get assigned for the entities that associate with configuration of geolocations and geolocation filters:
•
–
–
–
–
•
–
–
–
–
Serviceability and RTMT Considerations
No serviceability nor RTMT considerations exist for geolocations or geolocation filters.
BAT Considerations
The Cisco Bulk Administration Tool specifies several new menu items to support geolocations. See the "Support for Geolocations and Logical Partitioning" section for details.
CAR/CDR Considerations
No CAR/CDR considerations exist for geolocations or geolocation filters.
Security Considerations
No security considerations exist for geolocations or geolocation filters.
For More Information
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
H.235—Pass-Through Support
Consider the following:
During a call that employs H.235 encryption, do not invoke mid-call features such as call transfer or hold/resume operations. If you do, the call may become unencrypted.
Cisco Unified Communications Manager does not support H.235 encryption when a media termination point or transcoder gets inserted into a call. If this occurs, the call will become unencrypted.
H.329—Extended Video Channel Support
The extended video channels feature works via H.239 protocol and enables multiple video channel support. Cisco Unified Communications Manager supports negotiating an extended video channel by using the H.239 protocol in direct point-to-point H.323 calls. This also includes calls across the H.323 intercluster trunk.
Cisco Unified Communications Manager supports all H.239 associated support signals and commands that are specified in the H.239 recommendation.
The following characteristics apply to the extended video channels feature:
•
•
•
•
•
•
•
Support for Third-Party H.323 Devices
The extended video channel feature supports H.239 interoperability among third-party video endpoints and Cisco Unified Voice Conferencing. Cisco Unified Communications Manager allows an extended video channel to be used for presentation and live meeting transmission. This feature focuses on multiple video channel support via H.245 signaling. The following presentation applications provide basis for this multichannel support:
•
•
Both Natural Presenter package and People + Content use the H.239 protocol to negotiate capabilities and define the roles of the additional video channels.
Note
Note
H.323 Devices Invoke Presentation Feature
Tandberg and Polycom terminals allow the user to share presentation materials from various components (for example, VCR, Projector, PC, and so on). The components can physically connect with the terminals, and the PC can also run presentation applications that are provided by the vendor to transmit the presentation image. Be aware that the source of presentation and the component connection with the terminal are irrelevant to the mechanism of establishing video channels by using H.239.
Note
When two H.239-enabled terminals attempt to establish a video call, they declare their video capabilities for the main video channel for meeting participants and their extended video capabilities (H.239 capabilities) for the second video channel. The following contents comprise H.239 capability signals:
1.
2.
–
–
After the capabilities have been exchanged, both terminals immediately open two-way audio channels and the main video channels as in the traditional video calls.
Opening Second Video Channels
Depending on the third-party terminal implementation, the second video channel gets handled differently among vendors.
Natural Presenter Package by Tandberg
Tandberg initiates the second video channel on demand. A Tandberg device does not open the second video channel immediately after the main video channel is established. The second channel gets opened when one of the callers (the presenter) specifies the source of the presentation and invokes a command to start the presentation.
When a Tandberg user decides to start sharing the presentation, Tandberg requests the other call party to open an extended video channel for receiving the presentation image; therefore, a Tandberg-Tandberg call has only one-way second video channel.
People + Content by Polycom
Unlike Tandberg, a Polycom terminal initiates the second video channel immediately as a part of the default mechanism, after both parties have confirmed that additional video channels can get supported.
Note
Polycom initiates a request for the second video channel to the other call party regardless of the usage of the second video channel; therefore, in a Polycom-Polycom call, two-way video channels get opened between the devices even if only one of them sends out presentation image/video.
This implementation ensures that both call parties have the second video channel ready for transmission when the call parties decide to take the token to present something. Although one of the two video channels remains idle (not sending anything), the Polycom device controls bandwidth to ensure load efficiency.
Note
Note
Call Admission Control (CAC) on Second Video Channels
The following call admission control policies of Cisco Unified Communications Manager get applied to the second video channels:
Cisco Unified Communications Manager restricts the bandwidth usage by the second video channels on the basis of location configuration. When the second video channel is being established, Cisco Unified Communications Manager makes sure that enough video bandwidth stays available within the location pool and reserves bandwidth accordingly. If the required bandwidth is not available, Cisco Unified Communications Manager instructs the channel to reduce the available bandwidth to zero.
No change occurs in the region configuration or policies to support the second video channels.
Traditionally, Cisco Unified Communications Manager region policy only supported a call with a single video channel, and the total bandwidth usage of this call never gets larger than what the region configuration specifies.
If the administrator sets a finite region video bandwidth restriction for an H.239 call, Cisco Unified Communications Manager will violate the region policy because the region value will get used against the bandwidth that is requested for each video channel independently.
Example:
If the region video bandwidth is set to 384Kbps and the audio channel uses 64Kb/s, the maximum allowed bandwidth for each video channel will be (384Kb/s - 64Kb/s)= 320Kb/s. i.e. the maximum bandwidth to be used by the H.239 call will be (audio bw + 2*(384 - audio bw)) = 704Kb/s, which goes beyond the 384Kb/s bandwidth that the region specifies.
Note
Number of Video Channels Allowed
Cisco Unified Communications Manager 7.1(2) supports only a maximum of two video channels due to the following reasons:
•
•
H.239 Commands and Indication Messages
Command and Indication (C&I) messages get used for H.239 to manage tokens for the Presentation and Live roles and to permit devices to request release of video flow control to enable the operation of additional media channels. Cisco Unified Communications Manager supports all the C & I messages. Whenever Cisco Unified Communications Manager receives C&I messages, it relays them to the call party accordingly.
Be aware that the flow control release request and response messages can be used to request that the far end release flow control, so it allows an endpoint to send the indicated channel at the indicated bit rate.
Note
The Presentation role token messages allow an H.239 device to acquire the token for presentation. The other call party may accept or reject the request. The presenter device sends out a token release message when it is no longer needed.
Topology and Protocol Interoperability Limitation
Cisco Unified Communications Manager 7.1(2) supports only H.239 in H.323 to H.323 calls. Cisco Unified Communications Manager allows H.239 calls to be established across H.323 intercluster trunk or multiple nodes. If an H.239-enabled device attempts to make a call with a non-H323 end, the H.239 capabilities will get ignore, and the call will get conducted like the traditional video calls that supported Cisco Unified Communications Manager supports.
Cisco Unified Communications Manager does not support a second video channel when a media termination point or transcoder is inserted into the call. If it happens, the call will fall back to normal video calls.
Mid-Call feature Limitation
Cisco Unified Communications Manager supports opening second video channels only in direct H.323 to H.323 calls.
Caution
Internet Protocol Version 6 (IPv6)
Cisco Unified Communications Manager Business Edition does not support IPv6, so you cannot successfully configure IPv6 in Cisco Unified Communications Manager Administration, Cisco Unified Communications Operating System, or the Command Line Interface.
Licensing Enhancements
Tip
Description
Cisco Unified Communications Manager Releases 7.1(2) and 6.1(3) identify the state of a license; that is, if it is missing, if it is a demo license, or if it is an uploaded license. In addition, Cisco Unified Communications Manager Administration warns you whether Cisco Unified Communications Manager currently operates with demo licenses, with an insufficient number of licenses, or with an incorrect software feature license.
Cisco Unified Communications Manager Administration Configuration Tips
For information on how to configure licensing, refer to the licensing chapters in the Cisco Unified Communications Manager Administration Guide and Cisco Unified Communications Manager Security Guide.
GUI Changes
The following windows display the state of licenses in Cisco Unified Communications Manager Administration:
•
–
–
–
•
•
Service Parameter and Enterprise Parameter Changes
No service parameters or enterprise parameters considerations exist for these licensing enhancements.
Installation/Upgrade (Migration) Considerations
After you upgrade to Cisco Unified Communications Manager 7.1(2) from a compatible Cisco Unified CM 5.X or 6.X release, the Cisco CallManager service does not automatically run, even though Cisco Unified Serviceability shows that the Cisco CallManager service is activated.
Immediately after you complete the upgrade to Cisco Unified Communications Manager 7.1(2), upload the software feature license that is required for Cisco Unified Communications Manager 7.1(2) in Cisco Unified Communications Manager Administration and restart the Cisco CallManager service in Cisco Unified Serviceability. Until you perform these tasks, devices fail to register with Cisco Unified Communications Manager 7.1(2).
Serviceability Considerations
After you upload a license file, you must restart the Cisco CallManager service for the changes to take effect.
BAT Considerations
No BAT considerations exist for these licensing enhancements.
CAR/CDR Considerations
No CAR or CDR considerations exist for these licensing enhancements.
Security Considerations
No security considerations exist for these licensing enhancements.
AXL and CTI Considerations
No AXL or CTI considerations exist for these licensing enhancements.
User Tips
This feature does not impact the end user.
For More Information
•
•
Location-Based Call Admission Control Over Intercluster Trunk
Tip
Description
When a call is made across cluster through an intercluster trunk (ICT) and gets hairpinned back to the same location or site of the same cluster, although the media is exchanged between two endpoints in the same site or location, the current design of Cisco Unified Communications Manager location call admission control (CAC) deducts location bandwidth twice, once for the outbound call and again for the inbound call. The result does not correctly reflect the bandwidth consumption, which eventually causes denial of a new call to or from the site or location.
To resolve the bandwidth calculation problem, this feature enables Cisco Unified Communications Manager to pass location information, the primary key ID (PKID) of location record and location name, as a proprietary information element (IE) between the calling and called parties through an ICT, either in the H.323 protocol or SIP. Thus, either endpoint knows the true location information of the party/endpoint, not the location information of the ICT.
Currently Cisco Unified Communications Manager has Hub_None as the default location that has unlimited bandwidth, plus any user-created location to which the user can assign a device and for which the user can configure bandwidth.
A new type of Cisco Unified Communications Manager location gets created specifically for the ICT for this type application. This new type of location, designated as the Phantom location, also has unlimited bandwidth. The locations server does not deduct bandwidth for a device that is assigned to the Phantom location. A device, such as the ICT, that is assigned to the Phantom location can use its own location or the true location of the connected device. Likewise, the outbound ICT can use its own location or the callee location, and the inbound ICT can use its own location or the caller location to deduct or adjust the bandwidth.
When the media connect, Cisco Unified Communications Manager adjusts the allocated location bandwidth according to the negotiated media codec. Cisco Unified Communications Manager can correctly readjust the location bandwidth based on received callee location information for the outbound call. This enhancement helps the outbound call, which has reserved bandwidth during call setup time, to adjust the bandwidth back to 0 if the call is hairpinned back to the same site or location.
Some supplementary services, such as transfer, can also hairpin the call back to the same site or location after the initial call setup process. Be aware that passing the location information of the final destination through the Notify signals (H.323) and re-INVITE signals (SIP) back to the calling cluster, so bandwidth can be adjusted to the right value, is also required.
Because location record PKID is uniquely defined within the Cisco Unified Communications Manager enterprise environment, Cisco Unified Communications Manager uses location record PKID to identify whether the call over ICT has been looped back to the same cluster for the location-based CAC purpose. If other applications, like Cisco Voice Proxy (CVP), that do not have access to the Cisco Unified Communications Manager database for location record PKID information and also because PKID is a string of characters and digits, applications may need to rely on the location name information being passed around for the purpose of CAC. The same location name may exist for different locations with different location PKIDs in two different Cisco Unified Communications Manager clusters, which may cause confusion to the applications.
Cisco Unified Communications Manager Administration Configuration Tips
The Location Configuration window specifies the Phantom location as a location, besides the Hub_None location, that can be selected. Administrators cannot delete the Phantom location.
Administrators can create a new default location for the new Phantom location, similar to the Hub_None location. The Phantom location includes unlimited audio and video bandwidth value, and the administrator cannot modify the audio and video bandwidth values. The user can assign a location-pair RSVP policy between this new location and other existing locations.
Tip
GUI Changes
This feature does not entail any new menu options or new fields in Cisco Unified Communications Manager Administration. The Phantom value gets added for all entities that specify a location in the Location drop-down list box. The Location field displays in the Device Pool Configuration, Annunciator Configuration, Music On Hold (MOH) Server Configuration, Conference Bridge Configuration, Voice Mail Port Configuration, Voice Mail Port Wizard Configuration, CTI Route Point Configuration, Gateway Configuration, Phone Configuration, Trunk Configuration, and Pilot Point Configuration windows.
Service Parameter and Enterprise Parameter Changes
No service parameter nor enterprise parameter changes apply to this feature.
Installation/Upgrade (Migration) Considerations
Cisco Unified Communications Manager maintains the RSVP policy for the Phantom location during migration.
Serviceability Considerations
No serviceability considerations exist for this feature.
BAT Considerations
No BAT considerations exist for this feature.
CAR/CDR Considerations
No CAR nor CDR considerations exist for this feature.
Security Considerations
No security considerations exist for this feature.
AXL and CTI Considerations
No AXL nor CTI considerations exist for this feature.
User Tips
This feature does not entail user interaction.
For More Information
•
•
•
•
Logging Missed Calls for Shared Lines
Tip
Description
With the missed call logging for shared lines feature, the administrator can configure Cisco Unified Communications Manager Administration, or the phone user can configure Cisco Unified CM User Options, so Cisco Unified Communications Manager logs missed calls in the call history to a specified shared-line appearance on a phone.
Tip
The examples in Table 9, which use the following phones, describe how the missed call logging feature works for shared lines:
•
•
•
Cisco Unified Communications Manager Administration Configuration Tips
If this feature is not configured, the call history on the phone does not display missed calls for the specified line appearance.
GUI Changes
If the phone supports this feature, the Directory Number Configuration window in Cisco Unified Communications Manager Administration displays the Log Missed Calls check box, which allows you to turn on or off this feature. If the check box displays as checked (turned on), which is the default for this setting, Cisco Unified Communications Manager logs missed calls in the call history for that shared line appearance on the phone. To access the Directory Number Configuration window, choose Call Routing > Directory Number.
The Directory Number Configuration window in Cisco Unified Communications Manager Administration displays the Logged Missed Calls check box, which turns this feature on or off. If the check box displays as checked (turned on), which is the default for this setting, Cisco Unified Communications Manager logs missed calls in the call history for that shared line appearance on the phone. To access the check box, choose Call Routing > Directory Number. In the Directory Number Configuration window, highlight the associated device in the Associated Devices pane; then, click the Edit Line Appearance button.
In the Line Settings Configuration window in the Cisco Unified CM User Options, the phone user can check and uncheck the Log Missed Calls check box.
Service Parameter and Enterprise Parameter Changes
No new or updated parameters exist for this feature.
Installation/Upgrade (Migration) Considerations
After you install Cisco Unified Communications Manager 7.1(2) or upgrade to 7.1(2), you can configure this feature.
Serviceability Considerations
No serviceability considerations exist for this feature.
BAT Considerations
The Bulk Administration GUI includes the following updates to support the Log Missed Calls feature:
•
Note
•
–
–
–
–
–
–
–
–
–
–
–
–
–
–
•
–
–
•
CAR/CDR Considerations
No CAR or CDR considerations exist for this feature.
Security Considerations
No security considerations exist for this feature.
AXL and CTI Considerations
No AXL or CTI considerations exist for this feature.
User Tips
Tip
For a list of phone models that support this feature, see the "Missed Calls" section.
For More Information
Logical Partitioning
This section, which describes logical partitioning support for Cisco Unified Communications Manager 7.1(2), contains information on the following topics:
•
–
–
•
•
•
•
•
•
•
•
•
•
•
Description of Logical Partitioning
The Logical Partitioning feature specifies the capability of a telephony system to control calls and features on the basis of specific allowed or forbidden configurations. A common telephony system can provide access to Voice over Internet Protocol (VoIP) and Public Switched Telephone Networks (PSTN), and configuration can control access.
Logical partitioning specifies a call control feature in Cisco Unified Communications Manager that provides functionality, so communication between the following pairs of VoIP entities can be controlled:
1.
2.
3.
4.
Options exist to configure Cisco Unified Communications Manager, so any such set of VoIP devices may be allowed communication with each other and any device can be restricted to one device or to a group of devices. No logical partitioning policy logic exists on endpoints.
Be aware that logical partitioning is required to control such communication not only during basic call establishment but also during mid-call as a result of midcall features.
The Cisco Unified Communications Manager basic routing policy constructs of calling search spaces and partitions suffice to prevent forbidden basic calls from being established but are not sufficient to prevent forbidden calls from being created as a result of midcall features. In Cisco Unified Communications Manager, such midcall features often get termed Join and Redirect features, because these primitives often get used internally to affect these features.
Logical partitioning enhances Cisco Unified Communications Manager to handle such midcall scenarios. Configuration for logical partitioning remains independent of supplementary features, where the policy checking gets performed based on devices being joined or redirected to a supplementary feature.
Note
The logical partitioning solution comprises the following elements:
•
•
•
Identifiers for Logical Partitioning
Identifiers specify a device type for every device (element) in a Cisco Unified Communications Manager logical partitioning solution. Device types classify all elements into two types: interior and border. Table 10 specifies the Cisco Unified Communications Manager devices that associate with each device type:
Note
Allow and Deny Policies for Logical Partitioning
Based on the system requirements for VoIP network topology, you can configure Cisco Unified Communications Manager to provide the following default system policy for logical partitioning:
•
To allow VoIP communication, ensure the Allow policy is configured through logical partitioning configuration.
•
To deny VoIP communication, ensure the Deny policy is configured through logical partitioning configuration.
Cisco Unified Communications Manager Administration Configuration Tips for Logical Partitioning
Table 11 displays the configuration checklist for logical partitioning, which is documented in the "Logical Partitioning" chapter in the Cisco Unified Communications Manager Features and Services Guide. Before you configure logical partitioning in your network, review Table 11.
See the "Geolocations and Geolocation Filters" section for detailed information about the following entities that must be configured for logical partitioning:
•
•
The following entities in a Cisco Unified Communications Manager system can have geolocation values assigned:
•
•
•
•
•
•
•
Media devices, such as media termination points (MTP), conference bridges (CFB), annunciators, and music on hold (MOH) servers, do not need to associate with geolocation values.
Interactions and Limitations for Logical Partitioning
Beyond the configuration of geolocations, geolocation filters, and logical partitioning policies, logical partitioning requires special configuration when an allowed call changes due to the following features:
•
•
•
•
•
•
•
•
•
•
•
•
The following limitations apply to logical partitioning:
•
The UAS uses UPDATE request to communicate geolocation of the called party to the User Agent Client (UAC). This normally happens after 180 Ringing.
The logical partitioning policy checks may CANCEL the call if policy gets denied.
•
For example, meet-me and ad hoc chained conferences can have participants that have logical partitioning denied.
•
Be aware that the ICT with Q.SIG protocol is not allowed to communicate geolocation info for the caller or callee device. The ICT configuration for "Send Geolocation Information" gets disabled when the Q.SIG tunneled protocol gets selected.
•
For logical partitioning restricted scenario, the shared line drops the active call information for the duration of the call, even if some feature moves the shared-line call to allowed category.
•
Barge/cBarge does not occur because it gets prevented by not allowing shared lines to attempt these features based on logical partitioning deny policy with the connected party (the call instance gets dropped).
However, when the connected party is a conference bridge due to an active feature, such as Conference or Meet-Me, and an active shared-line device associates with a geolocation that is allowed for all the devices in the conference, the remote-in-use shared-line device shows call instance information. In this case, the remote-in-use phone can always perform the cBarge/Barge feature even if a disallowed participant participates in the conference. For the participants in cBarge/Barge, no logical partitioning policy checking exists, and you cannot prevent logical-partitioning-denied scenarios.
•
Communication to a SIP gateway can get disabled from a SIP trunk check box.
•
•
Phone A on CCM1 calls Phone B on CCM2 (using ICT or SIP trunk).
Phone B presses conference and invites PSTN to conference.
Limitation: The conference gets established.
After phone B goes on hook, the call between phone A and the PSTN on Cisco Unified Communications Manager 2 gets cleared with a reorder tone.
•
The logical partitioning policy check does not happen before the call gets placed to the mobile phone (as it happens for a basic SNR call). The current design checks logical partitioning policy only after SsJoinReq processing, which takes place after the mobile phone answers the call.
•
Outgoing PSTN calls can occur when Local Route Groups are configured.
Incoming PSTN calls do not get placed to the phone but receive a reorder tone.
•
Currently, no logical partitioning infrastructure gets added for notifications.
For forwarding failures, the RTMT Number of Forwarding Failures performance monitor counter does not increment. Instead, the Number of Basic Call Failures performance monitor counter increments.
•
Example
Remote destination (RD) phone that is behind IOS SIP or H.323 gateway calls VoIP phone A.
After authentication completes, RD phone makes a call to phone C, but the call gets denied due to logical partitioning restricted policy.
Call gets cleared to RD phone with cause 63 (Service or option not available), but no reorder tone gets played to the RD phone.
Note
This behavior occurs due to a design limitation on the IOS gateway side, which does not play reorder tone after the CONNECT state. The only tones that play after the CONNECT state specify 17 (Busy) or 44 (No Circuit Available).
Similar limitations apply for Hook Flash, Onhook Transfer, and other supplementary features.
•
•
•
GUI Changes for Logical Partitioning
Use the following new menu options in Cisco Unified Communications Manager Administration to configure the logical partitioning feature:
•
•
•
The following existing Cisco Unified Communications Manager Administration windows contain new fields for configuring logical partitioning:
•
•
•
•
•
Service Parameter and Enterprise Parameter Changes for Logical Partitioning
The following new enterprise parameters affect the configuration of the logical partitioning feature:
•
•
•
•
Installation/Upgrade (Migration) Considerations for Logical Partitioning
The following migration considerations that affect the dial plan exist for the logical partitioning feature when you are migrating from releases of Cisco Unified Communications Manager earlier than Release 7.1(2):
•
–
–
–
–
–
•
During upgrade of Cisco Unified Communications Manager Release 7.1(x) or later from a previous release, the following values get assigned for the entities that associate with logical partitioning configuration:
•
•
•
–
–
–
–
•
–
–
–
–
•
–
Serviceability Considerations for Logical Partitioning
The following consideration exists for the logical partitioning feature:
•
–
–
–
–
–
–
–
–
–
–
See the "Performance Objects and Counters for Cisco Unified Communications Manager" appendix of the Cisco Unified Real-Time Monitoring Tool Administration Guide for details.
BAT Considerations for Logical Partitioning
The Cisco Bulk Administration Tool specifies several new menu items to support logical partitioning. See the "Support for Geolocations and Logical Partitioning" section for details.
CAR/CDR Considerations for Logical Partitioning
The following CAR and CDR considerations exist for the logical partitioning feature:
•
•
Security Considerations for Logical Partitioning
No security considerations exist for the logical partitioning feature.
AXL and CTI Considerations for Logical Partitioning
AXL supports all geolocation-related database changes in Cisco Unified Communications Manager. The AXL SOAP interface gets modified to accommodate all new configuration that the logical partitioning feature requires.
The following CTI considerations exist for the logical partitioning feature:
•
•
•
User Tips for Logical Partitioning
No user tips exist for the logical partitioning feature.
For More Information About Logical Partitioning
•
•
•
•
•
•
•
•
•
•
•
Multicast Music On Hold Over H.323 Intercluster Trunks
Tip
Description
The Multicast Music on Hold (MOH) over H.323 Trunk feature allows multicast MOH to work over H.323 intercluster trunks (ICTs). Prior to the implementation of this feature, multicast MOH used bandwidth for each unicast MOH over the same ICT, which wasted bandwidth.
Prior to the implementation of this feature in 6.1(3) and 7.1(2), the H.323 Open Logical Channel (OLC) ACK message carried the IP address and port for multicast MOH. With the implementation of this feature, the H.323 OLC message now carries the IP address and port for multicast MOH, and Cisco Unified Communications Manager adds the mechanism to handle the information in the H.323 OLC message.
The new service parameter, Send Multicast MOH in H.245 OLC Message, controls the Multicast Music On Hold Over H.323 Intercluster Trunk feature. Both Cisco Unified Communications Manager nodes that are involved in the call must support single-transmitter multicast for the setting of this parameter to have any effect. This service parameter affects only the side of the party that places the call on hold and does not affect how the far end carries the multicast transport address. Even if this parameter is turned off, multicast MOH applies for the held-party side of the call as long as the held party has the capability to support single-transmitter multicast.
When a call connects over an intercluster trunk and one of the parties presses the Hold key, MOH will stream over the intercluster trunk. If multicast MOH is turned on and the holding party and trunk are configured to use the multicast MOH server, MOH streams with multicast. Only one multicast MOH stream streams over the trunk no matter how many calls are put on hold on this trunk.
Cisco Unified Communications Manager Administration Configuration Tips
Calls that connect over Cisco Unified Communications Manager intercluster trunks use this feature for multicast MOH. This feature does not work if any middle box between Cisco Unified Communications Managers does not pass the new fields in Terminal Capability Set (TCS) and OLC message.
No additional configuration exists for this new feature in addition to the normal configuration for setting up multicast MOH. This new feature only applies between Cisco Unified Communications Managers that support single-transmitter multicast.
You can turn this feature off by changing the default True value of the new Send Multicast MOH in H.245 OLC Message service parameter to False. You may need to do so if an interoperability issue arises.
GUI Changes
This feature does not entail any GUI changes to Cisco Unified Communications Manager Administration.
Service Parameter and Enterprise Parameter Changes
If you want to configure this feature via the clusterwide service parameter, Send Multicast MOH in H.245 OLC Message, which supports the Cisco CallManager service, choose System > Service Parameters in Cisco Unified Communications Manager Administration. Then, choose the server and the Cisco CallManager service. From the Send Multicast OH in H.245 OLC Message drop-down list box, choose True.
The new feature stays active by default. To turn off the feature, set the value of the Send Multicast MOH in H.245 OLC Message service parameter to False. Do so to resolve interoperability issues that the feature may cause.
The new service parameter governs the multicast MOH behavior on H.323 trunks and devices. The new service parameter does not control multicast MOH over SIP trunks because multicast MOH over SIP trunks does not constitute a new behavior.
Installation/Upgrade (Migration) Considerations
No installation nor upgrade considerations exist for this feature. You may, however, turn off the feature if interoperability issues arise as a result of the feature. To do so, set the value of the Send Multicast MOH in H.245 OLC Message service parameter to False.
Serviceability Considerations
No serviceability considerations exist for this feature.
BAT Considerations
No BAT considerations exist for this feature.
CAR/CDR Considerations
No CAR nor CDR considerations exist for this feature.
Security Considerations
No security considerations exist for this feature.
AXL and CTI Considerations
No AXL considerations exist for this feature.
CTI-controlled phones work as before for multicast MOH. CTI-controlled applications such as CTI ports and CTI route points do not perform multicast MOH, which is the same behavior as prior to the implementation of this feature.
User Tips
When multicast MOH gets turned on in Cisco Unified Communications Manager Administration, phone users receive MOH if the call connects through an intercluster trunk.
For More Information
•
Off-Hook Abbreviated Dial
Description
Cisco Unified Communications Manager Release 7.1(2) introduces an enhancement to the existing Abbreviated Dial feature to allow abbreviated dialing while off hook. The user can initiate Off-Hook Abbreviated Dialing while placing a basic call, while conferencing a call, while transferring a call, or while a call is on hold.
To enable Off-Hook Abbreviated Dialing, assign the softkey Abbreviated Dial (AbbrDial) to a softkey template and assign the template to the phone. Be aware that the Abbreviated Dial (AbbrDial) softkey can be included in the Off Hook, Off Hook With Feature, or Digits After First states of a Softkey Layout Configuration.
Cisco Unified Communications Manager Administration Configuration Tips
Step 1
a.
The Find and List Softkey Templates window displays. Records from an active (prior) query may also display in the window.
b.
To filter or search records
–
–
–
–
c.
All matching records display.
Step 2
a.
Note
b.
The Softkey Layout Configuration window displays. The Select a call state to configure drop-down list box lists each Cisco Unified Communications Manager call state for an IP phone.
c.
–
–
–
–
–
d.
e.
f.
GUI Changes
No GUI changes occurred to support this feature.
Service Parameter and Enterprise Parameter Changes
No service or enterprise parameter changes occurred to support this feature.
Installation/Upgrade (Migration) Considerations
Cisco Unified Communications Manager 7.1(2) introduces this feature. After you install or upgrade to 7.1(2), you can configure this feature.
Serviceability Considerations
This feature relies on the Cisco CallManager service, so make sure that you activated the Cisco CallManager service in the Service Activation window in Cisco Unified Serviceability.
BAT Considerations
The Bulk Administration Tool (BAT) supports the import and export of the AbbrDial softkey configuration.
CAR/CDR Considerations
No CAR/CDR considerations exist for this feature.
Security Considerations
No security considerations exist for this feature.
AXL and CTI Considerations
No AXL or CTI considerations exist for this feature.
User Tips
For information on user tips and phone support for this feature, see "Off-Hook Abbreviated Dialing" section.
For More Information
•
•
•
OpenLDAP 2.3.41 Can Synchronize with Cisco Unified Communications Manager Database
DirSync allows you to synchronize the data from corporate directories to Cisco Unified Communications Manager. Cisco Unified Communications Manager Release 7.1(2) allows synchronization from OpenLDAP 2.3.41 to the Cisco Unified Communications Manager database. In addition, Cisco Unified Communications Manager Release 7.1(2) allows synchronization from the following types of directories that were available in previous releases:
•
•
•
•
•
For more information, refer to the "Understanding the Directory" section of the Cisco Unified Communications Manager System Guide.
Party Entrance Tone
Tip
Description
Tip
With the party entrance tone feature, a tone plays on the phone when a basic call changes to a multiparty call; that is, when a basic call changes to a barged call, cBarged call, ad hoc conference, meet-me conference, or a joined call. In addition, a different tone plays when a party leaves the multiparty call.
If the controlling device, that is, the originator of the multiparty call has a built-in bridge, the tone plays to all parties if you configured party tone entrance for the controlling device. When the controlling device leaves the call, Cisco Unified Communications Manager identifies whether another device on the call can play the tone; if another device on the call can play the tone, Cisco Unified Communications Manager plays the tone. If the controlling device cannot play the tone, Cisco Unified Communications Manager does not play the tone even if you enable the party entrance tone feature.
When a joined call or ad hoc conference begins, Cisco Unified Communications Manager uses the party entrance tone configuration from the conference controller. Cisco Unified Communications Manager uses this configuration until the conference ends.
If two ad hoc conferences are chained together and the controlling device for one conference has the party entrance tone set to True while the other controlling device for the other conference has a party entrance tone of False, Cisco Unified Communications Manager determines whether to play the tone based on to which conference the new party is added.
When a barge call gets created, the party entrance tone configuration of the barge target that shares the line with the barge initiator determines whether Cisco Unified Communications Manager plays the party entrance tone.
When a cBarge call gets created, the party entrance tone configuration of the cBarge target that shares the line with the cBarge initiator determines whether Cisco Unified Communications Manager plays the party entrance tone. However, if the call for the target is an existing ad hoc conference that is in the same cluster, the party entrance tone configuration for the ad hoc conference controller determines whether Cisco Unified Communications Manager plays the tone.
When a meet-me conference gets created, the party entrance tone configuration for the first party to enter the conference determines whether Cisco Unified Communications Manager plays the tone. Cisco Unified Communications Manager uses the configuration for the first party until the conference ends.
Cisco Unified Communications Manager Administration Configuration Tips and GUI Changes
To use the party entrance feature, ensure that you turned the privacy feature off for the devices and ensure that the controlling device for the multiparty call has a built-in bridge.
To configure the party entrance tone for a specific directory number, choose Call Routing > Directory Number in Cisco Unified Communications Manager Administration. From the Party Entrance Tone drop-down list box, choose one of the following options:
•
•
•
Service Parameter and Enterprise Parameter Changes
If you want to configure this feature for the entire cluster instead of per line, configure the Party Entrance Tone service parameter, which supports the Cisco CallManager service. To access this parameter, choose System > Service Parameters in Cisco Unified Communications Manager Administration; choose the server and the Cisco CallManager service. When the parameters display, locate the Party Entrance Tone service parameter. For more information on this parameter, click the name of the service parameter or the question-mark button in the Service Parameter Configuration window.
Installation/Upgrade (Migration) Considerations
Cisco Unified Communications Manager 7.1(2) introduces this feature.
Serviceability Considerations
This feature relies on the Cisco CallManager service, so make sure that the service is activated in Cisco Unified Serviceability.
BAT Considerations
The Bulk Administration GUI has the following updates to support the party entrance tone feature:
•
–
–
–
Note
•
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
•
–
–
–
Note
CAR/CDR Considerations
No CAR or CDR considerations exist for this feature.
Security Considerations
No security considerations exist for this feature.
AXL and CTI Considerations
See the "Barge Enhancement Feature" section.
User Tips
For information on the phones that support this feature, see the "Barge Tone Enhancements" section.
For More Information
Phone Migration in Cisco Unified Communications Manager Administration
Description
The Phone Migration window in Cisco Unified Communications Manager Administration allows you to migrate feature, user, and line configuration for a phone to a different phone; that is, you can migrate data to a different phone model or to the same phone model that runs a different protocol. For example, you can migrate data from a Cisco Unified IP Phone 7965 to a Cisco Unified IP Phone 7975, or you can migrate data from a phone model that runs SCCP, for example, the Cisco Unified IP Phone 7965 (SCCP), and move it to the same phone model that runs SIP, for example, the Cisco Unified IP Phone 7965 (SIP).
Tip
Cisco Unified Communications Manager Administration Configuration Tips
Before you can migrate phone configuration to a new phone, consider the following information:
•
•
•
•
Migrating to a phone that uses fewer speed dials or lines does not remove the speed dials or lines for the original phone from Cisco Unified Communications Manager Administration/the Cisco Unified Communications Manager database, although some of the speed dials/lines do not display on the new phone. After you migrate the configuration, you can see all speed dials and lines for the original phone in the Phone Configuration window for the new phone.
•
•
GUI Changes
Table 12 describes the configuration settings that display in the Phone Migration Configuration window.
Service Parameter and Enterprise Parameter Changes
No service or enterprise parameter changes exist for this feature.
Installation/Upgrade (Migration) Considerations
No special installation or upgrade considerations exist for this feature. After you install or upgrade to Cisco Unified Communications Manager 7.1(2), you can use this feature.
Serviceability Considerations
No special serviceability considerations exist for this feature.
BAT Considerations
Before you can migrate the phone configuration in Cisco Unified Communications Manager Administration, you must create a phone template for the phone model to which you want to migrate in BAT (Bulk Administration > Phones > Phone Template). For example, if you want to migrate the configuration for a Cisco Unified IP Phone 7965 to a Cisco Unified IP Phone 7975, you create the phone template for the Cisco Unified IP Phone 7975.
If you want to migrate several phones at the same time, consider using BAT, as described in the "Phone Migration in BAT" section.
CAR/CDR Considerations
No CDR or CAR considerations exist for this feature.
Security Considerations
No security considerations exist for this feature.
User Tips
No end user tips exist for this feature.
For More Information
QSIG Variant Configuration for a Gateway or Trunk
Description
The QSIG variant specifies how to encode the Invoke Object ID (OID) for remote operations service element (ROSE) operations, as well as how to code the protocol profile for outbound facility Information elements.
Cisco Unified Communications Manager Release 7.1(2) introduces an enhancement to the existing QSIG variant feature to allow CCM administrators to configure QSIG variants for s specific trunk or gateway. In previous releases, you could configure the QSIG variant for cluster service configurations only.
Cisco Unified Communications Manager Release 7.1(2) also introduces support by using Annex M.1 to tunnel QSIG over intercluster trunks with the QSIG Variant ECMA.
Cisco Unified Communications Manager Administration Configuration Tips
To create Cisco Unified Communications Manager compatibility with your version of the QSIG protocol, configure the ASN.1 ROSE OID Encoding and QSIG Variant in the service parameters, for a gateway, or for a trunk.
Tip
If you choose ECMA for the QSIG Variant parameter, you must choose the Use Global Value (ECMA) setting for the ASN.1 ROSE OID Encoding service parameter.
If you choose ISO for the QSIG Variant parameter, you normally choose the Use Local Value setting for the ASN.1 ROSE OID Encoding service parameter. You may need other configurations in unusual situations.
Tip
Cisco Unified Communications Manager supports using Annex M.1 to tunnel QSIG over intercluster trunks. To configure Annex M.1, do one of the following tasks:
•
•
Serviceability Considerations
This feature relies on the Cisco CallManager service, so make sure that you activated the Cisco CallManager service in the Service Activation window in Cisco Unified Serviceability.
BAT Considerations
The Bulk Administration Tool (BAT) supports the import and export of the QSIG variant configuration.
CAR/CDR Considerations
No CAR/CDR considerations exist for this feature.
Security Considerations
No security considerations exist for this feature.
AXL and CTI Considerations
See the "QSIG variant Per Trunk or Gateway" section.
User Tips
This feature update does not impact end users.
For More Information
•
•
•
•
Standard Audit Log Administration Role
The Standard Audit Log role allows you to configure the following Resource Access Information. For each item, you can choose Read access, Update access, or both.
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Service Parameter and Enterprise Parameter Changes
This feature requires no configuration to work.
Installation/Upgrade (Migration) Considerations
After you install Cisco Unified Communications Manager 7.1(2) or upgrade to 7.1(2), you can use this feature.
Serviceability Considerations
For more information, refer to the "Audit Logging" section.
BAT Considerations
No BAT considerations exist for this feature.
CAR/CDR Considerations
No CAR or CDR considerations exist for this feature.
Security Considerations
No security considerations exist for this feature.
AXL and CTI Considerations
No AXL or CTI considerations exist for this feature.
User Tips
This feature does not affect the end user.
Standard Audit Users User Group
Only a user or application that is assigned to the Standard Audit Users user group can change audit log settings. By default, the CCMAdministrator application user gets assigned to the Standard Audit Users user group and can add or delete users from the Standard Audit Users user group.
You can configure the audit log settings that can be changed by a Standard Audit Log user through the Standard Audit Log Administration role. See the "Standard Audit Log Administration Role" section.
Service Parameter and Enterprise Parameter Changes
This feature requires no configuration to work.
Installation/Upgrade (Migration) Considerations
After you install Cisco Unified Communications Manager 7.1(2) or upgrade to 7.1(2), you can use this feature.
Serviceability Considerations
For more information, refer to the "Audit Logging" section.
BAT Considerations
No BAT considerations exist for this feature.
CAR/CDR Considerations
No CAR or CDR considerations exist for this feature.
Security Considerations
No security considerations exist for this feature.
AXL and CTI Considerations
No AXL or CTI considerations exist for this feature.
User Tips
This feature does not affect the end user.
Synchronization of Configuration Settings
Description
Cisco Unified Communications Manager Release 7.1(2) allows you to use a single button in Cisco Unified Communications Manager Administration to synchronize various devices with the most recent configuration changes. This button gets called "Apply Config" when it is located on a configuration window and gets called "Apply Config to Selected" when it is located in a Find and List window. These buttons apply any outstanding configuration settings in the least-intrusive manner possible. (For example, some devices may not require a reset/restart to apply the configuration.)
Cisco Unified Communications Manager Administration Configuration Tips
To synchronize a device with the most recent configuration changes, perform the following procedure.
Procedure
Step 1
The Find and List window for the applicable items displays.
Step 2
Step 3
Step 4
a.
–
–
–
b.
–
–
Make any additional configuration changes.
Click Save.
Click Apply Config.
Proceed to Step 5.
Step 5
Note
Click OK.
GUI Changes
Cisco Unified Communications Manager Administration added the "Apply Config" or "Apply Config to Selected" buttons to the windows that are listed in Table 13.
Service Parameter and Enterprise Parameter Changes
The Enterprise Parameters Configuration window (System > Enterprise Parameters) contains the "Apply Config" button.
Installation/Upgrade (Migration) Considerations
No specific installation or upgrade considerations exist for this feature.
Serviceability Considerations
No serviceability considerations exist for this feature.
BAT Considerations
BAT supports this feature by enabling the "Apply Config" button in the following windows:
•
•
CAR/CDR Considerations
No CAR/CDR considerations exist for this feature.
Security Considerations
No security considerations exist for this feature.
AXL and CTI Considerations
No AXL or CTI considerations exist for this feature.
User Tips
This feature does not affect the end user.
For More Information
Refer to configuration information as it pertains to the windows that are listed in Table 13 in the following documents:
•
•
•
Tip
Unconfigured Device Registration Attempts Restricted
Tip
Prior to Cisco Unified Communications Manager 6.1(3) or 7.1(2) (not 7.0(1), if a Cisco Unified IP Phone had not been added to the Cisco Unified Communications Manager database and did not have auto-registration enabled, the phone would repeatedly attempt to register (unsuccessfully) with Cisco Unified Communications Manager, thus wasting Cisco Unified Communications Manager capacity with these repeated registration requests.
However, in Cisco Unified Communications Manager 6.1(3) or 7.1(2), if auto-registration is not enabled and the phone has not been added to the Cisco Unified Communications Manager database, the phone will not attempt to register with Cisco Unified Communications Manager. The phone continues to display the Configuring IP message until auto-registration gets enabled or until the phone gets added to the Cisco Unified Communications Manager database.
Supported Devices
The following devices support this changed registration behavior:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Cisco Unified Communications Manager Administration Configuration Tips
For information on configuring autoregistration, refer to the "Autoregistration" chapter in the Cisco Unified Communications Manager System Guide. For information on configuring a phone, refer to the "Phone Configuration" chapter in the Cisco Unified Communications Manager Administration Guide.
Before you configure a phone, consider the following information:
•
–
–
•
For a phone that uses a real MAC address, not the dummy MAC address that is created via BAT, the check box displays as checked and disabled, which indicates that the phone uses device license units and can register with Cisco Unified Communications Manager.
For a phone that uses the dummy MAC address that is created via BAT, the Is Active check box displays as unchecked and enabled. If you manually convert the dummy MAC address to a real MAC address in the Phone Configuration window, check the Is Active check box, which ensures that the phone can register with Cisco Unified Communications Manager and that licensing consumes device license units for the phone.
•
•
•
•
GUI Changes
No new fields display in Cisco Unified Communications Manager Administration for this feature.
Service Parameter and Enterprise Parameter Changes
No parameter changes exist for this feature.
Installation/Upgrade (Migration) Considerations
After you install Cisco Unified Communications Manager 7.1(2), if auto-registration is not enabled and the phone has not been added to the Cisco Unified Communications Manager database, the phone does not attempt to register with Cisco Unified Communications Manager.
Serviceability Considerations
The Cisco Unified Real-Time Monitoring Tool and Cisco Unified Reporting can display information on registered and unregistered devices. For more information, refer to the Cisco Unified Real-Time Monitoring Tool Administration Guide and the Cisco Unified Reporting Administration Guide.
BAT Considerations
For information on adding devices through BAT, refer to the Cisco Unified Communications Manager Bulk Administration Guide.
CAR/CDR Considerations
No CAR or CDR considerations exist for this feature.
Security Considerations
No security considerations exist for this feature.
AXL and CTI Considerations
No AXL or CTI considerations exist for this feature.
User Tips
If the Configuring IP message displays on the phone, the phone user should contact the phone administrator.
Viewing Held Calls on Shared Lines
Tip
Description
With the held calls on shared lines feature, a phone user can determine whether the call was put on hold by the phone user locally at the primary device or by another party remotely on a shared device. How the held call displays on the devices depends on whether the primary device or shared device puts the call on hold. For information on how the held call displays on the devices, see the "Hold Status" section.
Cisco Unified Communications Manager Administration Configuration Tips and GUI Changes
This feature requires no configuration in Cisco Unified Communications Manager Administration to work. This feature works automatically after you install Cisco Unified Communications Manager 6.1(3) or 7.1(2).
Service Parameter and Enterprise Parameter Changes
This feature requires no configuration in Cisco Unified Communications Manager Administration to work. This feature works automatically after you install Cisco Unified Communications Manager 6.1(3) or 7.1(2).
Installation/Upgrade (Migration) Considerations
After you install Cisco Unified Communications Manager 7.1(2) or upgrade to 7.1(2), you can use this feature.
Serviceability Considerations
No serviceability considerations exist for this feature.
BAT Considerations
No BAT considerations exist for this feature.
CAR/CDR Considerations
No CAR or CDR considerations exist for this feature.
Security Considerations
No security considerations exist for this feature.
AXL and CTI Considerations
No AXL or CTI considerations exist for this feature.
User Tips
For a list of phones that support this feature, see the "Hold Status" section.
For More Information
Security
This section contains information on the following Cisco Unified Communications Manager Administration security features and applications:
•
•
•
CAPF Interaction with IPv6 Addressing
Cisco Unified Communications Manager Business Edition does not support IPv6, so ensure that the phone uses an IPv4 address, so it can connect to CAPF.
For More Information
•
•
SSH Credentials in the Common Device Profile window
Prior to Release 7.1(2), the SSH credentials fields only displayed in the Device Profile window for individual devices. The SSH credentials fields now also display in the Common Device Profile window, so you can set them as part of the common device profile.
For information on AXL support, see the "SSH Userid and Password Configured in the Common Phone Profile" section.
H.235 Pass-Through Support
Description
Cisco Unified Communications Manager allows some types of gateways and trunks to transparently pass through the shared secret (Diffie-Hellman key) and other H.235 data between two H.235 endpoints, so the two endpoints can establish a secure media channel.
To enable the passing through of H.235 data, check the H.235 pass through allowed check box in the configuration settings of the following trunks and gateways:
•
•
•
•
Cisco Unified Communications Manager Administration Configuration Tips
No configuration tips exist for this feature.
GUI Changes
The H.235 pass through allowed check box displays in the configuration window for each type of trunk and gateway that supports H.235 pass-through.
Service Parameter and Enterprise Parameter Changes
No service parameter or enterprise parameter changes exist for this feature.
Installation/Upgrade (Migration) Considerations
No installation or upgrade considerations exist for this feature.
Serviceability Considerations
No serviceability considerations exist for this feature.
BAT Considerations
No BAT considerations exist for this feature.
CAR/CDR Considerations
No CAR/CDR considerations exist for this feature.
Security Considerations
Some types of gateways and trunks can transparently pass through the shared secret (Diffie-Hellman key) and other H.235 data between two H.235 endpoints, so the two endpoints can establish a secure media channel.
AXL and CTI Considerations
See the "H.323 Security: Voice Encryption Profile with Native H.235/H.245 Key Management" section.
User Tips
No user tips exist.
For More Information
•
•
CTL File Size Limitation
The Cisco CTL Client limits the file size of a CTL file to 32 kilobytes because the phones cannot accept a larger CTL file. The following factors affect the size of a CTL file:
•
•
•
Firewalls with TLS Proxy feature act the same as nodes and therefore get included in the CTL file.
•
Because certificates (CAPF/CallManager) that are signed by an external CA are significantly larger than default self-signed certificates, this can limit the maximum number of certificates that can fit into the CTL file.
These factors directly limit the maximum number of certificates that you can fit in a 32-kilobyte CTL file, and therefore they dictate the maximum number of nodes or firewalls that you can have in a secure Cisco Unified Communications Manager deployment.
Security Icons
Description
Cisco Unified Communications Manager provides security status for a call, according to security levels that are configured for the Cisco Unified Communications Manager server(s) and devices that are participating in the call.
Phones that support security icons display the call security level.
•
•
Note
The security status of a call can change for point-to-point, intracluster, intercluster, and multihop calls. SCCP line, SIP line, and H.323 signaling support notification of call security status changes to participating endpoints. If a SIP trunk is involved in a call path, the call session status specifies nonsecure. Refer to Cisco Unified Communications Manager Security Guide for restrictions that are associated with security icons.
The call gets considered as secure only if both the audio and video portions are secure. Table 14 describes the rules that determine whether a security icon displays and which icon displays.
For conference and barge calls, the security icon displays the security status for the conference.
Cisco Unified Communications Manager Administration Configuration Tips
This feature requires no configuration to work.
GUI Changes
No GUI changes exist for this feature.
Service Parameter and Enterprise Parameter Changes
No service parameter or enterprise parameter changes exist for this feature.
Installation/Upgrade (Migration) Considerations
No installation or upgrade considerations exist for this feature.
Serviceability Considerations
No serviceability considerations exist for this feature.
BAT Considerations
No BAT considerations exist for this feature.
CAR/CDR Considerations
No CAR/CDR considerations exist for this feature.
Security Considerations
This feature changes the rules that determine the display of secure icons on secure phones.
AXL and CTI Considerations
No AXL considerations exist for this feature.
User Tips
None
For More Information
•
Cisco Security Agent Version
This release of Cisco Unified Communications Manager includes Cisco Security Agent version 5.2.
Accessing Cisco Security Agent Logs
The CLI command that accesses the log for Cisco Security Agent gets changed to utils create report csa. Refer to the Command Line Interface Reference Guide for Cisco Unified Solutions for more information about starting a CLI session and using CLI commands.
Bulk Administration Tool
This section contains information on the following topics:
•
•
•
•
•
•
Support for Party Entrance Tone
The Bulk Administration GUI includes the following updates to support the party entrance tone feature:
•
–
–
–
Note
•
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
•
–
–
–
•
Support for Log Missed Calls
The Bulk Administration GUI includes the following updates to support the Log Missed Calls feature:
•
Note
•
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
•
–
–
•
•
Support for Always Use Prime Line
The Bulk Administration GUI includes the following updates to support the Always Use Prime Line feature:
•
–
–
–
•
–
–
–
Note
Note
•
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
•
•
•
•
Support for VG202 and VG204 Gateways
BAT now supports VG202 and VG204 gateways. The Bulk Administration Tool includes the following updates to support VG202 and VG204 gateways:
•
•
•
•
•
•
•
Phone Migration in BAT
You can use the Phone Migration feature in Cisco Unified Communications Manager Bulk Administration Tool to migrate phones from one type to another in bulk. You can access the Phone Migration submenu from the Bulk Administration menu of Cisco Unified Communications Manager.
Some limitations that you need to keep in mind when you migrate phones follow:
•
•
•
•
•
You can create a CSV file for phone migration by using one of the following options:
•
•
Migrating Phones
To migrate phones in bulk with the Phone Migration feature in BAT, use the following procedure:
Before You Begin
•
•
•
Procedure
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
To return to the Phone Migration Configuration window without submitting the job, click Cancel;
OR
To continue with submitting the job, click OK.
A message in the Status section lets you know that the job was submitted successfully.
Step 9
Support for Geolocations and Logical Partitioning
BAT supports the logical partitioning feature by enabling geolocation configuration in bulk. The following BAT windows include the Geolocation field:
•
•
New fields That Are Supported for Export by Import/Export
Bulk Administration > Import/Export > Export. The following new fields get supported for export by the Import/Export tool:
System Data
•
•
•
Call Routing Data
•
Support for Seamless Integration (Apply Config)
BAT supports the seamless integration feature by enabling the Apply Config button in the following windows:
•
•
Cisco Unified Serviceability
This section provides information on the following topics:
IPv6 and Serviceability
Cisco Unified Communications Manager Business Edition does not support IPv6.
For More Information
Service Manager Enhancements
The following information describes enhancements for Service Manager.
Starting and Stopping Service States
Cisco Unified Communications Manager 7.1(2) includes two new service states: Starting and Stopping.
When the service state is stopping, a service cannot start. When a service state is starting, a service cannot stop. These states display in the Service Activation window in Cisco Unified Serviceabilityand in the command line interface (CLI).
Disaster Recovery System Enhancements for Service Manager
The Disaster Recovery System backs up the services.conf and servM.conf files. The restore process restores all services to their original forms.
Single Tomcat Session
Instead of creating a new session on the Tomcat manager webapp for every Tomcat request, service manager now creates a single session on the Tomcat manager webapp.
Security Enhancements
Service Manager listens to port 8889 at the local host.
Service Manager Return Codes
Table 15 describes the Service Manager return codes that Release 7.1(2) implements.
Audit Logging
Centralized audit logging ensures that configuration changes to the Cisco Unified Communications Manager system get logged in separate log files for auditing. The following four types of logs get saved to three folders in RTMT:
•
•
•
•
Access the audit logs in RTMT in Trace and Log Central. Go to System > Real-Time Trace > Audit Logs > Nodes. After you select the node, another window displays System > Cisco Audit Logs. The logs get stored in one of the following folders:
•
AuditApp creates one log file until the configured maximum file size is reached; then, it closes and creates a new log file. If the system specifies rotating the log files, AuditApp saves the configured number of files. You can view some of the logging events by using RTMT SyslogViewer.
•
•
For events that get logged, see the "Audit Logs in RTMT" section.
Audit logging contains the following parts:
•
The following example displays an API that a Cisco Unified Communications Manager component can use to send an alarm:
User ID: CCMAdministratorClient IP Address: 172.19.240.207Severity: 3EventType: ServiceStatusUpdatedResourceAccessed: CCMServiceEventStatus: SuccessfulDescription: CallManager Service status is stopped•
–
–
–
–
The following example displays a sample audit event:
CCM_TOMCAT-GENERIC-3-AuditEventGenerated: Audit Event Generated UserID:CCMAdministrator Client IP Address:172.19.240.207 Severity:3 EventType:ServiceStatusUpdated ResourceAccessed: CCMService EventStatus:Successful Description: Call Manager Service status is stopped App ID:Cisco Tomcat Cluster ID:StandAloneCluster Node ID:sa-cm1-3The Cisco Audit Event Service displays in Control Center—Network Services in Cisco Unified Serviceability, so you can start or stop the Audit Log service. To access this service, choose Tools > Control Center—Network Services.
To configure audit logging in Cisco Unified Serviceability, choose Tools > Audit Log Configuration. Use the Audit Log Configuration window to configure the settings for the Cisco Unified Communications Manager application audit logs. For a description of the settings that you can configure for audit log configuration, refer to the Cisco Unified Serviceability Administration Guide.
Tip
For More Information
•
Alarms
Cisco Unified Serviceability contains the following new alarm catalogs:
•
•
The following section contains information on updated and new alarms:
•
•
•
•
•
•
•
Refer to the Cisco Unified Serviceability Administration Guide for information on alarm definitions and for information on how to configure alarms.
kCtiProviderOpenFailure (Updated)
This alarm indicates that the CTI application failed to open provider. Cisco Unified Communications Manager Business Edition does not support IPv6, so the IPv6Address parameter does not apply.
•
•
•
kCtiProviderClosed (Updated)
This alarm indicates that CTI application connection is closed. Cisco Unified Communications Manager Business Edition does not support IPv6, so the IPv6Address parameter does not apply.
•
•
•
kCtiProviderOpened (Updated)
This alarm indicates that the CTI application connection opened. Cisco Unified Communications Manager Business Edition does not support IPv6, so the IPv6Address parameter does not apply.
•
•
•
kCtiIncompatibleProtocolVersion (Updated)
This alarm indicates that the The JTAPI/TAPI application version is not compatible with this version of CTIManager. Cisco Unified Communications Manager Business Edition does not support IPv6, so the IPv6Address parameter does not apply.
•
•
•
DeviceRegistered (Updated)
This alarm indicates that a device successfully registered with Cisco Unified Communications Manager. Cisco Unified Communications Manager Business Edition does not support IPv6, so the IPv6Address parameter and Enum Definitions do not apply.
•
•
•
–
–
–
–
•
–
–
–
–
•
–
–
–
–
DeviceUnregistered (Updated)
This alarm indicates that a device that was previously registered with Cisco Unified Communications Manager unregistered. This event may get issued as part of normal unregistration event or due to some other reason such as loss of keepalives. In cases of normal unregistration, if the Reason Code is CallManagerReset, CallManagerRestart, or DeviceInitiatedReset, the alarm severity gets lowered to Informational (6).
Cisco Unified Communications Manager Business Edition does not support IPv6, so the IPv6Address parameter and Enum Definitions do not apply.
•
•
•
–
–
–
•
–
–
–
–
•
–
–
–
–
DeviceTransientConnection (Updated)
This alarm indicates that a transient connection attempt occurred. A connection got established and immediately dropped before completing registration. Incomplete registration may indicate that a device is rehoming in the middle of registration. The alarm could also indicate a device misconfiguration, database error, or an illegal/unknown device trying to attempt a connection.
Cisco Unified Communications Manager Business Edition does not support IPv6, so the IPv6Address parameter and Enum Definitions do not apply.
•
•
•
–
–
–
•
–
–
–
–
•
–
–
–
–
SIPStarted (Updated)
This alarm indicates that Cisco Unified Communications Manager is ready to handle calls for the indicated SIP device. This alarm does not indicate the current state of the SIP device, only that Cisco Unified Communications Manager is prepared to handle calls to/from the SIP device.
Cisco Unified Communications Manager Business Edition does not support IPv6, so the IPv6Address parameter and Enum Definitions do not apply.
•
•
•
ServiceStarted (Updated)
Cisco Unified Communications Manager Business Edition does not support IPv6, so the IPv6Address parameter and Enum Definitions do not apply.
This alarm indicates that the service started.
•
•
•
AuditEventGenerated (New)
This alarm indicates that the application generated an audit event to the audit log.
•
•
•
–
–
–
–
–
–
–
–
DUPLEX_MISMATCH (New)
This alarm gets generated by Cisco CDP whenever a duplex mismatch occurs between the local interface and switch interface.
•
•
•
–
–
•
DeviceImageDownloadFailure (New)
This alarm gets generated when a Cisco Unified IP Phone failed to download its image.
•
•
•
–
–
–
–
–
–
–
–
•
–
–
–
•
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
•
–
–
–
DeviceImageDownloadStart (New)
Cisco Unified IP Phone has started downloading its image.
•
•
•
–
–
–
–
•
DeviceImageDownloadSuccess (New)
Cisco Unified IP Phone has successfully downloaded its image.
•
•
•
–
–
–
–
–
–
•
DeviceApplyConfigResult (New)
Cisco Unified IP Phone has applied its configuration.
•
•
•
–
–
–
–
–
•
Cisco Unified Cisco Unified Real-Time Monitoring Tool
This section contains these subsections:
•
IPv6 and RTMT
Cisco Unified Communications Manager Business Edition does not support IPv6. If you point RTMT to a Cisco Unified Communications Manager Business Edition 7.1(2) server, the IPv6 settings in RTMT do not apply.
For More Information
•
Performance Monitoring Counters
The following performance monitoring counter updates exist in Cisco Unified Real-Time Monitoring Tool for Cisco Unified Communications Manager 7.1(2):
•
Logical Partitioning
The Cisco Call Restriction counters specify a new group of performance monitoring counters that log the number of failures that result because of logical partitioning policy restrictions. The Cisco Call Restriction counters include the following performance monitoring counters:
•
•
•
•
•
•
•
•
•
IPv6
Cisco Unified Communications Manager Business Edition does not support IPv6, so the counters for the IP6 object do not apply.
Trace and Log Central
This section contains information on the following topics:
•
System History Log Displays in RTMT
Cisco Unified Communications Manager Releases 6.1(3) and 7.1(2) introduce the system history log.
To access the system history log in RTMT, navigate to RTMT Trace Collection:
RTMT > Trace Log Collection
For more information on the system history log, see the "System History Log for Cisco Unified Communications Manager" section.
Audit Logs in RTMT
Tip
With audit logging, any configuration change to the Cisco Unified Communications Manager system gets logged in separate log files for auditing. An audit event represents any event that is required to be logged.
The following events get logged for various components of Cisco Unified Communications Manager Administration:
•
•
•
•
•
Cisco Unified Serviceability logs the following events:
•
•
•
•
•
Cisco Unified Real-Time Monitoring Tool logs the following events with an audit event alarm:
•
•
•
•
•
•
•
•
•
•
Cisco Unified Communications Manager CDR Analysis and Reporting creates audit logs for the following events:
•
•
•
•
•
•
•
•
•
•
•
All audit logs get collected, viewed and deleted from Trace and Log Central in the Cisco Unified Real-Time Monitoring Tool.
Audit logs get written in the common partition. The Log Partition Monitor (LPM) manages the purging of these audit logs as needed, similar to trace files. By default, the LPM purges the audit logs, but the audit user can change this setting from the Audit User Configuration window in Cisco Unified Serviceability. In RTMT, choose Trace and Log Central > Audit Logs.The LPM sends an alert whenever the common partition disk usage exceeds the threshold; however, the alert does not have the information about whether the disk is full because of audit logs or trace files.
Quality Report Tool Reports
A change occurred in the Call State information that is collected from Cisco Unified Communications Manager/CTIManager and displayed in the Quality Report Tool (QRT) reports. Prior to Release 7.1(2), the information included Connected, Connected Conference, Connected Transfer, and On Hook call state information. Now, the report only includes Connected and On Hook call state information.
Cisco Unified Communications Manager CDR Analysis and Reporting
This section contains these subsections:
•
•
Audit Events Get Logged for CAR
Centralized audit logging ensures that a configuration change to the Cisco Unified Communications Manager system gets logged in separate log files for auditing. An audit event represents any event that is required to be logged. For information on the events that get logged for CAR, see the "Audit Logs in RTMT" section.For information about event logging, see the "Audit Logging" section.
Customized Log-on Message
You can upload a text file that contains a customized log-on message that displays in the initial Cisco Unified Communications Manager CDR Analysis and Reporting window.
Upgrade of CAR Data
Be aware that when you upgrade from an earlier version of Cisco Unified Communications Manager to a later version of Cisco Unified Communications Manager, you may not be able to upgrade all your CDR data.
The Cisco Unified Communications Manager installation program limits the time for the migration of the CAR records from the CSV files in the Data Migration Assistant (DMA) TAR file to the CAR database on the upgraded system. The migration time equals 60 minutes. To allow the migration of the highest number of CSV files in the allotted time, CAR record migration uses the following steps:
•
•
If the 60-minute migration time limit occurs at any point in the migration process, CAR data migration ceases, and the tbl_system_preferences of the CAR database gets updated to reflect the data that are present in the upgraded system database.
Backup of CAR Data
The CAR and CDR Disaster Recovery Service (DRS) now integrates into the Cisco Unified Communications Manager DRS. The DRS includes the backup of the CAR database, pregenerated reports, and the CDR preserved flat files.
The CAR Web Service and CAR Scheduler automatically stop before the backup and restore process begins and automatically restart after the backup and restore process completes.
Table 1-16 displays the features and components that the Disaster Recovery System can back up and restore. For each feature that you choose, the system backs up all its components automatically.
Ensure CAR Administrator Privileges Are Restored After Upgrade
When you use DMA to upgrade Cisco Unified Communications Manager, CAR users no longer have CAR administrator privileges after the upgrade and become standard end users. You must reset the CAR administrator privileges after the upgrade. Refer to the "Configuring CAR Administrators, Managers, and Users" section in the CDR Analysis and Reporting Administration Guide for more information on how to configure CAR administrators.
Cisco Unified Communications Manager Call Detail Records
This section contains these subsections:
•
•
•
IPv6 and CDRs
Cisco Unified Communications Manager Business Edition does not support IPv6, so the origIpv4v6Addr and destIpv4v6Addr report IPv4 addresses for Cisco Unified Communications Manager Business Edition do not apply.
H.239 and CDRs
Cisco Unified Communications Manager Release 7.1(2) supports H.239. This feature defines the procedures for the use of up to two video channels in H.320-based systems and for labeling individual channels with a "role" (presentation or live). Requirements exist for processing both the channel and the role of the channel content in the call. Role labels apply to both H.320 and H.245 signaling-based systems.
Table 17 describes the CDR fields that support a second video channel for both the origination and destination devices.
Logical Partitioning
Cisco Unified Communications Manager Release 7.1(2) supports logical partitioning. CDR examples that use logical partitioning get provided for call termination cause code 424 and cause code 503.
New Call Termination Cause Codes
Table 18 describes new Cisco-specific call termination cause codes for logical partitioning.
SIP Calls with URL in callingPartyNumber Field
A new CDR example applies for this situation: an incoming call is received through a SIP trunk by the Cisco Unified Communications Manager. The call contains a SIP URL for the callingPartyNumber CDR field.
GlobalCallId Survives Over Cisco Unified Communications Manager Restarts
For Cisco Unified Communications Manager Release 5.x and later releases, the value in the GlobalCallId CDR field survives over Cisco Unified Communications Manager restarts. In Release 4.x and earlier releases, even though the GlobalCallId field is time-based, the field gets reused under conditions of heavy traffic. Because of this behavior, problems can occur with customer billing applications and the ability of CAR to correlate CMRs with CDRs and to correlate conference call CDRs. For Release 5.x and later releases, GlobalCallId redesign ensures the field retains a unique value, at least for a certain number of days. Now, the last used globalCallId_callId value gets written to disk periodically (for every x number of calls). The value gets retrieved after a Cisco Unified Communications Manager restart, and the new globalCallId_callId value begins with this number plus x.
Cisco Unified Reporting
For a complete description of reports that are available on your system and the data that gets captured in a report, access the Report Descriptions report, as described in the Cisco Unified Reporting Administration Guide.
Table 19 describes the standard reports that display in Cisco Unified Reporting after a Cisco Unified Communications Manager upgrade/installation.
APIs
This section describes the new and changed API features in Cisco Unified Communications Manager Release 7.1(2). It contains the following sections:
•
•
•
•
Cisco Unified TAPI Service Provider (TSP)
This section describes the new and changed features that are supported in TAPI for Cisco Unified Communications Manager Release 7.1(2).
Direct Transfer Across Lines Support
The Direct Transfer Across Lines feature allows the application to directly transfer calls across the lines that are configured on the device. The application must monitor both lines when the calls are directly transferred across lines.
A new LineDevSpecific extension, CciscoLineDevSpecificDirectTransfer, can direct transfer calls across the lines or on the same line. Be aware that Extension 0x00090000 must be negotiated to use CciscoLineDevSpecificDirectTransfer.
Device State Server Support
Device State Server feature provides accumulative State of all the lines on the device. Applications get notified about the device status through PHONE_DEVSPECIFIC and LINE_DEVSPECIFIC Events.
For an application to enable the Device State Server Support, it needs to set the DEVSPECIFIC_DEVICE_STATE and DEVSPECIFIC_DEVICE_STATE_STATUS_ message flag by means of the lineDevSpecific SLDST_SET_STATUS_MESSAGES request and PhoneDevSpecific CPDST_SET_DEVICE_STATUS_MESSAGES request, respectively.
TAPI will provide notification of the device state of the device to its applications through PHONE_DEVSPECIFIC and LINE_DEVSPECIFIC events.
The possible device states that are delivered to an application from TSP include ACTIVE, ALERTING, HELP, WHISPER, and IDLE.
Drop-Any-Party Support
The Drop-Any-Party feature enables the application to drop any call from the ad hoc conference. This feature currently gets supported from the phone interface. The application uses the LineRemoveFromConference function to drop the call from a conference. When the call is dropped from a conference, the TSP receives CtiDropConferee as the call state change cause, and this gets sent to TAPI as the default cause.
Logical Partitioning Support
The Logical Partitioning feature restricts VoIP to PSTN calls, and vice versa, based on the logical partitioning policy. Any request that interconnects a VOIP call to a PSTN call, or vice versa, in two different geographical locations fails, and the error code gets sent back to the applications.
The device, device pool, trunk, and gateway windows now provide configuration to select geolocation values and construction rules for geolocation strings.
A new enterprise parameter for this feature includes the following values:
•
•
•
This release adds the following error code for this feature: LINEERR_INVALID_CALL_PARTITIONING_POLICY 0xC000000C
Cisco Unified JTAPI
This section describes the new and changed features that are supported in JTAPI for Cisco Unified Communications Manager Release 7.1(2).
Drop Any Party
This feature provides the capability to drop any participants from a conference call. JTAPI allows applications to drop participants from conference by using the existing interface Connection.disconnect() even if the application is not observing the address for the connection. Previously, applications could only disconnect connections for which Address is an observed Address.
Feature behavior varies based on the settings for the Unified CM service parameter Advanced Ad Hoc Conference Enabled. If this service parameter is set to False, applications can drop connections for an unobserved address in a conference call only if the application observes the conference controller address. If this parameter is set to True, applications can drop connections without any restriction.
JTAPI provides an interface on CiscoConnection to get an array of CiscoPartyInfo objects for the connection. CiscoPartyInfo gets used to disconnect participants from a conference by using a new interface, disconnect(), that is provided on CiscoConnection. A normal line includes only one CiscoPartyInfo on its connection, but a shared-line has one CiscoPartyInfo for each line in the shared-line. This enables applications to selectively disconnect a shared line participant if more than one shared line participants is in the conference call. Because shared line participants have only one connection, if the application uses the existing Connection.disconnect() API, it drops all the shared line participants.
JTAPI provides an interface setDropAnyPartyEnabled() on CiscoJtapiProperties to enable or disable this feature and by default, it stays enabled. Alternatively, applications can have the JTAPI ini parameter dropAnyPartyEnabled=0 in jtapi.ini file to disable Drop Any Party feature and dropAnyPartyEnable=1 to enable this feature. If dropAnyPartyEnable parameter is not present in jtapi.ini file, the feature stays enabled by default.
JTAPI also provides an interface, isConferenceCall(), on CiscoCall to determine whether a call is a conference call. This simple method returns a Boolean result.
Direct Transfer Across Lines
The Direct Transfer Across Lines feature allows support for transfer across lines. It allows two calls on different addresses of the same terminal to be transferred though the Transfer softkey on the phone or transfer() API that is provided by JTAPI and Transfer softkey on certain newer phones. When a transfer is done across lines, the behavior to JTAPI applications changes, as applications do not see a common controller address in final and consult calls. No change occurs in the API, and the same events get delivered whether calls are transferred on the same address (regular transfer) or across addresses (Direct Tx across lines). This feature gets supported on all supported phones - including CTI port, SCCP devices, and SIP devices.
If observer is not added on either of the two addresses across which Transfer is being attempted from JTAPI API, JTAPI throws PlatformException with error: Transfer controller does not get set and could not find a suitable TerminalConnection.
Join Across Lines or Connected Conference Across Lines
User experience gets enhanced in Cisco Unified Communications Manager Release 7.1(2) by introducing new phones that fall outside the purview of existing Join Across Lines feature always Enabled without any service parameter. For these devices, the features remains Enabled to turn it off.
Enhanced MWI
The Enhanced MWI feature allows applications to provide the following message counts to be displayed on phones that support the enhanced message waiting counts:
•
•
•
•
•
•
•
•
Two new added APIs as CiscoAddress JTAPI extensions provide the enhanced MWI message summary information. Similar to the existing setMessageWaiting APIs, one API allows you to set the summary information for the observed address. The other API allows you to set message summary information on any address that is reachable on the observed address, as defined by the configured calling search space of the observed address.
These new APIs can also get used on phone types that do not support the enhanced message counts. If used on non-supported phones, these APIs behave similar to the existing setMessageWaiting method; that is, only the messaging waiting indicator lamp gets turned on or off, and counts do not display.
Logical Partitioning
This feature allows administrators to configure geographical locations and restrict calls that pass through a PSTN gateway to be connected directly to a VoIP phone or VoIP PSTN gateway in another geographic location. This feature allows using single-line analog phones and remains complaint with Telecom Regulatory Authority of India (TRAI) regulation.
You can turn off this feature by using the Logical Partitioning Enabled service parameter, and the feature stays disabled by default.
Component Updater
ComponentUpdater interface gets enhanced to allow applications to specify the location of updater log. Currently updater log gets created in the same directory as the application. This enhancement allows applications to specify the trace location.
Skinny Client Control Protocol (SCCP)
Enhanced Message Waiting Indication Data
The enhanced Enhanced Message Waiting (MWI) data comprise voice and fax counts. This feature enables a voice mail server to report urgent and nonurgent voice mail and fax counts to the Cisco Unified Communications Manager. The Cisco Unified Communications Manager in turn sends the enhanced MWI data to the respective client.
Two new messages get defined. One message gets sent by the voice mail server to notify the Cisco Unified Communications Manager of the MWI data. The other message gets sent by the Cisco Unified Communications Manager in response and indicates whether the notification was successful.
H.264 Video Channel Negotiation
Because the earlier versions of the SCCP specifications were unclear about certain aspects of H.264 negotiation such as sending and receiving of frame rates below the advertised level, Release 7.1(2) added new guidelines for clients and servers to follow.
IP to IP Gateway Support
A new field that is added to the StationOpenReceiveChannelMessage carries the audio level (gain/loss) for the requested audio stream. Only the IP-IP [IOS] gateway utilizes this field.
Deprecation of Messages
StationUpdateCapabilitiesMessage and StationUpdateCapabilitiesVersion2Message get deprecated because these messages represent a subset of UpdateCapabilitiesV3Message. Therefore, clients that are compliant to SCCPv18 specification must use UpdateCapabilitiesV3Message instead. Table 1-20 lists the skinny messages that are added, modified, and deleted for Release 7.1(2).
Administrative XML (AXL) Programming
This section describes the changes that occur in Cisco Unified Communications Manager Administrative XML (AXL) APIs to support the new and updated features for the Cisco Unified Communications Manager Release 7.1(2).
H.323 Security: Voice Encryption Profile with Native H.235/H.245 Key Management
The H.235 security recommendation feature in Unified CM 7.1(2) supports the Diffie-Hellman key exchange mechanism for media encryption in a H.323 network by using procedures that are recommended in the H.235.6 Voice encryption profile with native H.235/H.245 key management standard. This feature allows the Cisco Unified Communications Manager to transparently pass the shared secret (Diffie-Hellman key) and other H.235 data between two H.235 endpoints, so the two endpoints can establish a secure media channel.
To support this feature, the following changes occurred in the AXL API:
Logical Partitioning
Cisco Unified Communications Manager Release 7.1(2) supports logical partitioning. The logical partitioning feature restricts VoIP to PSTN calls, and vice versa, based on the logical partitioning policy. Any request that interconnects a VOIP call to a PSTN call, or vice versa, in two different geographical locations fails, and the error code gets sent back to the applications.
QSIG variant Per Trunk or Gateway
A Q.SIG variant that is selectable by trunk or gateway feature allows you to configure QSIG variants on a per trunk/gateway basis.
To support this feature, the following changes occurred in the AXL API:
Enhancements to Calling Party Number Transformations
The Calling Party Number (CPN) enhancement feature enhances Cisco Unified Communications Manager system capability to provide accurate calling party number information to the phones. Cisco Unified CM DB/Administrator gets enhanced to allow configuration of transformation CSS for each calling party number type (National, International, Unknown, Subscriber) on the gateway, trunk, and device pool configuration windows. This gives Cisco Unified CM the ability to conditionally transform the calling party number based on the number type. Also, an option that is provided in Cisco Unified CM administrator allows you to configure Number of Digits to Strip for each number type in addition to the already available Prefix fields. This replaces the colon (:) notation that was added in earlier releases. You can do this only at the device/device-pool level. At the service parameter level, the existing colon (:) notation remains.
Barge Enhancement Feature
Party Entrance Tone configuration gets provided on a per-line basis. This Party Entrance Tone gets used for barge, cBarge, ad hoc conference, join, and meet-me conference.
To support this feature, an optional parameter, partyEntranceTone, now exists in the Line (add/update/get) API.
Enhanced Clear Channel (G.clear) Support
The enhanced Clear Channel feature enhances sRTP support for a Clear Channel (G.Clear) data call between MGCP, SIP line, and SIP trunk. H323 endpoint does not get included in this feature.
Prior to this feature, Cisco Unified Communications Manager only supported non-secured G.Clear call. G.Clear call over SIP interface requires early offer. For MGCP-to-SIP interoperability, no sRTP key gets provided to exchange for early offer call. With this feature, the RSVP layer generates a fake key for the SDP in the outgoing INVITE if this is sRTP call for G.Clear early offer call.
To support this feature, an optional parameter, gClear, now exists in the SIPProfile (add/update/get) API.
Always Use Prime Line
The Always Use Prime line feature enables a user to always answer on prime line upon off hook. The Always Use Prime Line for voice message capability enables user to always access a voice message on prime line when messages button is pressed. This feature previously got supported at the system level. Current enhancement provides control at the device level, which enables the individual device/user to control.
To support this feature, the following changes occurred in the AXL API:
SSH Userid and Password Configured in the Common Phone Profile
Before Release 7.1(2), you configured SSH credentials in the device window, and that made it time-consuming to configure credentials for a large number of phones. This feature enables configuring once in the Common Phone Profile that enables SSH credentials in a group of phones.
To support this feature, Release 7.1(2) adds a new API, CommonPhoneConfig (add/update/get), with the following optional parameters:
•
•
Serviceability XML Programming
This section describes the changes that were made in the Cisco Unified Communications Manager Serviceability APIs to support the new and updated features for Cisco Unified Communications Manager Release 7.1(2).
Seamless Upgrade
Seamless Upgrade represents the ability of phones to download a new firmware image in the background while phones remain in service.
To support this feature, the Serviceability APIs optionally provide the following information per device:
•
•
•
•
•
Cisco Unified IP Phones
This section provides information for the following features:
•
•
•
•
•
•
•
Cisco Unified IP Phone 6900 Series
The Cisco Unified IP Phone 6900 Series is a new and innovative portfolio of endpoints that deliver affordable, business-grade, voice communication services to customers worldwide. Three models are available:
•
•
•
All three models support the following features:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
–
–
–
For more information, click the following URL:
http://www.cisco.com/en/US/prod/collateral/voicesw/ps6788/phones/ps10326/data_sheet_c78-541199.html
Requirements
The Cisco Unified IP Phone 6900 Series requires the following release:
•
Where to Find More Information
•
•
•
•
Enterprise Phone Configuration Window
The Enterprise Phone Configuration window (System > Enterprise Phone Configuration) for Cisco Unified Communications Manager Release 7.1(2) supports only the Cisco Unified IP Phones 6921, 6941, and 6961, and only the Join and Direct Transfer Policy parameter is supported.
For information about the Join and Direct Transfer Policy parameter, see the "Join and Direct Transfer Policy Configuration Parameter" section.
Join and Direct Transfer Policy Configuration Parameter
Cisco Unified IP Phone firmware release 8.5(2) allows you to disable the Join and Direct Transfer Policy parameter in Cisco Unified Communications Manager Administration (System > Enterprise Phone Configuration) for the following IP phones:
•
•
•
Because some JTAPI and TAPI applications are not compatible with the join and direct transfer features, for these applications to control and monitor the Cisco Unified IP Phones 6921, 6941, and 6961, you may need to disable join and direct transfer on the same line and possibly across lines. Refer to the documentation of the JTAPI or TAPI application(s) that you are running.
Where to Find More Information
•
•
Barge Tone Enhancements
Be aware that the Party Entrance Tone configuration is available as a per-line setting, in addition to a service parameter setting for Cisco Unified CM administrators. The default value for the line setting specifies the service parameter setting. The Party Entrance Tone setting gets applied to barge, cBarge, join, ad hoc, and meet-me conferences. For more information, see the "Party Entrance Tone" section.
Barge and cBarge support the interaction with Private Line Automatic Ringdown (PLAR). When a shared line has PLAR configured, a user can Barge or cBarge into a call that is connected on the shared PLAR line.
These Barge Tone enhancements get supported on the following phones that are running SIP and SCCP:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Where to Find More Information
•
•
•
Cisco Unified IP Phone Support HTTPS
Cisco Unified IP Phones can securely access the web with the use of a phone trust store that is called "phone-trust." Administrators can upload certificates to a phone-trust store by using the Cisco Unified Communications Manager Operating System GUI. The Cisco Unified IP Phone will display a menu option called "Application Server" for each phone-trust store whose certificates have been uploaded into Cisco Unified OS Administration and later downloaded into the Cisco Unified IP Phone CTL file.
The phone-trust certificates and secure HTTPS web access get supported on the following phones that are running SIP and SCCP:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Where to Find More Information
•
•
•
Hold Status
Cisco Unified Communications Manager 6.1(3) and 7.1(2) introduced the following enhancements to hold status:
•
•
The hold status enhancement gets supported on the following phones that are running SIP and SCCP:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Where to Find More Information
•
•
•
Internet Protocol Version 6 on the Cisco Unified IP Phone
Cisco Unified Communications Manager Business Edition does not support IPv6, so ensure that the phone obtains an IPv4 address.
Line Select
Cisco Unified Communications Manager 6.1(3) and 7.1(2) introduced settings to determine whether the primary line gets automatically selected when a call is answered or when the Messages button gets pressed. You can configure these settings for all phones in the system, or for a single phone.
•
•
Note
These enhancements get supported on the following phones that are running SCCP or SIP:
•
•
•
•
•
•
•
•
•
•
•
•
Where to Find More Information
•
•
•
Missed Calls
The Missed Calls feature allows the phone administrator to specify whether missed calls will get logged in the missed calls directory for a given line appearance. The following properties apply to the missed calls feature:
•
•
•
•
•
•
•
•
In addition to these properties, the following properties continue to apply to all calls:
•
•
The missed calls feature gets supported on the following phones that are running SCCP or SIP:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Where to Find More Information
•
•
Off-Hook Abbreviated Dialing
Cisco Unified Communications Manager Release 7.1(2) introduces the Off-Hook Abbreviated Dialing feature. The user can initiate off-hook abbreviated dialing while user is conferencing a call, while user is transferring a call, or while user is placing a new call after putting a call on hold.
Cisco Unified Communications Manager Configuration Tips
•
The Off-Hook Abbreviated Dialing feature gets supported on the following phones that are running SCCP or SIP:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
For More Information
•
•
•
•
•
Restrict Unconfigured Phone Registration
In Cisco Unified Communications Manager releases other than 6.1(3) and 7.1(2), if a Cisco Unified IP Phone had not been added to the Cisco Unified Communications Manager database and did not have autoregistration enabled, the phone would repeatedly attempt to register (unsuccessfully) with Cisco Unified Communications Manager, thus continually notifying Cisco Unified Communications Manager with these repeated registration requests.
With Cisco Unified Communications Manager Releases 6.1(3) and 7.1(2), if autoregistration is not enabled and the phone has not been added to the Cisco Unified Communications Manager database, the phone does not attempt to register with Cisco Unified Communications Manager. The phone continues to display the "Configuring IP" message until autoregistration is enabled or until the phone has been added to the Cisco Unified Communications Manager database.
The registration behavior gets supported on the following devices or phones that are running SIP or SCCP:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Where to Find More Information
•
•
Secure Icon
Cisco Unified Communications Manager Release 7.1(2) uses a different method to calculate which Security icon to send to Cisco Unified IP Phones. Prior to release 7.1(2), the audio stream that was involved in a call or conference provided the sole basis for the type of security icon that Cisco Unified Communications Manager sent to phones. However, in Cisco Unified Communications Manager Release 7.1(2), Cisco Unified Communications Manager calculates which security icon to display based on both audio and video (if applicable) streams, and sends the resulting security icon to the Cisco Unified IP Phone.
All media that are involved in the call must be secure for the Lock (Encrypted) icon to display on the phone. For example, if the audio is encrypted but the video is not encrypted, the security icon that displays does not represent the Lock (Encrypted) icon because the call as a whole is not encrypted. Instead, the Shield (Authenticated) icon, if one exists for the given phone model, displays on the phone. For phones that do not support Shield icons, these phones will not display any security icon for an Authenticated call or conference.
For a table that shows which type of security icon to expect for various call scenarios, refer to the Cisco Unified Communications Manager Security Guide, "Security Icons" section.
New Behavior for Secure-Tone Feature
In releases prior to Cisco Unified Communications Manager Release 7.1(2), a security tone would play to indicate that a call was "protected," which meant that two phones on a call were configured for Protected mode and that the phones were receiving and transmitting encrypted audio. Beginning with Cisco Unified Communications Manager Release 7.1(2), if a video stream is also involved in the call, the security tone will play only if both phones are receiving and transmitting encrypted video as well as encrypted audio.
The secure icon feature gets supported on the following phones that run SCCP or SIP:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
For More Information
•
•
Cisco Web Dialer Enhancements
Cisco Unified Communications Manager supports the following Cisco Web Dialer enhancements:
•
For more information on this topic, see the "Cisco Web Dialer Configured in Application Server Window" section.
•
•
•
•
Calling <Username if available> at <dial-out number>
If authorization codes are required, enter them now
The Cisco Web Dialer enhancements get supported on the following phones that are running SIP or SCCP:
•
•
•
•
•
•
•
•
•
•
•
•
Where to Find More Information
•
Table 24 lists Cisco Unified IP Phones that support new Cisco Unified Communications Manager features.
Cisco Unified CM User Options
See the following sections for enhancements to the Cisco Unified CM User Options:
•
•
Caveats
The following sections contain information on how to obtain the latest resolved caveat information and descriptions of open caveats of severity levels 1, 2, and 3.
Caveats describe unexpected behavior on a Cisco Unified Communications server. Severity 1 caveats represent the most serious caveats, severity 2 caveats represent less serious caveats, and severity 3 caveats represent moderate caveats.
Resolved Caveats
You can find the latest resolved caveat information for Cisco Unified Communications Manager Release 7.1 by using Bug Toolkit, which is an online tool that is available for customers to query defects according to their own needs.
Tip
To access the Bug Toolkit, log on to http://tools.cisco.com/Support/BugToolKit.
UsingBug Toolkit
The system grades known problems (bugs) according to severity level. These release notes contain descriptions of the following bug levels:
•
•
You can search for problems by using the Cisco Software Bug Toolkit.
To access Bug Toolkit, you need the following items:
•
•
•
To use the Software Bug Toolkit, follow these steps:
Procedure
Step 1
Step 2
Step 3
Tip
Open Caveats
Open Caveats for Cisco Unified Communications Manager Release 7.1(2) As of May 27, 2009 describe possible unexpected behaviors in Cisco Unified Communications Manager Release 7.1, which are sorted by component.
Tip
Understanding the Fixed-in Version Field in the Online Defect Record
When you open the online record for a defect, you will see data in the "First Fixed-in Version" field. The information that displays in this field identifies the list of Cisco Unified Communications Manager interim versions in which the defect was fixed. These interim versions then get integrated into Cisco Unified Communications Manager releases.
Some more clearly defined versions include identification for Engineering Specials (ES) or Service Releases (SR); for example 03.3(04)ES29 and 04.0(02a)SR1. However, the version information that displays for the Cisco Unified Communications Manager maintenance releases may not be as clearly identified.
The following examples show how you can decode the maintenance release interim version information. These examples show you the format of the interim version along with the corresponding Cisco Unified Communications Manager release that includes that interim version. You can use these examples as guidance to better understand the presentation of information in these fields.
•
•
•
•
•
•
Note
Tip
Open Caveats for Cisco Unified Communications Manager Release 7.1(2) As of May 27, 2009
The following information comprises unexpected behavior (as of May 27, 2009) that you may encounter in Release 7.1(2) of Cisco Unified Communications Manager.
BPS BAT
•
CAR
•
•
CM Serviceability
•
CMCTI
•
•
•
•
•
•
CMUI
•
•
•
•
•
•
•
CP-CAC
•
CP-ChangeNotify
•
CP-H323
•
•
CP-LineControl
•
CP-MediaControl
•
•
•
•
•
•
•
CP-PRI
•
CP-SCCP
•
CP-SIP Trunk
•
•
CP-System
•
•
CPI AppInstall
•
CPI Diagnose
•
CPI OS
•
•
•
•
CPI Platform API
•
•
CPI Security
•
•
•
Database
•
•
•
•
Database IDS
•
JTAPI SDK
•
•
•
•
RISDC
•
RTMT
•
Voice SIPstack
•
Documentation Updates
This section contains information on documentation omissions, errors, and updates for the following Release 7.1(2) documentation:
•
•
•
•
Cisco Unified Communication Manager CDR Analysis and Reporting
This section contains information on documentation omissions, errors and updates for the CDR Analysis and Reporting Administration Guide.
•
•
Purpose of Cisco Unified Communications Manager CDR Analysis and Reporting
The CDR Analysis and Reporting Administration Guide omits the following statement about the primary purpose of the Cisco Unified Communications Manager CDR Analysis and Reporting (CAR) software:
CAR is not intended to replace call accounting and billing solutions that third-party companies provide. You can find the companies that provide these solutions and that are members of the Cisco Technology Developer Program by searching the home page of the Cisco Developer Community at this URL: http://developer.cisco.com/web/cdc/home.
The following online document has been revised to include the omitted statement:
•
chapter: CDR Analysis and Reporting Overview"Mailing a Report" Recipients
The "Mailing a Report" chapter in the CDR Analysis and Reporting Administration Guide omits this information:
When the Mailing option gets enabled,
•
•
•
Cisco Unified Communications Manager Security
This section contains information on documentation omissions, errors and updates for the Cisco Unified Communications Manager Security Guide.
•
•
Definition of Locally Significant Certificate
The definition of Locally Significant Certificate (LSC) in the Cisco Unified Communications Manager Security Guide need correction as follows: A third-party certificate authority (CA) cannot issue an LSC. An LSC represents a digital X.509v3 certificate that CAPF issues. It gets installed on a phone or JTAPI/TAPI/CTI application.
Using Certificates Issued by a Third-Party Certificate Authority
This information supplements the documentation about using certificates that are issued by a third-party certificate authority (CA) that is in the Cisco Unified Communications Operating System Administration Guide.
•
•
•
–
X509v3 extensions:X509v3 Key Usage:Digital Signature, Certificate SignX509v3 Extended Key Usage:TLS Web Server Authentication, IPSec End System–
X509v3 Key Usage:Digital Signature, Key Encipherment, Data Encipherment, Key AgreementX509v3 Extended Key Usage:TLS Web Server Authentication, TLS Web Client Authentication, IPSec End System•
•
•
Cisco Unified Communications Operating System
This section contains information on documentation omissions, errors, and updates for the Cisco Unified Communications Operating System Administration Guide.
•
•
Guidelines for Installing COP Files
The following guidelines apply to installing COP files. If the documentation for a specific COP file contradicts these general guidelines, follow the COP file documentation:
•
•
This restart ensures that configuration changes that are made during the COP file installation get written into the database. Cisco recommends that you perform this restart during an off-peak period.
Disk Space Before Upgrading
Before you upgrade to Cisco Unified Communications Manager from supported appliance releases, make sure that you have enough disk space on the common partition to perform the upgrade. To ensure that you have enough disk space, determine the size of the ISO file on your DVD or on Cisco.com. If you are upgrading from a local source (DVD), you need the same amount of disk space as the size of the ISO file. If you are upgrading from a network source, you need twice the amount of disk space as the size of the combined ISO file.
To verify the disk space on the common partition, do one of the following tasks:
•
•
•
If you do not have enough disk space, use Cisco Unified Real-Time Monitoring Tool to collect core and trace files and delete them from the server. For more information on collecting files, refer to the Cisco Unified Real-Time Monitoring Tool Administration Guide.
You can also use the log partition monitoring service or the command line interface (CLI) to delete files on your server; however, Cisco does not recommend using these tools to delete files during regular business hours, as they can impact system performance. For more information on configuring log partition monitoring, see the Cisco Unified Real-Time Monitoring Tool Administration Guide. For more information on the CLI, see the Command Line Interface Reference Guide for Cisco Unified Communications Solutions.
Note
Pre-Upgrade Task Is Omitted From Software Upgrades Chapter
The "Software Upgrades" chapter in the Cisco Unified Communications Operating System Administration Guide omits the following pre-upgrade task:
Before you perform the Cisco Unified Communications Manager 7.1(2) upgrade, ensure that the device name for the Cisco Unified Mobile Communicator device contains 15 or fewer characters. If the device name contains more than 15 characters for the Cisco Unified Mobile Communicator, the device does not migrate during the upgrade.
Cisco Unified Communications Manager Administration
This section contains information on documentation omissions, errors, and updates for the Cisco Unified Communications Manager Administration Guide, Cisco Unified Communications Manager Features and Services Guide, and the Cisco Unified Communications Manager System Guide.
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Administrator Can Set User Credential Policy to Expire Without Making a Global Policy Change
The Credential Settings and Fields section of the "End User Configuration" chapter in the Cisco Unified Communications Manager Administration Guide incorrectly includes the following information:
For example, if the policy has the Never Expires check box checked, you cannot uncheck and save the Does Not Expire check box in the user Credential Configuration window. You can, however, set a different credential expiration for the user, including Does Not Expire, if the Never Expires policy setting is not checked; the user setting overrides the policy setting.
And, again, regarding the Does Not Expire checkbox:
You cannot uncheck this check box if the policy setting specifies Never Expires.
For releases above 6.1(3), this is not true. An administrator can set a user credential policy to expire without making a global policy change.
Number of Digits Field Description is Incorrect
The Application Dial Rules Configuration Error Checking section of the Dial Rules Overview chapter of the Cisco Unified Communications Manager System Guide mis-states information about the Number of Digits field.
The correct information follows:
The Number of Digits field supports digits between 1 and 100, as well as the plus sign (+), the asterisk (*), and the number sign (#). Enter the number of digits of the dialed numbers to which you want to apply this application dial rule. You cannot allow this field to be blank for a dial rule.
Number of Locations and Regions That Cisco Unified Communications Manager Supports
The Cisco Unified Communications Manager Administration documentation incorrectly states the number of locations and regions that Cisco Unified Communications Manager supports. The correct limits follow:
•
•
The following online documents have been revised with the correct limits:
•
chapter: Location Configuration•
chapter: Region Configuration•
chapter: System-Level Configuration SettingsIntercom Route Partition Configuration Settings Description Field Information Is Incorrect
The Intercom Route Partition Configuration Settings description field in the Configuring Intercom chapter of the Cisco Unified Communications Manager Administration Guide omits a complete list of the non-alphanumeric characters that are not allowed in the description. The unacceptable characters comprise double-quotes ("), angle brackets (<>), square bracket ([ ]), ampersand (&), and percentage sign (%).
Mobile Connect Support Restrictions
The "Cisco Unified Mobility" chapter of the Cisco Unified Communications Manager Features and Services Guide omits the following restriction:
The Mobile Connect feature gets supported only for Primary Rate Interface (PRI) public switched telephone network (PSTN) connections.
For SIP trunks, Mobile Connect gets supported via IOS gateways or intercluster trunks.
Configuring an H.323 Gateway for System Remote Access by Using Hairpinning
The "Cisco Unified Mobility" chapter of the Cisco Unified Communications Manager Features and Services Guide omits the following (final) step in the "Configuring an H.323 Gateway for System Remote Access by Using Hairpinning" procedure:
Step 5
Enterprise Feature Access Two-Stage Dialing
The "Cisco Unified Mobility" chapter of the Cisco Unified Communications Manager Features and Services Guide omits the following (final) steps in the "Enterprise Feature Access Two-Stage Dialing" procedure:
Step 8
Step 9
Note
Refer to the Cisco Unified Communications Solution Reference Network Design (SRND) Based on Cisco Unified Communications Manager for the list of steps that you need to configure Enterprise Feature Access.
Valid Characters in Name Field of Access List Configuration Window
In the Cisco Unified Communications Manager Features and Services Guide, be aware that the description for the Name field in the Access List Configuration window in the "Cisco Unified Mobility" chapter is incomplete. The complete description follows:
Enter a text name for the access list.
This name can comprise up to 50 characters. You can use all characters except quotes ("), close angle bracket (>), open angle bracket (<), backslash (\), ampersand (&), and percent sign (%).
Valid Characters in Name Field of Role Configuration Window
In the Cisco Unified Communications Manager Administration Guide, be aware that the description for the Name field in the Role Configuration window in the "Role Configuration" chapter is incomplete. The complete description follows:
Enter a name for the role. Roles can comprise up to 128 characters.
Valid characters include letters, numbers, dashes, dots (periods), spaces, and underscores.
Valid Characters in Name and Description Fields of Remote Destination Profile Window
In the Cisco Unified Communications Manager Features and Services Guide, be aware that the description for the Name and Description fields on the Remote Destination Profile Configuration window in the "Cisco Unified Mobility" chapter is incomplete. The complete descriptions follow.
Name
Enter a text name for the remote destination profile.
This name can comprise up to 50 characters. Valid characters include letters, numbers, dashes, dots (periods), spaces, and underscores.
Description
Enter a text description of the remote destination profile.
This field can comprise up to 128 characters. You can use all characters except quotes ("), close angle bracket (>), open angle bracket (<), backslash (\), ampersand (&), and percent sign (%).
Valid Characters in Name Field of Geolocation Filter Configuration Window
In the Cisco Unified Communications Manager Features and Services Guide, be aware that the description for the Name field in the Geolocation Filter Configuration window in the "Geolocations" chapter is incomplete. The complete description follows:
Enter a unique name for this geolocation filter. Default name cannot be blank.
This field can contain up to 50 ASCII characters. You can use all characters except quotes ("), close angle bracket (>), open angle bracket (<), backslash (\), ampersand (&), and percent sign (%).
Valid Characters in Name Field of Geolocation Configuration Window
In the Cisco Unified Communications Manager Features and Services Guide, the description for the Name field in the Geolocation Configuration window in the "Geolocations" chapter is incomplete. The complete description follows:
Enter a unique name for this geolocation.
The name can contain up to 50 ASCII characters. You can use all characters except quotes ("), close angle bracket (>), open angle bracket (<), backslash (\), ampersand (&), and percent sign (%).
Directory Number Chapter Includes Incorrect Information on Alerting Name and Display Name Fields
The "Directory Number Configuration" chapter in the Cisco Unified Communications Manager Administration Guide incorrectly describes the Alerting Name field. In addition, The chapter does not describe the relationship between the Alerting Name field and Display (Internal Caller ID) field.
Incorrect Information
For the Alerting Name field, enter a name that you want to display on the phone of the caller.
This setting, which supports the Identification Services for the QSIG protocol, applies to shared and nonshared directory numbers. If you configure an alerting name for a directory number with shared-line appearances, when the phone rings at the terminating PINX, the system performs the following tasks:
•
•
If you do not configure an alerting name, "Name Not Available" may display on the caller phone. If you do not enter a name for the Display (Internal Caller ID) field, the information in the Alerting Name field displays in the Display (Internal Caller ID) field.
Setting the Always Display Original Dialed Number service parameter to True impacts the alerting name functionality. If you set the service parameter to True, the alerting name does not display on the calling phone; only the original dialed number displays.
Correct Information
For the Alerting Name field, enter a name that you want to display on the phone of the caller when the called phone is ringing.
This setting, which supports the Identification Services for the QSIG protocol, applies to shared and nonshared directory numbers. When the phone rings at the terminating PINX, if you configured an alerting name for a directory number with shared-line appearances, the system performs the following tasks:
•
•
Depending on the state of the call and your configuration, the alerting name, directory number, or display (internal caller ID) configuration may display on the phone, as described in the following bullets.
•
•
•
Setting the Always Display Original Dialed Number service parameter to True impacts the alerting name functionality. If you set the service parameter to True, the original dialed number and the alerting name displays during the call.
End User Chapter Includes Incorrect Information for Manager User ID Field
The "End User Configuration" chapter in the Cisco Unified Communications Manager Administration Guide incorrectly describes the Manager User ID field.
Incorrect Description
For the Manager User ID field, enter the user ID of the end user manager ID. The manager user ID that you enter must already exist in the directory as an end user.
Correct Description
For the Manager User ID field, enter the user ID of the end user manager ID..Intercom Calls Cannot Be Placed on Hold
The Restrictions section of the "Intercom" chapter in the Cisco Unified Communications Manager Features and Services Guide incorrectly indicates that intercom calls can be placed on hold. Actually, intercom calls cannot be placed on hold.
Device Pool Configuration Chapter Does Not State That You Can Enter -1 in the Connection Monitor Duration Field
The "Device Pool Configuration" chapter in the Cisco Unified Communications Manager Administration Guide does not state that, for the Connection Monitor Duration field, you can enter -1 or leave the field blank to use the configuration for the enterprise parameter. When you configure the Connection Monitor Duration field in the Device Pool Configuration window, use the following information:
This setting defines the time that the Cisco Unified IP Phone monitors its connection to Cisco Unified Communications Manager before it unregisters from SRST and reregisters to Cisco Unified Communications Manager.
To use the configuration for the enterprise parameter, you can enter -1 or leave the field blank. The default value for the enterprise parameter equals 120 seconds.
Change this setting if you need to disable the connection monitor or if you want to extend the connection monitor time. The maximum number of seconds that you can enter in the field equals 2592000.
Tip
Trunk Configuration Chapter Does Not State That You Can Enter Hostname in Destination Address Field
The "Trunk Configuration' chapter in the Cisco Unified Communications Manager Administration Guide does not state that you can enter a hostname in the Destination Address field, which supports SIP trunks. Use the following information when you configure the Destination Address field:
The Destination Address represents the remote SIP peer with which this trunk will communicate. The allowed values for this field specify a valid V4 dotted IP address, a hostname, a fully qualified domain name (FQDN), or DNS SRV record only if the Destination Address is an SRV field is checked.
SIP trunks only accept incoming requests from the configured Destination Address and the specified incoming port that is specified in the SIP Trunk Security Profile that is associated with this trunk.
For configuring SIP trunks when you have multiple device pools in a cluster, you must configure a destination address that is a DNS SRV destination port. Enter the name of a DNS SRV port for the Destination Address and check the Destination Address is an SRV Destination Port check box.
If the remote end is a Cisco Unified Communications Manager cluster, DNS SRV represents the recommended choice for this field. The DNS SRV record should include all Cisco Unified Communications Managers within the cluster.
Cisco Unified Communications Manager Does Not Support Logical Partitioning for Cisco Unified MeetingPlace and Cisco Unified MeetingPlace Express Calls
Cisco Unified Communications Manager does not support the logical partitioning feature for calls that involve Cisco Unified MeetingPlace or Cisco Unified MeetingPlace Express.
The following document omits this limitation:
•
chapter: Logical Partitioning
topic: LimitationsLicensing Chapter Does Not State That You Should Use Microsoft Outlook to Receive Licenses
The "Licensing" chapter in the Cisco Unified Communications Manager System Guide does not state that Cisco recommends that you use Microsoft Outlook when you receive Cisco Unified Communications Manager licenses. For more information on this topic, see the "Use Microsoft Outlook to Receive Cisco Unified Communications Manager Licenses" section.
Cisco Unified Communications Manager Does Not Support Logical Partitioning for Cisco Unified MeetingPlace and Cisco Unified MeetingPlace Express Calls
Cisco Unified Communications Manager does not support the logical partitioning feature for calls that involve Cisco Unified MeetingPlace or Cisco Unified MeetingPlace Express.
The following document omits this limitation:
•
chapter: Logical Partitioning
topic: LimitationsDevice Name of Cisco Unified Mobile Communicator Must Not Exceed 15 Characters
The description of the Device Name field on the "Phone Configuration" chapter omits the following note:
Note
Mobile Voice Access Directory Number Field Description
In the "Cisco Unified Mobility" chapter of the Cisco Unified Communications Manager Features and Services Guide, the description of the Mobile Voice Access Directory Number field on the Mobile Voice Access window omits the following information:
Enter a value between 1 and 24 digits in length. You may use the following characters: 0 to 9.
Recording Destination Address Field Description
In the "Recording Profile Configuration" chapter of the Cisco Unified Communications Manager Administration Guide, the description of the Recording Destination Address field on the Recording Profile Configuration window omits the following information:
This field allows any characters except the following characters: double quotation marks ("), back quote (`), and space ( ).
OpenLDAP Version 2.3.41 Not Listed in LDAP Synchronization Documentation
The "Understanding the Directory" chapter in the Cisco Unified Communications Manager System Guide does not state the version of OpenLDAP that is supported for LDAP Synchronization with Cisco Unified Communications Manager Release 7.1(2). To identify the supported version, see the OpenLDAP 2.3.41 Can Synchronize with Cisco Unified Communications Manager Database.
Do Not Begin Starting and Ending Directory Numbers with a Zero (0)
In Table 3 of the "Cisco Unified Communications Manager Configuration" chapter, under Auto-registration Information, the descriptions of Starting Directory Number and Ending Directory Number omit the information that neither number should begin with a zero (0).
Time-of-Day Routing Chapter Omits Information About Defined Time Periods
The "Time-of-Day Routing" chapter of the Cisco Unified Communications Manager System Guide omits the following information.
•
Example:
Consider the following example:
•
•
In this case, on December 31st, the afterofficehours period will not be considered because it gets overriden by the more specific newyearseve period.
Changed Values of Mobility Cell Pick
The Mobility section of "CDR Examples" chapter in Cisco Unified Communications Manager - Call Detail Records Administration Guide has wrong values for some field names. The corrected values follow:
Cisco Unified Serviceability
This section contains information on documentation omissions, errors, and updates for Cisco Unified Serviceability.
Password Description Omitted
The Application Billing Server Parameter Settings table in "Configuring CDR Repository Manager" chapter of the Cisco Unified Communications Manager Serviceability Guide omits this information:
Password - Enter the password that is used to access the application billing server.
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop by using a reader application. Be aware that the RSS feeds are a free service, and Cisco currently supports RSS version 2.0.
CCDE, CCSI, CCENT, Cisco Eos, Cisco HealthPresence, the Cisco logo, Cisco Lumin, Cisco Nexus, Cisco Nurse Connect, Cisco Stackpower, Cisco StadiumVision, Cisco TelePresence, Cisco WebEx, DCE, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn and Cisco Store are service marks; and Access Registrar, Aironet, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, EtherFast, EtherSwitch, Event Center, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, iQuick Study, IronPort, the IronPort logo, LightStream, Linksys, MediaTone, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerPanels, ProConnect, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0903R)
Feedback