Release Notes for Cisco Unity Connection Release 10.0(1)

Originally Published December, 2013

These release notes contain information on Cisco Unity Connection 10.0(1) new and changed support, new and changed functionality, and limitations and restrictions for Cisco Unity Connection Release 10.0(1).

Cisco Personal Communications Assistant Application

To Determine the Version of the 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.

To Determine the Version of the Cisco Unified Communications Operating System by 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.

To Determine the Version of the Cisco Unified Communications Operating System by Using the Command-Line Interface

New Functionality—Release 10.0(1)

Cisco Unity Connection 8.6(2) and later releases provides single sign-on (SSO) access to web applications to users using OpenAM based single sign-on. The SSO feature allows users to access the following web applications on Unity Connection:

Cisco Unity Connection Administration

Cisco Unity Connection Serviceability

Cisco Personal Communications Assistant

Web Inbox

Cisco Unity Connection Rest APIs

Cisco Unity Connection 10.0(1) and later releases introduces an enhanced single sign-on feature using open industry standard protocol SAML (Security Assertion Markup Language). SAML SSO allows a user to gain single sign-on access with Unity Connection subscriber web interfaces and across the administrative web applications on the following Unified Communication products:

A user signs in to any of the supported web applications on Unified Communication products (after enabling the SAML SSO feature) and also gains access to the following Unity Connection applications (apart from Cisco Unified Communications Manager and Cisco Unified CM IM/Presence):

Table 1 Access to Web Applications

Unity Connection users

Web applications

LDAP users with administrator rights

Unity Unity Connection Administration

Cisco Unity Connection Serviceability

Cisco Unified Serviceability

Cisco Personal Communications Assistant

Web Inbox

Mini Web Inbox(desktop version)

LDAP users without administrator rights

Cisco Personal Communications Assistant

Web Inbox

Mini Web Inbox(desktop version)

Note To access Web Inbox and Mini Web Inbox, you must have a user with mailbox. Also navigate to Unity Connection Administration> Class of Service> Licensed features and make sure that the Allow Users to Use the Web Inbox, Messaging Inbox and RSS Feeds check box is checked.

HTTPS Networking in Cisco Unity Connection 10.0(1)

Beginning with Unity Connection 10.0(1) and later, a new type of networking, HTTPS Networking, is introduced to connect different Unity Connection servers and clusters in a single site network. The main objective of introducing HTTPS networking is to increase the scalability of Unity Connection deployments. The architecture of HTTPS networking is scalable both in terms of number of Unity Connection locations and the total directory size.

You can join two or more Unity Connection servers or clusters to form a well-connected network, which is referred to as an HTTPS Unity Connection network. The servers that are joined to the network are referred to as locations. In case of a Unity Connection cluster, the cluster counts as one location in the network. Within a network, each location uses HTTPS protocol to exchange directory information and SMTP protocol to exchange voice messages with each other.

The locations in an HTTPS network are linked together through an HTTPSlink. The topology used in HTTPS networking is hub and spoke topology that plays an important role in increasing scalability of directory size and number of Unity Connection locations. In hub-spoke topology, there are two types of locations: hub location and spoke location. The Unity Connection location which has more than one HTTPS links is known as hub location and the Unity Connection location which has only one HTTPS link is known as spoke location.

For more information on HTTPS networking, refer to the HTTPS Networking Guide for Cisco Unity Connection 10.x and later guide.

Cisco Unity Connection support for Video Greetings

Cisco Unity Connection 10.0(1) and later releases have enhanced the current greeting experience by providing the video greetings to the caller. Unity Connection facilitates the user to record and play video greetings for the identified callers using a video endpoint. For the outside callers, Unity Connection only plays the video greetings depending on the class of service configuration. You can record and play six types of personal video greetings, however, error greetings are played audio only.

To access the video greetings feature, the administrator needs to create video service account for a user and configure it with the video services. Video services allow Unity Connection to integrate with video server for the storage and retrieval of video greetings recorded by the user. For more information on configuring video service account with video services, see the "Configuring Video Services and Video Services Accounts in Cisco Unity Connection 10.x" section of "Managing Video Greetings in Cisco Unity Connection 10.x" chapter in System Administration Guide for Cisco Unity Connection Release 10.x http://www.cisco.com/en/US/docs/voice_ip_comm/connection/10x/administration/guide/10xcucsag091.html.

Note We recommend that you do not enable the video greetings feature if Unity Connection is configured in IPv6 mode as video greetings are not supported in the IPv6 and dual (IPv4/IPv6) modes.

When a call comes, Unity Connection applies all the pre-checks required to establish a video call. A user will be able to record and play video greetings, if all the pre-checks required for each video call are satisfied. For more information on pre-checks, see the "Pre-checks Required for Video Greetings" section of "Managing Video Greetings in Cisco Unity Connection 10.x" chapter in System Administration Guide for Cisco Unity Connection Release 10.x http://www.cisco.com/en/US/docs/voice_ip_comm/connection/10x/administration/guide/10xcucsag091.html.

After configuring video greeting settings in Unity Connection, a user will be able to successfully record and play video greetings. Consider the following scenarios, when Unity Connection allows:

Users login via direct sign-in using the telephone user interface (touchtone conversation) to record and play video greetings, which is supported by the setup options and self-enrollment.

Called users to play video greetings, when the calling user receives unanswered call ("ring-no-answer") from the called user.

For more information on recording video greeting using telephone user interface, see the "Recording Your Video Greeting" section in "Managing Personal Greetings" chapter of User Guide for the Cisco Unity Connection Phone Interface at

Tenant Partitioning in Cisco Unity Connection 10.0(1)

Tenant partitioned Cisco Unity Connection can be thought of as a cloud based voice mail solution where service providers can provide voice mail service to multiple small medium businesses (SMBs)on single installation of Cisco Unity Connection.A Tenant is a logical grouping of objects within the Unity Connection appliance that together make an independent tenant (customer) hosted on the server. Unity Connection will let you have more than one tenant on a single installation. These tenants will exist as islands within the server and would have no knowledge of each other.

The administrator is common to all tenants hosted on a single server. He or she can use the REST APIs that provides (Create, Read, Update, and Delete) CRUD access to perform different operations. The Tenant, Licensing Dump, and Licensing User Entitlement REST APIs have been introduced with this release specifically for the Tenant Partitioning system. For more information on other new APIs that have been introduced with Unity Connection 10.0(1) release, refer to the Changed Functionality—Release 10.0(1) section of this document.

Support for Playing Message Status on Reply and Reply-All in Cisco Unity Connection 10.0(1)

Cisco Unity Connection 10.0(1) and later releases play the status of the message to users when they reply or reply-all to a message using TUI and VUI Interface. Unity Connection plays the following message status, when the Announce Message Status to User(s) while Replying check box is checked:

For more information on announcing message status on reply and reply-all, see the section of the chapter in System Administration Guide for Cisco Unity Connection for 10.x.

Support for Playing Recipient List on Reply-All when Number of Recipients are Below Maximum in Cisco Unity Connection 10.0(1)

With Cisco Unity Connection 10.0(1) and later, when the user reply-all to a message, Unity Connection plays the recipient list, if the number of recipients is less than the number specified in the Maximum Number of Recipients Before Reply-all Warning field. To play the recipient list when you reply-all to a message, check the Announce Recipients list to User(s) while Replying check box. For more information on the Maximum Number of Recipients Before Reply-all Warning field, see the System Administration Guide.

Hardware Support for Unity Connection 10.0(1)

You must install Cisco Unity Connection 10.0(1) release on a virtual machine using 10.0 OVA files.

If you are upgrading a Unity Connection server, ensure that the guest operating system of the virtual machine must be changed to 64 bit after the upgrade completes successfully.

Installing a New Unity Connection 10.0(1) Server

The installation process has not changed since version 8.6(2), so the Installation Guide for Cisco Unity Connection Release 10.x is sufficient to guide you through the installation of a Unity Connection 10.0(1) server Starting from Cisco Unity Connection 10.0(1) release, the Unity Connection deployments will work only on virtual machines.

Caution If a virtual machine is running with an earlier version of Unity Connection, make sure that the machine has the updated VMWare tools installed before upgrading to Unity Connection 10.0(1). New and Changed Requirements and Support—Release 10.0(1)

Support for Cisco Prime Collaboration Deployment

Cisco Unity Connection 8.6(2) and later supports Cisco Prime Collaboration Deployment. It is an application designed to assist in the management of Unified Communication applications. It allows the user to perform tasks such as upgrade, restart, Changing IP Addresses/hostnames on existing clusters. Cisco Prime Collaboration Deployment application also supports mail notification for the tasks performed. Cisco Prime Collaboration Deployment has two primary, high-level functions.

Perform operations on existing clusters (8.6(2) and later). Examples of these operations include

Support for Mailbox-Size Quota Notification Mail

Cisco Unity Connection allows you to specify the maximum size or quota for the mailbox of every user in a Unity Connection system. In Unity Connection 9.1(1) and earlier releases, when a user exceeds the maximum assigned quota, the user recieves a prompt for the mailbox quota overflow.

Beginning with Cisco Unity Connection 10.0(1) and later releases, when the mailbox size of a user starts reaching its specified threshold limit on Unity Connection, the user will receive a quota notification message.

A quota notification message is an email that is sent automatically by Unity Connection to the corporate email address of the voice mailbox when the voice mailbox size of the user exceeds its threshold limit. You can use Cisco Unity Connection Administration to view the default quota notification message or to create, view, and modify customized quota notification messages.

Cisco Unity Connection 9.1(1) and earlier releases allow you to set the expiration warning days of a password or PINs and the number of days after which your credentials will expire. Unity Connection plays a warning prompt for the expiry of the PINs on each login when the number of days is less than or equal to the number of days specified in the Expiration Warning Days field and greater than zero.

In Cisco Unity Connection 10.0(1) and later, the administrator has the privilege to set the time interval during which the conditional expiry warning prompt (after which your credentials will expire) will be played. Run the command utils cuc set PinExpiry_PromptTime "Authentication Rule Name" in the Command Line Interface (CLI) to update the time interval and the warning flag. For more information, see Utils cuc section of Utils Command chapter in the Command Line Interface Reference Guide for Cisco Unified Communications Solutions, Release 10.0(1) at http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/cli_ref/10_0_1/CUCM_BK_C6AE17AA_00_cucm-cli-reference-guide-101.html.

If the administrator entered the value as 0 (disable), and then the expiry warning prompt will be played (default behavior) every day to the user on each login till the number of days specified in the Expiration Warning Days field.

If the administrator entered the value as 1 (enable), then he or she will be asked to enter the time interval during which the conditional expiry warning prompt will be played. If the administrator does not enter any time interval, the warning prompt will be played to the user on every 30 th, 15 th, 5 th, 4 th, 3 rd, 2 nd, and 1 st day.

Note If the administrator entered a value other than 0 or 1, Cisco Unity Connection will prompt it as Invalid Response.

Voice Message as an attachment in HTML Notification

The administrator can configure Unity Connection to send the voice message as an attachment in the HTML notification to the user.The size of the voice message attachment can also be configured. For more information on how to configure, see the Configuring Cisco Unity Connection for HTML-based Message Notification section of the “Configuring an Email Account to Access Cisco Unity Connection Voice Messages” chapter of the User Workstation Setup Guide for Cisco Unity Connection available at

Support for 64 Bit Operating System in Cisco Unity Connection 10.0(1)

Starting from Cisco Unity Connection 10.0(1) release, the operating system is running on 64 bit and the Unity Connection applications remains on 32 bit.

Significant Changes to Unity Connection Upgrade Process Result in New Requirements

To upgrade from earlier versions to Unity Connection version 10.0(1), the following are required:

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

– You need not to install a Cisco Options Package when upgrading from Unity Connection 8.6 or 9.x to Unity Connection 10.0(1)

– You must download and install a Cisco Options Package when upgrading from Unity Connection 7.x, 8.0, or 8.5 to Unity Connection 10.0(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 from a Cisco Unity Connection Standalone Physical Server to a Unity Connection 10.x Virtual Machine” chapter of the Upgrade Guide for Cisco Unity Connection at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/10x/upgrade/guide/10xcucrug025.html.

The upgrade from an existing Unity Connection server to Unity Connection 10.0(1) is dependant on your existing version of Unity Connection.

Upgrade Path

COP File

10.0 to 10.0

Not Required

9.1 to 10.0

Not Required

9.0 to 10.0

Not Required

8.6 to 10.0

Not Required

8.5 to 10.0

V1.1 Unsigned COP - ciscocm.refresh_upgrade_v1.1.cop

V1.1 Signed COP - ciscocm.refresh_upgrade_v1.1.cop.sgn

8.0.2 to 10.0

V1.1 Unsigned COP - ciscocm.refresh_upgrade_v1.1.cop

V1.1 Signed COP - ciscocm.refresh_upgrade_v1.1.cop.sgn

7.1.5 to 10.0

V1.1 Unsigned COP - ciscocm.refresh_upgrade_v1.1.cop

V1.1 Signed COP - ciscocm.refresh_upgrade_v1.1.cop.sgn

Upgrade Path

COP File

8.5 to 10.0

V1.1 Unsigned COP - ciscocm.refresh_upgrade_v1.1.cop

V1.1 Signed COP - ciscocm.refresh_upgrade_v1.1.cop.sgn

8.0.2 to 10.0

V1.1 Unsigned COP - ciscocm.refresh_upgrade_v1.1.cop

V1.1 Signed COP - ciscocm.refresh_upgrade_v1.1.cop.sgn

7.1.5 to 10.0

V1.1 Unsigned COP - ciscocm.refresh_upgrade_v1.1.cop

V1.1 Signed COP - ciscocm.refresh_upgrade_v1.1.cop.sgn

Software Qualified for Use with Cisco Unity Connection on User Workstations

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.

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.0(1) Virtual Machine.” The installation and migration documentation tells you when to deploy the template.

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.0(1) Virtual Machine

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 Cisco Unity Connection Version on the Inactive Partition

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

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 is a free service and Cisco currently supports RSS version 2.0.

Cisco Product Security Overview

This product contains cryptographic features and is subject to United States and local country laws governing import, export, transfer and use. Delivery of Cisco cryptographic products does not imply third-party authority to import, export, distribute, or use encryption. Importers, exporters, distributors and users are responsible for compliance with U.S. and local country laws. By using this product you agree to comply with applicable laws and regulations. If you are unable to comply with U.S. and local laws, return this product immediately.

Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at 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. (1005R)

Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.