Funkcionalnosć tutoho sydła so přez wothladowanske dźěła wobmjezuje, kotrež maja waše dožiwjenje polěpšić. Jeli nastawk waš problem njerozrisuje a chceće prašenje stajić, wobroćće so na naše zhromodźenstwo pomocy, kotrež na to čaka, wam na @FirefoxSupport na Twitter a /r/firefox na Reddit pomhać.

Pomoc přepytać

Hladajće so wobšudstwa pomocy. Njenamołwimy was ženje, telefonowe čisło zawołać, SMS pósłać abo wosobinske informacije přeradźić. Prošu zdźělće podhladnu aktiwitu z pomocu nastajenja „Znjewužiwanje zdźělić“.

Dalše informacije

Tuta nitka je so začiniła a archiwowała. Prošu stajće nowe prašenje, jeli pomoc trjebaće.

Webrtc connection issue from chrome to firefox

  • 1 wotmołwa
  • 1 ma tutón problem
  • 3 napohlady
  • Poslednja wotmołwa wot Moses

more options

In my webrtc video application when there is always a connection issue from chrome to firefox. If the user on Firefox joins first to the room and the 2nd user on chrome joins second then ther is no issue. It connects smoothly. But in the reverse case there is a connection but no audio and video. You can check the app at : https://uc.connectuscom.com/video/#k9EBX8xd#Video

open one instance of this this link on chrome and then another on Firefox to reproduce the issue. Use 2 separate machines to avoid the issue of camera availability for the browsers.

In my webrtc video application when there is always a connection issue from chrome to firefox. If the user on Firefox joins first to the room and the 2nd user on chrome joins second then ther is no issue. It connects smoothly. But in the reverse case there is a connection but no audio and video. You can check the app at : https://uc.connectuscom.com/video/#k9EBX8xd#Video open one instance of this this link on chrome and then another on Firefox to reproduce the issue. Use 2 separate machines to avoid the issue of camera availability for the browsers.

Wšě wotmołwy (1)

more options

Hi,

You posted two questions on the same topic. Seems like you pressed Post twice. Please continue at /questions/994533. I'll be closing this thread.