Since the redirect response is 3xx+, you should catch it in a failure_route[], which is armed with t_on_failure().
In the failure_route, you can check if the failure_route was invoked because of a timeout with if(t_branch_timeout()), and if it was not, extract the reply code with $T_rpl($rs). Then, you modify the R-URI ($ru) to proceed to the original destination and call t_relay() again. -- Alex > On May 19, 2025, at 3:45 PM, JR Richardson via sr-users > <[email protected]> wrote: > > Hey Folks, > > I'm integrating STIR/SHAKEN using kamailio, but not using self hosted certs > with the secsipid module, just using a redirect from clearip on the SIP > Calls. I've got the basic connection to clearip using t_relay_to_tcp for > testing, but I'm struggling with the checks and timeouts. I have call > progress past the initial request where I need to wait for a response. Should > I put the clearip invite in its own route block use return? Has anyone > successfully integrated the redirect method with kamailio to clearip and can > give me some example route checks in the kamailio configs? > > Thanks. > JR > > __________________________________________________________ > Kamailio - Users Mailing List - Non Commercial Discussions -- > [email protected] > To unsubscribe send an email to [email protected] > Important: keep the mailing list in the recipients, do not reply only to the > sender! -- Alex Balashov Principal Consultant Evariste Systems LLC Web: https://evaristesys.com Tel: +1-706-510-6800 __________________________________________________________ Kamailio - Users Mailing List - Non Commercial Discussions -- [email protected] To unsubscribe send an email to [email protected] Important: keep the mailing list in the recipients, do not reply only to the sender!
