problem with webrtc versus Janus which operates through a proxy

45 views
Skip to first unread message

Rani Yaroshinski

unread,
Dec 2, 2021, 11:51:44 AM12/2/21
to meetecho-janus
I am using a "middle man" I wrote to make the commands versus Janus for my peer.
For some reason when I am getting the SDP answer ,
I am trying to start the DTLS session with webRTC, and I keep getting the problem :

[ERR] [ice.c:janus_ice_setup_remote_candidates:3437] [1265735458241831] No remote candidates for component 1 in stream 1: was the remote SDP parsed?


I wonder why does Janus-Gateway "think" that I haven't parsed the SDP ?

Is it a requirement from Janus-Gateway that the SDP will come directly to the peer from it ?


Regards,

Rani

Alessandro Toppi

unread,
Dec 3, 2021, 6:22:11 AM12/3/21
to meetecho-janus
> Is it a requirement from Janus-Gateway that the SDP will come directly to the peer from it ?

No, it isn't.

Lorenzo Miniero

unread,
Dec 3, 2021, 11:01:51 AM12/3/21
to meetecho-janus
Il giorno giovedì 2 dicembre 2021 alle 17:51:44 UTC+1 rani.yar...@gmail.com ha scritto:
I am using a "middle man" I wrote to make the commands versus Janus for my peer.
For some reason when I am getting the SDP answer ,
I am trying to start the DTLS session with webRTC, and I keep getting the problem :

[ERR] [ice.c:janus_ice_setup_remote_candidates:3437] [1265735458241831] No remote candidates for component 1 in stream 1: was the remote SDP parsed?


I wonder why does Janus-Gateway "think" that I haven't parsed the SDP ?


It's not wondering anything like that at all. It's asking itself if *it* (Janus) has parsed your SDP, as that sometimes contains candidates too and it can't find any. As I already told you on github (please stop asking the same things over and over in multiple locations) check the Admin API.

L.
Reply all
Reply to author
Forward
0 new messages