Cisco Cisco TelePresence Management Suite (TMS) Version 15 Developer's Guide
Replication
Cisco TMSBA supports two-way replication between the client and Cisco TMS. If the client maintains its own copy of
the reservation database, it must periodically ask Cisco TMS for changes.
the reservation database, it must periodically ask Cisco TMS for changes.
In Cisco TMS, all changes to bookings are tracked in the Cisco TMS (tmsng) database. The data in this table is
available in Cisco TMSBA through the
available in Cisco TMSBA through the
GetTransactionsSince
function. This function gives the client a list of recent
changes on the Cisco TMS side. This function should be run fairly often (such as every five minutes) so that the client
and Cisco TMS reservation databases are in a consistent state.
and Cisco TMS reservation databases are in a consistent state.
Booking Modes
The client can request one of two booking modes from Cisco TMS:
■
Strict–all conferences that cannot be scheduled exactly as requested will cause Cisco TMS to throw an
exception, and the conferences will not be saved.
exception, and the conferences will not be saved.
■
BestEffortForced–conferences that have a resource conflict or routing issue will be saved in Cisco TMS as
Defective, which is shown to the client as a conferencestate on the returned conference object.
Defective, which is shown to the client as a conferencestate on the returned conference object.
This mode works as described below.
Defective Conferences
A Defective conference in Cisco TMS has been booked by an external client that encountered a resource conflict or
routing problem.
routing problem.
A defective conference retains all properties of the booking request without setting up routing or consuming
telepresence resources. Until all issues are resolved, Cisco TMS will not initiate a defective conference or send it to
endpoints.
telepresence resources. Until all issues are resolved, Cisco TMS will not initiate a defective conference or send it to
endpoints.
■
In the case of a routing issue, all endpoints in the booking will be set to Busy for the scheduled time, keeping the
reservation while the administrator or user resolves the issue.
reservation while the administrator or user resolves the issue.
■
In the rare case of an endpoint reservation conflict, the endpoints will not be set to Busy for the defective
booking.
booking.
Defective conferences can be corrected by the organizer or the administrator:
■
Users who book conferences that are saved as defective will be notified by email and can resolve most issues by
changing their request and rescheduling from their client.
changing their request and rescheduling from their client.
■
Administrators can locate and resolve defective conferences in Cisco TMS by going to
Administrative Tools >
Diagnostics > Conference Diagnostics
or
Booking > List Conferences
.
Conferences that are defective because of configuration errors or a permanent lack of routing resources must
be resolved by an administrator.
be resolved by an administrator.
When scheduling a series where only some occurrences have a resource conflict or routing issue, Cisco TMS will
only store the problematic occurrences as defective, leaving the remaining occurrences unaffected.
only store the problematic occurrences as defective, leaving the remaining occurrences unaffected.
If you apply the BestEffortForced booking mode, Cisco TMS will apply the same logic to bookings from your client, and
return defective on conferences that have a resource conflict or routing problem.
return defective on conferences that have a resource conflict or routing problem.
Cisco TMS Entities
System
A system entity in Cisco TMS is any item that can be booked. Note that systems provisioned using Cisco
TelePresence Management Suite Provisioning Extension cannot be booked and are therefore not considered systems
TelePresence Management Suite Provisioning Extension cannot be booked and are therefore not considered systems
5
Cisco TelePresence Management Suite Extension Booking API Programming Reference Guide