| Summary: | ASTERISK-29084: TLS registration crashing asterisk | ||
| Reporter: | pnkasodj (pinkoman) | Labels: | |
| Date Opened: | 2020-09-16 01:51:24 | Date Closed: | 2020-09-25 09:40:15 |
| Priority: | Minor | Regression? | |
| Status: | Closed/Complete | Components: | pjproject/pjsip |
| Versions: | 17.7.0 | Frequency of Occurrence | |
| Related Issues: | |||
| Environment: | Attachments: | ( 0) brief.txt | |
| Description: | Hello all,i have the latest freepbx distro with asterisk 17.7 installed, freepbx 15 , all up to date.
Lately with the 17 asterisk version i am having asterisk crashes ( core files generated in /tmp directory), when i try to register a pjsip client with tls (groundwire android). After 1-2 crashes it registers and everything works correctrly.Then again the same when i try to register the client again by opening the software. I attach a brief txt of the core dump in case someone can find the reason. Thank you. | ||
| Comments: | By: Asterisk Team (asteriskteam) 2020-09-16 01:51:25.835-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. Please note that log messages and other files should not be sent to the Sangoma Asterisk Team unless explicitly asked for. All files should be placed on this issue in a sanitized fashion as needed. 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. Please note that by submitting data, code, or documentation to Sangoma through JIRA, you accept the Terms of Use present at [https://www.asterisk.org/terms-of-use/|https://www.asterisk.org/terms-of-use/]. By: Benjamin Keith Ford (bford) 2020-09-16 09:56:28.975-0500 Looks like this may be getting into DPMA territory. Do you know which Asterisk version this crash started happening in? Also, can you provide a packet capture with this happening? Unfortunately there's not much to go off of in the backtrace since there's no line numbers or information on variables to see what might be causing it. By: Joshua C. Colp (jcolp) 2020-09-25 09:40:15.099-0500 DPMA 3.5.5 has been released which resolves this issue. You can download the version from the downloads server[1] or it will be automatically downloaded when using "make menuselect". [1] http://downloads.digium.com/pub/telephony/res_digium_phone/ | ||