[asterisk-bugs] [JIRA] (ASTERISK-21180) Implement channel state events for Stasis HTTP

[Kinsey Moore (JIRA)]

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

Kinsey Moore updated ASTERISK-21180:
------------------------------------

    Description: 
Now that Stasis-Core is moving along and channel state is getting put out onto the Stasis-Core message bus, we can start exposing channel state changes through Stasis-HTTP.

Channels in a Stasis application - or created as a result of an action in a Stasis application (such as an outbound dial) should have their states sent to the appropriate client over websockets.

 * Create JSON events representing channel state changes, channel creation, and channel hangup.
 * -Create an XML schema in source for documenting the events. This might be similar to the existing managerEvent schema (but will probably be better served by something less AMI peculiar)-
 * Pass events through Stasis-Core out app_stasis' websocket. Note that the channel events might want to live in something other than res_stasis_http

Revised task list:
 * Get parity with AMI for channels that are already in a Stasis Application
 * Define the subscription model for channels/endpoints
 * Scope out the work for propagating channel/endpoint messages for subscriptions

  was:
Now that Stasis-Core is moving along and channel state is getting put out onto the Stasis-Core message bus, we can start exposing channel state changes through Stasis-HTTP.

Channels in a Stasis application - or created as a result of an action in a Stasis application (such as an outbound dial) should have their states sent to the appropriate client over websockets.

 * Create JSON events representing channel state changes, channel creation, and channel hangup.
 * Create an XML schema in source for documenting the events. This might be similar to the existing managerEvent schema (but will probably be better served by something less AMI peculiar)
 * Pass events through Stasis-Core out Stasis-HTTP's websocket. Note that the channel events might want to live in something other than res_stasis_http

    
> Implement channel state events for Stasis HTTP
> ----------------------------------------------
>
>                 Key: ASTERISK-21180
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-21180
>             Project: Asterisk
>          Issue Type: New Feature
>      Security Level: None
>          Components: Core/Stasis, Resources/res_stasis_http
>    Affects Versions: 12
>            Reporter: Matt Jordan
>            Assignee: Kinsey Moore
>              Labels: Asterisk12
>
> Now that Stasis-Core is moving along and channel state is getting put out onto the Stasis-Core message bus, we can start exposing channel state changes through Stasis-HTTP.
> Channels in a Stasis application - or created as a result of an action in a Stasis application (such as an outbound dial) should have their states sent to the appropriate client over websockets.
>  * Create JSON events representing channel state changes, channel creation, and channel hangup.
>  * -Create an XML schema in source for documenting the events. This might be similar to the existing managerEvent schema (but will probably be better served by something less AMI peculiar)-
>  * Pass events through Stasis-Core out app_stasis' websocket. Note that the channel events might want to live in something other than res_stasis_http
> Revised task list:
>  * Get parity with AMI for channels that are already in a Stasis Application
>  * Define the subscription model for channels/endpoints
>  * Scope out the work for propagating channel/endpoint messages for subscriptions

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