<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hi all,<div class=""><br class=""></div><div class="">I have a prioritised list of endpoints, where endpoints with the same priority should be sent in parallel:</div><div class=""><br class=""></div><div class="">- endpoint_1_uri; p = 1</div><div class="">- <span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);" class="">endpoint_2_uri</span>; p = 2</div><div class="">- <span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);" class="">endpoint_3_uri</span>; p = 4</div><div class="">- <span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);" class="">endpoint_4_uri</span>; p = 5</div><div class=""><br class=""></div><div class="">As some of the lower priority endpoints are not known upfront, I can not load entire list into the contact list and use TM module's “forking based on Q value” to take care of the rest. So my plan is to load all endpoints with the same priority and fork them in parallel. If none succeed - obtain next endpoint(s) and repeat the process. </div><div class=""><br class=""></div><div class="">As I go through the above process, I need to update some counters each time delivery to one of the endpoints succeeds or fails. To be able to perform these “housekeeping” tasks I need to be able to clearly identify branches and link them to the destination URI (endpoint URI) of the forked INVITE that started them. Ideally I would like to be able to maintain relationship “branch_id” => “destination URI” where “branch_id” is the identifier that is appended to Via branch parameter. <span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);" class="">What is the best/most reliable way to achieve this?</span></div><div class=""><br class=""></div><div class="">I tried logging and observing the value of $du - it<font color="#000000" class=""><span style="caret-color: rgb(0, 0, 0);" class=""> was available just before sending out a forked INVITE, but in branch_failure and onreply_route it was <null>.</span></font></div><div class=""><font color="#000000" class=""><span style="caret-color: rgb(0, 0, 0);" class=""><br class=""></span></font></div><div class=""><font color="#000000" class=""><span style="caret-color: rgb(0, 0, 0);" class="">I tried logging and observing $T_req($du) - I only expected it to work from onreply_route, but it was also <null>.</span></font></div><div class=""><font color="#000000" class=""><span style="caret-color: rgb(0, 0, 0);" class=""><br class=""></span></font></div><div class=""><font color="#000000" class="">I tried logging and observing $T_branch_idx - while it was showing meaningful data before sending forked INVITE and during branch_failure route, I couldn’t access it from onreply_route so I couldn’t tell which of the branches current reply is for.</font></div><div class=""><font color="#000000" class=""><br class=""></font></div><div class=""><font color="#000000" class="">Are there any more variables that could help me build </font><span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);" class="">“branch_id” => “destination URI” relationship and access information about </span><span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);" class="">“branch_id” and/or “destination URI” from branch_failure and onreply_route?</span></div><div class=""><span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);" class=""><br class=""></span></div><div class=""><font color="#000000" class="">Apologies in advance for a lengthy description, I did my best to summarise the situation and what I’m trying to achieve.</font></div><div class=""><font color="#000000" class=""><br class=""></font></div><div class=""><font color="#000000" class="">Regards,</font></div><div class=""><font color="#000000" class="">Ivan</font></div><div class=""><font color="#000000" class=""><span style="caret-color: rgb(0, 0, 0);" class=""><br class=""></span></font></div><div class=""><br class=""></div></body></html>