| Summary: | ASTERISK-29195: app_queue: AMI QueueMemberStatus event property "InCall" not updated | ||||
| Reporter: | Flamur Dervishi (flamur.dervishi@ikanbi.tech) | Labels: | |||
| Date Opened: | 2020-12-04 03:33:08.000-0600 | Date Closed: | |||
| Priority: | Minor | Regression? | |||
| Status: | Open/New | Components: | Applications/app_queue | ||
| Versions: | 16.15.0 | Frequency of Occurrence | Constant | ||
| Related Issues: |
| ||||
| Environment: | Debian 10, x64 Asterisk 16.15.0 | Attachments: | ( 0) full.txt ( 1) queue_ami_events.txt ( 2) queues.conf.txt | ||
| Description: | We are building a web interface for displaying queues and their members. In order to track the current status of a member we are listening for the event "QueueMemberStatus".
https://wiki.asterisk.org/wiki/display/AST/Asterisk+16+ManagerEvent_QueueMemberStatus This event has a property called "InCall" which according to the documentation tells if a member is currently in call or not. InCall - Set to 1 if member is in call. Set to 0 after LastCall time is updated. When a call is received in this queue, asterisk generates a QueueMemberStatus event, but eventhough the member now is in call, the event property "InCall" is still 0. Event: QueueMemberStatus Privilege: agent,all Timestamp: 1607091943.951917 Queue: Support MemberName: PJSIP/1004 Interface: PJSIP/1004 StateInterface: PJSIP/1004 Membership: dynamic Penalty: 0 CallsTaken: 3 LastCall: 1607086469 LastPause: 1607086441 InCall: 0 Status: 2 Paused: 0 PausedReason: Ringinuse: 0 Wrapuptime: 0 I can confirm that the member is indeed in call also by looking at the Status property of this event: Status: 2 , meaning IN_USE. | ||||
| Comments: | By: Asterisk Team (asteriskteam) 2020-12-04 03:33:10.742-0600 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) 2020-12-04 05:23:48.397-0600 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: Flamur Dervishi (flamur.dervishi@ikanbi.tech) 2020-12-07 06:20:28.083-0600 I tried to give more details by modifying the original post By: Kevin Harwell (kharwell) 2020-12-07 15:47:59.013-0600 Could you please post the full AMI trace from when the agent is rung to answer to when the QueueMemberStatus event is output. Also if you change the agent status after answering does is it still zero? For instance, if you put them on hold. By: Flamur Dervishi (flamur.dervishi@ikanbi.tech) 2020-12-16 04:21:59.187-0600 Below the full trace of AMI events. <removed and added as file> By: Flamur Dervishi (flamur.dervishi@ikanbi.tech) 2020-12-16 04:25:02.957-0600 @Kevin Harwell Indeed the change was reflected when the agent was put on Hold. After the Hold event, the QueueMemberStatus InCall value was set to 1 as you can see above. By: Joshua C. Colp (jcolp) 2020-12-16 04:33:37.932-0600 What is the actual configuration from queues.conf that causes this? (Something as simple as a single option in app_queue can change things so ensuring that configuration is provided for when this issue is worked is important) As well, I posted previously about getting a debug log[1] as app_queue has explicit logging for things going on - is that not possible to get? [1] https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information By: Flamur Dervishi (flamur.dervishi@ikanbi.tech) 2020-12-16 06:38:35.909-0600 We are using realtime configuration for Queues and Queue Members. The definitions of the Queue and QueueMember used to test are in the beginning of the file. The rest of the file is the full debug log while making the test to reproduce the problem. By: Joshua C. Colp (jcolp) 2020-12-16 06:48:26.585-0600 There are still configuration options which can only be set in the queues.conf configuration file, so please attach it as well. By: Flamur Dervishi (flamur.dervishi@ikanbi.tech) 2020-12-16 06:57:11.736-0600 Attached queues.conf configuration file By: Roman Pertsev (romkazor) 2021-03-19 17:20:19.273-0500 Confirm in ASTERISK-29357 | ||||