Summary:	ASTERISK-25431: A11 SIGSEGV in check_cached_response (ast_rtcp_read -> pj_stun_session_on_rx_pkt)
Reporter:	Nicole McIntosh (atna99)	Labels:
Date Opened:	2015-09-28 15:42:05	Date Closed:	2017-12-18 05:30:08.000-0600
Priority:	Major	Regression?	No
Status:	Closed/Complete	Components:
Versions:	11.19.0	Frequency of Occurrence	Occasional
Related Issues:
Environment:	Ubuntu 14.04.2 LTS , asterisk version 11.19 updated to trunk, last commit: b4535b0	Attachments:	( 0) narvi_fullbt_sept28_c.txt ( 1) narvi_last10kdebug_c.txt
Description:	Happens about once a day across many servers. initial backtrace: {noformat} #0  0x00007f78b4b69ada in check_cached_response () from /usr/lib/asterisk/modules/res_rtp_asterisk.so #1  0x00007f78b4b6a04b in pj_stun_session_on_rx_pkt () from /usr/lib/asterisk/modules/res_rtp_asterisk.so #2  0x00007f78b4b63291 in pj_ice_sess_on_rx_pkt () from /usr/lib/asterisk/modules/res_rtp_asterisk.so #3  0x00007f78b4b4e4aa in __rtp_recvfrom (instance=0x7f77e1b333e8, buf=0x7f77e315ece8, size=8192, flags=0,    sa=0x7f789c404440, rtcp=0) at res_rtp_asterisk.c:2126 #4  0x00007f78b4b4e655 in rtp_recvfrom (instance=0x7f77e1b333e8, buf=0x7f77e315ece8, size=8192, flags=0,    sa=0x7f789c404440) at res_rtp_asterisk.c:2158 #5  0x00007f78b4b57e42 in ast_rtp_read (instance=0x7f77e1b333e8, rtcp=0) at res_rtp_asterisk.c:4178 #6  0x0000000000550f92 in ast_rtp_instance_read (instance=0x7f77e1b333e8, rtcp=0) at rtp_engine.c:314 #7  0x00007f78b425abf5 in sip_rtp_read (ast=0x7f77e21ff6c8, p=0x7f77e2a76d08, faxdetect=0x7f789c4047bc)    at chan_sip.c:8200 #8  0x00007f78b425b3a8 in sip_read (ast=0x7f77e21ff6c8) at chan_sip.c:8297 #9  0x000000000047ca8b in __ast_read (chan=0x7f77e21ff6c8, dropaudio=0) at channel.c:4054 #10 0x000000000047e7a5 in ast_read (chan=0x7f77e21ff6c8) at channel.c:4408 #11 0x0000000000489282 in ast_generic_bridge (c0=0x7f77e18def88, c1=0x7f77e21ff6c8, config=0x7f789c405570,    fo=0x7f789c404d10, rc=0x7f789c404d18) at channel.c:7638 #12 0x000000000048b868 in ast_channel_bridge (c0=0x7f77e18def88, c1=0x7f77e21ff6c8, config=0x7f789c405570,    fo=0x7f789c404d10, rc=0x7f789c404d18) at channel.c:8113 #13 0x00000000004d5f7a in ast_bridge_call (chan=0x7f77e18def88, peer=0x7f77e21ff6c8, config=0x7f789c405570)    at features.c:4489 #14 0x00007f78a246715d in try_calling (qe=0x7f789c4072f0, opts=..., opt_args=0x7f789c4071f0,    announceoverride=0x7f789c40716f "beep", url=0x7f789c40716e "", tries=0x7f789c4071c8, noption=0x7f789c4071cc,    agi=0x0, macro=0x0, gosub=0x0, ringing=0) at app_queue.c:5983 #15 0x00007f78a246ba62 in queue_exec (chan=0x7f77e18def88, data=0x7f789c408b30 "690-P0^82,Tti,,beep,10")    at app_queue.c:7225 #16 0x000000000052ab77 in pbx_exec (c=0x7f77e18def88, app=0x3443e70, data=0x7f789c408b30 "690-P0^82,Tti,,beep,10")    at pbx.c:1677 #17 0x000000000053565f in pbx_extension_helper (c=0x7f77e18def88, con=0x0, context=0x7f77e18dfdd8 "690_context",    exten=0x7f77e18dfe28 "000^82", priority=19, label=0x0, callerid=0x7f77e17af8f0 "330454XXXX", action=E_SPAWN,    found=0x7f789c40cc1c, combined_find_spawn=1) at pbx.c:4970 #18 0x0000000000538b41 in ast_spawn_extension (c=0x7f77e18def88, context=0x7f77e18dfdd8 "690_context",    exten=0x7f77e18dfe28 "000^82", priority=19, callerid=0x7f77e17af8f0 "330454XXXX", found=0x7f789c40cc1c,    combined_find_spawn=1) at pbx.c:6100 #19 0x000000000053a1e8 in __ast_pbx_run (c=0x7f77e18def88, args=0x0) at pbx.c:6575 #20 0x000000000053bb3c in pbx_thread (data=0x7f77e18def88) at pbx.c:6905 #21 0x000000000059a430 in dummy_start (data=0x7f77e1bda790) at utils.c:1223 #22 0x00007f5550000000 in start_thread (arg=0x7f789c40d700) at pthread_create.c:312 #23 0x00007f79027be47d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 {noformat}
Comments:	By: Asterisk Team (asteriskteam) 2015-09-28 15:42:06.477-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: Nicole McIntosh (atna99) 2015-09-28 15:43:32.751-0500 full backtrace and last 10,000 lines (before crash) debug log. By: Joshua C. Colp (jcolp) 2017-12-18 05:30:08.688-0600 This has been fixed upstream and since we now use the system PJSIP or bundled PJSIP it is no longer applicable to 13 and above.