Alon, I don’t really understand the question here.

WebRTC needs signaling to be able to connect sessions (theoretically, you need signaling to connect anything – not only WebRTC). The only difference between WebRTC and most other VoIP protocols is that WebRTC doesn’t enforce any specific signaling and leaves that part to the implementer.

For example my application have one static point(a cam on a drone with static IP) streaming video to a random Client .

the client can connect thru a mobile app or web browser.

Is it safe to say no signaling no WebRTC ?

I did some tests and searches, I tried using wrtc or webrtc-native but in both cases I can’t get them works getting builded binaries or rebuild them (tried on Debian 8, Ubuntu 14 and 16). It also seems the projects are discontinued and I found only articles having 2-3 years old.

I’m looking for advices about modules or libraries to use, or how to make wrtc or webrtc-native works.

It doesn’t. But it does help in getting the media server connected from wherever it is to the users.

That means that you can place the media server in a more protected accommodations, and being a more complex beast with more angles of attack – it means making it less vulnerable to such attacks.

I guess that a lot of the protection will end up taking place in the signaling that happens in front of the media server, and there, my usual suggestion is having that signaling/control done by the signaling server and not between the media server and the browser/client directly.