Jitter - Packet Loss via List Meas Stat Interpretation

[griffitovic]

A partner of ours has IP phones deployed remotely off of their S8700 switch. They have been experiencing choppy lines, disconnects, long beeps, etc on calls. We've pretty much eliminating timing on the inbound T-1s and phone problems. My guess is IP related problems. We had them run 'list meas stat' on some of the IP phones and the report doesn't look clean like they do when we run the same measurements on our in-house IP phones. Can someone provide assistance on interpreting this? Specifically what do the asterisks showing up on the Pkloss line mean? How about the WC:X counts on the Jitter lines? Any assistance would be appreciated. Excerpts below:


station 54054 Page 2

LIST TRACE

time data
05:37:37 Jitter:0 0 0 0 0 0 0 0 0 0: Buff:8 WC:5 Avg:0
05:37:37 Pkloss:* * * * * * * * * *: Oofo:0 WC:0 Avg:0
VOIP data from: 192.168.1.14:2068
05:37:47 Jitter:0 0 0 0 0 0 0 0 0 0: Buff:8 WC:5 Avg:0
05:37:47 Pkloss:* * * * * 0 0 0 0 *: Oofo:0 WC:0 Avg:0
VOIP data from: 192.168.1.14:2068
05:37:57 Jitter:0 0 0 0 0 0 0 0 0 0: Buff:8 WC:5 Avg:0
05:37:57 Pkloss:* 0 0 * * * * * * *: Oofo:0 WC:0 Avg:0
VOIP data from: 192.168.1.14:2068
05:38:07 Jitter:0 0 0 0 0 0 0 0 0 0: Buff:8 WC:5 Avg:0
05:38:07 Pkloss:0 0 0 0 0 0 0 0 0 *: Oofo:0 WC:0 Avg:0
VOIP data from: 192.168.1.14:2068
05:38:17 Jitter:0 0 0 0 0 0 0 0 0 0: Buff:8 WC:5 Avg:0
05:38:17 Pkloss:0 0 * 0 0 0 0 0 0 0: Oofo:0 WC:0 Avg:0
VOIP data from: 192.168.1.14:2068
05:38:27 Jitter:0 0 0 0 0 0 0 0 0 0: Buff:8 WC:5 Avg:0

press CANCEL to quit -- press NEXT PAGE to continue

ace station 54054 Page 3

LIST TRACE

time data
05:38:27 Pkloss:0 0 * * * 0 0 * 0 0: Oofo:0 WC:0 Avg:0
VOIP data from: 192.168.1.14:2068
05:38:37 Jitter:0 0 0 0 0 0 0 0 0 0: Buff:8 WC:5 Avg:0
05:38:37 Pkloss:0 0 * 0 0 0 0 * 0 0: Oofo:0 WC:0 Avg:0
VOIP data from: 192.168.1.14:2068
05:38:47 Jitter:0 0 0 0 0 0 0 0 0 0: Buff:8 WC:5 Avg:0
05:38:47 Pkloss:0 0 0 0 * 0 0 0 * 0: Oofo:0 WC:0 Avg:0
VOIP data from: 192.168.1.14:2068
05:38:57 Jitter:0 0 0 0 0 0 0 0 0 0: Buff:8 WC:5 Avg:0
05:38:57 Pkloss:0 * * * * * * * 0 0: Oofo:0 WC:0 Avg:0
VOIP data from: 192.168.1.14:2068
05:39:07 Jitter:0 0 0 0 0 0 0 0 0 0: Buff:8 WC:5 Avg:0
05:39:07 Pkloss:0 0 0 * * * * * * 0: Oofo:0 WC:0 Avg:0
05:39:10 hold station 54054 cid 0x912


tation 54111 Page 1

LIST TRACE

time data

05:43:15 G711A ssn ps:20 rn:2/2 10.5.2.8:2568 192.168.1.12:2696
05:43:20 active station 54111 cid 0xab4
VOIP data from: 192.168.1.12:2696
05:43:27 Jitter:0 0 0 0 0 0 0 0 0 0: Buff:8 WC:1 Avg:0
05:43:27 Pkloss:* * 0 0 0 0 * 0 0 0: Oofo:0 WC:0 Avg:0
VOIP data from: 192.168.1.12:2696
05:43:37 Jitter:0 0 0 0 0 0 0 0 0 0: Buff:8 WC:1 Avg:0
05:43:37 Pkloss:0 * 0 * * * * * * *: Oofo:0 WC:0 Avg:0
VOIP data from: 192.168.1.12:2696
05:43:46 Jitter:0 0 0 0 0 0 0 0 0 0: Buff:8 WC:1 Avg:0
05:43:46 Pkloss:* * * 0 0 0 0 0 0 0: Oofo:0 WC:0 Avg:0
VOIP data from: 192.168.1.12:2696
05:43:56 Jitter:0 0 0 0 0 0 0 0 0 0: Buff:8 WC:1 Avg:0
05:43:57 Pkloss:* * * * 0 * * * * *: Oofo:0 WC:0 Avg:0
VOIP data from: 192.168.1.12:2696

Thanks! griffitovic

 

[JayNEC]

* on the packet loss mean 100% loss for that time interval - 1 second. Eg, each line is 10 seconds of history.

 

[98Converter]

Have your network guys check the utilization on the WAN. You could be running low on bandwidth - we're battling that right now. Also make sure your settings are correct on both ends (Network Router & PBX) of your MedPro's (100 Full/Duplex). You may want to confirm whether there on 100mb Blades or 1gig as well...

Hope this helps,
Chris

We are what we repeatedly do. Excellence, then, is not an act but a habit. ARISTOTLE 384-322 B.C.