Cisco Cisco TelePresence Management Suite (TMS) Version 15
Example scheduling scenarios
Here are examples of some common scheduling scenarios and descriptions of how to set up your pools and
service preferences accordingly. There are advantages and disadvantages to every scenario, which are also
mentioned below.
service preferences accordingly. There are advantages and disadvantages to every scenario, which are also
mentioned below.
Service
Preference
contains ...
Preference
contains ...
Configuration
Advantages
Disadvantages
Example 1
Dedicated
bridge for
scheduled
conferences.
bridge for
scheduled
conferences.
Single pool, with a single
conference bridge.
conference bridge.
Pool marked to be used for
scheduling in the
TelePresence Conductor
Service Preference. Pool is
reported to Cisco TMS in
capacity information
requests.
scheduling in the
TelePresence Conductor
Service Preference. Pool is
reported to Cisco TMS in
capacity information
requests.
Conference
availability is
guaranteed,
subject to bridge
failure (or full
capacity).
availability is
guaranteed,
subject to bridge
failure (or full
capacity).
Maximizes use
of resources, as
Cisco TMS will
book ports until
the bridge is full.
of resources, as
Cisco TMS will
book ports until
the bridge is full.
Uses one conference
bridge exclusively for
scheduling.
bridge exclusively for
scheduling.
Cascaded conferencing
does not occur: to avoid
wasting resources,
cascading should be
disabled.
does not occur: to avoid
wasting resources,
cascading should be
disabled.
Example 2
n
Dedicated
bridge for
scheduled
conferences
bridge for
scheduled
conferences
n
Dedicated
backup
bridge
backup
bridge
Two pools.
Both pools contain a single
conference bridge. The
second pool is used as a
backup if the bridge in the
highest priority pool fails.
conference bridge. The
second pool is used as a
backup if the bridge in the
highest priority pool fails.
Only the first pool is marked
for scheduling in the
TelePresence Conductor
Service Preference and
reported to Cisco TMS.
for scheduling in the
TelePresence Conductor
Service Preference and
reported to Cisco TMS.
As for Example
1, with added
benefit of
fallback in case
of bridge failure.
1, with added
benefit of
fallback in case
of bridge failure.
Uses two conference
bridges exclusively for
scheduling.
bridges exclusively for
scheduling.
Consumes backup
resources.
resources.
To avoid wasting
resources, cascading
should be disabled.
resources, cascading
should be disabled.
Example 3
n
Dedicated
bridge for
scheduled
conferences
bridge for
scheduled
conferences
n
Shared-use
backup
bridges for
both
scheduled
and non-
scheduled
conferences
backup
bridges for
both
scheduled
and non-
scheduled
conferences
Two or more pools.
Highest priority pool with
one bridge only, used for
scheduled conferences.
one bridge only, used for
scheduled conferences.
Other pools contain bridges
for both scheduled (as
backup) and non-scheduled
conferences.
for both scheduled (as
backup) and non-scheduled
conferences.
Only the first pool is marked
for scheduling in the
TelePresence Conductor
Service Preference and
reported to Cisco TMS.
for scheduling in the
TelePresence Conductor
Service Preference and
reported to Cisco TMS.
As for Example
1, with possible
benefit of
fallback in case
of bridge failure if
the other pools
have spare
capacity.
1, with possible
benefit of
fallback in case
of bridge failure if
the other pools
have spare
capacity.
Uses one conference
bridge exclusively for
scheduling.
bridge exclusively for
scheduling.
To avoid wasting
resources on the
dedicated bridge,
cascading should be
disabled.
resources on the
dedicated bridge,
cascading should be
disabled.
Table 9: Comparison of scheduling scenarios
Cisco TelePresence Conductor with Cisco TMS Deployment Guide (XC3.0 with 14.6)
Page 20 of 25
Example scheduling scenarios