FOP2 Vanilla Asterisk

Damir

Hi, guys!
We bought FOP2 and use it on FreePBX distro. There is any issues.
But we decided to install it on vanilla Aster.
It connects to manager without issues, but there is any button and user in FOP2 Manager (we installed it too). We thought that FOP2 could work with vanilla Aster too. We've fop2 base with mysql user and password delegation, but there aren't any tables in that.
Is there any full workaround for installing FOP2 on vanilla aster? in your topics there is information about handle setting among using FOP manager, which from that is usable?
Also, we've been getting this error when logging out FOP2 Manager:
"Warning
You must have a functions-custom.php file in the manager directory.
FOP2 Manager - Version 1.1.4"
But functions-custom.php there is in FOP2/admin folder already.
Please help to understand all of this)

Damir

Haven't any idea?))))) Silence is all around.....

nicolas

People tend to enjoy leisure time from friday night until next monday morning.. so you sure will find silence here.

FOP2 works perfectly fine with vanilla Asterisk.. and in the same way you had to work your ?!?2 off to configure vanilla Asterisk, you will have to with FOP2.

Asteirsk did not configure your phones itself, did it? No, you configured them by hand, and configured Asterisk by hand also to make them work.

Expect the same with FOP2. if you have vanilla, you either have to tweak functions-custom.php in the FOP2 manager, or you can edit buttons_custom.cfg file and configure buttons manually as it is described in the online documentation (you can use buttons.cfg.sample as a base also).

Editing the FOP2 manager functions-custom.php file is not that hard if you know PHP, read the functions-xxxx.php family files to see how other backends work.

Best regards,

Damir

Thanks! What about mysql base for FOP2? Should we create it out?
And what about this warning till FOP2 manager logoff:
"Warning
You must have a functions-custom.php file in the manager directory.
FOP2 Manager - Version 1.1.4"

That file presents in manager directory, but error comes again.
And how we can use FOP2 manger? There aren't any buttons and users in it while we've configured them in *.cfg files....

nicolas

You must create the fop2 database and set correct mysql credentials in fop2/config.php and fop2/admin/config.php. The mysql user must have create permissions also, as when you log into the fop2 manager it will create the needed tables if they are not present automatically. Once tables are created, you will be able to configure things, otherwise the manager won't work. You can enable debug in config.php also to see the actual errors (About database issues) as it seems you do not have the database created.

Best regards,

Damir

Trip with vanilla Asterisk is going on((((((((((
We've bought out 40$ license, please help us!!!
Asterisk 1.8.32.3 on CentOS 7
Guys, at last we have several issues:
1. Supervised transfer doesn't work - works only blind transfer in panel;
2. We can't see outgoing and incoming caller id in extension buttons while making call;
3. After FOP2 base created, buttons added manually to buttons.cfg are absent among extension buttons in the panel.
......
Attached screen and buttons.cfg, fop2.cfg files.

Damir

We've solved out 1 and 3 issue...
There is only second question described in attached screenshot...!!!!!

nicolas

If you set

privacy=clid

You are telling FOP2 to NOT DISPLAY callerid. So what you see is exactly what you have configured.

Remove privacy=clid line from all your buttons configuration and you will see clid/dialed numbers

Best regards,

Damir

Thanks a lot....Could you tell me.....why we can't see any call in call history? mysql database created....

Damir

Thanks a lot....Could you tell me.....why we can't see any call in call history? mysql database created....

Damir

It becomes an error till opening it in panel((((

nicolas

I cannot say without looking at the error, most probably mysql credentials are not correct or the cdr database/table is not well set in config.php or your cdr schema does not match what FOP2 expects. You have to enable debug in config.php and check if you see any specific DB errors there.