Cisco Unity Connection 11.x Supported Platforms List

Revised June, 2016

This document provides information about the platforms supported for Cisco Unity Connection 11.x. The Unity Connection installation application prevents installation on servers that do not meet the exact specifications or models listed in this document.

Platform Overlays for Unity Connection

Unity Connection 11.x supports only virtual machines for installation. The Specifications for Virtual Platform Overlays for Currently Shipping Unity Connection lists the virtualization specifications, and the user and port limits when you install Unity Connection 11.x on a virtual machine.


Note
Unity Connection is not pre-installed on any platform. Unity Connection can only be installed on virtual machines.

Specifications for Virtual Platform Overlays for Currently Shipping Unity Connection Servers

This section describes specifications and limits for Unity Connection installed on a virtual machine.

For information on system requirements for a virtual environment, see the “Requirements for Installing Unity Connection on a Virtual Machine” section in the System Requirements for Cisco Unity Connection Release 11.x at https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/11x/requirements/b_11xcucsysreqs.html.

For platform/part number, see the link: http://docwiki.cisco.com/wiki/Virtualization_for_Cisco_Unity_Connection

Table 1. Specifications for Virtual Platform Overlays for Currently Shipping Unity Connection Servers

Virtual Platform Overlay for up to 200 Users

Virtual Platform Overlay for up to 1,000 Users

Virtual Platform Overlay for up to 5,000 Users

Virtual Platform Overlay for up to 10,000 Users

Virtual Platform Overlay for up to 20,000 Users

vCPU (Number of Virtual Processors)1 Cores and Speed per Core2

1@a minimum of 1.8 GHz

1@a minimum of 2.13 GHz (2.13 GHz reserved) or

2 @ minimum of 1.8 GHz each (3.6 GHz reserved)

2@a minimum of 2.53 GHz each (5.06 GHz reserved)

4@a for Xeon 5600 and 7500 processors- minimum of 2.53 GHz each(10.12 GHz reserved) or

4@a for Xeon E7 processors-minimum of 2.4 GHz each(9.6 GHz reserved)

7@a for Xeon 5600 and 7500 processors - minimum of 2.53 GHz each (17.71 GHz reserved)

7@a for Xeon E7 processors - minimum of 2.4 GHz each (16.8 GHz reserved)

vRAM (Amount of Virtual RAM)

4 GB reserved

4 GB reserved

6 GB reserved

6 GB reserved

8 GB reserved

vDisk (Size of Virtual Hard Disks)

1 x 160GB

1 x 160GB, file system aligned at 64KB blocks

1 x 200 GB, file system aligned at 64KB blocks

Select the required OVA configuration from the drop-down list available for up to 10,000 users:

  • 2 x 146 GB

  • 2 x 300 GB

  • 2 x 500 GB

File system aligned at 64KB blocks

Select the required OVA configuration from the drop-down list available for up to 20,000 users:

  • 2 x 300 GB

  • 2 x 500 GB

File system aligned at 64KB blocks

Total number of Tenants supported on Unity Connection

-

5

20

30

60

Total number of available ports per virtual machine: Voice + TTS  + Voice recognition

83

24

100

150

250

Total number of available ports in a cluster 4

16

48

200

300

500

Total number of concurrent video calls on each virtual machine (cluster/standalone deployment 4

0

2

2

2

20

Total number of users with mailboxes

200

1,000

5,000

10,000

20,000

Number of Cisco Personal Communications Assistant users

200

1,000

5,000

10,000

20,000

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)

0

1,000

5,000

10,000

20,000

Total number of LDAP Corporate Directory Users

200

1,000

5,000

10,000

20,000

Approximate message storage, G-711 codec, minutes

75,000

72,944

137,298

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

0

3

10

10

25

Total number of Unity Connection SRSV branches supported

0

10

35

35

35

Maximum number of Microsoft Office 365 users supported

0

For 1 vCPU - 0

For 2 vCPU - 1000 5

3000

6000

8000

Maximum number of Unified Messaging (SIB) users supported

0

For 1 vCPU - 0

For 2 vCPU - 1000 5

5000

10000

20000

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 Spec- based processor requirements, see http://docwiki.cisco.com/wiki/Unified_Communications_in_a_Virtualized_Environment
3 For 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.
4 For more information on MediaSense capabilities and supported concurrent video calls, see http://docwiki.cisco.com/wiki/Virtualization_for_Cisco_MediaSense. For lab testing purpose, any lower end MediaSense OVAs can be deployed.
5 To change the number of CPUs(1vCPU to 2vCPU) for 1000 users overlay, see "Modifying the CPU" section in the ReadMe of the applicable OVAs at https://software.cisco.com/download/type.html?mdfid=283062758&flowid=77763

Additional Information Related to Platform-Overlay Specifications

Unity Connection Cluster

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.

If the hard disk space does not match on the two servers that you are using for a cluster, the smaller amount of disk space determines the storage capacity for each server in the cluster. See also the “Requirements for a Unity Connection Cluster” section in System Requirements for Cisco Unity Connection Release 11.x at https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/11x/requirements/b_11xcucsysreqs.html.

IMAP Idle Clients

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

Revised May, 2019

The table contains information on the number of Jabber endpoints that Unity Connection supports with single inbox users for specific OVA.

Table 2. Non Secure Jabber Endpoints with Single Inbox Users
Virtual Platform Overlay vCPU (Number of Virtual Processors) Cores and Speed per Core Single Inbox Users Jabber Endpoints on a Standalone Server

Total Jabber Endpoints Per CUC Cluster (Load Balancing) 6

HA Jabber Endpoints Per CUC HA Pair

7
20,000 Users 7 vCPU 20,000 5,000 10,000 5,000
15,000 7,500 15,000 7,500
10,000 8,000 16,000 8,000
5,000 8,500 17,000 8,500
0 10,000 20,000 10,000
10,000 Users 4 vCPU 10,000 2,000 4,000 2,000
0 4,000 8,000 4,000
5,000 Users 2 vCPU 5,000 1,000 2,000 1,000

0

2,000

4,000

2,000
1,000 Users 2 vCPU 1,000 200 400 200
0 500 1000 500
1vCPU 0 100 200 100

The table contains information on the number of Jabber endpoints that Unity Connection supports with office 365 users for specific OVA.

Table 3. Non Secure Jabber Endpoints with Office 365 Users

Virtual Platform Overlay

vCPU (Number of Virtual Processors) Cores and Speed per Core

Office 365 Users

Jabber Endpoints on a Standalone Server

Total Jabber Endpoints Per CUC Cluster (Load Balancing) 6

HA Jabber Endpoints Per CUC HA Pair 7

20,000 Users

7vCPU

8,000

12,000

16,000

12,000

Note

Non secure Jabber endpoints for Office 365 users are yet not qualified with lower end OVAs

The table contains information on the number of secure Jabber endpoints that Unity Connection supports along with single inbox users.

Table 4. Secure Jabber Endpoints with Single Inbox Users
Virtual Platform Overlay vCPU (Number of Virtual Processors) Cores and Speed per Core Single Inbox Users Secure Jabber Endpoints on a Standalone Server

Total Secure Jabber Endpoints Per CUC Cluster (Load Balancing) 6

HA Secure Jabber Endpoints

Per CUC HA Pair 7

20,000 Users 7 vCPU 20,000 2,500 5,000 2,500
15,000 5,000 10,000 5,000
6 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.
7 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.

Note

  • The performance numbers qualified given are based on the assumptions that while user is using Jabber for voice messaging operation the user is having less telephony usage.

  • Secure Jabber endpoints for Single Inbox users are yet not qualified with lower end OVAs.

Configuring vCPU, vRAM, and vDisk for Unity Connection on 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.


Caution
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).

For information on downloading the latest OVA files, see the “Installation and Upgrade Information” section in the applicable Release Notes for Cisco Unity Connection at http://www.cisco.com/en/US/products/ps6509/prod_release_notes_list.html.

For information on deploying an OVA file while installing a new Unity Connection virtual server, see the “Installing Cisco Unity Connection” chapter of the Install, Upgrade, and Maintenance Guide for Cisco Unity Connection Release 11.x, at https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/11x/install_upgrade/guide/b_11xcuciumg.html.

For information on deploying an OVA file while migrating from a physical server to a virtual server, see the “Migrating a Physical Server to Virtual Machine” section of the “Maintaining Cisco Unity Connection Server” chapter of the Install, Upgrade, and Maintenance Guide for Cisco Unity Connection, Release 11.x, at https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/11x/install_upgrade/guide/b_11xcuciumg.html.

For information on deploying other Unified Communication applications on the same physical server with Unity Connection, see the Unified Communications Virtualization wiki at http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization.

Additional Platform Information

Replacing a Unity Connection Server as You Upgrade to Unity Connection 11.x

MCS servers are not supported for use with Unity Connection 11.x, and an attempt to install or upgrade to Unity Connection 11.x on these servers will fail. For more information on migrating a physical server to a virtual machine as you upgrade to Unity Connection 11.x, see the “Maintaining Cisco Unity Connection Server” chapter of the Install, Upgrade, and Maintenance Guide for Cisco Unity Connection, Release 11.x, at https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/11x/install_upgrade/guide/b_11xcuciumg.html.

Platform Overlays for Unity Connection SRSV

For hardware specifications and support limits on each platform, see the Specification for Hardware Platforms and Cisco IOS Software Releases Supported by Unity Connection SRSV.

The Specifications for Virtual Platform Overlays Supported by Unity Connection SRSV table lists the virtualization specifications, the user limit, and the port limit when you install Unity Connection SRSV on a virtual machine.

Specification for Hardware Platforms and Cisco IOS Software Releases Supported by Unity Connection SRSV

This section lists the supported hardware platforms and the minimum Cisco IOS software release required to support the hardware platform Unity Connection SRSV.

Table 5. Specifications for Unity Connection SRSV

Cisco Platform

Unity Connection SRSV on SM-SRE-900-K9

Unity Connection SRSV on SM-SRE-910-K9

UCS E140D, E140DP, E160D, and E160 DP

Cisco 2911

Cisco 2921

Cisco 2951

15.2(4)M4

15.2(4)M4

15.2(4)T

Cisco 3925

Cisco 3945

15.4(1)T

15.4(1)T

15.2(4)T

Cisco 3925E

Cisco 3945E

15.1(3)T

15.1(3)T

15.2(4)T

Cisco 4300

-

-

3.12S

Cisco 4400

-

-

3.13S and later


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

This section lists the specifications for virtual platform overlays supported by Cisco \\Unity Connection SRSV.

Table 6. Specifications for Supported Virtual Platform Overlays by Unity Connection SRSV

Virtual Platform Overlay

vCPU (Number of Virtual Processors) Cores and Speed per Core

1@a minimum of 1.8 GHz

vRAM (Amount of Virtual RAM)

4 GB

vDisk (Size of Virtual Hard Disks)

1x160GB

Total number of available voice ports

12

Total number of users with mailboxes

500

Approximate message storage, G-711 codec, minutes

72,944

Number of public distribution lists

500

Number of Call Handlers

500

Number of languages supported

2