You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If someone builds/packs it's own Asterisk, or uses some pre-built Asterisk packages (like the ones provided by Debian), it will most probably have a systemd service file that he can use to start/stop Asterisk.
In those situations, it will be a nice addition if someone that starts/stops Asterisk via fwconsole start/stop/restart commands will downwards cause the invocation of systemctl start/stop/restart asterisk.service commands.
I've successfully tested using systemctl to start/stop Asterisk in my system with these patches to FreePBX libraries:
My suggestion would be to add a config variable to /etc/freepbx.conf that would control which commands are used to start/stop Asterisk gracefully.
By default, the old behaviour of stopping with asterisk -rx "core stop gracefully" and starting with safe_asterisk would be used.
When that new config variable was set to a value that would cause the usage of the new start/stop commands, systemctl would be used to start/stop Asterisk.
The text was updated successfully, but these errors were encountered:
FreePBX Version
FreePBX 17
Improvement Description
If someone builds/packs it's own Asterisk, or uses some pre-built Asterisk packages (like the ones provided by Debian), it will most probably have a systemd service file that he can use to start/stop Asterisk.
In those situations, it will be a nice addition if someone that starts/stops Asterisk via
fwconsole start/stop/restart
commands will downwards cause the invocation ofsystemctl start/stop/restart asterisk.service
commands.I've successfully tested using
systemctl
to start/stop Asterisk in my system with these patches to FreePBX libraries:My suggestion would be to add a config variable to
/etc/freepbx.conf
that would control which commands are used to start/stop Asterisk gracefully.By default, the old behaviour of stopping with
asterisk -rx "core stop gracefully"
and starting withsafe_asterisk
would be used.When that new config variable was set to a value that would cause the usage of the new start/stop commands,
systemctl
would be used to start/stop Asterisk.The text was updated successfully, but these errors were encountered: