[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
Thu Jan 22 14:14:22 CST 2009
The following issue has been UPDATED.
======================================================================
http://bugs.digium.com/view.php?id=13053
======================================================================
Reported By: Seb7
Assigned To: jpeeler
======================================================================
Project: Asterisk
Issue ID: 13053
Category: Channels/chan_dahdi
Reproducibility: always
Severity: minor
Priority: normal
Status: closed
Asterisk Version: 1.4.19
Regression: No
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
Resolution: unable to reproduce
Fixed in Version:
======================================================================
Date Submitted: 2008-07-10 09:50 CDT
Last Modified: 2009-01-22 14:14 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.
======================================================================
----------------------------------------------------------------------
(0098479) jpeeler (administrator) - 2009-01-22 14:14
http://bugs.digium.com/view.php?id=13053#c98479
----------------------------------------------------------------------
I'm closing this issue since I have no further data to work with. If
anybody can reproduce the DTMF detection problem, please reopen. Make sure
to include the DTMF logs as well as recordings so that they can be analyzed
using some DTMF detection tests.
Issue History
Date Modified Username Field Change
======================================================================
2009-01-22 14:14 jpeeler Note Added: 0098479
2009-01-22 14:14 jpeeler Status assigned => closed
2009-01-22 14:14 jpeeler Resolution open => unable to
reproduce
======================================================================
More information about the asterisk-bugs
mailing list