Cisco Cisco TelePresence MCU 4510 Installation Guide
Deploying an MCU registered to Cisco VCS
Deployment overview
This deployment uses Cisco VCS as the registration mechanism for the MCU and conferences are
scheduled using Cisco TMS: separate MCUs are used; one for scheduled conferences and one for non-
scheduled conferences. Endpoints registered to Cisco VCS (or a Unified CM trunked to the Cisco 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 Cisco TMS: separate MCUs are used; one for scheduled conferences and one for non-
scheduled conferences. Endpoints registered to Cisco VCS (or a Unified CM trunked to the Cisco 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:
Functionality
Description
Management
MCU is manageable from Cisco TMS. The management access to the MCU is restricted to the
administrator.
administrator.
Non scheduled
conferencing
conferencing
A conference can be:
n
Created on the fly by dialing a service prefix and a conference numeric identifier.
n
Statically configured on an MCU
n
Created and joined via the auto attendant
n
Created and joined using the Multiway mechanism
Scheduled
conferencing
conferencing
A conference created by Cisco TMS and connected to by either dialing the scheduled number,
using One Button to Push or being auto-dialled out from the MCU.
using One Button to Push or being auto-dialled out from the MCU.
Secure
conferencing
conferencing
n
Encrypted media and signaling using AES, SRTP and TLS encrypted calls.
n
Restricted access to call into conference; the caller has to enter a PIN to connect to the
conference.
conference.
Table 8: Overview of covered functionality
Prerequisites
Before carrying out the configuration of Cisco VCS, Cisco MCU and Cisco TMS ensure that the following
prerequisites are met:
prerequisites are met:
n
At least one Cisco VCS running X7.2.2 software.
n
At least one MCU using 4.4 software for scheduled conferences.
n
Additional MCU for non-scheduled conferences.
n
Cisco TMS running 14.1.1 software.
n
Cisco VCS and Cisco TMS are installed and configured for base operation using the relevant deployment
guide (listed below).
guide (listed below).
n
MCUs used start with the base settings covered in
.
n
Cisco TMS has enough system licenses to add the relevant number of MCUs.
Document List
Cisco TelePresence MCU Deployment Guide 4.4
Page 18 of 53
Deploying an MCU registered to Cisco VCS