[prev in list] [next in list] [prev in thread] [next in thread] 

List:       wireshark-bugs
Subject:    [Wireshark-bugs] [Bug 5527] Adding arbitrary value to x-axis RTP
From:       bugzilla-daemon () wireshark ! org
Date:       2010-12-29 13:16:12
Message-ID: 20101229131612.CE6FF2317A () mail ! wireshark ! org
[Download RAW message or body]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5527

--- Comment #10 from Frank Bulk <frnkblk@iname.com> 2010-12-29 05:16:09 PST ---
Thanks.  

If I understand you correctly, the timestamp is based on the sampling time. 
Doesn't seem like a very wise approach if the sampling time is said to be one
thing but the actual output rate is another.  I can see a slight skewing
possibly happen.  And how does it accommodate for missing and re-ordered
packets?

It sounds to me that the ingest process may need to be changed so that as it
reads the payload from each RTP packet, capture time, packet number, RTP
timestamp, etc are also read in, so that they can be displayed with the output. 

Frank

-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
___________________________________________________________________________
Sent via:    Wireshark-bugs mailing list <wireshark-bugs@wireshark.org>
Archives:    http://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://wireshark.org/mailman/options/wireshark-bugs
             mailto:wireshark-bugs-request@wireshark.org?subject=unsubscribe
[prev in list] [next in list] [prev in thread] [next in thread]