[asterisk-bugs] [Asterisk 0012592]: DTMF issues in 1.4.19 with missing digits

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12592 
====================================================================== 
Reported By:                dawebber
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   12592
Category:                   Channels/chan_zap
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     new
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:             05-06-2008 13:41 CDT
Last Modified:              05-12-2008 12:27 CDT
====================================================================== 
Summary:                    DTMF issues in 1.4.19 with missing digits
Description: 
Trying to figure out an issue with DTMF recognition with 1.4.19. This  
is somewhat similar to the issue described here:  
http://bugs.digium.com/view.php?id=11740, but it might be a different  
issue altogether.

I have 1.4.19 running with TE212P on a US PRI hooked up to Time Warner
Telecom. DTMF debugging enabled.

LibPRI 1.4.3
Zaptel 1.4.9
====================================================================== 

---------------------------------------------------------------------- 
 dimas - 05-12-08 12:27  
---------------------------------------------------------------------- 
I'm not familar with Cepstral/ However, again, to me it looks like DTMF_END
somtimes aren't just read from Zap channel. This can happen when Zap
channel is not read for a long time (200ms is long enough) and NOT
autoserviced at that time.

If it is an issue, then Cepstral should put channel to autoservice and
back before and after doing long operation (external lookups etc). Just
setting DTMF_END_ONLY flag won't cure the issue... 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
05-12-08 12:27  dimas          Note Added: 0086732                          
======================================================================