1164530 - Create integration points to allow Caller ID & Block apps

Status: RESOLVED INCOMPLETE

(Firefox OS Graveyard :: Gaia::Dialer, defect)

Description

[:Harald Kirschner :digitarald]

TrueCaller, Whitepages and others are interested in launching their services on Firefox OS, which mainly include:

- Caller ID: Identify calls from numbers that are not in your address book.
- Call Blocking: Block spam, scams and telemarketers.

Android (via PhoneStateListener et al) and Tizen (via ITelephonyCallEventListener et al) both provide events and APIs to support Caller ID apps that can be used as reference.

Comment 1

[:Harald Kirschner :digitarald]

+Vishy for more product input.

Comment 2

[:Harald Kirschner :digitarald]

+Andrew to find somebody from the WebAPI team to provide input.

+Paul for the security aspect (is it too early?).

Comment 3

[Andrew Overholt [:overholt]]

Hsin-Yi would know more about event/API additions here.

Comment 4

[Paul Theriault [:pauljt] (no longer reading bugmail)]

Probably too early. My only comment is that currently all telephony related APIs are certified only. I think we will move most/all APIs to privileged however, and enforce restrictions in marketplace instead of within gecko. This gives us the ability to give partner apps with increased permissions that we dont want to give out to apps in general. (the main reason is to avoid the prior situation for apps like loop where we need to create app specific permissions).

Of course it all depends on exactly what you plan to expose.

TLDR: we probably dont want this exposed broadly by can perhaps grant it by exception to partners apps. Thats about all I have to add for now. I've CC'd Stephanie who provide a more detailed review once we get closer to defining an API.

Comment 5

[Hsin-Yi Tsai (she/her) [:hsinyi]]

Sorry for being late here. We've provided call id information via TelephonyCall.webidl and TelephonyCallId.webidl. One thing to note that, as Paul mentioned, these APIs are certified-app only now.

Comment 6

[vkrishnamoorthy]

In addition to use cases such as call block, there are other interesting use cases for intercepting call status and performing actions on the status.

Also, in addition to CallID, we will also need a way to get the call_state and set listeners for the various call states.

I can see both the upside and flexibility such an API would provide as well as the downside in terms of security risks.

Is the WebTelephony API http://www.w3.org/TR/2013/WD-telephony-20130620/ currently being worked on?

Comment 7

[:Harald Kirschner :digitarald]

Maybe :hsinyi can answer on the work on WebTelephony API

Comment 8

[:Harald Kirschner :digitarald]

This should probably be covered as use case for addons as it is a prime example of partners extending a built in app.