Cisco Cisco TelePresence Management Suite (TMS) Version 15 Release Notes
Resolved issues
Cisco TelePresence Management Suite Release Notes Software Release Notes (14.4)
Page 36 of 72
Recurrence
Identifier
Description
CSCun81304
Resolved the issue where editing a recurrent conference series with recurrence pattern ' First
Day of every month' changed the recurrence pattern to 'First Sunday of every month'.
Cancelling the edit and then saving the conference changed it from a recurrent to a non-
recurrent conference.
Day of every month' changed the recurrence pattern to 'First Sunday of every month'.
Cancelling the edit and then saving the conference changed it from a recurrent to a non-
recurrent conference.
CSCun81313
Resolved the issue where deleting the first occurrence of a recurrent series, then editing the
series to disable recurrence, deleted all occurrences of the conference. The instance that was
edited to remove recurrence should have remained as a non-recurrent conference.
series to disable recurrence, deleted all occurrences of the conference. The instance that was
edited to remove recurrence should have remained as a non-recurrent conference.
CSCue26779
Resolved the issue where Cisco TMS consumed ports after a conference had been moved to
a different MCU. This only occurred for recurrent conferences, if an instance was moved to a
different MCU.
a different MCU. This only occurred for recurrent conferences, if an instance was moved to a
different MCU.
CSCtr53461
Resolved the issue where swapping the bridge for one meeting occurrence in a recurrent
series still showed that bridge as being in the conference in the
series still showed that bridge as being in the conference in the
List Conferences
page, when
filtering on the original bridge.
CSCum41801
Resolved the issue where booking a daily recurrent conference using the End by Date option
ended the conference series the day before the date specified. This occurred if the user
booking the conference was in a time zone with a negative UTC offset.
ended the conference series the day before the date specified. This occurred if the user
booking the conference was in a time zone with a negative UTC offset.
CSCun81618
It is now possible to move an instance past a deleted or previously moved instance of the
same series.
same series.
CSCui04546
Resolved the issue where Cisco TMS incorrectly selected a bridge for a recurrent series that
had no capacity for one of the occurrences; as a consequence, saving the conference failed.
had no capacity for one of the occurrences; as a consequence, saving the conference failed.
CSCun81408
Resolved the issue where deleted participants in a recurrent series incorrectly appeared
under the Location section of the Booking Confirmation Email.
under the Location section of the Booking Confirmation Email.
CSCui68087
Resolved the issue that occurred when a recurrent meeting series was edited, where any
changes made previously to an individual occurrence in the series were lost.
changes made previously to an individual occurrence in the series were lost.
CSCtt45102
Resolved the issue where it was not possible to make changes to a recurrent series when a
participant that had been removed from the series was part of a new booking that overlapped
the first series.
participant that had been removed from the series was part of a new booking that overlapped
the first series.
CSCuo49886
In
Booking > List Conferences > Edit Conference
, made Owner field read-only when editing
an instance of a series.
TMS Tools
Identifier
Description
CSCul81067
Resolved the issue where it was not possible to access the Cisco TMSPE Database
Connection settings page in
Connection settings page in
TMS Tools.
The message: "Current settings could not be read, the
dialog will be populated with default values." was displayed.
CSCul44318
CSCun15585
TMS Tools > Configuration >
Cisco TMSPE Database Connection Settings incorrectly
accepted a comma as the port delimiter. This did not, however, set the port and Cisco TMS
was not able to connect to the Cisco TMSPE database. A Port field has been added to this
page.
was not able to connect to the Cisco TMSPE database. A Port field has been added to this
page.
CSCum88383
Resolved the issue where editing the Cisco TMSPE Database Connection Settings using
Cisco TMS Tools could wipe the database connection password field, breaking the connection
between Cisco TMS and Cisco TMSPE.
Cisco TMS Tools could wipe the database connection password field, breaking the connection
between Cisco TMS and Cisco TMSPE.