Web Real-Time Communication (WebRTC) technology permits real-time media and data exchange between browsers. A connection is proven via a detection procedure named signalling. However, signalling has no exact definition in WebRTC. This paper aims to design and implement WebRTC chat, video communication, and recording between peers (browserto-browser) in the real application using Chrome and Firefox based on mesh topology. Thus, a signalling channel between two peers for chat and video conferencing using the following: Socket.io mechanism, Node.JS platform, and Express.JS has been produced and performed. Including, Axios (HTTP JSON), and JavaScript as the main programing language utilised. The results of this work have ensured that a signalling channel has been built and implemented. Keywords: Web Real-Time Communication (Webrtc); Session Description Protocol (SDP); Socket.Io Protocol; Node. JS, Javascript (JS); Local Area Network (LAN)

To connect with user media devices such as microphones and cameras, browsers formerly required Flash. Flash has essentially replaced Web Real-Time Communication (WebRTC) in recent years. The principles of WebRTC have not agreed on how browsers can capture audio, video, and data or screens. The major purpose of this research is to create a new WebRTC recording method that uses Google Chrome and Firefox to capture a mixture of cameras, microphones, and screens. In addition, this study used Software Engineering (SE) concepts such as the software design process and interface design, which is the description of a system's relationships with its environment, including the analysis and development of the designed systems. The MultiStreamsMixer.js libraries were used to design and implement a mixer of many cameras, microphones, and screens using the Ethernet and Wireless of the 4th generation (4G) network. The suggested technique also makes use of the JavaScript Library to capture audio, video, and screen (two-dimensional and three-dimensional animations); as well as numerous audio and video codecs, such as VP8 and VP9 for video and Opus for audio, were also utilized in Chrome and Firefox. Additionally, multiple bitrates ranging from 100 bytes per second to 1 Gigabit per second were also tested. Besides, various resolutions ranging from 480p to HD (3840* 2160) and frame rates ranging from 5 to 70, increasing by 5% each time were applied. In addition, the recording device, Quality of Experience (QoE) over real operators, and resources were evaluated.