[asterisk-bugs] [JIRA] (ASTERISK-21712) Stasis API - Incorporate the bridging framework into res_stasis app

[Matt Jordan (JIRA)]

Matt Jordan created ASTERISK-21712:
--------------------------------------

             Summary: Stasis API - Incorporate the bridging framework into res_stasis app
                 Key: ASTERISK-21712
                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-21712
             Project: Asterisk
          Issue Type: New Feature
      Security Level: None
          Components: Core/Stasis, Resources/res_stasis_http
            Reporter: Matt Jordan


The Stasis-HTTP application (the actual application provided by res_stasis, not the REST interface portion) needs to be able to do the following:

* For bridges created via the RESTful interface, own and manage the bridges and the channels within them
** Put channels into a bridge
** Remove channels from a bridge
* Maintain knowledge of the bridges for each application and for the channels, such that they can be easily accessed

In general, an application object should own a container of bridge and a container of channels. As channels enter into the Stasis application, they are added to the container of channels.

Bridges should always be created via a REST-ful call, and hence can be added directly without looking for events.

Bridge destruction can occur either through an explicit call or through channel hangup; hence, the application should subscribe to each bridge that it creates.

{noformat}
           1  1                         0   n
app_object ---> ao2_container(channels) ----> ast_channel
        |
        |  1  1                         0   n
        |-----> ao2_container(bridges) -----> ast_bridge
{noformat}

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