CNAM Explained: What It Is & How CNAM Lookup Works

CNAM (Calling Name) is the name — up to 15 characters — that displays on a phone next to an incoming number. The name is not transmitted with the call. When your call arrives, the recipient’s carrier performs a CNAM lookup against a third-party database, keyed on your phone number, and displays whatever string it finds. That one architectural fact explains nearly every caller ID name problem an outbound operation will ever hit: wrong names, stale names, “WIRELESS CALLER,” and names that display correctly on a landline but not on a cell phone.

If you run a business that depends on answered calls, this matters in a very concrete way. Your caller ID might still display the name of the company that owned your phone number three years ago. Your customers do not recognize it, so they do not pick up — and you blame your dialer, your carrier, or your leads, when the actual problem is a 15-character text string sitting in a database you have never heard of. This guide is the carrier-side view of that database, written by SIPNEX, an FCC-licensed carrier that provisions DIDs and manages CNAM records as part of standard carrier operations.

What is CNAM?

CNAM is short for Calling Name. It is the name string — a maximum of 15 printable characters (letters, digits, and some punctuation) — that displays on the recipient’s phone alongside the calling number when an inbound call arrives. When a phone shows “JOHN SMITH” or “ABC PLUMBING” next to an incoming number, that name came from a CNAM lookup performed by the recipient’s carrier at the moment the call arrived.

CNAM records live in databases historically called LIDB — Line Information Database — plus the third-party CNAM databases that grew up around it. LIDB was built for the landline network of the 1980s and 1990s, designed for a world where phone numbers were permanently bolted to copper lines owned by a handful of local telephone companies. That world is gone, but the CNAM infrastructure still runs on its assumptions — including the 15-character cap, a limit inherited from the legacy caller ID specifications of that era. In 2026 your smartphone can render a paragraph, but “SIPNEX TELECOMMUNICATIONS LLC” still gets truncated to “SIPNEX TELECOMM” and the rest discarded.

Who sets the record? The carrier serving the number — or the number’s owner, through that carrier — registers the name with a CNAM data provider. The record then propagates across the ecosystem, which is not instant and not uniform. There is no single authoritative CNAM database for North America; several providers maintain separate databases, and the name a recipient sees depends on which one their carrier queries.

Caller ID vs CNAM

People use “caller ID” to mean the name and the number together, but they are two separate systems that travel two completely different paths — and confusing them leads to fixing the wrong one.

Caller ID (the number) rides with the call. Your PBX or dialer places the calling number in the SIP signaling, and it is carried end to end through every carrier in the path until it reaches the recipient’s handset. Because the number is asserted by the caller’s own equipment, it can be set to anything — which is exactly the mechanism behind caller ID spoofing and the reason STIR/SHAKEN exists to verify it.

CNAM (the name) does not ride with the call. SIP can carry a display name in the From header, but US terminating carriers generally ignore it for CNAM purposes. Instead, the terminating carrier performs its own real-time database dip — over SS7/TCAP, SIP, or HTTPS depending on the network — using the calling number as the key, and displays whatever its chosen database returns. The dip typically completes in a fraction of a second; occasionally the phone rings before it finishes and the name pops in a beat after the number.

The practical consequences of this split:

• You control the number you send; you only influence the name. The name comes from databases you must register into, not from anything in your call.
• The number is consistent everywhere; the name is not. Carrier A querying one database may show “ABC PLUMBING” while Carrier B querying another shows “UNKNOWN” for the same call.
• STIR/SHAKEN verifies the number, not the name. STIR/SHAKEN is a cryptographic attestation that the originating carrier vouches for the caller’s right to use the number. CNAM is a text label with no trust judgment attached. You need both managed: an accurate name and a signed, A-level-attested number. A correct CNAM with weak attestation can display alongside a warning; a verified call with a stale CNAM shows a stranger’s name with a checkmark. For the labeling engines, attestation is one input scored alongside calling patterns and complaint data when they decide how to present your call.

How a CNAM lookup works

The end-to-end flow, from origination to display:

Step 1 — Origination. Your PBX or dialer sends a SIP INVITE through your SIP trunk with your calling number in the From header. No name is meaningfully transmitted.

Step 2 — The dip. The terminating carrier — the one serving the person you called — receives the call and, before or while ringing the subscriber, fires a CNAM query using your 10-digit number as the lookup key.

Step 3 — The database answers. The carrier’s CNAM data provider looks up the number and returns the associated 15-character record, or nothing if no record exists.

Step 4 — Display. The carrier passes the returned string to the handset, which renders it next to the number.

Two structural quirks of this flow generate most real-world confusion:

The multi-database problem. Because multiple CNAM databases exist and each terminating carrier picks its own provider, your registered name reaches some databases faster than others — and possibly never reaches a few. This fragmentation, not any single misconfiguration, is the root cause of the inconsistent name display that frustrates operators.

The wireless gap. Traditional CNAM dips remain the primary name source on landlines and VoIP endpoints. On major US wireless networks, what shows for a number outside the recipient’s contacts depends on the carrier’s own caller ID and spam services and on the subscriber’s plan. Verizon, for example, lists caller name ID as a feature of its paid Call Filter Plus tier. Spam labels come from analytics partners — First Orion for T-Mobile’s Scam Shield, Hiya for AT&T’s ActiveArmor and Samsung’s Smart Call, and TNS for Verizon’s Call Filter.

A perfect CNAM record can be irrelevant, or overridden entirely by a spam label, on a wireless handset. That override problem is its own discipline — see what to do about a “potential spam” label.

For wireless spam labels specifically, the highest-leverage single action is the Free Caller Registry (freecallerregistry.com) — a joint registry from First Orion, Hiya, and TNS. One submission of your business details and numbers reaches all three analytics engines, which feed the labels on the three largest US wireless networks. It affects labels, not names: the registry states that neither the engines nor their carrier partners use its data to deliver caller ID name. It complements CNAM registration; it does not replace it. Which portal handles labels for each caller type is sorted in the business phone number registration guide.

Why your caller ID shows the wrong name

If your outbound calls display the wrong name, one of these six causes is responsible.

Stale records. CNAM databases do not update in real time. Changes propagate over roughly 24 to 72 hours, and some databases take longer. If the previous owner of your number was “QUICK LOANS LLC,” that name can linger in some databases for days or weeks after you register your own.

No registration at all. Many VoIP providers provision numbers without ever registering CNAM. The number works, but every dip comes back empty, so handsets show “UNKNOWN” or a generic city-state label derived from the area code. If your carrier did not register CNAM when they provisioned your DID, you are dialing with no name attached.

Porting lag. CNAM records do not transfer automatically when a number ports between carriers. The losing carrier’s record can persist while the gaining carrier registers nothing — unless re-registration is an explicit part of the port workflow.

Truncation. “Northeast Property Management Group” becomes “NORTHEAST PROPE” at 15 characters. Not a bug — a hard spec limit. The fix is choosing a deliberate short form your customers recognize: “NE PROP MGMT” beats a garbled truncation.

Recycled numbers with history. Released numbers get reassigned, and the new holder inherits both the old CNAM record and — more damagingly — the old spam-analytics reputation. Re-registering CNAM fixes the name; the reputation side needs separate remediation.

Wireless-side overrides. As covered above, T-Mobile, Verizon, and AT&T handsets can display their analytics partners’ data instead of your CNAM record — a different name, a spam label, or nothing — based on their own scoring and your attestation. Correct CNAM is necessary but not sufficient on wireless.

Branded calling and Rich Call Data

CNAM’s terminating-side-lookup architecture is the thing the industry is now actively engineering around. The replacement direction is Rich Call Data (RCD) — and its trust model is the inverse of CNAM’s.

RCD became a published standard in July 2025: RFC 9795, an IETF standards-track RFC that extends the STIR/SHAKEN PASSporT. Instead of the terminating carrier fetching a name from a third-party database, the originating provider asserts the caller’s display name — and optionally a logo, an informational URL, and a call reason — inside the cryptographically signed PASSporT that already carries the call’s attestation. The terminating side verifies the signature the same way it verifies any STIR/SHAKEN call. The name arrives with the call, signed, rather than being looked up after the fact.

The commercial wrapper around RCD is CTIA’s Branded Calling ID (BCID) ecosystem, which vets businesses before their branding is displayed. Adoption is real but partial. CTIA announced in September 2025 that Verizon would integrate BCID, and BCID partner Numeracle reported in November 2025 that Verizon and T-Mobile both support BCID as terminating providers. What displays still depends on the recipient’s carrier and handset.

The FCC is pushing in the same direction. In an October 2025 Further Notice of Proposed Rulemaking (FCC 25-76, WC Docket No. 17-97), the Commission proposed — proposed, not adopted — requiring terminating providers that show an A-level attestation indicator on the handset to also transmit a verified caller name, and requiring originating providers to take reasonable measures to verify that name. It also sought comment on mandating RCD for this on IP networks. Check the docket for its current status, and treat RCD display as an emerging advantage, not a compliance requirement.

Where does that leave an operator in 2026? CNAM still determines your name on landlines, VoIP endpoints, and every network segment where RCD has not landed. Branded calling programs govern verified name display on wireless today, and the Free Caller Registry feeds the spam-label side. RCD is the trajectory. SIPNEX’s role in that stack is the carrier layer: we sign your outbound calls directly with our own STIR/SHAKEN SP certificate at A-level attestation — the signed foundation that both today’s analytics engines and tomorrow’s RCD delivery build on.

Managing CNAM on your numbers

What comes with each SIPNEX number is listed on our DID numbers page. Whichever carrier serves your numbers, the working details are the same:

At provisioning. Give your carrier the name string when you order numbers, so the record is registered with its CNAM data provider during provisioning. Propagation across the major databases takes roughly 24 to 72 hours, so request registration when you order and the window runs while you set up campaigns rather than after you start dialing.

Choosing the string. Fifteen characters, all caps by convention, and the most recognizable version of your name rather than the legal entity: “SIPNEX” over “SIPNEX TELECOM LLC.” The test is simple — if a customer saw this on their phone, would they pick up?

At porting. CNAM records do not move with a port, and existing records are frequently stale or missing. Ask the gaining carrier to re-register the name as part of port completion, and to coordinate timing if the record must be corrected before the port finishes.

Ongoing checks. Periodically call a landline (landlines typically perform CNAM dips) from each of your outbound DIDs and note what displays, as part of a broader caller ID test. Wrong or missing names go to your carrier’s support team for verification and re-registration. And because some percentage of calls will always roll to voicemail regardless of what displays, make sure the callback experience holds up too — a professional voicemail greeting is the other half of the first impression.

One honest boundary: a carrier can manage your records in the CNAM ecosystem, but it does not control how wireless carriers’ analytics partners choose to render your calls. For wireless display, submit to the Free Caller Registry and keep your number reputation clean alongside your CNAM records — the operators whose names display correctly everywhere are managing the name, the attestation, and the reputation as one system.

Frequently asked questions

Does CNAM work on cell phones?

Not the way it works on landlines. On major US wireless networks, name display for a number outside the recipient’s contacts depends on the carrier’s own caller ID and spam services and on the subscriber’s plan — Verizon, for example, puts caller name ID in its paid Call Filter Plus tier. Spam labels come from analytics partners: First Orion for T-Mobile, Hiya for AT&T and Samsung’s Smart Call, and TNS for Verizon. Your CNAM record still governs landlines and VoIP endpoints. For wireless labels, also submit your numbers to the Free Caller Registry and monitor your number reputation, because a spam label can override a correct name.

How do I change the name that shows on my caller ID?

Ask your carrier to update the CNAM record for the specific numbers, providing the exact string you want — 15 characters or fewer, the most recognizable form of your business name. If your provider says CNAM updates are “not available for VoIP numbers,” that is a limitation of that provider, not of the technology — a carrier that manages its own CNAM registration can generally update the record for the numbers it serves. Wireless display is a separate channel: the name there comes from the carrier’s own caller ID services or a branded calling program, and the Free Caller Registry covers spam labels, not names.

How long does a CNAM update take?

Plan on 24 to 72 hours for propagation across the major databases, with some databases taking longer. The spread exists because there is no single authoritative CNAM database — multiple providers maintain separate copies that synchronize on their own schedules. During the window, recipients on different carriers may see different names for the same number. Register CNAM at the moment you order new numbers so propagation finishes before you start dialing on them.

---

SIPNEX signs outbound calls directly with our own STIR/SHAKEN SP certificate at A-level attestation, the trust signal that sits alongside your CNAM name. Ask about CNAM on your numbers.