Hello List,<br><br>Upon looking at the enhancements of drouting in 1.8, I'm a bit confused at all the new options for the gwlist fields. I found this snippet on the list:<br><pre>>>>> gateways : g1, g2, g3, g4, g5
>>>> carriers : c1 = g1=75,g2=25 (a premium carrier), ordering based
>>>> on weight
>>>> c2 = g3,g4 (a standard carrier), ordering based on
>>>> given order
>>>> rules: prefix= 004021 ; list = #c1,#c2,g5 - first we will try do
>>>> distribute 75/25 the traffic
>>>> between the gws from carrier c1 and if all fail, we
>>>> will try gws from carrier c2
>>>> (according the ordering defined for c2), and so on
>>>>
>>>> prefix= 004072 ; list = #c2=50,g5=50 - all traffic will
>>>> be weight balanced between carrier
>>>> c2 and gw g5; of course, if carrier c2 is to be used,
>>>> the corresponding traffic will
>>>> routed over the c2 gateways according to its
>>>> definition
>>>>
>>>><br><br>Which seems to indicate the new "weights" option can be used by specifying a gateway_id followed by an "=<0-100>" where <0-100> is weight.<br><br>I can't really find how this is documented anywhere. Also what gets picked first? 0 weight? or 100 weight?<br>
<br>What if I just want it to try 1 gateway for each carrier and not roll from gateway to gateway to gateway? For<br>example, I'd like to see where I can do something like this in the CARRIER definition:<br>g1=75,g2=25<br>
<br><br>and then every time I pick that carrierid, 75% of the time g1 will get picked, and 25% of the time g2 will be <br>picked. But it will never go from g1, then g2 (rather I'd like it to proceed in my script logic so I can pick<br>
another carrier).<br><br>Or does it already do that? If I don't specify weights, does it try them in serial order? <br><br><br>Is this documented somewhere that I'm missing? The regular module docs dont' seem to show it. <br>
<br>Thanks,<br>-Brett<br><br></pre><br>