[asterisk-bugs] [Asterisk 0018611]: inband DTMF cannot be detected and trigger service execute when A and B both use u-law (the same codec)

Asterisk Bug Tracker noreply at bugs.digium.com
Sun Jan 16 05:43:54 CST 2011


A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=18611 
====================================================================== 
Reported By:                shihchuan
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   18611
Category:                   Core/RTP
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.8.1.1 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2011-01-13 05:04 CST
Last Modified:              2011-01-16 05:43 CST
====================================================================== 
Summary:                    inband DTMF cannot be detected and trigger service
execute when A and B both use u-law (the same codec)
Description: 
1. A and B both use the same codec (u-law, a-law).
When A enter *96(transfer feature key), transfer service don't be executed
but B hear dtmf tone.

2. If A and B use different codec.(A use u-law, B use a-law) 
When A enter *96(transfer feature key), transfer sevice is executed.

====================================================================== 

---------------------------------------------------------------------- 
 (0130530) nickilo (reporter) - 2011-01-16 05:43
 https://issues.asterisk.org/view.php?id=18611#c130530 
---------------------------------------------------------------------- 
I can confirm this bug exist. But at the moment i have two asterisk with
the same binary, the same configuration files. On can reproduce the
problem, the other not.
I'm gonna try to understand the problem, give you a way to reproduce the
problem and the debug output.

I confirm also that using différent codecs "solves" the problem. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2011-01-16 05:43 nickilo        Note Added: 0130530                          
======================================================================




More information about the asterisk-bugs mailing list