Cisco Cisco TelePresence Management Suite (TMS) Version 15 Maintenance Manual
Viewing System Tickets
The System Tickets area in the left-hand panel contains tickets from relevant systems. A detailed list and display
options are available from the drop-down icon on the System Tickets header.
options are available from the drop-down icon on the System Tickets header.
Controlling Sound Alerts
Click Sound Alerts to configure alerts for errors and other events in active and/or opened conferences.
Sound alert settings are stored per user.
Conference Event Log
To see an audit trail of changes to a booking, or connection issues in an ongoing conference, look at the conference
event log. This log can be found in two places in Cisco TMS:
event log. This log can be found in two places in Cisco TMS:
■
when viewing or editing an already booked conference, on the Event Log tab in the lower half of the screen.
■
on the Event Log tab for each conference in Conference Control Center (CCC).
The log lists all changes to the conference since it was booked. The contents of the logs are identical in the two
locations, but CCC includes additional options for running diagnostics and opening the list as text.
locations, but CCC includes additional options for running diagnostics and opening the list as text.
Reading the Log
In CCC you will always read the event log on an instance basis. In List Conferences, to view the event log for the
series you need to edit the series rather than the instance. Note that an instance's Event Log always contains both
the series' events and the instance's events.
series you need to edit the series rather than the instance. Note that an instance's Event Log always contains both
the series' events and the instance's events.
The Event Log identifies whether changes were made to conferences series or single instances by using the prefixes:
'Conference' or 'Instance' in log entries.
'Conference' or 'Instance' in log entries.
The log includes a timestamp, the user that made the change, and details of any changes to:
■
start and end time
■
conference type
■
recurrence pattern
■
WebEx included in the conference of not
■
picture mode
■
participants. Adding or removing a recording alias will be logged as (recording) participant added or removed
For the user field, note that any changed performed through Cisco TMSBA will be logged as originating from the
service user.
service user.
The user nt authority\network service indicates automatic actions taken or initiated by Cisco TMS, such as:
■
dial attempts from the main participant
■
automatic messages sent to participants
■
automatic extensions to the meeting
During the conference, the following will also be logged:
■
participants connecting and disconnecting, including ad hoc participants
■
actions performed through Conference Control Center, including muting of participants and messages sent to
participants
participants
For changes not mentioned above, the log will generally state "Conference updated".
All changes to ongoing conferences will be logged on an instance level.
196
Cisco TelePresence Management Suite Administrator Guide
Monitoring