Tutorial: Installing FOP2 on Elastix & other Freepbx Dist.

[nicolas]

One thing is the server connection to the asterisk box

Another thing is your browser trying to connect to fop2 server

You are --testing the former

You have problems with the later.

To troubleshot CLIENT problems, there is a nice troubleshoter that might help you out

http://support.asternic.biz/index.php?/ ... tep/View/4

My guess is that you have a firewall in place preventing connection to port tcp/4445 OR the fop2 service is not started

[edem]

Hello Admins,

Please help me with my issue

I installed Asterisk PBX Distro 64bit:

Stable-3.211.63-10
FreePBX 2.11, Centos 6.3
Asterisk 1.8

After that installed fop2 trial version.

When I checked

/usr/local/fop2/fop2_server –test

I have this is message in console

Flash Operator Panel 2 - No valid license found. Demo Mode

Can't listen to port 4445

Early I don't installed previous version FOP.
How I can fix this problem?
Thank you in advance!

[nicolas]

It is --test (dash dash test)

It seems you are entering only one dash, so when you type that fop2 tries to execute normally, and if it is already running, it will say that it can listen to port 4445.

Best regards,

[edem]

Thank you!
This is really fixed my issue.

Best regards,
Edem

[julianjpayne]

I have a problem installing FOP2 admin on freepbx. I have made sure that I have the park and queue modules enabled, I have even re-installed them. But I still get the 'Please wait while module actions are performed' hanging upon trying to install the module.

I am using FreePBX 2.11

Any help would be greatly appreciated

[nicolas]

what fop2admin version are you having problems with?

[ictiucn]

Hi All,
Before I get the login screen the message "something went wrong" appears briefly. When I am logged in to FOP2 I only see a menu bar with Filter, Dial, and Available buttons on the left and a Logout button on the right. No buttons for extensions, queues etc. The placeholders for the extensions, queues etc areas briefly show up after I login but they are not filled in and disappear. The screen remains blank with a dark grey status bar at the bottom ("FOP2 - Version 2.28 - Lite Version - Limited to 15 extensions . Buy it now for unlimited extensions. If you already have a code enter it here"),

I Installed the i386 version fop2-2.28-centos-i386(1).tgz according to the tutorial.
on PBX in A Flash :
PIAF Installed Version = 2.0.6.5
FreePBX Version = 2.10.1.16
Running Asterisk Version = 11.10.0
Asterisk Source Version = 11.10.0
Dahdi Source Version = 2.9.0
Libpri Source Version = 1.4.14
Operating System = CentOS release 6.5 (Final)
Kernel Version = 2.6.32-431.1.2.0.1.el6.i686 - 32 Bit

I uninstalled FOP ( 1) amportal stop_fop, 2) in freepbx:module admin remove the fop framework. 3) and then reboot)

"/usr/local/fop2/fop2_server --test" gives:
Flash Operator Panel 2 - License file fop2.lic not found.
Running in Demo Mode
Connection to manager OK!

I enabled a debug log with options "-l /var/log -X 15". This produced a log in which I can find no obvious errors. All extensions and one queue on my system seem to be found,

Any idea what is wrong?

regards,
Tom

[nicolas]

Did you modify fop2.cfg in any way appart from the manager user and secret?

What is the output from :

/usr/local/fop2/autoconfig-users.sh

?

[ictiucn]

The output of
Hi
Thanks for the quick reply,

$ /usr/local/fop2/autoconfig-users.sh
user=1234:4242:all
user=234:1234:all
user=1234:5678:all

buttonfile=autobuttons.cfg

In the proces of getting things to work I changed :

manager_host=localhost  to manager_host=127.0.0.1   (seems hardly a change :D  )
monitor_ipaddress = 1 (not relevant i suppose)

and added:

user=712:ab12:all (which gives the same result as an extension login)

regards
Tom

[ictiucn]

BTW , I did not change the manager user and secret, this is still testing. They are the same as in the other file

Tom

[nicolas]

For the user configuration it seems you did not log into fop2manager or you did not apply changes into freepbx configuration so the fop2manager could do its job. Go to http://your.server/fop2/admin and check the "fop2 users" and "fop2 buttons" tabs, what do you see there? After that, restart fop2 with the command "service fop2 restart" and try again.

Best regards,

[ictiucn]

Hi Nicolas,

That works!
(How did I miss fop2 manager?)

When connecting to fop2/admin, the user tab says 6 users, the buttons tab 7 buttons. Restart of fop2 did not do the trick but a compleet reboot did. I have a working fop2 now with all extension buttons and queue button, and function buttons on the menu bar. Thanks!

When connecting to the fop2 page I still get a message "Something went wrong". Apparently there is:
The groups I created in the groups tab (add group, mark some extensions , reload asterisk with the button on bottom left) were not visible as boxes in the fop2 panel. The group names were also not filled in in the 'Group' field for each button on the buttons tab, When I filled in the group names there (with pressing reload asterisk on bottom left), the group boxes were still not visible
amportal stop; service fop2 restart; amportal start did result in group boxes for the extensions.
Any idea why the boxes do not show up until after a compleet restart of Asterisk? However, this is not a big problem.

Thanks for helping me so quickly. Everything is working now as far as I can see, but I still need to get to the telephones and try it.

regards,
Tom

[nicolas]

Hi,

The "something went wrong" message is always there, but is quickly hidden when the app statrs. If the app fails for whatever reason, then you will still see the message and that is how you know that something went bad, otherwise if the app fails you won't notice as the app itself is the one that hides/unhides page elements.

As for the groups, there are two kinds of groups, you are interested in the visual grouping of buttons on the page, that is set only in the "fop2 buttons" tab, not in the "fop2 groups" tab (fop2 groups are used to filter views or to limit advanced permissions, not to visually group on the display.

There is no need to restart asterisk for any fop2 settings to work, you need to reload fop2 (and that reload is triggered also when asterisk itself reloads). Then login off and on again into fop2 should work. The only exception are install/uninstall plugins, for new plugins to be activated fop2 needs to be restarted (not asterisk), with the command: "service fop2 restart".

If the asterisk reload from menu does not appear to work when changing some settings, you might have some kind of problem with the execution of the script that actually reloads fop2 (/var/www/html/fop2/admin/update_conf.php). You can try to execute that script from the command line and check for errors there, if you do not see any errors, then you should be fine.

Best regards,

[ictiucn]

OK, perfect!

thanks again,

Tom