Cisco Cisco TelePresence Management Suite (TMS) Version 15 Maintenance Manual
route. If you have manually added an MCU to the conference during booking, the route with this MCU is
chosen. If not, the route with the lowest weight is chosen. The dropdown for changing the Main participant
during booking is ordered based on these weights.
chosen. If not, the route with the lowest weight is chosen. The dropdown for changing the Main participant
during booking is ordered based on these weights.
The following must be noted:
n
There can only be one Main participant per conference.
n
You cannot change the Main participant once the conference has started.
n
The Main participant can never be disconnected as this will tear down the whole conference.
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
are actioned only on the Main
participant, which then carries out that action on all the other participants, for example Mute All, or
Disconnect.
Disconnect.
Allocation
For a scheduled conference, allocation of systems takes place at the conference start time. 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.
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.
Cisco TMS will retry allocation according to the value set in
Administrative Tools > Configuration >
Conference Settings >
Allocation attempts for scheduled calls.
Once Cisco TMS has successfully connected to all participants, the following takes place:
n
Encryption is set for endpoints.
n
Feedback receivers are set on endpoints and bridges.
n
The settings selected in the
MCU 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 conference.
start is a One Button To Push conference.
If connection to the bridge or endpoint fails at any time, allocation of that system fails.
Once allocation is successful,Cisco TMS sends the dial command to each participant. If dialing fails, Cisco
TMS will retry according to the value set in
TMS will retry according to the value set in
Administrative Tools > Configuration > Conference Settings
>
Connection Attempts for Scheduled Calls.
Cisco TMS Administrator Guide (14.3.2)
Page 41 of 342
Routing
Introduction to routing