1 Sep
2016
1 Sep
'16
6:57 p.m.
Thanks, but the problem, that there are situations when the socket seems not to be closed
but the communication with the client cannot be possible. E.g. if the client is in
airplane mode, Kamailio does not detect tcp lost, in the location table, the user exists
with real connection_id, but I cannot call him or
write a message.
I would be interested in if it is possible to detect such situations on Kamailio side when
for example a message cannot be delivered because of such network conditions like airplane
mode?
Peter
-----Original Message-----
From: sr-users [mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of Camille Oudot
Sent: Monday, August 29, 2016 6:13 PM
To: sr-users(a)lists.sip-router.org
Subject: Re: [SR-Users] detect failed socket
Is it possible to check the socket towards the
receiver user at the
moment when the message arrives at Kamailio? I think if I would check
that if the socket is not fine, I could send the message to the msilo
directly and the client would not have wait for timeout to resend.
Hi,
one solution would be to use the handle_lost_tcp parameter from usrloc so that the record
will be removed from it if the connection is closed:
http://kamailio.org/docs/modules/stable/modules/usrloc.html#usrloc.p.handle…
--
Camille
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users