Cisco Cisco TelePresence Management Suite (TMS) Version 15 Release Notes
New features
Cisco TelePresence Management Suite Release Notes Software Release Notes (14.4)
Page 22 of 72
n
WebEx Enabled TelePresence is supported by Cisco TMSBA. We strongly recommend using the new
ExternalConference attribute to add WebEx to a conference.
The previous way of adding WebEx to conferences (DataConference) has been kept for backwards
compatibility. Support for non-WebEx data conferences was discontinued in API version 10 (Cisco TMS
14.1).
ExternalConference attribute to add WebEx to a conference.
The previous way of adding WebEx to conferences (DataConference) has been kept for backwards
compatibility. Support for non-WebEx data conferences was discontinued in API version 10 (Cisco TMS
14.1).
n
Booking of SIP Audio dial-in and dial-out participants is now fully supported.
n
Clients now have two new functions for invoking email confirmation or notifications of other booking
events; GetConferenceBookingEventMail and GetConferenceInviteMail. Clients may also insert their
own errors, warnings, or informational messages into email notifications. A new SendConfirmationMail flag
in the SOAP header lets clients determine whether email notifications should be sent for each booking
request.
events; GetConferenceBookingEventMail and GetConferenceInviteMail. Clients may also insert their
own errors, warnings, or informational messages into email notifications. A new SendConfirmationMail flag
in the SOAP header lets clients determine whether email notifications should be sent for each booking
request.
n
Language support for email notifications: The new ConferenceLanguage attribute of the Conference object
specifies which language to use for notifications. The new Remote Setup API function
GetConferenceLanguages returns a full list of supported languages.
specifies which language to use for notifications. The new Remote Setup API function
GetConferenceLanguages returns a full list of supported languages.
The following changes have been made to existing functionality:
n
GetConferencesForSystems now returns scheduled conferences only, and no longer includes ad hoc
conferences.
conferences.
n
GetConferencesForUser and GetConferencesForSystem now calculate using minutes instead of
rounding to the nearest day.
rounding to the nearest day.
Several changes have been implemented to how ongoing conferences are handled:
n
Cisco TMS no longer clears the existing call route when adding or removing a participant using Cisco
TMSBA during an ongoing conference.
TMSBA during an ongoing conference.
n
When the start time of an ongoing conference is changed, the conference will be re-seeded, and the
ongoing conference may be disrupted.
ongoing conference may be disrupted.
n
For any changes to the booking of an ongoing occurrence of a series using SaveConference, a new
Ongoing element has been introduced which the client may use to prevent the ongoing meeting from being
affected by changes, to avoid disruptive effects to the meeting or series.
Ongoing element has been introduced which the client may use to prevent the ongoing meeting from being
affected by changes, to avoid disruptive effects to the meeting or series.
n
GetRecurrentConferenceById now returns the start and end time both for any ongoing occurrence and
the next upcoming occurrence of the series.
the next upcoming occurrence of the series.
For further detail on the features described above and how to use them, see Cisco TelePresence
Management Suite Extension Booking API Programming Reference Guide for this version.
Management Suite Extension Booking API Programming Reference Guide for this version.
Changed in 14.2
Changes to service pack requirements for Windows Server 2008 and Windows Server 2008 R2
Before upgrading to this version of Cisco TMS:
n
Windows Server 2008 requires Service Pack 2.
n
Windows Server 2008 R2 requires Service Pack 1.
HTTPS enabled by default for the Cisco TMS website
To improve security, HTTPS is now enabled by default for the Cisco TMS website. Administrators will be
asked if they want to provide a certificate or generate a self-signed certificate during install.
asked if they want to provide a certificate or generate a self-signed certificate during install.