Hi Brett,

False, the module is first doing re-ordering (based on weights) and after then truncates to "first one only". See my email with the test results. Shortly 0x3 should work by randomly (with weights) picking only GW from the carrier list.

Regards,

Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com

On 24.07.2014 09:38, Brett Nemeroff wrote:
Unfortunately it doesn't seem like drouting will do this kind of routing. If you select flags 0x3 and set equal weights, it won'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.
-Brett



On Wed, Jul 23, 2014 at 2:04 PM, Ricky Keele <rjke...@digitalipvoice.com <mailto:rjke...@digitalipvoice.com>> wrote:

    Just to be clear. We do routing to customer GW'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?

    Ricky
    On 7/23/2014 10:37 AM, Kneeoh wrote:

        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

        Ultimately I'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



        On Wednesday, July 23, 2014 10:07 AM, Bogdan-Andrei Iancu
        <bog...@opensips.org <mailto:bog...@opensips.org>> wrote:
        Hi,

        Actually you can combine the flags and use 0x03 - ordering by
        weights
        and use only first. Just give it a try.

        Regards,

        Bogdan-Andrei Iancu
        OpenSIPS Founder and Developer
        http://www.opensips-solutions.com




        On 23.07.2014 03:29, Kneeoh wrote:

            It would be great if you could combine the binary Flags
            for dr_carrier routing:

            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

            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.


            _______________________________________________
            Users mailing list
            Users@lists.opensips.org <mailto:Users@lists.opensips.org>
            http://lists.opensips.org/cgi-bin/mailman/listinfo/users

        _______________________________________________
        Users mailing list
        Users@lists.opensips.org <mailto:Users@lists.opensips.org>
        http://lists.opensips.org/cgi-bin/mailman/listinfo/users



    _______________________________________________
    Users mailing list
    Users@lists.opensips.org <mailto:Users@lists.opensips.org>
    http://lists.opensips.org/cgi-bin/mailman/listinfo/users




_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Reply via email to