MSGC, or an SMS centre for APRS
An APRS message only gets through if the addressee is in range at that very moment. The sender's radio retries a few times over a couple of minutes, nobody acks, and the message is gone - while the other radio was parked in a garage, switched off or behind a hill, away from any digi. GSM solved this long ago: an SMS waits in the SMS centre until the phone is back on the network.
MSGC does the same for APRS. It listens to the whole of APRS-IS, spots messages that never got an ACK, stores them (up to 72 h) and delivers them when the addressee shows up again - any packet will do: a position, a status, anything. The message is delivered as coming from the original sender, with the original text and message number, and the recipient's radio acks it as usual. In the first test a message sent to a switched-off TH-D74 arrived 15 seconds after its first beacon.
Test service, running since 21 November 2026.
How it works
- Station A sends a message to B. B is out of range, so nobody acks.
- 10 minutes after radio A's last retry MSGC treats the message as undelivered and stores it.
- B shows up on the network (a beacon through any iGate). About 10 seconds later MSGC sends the message again, on behalf of A.
- The iGate that heard B puts it on RF. Radio B shows the message from A and sends the ACK to A. MSGC sees that ACK and is done.
Without an ACK MSGC tries 3 more times within a few minutes, then again whenever B shows up, at most every 30 minutes and up to 5 rounds. The replay on APRS-IS looks like this:
SP9ABC-4>MSGC,TCPIP*,qAS,MSGC::SP9XYZ-7 :Hi, call me back{12
The destination (tocall) field is MSGC - that is how you recognise a message from the store on aprs.fi.
Joining and commands
Send an APRS message to the station MSGC. Case does not matter, only the first word counts:
| Command | Also works | What it does |
|---|---|---|
| ON | SUB, SUBSCRIBE, START, JOIN | join - for the whole callsign, all SSIDs |
| OFF | UNSUB, UNSUBSCRIBE, STOP, LEAVE | leave and opt out - MSGC stores neither your messages nor messages to you |
| S | STATUS | your status and the number of waiting messages |
| ? | HELP, INFO | short help |
MSGC acks the command within a few seconds and replies with a message from MSGC shortly after. One side being joined is enough: messages to you (from anyone) and from you (to anyone) are stored.
Requirements
- Messages sent with ACK, i.e. numbered and requesting an acknowledgement. Kenwood and Yaesu radios and APRSdroid do this by default; some programs and apps have it as an option (ACK, retry, numbered messages) that must be on. MSGC ignores messages without ACK, as it cannot tell whether they were delivered.
- The recipient's radio sends ACKs (the default). That is how MSGC knows it delivered; without them it keeps retrying.
- An iGate near the recipient gates APRS-IS to RF - an ordinary two-way iGate. A receive-only one is not enough.
- An ordinary callsign with a digit. Tactical calls and bots (ECHO, OTA, WXYO...) are skipped.
How to test
- Switch radio B off (or move out of range) for at least 30 minutes.
- Send a message from A to B. Radio A gets no ack - that is expected.
- Wait at least 10 minutes after radio A's last retry.
- Switch B on and send a beacon. The message should arrive within seconds.
FAQ
It was not delivered - why?
- The recipient was heard less than 30 minutes before the message was sent - MSGC then considers it present (the missing ACK may have another cause) and does not store the message.
- The recipient came back less than 10 minutes after the sender's last retry - the message was not stored yet, but MSGC will deliver it if the recipient is still around.
- The recipient's iGate is receive-only and does not gate APRS-IS to RF.
- The sender is logged in to APRS-IS at that moment (e.g. APRSdroid over the internet) on the same server as MSGC - the server then drops the replay under the sender's callsign. Rare; a fallback sent from MSGC's own callsign is planned.
- Neither side has joined, or one of them sent OFF.
- A message without a number, a bulletin, telemetry, an
AA:auto-answer or a message to or from a bot - MSGC deliberately does not store these.
Does MSGC read my messages?
APRS is public - every message is visible anyway, e.g. on aprs.fi. MSGC keeps the text of a stored message only until it is delivered or expires (72 h) and keeps technical statistics. The OFF command stops storing your messages altogether.
Won't this clog the channel?
At most 10 messages wait for one recipient and at most 20 from one sender, and only one message per recipient is in flight - the next one only after the previous one is acked. Messages to and from bots and services are not stored at all. Persistent abuse goes to a separate, manual block list.
What does an iGate operator see?
An ordinary APRS-IS message: source = the original sender, destination = MSGC, path TCPIP*,qAS,MSGC. The APRS-IS servers route it to the iGate that heard the addressee within the last 3 hours, and the iGate puts it on RF under its usual rules (addressee heard locally). Replies to commands come from MSGC>APZMSG.
How do I leave?
Send OFF to MSGC. It takes effect immediately, and messages already stored to or from you are removed from the queue.