Cisco Cisco TelePresence Management Suite (TMS) Version 15 Installation Guide
n
Exceptions to recurrent meeting series are not supported in Smart Scheduler. Any modification will be
applied to all instances.
applied to all instances.
n
Smart Scheduler will rename call-in participants added from Cisco TMS.
Booking limitations
Booking through Cisco TelePresence Management Suite Extension Booking API has the following
limitations:
limitations:
n
The use of setup and teardown buffers in Cisco TMS is not supported.
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 default MCU in Cisco TMS.
not supported.
To support such scenarios, set up Cisco TelePresence Conductor as the default 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
You cannot move a meeting from the past to the future. This includes changing the start time of a meeting
that is already ongoing.
that is already ongoing.
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 modifying a recurrent series while an occurrence is ongoing:
n
changing the start time will be applied to the entire series, and the ongoing meeting will be disrupted.
Meetings set to connect automatically will be reconnected.
Meetings set to connect automatically will be reconnected.
n
any other modifications will be applied to upcoming instances only, and the ongoing meeting will be marked
as an exception in Cisco TMS.
as an exception in Cisco TMS.
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:
Cisco TMSPE Provisioning Deployment Guide
Page 43 of 78
Deploying Smart Scheduler