Hi Juha,
for such case, I built a string with the values separated by semicolon
(or other delimiter) and based on the needs, either I do search to match
something or a break it with transformations or Lua scripts.
A native version would be good to have, but should be in the next devel
cycle (3.3.0) -- we are in testing phase for 3.2.0. I prefer to refactor
a bit, to cope better with major changes and specific structures -- at
least the part with value type to be per tree and use xavps for such
composed structures.
If you need it and code it, please push it to a personal branch on GIT
for now.
Thanks,
Daniel
On 8/25/11 8:55 PM, Juha Heinanen wrote:
daniel,
if i have understood correctly, current mtree implementation does not
allow more than one value per node (prefix) in the three. it some cases
it might make sense to have more that one value.
for example, if an mtree is used to map telephone numbers to values, one
could have:
prefix value
0046 sweden
0046 nordic country
0046 eu member
0046 european country
00375 belarus
00375 european country
and when a telephone number, such as 004692345678 or 0037592345678 is
matched, all values that the prefix has, would be assigned to an avp.
is is ok for you as author of mtree module, if i try to extend it so
that a prefix could be associated with more than one value?
-- juha
_______________________________________________
sr-dev mailing list
sr-dev(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
--
Daniel-Constantin Mierla --
http://www.asipto.com
Kamailio Advanced Training, Oct 10-13, Berlin:
http://asipto.com/u/kat
http://linkedin.com/in/miconda --
http://twitter.com/miconda