Back to TMS, you god fearing bastards! Telepresence Management suite.
Very closely related to VCS in most cases. For all intents and purposes I will base this post on a recent post I did on VCS and refer to it here in there, in terms of integration with TMS
What is it?
TMS is basically a portal where users can schedule meetings and administrators can control meetings, endpoints and other media devices. It will allow users to schedule/book meetings with automatic dial out to the participating endpoints, it will allow scheduling of reoccurring meetings etc etc. It will also allow administrators, to monitor meetings, report on them and push out phone books to end points as well as check alerts. Figure 1 shows the initial portal when opening/logging into the TMS GUI.
|Figure 1 - TMS portal (administrator view)|
TMS runs on WIN2k8 (32 or 64 bit, or 64 bit only on R2) or on 2k3 (32 bit only). It uses SQL as its DB and uses IIS for its front end. Please note that TMS can also point to an external SQL instance as its DB.
How to integrate TMS with VCS
TMS predominately uses SNMP for automatic device discovery. During installation of TMS, it will then add the discovered device in folders. After discovery, the TMS server will show the endpoints, gateways, gatekeepers and MCU's (Fig.3).
On the VCS:
- Ensure SIP is turned on
- Ensure the SIP domain is specified
- Enable SNMP on the VCS (System Configuration>SNMP). This is the best way for TMS to detect and add the VCS
- Configure an external Manager (System Configuration>External Manager>Address). See figure 2
|Figure 3- TMS endpoints|
In Figure 3, the MCU called "Conference" is actually a TANDBERG Codian MCU 5320.