I have frequent outgoing calls where others cannot understand me. They describe my sounding "underwater" or garbled. Sometimes they can't hear me at all.
1. Anacortes, WA 98221
2. WaveBroadband Cable
3. Upload 1.08 Mbps Download 1.74 Mbps
4. Arris TM502G cable Modem
5. Vonage VT2142-VR
6. Cable Modem - WRT54G Router - Vonage Device (Vonage Device is 3 feet From Modem and Router)
7. I have 900, 2.4, and 5.8 MHz cordless phones. The problems seem to occur on all.
I ran the Vonage® VoIP Speed Test many times and below are the results from several.
Thanks. Ken
Speed test statistics
---------------------
Download speed: 1201040 bps
Upload speed: 1090216 bps
Quality of service: -- %
Download test type: socket
Upload test type: socket
Maximum download pause: 2320 ms
Average download pause: 32 ms
Minimum round trip time to server: 86 ms
Average round trip time to server: 115 ms
VoIP test statistics
--------------------
Jitter: you --> server: 3.3 ms
Jitter: server --> you: 12.4 ms
Packet loss: you --> server: 0.0 %
Packet loss: server --> you: 0.0 %
Packet discards: 0.0 %
Packets out of order: 0.0 %
Number of supported VoIP lines: 18
Estimated MOS score: 3.9
Speed test statistics
---------------------
Download speed: 1302272 bps
Upload speed: 1090592 bps
Quality of service: 49 %
Download test type: socket
Upload test type: socket
Maximum download pause: 192 ms
Average download pause: 31 ms
Minimum round trip time to server: 92 ms
Average round trip time to server: 95 ms
VoIP test statistics
--------------------
Jitter: you --> server: 226.3 ms
Jitter: server --> you: 70.4 ms
Packet loss: you --> server: 0.0 %
Packet loss: server --> you: 6.6 %
Packet discards: 0.0 %
Packets out of order: 0.0 %
Number of supported VoIP lines: 18
Estimated MOS score: 3.1
Speed test statistics
---------------------
Download speed: 668552 bps
Upload speed: 1089664 bps
Quality of service: 1 %
Download test type: socket
Upload test type: socket
Maximum download pause: 2276 ms
Average download pause: 58 ms
Minimum round trip time to server: 315 ms
Average round trip time to server: 327 ms
VoIP test statistics
--------------------
Jitter: you --> server: 3.2 ms
Jitter: server --> you: 9.0 ms
Packet loss: you --> server: 0.0 %
Packet loss: server --> you: 0.5 %
Packet discards: 0.0 %
Packets out of order: 0.0 %
Number of supported VoIP lines: 11
Estimated MOS score: 3.7
Speed test statistics
---------------------
Download speed: 618328 bps
Upload speed: 1081976 bps
Quality of service: 15 %
Download test type: socket
Upload test type: socket
Maximum download pause: 632 ms
Average download pause: 64 ms
Minimum round trip time to server: 88 ms
Average round trip time to server: 175 ms
VoIP test statistics
--------------------
Jitter: you --> server: 220.1 ms
Jitter: server --> you: 38.7 ms
Packet loss: you --> server: 0.2 %
Packet loss: server --> you: 7.6 %
Packet discards: 0.0 %
Packets out of order: 0.0 %
Number of supported VoIP lines: 10
Estimated MOS score: 3.2
From your test results, you have really bad jitter. Jitter occurs when sequential packets are not received in the order and spacing that they were sent out at. If the packets are far enough out of order, they are as good as lost because the time slot that they were needed for came and went. This causes the audio to break up. Basically your internet connection is broken. You will need to report the problem to your ISP.
On your PC, run the following command in the command prompt:
This is a ping test that will send packets to Yahoo's web server and record the time it takes to get there and come back. The difference between the minimum and maximum times should be no more than about 20 milliseconds. Any more and you'll have the audio problem that you're describing.
Call up your ISP and tell them that your internet connection has high jitter and its causing you problems with using streaming audio services (don't mention Vonage specifically). Give them the results of the ping test. Don't take them having you run a speed test, "pinging your modem", or "checking your signal" and saying everything is fine -- it isn't fine. Once they fix whatever is causing the problem, you shouldn't have those problems anymore.
The character you are referring to should be a lower case L as that is what specifics the packet size sent. In this scenario, you are being instructed to send a 600 byte size packet. Those are hyphens or minus signs used in front of the n and the lower case L. You can copy and paste the command into your command prompt window if your unsure.
Call up your ISP and tell them that your internet connection has high jitter and its causing you problems with using streaming audio services (don't mention Vonage specifically). Give them the results of the ping test.
Does this Ping result support that explanation? I think the problem is intermittent and I am unable to read the results to know if these results reflect the jitter problem. If necessary I can run the test repeatedly until I get an evaluation that will be persuasive when I contact my ISP.
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Andy>ping -n 100 -l 600 www.yahoo.com
Reply from 209.131.36.158: bytes=600 time=34ms TTL=55
Reply from 209.131.36.158: bytes=600 time=33ms TTL=55
Reply from 209.131.36.158: bytes=600 time=33ms TTL=55
Reply from 209.131.36.158: bytes=600 time=35ms TTL=55
Reply from 209.131.36.158: bytes=600 time=32ms TTL=55
Reply from 209.131.36.158: bytes=600 time=1391ms TTL=55
Reply from 209.131.36.158: bytes=600 time=33ms TTL=55
Reply from 209.131.36.158: bytes=600 time=32ms TTL=55
Reply from 209.131.36.158: bytes=600 time=34ms TTL=55
Reply from 209.131.36.158: bytes=600 time=32ms TTL=55
Reply from 209.131.36.158: bytes=600 time=32ms TTL=55
Reply from 209.131.36.158: bytes=600 time=32ms TTL=55
Reply from 209.131.36.158: bytes=600 time=32ms TTL=55
Reply from 209.131.36.158: bytes=600 time=37ms TTL=55
Reply from 209.131.36.158: bytes=600 time=33ms TTL=55
Reply from 209.131.36.158: bytes=600 time=32ms TTL=55
Reply from 209.131.36.158: bytes=600 time=33ms TTL=55
Reply from 209.131.36.158: bytes=600 time=32ms TTL=55
Reply from 209.131.36.158: bytes=600 time=34ms TTL=55
Reply from 209.131.36.158: bytes=600 time=32ms TTL=55
Reply from 209.131.36.158: bytes=600 time=32ms TTL=55
Reply from 209.131.36.158: bytes=600 time=34ms TTL=55
Reply from 209.131.36.158: bytes=600 time=34ms TTL=55
Reply from 209.131.36.158: bytes=600 time=35ms TTL=55
Reply from 209.131.36.158: bytes=600 time=34ms TTL=55
Reply from 209.131.36.158: bytes=600 time=32ms TTL=55
Reply from 209.131.36.158: bytes=600 time=33ms TTL=55
Reply from 209.131.36.158: bytes=600 time=33ms TTL=55
Reply from 209.131.36.158: bytes=600 time=32ms TTL=55
Reply from 209.131.36.158: bytes=600 time=31ms TTL=55
Reply from 209.131.36.158: bytes=600 time=33ms TTL=55
Reply from 209.131.36.158: bytes=600 time=32ms TTL=55
Reply from 209.131.36.158: bytes=600 time=33ms TTL=55
Reply from 209.131.36.158: bytes=600 time=33ms TTL=55
Reply from 209.131.36.158: bytes=600 time=34ms TTL=55
Reply from 209.131.36.158: bytes=600 time=36ms TTL=55
Reply from 209.131.36.158: bytes=600 time=33ms TTL=55
Reply from 209.131.36.158: bytes=600 time=32ms TTL=55
Reply from 209.131.36.158: bytes=600 time=31ms TTL=55
Reply from 209.131.36.158: bytes=600 time=33ms TTL=55
Reply from 209.131.36.158: bytes=600 time=32ms TTL=55
Reply from 209.131.36.158: bytes=600 time=33ms TTL=55
Reply from 209.131.36.158: bytes=600 time=33ms TTL=55
Reply from 209.131.36.158: bytes=600 time=31ms TTL=55
Reply from 209.131.36.158: bytes=600 time=32ms TTL=55
Reply from 209.131.36.158: bytes=600 time=32ms TTL=55
Reply from 209.131.36.158: bytes=600 time=31ms TTL=55
Reply from 209.131.36.158: bytes=600 time=33ms TTL=55
Reply from 209.131.36.158: bytes=600 time=32ms TTL=55
Reply from 209.131.36.158: bytes=600 time=32ms TTL=55
Reply from 209.131.36.158: bytes=600 time=32ms TTL=55
Reply from 209.131.36.158: bytes=600 time=31ms TTL=55
Reply from 209.131.36.158: bytes=600 time=32ms TTL=55
Reply from 209.131.36.158: bytes=600 time=40ms TTL=55
Reply from 209.131.36.158: bytes=600 time=35ms TTL=55
Reply from 209.131.36.158: bytes=600 time=32ms TTL=55
Reply from 209.131.36.158: bytes=600 time=32ms TTL=55
Reply from 209.131.36.158: bytes=600 time=34ms TTL=55
Reply from 209.131.36.158: bytes=600 time=32ms TTL=55
Reply from 209.131.36.158: bytes=600 time=38ms TTL=55
Reply from 209.131.36.158: bytes=600 time=39ms TTL=55
Reply from 209.131.36.158: bytes=600 time=33ms TTL=55
Reply from 209.131.36.158: bytes=600 time=33ms TTL=55
Reply from 209.131.36.158: bytes=600 time=31ms TTL=55
Reply from 209.131.36.158: bytes=600 time=33ms TTL=55
Reply from 209.131.36.158: bytes=600 time=33ms TTL=55
Reply from 209.131.36.158: bytes=600 time=1153ms TTL=55
Reply from 209.131.36.158: bytes=600 time=32ms TTL=55
Reply from 209.131.36.158: bytes=600 time=32ms TTL=55
Reply from 209.131.36.158: bytes=600 time=34ms TTL=55
Reply from 209.131.36.158: bytes=600 time=33ms TTL=55
Reply from 209.131.36.158: bytes=600 time=33ms TTL=55
Reply from 209.131.36.158: bytes=600 time=34ms TTL=55
Reply from 209.131.36.158: bytes=600 time=31ms TTL=55
Reply from 209.131.36.158: bytes=600 time=35ms TTL=55
Reply from 209.131.36.158: bytes=600 time=32ms TTL=55
Reply from 209.131.36.158: bytes=600 time=32ms TTL=55
Reply from 209.131.36.158: bytes=600 time=32ms TTL=55
Reply from 209.131.36.158: bytes=600 time=32ms TTL=55
Reply from 209.131.36.158: bytes=600 time=38ms TTL=55
Reply from 209.131.36.158: bytes=600 time=32ms TTL=55
Reply from 209.131.36.158: bytes=600 time=33ms TTL=55
Reply from 209.131.36.158: bytes=600 time=33ms TTL=55
Reply from 209.131.36.158: bytes=600 time=33ms TTL=55
Reply from 209.131.36.158: bytes=600 time=32ms TTL=55
Reply from 209.131.36.158: bytes=600 time=32ms TTL=55
Reply from 209.131.36.158: bytes=600 time=31ms TTL=55
Reply from 209.131.36.158: bytes=600 time=45ms TTL=55
Reply from 209.131.36.158: bytes=600 time=33ms TTL=55
Reply from 209.131.36.158: bytes=600 time=33ms TTL=55
Reply from 209.131.36.158: bytes=600 time=32ms TTL=55
Reply from 209.131.36.158: bytes=600 time=33ms TTL=55
Reply from 209.131.36.158: bytes=600 time=34ms TTL=55
Reply from 209.131.36.158: bytes=600 time=38ms TTL=55
Reply from 209.131.36.158: bytes=600 time=33ms TTL=55
Reply from 209.131.36.158: bytes=600 time=38ms TTL=55
Reply from 209.131.36.158: bytes=600 time=32ms TTL=55
Reply from 209.131.36.158: bytes=600 time=33ms TTL=55
Reply from 209.131.36.158: bytes=600 time=33ms TTL=55
Reply from 209.131.36.158: bytes=600 time=32ms TTL=55
Ping statistics for 209.131.36.158:
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 31ms, Maximum = 1391ms, Average = 57ms
Last edited by weflyuniv on Thu Oct 09, 2008 3:33 pm; edited 1 time in total
You also mention that it is intermittent. Would you say this happens and becomes worse during peak hours when more people happen to be home and using the internet? Is your wireless router completely secured so that there are no neighbors or war drivers hijacking your connection for their own use? Many intermittent audio issues are caused by saturated nodes on the local ISP's network, P2P file sharing, online gaming, etc... So you need to make sure no one else can possibly be using your connection through your wireless router. Also take note to the time of day the issue may tend to occur.
You also mention that it is intermittent. Would you say this happens and becomes worse during peak hours when more people happen to be home and using the internet? Is your wireless router completely secured so that there are no neighbors or war drivers hijacking your connection for their own use? Many intermittent audio issues are caused by saturated nodes on the local ISP's network, P2P file sharing, online gaming, etc... So you need to make sure no one else can possibly be using your connection through your wireless router. Also take note to the time of day the issue may tend to occur.
Sorry. Now they are there.
My router has the WEP protection with a password so I think it is unavailable for others.
So your results are not terrible outside of 2 packets that reached over 1 full second of latency. While this will not cause extended audio problems, if at different times of the day, your seeing your round trip times jumping around from 30 to 100 to 20 to 150 to 1000 back to 30 or multiple packets ranging in the hundreds of milliseconds or request timeouts, this would uncover your problem.
One thing to note is that your also running a Ping to yahoo. Obviously when making a phone call, your audio is going to be streaming from one of Vonage Co locations. This means that the path between you and a Vonage media relay will be different from the path from you to yahoo. Therefore, this test will only show you if you have inherent latency, packet loss and jitter within your own LAN or through the first few hops through your ISP.
In order to be more accurate, you would need to run the same ping command and traceroutes to Vonage media relay IP addresses during the times that your audio is affected. The traceroute will better pinpoint where the issue may be occurring.
Might I add to this conversation that WEP is definitely not the wireless security protocol to use this day and age. Use either wpa or wpa2. WEP is very easy to crack into now.
tglea Vonage Forum Evangelist
Joined: Nov 22, 2006 Posts: 429
Location: Nebraska
In order to be more accurate, you would need to run the same ping command and traceroutes to Vonage media relay IP addresses during the times that your audio is affected. The traceroute will better pinpoint where the issue may be occurring
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
All times are GMT - 5 Hours
Vonage Service Plans
Vonage VoIP Members
Members New anke New Today 1 Yesterday 6 Total 55097 Who Is On Site Visitors 245 Members 2 Total 247
High-speed Internet required. Unlimited calling subject to normal residential use. Vonage 911 service operates differently than traditional 911. See www.vonage.com/911 for details. Alarms, TTY and other systems may not be compatible.
Thinking of signing up for Vonage but have questions? Business and Residential customers can call Toll Free 24 hours a day at: 1-888-692-8074 No Vonage Promotional Codes or Coupon Codes are required at www.vonage.com.
The Vonage Forum provides the Vonage Free
Month sign up Best Offer Promotion Deal as a means to offset
our cost. If you are considering signing up for Vonage and have found our Vonage
News, Customer Reviews, Forums & all other parts of this site useful, please
use our Vonage Free Month sign up offer Deal Coupon.
Vonage VoIP Phone Service is redefining communications by offering consumers & small business VoIP Internet phones, an affordable alternative to traditional phone service.
The Vonage VoIP Forum Generated This Page In: 0.52 Seconds and 264 Pages In The Last 60 Seconds The Vonage VoIP Forum
Members
New 
New Today 1
Yesterday 6
Total 55097
Who Is On Site
Visitors 245
Members 2
Total 247
-0.04