Cisco Cisco TelePresence Management Suite (TMS) Version 15 Developer's Guide
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 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.
is 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.
Booking modes
The client can request one of two booking modes from Cisco TMS:
n
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.
n
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.
This mode works as described below.
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.
conflict or 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.
n
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.
keeping the reservation while the administrator or user resolves the issue.
n
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:
n
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.
issues by changing their request and rescheduling from their client.
n
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.
must 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.
TMS will 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.
client, and return defective on conferences that have a resource conflict or routing problem.
Cisco TelePresence Management Suite Extension Booking API Programming Reference Guide (14.6)
Page 9 of 81
API overview
Functional overview