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

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:                   major
Priority:                   normal
Status:                     new
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-13 05:35 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.

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

---------------------------------------------------------------------- 
 (0130447) davidw (reporter) - 2011-01-13 05:35
 https://issues.asterisk.org/view.php?id=18611#c130447 
---------------------------------------------------------------------- 
I think it almost certain that the channel technology affects this.  In
particular, it may be erroneously doing an external bridge.  Assuming you
are using SIP, I think you need to follow the rules for reporting SIP
problems.  You also need to provide the dialplan, just in case the real
problem is that the feature code is being erroneously detected when
transfers are disabled. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2011-01-13 05:35 davidw         Note Added: 0130447                          
======================================================================