Peridocally we see MOS deviations that cannot be explained by errors on the network (primarily our radio WAN). This sample shows PacketLossSD. The router we use for IP SLA does not show any output drops, nor do any of the relevant switch interfaces between the SLA router and the responder. All switches do not show any QOS issues, nor any relevant queue drops. Are there any additional things that can be checked to determine where the packet loss is occurring? Additional ideas would be apprecated. The SLA router and responder (router) are separated by three switches:
ICPIF Value: 38 MOS score: 2.85 RTT Values (milliseconds): NumOfRTT: 247 RTTAvg: 2 RTTMin: 2 RTTMax: 3 RTTSum: 496 RTTSum2: 998 Packet Loss Values: PacketLossSD: 753 PacketLossDS: 0 PacketOutOfSequence: 0 PacketMIA: 0 PacketLateArrival: 0 InternalError: 0 Busies: 0 PacketSkipped: 0 Jitter Values (milliseconds): MinOfPositivesSD: 1 MaxOfPositivesSD: 1 NumOfPositivesSD: 35 SumOfPositivesSD: 35 Sum2PositivesSD: 35 MinOfNegativesSD: 1 MaxOfNegativesSD: 1 NumOfNegativesSD: 35 SumOfNegativesSD: 35 Sum2NegativesSD: 35 MinOfPositivesDS: 1 MaxOfPositivesDS: 1 NumOfPositivesDS: 33 SumOfPositivesDS: 33 Sum2PositivesDS: 33 MinOfNegativesDS: 1 MaxOfNegativesDS: 1 NumOfNegativesDS: 33 SumOfNegativesDS: 33 Sum2NegativesDS: 33 Jitter Avg: 1 JitterSD Avg: 1 JitterDS Avg: 1 Interarrival jitterout: 0 Interarrival jitterin: 0 One Way Values (milliseconds): NumOfOW: 247 OWMinSD: 1 OWMaxSD: 2 OWSumSD: 282 OWSum2SD: 352 OWMinDS: 1 OWMaxDS: 1 OWSumDS: 214 OWSum2DS: 214 OWAvgSD: 1 OWAvgDS: 0 Bucket Index: 80 Aggregation start time 07:18:22.629 PDT Wed Apr 21 2010 Target Address: 10.8.2.26 Number of failed operations due to a Disconnect: 0 Number of failed operations due to a Timeout: 0 Number of failed operations due to a Busy: 0 Number of failed operations due to a No Connection: 0 Number of failed operations due to an Internal Error: 0 Number of failed operations due to a Sequence Error: 0 Number of failed operations due to a Verify Error: 0
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...