Skip to content

TAK Client Setup

MAGK uses TAK (Team Awareness Kit) clients for real-time position tracking and tactical communication. This guide walks you through installing a TAK client, importing your certificate, and connecting to the MAGK server.

Supported Clients

Client Platform Source
ATAK Android Google Play Store or TAK.gov
iTAK iOS Apple App Store
WinTAK Windows TAK.gov

TAK.gov Account

ATAK and WinTAK downloads from TAK.gov require a free account. Register at tak.gov if you don't have one. iTAK is available directly from the App Store.

Step 1: Install the Client

  1. Open the Google Play Store on your Android device
  2. Search for ATAK-CIV (the civilian version)
  3. Tap Install and wait for the download to complete
  4. Open ATAK — the app will run through an initial setup wizard
  5. Set your callsign when prompted (use the same callsign from your event registration)
  6. Grant location permissions when asked — ATAK needs GPS access to share your position

ATAK Plugins

ATAK supports plugins for extended functionality. For basic event participation, the default installation is sufficient.

  1. Open the App Store on your iPhone or iPad
  2. Search for iTAK
  3. Tap Get to download and install
  4. Open iTAK and complete the initial setup
  5. Set your callsign to match your event registration
  6. Allow location access when prompted
  1. Download WinTAK from TAK.gov (requires a TAK.gov account)
  2. Run the installer and follow the setup wizard
  3. Choose the default installation options unless your organizer specifies otherwise
  4. Launch WinTAK after installation
  5. Set your callsign during the initial configuration

Step 2: Import Your Certificate

After your event registration is approved, you'll receive a certificate package for secure server authentication. The format depends on your client.

Using a Data Package (.zip):

  1. Download the certificate data package (.zip) from your registration confirmation email or the MAGK platform
  2. Open ATAK
  3. Go to Settings → Network Preferences → Manage Server Connections
  4. Tap Import and select the downloaded .zip file
  5. ATAK automatically extracts the certificate and configures the server connection
  6. The connection status should show Connected within a few seconds

Using a .p12 file:

  1. Download the .p12 certificate file
  2. In ATAK, go to Settings → Network Preferences → Manage Server Connections
  3. Tap Add to create a new connection
  4. Select the .p12 file as the client certificate
  5. Enter the certificate password provided by your organizer
  6. Configure the server address and port (see Step 3)
  1. Download the .p12 certificate file from your registration confirmation
  2. Open iTAK and navigate to Settings → Certificates
  3. Tap Import Certificate
  4. Select the .p12 file from your device's file browser
  5. Enter the certificate password when prompted
  6. The certificate appears in the installed certificates list
  7. Proceed to configure the server connection (see Step 3)

iOS File Access

If the .p12 file doesn't appear in the file picker, make sure it's saved to your device's Files app (not just in an email attachment). Download it to the On My iPhone or iCloud Drive location first.

Using a Data Package (.zip):

  1. Download the certificate data package (.zip) from the MAGK platform
  2. Open WinTAK
  3. Go to Settings → Network → Manage Server Connections
  4. Click Import and browse to the downloaded .zip file
  5. WinTAK extracts the certificate and configures the connection automatically

Using a .p12 file:

  1. Download the .p12 certificate file
  2. In WinTAK, go to Settings → Network → Manage Server Connections
  3. Click Add to create a new connection
  4. Browse to the .p12 file for the client certificate
  5. Enter the certificate password
  6. Configure the server address and port (see Step 3)

Step 3: Configure Server Connection

If your certificate data package didn't auto-configure the connection, enter the server details manually.

  1. Go to Settings → Network Preferences → Manage Server Connections
  2. Tap Add (or edit the existing connection)

  3. Enter the connection details:

    Setting Value
    Description Your event name
    Address Server address from your organizer
    Port 8089
    Protocol SSL
    Client Certificate Select the imported certificate

  4. Tap OK to save

  5. The connection status indicator turns green when connected
  1. Go to Settings → Servers
  2. Tap Add Server

  3. Enter the connection details:

    Setting Value
    Name Your event name
    Address Server address from your organizer
    Port 8089
    Protocol SSL
    Certificate Select the imported certificate

  4. Tap Save

  5. Toggle the server connection to On
  6. Verify the status shows Connected
  1. Go to Settings → Network → Manage Server Connections
  2. Click Add (or edit the existing connection)

  3. Enter the connection details:

    Setting Value
    Description Your event name
    Address Server address from your organizer
    Port 8089
    Protocol SSL
    Client Certificate Select the imported certificate

  4. Click OK to save

  5. Check the connection status in the server list

Connection Details Reference

Your organizer provides these values. Common defaults:

Setting Default Value Notes
Server Address Varies per event e.g., magktech.com
SSL Port 8089 Encrypted CoT — recommended
TCP Port 8087 Plaintext CoT — use only if directed
Protocol SSL Always prefer SSL over TCP

Verifying Your Connection

After connecting, confirm everything is working:

  1. Connection indicator — Your TAK client shows a green/connected status
  2. Position on map — Your icon appears on the tactical map at your current GPS location
  3. Other players visible — You can see other connected players on the map (if the event is active)
  4. Callsign correct — Your callsign displays correctly on the map marker

Troubleshooting

Issue Solution
Certificate import fails Verify the .p12 password matches what your organizer provided. Re-download the file if corrupted.
Connection timeout Check that port 8089 is reachable from your network. Try switching to a different network (cellular vs. WiFi).
"Certificate not trusted" error Ensure you imported the correct certificate for this event. Each event may use different certificates.
Position not showing on map Enable GPS/location services on your device. Move outdoors for better GPS signal.
Client crashes on connect Update to the latest client version. Clear the app cache and retry.
Wrong callsign displayed Update your callsign in the TAK client settings to match your registration.

For additional help, see the Troubleshooting page or contact your event organizer.

Voice Communications (Vx Plugin)

If your event has Mumble voice communications enabled, the ATAK Vx plugin provides push-to-talk voice directly within ATAK.

Automatic Configuration

When you import your TAK data package, the Vx plugin is automatically configured with:

  • Mumble server address and port
  • Your assigned username
  • Your squad channel assignment

No additional setup is needed — open the Vx plugin panel and tap Connect.

Manual Vx Configuration

If the data package didn't configure voice automatically:

  1. Open the Vx plugin panel in ATAK (voice icon in the toolbar)
  2. Tap Settings → Voice Preferences

  3. Enter the connection details:

    Setting Value
    Server Address Mumble server address from your organizer
    Port 64738
    Username Your Mumble username (from registration email)
    Password Your LDAP password (same as TAK credentials)
    Channel Your assigned channel path (e.g., Operation Sunrise/1st Platoon/Alpha)

  4. Tap Connect

Using Push-to-Talk

  1. Open the Vx plugin panel
  2. Hold the PTT button to transmit
  3. Release to stop transmitting
  4. Your squad members will hear you in the assigned channel

Headphones Recommended

Use headphones or earbuds to prevent echo and feedback. Voice activation mode is available but push-to-talk is recommended in noisy field environments.

Vx Troubleshooting

Issue Solution
"Certificate not trusted" Re-import your data package or manually trust the Mumble certificate in ATAK settings
No audio Check microphone permissions for ATAK in Android settings
One-way audio Ensure UDP port 64738 is not blocked by your network
"Connection refused" Verify the Mumble server is running — contact your organizer

For standalone Mumble clients (Mumla, desktop), see the Voice Setup guide.