Cisco Cisco TelePresence Management Suite (TMS) Version 15 Release Notes
New features
Cisco TelePresence Management Suite Release Notes Software Release Notes (14.6.2)
Page 18 of 89
n
Bridges can be replaced with any other bridge, but this is a best effort feature and should be used with
caution.
caution.
Conference Diagnostics
must be run after swapping a bridge.
n
On replacing a system, a warning is shown stating that future conferences may be affected and advising
that
that
Conference Diagnostics
should be run to check and fix any errors. This is particularly valuable for
identifying issues when swapping bridges.
n
The original system will now always be purged.
n
The GUI has been simplified and now includes a search feature.
Improvements to the web interface, text strings, and error messages
n
Added the field Protocol for Web Interface Link to Room systems.
n
Clicking the Help icon after selecting a system in
Systems > Navigator
will now bring up a help page for
that particular System Type. Previously the main Navigator help page would be displayed regardless of
which system was selected.
which system was selected.
n
You can now delete option keys from the
Administrative Tools > General Settings
page. This could
previously only be done directly in the database.
n
You can now search the
Audit Log
using both date and time constraints: the fields Start Date and End
Date have been replaced with Start Time and End Time.
n
System names in
Software Manager
have been updated to reflect current product group names.
n
Updated the Windows icon for the Cisco TMS application and for Cisco TMS Tools and the tool to enable
HTTPS.
HTTPS.
n
All input fields with a maximum value are now restricted to a maximum of 5 digits.
n
New fields in
Systems > Navigator
indicate which Unified CM or TelePresence Conductor a system is
managed by.
n
The hostname of the Cisco TMS server is now displayed in parentheses at the bottom right of the web
interface, next to the serial number. In a redundant deployment, the hostname of the active node will be
shown.
interface, next to the serial number. In a redundant deployment, the hostname of the active node will be
shown.
n
When selecting a TelePresence Conductor in
Systems > Navigator
, the tab
Managed Systems
has been
renamed to
Conference Bridges
to better reflect the functionality.
n
Several improvements have been made to
Systems > Navigator >
select a system
> Summary
,
including useful links to the Tickets section.
Phone book support for Unified CM-registered Cisco TelePresence System TC Series endpoints
It is now possible to set Cisco TMS phone books on endpoints running Cisco TelePresence System TC
series software version 7 or later that are registered to a Unified CM. The parameters of the phone book
server (the Cisco TMS server) must be provisioned to the endpoint by the Unified CM.
series software version 7 or later that are registered to a Unified CM. The parameters of the phone book
server (the Cisco TMS server) must be provisioned to the endpoint by the Unified CM.
Improvements to migration of endpoints from Cisco VCS- to Unified CM-provisioned
For administrators migrating their call control infrastructure from Cisco VCS to Unified CM, Cisco TMS now
understands that a system being added from a Unified CM was already managed by Cisco TMS.
understands that a system being added from a Unified CM was already managed by Cisco TMS.
If a system that is direct-managed by Cisco TMS is registered to a Unified CM and then imported to Cisco
TMS using
TMS using
Add Systems > From List > Unified CM
, Cisco TMS now recognizes that the two systems are
in fact the same, and replaces the original system with the Unified CM-registered one, so all CDR and future
conference data is retained.
conference data is retained.
Conference Diagnostics
must be run after migrating an endpoint.