Files
ts3java/ts3-client/docs/myteamspeak/myteamspeak_server_signin.md
T
erikbrockoandClaude Opus 5.5 ca86c510b7 myTeamSpeak: import TeamSpeak 6 contacts; bookmark myTeamSpeak switch
TeamSpeak 6 syncs chat contacts as item class 8 (Item_Data field 25). They
are imported as friends keyed by myTeamSpeak ID, taken from the item or from
the partner's chat ID (@<base32 id>:<homeserver>), the same bytes servers
report as base64 client_myteamspeak_id. The contact list matches them to
clients through the ID each client carries.

Bookmarks gain TeamSpeak's "Enable myTeamSpeak features" switch
(send_mytsid_on_server), stored and imported but not yet sent; what is
still missing is noted in docs/myteamspeak/myteamspeak_server_signin.md.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-10 17:56:29 +00:00

2.8 KiB

Announcing the myTeamSpeak ID to a server

What the client has to send so that a server shows our client_myteamspeak_id, the way the official client does when a bookmark has "Enable myTeamSpeak features" on. Observed with TS3 3.6.2 signed in to the throwaway account against the test server, 2026-10-10.

The switch

Connect dialog and bookmarks: "Enable myTeamSpeak features", on by default. It is Bookmark_Data.send_mytsid_on_server (22) in the sync schema. When it is on and the client is signed in, clientinit carries the extra parameters below. client_myteamspeak_id itself is sent empty; the server fills it in from them and announces it to everyone (notifycliententerview client_myteamspeak_id=<base64>).

The official client also has a post-connect updatemytsid command, which takes the same data, for signing in or out while connected. It was not hit during a normal connect.

Extra clientinit parameters

Parameter Value Source
myTeamspeakId base64 of the 33-byte myTeamSpeak ID (01 20 …) known: login myts_id_data.my_teamspeak_id (4)
acTime account creation time as a u64, byte-swapped, in decimal known: login myts_id_data.account_creation_time (3)
userPubKey base64, 32 bytes (Ed25519 public key) known: login myts_id_data.user_public_key (1)
pubSign base64, 64 bytes known: first 64 bytes of login myts_id_data.public_signature (5)
pubSignCert base64, 112 bytes (certificate naming "TeamSpeak Systems GmbH") known: remaining 112 bytes of public_signature (5)
authSign base64, 64 bytes unknown, still to find

acTime example: creation time 1790376353 = 0x6AB6F9A1; as big-endian u64 a1f9b66a00000000 = 11671560475690139648.

Still to find: authSign

  • It is made fresh for each connection. It is not part of the login reply, and replaying an old one is not expected to work.
  • Without valid data the server refuses the ID: clientupdate client_myteamspeak_id=<anything> gives "invalid parameter".
  • To find: what authSign covers and how the client produces it, using only what our existing sign-in (MyTeamSpeakLogin) already holds.

Verification once it is known

  1. Connect our client with the switch on, signed in to the throwaway account.
  2. From a second client (the ts3j probe bot), check that notifycliententerview carries client_myteamspeak_id=ASCwXERY29umCjNyMewplck8cVzzMx/Xsh8vab8V7grN, the throwaway's ID.
  3. Check that with the switch off the field stays empty.