Table Of Contents
Release Notes for Cisco Unified Communications Manager Release 6.1(4)
Updated January 4, 2013
Note To view release notes for Cisco Unified Communications Manager Business Edition, go to http://www.cisco.com/en/US/products/ps7273/prod_release_notes_list.html.
Caution Be aware that you cannot upgrade directly from Unified CM 6.1(4) to Unified CM 7.0
This document contains information pertinent to Cisco Unified Communications Manager
Before you install Cisco Unified Communications Manager, Cisco recommends that you review the "Upgrading to Cisco Unified Communications Manager 6.1(4)" section for information about upgrading 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.
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.
Make sure that you install and configure Cisco Unified CM Release 6.1(4) on a Cisco Media Convergence Server (MCS) or a Cisco-approved HP server configuration or a Cisco-approved IBM server configuration.
To find which MCS are compatible with Cisco Unified CM Release 6.1(4), refer to the Supported Servers for Cisco Unified Communications Manager Releases, go here.
Note Make sure that the matrix indicates that your server model supports Cisco Unified Communications Manager Release 6.1(4).
Note Some servers that are listed in the compatibility matrix may require additional hardware support for Cisco Unified Communications Manager Release 6.1(4). 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.
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 Failure 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.
The following sections comprise installation notes for Unified CM 6.1(4).
Windows 2000 Users Must Download Windows Installer 3.0 Updates
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:
Note Windows 2000 comes with Windows Installer 2.0.
Step 1 Windows Installer 3.0 requires validation. Validate your PC by following the instructions.
Step 2 Install Windows Installer 3.0.
Step 3 Reboot your machine, if necessary.
Step 4 Proceed with CTL Client plug-ins installation.
Do Not Install Cisco Unified CM in a Large Class A or Class B Subnet That Contains a Large Number of Devices
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 experiences difficulty communicating with endpoints and cannot add more phones.
Upgrading to Cisco Unified Communications Manager 6.1(4)
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:
•Cisco Unified Communications Manager System version.
•Login to CLI.
•Enter show version active CLI command.
Note If you get the error, GUI lost communication with the system during the upgrade, login again to OS Admin and assume that control to check the upgrade status. Otherwise, you need to use CLI command utlis system upgrade status to check the upgrade status.
Special Upgrade Considerations
Cisco only supports replacing failed hard drives. Cisco does not support drive pulling/swapping as a method of fast upgrade reversion, restore, or server recovery.
Note After you perform a switch version when you upgrade Unified CM, IP phones request a new configuration file. This request results in an automatic upgrade to the device firmware.
Upgrade Paths to Cisco Unified Communications Manager 6.1(4)
For information about supported Cisco Unified CM upgrades, see the Cisco Unified Communications Manager Compatibility Matrix at the following URL:
Caution Use the ISO files that are mentioned in the "Upgrading to Unified CM Release 6.1(4) by Using the UCSInstall File" section for upgrades from 6.1(1x) and later.
Upgrading to Unified CM 6.1(4) from Unified CM 4.x and 5.x
If you are upgrading from 4.1.3, 4.2.3, 4.3(2), 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.
Note During an upgrade from a compatible Cisco Unified CM 5.1 version (see the Compatibility Matrix at http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/compat/ccmcompmatr.html) to Cisco Unified CM 6.1(4) by using a DVD, in the Software Installation/Upgrade window, ignore the checksum step that tells you "To ensure the integrity of the installation file, verify the MD5 hash value against the Cisco Systems website." Click "Next".
Upgrading from an Engineering Special
If you want to upgrade to Cisco Unified CM 6.1(4) and you are currently running an Engineering Special (ES), contact TAC to obtain the fixes that are included in the ES that you currently use.
Upgrading to Unified CM Release 6.1(4) by Using the UCSInstall File
Because of its size, the UCSInstall iso file, UCOS_184.108.40.2060-10.sgn.iso, comprises two parts:
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 220.127.116.110-10 build represents a non-bootable ISO that is only useful for upgrades. You cannot use it 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_18.104.22.1680-10.sgn.iso_part1of2 UCSInstall_UCOS_22.214.171.1240-10.sgn.iso_part2of2 > UCSInstall_UCOS_126.96.36.1990-10.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_188.8.131.520-10.sgn.iso_part1of2+UCSInstall_UCOS_184.108.40.2060-10.sgn.iso_part2of2 UCSInstall_UCOS_220.127.116.110-10.sgn.iso
Step 3 Use an md5sum utility to verify that the MD5 sum of the final file is correct.
The documentation that supports Cisco Unified Communications Manager Release 6.1 resides at
Limitations 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 Release 6.1(4). 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.
Software Download URLs
You can access the latest software upgrades for Cisco Unified Communications Manager at http://tools.cisco.com/support/downloads/go/Redirect.x?mdfid=278875240
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(4).
Adding or Updating SIP Dial Rules Causes Cisco TFTP Service To Rebuild All Phone Configuration Files
When you add or update a SIP dial rule in Cisco Unified Communications Manager Administration, be aware that the Cisco TFTP service rebuilds all phone configuration files, which may cause CPU to spike on the server where the Cisco TFTP service runs, especially if you have a large system with many phones. To ensure that CPU does not spike, add or update the SIP dial rule during a maintenance window or temporarily stop the Cisco TFTP service in Cisco Unified Serviceability before you make the configuration change. If you stop the Cisco TFTP service, remember to restart the service in Cisco Unified Serviceability after you add or update the SIP dial rule.
CSCta10219 Unicast Music on Hold May Not Play
After you invoke music on hold (MOH) several times, unicast MOH may not play. MOH can be invoked by using hold, transfer, conference, park, and so on.
Workaround - Option 1
Upgrade to a version of Cisco Unified Communications Manager that contains a fix for this issue.
Workaround - Option 2
Configure the MOH servers to send out multicast MOH and unicast MOH on the same MOH resources.
Step 1 Configure each MOH audio source ID for multicast.
Step 2 Configure each MOH server to multicast.
Step 3 Make sure that Media Resource Groups (if any are defined) do not have multicast enabled.
Be aware that no network (router) changes to forward multicast MOH packets are required if Media Resource Groups (MRG) are not configured to enable multicast MOH.
Note The MOH servers transmit multicast streams for each MOH source and MOH codec, so network traffic to the local network may increase. The multicast streams will remain continuous and run at all times.
The MOH servers send the multicast streams to the local router; but, if the rounter is not configured to forward the MOH multicast packets, impact to the LAN traffic will be minimal. By default, routers do not forward multicast MOH packets.
Cisco Unified JTAPI
In Cisco Unified Communications Manager Releases 6.x and 5.x, if an application tries to conference two or more addresses on the same terminal, based on the order of participants in the request, an application may receive CiscoJtapiException.CONFERENCE_INVALID_PARTICIPANT for the conference request. The conference might then start successfully with some of the participants. In such cases, no guarantees exist about which application joins the conference. The system creates the conference with only one of the addresses on a terminal. It ignores the other addresses.
This situation occurs in the following scenarios.
Assume that B1 and B2 represent different addresses on the same terminal, TB.
A -> B1 - GC1
A -> B2 - GC2
A -> C - GC3
Assume that an application issues a conference request GC1.conference(GC2,GC3).
In Cisco Unified Communications Manager Releases 6.x and 5.x, the application receives CiscoJtapiException.CONFERENCE_INVALID_PARTICIPANT; however, A, B1, and C join into conference, and the following normal set of events in a conference scenario occur:GC1 CiscoConferenceStartEvGC2 TermConnDroppedEv TBGC2 CallCtlTermConnDroppedEv TBGC2 ConnDisconnectedEv B1GC2 CallCtlConnDisconnectedEv B1GC1 CallCtlTermConnTalkingEv TBGC2 CiscoCallChangedEvGC1 ConnCreatedEv CGC1 ConnConnectedEv CGC1 CallCtlConnEstablishedEv CGC1 TermConnCreatedEv TCGC1 TermConnActiveEv TCGC1 CallCtlTermConnTalkingEv TCGC2 TermConnDroppedEv TCGC2 CallCtlTermConnDroppedEv TCGC2 ConnDisconnectedEv CGC2 CallCtlConnDisconnectedEv CGC2 CallInvalidEvGC1 CiscoConferenceEndEv
Assume that B1 and B2 represent different addresses on the same terminal, TB.
A -> B1 - GC1
A -> B2 - GC2
A -> C - GC3
Assume that an application issues a conference request GC3.conference(GC1,GC2).
In Cisco Unified Communications Manager Release 5.x, the application does not receive an exception, and the request processes successfully. A, C, and B1 join the conference with the regular set of conference events.
In Cisco Unified Communications Manager Releases 5.x and 6.x, the application receives CiscoJtapiException.CONFERENCE_INVALID_PARTICIPANT; however, A, C, B1 join conference, and the normal set of conference events occurs.
SFTP Server Products
Cisco allows you to use any SFTP server product with applications that require SFTP access but recommends SFTP products that have been certified with Cisco through the Cisco Technology Developer Partner program (CTDP). CTDP partners, such as GlobalSCAPE, certify their products with specified version of Cisco Unified Communications Manager. For information on which vendors have certified their products with your version of Cisco Unified Communications Manager, refer to http://www.cisco.com/pcgi-bin/ctdp/Search.pl. For information on using GlobalSCAPE with supported Cisco Unified Communications versions, refer to http://www.globalscape.com/gsftps/cisco.aspx. Cisco uses the following servers for internal testing. You may use one of the servers, but you must contact the vendor for support:
•Open SSH (refer to http://sshwindows.sourceforge.net/)
•Cygwin (refer to http://www.cygwin.com/)
•Titan (refer http://www.titanftp.com/)
Note For issues with third-party products that have not been certified through the CTDP process, contact the third-party vendor for support.
CSCsu08609 Unanswered Conference Call or Blind Transfer Over QSIG Trunk Goes to Third-Party Voice Messaging System Instead of Called Party
A blind transfer or an unanswered conference call that is forwarded to an Avaya system over a QSIG PRI trunk causes the call to go to the third-party voice messaging system instead of the called party. No workaround exists for this issue.
Use Microsoft Outlook to Receive Cisco Unified Communications Manager Licenses
When you obtain a license file from the Product License Registration window on www.cisco.com, the system sends the license file(s) to you via e-mail by using the e-mail ID that you provided. When you receive license files from e-mail clients other than Microsoft Outlook, for example, Microsoft Entourage, additional characters may exist in the license file, which can prevent you from being able to upload the license file in Cisco Unified Communications Manager Administration. To avoid this issue, Cisco recommends that you use Microsoft Outlook when you receive license files for Cisco Unified Communications Manager.
If you obtained a license file with additional characters in it, perform the following procedure:
Step 1 Use the CLI to delete the license file from the Cisco Unified Communications Manager server. In the CLI, run the command, file delete license <name of license file>.
Step 2 Restart the Cisco License Manager service in Cisco Unified Serviceability.
Step 3 To save the received license file, use Microsoft Outlook.
Step 4 In Cisco Unified Communications Manager Administration, upload the saved license file, as described in the "Uploading a License File" section of the Cisco Unified Communications Manager Administration Guide.
For More Information
•"Licensing" chapter, Cisco Unified Communications Manager System Guide
CSCsr80287 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 by 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.
Partition Size Limitations When You Upgrade from a 5.x Release to a 6.x Release
Cisco Unified Communications Manager 5.x releases create disk partitions of a fixed size. If you install a 5.x release on a server with more disk space than is required by the fixed partitions, the partitions still get created at the fixed size.
When you upgrade such a server from a 5.x release to a 6.x release, the disk partitions remain at the fixed size. If you perform a fresh installation of a 6.x release, the disk partitions get created as percentages of the available disk space, so your server will use all the available disk space effectively.
Note Likelihood of getting low active partition disk space alerts, if upgrading from 5.x to 6.1(4) with lots of locales, is low because of improvements made in 6.1(4)
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 When you attempt to delete a server from the Server Configuration window, a message that is similar to the one in the preceding paragraph displays. If you click OK, the server gets deleted from the Cisco Unified CM database and is not available for use.
Before you delete a server, consider the following information:
•Cisco Unified CM Administration does not allow you to delete the first node in the cluster, but you can delete any subsequent node.
•Cisco recommends that you do not delete any node that has Cisco Unified CM running on it, especially if the node has devices, such as phones, registered with it.
•Although dependency records exist for the subsequent nodes, the records do not prevent you from deleting the node.
•If any call park numbers are configured for Cisco Unified CM on the node that is being deleted, the deletion fails. Before you can delete the node, you must delete the call park numbers in Cisco Unified CM Administration.
•If a configuration field in Cisco Unified CM Administration contains the IP address or host name for a server that you plan to delete, update the configuration before you delete the server. If you do not perform this task, features that rely on the configuration may not work after you delete the server; for example, if you enter the IP address or host name for a service parameter, enterprise parameter, service URL, directory URL, IP phone service, and so on, update this configuration before you delete the server.
•If an application GUI, for example, Cisco Unity, Cisco Unity Connection, and so on, contains the IP address or hostname for the server that you plan to delete, update the configuration in the corresponding GUIs before you delete the server. If you do not perform this task, features that rely on the configuration may not work after you delete the server.
•The system may automatically delete some devices, such as MOH servers, when you delete a server.
•Before you delete a node, Cisco recommends that you deactivate the services that are active on the subsequent node. Performing this task ensures that the services work after you delete the node.
•Changes to the server configuration do not take effect until you restart Cisco Unified CM. For information about restarting the Cisco CallManager service, refer to the serviceability documentation for Cisco Unified CM.
•To ensure that database files get updated correctly, you must reboot the cluster after you delete a server.
•After you delete the node, access Cisco Unified Reporting to verify Cisco Unified CM removed the node from the cluster. In addition, access Cisco Unified Reporting, RTMT, or the CLI to verify that database replication is occurring between existing nodes; if necessary, repair database replication between the nodes.
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:
Step 1 In Cisco Unified CM Administration, add the server by choosing System > Server.
Step 2 After you add the subsequent node to Cisco Unified CM Administration, perform an installation on the server by using the disk that Cisco provided in your software kit.
Tip For example, if you have a version 6.1(4) disk, perform a 6.1(4) installation on the node. If you have a disk with a compatible version of 5.X on it, for example, use the disk to install Cisco Unified CM on the subsequent node; during the installation, choose the Upgrade During Install option when the installation displays the options.
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(4) 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 to installation documentation that supports your version of Unified CM.
Step 3 After you install Unified CM, configure the subsequent node, as described in the installation documentation that supports your version of Unified CM.
Step 4 Access the Cisco Unified Reporting, RTMT, or the CLI to verify that database replication is occurring between existing nodes; if necessary, repair database replication between the nodes.
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 makes the terminology compliant with the Bulk Administration user interface.
For More Information
For information on configuring additional features in Bulk Administration Tool, refer to the BAT documentation for Cisco Unified CM.
Basic Uninterruptible Power Supply (UPS) Integration
When Cisco Unified Communications Manager 6.1(4) 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 that 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.
Strict Version Checking
Disaster Recovery System adheres to strict version checking and allows restore only between matching versions of Cisco Unified Communications Manager.
Note Make sure that the restore runs on the same Cisco Unified Communications Manager version as the backup. The Disaster Recovery System supports only matching versions of Cisco Unified Communications Manager for restore.
Consider the following examples of restore to understand strict version checking:
Table 2 Restore Examples
From version To version Allowed / Not allowed
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 Cisco Unified Serviceability from Cisco Unified OS Administration. The window 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-messaging 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 Unified CM server uses the diversion header to choose a mailbox.
CTL Client 5.0 Plug-In Installation Note
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:
Step 1 Download Windows Installer Cleanup Utility at the following URL:
Step 2 Install the utility on your PC.
Step 3 Run the utility.
Step 4 Find eToken rte3.0 in the list of programs and remove it.
Step 5 Proceed with CTL Client installation.
Out-of-Service Nodes and Cisco License Manager
After an upgrade from Cisco Unified CallManager Release 5.1(x) to Cisco Unified Communications Manager 6.1(4), apply the 6.x software license. Restart Unified CM services on all nodes. Cisco Unified Communications Manager and all services start, except Cisco License Manager. Attempts to manually restart Cisco License Manager do not succeed.
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 to indicate 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 that was 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 gets 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.
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=.
Database Replication When You Revert 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 that reminds you about the requirement to reset database replication if you are reverting to an older product release. The caveats CSCsl57629 and CSCsl57655 also document this behavior.
For information about the utils dbreplication clusterreset, utils dbreplication dropadmindb, and utils dbreplication forcedatasyncsub commands, see the Command Line Interface Reference Guide for Cisco Unified Communications Solutions Release 7.0(1) document at http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/cli_ref/7_0_1/cli_ref.html.
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 you are installing RTMT. To continue, select Allow.
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 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.
Serviceability Session Timeout is 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 it indicates that the session timed out and redirects you to the login window. After you log in again, you may need to repeat those changes. This behavior occurs in the Alarm, Trace, Service Activation, Control Center, and SNMP windows.
If you know that the session has been idle for more than 30 minutes, log out by 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 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.  Check the type of device specified in fkDevice_DualMode. Remote Destinations 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 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.
Configuring the Hostname/IP Address for the Cisco Unified Communications Manager Server
Table 3 lists the locations where you can configure a host name for the Cisco Unified Communications Manager server, the allowed number of characters for the host name, and the recommended first and last characters for the host name. Be aware that, if you do not configure the host name correctly, some components in Cisco Unified Communications Manager, such as the operating system, database, installation, and so on, may not work as expected.
Caution Before you change the host name or IP address for any locations that are listed in Table 3, refer to Changing the IP Address and Host Name for Cisco Unified Communications Manager 5.x and 6.x Servers. Failing to update the host name or IP address correctly after it is configured may cause problems for Cisco Unified Communications Manager.
Tip The host name must follow the rules for ARPANET host names. Between the first and last character of the host name, you can enter alphanumeric characters and hyphens.
Before you configure the host name in any of the locations in Table 3, review the following information:
•The Host Name/IP Address field in the Server Configuration window, which supports device-to-server, application-to-server, and server-to-server communication, allows you to enter an IPv4 address in dotted decimal format or a host name.
After you install Cisco Unified Communications Manager on the publisher database server, the host name for the publisher automatically displays in this field. Before you install Cisco Unified Communications Manager on the subscriber server, enter either the IP address or the host name for the subscriber server in this field on the publisher database server.
In this field, only configure a host name if Cisco Unified Communications Manager can access the DNS server to resolve host names to IP addresses; make sure that you configure the Cisco Unified Communications Manager name and address information on the DNS server.
Tip In addition to configuring Cisco Unified Communications Manager information on the DNS server, you enter DNS information during the Cisco Unified Communications Manager installation.
•During the Cisco Unified Communications Manager installation of the publisher database server, you enter the host name, which is mandatory, and IP address of the publisher server to configure network information; that is, if you want to use static networking.
During the Cisco Unified Communications Manager installation on the subscriber server, you enter the hostname and IP address of the publisher database server, so Cisco Unified Communications Manager can verify network connectivity and publisher-subscriber validation. Additionally, you must enter the host name and the IP address for the subscriber server. When the Cisco Unified Communications Manager installation prompts you for the host name of the subscriber server, enter the value that displays in the Server Configuration window in Cisco Unified Communications Manager Administration; that is, if you configured a host name for the subscriber server in the Host Name/IP Address field.
•"Server Configuration" chapter, Cisco Unified Communications Manager Administration Guide
•Installing Cisco Unified Communications Manager, Release 6.1(1)
•Cisco Unified Communications Operating System Administration Guide
•Command Line Interface Reference Guide for Cisco Unified Solutions
•Changing the IP Address and Host Name for Cisco Unified Communications Manager 5.x and 6.x Servers
Serviceability Limitations When You Modify the IP Address
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 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.
SIP Network/IP Address Field that is 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.
Network Time Protocol Version 4
To avoid potential compatibility, accuracy, and network jitter problems, the external NTP servers that you specify for the primary node should be NTP v4 (version 4).
CSCtj61834 MLPP Default Domain Name Displays MLPP ID Value
When you configure the MLPP Domain Name in Cisco Unified Communications Manager, the default name for MLPP Domain Name displays the MLPP ID value 000000 instead of Default as stated on the help page.
CSCtr84167 Block Offnet to Offnet Transfer
When you enable the service parameter "Block Offnet to Offnet Transfer" and make a blind transfer with Cisco Unity Connection, the Q.931 SETUP message which Cisco Unified Communications Manager sends to the PSTN gateway for an outbound PRI call still reaches the gateway. This transfer results in a dropped call.
CSCtx86215 Database Replication
This section of the Cisco Unified Communications Manager System Issues chapter in the Troubleshooting Guide for Cisco Unified Communications Manager requires this addition:
Extension Mobility does not work when database replication breaks between the Unified CM node running Extension Mobility and the Unified CM node to which the phone is registered.
CSCuc10415 Tip for Adding a New Server
The following tip needs to be added to the "Server settings" topic in the Cisco Unified Communications Manager Administration Guide.
To avoid errors, Cisco recommends that you add a server to the system with a name that has less than 47 characters. Then, update the server name to the target length.
CSCuc79185 Device Mobility Calling Search Space is Used When Device CSS is <none>
The following note is missing from the "Phone Settings" topic in the Cisco Unified Communications Manager Administration Guide:
When set to <none>, Unified CM uses the device mobility calling search space, which is configured on the device pool.
CSCtw44980 Missing Exceptions for Voice-Mail Pilot
The following information is missing for the Voice Mail Pilot Name field description in the "Voice-Mail Pilot Settings" topic in the Cisco Unified Communications Manager Administration Guide:
Allowed characters are numeric (0-9), plus (+), asterisk (*), and pound (#).
CSCud34740 Application User AXL Password Must Not Contain Special Characters
The following note is missing from the Application User Settings topic in the Cisco Unified Communications Manager Administration Online Help:
Note Do not use special characters when you create an AXL password for an application user.
CSCud70447 Missing Etoken Recovery Steps in Troubleshooting Guide
The Cisco Unified Communications Manager Troubleshooting Guide is missing the following procedure for troubleshooting if you lose all security tokens (etokens):
Perform the following procedure if you lose the security tokens and you need to update the CTL file.
Tip Perform the following procedure during a scheduled maintenance window, because you must reboot all servers in the cluster for the changes to take effect.
Step 1 On every Cisco Unified CallManager, Cisco TFTP, or alternate TFTP server, verify that CTLFile.tlv exists from the OS SSH command line.
file list tftp CTLFile.tlv
Step 2 Delete CTLFile.tlv.
file delete tftp CTLFile.tlv
Step 3 Repeat step 1 and step 2 for every Cisco Unified CallManager, Cisco TFTP, and alternate TFTP server.
Step 4 Obtain at least two new security tokens.
Step 5 By using the Cisco CTL client, create the CTL File, as described in "Installing the Cisco CTL Client" and "Configuring the Cisco CTL Client".
Tip If the clusterwide security mode is in mixed mode, the Cisco CTL client displays the message No CTL File exists on the server but the CallManager Cluster Security Mode is in Mixed Mode. For the system to function, you must create the CTL File and set CallManager Cluster to Mixed Mode. Click OK; then, choose Set CallManager Cluster to Mixed Mode and complete the CTL file configuration.
Step 6 Reboot all the servers in the cluster.
Step 7 After you create the CTL file on all the servers and reboot all servers in the cluster, delete the CTL file from the phone, as described in "Deleting the CTL File on the Cisco Unified IP Phone".
New and Changed Information
This section contains information on the following topics:
Installation, Upgrade, and Migration
The following sections describe the changes for installation, upgrade, and migration in Cisco Unified Communications Manager 6.1(4):
System History Log for Cisco Unified Communications Manager
This system history log provides a central location for getting a quick overview of the initial system install, system upgrades, Cisco option installations, DRS backups and DRS restores, as well as switch version and reboot history.
This section provides a description of the system history log feature.
The system history log exists as a simple ASCII file, system-history.log, and the data does not get maintained in the database. Because it does not get excessively large, the system history file does not get rotated.
The system history log provides the following functions:
•Logs the initial software installation on a server.
•Logs the success and failure or cancellation of every software upgrade (Cisco option files and patches).
•Logs every DRS backup and restore that is performed.
•Logs every invocation of Switch Version that is issued through either the CLI or the GUI.
•Logs every invocation of Restart and Shutdown that is issued through either the CLI or the GUI.
•Logs every boot of the system. If not correlated with a restart or shutdown entry, the boot results from a manual reboot, power cycle, or kernal panic.
•Maintains a single file that contains the system history, since initial installation or since feature availability.
•Exists in the install folder. Access the log from the CLI by using the file commands and by using the Real-Time Monitoring Tool (RTMT).
System History Log Fields
Each system history log entry contains the following fields:
•<timestamp> <userid> <action> <description> <start>
The log also displays a common header which contains information about product name, product version and kernel image.
Product Name - Cisco Unified Communications Manager
Product Version - 18.104.22.168000-9023
Kernel Image - 2.6.9-67.EL
The system history log fields can contain the following values:
•timestamp—Displays the local time and date on the server with the format mm/dd/yyyy hh:mm:ss.
•userid—Displays the user name of the user who invokes the action.
•action—Displays one of the following actions:
–Upgrade During Install
–Cisco Option Install
•description—Displays one of the following messages:
–Version: Displays for the Install, Windows Upgrade, Upgrade During Install, Upgrade, and ServerPak Install actions.
–Cisco Option file name: Displays for the Cisco Option Install action.
–Timestamp: Displays for the DRS Backup and DRS Restore actions.
–Active version to inactive version: Displays for the Switch Version action.
–Active version: Displays for the System Restart, Shutdown, and Boot actions.
•result—Displays the following results:
–Success or Failure
Example 1 shows a sample of the system history log.
Example 1 System History Logadmin:file dump install system-history.log=======================================Product Name - Cisco Unified Communications ManagerProduct Version - 22.214.171.12401-117Kernel Image - 2.4.21-47.EL.cs.3BOOT=======================================07/25/2008 14:20:06 | root: Install 126.96.36.19901-117 Start07/25/2008 14:50:38 | root: Boot 188.8.131.5201-117 Start07/25/2008 15:05:37 | root: Install 184.108.40.20601-117 Success07/25/2008 15:05:38 | root: Boot 220.127.116.1101-117 Start07/30/2008 10:08:56 | root: Upgrade 18.104.22.16801-126 Start07/30/2008 10:46:31 | root: Upgrade 22.214.171.12401-126 Success07/30/2008 10:46:43 | root: Switch Version 126.96.36.19901-117 to 188.8.131.5201-126 Start07/30/2008 10:48:39 | root: Switch Version 184.108.40.20601-117 to 220.127.116.1101-126 Success07/30/2008 10:48:39 | root: Restart 18.104.22.16801-126 Start07/30/2008 10:51:27 | root: Boot 22.214.171.12401-126 Start08/01/2008 16:29:31 | root: Restart 126.96.36.19901-126 Start08/01/2008 16:32:31 | root: Boot 188.8.131.5201-126 Start
You can access the system history log by using the CLI file command; for example:
•file view install system-history.log
•file get install system-history.log
Cisco Unified Communications Manager Administration Configuration Tips
No Cisco Unified Communications Manager Administration configuration tips exist for this feature.
No GUI changes exist for this feature.
Service Parameter and Enterprise Parameter Changes
No service parameter and enterprise parameter changes exist for this feature.
Installation/Upgrade (Migration) Considerations
No installation or upgrade consideration exist for this feature.
To access the system history log in RTMT, navigate to RTMT Trace Collection:
RTMT > Trace Log Collection
No BAT considerations exist for this feature.
No CAR/CDR considerations exist for this feature.
No security considerations exist for this feature.
AXL and CTI Considerations
No AXL and CTI considerations exist for this feature.
No user tips exist for this feature.
For More Information
For more information about using the CLI, see the Cisco Unified Communications Operating System Administration Guide or the Command Line Interface Reference Guide for Cisco Unified Solutions.
For more information about RTMT, see the Cisco Unified Communications Manager Real-Time Monitoring Tool Administration Guide.
This section highlights some documentation changes for the 6.1(4) release. This section does not contain all the documentation updates for the 6.1(4) release. Use this section in conjunction with the information in the "New and Changed Information" section and the "Documentation Updates" section.
For information on features that are introduced in Cisco Unified Communications Manager 6.1(4), see the Release Notes for Cisco Unified Communications Manager Release 6.1(4). For a list of documents that are updated for Cisco Unified Communications Manager 6.1(4), refer to the Cisco Unified Communications Manager Documentation Guide for Release 6.1(4).
When you view online help in Cisco Unified Communications Manager 6.1(4), be aware that the online help did not get updated for 6.1(4). The following graphical user interfaces (GUIs) contain online help:
•Cisco Unified Communications Manager Administration, which displays online help from 6.1(1)
•Cisco Unified Reporting, which displays online help from 6.1(1)
•Cisco Unified Serviceability, which displays online help from 6.1(1)
•Cisco Unified Communications Operating System Administration, which displays online help from 6.1(1)
Command Line Interface
The Command Line Interface Reference Guide for Cisco Unified Communications Solutions Release 6.1(3) does not contain updated information for the show memory command. Use the following updated information.
This command displays information about the server memory.
•count—Displays the number of memory modules on the system.
•modules—Displays detailed information about all the memory modules.
•size—Displays the total amount of memory.
Cisco Unified Communications Manager Administration
This section contains information on the following topics:
New and Updated Enterprise and System Parameters
The following sections contain information on new and updated enterprise and service parameters:
To access the enterprise parameters in Cisco Unified Communications Manager Administration, choose System > Enterprise Parameters. To display the help for the service parameter, click the name of the enterprise parameter in the window.
Cisco Unified Communications Manager 6.1(4) does not contain any new enterprise parameters.
To access the service parameters in Cisco Unified Communications Manager Administration, choose System > Service Parameters. Choose the server and the service name that the parameter supports. For some parameters, you may need to click Advanced to display the service parameter. To display the help for the service parameter, click the name of the service parameter in the window.
•The SIP Interoperability Enabled service parameter, which supports the Cisco CallManager service, determines whether Cisco Unified Communications Manager supports Session Initiation Protocol (SIP) for SIP stations and SIP trunks. Devices that run SIP, for example, phones and trunks, require that you set this parameter to True; when you set this parameter to False, Cisco Unified Communications Manager ignores SIP messages, and SIP devices do not function; that is, phones that run SIP cannot register with Cisco Unified Communications Manager and SIP trunks cannot interact with Cisco Unified Communications Manager. The default value specifies True. You must restart the Cisco CallManager service if you change the value of this parameter.
This section contains information on the following menus in Cisco Unified Communications Manager Administration:
No changes exist for the main window.
No changes exist for the System menu.
No changes exist for the Call Routing menu.
No changes exist for the Media Resources menu.
No changes exist for the Voice Mail menu.
No changes exist for the Device menu.
No updates or new fields exist for this menu.
No updates or new fields exist for this menu.
No changes exist for the Bulk Administration.
Cisco Unified Communications Manager Features and Applications
This section contains information on the following Cisco Unified Communications Manager Administration features and applications:
As of Release 6.1(4), if the system administrator changes a user username, preferred location, or password (assistants), that user does not get logged off. For user-ID changes, neither the manager nor his or her assistant gets logged off when that manager user ID is changed; however, an assistant gets logged off the assistant phone and the Assistant Console when that assistant user ID is changed.
LDAP Synchronization and Authentication with Active Directory 2003 sp2 on VMWare ESX 3.5 Update 2
The Cisco DirSync service in Cisco Unified Communications Manager 6.1(4) can connect to a Windows Server Active Directory 2003 sp2 (or later) in a VMWare ESX 3.5 Update 2 (or later) session that complies with Microsoft recommended deployment guidelines for VMware ESX 3.5 Update 2. For information on deployment guidelines, refer to the Microsoft website.
After you install Active Directory 2003 sp2 (or later) on a VMWare ESX 3.5 Update 2 (or later) server, you can configure LDAP synchronization and authentication. Make sure that you activate the Cisco DirSync service in Cisco Unified Serviceability before you configure synchronization. For more information on synchronization and authentication, refer to the Cisco Unified Communications Manager System Guide and the Cisco Unified Communications Manager Administration Guide.
Ensure the following conditions are met:
•The VMWare image has 15GB or more of hard drive space allocated.
•The OS that is being installed represents 2003.1.2a or greater; Windows 2000 does not get supported
•The disc from which install occurs must be either HP or IBM install disc;
•Install VMware ESX Server: 3.5.0 and follow by Windows 2003 and AD on top of it.
Redirected Dialed Number Identification Service and Diversion Header
Release 6.1(4) adds the Redirected Dialed Number Identification Service (RDNIS) and diversion header capability for certain calls that use the Cisco Unified Mobility Mobile Connect feature.
The RDNIS/diversion header for Mobile Connect enhances this Cisco Unified Mobility feature to include the RDNIS or diversion header information on the forked call to the mobile device. Service providers and customers use the RDNIS for correct billing of end users who make Cisco Unified Mobility Mobile Connect calls.
For Mobile Connect calls, the Service Providers use the RDNIS/diversion header to authorize and allow calls to originate from the enterprise, even if the caller ID does not belong to the enterprise Direct Inward Dial (DID) range.
Example Use Case
Consider a user that has the following setup:
Desk phone number specifies 89012345.
Enterprise number specifies 4089012345.
Remote destination number specifies 4088810001.
User gets a call on desk phone number (89012345) that causes the remote destination (4088810001) to ring as well.
If the user gets a call from a nonenterprise number (5101234567) on the enterprise number (4089012345), the user desk phone (89012345) rings, and the call gets extended to the remote destination (4088810001) as well.
Prior to the implementation of the RDNIS/diversion header capability, the fields populated as follows:
Calling Party Number (From header in case of SIP): 5101234567
Called Party Number (To header in case of SIP): 4088810001
After implementation of the RDNIS/diversion header capability, the Calling Party Number and Called Party Number fields populate as before, but the following additional field gets populated as specified:
Redirect Party Number (Diversion Header in case of SIP): 4089012345
Thus, the RDNIS/diversion header specifies the enterprise number that is associated with the remote destination.
Configuration in Cisco Unified Communications Manager Administration
To enable the RDNIS/diversion header capability for Mobile Connect calls, ensure the following configuration takes place in Cisco Unified Communications Manager Administration:
All gateways and trunks must specify that the Redirecting Number IE Delivery — Outbound check box gets checked.
In Cisco Unified Communications Manager Administration, you can find this check box by following the following menu paths:
For H.323 and MGCP gateways, execute Device > Gateway and find the gateway that you need to configure. In the Call Routing Information - Outbound calls pane, ensure that the Redirecting Number IE Delivery - Outbound check box gets checked. For T1/E1 gateways, check the Redirecting Number IE Delivery - Outbound check box in the PRI Protocol Type Information pane.
•For SIP trunks, execute Device > Trunk and find the SIP trunk that you need to configure. In the Outbound Calls pane, ensure that the Redirecting Diversion Header Delivery - Outbound check box gets checked.
Bulk Administration Tool
This section contains information on the following topic:
Inserting User Device Profiles and Phones into Cisco Unified Communications Manager
While you insert user device profiles for user devices and inserting phones into Cisco Unified Communications Manager, the following check boxes get enabled for selection after you have checked the Override the existing configuration check box.
•Delete all existing speed dials before adding new speed dials.
•Delete all existing BLF Speed Dials before adding new BLF Speed Dials.
•Delete all existing Subscribed Services before adding new services.
Note Check the check box(es) to delete all existing Speed Dials, BLF Speed Dials, or Subscribed Services records and add new records. Leave the check box(es) unchecked if you want to append these to existing records.
The following sections contain information on how to obtain the latest resolved caveat information and descriptions of open caveats of severity level 1, 2, and 3.
Caveats describe unexpected behavior on a Cisco Unified Communications Manager server. Severity 1 caveats represent the most serious caveats, severity 2 caveats represent less serious caveats, and severity 3 caveats represent moderate caveats.
You can find the latest resolved caveat information for Cisco Unified Communications Manager Release 6.1(4) by using Bug Toolkit, which is an online tool that is available for customers to query defects according to their own needs.
From http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs perform the following:
Step 1 In the Select Product Category list, double-click Voice and Unified Communications.
Step 2 In the Select Product list, double-click Cisco Unified Communications Manager (CallManager).
Step 3 From the Version drop-down list, select the Unified CM version train for which you want to see defects (for example, for Unified CM Release 6.1(3x), select 6.1.).
Step 4 Under Advanced Options, select Use custom settings for severity, status, and others.
Step 5 In the options that display, click the Open check box to deselect that option.
Now, the only option that will get acted upon is the Fixed option.
Step 6 Click Search.
Tip You need an account with Cisco.com (Cisco Connection Online) to use the Bug Toolkit to find open and resolved caveats of any severity for any release.
To access the Bug Toolkit, log on to http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs.
Using Bug Toolkit
Known problems (bugs) get graded according to severity level. These release notes contain descriptions of
•All severity level 1 or 2 bugs.
•Significant severity level 3 bugs.
You can search for problems by using the Cisco Software Bug Toolkit.
To access Bug Toolkit, you need the following items:
•Cisco.com user ID and password
To use the Software Bug Toolkit, follow these steps:
Step 1 To access the Bug Toolkit, go to http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs.
Step 2 Log in with your Cisco.com user ID and password.
Step 3 To look for information about a specific problem, enter the bug ID number in the "Search for Bug ID" field; then, click Go.
For information about how to search for bugs, create saved searches, create bug groups, and so on, click Help in the Bug Toolkit window.
The "Open Caveats as of July 9, 2009" section describes possible unexpected behaviors, supported by component, in Cisco Unified Communications Manager Release 6.1(4).
Tip For more information about an individual defect, click the associated Identifier in "Open Caveats as of July 9, 2009" section to access the online record for that defect, including workarounds.
Understanding the Fixed-in Version and the Integrated-in Fields in the Online Defect Record
When you open the online record for a defect, you may see data in the "First Fixed-in Version" or "Integrated-in" fields. The information that displays in these fields identifies the list of Cisco Unified Communications Manager interim versions in which the defect was fixed. These interim versions then get integrated into Cisco Unified Communications Manager releases.
Some more clearly defined versions include identification for Engineering Specials (ES) or Service Releases (SR); for example 03.3(04)ES29 and 04.0(02a)SR1. However, the version information that displays for the Cisco Unified Communications Manager maintenance releases may not be as clearly identified.
The following examples show how you can decode the maintenance release interim version information. These examples show you the format of the interim version along with the corresponding Cisco Unified Communications Manager release that includes that interim version. You can use these examples as guidance to better understand the presentation of information in these fields.
•005.000(000.123) = Cisco Unified Communications Manager Release 5.0(1)
•005.000(001.008) = Cisco Unified Communications Manager Release 5.0(2)
•005.001(002.201) = Cisco Unified Communications Manager Release 5.1(3)
•006.000(000.123) = Cisco Unified Communications Manager Release 6.0(1)
•006.001(003.150) = Cisco Unified Communications Manager Release 6.1(4)
Note Because defect status continually changes, be aware that Open Caveats as of July 9, 2009 reflects a snapshot of the defects that were open at the time this report was compiled. For an updated view of open defects, access Bug Toolkit and follow the instructions as described in the "Using Bug Toolkit" section.
Tip Bug Toolkit requires that you have an account with Cisco.com (Cisco Connection Online). By using the Bug Toolkit, you can find caveats of any severity for any release. Bug Toolkit may also provide a more current listing than this document provides. To access the Bug Toolkit, log on to http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs.
Open Caveats as of July 9, 2009
The following list contains the caveat that was open on June 17, 2009.
Headline: Unicast Music on Hold May Not Play.
Headline: User cannot specify two IPSEC policies to the same endpoint in Cisco Unified CM.
Component : cpi-security
Headline: Critical sshd: Fatal: Write failed: Peer reset connection.
Headline: Incorrect corporate DIR characters with Turkish locale input on 7940/7960.
Headline: Pulling drives for upgrades of appliance-based application does not get supported.
Headline: CFA gets reported as activated for all lines after Extension Mobility login.
Headline: RouteListExhausted Alert gets raised ignoring Stop Routing Service Params.
Headline: Database Replication Setup Must Be *MUCH* Faster.
Headline: BW partially reserved: Ph in LOC-1 to VXMLGW in LOC-2 via SIP/H323 trunk.
Headline: Delayed Media Setup w/ICT/GK Internode Call and Shared Lines (43 Phones).
Headline: Handle video channel failure properly so that call won't fail.
Headline: RTMT: create directory button disabled.
Headline: Replication not working after running "clusterreset".
Headline: DND softkey is not getting displayed for the shared line manager.
Headline: Updating the DPark number to Range should not update the BLF key.
Headline: Workaroung for DSCP in UDP signalling is 0 if >CS4 selected on admin GUI.
Headline: Wrong MNC value getting reported during mismatch login.
Headline: JPN:Katakana Strings on IP Phone's Personal Directory pages.
Headline: H323 ended 500 Internal Server Error Call with normal clearing.
Headline: wrong UnmodifiedCallingParty is getting reported during a GW call.
Headline: PMR 85079: JTAPI unable to failover to Sub CTI manager.
Headline: Desk phone stays 'remote-in-use' after remote destination transfers call.
Headline: CTI Reports a ghost line when IPMA enumerates lines on device.
Headline: unicast moh did not played in timeing/race condition.
Headline: Remove logic to clear networkLocale ,mrg list in device pool.
Headline: Dependency Records for Route Lists not available in CUCM 6.1.
Headline: Product Specific Configuration Layout section missing from device page.
The Updates to Cisco Unified Communications Manager 6.1(1) Documentation document provides information about documentation omissions, errors, or updates that are not included in the documentation that supports the Unified CM 6.1(x) release train. To obtain this document, go to the following URL:
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0.
CCDE, CCENT, CCSI, Cisco Eos, Cisco HealthPresence, Cisco Ironport, the Cisco logo, Cisco Lumin, Cisco Nexus, Cisco Nurse Connect, Cisco Stackpower, Cisco StadiumVision, Cisco TelePresence, Cisco Unified Computing System, Cisco WebEx, DCE, Flip Channels, Flip for Good, Flip Mino, Flip Video, Flip Video (Design), Flipshare (Design), Flip Ultra, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn, Cisco Store, and Flip Gift Card are service marks; and Access Registrar, Aironet, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, EtherFast, EtherSwitch, Event Center, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, iQuick Study, IronPort, the IronPort logo, LightStream, Linksys, MediaTone, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerPanels, ProConnect, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0907R)