[asterisk-bugs] [AsteriskNOW and Packages 0017442]: After the AsteriskNOW 1.7.0 yum update chan_sip and pbx_config could not initialize

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=17442 
====================================================================== 
Reported By:                vmikhelson
Assigned To:                qwell
====================================================================== 
Project:                    AsteriskNOW and Packages
Issue ID:                   17442
Category:                   Installer Issues
Reproducibility:            have not tried
Severity:                   major
Priority:                   normal
Status:                     assigned
JIRA:                        
====================================================================== 
Date Submitted:             2010-06-02 03:46 CDT
Last Modified:              2010-06-02 23:35 CDT
====================================================================== 
Summary:                    After the AsteriskNOW 1.7.0 yum update chan_sip and
pbx_config could not initialize
Description: 
Applied AsteriskNow 1.7.0 via yum update. Updated modules in FreePBX as
instructed.

Asterisk is not functional as the dialplan and the SIP configuration fail
to load.
====================================================================== 

---------------------------------------------------------------------- 
 (0122863) vmikhelson (reporter) - 2010-06-02 23:35
 https://issues.asterisk.org/view.php?id=17442#c122863 
---------------------------------------------------------------------- 
Ok, here is the solution I devised. It runs Asterisk as 'asterisk' user and
'apache' group. Tested by 'amportal restart' and by the system reboot.

The only security implication I see Asterisk and Apache become close
relatives which I believe is kind of a necessity in the FreePBX environment
where Apache modifies Asterisk objects and Asterisk needs access to what
was modified by Apache. Further refinement is always possible by assigning
more granular file / directory permissions.


1. Make sure user 'apache' is a member of the 'asterisk' group or run
'gpasswd -a apache asterisk'

2. Make sure user 'asterisk' is a member of the 'apache' group or run
'gpasswd -a asterisk apache'

3. Add the following line at the end of the /etc/amportal.conf:
              AMPASTERISKGROUP=apache

4. Run 'chmod g+w /var/log/asterisk/full'

5. Optionally add the following line to the
/var/lib/asterisk/bin/freepbx_engine, immediately before 'Echo "Asterisk
Stopped"' line in the stop_asterisk() function:
              sleep 20

The last enhancement allows the asterisk exit gracefully if it has a
lengthy dialplan to unregister. Absolutely not related to the rights
issue... 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-06-02 23:35 vmikhelson     Note Added: 0122863                          
======================================================================