What is the “cloud phone”?
The last time, in the world of web development concept of cloud telephony has become quite frequently used. It appeared a few years ago with Ribbit, and attracted a lot of attention, along with the advent of Twilio and Tropo. As long as the phone features were not easily accessible, the industry itself considered sufficient telephony boring. Now, asynchronous access to telephony API, a variety of applications for telephony, as well as their integration with Web sites pop up everywhere on the Internet. And we can say that this is really a brand new ecosystem.
Remember 5 years ago, would you do the same thing with Asterisk? Naturally, it is now much easier.
But do you know what’s going on “behind the scenes” when you decide to call someone?
How traditional ITSPs operate
If you are looking for offers for broadband Internet, you’ll like the triple option – Internet, telephone, mobile phone or IPTV. In general, almost all providers offer telephony over IP, even if you do not know it. They rent the last mile from the existing DSL or have their own access networks (cable, WiMax, Wi-Fi), and thus telephony is just another service IP network. With most routers, EMTA, modems, you do not need to buy new equipment, you can use the old phone. After all, in fact, most consumers do not care about technical issues – they just want to use the phone.
But do you know what is required from a technical aspect to your call was successful? The telephone network is still running 99.999% per year. That’s about 5.5 minutes of downtime per year. And that’s fine, because you do not fall asleep while your ITSP will contact the server and the phone will send you a signal.
As the phone falls into the cloud?
When you, as a seller, offer telephony services to the cloud, you have to control their own software. A positive aspect is that (for example, Amazon EC2), you scale horizontally fast enough when it comes to hardware, because the new copies appear fairly quickly. But the downside is that you still need to take care of scalability at the application level. Even if you add additional server instances, it does not help if you can not use them at the application level. Again, no big difference, if you run the software on real hardware, or in the “cloud.” In addition, you do not need to analyze the basic software and hardware architecture, so you do not have a problem kasnetsya. All good for you as long as everything is working properly.
But the most important thing is this: your cloud gave an error!
. Always have the feeling that you missed something that you can not control the Active / Active or Active / standby, as they are “in the cloud”.
What happens to the cloud telephony?
The term “cloud telephony” really does not say anything. For example, SPCE works for instance Amazon EC2, which means that you do not have to pay in advance for the bare metal and power cooling costs. No more and no less. And this applies to any other vendor or service. But what happens when one of them breaks down? How will the cloud? Nothing.
If you want a reliable service, to dig deep into the architecture and see how it works. If you say, “we simply reliable, because we use the cloud,” you can safely raise a big red flag. So if Twilio, Tropo and Co. want to develop from a pure “approach, the end user” to something like B2B resale model, they should be ready for some serious issues related to architecture and other things. Stories that ITSP uses an optional external service “work in the cloud” on the top of our soft switch does not make much of an impression, although customers can and highly evaluate it.
But remember, if something breaks, it will be wine ITSP, and not the fault of the manufacturer. At least from the standpoint of consumers.