1008643 - [Gaia] Implement caller ID

Status: RESOLVED WONTFIX

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

Description

[rejuasjuas]

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux i686; rv:29.0) Gecko/20100101 Firefox/29.0 (Beta/Release)
Build ID: 20140428194004

Steps to reproduce:

alcatel one touch fire FFOS 1.1.0.0-02002 , when inconming calls come , only show the phone number , not the name of the caller

Comment 1

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

(In reply to rejuasjuas from comment #0)
> User Agent: Mozilla/5.0 (X11; Ubuntu; Linux i686; rv:29.0) Gecko/20100101
> Firefox/29.0 (Beta/Release)
> Build ID: 20140428194004
> 
> Steps to reproduce:
> 
> alcatel one touch fire FFOS 1.1.0.0-02002 , when inconming calls come , only
> show the phone number , not the name of the caller

This feature hasn't been supported yet. The referred gaia bug is Bug 980598. Gecko work is bug 981519.

Comment 3

[Doug Sherk (:drs) (inactive)]

STR and relevant information from bug 980598:

(In reply to promise09th from comment #0)
> Title : Implement Call reception operation
> Scenario : 
> 1) Make a new call adding 184/186 prefix in sender device
> 2) Receive call in receiver device
> 3) Show four types string in receiver device : 
> - Unavailable
> - Reject by user
> - Interaction with other services
> - Coin line / pay phone

(In reply to shawn ku [:sku] from comment #3)
> Per GET_CURRENT_CALLS, there should be numberPresentation contained. [1]
> 0=Allowed, 
> 1=Restricted, 
> 2=Not Specified/Unknown 
> 3=Payphone
> 
> GECKO should already pass it to Gaia.
> 
> 
> [1]
> https://github.com/android/platform_hardware_ril/blob/master/include/
> telephony/ril.h#L188

Comment 5

[Mike Lee [:mlee]]

CAF (Code Aurora Foundation) investigating origin of request to add this feature to 2.2 and will respond here.

Comment 6

[Anshul]

Yes, this feature hasn't been supported properly by Gaia since always. But this is a certification blocker and our customers(OEM/network operators) get to decide if this is a blocker for them or can they provide us an exception.

Is moz is deciding to not fix this in 2.2, we need to find a way to fix all such certification blockers with higher priority in the next release.

Comment 7

[Mike Lee [:mlee]]

Sandip & Ravi,

How does product want to handle this?

(In reply to Anshul from comment #6)
> Yes, this feature hasn't been supported properly by Gaia since always. But
> this is a certification blocker and our customers(OEM/network operators) get
> to decide if this is a blocker for them or can they provide us an exception.
> 
> Is moz is deciding to not fix this in 2.2, we need to find a way to fix all
> such certification blockers with higher priority in the next release.

Comment 8

[Ravi Dandu]

Hi Anshul, Can you help identifying which network operator certification this blocks?

Comment 9

[Ravi Dandu]

Hi Anshul, Can you help identifying which network operator certification this blocks?

Comment 10

[Anshul]

Ravi, this is part of GCF certification so any operator that blocks a release pending GCF compliance will need this support.

Comment 11

[BMO Automation]

Firefox OS is not being worked on