Cisco Cisco TelePresence Management Suite (TMS) Version 15 Developer's Guide
Entities in Cisco TMS
Cisco TMS Extension Booking API Programming Reference Guide (13.0.1)
Page 6 of 33
Entities in Cisco TMS
System entity
A Cisco TMS System Entity is an entity used to describe an item that can be booked. In the Cisco TMS
user interface, Cisco TMS system entities are seen as systems and rooms (e.g. the entities viewable in
the System Navigator). Neither phone book entries nor web conference servers are systems.
user interface, Cisco TMS system entities are seen as systems and rooms (e.g. the entities viewable in
the System Navigator). Neither phone book entries nor web conference servers are systems.
In Cisco TMS each systems has a unique identifier or ID. This ID is visible in the user interface as of Cisco
TMS 9.5. Cisco TMS allows a single system to be located in multiple folders, however the underlying
system entity (and ID) will be equal for all instances of the system in Cisco TMS.
TMS 9.5. Cisco TMS allows a single system to be located in multiple folders, however the underlying
system entity (and ID) will be equal for all instances of the system in Cisco TMS.
The table in the database that contains systems is the objSystem table. It is not recommended to update
this table manually; however reading information does not cause issues.
this table manually; however reading information does not cause issues.
Conference entity
A Cisco TMS Conference Entity is an entity that describes a reservation in Cisco TMS (Conferences in
Cisco TMS are also known as Bookings). All conferences in Cisco TMS must make at least one
reservation of a Cisco TMS System Entity. For example, it is not possible to create a conference that
contains only phone book entries. Cisco TMS will at the time the conference is saved add the required
MCU reservations (the Cisco TMS System Entity) to allow the call to complete.
Cisco TMS are also known as Bookings). All conferences in Cisco TMS must make at least one
reservation of a Cisco TMS System Entity. For example, it is not possible to create a conference that
contains only phone book entries. Cisco TMS will at the time the conference is saved add the required
MCU reservations (the Cisco TMS System Entity) to allow the call to complete.
One limitation is when reserving web conference resources. Due to Web Conference resources not being
Cisco TMS System Entities, it is not possible to only reserve a web conference; you will also need to
include at least one Cisco TMS system entity reservation.
Cisco TMS System Entities, it is not possible to only reserve a web conference; you will also need to
include at least one Cisco TMS system entity reservation.
A conference is stored in the database in the ScheduledCall table. Each conference has a unique
identifier (ID). The Cisco TMS System Entity reservation, dial-in slots, phone book entries etc. are stored
in the ScheduledParticipant table. This table is coupled to the ScheduledCall table with the foreign key the
ScheduledCall.Id from ScheduledParticipant.ScheduledCallId.
identifier (ID). The Cisco TMS System Entity reservation, dial-in slots, phone book entries etc. are stored
in the ScheduledParticipant table. This table is coupled to the ScheduledCall table with the foreign key the
ScheduledCall.Id from ScheduledParticipant.ScheduledCallId.
A conference ID can be seen in the Cisco TMS user interface under
Booking -> List Conferences -> Id
column
.
User entity
The Cisco TMS User Entity holds information about Cisco TMS users such as name, time zone, and e-
mail.
mail.