kelmore

Member

Last active 7 years ago

  1. 8 years ago
    Fri Feb 12 16:20:07 2016
    kelmore started the conversation Auto wrapup not working.

    I have purchased and activated the Auto Wrapup plugin, then installed the plugin and set wrap-up times to be 90 seconds in FOP manager on each of my three queues. I then enabled the plugin on the call center and admin templates I've created so the plugin is enabled on each user's account. Nothing is happening in the FOP2 user interface with regard to the wrap up time. There should be some alert right?

    I have set FreePBX to have a queue auto-wrapup of 0 seconds and then 2 minutes and tested each way, neither of which solves the issue. Is there a place with some more documentation for this plugin? How do I need to have the queues set up in FreePBX for this to work properly?

    The queue wrap ups were working properly with no FOP2 plugin, and queue wrapup times set in FreePBX, but as indicated in the plugin description, there was no display in FOP2 to let users know they were in their wrap-up period.
    Thanks,
    Kevin

  2. Thu Feb 11 00:36:16 2016

    This seemed to do the trick! Thanks!!!!

  3. Wed Feb 10 15:18:47 2016

    Here's what I just tried:

    Please note most tasks should be handled through the GUI.
    You can access the GUI by typing one of the above IPs in to your web browser.
    For support please visit:
    http://www.freepbx.org/support-and-professional-services

    [root@lion2 ~]# service fop2 status
    fop2_server is stopped
    [root@lion2 ~]# service fop2 start
    Starting Flash Operator Panel 2: [ OK ]
    [root@lion2 ~]# service fop2 status
    fop2_server dead but subsys locked
    [root@lion2 ~]# ps aux | grep fop2
    root 1520 0.0 7.8 309524 150680 ? Ss Feb04 6:38 /usr/local/fop2 /fop2_serve -d
    root 4261 0.0 6.3 307804 121236 ? Ss Feb08 1:21 /usr/local/fop2 /fop2_serve -d
    root 29325 0.3 5.4 307188 104020 ? Ss 10:14 0:00 /usr/local/fop2 /fop2_serve -d
    root 31209 0.0 0.0 103248 872 pts/0 S+ 10:15 0:00 grep fop2
    [root@lion2 ~]# service fop2 stop
    Shutting down Flash Operator Panel 2: [FAILED]
    [root@lion2 ~]# kill 29325
    [root@lion2 ~]# ps aux | grep fop2
    root 1520 0.0 7.8 309524 150680 ? Ss Feb04 6:38 /usr/local/fop2/fop2_serve -d
    root 4261 0.0 6.3 307804 121236 ? Ss Feb08 1:21 /usr/local/fop2/fop2_serve -d
    root 31258 0.0 0.0 103248 876 pts/0 S+ 10:16 0:00 grep fop2
    [root@lion2 ~]# kill 4261
    [root@lion2 ~]# kill 1520
    [root@lion2 ~]# service fop2 start
    Starting Flash Operator Panel 2: [ OK ]
    [root@lion2 ~]# ps aux | grep fop2
    root 656 0.0 0.0 103244 864 pts/0 R+ 10:17 0:00 grep fop2
    root 31282 3.4 5.3 307188 103796 ? Ss 10:17 0:00 /usr/local/fop2/fop2_serve -d
    [root@lion2 ~]# service fop2 restart
    Shutting down Flash Operator Panel 2: [FAILED]
    Starting Flash Operator Panel 2: [ OK ]
    [root@lion2 ~]# ps aux | grep fop2
    root 896 2.4 5.4 308256 104176 ? Ss 10:17 0:00 /usr/local/fop2/fop2_serve -d
    root 2797 0.0 0.0 103244 864 pts/0 S+ 10:17 0:00 grep fop2
    root 31282 3.2 5.6 307188 108932 ? Ss 10:17 0:01 /usr/local/fop2/fop2_serve -d
    [root@lion2 ~]#

  4. Wed Feb 10 05:19:53 2016

    Yes, starts at boot with no issue, all automatically. I don't believe I made any odd changes to the init script.

  5. Tue Feb 9 14:12:51 2016

    Last month I installed a FreePBX distro and then added FOP2, never used FOP1, unless it's bundled with FreePBX.

    [root@XX ~]# netstat -lnp | grep 444
    tcp 0 0 0.0.0.0:4445 0.0.0.0:* LISTEN 1520/fop2_serve
    unix 2 [ ACC ] STREAM LISTENING 10598 1444/gam_server @/tmp/fam-root-

  6. Tue Feb 9 00:14:14 2016

    [root@lion2 ~]# /usr/local/fop2/fop2_server -X 1
    Flash Operator Panel 2 - White Label Version
    unable to initialize libusb: -99
    EV: error in callback (ignoring): bind: Address already in use at script/fop2_server.pl line 14203.
    127.0.0.1 <- Response: Success
    127.0.0.1 <- ActionID: 1
    127.0.0.1 <- Challenge: 181433702

    127.0.0.1 <- Response: Success
    127.0.0.1 <- ActionID: 2
    127.0.0.1 <- Message: Authentication accepted

    127.0.0.1 <- Event: FullyBooted
    127.0.0.1 <- Privilege: system,all
    127.0.0.1 <- Status: Fully Booted

    127.0.0.1 <- Response: Success
    127.0.0.1 <- ActionID: 3
    127.0.0.1 <- Message: Mailbox Message Count
    127.0.0.1 <- Mailbox: 6603@default
    127.0.0.1 <- UrgMessages: 0
    127.0.0.1 <- NewMessages: 0
    127.0.0.1 <- OldMessages: 0

    127.0.0.1 <- Event: VarSet
    127.0.0.1 <- Privilege: dialplan,all
    127.0.0.1 <- Channel: Local/s@tc-maint-00001db3;2
    127.0.0.1 <- ChannelState: 4
    127.0.0.1 <- ChannelStateDesc: Ring
    127.0.0.1 <- CallerIDNum: 0
    127.0.0.1 <- CallerIDName: 0
    127.0.0.1 <- ConnectedLineNum: 0
    127.0.0.1 <- ConnectedLineName: 0
    127.0.0.1 <- Language: en
    127.0.0.1 <- AccountCode:
    127.0.0.1 <- Context: timeconditions
    127.0.0.1 <- Exten: 3
    127.0.0.1 <- Priority: 4
    127.0.0.1 <- Uniqueid: 1454976540.16105
    127.0.0.1 <- Linkedid: 1454976540.16104
    127.0.0.1 <- Variable: DB_RESULT
    127.0.0.1 <- Value:

    127.0.0.1 <- Event: Newexten
    127.0.0.1 <- Privilege: call,all
    127.0.0.1 <- Channel: Local/s@tc-maint-00001db3;2
    127.0.0.1 <- ChannelState: 4
    127.0.0.1 <- ChannelStateDesc: Ring
    127.0.0.1 <- CallerIDNum: 0
    127.0.0.1 <- CallerIDName: 0
    127.0.0.1 <- ConnectedLineNum: 0
    127.0.0.1 <- ConnectedLineName: 0
    127.0.0.1 <- Language: en
    127.0.0.1 <- AccountCode:
    127.0.0.1 <- Context: timeconditions
    127.0.0.1 <- Exten: 3
    127.0.0.1 <- Priority: 5
    127.0.0.1 <- Uniqueid: 1454976540.16105
    127.0.0.1 <- Linkedid: 1454976540.16104
    127.0.0.1 <- Extension: 3
    127.0.0.1 <- Application: ExecIf
    127.0.0.1 <- AppData: 0?Set(DB(TC/3)=)

    127.0.0.1 <- Event: Newexten
    127.0.0.1 <- Privilege: call,all
    127.0.0.1 <- Channel: Local/s@tc-maint-00001db3;2
    127.0.0.1 <- ChannelState: 4
    127.0.0.1 <- ChannelStateDesc: Ring
    127.0.0.1 <- CallerIDNum: 0
    127.0.0.1 <- CallerIDName: 0
    127.0.0.1 <- ConnectedLineNum: 0
    127.0.0.1 <- ConnectedLineName: 0
    127.0.0.1 <- Language: en
    127.0.0.1 <- AccountCode:
    127.0.0.1 <- Context: timeconditions
    127.0.0.1 <- Exten: 3
    127.0.0.1 <- Priority: 6
    127.0.0.1 <- Uniqueid: 1454976540.16105
    127.0.0.1 <- Linkedid: 1454976540.16104
    127.0.0.1 <- Extension: 3
    127.0.0.1 <- Application: Set
    127.0.0.1 <- AppData: DEVICE_STATE(Custom:TC3)=INUSE

    127.0.0.1 <- Event: VarSet
    127.0.0.1 <- Privilege: dialplan,all
    127.0.0.1 <- Channel: Local/s@tc-maint-00001db3;2
    127.0.0.1 <- ChannelState: 4
    127.0.0.1 <- ChannelStateDesc: Ring
    127.0.0.1 <- CallerIDNum: 0
    127.0.0.1 <- CallerIDName: 0
    127.0.0.1 <- ConnectedLineNum: 0
    127.0.0.1 <- ConnectedLineName: 0
    127.0.0.1 <- Language: en
    127.0.0.1 <- AccountCode:
    127.0.0.1 <- Context: timeconditions
    127.0.0.1 <- Exten: 3
    127.0.0.1 <- Priority: 6
    127.0.0.1 <- Uniqueid: 1454976540.16105
    127.0.0.1 <- Linkedid: 1454976540.16104
    127.0.0.1 <- Variable: DB_RESULT
    127.0.0.1 <- Value:

    127.0.0.1 <- Event: Newexten
    127.0.0.1 <- Privilege: call,all
    127.0.0.1 <- Channel: Local/s@tc-maint-00001db3;2
    127.0.0.1 <- ChannelState: 4
    127.0.0.1 <- ChannelStateDesc: Ring
    127.0.0.1 <- CallerIDNum: 0
    127.0.0.1 <- CallerIDName: 0
    127.0.0.1 <- ConnectedLineNum: 0
    127.0.0.1 <- ConnectedLineName: 0
    127.0.0.1 <- Language: en
    127.0.0.1 <- AccountCode:
    127.0.0.1 <- Context: timeconditions
    127.0.0.1 <- Exten: 3
    127.0.0.1 <- Priority: 7
    127.0.0.1 <- Uniqueid: 1454976540.16105
    127.0.0.1 <- Linkedid: 1454976540.16104
    127.0.0.1 <- Extension: 3
    127.0.0.1 <- Application: ExecIf
    127.0.0.1 <- AppData: 0?Set(NOT_INUSE)

  7. Mon Feb 8 23:57:58 2016

    Everything seems to be running fine, except the Call History plugin which I have found a few posts about but haven't tackled yet. When I want to install a new licensed plugin, I do need to restart the service from the command line in this way to activate it, correct?

    [root@XX ~]# service fop2 status
    fop2_server dead but subsys locked
    [root@XX ~]# service fop2 start
    Starting Flash Operator Panel 2: [ OK ]
    [root@XX ~]# service fop2 status
    fop2_server dead but subsys locked
    [root@XX ~]# service fop2 stop
    Shutting down Flash Operator Panel 2: [FAILED]

  8. Thu Feb 4 17:37:57 2016
    kelmore started the conversation updating plugin, can't restart service fop2.

    Each time I try to restart fop2 using stop or restart it fails. I've restarted the entire freepbx server and I get the same message.

    [root@lion2 ~]# service fop2 stop
    Shutting down Flash Operator Panel 2: [FAILED]

    I'm using FOP2 Server Status: OK - Version: 2.30.04 with FreePBX 13.0.49
    Anything I can check?
    Thanks

  9. Thu Feb 4 16:38:19 2016
    kelmore posted in just starting, two questions.

    Good news, title is working and everything else seems to be fine.
    Thanks for the help!

  10. Wed Feb 3 22:03:31 2016
    kelmore started the conversation just starting, two questions.

    Hi,
    We've been getting FreePBX and FOP2 set up over the last month, transitioning a small call center over from a ShoreTel system era 2004.
    I have two questions.
    1)We purchased the White Label, and I tried changing the index.html <title> tag to "Phones." When I load the FOP2 panel, the tab name is correct for less than a minute, then reverts to "Flash Operator Panel 2". Do I need to change this somewhere else?

    2) We have created a virtual host on our web server machine so that instead of users accessing "freepbx.ourserver.com/fop2/", they can access this FOP2 by going to "phones.ourserver.com" Everything seems to work fine, but are there any repercussions you can think of that would pose an issue? It may potentially change the location of html links for folders -beneath- fop2, like in the base directory, but if there really are no html links to things beaneath the FOP2 folder, then we should be fine, right? I was thinking FOP2 is actually modifying the asterisk/freepbx database in other ways.

    Thanks!
    Kevin

View more