Cisco Cisco TelePresence Management Suite (TMS) Version 15 Developer's Guide
API version
Cisco TMS version
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.
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
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:
of the API, regardless of Cisco TMS version:
■
Booking dates must be in UTC.
■
DayOfWeek values in recurrence patterns must be given in UTC if the API version used is 8 or later.
■
Dates are provided in UTC when retrieving conference information.
■
Cisco TMS uses the time zone rules of the server.
Note that these conferences will be prone to DST change errors when the time zone of the client is not the same as
the configured time zone on the Cisco TMS server.
the configured time zone on the Cisco TMS server.
Introducing a New Bandwidth Value
When, for example, support for an additional bandwidth value is added to the API, the WSDL changes, and the
version number is increased. If this new bandwidth value is added in version 9 of the API, every client declaring that
they are using version 9 or later will get this new value returned from Cisco TMSBA.
version number is increased. If this new bandwidth value is added in version 9 of the API, every client declaring that
they are using version 9 or later will get this new value returned from Cisco TMSBA.
Clients that announce compliance to versions earlier than 9 will not get the new value returned. Instead , the API
returns the special value default. The API allows all incoming values, but filters values going out. A client declaring a
version lower than 9, that then enumerates a conference with the new bandwidth value, will get the special value
default returned.
returns the special value default. The API allows all incoming values, but filters values going out. A client declaring a
version lower than 9, that then enumerates a conference with the new bandwidth value, will get the special value
default returned.
If the client uses this conference and updates the conference with bandwidth set to default, no change to the
bandwidth value is made, as the API knows this special value means no changes should be made.
bandwidth value is made, as the API knows this special value means no changes should be made.
This filtering of values that older clients do not understand makes the API backwards compatible; older clients built on
older WSDLs can still use an API with a higher version.
older WSDLs can still use an API with a higher version.
7
Cisco TelePresence Management Suite Extension Booking API Programming Reference Guide