Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

FOP2 Community Forum

M

mbr01

@mbr01
Unfollow Follow
About
Posts
3
Topics
1
Shares
0
Groups
0
Followers
0
Following
0

Posts

Recent Best Controversial

  • fop2 manager cannot connect after upgrade to 2.28
    M mbr01
    Support

    Thanks for the explanations.
    This makes sense now.
    Have a good day


  • fop2 manager cannot connect after upgrade to 2.28
    M mbr01
    Support

    This is a follow up to my previous post.

    I just found that if I update /usr/local/fop2/fop2.cfg instead of /etc/asterisk/fop2, then fop2 server can connect.
    So my question is, is it how it is supposed to work ? If yes, then why copying the file from /usr/local/fop2 to /etc/asterisk/fop2 ?

    thanks


  • fop2 manager cannot connect after upgrade to 2.28
    M mbr01
    Support

    Hi,
    My system is Elastix 2.5. I installed fop2 from the add ons web page. Fop2 is working fine (version 2.25).

    I then update to fop2 version 2.28 by manually download the update and do the 'make install' command.
    As per another post, I then issue the following commands :
    cp /usr/local/fop2/fop2.cfg /etc/asterisk/fop2
    cp /usr/local/fop2/autoconfig* /etc/asterisk/fop2
    cp /var/www/html/fop2/index.html /var/www/html/fop2/fop2.html
    then update /etc/asterisk/fop2/fop2.cfg with the manager credentials.

    But now fop2 manager cannot connect, reporting that authentication is failing:

    [root@ELASTIX25 fop2]# /usr/local/fop2/fop2_server --debuglevel 9
    Flash Operator Panel 2 - License file fop2.lic not found.
    127.0.0.1 <- Response: Success
    127.0.0.1 <- ActionID: 1
    127.0.0.1 <- Challenge: 631291271

    127.0.0.1 <- Response: Error
    127.0.0.1 <- ActionID: 2
    127.0.0.1 <- Message: Authentication failed

    Failed to connect to asterisk - localhost:5038
    Error Message: Login Failed to Asterisk (bad auth) at localhost:5038. Check your manager credentials!
    Error occured on socket FOP2::AMI2=HASH(0x16b62e50)
    CLEAN activity for buttons for server localhost as the connection was lost

    Removing /var/www/html/fop2/fop2-variablesGENERAL.txt...

    The thing is I am confident that my login/pwd are ok in fop2.cfg (and in manager.conf).
    When I use the very same credentials in another app connecting to AMI, it's working fine. So for me the manager side is ok.

    Any help appreciated.
    Thanks

  • Login

  • Don't have an account? Register

  • Login or register to search.
Powered by NodeBB Contributors
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups