Cisco Cisco TelePresence Management Suite (TMS) Version 15 Developer's Guide
Limitations
WebEx booking limitations
WebEx booking does not support all recurrence patterns and options supported by Cisco TMS:
n
Exceptions from a recurrence pattern (moving or updating one or more meetings) are not supported.
n
Some advanced recurrence patterns are not supported.
When WebEx is not supported for a particular booking, the booking will fall back to telepresence only.
WebEx-only meetings not supported
WebEx-only meetings should not be booked using Cisco TMSBA. If using Cisco TMS to create a conference
that includes WebEx without including any telepresence participants, telepresence resources will still be
taken up, as an MCU will connect to the conference. The API will book the conference, but return a warning
when such conferences are created.
that includes WebEx without including any telepresence participants, telepresence resources will still be
taken up, as an MCU will connect to the conference. The API will book the conference, but return a warning
when such conferences are created.
Also note that WebEx bookings do not support time zone rules.
Other 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.
Modifying ongoing meetings
Updating a single meeting that is currently ongoing is possible, but will not always be successful.
For example:
n
changing the start time may disrupt the 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.
If modifying a recurrent series while an instance is ongoing:
n
changing the start time will be applied to the entire series, and the ongoing meeting may be disrupted.
n
making any other modifications will be applied to upcoming instances only, and the ongoing meeting will be
marked as an exception in Cisco TMS.
marked as an exception in Cisco TMS.
Unused values
The following values are present in the API, but not in use:
Cisco TMSBA Programming Reference Guide
Page 21 of 68
Using the APIs for remote setup and booking