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 TelePresence Conductor.
Direct-managed
TelePresence Conductor-managed
Booking
n
Conference
configurations can be
set per conference,
over-riding default
conference settings.
n
Cisco TMS chooses
the SIP URI to provide
the dial-in number for
the conference.
n
Can be added to Cisco
TMS participant 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.
n
Users can input the variable part of the alias during booking to
create the dial-in number for the conference.
n
Cannot be added to Cisco TMS participant 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 resources 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.
Table 18: Differences when scheduling TelePresence Conductor-managed bridges
Cisco Collaboration Meeting Rooms (CMR) Hybrid Configuration Guide (TMS 14.6 - WebEx WBS29.11)
Page 68 of 254
Configuration Checklist
Differences When Scheduling TelePresence Conductor-Managed Bridges