[asterisk-bugs] [JIRA] (ASTERISK-17640) [patch] Enabled dynamic features swallow DTMF codes (even if no match)

[Matt Jordan (JIRA)]

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

Matt Jordan closed ASTERISK-17640.
----------------------------------

    Resolution: Duplicate

This looks to have been a duplicate of ASTERISK-17640. If that is not the case, please contact a bug marshal in #asterisk-bugs and we will be happy to reopen this issue. Thanks!
                
> [patch] Enabled dynamic features swallow DTMF codes (even if no match)
> ----------------------------------------------------------------------
>
>                 Key: ASTERISK-17640
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-17640
>             Project: Asterisk
>          Issue Type: Bug
>          Components: Features
>            Reporter: Kirill Katsnelson
>            Severity: Minor
>         Attachments: dtmffix.patch, dtmf.patch
>
>
> With a dynamic feature enabled, DTMF messages, if sent quickly enough, intermittently dropped.
> ****** STEPS TO REPRODUCE ******
> 1. Create 2 SIP peers in sip.conf. No special settings necessary.
> {code}
> [base](!)
>   context=from-sip
>   type=friend
>   host=dynamic
>   qualify=no
> [250](base)
> [252](base)
> {code}
> 2. In features.conf, add a dynamic feature. It is essential for the reproduction that feature DTMF pattern is longer that 1 digit.
> {code}
> xpeercallee => AA,peer/callee,Noop
> xpeercaller => BB,peer/caller,Noop
> xselfcallee => CC,self/callee,Noop
> xselfcaller => DD,self/caller,Noop
> {code}
> 3. In extension.ael, add
> {code}
> context from-sip {
>   252 => {
>     __DYNAMIC_FEATURES="xpeercaller";
> //    __DYNAMIC_FEATURES="xselfcaller";
> //    __DYNAMIC_FEATURES="xpeercallee";
> //    __DYNAMIC_FEATURES="xselfcallee";
>     Dial(SIP/252);
>    }
> }
> {code}
> 4. Reload asterisk, register 2 phones for the peers, and from peer 250 dial 252. Answer 252. Prepare to register DTMF messages on the called device, either by hearing, or logging on a softphone, or capturing RTP traffic. I did all three.
> Type a sequence of DTMF digits quickly, like 1/16 notes in quite a fast tempo. I find it convenient to play 4555556. Of that sequence of 7 messages, you will hear between 2 and 4 on the called device, depending on how fast or lucky you are.
> 5. Repeat with
>  * xselfcaller only enabled (reproduces);
>  * peercallee/selfcallee enabled (does not reproduce; which means the bug happens only if a feature is enabled on the controlling channel, the caller in our case)
>  * none of the dynamic features enabled (does not reproduce)
>  * With feature codes shortened to one digit (does not reproduce: need at least 2-digit long codes). I. e. this does not repro the problem
> {code}
> xpeercallee => A,peer/callee,Noop
> xpeercaller => B,peer/caller,Noop
> xselfcallee => C,self/callee,Noop
> xselfcaller => D,self/caller,Noop
> {code}
> ****** ADDITIONAL INFORMATION ******
> This is regression, 1.6 did not have the problem.
> I do not have a patch, have not been working on one, and currently not looking into the problem.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira