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 24 of 89
n
Added secure-only support for Cisco TelePresence ISDN Gateway.
n
SchedulerService now retries failed registrations of scheduled conferences every 5 minutes until 5 minutes
after the conference was scheduled to start.
after the conference was scheduled to start.
n
Cisco TMS's Windows services are now configured to restart automatically if they unexpectedly crash.
The restart will be attempted every 1 minute. Previously no action was taken if one of the services
unexpectedly crashed.
The restart will be attempted every 1 minute. Previously no action was taken if one of the services
unexpectedly crashed.
n
It is no longer possible to delete Registering conference events from the
Activity Status
overview list, as
doing so would prevent the conference from launching.
n
It is no longer possible to sort by Owner on the
List Conferences
page.
n
Conferences booked on behalf of another user are now visible to users in groups that have the following
permissions set:
permissions set:
l
List Conferences - All: No options checked
l
List Conferences - Mine: Read and Update checked
Changes to Cisco TMSBA (Booking API)
The Cisco TMSBA version number for this release is 13. Note that some of the changes below are not
versioned, and will affect any client using the API with Cisco TMS14.6.2, regardless of the API version
called.
versioned, and will affect any client using the API with Cisco TMS14.6.2, regardless of the API version
called.
.
Changes to the handling of ongoing and deleted meetings
above also affect all
Cisco TMSBA versions used with Cisco TMS 14.4.
Support for the No Connect meeting type
Cisco TMSBA now supports booking meetings as No Connect, which is where all participants must dial in,
and none are connected or prompted automatically.
and none are connected or prompted automatically.
Support for including email addresses in meetings
Including an email address per participant is now supported, and can be used to make Cisco TMS send
conference email notifications to participants. As of Cisco TMSPE 1.2, Smart Scheduler uses this feature to
invite Cisco TMSPE users to meetings.
conference email notifications to participants. As of Cisco TMSPE 1.2, Smart Scheduler uses this feature to
invite Cisco TMSPE users to meetings.
License tracking change
A client session string has been added to the SOAP header to allow Cisco TMS to recognize each client
consuming a license key. Previously, the key was tied to the IP address of the client server.
consuming a license key. Previously, the key was tied to the IP address of the client server.
The new implementation allows different nodes in a redundant client deployment to use the same license key
for Cisco TMSBA.
for Cisco TMSBA.
for implementation details.
Meeting extensions no longer synchronized