THE CLOUD MUST BE OPEN! Voxeo Announces Tropo: The Open Source Cloud Telephony Service

July 23rd, 2009 by Dan York

tropo.comlogo.jpgTHE CLOUD MUST BE OPEN!

Can we say that any clearer? What is the point of running your applications “in the cloud” if you are locked-in to using a single cloud provider?

Here at OSCON yesterday, Tim O’Reilly stood onstage in his keynote and spoke about centralized services and databases and their “natural tendency toward monopoly“. He and others here continue to sound the alarm and warn that our increasing reliance on “the cloud” brings with it the danger of relying on cloud services that will simply lock us in to new proprietary systems and protocols.

We agree.

At Voxeo, we don’t think you should be forced to use a particular cloud telephony service simply because they are the only one who supports the protocol or language you want to use. When we launched Tropo.com back at eComm in March, this was one of our underlying concerns:

How do we prevent vendor lock-in for cloud telephony?

How do we make it so that our customers can develop their applications on Tropo.com, but yet have the freedom to take those applications and run them on some other provider’s service if they want to?

In looking at it, we saw the fairly obvious route that will no doubt seem radical to many:

We are making the Tropo.com source code available as open source. 

Yep… we’re opening the cloud. As our CEO Jonathan Taylor said (and yes, he actually did write this):

“Since 1999, Voxeo’s core mission has been to make telephony easy, effective and free of lock-in. We’ve been tearing down the walled gardens of telecom and replacing them with an open and accessible environment,” said Jonathan Taylor, CEO of Voxeo. “Nothing demonstrates this commitment better than Tropo’s completely open standards foundation and open-source availability. Unlike cloud vendors that use open-source but offer little back to the open-source community, we’re showing how cloud computing can be both completely open for end customers and concretely beneficial to open-source developers.” 

As both the news release and the post on our Tropo blog indicate, today marks the start of the process. We’ve made available two of the components that make up Tropo.com:

  • Tropo SIP Servlet, which implements the Tropo core Java API for telephony applications and a mechanism to host a wide variety of programming languages on top of that API. The Tropo SIP Servlet is built on the Java SIP Servlet standard, JSR-289. SIP Servlet platforms are available from many vendors including Voxeo, Oracle, Avaya, and Redhat. The Tropo SIP Servlet uses another standard, the IETF’s MRCP standard to control audio interaction during calls. By open-sourcing this technology, we hope to support a wider variety of MRCP servers, and ultimately support any media platform that implements the Java Media Server Control API, JSR-309. 
  • Tropo “Shims” for Groovy, JavaScript, Python, PHP and Ruby programming languages. Tropo Shims adapt the Tropo core API for use in a specific programming language. Open-sourcing these components enables Tropo to quickly support other programming languages. By releasing this code and working with the open-source telephony community, we hope to add support for additional programming languages such as Clojure, JavaFX, and Scala.

Over the coming weeks, Jason Goecke and Jay Phillips of our newly-announced Voxeo Labs team will release additional Tropo components that will allow you to run your own Tropo applications in private clouds, elastic computing services, or on your own servers in conjunction with Voxeo’s free Prophecy platform. Over the coming months, Voxeo Labs will work to support the widest variety of SIP Servlet and media server platforms, ultimately giving you a simple yet powerful telephony API that will work across the widest variety of platforms and vendors. Jason and Jay will be posting more information to the Voxeo Labs blog in the days and weeks ahead.

It’s all about having an open and interoperable cloud.

We’re excited about the possibilities – we hope you are, too. Will you join us now in bringing about open and interoperable cloud telephony?


P.S. This move may not be a surprise to those of you familiar with our traditional VoiceXML hosting business. You know that for 10 years we’ve been providing the most open standards-compliant XML voice application platform and today have grown to be the world’s largest provider of VoiceXML hosting, with more companies bringing their XML applications to our platform every day. We have grown our business successfully by providing those customers the best possible platform and providing the industry’s best customer service… not by locking them in…

Related posts:

  1. Voxeo’s launch of Tropo.com: an update one week later
  2. Voxeo providing hosting for open source Adhearsion project
  3. Voxeo announces Prophecy 9 with new management UI, new SIP APIs… and Linux and Mac OS X support!
  4. Dan York speaking on “Securing Cloud Telephony” at SpeechTEK in August
  5. Voice & Cloud Computing: “Pushing IVR Into The Cloud, Part 1: Making the Move”

Tags: , , ,


Want to learn how Voxeo can help unlock your communications and deliver a better customer experience? Please contact us!

If you found this post interesting or helpful, please consider either subscribing via RSS, becoming a fan on Facebook, or following us on Twitter.


13 Tweets

12 Responses to “THE CLOUD MUST BE OPEN! Voxeo Announces Tropo: The Open Source Cloud Telephony Service”

  1. voxeo Says:

    THE CLOUD MUST BE OPEN! Voxeo Announces Tropo: The Open Source Cloud Telephony Service http://bit.ly/2nhRE

    This comment was originally posted on Twitter

  2. nwgsweet Says:

    @voxeo opening the cloud http://bit.ly/p7PMD

    This comment was originally posted on Twitter

  3. adhearsion Says:

    THE CLOUD MUST BE OPEN! Voxeo Announces Tropo: The Open Source Cloud Telephony Service http://bit.ly/2nhRE (via @voxeo)

    This comment was originally posted on Twitter

  4. Mark Says:

    I see a PHP shim in the Github repository as well, correct? The post above mentions only “Groovy, JavaScript, Python, and Ruby” unless I missed something – just wanted to make sure I wasn’t seeing things. ;-)

    Major props for this, I’ll be looking forward to future posts from Jason and Jay!

  5. Dan York Says:

    Yikes! How could I forget PHP?

    Thanks for pointing it out… I’ll make the correction.

  6. mheadd Says:

    #Voxeo’s Tropo to become “an open and interoperable [telephony] cloud.” Sweet! http://is.gd/1J1MN

    This comment was originally posted on Twitter

  7. Mark Says:

    I’ve got PHP on the brain. ;-)

  8. voxeo Says:

    THE CLOUD MUST BE OPEN! Voxeo Announces Tropo: The Open Source Cloud Telephony Service – http://bit.ly/p7PMD #OSCON

    This comment was originally posted on Twitter

  9. voxeo Says:

    If you are at #OSCON and interested to speak to someone about our Tropo open source news – http://bit.ly/p7PMD – @danyork is there at OSCON

    This comment was originally posted on Twitter

  10. jicksta Says:

    Voxeo’s commitment to open-source and a non-monopolistic telephony cloud is overwhelmingly awesome: http://bit.ly/u5JW8

    This comment was originally posted on Twitter

  11. stacy Says:

    Hey Dan is Voxeo purposely excluding Asp.net because of the heavy open source focus?

  12. Speaking of Standards » Blog Archive » Must-See Video: Tim O’Reilly’s Web 2.0 Keynote on The War For The Web Says:

    [...] in open standards (and chair/co-chair many of the standards committees), where we do things like open source our Tropo cloud telephony platform (“The Cloud Must Be Open!”) and where, in contrast to Nuance and TellMe as Tim mentions [...]

Leave a Reply

Please note: By submitting a comment you agree to comply with our Comment Policy. We welcome all comments, positive or negative, but do reserve the right to remove all or part of blog comments that do not comply with our policy.

Additionally, the first time you leave a comment on this blog, it will be held for moderation. After that first comment has been approved, future comments will be posted without delay.

Additional comments powered by BackType