Telephony API Providers and Why They Suck (WTS)
So on the road of developing the StudioTalker product, we recently met a fork. The media backend for the app is easy, we can handle that just fine. Signalling, on the other hand, is a lot of work. What do you do when something is a lot of work? You outsource it….
Except that’s tricky. The vast majority of “Cloud Telephony” products, which are essentially large signalling and API farms, are based on the same pretence - a simple call flow, be it basic playback, DTMF or voice control and maybe an IVR, and then hangup. That’s all well and good if you’re doing appointment reminders, but StudioTalker is more complicated than that.
So then we found Ribbit. Ribbit looks cool, until you realise that they don’t like SIP endpoints and they do like Flash. Oh dear.
Next up, onSIP. US only. Fail!
Unfortunately, this leaves us with few other options, so it looks like we’ll be taking the other route and doing this ourselves; this is gonna take time, but we may just sell our byproduct…
