Bug #4717
closed
Asterisk needs workarounds to work properly
Added by Frederic Steinfels over 9 years ago.
Updated over 9 years ago.
Description
In order to have the asterisk package working, I needed to install the "shellcmd" package with this configuration:
mkdir /var/run/asterisk /var/db/asterisk /var/log/asterisk /var/log/asterisk/cdr-csv
chown asterisk:asterisk /var/run/asterisk /var/db/asterisk /var/log/asterisk /var/log/asterisk/cdr-csv
both with type "shellcmd"
it seems there is something wrong with the package. this was on a fresh 2.2.2 install.
Files
Can you post the contents of /usr/local/etc/rc.d/asterisk ?
It seems the start script is doing more or less the same. I have no clue why the script did not get executed. However asterisk requires a reboot after a fresh install. I am getting tons of network errors on the shell without doing a reboot first. Maybe I was confused because of a combination of errors. Anyway, going to a more decent version of asterisk wouldnt harm because this one is losing iax connections (through openvpn) after a couple of weeks. Sometimes only a reboot will help.
Try with 0.3.2 package version, please.
One explanation might be that I have not made a reboot after installing the asterisk pbi. It might as well have happened after the upgrade process. Maybe it would have worked right away. Anyway I will update pfsense on some 2.2.3 devices and check what happens.
This shouldn't require any reboot really.
Update to 2.2.4 and the subsequent reinstallation of asterisk worked flawlessly without the shellcmd.
- Status changed from New to Resolved
Also available in: Atom
PDF