| Summary: | ASTERISK-21549: AMI 1.4 Improvements - refactor ast_pbx_outgoing_* to use the dial API; add Originate AMI Events | ||
| Reporter: | Matt Jordan (mjordan) | Labels: | Asterisk12 |
| Date Opened: | 2013-04-17 21:08:40 | Date Closed: | 2013-05-18 14:48:24 |
| Priority: | Major | Regression? | |
| Status: | Closed/Complete | Components: | Core/ManagerInterface Core/Stasis |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | 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. | ||
| Comments: | |||