Iñaki Baz Castillo wrote: > 2009/9/15 Bogdan-Andrei Iancu <[email protected]>: > >> Hi Iñaki, >> >> priority applies only to rules that overlap - this can happens only when >> time selection is used for the rules: >> >> Ex: RULE1: for prefix 1234, all the time, use GW1, prio =1 >> RULE2: for prefix 1234, during weekend, use GW1, prio = 4 >> >> Here the rules will overlap during the weekend - they both match; in >> this interval, the highest priority rule will be used. >> >> The priority mechanism is used exclusively for this case. >> > > So in case time selection is null in botrules, priority mechanism > doesn't matter, right? > If so, I suggest to explain it in the documentation, as I couldn't > understand it after several reads :) >
Let me tell you a joke: Q: "What do engineers and dogs have in common ? " A: "They both have an intelligent eyes/look, but none of them can express themselves" So, I will try to re-work the explanation there. > > >> The module does not do any rule fallback - once a rule is match, it will >> use only the destination from the rules and it will not try to re-match >> a different rule. >> > > Yes, but if all the gws in a rule (prio 10) fail (so "use_next_gw" > returns false) then this rule (or its gws) would be automatically > included in a blacklist, so if then I call again > "do_routing(SAME_GROUPID)" then the next rule (minor priority) would > be taken, am I right? > yes, make sense - probably we can add it for 1.7 ....for 1.6 is a bit too late. Best regards, Bogdan _______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
