Cisco Cisco TelePresence Management Suite (TMS) Version 15 Release Notes
Resolved issues in 14.0
Cisco TelePresence Management Suite 14.1.1 Software Release Notes
Page 16 of 21
Identifier
Bug Description
meeting series in which it was a participant was changed to a date in the past.
Monitoring
Identifier
Bug Description
CSCua60141
Resolved the issue where removing a participant from a scheduled One Button To Push
conference did not update that participant’s Meetings calendar to inform it that it had been
removed from the conference.
conference did not update that participant’s Meetings calendar to inform it that it had been
removed from the conference.
Systems Management
Identifier
Bug Description
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.
SX20 systems which were registered to a Cisco Unified CM to Cisco TMS.
CSCua52567
Cisco TMS now downloads software and release keys for provisioned systems.
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.
the external manager address set on the Cisco VCS from the FQDN of the Cisco TMS to the IP
address of the Cisco TMS.
CSCua65556
Resolved the issue where it was not possible to add systems to Cisco TMS if the default ISDN or
IP Zone value had been set to None in
IP Zone value had been set to None in
Administrative Tools > General Settings >
Default
ISDN/IP Zone after initially creating the default zones during the install process. A “System not
found!” error was invoked.
found!” error was invoked.
CSCua26092
Resolved the issue where changing the URL Where Software Packages Can Be Downloaded:
in
in
Administrative Tools > Configuration > Network Settings > General Network Settings
could cause a stack trace error when accessing the
Systems > System Upgrade > Software
Manager
page.
This happened if the IIS user Cisco TMS was running under did not have access to the folder
specified.
A valid error message will now appear.
specified.
A valid error message will now appear.
CSCua26087
Removed the field SNMP Get Community Name: from
Systems > Navigator >
Select a system
> Connection
tab for systems which do not support this setting, for example Cisco Unified CM
and Cisco TelePresence Server.
CSCua59944
Resolved the issue where no system name was displayed for systems which did not have a name.
This occurred in
This occurred in
Systems > Event Notification Manager >
edit an account in the Name column.
Select a system with No Name in the Select Systems column, and an event type in the Select
Event Types column, then click on the arrow to move it into the Stored Event Notifications
column and click Save. Now view the same account in
Event Types column, then click on the arrow to move it into the Stored Event Notifications
column and click Save. Now view the same account in
Systems > Event Notification Manager
.
Nothing is displayed in the System column for the system name.
CSCtr25908
Resolved the issue where endpoints running TC and TE software, and the Cisco VCS showed the
SNMP port as 0 instead of 161 in
SNMP port as 0 instead of 161 in
Systems > System Overview >
Select a system from the
Systems folder list and SNMP Settings from System Parameters list
>
click View
>
SNMP port
column.
This is a hard-coded value in Cisco TMS, it is not read from the system itself.
This is a hard-coded value in Cisco TMS, it is not read from the system itself.