@admin Did you upgrade the FOP2 *server*?? Not the FOP2 Manager, but the whole server?

/usr/local/fop2/fop2_server -v

What is the output?

Yes. The admin page says;
FOP2 Server Status: OK - Version: 2.30.03

I'm trying to run /usr/local/fop2/fop2_server -v (as root user) and it won't complete the command, it just hangs...and top shows fop2_server using 99% CPU.

Another server running this same setup does not have these issues. Very confused.

Hi again. I'm finally getting some time to come back to this. I've cleared the cache on multiple computers. No difference. Here is an example of how strange this is.
Login1: everyone but login user shows in queue
Login2: only 1 user shows in queue
Login3: different 1 user shows in queue
Login4: all users show in queue except the user that was shown in login3
and so on
And then eventually sometimes the queue shows up correctly.

After performing an upgrade through the admin section I clicked the "reload FOP2" button which I thought restarted the FOP2 service.

So, sometimes when an agent logs into FOP2 the queues won't show all agents. For instance I have a queue with 4 static agents. They are all available but the queue only shows 2 of them. I reload the panel and then SOMETIMES all 4 agents show up, no other changes made. And I THINK (but haven't verified) that they will eventually just show up on their own after a certain amount of time, sometimes quite a while.

FreePBX: 10.13.66-13
Asterisk: 13.9.1
FOP2: 2.30.03

I don't manually define any buttons, queues, or anything like that. I installed and ran through the instructions on integration of FOP2 with FreePBX. I have however upgraded FOP2 and FreePBX over multiple versions over time.

Any idea why this might happen and what I could look at to help determine the cause.

So I tried the steps in the FAQ.

How to replace the FOP link in FreePBX to FOP2?
You can do it by means of modifying your apache configuration file. In Centos the file is located in /etc/httpd/conf/httpd.conf. In Debian it is located in /etc/apache2/sites-available/default. For other distros you can check apache wiki. In this file add the following line:

alias /panel/ "/var/www/html/fop2/"
You will then need to copy the index.html file to index_amp.php in order to make FreePBX happy:

cp /var/www/html/fop2/index.html /var/www/html/fop2/index_amp.php
After the changes, reload Apache. From then one, all requests to /panel will be redirected to your FOP2 install.

It doesn't seem to be working for me. I assume this was written for moving from FOP to FOP2. And since FreePBX now provide that other panel by default, I assume the steps aren't the same. I also tried making requests to http://server/panel but that didn't redirect to fop2 either.

What I was hoping to do was direct the "Operator Panel" links in FreePBX to FOP2. This is a current release of FreePBX. Is this possible?

I guess things always work this way for me. Once I post something I fix it.
I thought reloading FOP2 from the manager would be the same as starting and stopping the service from the CLI. However that didn't solve my problem. As soon as I ran;

service fop2 stop
service fop2 start

The buttons cleared state and seem to be working fine again.

Hello,

I installed FOP2 months ago in preparation for a bigger deployment and actually purchasing it. At the time everything seemed to work fine. I've since updated the server and updated FOP2. And before I purchased I was going to just make sure everything was still working.

Well for whatever reason buttons for user extensions seem to be "stuck". For instance I types a feature code *73 and now my line 1 shows that I still have an active outbound call to that number. Another one has *79 stuck. Another has an outbound call to 11 digit North American phone #. I've tried reloading FOP2, reloading Asterisk, and a few other things but nothing worked.

Any help on why this would be happening and how to fix it?