Cisco Cisco TelePresence Management Suite (TMS) Version 15
Bridge behavior
Area of interest
Description
Image quality
Multipoint Switch does not transcode (encode/decode). This leaves the video stream
untouched with low latency.
untouched with low latency.
TelePresence Server always transcodes video, which:
n
is a requirement for offering broad interoperability
n
offers added benefits such as active presence
n
creates slight quality degradation and delay compared to switched video
Meeting entry
protection
protection
Cisco TMS scheduling assigns the dial-in number for a conference from a pool of
available URIs and E.164 aliases assigned to the scheduled bridge. Attendees who
manually dial into the conference only use the provided alias.
available URIs and E.164 aliases assigned to the scheduled bridge. Attendees who
manually dial into the conference only use the provided alias.
Users calling in do not need a meeting number, unlike when using the call-in feature of
the Multipoint Switch. This means there is a greater risk of a user joining the wrong
meeting inadvertently. To prevent this:
the Multipoint Switch. This means there is a greater risk of a user joining the wrong
meeting inadvertently. To prevent this:
n
Administrators must make sure to configure bridges with a sufficient number of aliases
in Cisco TMS to minimize reuse of aliases in adjacent conferences. We recommend a
minimum of 1-2 aliases per available bridge port for each bridge.
in Cisco TMS to minimize reuse of aliases in adjacent conferences. We recommend a
minimum of 1-2 aliases per available bridge port for each bridge.
n
Organizers can require a PIN for the conference or lock the conference when all
intended participants are present.
intended participants are present.
Director controls
Multipoint Switch director controls allow explicit control of the layouts that participants see.
With TelePresence Server, this is not available, but you can mark a participant as
Important, which makes them visible in the conference at all times.
With TelePresence Server, this is not available, but you can mark a participant as
Important, which makes them visible in the conference at all times.
Conference Control Center in Cisco TMS provides additional conference controls.
Role-based
privileges
privileges
With Multipoint Switch, users have access to the bridge for conference controls.
The TelePresence Server interface is only for administrator use.
If you set up users with the appropriate roles and permissions, they can access their
scheduled and ongoing conferences in Cisco TMS.
scheduled and ongoing conferences in Cisco TMS.
Maximum
conference size
conference size
Cisco TelePresence Manager 1.9.x supported cascading for up to 11 Multipoint Switches
and 440 segments in scheduled meetings through Network Multipoint.
and 440 segments in scheduled meetings through Network Multipoint.
Cisco TelePresence Server on Cisco MSE 8710 supports up to 48 FullHD (1080p30) or
96 HD (720p30) screens per conference when four blades are clustered. Up to 200 calls
are supported in one cluster of blades with up to 104 in each conference.
96 HD (720p30) screens per conference when four blades are clustered. Up to 200 calls
are supported in one cluster of blades with up to 104 in each conference.
Scheduled versus
ad-hoc resources
ad-hoc resources
With Multipoint Switch, you can assign a certain number of ports for ad hoc use and a
certain number of ports for scheduled conferences. This ensures that scheduled meeting
ports are never consumed by an ad hoc user.
certain number of ports for scheduled conferences. This ensures that scheduled meeting
ports are never consumed by an ad hoc user.
TelePresence Server does not support splitting its capacity in this fashion and does not
stop ad hoc call-in users from using up scheduled ports. This can lead to contention and
failure for scheduled calls if scheduling uses the same TelePresence Server as ad hoc
calls.
stop ad hoc call-in users from using up scheduled ports. This can lead to contention and
failure for scheduled calls if scheduling uses the same TelePresence Server as ad hoc
calls.
Call-in meeting
behavior (Auto
Attendant)
behavior (Auto
Attendant)
When using dial-in with Multipoint Switch, participants must enter the meeting ID.
Calls into a TelePresence Server are routed directly to the conference, and no auto
attendant is required.
attendant is required.
Table 1: Bridge behavior and functionality
Replacing Cisco TelePresence Manager with Cisco TMS and Cisco TMSXE Deployment Guide (14.5 and
4.1)
4.1)
Page 10 of 51
Comparing deployment models