Table Of Contents
Release Notes for Cisco Unified Communications Manager Release 6.1(2)
Upgrading to Cisco Unified Communications Manager 6.1(2)
Upgrade Paths To Cisco Unified Communications Manager 6.1(2)
Upgrading from Unified CM 4.x and 5.x
Cisco CallManager Service Stops After Upgrade to Cisco Unified Communications Manager 6.X
Important Information about Delete Transaction Using Custom File in BAT
Deleting a Server and Adding a Deleted Server to a Cluster
Clarification for Call Park Configuration
Viewing Privileges for Roles in Cisco Unified CM Administration
TAPS Name Change in Bulk Administration Tool
Basic Uninterruptible Power Supply (UPS) Integration
CSCsq22385 Database Replication Setup Fails After You Add a New Subscriber to a Cluster
Serviceability Not Always Accessible from OS Administration
Voice Mailbox Mask Interacts with Diversion Header
Installation Note for CTL Client 5.0 Plug-In
Installation Note for Windows 2000 Users
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(2)
Improved Access to Personal Address Book
Cisco GD-1T3 Voice Gateway Support in Cisco Unified Communications Manager Administration
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
New Preconfigured Alerts in Cisco Unified Serviceability
New Highlight Capability on RTMT Graphs and Charts
Consistent RTMT Severity and Syslog Severity
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 IP Phone Expansion Modules
Call Park Reversion (Inconsistent Messages)
Using Call Pickup Groups with BLF Pickup
Parallel Installations of Cisco Unified Communications Manager 6.1(2)
Parallel Upgrades from Unified CM Releases 5.x and 6.x to Unified CM Release 6.1(2)
Parallel Upgrades from Unified CM Release 4.x to Unified CM Release 6.1(2)
Enhancements for Cisco Unified CM User Options
Enhancements for Data Migration Assistant
Enhancements for the Disaster Recovery System
Changing the Hostname of Cisco Unified Communications Manager Servers
Enhancements for Cisco Unified Serviceability
New Preconfigured Alerts in Cisco Unified Serviceability
New Highlight Capability on RTMT Graphs and Charts
Consistent RTMT Severity and Syslog Severity
CAR - Configuring Individual and Department Bills Reports
Enhancements for Cisco Unified Reporting
New Service Parameters Added to Extension Mobility
Cisco Unified Communications Manager Configuration XML
Cisco Unified Communications Manager Serviceability XML
Information Omitted for Reroute Incoming Request to new Trunk based on Setting
CTI and Attendant Console Chapters Omit Information on CTI Monitored Lines
Trunk Chapter Omits Restrictions for H.323/H.225 Trunks
cBarge Chapter Omits Information on Shared Line Restriction for Conferences
Information About Changing Region Bandwidth Settings When Video Calls Are Made
Cisco Unified Mobility User Hangs Up Mobile Phone But Cannot Resume Call on Desktop Phone
Online Help Notes for Hebrew and Arabic
Clustering Chapter Omits Information about Subsequent (Subscriber) Node
Licensing Chapter Omits Information on Adjunct Licensing
Cisco TFTP Chapter Omits Configuration Tip on Centralized TFTP
For SIP Trunks Used with Multiple Device Pools, Configure an SRV Destination Port
Characters Allowed in a Pre-Shared Key
LDAP Authentication Chapter Omits Information on SSL Certificates and IP Addresses/Hostnames
Enterprise Parameters and Service Parameters Chapters Omit Information on Set to Default Button
Information About Using an SRV Destination Port for the CUP Publish Trunk Service Parameter
Disaster Recovery System Restoration Process
Automated Alternate Routing (AAR) Limitation with Remote Gateways
Recovering Administrator and Security Passwords
System Generates a DBReplicationFailure Alert
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)
Directory Numbers Chapter Includes Incorrect Example for Shared Lines and Call Forward Busy Trigger
Default Device Profile Chapter Incorrectly Includes Expansion Module Settings
Hunt Pilot Chapter Needs Clarification of Maximum Hunt Timer Setting
Annunciator Chapter Contains Incorrect Information on Description Field
Gateway Configuration Chapter Contains Incorrect Information on Domain Name Field
AAR Group Chapter Includes Incorrect Description for Dial Prefix Field
Cisco Unified Wireless IP Phone Guide 7920 for Cisco Unified CallManager 5.0 (SCCP)
Using Personal Directory on Your Phone
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
Creating Filter Lists for a Manager
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
Cisco Unified Communications Manager Assistant
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(2)
Updated September 8, 2008
This document contains information included in the release notes for Cisco Unified Communications Manager Releases 6.1(1), 6.1(1a), and 6.1(1b) and new information for Cisco Unified Communications Manager Release 6.1(2). Table 1 describes the additions and changes made for Release 6.1(2)
Before you install Cisco Unified Communications Manager, Cisco recommends that you review the "Upgrading to Cisco Unified Communications Manager 6.1(2)" section for information about uprading and the "Important Notes" section for information about issues that may affect your system.
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
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 "Before You Begin" section.
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.1(2) 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(2), 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.1(2), 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(2), 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 to Cisco Unified Communications Manager 6.1(2)
The following sections contain information pertinent to upgrading to this release of Unified CM.
•
•
Before You Begin
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:
•
•
Upgrade Paths To Cisco Unified Communications Manager 6.1(2)
You can upgrade directly to Cisco Unified Communications Manager 6.1(2) 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 that is for registered customers only to obtain a media kit and license or to purchase the upgrade from Cisco Sales.
To use the PUT, youmust 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
Cisco Recommendations
Cisco offers the following recommendations.
Upgrading from Cisco Unified Communications Manager Release 6.0.(1a) or higher to Release 6.1(2) by Using the UCSInstall File
Because of its size, the UCSInstall iso file, UCOS_6.1.2.1000-13.sgn.iso, comprises two parts:
•
•
Procedure
Step 1
Step 2
Note
a.
cat UCSInstall_UCOS_6.1.2.1000-13.sgn.iso_part1of2 UCSInstall_UCOS_6.1.2.1000-13.sgn.iso_part2of2 > UCSInstall_UCOS_6.1.2.1000-13.sgn.iso
b.
COPY /B UCSInstall_UCOS_6.1.2.1000-13.sgn.iso_part1of2+UCSInstall_UCOS_6.1.2.1000-13.sgn.iso_part2of2 UCSInstall_UCOS_6.1.2.1000-13.sgn.iso
Step 3
68e99f0b080298d65b4b82a8befbfe8b UCSInstall_UCOS_6.1.2.1000-13.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 Download URLs for Software Upgrades
Cisco Unified Communications Manager 6.1(2)
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(2). 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(2).
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Cisco CallManager Service Stops After Upgrade to Cisco Unified Communications Manager 6.X
After you upgrade to Cisco Unified Communications Manager 6.X from a compatible Cisco Unified CM 5.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, upload the software feature license that is required for Cisco Unified Communications Manager 6.X 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.
For more information on licensing, refer to the licensing chapters in the Cisco Unified Communications Manager Administration Guide and the Cisco Unified Communications Manager System Guide.
Important Information about Delete Transaction Using Custom File in BAT
Do not use the insert or export transaction files that are created with bat.xlt for the delete transaction. Instead, you must create a custom file with the details of the records that need to be deleted. Use only this file for the delete transaction. In this custom delete file, you do not need a header, and you can enter values for name, description, or user.
Cisco Unified Communications Manager Does Not Support Recovery of Administration or Security Passwords
Cisco Unified Communications Manager does not support recovery of administration or security passwords. If you lose these passwords, you must reset the passwords, as described in the Cisco Unified Communications Operating System Administration Guide.
The Cisco Unified Communications Operating System Administration Guide calls the section, "Recovering the Administrator or Security Passwords," instead of "Resetting the Administrator or Security Passwords." Access the "Recovering the Administrator or Security Passwords" section to reset the passwords.
Deleting a Server and Adding a Deleted Server to a Cluster
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 CM 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 CM database and is not available for use.
Tip
Before you delete a server, consider the following information:
•
•
•
•
•
•
•
•
•
•
•
If you delete a subsequent node (subscriber) from Cisco Unified CM Administration and you want to add it back to the cluster, perform the following procedure:
Procedure
Step 1
Step 2
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 Cisco Unified Communications Manager 6.1(2) version 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 toinstallation documentation that supports your version of Cisco Unified CM.Step 3
Step 4
Clarification for Call Park Configuration
Consider the following information when you configure Call Park:
Call Park numbers cannot overlap between Cisco Unified CM servers. Ensure that each Cisco Unified CM 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, you must define a unique call park number or range of call park extension numbers 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.
Viewing Privileges for Roles in Cisco Unified CM Administration
The Role Configuration window in Cisco Unified CM Administration displays the privileges for each standard role. To access the Role Configuration window, find the role by choosing User Management > Role; when the Find and List Roles window displays, click Find. Click the link for the standard role that you want to view. After the Role Configuration window displays, you can view the privileges in the Resource Access Information pane.
TAPS Name Change in Bulk Administration Tool
Documentation refers to the Tool for Auto-Registered Phone Support (TAPS) as Cisco Unified Communications Manager Auto-Register Phone Tool in the Online Help for Bulk Administration. All references to 'Cisco Unified Communications Manager Auto-Register Phone Tool' in the Bulk Administration Tool Online Help should be read as 'Tool for Auto-Registered Phone Support (TAPS)'. This is in compliance with the Bulk Administration user interface.
For More Information
For information on configuring additional features in BAT, refer to the BAT documentation for Cisco Unified CM.
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.
CSCsq22385 Database Replication Setup Fails After You Add a New Subscriber to a Cluster
Database replication failure alert displays after you add a new subscriber node to an existing cluster.
After the fresh install completes successfully, the following alert displays (date and time vary).May 7 16:02:09 lg-pub-1 local7 2 : 116: May 07 20:02:09.491 UTC : %CCM_RTMT-RTMT-2-RTMT-ERROR-ALERT: RTMT Alert Name:DBReplicationFailure Detail: DBReplicationFailure occured. CallManager database replication errors, Reason code: Replication setup failed. The alert is generated on Wed May 07 16:02:09 EDT 2008 on node 10.1.1.1. App ID:Cisco AMC Service Cluster ID: Node ID:xxxThe primary AMC server, which by default is the publisher node, raises the DBReplicationFailure alert. You can observe this alert by using RTMT Alert Central or Summary view. You can also find the alerts in the EventViewer - Application Logs (CiscoSyslog) that you can access by using RTMT syslog viewer or platform CLI by using the file view activelog syslog/CiscoSyslog command.
Other Symptoms
The following list gives more symptoms of DBReplicationFailure that you may experience:
1.
dbl_repl_cdr_define_lg_sub_8_ccm6_1_2_1000_13-2008_05_07_12_00_20.logsucmd_err [su -c 'ulimit -c 0;cdr err --zap' - informix ]Executing [su -c 'ulimit -c 0;cdr define server --connect=lg_sub_8_ccm6_1_2_1000_13 --idle=0 --init --sync=g_lg_pub_1_ccm6_1_2_1000_13 g_lg_sub_8_ccm6_1_2_1000_13 --ats=/var/log/active/cm/log/informix/ats --ris=/var/log/active/cm/log/informix/ris;' - informix]We got exception in Cdr defineException from cdr define e.value[100] e.msg [Error executing [su -c 'ulimit -c 0;cdr define server --connect=lg_sub_8_ccm6_1_2_1000_13 --idle=0 --init --sync=g_lg_pub_1_ccm6_1_2_1000_13 g_lg_sub_8_ccm6_1_2_1000_13 --ats=/var/log/active/cm/log/informix/ats --ris=/var/log/active/cm/log/informix/ris;' - informix] returned [25600]]2.
11:47:51 CDR GC: GC could not verify the local server identity in CDR catalog with that in sqlhost file during CDR recovery.3.
By default, the publisher node DB replicator service continuously attempts to define the new server and generates a new log every five minutes.
Workaround for a Single Node
Use the following workaround for this caveat.
Caution
node 10.1.1.1. App ID:Cisco AMC Service Cluster ID: Node ID:xxx
Step 1
Step 2
utils dbreplication stop.
Caution
Wait for it to finish before you continue.
Step 3
utils dbreplication dropadmindb
Step 4
utils dbreplication reset <subname> (<subname> equals the name of the subscriber)
At the end of the command output, the following message displays:
admin:utils dbreplication reset nw104a-195Repairing of replication is in progress.Background repair of replication will continue after that for 30 minutes..command failed -- Enterprise Replication not active (62)This output does not indicate a failure in the reset command. It serves as an informational message that got generated when you dropped the admindb on the subcriber. The reset will complete successfully.
The reset command returns immediately, but the operation can take 30 minutes or more to finish.
Workaround for Multiple Nodes
The preceding instructions apply for single nodes, but multiple subscribers may experience this failure. If that occurs, for each subscriber node that is a fresh install and displays the DBReplicationFailure alert, repeat the preceding steps.
Verification
Be aware that replication is set correctly when the RTMT Replication counter "Replicate_State" equals 2 for both the publisher and the subscriber that you reset.
You can monitor the counter via the RTMT Database Summary window or via the platform CLI.
Strict Version Checking
Disaster Recovery System adheres to strict version checking and allows restore only between matching versions of Cisco Unified Communications Manager.
Note
Consider the following examples of restore to understand strict version checking:
In essence, the product version needs to match, end-to-end, for the Disaster Recovery System to run a successful Cisco Unified Communications Manager database restore.
Serviceability Not Always Accessible from OS Administration
In some scenarios, you cannot access the Cisco Unified Serviceability from Cisco Unified OS Administration. The page displays a "Loading, please wait" message indefinitely.
If the redirect fails, log out from Cisco Unified OS Administration, select Cisco Unified Serviceability from the navigation menu, and log in to Cisco Unified Serviceability.
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 by 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. Be aware that this behavior is expected because the the Unified CM server uses the diversion header to choose a mailbox.
Installation Note for CTL Client 5.0 Plug-In
If you are upgrading to the CTL Client 5.0 plug-in, you first need to remove eToken Run Time Environment 3.00 by performing the following steps:
Procedure
Step 1
http://support.microsoft.com/kb/290301Step 2
Step 3
Step 4
Step 5
Installation Note for Windows 2000 Users
If you are running Windows 2000 on your workstation or server, you must download Windows Installer 3.0 updates to correctly install CTL Client plug-ins. You can obtain Windows Installer 3.0 at the following URL:
http://www.microsoft.com/downloads/details.aspx?familyid=5FBC5470-B259-4733-A914-A956122E08E8&displaylang=en
Note
Windows Installer 3.0 requires validation. Follow the instructions to have your PC validated; then, install Windows Installer 3.0; reboot your machine, if necessary, and proceed with CTL Client installation.
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
Step 2
Note
Note
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.
Guest
