Bug #4717
closed
Asterisk needs workarounds to work properly
0%
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
Updated by Kill Bill over 9 years ago
Can you post the contents of /usr/local/etc/rc.d/asterisk ?
Updated by Frederic Steinfels over 9 years ago
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.
Updated by Kill Bill over 9 years ago
Frederic Steinfels wrote:
It seems the start script is doing more or less the same. I have no clue why the script did not get executed.
Yeah, I was looking at the PHP code [1] and wondering whether it somehow failed to add those lines, but apparently not. No idea why this wouldn't work.
[1] https://github.com/pfsense/pfsense-packages/blob/master/config/asterisk/asterisk.inc#L389
Updated by Frederic Steinfels over 9 years ago
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.
Updated by Frederic Steinfels over 9 years ago
Update to 2.2.4 and the subsequent reinstallation of asterisk worked flawlessly without the shellcmd.
Updated by