Thanks for the clarification. That wasn't clear
from the
documentation wiki. Is there some standard documentation format we
can establish to clearly show what functions accept variables and what
don't?
the readme of the modules should be updated, somehow this info was
forgotten. I will take care soon.
Cheers,
Daniel
On Thu, Jul 15, 2010 at 4:53 AM, Daniel-Constantin Mierla
<miconda(a)gmail.com <mailto:miconda@gmail.com>> wrote:
Hello,
On 7/15/10 9:15 AM, Vic Jolin wrote:
I sure would love to know if this will work
On Thu, Jul 15, 2010 at 2:01 PM, Geoffrey Mina
<geoffreymina(a)gmail.com <mailto:geoffreymina@gmail.com>> wrote:
How difficult would it be to make ds_select_domain(set, alg)
accept a pseudo variable for the "set" argument? I would
like to map the $rU to a specific dispatcher set via a
database table. I suppose i could just hard code three or
four sets with a conditional if() statement, but I would
prefer to make it a little more dyanimc.
Correct me if I am wrong in my assumption that
ds_select_domain() doesn't accept pseudo variables.
the function accept variables in both parameters, set and alg.
Cheers,
Daniel
Thanks.
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users
mailing list
sr-users(a)lists.sip-router.org
<mailto: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(a)lists.sip-router.org <mailto:sr-users@lists.sip-router.org>
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
--
Daniel-Constantin Mierla
http://www.asipto.com/