Jump to content
Sign in to follow this  
purewhitelight

Time outs on Cable Modem VoIP drops

Recommended Posts

Hi and thanks - 

I have high speed cable modem.  I am running Windows XP SP2, I have a Linksys Wireless G Modem, but the main computer is "Hard Wired".  I have fast speeds, as the download stats show, but I have time outs.  Symptom = Those time-outs cause my VioIP (Company = Packet 8)  phone to drop calls. 

The tests below are self titled - you can see that I get time outs - and also HUGE fluctuations in response times and time outs (see below).  The cable company (Time Warner Roadrunner - SoCal - I am in Venice - Los Angeles, CA) has rewired the house and tells me I have a strong signal, even though the "drop outs" occur while still on their network.  (See step # 5 on the tracerouts.)

On the ping tests, the phone company tells me I can expect drop-outs and dropped calls if the fluctuation range is over 30 ms.  You can see that mine is 58ms, not counting the time out.  This is typical.

Can you help me solve this problem?

Here are tests:

:::.. Download Stats ..:::

Download Connection is:: 9340 Kbps about 9.3 Mbps (tested with 12160 kB)

Download Speed is:: 1140 kB/s

Tested From:: https://testmy.net/ (Main)

Test Time:: 2008/02/03 - 11:51pm

Bottom Line:: 163X faster than 56K 1MB Download in 0.9 sec

Tested from a 12160 kB file and took 10.665 seconds to complete

Download Diagnosis:: Awesome! 20% + : 83.28 % faster than the average for host (rr.com)

D-Validation Link:: https://testmy.net/stats/id-78X9JI5NW

User Agent:: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.11) Gecko/20071127 Firefox/2.0.0.11 [!]

C:Documents and Settingspurewhitelight>ping testmy.net

Pinging testmy.net [74.52.182.125] with 32 bytes of data:

Reply from 74.52.182.125: bytes=32 time=49ms TTL=49

Reply from 74.52.182.125: bytes=32 time=66ms TTL=49

Reply from 74.52.182.125: bytes=32 time=53ms TTL=49

Reply from 74.52.182.125: bytes=32 time=52ms TTL=49

Ping statistics for 74.52.182.125:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 49ms, Maximum = 66ms, Average = 55ms

C:Documents and Settingspurewhitelight>ping -t -l 500 testmy.net

Pinging testmy.net [74.52.182.125] with 500 bytes of data:

Reply from 74.52.182.125: bytes=500 time=56ms TTL=49

Reply from 74.52.182.125: bytes=500 time=54ms TTL=49

Reply from 74.52.182.125: bytes=500 time=52ms TTL=49

Reply from 74.52.182.125: bytes=500 time=50ms TTL=49

Reply from 74.52.182.125: bytes=500 time=53ms TTL=49

Reply from 74.52.182.125: bytes=500 time=64ms TTL=49

Reply from 74.52.182.125: bytes=500 time=50ms TTL=49

Reply from 74.52.182.125: bytes=500 time=54ms TTL=49

Reply from 74.52.182.125: bytes=500 time=55ms TTL=49

Reply from 74.52.182.125: bytes=500 time=48ms TTL=49

Reply from 74.52.182.125: bytes=500 time=49ms TTL=49

Reply from 74.52.182.125: bytes=500 time=66ms TTL=49

Reply from 74.52.182.125: bytes=500 time=49ms TTL=49

Reply from 74.52.182.125: bytes=500 time=75ms TTL=49

Reply from 74.52.182.125: bytes=500 time=60ms TTL=49

Reply from 74.52.182.125: bytes=500 time=68ms TTL=49

Reply from 74.52.182.125: bytes=500 time=85ms TTL=49

Reply from 74.52.182.125: bytes=500 time=66ms TTL=49

Reply from 74.52.182.125: bytes=500 time=55ms TTL=49

Reply from 74.52.182.125: bytes=500 time=63ms TTL=49

Reply from 74.52.182.125: bytes=500 time=53ms TTL=49

Reply from 74.52.182.125: bytes=500 time=49ms TTL=49

Reply from 74.52.182.125: bytes=500 time=62ms TTL=49

Reply from 74.52.182.125: bytes=500 time=72ms TTL=49

Reply from 74.52.182.125: bytes=500 time=71ms TTL=49

Reply from 74.52.182.125: bytes=500 time=52ms TTL=49

Reply from 74.52.182.125: bytes=500 time=54ms TTL=49

Reply from 74.52.182.125: bytes=500 time=53ms TTL=49

Reply from 74.52.182.125: bytes=500 time=57ms TTL=49

Reply from 74.52.182.125: bytes=500 time=63ms TTL=49

Reply from 74.52.182.125: bytes=500 time=54ms TTL=49

Reply from 74.52.182.125: bytes=500 time=50ms TTL=49

Reply from 74.52.182.125: bytes=500 time=54ms TTL=49

Reply from 74.52.182.125: bytes=500 time=52ms TTL=49

Reply from 74.52.182.125: bytes=500 time=69ms TTL=49

Reply from 74.52.182.125: bytes=500 time=50ms TTL=49

Reply from 74.52.182.125: bytes=500 time=54ms TTL=49

Reply from 74.52.182.125: bytes=500 time=103ms TTL=49

Reply from 74.52.182.125: bytes=500 time=71ms TTL=49

Reply from 74.52.182.125: bytes=500 time=55ms TTL=49

Reply from 74.52.182.125: bytes=500 time=68ms TTL=49

Reply from 74.52.182.125: bytes=500 time=72ms TTL=49

Reply from 74.52.182.125: bytes=500 time=47ms TTL=49

Reply from 74.52.182.125: bytes=500 time=73ms TTL=49

Reply from 74.52.182.125: bytes=500 time=62ms TTL=49

Reply from 74.52.182.125: bytes=500 time=82ms TTL=49

Reply from 74.52.182.125: bytes=500 time=48ms TTL=49

Reply from 74.52.182.125: bytes=500 time=79ms TTL=49

Reply from 74.52.182.125: bytes=500 time=66ms TTL=49

Reply from 74.52.182.125: bytes=500 time=54ms TTL=49

Reply from 74.52.182.125: bytes=500 time=52ms TTL=49

Reply from 74.52.182.125: bytes=500 time=49ms TTL=49

Reply from 74.52.182.125: bytes=500 time=65ms TTL=49

Reply from 74.52.182.125: bytes=500 time=50ms TTL=49

Reply from 74.52.182.125: bytes=500 time=51ms TTL=49

Reply from 74.52.182.125: bytes=500 time=54ms TTL=49

Reply from 74.52.182.125: bytes=500 time=51ms TTL=49

Reply from 74.52.182.125: bytes=500 time=52ms TTL=49

Reply from 74.52.182.125: bytes=500 time=58ms TTL=49

Reply from 74.52.182.125: bytes=500 time=72ms TTL=49

Reply from 74.52.182.125: bytes=500 time=75ms TTL=49

Reply from 74.52.182.125: bytes=500 time=58ms TTL=49

Reply from 74.52.182.125: bytes=500 time=48ms TTL=49

Reply from 74.52.182.125: bytes=500 time=52ms TTL=49

Reply from 74.52.182.125: bytes=500 time=63ms TTL=49

Reply from 74.52.182.125: bytes=500 time=53ms TTL=49

Reply from 74.52.182.125: bytes=500 time=54ms TTL=49

Reply from 74.52.182.125: bytes=500 time=82ms TTL=49

Reply from 74.52.182.125: bytes=500 time=54ms TTL=49

Reply from 74.52.182.125: bytes=500 time=75ms TTL=49

Reply from 74.52.182.125: bytes=500 time=49ms TTL=49

Reply from 74.52.182.125: bytes=500 time=82ms TTL=49

Reply from 74.52.182.125: bytes=500 time=49ms TTL=49

Reply from 74.52.182.125: bytes=500 time=54ms TTL=49

Reply from 74.52.182.125: bytes=500 time=54ms TTL=49

Reply from 74.52.182.125: bytes=500 time=74ms TTL=49

Reply from 74.52.182.125: bytes=500 time=52ms TTL=49

Reply from 74.52.182.125: bytes=500 time=55ms TTL=49

Request timed out.

Reply from 74.52.182.125: bytes=500 time=52ms TTL=49

Reply from 74.52.182.125: bytes=500 time=65ms TTL=49

Reply from 74.52.182.125: bytes=500 time=52ms TTL=49

Reply from 74.52.182.125: bytes=500 time=59ms TTL=49

Reply from 74.52.182.125: bytes=500 time=54ms TTL=49

Reply from 74.52.182.125: bytes=500 time=61ms TTL=49

Reply from 74.52.182.125: bytes=500 time=53ms TTL=49

Reply from 74.52.182.125: bytes=500 time=55ms TTL=49

Reply from 74.52.182.125: bytes=500 time=55ms TTL=49

Reply from 74.52.182.125: bytes=500 time=49ms TTL=49

Reply from 74.52.182.125: bytes=500 time=52ms TTL=49

Reply from 74.52.182.125: bytes=500 time=54ms TTL=49

Reply from 74.52.182.125: bytes=500 time=61ms TTL=49

Reply from 74.52.182.125: bytes=500 time=63ms TTL=49

Reply from 74.52.182.125: bytes=500 time=63ms TTL=49

Reply from 74.52.182.125: bytes=500 time=54ms TTL=49

Ping statistics for 74.52.182.125:

    Packets: Sent = 95, Received = 94, Lost = 1 (1% loss),

Approximate round trip times in milli-seconds:

    Minimum = 47ms, Maximum = 103ms, Average = 59ms

Microsoft Windows XP [Version 5.1.2600]

© Copyright 1985-2001 Microsoft Corp.

C:Documents and Settingspurewhitelight>

C:Documents and Settingspurewhitelight>tracert yahoo.com

Tracing route to yahoo.com [66.94.234.13]

over a maximum of 30 hops:

  1    10 ms    12 ms    15 ms  cpe-76-91-192-1.socal.res.rr.com [76.91.192.1]

  2    11 ms    13 ms    11 ms  cpe-76-166-6-205.socal.res.rr.com [76.166.6.205]

  3    11 ms    19 ms    16 ms  tge9-3.bwlaca1-rtr2.socal.rr.com [76.166.1.6]

  4    12 ms    22 ms    24 ms  tge9-2.bwlaca1-rtr1.socal.rr.com [76.166.1.4]

  5    *      16 ms    15 ms  tge2-2-0.lsanca1-rtr1.socal.rr.com [66.75.161.20

1]

  6    19 ms    20 ms    31 ms  ae-3-0.cr0.lax00.tbone.rr.com [66.109.6.66]

  7    33 ms    25 ms    52 ms  66.109.6.6

  8    25 ms    25 ms    25 ms  ae-0-0.pr0.sjc20.tbone.rr.com [66.109.6.139]

  9    38 ms    28 ms    26 ms  66.109.9.177

10    28 ms    28 ms    26 ms  ge-4-0-0-p440.msr1.scd.yahoo.com [216.115.106.20

1]

11    28 ms    28 ms    34 ms  ten-2-3-bas2.scd.yahoo.com [66.218.82.223]

12    27 ms    28 ms    28 ms  w2.rc.vip.scd.yahoo.com [66.94.234.13]

Trace complete.

Microsoft Windows XP [Version 5.1.2600]

© Copyright 1985-2001 Microsoft Corp.

C:Documents and Settingspurewhitelight>

C:Documents and Settingspurewhitelight>tracert yahoo.com

Tracing route to yahoo.com [66.94.234.13]

over a maximum of 30 hops:

  1    10 ms    12 ms    15 ms  cpe-76-91-192-1.socal.res.rr.com [76.91.192.1]

  2    11 ms    13 ms    11 ms  cpe-76-166-6-205.socal.res.rr.com [76.166.6.205]

  3    11 ms    19 ms    16 ms  tge9-3.bwlaca1-rtr2.socal.rr.com [76.166.1.6]

  4    12 ms    22 ms    24 ms  tge9-2.bwlaca1-rtr1.socal.rr.com [76.166.1.4]

  5    *      16 ms    15 ms  tge2-2-0.lsanca1-rtr1.socal.rr.com [66.75.161.20

1]

  6    19 ms    20 ms    31 ms  ae-3-0.cr0.lax00.tbone.rr.com [66.109.6.66]

  7    33 ms    25 ms    52 ms  66.109.6.6

  8    25 ms    25 ms    25 ms  ae-0-0.pr0.sjc20.tbone.rr.com [66.109.6.139]

  9    38 ms    28 ms    26 ms  66.109.9.177

10    28 ms    28 ms    26 ms  ge-4-0-0-p440.msr1.scd.yahoo.com [216.115.106.20

1]

11    28 ms    28 ms    34 ms  ten-2-3-bas2.scd.yahoo.com [66.218.82.223]

12    27 ms    28 ms    28 ms  w2.rc.vip.scd.yahoo.com [66.94.234.13]

Trace complete.

C:Documents and Settingspurewhitelight>tracert testmy.net

Tracing route to testmy.net [74.52.182.125]

over a maximum of 30 hops:

  1    13 ms    17 ms    20 ms  cpe-76-91-192-1.socal.res.rr.com [76.91.192.1]

  2    21 ms    21 ms    11 ms  cpe-76-166-6-205.socal.res.rr.com [76.166.6.205]

  3    10 ms    13 ms    15 ms  tge9-3.bwlaca1-rtr2.socal.rr.com [76.166.1.6]

  4    13 ms    24 ms    12 ms  tge9-2.bwlaca1-rtr1.socal.rr.com [76.166.1.4]

  5    *      13 ms    17 ms  tge2-2-0.lsanca1-rtr1.socal.rr.com [66.75.161.201]

  6    16 ms    22 ms    18 ms  GIG2-0.TUSTCA1-RTR1.socal.rr.com [66.75.161.158]

  7    30 ms    30 ms    28 ms  ge-6-1-129.hsa1.Tustin1.Level3.net [4.79.140.37]

  8    20 ms    14 ms    19 ms  ae-11-11.car2.Tustin1.Level3.net [4.69.132.222]

  9    58 ms    55 ms    52 ms  ae-4-4.ebr1.Dallas1.Level3.net [4.69.132.226]

10    62 ms    72 ms    53 ms  ae-71-71.csw2.Dallas1.Level3.net [4.69.136.126]

11    47 ms    58 ms    54 ms  ae-24-79.car4.Dallas1.Level3.net [4.68.19.70]

12    53 ms    50 ms    61 ms  THE-PLANET.car4.Dallas1.Level3.net [4.71.122.2]

13    61 ms    52 ms    49 ms  te7-2.dsr02.dllstx3.theplanet.com [70.87.253.26]

14    47 ms    52 ms    66 ms  76.fd.5746.static.theplanet.com [70.87.253.118]

15    53 ms    53 ms    50 ms  po2.car03.dllstx6.theplanet.com [12.96.160.37]

16    50 ms    54 ms    50 ms  7d.b6.344a.static.theplanet.com [74.52.182.125]

Trace complete.

C:Documents and Settingspurewhitelight>pathping -p 200 66.75.161.201

Tracing route to tge2-2-0.lsanca1-rtr1.socal.rr.com [66.75.161.201]

over a maximum of 30 hops:

  0  purewhitelight [192.168.0.13]

  1  cpe-76-91-192-1.socal.res.rr.com [76.91.192.1]

  2  cpe-76-166-6-205.socal.res.rr.com [76.166.6.205]

  3  tge9-3.bwlaca1-rtr2.socal.rr.com [76.166.1.6]

  4  tge9-2.bwlaca1-rtr1.socal.rr.com [76.166.1.4]

  5  tge2-2-0.lsanca1-rtr1.socal.rr.com [66.75.161.201]

Computing statistics for 100 seconds...

            Source to Here  This Node/Link

Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address

  0                                          my computer [xxx.xxx.xxx.xxx]

                                0/ 100 =  0%  |

  1  12ms    0/ 100 =  0%    0/ 100 =  0%  cpe-76-91-192-1.socal.res.rr.com [76.91.192.1]

                                0/ 100 =  0%  |

  2  13ms    0/ 100 =  0%    0/ 100 =  0%  cpe-76-166-6-205.socal.res.rr.com [76.166.6.205]

                                0/ 100 =  0%  |

  3  13ms    0/ 100 =  0%    0/ 100 =  0%  tge9-3.bwlaca1-rtr2.socal.rr.com [76.166.1.6]

                                0/ 100 =  0%  |

  4  13ms    0/ 100 =  0%    0/ 100 =  0%  tge9-2.bwlaca1-rtr1.socal.rr.com [76.166.1.4]

                                0/ 100 =  0%  |

  5  15ms    0/ 100 =  0%    0/ 100 =  0%  tge2-2-0.lsanca1-rtr1.socal.rr.com [66.75.161.201]

Trace complete.

C:Documents and Settingspurewhitelight>pathping -p 200 testmy.net

Tracing route to testmy.net [74.52.182.125]

over a maximum of 30 hops:

  0  purewhitelight [192.168.0.13]

  1  cpe-76-91-192-1.socal.res.rr.com [76.91.192.1]

  2  cpe-76-166-6-205.socal.res.rr.com [76.166.6.205]

  3  tge9-3.bwlaca1-rtr2.socal.rr.com [76.166.1.6]

  4  tge9-2.bwlaca1-rtr1.socal.rr.com [76.166.1.4]

  5    *        *        *

Computing statistics for 100 seconds...

            Source to Here  This Node/Link

Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address

  0                                          my cmputer [xxx.xxx.xxx.xxx]

                                0/ 100 =  0%  |

  1  13ms    0/ 100 =  0%    0/ 100 =  0%  cpe-76-91-192-1.socal.res.rr.com [76.91.192.1]

                                0/ 100 =  0%  |

  2  14ms    0/ 100 =  0%    0/ 100 =  0%  cpe-76-166-6-205.socal.res.rr.com [76.166.6.205]

                                0/ 100 =  0%  |

  3  14ms    0/ 100 =  0%    0/ 100 =  0%  tge9-3.bwlaca1-rtr2.socal.rr.com [76.166.1.6]

                                0/ 100 =  0%  |

  4  13ms    0/ 100 =  0%    0/ 100 =  0%  tge9-2.bwlaca1-rtr1.socal.rr.com [76.166.1.4]

                              100/ 100 =100%  |

  5  ---    100/ 100 =100%    0/ 100 =  0%  timeout [0.0.0.0]

Trace complete.

C:Documents and Settingspurewhitelight>

Share this post


Link to post
Share on other sites

I have Vonage VOIP, and had the same issue's for some time. It had to do w/ a bad card in the local node.

In the mean time, check your upload speeds, VOIP depends on both up/down stream redundancy.  There should be settings  in the configuration of your VOIP , either in the router, or on there web based interface to control bandwidth, have you tried this?

If no luck, you could try setting a QOS in your router config, if the router you have ( not listed) allows for it.

I use a separate router for internal traffic , and set the VOIP router on a DMZ with mac filtering to allow for full bandwidth .

I would be looking at my upload speeds for the issue.

Welcome to the testmy.net forum.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this  

×
×
  • Create New...