Page 6 of 6 FirstFirst ... 456
Results 51 to 56 of 56

Thread: Busy Signal Outgoing Calls

  1. #51
    Join Date
    Feb 2007
    Location
    Irvine CA
    Posts
    1,542,128,044

    Default Re: Busy Signal Outgoing Calls

    How about 50.28.98.7? That's another facility we're considering for west coast. It's in Phoenix vs LA.
    Timothy Dick
    Founder/CEO
    VOIPo.com

    Interact with VOIPo: Twitter, Facebook

  2. #52
    Join Date
    Jul 2010
    Posts
    369

    Default Re: Busy Signal Outgoing Calls

    from Comcast, Houston, TX

    50.28.98.7
    51ms avg
    11 hops


    for any resellers that may not know how to get these numbers... open a command prompt in windows, then enter the following commands.

    (if you are on a Mac, open terminal instead, and use "traceroute" instead of "tracert")

    ping 50.28.98.7
    tracert 50.28.98.7

    ping 198.55.111.5
    tracert 198.55.111.5

    ping 72.52.231.45
    tracert 72.52.231.45

    ping 67.228.182.2
    tracert 67.228.182.2

  3. #53
    Join Date
    Feb 2007
    Location
    Kitsap County, WA.
    Posts
    734

    Default Re: Busy Signal Outgoing Calls

    From around Seattle

    Trace 198.55.111.5
    10 37 ms 37 ms 37 ms colo-lax6.as29761.net [96.44.180.34]
    11 36 ms 38 ms 37 ms repos.lax-noc.com [198.55.111.5]


    Trace 50.28.98.7

    15 64 ms 65 ms 65 ms 154.24.18.226
    16 103 ms 64 ms 63 ms cogent-phx.liquidweb.com [38.122.88.42]
    17 64 ms 65 ms 64 ms lw-dc4-dist2-po1.rtr.liquidweb.com [50.28.96.9]
    18 64 ms 64 ms 63 ms network-phx.noc.liquidweb.com [50.28.98.7]
    I Void Warranties.

  4. #54
    Join Date
    Feb 2007
    Location
    Kitsap County, WA.
    Posts
    734

    Default Re: Busy Signal Outgoing Calls

    Ill throw one in there for consideration

    Trace speedtest.sjc01.softlayer.com

    8 29 ms 29 ms 29 ms ae5.dar01.sr01.sjc01.networklayer.com [173.192.18.249]
    9 29 ms 29 ms 28 ms po1.fcr01.sr01.sjc01.networklayer.com [50.23.118.131]
    10 40 ms 29 ms 29 ms speedtest.sjc01.softlayer.com [50.23.64.58]
    I Void Warranties.

  5. #55
    Join Date
    Dec 2010
    Posts
    28

    Default Re: Busy Signal Outgoing Calls

    Quote Originally Posted by VOIPoTim View Post
    How about 50.28.98.7? That's another facility we're considering for west coast. It's in Phoenix vs LA.
    Tim - for me the first one is definitely better and I think it would be a better choice for West Coast folks:


    WinMTR to 198.55.111.5:

    |------------------------------------------------------------------------------------------|
    | WinMTR statistics |
    | Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
    |------------------------------------------------|------|------|------|------|------|------|
    | Router - 0 | 86 | 86 | 0 | 0 | 35 | 13 |
    | cpe-172-251-32-1.socal.res.rr.com - 0 | 86 | 86 | 7 | 14 | 231 | 17 |
    | tge0-9-0-16.simicacd01h.socal.rr.com - 0 | 86 | 86 | 8 | 12 | 48 | 11 |
    | agg23.vnnycajz01r.socal.rr.com - 0 | 86 | 86 | 11 | 15 | 53 | 19 |
    | agg29.lsancarc01r.socal.rr.com - 0 | 86 | 86 | 10 | 15 | 52 | 19 |
    |bu-ether36.lsancarc0yw-bcr00.tbone.rr.com - 2 | 83 | 82 | 10 | 20 | 478 | 12 |
    |bu-ether11.tustca4200w-bcr00.tbone.rr.com - 0 | 86 | 86 | 15 | 20 | 56 | 18 |
    | 0.ae3.pr1.lax10.tbone.rr.com - 0 | 86 | 86 | 13 | 17 | 59 | 14 |
    | 66.109.7.38 - 0 | 86 | 86 | 13 | 18 | 53 | 20 |
    |64.124.12.126.IPYX-100216-005-ZYO.above.net - 0 | 86 | 86 | 11 | 15 | 52 | 18 |
    | colo-lax6.as29761.net - 0 | 86 | 86 | 13 | 18 | 86 | 19 |
    | repos.lax-noc.com - 0 | 86 | 86 | 12 | 15 | 51 | 16 |
    |________________________________________________| ______|______|______|______|______|______|
    WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider


    WinMTR to 50.28.98.7
    |------------------------------------------------------------------------------------------|
    | WinMTR statistics |
    | Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
    |------------------------------------------------|------|------|------|------|------|------|
    | Router - 0 | 51 | 51 | 0 | 0 | 0 | 0 |
    | cpe-172-251-32-1.socal.res.rr.com - 0 | 51 | 51 | 8 | 11 | 15 | 12 |
    | tge0-9-0-16.simicacd01h.socal.rr.com - 0 | 51 | 51 | 9 | 12 | 16 | 11 |
    | agg23.vnnycajz01r.socal.rr.com - 0 | 51 | 51 | 9 | 13 | 24 | 17 |
    | agg29.lsancarc01r.socal.rr.com - 0 | 51 | 51 | 11 | 14 | 20 | 14 |
    |bu-ether26.lsancarc0yw-bcr00.tbone.rr.com - 0 | 51 | 51 | 13 | 15 | 21 | 18 |
    | 0.ae1.pr0.lax00.tbone.rr.com - 0 | 51 | 51 | 40 | 49 | 132 | 40 |
    | 66.109.9.122 - 3 | 47 | 46 | 10 | 15 | 78 | 11 |
    | ae-1-4.bar2.Phoenix1.Level3.net - 0 | 51 | 51 | 20 | 30 | 82 | 25 |
    | ae-1-4.bar2.Phoenix1.Level3.net - 0 | 51 | 51 | 20 | 29 | 81 | 20 |
    | LIQUID-WEB.bar2.Phoenix1.Level3.net - 0 | 51 | 51 | 22 | 26 | 69 | 25 |
    | lw-dc4-dist1-po2.rtr.liquidweb.com - 0 | 51 | 51 | 22 | 24 | 37 | 24 |
    | network-phx.noc.liquidweb.com - 0 | 51 | 51 | 24 | 25 | 37 | 25 |
    |________________________________________________| ______|______|______|______|______|______|
    WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

  6. #56
    Join Date
    Jul 2010
    Posts
    180

    Default Re: Busy Signal Outgoing Calls

    Quote Originally Posted by VOIPoTim View Post
    For those of you wanting a west coast node, how is your connection to this IP? 198.55.111.5

    It's is a facility we're considering.
    Tim

    LA is better, but PHX is not good, looks like anything going to 'Liquidweb' has poor routing, or maybe its 'Level3' that's the problem.
    here is traces and pings:

    Pinging 198.55.111.5 with 32 bytes of data:
    Reply from 198.55.111.5: bytes=32 time=72ms TTL=57
    Reply from 198.55.111.5: bytes=32 time=70ms TTL=57
    Reply from 198.55.111.5: bytes=32 time=70ms TTL=57
    Reply from 198.55.111.5: bytes=32 time=74ms TTL=57

    Ping statistics for 198.55.111.5:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 70ms, Maximum = 74ms, Average = 71ms

    Tracing route to repos.lax-noc.com [198.55.111.5]
    over a maximum of 30 hops:

    1 <1 ms <1 ms <1 ms 192.168.0.1
    2 42 ms 44 ms 42 ms 63.231.10.248
    3 44 ms 43 ms 46 ms tukw-agw1.inet.qwest.net [71.217.185.185]
    4 44 ms 44 ms 48 ms sea-brdr-02.inet.qwest.net [67.14.41.18]
    5 74 ms 73 ms 69 ms ae-20.r04.sttlwa01.us.bb.gin.ntt.net [129.250.9.133]
    6 71 ms 72 ms 73 ms ae-6.r20.sttlwa01.us.bb.gin.ntt.net [129.250.5.42]
    7 68 ms 70 ms 68 ms ae-3.r23.snjsca04.us.bb.gin.ntt.net [129.250.3.124]
    8 67 ms 64 ms 65 ms ae-0.r22.snjsca04.us.bb.gin.ntt.net [129.250.2.182]
    9 73 ms 80 ms 73 ms ae-7.r21.lsanca03.us.bb.gin.ntt.net [129.250.4.151]
    10 69 ms 73 ms 70 ms ae-2.r04.lsanca03.us.bb.gin.ntt.net [129.250.5.70]
    11 73 ms 71 ms 72 ms xe-0-6-0-4.r04.lsanca03.us.ce.gin.ntt.net [129.250.201.50]
    12 71 ms 68 ms 70 ms colo-lax6.as29761.net [96.44.180.102]
    13 72 ms 70 ms 70 ms repos.lax-noc.com [198.55.111.5]



    Pinging 50.28.98.7 with 32 bytes of data:
    Reply from 50.28.98.7: bytes=32 time=97ms TTL=53
    Reply from 50.28.98.7: bytes=32 time=101ms TTL=53
    Reply from 50.28.98.7: bytes=32 time=95ms TTL=53
    Reply from 50.28.98.7: bytes=32 time=97ms TTL=53

    Ping statistics for 50.28.98.7:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 95ms, Maximum = 101ms, Average = 97ms


    Tracing route to network-phx.noc.liquidweb.com [50.28.98.7]
    over a maximum of 30 hops:

    1 <1 ms 1 ms <1 ms 192.168.0.1
    2 45 ms 47 ms 46 ms 63.231.10.248
    3 41 ms 46 ms 42 ms tukw-agw1.inet.qwest.net [71.217.185.185]
    4 * * * Request timed out.
    5 46 ms 44 ms 48 ms ae14.edge2.Seattle1.Level3.net [4.68.62.189]
    6 93 ms 93 ms 101 ms ae-0-11.bar2.Phoenix1.Level3.net [4.69.148.114]
    7 94 ms 91 ms 91 ms LIQUID-WEB.bar2.Phoenix1.Level3.net [4.28.83.26]
    8 94 ms 97 ms 97 ms lw-dc4-dist1-po2.rtr.liquidweb.com [50.28.96.11]
    9 97 ms 96 ms 95 ms network-phx.noc.liquidweb.com [50.28.98.7]

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •