<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#666666">
<div class="moz-cite-prefix">Op 24-08-12 04:35, Paul Belanger
schreef:<br>
</div>
<blockquote cite="mid:5036E88D.1000605@polybeacon.com" type="cite">I'm
slowly starting to testing Asterisk 11 and noticed something about
our new modules config file names:
<br>
<br>
chan_motif.so -> motif.conf
<br>
<br>
and
<br>
<br>
res_corosync.so -> res_corosync.conf
<br>
res_xmpp.so -> xmpp.conf
<br>
<br>
When chan_dahdi was rewritten we moved to chan_dahdi.conf. Should
we do the same for chan_motif -> chan_motif.conf?
<br>
<br>
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.
<br>
<br>
Thoughts?
<br>
<br>
</blockquote>
<font size="-1"><font face="DejaVu Sans">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<br>
<br>
[modules]<br>
autoload=yes<br>
load => chan_sip.so<br>
noload => chan_alsa.so<br>
<br>
[chan_sip.so]<br>
mainconfig=sip.conf ; Expected to be in the "astetcdir" path<br>
notifyconfig=/usr/local/asterisk/etc/sip_notify.conf<br>
<br>
[chan_iax.so]<br>
mainconfig=iax.con<br>
provconf=iaxprov.conf<br>
<br>
With this setup when a modules is ever renamed a new section is
added. People can customize to their own specifics.<br>
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".<br>
<br>
This is just an idea.<br>
<br>
Regards,<br>
<br>
Michel.<br>
<br>
</font></font>
</body>
</html>