GitLab

I hope this is the right place to rise the issue.

I've developed a small webrtcbin wrapper (based on webrtc-sendrecv.c) for Janus-GW including basic janus stuff.

Everything works quite well whenever both Janus and webrtcbin client run on the same subnet. On the other hand, I cannot manage to make it work if there's any NAT in between. It doesn't look like a problem with Janus, as far as I can manage to run the js demos samples without any problem.

You can find here one gist with two logs (both situations) 1-trace_jaanus_local_NET_ok.log 2-trace_janus_aws_ko.log

https://gist.github.com/jmorgade/4e7716fd2b1c91ca6563336b22f5d567

I don't quite understand where is the problem ... trickle negation and main steps work exactly equally in both cases but it gets stacked at bellow stage when Janus is running on i.e AWS sever. Actually, it never starts the dtls handshake.

0:00:10.112729724 [332m23713[00m 0x1a0d5e0 [37mTRACE [00m [00m webrtcbin gstwebrtcbin.c:884:_collate_peer_connection_states:[00m ICE connection state: 0x8. DTLS connection state: 0x1 0:00:10.112737291 [332m23713[00m 0x1a0d5e0 [37mTRACE [00m [00m webrtcbin gstwebrtcbin.c:947:_collate_peer_connection_states:[00m returning new

I miss many details about gstreamer webrtc implementation so any hint or suggestion where to debug ... would be really welcome