question regarding ice trickle ports

46 views
Skip to first unread message

Andres Gonzalez

unread,
Jan 4, 2016, 4:56:10 PM1/4/16
to meetecho-janus
Hi,

Using the streaming plugin, I am able to complete the call setup successfully but I am still having issues with the port assignments. I have a couple of question about the ICE candidates. I get the following:

for local candidates:

1 1 udp 2013266431 192.168.1.80 54888 typ host
2 1 udp 1677721855 173.2.140.15 54888 typ srflx raddr 192.168.1.80 rport 54888

for remote candidates:

1268038522 1 udp 2122260223 192.168.1.75 58785 typ host generation 0
3179594414 1 udp 1686052607 173.2.140.15 58785 typ srflx raddr 192.168.1.75 rport 58785 generation 0

As you can see, both the Janus server and the web browser client are on a local network, the server at 192.168.1.80 and the browser on 192.168.1 75

the selected pair are:

1 <-> 1268038522

Question 1: are the port number given in the candidates above the ports for the signaling channel between the local and remote ends?  Or are they media ports?
Question 2: what is the port number the remote browser is expecting to receive video on?  I thought it was the videoport specified in the janus.plugin.streaming.cfg

In that config file I specified a port of 8008 but when I send gstreamer video to 192.168.1.75:8008 I get no media (the in_stats/out_stats for video_bytes is 0)
Likewise if I send gstreamer data to 192.168.75:58785 I get no media.

Thanks,

-Andres


Lorenzo Miniero

unread,
Jan 5, 2016, 4:38:48 AM1/5/16
to meetecho-janus
1. they're media ports; you do signalling and plugin messaging through the Janus API;
2. the video port in the streaming plugin configuration is only the port the *plugin* binds to to receive video from, e.g., gstreamer/ffmpeg, that is to receive whatever needs to be restreamed; it has nothing to do with viewers, that are negotiated as part of a WebRTC PeerConnection elsewhere.

L.
Reply all
Reply to author
Forward
0 new messages