Summary:	ASTERISK-28010: PJSIP: Crash with MWI implicit subscription replaced by explicit
Reporter:	David Watson (dwatson)	Labels:	pjsip
Date Opened:	2018-08-13 19:56:28	Date Closed:
Priority:	Major	Regression?
Status:	Open/New	Components:	Channels/chan_pjsip Resources/res_pjsip_mwi
Versions:	13.22.0	Frequency of Occurrence	One Time
Related Issues:
Environment:	Sangoma SNG7, FreePBX14, asterisk 13.22.0	Attachments:	( 0) core.pbxchc.jadeworld.com-2018-08-13T08-41-35+1200-brief.txt ( 1) core.pbxchc.jadeworld.com-2018-08-13T08-41-35+1200-full.txt ( 2) core.pbxchc.jadeworld.com-2018-08-13T08-41-35+1200-locks.txt ( 3) core.pbxchc.jadeworld.com-2018-08-13T08-41-35+1200-thread1.txt ( 4) freepbx.log ( 5) full-20180814
Description:	It looks like there's an issue with MWI subscriptions and the topic somehow ends up NULL. This could be due to implicit subscriptions changing to explicit. There could be a race condition when things are being set up and the call is hung up almost immediately. {noformat} [2018-08-13 08:41:31] ERROR[96783] astobj2.c: FRACK!, Failed assertion user_data is NULL (0) [2018-08-13 08:41:31] VERBOSE[96783] logger.c: Got 27 backtrace records [2018-08-13 08:41:31] VERBOSE[96783] logger.c: #0: [0x5fcc55] asterisk __ast_assert_failed() (0x5fcbd1+84) [2018-08-13 08:41:31] VERBOSE[96783] logger.c: #1: [0x45ccf4] asterisk <unknown>() [2018-08-13 08:41:31] VERBOSE[96783] logger.c: #2: [0x45cdbc] asterisk __ao2_lock() (0x45cd91+2B) [2018-08-13 08:41:31] VERBOSE[96783] logger.c: #3: [0x5c80af] asterisk <unknown>() [2018-08-13 08:41:31] VERBOSE[96783] logger.c: #4: [0x5c7afd] asterisk stasis_unsubscribe() (0x5c7a9d+60) [2018-08-13 08:41:31] VERBOSE[96783] logger.c: #5: [0x5c7d25] asterisk stasis_unsubscribe_and_join() (0x5c7cee+37) [2018-08-13 08:41:31] VERBOSE[96783] logger.c: #6: [0x7f7251109e8d] res_pjsip_mwi.so <unknown>() [2018-08-13 08:41:31] VERBOSE[96783] logger.c: #7: [0x7f7251109f9a] res_pjsip_mwi.so <unknown>() [2018-08-13 08:41:31] VERBOSE[96783] logger.c: #8: [0x7f725110a0ca] res_pjsip_mwi.so <unknown>() [2018-08-13 08:41:31] VERBOSE[96783] logger.c: #9: [0x7f725110a28d] res_pjsip_mwi.so <unknown>() [2018-08-13 08:41:31] VERBOSE[96783] logger.c: #10: [0x7f72b080ad68] res_pjsip_pubsub.so <unknown>() [2018-08-13 08:41:31] VERBOSE[96783] logger.c: #11: [0x7f72b080cf57] res_pjsip_pubsub.so <unknown>() [2018-08-13 08:41:31] VERBOSE[96783] logger.c: #12: [0x7f72b080dee0] res_pjsip_pubsub.so <unknown>() [2018-08-13 08:41:31] VERBOSE[96783] logger.c: #13: [0x7f7300edc4e5] libasteriskpj.so.2 pjsip_endpt_process_rx_data() (0x7f7300edc339+1AC) [2018-08-13 08:41:31] VERBOSE[96783] logger.c: #14: [0x7f72733943b1] res_pjsip.so <unknown>() [2018-08-13 08:41:31] VERBOSE[96783] logger.c: #15: [0x5e4965] asterisk ast_taskprocessor_execute() (0x5e4858+10D) [2018-08-13 08:41:31] VERBOSE[96783] logger.c: #16: [0x5ee123] asterisk <unknown>() [2018-08-13 08:41:31] VERBOSE[96783] logger.c: #17: [0x5e4965] asterisk ast_taskprocessor_execute() (0x5e4858+10D) [2018-08-13 08:41:31] VERBOSE[96783] logger.c: #18: [0x5ec3fa] asterisk <unknown>() [2018-08-13 08:41:31] VERBOSE[96783] logger.c: #19: [0x5eda99] asterisk <unknown>() [2018-08-13 08:41:31] VERBOSE[96783] logger.c: #20: [0x5ed852] asterisk <unknown>() [2018-08-13 08:41:31] VERBOSE[96783] logger.c: #21: [0x5f9c08] asterisk <unknown>() {noformat}
Comments:	By: Asterisk Team (asteriskteam) 2018-08-13 19:56:29.491-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: Benjamin Keith Ford (bford) 2018-08-14 09:57:13.268-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 We will also need the actual backtrace to help understand what's going on. More information on how to do that can be found here https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace By: David Watson (dwatson) 2018-08-14 17:44:37.306-0500 Extracted crash debug logs plus sections of freepbx and asterisk/full logs By: David Watson (dwatson) 2018-08-14 17:49:23.198-0500 System has more than 150 pjsip TLS/SRTP polycom handsets I am not aware of any action causing this although there is a pattern in common with previous asterisk13 software builds. This crash appears to occurs only when a PJSIP call is hungup. By: Benjamin Keith Ford (bford) 2018-08-15 11:03:32.375-0500 [~dwatson], I've gone ahead and opened up this issue. It seems like there's something going on with subscriptions. If you can turn up any more information on this issue, or happen to pinpoint a scenario where this occurs, please post it here!