Is now a bad time to consider jumping into Incredible, and Raspberry Pi, and I should wait to see if the outcome of the Sangoma takeover ends up successful, as far as Incredible goes, or it effectively destroys its value, and thus its reason for existence?

Any feedback from you guys would be helpful, thank you.

[WM: The new 16-15 builds (including 16-15.2 for CentOS coming Sep. 16) should buy you about four years of safety even with Sangoma at the helm. A lot can improve in that time frame.]

[WM: Gotta love Sangoma employees that post back-slappin’ attaboys when not a single person has even tested the new code. Not only does it blow up whenever it’s run (see below), but even after manually fixing that bug, it (still) doesn’t restore voicemail data and settings from the backup. Way to go team Sangoma.]

Backup extracted to /tmp/backup/fbcb7460-44db-4626-a727-b4b868c9184d. These files will remain until a new restore is run or until cleaned manually.
Loading manifest to memory
Loading astdb to memory
Parsing out SQL tables. This may take a moment depending on backup size.
Found 2 database files in the backup.
File named: /tmp/backup/fbcb7460-44db-4626-a727-b4b868c9184d/mysql-2.sql.gz
Detected file /tmp/backup/fbcb7460-44db-4626-a727-b4b868c9184d/mysql-2.sql.gz as the PBX (Asterisk) database. Attempting restore
Extracting supplied database file mysql-2.sql.gz
Loading supplied database file mysql-2.sql
SQLSTATE[HY000]: General error: 1 near "COMMENT": syntax error


Sorry to hear you guys ran into an issue related to Backup and Restore being dependent on a the commercial module SysAdmin. I think that was unintentional, and I believe we have that dependency removed now (in the above linked bug on the issue tracker).

Best wishes,

Matthew Fredrickson

Also, after restoral, the admin passwords do not match so Asterisk does not correctly restart. This is a known difference between FreePBX and IncrdiblePBX passwords on the database.

Progress is, at least, being made.