Summary:	ASTERISK-28968: res_pjsip: Crash when comparing header in outgoing SIP request
Reporter:	Jonas (boettner)	Labels:
Date Opened:	2020-06-29 05:10:23	Date Closed:	2020-07-09 04:55:02
Priority:	Minor	Regression?	No
Status:	Closed/Complete	Components:	Resources/res_pjsip
Versions:	17.5.1	Frequency of Occurrence	One Time
Related Issues:
Environment:	Debian 10.4 (buster) on Dell PowerEdge R330	Attachments:	( 0) core_asterisk_19870_11_113_1593077450-locks.txt ( 1) core_asterisk_19870_11_113_1593077450-thread1.txt
Description:	A few days after upgrading asterisk to version 17.5.1 one instance crashed. We'll send ast_coredumper output via E-Mail. If you need any further information please let us know.
Comments:	By: Asterisk Team (asteriskteam) 2020-06-29 05:10:24.580-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]. Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur. By: Joshua C. Colp (jcolp) 2020-06-29 05:14:27.385-0500 Please attach the information to the issue, sanitized to your needs. If a core dump itself is required then it will be requested. We try to reserve sending things directly for cases where it is absolutely not possible to sanitize. This is because it reduces the number of people who can participate to those who strictly work for Sangoma, while Asterisk is itself an open source project with many people who may want to investigate/work on issues. By: Jonas (boettner) 2020-06-29 07:58:30.958-0500 Hi, we attached the files without private user data. The other files are full of customer or network data and quite impossible to sanitize. We sent them via email. By: Joshua C. Colp (jcolp) 2020-06-29 08:08:24.312-0500 Is there an accompanying Asterisk log? What transports are in use on the system? Has this happened multiple times or just once? By: Jonas (boettner) 2020-06-29 08:58:39.388-0500 There weren't any remarkable log output. It suddenly stopped. This system is listening to UDP only. This is the first crash since we upgraded to 17.5.1 a couple of days before. By: Joshua C. Colp (jcolp) 2020-06-30 07:45:23.465-0500 Unfortunately with the provided information there's no clear cause. It appears as though there is memory corruption or premature destruction of a SIP message. The provided core dump in private unfortunately could not be opened as I was unable to reproduce an equivalent build, and the binaries were not provided. By: Jonas (boettner) 2020-07-09 04:46:37.577-0500 We suggest to close this ticket, as it seems to be an individual case. Since then, there wasn't any asterisk crash.