[Home]

Summary:ASTERISK-22682: No dtmf cognition of features.conf after Ami Action Bridge
Reporter:Dirk Wendland (kesselklopfer79)Labels:
Date Opened:2013-10-11 07:14:20Date Closed:2013-10-14 12:42:20
Priority:CriticalRegression?
Status:Closed/CompleteComponents:
Versions:11.5.1 Frequency of
Occurrence
Related
Issues:
is duplicated byASTERISK-22706 No dtmf cognition of features.conf after Ami Action Bridge
Environment:Attachments:
Description:Szenario
{NOFORMAT}
First attended transfer works well:

SipAccount1 <-> LocalChannel <-> LocalChannel <-> SipAccount2

Now we Bridge over Ami

SipAccount1 <-> SipAccount2

Now no dtmf feature codes are working. A second attended transfer is impossible.
{NOFORMAT}
Comments:By: Matt Jordan (mjordan) 2013-10-14 12:41:56.810-0500

This is not a bug. Bridges created as a result of the AMI Bridge Action do not have DTMF feature codes enabled for them. If anything, this would be a feature request.
By: Dirk Wendland (kesselklopfer79) 2013-10-15 02:26:18.272-0500

Created => https://issues.asterisk.org/jira/browse/ASTERISK-22706
By: Matt Jordan (mjordan) 2013-10-15 07:39:36.594-0500

As I've already commented, creating additional issues when your original issue has been closed is not helpful. Please do not continue to do this.

The Bridge AMI action does not have the ability to specify DTMF features on the channels placed into the bridge, at least in Asterisk 11. Asterisk 12 has some capabilities in this regard by using the CHANNEL function's dtmf_features attribute and the FEATURE_MAP function.
By: Matt Jordan (mjordan) 2013-10-15 07:44:58.610-0500

Regardless, this would be considered an improvement to the Bridge AMI action, and not a bug. If you'd like to provide this improvement to the action, this issue can be reopened when a patch is attached.

As a workaround, you can:

(a) Redirect the channels to an extension that uses the Bridge application to bridge the two channels together
(b) Use the LocalOptimizeAway action to force an optimization of the Local channel. So long as DTMF features were put on the original bridge between the SIP channels and Local channels, whichever bridge "survives" the optimization will continue to have features.