After
chmod 777 extensions_additional.conf
meetme_additional.conf
sip_additional.conf
sip_registrations.conf
iax_additional.conf
iax_registrations.conf
zapata_additional.conf
queues_additional.conf
asterisk works with sipgate.
Can you guys please look at our perl scripts in /usr/pluto/bin to try and make this work out of the box? Thanks.
-Thom
Hi all,
inste of doing this to change to permissin I've checked that those files had the not right owner.
Then I've only make this :
chown asterisk:asterisk extensions_additional.conf extensions_pluto_dial.conf iax_additional.conf iax_registrations.conf meetme_additional.conf provider_list.txt queues_additional.conf sccp.conf sccp.conf.template sip_additional.conf sip_registrations.conf zapata_additional.conf
The problem was that this files had root.root as owner and not the asterisk user and group, like FreePBX web interface would like to use.
Next when I make every changes in configuration and then apply config, don't ever receive the error message and all works great.
Regards
Luke
what kind of error message did you have initially?
Murcel
Hi Murcel,
see this forum messages :
http://forum.linuxmce.org/index.php?topic=8355.0
http://forum.linuxmce.org/index.php?PHPSESSID=7c0a86df1d22e8c00a602395ee3ad225&topic=8196.0
This are the common errors that happens when you try to apply for the first time you connect to freepbx and need to apply changes.
I receive this, post adding my cisco 7970 in a correct way for use it both with linuxmce and asterisk.
Bye
Luke
As Thom said, please please look at our perl scripts in /usr/pluto/bin to try and make this work out of the box and resubmit the new file to trac.
i am currently setting up the enviroment and will fix this issue.
murcel
Murcel,
I had found this script in /usr/pluto/bin sync_pluto2amp.pl
In the file there are these fixing processes:
#fix permissions on each run
`chmod g+w /etc/asterisk/*`;
# fix some permisions
`chown asterisk.asterisk /usr/share/asterisk/agi-bin/*`;
I'm not a developer but I think that could be this the script that need some arrangement, I hope . It's necessary to add the chown also for the /etc/asterisk/* .
Please tell me if it's the possible correct way to fix it.
Regards
Luke
I had a brief look for the scripts but got lost and couldn´t find where to fix.
Instead of doing a chmod 777 this would be more secure.
cd /etc/asterisk
chown asterisk:asterisk *
chmod o+r *
gadget
everything in /etc/asterisk is already owned by asterisk from what I saw. if the apache user (www-data) is in the "asterisk" group, then yeah just giving write privs to "group" should work. I couldnt see where www-data was in the asterisk group, but maybe it is already.
I just got my build environment sorted out again this morning so I will take a look at this script and get a patch ready.