Summary:ASTERISK-21566: API Enhancements - CEL refactoring - cleanup
Reporter:Matt Jordan (mjordan)Labels:Asterisk12
Date Opened:2013-04-17 22:24:41Date Closed:2013-06-25 08:11:01
Status:Closed/CompleteComponents:CEL/General Core/Stasis
Versions:Frequency of
Description:Yay, CEL!

With Stasis-Core, we no longer need a bunch of CEL events all over the code, as the state of channels and bridges is conveyed across the Stasis-Core message bus. The final step is to refactor the following:

* Determine when a call is being forwarded. We currently don't have a Stasis-Core message for this, and we typically infer this by a dial message. If needed, add a new JSON blob to the various Dial messages raised when a call forward occurs and raise AST_CEL_FORWARD. Note both {{app_dial}} and {{app_queue}} do this currently.
* Remove AST_CEL_BRIDGE_UPDATE. Masquerades shouldn't occur in situations that aren't accounted for both other operations.
* Add a CEL topic with a generic JSON blob message. Add a message router for this.
** Refactor the generic CEL user event to publish to this topic. Send the message as JSON; put out over CEL.
** Refactor instances of AST_CEL_HOOKFLASH, AST_CEL_3WAY_START, AST_CEL_3WAY_END to use JSON to the CEL topic.
Comments:By: Kinsey Moore (kmoore) 2013-06-17 07:34:24.189-0500

Work on this issue will be occurring in https://origsvn.digium.com/svn/asterisk/team/kmoore/cel_cleanup

By: Kinsey Moore (kmoore) 2013-06-20 09:11:22.896-0500

Work for the first two parts is now committed. There were no instances of hookflash or 3way start/end to refactor in 11 or trunk.