Post a Reply
8062 views

Queue is not showing members

  1. 12 years ago

    krtapas

    30 Dec 2011

    Hi, I've using fop2 v2.24, Chrome 16.0.912.63 m, Debian 32 bits and asterisk 1.4.42 and I'm having next issue:

    When I add a member to a queue, it is now showed in the queue button. Here is my button.cfg code:

    [SIP/1010]
type=extension
extension=1010
context=agentes
label=Extension 1010
mailbox=1010@default
channel=SIP/1010
;
[QUEUE/100]
type=queue
label=Entrante

    The server log output

    ** DIGEST_EVENT: start

** PROCESA_BLOQUE  0
** PROCESA_BLOQUE QUEUEMEMBERREMOVED 0

** QUEUE MEMBER LIST start for queue QUEUE/100^0
** QUEUE MEMBER LIST devuelve 

DIGEST canal QUEUE/100^0, comando queuemembers, datos , slot 

** MAIN AMI event received...
** MAIN Processing command received from flash clients...

200.xx.xx.xx  <= <msg data="100|queueadd|1-0|8190407629ea65b11db225e884947dd6" />

-- PROCESS_FLASH_COMMAND origen 100 accion queueadd destino 1-0 password 8190407629ea65b11db225e884947dd6

VALIDAR USUARIO admin@GENERAL

VALIDAR USUARIO admin OK con clave regular (200.xx.xx.xx)

Validation ok, have all permissions for all buttons (0) 1

127.0.0.1       -> Action: QueueAdd
127.0.0.1       -> Queue: 100
127.0.0.1       -> Interface: SIP/1010

** MAIN End of block from localhost

127.0.0.1       <- Response: Success
127.0.0.1       <- Message: Added interface to queue
127.0.0.1       <- Server: 0

** MAIN AMI event received...
** MAIN No 'Event' nor 'End'. Erasing block...
** MAIN End of block from localhost

127.0.0.1       <- Event: QueueMemberAdded
127.0.0.1       <- Privilege: agent,all
127.0.0.1       <- Queue: 100
127.0.0.1       <- Location: SIP/1010
127.0.0.1       <- MemberName: SIP/1010
127.0.0.1       <- Membership: dynamic
127.0.0.1       <- Penalty: 0
127.0.0.1       <- CallsTaken: 0
127.0.0.1       <- LastCall: 0
127.0.0.1       <- Status: 5
127.0.0.1       <- Paused: 0
127.0.0.1       <- Server: 0

** MAIN AMI event received...
** MAIN There's an 'Event' in the event block
** MAIN Event detected block_count = 1 (Event: QueueMemberAdded)
** MAIN There are 1 blocks for processing
** MAIN Answer block cleared

** DIGEST_EVENT: start

** PROCESA_BLOQUE  0
** PROCESA_BLOQUE QUEUEMEMBERADDED 0

** QUEUE MEMBER LIST start for queue QUEUE/100^0
** QUEUE MEMBER LIST devuelve <div class='memberinvalid myclick' id='qm!QUEUE/100^0!SIP/1010'></div><span>Extension 1010</span><br class='clear'/>

DIGEST canal QUEUE/100^0, comando queuemembers, datos PGRpdiBjbGFzcz0nbWVtYmVyaW52YWxpZCBteWNsaWNrJyBpZD0ncW0hUVVFVUUvMTAwXjAhU0lQLzEwMTAnPjwvZGl2PjxzcGFuPkV4dGVuc2lvbiAxMDEwPC9zcGFuPjxiciBjbGFzcz0nY2xlYXInLz4=, slot 

** MAIN AMI event received...
** MAIN Processing command received from flash clients...

200.xx.xx.xx  <= <msg data="1|ping||" />

    Asterisk queue show command:

    CLI> queue show
100          has 0 calls (max unlimited) in 'rrmemory' strategy (0s holdtime), W:0, C:0, A:0, SL:0.0% within 5s
   Members: 
      SIP/1010 (dynamic) (Unavailable) has taken no calls yet
   No Callers

    In presence.js, queue is in "max" mode.

    http://i511.photobucket.com/albums/s353 ... s/fop2.jpg

    Thanks for your help!

  2. admin

    31 Dec 2011 Administrator

    The queue member list is being sent by the server:

    ** QUEUE MEMBER LIST devuelve <div class='memberinvalid myclick' id='qm!QUEUE/100^0!SIP/1010'></div><span>Extension 1010</span><br class='clear'/>

    My guess is that you have the queue button in minimized state (the presence.js is a global value that can be overriden by personal preference or even individual selection when clicking on the queue button icon in the top right.

  3. krtapas

    31 Dec 2011

    I've configured Detailed view in user 1010 and the trouble persists. I'd cleared my cache, restarted service and restarted server.

    http://i511.photobucket.com/albums/s353 ... fop2-1.jpg

    I'll try to upgrade to asterisk 1.6 because I need a feature not present in 1.4, and I hope it causes some magical effect, jeje.

    Thanks Nicolás, I really do appreciate any other idea.

  4. admin

    31 Dec 2011 Administrator

    The queue button in the background is *not* the detailed view.

    The individual setting will override the general setting or the global setting too.

  5. krtapas

    31 Dec 2011

    Sorry but I cannot understand what are you talking about.

    I've displayQueue = 'max' in presence.js and Detailed view in the user configuration. I don't know another parameter to configure this. Sorry for my ignorance.

  6. admin

    2 Jan 2012 Administrator

    Do no configure, click on the top right icon of the queue button. Several times. You will see.

  7. krtapas

    2 Jan 2012

    I had seen minimize option. I didn't understand what was you talking about, but I was tried with it. I have an agent in two queues, but still not working.

    http://i511.photobucket.com/albums/s353/krtapas/fop2c.jpg

    http://i511.photobucket.com/albums/s353/krtapas/fop2-2.jpg

    http://i511.photobucket.com/albums/s353/krtapas/fop2b.jpg

  8. admin

    2 Jan 2012 Administrator

    The first capture is the normal/maximed state, you should leave it as that.

    My guess is that you have a modifed css file or something to that effect, on one of your first captures there was a message being sent to the client to update the queue button. Either your .css file is custom modified to hide agents (there are several posts here describing how to do that, some people do not want to see agents). Or you have a mixed version of client/server fop2 files, and old fop2.js and operator.css file agains a new fop2_server, or viceversa.

    Try to catch me on the live help to chat, I am online right now.

  9. krtapas

    2 Jan 2012

    I have installed fop2 from source and I haven't done any modification to css files, only buttons.cfg and fop2.cfg.

    Thanks for your attention Nicolás.

  10. admin

    2 Jan 2012 Administrator

    Ok, catch me on the live help. This post is not good for tracking issues, you probably have a misconfigurtion in your button definition. You started with a capture of Queue/100, but then you have Queue/inbound or Queue/outbound, etc. It is a big bag of mxed logs and information.

    As a rule of thumb, case is important. QUEUE/Inbound is not the same as Queue/INBOUND.

    Please catch me on the live help.. best regards,

  11. dimmik

    1 Mar 2012

    Hello,

    I have exactly the same problem using version 2.24 on debian x64 with asterisk 1.8.9.0
    No modifications on css.
    How was this fixed?

    Thanks

  12. admin

    1 Mar 2012 Administrator

    If you use automatic button configuration file for freepbx, install the fop2admin manager module for it.

    If you configured buttons manually, add the context=xxx line to your queue button configuration.

    Best regards,

  13. krtapas

    1 Mar 2012

    I put context=1 in Queue section and it worked. Thanks Nicolas for your help.

  14. admin

    1 Mar 2012 Administrator

    For other users that might have the same problem, since version 2.24 the queue button configuration requires you to set *both* extension and context:

    [QUEUE/100]
    type=queue
    extension=100
    context=from-queue
    label=Sales

or Sign Up to reply!