<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <font face="monospace">The uac_auth() works only upon transaction
      failure, so you have to wait for all the branches to fail and only
      then you can do the auth.<br>
      <br>
      IF you need to do individual auth for each branch, I would advice
      to spiral OpenSIPS, in order to handle each branch as an
      individual transaction.<br>
          UAC -> OpenSIPS (parallel forking) -> OpenSIPS (doing
      auth) -> UAS<br>
      <br>
      Regards,<br>
    </font>
    <pre class="moz-signature" cols="72">Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
  <a class="moz-txt-link-freetext" href="https://www.opensips-solutions.com">https://www.opensips-solutions.com</a>
  <a class="moz-txt-link-freetext" href="https://www.siphub.com">https://www.siphub.com</a></pre>
    <div class="moz-cite-prefix">On 6/13/23 4:42 PM, Yury Kirsanov
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAD1_sesDfE0BsXf01TyeivnCpdRiSrNkud93XfAaR0ZMOMbd=A@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="ltr">Thanks, Bogdan,
        <div>But what if I need to perform uac_auth in one of the
          branches? I can't originate anything from the on_reply route,
          unfortunately :(</div>
        <div><br>
        </div>
        <div>Regards,</div>
        <div>Yury.</div>
      </div>
      <br>
      <div class="gmail_quote">
        <div dir="ltr" class="gmail_attr">On Tue, Jun 13, 2023 at
          8:44 PM Bogdan-Andrei Iancu <<a
            href="mailto:bogdan@opensips.org" moz-do-not-send="true">bogdan@opensips.org</a>>
          wrote:<br>
        </div>
        <blockquote class="gmail_quote" style="margin:0px 0px 0px
          0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
          <div> <font face="monospace">Hi,<br>
              <br>
              you can gain access to all replies from all branches via
              the onreply route.<br>
              <br>
              Regards,<br>
            </font>
            <pre cols="72">Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
  <a href="https://www.opensips-solutions.com" target="_blank" moz-do-not-send="true">https://www.opensips-solutions.com</a>
  <a href="https://www.siphub.com" target="_blank" moz-do-not-send="true">https://www.siphub.com</a></pre>
            <div>On 6/13/23 1:07 PM, Yury Kirsanov wrote:<br>
            </div>
            <blockquote type="cite">
              <div dir="ltr">Hi Bogdan,
                <div>Thanks a lot for clarification, is there any way to
                  'catch' other branches? Or maybe I should open a
                  feature request for that? It's quite important from
                  the point of view of billing to have these branches
                  processed too. Thanks!</div>
                <div><br>
                </div>
                <div>Best regards,</div>
                <div>Yury.</div>
              </div>
              <br>
              <div class="gmail_quote">
                <div dir="ltr" class="gmail_attr">On Tue, Jun 13, 2023
                  at 5:31 PM Bogdan-Andrei Iancu <<a
                    href="mailto:bogdan@opensips.org" target="_blank"
                    moz-do-not-send="true">bogdan@opensips.org</a>>
                  wrote:<br>
                </div>
                <blockquote class="gmail_quote" style="margin:0px 0px
                  0px 0.8ex;border-left:1px solid
                  rgb(204,204,204);padding-left:1ex">
                  <div> <font face="monospace">Hi Yury,<br>
                      <br>
                      Yes, the failure route is per-transaction - it is
                      triggered when the whole transaction fails,
                      meaning it got negative replies on all its
                      branches. In failure route you see only the
                      "wining" branch (from all existing branches),
                      meaning the branch with the lowest reply code.<br>
                      <br>
                      Best regards,<br>
                    </font>
                    <pre cols="72">Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
  <a href="https://www.opensips-solutions.com" target="_blank" moz-do-not-send="true">https://www.opensips-solutions.com</a>
  <a href="https://www.siphub.com" target="_blank" moz-do-not-send="true">https://www.siphub.com</a></pre>
                    <div>On 5/14/23 4:47 PM, Yury Kirsanov wrote:<br>
                    </div>
                    <blockquote type="cite">
                      <div dir="ltr">Hi,
                        <div>I'm adding multiple branches to the initial
                          request and then use t_relay() to fire them
                          all up to multiple destinations. But it seems
                          that I can only set up only one t_on_failure
                          route. How do I distinguish between branches
                          in that failure route? Part of the branches
                          can respond with 4xx, part - with 5xx and so
                          on and only one would respond with 200 OK. I
                          need to process all FAILED branches, not
                          caring too much about the successful one. What
                          would be the best way to do this? Thanks.</div>
                        <div><br>
                        </div>
                        <div>Regards,</div>
                        <div>Yury.</div>
                      </div>
                      <br>
                      <fieldset></fieldset>
                      <pre>_______________________________________________
Users mailing list
<a href="mailto:Users@lists.opensips.org" target="_blank" moz-do-not-send="true">Users@lists.opensips.org</a>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank" moz-do-not-send="true">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a>
</pre>
                    </blockquote>
                    <br>
                  </div>
                </blockquote>
              </div>
            </blockquote>
            <br>
          </div>
        </blockquote>
      </div>
    </blockquote>
    <br>
  </body>
</html>