[asterisk-bugs] [Asterisk 0014329]: wrapuptime=0 in 1.6.0.1 and 1.6.0.3

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=14329 
====================================================================== 
Reported By:                x86
Assigned To:                putnopvut
====================================================================== 
Project:                    Asterisk
Issue ID:                   14329
Category:                   Applications/app_queue
Reproducibility:            sometimes
Severity:                   major
Priority:                   normal
Status:                     acknowledged
Asterisk Version:           1.6.0.3 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-01-25 17:23 CST
Last Modified:              2009-02-06 15:26 CST
====================================================================== 
Summary:                    wrapuptime=0 in 1.6.0.1 and 1.6.0.3
Description: 
When you set wrapuptime=0 in queues.conf on any queue, persistent (afaik...
did not try dynamic agents) members of that queue will randomly (more so
than not) miss calls if they recently got off of the phone. It seems that
when the wrap up time is set to 0, app_queue ignores the 0 and defaults the
value to something around 10 seconds.
====================================================================== 

---------------------------------------------------------------------- 
 (0099652) putnopvut (administrator) - 2009-02-06 15:26
 http://bugs.digium.com/view.php?id=14329#c99652 
---------------------------------------------------------------------- 
I copied the general section and service queue into my queues.conf and made
a couple of insignificant modifications (like changing the members to
correspond to my SIP peers and changing the periodic-announce file to play
a sound I have on my computer).

I tried a couple of different tests. In one, I continually called the
queue with the same phone and would randomly pick a different member to
answer the call. I ran probably about 25 calls this way and did not
reproduce the behavior. In the other test I ran, I had two callers in the
queue. One of the calls was answered while the other caller waited. Doing
things this way, I also saw that the waiting caller would immediately ring
the queue member when the first call completed.

This got me thinking a bit, and so let me specify a scenario, given your
setup, where I can see the behavior you describe happening.

Let's say that caller A calls the "service" queue. All the queue members'
phones start ringing. Member 1 picks up the phone. While caller A and
Member 1 are talking, caller B calls the "others" queue. Since both queues
contain the same members, all the same people's phones ring again, except
for member 1 since he is currently talking to caller A. Member 1 finishes
talking to caller A and hangs up. Now what you will see is that all the
other members' phones are ringing, but member 1's phone will not (until the
timeout configured in queues.conf is reached).

Does this sound at all like what you were seeing? Do you have to use
multiple queues and have callers in both of them to reproduce the problem? 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-02-06 15:26 putnopvut      Note Added: 0099652                          
======================================================================