This section describes, in a technical and objective way, the communication flow when a user selects a POS to view video.
The browser sends an HTTPS request to the platform, where the following occurs:
The platform returns:
At this point, the platform acts only as a control and orchestration layer.
The browser initiates a direct connection with the store’s local server (EASiCash / Janus) using WebRTC.
This step involves:
The store server maintains a continuous connection with the DVR/NVR.
Note:
The server sends the video to the browser in real time via WebRTC.
Browser → Platform (control)
Browser ↔ Store Server (media)
Server → DVR → Camera (video source)
The platform does not participate in media transmission, only in the initial signaling.
| Source | Destination | Function |
|---|---|---|
| Browser | easi.live | Authentication and signaling |
| Browser | Store Server | Video reception (WebRTC) |
| Store Server | DVR/NVR | Continuous stream consumption |
| DVR/NVR | Cameras | Video source |
Typical flow:
Browser → Store Server (private network/VPN)
When a direct (peer-to-peer) connection cannot be established, traffic may be routed through a TURN server.
Note:
Flow with TURN:
Browser → TURN → Store Server
When selecting a POS, the browser uses the platform only for control and signaling.
Video transmission occurs directly between the store server and the browser whenever possible.
In scenarios where a direct connection is not feasible, TURN ensures communication, but with increased latency.