1039596 - Loop client does not work on certain networks

Status: RESOLVED WORKSFORME

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

Description

[Diego Wilson [:diego]]

Attachment: Wifi tcpdump

I loaded the latest Loop mobile client as of July 14th [1]. I'm able to set up the FxOS account but the connection fails. I see a "connecting..." spinner that never ends. Logcat and tcpdump attached.

[1] https://github.com/mozilla-b2g/firefoxos-loop-client/commit/9330d3750bde85b21b21e11ff24d04578f70428f

Comment 1

[Diego Wilson [:diego]]

Attachment: Wifi logcat

Comment 2

[Diego Wilson [:diego]]

I will try out 3G network next to rule out setup or device specific issues.

Comment 3

[Mark Banner (:standard8)]

Moving to Firefox OS product, as that's where the Loop Client for the OS is handled.

Comment 4

[Dan Mosedale (:dmosedale, :dmose)]

We used to see this generically (not just with loop) long ago.  There were certain Wifi networks that completely blocked WebRTC; Mozilla-Guest was one of them.

Comment 5

[Diego Wilson [:diego]]

Attachment: 3G data tcpdump

Comment 6

[Diego Wilson [:diego]]

Attachment: 3G data logcat

Comment 7

[Diego Wilson [:diego]]

I tested on AT&T 3G data (HDSPA). Now the phone at least can find each other, but the call still failed.

The get an "incoming call" screen on the receiving end, but the calls fails as soon as I accept it. Logs attached.

Comment 8

[José Antonio Olivera Ortega [:jaoo]]

Try the code at [1] and let us know please. Calls should be working, try the wifi network you have been testing with lately.

[1] https://github.com/jaoo/firefoxos-loop-client/tree/call-progress-protocol-disabled

Comment 9

[José Antonio Olivera Ortega [:jaoo]]

Mmm I see [1] in the WiFi logs attached, we fixed that issue in bug 1036857. You sure you are running the latest version of the app?

[1] E/GeckoConsole( 1442): [JavaScript Error: "TypeError: attention is null" {file: "app://loop.dev.mozaws.net/js/helpers/call_screen_manager.js" line: 32}]

Comment 10

[Diego Wilson [:diego]]

Jaoo,

I tried your branch [1]. The receiving phone does get a call, but I get this message at the top of the screen while the connection is attempted "The stream was unable to connect due to a network error. Make sure your connection isn't locked by a firewall". I see this message both on my work wifi network and the AT&T 3G data network.

I'm attaching logcat/tcpdump logs

[1] https://github.com/jaoo/firefoxos-loop-client/tree/call-progress-protocol-disabled

Comment 11

[Diego Wilson [:diego]]

Attachment: jaoo branch logcat

Comment 12

[Diego Wilson [:diego]]

Attachment: jaoo branch tcpdump

Comment 13

[José Antonio Olivera Ortega [:jaoo]]

(In reply to Diego Wilson [:diego] from comment #10)

> I tried your branch [1]. The receiving phone does get a call, but I get this
> message at the top of the screen while the connection is attempted "The
> stream was unable to connect due to a network error. Make sure your
> connection isn't locked by a firewall".

Oh, that's a step forward! It seems the call progress protocol cannot work in the wifi network you were testing. The firewall issue is being tracked on bug 1039188.

It would be super useful you to test the latest code at master branch and switch to another different WiFi network. Could you do it please? Thanks!

I'll talk to the Loop server guys so they might know about the call progress protocol (which is websocket-based) issue for some WiFi networks as yours.

Comment 14

[Diego Wilson [:diego]]

Progress!

From my home network I'm able to complete a full video/audio call with fxaccounts using jaoo/call-progress-protocol-disabled branch. It still fails to connect with mozilla-b2g/master.

Comment 15

[José Antonio Olivera Ortega [:jaoo]]

Talked to :natim on IRC about it. We are going to take care of this issue by adding a fallback to the websocket communication mechanism for the call progress protocol. See bug 1040702 please.

Comment 16

[Maria Angeles Oteo (:oteo)]

(In reply to Diego Wilson [:diego] from comment #14)

> 
>  It still fails to connect with mozilla-b2g/master.

Hi Diego, just to clarify, when you say that it fails with mozilla-b2g/master, do you mean it fails with the master branch of https://github.com/mozilla-b2g/firefoxos-loop-client?

Comment 17

[Diego Wilson [:diego]]

(In reply to Maria Angeles Oteo (:oteo) from comment #16)
> (In reply to Diego Wilson [:diego] from comment #14)
> 
> > 
> >  It still fails to connect with mozilla-b2g/master.
> 
> Hi Diego, just to clarify, when you say that it fails with
> mozilla-b2g/master, do you mean it fails with the master branch of
> https://github.com/mozilla-b2g/firefoxos-loop-client?

Yes

Comment 18

[José Antonio Olivera Ortega [:jaoo]]

Taking this as per comment at https://bugzilla.mozilla.org/show_bug.cgi?id=1040702#c3

Comment 19

[Mandyam Vikram]

It would be most productive for us to use  https://github.com/mozilla-b2g/firefoxos-loop-client

Please keep us posted on updates to this and when it should be ready for us to be tested.

Comment 20

[José Antonio Olivera Ortega [:jaoo]]

The plan I have in mind for this is to add to the client the logic it needs to be able of continuing with the call even when the websocket connection for the call progress protocol dance fails. On the other hand I talked on the IRC to Alexis [:alexis] about what might be cause the websocket connection failure. I pointed out a possible reason regarding the nginx configuration. We will continue debugging this to figure out what's going on.

Comment 21

[José Antonio Olivera Ortega [:jaoo]]

Hey Diego, could you give a try with the latest code at [1] and let us know please? The server is now behind ssl. Thanks!

Comment 22

[Diego Wilson [:diego]]

I just tested the latest as of this morning [1].

I still can't make a call on either my office network or the AT&T 3G data network.

In my office wifi I see an incoming call on the receiving end, by call fails to establish.

On the AT&T 3G data network I don't even see an incoming call.

I'm updating the logcat logs, but the tcpdump command [2] doesn't show anything anymore 

[1] https://github.com/mozilla-b2g/firefoxos-loop-client/commit/72448519db27ed0b07c70574acb223b179229758
[2] adb shell tcpdump -s 0 -A -l host loop.dev.mozaws.net

Comment 23

[Diego Wilson [:diego]]

Attachment: 3G data logcat

Comment 24

[Diego Wilson [:diego]]

Attachment: Wifi logcat

Comment 25

[Diego Wilson [:diego]]

Has Loop mobile been tested on any 3G data network by anyone else?

Comment 26

[José Antonio Olivera Ortega [:jaoo]]

(In reply to Diego Wilson [:diego] from comment #22)
> I still can't make a call on either my office network or the AT&T 3G data
> network.

I see in the logs that the websocket connection issue we had is not happening anymore. This is good news.
 
> In my office wifi I see an incoming call on the receiving end, by call fails
> to establish.

I see in the logs that everything seems to be right. The call progress protocol could drop the call if it takes too much time to establish. You should try another time until it establishes as It seems everything is correct. Maybe we should enable some logs for the call progress protocol.

> On the AT&T 3G data network I don't even see an incoming call.

It should works as well.

> I'm updating the logcat logs, but the tcpdump command [2] doesn't show
> anything anymore 

This is because the server url is now https://loop-dev.stage.mozaws.net

(In reply to Diego Wilson [:diego] from comment #25)
> Has Loop mobile been tested on any 3G data network by anyone else?

Yes, it has. It has been tested by us and it works on TEF cellular network.

Comment 27

[Daniel Coloma:dcoloma]

(In reply to Diego Wilson [:diego] from comment #25)
> Has Loop mobile been tested on any 3G data network by anyone else?

3g issue might be due to not having bug 1042873 landed in 2.0 when you created the build. Is that the case?

Comment 28

[Diego Wilson [:diego]]

Finally a successful call on my office network!

In fact, I have H.264 WebRTC enabled on my phones and that worked fine. So in case you were wondering, the Loop mobile app works well with hardware accelerated H.264 video.

3G data still fails during the connection set up. Sometimes I see the feedback screen as soon as I accept the call. Sometimes it just keeps spinning indefinitely while connecting.

I'm using the latest gecko/gaia/loop as of this morning:

Loop: 71e7005bc31b84653dbd03da4c3a597d18251b51
Gecko: cf7a0aebe087f2efb7d20d5575312adb43184d35
Gaia: cfc4d71c36c6e9f6731f2060427f80e2996bc066

Comment 29

[Diego Wilson [:diego]]

Attachment: 3G data logcat

Updated 3G data logcat

Comment 30

[Diego Wilson [:diego]]

Attachment: 3G data tcpdump

Updated 3G data tcpdump

Comment 31

[José Antonio Olivera Ortega [:jaoo]]

(In reply to Diego Wilson [:diego] from comment #28)
> Finally a successful call on my office network!

\o/ Glad it works!

> 3G data still fails during the connection set up. Sometimes I see the
> feedback screen as soon as I accept the call.

Mmm, we increased the connection timer to 10 seconds on bug 1037979 and it should be enough IMHO.

Comment 32

[Diego Wilson [:diego]]

(In reply to José Antonio Olivera Ortega [:jaoo] PTO till 8/18 from comment #31)
> Mmm, we increased the connection timer to 10 seconds on bug 1037979 and it
> should be enough IMHO.

I *did* see a successful connection on AT&T 3G once and only once out of ~20 tries. I also suspect a timing issue.

Comment 33

[Borja Salguero [:borjasalguero]]

Hi Diego! Any update here? I've made some calls without any issue between my 3G & Wifi Firefox OS Devices with O2 UK. Could you try again and give us some feedback? Thanks!

Comment 34

[José Antonio Olivera Ortega [:jaoo]]

IMHO there are not actionable items on this bug, so closing as WORKSFORME. Please repoen it if needed.