Cisco Cisco TelePresence Management Suite (TMS) Version 15 Developer's Guide
■
One Cisco TMSXE – Extension for Microsoft Exchange option key per 25 telepresence endpoints integrated
with Cisco TMS, usually recommended for smaller deployments. See below for detail on how system licenses
are activated.
with Cisco TMS, usually recommended for smaller deployments. See below for detail on how system licenses
are activated.
■
One Cisco TelePresence Management Suite Booking API license per 25 registered endpoints per 25
telepresence endpoints integrated with Cisco TMS, usually recommended for smaller deployments. See below
for detail on how system licenses are activated.
telepresence endpoints integrated with Cisco TMS, usually recommended for smaller deployments. See below
for detail on how system licenses are activated.
■
One Cisco TelePresence Management Suite Extension for IBM Lotus Notes option key per 25 telepresence
endpoints integrated with Cisco TMS, usually recommended for smaller deployments. See below for detail on
how system licenses are activated.
endpoints integrated with Cisco TMS, usually recommended for smaller deployments. See below for detail on
how system licenses are activated.
■
One Application Integration Package option key per Cisco TMSBA installation. This option is recommended for
deployments with a large number of endpoints.
deployments with a large number of endpoints.
Note:
If both license keys are present, Cisco TMS will only use the Application Integration Package key.
Enabling Option Keys
To enable an option key in Cisco TMS:
1.
Go to Administrative Tools > Configuration > General Settings.
2.
In the Licenses and Option Keys pane, click Add Option Key.
3.
Input the option key string.
4.
Click Save.
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.
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.
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.
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.
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.
Booking Rights
Importing from Cisco TMS and booking meetings through the API requires authentication with Cisco TMS.
9
Cisco TelePresence Management Suite Extension Booking API Programming Reference Guide