[asterisk-bugs] [Asterisk 0011189]: chan_zap causing reset on E1 and eventually crashed asterisk

noreply at bugs.digium.com noreply at bugs.digium.com
Mon Feb 18 22:06:45 CST 2008


A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=11189 
====================================================================== 
Reported By:                freon1
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   11189
Category:                   Channels/chan_zap
Reproducibility:            always
Severity:                   crash
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.4.13  
SVN Branch (only for SVN checkouts, not tarball releases): N/A  
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             11-07-2007 21:03 CST
Last Modified:              02-18-2008 22:06 CST
====================================================================== 
Summary:                    chan_zap causing reset on E1 and eventually crashed
asterisk
Description: 
I have a TE410 and TC400B installed under Fedora 7 kernel 2.6.23.1-10. with
asterisk-1.4.13, zaptel-1.4.6, libpri-1.4.2.  I have two E1 installed on
the TE410 card my calls are all going from IP to PSTN.  When I have above
40-45 calls (if it is less than 40 I havent noticed any problems) after a
while I start getting error similar to:  
[Nov  6 17:32:18] ERROR[32610] chan_zap.c: !! Got reject for frame 30,
retransmitting frame 30 now, updating n_r!
the number of errors increase and all of a sudden one of the E1s resets
and all the calls drop on that E1. The problem repeats and at some point
the other E1 resets which E1 resets is pretty random.  Then after several
of these errors the asterisk core dumps.  I have tested the hardware with
the help of digium support and have eliminated the hardware as an issue.  I
also tested the E1s and they are clean.  I also to the best of my ability
eliminated the problem being caused by conflict of any unrelated modules. 
I have the full debug (crash at 18:29:37) also the core dump both are
tar.gz(ipped).. I am available to provide further testing with live calls
if we need to get more data or test with live calls if there is a patch.
Thanks 
====================================================================== 

---------------------------------------------------------------------- 
 freon1 - 02-18-08 22:06  
---------------------------------------------------------------------- 
Yes it still crashes.  I have identified what crashes and what doesn't to
the best I could:

asterisk-1.2.24 Doesn't crash
asterisk-1.2.26.2 Crashes but very infrequently

asterisk-1.4.xx all the way to the current release of 1.4.18 crashes
several times a day and never supports more than 40 channels. Also they
reset E1's many times a day so calls get dropped.

I am sending live traffic doing too much testing is somewhat impossible,
some of the debugging I had to do didn't let more than a couple of calls go
thru so it never got to a point where I could get 40 to 50 calls in order
to get to a point where it would crash.  So I started using 1.2.24.  I am
willing to have the system open to you so someone with expertise can look
and find out what is exactly happening.  The best time to do this is in the
mornings I have other routes that I can reroute my traffic and when needed
send traffic to the box and have you look at what is happening.  I am on
MSN messenger under mbintampa at hotmail.com and yahoo under newnetbldr please
feel free to message me if this works for you. Thanks. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
02-18-08 22:06  freon1         Note Added: 0082544                          
======================================================================




More information about the asterisk-bugs mailing list