[asterisk-bugs] [JIRA] (ASTERISK-21549) AMI 1.4 Improvements - refactor ast_pbx_outgoing_* to use the dial API; add Originate AMI Events

[Joshua Colp (JIRA)]

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

Joshua Colp closed ASTERISK-21549.
----------------------------------

    Resolution: Fixed
    
> AMI 1.4 Improvements - refactor ast_pbx_outgoing_* to use the dial API; add Originate AMI Events
> ------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-21549
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-21549
>             Project: Asterisk
>          Issue Type: New Feature
>          Components: Core/ManagerInterface, Core/Stasis
>            Reporter: Matt Jordan
>            Assignee: Joshua Colp
>              Labels: Asterisk12
>
> Originated calls (via Manager, CLI, Application, Callfile, or Carrier Pigeon) needs to have Dial stasis messages generated for it. This means both {{ast_pbx_outgoing_app}} and {{ast_pbx_outgoing_exten}} need to start a dial operation (potentially asynchronously) and set the channel flag to denote that the channel is being originated.
> The dial API should already raise the appropriate Dial Stasis messages.
> The existing Originate events should be removed and refactored. These should look for Dial stasis messages that have a peer but no caller. This indicates that a channel is being Originated. AMI should raise the event appropriately.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira