Freepbx hangup the calls when you apply settings

I wonder if it’s normal for freepbx to turn off active calls when we apply any settings on your web interface?

If this is normal … is there any way to change?

tks!

It’s not typical. I reload the system all the time and I’ve never lost a call.

ok!
can you help me? Do you know what could be happening?

Nope - it’s literally never happened to me in 15 years of using Asterisk.

OK!
Let’s see if anyone has already gone through this.

thank you

this means asterisk is likely crashing for some reason…

in ssh run “asterisk -r” for thr CLI then click reload. If you get kicked out then you know asterisk crashed.

then you will want something like https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace

People here like information, like log extracts or versions before they’ll really get involved. Without that you’re not likely to inspire confidence for busy people.

1 Like

OK!
I did the commands, but did not leave the CLI, only notified with many WARNING and some ERROR.

Only restarts asterisk when I apply the configurations through the web interface

OK!
I did the commands, but did not leave the CLI, only notified with many WARNING and some ERROR.

Only restarts asterisk when I apply the configurations through the web interface

ip-XXXXCLI>
[2017-06-07 18:13:41] ERROR[19912]: config_options.c:652 aco_process_config: Unable to load config file ‘acl.conf’
[2017-06-07 18:13:41] WARNING[19912]: named_acl.c:424 ast_named_acl_reload: Could not reload ACL config
ip-XXXX
CLI>
Disconnected from Asterisk server
Asterisk cleanly ending (0).
Executing last minute cleanups
You have new mail in /var/spool/mail/root
[root@XXXX ~]#

More info:

Versions?
Distributions?
Hardware?

This sounds like a typical RasPBX problem (they lose files all the time), but the ACL file not being available could be enough to kill Asterisk, which would drop all your calls. Get the backtrace and let us know what else you find.

Freepbx 13
Centos 7
Amazon EC2

I’ll arrange the backtrace.

Had the same Problem with Asterisk 13.14.0.
Remove the two includes in /etc/asterisk/http.conf did the trick for me.

;#include http_additional.conf
;#include http_custom.conf

Had the same issue on on FreePBX 13.0.192.8, Asterisk 13.14.0, Linux 4.4.0-78-generic #99~14.04.2-Ubuntu and thanks for this trick. But what is the problem and why it is?

This is not a fix, this is a hack, it will cause tampered file warnings and your fix will break with module upgrades. There is content in the one of the two included files that is causing Asterisk to crash, you need to identify what it is.

see here: Asterisk Restarts After Clicking Apply Config Changes

After I remove the two items, now does not apply the settings, and this error appears:

exit: 1
Unable to connect to remote asterisk (does /var/run/asterisk/asterisk.ctl exist?)
Exception: Unable to connect to Asterisk through the CLI in file /var/lib/asterisk/bin/retrieve_conf on line 41
Stack trace:

  1. Exception->() /var/lib/asterisk/bin/retrieve_conf:41

Inverse Progress!

You went from crashing and restarting to crashing and not restarting. Time to roll back that change and start looking for the reasons why your system is crashing. Blindly applying random changes from people that might have a problem that looks similar to yours is usually the road to “just start over from the Distro”.

Yes!
I’ve reset the settings!
In the forum suggested above, it is recommended to downgrade the asterisk version.
Do you find it viable?

1 Like

There is a bug in asterisk 13.14.0. Upgrade to lastest, or downgrade, just don’t stay with that one. I imagine that is you use Asterisk-version-switch command you can select version 13 and reinstall the latest, or YUM - upgrade, or run one of the upgrade scripts available on FreePBX.org (use google to find quickly)

The bug crashed asterisk on reload. An asterisk monitor will restart it, but there is a delay.