Busy Signal Outgoing Calls

**GreenLantern** · 01-28-2015 12:21 PM

Originally Posted by chpalmer

I too get better traceroute results to Texas but find sip7 works very well from Bremerton. Who is your ISP chevyman?

74ms but my jitter is relatively low.

[/code]

Same here. SIP7 doesn't look as good "on paper", but seems to work better in practice.

But now that the TCP flooding has been cleaned up, SIP in Texas seems to work pretty well too.

**VOIPoTim** · 01-28-2015 04:24 PM

Originally Posted by chevyman

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.

**chevyman** · 02-05-2015 05:25 AM

Originally Posted by VOIPoTim

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

**VOIPoTim** · 02-05-2015 01:34 PM

Originally Posted by chevyman

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.

**chevyman** · 02-07-2015 07:48 PM

Originally Posted by VOIPoTim

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]

**chevyman** · 02-05-2015 05:08 AM

I'm using Centurylink (old Qwest), i think they are getting cheap. A while back i was having problems and found they had started to use Comcast for a while and now it seems they are using some (zip.zayo.com) whoever they are. here is a trace back on 9-2013.

http://forums.voipo.com/showthread.p...8805#post58805

It was 71 ms to texas now i'm getting 125 ms

**GreenLantern** · 02-05-2015 09:04 PM

I'm not west coast, but here's some data. I'm using Comcast in Texas.

west coast server

198.55.111.5
53ms avg
14 hops

here's sip7

72.52.231.45
58ms avg
14 hops

and dallas

67.228.182.2
18ms avg
10 hops

**VOIPoTim** · 02-05-2015 09:22 PM

How about 50.28.98.7? That's another facility we're considering for west coast. It's in Phoenix vs LA.

**racerdude** · 02-07-2015 02:55 PM

Originally Posted by VOIPoTim

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

**GreenLantern** · 02-06-2015 09:29 AM

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