Hello,
that is via the mode param of the sip_trace() function -- is not
considering the trace_flag/setflag() option of marking the traffic for
tracing?
We can make the init log message debug and check if dialog api was
loaded if sip_trace() mode is 'd', printing error at that level.
Cheers,
Dani
Hello,
I think the way it is documented (with a dedicated mode for the dialog
tracing functionality) it should not be active if the dialog tracing
parameter is not used. I just quickly looked into the code, but it seems
to be the implemented like this.
Cheers,
Henning
Am 09.09.19 um 08:39 s
Hello,
I made that warning an info message (commit
ce19d9212feb0ff4b017b5eaa71e4637a71aa4b9), but I am considering to add a
param to be able to control if dialog tracking should be done. I didn't
have time to dig much into it, but I do not want tracking of dialog
automatically if dialog module is
Henning Westerholt writes:
> just to understand it correctly:
>
> - is the dialog module loaded and acc generates the warning nevertheless?
>
> - is the dialog module not loaded, but you don't use the dialog
> functionality of acc?
Dialog module is not loaded and I'm not tracing dialogs.
-- J
Hello Juha,
just to understand it correctly:
- is the dialog module loaded and acc generates the warning nevertheless?
- is the dialog module not loaded, but you don't use the dialog
functionality of acc?
Cheers,
Henning
Am 07.09.19 um 14:24 schrieb Juha Heinanen:
> On masterm, I noticed tha
On masterm, I noticed that I have started to get a warning from siptrace
mod_init() even when there is nothing to warn about:
Sep 7 15:21:45 salmon /usr/bin/sip-proxy[30966]: WARNING: siptrace
[siptrace.c:338]: mod_init(): can't load dlg api. Will not install dialog
callbacks.
-- Juha
___
