Summary:	ASTERISK-26079: Regular Segfaults of Asterisk w/ARI
Reporter:	Tom Pawelek (tompaw)	Labels:
Date Opened:	2016-05-31 15:46:08	Date Closed:	2016-05-31 15:52:23
Priority:	Critical	Regression?
Status:	Closed/Complete	Components:
Versions:	13.7.0 13.7.1 13.7.2	Frequency of Occurrence	Frequent
Related Issues:	duplicates ASTERISK-25941 chan_pjsip: Crash on an immediate SIP final response
Environment:	Linux 4.2.0	Attachments:	( 0) backtrace.txt
Description:	I run a distributed call center dialer based on ARI. On average, asterisk would crash on a given server at least once every 5 business days. It doesn't seem to be related to call volume, but it only happens when there is ARI activity present. Upstart usually restarts Asterisk within seconds, but it remains a major inconvenience, especially as far as scaling up is concerned (can't put too many people on one server to limit the number of dropped calls every time it happens). NOTE: Since we are running a PXE-based diskless setup, it is not trivial to recompile asterisk with DONT_OPTIMIZE and push it to production. However, I am ready to do so if the attached backtrace proves to be useless due to optimization.
Comments:	By: Asterisk Team (asteriskteam) 2016-05-31 15:46:08.756-0500 Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report. Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process]. By: Tom Pawelek (tompaw) 2016-05-31 15:46:52.408-0500 Backtrace w/optimized values (see NOTE in Description)