[asterisk-dev] DTMF end accepted without begin

[Dmitry Andrianov]

As far as I understand, Asterisk DSP code does not generate DTMF_BEGIN frames (at least unless DSP_DIGITMODE_MUTECONF+DSP_DIGITMODE_MUTEMAX flags are passed to DSP - I do not completely understand that branch of code). This means it is not problem with your configuration, it is the way how DSP code works now.

I believe this can be easily fixed if anyone needs these BEGIN frames.

From: asterisk-dev-bounces at lists.digium.com [mailto:asterisk-dev-bounces at lists.digium.com] On Behalf Of John Aughey
Sent: Sunday, December 02, 2007 3:20 PM
To: asterisk-dev at lists.digium.com
Subject: [asterisk-dev] DTMF end accepted without begin

I was having problems with consistent DTMF detection on a FXO Zap device, so I turned on DTMF logging.  I noticed that it always reports "DTMF end accepted without begin" for every digit pressed.  I've verified this on 1.4.15 and the latest svn release.  It indicates a duration of 0ms which is consistent with not receiving a begin event.  The tones get "detected", but it can't do any filtering based on duration this way.

This seems to be a core problem that the Zap layer isn't passing on DTMF_BEGIN events.  Is this a known issue or is anyone working on this problem?  Or could I have something messed up in my own configuration?

Thanks

John Aughey
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-dev/attachments/20071203/bc9da581/attachment.htm