Cisco Cisco TelePresence Video Communication Server Expressway
Cisco Multiway with TelePresence Conductor
Cisco TelePresence Multiway Deployment Guide (Cisco VCS X7.2 and Conductor XC2.2)
Page 6 of 41
Cisco Multiway with TelePresence Conductor
The advantages of using TelePresence Conductor and
Multiway
Multiway
Multiway with TelePresence Conductor adds several improvements over Multiway without TelePresence
Conductor, namely:
Conductor, namely:
n
Each user can be provisioned with their own personal Multiway (rendezvous) alias. The advantages of this
are threefold:
are threefold:
l
This allows users to either dial directly into the conference or be joined to the conference by dialing other
members of the conference. This limits one conference alias to a conference with a specific individual.
members of the conference. This limits one conference alias to a conference with a specific individual.
l
Administrators can provision different levels of service to different users.
l
Each user can have a personalized Multiway conference, with unique viewtypes, PINs and conference
settings.
settings.
n
Greater scalability and reliability of the video network.
l
Better handling of mixed SIP and H.323 conferences.
l
Added resiliency against conference bridge failure. If a conference bridge or the network connection to it
fails, TelePresence Conductor will recognize this and mark them as unusable. This allows users to
redial and arrive at a separate conference bridge.
fails, TelePresence Conductor will recognize this and mark them as unusable. This allows users to
redial and arrive at a separate conference bridge.
n
Support for TelePresence Server, which is not available in a deployment without the TelePresence
Conductor.
Conductor.
n
TelePresence Conductor manages conference bridges and distributes load across pools of conference
bridges this allows:
bridges this allows:
l
Improved load balancing across multiple conference bridges, especially for SIP (the VCS supports basic
load balancing for registered H.323 MCUs, but the VCS alone does not support SIP load balancing).
load balancing for registered H.323 MCUs, but the VCS alone does not support SIP load balancing).
l
Conference bridges can be disabled from the TelePresence Conductor's pool of conference bridges
allowing them to be taken offline for upgrades or network without a loss in service.
allowing them to be taken offline for upgrades or network without a loss in service.
n
If a conference exceeds the capability of a single MCU the conference can be cascaded to a second MCU.
This is currently not supported on a TelePresence Server.
This is currently not supported on a TelePresence Server.
n
Greater administrative control over the conferencing resources used: allowing the administrator to decide
on a per user basis:
on a per user basis:
l
The maximum number of participants allowed in a conference.
l
If content is allowed.
l
If a conference can cascade across multiple MCUs.
l
Preferentially refer users to conference bridges local to their geographic region.
l
Allow some users HD services and some users SD services.
TelePresence Conductor is highly configurable, for more details of the benefits of TelePresence Conductor,
see
see
and the relevant deployment guide.
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
(MultiSite), Jabber Video and EX90 users and those endpoints without the built-in conference feature
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
(MultiSite), Jabber Video and EX90 users and those endpoints without the built-in conference feature