[asterisk-bugs] [JIRA] (ASTERISK-21563) API Enhancements - CEL refactoring - channel state

[Matt Jordan (JIRA)]

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

Matt Jordan updated ASTERISK-21563:
-----------------------------------

    Target Release Version/s:     (was: 1.8.24.0)
    
> API Enhancements - CEL refactoring - channel state
> --------------------------------------------------
>
>                 Key: ASTERISK-21563
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-21563
>             Project: Asterisk
>          Issue Type: New Feature
>          Components: CEL/General, Core/Stasis
>            Reporter: Matt Jordan
>            Assignee: Kinsey Moore
>              Labels: Asterisk12
>
> 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 first step is to refactor the following:
> * Subscribe to the all channel caching topic in cel.c. Set up a message router to handle channel updates.
> ** When a channel is created, create an AST_CEL_CHANNEL_START event
> ** When a channel is hungup, create an AST_CEL_HANGUP event
> ** When a channel is removed from the cache, create an AST_CEL_CHANNEL_END event
> ** When a channel is answered, create an AST_CEL_ANSWER event
> ** If the application changes on a snapshot, create an AST_CEL_APP_START from the new snapshot
> ** If the application changes on a snapshot, create an AST_CEL_APP_END from the old snapshot
> * Remove all events referenced above
> * Refactor {{ast_cel_check_retire_linkedid}} to occur when an AST_CEL_CHANNEL_END would be raised, that is, when a channel is destroyed. Remove references to it from channel.c; make it a private function.
> ** If a linkedid changes on a channel, call the private version of {{ast_cel_check_retire_linkedid}}

--
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