Network and Firewall
- 09 Sep 2024
- 1 Minute to read
- Print
- DarkLight
- PDF
Network and Firewall
- Updated on 09 Sep 2024
- 1 Minute to read
- Print
- DarkLight
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
Each Endpoint Client (EPC) and Endpoint Hub (EPH) connect to the centralised controller and establish a secure TCP control connection.
| Source | Destination | Protocol | Traffic Direction | Remarks |
|---|---|---|---|---|
| EPC | Controller | TCP 443 | Outbound | Controller control/test result connection using AES-256 encryption |
| EPH | Controller | TCP 443 | Outbound | Controller control/test result connection using AES-256 encryption |
Tests are schedule by the controller which informs a source Endpoint (EPC or EPH) what the destination endpoint is and the type of test to perform. Equally the controller informs the destination endpoint (EPC or EPH) that at test is scheduled to be run against it. Once tests are completed the results are send from both endpoints involved in the test back to the controller over the endpoint -> controller secure connection established previously.
For P2P tests, test traffic flows directly between the Endpoints:
| Source | Destination | Protocol | Traffic Direction | Remarks |
|---|---|---|---|---|
| EPC | EPH | UDP 29999 | Outbound | P2P network test |
For VoIP tests, test traffic flows directly between the Endpoints. A VoIP call is established between the source and destination endpoints using the standard Session Initiation Protcol (SIP) and then bidirectional audio data passes between them using the standard Realtime Protocol (RTP):
| Source | Destination | Protocol | Traffic Direction | Remarks |
|---|---|---|---|---|
| EPC | EPH | TCP 5060 (SIP) | Outbound | Session Initiation Protocol |
| EPC | EPH | UDP 30000-50000 (RTP) | Outbound | Realtime Protocol (audio from source) |
| EPH | EPC | UDP 30000-50000 (RTP) | Outbound | Realtime Protocol (audio to source) |
Was this article helpful?