Send cisco-voip mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://puck.nether.net/mailman/listinfo/cisco-voip
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of cisco-voip digest..."
Today's Topics:
1. Re: Tools to analyze call-quality issues after-the-fact?
(Nick Matthews)
----------------------------------------------------------------------
Message: 1
Date: Sun, 8 Sep 2013 15:08:14 -0400
From: Nick Matthews <[email protected]>
To: Robert Kulagowski <[email protected]>
Cc: Cisco VOIP <[email protected]>
Subject: Re: [cisco-voip] Tools to analyze call-quality issues
after-the-fact?
Message-ID:
<cam-k-nq2w+aforufgq37fnobgljvogq8rj39z1pfs3ngge5...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
To keep wireshark from crashing you can try a few things:
-Use some of the command line tools available to prune just the voice
conversation you care about using ports/IP addresses. Example: "tshark -R
ip.addr==1.1.1.1 -r test.pcap -w testout.pcap" more info here:
http://www.wireshark.org/docs/wsug_html_chunked/AppToolstshark.html
-Load/use a windows/linux server instance with lots of memory. I had some
servers I had wireshark on that I could use in a pinch if I was too
lazy/unable to filter the capture via CLI.
These tools (never used) may be of use:
http://www.dallachiesa.com/code/rtpbreak/doc/rtpbreak_en.html
http://www.cs.columbia.edu/irt/software/rtptools/
I'm sure there are some commercial products with similar outputs, I'm just
not familiar with them.
-nick
On Fri, Sep 6, 2013 at 4:30 PM, Robert Kulagowski <[email protected]>wrote:
> Since we're in the early stages of a SIP deployment, I've had a
> sniffer running on the outside of my firewall capturing packets.
> During a long duration call I realized that the audio issues I was
> hearing were probably being captured in the sniffer; hitting ? ? on my
> phone showed a non-periodic "hiccup" which incremented the error count
> by 7 each time and resulted in a burst of static.
>
> Wireshark seems to crash a lot in the current 1.10.1 version.
>
> In wireshark, I can import the PCAP and use the "Telephony" option and
> it shows the calls that were captured. If I select my call, then go
> into the player, I can play the stream and hear the glitch. But
> Wireshark doesn't make it easy to analyze the calls; I keep getting
> crashes as it follows the RTP streams. :(
>
> Any other tools that will allow me to import a PCAP and analyze my
> streams? The bad call has a non-zero percentage of out of order
> packets.
>
> Thanks.
> _______________________________________________
> cisco-voip mailing list
> [email protected]
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130908/f1c2bfcf/attachment-0001.html>
------------------------------
Subject: Digest Footer
_______________________________________________
cisco-voip mailing list
[email protected]
https://puck.nether.net/mailman/listinfo/cisco-voip
------------------------------
End of cisco-voip Digest, Vol 119, Issue 8
******************************************
