Tim
What about the confirmation tone (Thank You) for the * codes working on 'sip7' and getting a "busy" confirmation tone on 'sip' ?
Printable View
Tim
What about the confirmation tone (Thank You) for the * codes working on 'sip7' and getting a "busy" confirmation tone on 'sip' ?
Open a ticket on it with info on how to reproduce and devs will look into it. Could be a bug.Quote:
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?
Quote:
Originally Posted by chevyman
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:C:\>tracert sip7.voipwelcome.com
Tracing route to sip7.voipwelcome.com [72.52.231.45]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms [172.31.125.1]
2 9 ms 10 ms 11 ms 10.28.0.1
3 13 ms 11 ms 11 ms static-24-113-126-254.wavecable.com [24.113.126.254]
4 13 ms 11 ms 10 ms wave-gw.ae0.sea-bdr0.noanet.net [64.146.252.249]
5 12 ms 13 ms 13 ms xe-0-0-0.3006.oly-cor1.noanet.net [64.184.178.22]
6 17 ms 17 ms 17 ms xe-0-3-1.3026.ptl-bdr0.noanet.net [64.184.178.89]
7 16 ms 17 ms 17 ms te3-3.ccr01.pdx01.atlas.cogentco.com [38.104.104.181]
8 17 ms 18 ms 16 ms te0-0-2-2.rcr11.pdx02.atlas.cogentco.com [154.54.0.86]
9 20 ms 21 ms 21 ms te0-3-0-2.ccr21.sea01.atlas.cogentco.com [154.54.40.118]
10 21 ms 20 ms 22 ms be2083.ccr21.sea02.atlas.cogentco.com [154.54.0.250]
11 48 ms 42 ms 41 ms be2085.ccr21.slc01.atlas.cogentco.com [154.54.2.198]
12 52 ms 51 ms 52 ms be2126.ccr21.den01.atlas.cogentco.com [154.54.25.65]
13 64 ms 63 ms 64 ms be2128.ccr21.mci01.atlas.cogentco.com [154.54.25.174]
14 77 ms 76 ms 76 ms be2156.ccr41.ord01.atlas.cogentco.com [154.54.6.86]
15 82 ms 76 ms 76 ms be2005.ccr21.ord03.atlas.cogentco.com [66.28.4.74]
16 77 ms 77 ms 77 ms be2409.rcr11.b002281-5.ord03.atlas.cogentco.com[154.54.29.66]
17 101 ms 101 ms 94 ms cogent-chi.liquidweb.com [38.104.103.166]
18 72 ms 71 ms 71 ms lw-dc3-core2-te8-16.rtr.liquidweb.com [209.59.157.229]
19 74 ms 74 ms 73 ms lw-dc3-dist16-po6.rtr.liquidweb.com [69.167.128.95]
20 74 ms 73 ms 73 ms 72.52.231.45
Trace complete.
Same here. SIP7 doesn't look as good "on paper", but seems to work better in practice.Quote:
Originally Posted by chpalmer
But now that the TCP flooding has been cleaned up, SIP in Texas seems to work pretty well too.
Yes, we're planning to add a west coast POP soon.Quote:
Originally Posted by chevyman
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.
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
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 :)Quote:
Originally Posted by VOIPoTim
For those of you wanting a west coast node, how is your connection to this IP? 198.55.111.5Quote:
Originally Posted by chevyman
It's is a facility we're considering.
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
How about 50.28.98.7? That's another facility we're considering for west coast. It's in Phoenix vs LA.
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
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]
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]
Tim - for me the first one is definitely better and I think it would be a better choice for West Coast folks:Quote:
Originally Posted by VOIPoTim
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
TimQuote:
Originally Posted by VOIPoTim
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]