Cisco Unified MeetingPlace Release 8.5 -- System Capacity Quick Reference Tables

From DocWiki

Jump to: navigation, search

Main page: Cisco Unified MeetingPlace Release 8.5

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


Contents

Release 8.5 Using an Express Media Server for an Audio Only or MeetingPlace Scheduling Deployment

Configuration Details

This configuration is for an audio only or MeetingPlace Scheduling deployment and assumes the following:

  • One Cisco Unified MeetingPlace Application Server using a minimum MCS-7845-I3-RC2 or equivalent.
  • Two Web servers (one web server for Audio only)
  • Single node configuration using the Express Media Server
  • Supports both Cisco Unified MeetingPlace-scheduled meetings and reservationless meetings
  • Does not support Cisco WebEx-scheduled meetings

Capacity

Maximum Number Details

1200

Audio ports using G.711 (HC audio mode)

200

Audio ports using G.729 or G.722 (HQ audio mode)

600

Combined audio/video ports using G.711 and 384Kpbs (HC audio mode)

100

Combined audio/video ports using G.722 and 2Mbps (HQ audio mode)

50

Simultaneous meetings that can be recorded

60

Simultaneous Conference Manager sessions. A maximum of 20 sessions can be actively involved with scheduling, rescheduling, and canceling meeting operations. The rest are only involved with monitoring or in-session activities.

1000

Largest possible audio meeting (or 999 when recorded)1

249

Largest possible meeting with secure conferencing

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: Meeting recording requires resources equivalent to one meeting attendee.

Sizes

Maximum Size Component

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

12 CPS

Maximum call rate for inbound calls

Redundancy

Warm Standby Application Server is supported. This requires duplicate MCS/UCS hardware for the Application 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 8.5 Using a Hardware Media Server for an Audio Only or MeetingPlace Scheduling Deployment

Configuration Details

This configuration is for an audio only or MeetingPlace Scheduling deployment and assumes the following:

  • One Cisco Unified MeetingPlace Application Server using a minimum MCS-7845-I3-RC2 or equivalent.
  • Two Web servers (one Web server for Audio only)
  • Eight Audio blades
  • Eight Video blades
  • Single node configuration using the Hardware Media Server
  • 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

50

Simultaneous meetings that can be recorded

60

Simultaneous Conference Manager sessions. A maximum of 20 sessions can be actively involved with scheduling, rescheduling, and canceling meeting operations. The rest are only involved with monitoring or in-session activities.

1000

Largest possible audio meeting (or 999 when recorded)1

249

Largest possible meeting with secure conferencing

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: Meeting recording requires resources equivalent to one meeting attendee.

Sizes

Maximum Size Component

400,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. 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.5 Using an Express Media Server and Cisco WebEx Scheduling Deployment

Configuration Details

This configuration is for web conferencing with Cisco WebEx scheduling and assumes the following:

  • One Cisco Unified MeetingPlace Application Server using a minimum MCS-7845-I3-RC2 or equivalent.
  • Four Cisco WebEx Node for MCS servers maximum, unlimited Webex Node for ASR 1000
  • Uses Cisco WebEx front-end interfaces for web conferencing and Cisco WebEx productivity tools
  • Multinode capacity provides for 12 Conference Nodes plus 2 Conference Nodes for resiliency and 2 Meeting Director Nodes which support maximum of 14,400 G.711 ports
  • Webex SaaS capacity is 14,400 web session on Webex Node and in Collaboration Cloud

Capacity

Maximum Number Details

1200

Audio ports using G.711 (HC audio mode)

600

Combined audio/video ports using G.711 and 384Kpbs (HC audio mode)

100

Combined audio/video ports using G.722 and 2Mbps (HQ audio mode)

1000

Web sessions per Application Server

500

Number of concurrent audio and web meetings per Application Server

50

Simultaneous meetings that can be recorded

60

Conference Manager sessions involved with monitoring or in-session activities only

1000

Largest possible audio meeting (or 999 when recorded)1

1000

Largest possible web meeting using Meeting Center meetings. 500 with web and audio/video using Meeting Center meetings.2

249

Largest possible meeting with secure conferencing

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: Meeting recording requires resources equivalent to one meeting attendee.

Footnote 2: For larger meetings, we recommend that you use Event Center. Note that Event Center is not supported on Apple Mac systems.

Sizes

Maximum Size Component

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

12 CPS

Maximum call rate for inbound calls

Redundancy

A maximum of two Meeting Director(s) are supported for primary/standby configuration. Network latency between Meeting Directors affects failover timing. Audio/Video Conferencing nodes in multinode configuration support 14 nodes maximum, in 4 Regions, using load-sharing within regions. Cisco WebEx Node for MCS optional redundancy is supported with the four 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.5 Using a Hardware Media Server and Cisco WebEx Scheduling Deployment

Configuration Details

This configuration is for web conferencing with Cisco WebEx scheduling and assumes the following:

  • One Cisco Unified MeetingPlace Application Server using a minimum MCS-7845-I3-RC2 or equivalent.
  • Eight Audio blades per Conference Node
  • Eight Video blades per Conference Node
  • Four Cisco WebEx Node For MCS or unlimited Webex Node for ASR
  • Single node configuration using the Hardware Media Server capacities below
  • Uses Cisco WebEx front-end interfaces for web conferencing and Cisco WebEx productivity tools
  • Multinode capacity provides for 12 Conference Nodes plus 2 Conference Nodes for resiliency and 2 Meeting Director Nodes which support maximum of 14,400 G.711 ports
  • Webex SaaS capacity is 14,400 web session on Webex Node and in Collaboration Cloud

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

60

Conference Manager sessions involved with monitoring or in-session activities only

1000

Largest possible audio meeting (or 999 when recorded)1

1000

Largest possible web meeting using Meeting Center meetings. 500 with web and audio/video using Meeting Center meetings.2

249

Largest possible meeting with secure conferencing

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: Meeting recording requires resources equivalent to one meeting attendee.

Footnote 2: For larger meetings, we recommend that you use Event Center. Note that Event Center is not supported on Apple Mac systems.

Sizes

Maximum Size Component

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

Rating: 4.4/5 (5 votes cast)

Personal tools