OK. WE have made a change so that the priority is 0 for the route that has the from_uri. We are still not seeing this route get matched properly.
Here is what the INVITE looks like: INVITE sip:+19137274555@1.2.3.4:5060 SIP/2.0 Via: SIP/2.0/UDP 1.2.3.4:5060;branch=z9hG4bK5b52e524;rport From: "2089328663" <sip:2089328...@blah.com>;tag=as37fe796f To: <sip:+19137274555@1.2.3.4:5060> Contact: <sip:2089328663@1.2.3.4> Call-ID: 09ed895a452fac516a0d11e237bd1...@blah.com CSeq: 102 INVITE User-Agent: Kamailio Max-Forwards: 70 Date: Tue, 22 Apr 2014 14:42:16 GMT Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO Supported: replaces P-Account-ID: 12680001 P-Charge-Info: "4019921313" <sip:4019921...@blah.com> Content-Type: application/sdp Content-Length: 236 Here is what lcr.dump_rules looks like: kamcmd> lcr.dump_rules { lcr_id: 1 rule_id: 31 prefix: +1 from_uri: 2089328663 request_uri: stopper: 0 } { gw_index: 6 priority: 0 weight: 1 } { lcr_id: 1 rule_id: 5 prefix: +1 from_uri: request_uri: stopper: 0 } { gw_index: 7 priority: 1 weight: 1 } On Tue, Apr 22, 2014 at 12:56 AM, Juha Heinanen <j...@tutpro.com> wrote: > 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 >
_______________________________________________ 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