Chicago Testing

[VOIPoTim]

Anyone interested in testing new Chicago SIP servers?

We're looking for a few volunteers to be switched over now (and use their phones normally) to make sure no one discovers issues before we integrate it into our dynamic provisioning/server distribution next week.

We don't expect any issues and haven't had any reported at all, but there's always a possibility we missed something since it's new.

If so, PM me your VOIPo number and I can get you moved over.

For those interested in ping times/traceroutes or those with grandfathered accounts that have full SIP access, you can test using sip-chicago.voipwelcome.com.

[usa2k]

I've been on Chicago a couple days and its been business as normal :)

I am impressed that VOIPo keeps on adding things like this. The three geographical regions seemed like a very robust setup to me as an outside observer. VOIPo keeps growing and adding to its portfolio as a first class business.

[tylerscell1]

I can tim if you want. You know how to contact me...

Tyler

[MisterEd]

Getting much better pings to EAST 10-15ms vs 33-37 to CHICAGO. (250 miles to DC vs 900 miles to Chi-town). Tracert is much better to DC as well.

C:\Users\Ed>tracert sip-chicago.voipwelcome.com
tracing route to sip-chicago.voipwelcome.com [209.212.145.109]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms unknown [192.168.1.1]
2 1 ms 2 ms 1 ms L100.NWRKNJ-VFTTP-52.verizon-gni.net [71.251.210.1]
3 3 ms 2 ms 2 ms 14-0-0-652.NWRKNJ-LCR-06.verizon-gni.net [130.81.60.30]
4 3 ms 3 ms 3 ms so-6-2-0-0.NWRK-BB-RTR2.verizon-gni.net [130.81.28.150]
5 3 ms 4 ms 3 ms 0.so-7-0-0.XL4.EWR6.ALTER.NET [152.63.20.13]
6 4 ms 4 ms 4 ms 0.so-1-0-3.XL4.NYC4.ALTER.NET [152.63.17.110]
7 6 ms 7 ms 7 ms GigabitEthernet5-0-0.GW1.NYC4.ALTER.NET [152.63.20.101]
8 4 ms 4 ms 4 ms teliasonera-gw.customer.alter.net [157.130.60.14]
9 4 ms 4 ms 4 ms nyk-bb2-link.telia.net [80.91.253.105]
10 29 ms 28 ms 29 ms chi-bb1-link.telia.net [80.91.248.196]
11 32 ms 30 ms 31 ms ae11.er1.Chi2.Servernap.net [66.252.3.137]
12 33 ms 34 ms 33 ms te9-4.csr2.Chi3.Servernap.net [66.252.0.69]
13 33 ms 33 ms 33 ms p106.ddr3.Chi3.Servernap.net [66.252.0.150]
14 32 ms 34 ms 32 ms 209.212.145.109



c:\Users\Ed>tracert sip-east01.voipwelcome.com
tracing route to sip-east01.voipwelcome.com [208.43.68.151]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms unknown [192.168.1.1]
2 1 ms 3 ms 1 ms L100.NWRKNJ-VFTTP-52.verizon-gni.net [71.251.210.1]
3 2 ms 2 ms 2 ms 14-0-0-652.NWRKNJ-LCR-06.verizon-gni.net [130.81.60.30]
4 3 ms 3 ms 3 ms so-6-2-0-0.NWRK-BB-RTR2.verizon-gni.net [130.81.28.150]
5 3 ms 3 ms 3 ms 0.so-7-0-0.XL4.EWR6.ALTER.NET [152.63.20.13]
6 15 ms 17 ms 14 ms 0.so-6-0-0.XL4.IAD8.ALTER.NET [152.63.0.130]
7 16 ms 16 ms 14 ms TenGigE0-7-2-0.GW1.IAD8.ALTER.NET [152.63.35.153]
8 16 ms 16 ms 16 ms internap-gw.customer.alter.net [152.179.50.54]
9 21 ms 24 ms 26 ms border1.te7-1-bbnet1.wdc008.pnap.net [216.52.127.36]
10 15 ms 15 ms 14 ms te1-1.cer01.wdc01.washingtondc-datacenter.com [66.151.100.66]
11 14 ms 15 ms 14 ms po1.fcr01.wdc01.washingtondc-datacenter.com [208.43.118.134]
12 15 ms 15 ms 12 ms sip-east01.voipwelcome.com [208.43.68.151]

[voipinit]

Trace times look good. Switched over and working fine.

FYI - Under Features --> Devices - the connected to server is blank for Chicago, just in case you weren't aware.

[usa2k]

FYI - Under Features --> Devices - the connected to server is blank for Chicago, just in case you weren't aware.I noticed that too.

Wife had a 17 minute call from FL on the upgraded 2nd line yesterday, and never noticed any difference.

[VOIPoTim]

I noticed that too.

Wife had a 17 minute call from FL on the upgraded 2nd line yesterday, and never noticed any difference.

The little tool that shows where connected just looks at the IP you're connected to and matches it up with a name. It's very low-tech. Have not added Chicago to it.

[scott2020]

What about BYOD people? Is it OK to point to this?

[VOIPoTim]

What about BYOD people? Is it OK to point to this?

If you are grandfathered and using the main SIP credentials, yes.

[scott2020]

Oops! Sorry I missed that on your first post. It seems all of my Internet traffic goes through Chicago so pings/traces are good for me.

[scott2020]

So far Chicago has been great. Very low latency and short hops at least for me. The Canal St. facility is excellent, if that is where the new servers are anyway.

[tylerscell1]

Im not sure if you ever switched me over tim but things seem to be fine.

[uhf]

I haven't noticed any issues here either.

[voipinit]

Maybe it's because the number of people are on it, but throughput has been exceptional.

[jlachowin]

Tim, check your PM's. I want in!

[VOIPoTim]

Tim, check your PM's. I want in!

OK, I'll get you added and anyone else that PMed.

We're finished testing now and don't need additional volunteers at this time.

In the next few days, we'll start testing some other new cities that have been added and I'll post again at that time.

We've been testing connectivity to a lot of new cities and we'll be determining which ones to add over the next few weeks for the final network expansion before reseller soft launch.

[burris]

Although the service has always been good for me, since I moved over to Chicago last week, unless it's my imagination, I think the post dial delay is faster for me. Hard to tell about anything else since everything is quite good..

[VOIPoTim]

We will be automatically moving anyone on Chicago to DC later this evening for tonight so we can tweak a few things on it.

If you're on it, you don't need to do anything for this to happen.

[burris]

We will be automatically moving anyone on Chicago to DC later this evening for tonight so we can tweak a few things on it.

If you're on it, you don't need to do anything for this to happen.

Even if we did it ourselves and are not provisioned at the moment?

[VOIPoTim]

Even if we did it ourselves and are not provisioned at the moment?

Yeah, the DNS will automatically update for the hostname too.


BTW looks like I edited your post with reply instead of replying. Fixing.

[voipinit]

Chicago stopped registering, back on east. Appears chicago is pointing to east as well.

[burris]

I think Tim indicated earlier that he was switching those who are on Chicago to another server.

[voipinit]

Yeah, I had to change servers in my ATA, Chicago did not re-route for me, just failed to register.

[usa2k]

I think mine is still OK on Chicago today. I know it is blank in devices under "Connected To". That has been true for Chicago.

[voipinit]

It's registering with Chicago again. Although if you do a tracert you will see it route to east.

[VOIPoTim]

Yeah, I had to change servers in my ATA, Chicago did not re-route for me, just failed to register.

Do you have provisioning enabled?

[uhf]

Tim,

The additional geographic servers are great, but what about the issues when Softlayer in Dallas goes down? Is there a way to add some redundancy to prevent that from being an issue? In theory, it should never go down, but...

[VOIPoTim]

Tim,

The additional geographic servers are great, but what about the issues when Softlayer in Dallas goes down? Is there a way to add some redundancy to prevent that from being an issue? In theory, it should never go down, but...

We just signed a new deal this week for upcoming network expansion which will help with that.

[uhf]

Great news, Tim! Thanks for the update.

[VOIPoTim]

We just signed a new deal this week for upcoming network expansion which will help with that.

The plan is to integrate Peer1 for full failover outside of Softlayer.

They have some pretty well-known clients such as Vonage, PlentyofFish, etc. http://www.peer1.com/whypeer1/customer_stories_vonage.php