Virtualization for Cisco Meeting Server

If you want to run Meeting Server on hardware that is not listed below (e.g. Cisco Multiparty Media 400v/ 410v Server/ 410v Blade Server or CMS1000) then see Cisco Meeting Server documentation.

Co-residency support = See notes for Recording and Streaming VM
Full for all other VMs

Supported Versions of VMware vSphere ESXi = 6.0 U3, 6.5 U2, 6.7, (VMware have made changes in their recent versions (6.0 U3, 6.5 U2 and 6.7). As a consequence of these changes the throughput of audio calls on Cisco Meeting Server has been reduced (video capacity is unaffected) refer to release notes for more information.)
Click for "IOPS"

Component &
Capacity Point

VM Configuration Requirements
click to download OVA file

Supported Hardware (Latest)
Click here to download support of older/non-orderable servers

vCPU

vRAM

vDisk

vNIC

UCS Tested Reference Configurations

UCS or 3rd-party Specs-based on Intel Xeon

Callbridge VM or
Combined VM (Edge + Callbridge + DB)
See notes

4+
(1 vCPU per 1.25 HD ports)

4+ GB
(1 per Physical Core)

1x 100GB

1

No

Yes
See notes

Yes
See notes

Yes

All except HX220c M5SX TRC#1

Yes

Yes
See notes

Edge VM

4 or 8
See notes

4 or 8GB
See notes

1x 100GB

1

No

Yes

Yes

Yes

All except HX220c M5SX TRC#1

Yes

Yes

Database VM

8

8GB

1x 100GB

1

No

Yes

Yes

Yes

All except HX220c M5SX TRC#1

Yes

Yes

Recording VM

min 4
See notes

min 4GB and .5GB per vCPU
See notes

1x 100GB

1

No

Yes

Yes

Yes

All except HX220c M5SX TRC#1

Yes

Yes
See notes

Streaming VM

min 4, max 8
See notes

min 4, recommended 8GB
See notes

1x 100GB

1

No

Yes

Yes

Yes

All except HX220c M5SX TRC#1

Yes

Yes
See notes

Version 2.9

(top)

ALERT! This page has been updated to reflect compatibility with the latest M5 hardware. Click here to download support for M4 and older hardware.

This information listed here for convenience. For latest information, when in doubt, conflict, review the Cisco Meeting Server documentation.

If you want to run Meeting Server on hardware that is not listed below (e.g. Cisco Multiparty Media 400v/ 410v Server/ 410v Blade Server or CMS1000) then see Cisco Meeting Server documentation.

Co-residency support = See deployment guide for Recording and Streaming VM
Full for all other VMs

Supported Versions of VMware vSphere ESXi = 6.0 U3, 6.5 U2, 6.7 (VMware have made changes in their recent versions (6.0 U3, 6.5 U2 and 6.7). As a consequence of these changes the throughput of audio calls on Cisco Meeting Server has been reduced (video capacity is unaffected) refer to release notes for more information.)
Click for "IOPS"

Component &
Capacity Point

VM Configuration Requirements
click to download OVA file

Supported Hardware (Latest)
Click here to download support of older/non-orderable servers

vCPU

vRAM

vDisk

vNIC

UCS Tested Reference Configurations

UCS or 3rd-party Specs-based on Intel Xeon

Callbridge VM or
Combined VM (Edge + Callbridge + DB)
See notes

4+
(1 vCPU per 1.25 HD ports)

4+ GB
(1 per Physical Core)

1x 100GB

1

No

Yes
See notes

Yes
See notes

Yes

All except HX220c M5SX TRC#1

Yes

Yes
See notes

Edge VM

4 or 8
See notes

4 or 8GB
See notes

1x 100GB

1

No

Yes

Yes

Yes

All except HX220c M5SX TRC#1

Yes

Yes

Database VM

8

8GB

1x 100GB

1

No

Yes

Yes

Yes

All except HX220c M5SX TRC#1

Yes

Yes

Recording VM

min 4, max 24
See deployment guide

0.5GB per vCPU
See deployment guide

1x 100GB

1

No

Yes

Yes

Yes

All except HX220c M5SX TRC#1

Yes

Yes
See deployment guide

Streaming VM

min 4, max 32
See deployment guide

1GB per vCPU
See deployment guide

1x 100GB

1

No

Yes

Yes

Yes

All except HX220c M5SX TRC#1

Yes

Yes
See deployment guide

Version 2.8

(top)

ALERT! This page has been updated to reflect compatibility with the latest M5 hardware. Click here to download support for M4 and older hardware.

This information listed here for convenience. For latest information, when in doubt, conflict, review the Cisco Meeting Server documentation.

If you want to run Meeting Server on hardware that is not listed below (e.g. Cisco Multiparty Media 400v/ 410v Server/ 410v Blade Server or CMS1000) then see Cisco Meeting Server documentation.

Version 2.7

(top)

ALERT! This page has been updated to reflect compatibility with the latest M5 hardware. Click here to download support for M4 and older hardware.

This information listed here for convenience. For latest information, when in doubt, conflict, review the Cisco Meeting Server documentation.

If you want to run Meeting Server on hardware that is not listed below (e.g. Cisco Multiparty Media 400v/ 410v Server/ 410v Blade Server or CMS1000) then see Cisco Meeting Server documentation.

Co-residency support = Full for all other VMs

Supported Versions of VMware vSphere ESXi = 6.0 U3, 6.5 U2, 6.7 (ESXi 6.7 is not supported with the C220/C240 M4 models including CMS 1000 M4 model. For application fresh installs on ESXi 6.5 (VMFS5 or 6) and/or vCenter 6.5, use minimum OVA file version Cisco_Meeting_Server_2_7_0.ova. Does not apply to ESXi version upgrades. See Ordering guide for ESXi minimum feature level.)
Click for "IOPS"

Component &
Capacity Point

VM Configuration Requirements
click to download OVA file

Supported Hardware (Latest)
Click here to download support of older/non-orderable servers

vCPU

vRAM

vDisk

vNIC

UCS Tested Reference Configurations

UCS or 3rd-party Specs-based on Intel Xeon

Callbridge VM or
Combined VM (Edge + Callbridge + DB)

4+
(1 vCPU per 1.25 HD ports)

4+ GB
(1 per Physical Core)

1x 100GB

1

No

Yes

Yes

Yes

All except HX220c M5SX TRC#1

Yes

Yes

Edge VM

4 or 8

4 or 8GB

1x 100GB

1

No

Yes

Yes

Yes

All except HX220c M5SX TRC#1

Yes

Yes

Database VM

8

8GB

1x 100GB

1

No

Yes

Yes

Yes

All except HX220c M5SX TRC#1

Yes

Yes

Recording VM

min 4, max 24

0.5GB per vCPU

1x 100GB

1

No

Yes

Yes

Yes

All except HX220c M5SX TRC#1

Yes

Yes

Streaming VM

min 4, max 32

1GB per vCPU

1x 100GB

1

No

Yes

Yes

Yes

All except HX220c M5SX TRC#1

Yes

Yes

Version 2.6

(top)

ALERT! This page has been updated to reflect compatibility with the latest M5 hardware. Click here to download support for M4 and older hardware.

This information listed here for convenience. For latest information, when in doubt, conflict, review the Cisco Meeting Server documentation.

If you want to run Meeting Server on hardware that is not listed below (e.g. Cisco Multiparty Media 400v/ 410v Server/ 410v Blade Server or CMS1000) then see Cisco Meeting Server documentation.

Co-residency support = Full for all other VMs

Supported Versions of VMware vSphere ESXi = 6.0 U3, 6.5 U2, 6.7 (ESXi 6.7 is not supported with the C220/C240 M4 models including CMS 1000 M4 model. For application fresh installs on ESXi 6.5 (VMFS5 or 6) and/or vCenter 6.5, use minimum OVA file version Cisco_Meeting_Server_2_6_0.ova. Does not apply to ESXi version upgrades. See Ordering guide for ESXi minimum feature level.)
Click for "IOPS"

Component &
Capacity Point

VM Configuration Requirements
click to download OVA file

Supported Hardware (Latest)
Click here to download support of older/non-orderable servers

vCPU

vRAM

vDisk

vNIC

UCS Tested Reference Configurations

UCS or 3rd-party Specs-based on Intel Xeon

Callbridge VM or
Combined VM (Edge + Callbridge + DB)

4+
(1 vCPU per 1.25 HD ports)

4+ GB
(1 per Physical Core)

1x 100GB

1

No

Yes

Yes

Yes

All except HX220c M5SX TRC#1

Yes

Yes

Edge VM

4 or 8

4 or 8GB

1x 100GB

1

No

Yes

Yes

Yes

All except HX220c M5SX TRC#1

Yes

Yes

Database VM

8

8GB

1x 100GB

1

No

Yes

Yes

Yes

All except HX220c M5SX TRC#1

Yes

Yes

Recording VM

min 4, max 24

0.5GB per vCPU

1x 100GB

1

No

Yes

Yes

Yes

All except HX220c M5SX TRC#1

Yes

Yes

Streaming VM

min 4, max 32

1GB per vCPU

1x 100GB

1

No

Yes

Yes

Yes

All except HX220c M5SX TRC#1

Yes

Yes

Version 2.5

(top)

ALERT! This page has been updated to reflect compatibility with the latest M5 hardware. Click here to download support for M4 and older hardware.

This information listed here for convenience. For latest information, when in doubt, conflict, review the Cisco Meeting Server documentation.

If you want to run Meeting Server on hardware that is not listed below (e.g. Cisco Multiparty Media 400v/ 410v Server/ 410v Blade Server or CMS1000) then see Cisco Meeting Server documentation.

Co-residency support = Full for all other VMs

Supported Versions of VMware vSphere ESXi = 6.0 U3, 6.5 (For application fresh installs on ESXi 6.5 (VMFS5 or 6) and/or vCenter 6.5, use minimum OVA file version Cisco_Meeting_Server_2_5_0.ova. Does not apply to ESXi version upgrades. See Ordering guide for ESXi minimum feature level.)
Click for "IOPS"

Component &
Capacity Point

VM Configuration Requirements
click to download OVA file

Supported Hardware (Latest)
Click here to download support of older/non-orderable servers

vCPU

vRAM

vDisk

vNIC

UCS Tested Reference Configurations

UCS or 3rd-party Specs-based on Intel Xeon

Callbridge VM or
Combined VM (Edge + Callbridge + DB)

4+
(1 vCPU per 1.25 HD ports)

4+ GB
(1 per Physical Core)

1x 100GB

1

No

Yes

Yes

Yes

All except HX220c M5SX TRC#1

Yes

Yes

Edge VM

4 or 8

4 or 8GB

1x 100GB

1

No

Yes

Yes

Yes

All except HX220c M5SX TRC#1

Yes

Yes

Database VM

8

8GB

1x 100GB

1

No

Yes

Yes

Yes

All except HX220c M5SX TRC#1

Yes

Yes

Recording VM

min 4, max 24

0.5GB per vCPU

1x 100GB

1

No

Yes

Yes

Yes

All except HX220c M5SX TRC#1

Yes

Yes

Streaming VM

min 4, max 32

1GB per vCPU

1x 100GB

1

No

Yes

Yes

Yes

All except HX220c M5SX TRC#1

Yes

Yes

Version 2.4

(top)

ALERT! This page has been updated to reflect compatibility with the latest M5 hardware. Click here to download support for M4 and older hardware.

This information listed here for convenience. For latest information, when in doubt, conflict, review the Cisco Meeting Server documentation.

If you want to run Meeting Server on hardware that is not listed below (e.g. Cisco Multiparty Media 400v/ 410v Server/ 410v Blade Server or CMS1000) then see Cisco Meeting Server documentation.

Co-residency support = Full for all other VMs

Supported Versions of VMware vSphere ESXi = 6.0 U3, 6.5 (For application fresh installs on ESXi 6.5 (VMFS5 or 6) and/or vCenter 6.5, use minimum OVA file version Cisco_Meeting_Server_2_4_0.ova. Does not apply to ESXi version upgrades. See Ordering guide for ESXi minimum feature level.)
Click for "IOPS"

Component &
Capacity Point

VM Configuration Requirements
click to download OVA file

Supported Hardware (Latest)
Click here to download support of older/non-orderable servers

vCPU

vRAM

vDisk

vNIC

UCS Tested Reference Configurations

UCS or 3rd-party Specs-based on Intel Xeon

Callbridge VM or
Combined VM (Edge + Callbridge + DB)

4+
(1 vCPU per 1.25 HD ports)

4+ GB
(1 per Physical Core)

1x 100GB

1

No

Yes

Yes

Yes

All except HX220c M5SX TRC#1

Yes

Yes

Edge VM

4 or 8

4 or 8GB

1x 100GB

1

No

Yes

Yes

Yes

All except HX220c M5SX TRC#1

Yes

Yes

Database VM

8

8GB

1x 100GB

1

No

Yes

Yes

Yes

All except HX220c M5SX TRC#1

Yes

Yes

Recording VM

min 4, max 24

0.5GB per vCPU

1x 100GB

1

No

Yes

Yes

Yes

All except HX220c M5SX TRC#1

Yes

Yes

Streaming VM

min 4, max 32

1GB per vCPU

1x 100GB

1

No

Yes

Yes

Yes

All except HX220c M5SX TRC#1

Yes

Yes

Version 2.3

(top)

ALERT! This page has been updated to reflect compatibility with the latest M5 hardware. Click here to download support for M4 and older hardware.

This information listed here for convenience. For latest information, when in doubt, conflict, review the Cisco Meeting Server documentation.

If you want to run Meeting Server on hardware that is not listed below (e.g. Cisco Multiparty Media 400v/ 410v Server/ 410v Blade Server or CMS1000) then see Cisco Meeting Server documentation.

Co-residency support = Full for all other VMs

Supported Versions of VMware vSphere ESXi = 6.0 U3, 6.5 (For application fresh installs on ESXi 6.5 (VMFS5 or 6) and/or vCenter 6.5, use minimum OVA file version Cisco_Meeting_Server_2_3_0.ova. Does not apply to ESXi version upgrades. See Ordering guide for ESXi minimum feature level.)
Click for "IOPS"

Component &
Capacity Point

VM Configuration Requirements
click to download OVA file

Supported Hardware (Latest)
Click here to download support of older/non-orderable servers

vCPU

vRAM

vDisk

vNIC

UCS Tested Reference Configurations

UCS or 3rd-party Specs-based on Intel Xeon

Callbridge VM or
Combined VM (Edge + Callbridge + DB)

4+
(1 vCPU per 1.25 HD ports)

4+ GB
(1 per Physical Core)

1x 100GB

1

No

Yes

Yes

Yes

All except HX220c M5SX TRC#1

Yes

Yes

Edge VM

4 or 8

4 or 8GB

1x 100GB

1

No

Yes

Yes

Yes

All except HX220c M5SX TRC#1

Yes

Yes

Database VM

8

8GB

1x 100GB

1

No

Yes

Yes

Yes

All except HX220c M5SX TRC#1

Yes

Yes

Recording VM

min 4, max 24

0.5GB per vCPU

1x 100GB

1

No

Yes

Yes

Yes

All except HX220c M5SX TRC#1

Yes

Yes

Streaming VM

min 4, max 32

1GB per vCPU

1x 100GB

1

No

Yes

Yes

Yes

All except HX220c M5SX TRC#1

Yes

Yes

Version 2.2

(top)

ALERT! This page has been updated to reflect compatibility with the latest M5 hardware. Click here to download support for M4 and older hardware.

This information listed here for convenience. For latest information, when in doubt, conflict, review the Cisco Meeting Server documentation.

If you want to run Meeting Server on hardware that is not listed below (e.g. Cisco Multiparty Media 400v/ 410v Server/ 410v Blade Server or CMS1000) then see Cisco Meeting Server documentation.

Co-residency support = Full for all other VMs

Supported Versions of VMware vSphere ESXi = 5.1 U2, 5.5 U1, 6.0 (See Ordering guide for ESXi minimum feature level)
Click for "IOPS"

Component &
Capacity Point

VM Configuration Requirements
click to download OVA file

Supported Hardware (Latest)
Click here to download support of older/non-orderable servers

vCPU

vRAM

vDisk

vNIC

UCS Tested Reference Configurations

UCS or 3rd-party Specs-based on Intel Xeon

Callbridge VM or
Combined VM (Edge + Callbridge + DB)

4+
(1 vCPU per 1.25 HD ports)

4+ GB
(1 per Physical Core)

1x 100GB

1

No

Yes

Yes

Yes

All except HX220c M5SX TRC#1

Yes

Yes

Edge VM

4 or 8

4 or 8GB

1x 100GB

1

No

Yes

Yes

Yes

All except HX220c M5SX TRC#1

Yes

Yes

Database VM

8

8GB

1x 100GB

1

No

Yes

Yes

Yes

All except HX220c M5SX TRC#1

Yes

Yes

Recording VM

min 4, max 24

0.5GB per vCPU

1x 100GB

1

No

Yes

Yes

Yes

All except HX220c M5SX TRC#1

Yes

Yes

Streaming VM

min 4, max 32

1GB per vCPU

1x 100GB

1

No

Yes

Yes

Yes

All except HX220c M5SX TRC#1

Yes

Yes

Version 2.1

(top)

ALERT! This page has been updated to reflect compatibility with the latest M5 hardware. Click here to download support for M4 and older hardware.

This information listed here for convenience. For latest information, when in doubt, conflict, review the Cisco Meeting Server documentation.

If you want to run Meeting Server on hardware that is not listed below (e.g. Cisco Multiparty Media 400v/ 410v Server/ 410v Blade Server or CMS1000) then see Cisco Meeting Server documentation.

Co-residency support = Full for all other VMs

Supported Versions of VMware vSphere ESXi = 5.1 U2, 5.5 U1, 6.0 (See Ordering guide for ESXi minimum feature level)
Click for "IOPS"

Component &
Capacity Point

VM Configuration Requirements
click to download OVA file

Supported Hardware (Latest)
Click here to download support of older/non-orderable servers

vCPU

vRAM

vDisk

vNIC

UCS Tested Reference Configurations

UCS or 3rd-party Specs-based on Intel Xeon

Callbridge VM or
Combined VM (Edge + Callbridge + DB)

4+
(1 vCPU per 1.25 HD ports)

4+ GB
(1 per Physical Core)

1x 100GB

1

No

No

No

No

No

No

No

Edge VM

4 or 8

4 or 8GB

1x 100GB

1

No

No

No

No

No

No

No

Database VM

8

8GB

1x 100GB

1

No

No

No

No

No

No

No

Recording VM

min 4, max 24

0.5GB per vCPU

1x 100GB

1

No

No

No

No

No

No

No

Streaming VM

min 4, max 32

1GB per vCPU

1x 100GB

1

No

No

No

No

No

No

No

* See mouse-over column heading for details

Version 2.0

(top)

ALERT! This page has been updated to reflect compatibility with the latest M5 hardware. Click here to download support for M4 and older hardware.

This information listed here for convenience. For latest information, when in doubt, conflict, review the Cisco Meeting Server documentation.

If you want to run Meeting Server on hardware that is not listed below (e.g. Cisco Multiparty Media 400v/ 410v Server/ 410v Blade Server or CMS1000) then see Cisco Meeting Server documentation.

Co-residency support = Full for all other VMs.

Supported Versions of VMware vSphere ESXi = 5.1 U2, 5.5 U1, 6.0 (See Ordering guide for ESXi minimum feature level)
Click for "IOPS"

Component &
Capacity Point

VM Configuration Requirements
click to download OVA file

Supported Hardware (Latest)
Click here to download support of older/non-orderable servers

vCPU

vRAM

vDisk

vNIC

UCS Tested Reference Configurations

UCS or 3rd-party Specs-based on Intel Xeon

Callbridge VM or
Combined VM (Edge + Callbridge + DB)

4+
(1 vCPU per 1.25 HD ports)

4+ GB
(1 per Physical Core)

1x 100GB

1

No

No

No

No

No

No

No

Edge VM

4 or 8

4 or 8GB

1x 100GB

1

No

No

No

No

No

No

No

Database VM

8

8GB

1x 100GB

1

No

No

No

No

No

No

No

Recording VM

min 4, max 24

.5GB per vCPU

1x 100GB

1

No

No

No

No

No

No

No

* See mouse-over column heading for details

Notes

(top)

Review the Cisco Meeting Server documentation for more information

Callbridge VM or Combined VM (Edge + Callbridge):
The Callbridge supports Intel Xeon E5 2600 series (i.e. dual socket) or later processors and requires a minimum quantity of 4 vCPU. Where the clock speed is 2.5GHz or above each vCPU provides 1.25 HD ports. Where the clock speed is less than 2.5GHz, the 4 vCPU minimum still applies but each vCPU provides less than 1.25 HD ports. To calculate the capacity of each vCPU, divide the clock speed by 2.5 and multiply that by 1.25, for example a processor with 2.0GHz provides (2.0/ 2.5) x 1.25 = 1 HD port per vCPU. Capacity scales linearly with number of vCPUs so a system with 40 vCPUs allocated to CMS, with a clock speed of 2.5GHz can handle 50 concurrent 720p30 H.264 call legs.

Running a single VM
When running a single virtual machine on a host, one physical core per host must be left unused by apps for ESXi scheduler. With a single VM, it is possible to use hyper-threading to increase the available capacity. In this case the number of available vCPUs is double the number of physical cores in use. So a two socket system which has 20 physical cores will have 19 available to the application. With hyper-threading enabled, 38vCPUs can be used, which should be allocated to the CMS VM, and the other 2 left unused. If an option is available to choose both number of sockets and number of cores per socket, then these should mirror the underlying hardware.

Running multiple VMs co-resident on a single host
When running multiple virtual machine on a single host, at most one vCPU per physical core should be allocated regardless of the hyper-threading mode. If an option is available to choose both number of sockets and number of cores per socket for a VM, a single socket should be configured with all the virtual CPU cores.

When using VMware 5.5+ with multiple VMs and the Latency Sensitivity feature, one vCPUs per physical core can be assigned to applications. This requires the Cisco Meeting Server Core / Combined VM's Latency Sensitivity to be set to 'High' with one or more other VMs set to 'Normal'. So a two socket system which has 20 physical cores will have 20 vCPU available for the co-resident applications. If no other VMs can be set to 'Normal' then one physical core must be left unused. When using VMware release 5.1, or VMware 5.5+ without Latency Sensitivity, one physical core per physical server must be left unused by apps for ESXi scheduler. So a two socket system which has 20 physical cores will have 19 vCPU available for the co-resident applications. Use Quote Collab for assistance.

Over subscription of the host, either by incorrectly setting the number of Cisco Meeting Server VM virtual CPUs or by contention for CPU resources amongst VMs, causes scheduling delays and results in degraded media quality. A Cisco Meeting Server VM, correctly configured according to the recommendations above, will degrade gracefully by dropping frame rate and/or resolution if pushed over capacity.

Edge VM:

Version 3.1:Two Edge VMs are supported:

Small Edge: 4vCPU, 4GB RAM and 1GB NIC
Large Edge: 16vCPU, 8GB RAM and 10GB NIC

Call capacities for server specifications

Types of calls	1 x 4vCPU VM call capacity	1 x 16vCPU VM call capacity
Full HD calls 1080p30 video	100	350
HD calls 720p30 video	175	700
SD calls 448p30 video	250	1000
Audio calls (G.711)	850	3000

We recommend:

1 vCPU to 1 physical CPU.
The edge server can be co-resident with other VMs. However, each 4 vCPU VM has a 1 Gbps NIC requirement and each 16 vCPU has a 10Gbps NIC requirement. The VM host will need sufficient NIC capacity for all applications.
All edge servers are the same capacity, i.e. all 4 vCPUs or all 16 vCPUs, not a mix of both.
Callbridge to edge VM ratios can be any of the following: many:1, 1:1, or 1:many
Callbridge groups are configured. This allows you to assign a unique group of TURN servers to each Callbridge group which is useful for:
- helping with load balancing
- keeping TURN servers sensibly geolocated with Callbridges
- Scaling edge servers - in order for webRTC to match SIP scale we support multiple edges (up to 24 per cluster) however only up to 10 per group, deployments needing more than 10 would need to use Callbridge groups (with each callbridge group supporting up to 10 edges).

Version 3.0 and earlier: Edge VMs that connect to a single Meeting Server Callbridge use 4 vCPUs and 4 GB vRAM. In other cases use 8vCPU and 8 GB vRAM.

Recording VM:
Internal SIP recorder performance and resource usage

Recording Setting Recording per vCPU RAM required per recording Disk budget per hour Maximum concurrent recording

720p 2 0.5GB 1GB 40

1080p 1 1GB 2GB 20

audio 16 100MB 150MB 100

Performance scales linearly adding vCPUs up to the number of host physical cores.

Can scale-out up to 8 Recorder VMs. If seeking >8, review by Cisco video team required (see your Cisco account team for process).

See www.cisco.com/go/meetingserver for all other details.

Streaming VM:
Internal SIP streamer recommended specifications

Number of vCPUs RAM Number of 720p streams Number of 1080p streams Number of audio-only streams

4 4GB 50 37 100

4 8GB 100 75 200

8 8GB 200 150 200

Number of vCPUs should not oversubscribe the number of physical cores.

Maximum number of 720p streams supported is 200 regardless of adding more vCPUs

Maximum number of 1080p streams supported is 150 regardless of adding more vCPUs.

Maximum number of audio-only streams supported is 200 regardless of adding more vCPUs.

Can scale-out up to 6 Streaming VMs. If seeking >6, review by Cisco video team required (see your Cisco account team for process).

See www.cisco.com/go/meetingserver for all other details.

IOPS and Storage System Performance Requirements

(top)

Coming soon.