 espaethDigital PlumberPremium,MVM
join:2001-04-21
Minneapolis, MN
kudos:2
 ·Vitelity VOIP
1 edit | reply to Davesnothere
Re: Where are the SERVERS ? - Summary Vitelity -- multiple facilities in the Denver area, primary facility in Englewood is owned by the company, has direct carrier interconnects with XO, Level(3)/GlobalCrossing, Paetec, and PacWest. Backup power provided by UPS and generator. There is no geographic redundancy for core call processing functions. Facility details: »www.freshnews.com/news/554904/vi···atforms-
VOIPo -- operates on server equipment supplied from Softlayer in their Dallas and Washington DC locations. Specifics for each datacenter can be found at: »www.softlayer.com/about/datacenters/dallas
Primary call delivery is via SIP from their CLEC vendors, so automated failover (via DNS) is performed between their Dallas and Washington DC infrastructure. |
|
sokhapkinPremium
join:2003-05-08
Cape Coral, FL | reply to Davesnothere
What is the point of this thread? Where is the summary? |
|
DavesnothereNo-BHELL-ity DOES have its Advantages
join:2009-06-15
START&Cogeco
kudos:6
4 edits | said by sokhapkin:What is the point of this thread? Where is the summary?
Thanks for dropping in.
After what just happened to CallCentric in its NYC operations (and what VOIP.MS managed to avoid in theirs), this short thread is intended to become a ONE-STOP SUMMARY of the scattered info about VoIP providers' server locations and failover redundancy plans, some of which I have seen posted in various other recent threads here (often for the first time), plus info about additional VoIP providers of which I did not know before.
Therefore I would be both pleased and honoured if you would post the info for CallWithUs.  |
|
sokhapkinPremium
join:2003-05-08
Cape Coral, FL | Good. Where is the URL of the summary?
--
»www.callwithus.com |
|
|
|
 VexorgTR
join:2012-08-27
Sheffield Lake, OH | reply to Davesnothere
Appia:
Traverse City MI,
Chicago, IL |
|
espaethDigital PlumberPremium,MVM
join:2001-04-21
Minneapolis, MN
kudos:2 Reviews:
·Vitelity VOIP
| reply to Davesnothere
said by Davesnothere:this thread itself is supposed to become a summary of all of the scattered info about VoIP providers' servers and of their redundancy plans Can you edit your first post in the thread so that all the info is consolidated there, rather than having to scan through the thread? |
|
hardlyPremium
join:2004-02-10
USA | reply to espaeth
said by espaeth:Vitelity -- multiple facilities in the Denver area, primary facility in Englewood is owned by the company, has direct carrier interconnects with XO, Level(3)/GlobalCrossing, Paetec, and PacWest. Backup power provided by UPS and generator. There is no geographic redundancy for core call processing functions. Facility details: »www.freshnews.com/news/554904/vi···atforms-
...
It sticks in the back of my mind that Vitelity is one of voip.ms DID suppliers. Is that correct? |
|
1 edit | reply to Davesnothere
I think counting and listing server locations is based on a noble idea, but not likely to capture or characterize the systems in a meaningful way to customers.
Customers are interested in the reliability and availability of the services they've purchased. Let's begin with two simple definitions so we're all talking the same language.
Reliability: How often I can expect something to fail (or be unavailable) in a specified period of time.
Availability: What percentage of time I can expect something to be working. The standard availability formula is:
availability = uptime / (uptime + downtime)
Those are not two terms for the same thing. Something that fails 10 times a year for one minute each time has the same expected availability as another thing that fails once per year, but is out for 10 minutes. Their reliability is different, though.
VoIP customers are usually primarily interested in the reliability and availability of three things:
1. The ability to place outgoing calls from my phone.
2. The ability to receive incoming calls to my DID.
3. The ability to provision or make changes to account account/service.
There are other things, but those are the big three. Different customers will put them in different order or place different priorities on them based on their personal or business needs.
A server failure (or any other failure) may affect all of the services I'm interested in or just a subset. There are many failure modes in a distributed architecture.
The number and location of servers are just two of many factors contributing to the reliability and availability of customer purchased services. The design of the servers themselves, the architecture of the overall solution, and the availability of repair/correction staff are among a long list of other factors. Then you have to add in the expected reliability and availability of elements outside of the provider's direct control, such as physical CLEC connections and interconnecting IP networks.
Unfortunately, the detailed data necessary to estimate the expected availability of purchased services isn't readily available, so we're left with personal experience and that of others (word of mouth, reviews, forum info, etc.).
A typical VoIP provider will use several different kinds of servers to perform the various functions. It's unlikely any are using the same physical servers to host their web pages and provisioning as their SIP proxy servers. It's possible to have one web server and numerous SIP proxy servers scattered around or vice versa, although neither configuration makes much practical sense. The point is counting something as generic as "servers" doesn't tell you much about the expected reliability or availability of your DID line. |
|
 w8sdz
join:2001-05-21
Port Orange, FL | said by User834:VoIP customers are usually primarily interested in the reliability and availability of three things:
1. The ability to place outgoing calls from my phone.
2. The ability to receive incoming calls to my DID.
3. The ability to provision or make changes to account account/service.
The bottom line is: does the provider have a disaster recovery plan? Unfortunately Callcentric does not.
Think about this: What would happen if a natural or man-made disaster totally destroyed your provider's central operation.
One example of a good recovery plan is Anveo which has three data centers, widely separated in three different countries.
Your standard formula does't work when a single-site provider is destroyed.
--
73 de w8sdz - sip:w8sdz@getonsip.com - Google+: »plus.google.com/+w8sdz
|
|
DavesnothereNo-BHELL-ity DOES have its Advantages
join:2009-06-15
START&Cogeco
kudos:6
2 edits | reply to sokhapkin
said by sokhapkin:Good. Where is the URL of the summary?
I'm not sure what you are asking.
This thread IS the summary of what I have been able to find elsewhere, with contributions from other folks too, hopefully including yourself.
You are already here : »SERVER & GENERATOR LOCATIONS
Your website URL is helpful and appreciated, but I'm trying to only put the info about server locations and redundancy plans, and not other details of functions and features. |
|
DavesnothereNo-BHELL-ity DOES have its Advantages
join:2009-06-15
START&Cogeco
kudos:6
4 edits | reply to espaeth
said by espaeth:said by Davesnothere:this thread itself is supposed to become a summary of all of the scattered info about VoIP providers' servers and of their redundancy plans Can you edit your first post in the thread so that all the info is consolidated there, rather than having to scan through the thread?
I guess I could try that, but this is not a very long thread as it is.
Some of this info is in/from the 109 page omnibus CallCentric thread too »CallCentric tech issues today? , and I think that by getting it into here I have already reduced peoples' reading times considerably.
Also, some posters in the current thread, while their input is still valuable, have given incomplete info, and I encourage them to return and edit their posts if they learn any more about those particular providers during the next couple of days, before their posts get frozen.
Plus I was thinking of doing a spreadsheet or some sort of table afterwards, but I wish to wait a bit longer to see how many more providers get listed here.
And yes, I realize that DSLR locks each post after about 5 days. |
|
DavesnothereNo-BHELL-ity DOES have its Advantages
join:2009-06-15
START&Cogeco
kudos:6
1 edit | reply to User834
said by User834:I think counting and listing server locations is based on a noble idea, but not likely to capture or characterize the systems in a meaningful way to customers....
Interesting proposal, but I will be lucky to receive the level of info which I requested, never mind the degree of detail required to do calculations as you suggested. |
|
DavesnothereNo-BHELL-ity DOES have its Advantages
join:2009-06-15
START&Cogeco
kudos:6
2 edits | reply to hardly
said by hardly:It sticks in the back of my mind that Vitelity is one of voip.ms DID suppliers. Is that correct?
Yes, I believe so, and Fibernetics of Waterloo Ontario Canada is another provider to VOIP.MS for DIDs in Eastern Ontario Canada, and likely further areas.
Fibernetics is also a CLEC, and they provide DIDs to CallCentric and other VoIPPs in these same areas, which I learned while researching my OWN options, as I live there. |
|
DavesnothereNo-BHELL-ity DOES have its Advantages
join:2009-06-15
START&Cogeco
kudos:6
2 edits | reply to w8sdz
said by w8sdz:The bottom line is: Does the provider have a disaster recovery plan ? ....
.... right, and if yes, then what sort of a plan ?
Essentially that is all I wish to establish at this time.
AND, I am trying to avoid words which are open to misinterpretation, such as some of those contained in CallCentric's self-posted mission statement description on their own site. |
|
| reply to w8sdz
said by w8sdz:One example of a good recovery plan is Anveo which has three data centers, widely separated in three different countries. One small observation, if you want the security of servers on three sites make sure you specify anveo.com as the proxy rather than sip.anveo.com, sip.ca.anveo.com or sip.de.anveo.com. It's the only SRV record that points to all three servers.
--
DPC3825 (bridged mode) - WRT610N + Tomato - Panasonic KX-TGP500 - Asterisk 1.8.11.0 with Asterisk GUI on Virtual Server
Anveo - Voxbeam - Numbergroup - Callcentric - VoIP.MS - Localphone - UKDDI |
|
| reply to w8sdz
said by w8sdz:said by User834:VoIP customers are usually primarily interested in the reliability and availability of three things:
1. The ability to place outgoing calls from my phone.
2. The ability to receive incoming calls to my DID.
3. The ability to provision or make changes to account account/service.
The bottom line is: does the provider have a disaster recovery plan? Unfortunately Callcentric does not. Think about this: What would happen if a natural or man-made disaster totally destroyed your provider's central operation. One example of a good recovery plan is Anveo which has three data centers, widely separated in three different countries. Your standard formula does't work when a single-site provider is destroyed. How can the bottom line be anything other than, "do I have the services I paid for?"
A provider can have 100 servers, yet a single failure might render your DID number completely unworkable until it's resolved. Of course having a single server or a single location makes it vulnerable to location-wide disasters that affect all of their services, but that's just one of many failure modes that will affect the services you paid for. |
|
| reply to grand total
said by grand total:One small observation, if you want the security of servers on three sites make sure you specify anveo.com as the proxy rather than sip.anveo.com, sip.ca.anveo.com or sip.de.anveo.com. It's the only SRV record that points to all three servers.
Done, and thanks.
Anveo should document things like this. |
|
 Arne BolenHappy Anveo customerPremium
join:2009-06-21
Planet Earth
kudos:4
·Anveo
·callwithus
·Callcentric
·voip.ms
| reply to User834
said by User834:How can the bottom line be anything other than, "do I have the services I paid for?" One more bottom line:
"Does the customer have a disaster recovery plan?"
Voip is a wonderful service saving us $$$. But IMHO the user needs to have a disaster recovery plan. Having at least one backup voip provider and a cell phone is always a good part of a disaster recovery plan.
Your internet connection could also fail so a backup internet connection should be considered. Your provider can have geo redundancy but that won't help you if your internet connection fails.
Also, an UPS must be considered as mandatory for a responsible voip user.
--
My VoIP News |
|
 XCOMdigitalnUllPremium
join:2002-06-10
Spring, TX
·flowroute
 ·Comcast
·voip.ms
·Callcentric
·SIPBRI
| said by Arne Bolen:said by User834:How can the bottom line be anything other than, "do I have the services I paid for?" One more bottom line: "Does the customer have a disaster recovery plan?" Voip is a wonderful service saving us $$$. But IMHO the user needs to have a disaster recovery plan. Having at least one backup voip provider and a cell phone is always a good part of a disaster recovery plan. Your internet connection could also fail so a backup internet connection should be considered. Your provider can have geo redundancy but that won't help you if your internet connection fails. Also, an UPS must be considered as mandatory for a responsible voip user. +1
--
[nUll@dcypher ~]$ |
|
DavesnothereNo-BHELL-ity DOES have its Advantages
join:2009-06-15
START&Cogeco
kudos:6
2 edits | reply to userofdsl
said by userofdsl:said by grand total:One small observation, if you want the security of servers on three sites make sure you specify anveo.com as the proxy rather than sip.anveo.com, sip.ca.anveo.com or sip.de.anveo.com.
It's the only SRV record that points to all three servers.
Done, and thanks. Anveo should document things like this.
Fixed it for ya ! 
But seriously, how does one get an SRV record to reveal itself ?
I'm still a N00B on that.
And BTW, then does this observation also imply that if I am in Canada, 2 hours from Montreal, that I should specify ca.anveo.com rather than sip.ca.anveo.com ? (in my ATA)
On test, their Montreal server did yield a notably sharter PING than the next best one (USA) for me. |
|
