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.)
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.
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.
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.
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
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.
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.
V1.1 Signed COP - ciscocm.version3-keys_v1.1.cop.sgn
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.
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
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:
For up to 1,000 Unity Connection users.
Configures one virtual CPU, 4 GB RAM, and one 160-GB virtual disk with the file system aligned at 64KB blocks.
Configures two virtual CPU, 4 GB RAM, and one 160-GB virtual disk with the file system aligned at 64KB blocks.
For up to 5,000 Unity Connection users.
Configures two virtual CPUs, 6 GB RAM, and one 200-GB virtual disk with the file system aligned at 64KB blocks.
For up to 10,000 Unity Connection users.
Configures four virtual CPUs, 6 GB RAM, and two 146-GB virtual disks with the file system aligned at 64 KB blocks.
Comes in 3 variations: 146 GB, 300 GB, and 500 GB. In 300 GB and 500 GB variations, the datastore where the Unity Connection virtual machine will reside must be formatted with a VMware VMFS block size of 2 MB or more. A block size of 1 MB limits the maximum virtual hard disk size to 256 GB. A block size of 2 MB allows 512 GB virtual disks.
For up to 20,000 Unity Connection users.
Configures sever virtual CPUs, 8 GB RAM, and either two 300-GB virtual disks or two 500-GB virtual disks with the file system aligned at 64KB blocks.
When running on VMWare vSphere version ESXi4.x requires Enterprise Plus solution. There is no restriction when running on VMWare vSphere version ESXi5.x.
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).
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.
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 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)