Table Of Contents
Release Notes for Cisco Unified Communications Manager Release 6.1(1b)
Upgrade Paths To Cisco Unified Communications Manager 6.1(1b)
Out of Service Nodes and Cisco License Manager
Reset the Cluster After You Change the Security Password
Best Practices for Assigning Roles to Serviceability Administrators
For Serviceability, the Administrator That is Created During Installation Must Not Be Removed
Clarification for Call Park Configuration
Connecting to Third-Party Voice Messaging Systems
Resetting Database Replication When Reverting To an Older Product Release
utils dbreplication clusterreset
utils dbreplication dropadmindb
User Account Control Pop-up Window Displays During Installation of RTMT
CiscoTSP Limitations on Windows Vista Platform
Time Required for Disk Mirroring
Cisco Unified Mobility Supports Nine Locales
Each Remote Destination Supports a Maximum of Two Active Calls
Changes to Cisco Extension Mobility After Upgrade
RTMT Requirement When Cisco Unified Communications Manager Is Upgraded
Changes to Cisco Extension Mobility After Upgrade
Serviceability Session Timeout Not Graceful
Updating the IP Address in the Server Configuration Window
Deleting Then Adding Back a Server in Cisco Unified Communications Manager Administration
SIP Network/IP Address Field Required for SIP Fallback to SRST Gateway
Cisco Unified Reporting Application
New and Changed Information in Cisco Unified Communications Manager 6.1(1x)
Basic Uninterruptible Power Supply (UPS) Integration
New Service Parameters Added to Extension Mobility
Disaster Recovery Manual Backup Window
Cisco Unified Communications Operating System CLI Commands
utils dbreplication clusterreset
utils dbreplication dropadmindb
utils dbreplication setrepltimeout
Installation, Upgrade, Migration, and Disaster Recovery
Where to Find More Information
Cisco Unified Communications Operating System Administration
Where to Find More Information
Cisco Unified Communications Manager Administration
Browser Requirements for Cisco Unified Communications Manager Administration
Service Parameter and Enterprise Parameter Changes
Where to Find More Information
Cisco Unified Communications Manager Features and Applications
Cisco Unified Communications Manager Assistant
Intercom for Cisco Extension Mobility
Licensing for Cisco Unified Mobility
Phone Button Template, Line, and Security Enhancements for the Nokia S60 Device
Cisco Unified Communications Manager Bulk Administration Tool
Database Summary Includes Database Replication Information
New Preconfigured Alerts in Cisco Unified Serviceability
Adding RTMT Performance Counters in Bulk
RTMT Trace and Log Central Disk IO and CPU Throttling
CDR Analysis and Reporting Tool/Call Detail Record (CAR/CDR)
CAR System Scheduler Default Status
Automatically Generated Reports
Tbl_pregenmail_option Table Data
Calculation of the Utilization of H.323 Gateways
CDR Search Reports Display Time in Two Ways
CAR Scheduler Now a Network Service
Cisco Unified Communications Manager User Options
Cisco Unified IP Phone 7965G and 7945G
Cisco Unified IP Phone 7962G and 7942G
Cisco Unified IP Conference Station 7937G
Intercom with Cisco Extension Mobility
Cisco Unified IP Phone Support for Cisco Unified Communications Manager 6.1 Features
Cisco Unified Communications Manager Configuration XML
Cisco Unified Communications Manager Serviceability XML
Disaster Recovery Manual Backup Checkbox
set network dhcp eth0 disable Command Parameters
Remote Support Account Duration
Documentation Does Not State That Line Group With No Members Is Not Supported for Routing Calls
Cisco Unified IP Phones Supporting Call Back with PLKs
Number of Login or Logout Operations That Cisco Extension Mobility Supports
DNS Required for RTMT Alerts by E-mail
Minimum Memory Requirement for RTMT Client
RTMT Trace and Log Central Disk IO and CPU Throttling
Primary User Device Field on the Update Users Window in BAT
Single Button Barge (new field)—Phone Template Configuration Window in BAT
Join Across Lines (new field)—Phone Template Configuration Window in BAT
Single Button Barge (new field)—UDP Template configuration Window in BAT
Join Across Lines (new field)—UDP Template configuration Window in BAT
None Option Not Documented for DND Incoming Call Alert Setting
Attendant Console Phones Do Not Support the Intercom Feature
CTI Devices Do Not Support Multicast Music on Hold (MOH)
Cisco Unified IP Phone Administration Guides (7905G, 7912G, 7921G)
Configuring a Custom Background Image
Perfmon Log File—Maximum File Size Default Value
Path for Accessing Cisco Unified Reporting
Upgrade Procedure Contains Incorrect Information
Application Server Configuration Not Required for Cisco Unity Connection 2.x
Incorrect Documentation on How to Delete Parameter for Phone Service
Call Admission Control Bandwidth Example Correction
Barge with Shared Conference Bridge
Adding an Administrator User to Cisco Unity or Cisco Unity Connection
Number of Alphanumeric Characters Allowed in the Pickup Group Name Field
Incorrect Information on How to Install Assistant Console Application
Documentation Does Not Include the Latest List of Supported Phone Models
Perfmon Log File—Maximum File Size Default Value
Path for Accessing Cisco Unified Reporting
Do Not Disturb Documentation Provides Incorrect Information About Phone Tone
Incorrect Description for User ID Field in Application User Window
RSVP Reservation Teardown for Shared-Line Calls
Destination Number in Remote Destination Configuration Window
Updated List of Fields Supported for Export by the Import/Export Tool
SNMP Traps and Informs Correction
Unclear Documentation on How Locales Work for Mobile Voice Access
Warning Displays When Enabling SIP Stack Trace
Cisco Unified Communications Manager XML Developers Guide for Release 6.0(1)
Recovering Administrator and Security Passwords
Logging In To the Web Interface When the Firewall Is Disabled
Unclear Documentation on Called Party Name Presentation
Misleading Documentation About Creating Cisco Unity and Cisco Unity Connection Voice Mailboxes
Cisco Unified IP Phone User Guides
Using Cisco Extension Mobility
Cisco Extension Mobility Supplemental Information
Cisco Unified IP Phones Supporting Barge
Cisco Unified IP Phones Supporting Call Back
Extension Mobility Successful Authentication Cache
Software Conference Bridge Not Supported
Do Not Disturb Feature Priority
Warning Displays When SIP Stack Trace Is Enabled
Digital Certificate Key Length Restrictions
Third-Party Certificate Authority Verification
Recommended Number of Devices in Device Pool
Support for Certificates from External CAs
CAPF System Interactions and Requirements
Peer-to-Peer Image Distribution
Devices Associated with the Attendant Console Application User
Obtaining Documentation and Submitting a Service Request
Release Notes for Cisco Unified Communications Manager Release 6.1(1b)
June 10, 2008
This document contains information that existed in the Cisco Unified Communications Manager Releases 6.1(1), 6.1(1a) and the "For Release 6.1(1b)" information indicated in Table 1.
.
These release notes describe the caveats that release 6.1(1a) and 6.1(1b) resolve as well as the new features and caveats for Cisco Unified Communications Manager Release 6.1(1x). 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
Summary of Cisco Unified Communications Manager Release 6.1(1b)
The following noncomprehensive list gives the caveats that were resolved in this release of Unified CM:
1.
CSCsm37017 - Prior to this release, when you configured traces in the serviceability window, no CCMUser option existed, which meant that you could not change the default CCMuser trace level.
2.
CSCso11097 - Prior to this release, when you upgraded from Release 6.0 to 6.1, a corruption of the RAID controller firmware on a MCS-7845-I2 server existed. After the reboot that the upgrade required, the restart failed with an error:
"ATTENTION: The Firmware image in the controller is corrupted!! Please run the Firmware Update Utility from the OS to update the firmware. Error code: 86"
3.
CSCso53771 - According to Cisco Security, several products in the Cisco Unified Communications family of products contained a command execution vulnerability in the Disaster Recovery Framework (DRF) feature. A remote, unauthenticated user could exploit this vulnerability to execute arbitrary commands that may allow full administrative access to affected systems.
4.
CSCso45910 - Prior to this release, after an upgrade, the server would not boot to the new partition.
5.
CSCsm47603 - Prior to this release, the BIOS that is bundled with Release 6.1 did not support the E6400 processor that IBM put into their 7825I3 servers, and the BIOS got downrevved to the unsupported version during install/upgrade.
6.
CSCsl31392 - Prior to this release, in DMA messages intended to identify problems in the user data could be misinterpreted as logging errors. Even if the user correctly identified the problem, the required user action was not evident. Release 6.1(1b) includes expanded explanations for five additional error cases DMA. The resulting user visible error messages provide a better understanding of cause and resolution.
•
CSCsm15075 In 6.1(1), when you click the Find button an Access Denied error got generated on systems with more than 250 gateways and/or route lists provisioned. In 6.1(1a) permissions were changed to allow the Find and List window to be loaded from the Route Pattern window.
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
To ensure continuous operation and optimal performance of your Cisco Unified Communications Manager system, you must upgrade to Cisco Unified Communications Manager 6.1(1a).
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 "Upgrading System Software" section.
Contents
These release notes discuss the following topics:
•
Upgrade Paths To Cisco Unified Communications Manager 6.1(1b)
•
New and Changed Information in Cisco Unified Communications Manager 6.1(1x)
–
Open Caveats as of April 7, 2008
•
Obtaining Documentation and Submitting a Service Request
Introduction
Cisco Unified Communications Manager, the call-processing component of the Cisco Unified Communications System, extends enterprise telephony features and capabilities to IP phones, media processing devices, voice-over-IP (VoIP) gateways, mobile devices, and multimedia applications.
System Requirements
Server Support
Make sure that you install and configure Cisco Unified Communications Manager Release 6.1(1b) on a Cisco Media Convergence Server (MCS) or a Cisco-approved HP server configuration or a Cisco-approved IBM server configuration.
To find which servers support the Cisco Unified Communications Manager Release 6.1(1b), refer to the Cisco Unified Communications Manager Server Support Matrix at http://www.cisco.com/en/US/partner/products/hw/voiceapp/ps378/prod_brochure_list.html.
Note
Make sure that the matrix indicates that your server model supports Cisco Unified Communications Manager Release 6.1(1b).
Note
Some servers that are listed in the compatibility matrix may require additional hardware support for Cisco Unified Communications Manager Release 6.1(1b). Make sure that your server meets the minimum hardware requirements, as indicated in the footnotes of the compatibility matrix. Cisco Unified Communications Manager requires a minimum of 2 GB of memory, 72 GB disk drive, and 2 GHz processor.
To see which MCS server is compatible with Cisco Unified Communications Manager Release 6.1(1b), refer to http://www.cisco.com/en/US/products/hw/voiceapp/ps378/prod_models_home.html.
To find which servers support the Cisco Unified Communications Manager Release 6.1(1b), refer to the Cisco Unified Communications Manager Server Support Matrix at http://www.cisco.com/en/US/partner/products/hw/voiceapp/ps378/prod_brochure_list.html
Uninterruptible Power Supply
Ensure that you connect each Cisco Unified Communications Manager node to an uninterruptible power supply (UPS) to provide backup power and protect your system.
CautionFailure to connect the Cisco Unified Communication Manager nodes to a UPS may result in damage to physical media and require a new installation of Cisco Unified Communications Manager.
Upgrading System Software
Before you upgrade the software version of Cisco Unified Communications Manager, verify your current software version.
To do that, open Cisco Unified Communications Manager Administration. The following information displays:
•
Cisco Unified Communications Manager System version
•
Cisco Unified Communications Manager Administration version
Upgrade Paths To Cisco Unified Communications Manager 6.1(1b)
It is possible to upgrade directly to Cisco Unified Communications Manager 6.1(1b) from:
•
4.1(3x)
•
4.2(3x)
•
5.1(1x)
•
5.1(2x)
•
5.1(3x)
•
6.0(1x)
•
6.1(1x)
CautionUse the iso files mentioned in the "Upgrading from Cisco Unified Communications Manager Release 6.0(1a) or 6.1(1a) to Release 6.1(1b) Using the UCSInstall File" section for upgrades from 6.0(1a) or 6.1(1a) to 6.1(1b) only.
Upgrading from CUCM 4.x and 5.x
If you are upgrading from 4.1.3, 4.2.3, 5.1.1, 5.1.2, or 5.1.3, use the Product Upgrade Tool (PUT) or the PUT for registered customers only to obtain a media kit and license or purchase the upgrade from Cisco Sales.
To use the PUT, you are required to enter your Cisco Software Application Support Plus Upgrades (SASU) contract number and request the CD/CD set. If you do not have a SASU contract, you must purchase the upgrade from Cisco Sales.
For more information about supported Unified CM upgrades, see the Cisco Unified Communications Manager Compatibility Matrix at the following URL:
http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_device_support_tables_list.html
Upgrading from Cisco Unified Communications Manager Release 6.0(1a) or 6.1(1a) to Release 6.1(1b) Using the UCSInstall File
CautionDo not use the following information to upgrade from any Unified CM release other than 6.0(1a) or 6.1(1a).
Because of its size, the UCSInstall iso file, UCSInstall_UCOS_6.1.1.2000-3.sgn.iso, has been divided into two parts:
•
UCSInstall_UCOS_6.1.1.3000-2.sgn.iso_part1of2
–
MD5 value specifies 1e47a96d3b89b8e1dfcefef3e8cdaa3a
•
UCSInstall_UCOS_6.1.1.3000-2.sgn.iso_part2of2
–
MD5 value specified 885c93ae61d75978646ced37d25a791a)
Procedure
Step 1
From www.cisco.com, download the two UCSInstall files.
Step 2
Execute one of the following commands to reunite the two parts of the file.
Note
The 6.1.1.3000-2 build is a non-bootable ISO which is only useful for upgrades. It cannot be used for new installations.
a.
If you have a Unix/Linux system, cut and paste the following command from this document into the CLI to combine the two parts:
cat UCSInstall_UCOS_6.1.1.3000-2.sgn.iso_part1of2 UCSInstall_UCOS_6.1.1.3000-2.sgn.iso_part2of2 > UCSInstall_UCOS_6.1.1.3000-2.sgn.iso
b.
If you have a Windows system, cut and paste the following command from this document into the command prompt (cmd.exe) to combine the two parts:
COPY /B UCSInstall_UCOS_6.1.1.3000-2.sgn.iso_part1of2+UCSInstall_UCOS_6.1.1.3000-2.sgn.iso_part2of2 UCSInstall_UCOS_6.1.1.3000-2.sgn.iso
Step 3
Use an md5sum utility to verify that the MD5 sum of the final file is correct.
38ea200efd06fb6bb8c0515fd852aadb UCSInstall_UCOS_6.1.1.3000-2.sgn.iso
Software Download URLs
You can access the latest software upgrades for Cisco Unified Communications Manager 6.1 on Cisco.com. Table 2 lists the URLs from which you download the software.
Table 2 Download URLs for Software Upgrades
Software Download URLCisco Unified Communications Manager 6.1(1a)
Locale installers
http://www.cisco.com/kobayashi/sw-center/telephony/callmgr/locale-installer.shtml
Phone firmware
http://www.cisco.com/pcgi-bin/tablebuild.pl/ip-7900ser
http://www.cisco.com/pcgi-bin/tablebuild.pl/ip-7900ser-crypto
Cisco Security Agent (CSA)
Upgrade Assistant
http://www.cisco.com/pcgi-bin/tablebuild.pl/callmgr-utilpage
Related Documentation
The documentation that supports Cisco Unified Communications Manager Release 6.1 resides at
http://www.cisco.com/en/US/products/sw/voicesw/ps556/tsd_products_support_series_home.htmlLimitations and Restrictions
A recommendation of compatible software releases that have been verified by the test for customers represents a major deliverable of the Cisco Unified Communications System testing. The recommendations, which are not exclusive, represent an addition to interoperability recommendations for each individual voice application or voice infrastructure product.
For a list of software and firmware versions of IP telephony components that were tested for interoperability with Cisco Unified Communications Manager 6.1 as part of Unified Communications System Release 6.1 testing, see http://www.cisco.com/go/unified-techinfo.
For a list of software and firmware versions of contact center components that were tested for interoperability with Cisco Unified Communications Manager 6.1 as part of Unified Communications System Release 6.1 testing, see http://tools.cisco.com/ITDIT/vtgsca/.
Be aware that the release of Cisco IP telephony products does not always coincide with Cisco Unified Communications Manager releases. If a product does not meet the compatibility testing requirements with Cisco Unified Communications Manager, you need to wait until a compatible version of the product becomes available before you can upgrade to Cisco Unified Communications Manager 6.1(1a). For the most current compatibility combinations and defects that are associated with other Cisco Unified Communications products, refer to the documentation that is associated with those products.
Important Notes
The following section contains important information that may have been unavailable upon the initial release of documentation for Cisco Unified Communications Manager Release 6.1(1x).
•
Out of Service Nodes and Cisco License Manager
•
Reset the Cluster After You Change the Security Password
•
Best Practices for Assigning Roles to Serviceability Administrators
•
For Serviceability, the Administrator That is Created During Installation Must Not Be Removed
•
Clarification for Call Park Configuration
•
Connecting to Third-Party Voice Messaging Systems
•
Upgrade Paths To Cisco Unified Communications Manager 6.1(1b)
•
Resetting Database Replication When Reverting To an Older Product Release
•
User Account Control Pop-up Window Displays During Installation of RTMT
•
CiscoTSP Limitations on Windows Vista Platform
•
Time Required for Disk Mirroring
•
Cisco Unified Mobility Supports Nine Locales
•
Each Remote Destination Supports a Maximum of Two Active Calls
•
Changes to Cisco Extension Mobility After Upgrade
•
RTMT Requirement When Cisco Unified Communications Manager Is Upgraded
•
Changes to Cisco Extension Mobility After Upgrade
•
Serviceability Session Timeout Not Graceful
•
Updating the IP Address in the Server Configuration Window
•
Deleting Then Adding Back a Server in Cisco Unified Communications Manager Administration
•
SIP Network/IP Address Field Required for SIP Fallback to SRST Gateway
•
Cisco Unified Reporting Application
Cisco Recommendations
Cisco offers the following recommendations.
Installation Note
Do not install Cisco Unified Communications Manager in a large Class A or Class B subnet that contains a large number of devices. When you install Cisco Unified Communications Manager in a large subnet with a large number devices in that subnet, the Address Resolution Protocol (ARP) table can fill up quickly (maximum 1024 entries, by default).
When the ARP table gets full, Cisco Unified Communications Manager can have difficulty talking to endpoints and cannot add more phones.
Out of Service Nodes and Cisco License Manager
Symptom
After an upgrade from Cisco Unified CallManager Release 5.1.2 to Cisco Unified Communications Manager 6.1(1), apply the 6.x software license. Restart CUCM services on all nodes. Cisco Unified Communications Manager and all services start, except Cisco License Manager. Attempts to manually restart Cisco License Manager are not successful.
Workaround
If dummy nodes exist in the cluster, you should map the IP addresses of the dummy nodes to the hostnames in the DNS server. If you do not Cisco Unified Communications Manager generates alarms that the License Manager service is down.
Reset the Cluster After You Change the Security Password
Servers in a cluster use the Security password to authenticate communication between servers.
To change the Security password, use the set password security CLI command or reset the password from the console.
Step 1
Change the security password on the publisher server (first node) and then reboot the server (node).
Step 2
Change the security password on all the subsequent servers/nodes to the password created in Step 1 and restart subsequent nodes, including application servers, to propagate the password change.
Note
Cisco recommends that you restart each server after the password is changed on that server.
Note
Failure to reboot the servers (nodes) causes system service problems and problems with the Cisco Unified Communications Manager Administration windows on the subscriber servers.
Best Practices for Assigning Roles to Serviceability Administrators
Cisco recommends that you configure application users, rather than end users, to access remote nodes to perform such tasks as starting and stopping services. Starting and stopping services requires that the Standard SERVICEABILITY Administration and Standard RealtimeAndTraceCollection roles be assigned.
For Serviceability, the Administrator That is Created During Installation Must Not Be Removed
Removing the Administrator that is created during installation or upgrade can cause communication with remote nodes via Serviceability Administration to fail.
Clarification for Call Park Configuration
Consider the following information when you configure Call Park:
Call Park numbers cannot overlap between Cisco Unified Communications Manager servers. Ensure that each Cisco Unified Communications Manager server has its own unique number range.
Call Park numbers may have an associated partition that restricts access to the Call Park numbers and prevents retrieval of parked calls. If partitions are used to restrict access to Call Park numbers, a unique call park number or range of call park extension numbers must be defined for each partition on each Cisco Unified Communications Manager in the cluster.
When the end user invokes Call Park, Cisco Unified Communications Manager attempts to find an available Call Park number from a Call Park partition that is currently accessible via the calling search space for the party that invoked Call Park.
Connecting to Third-Party Voice Messaging Systems
Administrators can connect third-party voice-messaging systems to Cisco Unified Communications Manager. Ensure the voice-messaging system has a simplified message desk interface (SMDI) that is accessible with a null-modem EIA/TIA-232 cable (and an available serial port). To connect the EIA/TIA-232 cable to Cisco Unified Communications Manager Release 5.0 or later, use a Cisco certified serial-to-USB adapter with the part number USB-SERIAL-CA=.
Resetting Database Replication When Reverting To an Older Product Release
If you revert the servers in a cluster to run an older product release, you must manually reset database replication within the cluster. To reset database replication after you revert all the cluster servers to the older product release, enter the CLI command utils dbreplication reset all on the publisher server.
When you switch versions by using Cisco Unified Communications Operating System Administration or the CLI, you get a message reminding you about the requirement to reset database replication if you are reverting to an older product release. This behavior is also documented in the caveats CSCsl57629 and CSCsl57655.
utils dbreplication clusterreset
This command resets database replication on an entire cluster.
Command Syntax
utils dbreplication clusterreset
Usage Guidelines
Before you run this command, run the command utils dbreplication stop first on all subscribers servers, and then on the publisher server.
Requirements
Command privilege level: 0
Allowed during upgrade: Yes
utils dbreplication dropadmindb
This command drops the Informix syscdr database on any server in the cluster.
Command Syntax
utils dbreplication dropadmindb
Usage Guidelines
You should run this command only if database replication reset or cluster reset fails and replication cannot be restarted.
Requirements
Command privilege level: 0
Allowed during upgrade: Yes
User Account Control Pop-up Window Displays During Installation of RTMT
When you install RTMT on the Microsoft Vista platform, the system displays the User Account Control pop-up window to indicate that an unidentified program wants access to your computer. This occurs because of a limitation in the InstallAnywhere software. This one-time pop-up displays only when installing RTMT. Select Allow to continue.
CiscoTSP Limitations on Windows Vista Platform
Always perform the first-time installation of the CiscoTSP and Cisco Unified Communications Manager TSP Wave Driver on a Vista machine as a fresh install.
If secure connection to Cisco Unified Communications Manager is to be used, turn off the Windows firewall.
If Cisco Unified Communications Manager TSP Wave Driver is used for inbound audio streaming, turn off the Windows firewall.
If Cisco Unified Communications Manager TSP Wave Driver is used for audio streaming, disable all other devices in the "Sound, video and game controllers" group.
Time Required for Disk Mirroring
Disk mirroring on server model 7825 I3 with 160 GB SATA disk drives takes approximately 3 hours.
Disk mirroring on server model 7828 I3 with 250 GB SATA disk drives takes approximately 4 hours.
Cisco Unified Mobility Supports Nine Locales
Cisco Unified Mobility (Mobile Connect and Mobile Voice Access) support a maximum of nine locales, so Cisco Unified Communications Manager Administration blocks you from configuring 10 or more locales for Cisco Unified Mobility. In the Mobility Configuration window, more than nine locales can display in the Available Locales pane if they are installed for Cisco Unified Communications Manager, but you can only save nine locales in the Selected Locales pane. If you attempt to configure more than nine locales for Cisco Unified Mobility, the following error message displays: "Update failed. Check constraint (informix.cc_ivruserlocale_orderindex) failed."
Each Remote Destination Supports a Maximum of Two Active Calls
For Cisco Unified Mobility, each remote destination supports a maximum of two active calls via Cisco Unified Communications Manager. Using the enterprise feature access directory number (DID number) to transfer or conference with DTMF counts as one call. When a Cisco Unified Mobility user receives a call while the user has two active calls for the remote destination or while the user is using DTMF to transfer/conference a call from the remote destination, the received call does not reach the remote destination and instead goes to the enterprise voice mail; that is, if Call Forward No Answer (CFNA) is configured or if the call is not answered on a shared line.
Changes to Cisco Extension Mobility After Upgrade
If you chose a user created profile from the Log Out Profile drop-down list on the Phone Configuration window and checked the Enable Extension Mobility check box, the settings in that profile become the permanent settings on the phone after an upgrade from Cisco Unified CallManager 4.x or Cisco Unified Communications Manager 5.x to Cisco Unified Communications Manager 6.1(1a).
RTMT Requirement When Cisco Unified Communications Manager Is Upgraded
If you are running the Cisco Unified Communications Real-Time Monitoring Tool (RTMT) client and monitoring performance counters during a Cisco Unified Communications Manager upgrade, the performance counters will not update during and after the upgrade. To continue monitoring performance counters accurately after the upgrade completes, you must either reload the RTMT profile or restart the RTMT client.
Changes to Cisco Extension Mobility After Upgrade
If you chose a user created profile from the Log Out Profile drop-down list on the Phone Configuration window and checked the Enable Extension Mobility check box, the settings in that profile become the permanent settings on the phone after an upgrade from Cisco Unified CallManager 4.x or Cisco Unified Communications Manager 5.x to Cisco Unified Communications Manager 6.1(1a).
Serviceability Session Timeout Not Graceful
When a session has been idle for more than 30 minutes, the Cisco Unified Serviceability user interface allows you to make changes before indicating that the session has timed out and redirecting you to the login window. After you log in again, you may have to repeat those changes. This behavior occurs in the Alarm, Trace, Service Activation, Control Center, and SNMP windows.
Workaround
If you know that the session has been idle for more than 30 minutes, log out using the Logout button before making any changes in the user interface.
Problem Configuring Mobility Identity for Nokia S60 Device in Cisco Unified Communications Manager Administration
The following error message may display in the Phone Configuration window in Cisco Unified Communications Manager Administration when you try to configure Mobility Identity for the Nokia S60 device: "Add failed. [10102] Check the type of device specified in fkDevice_DualMode. Remote Destionations other than Dual Mode must use fkDevice_RemoteDestinationTemplate."
The error occurs under one of the following circumstances:
•
Circumstance 1—You provisioned Nokia S60 devices by using the pre-6.1(1a) Nokia S60 .cop file before or after you upgraded to Cisco Unified Communications Manager 6.1(1a). After you installed the latest 6.1(1a) compatible Nokia S60 .cop file, you tried to configure Mobility Identity for an existing Nokia S60 device in the Phone Configuration window in Cisco Unified Communications Manager Administration.
•
Circumstance 2- Previously, you provisioned Nokia S60 devices by using the pre-6.1(1a) Nokia S60 .cop file. Then, you installed the latest 6.1(1a) compatible Nokia S60 .cop file. After the latest .cop file was installed, you tried to configure Mobility Identity for an existing Nokia S60 device in the Phone Configuration window in Cisco Unified Communications Manager Administration.
If the error message displays, you can perform the following tasks to ensure that you can configure Mobility Identity for the Nokia S60 device:
1.
In Cisco Unified Communications Manager Administration 6.1, disable auto-registration.
2.
In the Find/List Phone window in Cisco Unified Communications Manager Administration, delete all Nokia S60 records.
Tip
In case of large number of existing Nokia devices, Cisco recommends that you delete the Nokia S60 records by using the Bulk Administration Tool by choosing Bulk Administration > Phones > Delete Phones
3.
In Cisco Unified Communications Manager Administration, configure all Nokia S60 devices by choosing Device > Phone > Add New > Nokia S60.
Tip
For a large number of Nokia S60 devices, you can provision the devices in the Bulk Administration Tool by choosing Bulk Administration > Phones > Insert Phones.
4.
Reset all Nokia S60 devices.
Updating the IP Address in the Server Configuration Window
Before you change the IP address of a server in the Server Configuration window in Cisco Unified Communications Manager Administration, consider the following information:
•
Cisco Unified Communications Manager Administration does not prevent you from updating the IP Address field under any circumstances.
•
When you attempt to change the IP address in the Server Configuration window, the following message displays after you save the configuration: "Changing the host name/IP Address of the server may cause problems with Cisco Unified Communications Manager. Are you sure that you want to continue?" Before you click OK, make sure that you understand the implications of updating this field; for example, updating this setting incorrectly may cause Cisco Unified Communications Manager to become inoperable; that is, the database may not work, you may not be able to access Cisco Unified Communications Manager Administration, and so on. In addition, updating this field without performing other related tasks may cause problems for Cisco Unified Communications Manager.
•
For additional information on changing IP addresses for Cisco Unified Communications Manager, refer to the following URL:
http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_tech_note09186a0080094601.shtml
Serviceability Limitations
When you modify the IP Address field, you cannot access the RTMT profiles, custom counters, custom alerts, and generic queries for Trace & Log Collection Tool (TLC) for that server.
You should manually remove any RTMT profiles, custom counters, custom alerts, and generic queries for Trace and Log Collection Tool (TLC) that were set for the old IP Address. When you modify the IP Address field, you will need to re-create the RTMT profile, custom counters, custom alerts, and generic queries for TLC the next time that you log in to the server on RTMT.
Cisco AMC Service service includes two user-configurable service parameters, Primary Collector and Failover Collector. These service parameters use Host Name/IP Address to designate the primary and failover AMC server. If you change the IP address of the AMC primary collector or failover collector, you should check these service parameters and update them accordingly.
Cisco Serviceability Reporter service includes one user-configurable service parameter, RTMT Reporter Designated Node. This service parameter uses Host Name/IP Address to designate the node on which RTMTReporter runs. If you changed the IP address of the RTMT Reporter Designated Node, you should check this service parameter and update it accordingly.
Deleting Then Adding Back a Server in Cisco Unified Communications Manager Administration
In Cisco Unified Communications Manager Administration, you cannot delete the first node of the cluster, but you can delete subsequent nodes. Before you delete a subsequent node in the Find and List Servers window, Cisco Unified Communications Manager Administration displays the following message: "You are about to permanently delete one or more servers. This action cannot be undone. Continue?". If you click OK, the server gets deleted from the Cisco Unified Communications Manager database and is not available for use.
Tip
When you attempt to delete a server from the Server Configuration window, a similar message as the one in the preceding paragraph displays. If you click OK, the server gets deleted from the Cisco Unified Communications Manager database and is not available for use.
If you delete a subsequent node (subscriber) from Cisco Unified Communications Manager Administration and you want to add it back to the cluster, perform the following procedure:
Tip
Before you perform the procedure, review the information in the "Deleting a Server" section, which provides important considerations on deleting a server.
Procedure
Step 1
In Cisco Unified Communications Manager Administration, add the server, as described in the "Configuring a Server" section (Server Configuration chapter) in the Cisco Unified Communications Manager Administration Guide.
Step 2
After you add the subsequent node to Cisco Unified Communications Manager Administration, perform a 6.1(1a) installation on it by using the 6.1(1a) disk that Cisco provided in your software kit.
Tip
Make sure that the version that you install on the subsequent node matches the version that runs on the first node (publisher) in the cluster.
If the first node in the cluster runs 6.1(1a) and a service release (or engineering special), you must choose the Upgrade During Install option when the installation displays the installation options; before you choose this option, ensure that you can access the service release (or engineering special) image on DVD or a remote server. For more information on how to perform an installation, refer to Installing Cisco Unified Communications Manager 6.1(1).Step 3
After you install Cisco Unified Communications Manager, configure the subsequent node, as described in the "Configuring a Subsequent Node" section in the document, Installing Cisco Unified Communications Manager 6.1(1).
SIP Network/IP Address Field Required for SIP Fallback to SRST Gateway
Although Cisco Unified Communications Manager Administration does not list the SIP Network/IP Address field as a required setting, you must configure the SIP Network/IP Address field and the SIP Port field in the SRST Reference Configuration window for a SIP device to fall back to the SRST-enabled gateway. For more information on these fields and SRST references, refer to the Cisco Unified Communications Manager Administration Guide.
Cisco Unified Reporting Application
The Cisco Unified Reporting web application, which is accessed at the Cisco Unified Communications Manager console or from the Cisco Unified Communications Manager Real-Time Monitoring Tool, generates reports for troubleshooting or inspecting cluster data. You can find more information about this application in the Cisco Unified Reporting Administration Guide.
New and Changed Information in Cisco Unified Communications Manager 6.1(1x)
The following section describes new features and changes that are pertinent to Cisco Unified Communications Manager, Release 6.1(1x) or later. The sections may include configuration tips for the administrator, information about users, and information about where to find more information.
•
Basic Uninterruptible Power Supply (UPS) Integration
•
New Service Parameters Added to Extension Mobility
•
Disaster Recovery Manual Backup Window
•
Cisco Unified Communications Operating System CLI Commands
•
Installation, Upgrade, Migration, and Disaster Recovery
•
Cisco Unified Communications Operating System Administration
•
Cisco Unified Communications Manager Administration
•
Cisco Unified Communications Manager Features and Applications
•
Cisco Unified Communications Manager Bulk Administration Tool
•
CDR Analysis and Reporting Tool/Call Detail Record (CAR/CDR)
•
Cisco Unified Communications Manager User Options
Basic Uninterruptible Power Supply (UPS) Integration
When Cisco Unified Communications Manager 6.0(1a) runs on an MCS 7825H2 or MCS 7835H2, basic integration to the UPS model APC SmartUPS 1500VA USB and APC 750VA XL USB gets supported. Integration occurs via a single point-to-point Universal Serial Bus (USB) connection. Serial and SNMP connectivity to UPS does not get supported, and the USB connection must be point-to-point (in other words, no USB hubs). Single- and dual-USB UPS models get supported. The feature activates automatically during bootup if a connected UPS gets detected.
Alternatively, on MCS-7835H2, you can execute the show ups CLI command which shows the current status of the USB-connected APC smart-UPS device and starts the monitoring service if it is not already started.
On supported servers, the CLI command also displays detected hardware, detected versions, current power draw, remaining battery runtime, and other relevant status information.
When the feature is activated, graceful shutdown will commence as soon as the low battery threshold is reached. Resumption or fluctuation of power will not interrupt or abort the shutdown.
For unsupported Cisco Unified Communications Manager releases, MCS models and/or UPS vendor/make/models, you can cause an external script to monitor the UPS. When low battery gets detected, you can log on to Cisco Unified Communications Manager by using Secure Shell (SSH), access the CLI, and execute the utils system shutdown command.
New Service Parameters Added to Extension Mobility
Extension Mobility includes four new service parameters. You can find these new parameters at System > Service Parameters > Cisco Extension Mobility > Advanced.
•
Extension Mobility Cache Size
Validate IP Address
This parameter specifies whether validation of the IP address of the source that is requesting login or logout occurs.
The paramater can take values of true or false.
•
If the parameter specifies true, the IP address from which an EM log in or log out request is made gets validated to ensure that it is a trusted IP address.
Validation Procedure
–
Validation is first performed against the cache for the device to be logged in or logged out.
–
If the requesting source IP address is not found in cache, the IP address gets checked against the list of trusted IP addresses and hostnames specified in the Trusted List of IPs service parameter.
–
If the requesting source IP address is not present in the Trusted List of IPs service parameter, it is checked against the list of devices registered to Cisco Unified CallManager.
Validation Effect
–
If the IP address of the requesting source is found in the cache or in the list of trusted IP addresses or is a registered device, the device is allowed to perform login or logout.
–
If the IP address is not found, the log in or log out attempt is blocked.
•
If the parameter specifies false, the EM log in or log out request does not get validated.
Note
Validation of IP addresses may increase the time required to log in or log out a device, but it offers an additional layer of security in the effort to prevent unauthorized log in or log out attempts, especially when used in conjunction with log ins from separate trusted proxy servers for remote devices.
For more information, refer to the design guidelines in the Extension Mobility documentation.
Trusted List of IPs
This parameter displays as a text box (maximum length - 1024 characters). You can enter strings of trusted IP addresses or hostnames, separated by semi-colons, in the text box. IP address ranges and regular expressions do not get supported.
Allow Proxy
Allow Proxy can take values of true or false.
•
If the parameter specifies true, EM log in and log out operations using a web proxy are allowed.
•
If the parameter specifies false, EM log in and log out requests coming from behind a proxy get rejected.
Note
The setting you select takes effect only if the Validate IP Address parameter specifies true.
Extension Mobility Cache Size
This parameter displays as a text box in which the administrator can configure the size of the device cache maintained by Extension Mobility. The minimum value for this field is 1000 and the maximum is 20000. The default specifies 10000.
Note
The value you enter takes effect only if the Validate IP Address parameter specifies true.
Disaster Recovery Manual Backup Window
Disaster Recovery System backs up CAR/CDR data automatically when you check the CCM checkbox on the Manual Backup window. The Manual Backup window no longer contains a CAR/CDR checkbox.
Cisco Unified Communications Operating System CLI Commands
This section describes Cisco Unified Communications Operating System CLI commands that are added or updated in this release.
file delete
The file delete command includes the parameters dir tftp and license. The file delete command deletes one or more files.
Command Syntax
file delete
dir tftp directory [detail]
license filename [detail]
Parameters
•
dir tftp directory deletes the TFTP directory specified by directory. You cannot enter the wildcard character (*) in directory.
•
license filename deletes the license file that is specified by license. You can enter the wildcard character (*) as filename to delete all the license files.
Options
•
detail—Displays details
Usage Guidelines
You get prompted for confirmation after entering the command.
You cannot delete directories or files that are in use.
file dump
The file dump command includes the new parameter sftpdetails. The file dump command dumps the contents of a file to the screen, a page at a time.
Command Syntax
file dump
sftpdetails filename [hex] [regexp expression] [recent]
Parameters
•
sftpdetails specifies SFTP-related files.
•
filename specifies the filename of the file to dump.
Options
•
hex—Displays output in hexadecimal
•
regexp expression—Displays only the lines in the file that match the regular expression expression.
•
recent—Displays the most recently modified file in the directory.
Usage Guidelines
To determine which files you can dump with this command, first enter the following command:
file list sftpdetails *
The output lists the filenames that you can dump.
Requirements
Command privilege level: 1
Allowed during upgrade: Yes
file fragmentation sdi
This command displays file fragmentation information about SDI log files.
Command Syntax
file fragmentation sdi
all outfilename
file filename {verbose}
most fragmented number
most recent number
Parameters
•
all records information about all files in the directory in the file that is specified by outfilename.
•
file displays information about the file that is specified by filename.
•
most fragmented displays information about the most fragmented files.
•
most recent displays information about the most recently logged fragmented file.
•
number specifies the number of files to list.
Options
•
verbose—Displays more detailed information
Requirements
Command privilege level: 1
Allowed during upgrade: Yes
file fragmentation sdl
This command displays file fragmentation information about SDL log files.
Command Syntax
file fragmentation sdl
all outfilename
file filename {verbose}
most fragmented number
most recent number
Parameters
•
all records information about all files in the directory in the file that is specified by outfilename.
•
file displays information about the file that is specified by filename.
•
most fragmented displays information about the most fragmented files.
•
most recent displays information about the most recently logged fragmented file.
•
number specifies the number of files to list.
Options
•
verbose—Displays more detailed information
Requirements
Command privilege level: 1
Allowed during upgrade: Yes
file get
The file get command includes the new parameters salog, partBsalog. The file get command sends the file to another system by using SFTP.
Command Syntax
file get
salog directory/filename [reltime] [abstime] [match] [recurs]
partBsalog directory/filename [reltime] [abstime] [match] [recurs]
Parameters
•
salog specifies the salog log directory.
•
partBsalog specifies the partBsalog log directory.
•
directory/filename specifies the path to the file(s) to get. You can use the wildcard character, *, for filename as long as it resolves to one file.
Options
•
abstime—Absolute time period, specified as hh:mm:MM/DD/YY hh:mm:MM/DD/YY
•
reltime—Relative time period, specified as minutes | hours | days | weeks | months value
•
match—Match a particular string in the filename, specified as string value
•
recurs—Get all files, including subdirectories
Usage Guidelines
After the command identifies the specified files, you get prompted to enter an SFTP host, username, and password.
Requirements
Command privilege level: 0
Allowed during upgrade: Yes
file list
The file list command includes the new parameters salog and partBsalog, and sftpdetails. The file list command lists the log files in an available log directory.
Command Syntax
file list
salog directory [page] [detail] [reverse] [date | size]
partBsalog directory [page] [detail] [reverse] [date | size]
sftpdetails filespec [page] [detail] [reverse] [date | size]
Parameters
•
salog specifies the salog log directory.
•
partBsalog specifies the partBsalog log directory.
•
sftplog specifies the SFTP log directory.
•
directory specifies the path to the directory to list. You can use a wildcard character, *, for directory as long as it resolves to one directory.



