| Summary: | ASTERISK-26036: res_pjsip: Asterisk crashes when an extension tries to use PJSIP trunk | ||||
| Reporter: | Steve Akerman (stevenA) | Labels: | |||
| Date Opened: | 2016-05-18 10:46:47 | Date Closed: | 2020-01-14 11:13:50.000-0600 | ||
| Priority: | Major | Regression? | |||
| Status: | Closed/Complete | Components: | pjproject/pjsip | ||
| Versions: | 13.9.1 | Frequency of Occurrence | Constant | ||
| Related Issues: |
| ||||
| Environment: | Raspbx on Raspberry Pi 3 / Jessie | Attachments: | ( 0) backtrace.txt ( 1) Debug_Output.txt | ||
| Description: | After Asterisk has registered, dial out from an extension that uses this PJSIP trunk results in a crash (gdb says program aborted?)
Asterisk is unable to qualify the server - this may or may not be relevant. Prior to registration of this PJSIP Trunk, Asterisk has been stable (no crashes) Very limited information in backtrace (asterisk was recompiled as per wiki instructions) | ||||
| Comments: | By: Asterisk Team (asteriskteam) 2016-05-18 10:46:47.792-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: Joshua C. Colp (jcolp) 2016-05-18 10:53:37.724-0500 As you mentioned the backtrace is useless, there's nothing to help in there. Did you recompile Asterisk and then try to use an old core dump? If so you'd get the results seen. The core dump has to be from a newly recompiled Asterisk itself. By: Steve Akerman (stevenA) 2016-05-18 11:01:58.843-0500 This was from a newly compiled Asterisk as per instructions on WIKI - before the dump, I ensure that the directory was empty. By: Joshua C. Colp (jcolp) 2016-05-18 12:36:03.513-0500 So this crashed while running the newly built Asterisk with debugging and dont optimize enabled? It may be platform specific... By: Steve Akerman (stevenA) 2016-05-18 12:53:11.431-0500 The build was made via make menu, and both DONT_OPTIMIZE and BETTER_BACKTRACES were selected (prior build did not have these options so no core dumps). I tried 3 times to get better results, but each time was the same. Each time, ps showed the -g option was enabled. What is the best Asterisk start command to use (I have seen versions run via gdb which yielded nothing, and the start-safe script)? The core file is significant BTW By: Joshua C. Colp (jcolp) 2016-05-20 12:13:49.424-0500 This is actually an abort and not a segmentation fault... If you build Asterisk without BUILD_NATIVE selected in "make menuselect" -> "Compiler Flags - Development" does the situation change? By: Asterisk Team (asteriskteam) 2016-06-04 12:00:01.319-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: Maxim Vasilev (helipopolis) 2017-06-07 04:21:03.101-0500 Same error while using pjsip trunk while from_user field contains "@". Asterisk certified/13.13-cert3 By: Maxim Vasilev (helipopolis) 2017-06-07 04:22:08.288-0500 I'm use PJSIP realtime configuration. from_user field in ps_endpoints table By: Joshua C. Colp (jcolp) 2017-06-07 04:28:51.013-0500 [~helipopolis] Please open a new issue with the needed information. | ||||