Cisco Cisco TelePresence Management Suite (TMS) Version 15 Release Notes
Resolved issues
Cisco TelePresence Management Suite Release Notes Software Release Notes (14.6)
Page 47 of 79
Users and groups
Identifier
Description
CSCun28017
Resolved the issue where editing any setting for a user when there were more existing groups
than the Records per Page value removed the user from any group that was not displayed in
the current page.
than the Records per Page value removed the user from any group that was not displayed in
the current page.
CSCun28084
Resolved the issue where an Active Directory user that had never logged into Cisco TMS
before was unable to log in. This occurred if
before was unable to log in. This occurred if
Administrative Tools > Configuration > Network
Settings > Active Directory >
Lookup User Information from Active Directory was set to
Yes, but one or more of the other fields in the
Active Directory
section contained incorrect
information.
Booking API (Cisco TMSBA)
Identifier
Description
CSCun25408
Resolved the issue where booking a conference using Cisco TMSBA gave an error in Cisco
TMS. This occurred when the user making the booking did not already exist in Cisco TMS and
had a username greater than 36 characters.
TMS. This occurred when the user making the booking did not already exist in Cisco TMS and
had a username greater than 36 characters.
CSCul50039
Resolved the issue where the "Allow Remote Booking" option was not visible in
Systems >
Navigator
for Unified CM-registered endpoints. This occurred if the "Per 25 Endpoints" option
key was used for activating Cisco TMSBA. This was mainly a cosmetic issue as the endpoints
were still bookable using Cisco TMSBA.
were still bookable using Cisco TMSBA.
CSCun27792
Resolved the issue where creating a conference that contained deleted systems using Cisco
TMSBA generated an exception. An email message is now sent.
TMSBA generated an exception. An email message is now sent.
CSCun81238
Resolved issue where GetRecurrentConference would be one day off when booking a
monthly recurrent series at the end of a month. This was a regression introduced in 14.2.2.
monthly recurrent series at the end of a month. This was a regression introduced in 14.2.2.
CSCun81246
Cisco TMS will now always return a populated DayOfWeek list when an empty list is submitted.
CSCum99999
Resolved issue where an exception to a series would sometimes be saved as a single
meeting.
meeting.
CSCun81291
Resolved issue where Cisco TMS would overwrite the specified time zone for single instances
with telepresence booked as part of a meeting series in Microsoft Outlook or another client
using Cisco TMSBA.
with telepresence booked as part of a meeting series in Microsoft Outlook or another client
using Cisco TMSBA.
CSCug26332
Resolved the issue where Cisco TMSBA's recurrenceID value did not correctly follow DST
changes.
changes.
CSCud35946
Resolved a number of inconsistencies in how Cisco TMS interpreted and executed recurrence
patterns.
patterns.
CSCug37575
Editing a conference that included a system that no longer existed in Cisco TMS caused
Cisco TMSXE to re-attempt the booking every 30 seconds, leading to an influx of email
notifications.
Cisco TMSXE to re-attempt the booking every 30 seconds, leading to an influx of email
notifications.
To prevent this, remove the non-existent system from Cisco TMSXE using the configuration
tool.
tool.
CSCuh55290
Resolved the issue with modifying the start time of an occurrence of a meeting series using
Cisco TMSBA so that the occurrence started earlier than originally scheduled, where Cisco
TMS correctly updated the end date, but not the start date, of the meeting.
Cisco TMSBA so that the occurrence started earlier than originally scheduled, where Cisco
TMS correctly updated the end date, but not the start date, of the meeting.