|
|
|
|
|
|
by car
2120 days ago
|
|
|
Looks great, now just have to find a counterpart to test it out with. I love the fact that it's native, props for that. I had no idea that people are putting Electron/browser apps out there, yuck. How does signaling between clients work? Is this going to a server you control? And what about encryption, is that enforced by WebRTC per se? Lastly, are you routing calls through TURN servers if NAT tunneling with STUN/ICE fails, or always? I just wish that SIP had taken off. Then we could just call each others email address. Kinda works with FaceTime, except it's Apple's garden. |
|
|
Yes, this is going to my own signaling server. No way around that. The signalling logic is very minimal though and no audio or video data touches the signalling server.
> And what about encryption, is that enforced by WebRTC per se?
In WebRTC, all communication between peers is encrypted once the connection has been established.
> Lastly, are you routing calls through TURN servers if NAT tunneling with STUN/ICE fails, or always?
I do have one TURN server based in SF in case STUN/ICE fails , yes. If I see a lot of usage in other geographies, we'll probably deploy more in different regions.