Queue member still showing, not cached.

  1. 11 years ago

    We have a queue member showing up in the queue listing even though she is not in the queue. It is not a client side cache bug, as any computer logging into FOP2 can duplicate it.

    On the right hand side the queue list doesnt show the user.
    http://i.imgur.com/0SUmx04.jpg

    When you click on it to see queue details, the user shows. "3224 Rebecca".
    http://i.imgur.com/WaD3SWh.jpg

    The user is not in the queue in asterisk.

    101          has 0 calls (max unlimited) in 'ringall' strategy (2s holdtime), W:0, C:6, A:0, SL:0.0% within 0s
       Members: 
          Local/3336@from-internal/n (Not in use) has taken 1 calls (last was 976 secs ago)
          Local/3269@from-internal/n (Not in use) has taken no calls yet
          Local/3333@from-internal/n (Not in use) has taken no calls yet
          Local/3323@from-internal/n (Not in use) has taken 1 calls (last was 459 secs ago)
          Local/3337@from-internal/n (Not in use) has taken 1 calls (last was 1833 secs ago)
          Local/3334@from-internal/n (In use) has taken 2 calls (last was 307 secs ago)
          Local/3338@from-internal/n (Not in use) has taken 1 calls (last was 724 secs ago)
          Local/3220@from-internal/n (Not in use) has taken no calls yet
          Local/3335@from-internal/n (Not in use) has taken no calls yet
          Local/3332@from-internal/n (Not in use) has taken no calls yet
       No Callers

    The extension is not auto subscribed.

    # asterisk -rx 'database show' | grep 3224 
    /AMPUSER/3224/cidname                             : Rebecca Gomez            
    /AMPUSER/3224/cidnum                              : 3224                     
    /AMPUSER/3224/device                              : 3224                     
    /AMPUSER/3224/language                            :                          
    /AMPUSER/3224/noanswer                            :                          
    /AMPUSER/3224/outboundcid                         :                          
    /AMPUSER/3224/password                            :                          
    /AMPUSER/3224/recording                           : out=Adhoc|in=Adhoc       
    /AMPUSER/3224/ringtimer                           : 0                        
    /AMPUSER/3224/vmx/busy/state                      : disabled                 
    /AMPUSER/3224/vmx/busy/vmxopts/timeout            :                          
    /AMPUSER/3224/vmx/unavail/state                   : disabled                 
    /AMPUSER/3224/vmx/unavail/vmxopts/timeout         :                          
    /AMPUSER/3224/voicemail                           : default                  
    /CALLTRACE/3224                                   : 8327711716               
    /CALLTRACE/3231                                   : 3224                     
    /CALLTRACE/3238                                   : 3224                     
    /CW/3224                                          : ENABLED                  
    /CustomDevstate/DEVDND3224                        : NOT_INUSE                
    /CustomDevstate/DND3224                           : NOT_INUSE                
    /DEVICE/3224/default_user                         : 3224                     
    /DEVICE/3224/dial                                 : SIP/3224                 
    /DEVICE/3224/type                                 : fixed                    
    /DEVICE/3224/user                                 : 3224                     
    /SIP/Registry/3224                                : 10.10.75.167:5060:3600:3224:sip:[email protected]:5060
  2. More info:

    Removed user's extension, re-added it. Still shows in the queue.
    Added user to queue, shows as expected in right side as well as queue detail. Removed user from queue, user not showing in right side, but shows in queue detail.

  3. admin

    5 Jun 2013 Administrator

    Hi,

    I think I am missing something. What do you mean by "queue detail"?

    The filter that occurs when you select the queue button? If you are referring to that, take into account that the filter applied is pretty dumb, it filters just be queue name/number as depicted in the queue button agent list. For example, if in the queue button you have a member "John", and you have 3 extensions named "John" , "John B" and "John C", all three will appear on the extension box when you click on the queue button, although only John is a queue member. The *actual* queue member list is on the queue button itself, the filtering is done for convenience, but it is not exact.

    Best regards,

  4. You are thinking right, by "queue detail" I meant the left screen "extension box".

    The method by which you're filtering doesn't make sense as to how it's not catching this extension right. Any hope for fixing it? Adding a smarter regex filter possibly. If we only were allowed to access the source, I would fix it!

  5. admin

    5 Jun 2013 Administrator

    It is not as simple as it might appear. The filter works fine as it is. The problem is that you have an agent named CC, you could rename that agent to a more meaningful name so it does not match rebeCCa

    Best regards,

  6. admin

    6 Jun 2013 Administrator

    Actually you were right about room for improvement on the regexp: it can be tightened to use word boundaries so it will work fine in your case. I will update it for 2.27 final. In any case, renaming that CC agent will fix it for you too.

  7. Awesome, we'll change the agent named CC. The problem is her name is actually "CC". We'll figure it out. Good catch, and thanks for updating in the next patch!

  8. admin

    6 Jun 2013 Administrator

    Perhaps renaming it to "C C" ?

or Sign Up to reply!