[asterisk-bugs] [Asterisk 0012916]: Multiple incoming call to free agent

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12916 
====================================================================== 
Reported By:                sgenyuk
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   12916
Category:                   Applications/app_queue
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.4.19 
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-23-2008 10:00 CDT
Last Modified:              06-24-2008 04:28 CDT
====================================================================== 
Summary:                    Multiple incoming call to free agent
Description: 
when agent become available during hight call volume in the queue he might
receive multiple calls. Like if agent has 6 lines on the phone it receive 6
different calls one per line. 
====================================================================== 

---------------------------------------------------------------------- 
 davidw - 06-24-08 04:28  
---------------------------------------------------------------------- 
http://bugs.digium.com/view.php?id=12771 is a race condition that means that the
agent isn't effectively
marked busy immediately.  Its potential failure mode is to cause multiple
calls to be accepted for an idle agent.  I don't understand your reference
to messages, and the failure mode would be "multiple calls when agent is
available".

What I don't know for certain is whether it generalises to
AgentCallBackLogin or queue members that aren't really Agents, which is why
I asked about the nature of your agents.  Also, that it will cause multiple
calls to be accepted is speculation, based on their being a real delay
between the agent being allocated the call and the queue considering the
agent busy.

It would be instructive to know if you are getting the warning mentioned
in that issue; putnopvut's second question is specifically about the issue
that is mentioned in that warning message.  Note that, for a real Agent, or
when you reach the call limit, it is conceivable that the status update
would have been completed by the time the message would be generated, but
not by the time that the system tried to offer the second and subsequent
calls, so the absence of the warning is not proof that the issues to which
it relates don't apply.

(I suspect, when putnopvut refers to having call limits set, he actually
means having them set to one.)

The reason that I assume that you are not using AgentLogin, is that there
is only one channel associated with AgentLogin, so any failure mode would
result in incoming calls being lost, or overriding earlier ones.  Some
people use Agent in a generic sense, rather than to mean Agent/xxxxx, which
is why I was asking whether you really meant Agents. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
06-24-08 04:28  davidw         Note Added: 0089138                          
======================================================================