Event Execution; Conference Connection And Control; Cisco Tms Redundancy Configuration And Overview - Cisco TMS SERVER REDUNDANCY - CONFIGURATION GUIDE 13.0 Configuration Manual

Cisco TMS Redundancy limitations and notes
This section will outline functionalities that may be affected or operate differently when using Cisco
TMS in a redundant fashion.

Event Execution

Events that have already begun to execute by a particular server will not be completed by another
server if the executing server fails.
Events can be executed by any Cisco TMS server connected to the database. Once an event
starts on a particular server, it will not be resumed by another server. So if a server fails, any
actively executing events on that server will potentially not complete. This only affects events that
are in progress. As most evens finish very quickly, the number of concurrently running events on
a server should be low, so the number of potential events affected by a server failure will be low .
Some examples of events that can be affected:
A software upgrade in mid-progress will fail if the server running the event fails.
A template push to systems will fail if the server running the event fails.

Conference Connection and Control

Execution of scheduled calls in Cisco TMS is actually broken into three phases. Initiation, Active
Monitoring, and Disconnection. Initiation and Disconnection are actually handled as separate events
for resiliency. Active Monitoring will be handled by the Cisco TMS Server who handled the call
initialization. By default, the same Cisco TMS server that was used to book a call will be the default to
execute the call and all phases of the call. If a server fails, there are limitations to how active calls
being handled by that server will be handled. Calls that have not begun the initialization phase or are
executing on other servers will not be affected.
Automatic call launch.
If the primary Cisco TMS server for call launching is not active, another active Cisco TMS server
will start the conference after 60 seconds. If no secondary server is running when the call is
scheduled to start, a check is made when a server does come up for any call that has not started
that should have been and will start them
Conferences that are still initializing and have not finished connecting will not automatically be
started.
15 minutes prior to a conference's scheduled start time, a conference will be initialized by one
server. If that Cisco TMS server fails before the conference finishes being connected, the
conference will not be connected by another Cisco TMS server.
Conferences that are in the process of being disconnected may fail to completely disconnect.
If the server performing the conference disconnection fails during the actual disconnection of the
conference, the conference may not automatically be ended.

Cisco TMS redundancy configuration and overview

Cisco Cisco TMS Redundancy limitations and notes
Page 31 of 32