Cisco Cisco TelePresence Management Suite (TMS) Version 15 Release Notes
Resolved issues
Cisco TelePresence Management Suite 13.2.1 Software Release Notes
Page 3 of 11
Systems management
Identifier
Bug Description
CSCua67538
Resolved the issue where editing the
Systems > Navigator > Edit Settings >
Management
Address field for systems registered to a Cisco Unified Communications Manager resulted in
Cisco TMS losing connection with the system.
It is no longer possible to edit the Name field under
Cisco TMS losing connection with the system.
It is no longer possible to edit the Name field under
Edit Settings
here – this must be done from
the Cisco Unified Communications Manager.
CSCtz83514
Resolved the issue where it was not possible to add Cisco TelePresence MX300, Profile 55 and
SX20 systems which were registered to a Cisco Unified CM to Cisco TMS.
When attempting to add the systems from
SX20 systems which were registered to a Cisco Unified CM to Cisco TMS.
When attempting to add the systems from
Systems > Navigator >
Add Systems
> From List >
CUCM
>
the system types above registered to the Cisco Unified CM are not displayed in the list.
CSCtz59012
Resolved the issue in
Systems > Navigator
where Cisco TMS inserted the system name in the
Settings > View Settings > Call Settings >
H323 ID field when H323 was disabled on the
system.
CSCua52598
Resolved the issue where it was not possible to initiate an outgoing call at a bandwidth of 2048
kbps from
kbps from
Systems > Navigator >
select a system running TC software
> Call Status
.
CSCua60353
Added Cisco TelePresence Server to the list of available MCUs to choose from in
Administrative
Tools > Configuration > Conference Settings > Advanced Conference Options >
Preferred
MCU Type in Routing
CSCua52587
Resolved the issue where enforcing management settings on a Cisco VCS in Cisco TMS changed
the external manager address set on the Cisco VCS from the FQDN of the Cisco TMS to the IP
address of the Cisco TMS. This could cause the HTTPS connection from the Cisco VCS to the
Cisco TMS to fail.
the external manager address set on the Cisco VCS from the FQDN of the Cisco TMS to the IP
address of the Cisco TMS. This could cause the HTTPS connection from the Cisco VCS to the
Cisco TMS to fail.
CSCua65305
Resolved the issue where VCS tickets contained an invalid link to the VCS Warnings page. VCS
tickets now contain a valid link to the Alarms page on the Cisco VCS.
tickets now contain a valid link to the Alarms page on the Cisco VCS.
CSCua52567
Cisco TMS now downloads software and release keys for Cisco TMSPE- and Cisco TMS Agent
Legacy-provisioned systems.
Legacy-provisioned systems.
CSCtz68686
Introduced a timeout increase option in the database for system upgrade software file upload.
CSCtz00863
Resolved the issue where Cisco TMS did not apply all persistent settings set here:
Systems >
Navigator >
select any system
> Settings > Persistent Settings,
after clicking Save.
CSCty90987
Resolved the issue where tickets generated from Cisco VCS alarms and/or warnings were not
clearing correctly in Cisco TMS once the issue had been fixed and acknowledged on the Cisco
VCS.
clearing correctly in Cisco TMS once the issue had been fixed and acknowledged on the Cisco
VCS.
CSCty90934
Resolved the issue where an incorrect software package was chosen when upgrading Cisco
TelePresence Provisioning Legacy-provisioned Cisco SX20 endpoints.
This occurred when upgrading from
TelePresence Provisioning Legacy-provisioned Cisco SX20 endpoints.
This occurred when upgrading from
Systems > System Upgrade > System Upgrade >
select
Systems managed by the TMS agent and select a system
>
select Upgrade Mode: Basic
>
Click Next. The
Select Software and Release Keys
page showed the incorrect software upgrade
package.
Phone books
Identifier
Bug Description
CSCtw52223
Resolved the issue where a call could fail when dialing an IP address entry from a Cisco TMS