| Summary: | ASTERISK-30130: app_queue: AMI "Event: AgentComplete" is sometimes missing data when channel is hung up by AMI | ||||
| Reporter: | Kristian Høgh (kfhdk) | Labels: | |||
| Date Opened: | 2022-07-07 04:22:20 | Date Closed: | |||
| Priority: | Minor | Regression? | No | ||
| Status: | Open/New | Components: | Applications/app_queue | ||
| Versions: | GIT 18.13.0 | Frequency of Occurrence | Occasional | ||
| Related Issues: |
| ||||
| Environment: | Attachments: | ( 0) bad_AgentComplete.txt ( 1) good_AgentComplete.txt | |||
| Description: | I call a queue and answers the call.
From AMI I send "Action: Hangup" on the agents channel. Sometimes the AMI "Event: AgentComplete" is incomplete. Bad: Event: AgentComplete Privilege: agent,all Timestamp: 1657183503.744112 Queue: q-8652-88 Interface: SIP/202@hpbx MemberName: 202 HoldTime: 3 TalkTime: 17 Reason: caller Good: Event: AgentComplete Privilege: agent,all Timestamp: 1657183715.561605 Channel: SIP/hpbx-0000000c ChannelState: 6 ChannelStateDesc: Up CallerIDNum: 201 CallerIDName: 201 ConnectedLineNum: <unknown> ConnectedLineName: <unknown> Language: da AccountCode: Context: queue Exten: s Priority: 40 Uniqueid: 1657183708.12 Linkedid: 1657183708.12 Queue: q-8652-88 Interface: SIP/202@hpbx MemberName: 202 HoldTime: 2 TalkTime: 5 Reason: caller | ||||
| Comments: | By: Asterisk Team (asteriskteam) 2022-07-07 04:22:20.771-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: Kristian Høgh (kfhdk) 2022-07-07 04:27:07.907-0500 Asterisk CLI with debug 9 as agent channel is hung up by AMI. A good and a bad AgentComplete example. By: Kristian Høgh (kfhdk) 2022-07-07 05:33:08.064-0500 I can't see it is the same problem as ASTERISK-25187 I always hang up the agents channel, and sometimes the AgenCompleted event is missing data. In ASTERISK-25187, the available data is dependent on which channel is hung up. Also, I can only reproduce the problem using AMI hangup action By: Asterisk Team (asteriskteam) 2022-07-07 05:33:08.280-0500 This issue has been reopened as a result of your commenting on it as the reporter. It will be triaged once again as applicable. By: Joshua C. Colp (jcolp) 2022-07-07 05:36:57.982-0500 I've leave this open and linked if you wish, but I do believe it's the same underlining issue with how the event is fundamentally produced, and what information is available at the time. This just exposes it in a different way. | ||||