Hello,
I am not sure I understand what you are looking for? A variable that you can use as a key per branch? Or per call? Maybe you can give an example how you want to use it and expected behavior, then we may be able to give some hints about what can be used.
Cheers, Daniel
On 18.03.19 11:43, Володимир Іванець wrote:
I found much better description of the problem here https://lists.kamailio.org/pipermail/users/2008-August/019070.html. Also I figured that calling *reg_fetch_contacts* and saving appropriate *$(ulc(callee=>addr)[$var(i)])* in /event_route[tm:branch-failure:FAILURE]/ will allow to match /t_on_reply("REPLY")/ by *$T(ruid)*.
пт, 15 бер. 2019 о 17:10 Володимир Іванець <volodyaivanets@gmail.com mailto:volodyaivanets@gmail.com> пише:
Hello! I have Kamailio setup with registrar configured to allow multiple registrations. /branch_route[MANAGE_BRANCH]/ contains /t_on_reply("REPLY")/ and /t_on_branch_failure("FAILURE")/. /event_route[tm:branch-failure:FAILURE]/ is used to do some logic, store information in htable and in the end it calls *t_relay* function. This creates new branch. Replies for this branch go to/ onreply_route[REPLY]/. The problem is that I can not find appropriate variable that would be available in both *event_route tm:branch-failure* and *onreply_route*. I need it to get saved data from htable. $T_reply_ruid is available in first one but not in second. $T_branch_idx obviously changes so it can not be used. Some registrations do not have *Received* value so source IP address and ports can not be used. *Address* value can be compared with *Contact* header from responce tacket but it is so long that it looks like it's not optimal way to do. What interesting is that $T_reply_ruid is accessible in original replies for branches that have not failed. Does anyone know what variable can be used in this case or how to make sure that $T_reply_ruid will be set? Thanks a lot!
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users