ECLWebRTC uses the following servers and ports:
- Dispatcher
| Direction | Protocol | Port | Server address | Purpose |
|---|---|---|---|---|
| Client -> Server | TCP(HTTPS) | 443 |
dispatcher.webrtc.ecl.ntt.com |
Get address of signaling server. |
- Signaling server
| Direction | Protocol | Port | Server address | Purpose |
|---|---|---|---|---|
| Client -> Server | TCP(WebSocket,HTTPS) | 443 |
*.webrtc.ecl.ntt.com |
Signaling and client management. |
- STUN server
| Direction | Protocol | Port | Server address | Purpose |
|---|---|---|---|---|
| Client -> Server | UDP | 3478 | stun.webrtc.ecl.ntt.com | Get your own global IP and port number. |
- P2P communication between clients
| Direction | Protocol | Port number | Client address | Purpose |
|---|---|---|---|---|
|
ClientA->ClientB ClientA<-ClientB |
UDP | Dynamic between 1024 and 65535 | Dynamic | P2P data and media communication. |
* If the client can't connect the STUN server, it will give up on connecting P2P and fall back to using the TURN server (see TURN server communication for details)
* If the client can't connecting P2P because there is a proxy server or firewall, please use the TURN server. You can fix the protocol, port number and FQDN.
- TURN server
| Direction | Protocol | Port | Server address | Purpose |
|---|---|---|---|---|
|
ClientA->ClientB |
UDP or TCP | 443 |
turn.webrtc.ecl.ntt.com |
When P2P communication cannot be established, communication is relayed. |
| ClientA<-ClientB | UDP | Dynamic between 1024 and 65535 |
turn.webrtc.ecl.ntt.com |
When P2P communication cannot be established, communication is relayed. |
* If the TURN server can not communicate with UDP via UDP, client B will try to communicate with UDP 443 or TCP 443, just like client A.
* Refer "Show me the IPs of TURN servers." to know the list of TURN servers' IPs.
- SFU server
| Direction | Protocol/Port | Server address | Purpose |
|---|---|---|---|
| Client→Server |
UDP 443 or UDP 10000 or TCP 443 or TCP 10000 |
Dynamic | Media communication. |
* If the client can't connecting the SFU server because there is a proxy server or firewall, please use the TURN server. You can fix the protocol, port number and FQDN.
- Recording control server
| Direction | Protocol | Port number | Client address | Purpose |
|---|---|---|---|---|
|
Client->Server |
TCP(HTTPS) | 443 |
recording.webrtc.ecl.ntt.com *.webrtc.ecl.ntt.com |
Signaling and operation for recording |
- Recording server
| Direction | Protocol | Port number | Client address | Purpose |
|---|---|---|---|---|
|
Client->Server |
UDP | Dynamic between 1024 and 65535 | Dynamic | Media communication for recording |
* If the client can't connecting the SFU server because there is a proxy server or firewall, please use the TURN server. You can fix the protocol, port number and FQDN.
Note: This list may change at any point in the future.
Comments
0 comments
Article is closed for comments.