[asterisk-bugs] [Asterisk 0012008]: Asterisk Frequent Crash

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12008 
====================================================================== 
Reported By:                destiny6628
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   12008
Category:                   Channels/chan_zap
Reproducibility:            always
Severity:                   crash
Priority:                   normal
Status:                     new
Asterisk Version:           1.4.18 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             02-16-2008 05:04 CST
Last Modified:              02-18-2008 08:47 CST
====================================================================== 
Summary:                    Asterisk Frequent Crash
Description: 
Hello , we have been facing asterisk frequent crashes on CENTOS 5.0 ,
Asterisk-1.4.18 , Zaptel-1.4.8 and Libpri-1.4.3 .

Over a period of time when zap channels goes above 85 to 90 then asterisk
starts getting crash frequently and starts giving core dump .

This is happening on Zap dialing and happening very frequently .

Is there any solution to same .

Everytime when asterisk has got crashed the status seems to be NO ANSWER
and wait for answer .


====================================================================== 

---------------------------------------------------------------------- 
 agupta - 02-18-08 08:47  
---------------------------------------------------------------------- 
opt_args = {0x0, 0x0, 0x0, 0x0, 0x0, 0x28 <Address 0x28 out of bounds>,
0x0, 0xb6396b00 "", 0x0}
This seems to be some issue with dial_exec_full .  We are also facing
slightly different issue but there also the same pointer and same function
dial_exec_full is creating a problem . 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
02-18-08 08:47  agupta         Note Added: 0082470                          
======================================================================