Release Notes for Cisco Unity Connection Release 10.5(1)

For Cisco 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 Cisco 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 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.

Support of Directory URI Dialing for Alternate Extensions

With Unity Connection 10.5(1) and later, Unity Connection supports dialing using directory URIs for alternate extensions. Directory URIs follow the username@host format where the host portion is an IPv4 address or a fully qualified domain name. A directory URI is a uniform resource identifier (a string of characters) that can be used to identify a directory number. If that directory number is assigned to a phone then Unity Connection can route calls to that phone using the directory URI. URI dialing is available for both SIP endpoints that support directory URIs.

For more information on directory URI, see the “ URI Dialing for Alternate Extensions ” section of the Integrating Cisco Unity Connection 10.x with the Phone System chapter of Design Guide for Cisco Unity Connection Release 10.x at http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/10x/design/guide/10xcucdgx.html.

Multi-Server Certificate Support for Tomcat

Multi-server Subject Alternate Name (SAN) is a section defined under X.509 certificate extensions. SAN contains multiple Fully Qualified Domain Names (FQDN), hostnames, or other valid names. X.509 technology allows placing a trust in the identity of an entity such as Internet websites when it is digitally signed by a Certificate Authority (CA). SAN field allows multiple FQDNs, domain names, or other approved names to be included in X.509 certificate. This way a user does not need to generate a certificate for each server. Instead one certificate identifies multiple servers.

Note For telephony integration, multi-server SAN certificate is supported only with SIP integration.

For more information on multi-server certificate, see “ Security ” chapter of Cisco Unified Communications Operating System Administration Guide for Cisco Unity Connection Release 10.x at http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/10x/os_administration/guide/10xcucosagx.html.

Support for Comet Notifications on Deleted Folder

Cisco Unity Connection 10.5(1) and earlier supports comet notifications for message operations with only the Inbox folder.

Unity Connection 10.5(1) and later now supports comet notifications for message operations also with the Deleted folder. For the Deleted folder, Unity Connection sends comet notifications on the following events:

• DELETED_MESSAGE_CREATE: This event is sent when a new message arrives in the Deleted folder.
• DELETED_MESSAGE_READ: This event is sent when a message is marked as read in the Deleted folder.
• DELETED_MESSAGE_UNREAD: The event is sent when a message is marked as unread in the Deleted folder.
• DELETED_MESSAGE_DELETE: The event is sent when a message is hard deleted from the Deleted or Inbox folders.
• DELETED_MESSAGE_UNDELETE: This event is sent when a message is marked as undeleted from the Deleted folder.

Note During the time when the Notifier service is down or inactive, if there is any action taken on a message that is either in the Inbox or Deleted folders, then the notification for the latest status of that message is sent when the service is back in the active state.

For more information on Comet Notifications on Deleted folder, see http://docwiki.cisco.com/wiki/Cisco_Unity_Connection_Messaging_Interface_(CUMI)_API_--_Using_the_CUMI_API_for_Sending_Notifications#Getting_Started.

Support for Microsoft Office 365 Wave 15

Unity Connection 10.5(1) and later now supports synchronization of voice messages in the user's mailbox with Microsoft Office 365 Wave 15 edition.

For more on Unified Messaging with Office 365 in Unity Connection 8.x and later, see http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/8x/unified_messaging/guide/85xcucumgx/85xcucumg025.html#wp1189441.

Support for NTLMv2

Unity Connection 10.5(1) and later now supports NTLMv2 based authentication, if user selects NTLM authentication mode for configuring Unified Messaging. For more information on NTLMv2, see the Unified Messaging Guide for Cisco Unity Connection 10.x, http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/10x/unified_messaging/guide/10xcucumgx/10xcucumg020.html.

Support for Cross-Origin Resource Sharing (CORS)

Unity Connection 10.5(1) and later has extended the support to the client applications of a cross domain server to access content on a Unity Connection server using Cross-Origin Resource Sharing (CORS) requests. CORS support in Unity Connection allows a user to create, send, or receive Unity Connection messages using cross domain client applications.

Without CORS, a cross domain client application cannot access the content on the non-origin server. For a web application, cross-origin requests from the original domain to another domain are forbidden by the web browser due to a Single Origin Policy. CORS standard supports the HTTP headers to establish an agreement between the web browser and Unity Connection server to provide services to the permitted domains.

The CORS request is processed between the client applications of a cross domain server and Unity Connection VMRest APIs in a more secured way. The entry of the cross domain server must preexist in the Unity Connection server.

Support for Message Waiting Indicator (MWI) for Unity Connection SRSV

With Unity Connection 10.5(1) and later, Cisco Unity Connection Survivable Remote Site Voicemail phone system can be configured to support MWI functionality. Once configured, a user can receives the MWI notification during WAN failure for the new notifications received at the branch server. For more information on configuring MWI, see the chapter “ Managing the Phone System Integrations in Unity Connection SRSV”, of Complete Reference Guide for Cisco Unity Connection Survivable Remote Site Voicemail (SRSV) Release 10.x at http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/10x/srsv/guide/10xcucsrsvx.html.

Note With Unity Connection 10.5(1) and later releases, SRSV branch supports 500 users per branch with a maximum of 35 branches per centralized Unity Connection server.

SAML SSO Support using OAuth 2.0

With Unity Connection 10.5(1) and later, VMRest APIs expand single sign-on access (SSO) support to include authentication using a SSO OAuth 2.0 token.

Support for Call Handler Owners Using Distribution List

In Unity Connection 10.5(1) and later, you can add one or more than one call handler owner using the distribution list. The member of distribution list should have all the privileges as a call handler user owner, such as recording a greeting.

For more information on call handler owners using distribution list, see the Call Handler Settings section in the “Call Management” chapter in the System Administration Guide for Cisco Unity Connection Release 10.x at http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/10x/administration/guide/10xcucsagx.html.

Support for Caller Directory Number Using Live Reply

In case of live reply, Unity Connection 10.5(1) and later populates the directory number of the caller in the Referred-By field of the TRANSFER message. Unity Connection populates the caller directory number only when the Use Calling Directory Number in Live Reply option is enabled.

For more information on caller directory number using live reply, see the Conversations section in the “Advanced System Settings” chapter in the System Administration Guide for Cisco Unity Connection Release 10.x at http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/10x/administration/guide/10xcucsagx.html.

Support for Comet Notifications over SSL

Unity Connection 10.5(1) and later allows the user to send comet notifications over SSL. To enable comet notifications over SSL, run the command utils cuc jetty ssl enable CLI command. For more information on comet notifications over SSL, see the “Comet Notifications Over SSL Mode” section in the Cisco Unity Connection 10.x Overview chapter of Design Guide for Cisco Unity Connection for Release 10.x http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/10x/design/guide/10xcucdgx.html.

Significant Changes to Unity Connection Upgrade Process

• You can upgrade from Unity Connection 10.0(1), 9.x, 8.x, and 7.x to Unity Connection 10.5(1).

Note To upgrade from Unity Connection 7.1(5x) and 7.1(3x) to Unity Connection 10.5(1), you must first upgrade to Unity Connection 8.x.

• To upgrade from earlier versions to Unity Connection version 10.5(1), 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) to Unity Connection 10.5(1).

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

– If you are running Unity Connection on a Cisco MCS server, you must first migrate your Unity Connection server to virtual machine. For more information on migration procedure to virtual machine, refer to the “ Migrating a Physical Server to a Virtual Machine ” section in the “Maintaining Cisco Unity Connection Server” chapter of the Install, Upgrade, and Maintainenance Guide for Cisco Unity Connection Release 10.x at http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/10x/install_upgrade/guide/10xcuciumgx.htm l.

• The upgrade from an existing Unity Connection server to Unity Connection 10.5(1) 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(1) 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 can either manually configure the virtual machine for Unity Connection or you can 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(1) 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(1) 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(1) 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 > Cisco Unity Connection, and select Cisco Unity Connection Virtualization.

Step 3 On the Download Software page, select OVA-10.5 ‘, 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
• Reverting a Server to the Unity Connection Version on the Inactive Partition

Installing Additional Unity Connection Languages

Revised September 10, 2014

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

For instructions on installing additional Unity Connection languages, see the “Adding or Removing Unity Connection Languages” section in the “Maintaining Cisco Unity Connection Server” chapter of the Install, Upgrade, and Maintainenance Guide for Cisco Unity Connection Release 10.x 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(1) to an earlier version of Unity Connection, some of the data for new Unity Connection 10.5(1) features is lost and cannot be retrieved when you upgrade again to Unity Connection 10.5(1).

For more information on how reverting affects Unity Connection features, see the “Rollback of Unity Connection” section in the “Upgrading Cisco Unity Connection” chapter of the Install, Upgrade, and Maintainenance Guide for Cisco Unity Connection Release 10.x at http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/10x/install_upgrade/guide/10xcuciumgx.html.

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 is not supported at this time.

Resolved Caveats

You can find the latest caveat information for Cisco Unity Connection version 10.5(1) by using the Bug Search tool, an online tool available for customers to query defects according to their own needs.

Note 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.

You can search for “Cisco Unity Connection” by selecting “Model/SW Family” in the Product drop-down list.

Open Caveats—Unity Connection Release 10.5(1)

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

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

Table 2 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(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/CUCM_BK_CE15D2A0_00_cucm-release-notes-1051_chapter_01.html#CUCM_RF_S07FB417_00.

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

• 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)