[asterisk-bugs] [JIRA] (ASTERISK-22037) Fix AMI action AttendedTransfer to use both DTMF Begin and End

[Richard Mudgett (JIRA)]

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

Richard Mudgett updated ASTERISK-22037:
---------------------------------------

    Reviewboard Link: https://reviewboard.asterisk.org/r/2752/
    
> Fix AMI action AttendedTransfer to use both DTMF Begin and End
> --------------------------------------------------------------
>
>                 Key: ASTERISK-22037
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-22037
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/ManagerInterface
>    Affects Versions: 12
>            Reporter: Matt Jordan
>            Assignee: Richard Mudgett
>      Target Release: 12
>
>
> The bridging core feature hooks need both a DTMF begin and end frame in order to fire. The AMI action AttendedTransfer only sends AST_FRAME_DTMF (end frames).
> {noformat}
> /* BUGBUG action_atxfer() is broken because the bridge DTMF hooks need both begin and end events to match correctly. */
> 	for (digit = feature_code; *digit; ++digit) {
> 		struct ast_frame f = { AST_FRAME_DTMF, .subclass.integer = *digit };
> 		ast_queue_frame(chan, &f);
> 	}
> 	for (digit = exten; *digit; ++digit) {
> 		struct ast_frame f = { AST_FRAME_DTMF, .subclass.integer = *digit };
> 		ast_queue_frame(chan, &f);
> 	}
> {noformat}
> *Note:*
> As goofy as setting a feature on a channel and then triggering it is, this works and it's not worth using a more elegant approach.

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