[Home]

Summary:ASTERISK-26989: Queue won't call members on calls from THAT queue
Reporter:Daniel Journo (journo)Labels:
Date Opened:2017-05-08 15:19:00Date Closed:2020-01-14 11:13:59.000-0600
Priority:MinorRegression?
Status:Closed/CompleteComponents:Applications/app_queue
Versions:13.15.0 Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:Since upgrading to v13 PJSIP from v11 chan_sip, pjsip queue members can only receive one call per queue even though 'ringinuse' is set on all queues.

In an example, I have two queues 'support' and 'sales'. All pjsip endpoints are members of both queues. If endpoint 1 takes a call from the support queue, they won't receive another call from the support queue until they end the first call. But they can receive a call from the sales queue.

Comments:By: Asterisk Team (asteriskteam) 2017-05-08 15:19:01.128-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.

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].

By: Daniel Journo (journo) 2017-05-08 15:30:21.817-0500

It seems that the issue only occurs when wrapuptime > 0.
If wrapuptime is 0, then there calls are sent through as expected.

Since an endpoint that is busy wrapping up is considered 'in-use', and ringinuse is set, I would expect the wrapuptime to be ignored.

By: Rusty Newton (rnewton) 2017-05-15 19:58:31.024-0500

Thank you for taking the time to report this bug and helping to make Asterisk better. Unfortunately, we cannot work on this bug because your description did not include enough information. Please read over the Asterisk Issue Guidelines [1] which discusses the information necessary for your issue to be resolved and the format that information needs to be in. We would be grateful if you would then provide a more complete description of the problem. At a minimum, we need:

1. The specific steps or actions you took that caused you to encounter the problem.
2. The behavior you expected and the location of documentation that led you to that expectation.
3. The behavior you actually encountered.

To demonstrate the issue in detail, please include Asterisk log files generated per the instructions on the wiki [2]. If applicable, please ensure that protocol-level trace debugging is enabled, e.g., 'sip set debug on' if the issue involves chan_sip, and configuration information such as dialplan and channel configuration.

Thanks!

[1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines

[2] https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information



By: Rusty Newton (rnewton) 2017-05-15 19:59:46.391-0500

In regards to my previous comment, specifically provide at least:

* Exact, minimal configuration required to reproduce the issue
* Asterisk logs, with verbose and debug levels, demonstrating the issue (be sure verbose and debug are both set to 5 or higher)


By: David Brillert (aragon) 2017-05-16 12:52:13.507-0500

Since the issue only occurs when wrapuptime > 0
This is probably another duplicate of ASTERISK-26400

By: Asterisk Team (asteriskteam) 2017-05-31 12:00:01.430-0500

Suspended due to lack of activity. This issue will be automatically re-opened if the reporter posts a comment. If you are not the reporter and would like this re-opened please create a new issue instead. If the new issue is related to this one a link will be created during the triage process. Further information on issue tracker usage can be found in the Asterisk Issue Guidlines [1].

[1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines