[OpenSIPS-Users] Parallel branches and failure route

[Bogdan-Andrei Iancu]

Hi,

you can gain access to all replies from all branches via the onreply route.

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com
   https://www.siphub.com

On 6/13/23 1:07 PM, Yury Kirsanov wrote:
> Hi Bogdan,
> Thanks a lot for clarification, is there any way to 'catch' other 
> branches? Or maybe I should open a feature request for that? It's 
> quite important from the point of view of billing to have these 
> branches processed too. Thanks!
>
> Best regards,
> Yury.
>
> On Tue, Jun 13, 2023 at 5:31 PM Bogdan-Andrei Iancu 
> <bogdan at opensips.org <mailto:bogdan at opensips.org>> wrote:
>
>     Hi Yury,
>
>     Yes, the failure route is per-transaction - it is triggered when
>     the whole transaction fails, meaning it got negative replies on
>     all its branches. In failure route you see only the "wining"
>     branch (from all existing branches), meaning the branch with the
>     lowest reply code.
>
>     Best regards,
>
>     Bogdan-Andrei Iancu
>
>     OpenSIPS Founder and Developer
>        https://www.opensips-solutions.com  <https://www.opensips-solutions.com>
>        https://www.siphub.com  <https://www.siphub.com>
>
>     On 5/14/23 4:47 PM, Yury Kirsanov wrote:
>>     Hi,
>>     I'm adding multiple branches to the initial request and then use
>>     t_relay() to fire them all up to multiple destinations. But it
>>     seems that I can only set up only one t_on_failure route. How do
>>     I distinguish between branches in that failure route? Part of the
>>     branches can respond with 4xx, part - with 5xx and so on and only
>>     one would respond with 200 OK. I need to process all FAILED
>>     branches, not caring too much about the successful one. What
>>     would be the best way to do this? Thanks.
>>
>>     Regards,
>>     Yury.
>>
>>     _______________________________________________
>>     Users mailing list
>>     Users at lists.opensips.org  <mailto:Users at lists.opensips.org>
>>     http://lists.opensips.org/cgi-bin/mailman/listinfo/users  <http://lists.opensips.org/cgi-bin/mailman/listinfo/users>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20230613/37a967ac/attachment.html>