Frequently Asked Questions
The table below shows the expansion in maximum call capacities on Meeting Servers by upgrading to later software versions. Bold indicates a new feature in that software version. Note that there are different capacities for a single or cluster of Meeting Servers compared to load balancing calls within a Call Bridge Group.
| Software version | 2.0 | 2.1 | 2.2 | 2.3 | 2.4 and 2.5 | 2.6 and 2.7 | 2.8 and later | |||||||||
| Cisco Meeting Server Platform | 1000 | 2000 | 1000 | 2000 | 1000 | 2000 | 1000 | 2000 | 1000 | 2000 | 1000 | 2000 | 1000 M4 | 1000 M5 | 2000 | |
| Individual Meeting Servers or Meeting Servers in a cluster (notes 1,2 3 and 4) | Full HD calls (1080p30) |
48
|
NA | 48 | NA | 48 | 250 | 48 | 250 | 48 | 350 | 48 | 350 | 48 | 48 | 350 |
| HD calls (720p30) |
96 |
NA | 96 | NA | 96 | 500 | 96 | 500 | 96 | 700 | 96 | 700 | 96 | 96 | 700 | |
| SD calls (448p30) | 192 | NA | 192 | NA | 192 | 1000 | 192 | 1000 | 192 | 1000 | 192 | 1000 | 192 | 192 | 1000 | |
| Audio | 3000 | NA | 3000 | NA | 3000 | 3000 | 3000 | 3000 | 3000 | 3000 | 3000 | 3000 | 1700 (note 6) | 2200 (note 6) | 3000 | |
| HD participants per conference per server | 96 | NA | 96 | NA | 96 | 100 | 96 | 100 | 96 | 450 | 96 | 450 | 96 | 96 | 450 | |
| WebRTC connections per Web Bridge | 100 | NA | 100 | NA | 100 | 100 | 100 | 100 | 100 | 100 | 100 | 100 | 100 | 100 | 100 | |
| Meeting Servers in a Call Bridge Group | Call type supported | NA | NA | Inbound SIP | NA | Inbound SIP Outbound SIP |
Inbound SIP Outbound SIP Cisco Meeting App |
Inbound SIP Outbound SIP Cisco Meeting App |
Inbound SIP Outbound SIP Cisco Meeting App |
Inbound SIP Outbound SIP Cisco Meeting App |
||||||
| Full HD calls (1080p30) | NA | NA | 48 | NA | 48 | 250 | 48 | 250 | 48 | 250 | 48 | 250 | 48 | 48 | 250 | |
| HD calls (720p30) | NA | NA | 96 | NA | 96 | 500 | 96 | 500 | 96 | 500 | 96 | 700 | 96 | 96 | 700 | |
| SD calls (448p30) | NA | NA | 192 | NA | 192 | 1000 | 192 | 1000 | 192 | 1000 | 192 | 1000 | 192 | 192 | 1000 | |
| Audio | NA | NA | 3000 | NA | 3000 | 3000 | 3000 | 3000 | 3000 | 3000 | 3000 | 3000 | 1700 (note 6) | 2200 (note 6) | 3000 | |
| Load limit | NA | NA | 96,000 | NA | 96,000 | 500,000 | 96,000 | 500,000 | 96,000 | 500,000 (note 5) | 96,000 | 700,000 (note 5) | 96,000 | 96,000 | 700,000 (note 5) | |
| Number of HD participants per conference per server | NA | NA | 96 | NA | 96 | 100 | 96 | 100 | 96 | 450 | 96 | 450 | 96 | 96 | 450 | |
| WebRTC connections per Web Bridge | NA | NA | 100 | NA | 100 | 100 | 100 | 100 | 100 | 100 | 100 | 100 | 100 | 100 | 100 | |
Note 1: Maximum of 24 Call Bridge nodes per cluster; cluster designs of 8 or more nodes need to be approved by Cisco, contact Cisco Support for more information.
Note 2: Clustered Cisco Meeting Server 2000s without Call Bridge Groups configured, support integer multiples of maximum calls, for example integer multiples of 700 HD calls.
Note 3: Up to 16,800 HD concurrent calls per cluster (24 nodes x 700 HD calls).
Note 4: A maximum of 2600 participants per conference per cluster depending on the s platforms within the cluster.
Note 5: From version 2.6 the call capacity for Meeting Server 2000 with Call Bridge Groups enabled, has increased to 700 HD calls, and the loadlimit has increased from 500000 to 700000. the load calculation for the different call resolutions has been updated to match the new 700000 limit. Load limits for other Meeting Server platforms stay as they were previously; these changes only apply to the Cisco Meeting Server 2000.
Note 6: VMware have made changes in their recent versions (ESXi 6.0 update 3, 6.5 update 2 and 6.7) that have reduced the throughput of audio calls on Cisco Meeting Server in version 2.8 and later (video capacity is unaffected).
- Last update:
- 28-Apr-2020
- FAQ ID:
- 1467