System Applications WG: Telephony API

From W3C Wiki
Revision as of 13:05, 15 April 2013 by Zkis (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

This is the Wiki page for the Telephony API draft in the W3C System Applications WG

Stakeholders

The Web Telephony API stakeholders are the following:

  • implementor: implements the API specification in a Web runtime, using the underlying platform features
  • developer: implements applications using the API specification
  • end user or user: provides input to the applications.

Use Cases (list of links)

The main use cases of the Telephony API from the end users point of view are the following:

  • make a call to a remote party
    • id multiple subscriber identities are configured, choose which identity should be used for a dialed call
    • hide the caller identity, if the network supports it
  • set a default subscriber identity, so that the identity is optional to provide before dialing
  • send DTMF tones to the telephony network
  • list the usable emergency numbers
  • dial an emergency call without having a SIM card
  • receive phone calls
  • handle waiting calls, when the service is available and enabled
  • put calls on hold
  • resume held calls
  • add new call participants to a call
  • remove call participants from a call
  • deflect an incoming call to be handled by another remote party
  • transfer an ongoing call with a remote party to become a call between the remote party and a third party
  • set the default sound volume for telephony
  • set the sound volume during a call
  • mute and unmute the microphone for a call
  • use headphones with calls

Further use cases, which are not currently implemented:

  • use external displays with calls
  • select between audio sources (microphones)
  • select between audio targets (speaker, headphones, etc)
  • see and manage call capabilities during a call, such as is multiparty call possible, is video possible, etc
  • set and check network services, such as call forwarding, call barring, network selection mode, call counters, etc.
  • save the list of past calls into call history.

The main use cases from the developers point of view are to use the API to programmatically implement the user use cases from above. In addition,

  • track the progress of calls through call state change event notifications
  • track enabled and disabled telephony services through event notifications
  • set DTMF mark and space parameters
  • use a well defined structure for call history

Technical requirements

The Telephony API MUST fulfill the following technical requirements:

  • The API MUST be agnostic of implementation details such as underlying platform architecture and telephony middleware implementation.

WG Drafts

Web Telephony API Editor's Draft

Proposals (list of links)