Cisco Unity Connection 10.x Supported Platforms List

Available Languages

Download Options

  • PDF     (337.5 KB)
    View with Adobe Reader on a variety of devices
Updated:July 23, 2014

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Table of Contents

Cisco Unity Connection 10.x Supported Platforms List

Contents

Platform Overlays

Specifications for Virtual Platform Overlays

Additional Information Related to Platform-Overlay Specifications

Cisco Unity Connection Cluster

IMAP Idle Clients

Jabber Scaling Platform (Unity Connection 10.5(2) SU2 and later)

Configuring vCPU, vRAM, and vDisk for Virtual Machines

Additional Platform Information

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

Supported Platform

Specifications for Currently Shipping Platforms Supported for Unity Connection 10.x

Currently Shipping Blade Servers for Cisco Integrated Services Routers Generation 2 (ISR G2)

Cisco SRE-900 and SRE-910

Cisco UCS E140D, E140DP, E160D, and E160DP

Currently Shipping Platforms for Virtual Configurations

Specification for Hardware Platforms and Cisco IOS Software Releases Supported by Unity Connection SRSV 10.0(1) and later

Specifications for Virtual Platform Overlays Supported by Unity Connection SRSV 10.0(1) and later

Specification for HTTPS Networking

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.

Contents

Platform Overlays

For additional specifications and support limits on each platform, see the applicable section:

Note Cisco Unity Connection 10.x is not pre-installed on any platform. Unity Connection 10.0(1) and later can only be installed on virtual machines.

Specifications for Virtual Platform Overlays

Revised March 10, 2015

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

For information on system requirements for a virtual environment, see the “Requirements for Installing Cisco Unity Connection on a Virtual Machine” section in the System Requirements for Cisco Unity Connection Release 10.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/10x/requirements/10xcucsysreqs.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 10.x Servers

Virtual Platform Overlay for up to 100 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 2 per Core 3

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)4

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

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

or

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

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

or

For Xeon E7 processors -7@a 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

85

24

100

150

250
Total number of available ports in a cluster

16

48

200

300

500
Total number of concurrent video calls

0

0

0

0

35
Total number of concurrent video calls in a cluster

0

0

0

0

40
Total number of users with mailboxes

1006

1,000

5,000

10,000

20,000
Number of Cisco Personal Communications Assistant users

100

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; see the “IMAP Idle Clients” section)

0

1,000

5,000

10,000

20,000
Total number of LDAP Corporate Directory Users

100

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

-

3

10

10

25
Total number of Unity Connection SRSV branches supported

0

107

358

359

3510
Maximum number of Microsoft Office 365 users supported

011

@ 1 vcpu - 0

@ 2 vcpu - 1000

3000

6000

8000
Maximum number of Unified Messaging (SIB) users supported

0 11

@ 1 vcpu - 0

@ 2 vcpu - 1000

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

3.For Spec- based processor requirements, see http://docwiki.cisco.com/wiki/Specification-Based_Hardware_Support#Processor_Requirements.

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.

11.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/release.html?mdfid=283062758&release=OVA-10.5&softwareid=282074348&sortparam=

Cisco 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 Cisco Unity Connection 10.x Cluster” section in System Requirements for Cisco Unity Connection Release 10.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/10x/requirements/10xcucsysreqs.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 (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.

Table 2 Jabber Scaling Platform
Single Inbox Users
Jabber Endpoints Per Single Server (PUB or SUB)
Total Jabber Endpoints
Per CUC Cluster (Load Balancing) 12
Jabber Endpoints
Per CUC HA Pair 13

7vCPU

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

4vCPU

10,000

2,000

4,000

2,000

2vcpu

5,000

1,000

2,000

1,000

1,000

200

400

200

0

500

1,000

500

1vcpu

0

100

200

100

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.

Note The 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.

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 Install, Upgrade,and Maintenance Guide for Cisco Unity Connection Release 10.x at http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/10x/install_upgrade/guide/10xcuciumgx.html.

For information on deploying an OVA file while migrating from a physical server to a virtual server, see the “Migrating from a Cisco Unity Connection Physical Server to a Unity Connection 10.x Virtual Server” chapter of the Reconfiguration and Upgrade Guide for Cisco Unity Connection Release 10.x. .

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

http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/10x/install_upgrade/guide/10xcuciumgx/10xcuciumg050.html#45986

Supported Platform

For detailed specifications on virtual platforms supported with Unity Unity Connection 10.0(1) and later, see

http://docwiki.cisco.com/wiki/Virtualization_for_Cisco_Unity_Connection.

Specifications for Currently Shipping Platforms Supported for Unity Connection 10.x

Currently Shipping Blade Servers for Cisco Integrated Services Routers Generation 2 (ISR G2)

Cisco SRE-900 and SRE-910

 

Table 3 Cisco SRE-900 and SRE-910 Platforms

Feature
Description

Model numbers

SM-SRE-900-K9

SM-SRE-910-K9

Supplier

Cisco

Form factor

SM

Mounting

Rack-mount

Physical processor(s)

Intel Core2 Duo, 1.86 GHz

Physical RAM (as shipped)

4 GB (default) or 8 GBDRAMs

Physical hard disk

Two 500-GB SATA (1 TB in non-RAID mode)

5400 rpm (SRE 900)

7200 rpm (SRE 910)

RAID controller

SATA on board

RAID configuration

RAID 0 or 1 (application dependant)

Total available disk space

1 TB

Hardware reconfiguration required

None

More information

http://www.cisco.com/en/US/prod/collateral/modules/ps10598/data_sheet_c78-553913.html

For more information on SRE-900 and SRE-910, refer to http://docwiki.cisco.com/wiki/Cisco_Unity_Connection_on_UCSE.

Cisco UCS E140D, E140DP, E160D, and E160DP

 

Table 4 Cisco UCS E140D, E140DP, E160D, and E160DP Platforms

Feature
Description

Model numbers

UCS E140D, E140DP, E160D, E160DP

Supplier

Cisco

Form factor

Double-wide Blades

Physical processor(s)

Intel® Xeon® E5-2418L 2.0GHz quad core processor

Intel® Xeon® E5-2428L 1.8GHz 6-core processor

Physical RAM (as shipped)

8 GB (default) and up to 48 GB (three 16-GB DIMMs)

Physical hard disk

Up to three (Cisco UCS E140D or E160D) or two (Cisco UCS E140DP or E160DP):

  • 7200-RPM SATA: 1 TB
  • 10,000-RPM SAS: 900 GB
  • 10,000-RPM SAS SED: 600 GB
  • SAS SSD SLC: 200 GB

RAID controller

LSI MegaRAID controller

RAID configuration
  • Cisco UCS E140D and E160D: Hardware RAID 0, 1, and 5
  • Cisco UCS E140DP and E160DP: Hardware RAID 0 and 1
  • LSI MegaRAID controller

Total available disk space

1 TB

Hardware reconfiguration required

None

More information

http://www.cisco.com/en/US/prod/collateral/ps10265/ps12629/data_sheet_c78-705787.html

For more information on UCS E-140D, E140DP, E160D, and E160DP, refer to http://docwiki.cisco.com/wiki/Cisco_Unity_Connection_on_UCSE.

Currently Shipping Platforms for Virtual Configurations

Unity Unity Connection 10.0(1) and later releases can only be installed on virtual machines. For more information on currently shipped platforms for virtual configurations, see

http://docwiki.cisco.com/wiki/Virtualization_for_Cisco_Unity_Connection

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
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)M

Cisco 3925

Cisco 3945

15.4(1)T

15.4(1)T

15.2(4)M

Cisco 3925E

Cisco 3945E

15.1(3)T

15.1(3)T

15.2(4)M

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

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 14

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

200
Number of languages supported

2

14.For Unity Connection 10.0(1), the total number of available voice ports is 8. Out of this, 6 ports are G.711 or G.729a (combined TUI or TTS) and 2 ports are iLBC or G.722

 

Specification for HTTPS Networking

You can use HTTPS networking to link one or more Cisco Unity Connection servers or clusters to form a well-connected network based on hub-spoke topology.

For more information, see Requirements for HTTPS Networking section in

http://www.cisco.com/en/US/docs/voice_ip_comm/connection/10x/requirements/10xcucsysreqs.html

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)

© 2014 Cisco Systems, Inc. All rights reserved.

Was this Document Helpful?

FeedbackFeedback

Contact Cisco