Closed
Bug 1123366
Opened 10 years ago
Closed 10 years ago
[Loop] Loop call can't be established when GSM call is established
Categories
(Firefox OS Graveyard :: Gaia::Loop, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1091790
People
(Reporter: lolimartinezcr, Unassigned)
Details
(Whiteboard: [Room1.1.1_TestRun1])
Flame 2.0
Gecko-5f9dc54
Gaia-31d6c94
Loop master version
User A logged in mobile loop app
Prerequisites:
Device A makes a GSM call to device B -> GSM call is established.
Device A logged in Mobile Loop application with MobileID.
Device C logged in Mobile Loop application with MobileID.
STR
1. Device C taps on "New conversation" button.
2. Device C Tap on contact A and taps on "Call" button.
3. Device A picks up Loop call (audio or video button).
Actual result:
In device A, Loop call can't be established. "Ended" status is shown in Device A
Expected result:
In device A, Loop call is established, and GSM call is in hold on
2. Change the date of the device so the room appears as expired in Room details
3. Tap on the room name to join
Reporter | ||
Updated•10 years ago
|
Whiteboard: [Room1.1.1_TestRun1]
Comment 1•10 years ago
|
||
Dup of 1091790 ?
Comment 2•10 years ago
|
||
(In reply to Beatriz Rodríguez [:brg] from comment #1)
> Dup of 1091790 ?
I would say yes. Unless bug 1091790 gets resolved and the patch reaches FxOS v2.0 WebRTC calls cannot be established when there is a GSM/CDMA call active.
Reporter | ||
Comment 3•10 years ago
|
||
Other scenario:
Prerequisites:
Device A makes a GSM call to device B -> GSM call is established.
Device A logged in Mobile Loop application with MobileID.
Device C logged in Mobile Loop application with MobileID.
STR
1. Device A is in GSM call screen, taps on "home" button.
2. Device A taps on Hello Dapplication.
1. Device A taps on "New conversation" button.
2. Device A Tap on contact C and taps on "Call" button.
Reporter | ||
Comment 4•10 years ago
|
||
Loop version: master/51a04dd
Comment 5•10 years ago
|
||
Yes, as Jose Antonio and Beatriz say in previous comments this bug is a duplicated of bug 1091790
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.
Description
•