Cisco Cisco TelePresence Management Suite (TMS) Version 15 Maintenance Manual
If an external main participant is required, Cisco TMS compiles a prioritized list of possible main participants
based on the criteria above. Cisco TMS chooses the first available participant to be the Main participant. If
multiple bridges have the same priority, one of these is selected at random.
based on the criteria above. Cisco TMS chooses the first available participant to be the Main participant. If
multiple bridges have the same priority, one of these is selected at random.
If you have manually added an MCU to the conference during booking, the route with this MCU is chosen.
The order in which Cisco TMS prioritizes the above criteria could change from one release of Cisco TMS to
the next.
the next.
You can use scheduling logging at INFO level to see how Cisco TMS compiled the prioritized list. See
The following must be noted:
n
There can only be one Main participant per conference.
n
The Main participant can be changed once the conference has started using
Conference Control Center
.
In this case the conference will be torn down, rerouted and reconnected.
n
If one of two sides of a call leg is an MCU, the MCU is always the Main system.
n
Cisco TMS communicates with the Main system to send conference disconnect and mute requests.
n
Cisco TMS monitors the Main system to provide conference information for
Conference Control Center
.
The default is that the Main participant places all calls in a scheduled conference, however in One Button To
Push conferences, systems dial into the Main participant instead. It is also possible to edit the connection
settings for a conference during booking (if using the Cisco TMS booking interface) so that systems dial into
the Main participant. This is not possible using the Cisco TMSBA. This option is not editable here for
cascaded conferences.
Push conferences, systems dial into the Main participant instead. It is also possible to edit the connection
settings for a conference during booking (if using the Cisco TMS booking interface) so that systems dial into
the Main participant. This is not possible using the Cisco TMSBA. This option is not editable here for
cascaded conferences.
Changes made to an ongoing conference in
Conference Control Center
, for example Mute All, or
Disconnect, are actioned only on the Main participant, which then carries out that action on all the other
participants. The only exceptions to this are Set Mic Off and Send Message, which are actioned on the
individual participants.
participants. The only exceptions to this are Set Mic Off and Send Message, which are actioned on the
individual participants.
Allocation
For a scheduled conference, allocation of systems takes place at the conference start time, unless you are
using Early Join. Cisco TMS allocates the Main participant first, and then all other participants. If the Main
participant cannot be allocated and MCU failover is unsuccessful, the conference itself will fail and no further
allocation will take place.
using Early Join. Cisco TMS allocates the Main participant first, and then all other participants. If the Main
participant cannot be allocated and MCU failover is unsuccessful, the conference itself will fail and no further
allocation will take place.
Allocation means that Cisco TMS attempts to connect to the system to do the following:
n
Encryption is set on the main participant.
n
Feedback receivers are set on endpoints and bridges.
n
The conference is created and the settings selected in the
MCU Settings
or
TelePresence Conductor
Settings
tab in the booking page are applied to the bridge.
n
Ad hoc calls that the endpoints are participating in are disconnected, unless the conference that is about to
start is a One Button To Push or No Connect conference.
start is a One Button To Push or No Connect conference.
Cisco TMS will retry allocation according to the value set in
Administrative Tools > Configuration >
Conference Settings >
Allocation attempts for scheduled calls.
If connection to the bridge or endpoint fails at any time, allocation of that system fails.
Cisco TelePresence Management Suite Administrator Guide (14.6)
Page 38 of 344
Routing
Introduction to routing