Cisco Cisco TelePresence Management Suite (TMS) Version 15 Release Notes
Resolved issues
Cisco TelePresence Management Suite Release Notes Software Release Notes (14.4)
Page 46 of 72
Identifier
Description
CSCui09920
Resolved the issue where an MCU could fail to dial out to WebEx participants in a scheduled
meeting if the WebEx site was configured with a bandwidth of 1536 or 1280 kbps in Cisco TMS.
meeting if the WebEx site was configured with a bandwidth of 1536 or 1280 kbps in Cisco TMS.
CSCui29432
Resolved the issue where
Administrative Tools > Configuration > WebEx Settings >
select a
Center & Connect WebEx authentication site
> Edit > WebEx Site Configuration >
Connection
Status displayed the error: Could not connect to site. Scheduling using this site worked correctly
despite this error.
despite this error.
CSCuh43678 Resolved the issue with Cisco TMSBA-scheduled recurrent meetings with WebEx, where the first
occurrence would have started before the time that the conference was booked in Cisco TMS.
When viewing the
Connection Settings
tab for the conference, the Number column for the
participants "Cisco WebEx Meeting" and "Cisco WebEx TSP Audio" would display as To be
populated by WebEx, instead of the correct information.
populated by WebEx, instead of the correct information.
Database
Identifier
Description
CSCue08333 Resolved the issue where Cisco TMS incorrectly warned about database size as it approached
4Gb for SQL Server 2008 R2. This version supports databases of up to 10Gb.
CSCui85970
It is no longer possible to add the value -1 in
Administrative Tools > TMS Server Maintenance >
Purge Old Data in Database Tables Plan
and
Purge Log Plan
.
CSCui71982
Resolved the issue where upgrading the Cisco TMS database failed and the database upgrade
log contained this error: "Violation of PRIMARY KEY constraint 'PK_field_SystemFieldSettings'".
This only affected deployments that included pre-registered Polycom systems.
log contained this error: "Violation of PRIMARY KEY constraint 'PK_field_SystemFieldSettings'".
This only affected deployments that included pre-registered Polycom systems.
General
Identifier
Description
CSCuj25642
Resolved the issue where the Time Zone Update Tool did not update the first instance of a
recurrent conference series. All other occurrences were updated correctly.
recurrent conference series. All other occurrences were updated correctly.
CSCuc00547
Resolved the issue where users in a different but trusted Active Directory (AD) domain to the
domain that the Cisco TMS server is a member of were removed from the Cisco TMS local users
group on AD sync.
domain that the Cisco TMS server is a member of were removed from the Cisco TMS local users
group on AD sync.
CSCui04173
Resolved the issue where Cisco TMS was unable to authenticate to an HTTP proxy using NTLM
authentication when checking for software upgrades.
authentication when checking for software upgrades.
CSCuj25633
Resolved the issue where changing the protocol for a Participant Template that had Bandwidth
set to Conference Bandwidth resulted in a stack trace error.
set to Conference Bandwidth resulted in a stack trace error.
CSCui35048
CSCui74631
Resolved the issue where Cisco TMS did not import Active Directory (AD) groups recursively.
This applied to both user and phone book source imports.
This applied to both user and phone book source imports.
CSCuh08527
CSCug16589
Resolved the issue where an error was displayed when clicking on the Log Out icon in Cisco
TMS.
TMS.
CSCua81744
Resolved the issue where Cisco TMS did not send its FQDN in its HELO/EHLO message. The
value specified in
value specified in
Administrative Tools > Configuration > Network Settings >
TMS Server
Fully Qualified Hostnamewill now be used.