Everything has been working fine for weeks.  Have taken the system down and brought it back up on several occasions, but as always happens with a demo, I was going to demo the Asterisk PBX with phones on 4 mesh nodes at a radio club meeting last night.  Murphy raised his ugly head.

The phones seemed to find the TFTP server just fine and configured themselves as expected.  But no cigar.  All phones just gave the re-order tones when trying to dial another extension.

Logging in to the FreePBX Admin program showed a Server Status of ERROR for Asterisk while other servers were listed as OK.

Not a Linux guru, so looking for help as where to turn next.

Again, all had been working just fine until I tried to do a real demo.

Steve G./N4TTY

Sounds like it might have been a fluke and Asterisk failed to start. Did you try an "amportal restart" in a SSH Console? If so, what was its output? How did your setups at your home and club meeting differ? Does/Did your home/club-setup mesh network have internet services made availabe? Did you install the fake hardware clock? Do you shutdown the Raspberry Pi properly through a terminal window?

As these type of things are a case-by-case basis, I would be interested in seeing your log files when this error occurs. You can find your log files on the Raspberry Pi here: /var/log/asterisk/ (that last part "/asterisk/" is a guess. It could be something different/similar).

Sometimes, it might just be easier to backup your configuration files and just re-image the Raspberry-Asterisk package to the SD Card (as that process does not take too terribly long). And afterwords...paying close attention to re-installing the fake-hwclock and properly shutting down the Pi. I have yet to experience any issues when paying close attention to the above items.