Currently keyed talkers. Mode is shown for local transmissions; bridge traffic shows RX only.

Active calls are highlighted. Data is kept for 24 hours.

A global ban blocks the user everywhere — radio (acl.cpp drops voice), web (require_login rejects sessions), SMS, APRS. System-reserved TGs (PARROT/SCAN/EMERGENCY/APRS/DISCONNECT) are not bypassed by global bans — banned users still get nothing.

No talkgroups in Redis yet — populate /registry/dmr/talkgroups/<tgid> hashes with id/name/description/website/country/language.

System events that involve your callsign or one of your DMR ids — admins see everything.

No events yet.

Hotspot Setup

Fill in your callsign + DMR id below, pick your hotspot firmware, and copy the generated settings into its configuration. The same approach works for Pi-Star, WPSD, openSPOT, MMDVMHost, and DMRGateway.

Each YSF reflector hosted by this server, with the endpoints currently connected (registered users with their DMR id, plus anonymous / guest endpoints).

No YSF reflectors configured.

M17 reflector instances hosted by this server, with the M17 clients currently connected.

No M17 reflectors configured.

NXDN reflector instances hosted by this server, with the NXDN clients currently connected (callsign + NXDN id when registered).

No NXDN reflectors configured.

Last GPS fix per callsign from DMR-mode radios (forwarded to APRS-IS, also stored locally for cross-mode use). Click a marker for details.

No positions in this window.

All configured outbound peers across HB, MMDVM, YSF, NXDN, M17, M2MC and OpenBridge. Status badge per row reflects live link state from Redis (CONNECTED / LINKED / BACKOFF / etc.). Click a row to expand all fields including live runtime values. Servers (reflectors) live under Monitor. Edit via Sysconfig.

No peers configured.

Last 24 hours on this TG

No activity in the last 24 hours.

Your Profile — where to find what

Once you're logged in, the dropdown under your callsign (top right) holds everything personal to you. This page walks through each item and what it's for.

Don't have a DMR ID yet?

A DMR ID is required to register and to operate on any DMR / NXDN / YSF / M17 network. Get one for free at:

• DMR / YSF / M17 — radioid.net (your DMR ID also serves as your YSF and M17 callsign-to-id).
• NXDN — nxdn.info.

callmgr syncs from those databases nightly. Once your callsign appears there, register on this site and your IDs show up automatically under My IDs.

Profile

Your account information. Six tabs:

• My Account — name, email, city / state / country, and your home position (lat / lon). The home position is a fallback for APRS when your radio isn't sending GPS — see APRS help. Change your web password from this tab too.
• API Key — generate / rotate a token if you want to call the API from a script.
• My IDs — every DMR and NXDN id registered to your callsign in the public databases. Read-only — they come from radioid.net / nxdn.info. New ID? Apply at radioid.net.
• My Peers — DMR Bridge (TGIF/BM), YSF, NXDN, M17, M2MC and OpenBridge peers + servers where your callsign is listed as admin. Click Edit to change settings.
• My Radios — hotspots and radios that have actually connected to this server. Shows last-seen time, current TGs, model.
• Last Heard — your own TX history on the global DMR network (via radioid.net).

User Security

Manage DMR security tokens for your radio IDs. A security token lets a radio prove it's yours without sharing your web password.

Selfcare

For each radio: pick which talkgroup goes on TS1 and which on TS2. Save — the change is live the next time the radio keys up. The number 4000 on a slot means "no TG, listen to nothing on this slot".

Custom Scan

Per-radio scan list — pick the talkgroups the scanner should watch. When any of them goes active the radio jumps to it. Use this when you want to monitor several TGs without locking a slot.

Request TG

Submit a request for a talkgroup that doesn't exist yet. See the Talkgroups help for details on the form and what happens after you submit.

Manage TG

Lists every talkgroup where you are owner or co-admin, plus your personal DMR-id TGs. Click Edit on any row to open the control panel — see Talkgroups for what each tab does.

Notifications (the bell)

The bell at the top right shows recent system events involving your account: TG request approved/denied, password resets, account changes. Clear individual entries with the X. Admins also see pending account approvals and TG requests in the same bell.

Other help pages: Talkgroups · Private Call · APRS · SMS

Talkgroups — request, manage, use

A talkgroup (TG) is a virtual channel many radios share. You pick which TGs your radio listens to, and you can request your own TG if you want one no one's claimed yet.

1. Pick TGs your radio listens to

Open Selfcare. For each radio, set which TG goes on TS1 and which on TS2. 4000 on a slot means "no TG on this slot".

2. Scan many TGs at once

Open Custom Scan. Add each TG you want the scanner to watch.

3. Request a new talkgroup

Open Request TG and fill in:

• TG ID — pick a free number between 1000 and 99999. Numbers below 1000 are reserved for system use.
• Name — short label (e.g. Stockholm).
• Description / Country / Language / Website — optional metadata.

Submit. An admin reviews the request — you get an email when it's approved. You can only have one pending request at a time.

4. Your DMR ID is also a TG (private)

Every DMR ID you own automatically counts as your personal TG. Other users can call you privately by sending a private call to that number. No request needed — it shows up in Manage TG as Owner (DMR id). See Private Call for how PCs work.

5. Manage TGs you own — control panel

Click Edit on any row in Manage TG. The control panel has three tabs:

Basic — name, description, country, language, website.

Access lists — three callsign lists per TG:

• Allow (whitelist) — if non-empty, only these callsigns can use the TG. Anyone not listed is blocked.
• Deny (blacklist) — listed callsigns are blocked from this TG.
• Listen-only — listed callsigns can hear the TG but cannot transmit.

TG Admins — add another callsign to give them edit rights on this TG. The owner is always shown first with an "owner" badge and can't be removed by co-admins.

6. Live activity

Under Monitoring: Lastheard shows who's keyed up right now; Lastheard 24h shows the past day; Talkgroups lists every TG in the directory.

Private Call (PC)

A Private Call is a direct call from your radio to one specific other radio — addressed by their DMR ID, not a talkgroup. Like dialing a phone number instead of joining a chat room.

How it differs from a talkgroup call

• TG (group call) — anyone subscribed to that talkgroup hears you. One-to-many.
• PC (private call) — only the radio with that exact DMR ID hears you. One-to-one.

callmgr routes both, but the path is different: PCs go directly to the destination's hotspot (no TG fan-out), TGs are broadcast to every subscriber of that TG.

Make a private call

On your radio, create a contact with:

• Call Type — Private Call (sometimes called "Individual" or "PC").
• Contact ID — the recipient's DMR ID (look it up at radioid.net by callsign).
• Time Slot — TS2 is most common for PCs on hotspots, TS1 on repeaters. Match what the recipient uses.

Select the contact, key up, and the radio will call only that ID. The recipient's radio will play your audio.

Receive private calls

Most radios show "PC" or "Private" on the display when receiving one, with the caller's ID. Some radios beep until you reply or dismiss the call. Make sure your radio's Private Call Confirmation setting matches what you want — leave it on if you want a beep, off if you want it silent.

Test it — Parrot echo

callmgr's parrot module replies to your transmission with a recording of itself. Two parrot numbers exist:

• Group call to 9990 on any TS — you hear yourself back as a group call.
• Private call to 240990 — you hear yourself back as a private call.

Use the parrot to verify your radio's audio + GPS + ID before trying real PCs.

Privacy and bridges

Private calls aren't encrypted on standard amateur DMR — anyone monitoring on the same hotspot/repeater can scan and hear them. The "Private" name is about routing (who gets the audio), not secrecy.

If the recipient's hotspot is bridged to a foreign network (BM/TGIF), the PC routes there too — same as TGs do.

Common gotchas

• Both radios must be on the same time slot. PC on TS1 to a radio listening on TS2 = no audio.
• The recipient must have their hotspot online and the right TS slot active.
• If their radio profile doesn't allow PCs (some Pi-Star configs disable them), the call won't reach the radio even if the hotspot is up.

APRS — text messages and position, everywhere

callmgr is a full APRS-IS gateway: you can send and receive APRS text messages as your own callsign (not as a shared gateway), see incoming messages in your web inbox, and get them pushed to your DMR radio as PC SMS — all without leaving the dashboard. Position bridging across modes works on top.

The four pipes (TX/RX × web/radio)

Configuring it — two places

1. Profile → APRS tab

For your account-level position + optional opt-in beacon:

• Latitude / Longitude — your QTH. Used as the position source when no live radio GPS is available. Decimal (56.3950) or APRS native (5639.50N) accepted.
• Broadcast my position to APRS-IS (opt-in) — server periodically beacons you as your own callsign. Disabled by default — your position is never broadcast unless you enable this.
• Interval — how often to beacon (15–1440 minutes, default 60).
• SSID — APRS SSID for the beacon (none = base callsign / Primary fixed; -7 = HT; -9 = mobile; etc).
• Symbol — map icon (Home, Car, Sailboat, IGate…). "Custom" lets advanced users enter any 2-char APRS symbol.
• Comment — free text up to 36 chars, shown next to your marker on aprs.fi.

2. Messages → APRS → My APRS routes (per-SSID node mapping)

For routing inbound APRS messages to your radio. Each row maps {SSID, DMR id} so the daemon knows where to deliver an incoming msg addressed to e.g. SA7AUX-9.

• Node — free label so YOU recognize the row (WPSD, OS2, "car", anything).
• SSID — APRS SSID variant of your callsign that this row catches. 9 = mobile, 7 = HT, etc. Leave empty for wildcard — that row catches every SSID variant of your callsign (SA7AUX, SA7AUX-1, SA7AUX-D, all of them).
• DMR id — your DMR id. Three valid forms: 240607 (6 digits, repeater), 2406078 (7 digits, user base), 240607801 (9 digits, user + ESSID). All resolve to the same base; daemon delivers to every online radio matching that base.

A typical setup: one row per SSID you use. Example — SA7AUX-9 ↔ your mobile DMR id, SA7AUX-7 ↔ your HT id. APRS messages addressed to those callsigns ring on the right radio.

Worked example — full config for SA7AUX

Here's what a typical complete setup looks like. Adjust callsign, lat/lon and DMR ids to your own.

Profile → APRS tab

Result: SA7AUX>APRS,TCPIP*::!5639.50N/01508.07E>DMR APRS user · SA7AUX beaconed every 60 minutes.

My APRS routes table

Two ways to set it up — pick whichever fits your usage:

A) Simple — one wildcard row, all SSIDs to one radio:

B) Per-SSID — different radios for different SSID variants:

In setup B, a wildcard row acts as fallback. When both a specific row and a wildcard row exist, both fire — the message is delivered to both radios. Trim the wildcard if you don't want fan-out.

Try sending one — from web

1. Go to Messages → APRS.
2. Open the Send an APRS message panel.
3. From: pick SSID -9 (mobile) → wire shows SA7AUX-9.
4. To: type KE8GIM, SSID -9 → wire shows KE8GIM-9.
5. Message: testing from car.
6. Click Send. Look at log: aprs.user_send: sent as SA7AUX-9 dst=KE8GIM-9 id=N: testing from car.
7. Check aprs.fi/?call=SA7AUX-9 messages tab — should appear within seconds.

Try sending one — from your DMR HT

1. Open Messages on your AnyTone / TYT.
2. New private SMS to id 9999 (the aprs-tg).
3. Body: KE8GIM-9 hi from radio (first word = dest, rest = text).
4. Send. Daemon log: mmdvm.in: APRS outbound queued src=240607701 dst=9999 text='KE8GIM-9 hi from radio'.
5. Then: aprs.from_radio: relay dmrid=240607701 call=SA7AUX -> KE8GIM-9: 'hi from radio'.
6. Then: aprs.user_send: sent as SA7AUX dst=KE8GIM-9 id=N: hi from radio.

The daemon resolves your radio's DMR id back to your callsign automatically — no extra config needed.

What happens behind the scenes

Sending from web

1. You compose a message in the Messages → APRS panel.
2. Daemon opens a fresh APRS-IS connection logged in as your callsign (with the auto-computed passcode for your call).
3. Frame is dispatched. Stays open 30s waiting for the recipient's ACK.
4. ACK status is recorded so you can see delivery state.

No need for you to know your APRS-IS passcode — it's derived from your callsign automatically. The recipient sees the message as coming from you, not from the server's gateway login.

Sending from a DMR radio

1. From your HT, send a private SMS to the magic dst (default 9999 — see Help → Connect Your Node for the live value).
2. Body format: DEST_CALL message text — first word is the destination callsign (with optional -SSID), the rest is the message body.
3. Daemon resolves your DMR id → callsign, computes your passcode, opens APRS-IS as you, sends.

Example body: KE8GIM-9 hello from the car sends "hello from the car" to KE8GIM-9 on APRS-IS as your callsign.

Receiving on web

Every APRS message addressed to any SSID variant of your callsign is captured by the daemon and lpush'd to your inbox. Persistent (no TTL — stays until you delete or the list hits its 200-message cap). Open Messages → APRS to see them. Outgoing messages you sent appear there too, marked OUT.

Receiving on radio

When an APRS message arrives for one of your registered callsigns and matches an entry in your APRS routes table, the daemon injects it into the existing DMR PC SMS pipe addressed to your DMR id. The body is prefixed with the sender (KE8GIM-9> hello) so you immediately see who it's from. All your online radios sharing that DMR base receive it.

Auto-ACK on your behalf

When someone messages you, the daemon ACKs back automatically as your callsign (using the per-user-TCP path again). The sender's APRS app stops retrying — they get a clean delivery confirmation even though you didn't physically touch a radio.

Unregistered hams — heard-cache routing

Random hams who key up through your repeater or hotspot don't have an account here, so they have no routes table entry. The daemon still tracks them so APRS messages can find them.

How it works

1. Every time a ham keys up via your aprs-tg (private SMS to 9999), the daemon records: callsign + last node + last DMR id + timestamp in aprs:heard/<CALLSIGN> with 4-hour TTL.
2. When an APRS message arrives for that callsign, after checking registered users' routes (no match) the daemon falls back to the heard-cache.
3. If found AND not opted out → DMR PC SMS delivered via the same node they last TX'd through, addressed to their DMR id.
4. Body prefix shows the sender so they see who's writing: KE8GIM> hello there.

TTL = 4h. If they don't TX again for 4 hours, the cache entry expires and APRS msgs stop being routed to them. Comes back automatically next time they key up.

Opt-out from your radio

Don't want unsolicited APRS messages popping up on your radio? Send a private DMR SMS to the aprs-tg (default 9999) with body:

• ?aprs off — adds your callsign to the deny-list. Heard-cache routing is suppressed for you. Web inbox still receives (if you have an account here).
• ?aprs on — re-enables routing. Removes you from the deny-list.

Default is opt-IN — you have to explicitly opt out. Daemon resolves your DMR id → callsign automatically; no need to identify yourself in the body. Your account-level web inbox is unaffected; this only controls radio-side delivery.

Priority order at delivery

1. Registered route, specific SSID match — exact ESSID-targeted PC SMS to your chosen radio.
2. Registered route, wildcard SSID — fan-out to all your radios that match.
3. No registered route, heard-cache hit, not opted out — PC SMS via last-heard node.
4. None of the above — drop (web inbox still written if user is registered with that callsign).

Position bridging (the original feature, still here)

For position reports on aprs.fi the daemon picks a source per transmission in this order (configurable, default radio → lastheard → home):

• radio — your radio's own GPS in the transmission (DMR talker alias, YSF DT1/DT2, M17 METATEXT, NXDN short-data — all bridged).
• lastheard — the most recent GPS fix this callsign sent in any mode (cross-mode cache).
• home — the lat/lon you saved in Profile → APRS.

Cross-mode bridging means a YSF GPS fix is reused next time you TX on DMR without GPS — your marker stays put on the map.

Enable GPS in your radio (if it has one)

• AnyTone D578 / D878 — set GPS on per channel; GPS Send Position interval ~30-60s.
• TYT MD-UV380 — enable GPS Beacon per channel.
• Yaesu FT3DR / FT5DR (C4FM) — APRS data mode in the DG-ID / Wires-X menu.

Verify it works

• Outgoing message — send to a callsign you control (or a known APRS station). Check aprs.fi → search your callsign → recent messages tab. Should appear within seconds.
• Position beacon — enable beacon, wait one interval, refresh aprs.fi for your callsign. Marker appears with your symbol + comment.
• Inbox RX — ask someone to send you a test message. It appears in Messages → APRS marked IN within a few seconds of their send.
• Radio RX — same test as above, your DMR radio should beep with a private SMS containing SENDER> body.
• Radio TX — from the HT, private SMS 9999 body SA7AUX-DB ping (or similar). Check daemon logs for aprs.from_radio: relay — and the message hits APRS-IS as you.

For server-side details (ports, hostnames, passwords), see Help → Connect Your Node.

SMS & SGS — text on DMR

DMR carries short text messages over the air, either to a single radio (private) or to a whole talkgroup. callmgr relays them between hotspots and across modes where it can.

Three flavors

• SMS to TG — your message goes to everyone listening on that talkgroup. Like sending a chat into a room.
• SMS to a radio (private) — addressed to a specific DMR ID. Only that radio receives it.
• SGS (Short Data Service / Status) — pre-defined short codes ("Status 1..8" buttons on AnyTone). callmgr can convert these into readable messages or relay them as-is.

Send an SMS from your radio

Most DMR HTs have a Messages or SMS menu. Pick a contact (or group), type the message, send. The radio packs it into a Short Data burst that the hotspot forwards to callmgr.

• AnyTone D578 / D878 — Menu → Messages → New, pick recipient (Contact or TG), type, send. Up to ~70 characters per packet; longer messages auto-split.
• TYT MD-UV380 — Menu → Messages, similar flow, shorter character limit.
• Pi-Star / WPSD hotspots — typically transparent: the hotspot just forwards whatever the radio sent.

Different radios speak different SMS dialects

DMR doesn't enforce one SMS encoding, so brands picked their own:

• AnyTone — UCS2-BE (16-bit Unicode, big-endian). Supports all characters incl. emoji.
• Hytera — ETSI standard 7-bit.
• Motorola — variant of ETSI.
• Pi-Star/WPSD bridges — pass-through, same encoding the underlying radio uses.

callmgr knows about each per-radio encoding via radio_profile in the directory and translates between them where possible. AnyTone-to-AnyTone always works. AnyTone-to-Hytera works for plain ASCII, may garble extended characters.

If you see weird characters

It's almost always a radio-profile mismatch — your hotspot is registered as one brand but you're using a different radio model. Open Profile → My Radios, check that the radio profile matches reality. If wrong, the operator can update sms_encoding_override for that hotspot.

SMS limits

• Length — radios usually accept 70-160 chars per message. Beyond that, the radio fragments and the receiver may show the parts as separate messages.
• Reliability — DMR Short Data has no retry. If the receiving hotspot is offline or scanning a different TG, the message is lost. There's no "delivered" receipt.
• Storage — your radio stores incoming SMS until its memory fills; callmgr does not store SMS history per user (yet).

SMS-to-APRS

If enabled by the operator, SMS sent to a special TG is forwarded to APRS-IS as a message to the recipient's callsign. The recipient (and anyone watching aprs.fi) sees it as an APRS message.

Common gotchas

• The other party's hotspot must be on the same TG (or PC route) when you send. SMS doesn't get queued and replayed.
• OS1 / OpenSpot 1 has limited SMS — RX usually works but some chars don't render.
• WPSD / Pi-Star scan lists can swallow SMS — make sure the TG you're sending to isn't being skipped on the receiver's hotspot.

Connect Your Node

Everything you need to wire your hotspot, repeater or node into this server. All values are pulled live from the running config — they reflect what the daemon is actually using right now.

1. Pick your protocol family

Match your hardware below to the right family, then jump to the matching section.

2. DMR servers (single-server families)

One server per family. Connect your hotspot to the one matching your firmware.

3. Reflectors (multi-server families)

Pick the reflector that matches the talk group / region you want. Each reflector has its own port. Hostname is the same as above for all reflectors.

4. Talkgroups reference

Special TGs always available regardless of which reflector you connect to.

5. Where to find your password

Callmgr is a lightweight, self-hosted call manager that bridges DMR, NXDN, YSF, M17 and more — all from a single server. Connect your hotspot, repeater or radio and start talking across networks.

What you get

• Multi-protocol bridging — DMR (MMDVM & Homebrew), NXDN, YSF, M17 and Hytera DMR-D, all cross-connected through one engine
• Hotspot & repeater support — openSPOT 1/2/3/4, Pi-Star/WPSD, MMDVM and Homebrew peers
• SMS & data services — send and receive text messages between radios, with automatic encoding for AnyTone, Motorola, Hytera and ETSI radios
• APRS integration — GPS position reporting from DMR radios to APRS-IS and back
• Selfcare portal — manage your talkgroups, security tokens, radio settings and API keys from your browser
• Scan & monitor — configurable scan lists per radio, follow activity across talkgroups
• Open peering — connect to YSF reflectors, NXDN servers, M17 reflectors and other networks as peers

Sign in with your callsign to get started.

Profile

DMR IDs & Security Tokens

My Hotspots / Radios

Click on a TS1/TS2 value to change talkgroup.

Custom Scan Lists

No talkgroups yet — request one via Request TG. Auto-granted personal TGs (your DMR ids) appear here too.

Request a New Talkgroup

God Mode

Login as another user to see their view.

Control