Hey Joshua,
Pilot is actually where I started but I don't see where it does
anything with RTP (just treats it as UDP) - am I missing something?
My goal is to take static .cap trace files (lots of them - and big!)
that have already been captured and analyze them for missing or
undordered RTP sequence numbers (etc). And then ideally provide one
report or graph or chart to my client that says "during n number of
hours of capture, you had x lost datagrams and y unordered
datagrams." Or, failing that, one report per trace file. I can do
this with Wireshark but it's very time consuming and the RTP analysis
popup window doesn't have a print or print to PDF function. It has a
graphing capability but that's limited to jitter - I need to export
sequence number analysis data.
Thanks much,
Scott
On Apr 20, 2011, at 9:40 , joshua atterbury wrote:
> Hi Scott,
>
> Try the 10 day eval version of Cace Pilot, http://www.cacetech.com/products/cascade_pilot_personal_edition.html
> I have used it for reports, just not RTP traffic.
>
> On Thu, Apr 21, 2011 at 4:00 AM, Scott M Vermillion <scott_at_it-
> ag.com> wrote:
> All:
>
> I have recently captured quite a large volume of RTP traffic using
> Wireshark and am searching for a way to generate some decent
> reporting against the trace files. Wireshark itself allows for some
> analysis via:
>
> Telephony->RTP->Stream Analysis
>
> However, other than saving the raw line-by-line statistics to a .csv
> file, there doesn't appear to be any rich reporting capability. In
> the analysis window, I see summary information as follows:
>
> Max delta = 16.75 ms at packet no. 328593
> Max jitter = 0.66 ms. Mean jitter = 0.12 ms.
> Max skew = -6.45 ms.
> Total RTP packets = 404234 (expected 404234) Lost RTP packets =
> 0 (0.00%) Sequence errors = 0
> Duration 600.00 s (-5 ms clock drift, corresponding to 89999 Hz
> (-0.00%)
>
> None of this is exported to the .csv file. My goal is to provide a
> client with a succinct report of these captured RTP streams (MPEG-
> II). In particular "Lost RTP packets" and "Sequence errors" are of
> interest. I evaluated Cascade Pilot from Cace Tech but they seem
> slanted towards TCP in their reporting capabilities. Anybody know
> of a trick in Wireshark or some other product that I can leverage
> for this purpose (short of doing a bunch of screen capture)?
>
> Thanks much,
>
> Scott
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:http://www.groupstudy.com/list/CCIELab.html
Blogs and organic groups at http://www.ccie.net
Received on Thu Apr 21 2011 - 10:32:24 ART
This archive was generated by hypermail 2.2.0 : Sun May 01 2011 - 09:00:29 ART