Talker Alias in DMR: a name and callsign instead of a numeric ID on the air

You hear a call, and the display shows a bare numeric DMR ID like 2501234 — but who that is remains a mystery. In the past, the only fix was a pre-loaded contact list with thousands of entries. Today there is an elegant solution built right into the standard: Talker Alias (TA) — sending the speaker's text name and callsign together with the voice. On the receiving radio the screen shows not a number but a living R0XXX Ivan, even if that contact is nowhere in your memory.

Talker Alias is part of the DMR specification suite (ETSI TS 102 361). The idea is simple: a short piece of text is "mixed in" alongside the voice in the over-the-air stream, and the receiver reassembles and displays it. Let's look at how it works, where it is supported, and how to turn it on.

What Talker Alias is and why you need it

Talker Alias is a text "signature" of the speaker, transmitted on the air during a voice call. It usually carries a callsign and a name, sometimes a city. The main value of TA is that displaying it requires no contact list: the name arrives "over the wire" from the transmitter itself.

• You can see who is talking, even if their DMR ID is missing from your database.
• No need to regularly update a huge list of tens of thousands of contacts just to keep up with new correspondents.
• Handy when travelling and on new talkgroups, where you run into unfamiliar operators.

How it works inside DMR frames

Voice in DMR travels in packets (a voice superframe), and these packets have room for embedded signalling (embedded data) — service information that rides along "in passing" with the speech without taking up a separate channel. Talker Alias uses exactly this mechanism.

• The TA text does not fit into a single frame, so it is split into blocks and sent piece by piece over the course of the call.
• There is a header service block (encoding format and length) and data blocks with the characters themselves.
• Different character encodings are supported (from a compact 7-bit one up to Unicode), which determines how many characters will fit.
• Because the text is reassembled over several frames, a short call may not give the receiver enough time to receive the whole alias.

Because of this "streaming" nature of TA, on short PTT presses the name sometimes appears with a delay or gets truncated — this is normal behaviour, not a fault. The basic structure of frames and slots is covered in the article on the basics of DMR, and the terms embedded data and superframe are explained in the DMR glossary.

Who supports Talker Alias

TA support exists on both the radio side and the network side, but it is not universal:

• Anytone (D878/D578 and relatives) — can both transmit and receive TA, with flexible format settings.
• Many modern OpenGD77 firmwares and commercial Motorola/Hytera radios also work with TA (with some caveats about format compatibility).
• BrandMeister networks and a number of others can build/forward TA, sometimes inserting it from the DMR ID database on the server side.
• Older or budget models may not show TA at all — you will only see the numeric ID.

How to enable it on Anytone and set the format

On the Anytone D878 (details about the radio itself are in the Anytone D878 review) the logic is usually as follows:

• In the codeplug (CPS) or in the menu you set up sending TA: the radio will transmit your signature when you go on the air. The text is taken from the radio settings (Radio Name / callsign).
• Separately you enable receiving and displaying TA for incoming calls — so that the correspondent's alias shows up on the screen.
• You can often choose the format/encoding and priority: whether to show the TA or the name from the contact list when both are available.
• It helps to keep the TA short (callsign + name): the longer the text, the more frames are needed to transmit it.

Relation to contact lists and Last Heard

Talker Alias and the contact list solve the same problem in different ways. The contact list is a local database of "DMR ID → name" loaded into the radio in advance. TA is a live signature arriving on the air. In practice they complement each other:

• If the ID is in the contacts, the radio usually shows the name from the list (fast, immediate).
• If the ID is unfamiliar but a TA arrived, the alias from the transmitter is shown.
• If there is neither, the numeric ID stays on the screen.

In the Last Heard log (the feed of "who has been on the air") the name can also be pulled either from the TA or from the network directory. In DMRhub the name and callsign come from the portal directory: when registering, an operator gets a DMR ID and callsign (see DMR ID registration), and the network knows how to label the call in the feed — even if the radio did not transmit TA. This removes the dependence on whether the alias managed to "make it" over the air.

Pitfalls and limitations

What to expect in practice:

• Not everyone receives it. On older radios TA simply will not be displayed — this is not a configuration error.
• Truncation by length. An alias that is too long may arrive incomplete; different encodings hold a different number of characters.
• Delayed appearance. The name shows up a fraction of a second after the call begins — while the blocks are being assembled. On a quick "tap" of PTT the TA may not arrive at all.
• Format incompatibility. Vendor implementations diverge in places; a rare receiver may show "gibberish" instead of a name.
• Display priority. If the radio is set to "contact takes priority over TA", a known ID will be shown as the name from the list rather than the sent alias — this is a matter of configuration, not a malfunction.

Summary

Talker Alias is a simple and useful DMR feature: the speaker's callsign name travels on the air together with the voice in embedded signalling and is shown on the display even without an entry in the contacts. Anytone, many modern firmwares and networks support it, but not all receivers display it, and length and delay impose limits. TA is a great complement to the contact list, while in your own network (like DMRhub) it is more reliable to take the call's signature from the portal directory — then the name and callsign are visible in Last Heard and in the app regardless of whether the radio transmitted the alias.