Persistent Protocol Tracing
This section explains how to configure persistent protocol tracing to capture specific SIP protocol message logs and persistently send them off the Oracle Communications Session Border Controller, even after rebooting the system. This feature is not applicable to log for H.323 or IWF.
About Persistent Protocol Tracing
You can configure sending protocol message logs off of the Oracle Communications Session Border Controller, and have that persist after a reboot. You no longer have to manually issue the notify command each time you reboot.
To support persistent protocol tracing, you configure the following system-config parameters:
- call-trace—Enable/disable protocol message tracing (currently only sipmsg.log and alg.log) regardless of the process-log-level setting. If the process-log-level is set to trace or debug, call-trace will not disable.
- internal-trace—Enable/disable internal ACP message tracing for all processes, regardless of process-log-level setting. This applies to all *.log (internal ACP message exchange) files other than sipmsg.log and alg.log. If the process-log-level is set to trace or debug, call-trace will not disable.
- log-filter—Determine
what combination of protocol traces and logs are sent to the log server defined by
the process-log-ip parameter value. You can also fork the traces and logs, meaning
that you keep trace and log information in local storage as well as sending it to
the server. You can set this parameter to any of the following values: none, traces,
traces-fork, logs, logs, all, or all-fork.
The Oracle Communications Session Border Controller uses the value of this parameter in conjunction with the process-log-ip and process-log-port values to determine what information to send. If you have configured the proc-log-ip and proc-log-port parameters, choosing traces sends just the trace information (provided they are turned on), logs sends only process logs (log.*), and all sends everything (which is the default).
Note:
Set the log-filter to all-fork for the system to include TCP and TLS traces in logs.
About the Logs
When you configure persistent protocol tracing, you affect the following types of logs.
Note:
Enabling logs can have an impact on Oracle Communications Session Border Controller performance.Process Logs
Events are logged to a process log flow from tasks and are specific to a single process running on the Oracle Communications Session Border Controller. By default they are placed into individual files associated with each process with the following name format:
log.<taskname>
By setting the new log-filter parameter, you can have the logs sent to a remote log server (if configured). If you set log-filter to logs or all, the logs are sent to the log server. Otherwise, the logs are still captured at the level the process-log-level parameter is set to, but the results are stored on the Oracle Communications Session Border Controller’s local storage.