Cisco Cisco TelePresence MCU 4510 Installation Guide

Page of 52
Conference
type
Options
Non-scheduled
n
Rendezvous – using static meeting numbers
Scheduled
n
Using Cisco TMS either directly or via an integration, for instance with Microsoft
Exchange.
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.
Known limitations
n
Cascading is not supported
n
Configuring the MCU as a Unified CM media resource and the MCU as a trunk for Rendezvous
conferencing at the same time without the use of another device such as TelePresence Conductor is not
supported.
Summary of deployment types
MCU deployed on
Cisco VCS
MCU deployed on
Cisco VCS with
TelePresence
Conductor
MCU deployed
as a media
resource on
Unified CM
MCU deployed with
TelePresence
Conductor on
Unified CM
MCU
trunked to
Unified CM
Assumed
Equipment
& Versions
MCU 4.5
Unified CM 10.0
Cisco VCS X8.5
Cisco TMS 14.5
MCU 4.5
TelePresence
Conductor XC2.x
Cisco VCS 8.5
Cisco TMS 14.5
MCU 4.5
Unified CM
10.0
Cisco TMS
14.5
MCU 4.5
Unified CM 10.0
TelePresence
Conductor XC3.0
Cisco TMS 14.5
MCU 4.5
Unified CM
10.0
Cisco TMS
14.5
Non-
scheduled
call
methods
supported
Auto Attendant
Rendezvous
Multiway
Rendezvous
Multiway
Conference
button
Unified CM
Rendezvous
Rendezvous,
Multiway*,
Conference button,
Unified CM
Rendezvous
Auto
Attendant,
Rendezvous
Scheduled
calls
Supported via TMS
Supported via
TMS
Supported via
TMS
Supported via TMS
Supported
via TMS
Scalability
Basic scalability
High scalability
High
scalability
High Scalability
High
Scalability
Resiliency
Basic resiliency
High resiliency
High resiliency
High resiliency
High
resiliency
Table 7: Choosing a deployment type
Cisco TelePresence MCU Deployment Guide 4.5
Page 16 of 52
Which deployment?