Table Of Contents
Release notes for Cisco Unified Presence release 8.6(5)
June 11, 2013
These release notes describe requirements, restrictions, and caveats for Cisco Unified Presence Release 8.6(5).
Note To view the release notes for previous versions of Cisco Unified Presence, go to the following URL: http://www.cisco.com/en/US/products/ps6837/prod_release_notes_list.html
Cisco Unified Presence collects information about user availability, such as whether users are using communications devices (for example, a phone) at a particular time. Cisco Unified Presence can also collect information about individual user communications capabilities, such as whether web collaboration or video conferencing is enabled. Applications such as Cisco Jabber and Cisco Unified Communications Manager use this information to improve productivity among employees, that is, to help employees connect with colleagues more efficiently and determine the most effective way for collaborative communication.
These release notes describe new features, requirements, restrictions, and caveats for Cisco Unified Presence Release 8.6(5). These release notes are updated for every maintenance release but not for patches or hot fixes.
Before you install Cisco Unified Presence, Cisco recommends that you review the "Related documentation" section for information about the documentation available for Cisco Unified Presence.
Hardware server requirements
Note For OVA template details and location, see http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Downloads_%28including_OVA/OVF_Templates%29#Cisco_Unified_Presence.
The Cisco Unified Presence system is a software product that is loaded onto a hardware server. The hardware server must meet the following requirements:
•One of the following server models:
–Cisco 7800 Series Media Convergence Server (MCS) listed in the Hardware and Software Compatibility Information for Cisco Unified Presence. Go to Cisco.com for the latest information:
Note Cisco Unified Presence does not support MCS-xxxx-I1-IPC1 or MCS-xxxx-H1-IPC1 servers. However, a bridged upgrade is available to customers who need to migrate from any discontinued hardware, except for the following servers: MCS-7825-H1-IPC1, MCS-7825-I2-IPC1, MCS-7825-I1-IPC1, MCS-7825-I2-IPC2. For details about the unsupported hardware and the bridged upgrade, see the Upgrade Guide for Cisco Unified Presence Release 8.6 here:
–Cisco-approved, customer-provided third-party server that is the exact equivalent of one of the supported Cisco MCS servers. Go to http://www.cisco.com/go/swonly.
–Cisco Unified Computing System B-series blades or Cisco Unified Computing System C-series rack-mount servers. For information about these Cisco Unified Computing System servers, see the Hardware and Software Compatibility Information for Cisco Unified Presence Release 8.x here:
•Keyboard, mouse, and monitor
Note Additional server requirements, such as port and IP address requirements, are described in Port Usage Information for Cisco Unified Presence.
The Cisco Unified Presence installer checks for the availability of the DVD-ROM drive, sufficient hard drive and memory size, and sufficient CPU type and speed.
Cisco Unified Presence supports bridged upgrades from any of the following servers:
•MCS-7845-H2-IPC1 (only if each of the two disks has less than 72 GB of storage space, otherwise it is fully supported)
The bridged upgrade allows you to create a Disaster Recovery System backup on the discontinued hardware. You can then restore the DRS backup on supported hardware after you complete a fresh Cisco Unified Presence installation on the supported hardware. If you attempt an upgrade on discontinued hardware, Cisco Unified Presence displays a warning on the interface and on the CLI, informing you that Cisco Unified Presence only supports the functionality to create a DRS backup on this server.
Server software requirements
The Cisco Unified Presence server runs on the Cisco Linux-based operating system. This operating system is included with the application.
Use Microsoft Internet Explorer Version 6.0 or a later release, or Mozilla Firefox Version 3.0 or a later release, to access these interfaces: Cisco Unified Presence Administration, Cisco Unified Serviceability, and Cisco Unified Operating System Administration.
Note Cisco Unified Presence does not currently support Safari or Google Chrome on the Mac OS or Microsoft Windows.
How to use Hypertext Transfer Protocol over Secure Sockets Layer
Hypertext Transfer Protocol over Secure Sockets Layer (HTTPS), which secures communication between the browser client and the Apache Tomcat web server, uses a certificate and a public key to encrypt the data that is transferred over the Internet. HTTPS, which ensures the identity of the server, supports applications such as Cisco Unified Serviceability. HTTPS also ensures that the user sign-in password is transported securely over the web.
HTTPS for Internet Explorer
The first time you access Cisco Unified Presence Administration or other Cisco Unified Presence Secure Sockets Layer (SSL)-enabled virtual directories after a Cisco Unified Presence installation or upgrade, a Security Alert dialog box asks whether you trust the server. When the dialog box displays, you must respond in one of the following ways:
•By selecting Yes, you select to trust the certificate for the current web session only. If you trust the certificate for the current session only, the Security Alert dialog box displays each time that you access the application: that is, until you install the certificate in the trusted folder.
•By selecting View Certificate > Install Certificate, you indicate that you intend to perform certificate installation tasks, so you always trust the certificate. If you install the certificate in the trusted folder, the Security Alert dialog box does not display every time you access the web application.
•By selecting No, you cancel the action. No authorization occurs, and you cannot access the web application. To access the web application, you must select Yes or install the certificate using the View Certificate > Install Certificate option.
Note The system issues the certificate using the hostname. If you attempt to access a web application using the IP address, the Security Alert dialog box displays, even though you installed the certificate on the client.
Saving the certificate to the trusted folder
You can save the CA Root certificate in the trusted folder, so the Security Alert dialog box does not display each time that you access the web application.
Step 1 Perform the required steps depending on the Internet browser you are using:
Installation and upgrade notes
You must perform the Cisco Unified Presence Release 8.6(x) upgrade before you perform the Cisco Unified Communications Manager Release 8.6(x) upgrade. Cisco does not support Cisco Unified Presence 8.0(x) servers running with Cisco Unified Communications Manager Release 8.5 or 8.6.
If you upgrade from Release 7.0(x) to Release 8.6(x), you require a new software version license for each Cisco Unified Presence server in your deployment. You must order a separate software version license for each Cisco Unified Presence server. However, you need to upload the license to the first node in a cluster. For information about Cisco Unified Presence licensing modes and requirements, see the Installation Guide for Cisco Unified Presence Release 8.6 here:
You can run this release of Cisco Unified Presence on a VMware virtual machine deployed on approved Cisco Unified Computing server hardware. For information about supported servers, see Hardware and Software Compatibility Information for Cisco Unified Presence Release 8.x. For information about the VMware licensing requirements, see the License Activation for Cisco UC on UCS Docwiki here:
Before you upgrade from Cisco Unified Presence Release 8.0(x), 8.5(x), or 8.6(x) to Release 8.6(5), Cisco strongly advises that you follow the recommended upgrade procedure in the Upgrade Guide for Cisco Unified Presence Release 8.6 here:
•Publisher node—Upgrade the Publisher node and switch the software to the new software release before you begin an upgrade and switch version on the Subscriber nodes. If the Cisco Unified Presence Administration GUI is operational on the Publisher node, it is safe to initiate an upgrade and switch version on the Subscriber node. Services on the Publisher will not start until the Subscribers are switched, restarted, and replication is successfully established on that cluster.
•High Availability User Support—Cisco Unified Presence Release 8.6(x) supports up to 45,000 Unified Communications mode users per cluster in a High Availability (HA) configuration across six nodes and up to 45,000 users per cluster in a non-HA configuration across three nodes. If, when you upgrade, you are left with a number of unsupported users, we recommend that you unlicense these surplus users on Cisco Unified Communications Manager before you perform the upgrade.
•Contact List Size—The default maximum value is 200; however you can configure this to a higher value, or configure 0 to set it to Unlimited. After you perform the upgrade, check that the contact list size for users has not reached the maximum value. If you have a large number of contacts per user, the number of users that a Cisco Unified Presence node supports is reduced.
•Platform Manager—You cannot use Platform Manager to upgrade to Cisco Unified Presence Release 8.6(5).
Upgrading to Cisco Unified Presence release 8.6(5)
Perform the following steps to upgrade from the following supported upgrade paths:
•Release 8.0(x) to Release 8.6(5)
•Release 8.5(x) to Release 8.6(5)
•Release 8.6(x) to Release 8.6(5)
Note Direct upgrades from Cisco Unified Presence Release 7.0(x) and earlier to Release 8.6(5) are not supported. You must first upgrade to another 8.x release, up to and including 8.6(3), and then perform a Refresh Upgrade. A Refresh Upgrade is significantly different from a Standard Upgrade. For more information, see the Upgrade Guide for Cisco Unified Presence 8.6. For more information about upgrading to Cisco Unified Presence Release 8.x, see the Upgrade Guide for Cisco Unified Presence:
Before you begin
•You can only download point releases of Cisco Unified Presence software from Cisco.com.
•Upgrades from 8.0(x) through to 8.6(3) require you to install a Cisco Options Package (COP) file on all nodes before you start the upgrade. Download the following COP file from Cico.com: ciscocm.cup.refresh_upgrade_v<latest_version>.cop
Step 1 Go to http://www.cisco.com/upgrade.
Step 2 Enter your software contract number.
Step 3 Select the CUP<pre-upgrade release>-8-6-U-K9= option to order. If you do not see this option, contact your Cisco Account Team or Reseller to resolve your Contract issue.
Step 4 Go to http://www.cisco.com/cisco/software/navigator.html.
Step 5 Navigate to Products > Voice and Unified Communications > Unified Communications Applications > Cisco Unified Presence > Cisco Unified Presence 8.6 > Unified Presence Server Updates.
Step 6 Download the complete ISO file: UCSInstall_CUP_220.127.116.1100-12.sgn.iso.
Use an md5sum utility to verify that the MD5 sum of the final file is correct:
You can upgrade the ISO image onto a remote server. Copy the ISO file (UCSInstall_CUP_18.104.22.16800-12.sgn.iso) to your FTP or SFTP server.
The complete Cisco Unified Presence documentation set, with the latest information for Release 8.6(x), is now available here on Cisco.com:
To search for documentation on any given release, we recommend that you use the Custom Google search capability that was introduced in the last release.
For more information, see the Deployment Guide for Cisco Unified Presence Release 8.6:
New and changed information
The following sections describe new features and changes that are pertinent to Cisco Unified Presence Release 8.6(5). The sections may include configuration tips, information about users, and where to find more information.
Enhanced Cisco Unified Presence deployment support
The enterprise-wide presence domain is no longer required to align with the DNS domain of any server. A Cisco Unified Presence deployment can have a common presence domain, while having nodes deployed across multiple DNS domains. If any Cisco Unified Presence node name is based on the hostname only, all Cisco Unified Presence nodes must share the same DNS domain. However, if all Cisco Unified Presence nodes within the deployment have a node name set to the FQDN or IP address for that node, the following deployment options are supported:
•Cisco Unified Presence clusters deployed in different DNS domain or subdomains
•Cisco Unified Presence nodes within a cluster deployed within different DNS domains or subdomains
•Cisco Unified Presence nodes within a cluster deployed in a DNS domain that is different to the associated Cisco Unified Communications Manager cluster
For more information, see the Deployment Guide for Cisco Unified Presence.
Bulk rename of contact IDs
The Cisco Unified Presence Bulk Administration Tool has been extended in Release 8.6(5) to support migrations where the SIP URI formats on Cisco Unified Presence and Lync/OCS/LCS differ. In Cisco Unified Presence Release 8.6(4) and earlier, you must change the SIP URI of all the migrating Lync/OCS/LCS users to match the Cisco Unified Presence SIP URI format before you migrate the first batch of users. From Cisco Unified Presence Release 8.6(5), you can change the SIP URI of migrating users just before each batch of users is migrated from Lync/OCS/LCS to Cisco Unified Presence. Cisco Unified Presence Bulk Administration Tool takes a CSV file with the list of migrated users as input and updates the contact lists for all users that have migrated users as contacts. For more information, see the Partitioned Intradomain Federation Guide for Cisco Unified Presence.
The following section contains information that may have been unavailable upon the initial release of documentation for Cisco Unified Presence Release 8.6(5).
CPU spike causes database connection failure
The following Cisco Unified Presence interfaces can become inaccessible due to database connectivity problems. When you attempt to log in to the following applications, the login will appear to hang and will not complete:
•Cisco Unified Presence Administration
•Cisco Unified Serviceability
•Cisco Unified Reporting
•Cisco Unified End User Options
This condition affects Cisco Unified Presence running in a virtualized environment where the virtual machine (VM) on which Cisco Unified Presence is running has only one CPU. A large CPU spike on the Cisco Unified Presence server can cause the database to become inaccessible. You can verify that you are experiencing this issue by performing the following procedure:
Step 1 From the Cisco Unified Presence CLI, execute the following command to view the database log file:
file view activelog /cm/log/informix/ccm.log
Step 2 Check the log file for entries similar to the following:
listener-thread: err = -25582: oserr = 0: errstr = : Network connection is broken.
To resolve this issue, add an additional CPU to the VM on which Cisco Unified Presence is running.
Using Bug Toolkit
Known problems (bugs) are graded according to severity level. These release notes contain descriptions for the following:
•All severity level 1 or 2 bugs
•Significant severity level 3 bugs
•All customer-found bugs
You can search for specific bugs using the Cisco Software Bug Toolkit.
Before you begin
To access Bug Toolkit, you need the following items:
•Cisco.com user ID and password
Step 1 To access the Bug Toolkit, go to http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs.
Step 2 Sign 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 select Go.
For information about how to search for bugs, create saved searches, and create bug groups, select Help on the Bug Toolkit page.
This section lists caveats that are resolved but that may be have been open in previous releases.
Bugs are listed in alphabetical order by component and then in numerical order by severity. Because defect status continually changes, be aware that this document reflects a snapshot of the defects that were resolved at the time this report was compiled. For an updated view of resolved defects, access the Bug Toolkit (see Using Bug Toolkit).
The caveats in the following table describe possible unexpected behavior in the latest Cisco Unified Presence release. These caveats may also be open in previous releases. Bugs are listed in alphabetical order by component and then in numerical order by severity.
For the latest versions of all Cisco Unified Presence documentation, go to http://www.cisco.com/en/US/products/ps6837/tsd_products_support_series_home.html
Updates were made to the following documents:
Online Help updates
Bulk administration tool contact rename
This topic was added to describe the Bulk Administration Tool Contact Rename feature.
Cluster topology configuration
This topic was updated to specify that node names must be defined by the FQDN or IP address.
Deployment Guide for Cisco Unified Presence Release 8.6
The Deployment Guide for Cisco Unified Presence Release 8.6 was updated with the following new sections:
•DNS Domain Configuration
•Configuring the DNS domain associated with a Cisco Unified Communications Manager cluster for Release 8.6(5) and later
•Bulk Rename of Contact IDs
The following chapters or sections were enhanced to provide more detailed information:
•Configuring Single Sign-On—Updated for enhanced usability. Note that procedural content for OpenAM configuration on Linux platforms has been removed.
•Node Name Recommendations—Updated with new recommendations for 8.6(5) and later.
•Replacing the Default Presence Domain after Installation—Updated to include a procedure for Release 8.6(4) and earlier and a procedure for Release 8.6(5) and later.
•Node Name Value for Intercluster Deployments—Updated with recommendations for Release 8.6(4) and earlier and Release 8.6(5) and later.
Serviceability Configuration and Maintenance Guide for Cisco Unified Presence Release 8.0, 8.5, and 8.6
The Serviceability Configuration and Maintenance Guide for Cisco Unified Presence Release 8.0, 8.5, and 8.6 was updated to indicate that end user configuration of IM chat rooms (ad hoc and persistent) is now logged by various components of the Cisco Unified Presence application.
Cisco Unified Operating System Maintenance Guide for Cisco Unified Presence Release 8.0, 8.5, and 8.6
The Cisco Unified Operating System Maintenance Guide for Cisco Unified Presence Release 8.0, 8.5, and 8.6 was updated to include Single Sign-On support for the Cisco UP Client Profile Agent (Cisco Jabber).
Installation Guide for Cisco Unified Presence Release 8.6
The postinstallation task to change the Cisco Unified Presence node name to a resolvable value has been updated with information for releases earlier than Cisco Unified Presence Release 8.6(5) and for Release 8.6(5) and later.
Partitioned Intradomain Federation for Cisco Unified Presence Release 8.6
The following updates have been made:
•Added a new chapter detailing user migration planning.
•Updated the workflow for user migration to include two new procedures:
–Verify Lync/OCS/LCS SIP URI Format for Migrating Users
–Rename Contact IDs in Cisco Unified Presence Contact Lists
•Added a detailed description of the new Bulk Administration Tool Contact Rename Tool
Changing the IP Address, Hostname, Domain Name, and Node Name for Cisco Unified Presence Release 8.6.5
This is a new document that describes how to change the server IP address, hostname, domain name, or node name for Cisco Unified Presence Release 8.6(5).
Obtaining documentation and submitting a service request
For information about 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.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned 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. (1110R)
© 2013 Cisco Systems, Inc. All rights reserved