Closed Bug 930866 Opened 11 years ago Closed 10 years ago

[DSDS] [Gaia][Dialer] Emergency call on the active SIM

Categories

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

x86_64
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1027478

People

(Reporter: hsinyi, Unassigned)

References

Details

(Whiteboard: [L2])

At any given time, user should be able to make an emergency call from the currently active SIM, even the active one isn't the default primary one.

To support this, Dialer needs to be more intelligent: if user is in call with non-primary SIM, the following outgoing calls (emergency call included) needs to be made with that SIM rather than the primary one.

Telephony API supports that. Dialer could check TelephonyCall.serviceId to know if the non-primary SIM is used. If yes, Dialer needs to clearly specify serviceId in telephony.dial(). 

Previous discussions: https://bugzilla.mozilla.org/show_bug.cgi?id=926345#c14
Joe, Anyone from comms team can take this bug?
blocking-b2g: --- → 1.3?
Flags: needinfo?(jcheng)
This is not in the scope of v1.3.
blocking-b2g: 1.3? → 1.4?
Summary: [DSDS] [Dialer] Emergency call on the active SIM → [DSDS] [Gaia][Dialer] Emergency call on the active SIM
this is related to https://bugzilla.mozilla.org/show_bug.cgi?id=926345#c19

if we can accept hanging up the call in progress before making the emergency call, this bug will not block 1.3. Waiting for more feedback on bug 926345
Flags: needinfo?(jcheng)
Joe, what's your take? In 1.3 or in 1.4? Looks like the effort is in Comms app team.
Flags: needinfo?(jcheng)
depend on https://bugzilla.mozilla.org/show_bug.cgi?id=926345#c19
prefer this is done in 1.4
Flags: needinfo?(jcheng)
Whiteboard: [L2]
If it's no longer a blocker for v1.3 bugs, I will remove the dependency to block 926345.
Blocks: backlog-RIL/Net/Conn
No longer blocks: 926345
blocking-b2g: 1.4? → ---
It isn't a RIL feature.
No longer blocks: backlog-RIL/Net/Conn
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.