| Summary: | ASTERISK-29623: app_queue: Un-ordered answering of callers | ||
| Reporter: | Leo (llcfhllml) | Labels: | |
| Date Opened: | 2021-08-31 05:28:28 | Date Closed: | |
| Priority: | Minor | Regression? | |
| Status: | Open/New | Components: | Applications/app_queue |
| Versions: | 16.16.2 18.6.0 | Frequency of Occurrence | |
| Related Issues: | |||
| Environment: | debian 10 | Attachments: | |
| Description: | Hi I have a 2 different queues configured with dynamic agents.
All the agents are logged in to all queues with the same weight and priority . When a call is waiting to be served in a queueA and another call waiting in queueB and a user become available in both queues asterisk serve the call with less waiting time. SIMPLE EXAMPLE agent 4000 is the only person logged on queue 301 and queue 302 agent 4000 is on call with CALL1 after 5sec external-number1 call queue 301 after 5sec external-number2 call queue 302 after 5sec agent 4000 hangup CALL1 and queue 302 is the first served by the system ( external-number2 ring on agent 4000) but the queue 301 is the oldest one. QUEUES CONFIG {noformat} [general] persistentmembers=yes eventwhencalled=yes shared_lastcall=yes [template](!) announce-frequency=0 announce-holdtime=no announce-position=no autopause=no autopausebusy=no autopausedelay=0 autopauseunavail=no leavewhenempty=no maxlen=0 memberdelay=0 musicclass=default penaltymemberslimit=0 periodic-announce-frequency=0 queue-callswaiting=silence/1 queue-thereare=silence/1 queue-youarenext=silence/1 reportholdtime=no ringinuse=no servicelevel=60 setinterfacevar=yes strategy=ringall timeoutrestart=no weight=0 wrapuptime=0 autofill=yes joinempty=unavailable [301](template) [302](template) maxlen=4 {noformat} | ||
| Comments: | By: Asterisk Team (asteriskteam) 2021-08-31 05:28:33.085-0500 Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. Please note that log messages and other files should not be sent to the Sangoma Asterisk Team unless explicitly asked for. All files should be placed on this issue in a sanitized fashion as needed. A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report. Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process]. Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur. Please note that by submitting data, code, or documentation to Sangoma through JIRA, you accept the Terms of Use present at [https://www.asterisk.org/terms-of-use/|https://www.asterisk.org/terms-of-use/]. By: Benjamin Keith Ford (bford) 2021-08-31 08:43:44.792-0500 I've opened a ticket for this, but there's no timeframe on when it will get worked. | ||