A TeamSpeak server can be deployed very quickly with Docker, which is often the easiest option if you just want to get the service running without much manual setup.

Use the following command:

docker run --name=teamspeak --restart always -p 9987:9987/udp -p 10011:10011 -p 30033:30033 -e TS3SERVER_LICENSE=accept -v /data2/www/docker/teamspeak:/var/ts3server teamspeak

In this command, /data2/www/docker/teamspeak is the local path on the host server. You can change it to any directory you prefer. Keeping the TeamSpeak data mounted to a local directory makes later backup and migration much easier.

After the command is executed, Docker will pull the TeamSpeak image automatically and create the server container. On the first startup, the server will generate a server administrator token. You will need this token after connecting with the TeamSpeak client in order to claim administrator permissions.

To view the token, check the container logs:

docker logs teamspeak

If you are deploying on a Windows server, the setup process is also fairly simple, although it is usually not as fast as a one-command Docker deployment.

Ports commonly used by TeamSpeak

<table> <thead> <tr> <th>Port</th> <th>Protocol</th> <th>Description</th> </tr> </thead> <tbody> <tr> <td>9987</td> <td>UDP</td> <td>Default voice service port</td> </tr> <tr> <td>10011</td> <td>TCP</td> <td>ServerQuery raw port</td> </tr> <tr> <td>10022</td> <td>TCP</td> <td>ServerQuery SSH port, available on server version 3.3.0 and above</td> </tr> <tr> <td>30033</td> <td>TCP</td> <td>File transfer port; required for uploads such as channel icons</td> </tr> <tr> <td>41144</td> <td>TCP</td> <td>TSDND</td> </tr> </tbody> </table>

If your server uses non-default ports but you still want users to connect through a domain name, you can configure DNS SRV records.

TeamSpeak provides documentation for this here:

https://support.teamspeak.com/hc/en-us/articles/360002711418-Does-TeamSpeak-3-support-DNS-SRV-records

Good luck running your server.