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. Chang status of queue members on web

Chang status of queue members on web

Scheduled Pinned Locked Moved Support
2 Posts 2 Posters 120 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
    Kate
    wrote on last edited by
    #1

    We use FOP2 version 2.26 and Asterisk 1.8.11. We have some problems with displaying status of queue members on the web. I change status one of queue members on paused in web. In CLI I can see that command was accepted, and status was changed.

    pbx2k*CLI> queue show
    pbx2k_general_queue has 0 calls (max unlimited) in 'rrmemory' strategy (0s holdtime, 0s talktime), W:0, C:0, A:0, SL:0.0% within 0s
       Members:
          3011-pbx2k (Local/03011@default/n) (dynamic) (paused) (Unknown) has taken no calls yet
       No Callers
    

    But this is not displaying on web. Queue member status on web is unpaused. Status on web will be changing on paused after refresh.
    buttons.cfg

    [IAX2/3011-pbx2k]
    type=extension
    extension=3011-pbx2k
    context=default
    label=operator
    queuechannel=Local/03011@default/n|Penalty=0|MemberName=3011-pbx2k|StateInterface=IAX2/3011-pbx2k
    
    1 Reply Last reply
    0
    • N
      N
      nicolas
      wrote on last edited by
      #2

      Your extension and member name convention is not compatible with what fop2 expects. What fop2 expects to match a Local queue member with an extension button, is to find a match between extension and queuecontext in the button config, with the Local/extension@context in the queue member string.

      In your case, your queue member is

      Local/03011@default

      Making the extension: 03011 and queue context "default"

      But your button config has:

      extension=3011-pbx2k (it does not match 03011)

      and you are missing a queuecontext

      Unfortunately there is no way to relate an extension button with a queue member if you use that convention. So you won't see the pause icon on the button.

      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