Re: [SR-Users] RFC: dispatcher refactoring to use xavp and options for attributes

2018-06-06 Thread Daniel-Constantin Mierla
Hello, something like that, maybe the parameter value will be only the name of the xavp, similar to xavp_cfg for registrar. For attrs and extra columns, I was thinking of concatenating all of them in 'attrs' field and have also separate those with a specific meaning (like socket, weight, ...)

Re: [SR-Users] RFC: dispatcher refactoring to use xavp and options for attributes

2018-06-06 Thread Luis Azedo
Hi Daniel, love the idea! just to be sure i understand..., current params declaration modparam("dispatcher", "dst_avp", "$avp(ds_dst)") modparam("dispatcher", "attrs_avp", "$avp(ds_attrs)") new params declaration modparam("dispatcher", "dst_xavp", "$xavp(ds_dst)") ##modparam("dispatcher",

[SR-Users] RFC: dispatcher refactoring to use xavp and options for attributes

2018-06-06 Thread Daniel-Constantin Mierla
Hello, I am starting a discussion here about my plans to do a bit of refactoring to dispatcher module and gather some feedback if people think of other improvements. 1) First is about moving from using avps to xavps. It should simplify at least the config in terms of modparams, but also makes it