<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Aptos;
panose-1:2 11 0 4 2 2 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
mso-ligatures:none;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-family:"Aptos",sans-serif">Sasmita,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Aptos",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Aptos",sans-serif">I can’t provide a working example as I don’t have a use case like this. However, this piece of script you’ve provided does not represent a correct flow. I think you may need to review how the
different types of routes, and particularly branch routes, work. [1]<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Aptos",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Aptos",sans-serif">I don’t have any experience with Registrar module, so take all of the following with a grain of salt. Someone with more experience with registrar can maybe keep me honest here.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Aptos",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Aptos",sans-serif">You should only need to call next_branches() one time, as it already loads all contacts returned by lookup() into parallel branches (assuming you are using the “b” flag for lookup()). This means
they are all sent out at once, not serially. So you don’t need to send the next branch in failure_route because they’ve all already been sent.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Aptos",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Aptos",sans-serif">The branch route is executed as the last route before the message is being sent out. You certainly do not need to call next_branches() there either, in fact its behavior in a branch route is
not defined in the docs. Also, I don’t know what your route “1” does, but you likely don’t need it from branch route either. As long as you don’t drop the branch, it will automatically be sent out. Lastly, you have the actual drop() command commented out,
so this code won’t work as I described.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Aptos",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Aptos",sans-serif">Lastly, failure_route is armed for the whole request. In the case of parallel branching, it will only be called once for the request, not once for each branch, and only if all branches receive
negative replies.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Aptos",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Aptos",sans-serif">One thing I’m not clear about is what happens if you end up dropping all the branches. I don’t know if failure_route would be called then, but it would be pretty easy to verify that. I think
it would.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Aptos",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Aptos",sans-serif">Again, I can’t speak to your specific use case, but a representative version of the solution I recommended is below. *<b>I have not tested or verified this code.</b>*<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Aptos",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal">route {</p>
<p class="MsoNormal"> # all of your normal routing logic</p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"> if (lookup(“<domain>”, “b”)) {</p>
<p class="MsoNormal"> if (next_branches()) {</p>
<p class="MsoNormal"> t_on_branch(“check_attrs”);</p>
<p class="MsoNormal"> t_on_failure(“no_branches”);</p>
<p class="MsoNormal"> }</p>
<p class="MsoNormal"> else {</p>
<p class="MsoNormal"> # handle case of no contacts</p>
<p class="MsoNormal"> t_reply(404, “Not Found”);</p>
<p class="MsoNormal"> }</p>
<p class="MsoNormal"> }</p>
<p class="MsoNormal"> else {</p>
<p class="MsoNormal"> # handle case of failed lookup</p>
<p class="MsoNormal"> t_reply(404, “Not Found”);</p>
<p class="MsoNormal"> }</p>
<p class="MsoNormal">}</p>
<p class="MsoNormal"><br>
branch_route[check_attrs] {<br>
$var(count) = $(hdr(Call-Info){csv.count});<br>
<br>
while($(var(count) >= 0)) {<br>
if ($(avp(attr){s.index, $(hdr(Call-Info){csv.value,$var(i)})}) == NULL) {</p>
<p class="MsoNormal"> # as soon as one requirement doesn’t match, you know you don’t want to route</p>
<p class="MsoNormal"> drop();</p>
<p class="MsoNormal"> }</p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"> xlog("count: $var(count)\n");<br>
$var(count) = $var(count) - 1;<br>
}</p>
<p class="MsoNormal">}</p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">failure_route[no_branches] {<br>
# handle case where all branches failed</p>
<p class="MsoNormal"> t_reply(404, “Not Found”);<br>
}<span style="font-family:"Aptos",sans-serif"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Aptos",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Aptos",sans-serif">[1] <a href="https://www.opensips.org/Documentation/Script-Routes-3-2">
https://www.opensips.org/Documentation/Script-Routes-3-2</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Aptos",sans-serif"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span style="color:black">Ben Newlin</span><span style="font-family:"Aptos",sans-serif"><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-family:"Aptos",sans-serif"><o:p> </o:p></span></p>
<div id="mail-editor-reference-message-container">
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-bottom:12.0pt"><b><span style="font-size:12.0pt;font-family:"Aptos",sans-serif;color:black">From:
</span></b><span style="font-size:12.0pt;font-family:"Aptos",sans-serif;color:black">Users <users-bounces@lists.opensips.org> on behalf of Sasmita Panda <spanda@3clogic.com><br>
<b>Date: </b>Thursday, November 2, 2023 at 9:36 AM<br>
<b>To: </b>OpenSIPS users mailling list <users@lists.opensips.org><br>
<b>Subject: </b>Re: [OpenSIPS-Users] I need some help in attr matching while forming the Branch .</span><span style="font-size:12.0pt;font-family:"Aptos",sans-serif"><o:p></o:p></span></p>
</div>
<div>
<div>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="0" width="100%" align="center">
</div>
</div>
<p class="MsoNormal">Hi Ben , </p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><br>
<br>
failure_route[1] {<br>
if ( t_check_status("404|477|480|481|408|486|50[234]")){ <br>
if (next_branches())<br>
{<br>
t_on_branch("attr");<br>
}<br>
<br>
} <br>
}<br>
<br>
<br>
branch_route[attr]<br>
{<br>
$var(count) = $(hdr(Call-Info){csv.count});<br>
<br>
$var(i) = 0;<br>
$var(match-count) = 0;<br>
<br>
while($var(i) < $(var(count))){<br>
<br>
if ($(avp(attr){s.index, $(hdr(Call-Info){csv.value,$var(i)})}) != NULL){<br>
xlog("counter: $var(i)th index matched in attribute \n");<br>
$var(match-count)= $var(match-count) + 1;<br>
}<br>
xlog("counter: $var(i)\n");<br>
$var(i) = $var(i) + 1;<br>
}<br>
<br>
if ($var(i) == $var(match-count)){<br>
## Here I want to give call to that contact .. if that fails then again it should come to next branch and again compare
<br>
t_on_failure("1");<br>
route(1);<br>
}<br>
else{<br>
# Here if the condition does not match . then i want to do the comparison again <br>
if (next_branches()){<br>
t_on_branch("attr");<br>
}<br>
# drop();<br>
}<br>
}</p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">As for my expectation, it's not working . How does it work ? Where should I use T_branch_Idx ? Can I get some examples of this ?</p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><br clear="all">
</p>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><b><i>Thanks & Regards</i></b></p>
<div>
<p class="MsoNormal"><i>Sasmita Panda</i></p>
</div>
<div>
<p class="MsoNormal"><i>Senior Network Testing and Software Engineer</i></p>
</div>
<div>
<p class="MsoNormal"><i>3CLogic , ph:07827611765</i></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt">
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</blockquote>
</div>
</div>
</div>
</div>
</body>
</html>