<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>Hi Alex, Daniel,<div><br></div><div>Crystal clear, thanks for your help! Time to dive into the config.</div><div><br></div><div>/Tobias<br><div><br><div>> Date: Thu, 9 Oct 2014 16:36:02 -0400<br>> From: abalashov@evaristesys.com<br>> To: sr-users@lists.sip-router.org<br>> Subject: Re: [SR-Users] Best way to handle 100 but no 180/183?<br>> <br>> Hello Tobias,<br>> <br>> fr_inv_timer won't do much for you, because it deals only with final <br>> replies (>= 200) to the INVITE transaction. 1xx replies are all <br>> provisional in nature.<br>> <br>> Thus, the nature of the problem is such that if you've received a 100 <br>> Trying, you've already dampened fr_timer, but the only other TM timer at <br>> your immediate disposal is fr_inv_timer, which is fired when a final <br>> reply, positive or negative, is not received within the specified time. <br>> That's the only built-in timing granularity that TM provides for the <br>> life cycle of an initial INVITE transaction.<br>> <br>> As you surmised and Daniel confirmed, your only solution is to "hack" <br>> around this by using a really low fr_inv_timer value. If you want, for <br>> example, your total PDD for any given vendor to not exceed 10s, then you <br>> can set fr_inv_timer to 10s. If you have received a non-100 1xx response <br>> (e.g. 18x) in the meantime, you can t_set_fr() the fr_inv_timeout to the <br>> more logical 120s or whatever.<br>> <br>> Note that fr_inv_timeout/t_set_fr() are per-branch. If you want to <br>> impose such lifetimes for the whole transaction, irrespectively of <br>> branch, you might also want to check out:<br>> <br>> http://kamailio.org/docs/modules/4.1.x/modules/tm.html#max_inv_lifetime<br>> <br>> http://kamailio.org/docs/modules/4.1.x/modules/tm.html#tm.f.t_set_max_lifetime<br>> <br>> -- Alex<br>> <br>> On 10/09/2014 03:29 PM, Tobias wrote:<br>> <br>> > Dear Kamailio users,<br>> ><br>> > I have an issue with some upstream carriers quickly replying with 100<br>> > Trying but then basically times out.<br>> ><br>> > I'm looking for a good solution to distinguish between the 100 reply and<br>> > any other replies, and alter the timeout values. My goal is to be able<br>> > to re-route calls where the 180/183 is not received within a few<br>> > seconds, and if the 180/183 is received I'd like to give the call a much<br>> > longer timeout.<br>> ><br>> > I realize there is a "fr_inv_timer" that would do this, but I would not<br>> > like to set that to low since I fear it would affect many other call<br>> > types, i.e. if a carrier would send 183 once but for some reason does<br>> > not resend on regular intervals.<br>> ><br>> > I'm on Kamailio 4.1 and my current settings are:<br>> > fr_timer : 2000<br>> > fr_inv_timer : 120000<br>> > restart_fr_on_each_reply : 1<br>> ><br>> > The only solution I can think of is to update the fr_inv_timer in an<br>> > on_reply-route if the reply code is 180/183 but I'm not sure that would<br>> > even work? Is that the way to go or is there another way?<br>> ><br>> > Thanks in advance!<br>> > /Tobias<br>> ><br>> ><br>> > _______________________________________________<br>> > SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list<br>> > sr-users@lists.sip-router.org<br>> > http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users<br>> ><br>> <br>> <br>> -- <br>> Alex Balashov - Principal<br>> Evariste Systems LLC<br>> Tel: +1-678-954-0670<br>> Web: http://www.evaristesys.com/, http://www.alexbalashov.com/<br>> <br>> Please be kind to the English language:<br>> <br>> http://www.entrepreneur.com/article/232906<br>> <br>> _______________________________________________<br>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list<br>> sr-users@lists.sip-router.org<br>> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users<br></div></div></div> </div></body>
</html>