Cisco Cisco TelePresence MCU 4510 Document
Deploying an MCU registered to Cisco TelePresence VCS
Cisco TelePresence MCU Deployment Guide
Page 15 of 32
Deploying an MCU registered to Cisco
TelePresence VCS
TelePresence VCS
Deployment overview
This deployment uses VCS as the registration mechanism for the MCU and conferences are
scheduled using TMS: separate MCUs are used for scheduling and ad hoc conferencing. Endpoints
registered to VCS (or a Unified CM trunked to the VCS) can join MCU calls. All MCUs are provided
with a unique prefix in order to route calls correctly and avoid the possibility of identical conference
numbers for scheduled or ad hoc conferences. This deployment covers:
scheduled using TMS: separate MCUs are used for scheduling and ad hoc conferencing. Endpoints
registered to VCS (or a Unified CM trunked to the VCS) can join MCU calls. All MCUs are provided
with a unique prefix in order to route calls correctly and avoid the possibility of identical conference
numbers for scheduled or ad hoc conferences. This deployment covers:
Table 7: Overview of covered functionality
Functionality
Description
Management
MCU is manageable from TMS. The management access to the MCU is
restricted to the administrator.
restricted to the administrator.
Ad hoc conferencing
A conference can be:
Created on the fly by dialing a service prefix and a conference
numeric identifier.
numeric identifier.
Statically configured on an MCU
Created and joined via the auto attendant
Created and joined using the Multiway mechanism
Pre-defined permanent
conferences
conferences
The administrator can create permanent conferences.
Secure conferencing
Encrypted media and signaling using AES, SRTP and TLS
encrypted calls.
encrypted calls.
Restricted access to call into conference; the caller has to enter
a PIN to connect to the conference.
a PIN to connect to the conference.
Prerequisites
Before carrying out the configuration of Cisco VCS, Cisco MCU and Cisco TMS ensure that the
following prerequisites are met:
following prerequisites are met:
At least one Cisco TelePresence VCS running X7.0 software.
At least one MCU using 4.2 software for scheduled conferences.
Additional MCU for ad hoc conferences.
Cisco TMS running 13.1.2 software.
Cisco VCS and TMS are installed and configured for base operation using the relevant
deployment guide (listed below).
deployment guide (listed below).
MCUs used start with the base settings covered in Table 2 above.
Cisco TMS has enough system licenses to add the relevant number of MCUs.
Document List