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.

I did do (a little) WSS testing and saw no problems myself.

Regards,

Peter

On 23 Jan 2013, at 22:12, Pete Kelly <pkelly@gmail.com> wrote:

Hi, I am having an issue at the moment with SIP NOTIFY messages being sent from Kamailio (latest git master) over wss transport
I am getting reports from the receiving end saying "Compressed bit must be 0 if no negotiated deflate-frame extension"
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: http://stackoverflow.com/questions/12308728/compressed-bit-must-be-0-when-sending-a-message-to-websocket-client

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.

_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users