Ok, let me try this a different way because I think I may be spreading my confusion. :)<div><br></div><div>The behavior I'm looking for is:</div><div>INVITE goes to carrier.</div><div>100 Trying MUST come back in 2 seconds</div>
<div>THEN</div><div>18X MUST come back in 5 seconds else FAIL</div><div>THEN</div><div>Allow ringing for 200 seconds</div><div><br></div><div>from what you've described, it sounds like I can't have the 2 seconds and 5 seconds be different numbers (static tm module param fr_timer). But even now.. I have fr_timer set to 5 and it's perfectly happy waiting 20 seconds between 100 and 180. Why does it not time out there?</div>
<div><br></div><div>Thanks!</div><div>-Brett</div><div><br></div><div><br></div><div><br><div class="gmail_quote">On Thu, Jun 11, 2009 at 9:44 AM, Bogdan-Andrei Iancu <span dir="ltr"><<a href="mailto:bogdan@voice-system.ro">bogdan@voice-system.ro</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Brett,<br>
<br>
first of all you cannot reset the timers manually from script - the timers handling is automatically done by TM, totally transparent for the script.<br>
<br>
second, the restart_fr_on_each_reply controls the fr_inv_timer.<div class="im"><br>
<br>
Brett Nemeroff wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Ok, so at first I was thinking.. what I need to do is set the fr_inv_timer to something like 10 seconds. But then in the on_reply route, check for a 18X reset the fr_inv_timer to like 200 seconds to allow the call to ring.<br>
<br>
I'm pretty confused now.. I thought the fr_timer was the timer to get a provisional reply. so as soon as you get a 100 the timer isn't used anymore. This option suggests that if you set restart_fr_on_each_reply to 1, then after you get a 100 Trying, then it will allow for fr_timer seconds again before timing out. Is that right? This of course, leads me to my next question, the documentation says that by default it does this, but I'm certainly not seeing this behavior.<br>
</blockquote></div>
maybe the the 100 + 180 where too fast and close to INVITE, and no other reply before 200 OK, so "visibly" effect of a restart....<div class="im"><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
let me make sure I have this clear please:<br>
fr_timer = time from trigger (request) to ANY reply. The trigger point depends on the restart_fr_on_each_reply setting. If off, it's just from the request. If on, each provisional reply will cause the timer to be reinvoked, else it would have been ignored. In other words if fr_timer = 5 seconds and I get a 100 Trying after 500ms, and then the 183 Ringing occurs 8 seconds later, the only way the timer would be tripped is if I set reset_fr_on_each_reply=1?<br>
<br>
fr_inv_timer = the max amount of time between an initial request and a positive final reply (2XX)<br>
</blockquote>
<br></div>
as said , the restart_fr_on_each_reply controls the fr_inv_timer. NOTE that setting a new avp for fr_inv_timer in onreply_route (set the usage of AVPs in onreply_route) will update the value of the timer !! interesting ;).<div class="im">
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
How mixed up am I? And is restart_fr_timer_on_each_reply really default to 1?<br>
</blockquote></div>
yes :)<div class="im"><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
and if so, why does it not work how I expect? (ie: now, as long as I get the 100 Trying in 5 secs (fr_timer) the 18X could come 20 seconds later and everything is happy (but me).<br>
</blockquote></div>
not sure I get the scenario.....<br>
<br>
Regards,<br>
Bogdan<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Thanks!<br>
-Brett<div class="im"><br>
<br>
<br>
<br>
<br>
On Thu, Jun 11, 2009 at 3:14 AM, Bogdan-Andrei Iancu <<a href="mailto:bogdan@voice-system.ro" target="_blank">bogdan@voice-system.ro</a> <mailto:<a href="mailto:bogdan@voice-system.ro" target="_blank">bogdan@voice-system.ro</a>>> wrote:<br>
<br>
Hi Brett,<br>
<br>
The relevant timer are:<br>
- A - timeout at transport level, if no reply comes back<br>
- B - timeout at transaction level, if the transaction did not<br>
completed (no final response received)<br>
<br>
What may help you is the fact that the B timer may be reset after<br>
each provisional reply. see:<br>
<a href="http://www.opensips.org/html/docs/modules/1.5.x/tm.html#id271074" target="_blank">http://www.opensips.org/html/docs/modules/1.5.x/tm.html#id271074</a><br>
<br>
Regards,<br>
Bogdan<br>
<br>
Brett Nemeroff wrote:<br>
<br>
All,<br>
Is there a tm timer for pdd?<br>
What I want is to timeout between a 100 and a 18X reply.. so<br>
if I get a 100 and say more than 6000ms elapses without<br>
another provisional reply, proceed to failure route.<br>
<br>
I don't see a way to do this now without fr_inv_timer which<br>
effectively is the "ring timer" as far as I understand. which<br>
isn't quite right (timer from 1XX to >=200?)<br>
<br>
Thanks,<br>
Brett<br>
<br>
<br>
------------------------------------------------------------------------<br>
<br>
_______________________________________________<br>
Users mailing list<br></div>
<a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a> <mailto:<a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a>><div class="im"><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
<br>
<br>
<br>
</div></blockquote>
<br>
</blockquote></div><br></div>