<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>Hey Bogdan,</div><div>I&#39;d love to be wrong here. :)</div><div><br></div><div>I tested this not too long ago and it didn&#39;t work. As I recall, weights were at 50, for all. Not 0. Not sure if that matters. In any case it&#39;s good news that I&#39;m wrong! I&#39;ll retest!</div>
<div><br></div><div><br>-Brett</div><div><br>On Jul 24, 2014, at 4:29 AM, Bogdan-Andrei Iancu &lt;<a href="mailto:bogdan@opensips.org">bogdan@opensips.org</a>&gt; wrote:<br><br></div><blockquote type="cite"><div>
  
    <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">
  
  
    <div class="moz-cite-prefix"><tt>Hi Brett,<br>
        <br>
        False, the module is first doing re-ordering (based on weights)
        and after then truncates to &quot;first one only&quot;.  See my email with
        the test results. Shortly 0x3 should work by randomly (with
        weights) picking only GW from the carrier list.<br>
        <br>
        Regards,<br>
      </tt>
      <pre class="moz-signature" cols="72">Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
<a class="moz-txt-link-freetext" href="http://www.opensips-solutions.com">http://www.opensips-solutions.com</a></pre>
      On 24.07.2014 09:38, Brett Nemeroff wrote:<br>
    </div>
    <blockquote cite="mid:CAPwC5wyRV1Rc_MRmxEUJ6G2eUM0GEow0=k+reZacYgAUQxoPdg@mail.gmail.com" type="cite">
      <div dir="ltr">Unfortunately it doesn&#39;t seem like drouting will do
        this kind of routing. If you select flags 0x3 and set equal
        weights, it won&#39;t randomize the gateway chosen and only pick
        one. This would be a good feature request because right now,
        even with 0x03, only the first gw is ever picked.
        <div>
          -Brett</div>
        <div><br>
        </div>
      </div>
      <div class="gmail_extra"><br>
        <br>
        <div class="gmail_quote">On Wed, Jul 23, 2014 at 2:04 PM, Ricky
          Keele <span dir="ltr">&lt;<a href="mailto:rjkeele@digitalipvoice.com" target="_blank">rjkeele@digitalipvoice.com</a>&gt;</span>
          wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Just to be
            clear. We do routing to customer GW&#39;s that require us to do
            round-robin which means we rotate the calls between
            gateways. I am assuming that the drouting module would do
            the same if the weights are equal say gw1=0 gw2=0. The other
            big request is where customer will have 3 or 4 gateways and
            they need to balance the traffic between the 3;example
            gw1=30%, gw2=50%, gw3=20%.. Is this possible with drouting
            module today?<br>
            <br>
            Ricky<br>
            On 7/23/2014 10:37 AM, Kneeoh wrote:<br>
            <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
              I thought that would work too. But if I put (dr_carriers
              table) gwlist:gw1=50,gw2=50 flags:3 it Always picks gw1. I
              want it to alternate between gw1 and gw2<br>
              <br>
              Ultimately I&#39;m trying to do something like: dr_rules:
              gwlist: #cr1=50,#cr2=50 lets say it picks cr1, then go to
              the dr_carriers table where it will pick ONE of the
              carrier gateways based on weight, if that gateway fails or
              times out use the next carrier cr2, not the next gateway
              for cr1
              <div>
                <div class="h5"><br>
                  <br>
                  <br>
                  On Wednesday, July 23, 2014 10:07 AM, Bogdan-Andrei
                  Iancu &lt;<a href="mailto:bogdan@opensips.org" target="_blank">bogdan@opensips.org</a>&gt;
                  wrote:<br>
                  Hi,<br>
                  <br>
                  Actually you can combine the flags and use 0x03 -
                  ordering by weights<br>
                  and use only first. Just give it a try.<br>
                  <br>
                  Regards,<br>
                  <br>
                  Bogdan-Andrei Iancu<br>
                  OpenSIPS Founder and Developer<br>
                  <a href="http://www.opensips-solutions.com" target="_blank">http://www.opensips-solutions.com</a><br>
                  <br>
                  <br>
                  <br>
                  <br>
                  On 23.07.2014 03:29, Kneeoh wrote:<br>
                  <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
                    It would be great if you could combine the binary
                    Flags for dr_carrier routing:<br>
                    <br>
                    flags : 0x1 - use weight for sorting the list and
                    not definition order; 0x2 - use only the first
                    gateway from the carrier (depending on the sorting);
                    0x4 - disable the usage of this carrier<br>
                    <br>
                    such that where 1+2 = 3 the gateways are first
                    sorted by weight then returns only the top result
                    for each carrier. This would allow for equitable
                    distribution between carrier gateways. This way
                    gw1=100,gw2=100 would have a roughly equal chance of
                    being picked (if enabled=true). At present it either
                    cycles through all carrier gateways OR when the
                    binary flag is set to 2, it picks the first gateway
                    ONLY, ALL THE TIME.<br>
                    <br>
                    <br>
                    _______________________________________________<br>
                    Users mailing list<br>
                    <a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a><br>
                    <a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
                  </blockquote>
                  _______________________________________________<br>
                  Users mailing list<br>
                  <a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a><br>
                  <a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
                </div>
              </div>
            </blockquote>
            <div class="HOEnZb">
              <div class="h5">
                <br>
                <br>
                _______________________________________________<br>
                Users mailing list<br>
                <a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a><br>
                <a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
              </div>
            </div>
          </blockquote>
        </div>
        <br>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre>_______________________________________________
Users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a>
<a class="moz-txt-link-freetext" href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a>
</pre>
    </blockquote>
    <br>
  

</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>Users mailing list</span><br><span><a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a></span><br>
<span><a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a></span><br></div></blockquote></body></html>