FreePBX Fop2 string (123) “256, SQL Error: DESC asterisk.parkinglot

One of our clients upgraded their stable FreePBX. After upgrading they have also decided to update the FOP2 there were using, and they did at the end. FreePBX version from 13  to 14, and FOP2 version 2.31.20. The Fop2 upgrade process went well except for the error shown below in the screenshot. During the upgrade process, it showed “SQL Error: DESC asterisk.parkinglot” error message and the error message occurred four times.

string (123) "256, SQL Error: DESC asterisk.parkinglot
Table 'asterisk.parkinglot' doesn't exist (/var/www/html/fop2/admin/dblib.php, 108"
═════════════════════════════════════════════════
Called from .../functions.php:2573 [fop2manager_error()]

SQL Error: DESC asterisk.parkinglotTable 'asterisk.parkinglot

Besides that SQL Error: DESC asterisk.parkinglotTable error, from Fop2 admin panel updating User Preferences (under “Automatic Popup” setting “Connect” “Yes“) was not taking place as well.  Refer the screenshot below.

Fop2 - Table 'asterisk.parkinglot' doesn't exist

To resolve this a table called “parkinglot” was created within the asterisk database.

create table parkinglot (
`id` int(11) NOT NULL AUTO_INCREMENT,
`data` varchar(30) NOT NULL,
`keyword` varchar(30) NOT NULL,
`name` varchar(20) NOT NULL,
`channel` varchar(20) NOT NULL,
`type` varchar(20) NOT NULL,
`exten` varchar(20) NOT NULL,
`context` varchar(20) NOT NULL,
`context_id` varchar(20) NOT NULL,
PRIMARY KEY (`id`)
) ENGINE=InnoDB AUTO_INCREMENT=56 DEFAULT CHARSET=utf8

Note: Fop2 2.31.20 is not compatible or is buggy with Asterisk 13. IT will continue to complain throwing “asterisk.parkinglot’ doesn’t exist” message. Auto popup on call connect feature will cause a double window open on chrome browser using chrome’s FOP2 extension.

Leave a Reply

Your email address will not be published. Required fields are marked *