Table Of Contents
Release Notes for Cisco Unified Communications Manager Release 6.0(1b)
Upgrading to Cisco Unified Communications Manager 6.0(1b)
Upgrade Paths To Cisco Unified Communications Manager 6.0(1b)
Upgrading from Unified CM 4.x and 5.x
CSCso94813: Subscriber Server Install Fails Due to 'hostname -i" Failing
Cisco Unified Communications Disaster Recovery Framework Command Execution
Voice Mailbox Mask Interacts with Diversion Header
Cisco Advisory for Cisco Unified Communications Manager Release 6.0(1a)
Cisco Security Agent (CSA) Drops Incoming TCP SYN Connection Attempts with No Logs
Do Not Upgrade from Cisco Unified CallManager 5.1(3) to Cisco Unified Communications Manager 6.x
CSCsi75567 MCS-7825H2-IPC1 Reboots Randomly
New Clustering Over WAN Requirements
Voice, Cisco Fax Relay and Fax Passthrough Calls Fail
No Such Name Error Returned in the SNMP Response
Value of the Maximum Current Requests Service Parameter After Upgrade to Release 6.0
IP Phone Messenger (IPPM) User Does Not Have Callback Capability
Monitoring Call Gets Dropped When Agent Call Is Put on Hold
DVDROM Not Accessible After Upgrade
Deleting Then Adding Back a Server in Cisco Unified Communications Manager Administration
Call History Might Get Lost When AAR Routes Over QSIG Trunk
Extension Mobility Maximum Concurrent Requests Number Does Not Change After Upgrade
Cisco Unified Communications Manager Assistant Limitations with Cisco IP Communicator
Subscribe Calendar 500 Internal Error
Disabling the Advertise G.722 Codec Enterprise Parameter When You Are Using System Features
Using FTP to Upgrade to Cisco Unified Communications Manager Release 6.0(1b)
Cisco Unified Personal Communicator LDAP Attribute Mappings
Terminal Server Causes RTMT to Display Repeating Syslog and Alert Messages
New and Changed Information in Cisco Unified Communications Manager Releases 6.0(1x)
Basic Uninterruptible Power Supply (UPS) Integration
HP NC-Series Broadcom Firmware Updates Available for Supported NICs.
Smart Array 6i Requires HD Firmware Update to Avoid POST Notification
CSCsj72914 Conference Calls Experience Poor Audio Quality
CSCsj55359 Installation Media Cannot Locate Available Patches
CSCsj42131 User with Incorrect Primary Extension in Directory Export
CSCsj22669 User and User Profile Association Issue in Directory Export
CSCsi71128 DMA Requires a Long Time to Run
CSCsi20684 CSS Call Forward All
Installation, Upgrade, Migration, and Disaster Recovery
Where to Find More Information
Cisco Unified Communications Operating System Administration
Platform Status and Configuration Enhancements
Security Configuration Enhancements
Software Upgrades Enhancements
Command Line Interface Enhancements
Where to Find More Information
Cisco Unified Communications Manager Administration
General Administration Enhancements
Navigating to IP Telephony Applications Within Cisco Unified Communications Manager Enhancements
Localizing Cisco Unified Communications Manager Administration
General Changes That Were Made to Multiple Windows
Locations and Region Enhancements
Where to Find More Information
Cisco Unified Communications Manager Features
Audible Message Waiting Indicator
Call Diagnostics and Voice Quality Metrics
Call Forward All Calling Search Space Backward Compatibility
Cisco Messaging Interface Enhancements
Cisco Unified Communications Manager T1 CAS Hookflash Transfer Support
Credential Policy and User Authentication
Overlap Sending and Receiving for H.323 Gateways
Third-Party Phones Enhancements for Phones That Are Using SIP
Cisco Unified Communications Manager Applications
Cisco Unified Communications Manager Extension Mobility
Cisco Unified Communications Manager Assistant
Migrating from Cisco Unified Mobility to Cisco Unified Communications Manager
Multilevel Precedence and Preemption (MLPP) Supplementary Services
Multilevel Precedence and Preemption Enhancements
Cisco Unified Communications Manager Bulk Administration Features
New and Changed Information for BAT
Cisco Unified Communications Manager Security Features
Cisco Unified Real-Time Monitoring Tool
Cisco Unified Communications Manager CDR Analysis and Reporting
Call Detail Record Definitions
Cisco Unified Communications Manager User Options Menu
Cisco Unified IP Phone 7965G and 7945G
Cisco Unified IP Phone 7962G and 7942G
Cisco Unified IP Phone 7931G (SCCP Only)
Cisco Unified IP Phone Support for Cisco Unified Communications Manager 6.0 Features
Feature Support by Cisco Unified IP Phone and Protocol
Call Forward All Loop Prevention Message Changes
Cisco Unified Communications Manager Developers Guide
Cisco Unified Communications Manager Data Dictionary
Cisco Unified JTAPI Developers Guide
Cisco Unified TAPI Developers Guide
Cisco Unified TSP Enhancements for Release 4.2(1)
SCCP Messaging Guide for Cisco Unified Communications Manager 6.0(1)
SCCP Messaging Guide for Cisco Unified CallManager 5.0(4)
SCCP Messaging Guide for Cisco Unified CallManager 5.0(2)
SCCP Messaging Guide for Cisco Unified CallManager 5.0(1)
Multicast Music On Hold and Media Termination Points
Cisco Unified IP Phones Supporting Cisco Call Back with PLKs
Call Throttling and the Code Yellow State
Call Throttling and Denial of Service (DOS) Attacks
Number of Login or Logout Operations that Cisco Extension Mobility Supports
New Cisco Signaling Performance Object
Modifying HostName/IP Address Creates Inaccessible RTMT Profiles
Collecting Installation Logs with RTMT
Replication Status on Database Summary in RTMT
set network dhcp eth0 disable Command Parameters
Default Device Profile Information
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
Cisco Extension Mobility Supplemental Information
Cisco Unified IP Phones That Support Barge
Cisco Unified IP Phones That Support Cisco Call Back
Extension Mobility Successful Authentication Cache
Software Conference Bridge Not Supported
Do Not Disturb Feature Priority
Recommended Number of Devices in Device Pool
Devices Associated with the Attendant Console Application User
Number of Replicates Created and State of Replication
Support for Certificates from External CAs
CAPF System Interactions and Requirements
Peer-to-Peer Image Distribution
Cisco Product Security Overview
Reporting Security Problems in Cisco Products
Release Notes for Cisco Unified Communications Manager Release 6.0(1b)
August 20, 2008
This document includes:
•
Information that was contained in the Release Notes for Cisco Unified CallManager Releases 6.0(1) and 6.0(1a)
•
Table 1 Information Added for Cisco Unified Communications Manager Release 6.0(1b)
August 20, 2008
•
April 14, 2008
•
–
–
–
•
•
•
These release notes describe the caveats that release 6.0(1) and 6.0(1a) resolve as well as the new features and caveats for Cisco Unified Communications Manager Release 6.0(1b). 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.0(1b)
The following non comprehensive list gives the caveats that were resolved in this release of Unified CM:
•
•
•
•
•
•
•
•
•
•
•
•
Contents
These release notes discuss the following topics:
–
–
•
–
•
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.0(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.0(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
Note
To see which MCS server is compatible with Cisco Unified Communications Manager Release 6.0(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.0(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.
Caution
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:
•
•
Upgrading to Cisco Unified Communications Manager 6.0(1b)
The following sections contain information pertinent to upgrading to this release of Unified CM.
•
•
•
Cisco Upgrade Recommendations
Cisco offers the following recommendations.
Upgrade Paths To Cisco Unified Communications Manager 6.0(1b)
It is possible to upgrade directly to Cisco Unified Communications Manager 6.1(1b) from:
•
•
•
•
•
•
Caution
Upgrading from Unified CM 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 must enter your Cisco contract number (Smartnet, SASU or ESW) and request the CD/CD set. If you do not have a contract for Cisco Unified Communications Manager, you must purchase the upgrade from Cisco Sales.
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) to Release 6.0(1b) Using the UCSInstall File
Caution
Because of its size, the UCSInstall iso file, UCSInstall_UCOS_6.0.1.3000-7.sgn.iso, has been divided into two parts:
•
•
Procedure
Step 1
Step 2
Note
a.
cat UCSInstall_UCOS_6.0.1.3000-7.sgn.iso_part1of2 UCSInstall_UCOS_6.0.1.3000-7.sgn.iso_part2of2 > UCSInstall_UCOS_6.0.1.3000-7.sgn.iso
b.
COPY /B UCSInstall_UCOS_6.0.1.3000-7.sgn.iso_part1of2+UCSInstall_UCOS_6.0.1.3000-7.sgn.iso_part2of2 UCSInstall_UCOS_6.0.1.3000-7.sgn.iso
Step 3
58cb11e2025f5e688abfc53daf3bef27 UCSInstall_UCOS_6.0.1.3000-7.sgn.iso
Software Download URLs
You can access the latest software upgrades for Cisco Unified Communications Manager 6.1 on Cisco.com. Table 3 lists the URLs from which you download the software.
Table 3 Software Download URLs
Cisco Unified Communications Manager 6.0(1b)
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.0(1b) 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.0(1b) as part of Unified Communications System Release 6.0(1b) 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.0(1) as part of Unified Communications System Release 6.0(1b) 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.0(1b). 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.0(1b).
Important Notes for Cisco Unified Communications Manager Release 6.0(1b)
•
•
•
Important Notes for Cisco Unified Communications Manager Release 6.0(1a)
•
•
•
•
Important Notes for Cisco Unified Communications Manager Release 6.0(1)
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
CSCso94813: Subscriber Server Install Fails Due to 'hostname -i" Failing
Ensure that the hostname of the publisher server and subscriber servers are distinctly different. Also ensure that the publisher server name does not appear as a substring of the subscriber server hostname.
If the names are not distinct, you will not be able to install the subscriber servers; and the install log file will indicate the following hostname failure: hostname: Host name lookup failure.
Example:The publisher server installs with a hostname of XXXX and a subscriber server gets defined to the publisher server. The subscriber server hostname is XXXX-YYY. The subscriber server hostname contains the publisher server hostname as a substring.In this case, the subscriber server install fails.Cisco Unified Communications Disaster Recovery Framework Command Execution
Several products in the Cisco Unified Communications family of products contain 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. There is a workaround for this vulnerability.
Cisco has released free software updates that address this vulnerability.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20080403-drf.shtml.
Voice Mailbox Mask Interacts with Diversion Header
When a call gets redirected from a DN to a voice-mail server/service that is integrated with Unified CM using a SIP trunk, the voice mailbox mask on the voice-mail profile for the phone modifies the diverting number in the SIP diversion header. This behavior is expected because the diversion header gets used by the Unified CM server to choose a mailbox.
Cisco Advisory for Cisco Unified Communications Manager Release 6.0(1a)
A Cisco advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20070801-IOS-voice.shtml.
SummaryCisco recommends that customers who run Cisco Unified Communications Manager Release 6.0(1) upgrade to release 6.0(1a). This recommendation applies because of the following information.
Cisco IOS software includes multiple voice-related vulnerabilities, one of which (malformed SIP packet) also gets shared with Cisco Unified Communications Manager.
SIP represents a protocol that is used to establish, modify, and terminate multimedia sessions. Most commonly, SIP gets used for Internet telephony. SIP call signaling can use UDP (User Datagram Protocol) or TCP (Transport Control Protocol) as an underlying transport protocol. In all cases processing a malformed SIP packet.can trigger vulnerabilities.
A malformed SIP packet can cause a vulnerable device to crash and can allow arbitrary code to be executed. The following Cisco Bug ID documents these vulnerabilities:
CSCsi80102 Cisco Unified Communications Manager crashes while processing malformed SIP packet.
Successful exploitation of the vulnerabilities that are listed as Cisco Bug ID CSCsi80102 can lead to remote code execution.
Successful exploitation of other SIP-related vulnerabilities that are listed in the Cisco Systems advisory can cause the affected device to crash. Repeated exploitation could result in a sustained denial of service (DoS) attack.
When considering software upgrades, also consult http://www.cisco.com/go/psirt and any subsequent advisories to determine exposure and a complete upgrade solution.
In all cases, you should exercise caution to be certain that the devices to be upgraded contain sufficient memory and that the new release will continue to support your current hardware and software configurations. If the information is not clear, contact the Cisco Technical Assistance Center (TAC) or your contracted maintenance provider for assistance.
No workarounds exist to mitigate the effects of any of the vulnerabilities apart from disabling the protocol or feature itself.
Obtaining Fixed Software
Cisco makes free software available to address these vulnerabilities. Prior to deploying software, customers should consult their maintenance provider or check the software for feature set compatibility and known issues that are specific to their environment.
Customers may only install and expect support for the feature sets that they have purchased. By installing, downloading, accessing, or otherwise using such software upgrades, customers agree to be bound by the terms of Cisco software license terms that are found at http://www.cisco.com/public/sw-license-agreement.html, or as otherwise set forth at Cisco.com Downloads at
http://www.cisco.com/public/sw-center/sw-usingswc.shtml.These release notes describe updates and caveats for Cisco Unified Communications Manager Release 6.0(1a). 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 "Upgrading System Software" section.
Cisco Security Agent (CSA) Drops Incoming TCP SYN Connection Attempts with No Logs
Under heavy call volume, when a large number of H.323 gateways are utilized, as calls are answered and media gets established, severe delays may occur with the H.245 connection between the gateways and the Cisco Unified Communications Manager server.
This condition causes calls to not connect or to be dropped unexpectedly. This also may impact other incoming TCP connections, and unexpected failures or delays may occur.
If you have CSA enabled, no workaround exists; however, you can disable CSA by using the utils csa disable CLI command.
Note
Do Not Upgrade from Cisco Unified CallManager 5.1(3) to Cisco Unified Communications Manager 6.x
You cannot successfully upgrade from Cisco Unified CallManager Release 5.1(3) to Cisco Unified Communications Manager Release 6.x.
CSCsi75567 MCS-7825H2-IPC1 Reboots Randomly
Sporadic reboots of the 7825H2 servers get triggered during long system hangs. ASR functionality autorecovers the servers after 10 minutes of kernel unresponsiveness. Event timing ranges from once every 3 months to once every 3 days.
Workaround
See http://www.cisco.com/warp/public/770/fn62850.shtml.
New Clustering Over WAN Requirements
Every 10,000 busy hour call attempts (BHCA) between sites that are clustered over the WAN requires 900 Kb/s of bandwidth for Intracluster Communication Signalling (ICCS). This minimum bandwidth requirement exists for call control traffic and gets classified as priority traffic. You should allocate additional ICCS bandwidth at 900 Kb/s per 10,000 BHCA.
The minimum recommended bandwidth between sites that are clustered over the WAN equals 1.544 Mbps. This amount allows for the minimum of 900 Kb/s for ICCS and 644 Kb/s for database and other interserver traffic.
In prior versions of Cisco Unified Communications Manager, subscriber servers in the cluster use the publisher database for READ/WRITE access and only use the local database for READ access when the publisher database cannot be reached. With Cisco Unified Communications Manager Release 6.0, subscriber servers in the cluster READ the local database. DB WRITES happens in both the local database and the publisher database, depending on the type of data. DBMS (IDS) replication synchronizes the databases on the nodes of the cluster. When recovering from a failover conditions such as loss of WAN connectivity for an extended period of time, ensure that the Cisco Unified Communications Manager databases get synchronized with any changes that may occurred during the outage. This process happens automatically when database connectivity gets restored. This process may take longer over low bandwidth and/or higher delay links.
DB REPLICATION REPAIR/RESET:
At some point, you may need to reset or repair database replication between the Cisco Unified Communications Manager servers. To do this, use the utils dbreplication repair all or utils dbreplication reset all command at the command line interface (CLI).
When you repair or reset database replication using the CLI on remote subscribers over the WAN, all Cisco Unified Communications Manager databases in the cluster get resynchronized, which requires additional bandwidth above 1.544 Mbps. Database replication over lower bandwidths may take longer.
Note
You can repair or reset database replication on multiple subscribers at different remote locations simultaneously.
Voice, Cisco Fax Relay and Fax Passthrough Calls Fail
Voice, Cisco Fax Relay and Fax Passthrough calls fail when mgcp fax t38 inhibit command is configured.
Workaround
When you disable T.38 fax relay, you should also disable fxr-package (which is enabled by default) and reset the MGCP service.
Note
Device Reset Speed
You might notice that phone device reset takes longer than in previous releases, especially in large-scale clusters.
Workaround
To mitigate the decrease in speed, Cisco recommends that customers with more than 1000 users on a system wait until the maintenance window to perform a device reset on the phones.
No Such Name Error Returned in the SNMP Response
If the getbulk/getnext/getmany request contains multiple OID variables in its request PDU and the subsequent tables appear empty in the CISCO-CCM MIB, the responses may include NO_SUCH_NAME, for SNMP v1 version or GENERIC_ERROR, for SNMP v2c or v3 version because the time that it takes to process the SNMP requests exceeds the MasterAgent timeout duration (currently set at 25 seconds).
Workaround
You can do many things to avoid this problem, including the following workaround:
•
•
•
•
•
•
Note
Value of the Maximum Current Requests Service Parameter After Upgrade to Release 6.0
The Cisco Extension Mobility service parameter, Maximum Concurrent Requests, does not change when you upgrade to Release 6.0 from an earlier release. This deliberate and intended situation allows you to retain the preexisting value even though Release 6.0 has a default value of 15 maximum concurrent requests. You can change this value on the Service Parameters Configuration window.
IP Phone Messenger (IPPM) User Does Not Have Callback Capability
An IPPM (IP Phone Messenger) user does not have callback capabilities if the user logs into IPPM on a phone where the user is not assigned to the line appearance. When a user logs in to the IPPM service on a Cisco Unified IP Phone and views the details of a MeetingPlace-based meeting on the phone screen, the Callback and Join softkeys do not display when the user is not associated with a line appearance. Although the user has associated himself with a device on the Cisco Unified Communication Manager Administration End User Configuration window, the line appearance on the device itself must get configured with an association to the user for the softkeys to display on the phone.
Workaround:
Associate the line appearance to the end user by using Cisco Unified Communications Manager Administration.
Step 1
The Find and List Phones window displays.
Step 2
The Phone Configuration window displays.
Step 3
Step 4
Note
Monitoring Call Gets Dropped When Agent Call Is Put on Hold
When the agent IP phone uses SIP and the supervisor IP phone uses SCCP, the monitoring call gets set up correctly; however. when the agent call is put on hold, the supervisor gets disconnected and receives a fast busy tone.
To avoid this problem, you can change the signaling protocol on either the agent or supervisor, so both phones use the same signaling protocol.
Note
DVDROM Not Accessible After Upgrade
If you pull the DVD drive out or the DVD drive becomes not accessible during an upgrade, the grub.conf file may become corrupted.
If this happens, you may experience problems when you try to switch versions. For example, rebooting to the upgraded partition may fail, or the reboot may fail, or the reboot will result in a grub menu.
Workaround
You should open a TAC case.
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
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
Procedure
Step 1
Step 2
Tip
If the first node in the cluster runs 6.0(1) 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.0(1).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.0(1).
Call History Might Get Lost When AAR Routes Over QSIG Trunk
When a call is forwarded to another cluster over a trunk/gateway by using QSIG because of insufficient bandwidth (Call Forward No Bandwidth - CFNB), call history might get lost.
If Phone A calls Phone B, which is in a low-bandwidth location, with CFNR set to forward calls to Phone C, which is in a different cluster, and the QSIG protocol is used on the trunk/gateway, the original called party and the last redirecting party might not get passed to the destination party.
Extension Mobility Maximum Concurrent Requests Number Does Not Change After Upgrade
When you upgrade from Cisco Unified CallManager Release 4.x or 5.x to Cisco Unified Communications Manager Release 6,0(1), and you navigate to System-->Service Parameters-->Cisco Extension Mobility, you will see that the maximum concurrent requests value does not change after the upgrade. The value remains the same as it was for Cisco Unified CallManager Release 4.x or 5.x, even though the default value for the maximum concurrent requests for extension mobility in Cisco Unified Communications Manager Release 6.0(1b) is 15.
You can manually change this number to the system default of 15 or greater.
•
Cisco Unified Communications Manager Assistant Limitations with Cisco IP Communicator
Cisco IP Communicator does not support Cisco Unified Communications Manager Assistant Releases 5.1 and 6.0.
Translation Pattern Support
If a calling party transformation mask is configured for a translation pattern that is applied to a JTAPI application-controlled address, the application may see extra connections that are created and disconnected when both the calling and called party are observed. The system creates a connection for a transformed calling party instead of the actual calling party, and CiscoCall.getCurrentCallingParty() would return the transformed calling party, when only the called party is observed. In general, JTAPI might not be able to create the appropriate connection in the call and might not be able to provide correct information for currentCalling, currentCalled, calling, called, and lastRedirecting parties.
For example, consider a translation pattern X that is configured with a calling party transformation mask Y and calledparty transformation mask B. If A calls X, the call goes to B. In this scenario
If the application is observing only B, JTAPI creates a connection for Y and B, and CiscoCall.getCurrentCallingParty() would return Address Y.
If the application is observing both A and B, a connection for A and B gets created, a connection for Y gets temporarily created and dropped, and CiscoCall.getCurrentCallingParty() would return Address Y.
Other inconsistencies could occur in the calling information if further features get performed on a basic call. Cisco recommends that you not configure a calling party transformation mask for a translation pattern that might get applied to JTAPI application-controlled addresses.
Subscribe Calendar 500 Internal Error
A large number of Cisco Unified Presence Communicator users (for example 150 or more), each with 30 or more contacts with calendar enabled, that log in within a short time can compromise the ability of the Microsoft Exchange server to process the requests. The Microsoft Exchange 2003 server will begin to return "500 Internal Server Error" response to most, if not all, requests. The Microsoft Exchange server may or may not recover from the load.
Note
Maximum Trace Settings
The maximum recommended Cisco Unified Communications Manager trace settings specifies 2,500 files of 2 MB each, for SDI and SDL traces, for a combined total of 5000 files. You can increase SDI traces to 5,000 files if SDL traces are disabled, but not vice versa. All other components should stay within 126 MB bucket (for example, 63 files of 2 MB). If you increase logs past the recommended limit, system performance gets reduced due to IOWAIT. After the system experiences IOWAIT related performance degradation, the only solution requires you to lower traces and use RTMT to remove all CCM/CTI SDI/SDL traces. For that reason, you should limit tracing to 5 GB for CCM and 5 GB for CTI.
Disabling the Advertise G.722 Codec Enterprise Parameter When You Are Using System Features
If you experience feature interoperability issues, and you have the Cisco Unified Communications Manager enterprise parameter Advertise G.722 Codec set to Enabled, change the setting to Disabled (the default setting specifies Enabled) and update the device pools for the phones. When this parameter specifies enabled, the enterprise parameter allows Cisco Unified IP Phones (such as 7971, 7970, 7941, 7961) to negotiate and use the G.722 codec when calls are within the same region.
If individual phone control and use of a specific codec type is required (for example, G.711), check the configuration of each phone (by using Phone Configuration) for the parameter Advertise G.722 Codec and change the setting to Disabled. Save and reset the device.
Note
For more information about the G.722 codec, see the "Using the G.722 Codec" section.
Using FTP to Upgrade to Cisco Unified Communications Manager Release 6.0(1b)
Even if enough disk space exists, if you upgrade to this release by using FTP, the upgrade might fail with an error message that states that not enough disk space exists to complete the upgrade.
If this happens, begin the upgrade again by using a different upgrade method (such as SFTP or LOCAL) or use different FTP server software.
Cisco Unified Personal Communicator LDAP Attribute Mappings
Be aware that Cisco Unified Personal Communicator LDAP attribute mappings are wrong for the Active Directory set of attribute mappings.
Before Cisco Unified Communications Manager Release 6.0(1), only one set of LDAP attribute mappings existed. In Cisco Unified Communications Manager Release 6.0(1), two sets of attribute mappings exist: for Netscape LDAP and for Active Directory LDAP. During an upgrade to this release, the default attribute mappings do not get correctly carried forward into the Cisco Unified Communications Manager Release 6.0(1) attribute mappings for Active Directory LDAP. (They correctly get carried forward for Netscape LDAP.)
This applies to default attribute mappings. Non-default attribute mappings (for example those explicitly specified by the user) properly get carried forward for both Netscape LDAP and Active Directory LDAP.
Before you upgrade to Cisco Unified Communications Manager Release 6.0(1b), make a note of the Cisco Unified Personal Communicator LDAP attribute mappings and enter the original values for the Active Directory set of attribute mappings
Terminal Server Causes RTMT to Display Repeating Syslog and Alert Messages
When a terminal server is connected to the serial port of a Cisco Unified Communications Manager server, the system generates a repeating alert message and corresponding syslog message similar to the following examples:
•
•
This includes a router that is being used as a terminal server.
Cisco recommended that you configure no exec on the lines that are connected to the console of the other devices.
New and Changed Information in Cisco Unified Communications Manager Releases 6.0(1x)
The following sections describe new features and changes that are pertinent to Cisco Unified Communications Manager, Release 6.0(1a and below). The sections may include configuration tips for the administrator, information about users, and information about where to find more information.
No new and changed information exists specifically for Cisco Unified Communications Manager Release 6.0(1b).
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Trace Compression Support
This feature enables the ROS (Recoverable Outstream) library to support the compressed output of trace files. The files get compressed as they are being generated. The following benefits of trace file compression apply:
•
•
For more information, see Documentation Updates
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 status CLI command to activate the feature (see "Command Line Interface Enhancements").
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.
HP NC-Series Broadcom Firmware Updates Available for Supported NICs.
The upgrade includes
•
•
You can update firmware manually by downloading and booting from the HP Firmware Maintenance CD version 7.80 (10 May 07) that is located at http://h18023.www1.hp.com/support/files/server/us/download/27225.html
Smart Array 6i Requires HD Firmware Update to Avoid POST Notification
You should upgrade hard drive models that experience excessive SCSI command timeout. Failure to upgrade may result in the bus down-shifting from Ultra 320 to Ultra 3.
Upgrade following hard disk models to the specified versions:
Workaround
You can update firmware manually by downloading and booting from the HP Firmware Maintenance CD version 7.80 (10 May 07) that is located at http://h18023.www1.hp.com/support/files/server/us/download/27225.html
CSCsj72914 Conference Calls Experience Poor Audio Quality
Conference calls that use the software media resources (MTP, MOH, and CFB) on a Cisco Unified CallManager 5.1(2) server experience poor audio quality when they traverse a WAN with QoS implemented.
Because the RTP that comes from Cisco Unified CallManager has a DSCP of 0x00, these packets get queued and/or dropped behind other voice signaling and RTP packets at the WAN router. Depending on network conditions for the WAN link, this can cause poor audio quality.
Current Condition
The release of Cisco Unified Communications Manager Release 6.0(1a) resolved this problem.
CSCsj61395 Spurious Error Message Displays During Installation of Locale COP Files on a Subscriber Server
Previously, when a user installed a locale COP file on a subscriber server, an error message displayed: "Status: Error Encountered."
Current Condition
The release of Cisco Unified Communications Manager Release 6.0(1a) resolved this problem.
CSCsj55359 Installation Media Cannot Locate Available Patches
The installation media does not find the available upgrade patches.
Workaround
The release of Cisco Unified Communications Manager Release 6.0(1a) resolved this problem.
CSCsj42131 User with Incorrect Primary Extension in Directory Export
Caveat
After migration from Cisco Unified CallManager Release 4.x to Cisco Unified CallManager Release 5.x, the user gets associated with the wrong primary extension.
Current Condition
The release of Data Migration Assistant 6.0(1a) and Cisco Unified Communications Manager resolved this problem.
CSCsj22669 User and User Profile Association Issue in Directory Export
Caveat
Multiple CNN-profiles per user exist in the Cisco Unified CallManager Release 4.x directory. After an upgrade to Cisco Unified Communications Manager 6.0(1), despite a clean DMA run, lost/missing/incorrect login profiles and device associations exist.
Current Condition
The release of Data Migration Assistant 6.0(1a) and Cisco Unified Communications Manager resolved this problem.
CSCsi71128 DMA Requires a Long Time to Run
Caveat
When users upgrade to Cisco Unified Communications Manager Release 6.x, from releases prior to release 4.1(3), DMA execution takes a very long time in the premigration phase. If this occurs, the users should wait for completion. A delay in this phase of up to 23 hours for 45,000 devices has occurred.
Current Condition
The release of Data Migration Assistant 6.0(1a) and Cisco Unified Communications Manager resolved this problem.
CSCsi20684 CSS Call Forward All
Caveat
DMA fails to validate when invalid contents exist in the CSSForCFA table:
Need exists for DMA processing to handle invalid CSS failures more efficiently.
Current Condition
The release of Data Migration Assistant 6.0(1a) and Cisco Unified Communications Manager resolved this problem.
Installation, Upgrade, Migration, and Disaster Recovery
The following sections describe the changes that were made to the installation, upgrade, and disaster recovery procedures in Cisco Unified Communications Manager 6.0(1):
Guest
