Lypp VoIP API, 37signals, Broadsoft Xtended, Ruby on Rails

We are just one day away from opening the doors to the 37signals Highrise + Lypp VoIP Mashup contest, we are all quite excited about what will come of that, the entire post is over here.

Something I read today that I thought was rather "timely" in this regard was Thomas Howe's post regarding his new Ruby Gem built for Broadsoft via Xtended.

For those who don't know, Broadsoft is essentially the leader in the VoIP softswitch department although they really like to be called a Voice Application vendor, I think, Scott will likely correct me on that 😉

At least one person has asked me what I think of BX (Broadsoft Xtended) and what it means to Lypp and specifically the impact it has on the Lypp API.

Here it is..

1. For carriers, the Lypp API is to some degree what Xtended is to Broadsoft, just not for Boradsoft. Our API was written so that we could easily port it to any softswitch, voice application platform, voip switch etc. So if Broadsoft customers or even competition wanted some of the same functionality that is delivered via Xtended they might take a look at the Lypp API.

2. For service providers, Lypp offers a complete service toolkit that not only gives you the API but also delivers the telephony service as well. Think of the Lypp API as the Amazon Web Services of VoIP. The API is free and so is a developer account, you only pay for what you use, just like Amazon Web Services.

3. For application developers, it is a brainless way to bring advanced telephony into existing or new applications (web, mobile, client-server, et al) without investing millions into infrastructure.

The impact Broadsoft Xtended has on Lypp is very positive. Broadsoft has plenty of marketing dollars and the more people that understand what Xtended is the more it will help little companies like Lypp accelerate their own growth.

So to this I say, "Go Broadsoft! Go Lypp! Go Rails!"

by Erik | http://sipthat.com

Tags: , , , , , , , , , ,

%d bloggers like this: