Cisco Cisco TelePresence Management Suite (TMS) Version 15 Release Notes
New features
Cisco TelePresence Management Suite Release Notes Software Release Notes (14.4)
Page 2 of 72
New features
New in 14.4
New redundancy model
Cisco TMS has moved to an active/passive failover redundancy model. Previously two nodes load-balanced
the network traffic and requests, now only one node is active at any one time. If the connection to that node
from the load balancer fails, or one of the services on the active node fails, the other node will activate and
take over.
the network traffic and requests, now only one node is active at any one time. If the connection to that node
from the load balancer fails, or one of the services on the active node fails, the other node will activate and
take over.
This feature is enabled in
General Settings > Enable TMS Redundancy
. Once enabled, redundancy
settings are visible in
Administrative Tools > TMS Server Maintenance
.
.
In conjunction with this new redundancy model, a new group permission has been added. In
Administrative
Tools > User Administration > Groups >
Set permissions for a group, the
Administrative Tools
>
Configuration setting now has an Update option as well as a Read option. The
Administrative Tools >
TMS Server Maintenance > TMS Redundancy >
Force Manual Failover button is disabled unless the
logged in user is a member of a group with Update selected.
Conference recurrence improvements
Extensive improvements to the Cisco TMS recurrence model including:
n
Cisco TMS now checks availability for only the current instance of a series when checking to see whether
the meeting can be extended. Previously Cisco TMS would check the entire series, so if one of the
participants was unavailable for another instance, the extend meeting request would be rejected.
the meeting can be extended. Previously Cisco TMS would check the entire series, so if one of the
participants was unavailable for another instance, the extend meeting request would be rejected.
n
Recurrence information expanded in the booking confirmation email.
n
A series that only contains exceptions is now supported. Cisco TMS retains information about the original
conference series, when all instances are edited to become exceptions to the original recurrence pattern.
conference series, when all instances are edited to become exceptions to the original recurrence pattern.
n
Improved the level of detail displayed in the
Activity Log
and the Conference Log when changes are
made to instances in a recurrent series using the Cisco TMS web UI and Cisco TMSBA.
n
Cisco TMS now supports richer recurrence patterns.
n
Improved feedback to user when editing an instance that belongs to a series external to Cisco TMS.
Changes to the handling of past, ongoing and deleted meetings
Ongoing or past conferences are no longer affected if a recurrent series is edited.
Meetings in the past and ongoing meetings can no longer be deleted:
n
Attempting to delete a conference in the past will not work as conference data is retained for call detail
records.
records.
n
Deleting an ongoing meeting will end it immediately, modify the end time, and free up all scheduled
resources used in the meeting. The ended meeting will not be deleted.
resources used in the meeting. The ended meeting will not be deleted.
n
Ending an instance of a series before the scheduled time will similarly modify the end time, free up
resources, and mark the instance as an exception.
resources, and mark the instance as an exception.
n
Making changes to a series with an ongoing instance will now transform the instance into a single meeting.
Any instances of the modified series that conflict with the single meeting will not be created.
Any instances of the modified series that conflict with the single meeting will not be created.