<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>I shod also add that the Kamailio WebSocket implementation does not support any extensions. So unless the deflate frame extension is implicit for TLS it will not be negotiated. Further, the implementation does not set any compressed bits and all unused flags etc should be zeroed automatically - but I will look at the code later.</div><div><br></div><div>Peter<br><br>On 24 Jan 2013, at 09:05, Peter Dunkley <<a href="mailto:peter.dunkley@crocodile-rcs.com">peter.dunkley@crocodile-rcs.com</a>> wrote:<br><br></div><blockquote type="cite"><div><meta http-equiv="content-type" content="text/html; charset=utf-8"><div>I am not sure how to investigate this. It sounds like it might be a TLS related problem (or a WebSocket/TLS interworking problem in Kamailio). I don't know anything about the Kamailio TLS implementation - I just drop WebSocket frames into it as required.</div><div><br></div><div>I did do (a little) WSS testing and saw no problems myself.</div><div><br></div><div>Regards,</div><div><br></div><div>Peter<br><br>On 23 Jan 2013, at 22:12, Pete Kelly <<a href="mailto:pkelly@gmail.com">pkelly@gmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div><div dir="ltr"><p style="font-family:arial,sans-serif;font-size:13px">Hi, I am having an issue at the moment with SIP NOTIFY messages being sent from Kamailio (latest git master) over wss transport</p><p style="font-family:arial,sans-serif;font-size:13px">
I am getting reports from the receiving end saying "Compressed bit must be 0 if no negotiated deflate-frame extension"</p><p style="font-family:arial,sans-serif;font-size:13px">The only reference I can find to it is at the following URL... where the problem was caused by the server miscalculating the size of the msg: <a href="http://stackoverflow.com/questions/12308728/compressed-bit-must-be-0-when-sending-a-message-to-websocket-client" target="_blank">http://stackoverflow.com/questions/12308728/compressed-bit-must-be-0-when-sending-a-message-to-websocket-client</a></p>
<p style="font-family:arial,sans-serif;font-size:13px">Does anyone have any suggestions as to how I could debug this within Kamailio? It sounds like Kamailio may be sending some incorrect packet information but I am unsure at this point.</p>
<p style="font-family:arial,sans-serif;font-size:13px"><br></p><p style="font-family:arial,sans-serif;font-size:13px"><br></p></div>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list</span><br><span><a href="mailto:sr-users@lists.sip-router.org">sr-users@lists.sip-router.org</a></span><br><span><a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a></span><br></div></blockquote></div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list</span><br><span><a href="mailto:sr-users@lists.sip-router.org">sr-users@lists.sip-router.org</a></span><br><span><a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a></span><br></div></blockquote></body></html>