Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Can't view WebRTC stream from Janus WebRTC Gateway in Firefox
314 views
Skip to first unread message
Rhythm Chopra
Feb 25, 2018, 10:52:27 PM2/25/18
to mozilla-...@lists.mozilla.org
I need to RTP media stream coming from Gstreamer over Web Browser, so I am using Janus WebRTC Gateway for the same. Media stream appears fine in Chrome, but when I try to view the same stream in Firefox, it can't view any stream, moreover the console throws me an error `ICE failed, add a TURN server and see about:webrtc for more details`. On debugging Janus, thorough its Admin API, I figured out that Firefox can't get Remote SDP, whereas Chrome get it. SDP Session state in firefox stays at `gathering` forever, but as soon as it changes to `ready` in Chrome, the stream appears.
Following are the Session logs for Chrome and FireFox:
Session Logs for Chrome: https://pastebin.com/WEkMj5DW
Session Logs for Firefox: https://pastebin.com/wmM6YKJK
On further debugging, I found out that answer created for SDP negotiation by RTCPeerConnection.createAnswer() returns the answer with attribute `rtpmap:120 VP8/90000` whereas, my stream is `H264/90000` encoded. Is there a way I can create a valid answer for SDP negotiation for H264 encoded stream.
Please suggest.
Regards,
Rhythm
Following are the Session logs for Chrome and FireFox:
Session Logs for Chrome: https://pastebin.com/WEkMj5DW
Session Logs for Firefox: https://pastebin.com/wmM6YKJK
On further debugging, I found out that answer created for SDP negotiation by RTCPeerConnection.createAnswer() returns the answer with attribute `rtpmap:120 VP8/90000` whereas, my stream is `H264/90000` encoded. Is there a way I can create a valid answer for SDP negotiation for H264 encoded stream.
Please suggest.
Regards,
Rhythm
Nils Ohlmeier
Feb 27, 2018, 12:45:50 PM2/27/18
to Rhythm Chopra, mozilla-...@lists.mozilla.org
Hi Rhythm,
I’m not an expert in reading Janus logs, but I noticed two differences in the logs you provided.
- In the Chrome log I see two ICE candidates from Janus, one for 192.168.x.x and one for 43.224.x.x.x. But in the Firefox log I only see the non-routable ICE candidate for 192.168.x.x. This would explain why ICE connection can’t get established. I would recommend to find out why in the Firefox case there is no public IP ICE candidate.
- In the Chrome log I see a local SDP (sips -> local) and remote SDP (spds -> remote). But in the Firefox log the remote SDP is missing. Without the remote SDP the ICE connection and DTLS won’t get established. This is the first problem I would try to debug/solve.
Best regards
Nils Ohlmeier
> _______________________________________________
> dev-media mailing list
> dev-...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-media
I’m not an expert in reading Janus logs, but I noticed two differences in the logs you provided.
- In the Chrome log I see two ICE candidates from Janus, one for 192.168.x.x and one for 43.224.x.x.x. But in the Firefox log I only see the non-routable ICE candidate for 192.168.x.x. This would explain why ICE connection can’t get established. I would recommend to find out why in the Firefox case there is no public IP ICE candidate.
- In the Chrome log I see a local SDP (sips -> local) and remote SDP (spds -> remote). But in the Firefox log the remote SDP is missing. Without the remote SDP the ICE connection and DTLS won’t get established. This is the first problem I would try to debug/solve.
Best regards
Nils Ohlmeier
> dev-media mailing list
> dev-...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-media
Lorenzo Miniero
Feb 27, 2018, 1:38:54 PM2/27/18
to mozilla-...@lists.mozilla.org
he discussed the issue on discuss-webrtc as well, and it turned out he was misconfiguring the Janus Streaming mountpoint, which caused the SDP not to contain a valid fmtp attribute for H.264.
Lorenzo
Rhythm Chopra
Feb 28, 2018, 8:37:41 AM2/28/18
to mozilla-...@lists.mozilla.org
The issue is resolved now.
Thanks
0 new messages