Some versions of FreePBX may contain tables with invalid/problematic schemas (possibly not even valid SQL but MySQL allows it).
HAAst is complaining that it can’t sync a table without a unique index. (Although this is likely an unimportant table as Sangoma may be cleaning up their tables slowly). The best solution is to wait for an update to FreePBX which fixes the table.
If you need an immediate fix please contact Telium technical support for further assistance and workarounds. When Telium performs the installation for the customer, we might modify the MySQL table, modify PHP code, or modify MySQL tools for synchronization. Customers who perform their own installation need to thoroughly test synchronization for moving to production.
Before you perform any changes to resolve this problem ensure you have a bare metal backup, and perform testing on a staging system.
