Bug 286718 – FEATURE REQUEST: install asterisk's sample dialplan *.conf to anywhere but /etc/asterisk/

• Product: Gentoo Linux
• Status: RESOLVED DUPLICATE

[Description Jeremy Johnson 2009-09-27 23:25:18 UTC]

It would be nice if net-misc/asterisk installed astererisk's sample dialplan *.conf to e.g. /usr/share/asterisk/<version>/
Then the user could decide, which if any, of the new configuration options should be include in their dialplan.
For example, I keep my dialplans in
/etc/dialplans/<freepbx-asterisk-version>
with a symlink /etc/asterisk -> choosen dialplan
so that asterisk can configure itself

Reproducible: Always

Actual Results:  
For for than a year, I had put off upgrading from asterisk 1.4 to 1.6
But asterisk-1.4 got masked pending removal from portage.
So I decided to test out asterisk-1.6

I backed up all of portage's asterisk*-1.4 ebuilds,
backed up my /etc/dialplan/freepbs-asterisk-1.4
and did a quickpkg of asterisk*-1.4 files + zaptel

Then I unmasked asterisk-1.6 and dahdi, 
uninstalled zaptel and replaced with dahdi-2.2.0.2
ran dahdi_cfg to generate /etc/dahdi/system.conf (replacement for /etc/zaptel)
and upgraded to asterisk-1.6.1.6

Then etc-update wanted to change ~50 files.
So I manually merged some of the files if the new file deleted lines, 
and updated others that didn't delete anything (other than comments)

I ended up with a functioning but partially broken dialplan.

So I untarred freepbx-2.6.0RC2
then copied the freepbx dialplan stubs back to /etc/asterisk
cd amp_conf; 
for f in `find . -name *.conf`; do B=`basename $f`; cp $f /etc/asterisk/$B; done
Then I set
/etc/asterisk/asterisk.conf:dahdichanname = no
/etc/amportal.conf:ZAP2DAHDICOMPAT=true
and let freepbx update (from the database backend) the supplemental configuration files which get included from the stub files.



Expected Results:  
Asterisk should be able to upgrade without overwriting users' dialplan.
I know I could point /etc/asterisk symlink to (say) /etc/dialplans/samples
but sometimes one does "emerge -uvDN world" and it would be nice not to have to
shutdown the phone system, point /etc/asterisk to somewhere innocuous, let things emerge, then restore symlink and restart phone system.



I know I could probably use CONFIG_PROTECT to spare my dialplan, 
but the configuration files from asterisk are merely templates with mostly comments, and some arbitrary phones and users. They are not a real working dialplan. My 2 cents suggestion is to put them in /usr/share/asterisk/<version>/

[Comment 1 Sebastian Luther (few) 2009-09-28 10:28:27 UTC]

*** This bug has been marked as a duplicate of bug 286574 ***