[Home]

Summary:ASTERISK-30443: app_queue: Add "Agent Abandoned" AMI event
Reporter:Joze Zivic (jozza)Labels:patch
Date Opened:2023-02-27 05:09:17.000-0600Date Closed:
Priority:MajorRegression?
Status:Open/NewComponents:Applications/app_queue Core/ManagerInterface
Versions:GIT 20.1.0 Frequency of
Occurrence
Related
Issues:
Environment:Attachments:( 0) agent_abandoned_ami_event.diff
Description:There should be an ami event "AgentAbandoned", when caller leaves the queue while agent device is ringing. This is important for sake of completion of the AgentCalled event, which designates a unique start of a channel call, which is now unlinked to the end of the call to the agent channel.
Comments:By: Asterisk Team (asteriskteam) 2023-02-27 05:09:20.002-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) 2023-02-27 05:15:14.763-0600

Do you plan on contributing such a change?

By: Joze Zivic (jozza) 2023-02-27 05:51:19.578-0600

Sure, why not.
I can provide a patch file with this feature, but don't have a wish to participate in the process of integrating the patch to the trunk through automated systems. There are just too many unrelated tasks there, which i don't want to learn. Would that be acceptable?


By: Joshua C. Colp (jcolp) 2023-02-27 05:54:17.518-0600

You're free to attach a patch, ultimately it will be up to someone else to go through that process instead. There's no time frame on if/when that would occur.

By: Joze Zivic (jozza) 2023-03-03 11:02:11.449-0600

Added AgentAbandoned AMI event, which is raised when a caller hangs up a ringing call at queue member

By: Joze Zivic (jozza) 2023-03-03 11:12:12.620-0600

I just realized that the event is currently only generated when caller hangs up, but it may not be generated when caller leaves the queue without hanging up. I haven't tested this.


By: Joze Zivic (jozza) 2023-03-05 03:40:02.539-0600

It seems that the patch is still ok, no additional changes were required, i only changed the doc description of the AgentAbandoned event to say it is raised  when a caller leaves the queue while member(s) still ringing.