TeamTalk
About TeamTalk
TeamTalk is a voice conferencing system that you can run entirely on your own server. Connect to a server, pick a channel from the tree on the left, and everyone in that channel hears each other, with text chat, webcam video, shared desktop applications and file exchange on tabs to the right. Up to a thousand people can sit on one server at once. Nothing passes through anyone else’s service unless you choose a public server, because the server program ships in the same download as the client.
The other thing that defines it is who it was built for. TeamTalk was designed from the start to work with screen readers, so a blind user can run every part of it from the keyboard, with spoken announcements for who joined, who is talking and what arrived in the chat.
That made it the conferencing tool of choice in communities of visually impaired users, for classes, broadcasts and daily conversation. It suits anyone who wants a private voice server under their own control, and the accessibility design is part of why it stays usable under pressure.
Servers and channels
Everything in TeamTalk happens on a server. Public ones are listed inside the client and open to anyone, and a private one is a small program that runs on any always-on machine, from a spare desktop to a single-board computer, listening on a port you choose. The server defines channels, which are rooms with their own audio settings and passwords, and their own permissions, and users move between them freely or stay in the one they were given. Channels nest, so a conference can have a lobby with breakout rooms beneath.
Connecting is a matter of an address, a port and optionally a user account, and a join code shortens the whole thing to one string that is pasted in. Several servers save as a list, each remembering its channel.
For a group that already lives on a hosted chat platform, Discord offers rooms without running anything, and the trade is that the server belongs to someone else.
Voice, codecs and the microphone
TeamTalk voice runs through modern codecs with a choice of quality per channel, in mono or stereo, so a music channel can carry full-bandwidth stereo while a talk channel saves bandwidth with narrow mono. Push-to-talk holds the microphone open while a key is pressed, and voice activation opens it when sound crosses a threshold you set, with a slider to tune it against background noise.
Each user’s volume can be adjusted individually, and a user can be muted locally without affecting anyone else. Sound events announce who arrives and leaves and what arrives in the chat, and conversations can be recorded to disk per channel, which is how a class or a broadcast gets kept.
Audio from the computer, a music file or a stream, can be played into a channel, and anyone mixing several sources will want a software mixer feeding the input.
Video, shared desktops and files
The TeamTalk Video tab shows webcam streams from everyone in the channel who has turned theirs on, in a grid or one at a time, at a resolution and frame rate the channel allows. It is adequate for seeing who is speaking and thin for a presentation.
Desktop sharing sends an application window or the whole screen to the channel, with an update interval and a cursor option, which covers a slide deck or a software walkthrough. The Files tab holds files uploaded to the channel, downloadable by anyone in it with permission, so handouts for a class or recordings from an earlier session sit where the people who need them are.
Quotas and permissions on uploads are set per channel, and files persist until removed, so for a recurring group the folder becomes the shared archive.
Accessibility, and why it matters here
Every TeamTalk control reaches by keyboard, the window layout is a tree and tabs that screen readers read in order, and events are spoken as they happen, with the choice of which ones and in what voice handed to the user. A blind user can host a server, run a channel, mute a troublemaker and share a file without a sighted assistant, which is rarer than it should be in conferencing software. Text-to-speech announcements and sound cues can be configured separately, so a sighted user can turn the speech off and keep the cues.
That design also makes the client fast for anyone who prefers the keyboard, since the interface never hides a function inside a graphic. The look is plain and dated as a result, a fair trade for a program that works for everyone in the room.
Running your own server
The TeamTalk server program has no interface of its own and is configured through a text file or from the client while logged in as administrator. Administrators create accounts with usernames and passwords, set what each account may do, from speaking and streaming video to uploading and kicking, and define the channel tree with its passwords and quotas. Bandwidth is the practical limit, since every stream passes through the server, and a home connection handles a few dozen voice users and far less video.
Encryption can be enabled so the connection between client and server is protected, and a server can be set to accept only encrypted clients. Against Mumble, the other self-hosted voice server people compare it with, this one adds video, desktop sharing and the accessibility design, and loses on the lowest latency for fast gaming, where that one still leads.
Where it falls short
Video is the weakest part, with low default resolutions and a tendency to stutter on ordinary connections, so it is not a substitute for a meeting platform built around faces. Running a server needs an always-on machine and a port opened on the router, which stops some people before they start.
The interface shows its age, permissions take reading to configure, and mobile clients lag the desktop one. None of this touches the core use, a reliable self-hosted voice channel that everyone, sighted or not, can operate.
Conclusion
TeamTalk suits groups who want a voice room they control, from a club running weekly meetings to a school teaching blind students to a family that would rather not hand its conversations to a platform. The self-hosted server, the nested channels and the recording cover the organisational side, and the accessibility design means nobody is left out.
It is the wrong choice for polished video meetings or for the lowest latency in competitive games, and running a server is a small project in itself. Start on a public server to learn the client, set up your own on a spare machine when the group is ready, and the result is a conferencing system that answers to nobody but its administrator.
Pros & Cons
- Self-hosted server included, with up to a thousand users and nested channels
- Push-to-talk or voice activation, with per-user volume and local muting
- Screen reader support with spoken events and full keyboard control
- Webcam video, application or screen sharing and per-channel file storage
- Per-channel codec and quality settings in mono or stereo
- Recording of conversations to disk and encryption between client and server
- Video is low resolution and drops frames on ordinary connections
- Running a server requires an always-on machine and an open port
- Interface looks dated and permissions take reading to configure
- Mobile clients trail the desktop client in features
Frequently asked questions
No. Public servers are listed inside the client. A private server is for groups who want their own channels and accounts, under their own control.
Yes. It was designed for it, with full keyboard control, spoken announcements of events and a layout screen readers read in order.
Yes. A chosen application window or the whole screen streams to the channel, with an update interval you set, and others view it in the Desktops tab.
Up to a thousand on one server, limited in practice by the host's bandwidth, since every stream passes through it.