W3C home > Mailing lists > Public > public-device-apis@w3.org > October 2010

Re: Phono potential use case

From: Neil Stratford <nstratford@voxeo.com>
Date: Thu, 28 Oct 2010 11:50:09 +0100
Message-ID: <4CC95561.2000200@voxeo.com>
To: Robin Berjon <robin@berjon.com>
CC: public-device-apis@w3.org, dburnett@voxeo.com
Hi Robin,

Phono is one of our products at Voxeo that we have just launched in 
beta. Our goal is to create an open flexible api for real-time 
communications that is independent of the underlying technology or 
vendor, and to work with standards as much as possible (especially IETF 
and W3C -- Dan Burnett, our Director of Standards and Speech 
Technologies at Voxeo, is chair of the HTML Speech Incubator and Voice 
Browser Working Groups and will be at TPAC next week and IETF 79 the 
following week.)

Most of the current Phono implementation is actually already in 
javascript - the call signaling is all carried using XMPP over BOSH 
direct from javascript. For the initial release we used flash as a 
mechanism to gain access to the microphone and stream audio, but we 
intend to support multiple mechanisms going forward (java is in the 
pipeline) and ultimately use whatever the browser can make available to 
us. There are more details of our current implementation here:
http://blog.phono.com/2010/10/25/behind-the-phone/

Neil

On 27/10/2010 11:08, Robin Berjon wrote:
> Hi,
>
> I don't know if you've seen this:
>
>    http://www.phono.com/
>
> It's a jQuery plugin that allows you to make a phone call from a web page. It works (I called Zakim). This seems to me like it could be a good use case to address (the wrapper is JS, but the actual implementation is Flash), looking at how we could integrate our various specifications to perhaps make it work, see what's missing, etc.. Thoughts?
>
Received on Thursday, 28 October 2010 19:23:05 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:32:23 UTC