[asterisk-bugs] [Asterisk 0015116]: Millions of "We're Zap/4-2, not", than crash

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15116 
====================================================================== 
Reported By:                Andrey Sofronov
Assigned To:                tilghman
====================================================================== 
Project:                    Asterisk
Issue ID:                   15116
Category:                   Channels/chan_dahdi
Reproducibility:            sometimes
Severity:                   block
Priority:                   normal
Status:                     feedback
Target Version:             1.4.27
Asterisk Version:           SVN 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-05-15 04:12 CDT
Last Modified:              2009-09-10 07:18 CDT
====================================================================== 
Summary:                    Millions of "We're Zap/4-2, not", than crash
Description: 
I have an asterisk server with Digium TDM840 card. Sometimes I get millions
of messages per second like "We're Zap/4-2, not" or "We're Zap/4-2, not
(null)". Than asterisk crashes: asterisk[3634]: segfault at 92765b41 ip
b7dd644b sp b6d4fe14 error 4 in libc-2.3.3.so[b7d5a000+142000].

Asterisk - 1.4.24
Zaptel - 1.4.11
====================================================================== 

---------------------------------------------------------------------- 
 (0110465) lmadsen (administrator) - 2009-09-10 07:18
 https://issues.asterisk.org/view.php?id=15116#c110465 
---------------------------------------------------------------------- 
OK, can you reproduce this on a test machine, or afterhours at all? We need
valgrind output in order to resolve this issue. Thanks! 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-09-10 07:18 lmadsen        Note Added: 0110465                          
======================================================================