Users & requests
| Status | Name / unit | Callsign | Team / role | OTS user | Devices | Requested |
|---|
Default: everyone sees everyone. Every user is in the OTS group of their team (TEAM_โฆ) with IN + OUT (send and receive) and reads the groups of the other teams. Untick = this team does not see the other one: OTS stops delivering positions, markers and chats of the hidden team. Devices have to reconnect afterwards. Single users can be set to "receive only" or "send only" under Users โ Edit.
Who sees whom?
Video feeds โ cameras from WebTAK (phone, helmet camera)
ATAK finds the streams under Video (rtsp://<TAK server>:8554/<path>). The path is built automatically from the name โ only change it if needed. Green dot = registered.
| Status | Stream | Camera | FPS | Viewers | Last image | Rotation | Image size | TAK path |
|---|
No streams yet. Users start video in WebTAK or sign up with the camera app QR code under "Links & QR codes".
Links & QR codes
Registration โ new users
Users send a request here; you approve it under "Users & requests". They then get login details, QR codes and a guide.
WebTAK app โ map, chat, video in the browser
For users with access. Video (phone/helmet camera) starts right in WebTAK and appears as a feed in the TAK server automatically.
Camera app โ camera only, without TAK access (helmet camera, phone as camera)
For cameras without their own TAK access: scan, enter name and unit, connect the camera, start the stream โ the feed appears in the TAK server automatically. Users with access start video right in WebTAK.
Create stream
Optional โ for a fixed helmet camera with its own QR code. Usually users sign up themselves.
WebTAK app (settings โ link and QR code under "Links & QR codes")
Users connect with their own TAK credentials (certificate enrollment, .p12 / data package or QR code from the TAK server). This server only relays the data โ certificates stay on the phone and are not stored here.
OTS users (all accounts in the TAK server)
All users from OpenTAKServer โ including those created directly in OTS. "Import" additionally manages a user in WebTAK (callsign, team, access page with QR codes).
| User | Role | Active | Groups | Devices | Last login | WebTAK |
|---|
Groups (OTS channels)
Members with IN send into a group; members with OUT receive it. Users without a group are in __ANON__. Manage memberships under "OTS users" โ Groups.
| Group | Description |
|---|
Missions (Data Sync)
| Mission | Description | Groups | Content | Created |
|---|
All feeds in the TAK server (OpenTAKServer/MediaMTX)
These are all feeds ATAK/iTAK/WinTAK see under "Video" โ the cameras from WebTAK (above) and other sources. Add another feed: OTS/MediaMTX pulls the video on demand from the source (camera, drone, another server) and provides it as rtsp://<TAK server>:8554/<path>. Without a source the path waits for a camera that sends to it itself.
๐ Send a drone (DJI), OBS or screen app directly to the TAK server
Nothing to create: whoever sends to a path with their TAK user and password shows up as a feed right away. Users find their ready-made address on their access page and in WebTAK under Video.
| RTMP (DJI Fly, DJI Pilot 2, OBS, Larix) | |
|---|---|
| RTSP | |
| SRT | |
DJI Fly: โฏ โ Transmission โ Live Streaming โ RTMP. DJI Pilot 2: โฏ โ Livestream โ RTMP. Phone screen: the "Larix Screencaster" app (Android) with the RTMP address โ browsers cannot share a phone screen. PC screen: in WebTAK under Video "Share screen".
| Path | Origin | Source | For ATAK |
|---|
Meshtastic channels
| Channel | Radio | Up/Down | Link |
|---|