[asterisk-dev] Asterisk 11 configuration files

[Andrew Latham]

On Tue, Aug 28, 2012 at 10:09 AM, Tilghman Lesher <tilghman at meg.abyt.es> wrote:
> On Tue, Aug 28, 2012 at 4:25 AM, Michel Verbraak <michel at verbraak.org> wrote:
>> Op 24-08-12 04:35, Paul Belanger schreef:
>>
>> > I'm slowly starting to testing Asterisk 11 and noticed something about our
>> > new modules config file names:
>> >
>> > chan_motif.so -> motif.conf
>> >
>> > and
>> >
>> > res_corosync.so -> res_corosync.conf
>> > res_xmpp.so -> xmpp.conf
>> >
>> > When chan_dahdi was rewritten we moved to chan_dahdi.conf. Should we do the
>> > same for chan_motif -> chan_motif.conf?
>> >
>> > Same for res_xmpp, we should move it to res_xmpp.conf.  This would line up
>> > with the majority of resource modules config file names.  Like we did for
>> > res_corosync.conf.
>>
>> Why not create per module a new section to the modules.conf file where it
>> has a config file with at least one line specifing the main config file.
>> Something like
>>
>> [modules]
>> autoload=yes
>> load => chan_sip.so
>> noload => chan_alsa.so
>>
>> [chan_sip.so]
>> mainconfig=sip.conf    ; Expected to be in the "astetcdir" path
>> notifyconfig=/usr/local/asterisk/etc/sip_notify.conf
>>
>> [chan_iax.so]
>> mainconfig=iax.con
>> provconf=iaxprov.conf
>>
>> With this setup when a modules is ever renamed a new section is added.
>> People can customize to their own specifics.
>> An interface needs to be created which every module can call to locate it's
>> config files. Each module specifies it's own lineids to use but the
>> main/initial config file lineid is always "mainconfig".
>
> That's not a bad idea.  However, it does not negate the need for a
> default, which would be used when a corresponding section does not
> exist in modules.conf.  We do need an upgrade path, after all, since
> these sections do not currently exist, and a person upgrading one
> major version should be able to expect that the upgrade did not break
> their system.
>
> -Tilghman

Also as a resent issue outlined the module should handle a missing
config file safely and not crash (confbridge issue).  Lets start
adding the expected config files to the doxygen tag above the
load_module() standardization that I am pushing for here
https://wiki.asterisk.org/wiki/display/AST/Modules


-- 
~ Andrew "lathama" Latham lathama at gmail.com http://lathama.net ~