This could be caused by a number of things, couple things I would check right away would be:
1. Crontab has ADMIN_keepalive_ALL.pl set to run every minute on every server.
2. The VARactive_keepalives are set correctly on each server within /etc/astguiclient.conf (bear in mind if making changes that keepalives 5, 7, 9 and E must only be active on one of the servers within the cluster)
3. Server entries in the GUI have the correct IP, asterisk version listed and have the Active Asterisk server set to Y and Generate Conf Files set to Y.
4. The AMI user credentials are correct for the server entry and match what's in /etc/asterisk/manager.conf
If this all looks good, I'd comment out temporarily the ADMIN_keepalive_ALL.pl crontab entry so I can run it manually after making some changes that would trigger an asterisk reload (such as changing phone details).
I'd make some changes to a phone or something else that would trigger a reload.
I'd then check the server had "Rebuild Conf Files" set to "Y" (This should happen automatically when you make changes affecting the asterisk config for that server).
I'd open two sessions to the server, one to issue the below command, and the other to watch the output of the asterisk cli when I do so. (much easier when no dialing in progress).
- Code: Select all
/usr/share/astguiclient/ADMIN_keepalive_ALL.pl --debugX
Then in the output look for "generating new auto-gen conf files", "writing auto-gen conf files" and "reloading asterisk modules" along with any errors that may appear during those processes,and look at asterisk cli to see if there was any authentication failures/errors or if the reload happened.
(If you resolve the issue, remember to uncomment the ADMIN_keepalive_ALL.pl entry in the crontab so it runs every minute as it should).