8 Jan
2013
8 Jan
'13
4:46 a.m.
Peter Dunkley writes:
One requirement of an outbound capable registrar is
that if a flow fails
(edge proxy returns a 430) the registrar should realise that the flow is
now dead and remove that contact binding from its database so it is not
used again as well as trying the next contact. I can't see anything that
will do this? Is this missing?
peter,
i didn't find in rfc5626 a requirement that registrar should remove 430
flow contact, but, if there is such a requirement, in my opinion removal
should be done from failure route in the script by a function that
removes the contact.
a similar thing was discussed a while back (see below).
-- juha
From: Juha Heinanen <jh(a)tutpro.com>
Sender: sr-dev-bounces(a)lists.sip-router.org
To: sr-dev(a)lists.sip-router.org
Subject: [sr-dev] git:master: usrloc(k): keep time of the last keepalive for
natted UDP contacts
Date: Thu, 13 Sep 2012 17:08:51 +0300
Klaus wrote:
Why only UDP? Are TCP contacts removed when the TCP connections is closed?
IMO there should also be a mechanism to remove ALL expired unresponsive
contacts.
how about the following for tcp contacts:
- set_forward_no_connect();
- if t_relay() fails because tcp connection does not exist,
unregister the AoR/contact
what would be needed is a find out that t_relay() failed due to
non-existing connection and a script function to do un-registration of
an AoR/contact.
perhaps both of these two things already exist?
-- juha