On Wednesday, February 28, 2018 at 12:08:54 AM UTC+5:30, Lorenzo Miniero wrote: > Il giorno martedì 27 febbraio 2018 18:45:50 UTC+1, Nils Ohlmeier ha scritto: > > 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 > > > > > On Feb 24, 2018, at 11:48, Rhythm Chopra <[email protected]> wrote: > > > > > > 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 > > > _______________________________________________ > > > dev-media mailing list > > > [email protected] > > > https://lists.mozilla.org/listinfo/dev-media > > > Hi Nils, > > 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
Yeah, The issue is resolved now. Thanks _______________________________________________ dev-media mailing list [email protected] https://lists.mozilla.org/listinfo/dev-media
