Results 1 to 10 of 56

Thread: Busy Signal Outgoing Calls

Hybrid View

Previous Post Previous Post   Next Post Next Post
  1. #1
    Join Date
    Feb 2007
    Location
    Irvine CA
    Posts
    1,542,128,044

    Default Re: Busy Signal Outgoing Calls

    Quote Originally Posted by chevyman View Post
    Tim

    Sip7.voipwelcome.com is unstable, sometimes i'll make a calls and the call don't go through, then it looses registration and I have to switch back to sip.voipwelcome.com.

    When i do a trace to sip7.voipwelcome.com its not very good to liquidweb.com from here in the Seattle area, its a lot better to softlayer.com on sip.voipwelcome.com.

    Is there any chance Voipo going to have a sip in the Northwest?
    Yes, we're planning to add a west coast POP soon.

    We still feel Dallas is the best for 99% of customers and the connectivity there is very robust especially since Softlayer is now owned by IBM, but we understand that there are a handful of people that may have a better connection to a different DC so that's where sip7 comes in and we're going to add a west coast option soon.

  2. #2
    Join Date
    Jul 2010
    Posts
    180

    Default Re: Busy Signal Outgoing Calls

    Quote Originally Posted by VOIPoTim View Post
    Yes, we're planning to add a west coast POP soon.

    We still feel Dallas is the best for 99% of customers and the connectivity there is very robust especially since Softlayer is now owned by IBM, but we understand that there are a handful of people that may have a better connection to a different DC so that's where sip7 comes in and we're going to add a west coast option soon.
    when i do a voip quality test with megapath's test, i get good results with San Francisco, so that would be a good west coast option, other than Seattle

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

    Default Re: Busy Signal Outgoing Calls

    Quote Originally Posted by chevyman View Post
    when i do a voip quality test with megapath's test, i get good results with San Francisco, so that would be a good west coast option, other than Seattle
    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.
    Timothy Dick
    Founder/CEO
    VOIPo.com

    Interact with VOIPo: Twitter, Facebook

  4. #4
    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
  •