Cisco Cisco TelePresence MCU 4510 Installation Guide
Conference type
Options
Non-scheduled
n
Rendezvous – using static meeting numbers
Table 6: Unified CM Rendezvous deployment capability overview
Scalability and resiliency
Unified CM provides excellent resiliency if using a prefix method where conferences are not configured on a
specific MCU. Setting static meeting numbers up on MCUs limits resiliency. Many MCUs can be added to
Unified CM in order to provide a large pool of available ports.
specific MCU. Setting static meeting numbers up on MCUs limits resiliency. Many MCUs can be added to
Unified CM in order to provide a large pool of available ports.
Known limitations
n
Scheduled conferencing is not supported
n
Cascading is not supported
Combined solution
Although each type of MCU deployment is discussed separately, it is possible to combine deployments in
order to provide all types of service. The figure below shows an example of a combined non-scheduled and
scheduled deployment.
order to provide all types of service. The figure below shows an example of a combined non-scheduled and
scheduled deployment.
Figure 6: MCU pools in a combined solution
This solution is viable provided each type of MCU pool has separate MCU resources to use.
Although endpoints registered to Unified CM do not support escalating a call to Multiway, they can be
escalated by an endpoint that supports the mechanism on Cisco VCS.
escalated by an endpoint that supports the mechanism on Cisco VCS.
Cisco TelePresence MCU Deployment Guide 4.4
Page 16 of 53
Which deployment?