Henning,<br><br>Let me attach the full cfg for clarity.<br><br>The flags are as you said; how can I do revert_uri before failure route? you mean within failure_route[20] do a revert_uri first thing before any further processing?<br>
<br>Thanks,<br>Uriel<br><br><div class="gmail_quote">On Mon, Mar 30, 2009 at 2:44 PM, Henning Westerholt <span dir="ltr"><<a href="mailto:henning.westerholt@1und1.de">henning.westerholt@1und1.de</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im">On Monday 30 March 2009, Uriel Rozenbaum wrote:<br>
</div><div class="im">> I'm using this piece of code as failure route:<br>
><br>
</div>> append_branch();<br>
<br>
Hi Uriel,<br>
<br>
do you do a "revert_uri()" somewhere before entering the failure_route? And<br>
can you check if you perhaps reset the failed flag somewhere later in your<br>
cfg?<br>
<br>
> [..]<br>
<div class="im">> And right in the main route i have:<br>
><br>
> if (is_method("INVITE|BYE|CANCEL"))<br>
> {<br>
> setflag(1);<br>
> setflag(2);<br>
> }<br>
><br>
> In order to bill all messages.<br>
><br>
> Is there any error in the failure logic?<br>
<br>
</div>Flag 1 is the successful, and 2 the failed flag?<br>
<br>
Cheers,<br>
<font color="#888888"><br>
Henning<br>
</font></blockquote></div><br>