Open LipkeGu opened 5 years ago
Update 1:
update 2
Hi @LipkeGu,
I like the idea of transforming config to uci. However I miss the possibility of configuring modules that your provided uci config does not handle. Have you thought about it?
@LipkeGu Have you considered using asterisk-realtime + sqlite3 instead. Most of the asterisk config can be moved to a database (odbc, mysql, postgresql, sqlite3 and/or ldap). For example sippeers / iaxpeers / voicemail / sccp / queues / musiconhold / meetme / confbridge and even dialplan (there are some caveats with extensions.conf though). That should/would get rid of a lot of the clutter and might make a nice frontend simpler. See:
Note:You would have to make sure to retain this sqlite3 db over openwrt upgrades though. Also note: setting up realtime can be a little bit daunting though (getting extconfig.conf + res_sqlite.conf right the first time). but once it is up and running it works really well and reduces the need for "module reload [all]" in a lot of cases.
When you are going to use files: do note that almost all asterisk config files parameters have sensible defaults don't have to be defined, which can reduce the size of files considerably.
Since a long time we have the problem that asterisk is very unfriendly to configure. It contains a lot of config files which are mostly full commented out.
i decided to write a uci file togehter with an init script to make it easier and flash friendlier. my way is to move "our" generated config files into
/tmp/asterisk/
instead of overwriting the/etc/
this allows us a first step to make configs upgrade persistent.In fact we cant cover all situations but generate a starting base to make asterisk more useable for embedded devices.
/etc/init.d/asterisk contains so far:
Im currently using it and it makes (except the dialplan patterns) the life of my box alot easier... Any suggestions?