Cisco Cisco TelePresence Management Suite (TMS) Version 15 Developer's Guide
Cisco TMS entities
System
A system entity in Cisco TMS is any item that can be booked. Note that systems provisioned using Cisco
TelePresence Management Suite Provisioning Extension cannot be booked and are therefore not considered
systems in this context.
TelePresence Management Suite Provisioning Extension cannot be booked and are therefore not considered
systems in this context.
There are two types of system entities:
n
systems that are controlled by Cisco TMS (and thus receive phonebooks, generate CDRs and so on)
n
systems added to Cisco TMS as "Room" and "Equipment".
Other types of entries, such as phonebook entries or provision directory users, are not system entities in
Cisco TMS.
Cisco TMS.
Each system entity has its own TMS System Id, which is used to uniquely identify the system in the Cisco
TMS database, tied to system settings such as SIP URIs, gatekeeper addresses, and software versions. A
subset of this system data is available in Cisco TMSBA through the GetSystemById function.
TMS database, tied to system settings such as SIP URIs, gatekeeper addresses, and software versions. A
subset of this system data is available in Cisco TMSBA through the GetSystemById function.
Conference
Each booking in Cisco TMS is a conference entity in the tmsng database. The conference has a unique
conference ID, that is tied to all conference attributes, such as the start time, end time, title, and participants
in the database.
conference ID, that is tied to all conference attributes, such as the start time, end time, title, and participants
in the database.
User
The Cisco TMS user entity holds information about Cisco TMS users, such as their first name, last name,
username, and email address. All users have a unique user ID.
username, and email address. All users have a unique user ID.
Cisco TelePresence Management Suite Extension Booking API Programming Reference Guide (14.4)
Page 10 of 74
API overview