Summary:ASTERISK-21542: Bridge API Enhancements - get DTMF attended transfers feature complete - configuration support
Reporter:Matt Jordan (mjordan)Labels:Asterisk12
Date Opened:2013-04-17 19:56:41Date Closed:2013-06-24 13:40:03
Status:Closed/CompleteComponents:Core/Bridging Features
Versions:Frequency of
Description:There's some oddities in attended transfers that have to be ironed out in the new Bridging Framework in order for the new system to be feature complete. The first step is just to implement the configuration parsing and storage of the following parameters:

* transferdigittimeout
* xfersound
* xferfailsound
* pickupexten
* pickupsound
* pickupfailsound
* featuredigittimeout
* atxfernoanswertimeout
* atxferdropcall
* atxferloopdelay
* atxfercallbackretries

We need to support defining a \[featuremap\] context:

* blindxfer
* disconnect
* automon
* atxfer
* parkcall
* automixmon

And we need to support an \[applicationmap\] context:

And all other contexts are a dynamic feature group.

These configuration items should be parsed using the Configuration Framework. APIs should be provided that let the bridging framework query for the features and configuration settings channels should have when they join a bridge.