Web Telephony API
Written by Kay Ewbank   
Tuesday, 25 June 2013

The System Applications Working Group of W3C has published a Working Draft of the Web Telephony API, which can be used to create apps to manage phone calls.

 

W3Clogo

 

A typical use of the Web Telephony API, according to the announcement of the working draft is the implementation of a 'Dialer' application supporting multiparty calls and multiple telephony services. The Web Telephony API allows applications to manage interaction with telephony call signaling, but does not handle audio channels management.

The API consists of a telephony manager interface that has a number of methods that you could use to carry out actions starting with making and receiving a call. There are options for hiding the caller identity, and for setting a default subscriber identity that will mean the caller doesn’t have to provide an identity when making a call. Calls can be put on hold and resumed, and new call participants can be added to (or removed from) an existing call. If the service being used can handle waiting calls, your app can put callers on hold and resume held calls. Incoming calls can be deflected to be handled by another number.

 Your app can send DTMF tones to the telephony network, and dial an emergency call without having a SIM card. Other options can be used to set the sound volume during a call, to  mute and unmute the microphone for a call, and to use headphones with calls.

The API makes use of various existing specifications, including the GSM-CALL suite for GSM, the IMS suite for IMS/SIP, and the Jingle specification for XMPP. The same API would work also for SIP and XMPP calls.  

 

W3Clogo

 

It seems that the Telephony API is more or less the same as the FireFox OS Telephony API as introduced as part of Mozilla's WebAPI efforts.  The only change seems to be the dropping of the moz prefix. If you are planning on making use of the Telephony API it is worth mentioning that under Firefox OS only certified apps will be allowed to use it and this means that it is effectively restricted to the phone manufacturer. The reason is, of course, security, but it is odd that an open platform like Firefox OS limits what you can do with the hardware you own. 

More Information

Web Telephony API First public working draft

Related Articles

Mozilla WebAPI - a universal phone app

Draft Specification of Streams API

Web Alarms API

Web Crypto APIs Work In Progress

W3C Draft For Device-Independent Input

W3C Publishes Push API Draft Specification

 

To be informed about new articles on I Programmer, install the I Programmer Toolbar, subscribe to the RSS feed, follow us on, Twitter, Facebook, Google+ or Linkedin,  or sign up for our weekly newsletter.

 

blog comments powered by Disqus

 

Banner


Open Source Code Puts Android At Risk
30/07/2014

A flaw in the Apache Harmony project has come back to threaten every version of Android from 2.1 to 4.4. It makes it possible to load apps that claim to be from almost any legitimate authority.



Google Frees Up More Patents
28/08/2014

Google has added 152 patents to the list of ones you can copy in your own open-source version and are covered by its OPN Pledge, whereby Google won't sue unless it is sued first.


More News

Last Updated ( Tuesday, 25 June 2013 )
 
 

   
RSS feed of news items only
I Programmer News
Copyright © 2014 i-programmer.info. All Rights Reserved.
Joomla! is Free Software released under the GNU/GPL License.