[asterisk-dev] Bug: Queue calls delivered out of order ( Fee for fix offered )

[Curtis Raams]

Are you looking to share that code? Even for a bounty?



Curtis Raams 
Chief Technical Officer 
Level 6, 140 Queen St. Melbourne Victoria 3000
T: 03 8665 8305 F: 03 9945 7502 M: 0404 394 904
E: craams at staff.ains.net.au W: www.ains.com.au


 
This email and any attachments may contain privileged and confidential information and are intended for the named addressee only. If you have received this e-mail in error, please notify us immediately by telephone on 1300 887 877 and delete this e-mail immediately. Any confidentiality, privilege or copyright is not waived or lost because this e-mail has been sent to you in error. It is your responsibility to check this e-mail and any attachments for viruses.
BE GREEN! Read from the screen.



-----Original Message-----
From: asterisk-dev-bounces at lists.digium.com [mailto:asterisk-dev-bounces at lists.digium.com] On Behalf Of Paul Belanger
Sent: Tuesday, 3 September 2013 12:26 PM
To: asterisk-dev at lists.digium.com
Subject: Re: [asterisk-dev] Bug: Queue calls delivered out of order ( Fee for fix offered )

On 13-09-02 07:55 AM, Curtis Raams wrote:
> Hello Developers,
>
> We are experiencing unexpected behaviour in queue call delivery when an agent is a member of multiple queues, all with the same priority and weights.
> My situation was described accurately be another user here: http://forums.digium.com/viewtopic.php?p=162018 however this remained unresolved.
>
> AINS would be willing to pay a fee to have this issue resolved urgently as it is impacting on service delivery to a high degree.
>
> I have pasted below (and attached) a list of sample calls which were out of order today. As you can see, the situation applies where the agent is a member of more than one queue.
> It never delivers a call out of order to the same queue, the situation is other queues not respecting the longest waiting caller across all queues.
>
> I have attempted various combinations of (autofill, shared_lastcall).
>
Know issue with app_queue, first in is not guaranteed to be the first out.  Additional, long wait call also does not mean first to be answered too.

Basically, we reworked our multi queue setup in app_queue to a single queue, updating reports to deal with the change.  That is going to be the fastest solution to your LWC issues.

Long term, we rewrote app_queue.  We are presenting our new application at astricon, so if you are going, feel free to sit in.

--
Paul Belanger | PolyBeacon, Inc.
Jabber: paul.belanger at polybeacon.com | IRC: pabelanger (Freenode)
Github: https://github.com/pabelanger | Twitter: 
https://twitter.com/pabelanger

--
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-dev

______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com ______________________________________________________________________

______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________