Closed Bug 1092908 Opened 10 years ago Closed 6 years ago

[Dialer] the 3rd (waiting) call should be rejected when there are one connected and one held calls

Categories

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

x86_64
Linux
defect
Not set
normal

Tracking

(b2g-v2.0 affected, b2g-v2.1 affected, b2g-v2.2 affected)

RESOLVED WONTFIX
Tracking Status
b2g-v2.0 --- affected
b2g-v2.1 --- affected
b2g-v2.2 --- affected

People

(Reporter: hsinyi, Unassigned)

Details

STR:
1) Dial out 1st call and remote party accepts it
2) Dial out 2nd call and remote party accepts it. Now we have 1st call on hold and 2nd call is connected
3) Have a MT (incoming) call

Actual result:
No UI was displayed for the 3rd call, but NO "hangup" command was sent to Gecko. The 3rd call wasn't released and the remote party heard the call kept ringing. 

Expected:
No UI was displayed for the 3rd call, and the 3rd call is rejected automatically in background [1].

[1] https://github.com/mozilla-b2g/gaia/blob/master/apps/callscreen/js/calls_handler.js#L141

I saw an error message that might be the cause:
W/GeckoConsole(  205): [JavaScript Error: "TypeError: this.updateCallNumber is not a function" {file: "app://callscreen.gaiamobile.org/gaia_buil     d_defer_index.js" line: 284}]
QA wanted for a branch check.
Keywords: qawanted
Tested with Shallow Flash on 319mb using Engineering builds

This bug repro's on Flame KK builds: Flame 2.2 kk, Flame 2.1 KK, Flame 2.0 KK, Flame 2.0 Base

Actual Results: No UI was displayed for the 3rd call, but NO "hangup" command was sent to Gecko. The 3rd call wasn't released and the remote party heard the call kept ringing.

Repro Rate: 2/2

Environmental Variables:
Device: Flame 2.2 KK
BuildID: 20141112125016
Gaia: 65d593cdd9d88648045a30a63fc329b7bb5d340b
Gecko: 66cdb18f36da
Version: 36.0a1 (2.2) 
Firmware Version: v188-1
User Agent: Mozilla/5.0 (Mobile; rv:36.0) Gecko/36.0 Firefox/36.0
-----------------------------------------------------------------
Environmental Variables:
Device: Flame 2.1 KK
BuildID: 20141114064525
Gaia: e6409eb6d2e8c13127f9e6e46995db03354e4b57
Gecko: 8657c038c437
Version: 34.0 (2.1) 
Firmware Version: v188-1
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0
-----------------------------------------------------------------
Environmental Variables:
Device: Flame 2.0 KK
BuildID: 20141114071116
Gaia: 086a668942292168f312b3bb53e275fa0886fab1
Gecko: dff15c618980
Version: 32.0 (2.0) 
Firmware Version: v188-1
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
-----------------------------------------------------------------
Environmental Variables:
Device: Flame 2.0 Base
BuildID: 20141021162107
Gaia: 8c5c956ee6909408e29f375cc7d843a03d92f3d8
Version: 32.0 (2.0)
Firmware: V188-1
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(jmitchell)
Keywords: qawanted
QA Contact: croesch
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(jmitchell)
QA Contact: croesch
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.