[asterisk-bugs] [Asterisk 0018132]: SIp channel stop work

Asterisk Bug Tracker noreply at bugs.digium.com
Wed Oct 13 10:32:31 CDT 2010


A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=18132 
====================================================================== 
Reported By:                mpiazzatnetbug
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   18132
Category:                   General
Reproducibility:            random
Severity:                   minor
Priority:                   normal
Status:                     new
Asterisk Version:           Older 1.4 - please test a newer version 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-10-13 07:29 CDT
Last Modified:              2010-10-13 10:32 CDT
====================================================================== 
Summary:                    SIp channel stop work
Description: 
Asterisk 1.4.26.3 


It's a production enviroment.
We start asterisk in safe mode. 
Every minutes with sipsak we check if sip the channel replys to a keep
alive sip message. If doesn't replay we kill the process with -6 option and
the asterisk re-starts himself.

Attached yuo find the gdp output of the core file produced by the
operation.
I'm not able to understand if the gdp outout is helpful or not. The
problem is happened after 4 weeks of uptime. We have 1020 peer registered
on the asterisk and an average of 30 channels up during office time.

I have some doubts for example about the lines as:
orig_channame =
"SIP/openser_comtn-b0bd5470\000?\000\000\000\000\020?DA\000\000\000\000%4D\000\000\000\000\000`\002\221??*\000\000\b?B\000\000\000\000\000`\002\221??*\000\000?>N\000\000\000\000"
 
====================================================================== 

---------------------------------------------------------------------- 
 (0127951) mpiazzatnetbug (reporter) - 2010-10-13 10:32
 https://issues.asterisk.org/view.php?id=18132#c127951 
---------------------------------------------------------------------- 
the issue is that if I have a production machine with 1000 phones, and some
of them are critical, and the sip stak stops to work my first priority is
not debug the issue but restart the service. I'm using the kill command
becuase it's produce a core file. If I use a command like stop now I will
not have a core dump file and any info at all about.
The only possible choice that I see it's automatize the gdb debug in some
way before to kill the process. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-10-13 10:32 mpiazzatnetbug Note Added: 0127951                          
======================================================================




More information about the asterisk-bugs mailing list