Wireshark-bugs: [Wireshark-bugs] [Bug 10665] RTP stream analysis reports high packet loss, when
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Sat, 11 Jul 2015 15:18:39 +0000

changed bug 10665


What Removed Added
CC   hadrielk@yahoo.com

Comment # 3 on bug 10665 from 
(In reply to Jeff Morriss from comment #2)
> Note how the sequence number jumps back to 20989, seemingly in the middle of
> the call.  The peers don't seem to mind this but it confuses Wireshark's
> packet loss calculation into saying the call had *negative* 94% packet loss.
> 
> I don't know about RTP to know what should be done here.

Technically this is permissible for RTP.  It's described in the algorithm given
in the appendix of RFC 3550.

It can happen due to a DSP/encoder restart, for example. (in practice it can
also happen with some middle-boxes hiding media switching, if they're not well
implemented)

Whether the RTP analyzer should handle it is a harder question, because I think
it would be hard to fix - and likely introduce more bugs - so it might not be
worth it just to cover an infrequent corner-case.

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