search

fpm123 / sipml5

Automatically exported from code.google.com/p/sipml5
0 stars 0 forks source link

“wss” is Not a Valid Transport #72

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?

N/A

What is the expected output? What do you see instead?

According to section 5.2.2 of draft-ietf-sipcore-sip-websocket 
(http://tools.ietf.org/html/draft-ietf-sipcore-sip-websocket-00#section-5.2.2) 
“ws” is the correct transport for WebSockets, whether or not you’re using 
WSS. sipML5 specifies a distinct tsip_transport_type_e.WSS which produces an 
invalid “;transport=wss” in the Contact SIP header.

This has caused us errors when using sipML5 to talk to the Kamailio SIP server 
(outlined here: 
http://lists.sip-router.org/pipermail/sr-users/2013-January/076436.html )

What version of the product are you using? On what operating system?

sipML5 v1.2.165
Chrome v26.0.1386.0 dev
Mac OS X 10.8.2 (Mountain Lion)
Kamailio 4.0.0-pre

Original issue reported on code.google.com by d...@davecardwell.co.uk on 24 Jan 2013 at 4:23

GoogleCodeExporter commented 8 years ago 
Attached is a patch that resolves this issue by adding an extra s_transport 
property to tsip_transport objects to be used instead of .s_protocol where 
appropriate.

Original comment by d...@davecardwell.co.uk on 26 Jan 2013 at 1:35

Attachments:

GoogleCodeExporter commented 8 years ago 
please apply this patch to solve kamailio issue when receiving call with wss
thank you

Original comment by luis.az...@factorlusitano.com on 27 Aug 2013 at 11:52

GoogleCodeExporter commented 8 years ago 
Is this patch still necessary? I am receiving the same error. How do I apply 
this patch. It appears that it is just a diff file.

Original comment by carl.j.p...@gmail.com on 21 Jul 2014 at 9:39

GoogleCodeExporter commented 8 years ago 
Nevermind. I figured it out. Yes, this patch is still necessary to use wss with 
Kamailio. I needed to download the sipml5 source, edit the files in this diff, 
and then compress them into the sipml-api.js with the release.sh file and 
replace the previous sipml-api.js file.

Original comment by carl.j.p...@gmail.com on 22 Jul 2014 at 2:35

GoogleCodeExporter commented 8 years ago 
Carl, is this still an issue in Kamilio <=> SIPml5 latest versions? (4.1.5 ; 
1.4.217)

Original comment by kobie.re...@gmail.com on 14 Sep 2014 at 9:27