[asterisk-bugs] [JIRA] (ASTERISK-29380) Add Flash AMI event to handle flash events

[Kevin Harwell (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-29380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=254433#comment-254433 ] 

Kevin Harwell commented on ASTERISK-29380:
------------------------------------------

Thanks for the contribution! If you'd like your contribution to be included faster, you should submit your patch for code review by the Asterisk Developer Community. To do so, please follow the Code Review [1] instructions on the wiki. Be sure to:
* Verify that your patch conforms to the Coding Guidelines [2]
* Review the Code Review Checklist [3] for common items reviewers will look for
* If necessary, provide tests for the Asterisk Test Suite that verify the correctness of your patch [4]

When ready, submit your patch and any tests to Gerrit [5] for code review.

Thanks!

[1] https://wiki.asterisk.org/wiki/display/AST/Code+Review
[2] https://wiki.asterisk.org/wiki/display/AST/Coding+Guidelines
[3] https://wiki.asterisk.org/wiki/display/AST/Code+Review+Checklist
[4] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Test+Suite+Documentation
[5] https://wiki.asterisk.org/wiki/display/AST/Gerrit+Usage



> Add Flash AMI event to handle flash events
> ------------------------------------------
>
>                 Key: ASTERISK-29380
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-29380
>             Project: Asterisk
>          Issue Type: Improvement
>      Security Level: None
>          Components: Channels/General, Channels/NewFeature
>    Affects Versions: 18.3.0
>            Reporter: N A
>              Labels: patch
>         Attachments: channel.patch, manager_channels.patch, stasis_channels.c.patch, stasis_channels.h.patch, stasis.patch, stasis_sample.patch
>
>
> The following patches raises AMI events upon AST_CONTROL_FLASH events so that hook flashes sent to Asterisk can be acted upon if desired. The following patch is currently in production on my switch and works as expected. It does not create a conflict with any existing functionality.



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