<p dir="ltr">Depending on what you wish to do this is a way of forwarding the failure to another host. Make sure this is the failure route you are declaring within your subroute </p>
<p dir="ltr">failure_route[1] {         if (t_was_cancelled()) {                 exit;         }         #  (t_check_status(&quot;477|401|403&quot;)) {         <br>
                rewritehostport(&quot;ip:port&quot;);         <br>
        t_relay();                 <br>
exit;         }</p>
<div class="gmail_quote">On Jun 3, 2015 11:27 PM, &quot;Podrigal, Aron&quot; &lt;<a href="mailto:aronp@guaranteedplus.com">aronp@guaranteedplus.com</a>&gt; wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi,<div><br></div><div>When I receive a 407 / 401 / 403 response from my carrier, I want to handle that as a failure and trigger the failure route without fowarding the 40x reply upstream. How would I do that?<br clear="all"><div><br></div>-- <br><div><div dir="ltr">Aron Podrigal<div>-</div><div>//Be happy :-)</div></div></div>
</div></div>
<br>_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><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></blockquote></div>