[SR-Users] unregister user when kamailio looses TCP connection.

[Olle E. Johansson]

Let's work on a description on the logic needed and see if Vitally's code is close:

1. Connection dies (tcp, tls, sctp)
2. Event-route activates
3. Check if there's a outbound flow with reg-id associated with the flow
4. If not, is there a registration associated with the flow
5. If 3 or 4 is true, do something

Do we have functions for 3 and 4? Can this be done in scripting?

/O



27 aug 2013 kl. 09:18 skrev Peter Dunkley <peter.dunkley at crocodilertc.net>:

> I started to implement this.  It is in a branch somewhere, but I couldn't get it working.
> 
> If someone who knows the TCP code better could take a look...
> 
> Regards,
> 
> Peter
> 
> 
> On 26 August 2013 23:28, Olle E. Johansson <oej at edvina.net> wrote:
> 
> 27 aug 2013 kl. 08:27 skrev "Olle E. Johansson" <oej at edvina.net>:
> 
> >
> > 27 aug 2013 kl. 00:29 skrev Vitaliy Aleksandrov <vitalik.voip at gmail.com>:
> >
> >> Hello,
> >>
> >> I've made a patch to kamailio-4.0.3 which removes stale registration when kamailio looses an incoming tcp connection.
> >> Of course this patch needs more work.
> >>
> >> Since the are no direct references between user location contacts and tcp connections callback function uses linear search through the whole location table using received field as a key.
> >>
> >> Can anybody more experienced in kamailio internals check if I chose the right place to get information about lost tcp connections ?
> >> Another thing I wanted to ask is maybe somebody can suggest a better way to tie a tcp connection to the user location information without complicating "usrloc" module by any heavy data structures.
> >>
> >> If anybody else except me need this It would be great to fix known problems and add it to kamailio.
> >> <remove_tcp_contacts.patch>_______________________________________________
> >
> > This is something required for outbound too. We need to remove the registration and thus the flow if a connection dies. The problem is that we can manage the connection on another server (edge proxy) too.
> 
> ...which is why I earlier proposed an event-route for this use-case.
> 
> /O
> _______________________________________________
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users at lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
> 
> 
> 
> -- 
> Peter Dunkley
> Technical Director
> Crocodile RCS Ltd
> _______________________________________________
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users at lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20130827/0416226d/attachment.html>