Hey guys just putting a list together of tools to diagnose network jitter what are you guys using out there? -carlos
Carlos Alcantar wrote:
Hey guys just putting a list together of tools to diagnose network jitter what are you guys using out there?
Wireshark. -- Alex Balashov - Principal Evariste Systems Web : http://www.evaristesys.com/ Tel : (+1) (678) 954-0670 Direct : (+1) (678) 954-0671
+1 on wireshark/packet tracing I actually wrote a 'interface' around gulp (a packet grabber) and pcapmerge to allow our support folk to selectivly pull traces from a bunch of passive taps in our network. Initially I was also capturing RTP streams, however, due to legal concerns, I now only turn up individual filters for RTP. however, all signalling still does get caught.. makes it really easy to retroactively look for a packet trace when the customer calls in an hour later with an issue. it all currently writes to a 16 TB dedicated EMC SAN. I'm getting ready to release my package as open source... internally I call it the 'MegaSniffer'... however, not really sure what to name it going forward. there's been lots of ideas for go-forward development, including auto-parsing the signalling data (sip ladder diagrams, etc)... however, the way it is right now has been used extensively by our support folk. -J
Carlos Alcantar wrote:
Hey guys just putting a list together of tools to diagnose network jitter what are you guys using out there?
Wireshark.
-- Alex Balashov - Principal Evariste Systems Web : http://www.evaristesys.com/ Tel : (+1) (678) 954-0670 Direct : (+1) (678) 954-0671 _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
That sounds sweet! I'd love to see/hear how you go from gulping chunks of data to finding and extracting what you want from all those streams (?) I hacked up a signalling only fault finding solution based on jNetPcap and the H2 in memory database so we capture and store all the signalling traffic on the front end of our SBCs... I can store about 7-8 million packets in about 15GB of RAM, which gives us a few hours of back history. Given some spare CPU cycles on the capture box we can also track and monitor things like registration continuity on clients, User-Agent make/model/version, and ASNum/CountryCode distribution of clients etc. On top of that we run a RESTlet server that allows our customer reps to run traces on customers via SQL on the in memory database.... the resultant data is converted via JavaScript into SVG ladder-trace diagrams In terms of the original query about network jitter I would assume running something like Cisco's IP-SLA or similar between the hop-on/ hop-off points of your network would give you some demonstrated confidence and assurance in the performance of your own network. Passive taps will only give you 'partial' view of performance, unless both ends support RTCP in which case life is much better. Cheers, Peter On 25/08/2009, at 2:42 AM, Jason Vanick wrote:
+1 on wireshark/packet tracing
I actually wrote a 'interface' around gulp (a packet grabber) and pcapmerge to allow our support folk to selectivly pull traces from a bunch of passive taps in our network.
Initially I was also capturing RTP streams, however, due to legal concerns, I now only turn up individual filters for RTP.
however, all signalling still does get caught.. makes it really easy to retroactively look for a packet trace when the customer calls in an hour later with an issue.
it all currently writes to a 16 TB dedicated EMC SAN.
I'm getting ready to release my package as open source... internally I call it the 'MegaSniffer'... however, not really sure what to name it going forward.
there's been lots of ideas for go-forward development, including auto-parsing the signalling data (sip ladder diagrams, etc)... however, the way it is right now has been used extensively by our support folk.
-J
Carlos Alcantar wrote:
Hey guys just putting a list together of tools to diagnose network jitter what are you guys using out there?
Wireshark.
On Aug 25, 2009, at 9:32 PM, Peter Childs wrote:
Passive taps will only give you 'partial' view of performance, unless both ends support RTCP in which case life is much better.
RTCP is very useful for some things, but not for jitter. Estimating jitter certainly APPEARS easier with RTCP -- but the facts disappoint. You can have a RTCP-reported jitter, but still have a terrible phone call. The RTCP-reported jitter average masks periods where the jitter buffer overflows (due to router queue compression) or underflows (due to long delays). The jitter calculation in RTCP gives, at best, a vague long- term statistical view. For example: using the RTCP jitter statistic defined in RFC 3550, suppose you have 20 ms ptime RTP, but network congestion causes each packet to arrive 25 ms apart. Suppose also you have a 6*ptime (120 ms) jitter buffer that begins playback when it's filled to 3*ptime (60 ms). RTCP will dutifully report 5 ms of jitter, but in reality the user will experience alternating periods of audio and silence (The pattern will be something like: 75 ms silence followed by 600 ms audio, then 75 ms silence, then 600 ms audio, etc.) RTCP XR (RFC 3611) does provide some additional useful data on this in the discard-rate field. This is a direct measurement of jitter buffer behavior. However, I believe you can still have silent periods due to network congestion, but report no discards and trivial jitter averages. mark r lindsey at e-c-group.com http://e-c-group.com/~lindsey +12293160013
smokeping may be interesting for you to take a look at. http://oss.oetiker.ch/smokeping/doc/index.en.html matt On Mon, 24 Aug 2009, Carlos Alcantar wrote:
Hey guys just putting a list together of tools to diagnose network jitter what are you guys using out there?
?
-carlos
From a CPE perspective, the Adtran Total Access 900s have excellent stats. Lee Matt Yaklin wrote:
smokeping may be interesting for you to take a look at.
http://oss.oetiker.ch/smokeping/doc/index.en.html
matt
On Mon, 24 Aug 2009, Carlos Alcantar wrote:
Hey guys just putting a list together of tools to diagnose network jitter what are you guys using out there?
-carlos
------------------------------------------------------------------------
_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
Another +1 for wireshark We also use PingPlotter pro sometimes.. -Jarrod On Mon, Aug 24, 2009 at 1:00 PM, Carlos Alcantar <carlos at race.com> wrote:
Hey guys just putting a list together of tools to diagnose network jitter what are you guys using out there?
-carlos
_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
-- Jarrod Lash, <jarrod at fed-com.com> Federated Communications Office: +1-412-357-2127 Mobile: +1-412-999-0049 Fax: +1-412-545-8368
Acme radius CDR's contain RTP statistics per-call for large scale statistics collection. Not sure if/what other SBC's make this data available. Wireshark for individual case analysis. Visualware also makes a decent test suite that doesn't break the bank, and is great for diagnosing subscriber connection issues. On Mon, 2009-08-24 at 10:00 -0700, Carlos Alcantar wrote:
Hey guys just putting a list together of tools to diagnose network jitter what are you guys using out there?
-carlos
_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
You could also take a look at the Hammer XMS. http://www.empirix.com/products/hammer_xms_service_assurance.asp -- Jason Nesheim ----- Original Message ----- From: "Nathan Stratton" <nathan at robotics.net> To: "anorexicpoodle" <anorexicpoodle at gmail.com> Cc: voiceops at voiceops.org Sent: Wednesday, August 26, 2009 7:46:59 AM Subject: Re: [VoiceOps] network jitter tools On Tue, 25 Aug 2009, anorexicpoodle wrote:
Acme radius CDR's contain RTP statistics per-call for large scale statistics collection. Not sure if/what other SBC's make this data available.
Covergence now acme also does. -Nathan _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
On Sat, Aug 29, 2009 at 10:31 AM, Jason L. Nesheim<jnesheim at cytek.biz> wrote:
You could also take a look at the Hammer XMS.
http://www.empirix.com/products/hammer_xms_service_assurance.asp
very expensive, and may or may not be what you are looking for in terms of actual features versus "thingsthatarecoolandwillbeaddedinanupcomingreleaseifyoupayforthemtobe" that being said, iperf can do jitter measurements: you could easily set it to run periodically from cron and pipe the output of the test to a shell/python/perl/etc script to parse and display. the same can be done with crisco's ip-sla goo, though it can take a heavy toll on the routers it is running on what kind of hammer do you want? how big is it? and how much do you want to pay for it? (not a reference to the empirix product) /joshua -- A common mistake that people make when trying to design something completely foolproof is to underestimate the ingenuity of complete fools. - Douglas Adams -
participants (12)
-
abalashov＠evaristesys.com -
anorexicpoodle＠gmail.com -
carlos＠race.com -
jarrod＠fed-com.com -
jnesheim＠cytek.biz -
jsahala＠gmail.com -
jvanick＠spruce.oaknet.com -
lindsey＠e-c-group.com -
lriemer＠bestline.net -
myaklin＠g4.net -
nathan＠robotics.net -
pchilds＠internode.com.au