Wireshark mailing list archives
Re: Issue with RTT values in Wireshark
From: Martin Mathieson <martin.r.mathieson () googlemail com>
Date: Sat, 7 Apr 2012 14:20:22 +0100
Hi Nitin, Is this the RTCP network roundtrip propagation delay? If it is, then the calculated time is between the point of capture and one of the endpoints. You must be capturing fairly close to one of the endpoints? If you look at the generated fields attached to the frame with the report, it has a detailed explanation of where the inputs came from and how the calculation was done (also see RFC 3550). When I first added this calculation, lots of RTCP stacks weren't filling the relevant fields in correctly, but your numbers sound very plausible. If you want to send a small capture I can explain how the calculation was done. I was interested to see recently that for Voice over LTE (VoLTE) implementers and being told not to fill the relevant fields in that would allow this calculation, but instead to fill them in with zeros.... Martin On Fri, Apr 6, 2012 at 6:09 AM, NITIN GOYAL <nitinkumgoyal () gmail com> wrote:
Hi All Can anybody help me out in the below query related to RTT calculation?? Thanks Nitin On Wed, Apr 4, 2012 at 1:16 PM, NITIN GOYAL <nitinkumgoyal () gmail com>wrote:Hi All I have an issue with the Wireshark for calcuating the RTT values. For few pcaps, I have a higher value of RTT on one side or direction but the lower value of RTT on other side. I have taken the trace in the middle of the connections and in one direction the RTT calculated by Wireshark is around 40 ms but on what other direction its 1.5 ms. But i think ideally both the sides should have the same values as its round trip time(like a loop). The trace is RTP over UDP over a VoIP tool. Now, when i use some other licensed tool based on libpacp used by Wireshark as well, the values for both the sides is almost same with the same pcap file. So, i am not sure if Wireshark is calculating the wrong RTT values or the interpreation is differnet by other tools as how to calcuate the RTT vlaues?? Any idea about this?? Regards Nitin___________________________________________________________________________ Sent via: Wireshark-users mailing list <wireshark-users () wireshark org> Archives: http://www.wireshark.org/lists/wireshark-users Unsubscribe: https://wireshark.org/mailman/options/wireshark-users mailto:wireshark-users-request () wireshark org ?subject=unsubscribe
___________________________________________________________________________ Sent via: Wireshark-users mailing list <wireshark-users () wireshark org> Archives: http://www.wireshark.org/lists/wireshark-users Unsubscribe: https://wireshark.org/mailman/options/wireshark-users mailto:wireshark-users-request () wireshark org?subject=unsubscribe
Current thread:
- Issue with RTT values in Wireshark NITIN GOYAL (Apr 04)
- Re: Issue with RTT values in Wireshark NITIN GOYAL (Apr 05)
- Re: Issue with RTT values in Wireshark Martin Visser (Apr 07)
- Re: Issue with RTT values in Wireshark Martin Mathieson (Apr 07)
- Message not available
- Re: Issue with RTT values in Wireshark NITIN GOYAL (Apr 08)
- Re: Issue with RTT values in Wireshark Martin Mathieson (Apr 08)
- Re: Issue with RTT values in Wireshark Martin Mathieson (Apr 08)
- Re: Issue with RTT values in Wireshark NITIN GOYAL (Apr 05)