Although unusual, this suggests that your FreePBX AstDB is corrupt or incomplete, and FreePBX is missing database entries needed by the dialplan. This can occur if you have installed a buggy FreePBX update, or FreePBX has crashed, etc.
There are four possible ways to correct the Asterisk database.
- Restore the node from a backup
- Request that FreePBX regenerate the Asterisk database using this BASH command (after stopping Asterisk). Note that some versions of FreePBX don’t support this command:
curl https://SERVER/freepbx/admin/config.php?type=setup&display=devices&action=resetall
- Recreate the Asterisk DB manually.
- Stop FreePBX
- Delete the /var/lib/asterisk/astdb.sqlite3
- Start FreePBX
- Edit & Submit each user
- Click apply
- Stop FreePBX on both peers and copy the file /var/lib/asterisk/astdb.sqlite3 from the working peer to the malfunctioning peer. (Be sure Asterisk is stopped on both systems before trying this).
Once corrected, be sure to resolve the underlying FreePBX/configuration/etc issue. As well, ensure that you have set the Asterisk database to synchronize in HAAst’s configuration file.