Cisco Unity Connection 10.x Supported Platforms List
Revised Feb, 2017
This document provides information about the platforms supported for Unity Connection 10.x, including those shipped by Cisco and those provided by customers. The Unity Connection installation application prevents installation on servers that do not meet the exact specifications or models listed in this document.
Number of Cisco Personal Communications Assistant users
Total number of active clients: Cisco Unified Personal Communicator + Third-party IMAP + Cisco Unity conferencing + Cisco Unified Mobile Advantage + RSS + Phone View users (assumes all IMAP Idle clients; see the
“IMAP Idle Clients” section)
Total number of LDAP Corporate Directory Users
Approximate message storage, G-711 codec, minutes
Depends on the.ova file:
2 x 146 GB: 252,831
2 x 300 GB: 514,287
2 x 500 GB: 919,992
Depends on the.ova file:
2 x 300 GB: 514,287
2 x 500 GB: 919,992
Unity Connection locations in the HTTPS network
Total number of Unity Connection SRSV branches supported
Maximum number of Unified Messaging (SIB) users supported
@ 1 vcpu - 0
@ 2 vcpu - 1000
1.For VMware vSphere ESXi 5.1 and earlier, at least one processor core must be available for the VMware ESXi hypervisor / scheduler.
2.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.
4.2 vCPU is supported only with Cisco Unity Connection 10.5(1) and later releases only.
5.For SRE-910 and UCS E blade, though you are allowed to create more than 8 ports on Cisco Unity Connection Administration, it is recommended to create a maximum of 8 ports to avoid performance issues.
6.The SRE-910 and UCS E blade support 100 users with voicemail only.
7.The total number of Unity Connection SRSV branches supported is applicable only for Unity Connection 10.5(1) and later releases. The total number for SRSV branches supported for Unity Connection 10.0(1) is 5.
8.The total number of Unity Connection SRSV branches supported is applicable only for Unity Connection 10.5(1) and later releases. The total number for SRSV branches supported for Unity Connection 10.0(1) is 10.
9.The total number of Unity Connection SRSV branches supported is applicable only for Unity Connection 10.5(1) and later releases. The total number for SRSV branches supported for Unity Connection 10.0(1) is 10.
10.The total number of Unity Connection SRSV branches supported is applicable only for Unity Connection 10.5(1) and later releases. The total number for SRSV branches supported for Unity Connection 10.0(1) is 10.
The Unity Connection cluster feature provides high-availability voice messaging with two Unity Connection servers that are configured in a cluster. In this configuration, also known as active-active high availability, a single node consists of two servers, and the number of ports depends on the server model. The total number of node ports is additive (meaning a single node can support up to 500 ports, but the total number of users supported is applicable only to the primary server. The primary and secondary servers in a cluster must match in CPU and amount of memory, or the configuration is not supported.
The calculations for the total number of active clients assume the use of IMAP clients that support IMAP Idle. Cisco Unified Personal Communicator 7.0 and earlier, Cisco Unified Mobility Advantage, and Cisco Unified Mobile Communicator do not support IMAP Idle. As a result, each active instance of each of these clients (that does not support IMAP Idle) that is accessing Unity Connection voice messages counts as four active clients.
Jabber Scaling Platform (Unity Connection 10.5(2) SU2 and later)
Updated Feb, 2017
The table displays information of the number of Jabber Client that are supported in Unity connection along with single inbox users based on specific OVA.
12.In Load Balancing, Jabber clients are statically configured on either publisher server or subscriber server. If any of the server stops functioning, the services of the Jabber clients configured on the server go down.
13.In HA pair, Jabber clients are configured on publisher server. If publisher server stops functioning, the subscriber server provides services to the configured Jabber clients. However, Jabber in HA is not supported during upgrade in RU and during switch version in L2.
NoteThe number of qualified users given in the table are based on the assumptions that while using Jabber for voice messaging operation the users have less telephony usage.
Configuring vCPU, vRAM, and vDisk for Virtual Machines
To simplify deployment of Unity Connection on a virtual machine, Cisco provides OVA templates for the virtual platform overlays defined in Table 1.
Changing the number of virtual CPUs, the amount of virtual RAM, or the number or size of virtual disks is not supported.
In addition, the OVA templates align the file system on the virtual disk(s) in the virtual machine at 64-KB blocks, which results in improved storage input/output operations per second (IOPS).
Replacing a Unity Connection Server as You Upgrade to Unity Connection 10.x
MCS servers are not supported for use with Unity Connection 10.x, and an attempt to install or upgrade to Unity Connection 10.x on these servers will fail. For more information on migrating a physical server to a virtual machine as you upgrade to Unity Connection 10.x, see the applicable chapter in the Reconfiguration and Upgrade Guide for Cisco Unity Connection Release 10.x at
Specification for Hardware Platforms and Cisco IOS Software Releases Supported by Unity Connection SRSV 10.0(1) and later
This section lists the supported hardware platforms and the minimum Cisco IOS software release required to support the hardware platform Cisco Unity Connection SRSV.
Table 5 Specifications for Cisco Unity Connection SRSV
Unity Connection SRSV on SM-SRE-900-K9
Unity Connection SRSV on SM-SRE-910-K9
UCS E140D, E140DP, E160D, and E160 DP
3.13S and later
NoteA different Cisco IOS software release may be required depending on the version of Cisco Unified Communications Manager Express or Cisco Unified Survivable Remote Site Telephony (SRST) being used. For more information refer to Cisco Unified Communications Manager Express documentation available at http://www.cisco.com/en/US/products/sw/voicesw/ps4625/index.html.
Specifications for Virtual Platform Overlays Supported by Unity Connection SRSV 10.0(1) and later
This section lists the specifications for virtual platform overlays supported by Cisco Unity Connection SRSV.
Table 6 Specifications for Supported Virtual Platform Overlays by Cisco Unity Connection SRSV
Virtual Platform Overlay
vCPU (Number of Virtual Processors) Cores and Speed per Core
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. (1721R)