On way is if you go into Statistics/RTP and stream analysis, you can sort by status and you will see the frames with the wrong sequence numbers. If you select the frame, you can click Jump To, and it will go to that frame.
Wes
--- On Fri, 4/24/09, Priscilla Oppenheimer <po@xxxxxxxxxxxxx> wrote:
> From: Priscilla Oppenheimer <po@xxxxxxxxxxxxx>
> Subject: [Wireshark-users] RTP video sequence errors
> To: "Community support list for Wireshark" <wireshark-users@xxxxxxxxxxxxx>
> Date: Friday, April 24, 2009, 12:10 PM
> Hi Wireshark folks,
>
> We're looking at some captured data for a new HD video
> application and
> have some questions.
>
> What does it mean when we see in the RTP Stream Analysis
> window
> Sequence Errors = 26. There's also Lost RTP Packets = 2%.
>
> Is the sequence error referring to the RTP sequence number?
> Is there a
> good way to find where in the trace file the problem
> occurred?
>
> The errors are in just one direction so we filtered on
> traffic for
> that direction and for the relevant SSRC. Now I'm scrolling
> down in
> the packet list pane to find any case where there's a
> missing sequence
> number or something of that sort, but haven't seen anything
> yet. Is
> there a better way?
>
> Does 2% packet loss seem worrisome? Is 26 sequence errors
> worrisome?
> The engineer captured just 3 MB for about 26 seconds to
> keep the file
> small, but hopefully it's a big enough sample to do some
> preliminary
> analysis.
>
> There aren't any user complains, but there aren't any users
> yet. The
> application hasn't gone into production yet; we're just
> gathering
> baseline data at this point.
>
> Thanks for your help!
> _________________
> Priscilla Oppenheimer
> http://www.priscilla.com
> Chase the dream, not the competition.
>
>
>
>
> ___________________________________________________________________________
> Sent via: Wireshark-users mailing list <wireshark-users@xxxxxxxxxxxxx>
> Archives: http://www.wireshark.org/lists/wireshark-users
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
>
> mailto:wireshark-users-request@xxxxxxxxxxxxx?subject=unsubscribe
>