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

  1. Home
  2. Support
  3. FOP2 buttons don't work after Asterisk Upgrade

FOP2 buttons don't work after Asterisk Upgrade

Scheduled Pinned Locked Moved Support
5 Posts 2 Posters 62 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • K
    K
    Kristofersen
    wrote on last edited by
    #1

    Hello,

    I just recently upgraded my PBX system to 1.8.17 which is running on Centos 5 OS. After the upgrade I registered my FOP2. Everything is looking okay except the buttons at the top of the screen no longer work. They were fine before the upgrade. Any ideas on what may cause this?

    Thanks.

    1 Reply Last reply
    0
    • N
      N
      nicolas
      wrote on last edited by
      #2

      Most probably you are lacking the "originate" permission in /etc/asterisk/manager.conf

      Look here for a good way to setup a manager user for fop2:

      http://www.fop2.com/blog/make-fop2-snap ... ventfilter

      1 Reply Last reply
      0
      • K
        K
        Kristofersen
        wrote on last edited by
        #3

        Thanks for the response. I think i am connected to the manager. I ran /usr/local/fop2/fop2_server --test and it said Connection to manager OK.

        1 Reply Last reply
        0
        • N
          N
          nicolas
          wrote on last edited by
          #4

          you can be connected, but with lack of permissions. Asterisk 1.6 included the "originate" permission that is needed to originate calls, that was not present in 1.4. Many of the actions in FOP2 require an originate command. So, change /etc/asterisk/manager.conf read/write permission lines to include the "originate" or "all" permission, then reload asterisk, reload fop2, and try again. If you use asterisk 1.8, you can go ahead and create a special user as specified in the blog post.

          1 Reply Last reply
          0
          • K
            K
            Kristofersen
            wrote on last edited by
            #5

            Yeah, that fixed it. Thanks.

            1 Reply Last reply
            0

            Hello! It looks like you're interested in this conversation, but you don't have an account yet.

            Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

            With your input, this post could be even better 💗

            Register Login
            Reply
            • Reply as topic
            Log in to reply
            • Oldest to Newest
            • Newest to Oldest
            • Most Votes


            • 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