kelmore

Member

Last active 7 years ago

  1. 8 years ago
    Mon May 9 16:01:22 2016

    This is now resolved. I was missing the definition of the custom permission I had defined.

    The output of /usr/local/fop2/autoconfig-users.sh should include, in the Permissions section:
    perm=check_queue_voicemails:voicemailadmin:VIRTUAL/399,VIRTUAL/299,VIRTUAL/199

    Initially I could not get these permissions to work as there were no extensions defined. It simply read:
    perm=check_queue_voicemails:voicemailadmin:

    We re-created the custom permission, checked the output of autoconfig-users.sh and all was working properly. Thanks for the help!

  2. Tue May 3 22:24:13 2016

    I believe we have some virtual extensions set up, and have added them as users / buttons. We labeled them Queue Voicemail - Billing, etc It seems we are using extension mailboxes, but maybe we're approaching this incorrectly.

    I looked around and could not find any documentation for defining mailboxes for queues in FOP2, where can I do this?

    From your Number 1 above: "create a fop2 group that contains only the emergency mailbox" - How have you set up this emergency mailbox?
    Thanks!
    Kevin

  3. Mon May 2 23:22:13 2016

    The user seems to have the correct permission.

    user=6603:6603:check_queue_voicemails,browser,callhistory,check,dial,hangup,hangupself,other,phonebook,pickup,preferences,queueagent,queuemanager,transfer,transferexternal,voicemails:All Queues,Call Center,Queue Voicemail Extensions:autowrapup,browser,callhistory,changepassword,clock,presencepause,queuecounter,queuelogin,configonreload

  4. Mon May 2 19:46:59 2016

    I can't seem to make this work correctly. The call center group can't access any voicemail as soon as I set all this up. Could you please review how I have this set up?

    I see now you instruct in 3 above to add this permission to a user, but I would assume it should work from a template as well, right?
    Fop 2.31

  5. Mon May 2 19:40:06 2016

    I have pings running to try to figure out what the issue is with disconnecting might be. I will be upgrading to the latest version and see if there are any improvements.

    I was thinking it would help the troubleshooting if there was a time stamp added to the Queue Login window that shows the last logout time and the last login time. Is there any where else this time is recorded?

    We will be installing the Call Center stats add-on as soon as we can get to the root cause of why the Queue Login window pops up multiple times a day. Maybe we need that add on to see when these log out/ins are occuring?
    Thanks!

  6. Wed Apr 27 15:16:18 2016

    I've come up with another theory for this. I believe more recent versions of Chrome have the ability to essentially drop an unused tab from memory, possibly sticking it in a cache after a period of inactivity (especially when lots of other tabs are open). Could this be triggering the queue login pop-up to re-appear?

    Also, I do recall some other posts where you suggest changing the php session timeout. I have not tried this yet. Do you think this is a related issue or not? What would you suggest I set it to?
    Thanks,
    Kevin

  7. Tue Apr 26 21:30:16 2016
    kelmore started the conversation Queue window feature request: agent/extension status.

    We use many of the options available for displaying the status of extensions and users, but all the good data presented with these options only shows up in the extension buttons, not in the queue details. In the image below, the pointer is hovered over the clock icon to show Paused status, but if I do the same over the clock icon in the queue window, I don't get any information.

    When there are many many extensions, it is hard to see the status of all of your agents at a glance since you may have to do lots of scrolling. The Queue window compresses all that information nicely already, so it'd be a good place to replicate this information.

    It'd be great to show Paused/unPaused status or Paused status with Reason (for agent wrap-up), as well as the status of the agent (available, out to lunch, meeting, etc) just as the extension buttons have it.

    Thanks for considering!

  8. Mon Apr 25 20:56:23 2016

    We upgraded to the newest version 2.30.06 last week. We are still getting the prompts from the Queue Login on our three agents. On one machine, its maybe once a day. Another machine it's at least once a day. On another machine, it averages 5 a day.

    Anything specific I should be looking for in the logs?

    Edit: I see you are still working on some php session timing improvements, I'll keep an eye on that thread too. Thanks!

  9. Thu Apr 14 16:53:15 2016
    kelmore started the conversation queue login window pops up every so often.

    We were having issues with one agent who would only wanted to be in 2 of our 3 queues. Normally, they would log in (automatically being added to all 3), then remove themselves from the third queue. But, they were being automatically added every so often back into this third queue and we couldn't figure out why.

    I installed the queue login plugin so that now, instead of all three queues to being with, they are prompted for which queues to be in. What's happening is that every 10-20 minutes they are re-prompted to log in. I ran pings to 8.8.8.8 to see if there was a correlation to the log outs, and pings wouldn't drop. I had them ping the asterisk/freepbx server, and maybe one ping would drop at the same time they were logged out.

    Is this a php session issue as I had read about in other issues like call history, or is this something else? Maybe it's just basic networking on our side, but why would the session get lost if communication only dropped for the duration of a ping?

    We're planning to install some freepbx updates soon and restart the server--maybe that has something to do with it. We're on 2.30.04 and Queue Login 1.0.5 and freepbx 13.0.99.

    Thanks for the help!
    K

  10. Thu Apr 7 15:46:03 2016

    Thanks for trying, I understand.
    I was able to change the file so that I could set a default state of "answered," so that using the browser back button won't change it from the one we look at most.

    in /var/www/html/fop2/admin/plugins/callhistory/callhistorybsgrid.php
    Change this line from:
    $mifilt = isset($_REQUEST['filterdispo'])?$_REQUEST['filterdispo']:'';
    to:
    $mifilt = isset($_REQUEST['filterdispo'])?$_REQUEST['filterdispo']:'answered';

View more