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 record_route_preset()
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...
cheers
p.s. anybody thinking of AVPing record_route_preset()
Elena Ramona Modroiu wrote:
Hi,
you could try m4 macro processor http://www.gnu.org/software/m4/ .
Regards, Ramona
Kanakatti Mahesh Subramanya wrote:
It would be useful if we could DEFINE parameters in the .cfg file e.g. define SOME_IP=1.2.3.4 and somewhere later in the file record_route_preset("SOME_IP;nat=yes");
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....
cheers
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users