Cisco Cisco TelePresence Management Suite (TMS) Version 15 Release Notes
Resolved caveats
Resolved caveats
The following issues were found in previous releases and were resolved in 13.1.
Booking API
Reference ID
Summary
84798
Resolved issue where a getconferencebyid search returned an unspecified error. The error
was due to the fact that more than one of the participants had been purged from Cisco TMS.
was due to the fact that more than one of the participants had been purged from Cisco TMS.
87585
Resolved issue where the ConferenceServiceDB.GetConferences method didn’t return any
conferences if there were no participants in the conference. This only happened through the
booking API. This is not possible in Cisco TMS Booking as you are not allowed to make a
booking without participants.
conferences if there were no participants in the conference. This only happened through the
booking API. This is not possible in Cisco TMS Booking as you are not allowed to make a
booking without participants.
87666
The Cisco TMS booking API now supports deletion and modification of exceptions by an
incoming ExConference instance member, the array RecurrenceException. In previous
versions of the booking API, clients needed to call SaveConferenceRecInstance separately
for each exception. Clients may now send all exceptions at once in the RecurrenceException
array.
incoming ExConference instance member, the array RecurrenceException. In previous
versions of the booking API, clients needed to call SaveConferenceRecInstance separately
for each exception. Clients may now send all exceptions at once in the RecurrenceException
array.
87297
Resolved issue where External MCU Usage in Routing is set to Always, except point to
point (Administrative Tools > Configuration > Conference Settings > Advanced
Conferencing Options) had no effect on the routing for the conference. Multisite was used
instead of an MCU.
This issue didn’t occur in Cisco TMS or Scheduler, only through the API (Cisco TMSXE,
Lotus Notes and the API).
point (Administrative Tools > Configuration > Conference Settings > Advanced
Conferencing Options) had no effect on the routing for the conference. Multisite was used
instead of an MCU.
This issue didn’t occur in Cisco TMS or Scheduler, only through the API (Cisco TMSXE,
Lotus Notes and the API).
88677
Resolved issue where the booking confirmation email showed Reservation only instead of
the default reservation type when booking through the API.
the default reservation type when booking through the API.
86356
Resolved issue where adding a Content Server through the booking API would give an
Unspecified error if the client did not provide a recording alias. Cisco TMS will now
automatically select an eligible booking alias if none is provided.
Unspecified error if the client did not provide a recording alias. Cisco TMS will now
automatically select an eligible booking alias if none is provided.
89056
The Cisco TMS booking API will now accept recurrent bookings containing instances both in
the past and in the future. The instances in the past are now skipped when changes are
saved to a series.
the past and in the future. The instances in the past are now skipped when changes are
saved to a series.
88605
Resolved issue where an update to a conference involving an MCU could fail if an MCU no
longer was necessary to connect the participants.
longer was necessary to connect the participants.
87566
The Cisco TMS booking API has a new method GetRecurrentConferenceById, returning a
Conference object with the given ConferenceId.
Conference object with the given ConferenceId.
87191
Resolved issue where Cisco TMS did not reset the master participant if a client sent a new
TMSMasterParticipant for an existing booking.
TMSMasterParticipant for an existing booking.
Installation
Reference ID
Summary
85134
An improvement has been made to the Cisco TMS installer where the SQL server version
and the compatibility level are enforced. The installer will ensure that if SQL 2008 is used the
compatibility level will be set to 100. If the SQL version is 2005, the compatibility level will be
set to 90.
and the compatibility level are enforced. The installer will ensure that if SQL 2008 is used the
compatibility level will be set to 100. If the SQL version is 2005, the compatibility level will be
set to 90.
85705
Resolved issue where a Cisco TMS upgrade made on Windows Server 2008, did not detect if
IIS was installed. This meant that a custom install did not allow virtual directories to be listed.
A blank box was displayed and the installation was made using the default website and not
on a customer specific virtual directory.
IIS was installed. This meant that a custom install did not allow virtual directories to be listed.
A blank box was displayed and the installation was made using the default website and not
on a customer specific virtual directory.
84382
An improvement has been made to the installer so that on a new installation of Cisco TMS,