1. Yes. In a way… to operate, such media servers have a demo/reference application or even a full fledged client. To run, they need signaling which is offered then by the media server framework itself. In most cases, my suggestion would be not to use that for a serious application as it lacks a lot of the logic you are going to need which is outside the scope of the video call itself.

2. Through the server, for the simple reason that a Kurento Media Server was developed to act like a media server…

3. Yes, but don’t expect it to offer good experience for a group video call.

4. Yes, as far as I know.

I am new to this webRTC and have few basic question which i am struggling to understand. I would really appreciate if you help me understand these.
1. webRTC/Kurenot/OpenVidu, all of these provides the framework with webRTC functionalities. But none provide the Signaling server and it has to be developed separately, is that right?
2. In my understanding, the Application developed (web/mobile app) based on webRTC, will have client side (developed mostly in Java) and then the WebRTC FW, which will provide the RTP Stack. Then these clients will talk to the signaling server which is somewhere in the cloud to contact the other peer. Once this is through, then the clients can communicate directly (peer-peer) using the RTP.
Now the question is, Kurento talks about the Kurento Media Server (KMS) and the media flows through it to the other peer. Why ?
3. Can we develop the peer to peer communication without the media server in between ?
4. Does OpenVidu provides the Signaling Server ?

Thanks,
Santosh

Georgi, thanks for sharing.

Can you please elaborate how has this combination been working for you?

I also would like to see Go more in the communication environment, there is a WebRTC server developed by a former googler in GitHub but very basic, just supporting the Data Channel, and a couple of SIP libraries but I didn’t find anything more.

Well… PHP will usually be used as the application server, connecting it to a signaling server which predominantly will be based on Node. I am sure that someone figured out how to PHP his way to WebRTC.

Go is something I’ve seen discussed but never used with WebRTC. Would like to see it adopted more as well.

IMO Go is probably one of the best options these days for a signaling server (a mix with the best parts of python, c and erlang). And in the JVM side Java or Scala with one of the cool frameworks (Akka, vert.x…)

Oops. Sorry for missing that one – you should probably update your documentation a bit to be more clear about this as well.

Will fix this article to fit.