Are there any friends involved in video calls based on WEBRTC and HTML5? -

WEBRTC reply content: I am in development and have a basic understanding of the WebRTC source code stack. It mainly consists of two key technologies: 1. webRTC Video/Voice Engine, including camera microphone operations, Video preprocessing, VP8 coding/decoding, and streaming media transmission (RTP/RTCP); 2. implement the P2P channel and use libjingle to completely implement the ICE, STUN, and TURN protocols to provide P2P communication capabilities. A set of JS APIs, including getUserMedia and peerconnection, are defined. You can use a few steps to implement the video call function. In addition, the PeerConnection DataChannel function is also provided, that is, not only to transmit multimedia data, but also to user-defined data, which is also very important.
Whether WebRTC can be fully compatible with various browsers still takes time. The key is that Microsoft's IE and VP8 Codec are two "political" issues. However, WebRTC's functionality is indeed very attractive. It can provide a brand new user experience for IM, streaming media, games (data channels), and applications like monitoring, so as to completely discard desktop software.
The development of WebRTC applications requires a complete solution, including signaling servers, STUN servers and TURN servers, development libraries for mobile phones and web pages, etc. Currently, this is the best technology import period.

Look at our products: http://yacamera.com We have previously prepared the doubango set, WebRTC and SIP, all kinds of pain points. Recently, I want to create a demo of a chrome to Android video. It is very difficult. The Javascript API is not complete yet. Maybe ROAP will change it one day. continue to pay attention to it ~
Chrome dev 19.0.20.1.1 this version directly crash when using the PeerConnection API. Today, I accidentally upgraded it to this version, which is a direct tragedy ~ Some NODEJS + WEBRTC
Https://github.com/baodao/nxfrtc Libjingle + webrtc audio and video can all be used, but it may be necessary to wait. After all, ICE is not a standard for google... I will wait for google to upgrade... Http://www.helome.com The video and audio parts are based on WebRTC. Some progress has been made on compatibility issues, but in general it is a tough nut to crack. I have already implemented the video demo of chrome 2 android, and I am currently working on a platform similar to opentok. You can learn at present, but it is not a good time for production. The whole community, such as supporting both webrtc and sip Softswitch, freeswitch/asterik takes two years to mature. Currently, the discussion and productization of WebRTC in the industry is quite popular, at least our company is working on solutions, and many traditional New Star companies will talk about cooperation and exchange.
Currently, most of the requirements are not limited to P2P applications. Therefore, when we discuss using WebRTC as a product, I personally think it is not limited to the standard-defined P2P model. We need to make products, we need to be able to crop WebRTC and seamlessly integrate with existing products/protocols.

The following is about learning WebRTC,
WebRTC alone does not consider javascript interfaces. It only talks about libjingle. It has benefited a lot from GIPS's media pipeline learning.
Most importantly, it lowers the threshold for expected participation in audio and video streaming media solutions. However, WebRTC is complicated and requires caution in learning. Find the points you want to follow.