Table of Contents
db_url (str)
table (str)
trace_flag (integer)
trace_on (integer)
traced_user_avp (str)
trace_table_avp (str)
duplicate_uri (str)
trace_to_database (integer)
trace_local_ip (str)
trace_sl_acks (integer)
xheaders_write (integer)
xheaders_read (integer)
hep_mode_on (integer)
List of Examples
db_url parametersip_trace parametertrace_flag parametertrace_on parametertraced_user_avp parametertrace_table_avp parameterduplicate_uri parametertrace_to_database parametertrace_local_ip parametertrace_sl_acks parameterxheaders_write parameterxheaders_read parameterhep_mode_on parametersip_trace() usageTable of Contents
db_url (str)
table (str)
trace_flag (integer)
trace_on (integer)
traced_user_avp (str)
trace_table_avp (str)
duplicate_uri (str)
trace_to_database (integer)
trace_local_ip (str)
trace_sl_acks (integer)
xheaders_write (integer)
xheaders_read (integer)
hep_mode_on (integer)
Offer a possibility to store incoming/outgoing SIP messages in database and/or duplicate to the capturing server (homer encapsulation protocol or plain sip mode)
There are two ways of storing information.
by calling explicitely the sip_trace() method in Kamailio configuration file. In this case the original message is processed.
by setting the flag equal with the value of 'trace_flag' (e.g., setflag(__trace_flag__)) parameter of the module. In this case, the\ message sent forward is processed. The logging mechanism is based on TM/SL callbacks, so only messages processed with TM/SL are logged.
The tracing can be turned on/off using fifo commad.
kamctl fifo sip_trace on
kamctl fifo sip_trace off
The following modules must be loaded before this module:
database module - mysql, postrgress, dbtext, unixodbc...
tm and sl modules - optional, only if you want to trace messages forwarded by these modules.
Database URL.
Default value is "".
Example 1.1. Set db_url parameter
...
modparam("siptrace", "db_url", "mysql://user:passwd@host/dbname")
...
Name of the table where to store the SIP messages.
Default value is "sip_trace".
Which flag is used to mark messages to trace
Default value is "0".
Parameter to enable/disable trace (on(1)/off(0))
Default value is "0".
The name of the AVP storing the SIP URI of the traced user. If the AVP is set, messages are stored in database table and 'traced_user' column is filled with AVP's value. You can store the message many times for many users by having multiple values for this AVP.
Default value is "NULL" (feature disabled).
Example 1.5. Set traced_user_avp parameter
...
modparam("siptrace", "traced_user_avp", "$avp(i:123)")
modparam("siptrace", "traced_user_avp", "$avp(s:user)")
...
The name of the AVP storing the name of the table where to store the SIP messages. If it is not set, the value of 'table' parameter is used. In this way one can select dynamically where to store the traced messages. The table must exists, and must have the same structure as 'sip_trace' table.
Default value is "NULL" (feature disabled).
Example 1.6. Set trace_table_avp parameter
...
modparam("siptrace", "trace_table_avp", "$avp(i:345)")
modparam("siptrace", "trace_table_avp", "$avp(s:siptrace_table)")
...
The address in form of SIP uri where to send a duplicate of traced message. It uses UDP all the time.
Default value is "NULL".
Example 1.7. Set duplicate_uri parameter
...
modparam("siptrace", "duplicate_uri", "sip:10.1.1.1:5888")
...
Parameter to enable/disable inserts to the Database from this Kamailio.
In case we only want to send the SIP-Messages to the duplicate_uri and not store the information to the local database we can set this to "0".
Default value is "1".
The address to be used in fromip field for local generated messages. If not set, the module sets it to the address of the socket that will be used to send the message.
Default value is "NULL".
Example 1.9. Set trace_local_ip parameter
...
modparam("siptrace", "trace_local_ip", "10.1.1.1:5064")
...
Parameter to enable/disable tracing of SL-filtered ACKs (on=1 / off=0).
By default all ACKs to replies generated by SL module are traced. There is no way to select among them. Now SL module is able to run an event route when such ACK arrives (event_route[sl:filtered-ack]). You can set this parameter to 0 and then execute sip_trace() in the event route, accompanied by config rules to decide which ACK to trace.
Default value is "1".
Parameter to enable/disable writing of x-headers.
Stores fromip, toip, method and direction in X-Siptrace-* headers. This allows to transmit them to a second kamailio server using the duplicate_uri feature. Because the headers are added after the data is written to the database, the headers only show up in the packets sent by duplicate_uri.
See xheaders_read, it should be used on the receiving
side.
Note: The headers are first read, then written. This allows to relay
the information over more then two kamailio servers by setting both
xheaders_write and xheaders_read
to "1" on the servers in the middle.
Default value is "0".
Parameter to enable/disable reading of x-headers.
Reads and removes the X-Siptrace-* headers. Packets not containing the
headers are neither stored to the database nor relayed (duplicate_uri).
See xheaders_write for further information.
Default value is "0".
Name: sip_trace
Parameters:
trace_mode : turns on/off SIP message tracing. Possible values are:
on
off
The parameter is optional - if missing, the command will return the status of the SIP message tracing (as string “on” or “off” ) without changing anything.
MI FIFO Command Format:
:sip_trace:_reply_fifo_file_ trace_mode _empty_line_
Before running Kamailio with siptrace, you have to setup the database tables where the module will store the data. For that, if the table were not created by the installation script or you choose to install everything by yourself you can use the siptrace-create.sql SQL script in the database directories in the kamailio/scripts folder as template. You can also find the complete database documentation on the project webpage, http://www.kamailio.org/docs/db-tables/kamailio-db-devel.html.