Last active 3 years ago
We are currently running FOP2 v2.29.00 and have noticed an unexpected behavior with the privacy settings of "Record" & "All". When either of these permissions are set the user is unable to record themselves (the button in FOP2 is grayed out) even though they have been granted the Recordself permission. Please let us know if this is expected or if this is something that can be corrected.
Great Thanks!! I have been checking for a forum post, I didn't think to check the download page.
Just wondering if v2.29.01 was close to being released.
Ok, sorry I missed that. Where are the plugin descriptions that you reference? I don't want to miss anything else!! The short description in FOP2 Manager is the only one I can find.
I recently globally enabled "Queue Pause from Presence box" plugin and we had "Presence Box DND Integration" globally enabled already. Last evening one of our 3rd shift agents uncovered some interesting behavior that does not appear appropriate to me. Here's a breakdown of what they did:
This behavior is consistent and we were able to duplicate it this morning by repeating these steps. We are running FOP2 v2.29.00 on FreePBX 12.0.39. Can you tell me if this is the expected behavior or is this something that should not occur?
No hurry I can wait till the release. I would like to know where the user preferences are stored so I can "fix" any modified by the users while they have this button enabled.
We upgraded to 2.29.00 yesterday from a pre-release version 2.29. Our users all now have the Preference button showing on their FOP2 panel but most of them do not have the "preferences" permission. The majority of our users are granted permissions using templates and are only granted: dial, hangupself, phonebook, pickup, queueagent, recordself, transfer.
Also I am curious where those individual user preferences are stored? Once we get this disabled again I will want to check and make sure no one has preferences set that may cause issues.
Let me know if you need more information regarding our environment.
Is this the most current list of events that are safe to filter out?
Hmmm, well it was set to 0 and I was not getting the pop-up. That's why I tried -1. I don't think I ever saved the settings after install, I just looked and saw it was 0 and left it alone. I just changed it back to 0 and I did get prompted on login. Perhaps there was just something funky with the default value after install.
We updated to the new version yesterday to see if it would work in our environment. Not really sure how to set the AutomaticLoginToAllQueue field in settings. The default was 0, I assumed that was disabled but with it set to 0 the users get no pop-up and are not logged into their queues. Setting it to -1 seems to bring the pop-up back. Can you let me know what values are valid here and what they do. Thanks