[Contents]
[Prev]
[Next]
[Index]
[Report an Error]
Tracing Border Signaling Gateway Operations
You can trace the following BSG operations and record them in
a log file:
- signaling
- sip-stack
- framework
- datastore
- session-trace
- sbc-utils
You configure any of the following trace options for the components
in the preceding list:
-
debug—Logging of all code flow of control.
-
trace—Logging of program trace START and
EXIT macros.
-
info—Summary logs for normal operations,
such as the policy decisions made for a call.
-
warning—Failure recovery or failure of
an external entity.
-
error—Failure with a short-term effect,
such as failed processing of a single call .
The following options are available for the sip-tracing component:
-
event-tracing—Activate or deactivate the
stack's event tracing.
-
ips-tracing—Activate or deactivate the
stack's IPS tracing.
-
per-tracing—Activate or deactivate the
stack's performance tracing.
-
pd-log-level—Specifies which types of PD
logs are printed to the log file. This can be set to:
-
problem—Send only messages with errors
to the log file.
-
exception—Send only messages with errors
or warnings to the log file.
-
audit—Send all log messages are sent to
the log file.
This option determines the minimum level
of logs to be sent to the log file. For example, setting this option
to exception causes both exception and problem logs to be
sent to the log file. Setting it to audit causes all logs
are sent to the log file. The default value is audit.
-
pd-detail—Specifies the amount of detail
to be sent to the log file.
-
full—All available information is sent
to the log file.
-
summary—The type of logging, the identifier
and the first line of the log message are sent to the log file.
-
dev-logging—Configure development tracing
for the stack.
-
verbose-logging—Configure verbose tracing
for the stack.
All log files are placed in the /var/log directory.
When a trace file reaches its maximum size, a .0 is appended
to the file name, then a new file is created with a .1 appended,
and so on. When the maximum number of trace files is reached, the
oldest trace file is overwritten.
[Contents]
[Prev]
[Next]
[Index]
[Report an Error]
