What is the technical difference between webRTC and VoIP communication

Can anyone help me on what is the technical difference between WebRTC communication and VoIP communication?

+3


source to share


3 answers


The question doesn't make much sense as it makes the assumption that VoIP is a technical stack, but it's not a concept. The concept of sending voice (V) over (o) Internet protocols (IP). This means that various technologies can be used to access / grab media, establish connections, negotiate streams, and transfer streams.



WebRTC is one such stack (set of APIs, methods and standards) for VoIP.

+8


source


VOIP - Voice over Internet Protocol was a concept that came with popularity on the Internet. This is due to the use of the Internet for the transmission of voice telephony data, mainly using the existing IP infrastructure for the transmission of audio streams without dedicated circuit switched telephony. Over time, popular VOIP applications have emerged such as Skype, Vonage and many in corporate telephony. VOIP had two parts: one signaling, mostly a controller part and other actual media. The actual media is usually, but not necessarily, RTP (Real Time). RTP can carry voice and video. The problem with RTP is that browsers don't natively support it, and it's not secure. Usually you need some kind of plugin for VOIP to work inside the browser.



Currently, the popular WebRTC browsers such as FF, Chrome and Opera, there is an RTP variant that is secure and can be invoked natively. Using WebRTC and Javascript browser you can send Voice, Video and Screen data (this is video only) to any other browser, which is very cool.

+3


source


VOIP: Voice over Internet Protocol uses DSL / Cable Modem Voice over Wi-Fi / 3G (VoWiFi / 3G), Voice over LTE (VoLTE) and Rich Communication Suite (RCS). VoIP is cloudy, calls are sent as digital data, and no cables are required to make a call, so any Internet connection can be used to make calls and from a variety of devices.

The RTC Web-: . Only OS browsers use real-time messaging. WebRTC requires the use of two main JavaScript APIs.

WebRTC is a VoIP browser extension. It can reuse existing VoIP infrastructure with incremental updates. This is good news for VoIP as the implementation of WebRTC only serves to increase the overall adoption of VoIP.

Additionally, WebRTC is ideal for low-cost, browser-based contact center applications. VoIP can serve carrier-controlled VoLTE applications. Hence, between WebRTC and VoIP, they can support a wide variety of consumer and enterprise applications.

+1


source







All Articles