DCS SRS Radio on Fox3 Servers: Client Setup, Auto Connect, and Discord Text to Speech
If you have ever jumped into a DCS multiplayer server expecting coordinated radio calls and instead heard nothing but dead air, you already know how important SRS is. SimpleRadioStandalone is the backbone of serious squadron communication in DCS World, and when it is working the way it should, it genuinely transforms how a mission feels.
Here is the good news if you fly on a Fox3 server. The hard part is already done. The SRS server is installed, running, and tuned by us. You do not maintain it, you do not babysit it, and you never touch a config file. Your only job is getting your own client set up correctly, and on a Fox3 server even that is mostly automatic.
This guide walks through exactly that. What we handle for you, how to set up your SRS client, how auto connect works on every Fox3 server, and how you can push text to speech straight onto the radio through the Fox3 Discord bot.
What Fox3 Handles For You
On a managed rig, running SRS means installing it, opening ports, writing a server config, keeping the process alive across mission resets, and patching it after every DCS update. That is the part most people get wrong, and it is the part we take off your plate entirely.
Here is what is already done on every Fox3 DCS server:
The SRS server is running on port 15002. That is the Fox3 standard port across the fleet. It is open, reachable, and monitored, so you do not have to forward anything or troubleshoot a blocked connection on the server side.
The server stays up independent of the mission. SRS keeps running while DCS cycles through mission rotations, restarts, and updates. Your pilots do not get dropped just because the mission rolled over.
Process monitoring is built in. If the SRS process ever stops, our monitoring brings it back. You are not the one getting a message at 2200 on a Friday during your squadron event asking why nobody can hear each other.
The server config is managed by us. Coalition audio security, external controller access, retransmission limits, and the rest of the server side settings are configured and maintained by the Fox3 team.
That last point is worth being clear about. Customers do not have access to the SRS config file, and that is by design. It keeps the radio network stable, consistent, and secure across the fleet. If you want a change, such as a different coalition security setting, an external controller password for your GCI team, or a custom retransmission setup, just open a support ticket. We make the change for you and confirm it is live. You get the result without the risk of a typo in a config file taking your comms offline mid campaign.
Setting Up Your SRS Client
Since the server side is handled, your real setup is the client. Every pilot who wants radio needs the SRS client installed on their own machine. It is a separate download from DCS and it is free.
Here is the clean version of the process:
Download the SRS client. Get it from the official SimpleRadioStandalone release page. Always grab a current release rather than an old archived build.
Run the installer. When it asks, point it at your DCS installation so it can drop in the small export script that lets SRS read your in cockpit radio state. This step is what makes your real aircraft radios drive what you hear and transmit.
Launch the SRS client. You can start it before or after DCS. Many pilots just leave it running.
Set the server address. Enter the Fox3 server address and port 15002. On a Fox3 server you will usually not even need to do this manually, which brings us to the best part.
Auto Connect: It Just Works On Every Fox3 Server
This is the feature that makes life easy and it is set up on every Fox3 server.
When you join a Fox3 DCS server, your SRS client is told the correct radio server address automatically. You do not have to look up an IP, you do not have to remember the port, and you do not have to fiddle with the connection field. Spawn into the server and your SRS client connects to that server's radio network on its own.
For your pilots this means one less thing to get wrong. A new member can install the SRS client, join your Fox3 server, and be on comms without anyone reading them an address over Discord. Each server points its players at the right radio network, so even if your squadron flies on more than one Fox3 server, auto connect sends each client to the correct one every time.
If auto connect ever does not fire for a particular pilot, it is almost always a client side detail rather than a server problem. The usual fixes are below.
Common Client Side Issues And How To Fix Them
Because Fox3 runs the server side, the vast majority of SRS problems come down to the individual client. These are the ones we see most often.
You connect to SRS but cannot hear anyone.
First, check that your in game radio is actually powered on and tuned to the same frequency as the people you are flying with. SRS respects the real cockpit radio state for aircraft that support it, so a cold radio means silence. Second, confirm the SRS client actually connected. The client window will show a connected status and a list of who is on the network.
SRS connects in the hangar but drops when you spawn.
This almost always means the SRS export script is missing or out of date in your DCS install. When you run the SRS installer, let it install the export integration into your DCS folder. After a DCS update overwrites things, simply run the SRS installer again so the export script is refreshed.
Auto connect did not connect you.
Make sure the SRS client is actually running before you spawn in. If it is running and still does not connect, update to the current SRS client release, then rejoin the server. A mismatched or very old client is the usual culprit.
Your push to talk does not transmit.
Open the SRS client controls and bind your radio transmit keys there. SRS uses its own key bindings separate from DCS, so a fresh install has nothing assigned until you set it.
Radio sync broke right after a DCS update.
DCS updates occasionally overwrite the export scripts SRS relies on. Run the SRS client installer again to restore the integration, then relaunch. This is the single most common post update question, and it is a one minute fix on your end.
Notice the pattern. Every one of these lives on the player's machine. The radio server itself is already up and waiting for you.
A Simple Frequency Plan For Your Flights
Even with a perfectly managed radio server, comms fall apart if nobody agrees on what frequency to use. The server cannot fix that for you, but a little planning before the mission goes a long way.
A clean and memorable plan looks like this:
Flight common. One frequency per flight, kept the same across missions. Flight one always uses 264.0, flight two always uses 265.0. Pilots memorize these fast.
Package common. One frequency every flight monitors for coordination between flights, for example 271.0.
AWACS or GCI. Whatever your controller team prefers, fixed across your campaign so nobody misses a threat call.
Guard. A common emergency and admin frequency such as 121.5 that everyone keeps an ear on.
Ground or tower. A field frequency such as 133.0 if your mission uses airbases or ground controllers.
Build a one image frequency card and drop it in your Discord before every event. List the frequencies, which preset they map to, and which radio carries which net. If you want those presets baked into the aircraft so pilots spawn already tuned, that lives in the mission file, and our team is happy to help you get it set up.
Bonus: Text to Speech On The Radio Through The Fox3 Discord Bot
Here is a feature most server operators do not realize they have. The Fox3 Discord bot can broadcast text to speech directly onto your SRS radio network.
Type a message and the Fox3 bot speaks it over the radio on the frequency you choose. That opens up some genuinely useful and fun possibilities:
Live announcements to everyone airborne without anyone having to leave the cockpit.
Mission and event calls such as a countdown to a push time or a ramp start cue, spoken on guard.
Atmosphere and immersion, from station identifiers to scripted control calls that make the world feel alive.
Admin notices like a server restart warning, delivered straight to the people who are actually flying rather than buried in a Discord channel they are not reading mid sortie.
It bridges your Discord and your in game radio, so the people who matter hear the message where they actually are, in the jet. It is one of those touches that makes a Fox3 hosted server feel a step above a plain rented box.
Frequently Asked Questions
Do all players need to install SRS?
Yes. SRS has a client side that each pilot installs on their own machine. The Fox3 server side is already running, but every pilot still needs the free SRS client to talk and listen. The best move is to put a download link in your server's Discord welcome channel so new members are sorted before their first event.
What port does Fox3 use for SRS?
Every Fox3 SRS server runs on port 15002. You will rarely need to enter it by hand because auto connect supplies the address and port for you, but that is the number if you ever want it.
Can I edit the SRS server config myself?
No, and that is intentional. We manage the server config for the whole fleet so the radio network stays stable and consistent. If you want a setting changed, such as coalition audio security or an external controller password for your GCI team, open a support ticket and we will make the change and confirm it is live.
How does auto connect work?
When you join a Fox3 DCS server, your SRS client is handed the correct radio server address automatically and connects on its own. You do not type an IP or a port. Just make sure your SRS client is running and current.
SRS was working, then a DCS update broke it. What do I do?
DCS updates can overwrite the export integration SRS uses to read your cockpit radio. Run the SRS client installer again to restore it, then relaunch SRS. This is a client side fix and takes about a minute.
How do I set up an external GCI or AWACS controller without a DCS slot?
SRS supports external controller mode, where a controller connects to the radio network with a coalition password instead of taking an aircraft slot. Because the server config is managed by us, just open a ticket telling us you want it enabled, and we will set the controller passwords and pass them to you securely.
Can the Discord bot really talk on the radio?
Yes. The Fox3 Discord bot can send text to speech onto your SRS network on the frequency you pick. It is great for announcements, event cues, and immersion. Ask us how to get it wired up for your server.
The whole point of a managed server is that you spend your time flying instead of administering. SRS on Fox3 reflects that. The radio server is already running on port 15002, it stays up across restarts and updates, auto connect puts your pilots on the right network without anyone reading out an address, and if you ever need a change you file a ticket instead of editing a config file at midnight.
Get your client installed, jump on the server, and your comms are live. You fly. We handle the rest.
Blue skies and clear comms.