[Users] #DEFINE equivalent?
bogdan at voice-system.ro
Mon Aug 29 11:37:30 CEST 2005
I'm for m4'ing (for the moment) for two reasons:
1) since we can do it with m4, I prefer to use the cycles for
something still missing;
2) using dynamic parameters (like via AVPs) reduce the performance -
time to look for the AVP and most critical the impossibility of calling
fixup functions at startup (which will force to fix params at runtime,
for each processing).
regarding the record_route_preset() - do you use dynamic parameters or
dynamic rr URI?
Kanakatti Mahesh Subramanya wrote:
> Actually, thats exactly what I'm using right now.
> Its just the difference 'tween m4'ing everything, vs. having some
> limited de-referencing capability built into the config file.
> Then again, now that I think about it, most everything that you can
> that requires hard_coding values can also be done using AVPs in some
> form or the other
> e.g. prefix(), strip(), etc. can be done through avpops.
> The only one that I can't think of an easy work around is
> So, short of some *very* fancy AVP logic, I guess that *that* would be
> the only place where one woudl need to actively hardcode stuff and/or
> use m4.
> I could live with that...
> p.s. anybody thinking of AVPing record_route_preset()
> Elena Ramona Modroiu wrote:
>> you could try m4 macro processor http://www.gnu.org/software/m4/ .
>> Kanakatti Mahesh Subramanya wrote:
>>> It would be useful if we could DEFINE parameters in the .cfg file
>>> define SOME_IP=184.108.40.206
>>> and somewhere later in the file
>>> Speaking as someone who has to manage openser.cfg instances across
>>> multiple servers (not to mention test environments!), it would
>>> certainly make my life a heck of a lot easier....
>>> Users mailing list
>>> Users at openser.org
>Users mailing list
>Users at openser.org
More information about the sr-users