[asterisk-bugs] [JIRA] (ASTERISK-15992) [patch] Originate Action output is inconsistent with other manager actions
Corey Farrell (JIRA)
noreply at issues.asterisk.org
Thu Dec 14 13:32:07 CST 2017
[ https://issues.asterisk.org/jira/browse/ASTERISK-15992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Corey Farrell updated ASTERISK-15992:
-------------------------------------
Assignee: Ryan Bullock
Status: Waiting for Feedback (was: Open)
Are you interested in pursuing this further? If so the patch will need to be rebased so it can apply the the current {{master}} branch and it will need to go through code review.
----
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
> [patch] Originate Action output is inconsistent with other manager actions
> --------------------------------------------------------------------------
>
> Key: ASTERISK-15992
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-15992
> Project: Asterisk
> Issue Type: Bug
> Components: Core/ManagerInterface
> Reporter: Ryan Bullock
> Assignee: Ryan Bullock
> Severity: Minor
> Attachments: orignatepatch2.diff, orignatepatch.diff
>
>
> The Orginate action output is inconsistent with how other manager actions respond, and is even inconsistent with how itself responds with/without Async: 1, supplying different information depending on if Async is used or not.
> It also will not send the response event (when using async) back to the manager session if that manager session has events turned off. Other actions that respond with events will do so even if events are turned off.
> ****** ADDITIONAL INFORMATION ******
> Responses should be consistent whether Async is used or not, and it should always respond on the manager connection regardless of the connections eventmask.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list