| Summary: | ASTERISK-29971: Calls not connected while using min_/max_penalty and weight | ||||
| Reporter: | EDV O-TON (edvoton) | Labels: | |||
| Date Opened: | 2022-03-16 05:06:43 | Date Closed: | 2022-03-16 05:37:36 | ||
| Priority: | Major | Regression? | No | ||
| Status: | Closed/Complete | Components: | Applications/app_queue | ||
| Versions: | 18.10.1 | Frequency of Occurrence | Constant | ||
| Related Issues: |
| ||||
| Environment: | Ubuntu 20.04 with latest patches | Attachments: | ( 0) debuglog.txt | ||
| Description: | We have some queues where we use queuerules and min-/max-penalties to create an overflow to other agents. If the weight of the queue with penalty settings is higher than other ones the agents are in, they will not get any calls of these queues until there are no calls for the higher weighted queues.
Description: Agent has two queues A and B, both with penalty 60. Queue A has a higher weight ( e.g. 66) than queue B (e.g. 65). Queue A has a min_penalty = 0 and max_penalty = 50, so that the agent is outside the range. Queue A has a queuerule, that will raise the maxpenalty after 30 seconds by 10, so that the agent gets the call. The queue A gets a call, then queue B gets a call, too. The queue B call isn't transferred to the agent until the call in queue A is connected to another agent or the caller quits. A test with weights vice versa worked as expected and the call ist immediately connected to the agent Here are the minimal config files to reproduce: queues.conf ------------ [666] weight=66 member => PJSIP/123,60,testagent defaultrule = testrule [667] weight=65 member => PJSIP/123,60,testagent ------------ extension.conf ------------ [default] exten => 666,1,Answer() same => n,Set(QUEUE_MIN_PENALTY=0) same => n,Set(QUEUE_MAX_PENALTY=50) same => n,Queue(666) exten => 667,1,Answer() same => n,Queue(667) ------------ queuerules.conf ------------ [testrule] penaltychange => 30,+10 ------------ | ||||
| Comments: | By: Asterisk Team (asteriskteam) 2022-03-16 05:06:45.464-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: Joshua C. Colp (jcolp) 2022-03-16 05:26:56.635-0500 Is this not a duplicate of ASTERISK-29199 that you've already filed? By: EDV O-TON (edvoton) 2022-03-16 05:33:00.164-0500 I think it's the same issue that's responsible for the bug, but we could nail it down and it's not due to paused agents but just to penalties and weight By: Joshua C. Colp (jcolp) 2022-03-16 05:37:36.316-0500 Please update that issue instead of creating a new issue. | ||||