Module: kamailio Branch: master Commit: 496f538e2ce8be9ed852a7bf8b1fe118b8971998 URL: https://github.com/kamailio/kamailio/commit/496f538e2ce8be9ed852a7bf8b1fe118...
Author: Kamailio Dev kamailio.dev@kamailio.org Committer: Kamailio Dev kamailio.dev@kamailio.org Date: 2017-08-21T16:46:27+02:00
modules: readme files regenerated - siptrace ... [skip ci]
---
Modified: src/modules/siptrace/README
---
Diff: https://github.com/kamailio/kamailio/commit/496f538e2ce8be9ed852a7bf8b1fe118... Patch: https://github.com/kamailio/kamailio/commit/496f538e2ce8be9ed852a7bf8b1fe118...
---
diff --git a/src/modules/siptrace/README b/src/modules/siptrace/README index edc71eb73c..383250d6f7 100644 --- a/src/modules/siptrace/README +++ b/src/modules/siptrace/README @@ -151,7 +151,7 @@ Chapter 1. Admin Guide SIP messages in a database and/or duplicate to the capturing server (using HEP, the Homer encapsulation protocol, or plain SIP mode)
- There are two ways of storing information: + There are multiple ways of storing information: * by calling the sip_trace() method explicitely in the Kamailio configuration file. In this case the original message is processed. * by setting the flag equal with the value of “trace_flag” (e.g., @@ -159,6 +159,7 @@ Chapter 1. Admin Guide message sent forward is processed. The logging mechanism is based on TM/SL callbacks, so only messages processed with the TM module or sent statelessly are logged. + * by setting “trace_mode” to mirror all traffic.
The tracing can be turned on/off using Kamailio RPC commands.