https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16710
Bug ID: 16710
Summary: Rendered ntp timestamp from RTCP SR seem incorrect
Product: Wireshark
Version: 3.2.4
Hardware: x86
OS: macOS 10.15
Status: UNCONFIRMED
Severity: Major
Priority: Low
Component: Dissection engine (libwireshark)
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
Created attachment 17889
--> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=17889&action=edit
raw pcap and dissection results from wireshark
Build Information:
Version 3.2.4 (v3.2.4-0-g893b5a5e1e3e)
--
While debugging an audio issue and looking over RTCP SR packets, I noticed the
ntp timestamps to vary wildly, and to not match the corresponding ntp
timestamps output by the webrtc client. I tested across different webrtc
clients, and observed the same which leads me to think that the issue is in
Wireshark in how it parses the ntp timestamps.
For the attached samples, samples include pcap of SR and RR for RTCP and the
dissection of SR and RR for RTCP, you will notice the dissection displays ntp
timestamps where the year will swing from 2063 to 2032 to 1968 and 1979. This
did not match the ntp timestamps output by the client which were all based in
year 2020.
--
You are receiving this mail because:
You are watching all bug changes.___________________________________________________________________________
Sent via: Wireshark-bugs mailing list <[email protected]>
Archives: https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
mailto:[email protected]?subject=unsubscribe
