Cisco Cisco TelePresence Management Suite (TMS) Version 15 Release Notes
Resolved issues
Cisco TelePresence Management Suite Release Notes Software Release Notes (14.6.1)
Page 59 of 90
Identifier
Description
CSCun81228
Resolved the issue with booking a monthly recurrent meeting with the pattern: Occurs on the
___ DOW of every ____ month(s), using Cisco TMSXE, where Cisco TMS and the Microsoft
Exchange server were in different time zones. The instances would be booked on the wrong
days.
___ DOW of every ____ month(s), using Cisco TMSXE, where Cisco TMS and the Microsoft
Exchange server were in different time zones. The instances would be booked on the wrong
days.
CSCun26518
Resolved the issue where creating a recurrent conference with pattern 'Occurs on [the last day]
of every month' selected an incorrect date for February if Microsoft Exchange and Outlook
were in a different time zone to the Cisco TMS server.
of every month' selected an incorrect date for February if Microsoft Exchange and Outlook
were in a different time zone to the Cisco TMS server.
CSCun81296
Resolved issue where the email generated when editing an instance of a recurrent series
using Cisco TMSBA suggested the entire series had been edited, and incorrect conference ID
information was returned by Cisco TMS.
using Cisco TMSBA suggested the entire series had been edited, and incorrect conference ID
information was returned by Cisco TMS.
CSCun83458
Resolved the issue where conferences that were scheduled using FrequencyType Default
were incorrectly auto extended. This affected bookings through Cisco TMSXE, if users
scheduled a single telepresence meeting that was part of a non-telepresence series in
Exchange.
were incorrectly auto extended. This affected bookings through Cisco TMSXE, if users
scheduled a single telepresence meeting that was part of a non-telepresence series in
Exchange.
General
Identifier
Description
CSCun25480
Resolved the issue where it was not possible to save an email template that used the
deprecated MOVI2_URL tag.
deprecated MOVI2_URL tag.
CSCtx98924
Resolved the issue where if two or more endpoints in a conference had system names that
exceeded 31 characters and the first 31 characters were identical, Cisco TelePresence MCU
could dial out to one, but not the others, as Cisco TMS crops the system name to conform to
MCU API requirements. The endpoints then appeared as duplicates to the MCU, which only
dialed the first participant.
exceeded 31 characters and the first 31 characters were identical, Cisco TelePresence MCU
could dial out to one, but not the others, as Cisco TMS crops the system name to conform to
MCU API requirements. The endpoints then appeared as duplicates to the MCU, which only
dialed the first participant.
CSCun28058
Resolved the issue where the Ticket Log was not purged according to the Number of Days To
Keep Data set in
Keep Data set in
Administrative Tools > TMS Server Maintenance > Purge Old Data in
Database Tables Plan
.
CSCun27778
Resolved the issue where deadlocks on the query to get ticket counts could cause an
exception when loading the Cisco TMS front page.
exception when loading the Cisco TMS front page.
CSCun27836
Resolved some display issues that occurred when banners were applied to Cisco TMS.
CSCun27847
Resolved a number of layout issues with Internet Explorer 10 when compatibility mode was
turned off.
turned off.
CSCum65583
Resolved the issue where conference start could be delayed during failover in a redundant
deployment.
deployment.
CSCun70364
Resolved the issue where the date picker did not open and generated JavaScript errors when
using Internet Explorer 10 in standards mode.
using Internet Explorer 10 in standards mode.