Wireshark-bugs: [Wireshark-bugs] [Bug 11420] Wire Shark Not Capturing register, invite , 200 ok
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Tue, 11 Aug 2015 12:51:56 +0000

changed bug 11420


What Removed Added
CC   alexis.lagoutte@gmail.com

Comment # 4 on bug 11420 from 
(In reply to Hadriel Kaplan from comment #3)
> (In reply to Hadriel Kaplan from comment #2)
> > 
> > 2) The second problem is your SIP over Websocket server: it's setting the
> > response frames to have a websocket opcode for "binary" instead of "Text",
> > which is just wrong. Your client correctly sets the opcode to "text", but
> > the response from the server are not.  So wireshark won't decode those
> > "binary" SIP messages from the server to the client as SIP even in 1.99.8;
> > but it will decode the messages from the client to the server.
> 
> Hmmm, I take it back, it's legal to use "binary" opcode for SIP in websocket
> per RFC 7118. Unfortunately Wireshark won't decode that as SIP even in
> 1.99.x. (really wireshark should base dissector decisions on the
> "Sec-WebSocket-Protocol" HTTP header field, not some preference setting for
> text only)

I think, yes it is good idea ! (When add web socket dissector there is no
applications using Sec-WebSocket-Protocol)

You are receiving this mail because:
  • You are watching all bug changes.