Alex, check my message below. If t_relay fails in request route, there must be a means to find out in request route , what happened in the failed branch route.
-- Juha On December 16, 2019 5:18:06 PM GMT+09:00, Alex Balashov <[email protected]> wrote: >But is there ever a situation where t_relay() immediately fails out of >hand yet TM state hooks like failure_route are invoked? > >I think the idea is to deal with the problem right then in the original >request route — having full access to variables and other initially >available state — and re-initiate t_relay(). Right? > >— >Sent from mobile, with due apologies for brevity and errors. > >> On Dec 16, 2019, at 3:00 AM, Juha Heinanen <[email protected]> wrote: >> >> Daniel-Constantin Mierla writes: >> >>> t_relay() should return negative (false) in such case, but I am not >sure >>> it returns a specific value for it -- this can be a variant to add >if >>> needed. >> >> Yes, t_relay() returns false, but the branch flags I set in the >branch >> route are lost and I don't know what happened there so that I could >> undo things. For example, if branch route called rtpengine_offer, I >> would need to know that. >> >> -- Juha >> >> _______________________________________________ >> Kamailio (SER) - Users Mailing List >> [email protected] >> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > >_______________________________________________ >Kamailio (SER) - Users Mailing List >[email protected] >https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users _______________________________________________ Kamailio (SER) - Users Mailing List [email protected] https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
