Cisco Cisco TelePresence Management Suite (TMS) Version 15 Release Notes
Resolved issues
Cisco TelePresence Management Suite Release Notes Software Release Notes (14.4.1)
Page 50 of 61
Identifier
Description
CSCty74386
Resolved the TMS Scheduler issue where adding a phone book entry as the first participant
followed by a dial-out number would lead to the phone book entry replacing all other participant
addresses.
followed by a dial-out number would lead to the phone book entry replacing all other participant
addresses.
CSCud39079
Improved Cisco TMS’ handling of database deadlocks.
Resolved in 14.0
The following issues were found in previous releases and were resolved in 14.0:
Booking
Identifier
Description
CSCua62217
Resolved the issue where an error could appear in the log-web.txt log when adding a non-Cisco
TMS-managed participant (dial-in, dial-out, phone book entry, user) to a One Button To Push
conference.
TMS-managed participant (dial-in, dial-out, phone book entry, user) to a One Button To Push
conference.
CSCty98098
Resolved the issue where confirmation emails were not received when booking a One Button To
Push conference which included at least one non-Cisco TMS-managed participant (dial-in, dial-
out, phone book entry, user).
Push conference which included at least one non-Cisco TMS-managed participant (dial-in, dial-
out, phone book entry, user).
CSCty94156
Resolved the issue where a SIP conference scheduled on an MCU in Cisco TMS did not register
as SIP if H323 was disabled on the MCU.
as SIP if H323 was disabled on the MCU.
This happened because SIP registration was dependent on the H323 MCU prefix setup,
meaning it would fail if H323 was turned off on the MCU.
meaning it would fail if H323 was turned off on the MCU.
CSCtx64185
Resolved the issue where Cisco TMS did not register SIP participants as taking up resources in
stored bookings on an MCU, which made it possible to overbook SIP participants on the MCU in
subsequent bookings.
stored bookings on an MCU, which made it possible to overbook SIP participants on the MCU in
subsequent bookings.
CSCua26100
Resolved the issue where in
Booking > New Conference >
Recurrence Settings the calendar
sometimes did not display in the
Recurrence Settings
pop up window.
CSCua60010
In
Booking > New Conference >
Add participants
>
add an MCU and some participants
>
OK
>MCU Settings
tab – the fields on this tab will now be shown in the language the logged-in
Cisco TMS user has selected.
Previously they were always in English regardless of the user language selected in Cisco TMS.
CSCty32654
Resolved the issue where it was possible to double book a system, if the start date of a recurrent
meeting series in which it was a participant was changed to a date in the past.
meeting series in which it was a participant was changed to a date in the past.
Monitoring
Identifier
Description
CSCua60141 Resolved the issue where removing a participant from a scheduled One Button To Push
conference did not update that participant’s Meetings calendar to inform it that it had been
removed from the conference.
removed from the conference.