7 Sep
2019
7 Sep
'19
3:24 p.m.
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
8 Sep
8 Sep
11:04 p.m.
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 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
_______________________________________________
Kamailio (SER) - Development Mailing List
sr-dev(a)lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev
--
Henning Westerholt - https://skalatan.de/blog/
Kamailio services - https://skalatan.de/services
9 Sep
9 Sep
9:07 a.m.
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.
-- Juha
9:39 a.m.
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 loaded -- if that's the case, it
should be a way to disable it. This is a new feature for 5.3, so it
should be tuned to match existing behavior.
Cheers,
Daniel
On 09.09.19 08:07, Juha Heinanen wrote:
Henning Westerholt writes:
--
Daniel-Constantin Mierla -- www.asipto.com
www.twitter.com/miconda -- www.linkedin.com/in/miconda
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.
-- Juha
_______________________________________________
Kamailio (SER) - Development Mailing List
sr-dev(a)lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev
10:43 a.m.
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 schrieb Daniel-Constantin Mierla:
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 loaded -- if that's the case, it
should be a way to disable it. This is a new feature for 5.3, so it
should be tuned to match existing behavior.
Cheers,
Daniel
On 09.09.19 08:07, Juha Heinanen wrote:
> 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.
>
> -- Juha
>
> _______________________________________________
> Kamailio (SER) - Development Mailing List
> sr-dev(a)lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev
--
Henning Westerholt - https://skalatan.de/blog/
Kamailio services - https://skalatan.de/services
11:01 a.m.
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,
Daniel
On 09.09.19 09:43, Henning Westerholt wrote:
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 schrieb Daniel-Constantin Mierla:
> 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 loaded -- if that's the case, it
> should be a way to disable it. This is a new feature for 5.3, so it
> should be tuned to match existing behavior.
>
> Cheers,
> Daniel
>
> On 09.09.19 08:07, Juha Heinanen wrote:
>> 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.
>>
>> -- Juha
>>
>> _______________________________________________
>> Kamailio (SER) - Development Mailing List
>> sr-dev(a)lists.kamailio.org
>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev
--
Daniel-Constantin Mierla -- www.asipto.com
www.twitter.com/miconda -- www.linkedin.com/in/miconda
1931
days inactive
1933
days old
5 comments
3 participants
participants (3)
-
Daniel-Constantin Mierla -
Henning Westerholt -
Juha Heinanen