Install a music bot on TeamSpeak

A music bot connects to your TeamSpeak server like a normal client and plays audio in a channel. Common solutions (Sinusbot, JTS3Servermod) work on the same principle: a Server Query account for authentication and a virtual client for playback.

Cause / The problem

Without a dedicated Server Query login, the bot tries to connect with unstable credentials and ends up banned for “flooding” (too many attempts). And without a permissions whitelist, the bot can neither join the channel nor speak in it.

Solution

1. Pick a bot: Sinusbot (web UI, scripts) or JTS3Servermod (lightweight, Java). Both connect as a TeamSpeak client.
2. Create a dedicated Server Query login for the bot. In the TeamSpeak client, connect as Server Admin then:
   • Tools → ServerQuery Login (or via the query port 10011).
   • Create a music_bot account and note the generated password.

   # Example query connection
   login music_bot GeneratedPassword
   use sid=1

3. Configure the bot with the server credentials:
   • IP, voice port (default 9987)
   • Server Query port (10011)
   • Server Query login/password
   • Target channel (channel ID)
4. Start the bot via the panel or command line. It appears in the channel like a normal client.
5. Whitelist the bot in permissions to avoid flood ban. Add its identity (unique ID) to a Bot group with:
   • Enough i_client_channel_join_power
   • b_virtualserver_client_permission if needed
   • i_client_music_volume (audio playback rights)
6. Avoid flood ban: if the bot fails several times in a row (wrong password, full channel), TeamSpeak bans the IP. Fixes:
   • Verify the Server Query password before launching the bot.
   • Add the bot’s IP to the Query IP Whitelist in query_ip_whitelist.txt.
   • Disable connection persistence if the bot restarts often.
7. If you hit a flood ban: wait (the ban usually lasts 1h) or unban via the panel. Fix the credentials before relaunching.
8. Basic commands: most bots are driven by chat (!play <url>, !stop, !volume 50) or through a web UI on the dedicated port (e.g. 8087 for Sinusbot).

On Mumble, there is no music bot as mature; solutions usually involve a bridge to a Discord channel or a custom Python bot via Ice/Murmur.