Cisco Cisco TelePresence Management Suite (TMS) Version 15 Release Notes
New features
Cisco TelePresence Management Suite Release Notes Software Release Notes (14.4)
Page 3 of 72
Pending instances will be assigned new conference IDs.
n
Improved handling of editing series where some instances are in the past. The recurrence pattern start date
is now correctly persisted.
is now correctly persisted.
Note that past instances of a series booked prior to upgrading to 14.4 will not be linked to the series in
Booking > List Conferences
. They will appear as single instance conferences.
If you still have the Delete button available in
Monitoring > Conference Control Center
, clear the Java
cache and the browser cache to remove it completely.
Recurrence changes on the New Conference page
The recurrence user interface has been redesigned:
n
Recurrence icon replaced with Add Recurrence... button in
Booking > New Conference
. The button text
changes to Edit Recurrence... once a recurrent series has been added to the conference.
n
Improved
Recurrence
pop up window, including new Remove Recurrence button.
n
New intuitive
Exceptions
pop up window including a calendar for editing and clear feedback for users.
n
It is now possible to edit all instances in a series while choosing not to edit any exceptions.
n
All exceptions in a series can be removed with one click using the new Reset Exceptions button.
n
Improved the validation of compatible recurrence patterns when WebEx is added to a conference series.
Conference Diagnostics
This new feature allows administrators to identify and fix problems with existing conferences, and is
particularly useful in the case of dial plan or infrastructure changes to your deployment, such as replacing a
bridge.
particularly useful in the case of dial plan or infrastructure changes to your deployment, such as replacing a
bridge.
When the diagnostics are run, Cisco TMS checks the following for all future scheduled conferences:
n
That all participants exist in the database.
n
That the route is valid: that all participants are still routable.
The Autocorrect feature attempts to fix selected conferences automatically, taking action such as rerouting
the conference, or removing invalid participants.
the conference, or removing invalid participants.
For further information see the Web Help for the
Conference Diagnostics
page in Cisco TMS.
Resource availability check on extension
Introduction of a new global setting:
Administrative Tools > Configuration > Conference Settings
>
Resource Availability Check on Extension.
This setting works in conjunction with Extend Conference Mode and applies to Automatic Best Effort or
Endpoint Prompt.
Endpoint Prompt.
The options are:
n
Best Effort: Conferences will only automatically extend beyond the scheduled end time on a best effort
basis if all resources are available for the next 15 minutes.
basis if all resources are available for the next 15 minutes.
n
Ignore: Cisco TMS will ignore the resource availability check, and conferences will automatically extend
beyond the scheduled end time regardless of whether all the resources are available or not. The only
exception to this is if the port used on the main participant clashes with another conference that takes place
during that extended time - in that case the conference will not be extended.
beyond the scheduled end time regardless of whether all the resources are available or not. The only
exception to this is if the port used on the main participant clashes with another conference that takes place
during that extended time - in that case the conference will not be extended.