There already is a special character to tell asterisk not to parse a line... its: ";" that is why the default configuration is completely filled with lines that start with ; its considered a comment character to asterisk and will make it ignore the line... you'd just want to add some extra characters to your program probably... something that would denote "this is a config line for script A"
so if you make your lines something like ;A: then you could have another character for script B that would have lines in the same file like: ;B: or w/e... its up to you to determine what characters you'd want to use beyond the ; to denote config lines for your other programs. -- Matt On Fri, May 22, 2009 at 3:23 AM, Olivier <oza-4...@myamail.com> wrote: > Hi, > > To a large extend, Asterisk's /etc/asterisk/*.conf configuration files > conform to a format such as: > > [section1] > key1=value1 > key2=value2 > > [section2] > key1=value1 > key2=value2 > ... > > To increase coherence when running custom-made application in Perl, Java, > PHP, ...) and Asterisk on the same platform, I'm wondering if could extend a > bit Asterisk's config files instead of duplicating data in an independant > config file. > > For instance, an app that uses Manager interface needs to be configured > with : > - the Asterisk manager interface IP address, > - a username and secret. > > The later 2 parameters are included /etc/asterisk/manager.conf but the > first one is not. > So instead of writing an independant myapp.conf holding all 3 parameters, > should I only add the first parameter to existing manager.conf file ? > > Doing this, I would have to make sure that when Asterisk is parsing its > config file, it doesn't stop when it reads unkown supplementary parameters > (those added for custom app). > It seems to be the case now with 1.6.1 : a NOTICE warning is sent but it > doesn't really hurt. > [May 22 09:15:32] NOTICE[15917]: manager.c:3903 __init_manager: Invalid > keyword <foo> = <bar> in manager.conf [general] > > Maybe, adding a keyword that would tell Asterisk to skip reading this > config file line would be a plus (avoiding warnings and collision with new > keywords). > What do you think ? > > Then, my next question, is there widely available librairies to parse > Asterisk's config files-like files ? > > Regards > > > _______________________________________________ > -- Bandwidth and Colocation Provided by http://www.api-digital.com -- > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users >
_______________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users