Cisco Cisco TelePresence Management Suite (TMS) Version 15 Developer's Guide
Per system licensing
Once the per system option key has been activated in Cisco TMS, the Allow Remote Bookings setting
determines whether each system is using a license.
determines whether each system is using a license.
This setting is void and hidden if the Application Integration Package option is used. If both option keys are
added, only the Application Integration Package option will be used by Cisco TMS.
added, only the Application Integration Package option will be used by Cisco TMS.
The first time a system is booked through Cisco TelePresence Management Suite Extension Booking API,
Allow Remote Bookings will be toggled to Yes for that system in Cisco TMS, provided a license is
available. If no more licenses are available, Allow Remote Bookings will be left as No for that system, and
the requested booking will be denied. A Cisco TMS ticket will be generated to notify the administrator that no
more licenses are available.
Allow Remote Bookings will be toggled to Yes for that system in Cisco TMS, provided a license is
available. If no more licenses are available, Allow Remote Bookings will be left as No for that system, and
the requested booking will be denied. A Cisco TMS ticket will be generated to notify the administrator that no
more licenses are available.
Note that Cisco TMSXE performs a test bookings as each endpoint is added through the configuration tool,
thus also enabling Allow Remote Bookings.
thus also enabling Allow Remote Bookings.
To view and/or modify the setting:
1. In Cisco TMS, go to
Systems > Navigator
.
2. Select the system you want.
3. Click the
Settings
tab.
4. In the
TMS Scheduling Settings
pane, you will find Allow Remote Bookings.
If the setting is Yes, the system is currently using an Exchange Integration Option license.
5. To disable the setting:
a. Click Edit Settings.
b. Uncheck Allow Remote Bookings.
c. Click Save.
b. Uncheck Allow Remote Bookings.
c. Click Save.
Booking rights
Importing from Cisco TMS and booking meetings through the API requires authentication with Cisco TMS.
There are two possible models for user authentication.
Service user books on behalf of users
The simplest approach is configuring one service user in Cisco TMS for your client, and granting this user
Book on behalf of permissions as described below.
Book on behalf of permissions as described below.
This model is only appropriate if all users with access to the client can be granted the same permissions in
Cisco TMS, as booking on behalf of someone will create a new Cisco TMS user in the default group if the
user does not already exist.
Cisco TMS, as booking on behalf of someone will create a new Cisco TMS user in the default group if the
user does not already exist.
All users book for themselves
If you need to set up different booking rights per user, or block some users from booking altogether, each user
must authenticate with Cisco TMS individually through the API.
must authenticate with Cisco TMS individually through the API.
Cisco TelePresence Management Suite Extension Booking API Programming Reference Guide (14.4)
Page 15 of 74
Using the APIs for remote setup and booking