this page is in an Unfinished state. Please do not use!
Teamspeak servers a pretty lightweight and don't require much maintanance. If you don't want to go trough the whole hassle of setting one up you can rent one. But often you pay a high price per slot.
For ultimate privacy and security, I recommend to host your own teamspeak 3 server. rather then renting servers. You can basiclly run a teamspeak server off your pc if you really wanted to.
With one installation of teamspeak you can run multiple instances. every server people can join is a virtual server.
The system requirements for a server are:
ARM CPUs are not supported for servers and Clients. This means you won't be able to use a raspberry pi to set up a server for example.
Check the Teamspeak website for the latest system requirements over here!
Windows 8.1 and newer, 32 and 64-bit
For Mac OS X:
Mac OS 10.14 Mojave and above, 32 and 64-bit Intel CPU
Any recent Linux distribution, 32 and 64-bit
10.2 and above, 32 and 64-bit
For the CPU:
SSE2 capable CPU
SSE4.x capable CPU with POPCNT enabled (Only for the 64-bit version on Windows)
This depends on the operating system being used, however a minimum of 1 GB RAM is recommended.
Total memory usage depends on the number and size of hosted virtual servers.
For the Hard disk:
The bare minimum installation is 15 MB.
Total disk usage is highly dependent on actual usage, size and the amount of hosted virtual servers.
Additional space is required for file transfer and for icon/avatar storage.
A teamspeak server is mainly build up out of different voice channels and spacers. Every voice channel and spacer comes with its own chat room, The server will also have a server wide chat. Only people with the right permissions will be allowed to speak in this server chat by default.
Spacer main function is to devide different voice channels in different sections. Important note is that spacer can only be created from the top level of teamspeak (Top channel is the server)
There are a few different formats for the spacers.
A spacers name will look like
?is for alighment your options are
l or just leave it empty (r = right, c = center, l = left).
# is nothing more then an identifyer. This can be a normal name, but I would highly suggest using numbers and have an increment of 5 between the spacers. This way you keep the clear spacer order and can always fit new spacer between older ones wihtout screwing up your spacer numbering order.
A last option is to use
* instead of the
as text you can just give it a nice fancy name. but you can also format it with the listed formats below.
Teamspeak 3 comes with 2 permssion systems, basic and advanced. If you want to properly configure a teamspeak server I'd highly recommend to use the advanced permssions system. The basic is too limited in making a nice layered system.
There isnt a nice way to make a hidden channel in teamspeak. however you can hide the clients in the channel by changing the subscription power.
TeamSpeak 3 comes with a big list of permissions with a lot of scalability and options. It's too much to keep it simple which is the reason why it is called advanced permissions. To be able to understand what’s going on with the permissions and what you can do with them, it's important to understand that there are a 5 different permission Tiers.
The way a client gets the permissions is determined through a 5 layer system. Each layer can overwrite permissions
from the previous layer. These are the 5 Layers:
Tier 1: Server Groups
Tier 2: Client Specific Permissions
Tier 3: Channel Specific Permissions
Tier 4: Channel Groups
Tier 5: Channel and Client Specific Permissions
You are in the “Guest” server group (Tier 1) which has the permission b_channel_modify_name set to false, but you are also
a “Channel Admin” (Tier 4) and a channel admin has b_channel_modify_name set to true. Since the channel group is in
a higher tier than the server group, in the end you can modify your channels name (but not that of other channels where
you are not channel admin).
In my server, it's mainly wishful behaviour, but if you do not want to work with channel groups, grant your server groups b_client_skip_channelgroup_permissions . I have this enabled for the Bot group, so bots are not effected by what channel they are in.
I recommend you to look into the permissiondoc.txt that comes with your teamspeak installation for full detail on the tiers
The document on them can be found in: Teamspeak3/doc/permissiondoc.txt
Or here: https://paste.ubuntu.com/p/WhCshPnW6Q/
Server groups are the permission group with the lowest Tier. The permission that come with these groups are permissions for the whole server. However channel groups overwrite server groups.
It is recommended to keep the permissions for these groups as limited as possible, especially for the bigger/public servers out there. Random people will come on the server and try things.
Channel groups are limited to a specific channel, so permissions are also limited to that channel.
Within the channel groups you can grant server wide permissions, so be careful what you grant someone in a channel.
Cosmetic use of server groups:
You can use these server groups as cosmetic features to add badges to people, for example, meet-ups.
We used to have these cosmetic ranks server wide.
Each of the above Tiers can be configured with a big list of permissions. Each permission has a unique name that can be seen when you enable "show names". The different permissions are:
Boolean Permissions (True/False) Starts with "b_"
Integer Permissions (Numeric) Starts with "I_"
Power and needed Power Permissions (These permissions are a special case of Integer Permissions) Starts with "I_"
MORE INFORMATION ABOUT THE DIFFERENT PERMISSIONS!
Permission Layout on my server
The permission system in my Teamspeak
The channel commander is a usefull feature in for example trategic battle games, where you deply as squads. The Channel commanders would be able (after setting a hot key) to talk to eachother.
Bots often use the query protocol described above. However the cleanest way to make the profiles/query logins for the bot(s) is to make local identities per bot, join ts with the identity and create a query login for the bot. This is the best solution when you use multiple bots at once.