9 Jun
2023
9 Jun
'23
9 p.m.
harneet singh writes:
"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."
Can someone explain/ share a sample lcr_rule table entries for the From
Username that can be matched against the incoming sip message for gw
selection? Do we need to manually create an mtree by the name "*lcr*".
Asking based on the below section in LCR documentation? Any pointers are
highly appreciated.
Default name of lcr module mtrees tname is "lcr". If you want to
include an mt_tvalue, e.g., "Nordic", in your lcr_rule, then caller URI
userpart must match a mtrees row tprefix, where tname=lcr and tvalue=
Nordic. Nordic rows could be like this:
lcr +45 Nordic
lcr +46 Nordic
lcr +47 Nordic
lcr +354 Nordic
lcr +358 Finland
It is not really intended to maintain lcr tables manually. You would
need, e.g., a web based app for it.
-- Juha