[asterisk-bugs] [JIRA] (ASTERISK-21972) Bridge creation should allow for something more than mixing type during creation

[Matt Jordan (JIRA)]

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

Matt Jordan reassigned ASTERISK-21972:
--------------------------------------

    Assignee:     (was: David M. Lee)
    
> Bridge creation should allow for something more than mixing type during creation
> --------------------------------------------------------------------------------
>
>                 Key: ASTERISK-21972
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-21972
>             Project: Asterisk
>          Issue Type: Bug
>          Components: Core/Stasis, Resources/res_stasis_http
>    Affects Versions: 12
>            Reporter: Matt Jordan
>              Labels: Asterisk12
>
> There's basically two kinds of bridges we want to make today through ARI:
> # Holding bridges, to be used for waiting areas
> # "smart" bridges for 2+ party mixing
> Currently, this is specified using "holding" and "mixing", which works well when you want to specify the media mixing used within a bridge.
> However, there are other things you want to specify.
> # You may want to specify that a features bridge with Asterisk DTMF capabilities is created. This would allow ARI to take advantage of most of the work being done in the increasingly inaptly named "basic" bridge.
> # You may subclass the holding bridge to provide a better queue experience. While this would continue to use the holding bridge mixing technology, it would be something a bit more than just the standard 'holding' bridge.
> In general, we should be able to specify a subclass of a particular mixing technology on creation OR specify parameters that we want to pass to the creation of the bridge. This would allow for further expansion of the bridging types, as well as allow users to take better advantage of the existing mixing technologies.

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