<div><div class="gmail_quote">On Fri, Aug 27, 2010 at 8:33 AM, Wesley Volcov <span dir="ltr"><<a href="mailto:wesleyvolcov@gmail.com">wesleyvolcov@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Follow my tests:<br>The INVITE was sent by opensiups to route at 09:03:42<br>The 100 TRY came from route to opensips at 09:03:42<br>The 183 came from route to opensips at 09:03:43<br>But, at 09:03:47 the was sent to Failure Route by Opensips.<br>
<br>The call is going to Failure Route 5 seconds after 100 TRY and not after 183/180.</blockquote><div><br></div><div>Wesley,</div><div>I had a similar situation as you. Basically I needed a PDD timeout to roll over to another carrier. The timer here is a timer to a final reply. In other words to an answer or reject. So what you need to do is in the onreply route check for a 18X type reply and if you get it, then reset the timer to the ring timeout, else the timer will still be at 5 seconds. The logic should be something like:<br>
Attempt call out to carrier</div><div>If 5 seconds without a 180/183, goto failure route</div><div>if 180/183 receieved onreply, then set timer to 120 seconds</div><div><br></div><div>Good Luck!</div><div>-Brett</div><div>
</div></div></div>