Cisco Cisco TelePresence Management Suite (TMS) Version 15 Maintenance Manual
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:
conference event log. This log can be found in two places in Cisco TMS:
n
when viewing or editing an already booked conference, on the
Event Log
tab in the lower half of the
screen.
n
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.
two locations, but CCC includes additional options for running diagnostics and opening the list as text.
Reading the log
The log includes a timestamp, the user that made the change, and detail if there are changes to:
n
start and end time
n
conference type
n
recurrence pattern
n
WebEx included in the conference of not
n
picture mode
n
participants. Adding or removing a recording alias will be logged as (recording) participant added or
removed
removed
For the user field, note that any changed performed through Cisco TMSBA will be logged as originating from
the service user.
the service user.
The user nt authority\network service indicates automatic actions taken or initiated by Cisco TMS, such
as:
as:
n
dial attempts from the main participant
n
automatic messages sent to participants
n
automatic extensions to the meeting
During the conference, the following will also be logged:
n
participants connecting and disconnecting, including ad hoc participants
n
actions performed through Conference Control Center, including muting of participants and messages sent
to participants
to participants
For changes not mentioned above, the log will generally state "Conference updated".
Changes made to an entire series will be added to the log of each instance.
Conference registration and diagnostics
The message "Conference registered" will be logged 15 minutes prior to the scheduled start time, when the
conference is handed over from schedulerservice to liveservice (see
conference is handed over from schedulerservice to liveservice (see
for more detail
on these).
At the same time, or at booking time if the start time is less than 15 minutes and more than one minute ahead
in time, Cisco TMS runs diagnostics on the conference. The diagnostics service checks all systems for
in time, Cisco TMS runs diagnostics on the conference. The diagnostics service checks all systems for
Cisco TelePresence Management Suite Administrator Guide (14.4)
Page 198 of 331
Monitoring
Conference Control Center