Network Requirements
Firewall settings requirements
Firewall must allow the required connections. The following table shows requirements for basic installation; rules must be specified.
| Protocol | Source | Destination | Port(s) | Usage |
|---|---|---|---|---|
| TCP | * | Server | 80, 443 | Port 80 is needed for Let’s Encrypt. 443 for SSL connection to deployed services |
| TCP | Server | 35.228.17.156 | 443 | If push notification will be used on Android/iOS. Signal server hosted by SSH. |
| TCP | Server | * | 80 | Let’s Encrypt functionality VERIFY |
| TCP & UDP | Server | * | 3478, 5349 | Outbound connection used by TURN server |
| TCP & UDP | * | Server | 3478, 5349 | Inbound connection used by TURN server |
| UDP | Server | * | 40000–40500 | Outbound used by TURN server for TURN connections |
| UDP | * | Server | 40000–40500 | Inbound used by TURN server for TURN connections |
| UDP | Server | * | 30300 | Outbound used for the media traffic by video conferencing system |
| UDP | * | Server | 30300 | Inbound used for the media traffic by video conferencing system |
DNS Required FQDNs
All following records are A-records pointing towards the server where SalaX Secure Messaging will be installed. NAT also needs to be taken into account.
- SalaX Wellknown URL: mydomain.com
- SalaX client URL: chat.mydomain.com
- Admin panel URL: admin.mydomain.com
- MAS URL: account.mydomain.com
- Keycloak URL: auth.mydomain.com
- Homeserver URL: matrix.mydomain.com
- Identity server URL: im.mydomain.com (on old installation it was sshsn-identity.xxx.xxx)
- Homepage URL: share.mydomain.com( for some installations it was home.xxx.xxx)
- Conference URL: conference.mydomain.com
- Turn URL: turn.mydomain.com
- Outlook AddIn: chat.ssh.net and meeting.addin.ssh.net. For airgapped installations, their own chat domain is used and a custom manifest file is provided to them.
Note: Additional subdomains may be utilized depending on the enabled add-on services.
Bandwidth Requirements for Video Conferencing
The Salax Secure Messaging group video conferencing solution is built on top of Jitsi, and the following requirements are based on Jitsi's official recommendations and best practices. While exact bandwidth usage depends on various implementation details and optimizations, the following estimates offer a general guideline based on video resolution:
| Resolution | Estimated Minimum Bandwidth Requirement |
|---|---|
| 180p | 200 kbit/s |
| 360p | 500 kbit/s |
| 720p (HD) | 2.5 Mbit/s |
| 4K | 10 Mbit/s |
Note: The table above shows estimated bandwidth requirements per user based on video resolution. Your actual network requirements will depend on how many users are active at the same time. For example, 20 users streaming 4K video simultaneously would require minimum 200 Mbit/s.
Recommendations
- For production/live deployments use, a 10 Gbit/s connection is recommended.