On 04.09.18 15:46, Juha Heinanen wrote:
> Daniel-Constantin Mierla writes:
>
>> The event_route was defined for the specific case where its name can be
>> anything and it is a matter of modules to execute some as they need.
>>
>> The interpreter which is defined in core has no clue about what
Daniel-Constantin Mierla writes:
> The event_route was defined for the specific case where its name can be
> anything and it is a matter of modules to execute some as they need.
>
> The interpreter which is defined in core has no clue about what names
> can be there. The modules cannot complain
On 04.09.18 13:23, Juha Heinanen wrote:
> Juha Heinanen writes:
>
>> I loaded tcpops module but still nothing to syslog from:
>>
>> event_route [tcp:close]
> I had typo in above: should be closed instead of close.
>
> This again shows that it would be nice if it would be checked that each
>
Juha Heinanen writes:
> I loaded tcpops module but still nothing to syslog from:
>
> event_route [tcp:close]
I had typo in above: should be closed instead of close.
This again shows that it would be nice if it would be checked that each
event_route has a home.
-- Juha
I loaded tcpops module but still nothing to syslog from:
event_route [tcp:close]
Debug (below) now shows this:
Sep 4 14:07:52 char /usr/bin/sip-proxy[6487]: DEBUG: tcpops [tcpops.c:233]:
tcpops_handle_tcp_closed(): received TCP closed event
Sep 4 14:07:52 char /usr/bin/sip-proxy[6487]:
I had not loaded tcpops module. Should work after that. How about
checking that all event routes in config have corresponding modules
loaded?
-- Juha
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
Daniel-Constantin Mierla writes:
> Can you test with latest master and debug=3, then send all debug
> messages from tcp connect to disconnect?
Below is the debug. First REGISTER comes at 13:13:26 and un-REGISTER at
13:13:29 followed by tcp connection close.
-- Juha
Sep 4 13:13:26 char
On 04.09.18 11:41, Juha Heinanen wrote:
> Daniel-Constantin Mierla writes:
>
>> Can you list the tcp connections via rpc and see if the one you expect
>> to be closed is still listed there?
> core.tcp_list after quiting baresip shows that the tcp connection has been
> removed, i.e., is not
Daniel-Constantin Mierla writes:
> Can you list the tcp connections via rpc and see if the one you expect
> to be closed is still listed there?
core.tcp_list after quiting baresip shows that the tcp connection has been
removed, i.e., is not anymore in the list
-- Juha
Can you list the tcp connections via rpc and see if the one you expect
to be closed is still listed there?
I haven't added the feature and not used it so far, but it might be the
cleanup timer routing for tcp connections that trigger the event route.
Cheers,
Daniel
On 04.09.18 11:07, Juha
Based on comment:
https://github.com/kamailio/kamailio/issues/171#issuecomment-418175840
I gave event_route [tcp:closed] a try:
event_route [tcp:closed] { # Handle TCP connection close
xlog("L_INFO", "$proto connection closed ($conid)\n");
}
Nothing comes to syslog when I quit my
11 matches
Mail list logo
