Cisco Cisco TelePresence Management Suite (TMS) Version 15 Developer's Guide
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.
applications 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
header. The API 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.
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
12
14.3
11
14.2
10
14.1.1
9
13.2
8
13.1.2
7
13.1
6
13.0.1
5
12.6
Versioning examples
When a change to the API is needed, the WSDL must be updated. The WSDL is the contract betweeen the
API and the clients and provides information covering all methods and data types, including values, that the
API supports.
API and the clients and provides information covering all methods and data types, including values, that the
API supports.
Time zone versioning
Cisco TMSBA allows each conference object to include a ConferenceTimeZoneRules element that
contains an array of rules for the time zone (UTC offset) and daylight savings time. (For detail about this
element, see
contains an array of rules for the time zone (UTC offset) and daylight savings time. (For detail about this
element, see
.)
This element was introduced in Cisco TMSBA version 11 with Cisco TMS 14.2. If a client is using version 10
or earlier of the API, regardless of Cisco TMS version:
or earlier of the API, regardless of Cisco TMS version:
n
Booking dates must be in UTC.
n
DayOfWeek values in recurrence patterns must be given in UTC if the API version used is 8 or later.
n
Dates are provided in UTC when retrieving conference information.
n
Cisco TMS uses the time zone rules of the server.
Cisco TMSBA Programming Reference Guide (14.3)
Page 10 of 67
API overview