Skip to main content

QUANTEEC WebRTC Requirements

In order to work, the P2P solutions of Quanteec have the following requirements.

Network requirements​

  1. The devices MUST allow WebSocket connections to controller-ws.quanteec.com, HTTPS/TCP on port 443. This port is used to connect to the Quanteec Controller that validates and provides the authorization for the peers to create connections with other peers.

  2. In order to support direct P2P connections between devices, the devices MUST allow WebRTC P2P traffic towards other peers by opening UDP ports 49152 to 65535.

note

The 2nd requirement can be an issue for eCDN use cases in secured networks where the ports are closed by default. One solution in such scenarios is to deploy a TURN server as a relay inside of the secured network. Then, the users should be allowed to connect to the TURN server through one port (for example, 3478/TCP). The TURN server will then be used as a relay between all of the connections, allowing fine-grained controls. Be sure to have enough bandwidth available to your TURN server because all of the P2P traffic will navigate through the relay.

Browser requirements​

  1. The browsers MUST have WebRTC and DataChannels activated. This is true by default, so if WebRTC has not been specifically deactivated, nothing needs to be done for this requirement.

  2. The browsers MIGHT need to disable mDNS. The protocol mDNS is used by default to mask the IP address of the devices.