[asterisk-bugs] [JIRA] (ASTERISK-28313) ARI: userevents should be delivered via AMI too

[Joshua C. Colp (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-28313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joshua C. Colp updated ASTERISK-28313:
--------------------------------------

    Assignee: Stefan Repke
      Status: Waiting for Feedback  (was: Triage)

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.

> ARI: userevents should be delivered via AMI too
> -----------------------------------------------
>
>                 Key: ASTERISK-28313
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28313
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_ari_events
>    Affects Versions: 13.8.2, 13.24.1, 16.1.1
>            Reporter: Stefan Repke
>            Assignee: Stefan Repke
>            Severity: Minor
>
> 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*.



--
This message was sent by Atlassian JIRA
(v6.2#6252)