Difference between revisions of "Packet Loss"
From Kolmisoft Wiki
Jump to navigationJump to search
(Created page with 'VoIP packet loss takes place when a large amount of traffic hits the network and causes it to drop packets. It usually manifest itself as dropped conversations or “tinny” sou…') |
|||
| (3 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
VoIP packet loss takes place when a large amount of traffic hits the network and causes it to drop packets. It usually manifest itself as dropped conversations or “tinny” sounds. Packet loss should never exceed 1% and most service providers guarantee service levels with .5% or less packet loss. Packet loss of 1% translates into one voice clip or skip every three minutes, while packet loss of .25% translates into one error every 53 minutes. | VoIP packet loss takes place when a large amount of traffic hits the network and causes it to drop packets. It usually manifest itself as dropped conversations or “tinny” sounds. | ||
Packet loss should never exceed 1% and most service providers guarantee service levels with .5% or less packet loss. | |||
Packet loss of 1% translates into one voice clip or skip every three minutes, while packet loss of .25% translates into one error every 53 minutes. | |||
Test with ping: | |||
ping -f -c 1000 -i 0.02 -v SERVER_IP | |||
NOTE: Change SERVER_IP to real server's IP | |||
packet loss should be < 2% (Example: 0% packet loss) | |||
<br><br> | |||
= See also = | |||
* [[RTPAUDIOQOS Demystified]] | |||
Latest revision as of 14:18, 29 October 2011
VoIP packet loss takes place when a large amount of traffic hits the network and causes it to drop packets. It usually manifest itself as dropped conversations or “tinny” sounds.
Packet loss should never exceed 1% and most service providers guarantee service levels with .5% or less packet loss.
Packet loss of 1% translates into one voice clip or skip every three minutes, while packet loss of .25% translates into one error every 53 minutes.
Test with ping:
ping -f -c 1000 -i 0.02 -v SERVER_IP NOTE: Change SERVER_IP to real server's IP packet loss should be < 2% (Example: 0% packet loss)
