Cisco Cisco TelePresence Management Suite (TMS) Version 15 Release Notes
New features
Cisco TelePresence Management Suite Release Notes Software Release Notes (14.6.2)
Page 5 of 89
n
Removed redundant
TMS Scheduling Settings
section from
Systems > Navigator
for non-bookable
systems.
n
Added IP Bandwidth value 6000 kbps when scheduling using
Booking > New Conference
and Cisco
TMSBA.
n
The configuration template for TC software has been updated to incorporate new settings introduced in the
TC7.2.1 release.
TC7.2.1 release.
n
For redundant Cisco TMS deployments, the following will now be logged when a failover takes place:
l
Which services were running on the node that retires.
l
When the services entered an active state.
Cisco TMS Booking API (Cisco TMSBA)
ClientSession ID now required on all licensed API calls
The client must now include a ClientSession ID in the SOAP header of each call requiring a license key, or
Cisco TMS will throw an exception and the call will fail. This exception will include a suggested ID string.
Cisco TMS will throw an exception and the call will fail. This exception will include a suggested ID string.
This change only affects API version 13 and later. The API version for 14.6 is 15.
License requirement changes
The following Cisco TMSBA methods no longer require a license key:
n
GetTransactionsSince
n
GetTransactionsSinceWithExternalId
n
GetRecordingAliases
n
GetConferenceInviteMail
n
GetConferenceBookingEventMail
These methods do now require a license key:
n
EndConferenceById
n
DeleteConferenceById
n
DeleteConferenceRecInstanceById
n
DeleteConferenceByExternalId
n
DeleteConferenceInstanceByExternaId
n
EndConferenceByExternalId
For a full overview of license key requirement, see Cisco TMSBA Programming Reference Guide.
Specifying recipients of booking email
It is now possible to specify email addresses that will receive booking confirmation and error notification
email messages when booking a conference using Cisco TMSBA. In the Cisco TMS web application this is
entered on the
email messages when booking a conference using Cisco TMSBA. In the Cisco TMS web application this is
entered on the
Conference Information
tab when booking a conference.
Reserved external source IDs
Using "TMS" and "TMS-ADHOC" as external source IDs is now reserved for Cisco TMS internal use. Cisco
TMSBA will throw an exception if either is used by another client.
TMSBA will throw an exception if either is used by another client.