Cisco Cisco TelePresence Management Suite (TMS) Version 15 Developer's Guide
■
systems that are controlled by Cisco TMS (and thus receive phonebooks, generate CDRs and so on)
■
systems added to Cisco TMS as "Unmanaged Endpoint".
Other types of entries, such as phonebook entries or provision directory users, are not system entities in Cisco TMS.
Each system entity has its own TMS System Id, which is used to uniquely identify the system in the Cisco TMS
database, tied to system settings such as SIP URIs, gatekeeper addresses, and software versions. A subset of this
system data is available in Cisco TMSBA through the
database, tied to system settings such as SIP URIs, gatekeeper addresses, and software versions. A subset of this
system data is available in Cisco TMSBA through the
GetSystemById
function.
Conference
Each booking in Cisco TMS is a conference entity in the tmsng database.
Each conference has a unique combination of ExternalSourceId and ExternalPrimaryKey used to identify the
conference. Each occurrence of a recurrent series is also identified by an InstanceId.
conference. Each occurrence of a recurrent series is also identified by an InstanceId.
Using ConferenceId as sole identifier is considered a legacy feature, but still supported by Cisco TMSBA.
User
The Cisco TMS user entity holds information about Cisco TMS users, such as their first name, last name, username,
and email address. All users have a unique user ID.
and email address. All users have a unique user ID.
API Versioning
Cisco TMSBA versioning is designed to provide a backwards compatible API to clients. This means that applications
written for an older version of the API will keep working when upgrading to Cisco TMS with a newer version of the
API.
written for an older version of the API will keep working when upgrading to Cisco TMS with a newer version of the
API.
Each SOAP message sent to the API by the client must announce which version it complies with in a header. The API
will filter what is returned to the client based on this announced version. See
will filter what is returned to the client based on this announced version. See
.
Version History
Version 0 of the API corresponds to version 9 of Cisco TMS. Not all versions of Cisco TMS include changes to the API.
Below is an overview of the last Cisco TMS versions that have included a new version of Cisco TMSBA.
API version
Cisco TMS version
17
15.2.1
17
15.1
16
15.0
15
14.6
14
14.5
13
14.4
12
14.3
11
14.2
10
14.1.1
9
13.2
8
13.1.2
6
Cisco TelePresence Management Suite Extension Booking API Programming Reference Guide