Hello

seems with t_flush_xflags() after setxflag on failure_route, it makes it work. However i don't know if that should be the expected behaviour, since with regular transaction flags there is no need to use t_flush_flags()

best regards

david

El mié, 10 feb 2021 a las 16:08, David Escartin (<descartin@sonoc.io>) escribió:

Dear all

i think i have noticed a wrong behaviour with xflags. When they are set in a failure_route and a t_relay is done after that to a destination, its state is lost in the next on_reply route.
This doesn't happen with regular transaction flags, and it doesn't happen with xflags either when xflag is set inside an onreply_route.

We have seen it on versions 5.3 and 5.4

Could you please confirm this?

thanks a lot

regards

david escartin

--

David Escartín Almudévar VoIP/Switch Engineer descartin@sonoc.io SONOC C/ Josefa Amar y Borbón, 10, 4ª · 50001 Zaragoza, España Tlf: +34 917019888 · www.sonoc.io

--

David Escartín Almudévar VoIP/Switch Engineer descartin@sonoc.io SONOC C/ Josefa Amar y Borbón, 10, 4ª · 50001 Zaragoza, España Tlf: +34 917019888 · www.sonoc.io