Hello,
On 3/24/12 1:25 PM, Alex Balashov wrote:
I am not sure that exporting #defines to third-party language API modules makes
much sense just because some user thought it would be neat.
The #!... constructs are all intended as preprocessor directives, to make
easier management of global con
I am not sure that exporting #defines to third-party language API modules makes
much sense just because some user thought it would be neat.
The #!... constructs are all intended as preprocessor directives, to make
easier management of global constant values in the native Kamailio config
environ
Hello,
On 3/23/12 2:00 PM, Asgaroth wrote:
I'll check this option out, thanks for the tip Alex.
it is a good way to do, $sel(...) are available in Lua, @... format not,
but they are the same, just different access mechanism.
I guess the other option too, which I have not tried, is to possib
I'll check this option out, thanks for the tip Alex.
I guess the other option too, which I have not tried, is to possibly
pass in the values as lua script parameters.
On 23/03/12 12:12, Alex Balashov wrote:
Have you considered using selectors/cfg_get variables instead?
They are also a common
Have you considered using selectors/cfg_get variables instead?
They are also a common way to store various types of "global" values/constants,
with the difference that they can be accessed at run time using PV container
functions instead of set at preprocessing.
myproject.local_ip = "1.2.3.4"
Hi All,
I am looking at writing a lua function that would really benefit from
accessing "variables" that I would have defined by using the #!define
statement. Is this at all possible? I've tried looking at the
documentation surrounding lua and kamailio, but I cannot see how I would
access it.
