[asterisk-bugs] [Asterisk 0014700]: CallerID lost some digit

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=14700 
====================================================================== 
Reported By:                BubbleBoy
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   14700
Category:                   Channels/chan_dahdi
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     new
Asterisk Version:           1.4.23-rc3 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-03-19 04:36 CDT
Last Modified:              2009-03-20 02:16 CDT
====================================================================== 
Summary:                    CallerID lost some digit
Description: 
I use asterisk from 1.2.x to 1.4.22.1 CallerID is work fine(at
Taiwan)(dahdi-linux-complete-2.1.0.4+2.1.0.2), but when I want upgrade to
1.4.23, I found my callerid always lost some digit(ex. 0123456789 become
01234789), I don't know how to fix this problem, I just know 1.4.23-rc2 is
OK, but after 1.4.23-rc3.....1.4.24 have same problem.
====================================================================== 

---------------------------------------------------------------------- 
 (0102007) BubbleBoy (reporter) - 2009-03-20 02:16
 http://bugs.digium.com/view.php?id=14700#c102007 
---------------------------------------------------------------------- 
I think problem begin this change:

2008-12-12 14:40 +0000 [r163448-163511]  Russell Bryant
<russell at digium.com>

* main/channel.c, main/autoservice.c, include/asterisk/channel.h:
  Resolve issues that could cause DTMF to be processed out of
  order. These changes come from team/russell/issue_12658 1) Change
  autoservice to put digits on the head of the channel's frame
  readq instead of the tail. If there were frames on the readq that
  autoservice had not yet read, the previous code would have
  resulted in out of order processing. This required a new API call
  to queue a frame to the head of the queue instead of the tail. 2)
  Change up the processing of DTMF in ast_read(). Some of the
  problems were the result of having two sources of pending DTMF
  frames. There was the dtmfq and the more generic readq. Both were
  used for pending DTMF in various scenarios. Simplifying things to
  only use the frame readq avoids some of the problems. 3) Fix a
  bug where a DTMF END frame could get passed through when it
  shouldn't have. If code set END_DTMF_ONLY in the middle of digit
  emulation, and a digit arrived before emulation was complete,
  digits would get processed out of order. (closes issue
http://bugs.digium.com/view.php?id=12658)
  Reported by: dimas Tested by: russell, file Review:
  http://reviewboard.digium.com/r/85/ 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-03-20 02:16 BubbleBoy      Note Added: 0102007                          
======================================================================