Release Notes for Cisco Unity Connection Release 10.5(2)

For Unity Connection

System Requirements for Cisco Unity Connection Release 10.x at

http://www.cisco.com/en/US/docs/voice_ip_comm/connection/10x/requirements/10xcucsysreqs.html

Compatibility Information

The following documents list the most current version combinations qualified for use with Unity Connection:

• Compatibility Matrix: Cisco Unity Connection and the Software on User Workstations
• SCCP Compatibility Matrix: Cisco Unity Connection, Cisco Unified Communications Manager, and Cisco Unified Communications Manager Express
• SIP Trunk Compatibility Matrix: Cisco Unity Connection, Cisco Unified Communications Manager, and Cisco Unified Communications Manager Express
• Video Compatibility Matrix: Video Endpoints, Cisco Unity Connection, Cisco Unified Communications Manager, and Cisco MediaSense

The documents are available on Cisco.com at http://www.cisco.com/en/US/products/ps6509/products_device_support_tables_list.html.

Determining the Software Version

This section contains procedures for determining the version in use for the following software:

• Cisco Unity Connection Application
• Cisco Personal Communications Assistant Application
• Cisco Unified Communications Operating System

Cisco Unity Connection Application

This section contains two procedures. Use the applicable procedure, depending on whether you want to use Unity Connection Administration or a command-line interface (CLI) session to determine the version.

Using Cisco Unity Connection Administration

Step 1 In Cisco Unity Connection Administration, in the upper-right corner below the Navigation list, select About.

The Unity Connection version is displayed below “Cisco Unity Connection Administration”.

Using the Command-Line Interface

Step 1 Start a command-line interface (CLI) session. (For more information, see the Cisco Unified Communications Operating System Administration Help.)

Step 2 Run the show cuc version command.

Cisco Personal Communications Assistant Application

This section contains the procedure to determine the version using Cisco Personal Communications Assistant application.

Using Cisco Personal Communications Assistant (PCA) Application

Step 1 Sign in to the Cisco PCA.

Step 2 On the Cisco PCA Home page, select About in the upper right corner. (The link is available on every Cisco PCA page.)

Step 3 The Cisco Unity Connection version is displayed. The Cisco PCA version is the same as the Unity Connection version.

Cisco Unified Communications Operating System

This section contains two procedures. Use the applicable procedure, depending on whether you want to use Cisco Unified Operating System Administration or a command-line interface session to determine the version.

Using Cisco Unified Operating System Administration

Step 1 In Cisco Unified Operating System Administration, the System Version is displayed below “Cisco Unified Operating System Administration” in the blue banner on the page that appears after you sign in.

Using the Command-Line Interface

Step 1 Start a command-line interface (CLI) session. (For more information, see Cisco Unified Operating System Administration Help.)

Step 2 Run the show version active command.

Single Sign-On Updates

The following SAML SSO - related enhancements are introduced in Cisco Unity Connection, Release 10.5(2).

Export/Import of SSO Metadata

In Cisco Unity Connection Administration, navigate to System Settings> SAML Single Sign on> the Export All Metadata button is enabled by default, regardless of whether the SAML SSO state is set to active.

Enable SAML SSO

The following note was added to the Enable SAML SSO procedure in the Features and Services Guide.

Note After you select Import IdP Metadata, then select Next, a new status message appears in the SAML Single Sign-On Configuration window. It provides information to either skip or continue further with steps to upload the server metadata to the IdP.

Touchless Installation for Virtual Machine

Touchless Installation for a virtual machine is a new feature supported with Unity Connection 10.5(2). It is used for simplified cluster installation using the Answer File Generation (AFG) and Subscriber Dynamic-Cluster-Configuration process. Using this feature, the deployment of new cluster can be done with minimum intervention.

For more information on Touchless Installation on virtual Machine, see the “ Touchless Installation for Virtual Machine ” section in the “Installing Cisco Unity Connection” chapter of the Install, Upgrade, and Maintainance Guide for Cisco Unity Connection at http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/10x/install_upgrade/guide/10xcuciumgx.html.

Significant Changes to Unity Connection Upgrade Process

Revised January 20, 2015

• You can upgrade from Unity Connection 10.5(1), 10.0(1), 9.x, and 8.x to Unity Connection 10.5(2).
• Before you upgrade from Unity Connection 10.5(1) to Unity Connection 10.5(2), change the value of Directory URI to None. For more information on changing the Directory URI value, see Pre-Upgrade Steps When Upgrading from Unity Connection 10.5(1) to Unity Connection 10.5(2).
• The Unity Connection upgrade files are available as ISO images or COP (Cisco Option Package) files. You can use either of the following interfaces to upgrade Unity Connection:

– Command Line Interface (CLI)

– Cisco Unified OS Administration web interface

For more information on the types of upgrade, see the “ Upgrade Types ” section of the “Upgrading Cisco Unity Connection” of the Install, Upgrade, and Maintainance Guide for Cisco Unity Connection at http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/10x/install_upgrade/guide/10xcuciumgx.html.

• To upgrade from earlier versions to Unity Connection version 10.5(2), the following are required:

– Starting from Unity Connection 10.0(1) and later, the Unity Connection servers will work only on the virtual machines.

– You need not to install a Cisco Options Package when upgrading from Unity Connection 10.0(1) and later to Unity Connection 10.5(2).

– You must download and install a Cisco Options Package when upgrading from Unity Connection 8.x, or 9.x to Unity Connection 10.5(2).

• If you are running Unity Connection on a Cisco MCS server, you must first migrate your Unity Connection server to virtual machine. For instructions on migrating from an existing Unity Connection physical server to a new virtual machine, see the “ Migrating a Physical Server to a Virtual Machine ” section of “Maintaining Unity Connection Server” chapter of the Install, Upgrade, and Maintainance Guide for Cisco Unity Connection at http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/10x/install_upgrade/guide/10xcuciumgx.html.
• If you want to upgrade a Unity Connection 10.x server on which the language files are installed to Unity Connection 10.5(2), do the following steps:

– Download and install the ciscocm.cuc_10.5.2_preupgrade.cop.sgn cop file from https://software.cisco.com/download/release.html?i=!y&mdfid=286268851&softwareid=282204704&release=COP-Files&os=.

– Uninstall the 10.5(1) language files.

– Upgrade the Unity Connection server to release 10.5(2).

– Install the 10.x language files.

For more information on upgrade process or language file installation, see the applicable chapter of the Install, Upgrade, and Maintainance Guide for Cisco Unity Connection at http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/10x/install_upgrade/guide/10xcuciumgx.html.

• The upgrade from an existing Unity Connection server to Unity Connection 10.5(2) is dependent on your existing version of Unity Connection.

Utility Updates on the Cisco Unity Tools Website

Updates to utilities on the Cisco Unity Tools website are frequently posted between Cisco Unity Connection releases. The updates commonly do not apply to a specific release, so we do not list the tools that have been updated since the last version of Unity Connection. However, you can sign up to be notified when the utilities posted on the Cisco Unity Tools website are updated. Go to http://www.ciscounitytools.com, and sign up for receiving notifications.

Virtualization Enhancements

Cisco Unity Connection 10.5(2) can be deployed with VMWare vSphere ESXi4.1, 5.0, 5.1, and 5.5. For more information on the VMware requirements, see http://docwiki.cisco.com/wiki/Unified_Communications_VMware_Requirements

For more information on running Cisco Unity Connection as a virtual machine, see http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization

Email IDs on the Active Directory Server

For the users that must be synchronized to the Cisco Unified Communications Manager database, their email ID fields on the active directory server must be unique or blank.

Installing Cisco Unity Connection for the First Time on a Virtual Machine

You must download and deploy a VMware OVA template, which automatically configures the virtual machine for Unity Connection. To download the template, see the next section, “Downloading a VMware OVA Template for a Unity Connection 10.5(2) Virtual Machine.” The installation and migration documentation tells you when to deploy the template.

Downloading a VMware OVA Template for a Unity Connection 10.5(2) Virtual Machine

A VMware OVA template is not required to configure VMware for Unity Connection, but templates are provided to simplify the process of configuring VMware for Unity Connection. If you want to deploy the VMware OVA template for Unity Connection, do the following procedure to download the OVA file.

To Download a VMware OVA Template for a Unity Connection 10.5(2) Virtual Machine

Step 1 Sign in to a computer with a high-speed Internet connection, and go to the Voice and Unified Communications Downloads page at http://www.cisco.com/cisco/software/navigator.html?mdfid=280082558.

Note To access the software download page, you must be signed in to Cisco.com as a registered user.

Step 2 In the tree control on the Downloads page, expand Products > Unified Communications >Unified Communications Applications > Messaging > Unity Connection, and select Unity Connection Virtualization.

Step 3 On the Download Software page, select OVA-10.5(2) and the download links appear on the right side of the page.

Step 4 Confirm that the computer you are using has sufficient hard-disk space for the downloaded files. (The download file sizes appear below the download links.)

Step 5 Select the applicable link to download.

The following configurations are available with the OVA file, and you can select the required configurations for deploying the OVA template:

Installation and Upgrade Notes

• Installing Additional Unity Connection Languages
• Pre-Upgrade Steps When Upgrading from Unity Connection 10.5(1) to Unity Connection 10.5(2)

Installing Additional Unity Connection Languages

Note All the locales are released for Unity Connection 10.5(2).

For instructions on installing additional Unity Connection languages on the following server types, see the referenced documentation:

• On a Unity Connection server, see the “ Adding and Removing Unity Connection Languages ” section of “Maintaining Unity Connection Server” chapter of the Install, Upgrade, and Maintainance Guide for Cisco Unity Connection at http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/10x/install_upgrade/guide/10xcuciumgx.html.

If you are installing Japanese because you want Cisco Unity Connection Administration to be localized, you must also install the Cisco Unified Communications Manager Japanese locale. See the “Locale Installation” section in the “Software Upgrades” chapter of the applicable Cisco Unified Communications Operating System Administration Guide at http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_maintenance_guides_list.html.If you are installing other languages because you want the Cisco Personal Communications Assistant to be localized, you must also install the corresponding Cisco Unified Communications Manager locales. See the “Locale Installation” section in the “Software Upgrades” chapter of the Cisco Unified Communications Operating System Administration Guide at http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_maintenance_guides_list.html.

Reverting a Server to the Unity Connection Version on the Inactive Partition

If you revert from Unity Connection 10.5(2) to an earlier version of Unity Connection, some of the data for new Unity Connection 10.5(2) features is lost and cannot be retrieved when you upgrade again to Unity Connection 10.5(2).

Pre-Upgrade Steps When Upgrading from Unity Connection 10.5(1) to Unity Connection 10.5(2)

Before you upgrade from Unity Connection 10.5(1) to Unity Connection 10.5(2), if the LDAP Configuration is enabled and the Directory URI is mapped to a non NULL LDAP attribute, then you must perform the following procedure for every LDAP Configuration.

Step 1 In Cisco Unity Connection Administration, navigate to LDAP Directory Configuration > Standard User Fields To Be Synchronized > Directory URI.

Step 2 Change the value of Directory URI to None (and select Save.

Step 3 Select the Perform Full Sync Now button and wait till the full sync process is complete. Select the Refresh button to verify the full sync process is complete.

Step 4 Change the value of Directory URI to its original LDAP attribute (non NULL) and select Save.

Step 5 Repeat Table 1 Table 1 Step 3.

Media Master Cannot Open WAV Files Saved on a Workstation in G.729a Format

The Media Master cannot open WAV files prerecorded in the G.729a audio format and saved to a workstation.

This limitation has the following workarounds:

• Convert the WAV file to another audio format (for example, convert it to the G.711 audio format).
• Use a WAV file that is recorded in a supported audio format other than G.729a.
• Make the recording by using a phone or a computer microphone.

Note that when Cisco Unity Connection is configured to record in the G.729a audio format, the Media Master functions correctly for recording and playing by using a phone or a computer microphone.

Secure Messaging Limitations Regarding ViewMail

Adding non-audio attachments to secure messages composed in Cisco ViewMail for Microsoft Outlook version 8.5 and later is not supported at this time.

Unity Connection expects the LDAP server to respond within 40 milliseconds

During LDAP authentication process, if the LDAP server takes more than 40 milliseconds to respond, Unity Connection web applications may not be accessible.

Resolved Caveats

You can find the latest caveat information for Cisco Unity Connection version 10.5(2) using the Bug Search tool, an online tool available for customers to query defects according to their own needs at https://tools.cisco.com/bugsearch/search?kw=*&pf=prdNm&pfVal=280082558&rls=10.5(2.&sb=fr&sts=fd&svr=5nH&srtBy=byRel&bt=custV.

Bug Search tool is available at https://tools.cisco.com/bugsearch/. To access Bug Search tool, you must be logged on to Cisco.com as a registered user.

Open Caveats—Unity Connection Release 10.5(2)

Revised January 15, 2015

This section list any Severity 1, 2, and 3 open caveats when Unity Connection version 10.5(2) was released.

Related Caveats—Cisco Unified Communications Manager 10.5(2) Components Used by Unity Connection 10.5(2)

Table 3 describes the Cisco Unified Communications Manager components used by Unity Connection. Caveat information for the Cisco Unified CM components is available in Release Notes for Cisco Unified Communications Manager Release 10.5(2) at http://www.cisco.com/c/en/us/support/unified-communications/unified-communications-manager-callmanager/products-release-notes-list.html.

Caveat information for the Cisco Unified CM components is available in the following documents:

• Release Notes for Cisco Unified Communications Manager Release 10.5(2) at http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/rel_notes/10_5_2/CUCM_BK_C6A7E384_00_cucm-release-notes-1052.html.
• Release Notes for Cisco Unified Communications Manager Release 10.5(1) at http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/rel_notes/10_5_1/CUCM_BK_CE15D2A0_00_cucm-release-notes-1051.html .
• Release Notes for Cisco Unified Communications Manager Release 10.0(1) at http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/rel_notes/10_0_1/CUCM_BK_RCAB8A43_00_cucm-release-notes-100.html.
• Release Notes for Cisco Unified Communications Manager Release 9.1(1) at http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/rel_notes/9_0_1/CUCM_BK_RF912712_00_cucm-release-notes-90.html.
• Release Notes for Cisco Unified Communications Manager Release 8.0(2a) at http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/rel_notes/8_0_2/cucm-rel_notes-802a.html.
• Release Notes for Cisco Unified Communications Manager Release 8.0(2) at http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/rel_notes/8_0_2/cucm-rel_notes-802.html.
• Release Notes for Cisco Unified Communications Manager Release 8.5(1) at http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/rel_notes/8_5_1/cucm-rel_notes-851.html.

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)

© 2014 Cisco Systems, Inc. All rights reserved.