Its listed here - https://opensips.org/html/docs/modules/3.1.x/tm.html#param_disable_6xx_block
So yes it should work. ________________________________ From: Users <[email protected]> on behalf of Saint Michael <[email protected]> Sent: Tuesday, October 25, 2022 9:52 AM To: OpenSIPS users mailling list <[email protected]> Subject: Re: [OpenSIPS-Users] 603 not treated as a failure Will that work on version 3.1X On Tue, Oct 25, 2022, 10:36 AM Social Boh <[email protected]<mailto:[email protected]>> wrote: maybe: * modparam("tm", "disable_6xx_block", 1) to TM module --- I'm SoCIaL, MayBe El 25/10/2022 a las 9:22 a. m., Richard Robson escribió: 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. 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.. 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.? Regards, Richard _______________________________________________ Users mailing list [email protected]<mailto:[email protected]> http://lists.opensips.org/cgi-bin/mailman/listinfo/users _______________________________________________ Users mailing list [email protected]<mailto:[email protected]> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
