[asterisk-bugs] [Asterisk 0012552]: Queue handling problems with IAX/possibly others

[Asterisk Bug Tracker]

The following issue has been REOPENED. 
====================================================================== 
http://bugs.digium.com/view.php?id=12552 
====================================================================== 
Reported By:                darren1713
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   12552
Category:                   Applications/app_queue
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     new
Asterisk Version:           1.4.18 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2008-04-29 16:42 CDT
Last Modified:              2008-07-25 18:28 CDT
====================================================================== 
Summary:                    Queue handling problems with IAX/possibly others
Description: 
I'll be glad to develop a fix for this, but I need some feedback as to
why/what/and general intentions.

I have 8 IAX members of a very basic rrmemory queue. When a call comes
into the queue, it will pick a single IAX channel to ring. 

The major problem is that until that IAX channel is answered, ALL
consecutive calls are routed to the same IAX channel. So, here's the
scenario.

> Inbound call -> app_queue -> ring IAX device
http://bugs.digium.com/view.php?id=1
> Inbound call -> app_queue -> ring IAX device
http://bugs.digium.com/view.php?id=1
> Inbound call -> app_queue -> ring IAX device
http://bugs.digium.com/view.php?id=1
IAX device http://bugs.digium.com/view.php?id=1 ANSWERED
> Inbound call -> app_queue -> ring IAX device
http://bugs.digium.com/view.php?id=2
> Inbound call -> app_queue -> ring IAX device
http://bugs.digium.com/view.php?id=2

and this should look like:

> Inbound call -> app_queue -> ring IAX device
http://bugs.digium.com/view.php?id=1
> Inbound call -> app_queue -> ring IAX device
http://bugs.digium.com/view.php?id=2
> Inbound call -> app_queue -> ring IAX device
http://bugs.digium.com/view.php?id=3
IAX device http://bugs.digium.com/view.php?id=1 ANSWERED
> Inbound call -> app_queue -> ring IAX device
http://bugs.digium.com/view.php?id=4
> Inbound call -> app_queue -> ring IAX device
http://bugs.digium.com/view.php?id=5

I would like to discuss why this is happening, or if it's intentional for
other channels such as SIP/ZAP/etc.

I have a patch for iax for counting currently active calls (minus
registrations/pokes/etc) which can help here too.
====================================================================== 

---------------------------------------------------------------------- 
 (0090725) darren1713 (reporter) - 2008-07-25 18:28
 http://bugs.digium.com/view.php?id=12552#c90725 
---------------------------------------------------------------------- 
Why would it be the default behavior to not ring 2 phones if there are two
calls in the queue?

If there are 100 people sitting at a desk, and 100 callers enter the
queue, the second line doesn't ring until the first one answers? and the
third doesn't ring until the second answers? I think the 100'th person
might be sitting there doing a whole lot of nothing for a very long time.

I understand that may be the way it is programmed to work, but it isn't
making much sense to me in a real world scenario. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-07-25 18:28 darren1713     Note Added: 0090725                          
2008-07-25 18:28 darren1713     Status                   closed => new       
2008-07-25 18:28 darren1713     Resolution               suspended => reopened
======================================================================