| Summary: | ASTERISK-21339: Bridge API Enhancements - add CCSS, Connected Line, Pre-Dial to the Dial API | ||
| Reporter: | Matt Jordan (mjordan) | Labels: | |
| Date Opened: | 2013-03-29 09:30:04 | Date Closed: | 2013-04-15 16:00:12 |
| Priority: | Major | Regression? | |
| Status: | Closed/Complete | Components: | Core/Bridging Core/Channels |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | Please see the [Bridge Construction|http://svn.asterisk.org/svn/asterisk/team/group/bridge_construction/] Team project for the current status of this work.
In order for the Dial API to be used by {{app_dial}} and other consumers, a number of features have to be incorporated into it from {{app_dial}}: * CCSS * Connected Line/Redirecting interception subroutines/macros * Pre-dial subroutines Additionally, the Dial API, being now a bridge mixing technology, needs to have the ability to have a subroutine/macro executed on the participating channels before it transitions to a two party bridge. This would probably be a useful enhancement to the Bridging Framework in general - when a bridge technology changes or a merge operation happens, execute a subroutine on some subset of channels. | ||
| Comments: | By: Matt Jordan (mjordan) 2013-04-15 16:00:12.760-0500 Initially we thought we would stick the Dial API under the Bridge API as well, but we're going to go a different path instead. While having dialing be a bridge has a lot of advantages, there's only so much we can cram into 12 and tackling all of the complexity of dialing is nearly as big a task as the bridging work. This can always be resurrected if someone would like to take it on or we have more time. | ||