BYOD Users: Testing Michigan Datacenter
Hey Guys,
We're doing some casual testing of a few new datacenters that we are considering adding into the mix so that there is an alternative option outside of our primary datacenter available for you guys to use if you prefer it for some reason.
Right now, we're testing a facility in Michigan. If you'd like to try it out, you can connect to sip7.voipwelcome.com instead of sip.voipwelcome.com. All BYOD users can register to it (and all reseller/resold accounts).
Please let me know what your connectivity is like to this facility and if you feel it's a better or worse connection for you. Traceroutes would be very helpful with feedback.
Our Dallas datacenter is owned by IBM now and is rock solid with excellent connectivity for most people, but one big difference with it and some of the others we're evaluating is that it has a lot of direct ISP peering in its routing so if a user is using a major ISP like Cox or Comcast the traffic is likely being routed directly to it. Other facilities we're looking at adding as an alternative don't have as much peering so they may have better routing for customers not on major ISPs or for certain geographical areas.
Current Facility: Softlayer - http://www.softlayer.com/about/network/carriers
sip.voipwelcome.com
Possible Addition/Alternative: Liquidweb - http://www.liquidweb.com/datacenter/network.html
sip7.voipwelcome.com
Again, this is just something we're testing. We are extremely happy with our current facility but have a few datacenters we're considering adding to the mix and this one in Michigan is currently our top choice so we'd like to get some testing. We have one reseller that seems to have a poor connection to our Dallas facility for some reason so we're re-exploring adding some diversity to the SIP server mix.
If anyone wants to test, please let me know how your connection (and post traceroutes if possible to compare). We'd like to get as much "real-world" data as possible.
Thanks!
1 Attachment(s)
Re: BYOD Users: Testing Michigan Datacenter
I get 17 hops to sip. and 15 hops to sip7.
I have attached a screenshot of both trace routes.
Re: BYOD Users: Testing Michigan Datacenter
Sorry- missed the requests for tracerts... :)
Code:
1 10.28.0.1 (10.28.0.1) 8.173 ms 12.951 ms 7.981 ms
2 static-24-113-126-57.wavecable.com (24.113.126.57) 8.178 ms 11.664 ms 4.985 ms
3 wave-gw.ae0.sea-bdr1.noanet.net (64.146.252.253) 6.987 ms 4.977 ms 5.885 ms
4 ae0-124.sea23.ip4.tinet.net (216.221.158.97) 26.355 ms 8.772 ms 4.587 ms
5 as3356.sea21.ip4.tinet.net (199.229.231.186) 15.371 ms 25.644 ms 10.279 ms
6 ae-32-52.ebr2.Seattle1.Level3.net (4.69.147.182) 58.007 ms 55.899 ms 56.144 ms
7 ae-2-2.ebr2.Denver1.Level3.net (4.69.132.54) 56.766 ms 56.788 ms 57.805 ms
8 ae-3-3.ebr1.Chicago2.Level3.net (4.69.132.62) 56.507 ms 60.393 ms 60.003 ms
9 ae-102-3502.edge2.Chicago2.Level3.net (4.69.158.5) 59.302 ms
ae-101-3501.edge2.Chicago2.Level3.net (4.69.158.1) 56.298 ms
ae-104-3504.edge2.Chicago2.Level3.net (4.69.158.13) 55.602 ms
10 CWIE-LLC.edge2.Chicago2.Level3.net (4.59.29.82) 66.380 ms 66.483 ms 66.393 ms
11 lw-core4-te91.rtr.liquidweb.com (209.59.157.206) 70.288 ms 73.669 ms 69.387 ms
12 lw-dc3-dist15.rtr.liquidweb.com (69.167.128.201) 71.687 ms 107.121 ms 74.780 ms
13 72.52.231.45 (72.52.231.45) 71.485 ms 81.453 ms 71.487 ms
Re: BYOD Users: Testing Michigan Datacenter
It appears to me from my firewall logs that sip7 is also handling the audio traffic... True in all cases or just some? Just trying to tighten my firewall rules up here.
Re: BYOD Users: Testing Michigan Datacenter
Moved to a new home office this morning—I now have Comcast and had CenturyLink prior—and I have been having issues registering so I figured I’d come over to the forums to see if there were other similar reports. Not seeing any and not being certain if my new Internet connection is to blame, I came across this thread and figured I’d give sip7 a try—and I have had zero registration issues since using it. While audio latency seems to be a bit more pronounced than sip.voipwelcome.com, my registration with sip7 appears to be solid.
>tracert sip.voipwelcome.com
Tracing route to sip.voipwelcome.com [67.228.182.2]
over a maximum of 30 hops:
1 3 ms 3 ms 3 ms 10.0.0.1
2 34 ms 30 ms 29 ms 50.155.214.1
3 29 ms 13 ms 15 ms te-7-4-ur02.englewood.co.denver.comcast.net [162.151.15.101]
4 13 ms 18 ms 18 ms te-0-0-0-4-ar02.aurora.co.denver.comcast.net [68.86.103.45]
5 19 ms 46 ms 15 ms he-3-10-0-0-cr01.denver.co.ibone.comcast.net [68.86.92.25]
6 18 ms 17 ms 16 ms xe-0-0-0.bbr01.cf01.den01.networklayer.com [75.149.228.102]
7 34 ms 29 ms 28 ms ae12.bbr02.eq01.dal03.networklayer.com [173.192.18.138]
8 29 ms 28 ms 32 ms ae1.dar02.sr01.dal01.networklayer.com [173.192.18.213]
9 282 ms 38 ms 32 ms po2.fcr04.sr05.dal01.networklayer.com [66.228.118.218]
10 30 ms 44 ms 62 ms 67.228.182.2-static.reverse.softlayer.com [67.228.182.2]
Trace complete.
>tracert sip7.voipwelcome.com
Tracing route to sip7.voipwelcome.com [72.52.231.45]
over a maximum of 30 hops:
1 3 ms 3 ms 3 ms 10.0.0.1
2 190 ms 28 ms 29 ms 50.155.214.1
3 18 ms 46 ms 13 ms te-7-4-ur02.englewood.co.denver.comcast.net [162.151.15.101]
4 19 ms 15 ms 16 ms te-0-2-0-6-ar02.aurora.co.denver.comcast.net [68.86.179.189]
5 87 ms 15 ms 18 ms he-3-10-0-0-cr01.denver.co.ibone.comcast.net [68.86.92.25]
6 340 ms 39 ms 39 ms he-5-11-0-0-cr01.350ecermak.il.ibone.comcast.net [68.86.86.185]
7 97 ms 37 ms 131 ms be-16-pe03.350ecermak.il.ibone.comcast.net [68.86.82.218]
8 108 ms 40 ms 37 ms 66.208.216.86
9 45 ms 44 ms 44 ms lw-dc2-core6-te9-2.rtr.liquidweb.com [209.59.157.226]
10 47 ms 63 ms 49 ms lw-dc3-dist15.rtr.liquidweb.com [69.167.128.205]
11 43 ms 44 ms 45 ms 72.52.231.45
Trace complete.
Re: BYOD Users: Testing Michigan Datacenter
I can confirm what Bink experienced. I had to move multiple accounts in several different cities over to SIP7.
Slightly higher ping times and more hops, but much more reliable connections.
All of my locations using Comcast in particular had to be moved to SIP7.
Your mileage may vary, but SIP7 seems more stable.
Re: BYOD Users: Testing Michigan Datacenter
I agree. sip.voipwelcome.com has been acting real flakey over the past couple of weeks (calls going to failover when registered, etc.). The reliability of this SIP server at Dallas compared to sip-central01 is definitely noticeable.
Lots of strange things happening of late...and it reminds me of the same issues experienced in this thread:
http://forums.voipo.com/showthread.p...oipwelcome.com
I had my father (located in Texas) who is on BYOD switch over to sip7 and the problems have simply went away.....
Re: BYOD Users: Testing Michigan Datacenter
Quote:
Originally Posted by
tritch
I agree. sip.voipwelcome.com has been acting real flakey over the past couple of weeks (calls going to failover when registered, etc.). The reliability of this SIP server at Dallas compared to sip-central01 is definitely noticeable.
Lots of strange things happening of late...and it reminds me of the same issues experienced in this thread:
http://forums.voipo.com/showthread.p...oipwelcome.com
I had my father (located in Texas) who is on BYOD switch over to sip7 and the problems have simply went away.....
We haven't noticed anything out of the ordinary, but I know some users have reported sip7 works better for them. If we find anything we'll address it, but so far it just seems like some people have better connectivity to sip7 and some better to sip.
Re: BYOD Users: Testing Michigan Datacenter
Tim - would love to see a new server on the West Coast, used to use sip-west01 before it was taken down. Any plans to setup one on the left coast?
Re: BYOD Users: Testing Michigan Datacenter
Quote:
Originally Posted by
racerdude
Tim - would love to see a new server on the West Coast, used to use sip-west01 before it was taken down. Any plans to setup one on the left coast?
I agree with racer... would love to see North, South, East and West. That should provide options to get around quirky local ISP issues, and provide good performance to more users.