Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Beginner
1 View

blank screen cross browsers

Recently I started testing cross browsers to see how they respond and with and without NAT setup. I noticed an issue with both chrome and firefox that most of the time, the screen on the joining stream stays blank and does not display the stream right away, it takes almost a min or more to start displaying stream and sometimes it stays blank permanently. Also on Android phones, on both firefox and chrome, it always stays blank but it does send the streams to PCs. Also behind a firewall, firefox works but chrome stays blank.

Do others get the same response as I am? Below is the log and I see lots of FIR packets getting created when 2nd stream joins and stays blank for a while.

Erizo LOG:

2015-05-16 20:52:55,345  - INFO: NiceConnection - remote candidate addr: 66.215.192.231:54667

2015-05-16 20:52:55,345  - INFO: DtlsTransport - video - Nice ready

2015-05-16 20:52:55,346  - INFO: DtlsTransport - video - DTLSRTP Start

2015-05-16 20:52:55,585  - INFO: WebRtcConnection - Update Transport State video to 2

2015-05-16 20:52:55,587  - INFO: WebRtcConnection - Ready to send and receive media

2015-05-16 20:52:55.588  - INFO: ErizoJSController - webrtc Addon status103

2015-05-16 20:52:55,586  - INFO: WebRtcConnection - Update Transport State video to 2

2015-05-16 20:52:55,589  - INFO: WebRtcConnection - Ready to send and receive media

2015-05-16 20:52:55.591  - INFO: ErizoJSController - webrtc Addon status103

2015-05-16 20:52:55,710  - DEBUG: mcu.media.VideoMixer - addSource - assigned input index is 1

2015-05-16 20:52:55,715  - DEBUG: mcu.media.VideoMixer - onInputProcessorInitOK - index: 1

2015-05-16 20:52:55,828  - DEBUG: mcu.media.VideoLayoutProcessor - addInput, input: 1

2015-05-16 20:52:55,828  - DEBUG: mcu.media.SoftVideoCompositor - Configuring layout

2015-05-16 20:52:55,828  - DEBUG: mcu.media.SoftVideoCompositor - configChanged is true

2015-05-16 20:52:55,955  - DEBUG: mcu.media.SoftVideoCompositor - commit customlayout

2015-05-16 20:52:56,067  - DEBUG: mcu.media.SoftVideoCompositor - configChanged sets to false after commitLayout!

2015-05-16 20:53:01,979  - DEBUG: WebRtcConnection - Generating FIR Packet

2015-05-16 20:53:02,940  - DEBUG: WebRtcConnection - Generating FIR Packet

2015-05-16 20:53:03,423  - DEBUG: WebRtcConnection - Generating FIR Packet

2015-05-16 20:53:03,783  - DEBUG: WebRtcConnection - Generating FIR Packet

2015-05-16 20:53:03,892  - DEBUG: WebRtcConnection - Generating FIR Packet

2015-05-16 20:53:03,902  - DEBUG: WebRtcConnection - Generating FIR Packet

2015-05-16 20:53:04,012  - DEBUG: WebRtcConnection - Generating FIR Packet

2015-05-16 20:53:04,741  - DEBUG: WebRtcConnection - Generating FIR Packet

2015-05-16 20:53:04,860  - DEBUG: WebRtcConnection - Generating FIR Packet

2015-05-16 20:53:05,459  - DEBUG: WebRtcConnection - Generating FIR Packet

2015-05-16 20:53:05,824  - DEBUG: WebRtcConnection - Generating FIR Packet

Tags (2)
0 Kudos
15 Replies
Highlighted
1 View

Hi Farrukh,

Hi Farrukh,

Thanks for the detailed information. But can you tell us the problems you discovered with TURN/STUN servers or without them?

0 Kudos
Highlighted
Beginner
1 View

Configuration is done with

Configuration is done with TURN/STUN server locally installed on the same system. Just to clarify what I said earlier

1) Chrome to Chrome = Works perfectly

2) 1st stream - Chrome, 2nd stream Firefox = Chrome display's both, Firebox blank

3) 1st stream Firefox, 2nd stream chrome = Firefox display's both, Chrome blank

4) 1st stream directly, 2nd stream Behind a firewall, firefox display's both, chrome blank

Regards

 

 

 

 

0 Kudos
Highlighted
Beginner
1 View

Chunbo, 

Chunbo, 

I would like to know what is your experience with cross browser streams? I have noticed in both chrome and firefox, 2nd system/stream stays black for almost 2 mins every time and then starts showing. Do you know how can I debug it?

Also I created a new m1.medium instance in aws, because I thought it might be due to cpu/memory but it had the exact same problem. Can you please help or guide me how to debug. Appreciate it.

Regards

 

0 Kudos
Highlighted
1 View

Hi Farrukh,

Hi Farrukh,

Can you tell us the browser versions you're using? Since our QA team are also continue testing the compatibility between different browsers... Thanks!

According to some previous cases, some of cross browser issues are caused by the SDP negotiation between those browsers (source code) and MCU server (source code). As you may know, nowadays Chrome and Firefox evolve rapidly regarding WebRTC technology... 

0 Kudos
Highlighted
1 View

HI Farrukh,

HI Farrukh,

I might need more information:

1. What's the MCU version you're testing with?

2. Is your TURN/STUN server deployed on the same machine as the MCU? Just to confirm...

3. The browser versions you're using?

0 Kudos
Highlighted
Beginner
1 View

Chunbu,

Chunbu,

you are abs right about SDP negotiations. I even tested peer to peer example and latest firefox and Chrome stops on negotiations using peercall.html.  If possible, please try it on your server as well.

MCU version is 2.1.1

TURN/STUN installed locally on the same machine

Chrome Version 43.0.2357.65 (64-bit), firefox 38.0.1

Regards

 

0 Kudos
Highlighted
1 View

Thanks a lot for the

Thanks a lot for the information and your valuable investigation! We're now actually dealing with both conference and p2p cases.

Will keep you updated!

0 Kudos
Highlighted
1 View

Another thing is the P2P

Another thing is the P2P conversation between Firefox and Chrome should use peercallff.html.

0 Kudos
Highlighted
Beginner
1 View

Dear Chunbo,

Dear Chunbo,

   I have tried peercall.html on chrome 43 side and peercallff.html on firefox 38.0.1 side. In this scenario Firefox was able to do start video chat with chrome but when you press "start video sharing" on chrome, it stops at negotiations as shown in attached picture. Let me know what could be the reason behind it?

Regards

 

0 Kudos
Highlighted
1 View

Hi Farrukh,

Hi Farrukh,

As I mentioned above, "Another thing is the P2P conversation between Firefox and Chrome should use peercallff.html.", which means peercallff needs to be used for both sides when Firefox gets involved.

0 Kudos
Highlighted
Beginner
1 View

Hello Chunbo,

Hello Chunbo,

 Thank you for your help. As you mentioned, if I use peercallff.html on both chrome and firefox, it does work.

As I requested earlier, if your team can look at MCU scenarios I mentioned earlier where 2nd stream browser takes a while to show the stream. Is there a solution for that? Thank you for your help.

Regards

 

0 Kudos
Highlighted
1 View

We're working on the

We're working on the following issues you mentioned. Thanks.

Farrukh M. wrote:

Configuration is done with TURN/STUN server locally installed on the same system. Just to clarify what I said earlier

1) Chrome to Chrome = Works perfectly

2) 1st stream - Chrome, 2nd stream Firefox = Chrome display's both, Firebox blank

3) 1st stream Firefox, 2nd stream chrome = Firefox display's both, Chrome blank

4) 1st stream directly, 2nd stream Behind a firewall, firefox display's both, chrome blank

0 Kudos
Highlighted
Beginner
1 View

Chubo,

Chubo,

  Can you please provide an update if any? Appreciate it.

Regards

0 Kudos
Highlighted
Beginner
1 View

Is this issue already resolve

0 Kudos
Highlighted
1 View

Hi there,

Hi there,

We're currently on those cross-browsers issues, especially with the latest Firefox.

Thanks for your patience. Stay tuned!

0 Kudos