<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>maybe:</p>
<p>
</p>
<ul>
<li>
<p style="margin-bottom: 0in" lang="es-CO" align="justify"><b>modparam("tm",
"disable_6xx_block", 1)</b></p>
</li>
</ul>
<p>to TM module<br>
</p>
<pre class="moz-signature" cols="72">---
I'm SoCIaL, MayBe</pre>
<div class="moz-cite-prefix">El 25/10/2022 a las 9:22 a. m., Richard
Robson escribió:<br>
</div>
<blockquote type="cite"
cite="mid:b9399ca0-ad7d-bcfd-9d7d-312cb987ab84@rikrobson.co.uk">I
am currently testing version 3.3 and I have a scenario where we
will receive a 603 to an invite. this needs to be failed over to
the next destination. we are using dispatcher for this.
<br>
<br>
While testing I am finding that opensips is treating the 603 a a
relpy and not as a failure and its being handled by the reply
route and not by the failure route. passing the message back to
the UAC..
<br>
<br>
Is this by design or is there some setting where the 603 can be
treated as a failure and be handled by the specified failure route
and failed over to the next destination.?
<br>
<br>
<br>
Regards,
<br>
<br>
<br>
Richard
<br>
<br>
<br>
_______________________________________________
<br>
Users mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a>
<br>
<a class="moz-txt-link-freetext" href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a>
<br>
</blockquote>
</body>
</html>