[sr-dev] CONID and tcp:close event on outbound TCP connections

[Olle E. Johansson]

> On 07 Jul 2016, at 10:58, Camille Oudot <camille.oudot at orange.com> wrote:
> 
>>> Trying to debug a case where I don’t get an event_route execution
>>> for a TCP connection.
>> 
>> The lack of answers seems to point to me having to put on a diving
>> suit and go deep into the TCP connection debugging mode.
>> 
>> …or?
> 
> Hi Olle,
> 
> While I don't have a specific answer to your question, here are a few
> pointers to some meaningful information (maybe you've seen it already):
> 
> - this message by the original author explains the intended behavior
>  and how it was implemented:
>  https://github.com/kamailio/kamailio/pull/454#issuecomment-168128187
> 
> - the event route can be triggered from two points in the code:
>  https://github.com/kamailio/kamailio/blob/master/tcp_read.c#L296
>  https://github.com/kamailio/kamailio/blob/master/tcp_read.c#L306
> 
> Hope this helps.
THank you!

That puts me on track. I don’t believe this TCP connection has a conid,
and I need to figure out why. Does outbound TCP connections from Kamailio
to any other server get that data structure at all? 

When do we assign connection ID’s to a specific
tcp/tls/sctp/websocket connection?

/O