Summary:	ASTERISK-25359: Leak when not Answering
Reporter:	cloos (cloos)	Labels:
Date Opened:	2015-08-31 11:43:03	Date Closed:	2017-02-21 16:36:28.000-0600
Priority:	Major	Regression?
Status:	Closed/Complete	Components:
Versions:	13.1.0	Frequency of Occurrence	Constant
Related Issues:
Environment:	Ubuntu; asterisk 1:13.1.0~dfsg-1ubuntu2	Attachments:
Description:	On an install which only generates a couple of CEL events, Waits for 5 min, and the hangs up, where the scammers sent to the box tend to hang up themselves after three minutes, asterisk eventually uses up all of the available ram. Regression status is unknown.
Comments:	By: Asterisk Team (asteriskteam) 2015-08-31 11:43:03.993-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: Rusty Newton (rnewton) 2015-09-04 18:24:46.413-0500 Thank you for taking the time to report this bug and helping to make Asterisk better. Unfortunately, we cannot work on this bug because your description did not include enough information. Please read over the Asterisk Issue Guidelines [1] which discusses the information necessary for your issue to be resolved and the format that information needs to be in. We would be grateful if you would then provide a more complete description of the problem. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected and the location of documentation that led you to that expectation. 3. The behavior you actually encountered. To demonstrate the issue in detail, please include Asterisk log files generated per the instructions on the wiki [2]. If applicable, please ensure that protocol-level trace debugging is enabled, e.g., 'sip set debug on' if the issue involves chan_sip, and configuration information such as dialplan and channel configuration. Thanks! [1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines [2] https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information By: Asterisk Team (asteriskteam) 2015-09-19 12:00:20.481-0500 Suspended due to lack of activity. This issue will be automatically re-opened if the reporter posts a comment. If you are not the reporter and would like this re-opened please create a new issue instead. If the new issue is related to this one a link will be created during the triage process. Further information on issue tracker usage can be found in the Asterisk Issue Guidlines [1]. [1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines By: cloos (cloos) 2017-02-21 16:35:40.669-0600 The machine I saw this on currently runs 13.6.0, and the crashes no longer occur. By: Asterisk Team (asteriskteam) 2017-02-21 16:35:40.885-0600 This issue has been reopened as a result of your commenting on it as the reporter. It will be triaged once again as applicable. By: cloos (cloos) 2017-02-21 16:36:28.656-0600 This got fixed at some point between 13.1 and 13.6.