Geoffrey Mina writes:
> The LCR module is behaving in a way that is inconsistent with our old 1.5
> versions. We have a customer that passes a certain caller-id. That
> from_uri should be routing over a specific trunk. Here are the relevant
> bits of the LCR data from kamcmd.
>
> I would expect gw_index: 7 to match before gw_index: 6 here, but that is
> not the case. Any help would be greatly appreciated. Please note, i Have
> stripped out a bunch of other routes that are not in play here... hence the
> reason gw_index starts at "6".
you didn't show how from uri of the call looks like. if it matches
from_uri: 2089328663, it will also match from_uri: and either rule can
get selected.
-- juha
> kamcmd> lcr.dump_rules
> {
> lcr_id: 1
> rule_id: 31
> prefix: +1
> from_uri: 2089328663
> request_uri:
> stopper: 0
> }
> {
> gw_index: 6
> priority: 1
> weight: 1
> }
> {
> lcr_id: 1
> rule_id: 5
> prefix: +1
> from_uri:
> request_uri:
> stopper: 0
> }
> {
> gw_index: 7
> priority: 1
> weight: 1
> }
> _______________________________________________
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users@lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
