webRTC - what are the tcp and udp ports, port ranges used, in case firewall/router it need to be set

[SProgrammer]

I have many scenario where webRTC simply does not working for the audio/video and signaling tried with turn/stun/ice servers.

To be sure its firewall/nat issue. Can anyone please let me know what are the ports that webRTC is using for audio/video/signaling?

[Alexandre GOUAILLARD]

Have you checked the peer connection "signalingState" and "iceConnectionState" to be sure you are stuck by a firewall/nat issue? ( are you stuck at "checking" ice state, or "connected" ice state with no audio or video streaming through? ).

The ports and IP are provided in the ice candidate themselves, which are either in the offer/answer SDPs for full ICE (firefox) or send offhand for trickle ICE (chrome). If the ice state is "connected" the port and ip used will be visible in chrome://webrtc-internals. Depending on BUNDLE/rtcp-mux presence in the offer/answer, there will be one, two or four ports for one audio/video stream.

On Thu, Nov 28, 2013 at 10:41 PM, SProgrammer <sha...@companysocia.com> wrote:

I have many scenario where webRTC simply does not working for the audio/video and signaling tried with turn/stun/ice servers.

To be sure its firewall/nat issue. Can anyone please let me know what are the ports that webRTC is using for audio/video/signaling?

--
 
---
You received this message because you are subscribed to the Google Groups "discuss-webrtc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrt...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Alexandre GOUAILLARD]

since, you don't answer,

and since the problem seems to have been solved,

I'll complement this thread for all those that will end up here after a search.

It looks like the culprit was not webRTC, but the installation of configuration of the TURN server.

https://groups.google.com/forum/#!topic/turn-server-project-rfc5766-turn-server/rQoAZoQyBBw

please disregard the "to be sure its firewall/nat issue" reported earlier.