 | 1 | initial version |
Hello Wireshark-Community,
I am currently analyzing packet loss in some huge PCAP files with thousands of RTP streams.
Question 1)
Is there a bug inside "RTP Streams" as it cannot sort the "Lost" column correctly (Both Screenshots from same file)?
Question 2)
Is is possible to only display missing (Lost) packets inside IO Graph, because it is close to impossible to detect missing packets with "rtp.seq"? If not, do you know (commerical) alternatives/workarounds?
Hello Wireshark-Community,
I am currently analyzing packet loss in some huge PCAP files with thousands of RTP streams.
streams.
Question 1)
Is there a bug inside "RTP Streams" as it cannot sort the "Lost" column correctly (Both Screenshots from same file)?
Question 2)
Is is possible to only display missing (Lost) packets inside IO Graph, because it is close to impossible to detect missing packets with "rtp.seq"? If not, do you know (commerical) alternatives/workarounds?
Hello Wireshark-Community, I am currently analyzing packet loss in some huge PCAP files with thousands of RTP streams.
Question 1)
Is there a bug inside "RTP Streams" as it cannot sort the "Lost" column correctly (Both Screenshots from same file)?
Question 2)
Is is possible to only display missing (Lost) packets inside IO Graph, because it is close to impossible to detect missing packets with "rtp.seq"? If not, do you know (commerical) alternatives/workarounds?
Question 3) Inside the IO Graph above you see that the RTP Seq field only has 16 Bit and restarts from 0 after 65535 packets. Is this the reason why multiple streams from same SSRC# show up inside "RTP Streams" Analysis in Wireshark? I think for every Seq-Number restart from 0 an individual stream is shown there. Can you confirm?
Thank you very much for helping!
Copyright Wireshark Foundation, 2017-2023 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
