Summary:	ASTERISK-25840: Asterisk 13.7.0 unable to send INVITEs to jsSIP (WebRTC) peer connected over WSS
Reporter:	Kirill Marchuk (62mkv)	Labels:	webrtc
Date Opened:	2016-03-11 07:51:30.000-0600	Date Closed:	2016-03-12 10:09:45.000-0600
Priority:	Major	Regression?
Status:	Closed/Complete	Components:	Channels/chan_sip/WebSocket
Versions:	13.7.0	Frequency of Occurrence	Constant
Related Issues:	duplicates ASTERISK-24330 Requirement for 'wss' value in Contact header transport parameter on inbound traffic violates RFC7118
Environment:	Server: Debian wheezy; Client: jsSIP 0.7.17; Chrome/Firefox: latest	Attachments:
Description:	Long story is here: https://groups.google.com/d/msg/jssip/1r6L2R0i1vk/fBrU7HAHBgAJ Long story short: as we connect jsSIP client to Asterisk over WSS, we can call and register, but we don't receive calls. Over WS we receive calls even with jsSIP; with sipML5 we receive calls even with WSS. I've posted this on jsSIP discussion group and their core maintainer (Inaki Baz Castillo) explained me that this is an Asterisk issue (see his reply to my message at the link above) I can confirm that "tcpdump port 8089" does NOT display anything when I run "channel originate SIP/<peer> application Playback hello-world", although I can see this in CLI: Reliably Transmitting (NAT) to 188.133.x.z:51147: INVITE sip:2lansdgc@6o5gvecvk9qu.invalid;transport=ws SIP/2.0 (I was pretty shocked that such a message in CLI does not mean that packet was actually sent, so this is a bug per se, IMHO) afterwards it does some attempts of retransmitting this packet, none of these appear in "tcpdump port 8089" output Can you confirm this is a bug or should I provide any additional information ?
Comments:	By: Asterisk Team (asteriskteam) 2016-03-11 07:51:31.530-0600 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: Iñaki Baz Castillo (ibc) 2016-03-11 08:03:57.823-0600 AFAIK Asteirsk fails when the endpoints connects via WSS (secure WebSocket) but indicates ;transport=ws in the Contact of the REGISTER. First of all: ;transport=wss does NOT exist (check RFC 7118), neither ;transport=tls. So Asterisk should NEVER rely on those non standard URI parameter values. By: Kirill Marchuk (62mkv) 2016-03-11 09:28:26.161-0600 Probably duplicates: ASTERISK-24330