| Author |
Message |
sundardba
Vonage Forum Associate


Joined: Dec 15, 2007
Posts: 15
|
I did speed test I got the result as below
Download speed 1646 Kbps (socket test) Upload speed 2972 Kbps (socket test) Quality of service 38 % Maximum delay 319 ms Round trip time 79 ms Upstream jitter 15.7 ms Upstream packet loss 0 % Upstream packet order 100 % Upstream discards 0 %
I am not expert in Voip. I am Vonage customer for past 2 years recently I moved to new appartment since then for past 2 months phone call gets disconnected automnatically most of the time.
Can any one suggest me is thare are any issues? |
|
|
|
|
 |
tglea
Vonage Forum Evangelist


Joined: Nov 22, 2006
Posts: 433
Location: Nebraska
|
Those results are not good at all. I would suspect that you have something wrong with the internet connection at your new place. Same company or different than before? Same equipment? |
_________________ Cox: 9Mbps/800kbps Router: D-Link DI-624 Vonage: V-Portal |
|
|
|
 |
sundardba
Vonage Forum Associate


Joined: Dec 15, 2007
Posts: 15
|
No it is same comcast connection and same equipment. Currently I have
Modem D Link DCM 202 --> Motorola 2142 VT --> D LINK DI 524 Wireless modem
I also tried connecting laptop directly to Cable modem but didn't help. |
|
|
|
|
 |
VonTechMgr
Vonage Forum Evangelist


Joined: Jan 02, 2008
Posts: 656
Location: NJ
|
Just keep in mind just because you had Comcast working fine in your previous location, does not mean it will operate the same in new location. Depending upon physical location will determine the ISP node you are on. And in some locations a node can be oversubscribed. This means that if the node has more traffic on it due to an over population and all this traffic will reduce each individuals internet experience. While you may not notice anything different when browsing and checking e-mail, an oversubscribed node will have adverse effects on streaming media such as Voip and online gaming.
This is why you hear some people state they have the same ISP as the next guy and one guy has no issues while the other has nothing but issues. |
|
|
|
|
 |
sundardba
Vonage Forum Associate


Joined: Dec 15, 2007
Posts: 15
|
I can completely understand that. I have complained this to comcast and a comcast service person checked the connection he also agreed there are some issues but it is outside the building. I spoke with Vonage support which they said doing the tracert www.yahoo.com should not give any * through the trace . But I am getting the trace. Is that actual issue?
Can some one please validate? is this is true and what can be done. |
|
|
|
|
 |
VonTechMgr
Vonage Forum Evangelist


Joined: Jan 02, 2008
Posts: 656
Location: NJ
|
A * on a traceroute does not necessarily indicate a problem. Some Core and Border routers are programed to pass but not reply to ICMP or certain types of ICMP messages.
Example of a non issue:
traceroute to www.yahoo.com (69.147.76.15), 30 hops max, 400 byte packets 1 192.168.254.1 (192.168.254.1) 6.186 ms 6.558 ms 7.535 ms 7.918 ms 8.293 ms 8.671 ms 9.047 ms 9.423 ms 9.814 ms 10.143 ms 2 10.240.165.5 (10.240.165.5) 11.888 ms 14.862 ms 19.907 ms 20.353 ms 20.811 ms 21.259 ms 13.124 ms 52.641 ms 53.741 ms 54.219 ms 3 dstswr2-vlan2.rh.pswynj.cv.net (67.83.249.34) 34.058 ms 35.569 ms 36.917 ms 38.041 ms 39.877 ms 41.020 ms 43.097 ms 44.589 ms 45.722 ms 46.874 ms 4 67.83.249.21 (67.83.249.21) 47.993 ms 49.127 ms 50.238 ms 22.339 ms 21.340 ms 27.518 ms 26.871 ms 25.415 ms 26.806 ms 25.207 ms 5 rtr4-tg11-3.wan.prnynj.cv.net (64.15.6.37) 24.173 ms 23.523 ms 22.837 ms 22.876 ms 22.213 ms 21.517 ms 20.036 ms 19.332 ms 13.974 ms 11.322 ms 6 64.15.0.65 (64.15.0.65) 16.500 ms 22.582 ms 23.031 ms 23.489 ms 23.958 ms 24.414 ms 24.882 ms 25.339 ms 26.871 ms 27.328 ms 7 64.15.0.94 (64.15.0.94) 33.654 ms 34.408 ms 34.875 ms 35.333 ms 35.607 ms 28.201 ms 17.906 ms 19.506 ms 21.931 ms 27.201 ms 8 * * * * * * * * * * 9 ae2-p141.msr1.re1.yahoo.com (216.115.108.59) 142.218 ms ae2-p151.msr2.re1.yahoo.com (216.115.108.63) 31.873 ms ae1-p141.msr1.re1.yahoo.com (216.115.108.19) 38.529 ms ae2-p151.msr2.re1.yahoo.com (216.115.108.63) 41.635 ms ae1-p141.msr1.re1.yahoo.com (216.115.108.19) 42.888 ms ae2-p151.msr2.re1.yahoo.com (216.115.108.63) 34.985 ms 30.993 ms 27.398 ms ae2-p141.msr1.re1.yahoo.com (216.115.108.59) 82.799 ms ae1-p141.msr1.re1.yahoo.com (216.115.108.19) 35.944 ms 10 te-9-4.bas-a2.re1.yahoo.com (66.196.112.203) 39.925 ms 39.704 ms 39.126 ms te-9-4.bas-a1.re1.yahoo.com (66.196.112.207) 17.287 ms te-9-4.bas-a2.re1.yahoo.com (66.196.112.203) 22.117 ms 29.619 ms te-9-4.bas-a1.re1.yahoo.com (66.196.112.207) 24.334 ms te-8-1.bas-a2.re1.yahoo.com (66.196.112.201) 20.076 ms te-9-4.bas-a1.re1.yahoo.com (66.196.112.207) 19.350 ms te-8-1.bas-a1.re1.yahoo.com (66.196.112.205) 17.708 ms
If you look at hop # 8, you will see that it does not respond to traceroute (ICMP type 30) but the trace does complete to the end point which indicates the router is passing it on.
Now if a traceroute looks more like this, there could be a possible problem.
traceroute to www.yahoo.com (69.147.76.15), 30 hops max, 400 byte packets 1 192.168.254.1 (192.168.254.1) 6.186 ms 6.558 ms 7.535 ms 7.918 ms 8.293 ms 8.671 ms 9.047 ms 9.423 ms 9.814 ms 10.143 ms 2 10.240.165.5 (10.240.165.5) 11.888 ms 14.862 ms 19.907 ms 20.353 ms 20.811 ms 21.259 ms 13.124 ms 52.641 ms 53.741 ms 54.219 ms 3 dstswr2-vlan2.rh.pswynj.cv.net (67.83.249.34) 34.058 ms 35.569 ms 36.917 ms 38.041 ms 39.877 ms 41.020 ms 43.097 ms 44.589 ms 45.722 ms 46.874 ms 4 67.83.249.21 (67.83.249.21) 47.993 ms 49.127 ms 50.238 ms 22.339 ms 21.340 ms 27.518 ms 26.871 ms 25.415 ms 26.806 ms 25.207 ms 5 rtr4-tg11-3.wan.prnynj.cv.net (64.15.6.37) 24.173 ms 23.523 ms 22.837 ms 22.876 ms 22.213 ms 21.517 ms 20.036 ms 19.332 ms 13.974 ms 11.322 ms 6 64.15.0.65 (64.15.0.65) 16.500 ms * 23.031 ms * * 24.414 ms * 25.339 ms * 27.328 ms 7 64.15.0.94 (64.15.0.94) * * 34.875 ms * 35.607 ms 28.201 ms * 19.506 ms * * 8 * * * * * * * * * * 9 ae2-p141.msr1.re1.yahoo.com (216.115.108.59) 142.218 ms ae2-p151.msr2.re1.yahoo.com (216.115.108.63) 31.873 ms ae1-p141.msr1.re1.yahoo.com (216.115.108.19) 38.529 ms ae2-p151.msr2.re1.yahoo.com (216.115.108.63) 41.635 ms ae1-p141.msr1.re1.yahoo.com (216.115.108.19) 42.888 ms ae2-p151.msr2.re1.yahoo.com (216.115.108.63) 34.985 ms 30.993 ms 27.398 ms ae2-p141.msr1.re1.yahoo.com (216.115.108.59) 82.799 ms ae1-p141.msr1.re1.yahoo.com (216.115.108.19) 35.944 ms 10 te-9-4.bas-a2.re1.yahoo.com (66.196.112.203) 39.925 ms 39.704 ms 39.126 ms te-9-4.bas-a1.re1.yahoo.com (66.196.112.207) 17.287 ms te-9-4.bas-a2.re1.yahoo.com (66.196.112.203) 22.117 ms 29.619 ms te-9-4.bas-a1.re1.yahoo.com (66.196.112.207) 24.334 ms te-8-1.bas-a2.re1.yahoo.com (66.196.112.201) 20.076 ms te-9-4.bas-a1.re1.yahoo.com (66.196.112.207) 19.350 ms te-8-1.bas-a1.re1.yahoo.com (66.196.112.205) 17.708 ms
Notice on hops 6 and 7, the ICMP reply times out periodically. This may or may not indicate an issue. Something like this could mean that a certain Core or Border router is dropping packets or it may just have ICMP set at a very low priority which means it may not respond on occasion when it is processing higher priority UDP and TCP packets.
Comcast should be checking the signal strength at your modem. You should also be looking for errors inside your modems internal interface. A quick method to confirm lost connectivity to Comcast is to check the status LED's on your cable modem at the time you notice no internet connectivity or phone service. To check your modem for signal and connection errors, go to http://192.168.100.1 and use a username of admin and a password of dlink. If this doesn't work try username admin and password of hitron or username dlink and password dlink If these don't work, you would need to contact Comcast as they may have locked it down.
If you get into your modem, go to the log section and look for errors similar to this:
SYNC Timing Synchronization failure - Failed to acquire FEC framing SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
Also check your signal levels for both upstream and downstream which will be on another page. The following web page will tell you what range a cable modems levels should be in.
http://homepage.ntlworld.com/robin.d.h.walker/cmtips/signal.html |
|
|
|
|
 |
sundardba
Vonage Forum Associate


Joined: Dec 15, 2007
Posts: 15
|
I just checked the log file from Modem It has these error messages
Index Date/Time ID Level Text 1 06/25/09 01:14:26 R04.0 critical Received Response to Broadcast Maintenance Request, but no Unicast Maintenance opportunities received - T4 timeout 2 06/25/09 01:14:27 T01.0 critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 3 06/25/09 01:24:09 R02.0 critical No Ranging Response received - T3 time-out 4 06/25/09 01:24:39 U02.0 critical UCD invalid or channel unusable 5 06/25/09 01:24:39 T01.0 critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 6 06/25/09 01:24:39 T04.0 critical SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within time-out period 7 06/25/09 02:13:19 R02.0 critical No Ranging Response received - T3 time-out 8 06/25/09 02:25:08 R04.0 critical Received Response to Broadcast Maintenance Request, but no Unicast Maintenance opportunities received - T4 timeout 9 06/25/09 02:25:08 T01.0 critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 10 06/25/09 02:37:46 R02.0 critical No Ranging Response received - T3 time-out 11 06/25/09 02:38:16 U02.0 critical UCD invalid or channel unusable 12 06/25/09 02:38:16 T01.0 critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 13 06/25/09 02:38:16 T04.0 critical SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within time-out period 14 07/03/09 16:15:27 R02.0 critical No Ranging Response received - T3 time-out 15 07/03/09 16:15:28 R03.0 critical Ranging Requests Retries exhausted 16 07/07/09 10:38:20 R02.0 critical No Ranging Response received - T3 time-out 17 07/07/09 10:38:21 R03.0 critical Ranging Requests Retries exhausted 18 07/10/09 05:11:02 R02.0 critical No Ranging Response received - T3 time-out 19 07/10/09 05:11:03 R03.0 critical Ranging Requests Retries exhausted 20 07/13/09 11:13:20 R02.0 critical No Ranging Response received - T3 time-out
Sorry for late reply. I really appreciate if you could help me if this is modem issue or with comcast connection. |
|
|
|
|
 |
sundardba
Vonage Forum Associate


Joined: Dec 15, 2007
Posts: 15
|
Below is the signal strength
Downstream Signal Default Downstream Frequency: Hz Frequency: 711000000 Hz QAM Mode: 256 QAM Channel Power: -3.5 dBmV SNR: 34.357 dB
Upstream Signal Channel Id: 2 Frequency: 34200000 Hz Channel Width: 6400000 Hz Channel Power: 44.5 dBmV
DOCSIS1.1 Quality of Service Parameters Direction Upstream Downstream SFID 0x19213 0x19214 SID 0x1a0f N/A Traffic Priority 1 1 Max Sustained Traffic Rate (bps) 2200000 13200000 Max Transmit Burst (bytes) 5000000 10000000 Min Reserved Traffic Rate (bps) 0 0 Service Flow Scheduling Type Best Effort N/A
************************** I did the Voip test
Voip test statistics -------------------- Jitter: you --> server: 126.6 ms Jitter: server --> you: 12.4 ms Packet loss: you --> server: 0.0 % Packet loss: server --> you: 0.0 % Packet discards: 0.2 % Packets out of order: 0.0 % Estimated MOS score: 3.6
Speed test statistics --------------------- Download speed: 3013232 bps Upload speed: 7312984 bps Download quality of service: 77 % Upload quality of service: 57 % Download test type: socket Upload test type: socket Maximum TCP delay: 372 ms Average download pause: 4 ms Minimum round trip time to server: 23 ms Average round trip time to server: 29 ms Estimated download bandwidth: 13600000bps Route concurrency: 4.5134263 Download TCP forced idle: 0 % Maximum route speed: 22794776bps
I really appreciate if some one could help me. This is so annoying I am really planning to switch to basic land line |
|
|
|
|
 |
VonTechMgr
Vonage Forum Evangelist


Joined: Jan 02, 2008
Posts: 656
Location: NJ
|
Your signal levels look OK and only you would know if these errors correspond to times the calls or internet had problems. Sometimes modem logs have tons of errors but no problems are ever experienced. This is why you need to monitor the status LED's on the modem. Some of these errors would indicate if this were an actual problem, the status LED on the modem would only show Send lit up. So remember to look at the modem when your have an issue with your phone.
Something else I would like to point out to you is that your using an old technology modem. Where you listed your signal levels, the 3rd section shows you have DOCSIS 1.1. The current technology is DOCSIS 2.0 and 3.0 is being deployed as we speak. Voip recommends DOCSIS 2.0 modems as 1.1 operates poorly with Voip and streaming media in general. Not sure how you used this modem in the other location and had no problems but you must have had a very under subscribed node and a really clean connection. |
|
|
|
|
 |
sundardba
Vonage Forum Associate


Joined: Dec 15, 2007
Posts: 15
|
|
|
|
 |
|
|