[asterisk-bugs] [Asterisk 0012771]: Bogus <member> is still 'Not in Use' warnings for AgentLogin'ed agents.

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12771 
====================================================================== 
Reported By:                davidw
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   12771
Category:                   Applications/app_queue
Reproducibility:            always
Severity:                   tweak
Priority:                   normal
Status:                     new
Asterisk Version:           1.4.20.1 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             06-02-2008 09:57 CDT
Last Modified:              06-05-2008 10:55 CDT
====================================================================== 
Summary:                    Bogus <member> is still 'Not in Use'  warnings for
AgentLogin'ed agents.
Description: 
Asterisk seems to correctly know when an AgentLogin type agent is busy on a
call, however every time our agent gets a call, we get a message like:

WARNING[16777] app_queue.c: The device state of this queue member,
Anonymous, is still 'Not in Use' when it probably should not be! Please
check UPGRADE.txt for correct configuration settings.

We've tried to get good presence information from the SIP phones that are
logging in as the agents, but haven't found a recipe that does achieves
this for outgoing calls.  However, this should be irrelevant as it is the
Agent itself whose state matters, not that of the SIP phone.  Moreover, for
AgentLogin, the busy state on the phone wouldn't change for each call, but
would cover the whole logged in period.

====================================================================== 

---------------------------------------------------------------------- 
 putnopvut - 06-05-08 10:55  
---------------------------------------------------------------------- 
aragon:

I suspect that the reason that the agent can receive multiple calls from
multiple queues is due to a race condition between the calling threads and
the device state thread. I cannot, however, state with any certainty if the
race is happening at the same place that davidw reported. As a result, I
also cannot say for sure if adding the memberdelay (as you correctly
assumed) will fix the issue.

I suspect that what's happening is that several different callers from a
queue are nearly simultaneously discovering that the agent is available,
and so those callers attempt to call the agent at the same time. The result
of that is that before the agent's state can change to "ringing" or "in
use" all the callers have called the agent at about the same time.

I'm going to devote some time today to inspect the odd device state
behaviour that appears to be creeping up lately here and in issue
http://bugs.digium.com/view.php?id=12672. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
06-05-08 10:55  putnopvut      Note Added: 0087851                          
======================================================================