[asterisk-bugs] [Asterisk 0013053]: Called Party's inband DTMF removed almost entirely with overlapdial and non-native bridging

Asterisk Bug Tracker noreply at bugs.digium.com
Wed Dec 10 12:19:52 CST 2008


A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=13053 
====================================================================== 
Reported By:                Seb7
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   13053
Category:                   Channels/chan_dahdi
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.4.19 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2008-07-10 09:50 CDT
Last Modified:              2008-12-10 12:19 CST
====================================================================== 
Summary:                    Called Party's inband DTMF removed almost entirely
with overlapdial and non-native bridging
Description: 
If you are using inband DTMF (tested on two Zap channels), and two bridged
channels are not bridged natively (e.g. because you are using MixMonitor),
and the incoming call used overlap dialing, and the Called Party tries
sending DTMF, you hear a blip and perhaps a few milliseconds of tone, but
not enough for the DTMF to be recognised by an application on the Calling
Party side. (Asterisk does not recognize the DTMF either). It is being
trimmed to within a millisecond of its life. Note, that the Calling Party's
DTMF is OK.
====================================================================== 

---------------------------------------------------------------------- 
 (0096117) Seb7 (reporter) - 2008-12-10 12:19
 http://bugs.digium.com/view.php?id=13053#c96117 
---------------------------------------------------------------------- 
If the code hasn't been changed then I don't see why it should not still be
a problem! Or are their changes you think may have fixed this? jpeeler, did
you test with Asterisk 1.4.19? It would probably be quite a work-up for me
to retest this now and it would be difficult to convince my boss that I
should spend an afternoon reproducing the same results I posted in the
first place... 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-12-10 12:19 Seb7           Note Added: 0096117                          
======================================================================




More information about the asterisk-bugs mailing list