blak3r

Member

Last active 11 years ago

  1. 11 years ago
    Wed Feb 27 10:03:57 2013

    yeah, it'd be nice if there was a way to disable the desktop notification thing. It's unlikely users who buy FOP2 as an extension to our CRM integration will want to use it.

    Also, is there any documentation on what users need to do with a stock FreePBX (in my case PIAF Purple) to exclude the FOP2 folder from first requiring the user to login to FreePBX? On my box I need to first login to FreePBX before I can send the FOP2 url string with basic auth params embedded.

  2. Tue Jan 22 05:25:03 2013

    We are integrating FOP2 support into yaai (yet another asterisk integration) it's sugarcrm's premier telephony integration.
    https://www.github.com/blak3r/yaai/wiki

    A) I'd like to be able to disable the growl style "click here to enable desktop notifications" globally. So, every user doesn't see this.

    B) It'e be nice if you could globally turn off some of the buttons across the top such as the dial bar, filter bar, extension dial etc which aren't really needed in our application.

    We've come up with workarounds and they are outlined here:
    https://github.com/blak3r/yaai/issues/110

    But, it'd be nice if we didn't have to tell users to modify core files in order to make it work.

  3. Fri Dec 28 20:47:29 2012

    Figured out my issue... I wasn't being patient enough after calling the service start before checking to see if port 4445 was bound yet.

    root@host:/etc/rc.d/init.d $ netstat -lnp | grep 444
    root@host:/etc/rc.d/init.d $ service fop2 start
    Starting Flash Operator Panel 2: daemon /usr/local/fop2/fop2_server -d -i venet0    <--- added this echo for debug
                                                               [  OK  ]
    root@host:/etc/rc.d/init.d $ netstat -lnp | grep 444   <--- ~500ms between each
    root@host:/etc/rc.d/init.d $ netstat -lnp | grep 444
    root@host:/etc/rc.d/init.d $ netstat -lnp | grep 444
    root@host:/etc/rc.d/init.d $ netstat -lnp | grep 444
    root@host:/etc/rc.d/init.d $ netstat -lnp | grep 444
    root@host:/etc/rc.d/init.d $ netstat -lnp | grep 444
    root@host:/etc/rc.d/init.d $ netstat -lnp | grep 444
    root@host:/etc/rc.d/init.d $ netstat -lnp | grep 444
    root@host:/etc/rc.d/init.d $ netstat -lnp | grep 444
    root@host:/etc/rc.d/init.d $ netstat -lnp | grep 444
    tcp        0      0 0.0.0.0:4445                0.0.0.0:*                   LISTEN      13623/fop2_server

    For reference, I'm using the latest as of 12/22/2012. I believe it's 2.26
    The distro is centos. It's a PIAF purple install.

  4. Sun Dec 23 00:09:12 2012

    Following instructions I've found on this forum, I did the screen thing and ran

    service fop2 stop
    cd /usr/local/fop2
    screen
    ./fop2_server -X 511 -i venet0    <--- Notice custom interface
    ctrl-a d

    Everything works.

    root@asdf:/etc/asterisk $ pgrep fop2_server
    1578
    root@asdf::/etc/asterisk $ netstat -lnp | grep 444
    tcp        0      0 0.0.0.0:4445                0.0.0.0:*                   LISTEN      1578/./fop2_server

    When I try to run as a daemon it doesn't.

    I took your suggestion from another forum and my /etc/sysconfig/fop2 looks like:

    OPTIONS="-d -i venet0"

    And it doesn't start up. Where do I go from here?

    Note: I disabled FOP (1) from amportal.conf etc.