31 Mar
2011
31 Mar
'11
11:42 a.m.
I would say:
http://www.kamailio.org/docs/modules/3.1.x/modules/tm.html#t_branch_timeout
would be more appropriate for detection local timeouts.
If a reply is generated locally (from the script) I don't think that
will end up in the failure route (I have not tested this scenario).
And even if it ends up in a failure route, a flag can be set to identify it.
Regards,
Ovidiu Sas
On Thu, Mar 31, 2011 at 11:28 AM, Klaus Darilion
<klaus.mailinglists(a)pernau.at> wrote:
maybe you can use t_any_timeout? I do not know if it
handles internal and
external timeout identical
http://www.kamailio.org/docs/modules/3.1.x/modules/tm#t_any_timeout
On 31.03.2011 16:58, Andreas Granig wrote:
Hi,
On 03/31/2011 03:38 PM, Juha Heinanen wrote:
_______________________________________________
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
Ricardo Martinez writes:
Until 1.5.x, there has been a t_local_replied() in tm for checking
whether the reply (e.g. the 408) has been generated locally. What
happened to that one? How would you do this in 3.x reliably without
depending on an 1xx response from the outside?
Andreas
_______________________________________________
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
This 408 response code is generated in the failure_route only?.... what
if
a gateway really answers a call with 408 because there was no answer
from
the client... this response is handled by the on_reply route , isn't?
before you call t_relay you set no-answer timeout to be a small value (a
few seconds) so that you are able to try the next gw as soon as
possible. if your gw is alive, it will give you immediately a 1xx
response, which you process in on_reply route. if you get 408 without
having seen 1xx, you can defunct the gw in failure route.