Cisco Cisco TelePresence Management Suite (TMS) Version 15 Release Notes
Resolved issues
Cisco TMS Release Notes (14.2.2)
Page 14 of 33
Identifier
Description
CSCuh09140 Resolved the issue where modifying the start time of a single (non-recurrent) conference using
the Cisco TMS web interface would cause Cisco TMSBA to return incorrect conference times to
clients. This would cause free/busy information for rooms in Cisco TMSXE, Smart Scheduler
(Cisco TMSPE), and other API clients to be out of sync with the Cisco TMS database.
clients. This would cause free/busy information for rooms in Cisco TMSXE, Smart Scheduler
(Cisco TMSPE), and other API clients to be out of sync with the Cisco TMS database.
CSCuh24788 Resolved the issue where the Cisco TMSPE Smart Scheduler did not allow bookings, and
displayed an error message: "An option key is required to use this feature. For more information,
contact Cisco". The Smart Scheduler does not require an option key.
contact Cisco". The Smart Scheduler does not require an option key.
Resolved in 14.2.1
The following issues were found in previous releases and were resolved in 14.2.1:
Identifier
Description
CSCug68465
CSCug61584
Resolved two issues where upgrading the database could fail.
CSCug53694
Resolved the issue where, under some circumstances, Cisco TMSBA would return meeting
series with deleted exceptions incorrectly, causing Cisco TMSXE to remove the series.
series with deleted exceptions incorrectly, causing Cisco TMSXE to remove the series.
Resolved in 14.2
The following issues were found in previous releases and were resolved in 14.2:
Booking
Identifier
Description
CSCts02650
Resolved the issue where booking a conference on a Cisco TelePresence MCU that had HTTPS
enabled and HTTP disabled could be very slow. This was due to a time-out while Cisco TMS
attempted to contact the MCU on HTTP first.
enabled and HTTP disabled could be very slow. This was due to a time-out while Cisco TMS
attempted to contact the MCU on HTTP first.
CSCud49452 Resolved the issue where editing an existing conference that included two or more dial-in
participants, and removing one participant, resulted in an error. This occurred only when editing
the booking using the Booking API.
the booking using the Booking API.
CSCug18393 Resolved the issue where creating a recurrent conference, then editing any occurrence except
the first and setting Recurrence Interval to None, still treated the conference as recurrent.
CSCud83501 Resolved the issue where booking a conference with a recording alias that is not the first one in
the list in
Booking > New Conference >
Recording, and then changing the route from the default
route defined by Cisco TMS, would disable recording for that conference.
CSCud83494 Resolved the issue where editing an ongoing conference that included recording to be No
Recording could disconnect the conference. This occurred if the route was changed during
booking from the default route defined by Cisco TMS.
booking from the default route defined by Cisco TMS.
CSCud71435 Resolved the issue where
Booking > View Conferences >
select a scheduled recurrent
conference
> Connection Settings
displayed an error and did not load.
CSCud95569 Resolved the issue where an unhandled exception occurred when a user who was a member of a
group that had Booking permissions only, clicked on
Booking > New Conference > Add
Participant
.