Summary

In this chapter we delved into WebRTC design, what infrastructure it requires, and what is similar and what is different from known VoIP.

We understood that WebRTC is only about media, and leave the signaling to the implementor.

Also, we get the specifics of WebRTC, its way of traversing NAT, its omnipresent encryption, and its peer to peer nature.

We witnessed going beyond peer to peer, connecting with the telecommunication world of services that need gateways for transport, protocol, and media translations.

FreeSWITCH is the perfect fit, as a WebRTC server, WebRTC gateway, and also as an application server.

And then we saw how to implement Verto, a signaling born on WebRTC, a JSON web protocol designed to exploit the additional features of WebRTC and of FreeSWITCH, like real time data structure synchronization, session rehydration, event systems, and so on.