Cisco Cisco TelePresence MCU 4510 Document
![Cisco](https://files.manualsbrain.com/attachments/7380d0050044647c30f5c24bbbf5d0c0b6d9bb84/common/fit/150/50/faa183d287233c52228cfea3dbc2a127fe780f60564fcb0955d9c3d1cd23/brand_logo.png)
Which deployment?
Cisco TelePresence MCU Deployment Guide
Page 10 of 32
Scalability and resiliency
VCS can support as many MCUs as the total number of VCS registrations and call licenses allow. The
MCU can be configured to register individual conferences but higher scale can be achieved by using
an H.323 service prefix and a SIP trunk so that all calls can be routed to the MCU without each
conference being registered individually. This enables very large deployments of MCUs to be used
directly with VCS. VCS can provide load balancing and resiliency across MCUs registered via H.323
only. For more information see the
MCU can be configured to register individual conferences but higher scale can be achieved by using
an H.323 service prefix and a SIP trunk so that all calls can be routed to the MCU without each
conference being registered individually. This enables very large deployments of MCUs to be used
directly with VCS. VCS can provide load balancing and resiliency across MCUs registered via H.323
only. For more information see the
For scheduled calls, TMS can reschedule conferences onto a different MCU if an MCU becomes
unavailable before or during a scheduled conference.
unavailable before or during a scheduled conference.
Known limitations
MCU load balancing and resiliency (through VCS) is limited to H.323 conferences only and is
basic in nature.
basic in nature.
MCU cascading is a manual process that requires pre-configuration. It is only necessary to
cascade MCUs when a conference with more participants than the maximum on one MCU is
required.
cascade MCUs when a conference with more participants than the maximum on one MCU is
required.
Deploying an MCU with Cisco TelePresence Conductor
In this deployment, MCUs are registered to VCS but conferences are controlled by Conductor and are
ad hoc only: see the figure and table below for details.
ad hoc only: see the figure and table below for details.
Figure 2: VCS deployment with Conductor: media, signaling and scheduling overview
The supported ad hoc methods are described in the table below.