Cisco Cisco TelePresence Management Suite (TMS) Version 15 Release Notes
Resolved issues
Cisco TelePresence Management Suite Release Notes Software Release Notes (14.4.2)
Page 33 of 65
Resolved in 14.3.1
The following issues were found in previous releases and were resolved in 14.3.1:
Booking
Identifier
Description
CSCuj25656 Resolved the issue where Cisco TMS incorrectly calculated resource availability for a Cisco
TelePresence Recording Server cluster node by looking at the availability for the entire cluster
instead of the single node. This could lead to overbooking of resources.
instead of the single node. This could lead to overbooking of resources.
CSCuj04722
Resolved the issue where an error occurred when adding a Cisco TelePresence Recording
Server recording alias to a booking in Cisco TMS, if there was already a conference that included
recording scheduled for the same day. This applied to clustered recording server setups only.
Server recording alias to a booking in Cisco TMS, if there was already a conference that included
recording scheduled for the same day. This applied to clustered recording server setups only.
CSCui09851
Resolved the issue where the Location for a meeting is not shown in the .ics file or in the Microsoft
Outlook calendar, although it does show in Cisco TMS.
Outlook calendar, although it does show in Cisco TMS.
CSCuh99378 Resolved the issue where Cisco TMS did not route scheduled conferences through a
TelePresence Conductor even though
Administrative Tools > Configuration > Conference
Settings >
Preferred MCU Type in Routing was set to Cisco TelePresence Conductor.
CSCuh89503 Resolved the issue where scheduled conferences with extremely long durations (one or two
years) could suddenly end for no apparent reason, a long time before the conference was
scheduled to end.
scheduled to end.
CSCuh43897 Resolved the issue where removing the <ADD:ICALENDAR_ATTACHMENT> tag from the
Booking Invite HTML email template did not remove the ICS attachment from the HTML email that
was generated and sent.
was generated and sent.
CSCuh61606 Resolved the issue where carriage returns and line breaks were not displayed in the booking
confirmation email.
CSCug88031 It is no longer possible to book a secure conference that includes a TelePresence Conductor. As
this is not supported in Cisco TMS, an error is now generated if the secure option is chosen.
Previously no error was shown during booking and the conference appeared to be secure
although it was not.
Previously no error was shown during booking and the conference appeared to be secure
although it was not.
CSCug75561 Resolved the issue where Cisco TMS did not resend updated calendar information to Cisco
TelePresence System 3000, 1000 and 500 series endpoints, or endpoints running Cisco
TelePresence TC software. This affected endpoints scheduled in recurrent conferences, if one
instance of the recurrent series was edited, or the entire recurrent series was deleted.
TelePresence TC software. This affected endpoints scheduled in recurrent conferences, if one
instance of the recurrent series was edited, or the entire recurrent series was deleted.
CSCuh39031 Resolved the issue where incomplete data was generated in the
Booking > List Conferences >
Export Log and Export Details Log.
CSCuh36391 Resolved the issue where it was not possible to create a conference that included ISDN audio
dial in participants.
CSCui74583
Resolved the issue where a conference with a teardown buffer could display the wrong end date
in
in
Booking > List Conferences
.
CSCug86198 Resolved the issue where the extend meeting message was not received on endpoints if there
was a special character in the field:
Administrative Tools > Configuration > Conference
Settings >
Contact Information to Extend Meetings.
CSCuh46375 Resolved the issue where editing the Extend Mode of an ongoing conference failed: it is no
longer possible to edit the Extend Mode for an ongoing conference.