Cisco Cisco TelePresence Video Communication Server Expressway
Introduction
Cisco VCS Deployment Guide: Multiway™ (Cisco VCS X7)
Page 5 of 30
Deployment scenario
A company is currently using video for point-to-point calling but wants to support 3-way video calls and
larger video conferences initiated by callers already in point-to-point calls. Although some of their
larger video conference systems support this through conference bridges built into the video endpoints
themselves, Movi and E20 users and those endpoints without the built-in conference feature licensed
cannot.
larger video conferences initiated by callers already in point-to-point calls. Although some of their
larger video conference systems support this through conference bridges built into the video endpoints
themselves, Movi and E20 users and those endpoints without the built-in conference feature licensed
cannot.
To implement Multiway:
the VCS Control or VCS Expressway needs to be running X5 or later software
a conference bridge needs to be available (MCU running software 3.1 or later)
Multiway makes use of video conferencing more intuitive and seamless, allowing multiple parties to be
added to a call during the call as and when required, rather than requiring individual parties to call into
a pre-setup video conference.
added to a call during the call as and when required, rather than requiring individual parties to call into
a pre-setup video conference.
This deployment guide describes how to configure the Cisco VCS and the MCU.
In this scenario, the MCU will be set up to receive calls with a prefix 555.
It is assumed that the Cisco VCS Control is running X5 code (or later) and has at least the following
option keys applied:
option keys applied:
H323-SIP interworking
Non-traversal calls
Traversal calls (if interworking is to be used)
Summary of configuration process
To make Multiway operational, configuration will be carried out on:
Cisco VCS
MCU
endpoints that need the ability to initiate a Multiway call