Cisco Unified MeetingPlace, Release 7.0 -- System Capacity Quick Reference Tables

From DocWiki

Main page: Cisco Unified MeetingPlace, Release 7.0

Up one level: Planning Your Deployment

This section provides a series of quick reference tables that describe the different capacity limits for several key configurations of Cisco Unified MeetingPlace Release 7.0 and 8.0.

For more detailed information, see the following:

• Release 7.0: System Capacity

• Release 8.0: Planning the Capacity of your Cisco Unified MeetingPlace System

Contents 1 Release 7.0.3 (MR2) with Cisco Unified MeetingPlace Web Conferencing 1.1 Configuration Details 1.2 Capacity 1.3 Sizes 1.4 Call Rate 1.5 Redundancy 1.6 Recommended Practices 2 Release 7.0.3 (MR2) with Cisco WebEx Web Conferencing 2.1 Configuration Details 2.2 Capacity 2.3 Sizes 2.4 Call Rate 2.5 Redundancy 2.6 Recommended Practices 3 Release 7.0.2 (MR1) with Cisco Unified MeetingPlace Web Conferencing 3.1 Configuration Details 3.2 Capacity 3.3 Sizes 3.4 Call Rate 3.5 Redundancy 3.6 Recommended Practices 4 Release 7.0.2 (MR1) with Cisco WebEx Web Conferencing 4.1 Configuration Details 4.2 Capacity 4.3 Sizes 4.4 Call Rate 4.5 Redundancy 4.6 Recommended Practices 5 Release 7.0.2 (MR1) Using RSNA 5.1 Configuration Details 5.2 Capacity 5.3 Sizes 5.4 Call Rate 5.5 Recommended Practices 6 Release 8.0 Using an Express Media Server 6.1 Configuration Details 6.2 Capacity 6.3 Sizes 6.4 Call Rate 6.5 Redundancy 6.6 Recommended Practices 7 Release 8.0 Using a Hardware Media Server 7.1 Configuration Details 7.2 Capacity 7.3 Sizes 7.4 Call Rate 7.5 Redundancy 7.6 Recommended Practices 8 Release 8.0 Using an Express Media Server from Cisco WebEx 8.1 Configuration Details 8.2 Capacity 8.3 Sizes 8.4 Call Rate 8.5 Redundancy 8.6 Recommended Practices 9 Release 8.0 Using a Hardware Media Server from Cisco WebEx 9.1 Configuration Details 9.2 Capacity 9.3 Sizes 9.4 Call Rate 9.5 Redundancy 9.6 Recommended Practices

Release 7.0.3 (MR2) with Cisco Unified MeetingPlace Web Conferencing

Configuration Details

This configuration assumes the following:

• One Cisco Unified MeetingPlace Application Server using a minimum MCS-7845-I3-RC1 or equivalent.
• Two Windows servers (the system supports a minimum of 2 servers but scales to 6 servers depending on your configuration and features)
• Six Audio blades
• Six Video blades
• Single node configuration using the Hardware Media Server and Cisco Unified MeetingPlace 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 or G.729 (without LEC)1
996	Audio ports using G.729 (with LEC), G.722, or iLBC1
240	Video ports using standard rate video
1000	Web sessions per Application Server when not using SSL or recording
1000	Web sessions per Application Server when using SSL or recording
500	Number of concurrent audio and web meetings per Application Server
3000	Total meetings per day
1000	Continuous meetings
50	Simultaneous meetings that can be recorded
300	Largest possible audio meeting (or 299 when recorded)2
300	Largest possible web meeting when not using SSL or recording3
300	Largest possible web meeting when using SSL or recording3
20	Simultaneous Conference Manager sessions
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: When using a 7835 (I2 or H2) server, the maximum audio ports supports is 500, independent of audio mode.

Footnote 2: We recommend that you schedule larger meetings.

Footnote 3: The Cisco MCS 7845-I3 Web Server supports a maximum of 600 web ports per server. However, the largest supported web meeting per server is subject to the size of the largest supported audio meeting per server. Audio meetings are restricted to 300 ports due to the rate at which a single Audio blade can accept traffic.

Sizes

Maximum Size	Component
250,000	User profiles in the database
400,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 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 Unified MeetingPlace web servers can be clustered for 3 internal and/or 3 external web meetings.

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 7.0.3 (MR2) with Cisco WebEx Web Conferencing

Configuration Details

This configuration assumes the following:

• One Cisco Unified MeetingPlace Application Server using a minimum MCS-7845-I3-RC1 or equivalent.
• One or two Windows web servers
• Six Audio blades
• Six Video blades
• Single node configuration using the Hardware Media Server and Cisco WebEx 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 or G.729 (without LEC)1
996	Audio ports using G.729 (with LEC), G.722, or iLBC1
240	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
300	Largest possible audio meeting (or 299 when recorded)2
500	Largest possible web meeting using Meeting Center meetings
20	Simultaneous Conference Manager sessions

Footnote 1: When using a 7835 (I2 or H2) server, the maximum audio ports supports is 500, independent of audio mode.

Footnote 2: We recommend that you schedule larger meetings.

Sizes

Maximum Size	Component
250,000	User profiles in the database
400,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 and would also require duplicate media hardware if the components are deployed in separate data centers. Single data center supports single shared Media Server. 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 7.0.2 (MR1) with Cisco Unified MeetingPlace Web Conferencing

Configuration Details

This configuration assumes the following:

• One Cisco Unified MeetingPlace Application Server using a minimum MCS-7845-I2-RC1 or equivalent.
• Two Windows servers (the system supports a minimum of 2 servers but scales to 6 servers depending on your configuration and features)
• Six Audio blades
• Six Video blades
• Single node configuration using the Hardware Media Server and Cisco Unified MeetingPlace 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 or G.729 (without LEC)
996	Audio ports using G.729 (with LEC), G.722, or iLBC
240	Video ports using standard rate video
1000	Web sessions per Application Server when not using SSL or recording
700	Web sessions per Application Server when using SSL or recording
500	Number of concurrent audio and web meetings per Application Server
50	Simultaneous meetings that can be recorded
300	Largest possible audio meeting (or 299 when recorded)1
300	Largest possible web meeting when not using SSL or recording2
300	Largest possible web meeting when using SSL or recording2
20	Simultaneous Conference Manager sessions
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.

Footnote 2: The Cisco MCS-7845-I2 Web Server supports a maximum of 500 web ports per server when there is no SSL/recording and 350 web ports per server when there is recording enabled. However, the largest supported web meeting per server is subject to the size of the largest supported audio meeting per server. Audio meetings are restricted to 300 ports due to the rate at which a single Audio blade can accept traffic.

Sizes

Maximum Size	Component
250,000	User profiles in the database
400,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 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 Unified MeetingPlace web servers can be clustered for 3 internal and/or 3 external web meetings.

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 7.0.2 (MR1) with Cisco WebEx Web Conferencing

Configuration Details

This configuration assumes the following:

• One Cisco Unified MeetingPlace Application Server using a minimum MCS-7845-I2-RC1 or equivalent.
• One or two Windows web servers
• Six Audio blades
• Six Video blades
• Single node configuration using the Hardware Media Server and Cisco WebEx 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 or G.729 (without LEC)
996	Audio ports using G.729 (with LEC), G.722, or iLBC
240	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
300	Largest possible audio meeting (or 299 when recorded)1
500	Largest possible web meeting using Meeting Center meetings1

Footnote 1: For larger meetings we recommend that you use Cisco WebEx Event Center.

Sizes

Maximum Size	Component
250,000	User profiles in the database
400,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 and would also require duplicate media hardware if the components are deployed in separate data centers. Single data center supports single shared Media Server. 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 7.0.2 (MR1) Using RSNA

Configuration Details

This configuration assumes the following:

• Two Cisco Unified MeetingPlace Application Server using a minimum MCS-7845-I2-RC1 or equivalent.
• 12 Audio blades
• 12 Video blades
• Two nodes using the Hardware Media Server
• Supports audio/video-only reservationless meetings
• There is no web conferencing and no scheduling interface

Capacity

Maximum Number	Details
2x1500	Audio ports using G.711 or G.729 (without LEC)
2x996	Audio ports using G.729 (with LEC), G.722, or iLBC
2x240	Video ports using standard rate video
1000	Simultaneous audio meetings
300	Largest possible audio meeting1

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
400,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
30 CPS	Maximum call rate for inbound calls

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

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
1300	Audio ports using G.711
260	Audio ports using G.729 or G.722
650	Combined audio/video ports using G.711 and 384Kpbs
108	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
1300	Audio ports using G.711
650	Combined audio/video ports using G.711 and 384Kpbs
108	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 recorded1
500	Largest possible web meeting using Meeting Center meetings1
3500	Largest possible meeting using Event Center as follows: Up to 500 users with speaking privileges on the Cisco Unified MeetingPlace audio bridge Up to 3000 users with listening-only privileges on the audio broadcast

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 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 recorded1
500	Largest possible web meeting using Meeting Center meetings1
3500	Largest possible meeting using Event Center as follows: Up to 500 users with speaking privileges on the Cisco Unified MeetingPlace audio bridge Up to 3000 users with listening-only privileges on the audio broadcast

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.

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.