cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
654
Views
0
Helpful
3
Replies

IP SLA records high jitter, but MoS seems good

3alee
Level 1
Level 1

Hi all,

 

IPSLAs Latest Operation Statistics
 
IPSLA operation id: 14
Type of operation: udp-jitter
Latest RTT: 1 milliseconds
Latest operation start time: 15:04:50 CCT Mon Aug 10 2015
Latest operation return code: OK
RTT Values:
Number Of RTT: 1000 RTT Min/Avg/Max: 1/1/1 milliseconds
Latency one-way time:
Number of Latency one-way Samples: 0
Source to Destination Latency one way Min/Avg/Max: 0/0/0 milliseconds
Destination to Source Latency one way Min/Avg/Max: 0/0/0 milliseconds
Jitter Time:
Number of SD Jitter Samples: 999
Number of DS Jitter Samples: 999
Source to Destination Jitter Min/Avg/Max: 14/41/984 milliseconds
Destination to Source Jitter Min/Avg/Max: 0/41/982 milliseconds
Packet Loss Values:
Loss Source to Destination: 0
Source to Destination Loss Periods Number: 0
Source to Destination Loss Period Length Min/Max: 0/0
Source to Destination Inter Loss Period Length Min/Max: 0/0
Loss Destination to Source: 0
Destination to Source Loss Periods Number: 0
Destination to Source Loss Period Length Min/Max: 0/0
Destination to Source Inter Loss Period Length Min/Max: 0/0
Out Of Sequence: 0 Tail Drop: 0
Packet Late Arrival: 0 Packet Skipped: 0
Voice Score Values:
Calculated Planning Impairment Factor (ICPIF): 1
MOS score: 4.34
Number of successes: 1
Number of failures: 0
Operation time to live: Forever
 
Switch(config)#do sh run | b ip sla 14
ip sla 14
 udp-jitter 10.246.44.116 5001 source-ip 10.246.180.116 source-port 16014 codec g711ulaw
 tos 160
ip sla schedule 14 life forever start-time now
 
 
The MoS seems ok, so can we ignore the max jitter value?
 
Thanks!
3 Replies 3

Hi,

 

MOS is calculated based on normalized/average values. If you have 999 samples and your MOS is 4.34 then you can ignore the max jitter value.

Thanks a lot!

 

Could you also suggest the ways to investigate and troubleshoot the high jitter?

For this instance you don't need to spend much time on it. But generally speaking, you can run use trace route to see at which hop you have problems.