SRS Server (WIP)

This page is aimed at Dedicated Server setups. If you find any information in this wiki/documentation which requires correction or updating, please leave a comment, contact one of the contributors, or leave a message on the SRS discord.

If this is your first time hosting a server, there are plenty of guides on the internet already dedicated to port forwarding! If you believe you have your ports forwarded and are still unable to get users connected to your server, make sure you have forwarded the ports on EVERY ROUTER between you and your ISP. Many times, your ISP will have a sort of virtual router installed or a physical router specific to your connection, somewhere in the physical node of your area. You are typically free to edit these, though the IP address to connect to them can vary. Call your ISP if you believe this is the case and cannot find the relevant IP to connect through.

SRS Server GUI Walkthrough

W.I.P.

1. Start/Stop Server

Starts and stops the SRS server.

2. Clients

The number of SR-Clients connected to the server.

3. Port

The Port the server is listening on.

4. Client Admin

View names of connected clients; The names of the clients will be displayed as follows:

if the Client is not in a DCS mission
'player' if the Client is in a Single Player DCS mission
if the Client is in a Multi Player DCS mission Kick a client to kick that client Ban a client to ban that client

5. Secure Coalition Radios On/Off

When turned ON - Each coalition can only hear other radios of the same Coalition. I.e. Red to Red, Blue to Blue, Spectator to Spectator

When turned OFF - Any coalition can hear any other coalitions radio. To keep your radio secure from eavesdropping, don't publish your frequencies to the enemy or if available, use encryption 👍

6. Spectator Audio

When the button shows 'Enabled' spectators are given the ability to use SimpleRadio as if they were in a FC3 ship and may send/receive on any channel they select.

7. Auto Export List

Exports the player list to clients-list.json file in the SRS folder.

8. Line of Sight

Radios will only work if they have line of sight of one another.

9. Distance Limit

Depending on the strength of the signal the radios might not have enough range to recieve signals.

10. IRL Radio Tx Behaviour

Radio will simulate real life behaviour of that specific radio when transmitting.

11. IRL Radio Rx Behaviour

Radio will simulate real life behaviour of that specific radio when recieving.

12. Radio Expansion

13. Allow Radio Encryption

This enables encryption for blue and red teams to stop them from being able to hear each other if tuned to the same frequency.

14. Check for beta updates

When updating the server will include the beta branches for updates.

15. External AWACS Mode (EAM)

This enables external DCS players to communicate as an AWACS

16. EAM blue coal. password

Blue Force password for EAM connections

17. EAM red coal. password

Red Force password for EAM connections

18. Test Frequencies AM (Mhz)

SRS test frequencies

19. Show Tuned/Client Count

When in the sim, it will show the number of clients tuned into that specific frequency. Disable this feature if you do not wish for players to get this information through SRS.

20. Global Lobby Freq. AM (Mhz)

This frequency will be audible by both teams simultaniously.

21. LotATC Transponder Export

This will allow for transponder beeps to be broadcast through SRS from LotATC.

22. Show Transmitter Name

This will show the pilot player or AWACS player that is speaking on the radio.

23. Retransmit Hop/Node Count

The amount of retrans hops a broadcast can travel through.

Methods of Starting SR-Server

W.I.P. In this section we will cover three methods of initialization for SR-Server.

Manual Server start

The SRS Server can be started by simply double clicking on the SR-Server.exe to start.

PowerShell Initialization Methods (Single Instance)

PowerShell stores data in variables, variables are identifiable by the preceeding '$'.

$srsDIR variable is the location of your SRS installation.

$srsEXE variable uses the $srsDIR variable and adds \SR-Server.exe to signify the executable for the SRS Server.

start-process is the PowerShell command that will execute SR-Server.exe and start your SRS Server. This command needs to know where the executable is ($srsEXE) and where the program will be working ($srsDIR)

Create a File called Start_SRS.ps1, open the file in your code / text file editor of choice. Copy the Code snippet below into the file.

$srsDIR = "<INSERT YOUR SRS INSTALL FOLDER HERE>"
$srsEXE = "$srsdir\SR-Server.exe"
start-process $srsexe -WorkingDirectory $srsDIR

PowerShell Initialization Methods (Mutli-Instance)

In addition to the Single Instance Variables, Multi-Instance deployments need some additional variables.

$srsCONFIGFile variable is the location of configuration file for this instance of SR-Server you are trying to run. e.g. $srsCONFIGFile= "server02.cfg"

$srsARGS variable is a set of arguments thrown to the start-process command, this is to call out the '-cfg=' argument.