Filter
Top Products
TANDBERG Border Controller User Manual
9 Logging
The Border Controller provides logging for troubleshooting and auditing purposes.
The event log may be viewed from the command line by using the eventlog command, specifying
the number of lines to display. Alter na tively the web page System Status → Event Log may be
used.
9.1 Controlling what is logged
You can control the verbosity with which the Border Controller logs information. All events have
an associated level in the range [1-3]. Level 1 refers to high level events such as registration
requests and call attempts. Level 2 events are recorded for incoming and outgoing message
- H.323, LDAP etc excluding noisy messages such as H.460.18 keep-alives and H.245 video
fast-updates. . Level 3 events include some of these noisy events. By default, logging is set to
level 1.
9.2 Event log format
The event log is displayed in an extension of the UNIX syslog format:
date time host name facility name <PID>: message details
date and time represent the local time at which the message was logged. host name is the name
of the system generating the log message, facility — the name of the program generating the log
message — will be tandberg for all messages originating from TANDBERG pr ocesses, but will
differ for messages from third party processes which are used in the Border Controller product.
For all messages logged from the tandberg process the message details field is structured to
allow easy parsing. It consists of a number of human-readable name=value pairs, separated by
a space. The first two fields are always:
Field Example Description
Time Time=2006/20/01-14:02:17 The UTC date and time at which the event was
generated.
Event Event=RegistrationRequest The event which caused the log message to
be generated.
and the last field of the message is always the event level:
Field Example Description
Level Level=1 The level of the event being logged.
34