[asterisk-bugs] [JIRA] (ASTERISK-22682) No dtmf cognition of features.conf after Ami Action Bridge

[Matt Jordan (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-22682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=210949#comment-210949 ] 

Matt Jordan edited comment on ASTERISK-22682 at 10/15/13 8:01 AM:
------------------------------------------------------------------

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.
                
      was (Author: mjordan):
    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 also redirect the channels to an extension that uses the Bridge application to bridge the two channels together.
                  
> No dtmf cognition of features.conf after Ami Action Bridge
> ----------------------------------------------------------
>
>                 Key: ASTERISK-22682
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-22682
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>    Affects Versions: 11.5.1
>            Reporter: Dirk Wendland
>            Severity: Critical
>
> 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}

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