I kind of agree. Although I think the underlying assumption is that it's an infrastructure as a service play, and so Twilio et al are creating value. Obviously their target market is the web app developer crowd.
To do it yourself you need to line up your outbound SIP providers, inbound DID providers (not one and the same once you dig into the details), then you need to operate a bunch of Freeswitch / Asterisk / whatever SIP servers, and learn how to program them, and learn how keep them running smooth (Not particularly difficult, but in terms of learning requirements - it's akin to meeting a database + web server for the first time).
Due to the real-time nature of telcos (and I mean that in the traditional clock-synch'd sense of the word) there are additional complications if you want to use a virtualised OS.
I get your point, but feel you are overplaying the difficulty. You can code in plain ol javascript on freeswitch to create complex inbound and outbound comms apps in a couple of hours. Plug it into a sip provider ( i use sipgate ) and there is nothing more complex to it. Far far cheaper too.
You dont need a bunch of servers either. If you are doing more than 200 simultaneous calls ( freeswitch easily achieves this on 1 box ) you shouldnt be looking at these entry level systems; Voxeo, Tropo's parent company has an incredibly powerful platform.
One box? One box is never a good idea for an application that is relied upon. You need to have redundancy (geographic even better), load-balancing, etc.
Sure, you may roll your own anything, but you are better off outsourcing much of that to cloud providers today. Freeing you to focus on your application that provides value to your users, not worrying about how to properly architect and scale telephony solutions.
Unfortunately, you can't get SMS when you do it yourself using SIP/FreeSwitch. These companies have made the deals with the individual telecom providers to do that for each of their DID numbers.
Well, you could it's just not easy. A GSM modem attached to the server would do the trick.
Apache's free and hardware's cheap. Yet Rackspace still manages to run a huge web hosting business.
For some people and some uses, building a web server and hosting it on your home or office network is acceptable. But those that don't count "web hosting" as their core business and want the reliability, security, and stability that comes from having a professional do it tend to hire a company to do it for them.
Like most other things in technology, it's a simple build-vs-buy question. Is it more cost effective and better suited to my needs to build it myself or to buy from someone who's an expert?
Freeswitch and Asterisk are great. I was the emcee at the Freeswitch developer conference last year and we financially support Adhearsion, an Asterisk development framwork. They fill a great niche for DIY telephony. For everyone else, there's hosted services.
To do it yourself you need to line up your outbound SIP providers, inbound DID providers (not one and the same once you dig into the details), then you need to operate a bunch of Freeswitch / Asterisk / whatever SIP servers, and learn how to program them, and learn how keep them running smooth (Not particularly difficult, but in terms of learning requirements - it's akin to meeting a database + web server for the first time).
Due to the real-time nature of telcos (and I mean that in the traditional clock-synch'd sense of the word) there are additional complications if you want to use a virtualised OS.