Closed
Bug 1045855
Opened 11 years ago
Closed 10 years ago
Loop mobile client connection fails if network changes
Categories
(Firefox OS Graveyard :: Gaia::Loop, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: diego, Unassigned)
References
Details
Attachments
(2 files)
STR:
1. Join wifi network
2. Open Loop mobile client app with Firefox account.
3. Make a call (it should work).
4. Disable wifi and use cell data network.
5. Open Loop mobile client app again.
6. Make a call.
Result: the receiving phone never even gets a call notification.
Workaround: If you log out and back in Loop settings after joining the the second network it works.
My guess is there's some IP dependent registration that does not get refreshed when the network changes. This is also reproducible if you switch between two wifi networks.
Comment 1•11 years ago
|
||
I've tested right now, and It seems running fine.
FireE vs FireE
Loop Version: Loop Version: 1a7255d
1.- First call: DeviceA in wifiA to DeviceB in WifiB. Both with FxAccount.
2.- Disable wifi in DeviceA and use cell data network.
3.- Open Loop mobile client app again.
4.- Second call: DeviceA in 3G to DeviceB in WifiB.
Can you test again in your environment?
Reporter | ||
Updated•10 years ago
|
Flags: needinfo?(dwilson)
Updated•10 years ago
|
Whiteboard: [feedback pending]
Tested with Flame 2.0 (v180) Gecko: 2e0f023 and Gaia:31434a3
Loop: 3cd2086
It works fine, so I close this bug.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Just checked on the newer version of loop mobile client: version '2c64362' and the problem is still there. I can see that the call connection is established as call duration timer started, but no video or audio.
The problem doesn't happen if I have both devices on the same network.
Can you help to check if there is any regression?
Status: VERIFIED → REOPENED
Flags: needinfo?(javier.deprado)
Resolution: FIXED → ---
Hi Jay
I'm not able to reproduce the bug. We have used the loop version 0a3ed53 and Gecko-243b231.Gaia-ddb7567.
Both calls are established (wifi and 3g), the only problem is that using the 3G connections the audio was very choppy.
Could you give us the exact steps in order to reproduce the problem in our environment. I mean, did you made the call from the call log or from the contact detail? Did you made audio call or video call? Did you use Firefox Account or Mobile ID? We have tested the call in two different wifi's (different cities) and works as expected, apart from the audio quality
Flags: needinfo?(javier.deprado)
Hi Javier,
I have a device connected to wifi AP and another device on 3G network. I started the video call from the call log and accepted the video call from the another device. I used Firefox Account for both devices.
CSF logging for test case is attached. There are two test cases.
1. 3G AP <-> 3G
2. 3G AP <-> QC Wifi
The log includes a readme.txt for each test cases that describe the procedure. It appears to me that case 1 and case 2 has different failure even though both are not working
Some update.
I tried the test @ home with my home wifi and 3G network. I was able to make a loop call (even though the quality is bad).
Also, I was able to make the 3G to 3G call after few tries. It is not consistent.
However, I couldn't make a successful call between company's wifi and 3G device so I guess this is to do with our networking setting.
Therefore, please, ignore the case #2 and help to see what caused case #1 failure.
Hi Jay
I'm not able to reproduce this. I've tried both cases, and in both cases I can establish the connection and audio and video are transmitted. The audio and video quality is poor due to some open bugs, but the connection is successfully established.
Comment 10•10 years ago
|
||
I attached the log from failure case. Do you see anything from the log?
Comment 11•10 years ago
|
||
We have tested the scenario 3g vs 3g. Attached the log. The video is transmitted and the quality is same than wifi scenario. The audio was choppy and sometime with echo, but is acceptable.
Comment 12•10 years ago
|
||
Flags: needinfo?(mbarone976)
Updated•10 years ago
|
Status: REOPENED → RESOLVED
Closed: 10 years ago → 10 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•