Closed Bug 1185850 Opened 9 years ago Closed 9 years ago

Call barring on a *specified* incoming call

Categories

(Firefox OS Graveyard :: RIL, defect)

Product:
Firefox OS Graveyard
Component:
RIL
Platform:
ARM
Gonk (Firefox OS)
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: hsinyi, Unassigned)

Details

User Story

As a user, I want to be able to barre a specific incoming call.
Currently mozilla supports call barring on *all* incoming calls. This bug requests mozilla support advanced call barring on a specified incoming call. From the network point of view, there's no network configuration of this feature, which however is a blacklist feature or a customized feature. So here is the suggestion from mozilla: vendor implements this blacklist feature on Gaia side Hi Carol, per our bi-weekly meeting, please provide us more details from carrier partners so that we could review if this solution is feasible or not. Thanks!
Flags: needinfo?(cyang)
Though we are still under discussion about which party, mozilla or partner, the effort of this bug falls into, file this bug for tracking and following-up.
No longer blocks: red-square
Flags: needinfo?(cyang)
(In reply to Hsin-Yi Tsai [:hsinyi] from comment #0) > Currently mozilla supports call barring on *all* incoming calls. This bug > requests mozilla support advanced call barring on a specified incoming call. > > From the network point of view, there's no network configuration of this > feature, which however is a blacklist feature or a customized feature. According the TS 24.611 [1], the network is responsible for barring even specific incoming call. Please refer to Incoming Communication Barring (ICB) in the spec. > > So here is the suggestion from mozilla: > vendor implements this blacklist feature on Gaia side Because network would be handling the call barring, we can also handle this via MMI if no UI is needed. > > Hi Carol, per our bi-weekly meeting, please provide us more details from > carrier partners so that we could review if this solution is feasible or > not. Thanks! [1] http://www.etsi.org/deliver/etsi_TS/124600_124699/124611/10.02.00_60/ts_124611v100200p.pdf
(In reply to Carol Yang [:cyang] from comment #2) > (In reply to Hsin-Yi Tsai [:hsinyi] from comment #0) > > Currently mozilla supports call barring on *all* incoming calls. This bug > > requests mozilla support advanced call barring on a specified incoming call. > > > > From the network point of view, there's no network configuration of this > > feature, which however is a blacklist feature or a customized feature. > > According the TS 24.611 [1], the network is responsible for barring even > specific incoming call. Please refer to Incoming Communication Barring (ICB) > in the spec. > Thanks for pointing this out. According to the rule "cp:identify" in the subclause 4.9.1.4, I think you are right. > > > > So here is the suggestion from mozilla: > > vendor implements this blacklist feature on Gaia side > > Because network would be handling the call barring, we can also handle this > via MMI if no UI is needed. > Sounds good to me, too. > > > > Hi Carol, per our bi-weekly meeting, please provide us more details from > > carrier partners so that we could review if this solution is feasible or > > not. Thanks! > > [1] > http://www.etsi.org/deliver/etsi_TS/124600_124699/124611/10.02.00_60/ > ts_124611v100200p.pdf
No work required on moz side.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.