Cisco Unified MeetingPlace Release 8.0 -- System Capacity Quick Reference Tables
From DocWiki
Main page: Cisco Unified MeetingPlace, Release 8.0
Navigation: Planning Your Deployment > Planning the Capacity of your Cisco Unified MeetingPlace System
This section provides a series of quick reference tables that describe the different capacity limits for several key configurations of Cisco Unified MeetingPlace Release 8.0.
Contents |
Release 8.0 Using an Express Media Server
Configuration Details
This configuration assumes the following:
- One Cisco Unified MeetingPlace Application Server using a minimum MCS-7845-I3-RC2 or equivalent.
- Two Web servers
- Three Cisco WebEx Node for MCS
- Single node configuration using the Express Media Server and Cisco WebEx Node for MCS web conferencing
- Supports both Cisco Unified MeetingPlace-scheduled meetings and reservationless meetings
- Does not support Cisco WebEx-scheduled meetings
Capacity
| Maximum Number | Details |
|---|---|
|
1500 |
Audio ports using G.711 |
|
300 |
Audio ports using G.729 or G.722 |
|
750 |
Combined audio/video ports using G.711 and 384Kpbs |
|
125 |
Combined audio/video ports using G.722 and 2Mbps |
|
1000 |
Web sessions per Application Server |
|
500 |
Maximum number of concurrent audio and web meetings per Application Server |
|
50 |
Simultaneous meetings that can be recorded |
|
1000 |
Largest possible audio meeting (or 999 when recorded)1 |
|
500 |
Largest possible web meeting using Meeting Center meetings1 |
|
1 |
Database replication connection per Windows cluster (internal and external). Customers desiring redundancy for the SQL database must set up a database cluster sharing that one replication connection. |
Footnote 1: We recommend that you schedule large meetings in order to obtain the maximum supported capacity.
Sizes
| Maximum Size | Component |
|---|---|
|
250,000 |
User profiles in the database |
|
700,000 |
Meetings in the database |
Call Rate
| Maximum | Details |
|---|---|
|
180 seconds |
Time to get all ports into meetings (includes the time to disconnect from previous meetings) |
|
20 seconds |
Time to get the meetings started |
|
15 CPS |
Maximum call rate for inbound calls |
Redundancy
Warm Standby Application Server is supported. This requires duplicate MCS hardware for the Application Server. Cisco Webex Node redundancy is supported with the 3 MCS server configuration. No redundant Cisco Unified MeetingPlace web servers are supported with the Cisco Webex integration.
Recommended Practices
- Scheduling and rescheduling of recurring meetings with more than 10 instances should be performed during off-peak times to minimize delays perceived by users joining meetings.
- Administrative reports should be run during off-peak times to minimize delays perceived by users joining meetings.
Release 8.0 Using a Hardware Media Server
Configuration Details
This configuration assumes the following:
- One Cisco Unified MeetingPlace Application Server using a minimum MCS-7845-I3-RC2 or equivalent.
- Two Web servers
- Eight Audio blades
- Eight Video blades
- Three Cisco WebEx Node for MCS
- Single node configuration using the Hardware Media Server and Cisco WebEx Node for MCS web conferencing
- Supports both Cisco Unified MeetingPlace-scheduled meetings and reservationless meetings
- Does not support Cisco WebEx-scheduled meetings
Capacity
| Maximum Number | Details |
|---|---|
|
2000 |
Audio ports using G.711 or G.729 (without LEC) |
|
1328 |
Audio ports using G.729 (with LEC), G.722, or iLBC |
|
300 |
Video ports using standard rate video |
|
1000 |
Web sessions per Application Server |
|
500 |
Number of concurrent audio and web meetings per Application Server |
|
50 |
Simultaneous meetings that can be recorded |
|
1000 |
Largest possible audio meeting (or 999 when recorded1 |
|
500 |
Largest possible web meeting using Meeting Center meetings1 |
|
1 |
Database replication connection per Windows cluster (internal and external). Customers desiring redundancy for the SQL database must set up a database cluster sharing that one replication connection.
|
Footnote 1: We recommend that you schedule large meetings in order to obtain the maximum supported capacity.
Sizes
| Maximum Size | Component |
|---|---|
|
250,000 |
User profiles in the database |
|
700,000 |
Meetings in the database |
Call Rate
| Maximum | Details |
|---|---|
|
180 seconds |
Time to get all ports into meetings (includes the time to disconnect from previous meetings) |
|
20 seconds |
Time to get the meetings started |
|
20 CPS |
Maximum call rate for inbound calls |
Redundancy
Warm Standby Application Server is supported. This requires duplicate MCS hardware for the Application Server and would also require duplicate media hardware if the components are deployed in separate data centers. Single data center supports single shared Media Server. Cisco Webex Node redundancy is supported with the 3 MCS server configuration. No redundant Cisco Unified MeetingPlace web servers are supported with the Cisco Webex integration.
Recommended Practices
- Scheduling and rescheduling of recurring meetings with more than 10 instances should be performed during off-peak times to minimize delays perceived by users joining meetings.
- Administrative reports should be run during off-peak times to minimize delays perceived by users joining meetings.
Release 8.0 Using an Express Media Server from Cisco WebEx
Configuration Details
This configuration assumes the following:
- One Cisco Unified MeetingPlace Application Server using a minimum MCS-7845-I3-RC2 or equivalent.
- Three Cisco WebEx Node for MCS
- Single node configuration using the Express Media Server and Cisco WebEx web conferencing
- Uses Cisco WebEx front-end interfaces for web conferencing and Cisco WebEx productivity tools
Capacity
| Maximum Number | Details |
|---|---|
|
1500 |
Audio ports using G.711 |
|
750 |
Combined audio/video ports using G.711 and 384Kpbs |
|
125 |
Combined audio/video ports using G.722 and 2Mbps |
|
1000 |
Web sessions per Application Server |
|
500 |
Number of concurrent audio and web meetings per Application Server |
|
50 |
Simultaneous meetings that can be recorded |
|
1000 |
Largest possible audio meeting (or 999 when recorded)1 |
|
500 |
Largest possible web meeting using Meeting Center meetings1 |
|
3500 |
Largest possible meeting using Event Center as follows:
|
Footnote 1: For larger meetings, we recommend that you use Event Center.
Sizes
| Maximum Size | Component |
|---|---|
|
250,000 |
User profiles in the database |
|
700,000 |
Meetings in the database |
Call Rate
| Maximum | Details |
|---|---|
|
180 seconds |
Time to get all ports into meetings (includes the time to disconnect from previous meetings) |
|
20 seconds |
Time to get the meetings started |
|
15 CPS |
Maximum call rate for inbound calls |
Redundancy
Warm Standby Application Server is supported. This requires duplicate hardware for the Application Server. Cisco Webex Node redundancy is supported with the 3 MCS server configuration.
Recommended Practices
- Scheduling and rescheduling of recurring meetings with more than 10 instances should be performed during off-peak times to minimize delays perceived by users joining meetings.
- Administrative reports should be run during off-peak times to minimize delays perceived by users joining meetings.
Release 8.0 Using a Hardware Media Server from Cisco WebEx
Configuration Details
This configuration assumes the following:
- One Cisco Unified MeetingPlace Application Server using a minimum MCS-7845-I3-RC2 or equivalent.
- Eight Audio blades
- Eight Video blades
- Three Cisco WebEx Node for MCS
- Single node configuration using the Hardware Media Server and Cisco WebEx Node for MCS web conferencing
- Uses Cisco WebEx front-end interfaces for web conferencing and Cisco WebEx productivity tools
Capacity
| Maximum Number | Details |
|---|---|
|
2000 |
Audio ports using G.711 or G.729 (without LEC) |
|
1328 |
Audio ports using G.729 (with LEC), G.722, or iLBC |
|
300 |
Video ports using standard rate video |
|
1000 |
Web sessions per Application Server |
|
500 |
Number of concurrent audio and web meetings per Application Server |
|
50 |
Simultaneous meetings that can be recorded |
|
1000 |
Largest possible audio meeting (or 999 when recorded)1 |
|
500 |
Largest possible web meeting using Meeting Center meetings1 |
|
3500 |
Largest possible meeting using Event Center as follows:
|
Footnote 1: For larger meetings, we recommend that you use Event Center.
Sizes
| Maximum Size | Component |
|---|---|
|
250,000 |
User profiles in the database |
|
700,000 |
Meetings in the database |
Call Rate
| Maximum | Details |
|---|---|
|
180 seconds |
Time to get all ports into meetings (includes the time to disconnect from previous meetings) |
|
20 seconds |
Time to get the meetings started |
|
20 CPS |
Maximum call rate for inbound calls |
Redundancy
Warm Standby Application Server is supported. This requires duplicate MCS hardware for the Application Server and would also require duplicate media hardware if the components are deployed in separate data centers. Single data center supports single shared Media Server. Cisco Webex Node redundancy is supported with the 3 MCS server configuration.
Recommended Practices
- Scheduling and rescheduling of recurring meetings with more than 10 instances should be performed during off-peak times to minimize delays perceived by users joining meetings.
- Administrative reports should be run during off-peak times to minimize delays perceived by users joining meetings.