You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Table of contents:

  1. General parameters for webrtc app
  2. Our signal server on Java
  3. Native client and MCU server

General parameters for webrtc app

First of all I define a "webrtc" term. Webrtc is a set of APIs for work with:

  • Capturing user media - get stream from camera or microphone via browser
  • RTCPeerConnection api which manage video/audio calls
  • RTCDataChannel api that allows transmit custom data between peers if they already have established connection

Secondly I describe two specials servers for establishing connection between peers.

Mostly devices in the Internet have gray IP addresses. They connect to the Internet via provides.

Providers have a lot of clients and small pool of public (white) IP addresses therefore they assign one public IP on one active client.

It can be done in various ways. This process is called NAT - network address translation. There are two big type of NAT - symmetric and asymmetric.

 

 

There are two servers - STUN and TURN. First is necessary for discovering your public IP address if you have gray address.

For example - you send some special message to the STUN and it responses with your NAT

  • No labels