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. System doesn't work after upgrade

System doesn't work after upgrade

Scheduled Pinned Locked Moved Support
4 Posts 2 Posters 74 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.
  • N
    N
    NexusManagement
    wrote on last edited by
    #1

    I just purchased an additional 1yr maintenance upgrade, and preformed the 2.26 upgrade (from 2.20). When deploying this, neither the stock HTML configuration, nor my customized one (only showing queues, as that is the requirement here) show calls in the queues. This is running against an Asterisk 1.4.x system. I can see the FOP logging in correctly in the asterisk console output, and the manager user has the following read/write permissions. system,call,command,agent,user,originate

    Any advice on how to proceed would be appreciated.

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

      Hi,

      The latests FOP2 version requires the queue button definition to include an extension and context. If not, you will not see activity. If you use fop2 on a separate server as asterisk or multi server setups, the server parameter is also required. Example:

      [QUEUE/1234]
      type=queue
      label=Some Name
      extension=1234
      context=from-queue

      Try that and let me know.

      Best regards,

      1 Reply Last reply
      0
      • N
        N
        NexusManagement
        wrote on last edited by
        #3

        Thank you, we had actually discovered that a day or so after I created the post. Is there a way for the queue buttons to include the extension, but not have the extension displayed? The addition of the extension to the label on the queue button is cumbersome for my use case.

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

          There is a global setting, but that affects any button type, in presence.js noExtenInLabel=true

          You might want to try, but I have never tried so use try at your own risk, to set the extension to  , something like

          extension= 

          It might work or not at all or break fop2 altogether.. you can test it out and let me know.

          Best regards,

          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