Sizes

Call Rate

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.

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 14 Audio/Video Conferencing Nodes in a regional deployment is supported. A maximum of 2 Meeting Director servers are required. Meeting Director can be combined with Audio/VIdeo Conferencing Nodes if there is 4 or fewer nodes deployed system wide on 2 of the Audio/Video Conferencing Nodes. The multinode deployment model supports active/active resiliency per site and per region in multiple sites so that if a particular audio/video conferencing server goes down, users dial back or use call back feature in Webex to re-join same meeting, that meeting is then re-established on an available Audio/Video Conferencing Node. This is done automically when using the Webex Schedulign model and 2 or more Audio/Video Conferencing Nodes.

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.

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

A maximum of 14 Audio/Video Conferencing Nodes in a regional deployment is supported. A maximum of 2 Meeting Director servers are required. Meeting Director can be combined with Audio/VIdeo Conferencing Nodes if there is 4 or fewer nodes deployed system wide on 2 of the Audio/Video Conferencing Nodes. The multinode deployment model supports active/active resiliency per site and per region in multiple sites so that if a particular audio/video conferencing server goes down, users dial back or use call back feature in Webex to re-join same meeting, that meeting is then re-established on an available Audio/Video Conferencing Node. This is done automically when using the Webex Schedulign model and 2 or more Audio/Video Conferencing Nodes.

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.