Summary:	ASTERISK-24334: Crash with chan_sip on SIP to SIP over WebSockets call (WebRTC, SIPML5)
Reporter:	Rusty Newton (rnewton)	Labels:
Date Opened:	2014-09-16 19:11:54	Date Closed:	2014-12-22 17:04:34.000-0600
Priority:	Critical	Regression?	Yes
Status:	Closed/Complete	Components:	Channels/chan_sip/General Channels/chan_sip/SRTP Channels/chan_sip/WebSocket
Versions:	SVN 12.5.0	Frequency of Occurrence	Constant
Related Issues:	is related to ASTERISK-24205 DTLS-SRTP fails on SIP over WebSockets call from SIPML5(chrome) to Asterisk is related to ASTERISK-24639 Crash with PJSIP on SIP to SIP over WebSockets call (WebRTC, SIPML5)
Environment:	SVN-branch-12-r423172, Chrome (37.0.2062.120), SIPML5 SVN 224 live demo.	Attachments:	( 0) backtrace.txt ( 1) full.txt ( 2) messages.txt ( 3) pcap_asterisk.pcap ( 4) pcap_chrome.pcap ( 5) sip.txt
Description:	Essentially the same configuration as ASTERISK-24205, but attempting to call from a local Digium phone configured as a SIP peer to the SIPML5 client in Chrome (which resides on another machine on local network). h2. The crash!: D Phone -> Box1(Asterisk) -> Box2(Chrome(SIPML5)) With this call path we see a crash after the answer button is clicked on the SIPML5 client interface. h2. Additional note: The opposite call path fails seemingly the same as seen in ASTERISK-24205. The path is contrasted with ASTERISK-24205 where the call is directly to an Asterisk application rather than another device registered to Asterisk. Box2(Chrome(SIPML5)) -> Box1(Asterisk) -> D Phone h2. The debug: Debug attached is for the crashing scenario only. pcap_asterisk, full, messages, backtrace.txt,sip.txt:  from the Asterisk box. pcap_chrome: pcap from the box where Chrome/SIPML5 was running. h2. The dialplan: {noformat} [default] ;for testing ASTERISK-24205 exten => 354,1,Dial(SIP/354) exten => 6001,1,Dial(SIP/6001) {noformat}
Comments:	By: Rusty Newton (rnewton) 2014-09-16 19:17:29.283-0500 Linking to ASTERISK-24205 as I used same configuration and see the failures in ASTERISK-24205 when calling along opposite paths. By: Matt Jordan (mjordan) 2014-09-17 10:50:45.969-0500 What version of OpenSSL are you using? The crash is in OpenSSL; looking at the backtrace, I don't see anything jumping out in {{res_rtp_asterisk}} that it is doing wrong. By: Rusty Newton (rnewton) 2014-09-18 15:11:21.381-0500 openssl       1.0.1-4ubuntu5.15 libssl1.0.0    1.0.1-4ubuntu5.17 By: Dafi Ni (dafi) 2014-09-22 07:33:14.002-0500 [~rnewton] You can try with 1.0.1f-1ubuntu2.5,  which has numerous DTLS related fixes https://launchpad.net/ubuntu/+source/openssl/1.0.1f-1ubuntu2.5 but You  are probably using 12.04 , 1.0.1f-1ubuntu2.5 is for 14.04 By: Rusty Newton (rnewton) 2014-12-22 17:04:34.746-0600 Going to close this out, because it is 12 (security fix only) and ASTERISK-24639 appears to be the same issue in 13.