SIPTRACE module
Admin Guide
Section titled “Admin Guide”Overview
Section titled “Overview”Offer a possibility to store incoming/outgoing SIP messages in database.
There are two ways of storing information.
- by calling explicitely the sip_trace() method in OpenSIPS 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.
opensipsctl fifo sip_trace on
opensipsctl fifo sip_trace off
### Dependencies
#### OpenSIPS Modules
The following modules must be loaded before this module:
- *database module* - mysql, postrgress,dbtext, unixodbc...- *tm and sl modules* - optional, only ifyou want to trace messages forwarded by these modules.
#### External Libraries or Applications
The following libraries or applications must be installed before runningOpenSIPS with this module loaded:
- *None*.
### Exported Parameters
#### db_url (str)
Database URL.
*Default value is "".*
```opensips title="Set db_url parameter"...modparam("siptrace", "db_url", "mysql://user:passwd@host/dbname")...trace_flag (integer)
Section titled “trace_flag (integer)”Which flag is used to mark messages to trace
Default value is “0”.
...modparam("siptrace", "trace_flag", 22)...trace_on (integer)
Section titled “trace_on (integer)”Parameter to enable/disable trace (on(1)/off(0))
Default value is “0”.
...modparam("siptrace", "trace_on", 1)...enable_ack_trace (integer)
Section titled “enable_ack_trace (integer)”Parameter to enable/disable tracing of statelessly received ACKs (on(1)/off(0))
Default value is “0”.
...modparam("siptrace", "enable_ack_trace", 1)...traced_user_avp (str)
Section titled “traced_user_avp (str)”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).
...modparam("siptrace", "traced_user_avp", "$avp(123)")modparam("siptrace", "traced_user_avp", "$avp(user)")...trace_table_avp (str)
Section titled “trace_table_avp (str)”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).
...modparam("siptrace", "trace_table_avp", "$avp(345)")modparam("siptrace", "trace_table_avp", "$avp(siptrace_table)")...duplicate_uri (str)
Section titled “duplicate_uri (str)”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”.
...modparam("siptrace", "duplicate_uri", "sip:10.1.1.1:5888")...trace_local_ip (str)
Section titled “trace_local_ip (str)”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”.
...modparam("siptrace", "trace_local_ip", "10.1.1.1:5064")...table (str)
Section titled “table (str)”Name of the table where to store the SIP messages.
Default value is “sip_trace”.
...modparam("siptrace", "table", "strace")...Exported Functions
Section titled “Exported Functions”sip_trace()
Section titled “sip_trace()”Store current processed SIP message in database. It is stored in the form prior applying chages made to it.
This function can be used from REQUEST_ROUTE, FAILURE_ROUTE, ONREPLY_ROUTE, BRANCH_ROUTE.
...sip_trace();...trace_dialog()
Section titled “trace_dialog()”The function triggers the tracing of all messages belonging to a dialog. The function must be called for the initial request (that starts the dialog) and it will automatically take care of tracing evertyhing related to that dialog.
When using this function, you do not have to explicity set any tracing flag or to explicitly call anothe trace function.
This function can be used from REQUEST_ROUTE.
...if(is_method("INVITE") && !has_totag()) trace_dialog();...Exported MI Functions
Section titled “Exported MI Functions”sip_trace
Section titled “sip_trace”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_Database setup
Section titled “Database setup”Before running OpenSIPS 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 opensips/scripts folder as template. You can also find the complete database documentation on the project webpage, http://www.opensips.org/html/docs/db/db-schema-devel.html.
Known Issues
Section titled “Known Issues”Stateless forwarded messages (forward()) are not logged if you set the flag, use sip_trace().
Contributors
Section titled “Contributors”By Commit Statistics
Section titled “By Commit Statistics”Top contributors by DevScore(1), authored commits(2) and lines added/removed(3)
| # | Name | DevScore | Commits | Lines++ | Lines— |
|---|---|---|---|---|---|
| 1. | Daniel-Constantin Mierla (@miconda) | 49 | 26 | 2247 | 223 |
| 2. | Bogdan-Andrei Iancu (@bogdan-iancu) | 44 | 34 | 479 | 288 |
| 3. | Henning Westerholt (@henningw) | 11 | 6 | 158 | 167 |
| 4. | Stefan Darius (@dariusstefan) | 10 | 5 | 375 | 55 |
| 5. | Razvan Crainea (@razvancrainea) | 6 | 4 | 22 | 26 |
| 6. | Vlad Paiu (@vladpaiu) | 5 | 3 | 93 | 32 |
| 7. | Andreas Heise | 4 | 1 | 90 | 102 |
| 8. | Sergio Gutierrez | 3 | 1 | 63 | 44 |
| 9. | Dan Pascu (@danpascu) | 3 | 1 | 4 | 4 |
| 10. | Konstantin Bokarius | 3 | 1 | 2 | 5 |
All remaining contributors: Iouri Kharon, Edson Gellert Schubert, Elena-Ramona Modroiu.
(1) DevScore = author_commits + author_lines_added / (project_lines_added / project_commits) + author_lines_deleted / (project_lines_deleted / project_commits)
(2) including any documentation-related commits, excluding merge commits
(3) ignoring whitespace edits, renamed files and auto-generated files
By Commit Activity
Section titled “By Commit Activity”| # | Name | Commit Activity |
|---|---|---|
| 1. | Stefan Darius (@dariusstefan) | Jun 2026 - Jul 2026 |
| 2. | Razvan Crainea (@razvancrainea) | Jun 2011 - Jun 2026 |
| 3. | Vlad Paiu (@vladpaiu) | Jun 2011 - Aug 2011 |
| 4. | Bogdan-Andrei Iancu (@bogdan-iancu) | Jul 2006 - Apr 2011 |
| 5. | Sergio Gutierrez | Sep 2009 - Sep 2009 |
| 6. | Dan Pascu (@danpascu) | Nov 2008 - Nov 2008 |
| 7. | Daniel-Constantin Mierla (@miconda) | Apr 2006 - May 2008 |
| 8. | Iouri Kharon | Apr 2008 - Apr 2008 |
| 9. | Konstantin Bokarius | Mar 2008 - Mar 2008 |
| 10. | Edson Gellert Schubert | Feb 2008 - Feb 2008 |
All remaining contributors: Henning Westerholt (@henningw), Andreas Heise, Elena-Ramona Modroiu.
(1) including any documentation-related commits, excluding merge commits
Documentation
Section titled “Documentation”Contributors
Section titled “Contributors”Last edited by: Razvan Crainea (@razvancrainea), Bogdan-Andrei Iancu (@bogdan-iancu), Daniel-Constantin Mierla (@miconda), Konstantin Bokarius, Edson Gellert Schubert, Henning Westerholt (@henningw), Elena-Ramona Modroiu.
License
Section titled “License”All documentation files (i.e. .md extension) are licensed under the Creative Common License 4.0