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 30 of 65
Identifier
Description
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.
Resolved in 14.3.2
The following issues were found in previous releases and were resolved in 14.3.2:
Booking
Identifier
Description
CSCul42930
Resolved the issue where a dial-in endpoint joined a conference using the IP bandwidth set for
the conference despite having a lower bandwidth set for the endpoint when booking the
conference.
the conference despite having a lower bandwidth set for the endpoint when booking the
conference.
CSCul33187
Resolved the issue where it was not possible to schedule a conference of Type: No Connect with
systems that were behind a firewall.
systems that were behind a firewall.
CSCul35748
Resolved the issue where Cisco TMS repeatedly added the same participants to a conference.
This occurred with SIP dial-out participants that did not contain a domain suffix. This occurred
most frequently for conferences hosted on a TelePresence Conductor deployed in Cisco VCS
B2BUA mode.
This occurred with SIP dial-out participants that did not contain a domain suffix. This occurred
most frequently for conferences hosted on a TelePresence Conductor deployed in Cisco VCS
B2BUA mode.
CSCuh32674 Resolved the issue where it was not possible to create conferences with ISDN dial-in and dial-out
participants when scheduling with TelePresence Conductor.
CSCuf21982
Resolved the issue where a dial-out participant template was changed to a dial-in participant
when added to a One Button to Push conference.
when added to a One Button to Push conference.
CSCuj60215
Resolved the issue where booking a recurrent conference on a date where DST changed at
midnight in the logged in user's time-zone generated an error.
midnight in the logged in user's time-zone generated an error.
CSCuj47583
Resolved the issue where it was not possible to add audio participants with country code +382 for
Montenegro to a conference. The error: 382 is not a valid country code was displayed.
Montenegro to a conference. The error: 382 is not a valid country code was displayed.