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 22 of 65
Resolved in 14.4
The following issues were found in previous releases and were resolved in 14.4:
Booking
Identifier
Description
CSCun25265
Resolved the issue where Cisco TMS threw an exception when saving a conference. This
occurred if the conference was set to Secure: Yes, and one of the participants was added from
a phone book entry and not managed by Cisco TMS, and the contact method was changed
during booking from the
occurred if the conference was set to Secure: Yes, and one of the participants was added from
a phone book entry and not managed by Cisco TMS, and the contact method was changed
during booking from the
Connection Settings
tab.
CSCun25278
Resolved the issue where the Booking Confirmation Email did not show the number for
participants to dial for point-to-point conferences.
participants to dial for point-to-point conferences.
CSCun25553
Resolved the issue in
Booking > List Conferences
where filtering on selected systems, then
resetting the filter to include all systems, caused an error. This was most likely to occur in
deployments with more than 400 systems managed by Cisco TMS.
deployments with more than 400 systems managed by Cisco TMS.
CSCun80913
Resolved the issue with conferences hosted on an MCU that used almost all the capacity (for
example one port is left). When editing the conference to add more dial-in participants, Cisco
TMS added one more than requested.
example one port is left). When editing the conference to add more dial-in participants, Cisco
TMS added one more than requested.
CSCue62960
Improved the error message displayed when booking a recurrent conference where the
duration of the conference had incorrectly been set as longer than how frequently it occurred.
duration of the conference had incorrectly been set as longer than how frequently it occurred.
CSCun26524
Resolved the issue where making changes to the MCU Settings during an ongoing
conference hosted by a TelePresence Server did not apply the changes to the TelePresence
Server.
conference hosted by a TelePresence Server did not apply the changes to the TelePresence
Server.
CSCun27746
Resolved the issue where it was possible to overbook an MCU that had been booked to full
capacity by adding a dial in to the conference after it was initially saved. A message will now
be displayed stating that the conference will be rerouted.
capacity by adding a dial in to the conference after it was initially saved. A message will now
be displayed stating that the conference will be rerouted.
CSCul81027
CSCul66891
Resolved the issue where
Booking > List Conferences >
Delete & Export Log Details threw
an error and the deletion or log export did not occur.
CSCun28082
Resolved the issue in
Booking > List Conferences
where clicking on a conference, then
selecting View from the dropdown menu, then clicking Cancel, generated an error. This
occurred if the server time was set to “pure” UTC (i.e. UTC with no DST rules).
occurred if the server time was set to “pure” UTC (i.e. UTC with no DST rules).
CSCun70487
Resolved the issue where deleting a future conference did not delete the registration event,
which caused a failed event to appear in the Activity Status log.
which caused a failed event to appear in the Activity Status log.
CSCun72824
Resolved the issue with booking a conference of type Manual Connect on a bridge and one
endpoint that did not have Master capability. On saving the conference, a message appeared
stating that the route was not valid. The correct behavior is that Cisco TMS changes the
connection type to No Connect without displaying an error message.
endpoint that did not have Master capability. On saving the conference, a message appeared
stating that the route was not valid. The correct behavior is that Cisco TMS changes the
connection type to No Connect without displaying an error message.
CSCun72876
Resolved the issue where the Booking Availability Grid could incorrectly show a system as
free when it was actually booked during a particular time period if the duration of the booked
conference was less than 30 minutes.
free when it was actually booked during a particular time period if the duration of the booked
conference was less than 30 minutes.
CSCun80937
Resolved the issue where meetings of duration 24 hrs displayed in the booking confirmation
email with a duration of 0 hrs. Meetings of duration 25 hrs were displayed with a duration of 1
hr and so on.
email with a duration of 0 hrs. Meetings of duration 25 hrs were displayed with a duration of 1
hr and so on.
CSCul68806
Resolved the issue in
Booking > New Conference >
Billing Code where double byte
characters were not supported.