• A server that meets Cisco Unity Connection specifications. See the Cisco Unity Connection 12.x Supported Platforms List at https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/12x/supported_platforms/b_12xcucspl.html.

  Caution

  If you try to install version 12.x on an unsupported platform, Unity Connection will not be displayed as an option in the Product Deployment Selection window of the installation program. See the server-specific table in the “Unity Connection Supported Servers” section of the Cisco Unity Connection 12.x Supported Platforms List to verify platform specifications, particularly regarding memory and processor speed.

• Unity Connection 12.x can only be installed on virtual servers. If you are upgrading from an earlier version of Unity Connection or migrating from Cisco Unity to Unity Connection 12.x, you need to replace the existing server with a virtual machine. For information on migrating a physical server to virtual server, see the “Migrating from Cisco Unity 4.x and Later to Unity Connection 7.x and Later” section of the “Maintaining Cisco Unity Connection Server” chapter of the Install, Upgrade, and Maintenance Guide for Cisco Unity Connection, Release 12.x, available at https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/12x/install_upgrade/guide/b_12xcuciumg.html.

• If you are adding features, for example, Unity Connection Networking, a Unity Connection cluster, or single inbox, you may need to replace hard disks or add memory to the Unity Connection server for the feature to be supported. For more information, see the applicable server-specific table in the Cisco Unity Connection 12.x Supported Platforms List .

• The list of supported virtual platform is listed in the Cisco Unity Connection 12.x Supported Platforms List.

This section contains the following information:

Unity Connection can be integrated with Cisco Unified Communications Manager and Cisco Unified Communications Manager Express.

In addition, Cisco Unified CM integrations with Unity Connection support the use at remote sites of Cisco Unified CM Express in Survivable Remote Site Telephony (SRST) mode or of SRST installed on Cisco IOS platforms.

For supported versions of Cisco Unified CM and Cisco Unified CM Express, see the Compatibility Matrix for Cisco Unity Connection at https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/compatibility/matrix/b_cucclientmtx.html.

• The SIP Trunk can also be referred for PIMG/TIMG integrations. For information on PIMG/TIMG integrations , see the applicable Cisco Unity Connection integration guides at http://www.cisco.com/c/en/us/support/unified-communications/unity-connection/products-installation-and-configuration-guides-list.html

  Note	Unity connection PIMG/TIMG integration supports Version 6.0, SU10 for Dialogic® 1000 and 2000 Media Gateway Series.

• Unity Connection can also be integrated with other supported phone systems and with multiple phone systems simultaneously. For information on other supported phone systems, see the applicable Cisco Unity Connection integration guides at http://www.cisco.com/c/en/us/support/unified-communications/unity-connection/products-installation-and-configuration-guides-list.html.

In Unity Connection, the licenses for Unity Connection are managed by the Cisco Smart Software Manager (CSSM). The following are the license tags supported by Unity Connection in conjunction with the CSSM:

• CUC_BasicMessaging: Allows you to use the following Unity Connection features:

  • Synchronization of Unity Connection and Exchange mailboxes (single inbox)

  • Calendar information for meetings

  • Exchange contact information

  • Intrasite/intersite networking

  • HTTPS Networking

  • VPIM networking

  • Personal call transfer rules

  • Users with Unity Connection mailboxes

  • Users with IMAP or Single Inbox access to voice messages

  • Recording length

  • Phone interface (TUI)

  • Mini Web Inbox

  • Web Inbox

  • Cisco Unity Connection ViewMail for Microsoft Outlook 11.5(1) and later

  • IMAP email client

  • Cisco Mobile and Cisco Unified Mobile Communicator

  • Cisco Unified Messaging with IBM Lotus Sametime

  • Visual Voicemail

  • RSS readers

  • Cisco Unity Connection Phone View

  • Video Greetings and messaging

  • Tenant Partitioning

  • SAML Single Sign-On

• CUC_SpeechView: Allows you to use SpeechView standard transcription service.

• CUC_SpeechViewPro: Allows you to use SpeechView professional transcription service.

• CUC_SpeechConnectPort: Allows you to use Speech Connect and voice-recognition features.

• CUC_EnhancedMessaging: Allows you to use Unity Connection SRSV feature along with Basic Messaging features.

The following are the supported mail servers with which you can integrate Unity Connection to enable Unified Messaging:

1. Microsoft Exchange 2019 and 2016 Servers.
2. Microsoft Office 365.
3. Gmail Server.

Following versions of Microsoft Exchange servers are supported:

• Exchange Server 2019 Cumulative Update 13 and earlier.

• Exchange Server 2016 Cumulative Update 23 and earlier.

The Unified Messaging requirements are as follows.

• Unity Connection must be integrated with supported version of Cisco MediaSense Primary node. Cisco MediaSense cluster is not supported.

• Unity Connection users must be assigned a class of service with video parameters enabled.

• Unity Connection is configured in IPv4 mode only.

• Unity Connection supports the following codecs in a video call

  • H.264 video codec

  • G.711ulaw audio codec

• Video messaging and video greetings are supported only over SIP Integration with Cisco Unified Communications Manager.

• The Primary DNS server should not have a response delay of more than 500 milliseconds.

• The MediaSense server must be co-located with Unity Connection server with 1Gbps connectivity between the servers and less than 10ms Round Trip Time (RTT) latency.

• You must have required licenses on Cisco Smart Software Manager (CSSM).

• Users must be assigned to a class of service enabled for using voice recognition.

• Phone systems must be configured to send calls to Unity Connection in any of the supported audio codecs except G729a. The G.729a audio codec is not supported with the voice-recognition features.

  Note	Remote Message Monitor is only supported if all end points (incoming, Unity, and outgoing) are using the same codec.

The SpeechView feature—which provides transcriptions of voice messages—is supported with Unity Connection.

• You must have required licenses on Cisco Smart Software Manager to use SpeechView service.

• Users must be assigned to a class of service enabled for using SpeechView transcriptions of voice messages.

For Unity Connection speechview transcription requirements, see the Unified Messaging Requirements: SpeechView Transcriptions

Messaging Assistant web tool

• Users must be assigned to a class of service enabled for using the Messaging Assistant.

• A supported operating system and web browser(s) on user workstations. See Compatibility Matrix for Cisco Unity Connection at https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/compatibility/matrix/b_cucclientmtx.html.

Web Inbox web tool

• Users must be assigned to a class of service enabled for using the Web Inbox and RSS feeds.

• A supported operating system and web browser(s) on user workstations. See Compatibility Matrix for Cisco Unity Connection at https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/compatibility/matrix/b_cucclientmtx.html.

• Users must be assigned to a class of service enabled for using the Web Inbox and RSS feeds.

• Adobe Flash Player version 30 or later on user workstations.

• A supported operating system and web browser(s) on user workstations. See Compatibility Matrix for Cisco Unity Connection at https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/compatibility/matrix/b_cucclientmtx.html.

  Note	Web Inbox is now supported over both IPv4 and IPv6. However, to access Web Inbox over IPv6, Unity Connection platform must be configured in Dual (IPv4/IPv6) mode.

  Caveats:

  The Internet Explorer does not support playback functionality for voice messages using Web Inbox.

• Make sure the trusted certificate of the certification authority is added to the Trusted Root Store on the user workstations in order to access the notifications via email and the voice message via Mini Web Inbox. For more information on how to configure the trusted certificate on Unity Connection, see the “Securing Unity Connection Administration, Cisco PCA, Unity Connection SRSV, and IMAP Client Access to Unity Connection” section of the “Using SSL to Secure Client/ Server Connections” chapter of the Security Guide for Cisco Unity Connection, Release 12.x, at https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/12x/security/b_12xcucsecx.html.

• Make sure to perform the steps to configure the HTML notification on user workstation. For more information on how to configure the HTML notifications, see the “Configuring 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, Release 12.x, available at https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/12x/user_setup/guide/b_12xcucuwsx.html.

• Make sure to perform the steps to configure the Mini Web Inbox on user workstation. For more information on how to configure the Mini Web Inbox, see the “Configuring Unity Connection for Mini Web Inbox” 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, Release 12.x, available at https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/12x/user_setup/guide/b_12xcucuwsx.html.

• Audio Playback on Computer

  • Mozilla Firefox plays voice messages on Mini Web Inbox using HTML 5 Audio (.wav format).

• Audio Recording on Computer

  • Microsoft Internet Explorer and Mozilla Firefox require the compatible Adobe Flash Player.

Caveats:

• On MAC OS - The recording on MAC OS is supported by telephone record and playback functionality only, computer based recording is not supported.

For supported operating system and web browser(s) on user workstations, see Compatibility Matrix for Cisco Unity Connection at https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/compatibility/matrix/b_cucclientmtx.html

Note	Mini Web Inbox is supported over both IPv4 and IPv6. However, to access Mini Web Inbox over IPv6, Unity Connection platform must be configured in Dual (IPv4/IPv6) mode.

• IMAP users only: Users must be assigned to a class of service that is enabled for accessing voice messages using an IMAP client.

• IMAP users only: Users must have email accounts in Outlook configured to access Unity Connection voice messages.

• Single-inbox users only: Users must have Exchange email accounts in Outlook pointing to their Exchange mailboxes.

• A ViewMail for Outlook version supported for use with the Outlook version and operating system on user workstations. See Requirements for Accessing Unity Connection Voice Messages Using an IMAP Email Client.

For workstation and other software-related requirements, and for installation and upgrade information, see Release Notes for Cisco ViewMail for Microsoft Outlook at http://www.cisco.com/en/US/products/ps6509/prod_release_notes_list.html.

Cisco Unity Connection ViewMail for Microsoft Outlook supports the single sign-on functionality.

Note	Cisco Unity Connection ViewMail for Microsoft Outlook (VMO) is supported over both IPv4 and IPv6. However, to access voice messages using IMAP clients over IPv6, Unity Connection platform must be configured in Dual (IPv4/IPv6) mode.

• Users must be assigned to a class of service that is enabled for accessing voice messages using an IMAP client.

• A supported IMAP email client on user workstations. See Compatibility Matrix for Cisco Unity Connection at https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/compatibility/matrix/b_cucclientmtx.html.

• Sound card, speakers, and media player on user workstations.

  Note	Accessing Unity Connection voice messages using IMAP clients is now supported over both IPv4 and IPv6. However, to access voice messages using IMAP clients over IPv6, Unity Connection platform must be configured in Dual (IPv4/IPv6) mode.

• Users must be assigned to a class of service that is enabled for accessing voice messages using a unified client.

• A supported version of Cisco Unified Personal Communicator on user workstations. See Compatibility Matrix for Cisco Unity Connection at https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/compatibility/matrix/b_cucclientmtx.html.

For workstation, system, and other software-related requirements, see the applicable Release Notes for Cisco Unified Personal Communicator at http://www.cisco.com/c/en/us/support/unified-communications/unified-personal-communicator/products-release-notes-list.html.

• Cisco Unified Personal Communicator 8.x support secure messaging with Unity Connection.

• Cisco Unified Personal Communicator versions 8.0 and later support IMAP IDLE.

Unity Connection supports Cisco Jabber 12.0(1) and later as client.

For more information on Cisco Jabber with operating systems, see the windows release notes at https://www.cisco.com/c/en/us/support/unified-communications/jabber-windows/tsd-products-support-series-home.html.

and for Macintosh, see the release notes at https://www.cisco.com/c/en/us/support/unified-communications/jabber-mac/tsd-products-support-series-home.html.

This section contains the following information:

• A supported Cisco Unified IP Phone model. (See the “Cisco Unified IP Phone Requirements” section under “System Requirements” in the Release Notes for Visual Voicemail.)

For server and phone firmware requirements, and other information about using Visual Voicemail, see the applicable Release Notes for Visual Voicemail at http://www.cisco.com/en/US/products/ps9929/prod_release_notes_list.html.

• Users must be assigned to a class of service enabled for using the Messaging Inbox and RSS feeds.

• Sound card, speakers, and media player on user workstations.

  Note	RSS feeds is now supported over both IPv4 and IPv6. However, to access RSS feeds over IPv6, Unity Connection platform must be configured in Dual (IPv4/IPv6) mode.

Unity Connection integrated with a supported application for calendar information:

For Unity Connection requirements, see the “Unified Messaging Requirements: Accessing Calendar Information for Meetings” section on page 10.

Note	Accessing calendars is supported with Exchange servers over both IPv4 and IPv6. However, to access the calendars over IPv6, Unity Connection platform must be configured in Dual (IPv4/IPv6) mode.

Exchange contacts can be imported into Unity Connection, allowing users to place outgoing calls using voice commands and to create personal call transfer rules based on the contact information.

• Unity Connection integrated with a supported version of Microsoft Exchange Server is required.

For Unity Connection 12.x requirements, see the Unified Messaging Requirements: Accessing Exchange Contact Information.

Note	Accessing contacts is supported with Exchange servers over both IPv4 and IPv6. However, to access the contacts over IPv6, Unity Connection platform must be configured in Dual (IPv4/IPv6) mode.

• Unity Connection integrated with a supported version of the Cisco Unified Communications Manager phone system. For supported versions, see the Compatibility Matrix for Cisco Unity Connection depending on the integration type at https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/compatibility/matrix/b_cucclientmtx.html.

• A supported Cisco Unified IP Phone model, with the supported Cisco Unified Communications Manager version firmware installed. The following IP Phone models are supported: 8865, 9971, 8845, 7821, EX90, DX70.

• Unity Connection must be integrated with the URI dialing supported version of Cisco Unified Communications Manager.

• Unity Connection supports URI Dialing over SIP Integration with Cisco Unified Communications Manager.

• Configure URI supported IP Phones (89xx or 99xx series) or Jabber/Webex using Cisco Unified Presence Server and CUCM, in order to dial via URI directly.

• Cisco Fax Server version 10.x (available from Cisco until May 2011)

• OpenText Fax Server, RightFax Edition, version 10.x and later.

• Sagemcom Xmedius Fax SP version 6.5.5.

  Note

  Cisco will no longer be selling Cisco Fax Server version 10.x after May 2011; however, support for Cisco Fax Server will continue until May 2014. For detailed information on end-of-sale and end-of life dates for the Cisco Fax Server, see the information at http://www.cisco.com/c/en/us/products/collateral/unified-communications/unity/end_of_life_notice_c51-630608.html.

If your system is configured for a Unity Connection cluster, consider how the requirements varies in the following scenarios.

Unity Connection servers can be joined through intrasite networking to form a single site (known as a Digital Network). you may add upto a maximum of ten Untiy Connection server or cluster per site. In addition, two Unity Connection sites can be linked together through intersite networking for a total of up to 20 Unity Connection servers sharing the same directory information

Alternatively, you can use intersite networking to link a single Unity Connection site of up to ten servers with a single Cisco Unity server or Digital Network. (In a Unity Connection cluster, only the publisher server is joined to the network, so a cluster counts as a single server toward the limit of ten in each site.)

HTTPS networking can be used to link up to 25 Unity Connection servers or clusters in a single site network, referred to as HTTPS Unity Connection network.

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:

• Cisco Unity Connection

• Cisco Unified Communications Manager

• Cisco Unified IM/Presence

• Cisco Unified Communications OS Administration

• Disaster Recovery System

For more information on accessing web application pages through SAML SSO, see the Quick Start Guide for SAML SSO in Cisco Unity Connection , Release 12.x, available at https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/12x/quick_start/guide/b_12xcucqssamlsso.html.

The SAML SSO feature requires the following third party applications:

• LDAP Directory.

• The Identity Provider authenticates an end user and returns SAML assertions. SAML Assertion shows either Yes (authenticated) or No (authentication fails) response. When an end user enters the username and password, the user credentials authenticates on Identity Provider. This further gives access to web applications on the Unity Connection server. The supported Identity Providers are:

  • Microsoft Active Directory Federation Services (ADFS) version 3.0, 4.0 and 5.0

  • Ping Federate version 6.10.0.4

  • OpenAM version 10.0.1

  • Oracle Identity Manager version 11.0

  • F5 BIG-IP 11.6.0

  • Okta 2017.38

• To enable the SAML SSO feature from Cisco Unity Connection Administration, make sure you have at least one LDAP user in Unity Connection with administrator rights.

  Note	Unity Connection supports SAML 2.0 protocol for the SAML SSO feature.

The third party products mentioned above must meet the following configuration requirements:

• Active directory domain controllers/global catalog servers and Active Directory Federated Services (ADFS) can be installed in any hardware virtualization environment supported by Microsoft. (Cisco does not provide technical support for DC/ GCs or ADFS that acts as an Identity Provider).

• The Identity Provider that you are using must be accessible by its hostname on the network to all the client systems like Unity Connection.

• The clocks of all entities participating in SAML SSO must be synchronized.

See the third-party product documentation for more information about the above products.

Note	Make sure that Domain Name Server (DNS) is configured on Unity Connection as SAML SSO is not supported with only IP address configuration of Unity Connection.

All web browsers that are currently supported with Unity Connection 12.x, allows SAML SSO access to web client applications.

Unity Connection supports Voice Profile for Internet Mail (VPIM) version 2 that allows the exchange of voice and text messages with other messaging systems.

VPIM Networking can be used to provide message networking between Unity Connection and the following messaging systems:

• Unity Connection 12.x, 11.x and 10.x.

• Cisco Unity 8.x and 7.x.

• Cisco Unity Express 3.2(1) and later.

• Third-party voice messaging systems that support the VPIM version 2 protocol, as defined in Internet RFC 3801.

For information on using VPIM in Unity Connection Unity Connection in Cisco Business Edition, see the “VPIM Networking” chapter of the Networking Guide for Cisco Unity Connection, Release 12.x, at https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/12x/networking/guide/b_12xcucnetx.html.

A supported provisioning application:

• Unimax Second Nature version 6.8 B0 and later.

Any technical support or troubleshooting required on the provisioning software must be obtained from the manufacturer. Cisco is responsible for providing technical support only on the Unity Connection application.

During the migration, only user data and, optionally, voice messages are preserved. System-level configuration data (for example, templates and classes of service) must be manually configured.

Caution

Requirements for Unity Connection 12.x are different from requirements for Unity Connection 7.x. The system must meet Unity Connection 12.x requirements to receive support from Cisco TAC.

A migration from Unity Connection version 7.x to 12.x has the following requirements:

• All applicable requirements listed in this document.
• A server that is supported for use with Unity Connection and that meets Unity Connection 12.x specifications, particularly regarding memory and processor speed. (Not all servers supported for use with Unity Connection 7.x are supported for use with Unity Connection 12.x.) For information on supported Unity Connection servers, including specifications on individual servers, see the Cisco Unity Connection 12.x Supported Platforms List at https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/12x/supported_platforms/b_12xcucspl.html.

Caution

If you try to install version 12.x on an unsupported platform, Unity Connection will not be displayed as an option in the Product Deployment Selection window of the installation program.

Caution

Requirements for Unity Connection are different from requirements for Cisco Unity. The system must meet Unity Connection 12.x requirements to receive support from Cisco TAC.

A migration from Cisco Unity to Unity Connection 12.x by gradually moving data has the following requirements:

• All applicable requirements listed in this document.
• A Cisco Unity Digital Network in which at least one server is running version 8.0(3) to act as a gateway to Unity Connection. Other servers in the Cisco Unity Digital Network must be running version 8.0(3) or later, or version 7.0(2) with Engineering Special (ES) 36 or later.
• A server that is supported for use with Unity Connection and that meets Unity Connection 12.x specifications, particularly regarding memory and processor speed. (Not all servers supported for use with Cisco Unity are supported for use with Unity Connection.) For information on supported Unity Connection servers, including specifications on individual servers, see the Cisco Unity Connection 12.x Supported Platforms List at https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/12x/supported_platforms/b_12xcucspl.html.

Caution

If you try to install version 12.x on an unsupported platform, Unity Connection will not be displayed as an option in the Product Deployment Selection window of the installation program.

Note that voice cards are not supported for integrations with circuit-switched phone systems.

For information on installing other Cisco Unified Communications applications on the same physical server on which Unity Connection is installed, see the Unified Communications Virtualization wiki at http://www.cisco.com/c/dam/en/us/td/docs/voice_ip_comm/uc_system/virtualization/virtualization-cisco-unity-connection.html.

• If you are running Unity Connection on a physical server and want to migrate over to Unity Connection 12.x, then it is required to migrate from a physical server to a virtual server since the physical Unity Connection server is not supported for use with Unity Connection 12.x.
• A physical host that meets Unity Connection specifications and that is supported for use in a virtualized environment. See the Cisco Unity Connection 12.x Supported Platforms List at https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/12x/supported_platforms/b_12xcucspl.html.

• The applicable edition of VMware vSphere ESXi Version 5.0 Update 1, 5.5, 6.0, 6.5, 6.5 Update 2 and 6.7 installed on the host server on which the Unity Connection virtual machine will run.

  Note	Updates to ESXi Version 5.0 Update 1, 5.5, 6.0, 6.5, 6.5 Update 2 and 6.7 are supported. Unity Connection 12.5(1) requires minimum ESXi version of 6.5 U2 with minimum VM Hardware version of 13.

• For VMware configurations supporting 300GB and 500GB vDisks: The datastore where the Unity Connection virtual machine will reside must be formatted with a VMware VMFS block size large enough to allow for the intended size of the virtual hard disk for the Unity Connection virtual machine. For example, a block size of 1MB limits the maximum virtual hard disk size to 256GB. A block size of 2MB allows 512GB virtual disks.
• Unity Connection 8.0(2) and later can be run on specification based hardware from Cisco, HP and IBM. However, some restrictions are applied. See http://www.cisco.com/c/dam/en/us/td/docs/voice_ip_comm/uc_system/virtualization/collaboration-virtualization-hardware.html for more information.
• The support for the Input/Output devices on the servers that are running Unity Connection as a virtual appliance has been enhanced to include FCoE and Cisco Converged Network adapters. See http://www.cisco.com/c/dam/en/us/td/docs/voice_ip_comm/uc_system/virtualization/collaboration-virtualization-hardware.html for more information.
• Unity Connection 8.0(2) and later now support FC, FCOE, iSCSI, and NFS SAN environments with some restrictions. See http://www.cisco.com/c/dam/en/us/td/docs/voice_ip_comm/uc_system/virtualization/virtualization-collaboration-storage-design-requirements.html for more information.
• For list of VMware features that are supported for Unity Connection, see http://www.cisco.com/c/dam/en/us/td/docs/voice_ip_comm/uc_system/virtualization/virtualization-collaboration-storage-design-requirements.html.
• Accessing a USB key is not supported.
• Oversubscribing processors and memory is not supported.
• For VMware vSphere ESXi 5.1 and earlier, at least one processor core must be available for the VMware ESXi hypervisor / scheduler.
• For VMware vSphere ESXi 5.5 and later, Latency Sensitivity function is included to reduce virtual machine latency. When the Latency Sensitivity value is set to high you do not need to leave any unused processor core for the ESXi hypervisor / scheduler.
• All virtual disks assigned to the Unity Connection virtual machine must be configured in independent-persistent mode, which provides the best storage performance.
• A network time protocol (NTP) server must be accessible to the Unity Connection server.
• When configuring a Unity Connection cluster, you can install Unity Connection on one physical server and one virtual machine, or on two virtual machines, but the two virtual machines must be on separate physical hosts. When using blades as hosts, we recommend that the blades be on separate chassis.
• If the hyper-threading feature is available on the CPU, you should enable the feature to create logical cores. However, the logical cores do not change the Unity Connection rule that is based on 1:1 mapping of physical cores to vcpu not the logical cores to vcpu.

Note

Languages are not licensed, and Unity Connection does not enforce a limit on the number of languages you can install and use. However, the more languages you install, the less hard-disk space is available for storing voice messages. In the Cisco Unity Connection 12.x Supported Platforms List at https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/12x/supported_platforms/b_12xcucspl.html), information on the number of minutes of storage available on each server assumes that you have installed no more than five languages.

This section lists the languages in which Unity Connection components are available.

Cisco Personal Communications Assistant (PCA)

Arabic-Saudi Arabia, Catalan, Chinese-Hong Kong, Chinese-PRC, Chinese-Taiwan, Czech, Danish, Dutch-Netherlands, English-United States, Finnish, French-Canada, French-France, German, Greek, Hebrew, Hungarian, Italian, Japanese, Korean, Norwegian, Polish, Portuguese-Brazil, Portuguese-Europe, Russian, Spanish-Latin America, Spanish-Spain, Swedish, Turkish

Cisco Personal Communications Assistant (PCA) Help

Arabic-Saudi Arabia, Chinese-PRC, Chinese-Taiwan, Czech, Danish, Dutch-Netherlands, English-United States, French-Canada, French-France, German, Hungarian, Italian, Japanese, Korean, Polish, Portuguese-Brazil, Russian, Spanish-Latin America, Spanish-Spain, Swedish, Turkish

Cisco Unity Connection Administration

English-United States, Japanese

Cisco Unity Connection Administration Help

English-United States

Cisco ViewMail for Microsoft Outlook 12.0 and later

Arabic-Saudi Arabia, Catalan, Chinese-Hong Kong, Chinese-PRC, Chinese-Taiwan, Czech, Danish, Dutch-Netherlands, Finnish, French-Canada, French-France, German, Greek, Hebrew, Hungarian, Italian, Japanese, Korean, Norwegian, Polish, Portuguese-Brazil, Portuguese-Europe, Russian, Spanish-Latin America, Spanish-Spain, Swedish, Turkish

Cisco Unity Connection Web Inbox

Catalan, Chinese-Hong Kong, Chinese-PRC, Chinese-Taiwan, Czech, Danish, Dutch-Netherlands, English-United States, Finnish, French-Canada, French-France, German, Greek, Hungarian, Italian, Japanese, Korean, Norwegian, Polish, Portuguese-Brazil, Portuguese-Europe, Russian, Spanish-Latin America, Spanish-Spain, Swedish, Turkish

Cisco Unity Connection Mini Web Inbox

English-United States

Text-to-speech engine

Arabic-Saudi Arabia, Chinese-PRC, Catalan, Chinese-Hong Kong, Chinese-Taiwan, Czech, Danish, Dutch-Netherlands, English-Australia, English-United States, English-United Kingdom, Finnish, French-Canada, French-France, German, Hungarian, Italian, Japanese, Korean, Norwegian, Polish, Portuguese-Brazil, Portuguese-Europe, Russian, Spanish-Latin America, Spanish-Spain, Swedish, Turkish, Hebrew.

Transcription service for Cisco SpeechView

English-Australia, English-United States, English-United Kingdom, French-Canada, French-France, German, Italian, Portuguese-Brazil, Spanish-Latin America, Spanish-Spain

Voice-recognition engine

English-United States

Product documentation for administrators/installers

English-United States, Japanese

Product documentation for end users

Chinese-PRC, Chinese-Taiwan, Danish, Dutch-Netherlands, English-United States, French-France, German, Italian, Japanese, Korean, Portuguese-Brazil, Russian, Spanish-Latin America, Spanish-Spain, Swedish

Translated versions of the five Cisco Unity Connection user guides are available at http://www.cisco.com/en/US/products/ps6509/tsd_products_support_translated_end_user_guides_list.html.