Cisco Cisco TelePresence Management Suite (TMS) Version 15 Maintenance Manual
Field
Description
System con-
nectivity
nectivity
Define the system's location on the network:
■
Inaccessible: The system cannot connect to Cisco TMS or vice versa. No attempts to
communicate will be made, but the system may be booked for future conferences. The setting is
intended for use in case of temporary system downtime for maintenance and similar situations.
communicate will be made, but the system may be booked for future conferences. The setting is
intended for use in case of temporary system downtime for maintenance and similar situations.
■
Reachable on LAN: The system is located on the same LAN as Cisco TMS and will
communicate using the IP address or FQDN configured in
communicate using the IP address or FQDN configured in
Advanced Network Settings for
Systems on Internal LAN
■
Reachable on Public Internet: The system is located outside the LAN, but is reachable on a
public network address and uses the TMS Server Address (FQDN or IPv4 Address) to
communicate with Cisco TMS, see
public network address and uses the TMS Server Address (FQDN or IPv4 Address) to
communicate with Cisco TMS, see
Allow Book-
ings
ings
Allows the system to be added to conferences.
Selecting
No will stop the system from being booked in the future but will not affect existing con-
ferences.
Table 51 Connection parameters for system communication on the Connection tab (continued)
Permissions
The Permissions tab controls permissions for the use and administration of a specific system for Cisco TMS user groups.
The permission levels that can be set are the same as can be set on folders. For details, see
The permission levels that can be set are the same as can be set on folders. For details, see
and
.
Logs
Log
Description
History
All detected changes that have been made to the system in Cisco TMS.
.
Audit Log Changes to attributes for this system. For more information, see
Table 52 The Logs contains all available logs for the system
Content Servers and Recording Servers
In Cisco TMS:
Systems > Navigator
a content server or recording server is selected
For information about the configuration options and maintenance of Cisco TelePresence Content Server, see
Content Server in Gateway Mode
If a Content Server is configured in Gateway mode, Cisco TMS will create a unique alias for each scheduled recording,
instead of using the number for the recording alias that has been selected.
instead of using the number for the recording alias that has been selected.
This individual generated alias is a longer random number unique to the conference, and has the same settings as the
selected recording alias. The reason Cisco TMS does this is so that if the Content Server drops out of the conference tem-
porarily, or the conference disconnects, the conference will continue recording to the original file when reconnected,
instead of creating a new recording file.
selected recording alias. The reason Cisco TMS does this is so that if the Content Server drops out of the conference tem-
porarily, or the conference disconnects, the conference will continue recording to the original file when reconnected,
instead of creating a new recording file.
95
Cisco TelePresence Management Suite Administrator Guide
Adding and Managing Systems