Summary:	ASTERISK-28313: ARI: userevents should be delivered via AMI too
Reporter:	Stefan Repke (stefffan@gmx.de)	Labels:
Date Opened:	2019-02-28 06:57:17.000-0600	Date Closed:	2019-03-01 07:24:55.000-0600
Priority:	Minor	Regression?
Status:	Closed/Complete	Components:	Resources/res_ari_events
Versions:	13.8.2 13.24.1 16.1.1	Frequency of Occurrence	Constant
Related Issues:
Environment:		Attachments:
Description:	ARI userevents (via POST /ari/events/user/\{eventName\}) are distributed via AMI if and only if a channel is set as source. In order to test it: 1. Listen to AMI 2. Create an ARI application 3a. Send userevent (via ARI; to the application) with channel source 3b. Send userevent (via ARI; to the application) with bridge source 3c. Send userevent (via ARI; to the application) with endpoint source 3d. Send userevent (via ARI; to the application) *without* source Results: All userevents were delivered to the ARI application. Only the userevent from case *3a* was delivered to the AMI listener. Expected results: All userevents should be delivered to the ARI application *and AMI listeners*.
Comments:	By: Asterisk Team (asteriskteam) 2019-02-28 06:57:17.919-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. 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. By: Joshua C. Colp (jcolp) 2019-02-28 07:09:05.652-0600 Are you planning to create a patch and submit it? The way it works now is due to AMI legacy. The only place you could execute UserEvent was from the dialplan, which is on a channel. That's why it behaves the way it does now. By: Stefan Repke (stefffan@gmx.de) 2019-03-01 07:00:30.194-0600 Thank you Joshua for sharing your thoughts. You are right: userevents that are created in the dialplan by the application {{UserEvent}} are always related to a channel. But you can also create them via AMI by the manager action {{UserEvent}} -- optionally related to a channel (by specifying {{channel}}/{{uniqueId}})! --- In our application, all clients have an AMI connection. Over the years, many parts of inter client communication is based on userevents created by AMI action. We have like 100 different userevent types and most of them are not related to a channel. This is the reason why I expect the ARI command {{userEvent}} to deliver all userevents via AMI too -- regardless of being related to a channel/bridge/etc. --- Regarding submission of a patch: Actually, I'm a Java pro with only theoretical expertise in C. I can try to fix this, but I can't promise ... ;-) By: Joshua C. Colp (jcolp) 2019-03-01 07:24:55.572-0600 This would be a feature improvement to this functionality, we don't currently keep issues open for these things so I'm suspending this. If someone would like to work on this then the issue can be reopened.