Cisco Cisco TelePresence Management Suite (TMS) Version 15 Developer's Guide
Cisco TMS entities
System
A system entity 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.
Management Suite Provisioning Extension cannot be booked and are therefore not considered systems in
this context.
There are two types of system entities: systems that are controlled by Cisco TMS (and thus receive
phonebooks, generate CDRs and so on), and systems added to Cisco TMS as the "Room" and "Equipment"
types. Other types of entries, such as phonebook entries or provision directory users, are not system entities
in Cisco TMS.
phonebooks, generate CDRs and so on), and systems added to Cisco TMS as the "Room" and "Equipment"
types. Other types of entries, such as phonebook entries or provision directory users, are not system entities
in Cisco TMS.
Each system entity has its own TMS System Id, which is used to uniquely identify the system in Cisco
TMS. A subset of this system data is available in Cisco TMSBA through the GetSystemById function.
TMS. A subset of this system data is available in Cisco TMSBA through the GetSystemById function.
In the tmsng database, systems are stored in the objSystem table. System settings (such as SIP URIs,
gatekeeper addresses, and software versions) are stored in the field_SystemField table.
gatekeeper addresses, and software versions) are stored in the field_SystemField table.
Conference
A conference entity, or booking, is a reservation in Cisco TMS. Each conference has a unique conference ID.
Conference and their attributes (ID, start time, end time, title, and so on) are stored in the tmsng database in
the ScheduledCall table. Phonebook entries, systems, and external participants that are part of a
conference are stored in the ScheduledParticipant table. The Cisco TMSBA functions that interact with
conferences, such as GetConferenceById, get and set data to and from both tables..
the ScheduledCall table. Phonebook entries, systems, and external participants that are part of a
conference are stored in the ScheduledParticipant table. The Cisco TMSBA functions that interact with
conferences, such as GetConferenceById, get and set data to and from both tables..
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.
This information is stored in the AclUser table in the tmsng database
Cisco TMSBA Programming Reference Guide
Page 9 of 68
API overview