Member
Last active 5 years ago
After upgrading to FOP2 Manager 1.1.2 it appears that they way in which queue logins work has changed. Previously there appeared to be no link between FreePBX Dynamic Agent settings and FOP2. Now it appears that FOP2 seems to honour the FreePBX Dynamic Agent settings.
Previously we had some queues with "Restrict Dynamic Agents" set to yes in FreePBX and some set to no. This did not make any difference to the queues that agents could log into via FOP2. Now it appears that this has changed and the "Restrict Dynamic Agents" setting is FreePBX is honoured by FOP2.
Is this a change that has been made for a specific reason? Will this remain the case in future releases?
Thanks in advance.
I have just purchased an annual upgrade license and applied it successfully:
Reactivation Successfull
Thanks! Do not forget to restart fop2 to activate the license.
[root@beckpbx fop2]# service fop2 restart
Shutting down Flash Operator Panel 2: [ OK ]
Starting Flash Operator Panel 2: [ OK ]
However when I try to upgrade from 2.28 to 2.30.06 by running make I get:
/bin/sh: line 9: server/fop2_server: cannot execute binary file
Upgrade Aborted. License reactivation failed.
Be sure you have internet access from this server,
and that your code is not older than a year.
If your license has expired, you must renew it in order to upgrade,
or you can still use your current FOP2 version for as long as you want.
If you already bought an upgrade code please run the following command:
server/fop2_server --upgrade
If the upgrade is successful run make again to retry the installation.
Contact us at [email protected] for more information.
Done!
So I can't do the upgrade. Any help would be appreciated.
We are not reloading Asterisk frequently or making FreePBX changes.
I will see if I can find out more information about what is happening. Many users on our system are running Apple MAC system using Chrome as the browser.
We have the Queue Login plugin enabled for agents and it works as expected. We are using the Chrome Browser. However what seems to happen is when an agent moved away from the active FOP2 browser tab to do something else they get logged out of the queues that they are in. When the browse back to the FOP2 tab they are still logged into FOP2 but they get offered the popup box to login to queues again and have to select the queues that they want to login to again.
Any assistance would be appreciated.
Lee
I think that fixed the issue that we were having.
Thanks
We did indeed have the auto-wrapup plugin installed and have now removed that temporarily to see if that makes any difference.
Thanks
Lee
It's installed but we're not using it at the moment. But we do intend to start using it soon.
Yes via the FOP2 GUI but also Asternic reports show the UNPAUSE. In addition the agents do still receive calls from the queue so even though I haven't actually see the output from asterisk "queue show" they are seen by Asterisk as unpaused.
I will see if I can do an asterisk "queue show" the next time this happens.
Lee
Thanks for this and sorry for the late reply. I haven't tried the audit log yet but will do. One thing that we have noticed is that if agents pause themselves using the "Pause Member" menu then all works fine and they stay paused. If they pause themselves using the Presence menu they become unpaused a few seconds later.
We are using the above plugin so that agents can pause themselves from the presence box but have also uncommented the pause states section in presence.js. However when agents pause themselves they seem to get unpaused automatically and then have to put themselves back on pause. This happens pretty regularly but seems random.
Any guidance on where to look to investigate this issue would be great.
Thanks
Lee