Cisco Cisco TelePresence Management Suite (TMS) Version 15 Developer's Guide
Get a list of transactions listed by transaction ID by using the GetTransactionsSince function. All conferences have a
transaction ID property
transaction ID property
The list of transactions contains:
■
The transaction type (New, Update, and Delete)
■
An associated conference ID.
Use
GetConferenceById
to get an updated Conference object and update the conference with the external source. The
current transaction ID should then be updated to the last conference’s TransactionId.
Booking
The API allows you to forward booking requests from an external booking system to Cisco TMS, and reserve the
resources there.
resources there.
■
Get Conference objects with default values for Conference properties defined in Cisco TMS by using
GetDefaultConference
.
■
Retrieve saved conferences by using one of the following functions:
—
GetConferenceById
—
GetConferenceIdByExternalId
—
GetRecurrentConferenceById
—
GetConferencesForUser
—
GetConferencesForSystems
■
Save changes to a conference by editing the conference properties and using the function
SaveConferenceWithMode
. This will save the conference to Cisco TMS if the properties validate. If not, an
exception will be raised. When saving, you must provide the same Version value as you got when retrieving the
conference, or the save will be declined. If the save is declined because your Version value is out of date,
retrieve the conference again prior to attempting another save operation
conference, or the save will be declined. If the save is declined because your Version value is out of date,
retrieve the conference again prior to attempting another save operation
Availability
The API allows you to display reservations from the Cisco TMS internal reservation database.
Limitations
WebEx Booking Limitations
WebEx booking does not support all recurrence patterns and options supported by Cisco TMS:
■
Exceptions from a recurrence pattern (moving or updating one or more meetings) are not supported.
■
Exceptions from a recurrence pattern (moving or updating one or more meetings) are not supported, unless
WebEx is booked as OwnedExternally. For more details see
WebEx is booked as OwnedExternally. For more details see
■
Some advanced recurrence patterns are not supported.
When WebEx is not supported for a particular booking, the booking will fall back to telepresence only.
WebEx-only meetings not supported
WebEx-only meetings should not be booked using Cisco TMSBA. If using Cisco TMS to create a conference that
includes WebEx without including any telepresence participants, telepresence resources will still be taken up, as an
includes WebEx without including any telepresence participants, telepresence resources will still be taken up, as an
15
Cisco TelePresence Management Suite Extension Booking API Programming Reference Guide