Cisco Cisco TelePresence Management Suite (TMS) Version 15
Differences when scheduling TelePresence
Conductor-managed bridges
Conductor-managed bridges
Before moving to a TelePresence Conductor scheduling deployment, note the following differences between
scheduling direct-managed bridges and bridges managed by a TelePresence Conductor:
scheduling direct-managed bridges and bridges managed by a TelePresence Conductor:
Direct-managed
TelePresence Conductor-managed
Booking
n
Conference configurations can be set
per conference, over-riding default
conference settings.
per conference, over-riding default
conference settings.
n
Cisco TMS chooses the SIP URI to
provide the dial-in number for the
conference.
provide the dial-in number for the
conference.
n
Can be added to Cisco TMS participant
and conference templates.
and conference templates.
n
No option to overbook bridge resources.
n
Some conference configurations are set
on the TelePresence Conductor
conference template, and cannot be
changed during booking.
on the TelePresence Conductor
conference template, and cannot be
changed during booking.
n
Users can input the variable part of the
alias during booking to create the dial-in
number for the conference.
alias during booking to create the dial-in
number for the conference.
n
Cannot be added to Cisco TMS participant
and conference templates.
and conference templates.
n
Overbooking of bridge resources: Using
the service preference capacity
adjustment feature, you can configure
Cisco TMS to allow overbooking of the
actual resource available on the bridges in
the pools associated with the service
preference. By doing this, you allow for the
case where users unnecessarily book
more ports than they need for
conferences, thereby freeing up unused
resources for other users.
the service preference capacity
adjustment feature, you can configure
Cisco TMS to allow overbooking of the
actual resource available on the bridges in
the pools associated with the service
preference. By doing this, you allow for the
case where users unnecessarily book
more ports than they need for
conferences, thereby freeing up unused
resources for other users.
Cascading
n
Does not support cascaded
TelePresence Servers.
TelePresence Servers.
n
Cisco TMS decides whether to cascade
MCUs when routing conferences.
MCUs when routing conferences.
n
Cisco TMS cannot create a cascade after
the conference has started if more
participants join than the capacity on the
hosting MCU(s).
the conference has started if more
participants join than the capacity on the
hosting MCU(s).
n
More functionality in
Conference
Control Center
for example, moving
participants from one cascaded MCU to
another.
another.
n
Cascading is selected using the
Distribution options when booking a
conference.
Distribution options when booking a
conference.
n
Cascading is not possible when booking
using clients that use Cisco TMS
Booking API (Cisco TMSBA) for
example: Microsoft Outlook and Smart
Scheduler.
using clients that use Cisco TMS
Booking API (Cisco TMSBA) for
example: Microsoft Outlook and Smart
Scheduler.
n
Supports cascaded TelePresence
Servers.
Servers.
n
TelePresence Conductor cascades the
bridges.
bridges.
n
TelePresence Conductor can cascade on
the fly if more participants join than the
initial capacity of the hosting bridge(s).
the fly if more participants join than the
initial capacity of the hosting bridge(s).
n
No functionality in
Conference Control
Center
except visibility of which bridge a
participant is connected to.
n
You have to select an alias that supports
cascading when booking the conference.
cascading when booking the conference.
n
Cascading is possible when booking
using clients that use Cisco TMS Booking
API (Cisco TMSBA) for example: Microsoft
Outlook and Smart Scheduler.
using clients that use Cisco TMS Booking
API (Cisco TMSBA) for example: Microsoft
Outlook and Smart Scheduler.
Table 1: Differences when scheduling TelePresence Conductor-managed bridges
Cisco TelePresence Conductor with Cisco TMS Deployment Guide (XC3.0 with 14.6)
Page 4 of 25
Differences when scheduling TelePresence Conductor-managed bridges