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 17 of 89
maximum value is 16. In previous releases of Cisco TMS, the number of auto-extends was hard-coded to 16.
Lowering this value gives administrators a way to restrict the amount of time spent on a video call.
Allow early join
Introduced the ability to enable participants to join a conference 5 minutes before the conference start time:
n
When set to Yes,
Administrative Tools > Configuration > Conference Settings >
Allow Participants
to Join 5 Minutes Early ensures that Cisco TMS allocates the conference 5 minutes before the
conference start time on the Main Participant.
conference start time on the Main Participant.
n
This duration is non-configurable and the setting is global.
n
Conference Control Center
reports that the conference started 5 minutes early in the event log, and
shows the conference as active from the Early Join start time. Conference Statistics reports will still track
the original start time, while Call Detail Records (CDRs) track the actual connection times.
the original start time, while Call Detail Records (CDRs) track the actual connection times.
n
This is a best effort feature, so if the Main Participant does not have the resources available, some or all
participants may be unable to join the conference within the 5 minute window.
participants may be unable to join the conference within the 5 minute window.
n
This feature extends the early join option to Cisco TMSBA clients, which did not support the
Setup/Teardown buffer that this feature has replaced.
Setup/Teardown buffer that this feature has replaced.
n
Note that Cisco TMS does not dial out to WebEx until the scheduled start time of the conference.
Installer improvements
Significant improvements to the Cisco TMS installer including:
n
The Complete/Custom choice has been removed to simplify the installation. The installer contains all
necessary dialogs in one install path. This means you can no longer change the database location during an
upgrade; if required this must be done using TMS Tools before upgrading.
necessary dialogs in one install path. This means you can no longer change the database location during an
upgrade; if required this must be done using TMS Tools before upgrading.
n
SQL Server is no longer installed as part of the Cisco TMS install.
n
The SQL Server backup dialog has been removed.
n
Customers upgrading from a version earlier than 14.2 will get a warning advising them to upgrade to 14.3.2,
run the Time Zone Migration Tool, then upgrade to 14.4.
run the Time Zone Migration Tool, then upgrade to 14.4.
Improved support for Unified CM clustering
n
A new
Clustering
tab has been added to
Systems > Navigator
for Unified CM systems. The following
cluster information is displayed for all Unified CMs:
l
A list of the cluster members.
l
Which is the primary node.
l
A View Details link to navigate to the other cluster nodes in
Systems > Navigator
.
n
Of the nodes in a cluster, Cisco TMS identifies the Publisher as the primary node, unless it is unavailable in
which case it picks a Subscriber. This is the only node that Cisco TMS communicates with to scan and
update Unified CM-imported systems.
which case it picks a Subscriber. This is the only node that Cisco TMS communicates with to scan and
update Unified CM-imported systems.
n
Unified CM versions 9.x and 10.x are supported (8.x is not).
Replace System GUI and functionality improvements
n
Systems registered to a Unified CM can now be replaced in the same way as systems registered to a
Cisco VCS.
Cisco VCS.
n
All endpoints can now be replaced with any other endpoint regardless of which call control system they are
registered to.
registered to.