John Cahill writes:
I'd like to build an LCR solution that routes on
both CLI & destination e.g.
CLI matches ^\+49*, destinations matches ^\+44* => route to gateway 5
for a large rule set (~ tens of thousands). Any recommendations for
which modules to use?
Check if LCR module scales for our use case. It does support your
routing requirement:
A gateway matches a request if user part of Request-URI matches
"prefix", caller URI matches "from_uri" pattern, caller URI
userpart
matches mtree with "mt_value", and callee URI matches "request_uri"
pattern in a tuple that is associated with the gateway.
-- Juha