Detect SIP Errors with Wireshark

[@gamophyte]

omg you saved the day, I kept using == and not understanding why I can't do greater than.

[@assadmoney]

Hi Laura, Could you please post a video by dissecting the SDP/SIP protocol going through the contents of its message body etc. This is to gain a deeper understanding on the contents of the packets.

[@LauraChappellLab]

Got it and placed it on the "Development List" here at our office.

[@gamophyte]

Laura, -how might you do a range?- (Edit: Never mind, found it.) I'm used to ports ranges with two dots but not sure about reponses. I guess I can do *sip.Status-Code > 199 && sip.Status-Code < 300* for 2XX but know of one line?

[@gamophyte]

omg I thought I was deep into wireshark as it was but I literally just now found out you can right click the display filter to find a builder! I now have *any sip.Status-Code in {200..299}*

[@gamophyte]

Okay well now I must admit this was to colorize packets. I realized it would be more useful to color specific types of responses to match the request method. Like both OPTIONS and 200 OK (OPTIONS) light yellow. I realized it's not good to go blanket all 4xx red for instance because 401 is so regular it shouldn't be bleeding eye red. Okay now I'm on the right path, thanks!

[@LeonErrante]

Thanks a lot!! great video!!

[@sayyadmujaffar747]

Awesome