Xlog("LOG_LOCAL6","L_INFO", "SIP Request: method from to \n") Xlog("L_INFO", "SIP Request: method from to \n") An specifier for printing has the same format and meaning as pseudo-variable ( ) Ĭomplete documentation of this module and its facilities can be found in module's “README” file located in sip_router/modules/xlog directory. The module exports two functions that allow to use specifiers which will be replaced with an appropriate value when printing the message. To print formatted log messages from Kamailio (OpenSER) configuration script, one can use “xlog” module. If no log level is specified, the messages are issued at log level 4 (L_DBG). It does not support specifiers, the message will be printed as it is. In addition to the log messages issued by Kamailio (OpenSER) internally, the administrators can configure Kamailio (OpenSER) to write more log messages using the “log” method explicitly in configuration file. Kamailio (OpenSER) core exports a method to log plain text messages while a module (xlog) allow writing more complex log messages based on specifiers. Usually the situation is described by one or two sentences and some processing data is logged as well when available. The format of the logs is loose, depending on the type of event being reported. Typically, Kamailio (OpenSER) is configured to issue a message to the syslog on errors or extraordinary situations of which the system administrator should be notified. This eases the troubleshooting and monitoring of the system. d - enable debugging mode (multiple -d increase the debug level, e.g., -ddddd)Īdmins can write log messages from configuration file. Core options are located at the beginning of the configuration file, before loading modules and any routing block.
Logging in Kamailio (OpenSER) can be configured using the following options. Logging Configuration Options Configuration File This level should be used to write messages for debugging. This level should be used to write informational messages This level should be used to report unusual situations.
This level should be used to write warning messages. This level should be used to report errors during data processing which do not cause system malfunctioning. This level should be used if the error is a critical situation. This level should be used if the error requires immediate action. further parameters, in case the “string” parameter includes printing specifiers. It may contain specifiers in the format of “printf()” C function. O level - the level where to print the messages. See the section “Log Levels” for more about the log levels.
It allows printing messages to different log levels. The Kamailio (OpenSER) API offers two functions for printing debug and log messages that can be used when write extensions for Kamailio. Later in this document, this feature will be presented in more details. You need to to configure your “syslog” daemon and set the “log_facility” Kamailio (OpenSER) configuration option to the appropriate value. Kamailio (OpenSER) can be configured to report the log messages to a custom syslog facility. The messages are printed only if their log level exceeds the threshold set with the “debug” parameter in the configuration file or specified by the command line parameter “-d”. By default, Kamailio (OpenSER) prints log messages to “syslog”. The switching between the two options can be done via command line parameters or configuration file. Kamailio (OpenSER) was designed to log debug and error messages either to “syslog” facility or to standard error display “stderr”. The logging methods are renamed from e.g. Please note: this tutorial is partly obsolete, logging backend in the server core
OPENSER XLOG HOW TO
Tutorial about how to print debug and syslog messages with Kamailio (OpenSER) SIP Server. Kamailio (OpenSER) - Debug and syslog messages Authors of initial tutorial:
0 kommentar(er)
