Closed Bug 861083 Opened 8 years ago Closed 8 years ago

B2G RIL: Move call forwarding related API from mozMobileConnection to mozIccManager

Categories

(Core :: DOM: Device Interfaces, defect)

x86_64
Windows 7
defect
Not set
normal

Tracking

()

RESOLVED WONTFIX

People

(Reporter: edgar, Assigned: edgar)

References

Details

In bug 857414, we plan to move all sim/icc related stuff from mozMobileConnection to mozIccManager. This bug is filed for call forwarding related API.
- setCallForwardingOption()
- getCallForwardingOption()
- oncfstatechange
It seems call forwarding APIs are not suitable to put into IccManager. Should call forwarding APIs belong to MobileConnection, IccManager or Telephony? let's offline discuss first. Thanks.
(In reply to Edgar Chen [:edgar][:echen] from comment #1)
> It seems call forwarding APIs are not suitable to put into IccManager.
> Should call forwarding APIs belong to MobileConnection, IccManager or
> Telephony? let's offline discuss first. Thanks.

Maybe, we have to implement a ssManager to handle supplementary services, because there are many kinds of supplementary services.
Here is the list for SS.
1. Multiparty Services.
2. Call Waiting.
3. Call Hold.
4. Call Forwarding.
5. Call Barring.
6. Number Identification-
   1)Calling Line Identification Presentation.
   2)Calling Line Identification Restriction.
   3)Connected Line Identification Presentation.
   4)Connected Line Identification Restriction.
   5)Malicious Call Identification.
7. Advice of Charge (AoC).
8. Closed User Groups (CUGs).
9. Unstructured supplementary services data (USSD).
After off-line discussion, we all agree it is not suitable to put call forwarding API into IccManager. Telephony is more suitable place for these API. So close this bug as WONTFIX. I will file another bug for moving into Telephony. Thanks.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.