Summary:	ASTERISK-29039: chan_mobile: Crash on dial/answer
Reporter:	Marcin Wieczorek (MarcinWieczorek)	Labels:
Date Opened:	2020-08-21 13:12:44	Date Closed:	2020-09-12 12:00:02
Priority:	Minor	Regression?
Status:	Closed/Complete	Components:	Addons/chan_mobile Channels/chan_pjsip
Versions:	17.6.0 17.7.0	Frequency of Occurrence	Constant
Related Issues:
Environment:	ArchLinux 5.7.12	Attachments:	( 0) console_log.txt ( 1) core-asterisk-1598032707.380612-brief.txt ( 2) core-asterisk-1598032707.380612-full.txt ( 3) core-asterisk-1598032707.380612-info.txt ( 4) core-asterisk-1598032707.380612-locks.txt ( 5) core-asterisk-1598032707.380612-thread1.txt
Description:	I was trying to set up asterisk with chan_mobile with my phone (Huawei Mate 10 lite) as a gateway via bluetooth. That part works and the phone starts calling correct number, but in the meantime asterisk crashes right after log line: Executing [censored_number@from-internal:1] Dial("PJSIP/6001-00000000", "Mobile/MATE10LITE/censored_number,45") in new stack. Same thing happens when I call that gateway phone, but the call gets answered before the crash. The phone number is real and it is replaced in the core dump with "CENSORED_NUMBER"
Comments:	By: Asterisk Team (asteriskteam) 2020-08-21 13:12:44.963-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. By: Joshua C. Colp (jcolp) 2020-08-24 04:49:34.373-0500 Can you confirm that chan_mobile was built for this version of Asterisk? The backtrace makes it seems as though chan_mobile is for a different version of Asterisk, causing a mismatch resulting in the wrong thing getting called. By: Joshua C. Colp (jcolp) 2020-08-24 04:53:29.266-0500 Specifically - it seems like this chan_mobile was built for Asterisk 13. By: Marcin Wieczorek (MarcinWieczorek) 2020-08-28 12:00:45.059-0500 Very unlikely that it's 13 (from what I think, not what the backtraces say), because my first attempt was to compile only the chan_mobile.so and put it in the system. I'm quite sure I used the same version and build settings so I was quite sure no big mistakes were made. Now I can see, that my later compilations didn't include chan_mobile.so (therefore if my other build seeks chan_mobile in the system then that wrong version would be used and my build was latest rc). In fact enabling it doesn't seem to be working. I'm using the nmenuselect because menuselect says I don't have ncurses. $ ./menuselect/nmenuselect --enable chan_mobile $ ./menuselect/nmenuselect --list-options G mob - chan_mobile                    MENUSELECT_ADDONS I'll provide more feedback when I manage to compile it correctly. By: Asterisk Team (asteriskteam) 2020-09-12 12:00:01.812-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