Cisco Cisco TelePresence Management Suite (TMS) Version 15 Installation Guide
n
Cascading to additional MCUs when the number of participants exceeds the capacity of the first MCU is
not supported.
To support such scenarios, set up Cisco TelePresence Conductor as the preferred MCU in Cisco TMS.
not supported.
To support such scenarios, set up Cisco TelePresence Conductor as the preferred MCU in Cisco TMS.
n
When a service user is performing all bookings, the booking permissions are the same for all users.
Individual permissions and restrictions are ignored.
Individual permissions and restrictions are ignored.
n
Meetings in the past cannot be changed or deleted, and you cannot move a meeting from the past to the
future.
future.
n
If sufficient system licenses are not available at the time of editing an existing booking, the booking will be
deleted.
deleted.
Modifying ongoing meetings
Updating a single meeting that is currently ongoing is possible, but will not always be successful.
When modifying any meeting:
n
if the meeting is using an MCU that does not support WebEx, WebEx may not be added, as the meeting
would have to be disconnected and re-routed for this to work.
would have to be disconnected and re-routed for this to work.
n
extending the meeting will fail if it creates a booking conflict for any of the participants.
When modifying single meetings, including meetings in a series:
n
editing the start time will not work and Cisco TMS will throw an exception.
n
any other aspects of the meeting can be modified, but if the number of participants exceeds the available
capacity of the MCU or TelePresence Server, Cisco TMS will throw an exception and the participants will
not be added.
capacity of the MCU or TelePresence Server, Cisco TMS will throw an exception and the participants will
not be added.
When deleting a recurrent series while a meeting in the series is ongoing, the ongoing meeting will end.
When modifying a recurrent series while a meeting in the series is ongoing, the ongoing occurrence is turned
into a single meeting, separate from the series, and:
into a single meeting, separate from the series, and:
n
any occurrences of the modified series that are in conflict with the ongoing meeting, will not be created.
n
any past occurrences in the series will not be modified.
n
pending occurrences are assigned new conference IDs.
User access to Smart Scheduler
Users with the necessary credentials can reach Smart Scheduler immediately on:
http://<Cisco TMS server address>/tmsagent/tmsportal/#scheduler
Users who already use Cisco TMS can also click the portal icon in the upper right corner to go to Smart
Scheduler and FindMe:
Scheduler and FindMe:
Access rights and permissions
For the user to be able to access the Smart Scheduler, the permission must be set for the user .
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide (1.2)
Page 46 of 88
Deploying Smart Scheduler