LIDB, CNAM, and the Alphabet Soup of Caller ID

TL;DR

What a prospect sees on their phone is the output of a cooperating stack: ANI, STIR/SHAKEN attestation (codified in 47 CFR Part 64 Subpart HH), LIDB CNAM dip, and an analytics verdict from Hiya Inc., Transaction Network Services (TNS), or First Orion. Every one of those layers has a known failure mode. Knowing which layer is broken is the difference between fixing the problem and guessing at it.

When a call hits a consumer phone, what the screen displays is the output of a small stack of databases, dips, attestations, and analytics verdicts — each owned by a different entity, each with its own refresh cycle, each with its own failure mode. Understanding this stack is the difference between guessing why a number is flagged and actually diagnosing it. This post walks through every acronym in the chain, plain English, in the order they touch the call.

The path of an outbound call

Here is what happens between the moment your agent presses dial and the moment the prospect's phone displays something.

1. Your PBX sends a SIP INVITE to your trunk provider with the ANI (calling number) and optionally a display name.
2. The trunk provider (your originating carrier) attaches a STIR/SHAKEN attestation and routes the call toward the terminating carrier.
3. The terminating carrier receives the INVITE, looks up the ANI in the LIDB to retrieve the registered caller name (the CNAM dip).
4. The terminating carrier runs the ANI through its analytics pipeline (Hiya, TNS, First Orion, or carrier-internal).
5. The handset OS and carrier overlay decide what to display.

Each step introduces acronyms. Here is the full soup.

ANI — Automatic Number Identification

The ANI is the calling number — the number that actually originated the call. It is the single most important identifier in the entire stack. Analytics engines, LIDB lookups, and attestation all key off the ANI.

Not to be confused with the display number (which can differ via call forwarding or spoofing). For legitimate outbound sales, ANI and display number should be identical — spoofing the display number is prohibited under the Telephone Robocall Abuse Criminal Enforcement and Deterrence (TRACED) Act (FCC TRACED Act Implementation).

CNAM — Caller Name

CNAM is the caller name string — up to 15 characters, all-caps in most legacy systems — that identifies the calling party. It is not stored with the call itself; it is retrieved on the terminating side via a LIDB dip.

Key fact: CNAM is tied to the number in the LIDB, not to the call. You cannot dynamically change CNAM per-call. Changing CNAM means updating the LIDB record for that number, which takes 24-72 hours to propagate.

LIDB — Line Information Database

LIDB is the industry-wide distributed database that stores the caller name and line-type data for each phone number. Every mobile and landline carrier operates or subscribes to LIDB services.

When the terminating carrier receives a call, it performs a CNAM dip — a query against LIDB — to retrieve the caller name for the ANI. The dip typically takes under a second.

LIDB records are owned by the carrier that holds the number. If you own a DID through a wholesale trunk provider, that provider (or its upstream carrier) writes the LIDB entry on your behalf. This is where most CNAM problems originate:

CNAM dip vs. P-Asserted-Identity

Two competing ways a caller name can reach the display:

• LIDB CNAM dip: terminating carrier looks up the ANI in LIDB. This is authoritative and the dominant path for US mobile.
• P-Asserted-Identity (PAI): the originating SIP header can include a display name. Some carriers honor it; most prefer LIDB.

Conflicts between the two (your SIP INVITE says "JOHN AGENCY" but LIDB says "UNKNOWN") are treated as suspicious by analytics engines. Keep them aligned.

RespOrg — Responsible Organization

RespOrg is the carrier or trunk provider that "owns" the number from an industry perspective — the entity listed in the SMS/800 database (for toll-free) or the assigned holder in the local number portability database (for geographic numbers). Reputation scoring often aggregates at the RespOrg level: if a RespOrg is associated with high-risk outbound traffic, numbers under it inherit partial baseline risk.

For agencies, this means the choice of wholesale trunk provider matters beyond price and features. Low-cost providers that accept any sign-up and resell to anonymous outbound operations build a RespOrg reputation that your numbers will inherit.

Sub-CSP / OCN

Even inside a RespOrg, numbers are assigned at the OCN (Operating Company Number) or sub-CSP level. Analytics engines can cluster at this sub-tier. Two DIDs from the same reseller but different upstream OCNs may have completely different reputation baselines.

STIR/SHAKEN

STIR (Secure Telephone Identity Revisited) and SHAKEN (Signature-based Handling of Asserted information using toKENs) together are the US standard for authenticating caller identity, codified at 47 CFR § 64.6301 and expanded in subsequent FCC orders closing the non-IP gap (FCC Fact Sheet, April 7, 2025). Every call gets an attestation level:

STIR/SHAKEN answers "is this call authorized" not "is this call wanted." An A-attested spam call is still a spam call. But a B or C attestation is an additional negative signal that can tip a borderline call into labeling. TNS reported that signed traffic between Tier-1 US carriers reached 85% in 2023 but only 17% between Tier-1 and smaller carriers (TNS 2024 Robocall Investigation Report) — meaning attestation quality varies substantially with the terminating carrier's peer set.

Your goal: every outbound DID should be A-attested. If your trunk provider is delivering B or C, either your DIDs are not properly registered on their end, or your provider's attestation practices are weak.

The analytics providers: Hiya, TNS, First Orion

These are the three major third-party analytics providers that partner with mobile carriers to score and label incoming calls. Each maintains its own reputation database built from:

• Call-pattern signals (volume, duration, answer rate)
• Crowdsourced user reports ("spam" button on the handset)
• Business registration data (Free Caller Registry, branded programs)
• Carrier-internal complaint data

Different mobile carriers partner with different providers. A number clean at one provider can be flagged at another (Hiya, "How carriers label spam calls"). See our spam-label remediation playbook for how to dispute at each.

First Orion reports that up to 87% of consumers ignore calls from unknown numbers (First Orion INFORM), which is why the analytics display layer has become the single most consequential part of the stack for outbound callers.

FCR — Free Caller Registry

FCR is a free registration service jointly operated by Hiya, TNS, and First Orion (launch announcement) that feeds baseline business data to all three analytics providers from a single intake. It is not a silver bullet, but it is the minimum bar — an unregistered DID making outbound calls has zero positive signal to offset any negative behavior.

RND — Reassigned Numbers Database

The Reassigned Numbers Database, operated by Somos Inc. under FCC authorization, lets callers check whether a consumer number has been permanently disconnected or reassigned since a known consent date. Checking the RND provides a Telephone Consumer Protection Act (TCPA) safe harbor for consent-based calls (Somos announcement) and prevents you from inheriting a prior owner's reputation problems on DID acquisition.

DNO — Do Not Originate

DNO is a list of numbers that should never originate calls (e.g., IRS inbound-only lines, invalid numbers). Calls originating from DNO numbers are blocked at the network layer. The FCC broadened DNO use in February 2025 to target numbers "highly likely to be illegal" (FCC enforcement update). Not relevant for legitimately owned DIDs but worth knowing as part of the stack.

The full stack at a glance

Common failure modes mapped to the stack

What to do with this knowledge

Three takeaways for agency operators:

1. Know which layer a problem lives in. "Our numbers are flagged" is not a diagnosis. Is it LIDB (fixable), analytics (remediable), or RespOrg (change provider)?
2. Keep every layer consistent. ANI = LIDB CNAM = PAI display name = registered FCR entity. Mismatches across layers are treated as suspicious.
3. Audit the whole stack regularly. The 10-minute self-audit touches each layer quickly.

Glossary

<dl> <dt>ANI</dt> <dd>Automatic Number Identification — the actual calling number attached to the call.</dd> <dt>CNAM</dt> <dd>Caller Name — up to 15-character string stored in LIDB, retrieved by the terminating carrier.</dd> <dt>LIDB</dt> <dd>Line Information Database — distributed industry directory of per-number name and line data.</dd> <dt>RespOrg</dt> <dd>Responsible Organization — the carrier or trunk provider that administratively owns the number.</dd> <dt>OCN</dt> <dd>Operating Company Number — sub-tier grouping inside a RespOrg, used for cluster scoring.</dd> <dt>STIR/SHAKEN</dt> <dd>Secure Telephone Identity Revisited / Signature-based Handling of Asserted information using toKENs — US caller-authentication framework.</dd> <dt>PAI</dt> <dd>P-Asserted-Identity — optional SIP header carrying a display name, usually overridden by LIDB on mobile.</dd> <dt>FCR</dt> <dd>Free Caller Registry — joint intake for Hiya, TNS, and First Orion business registration.</dd> <dt>RND</dt> <dd>Reassigned Numbers Database — FCC-mandated database for TCPA safe-harbor verification.</dd> <dt>DNO</dt> <dd>Do Not Originate — industry list of numbers blocked from originating calls.</dd> </dl>

FAQ

Q: Can I force a specific CNAM on a per-call basis? A: No, not reliably. You can set PAI, but most terminating carriers ignore it in favor of the LIDB dip. CNAM is a property of the number, not the call.

Q: How often does LIDB propagate? A: Updates typically propagate in 24-72 hours, but lingering cached entries at individual carriers can persist for up to a week.

Q: Is there a central place to check what my CNAM dip returns? A: Most wholesale trunk providers offer a dip lookup in their portal, and the LineAudit free check includes dip verification.

Q: What is the difference between "CNAM storage" and "CNAM delivery"? A: Storage = writing the record into your LIDB node. Delivery = terminating carrier dipping and displaying it. You pay for storage; delivery depends on the terminating carrier's dip behavior.

Q: Does STIR/SHAKEN cost extra? A: Attestation is baked into most US trunk providers' service per 47 CFR § 64.6301. Quality of attestation varies — ask your provider for their attestation rate.

Q: If I own a DID, can any other party write to my LIDB record? A: Only with your authorization (usually your trunk provider acts on your behalf). Unauthorized writes indicate a serious provisioning or security problem.

Q: Does a toll-free number have a different stack? A: Toll-free uses the SMS/800 database instead of standard LIDB for some data, and RespOrg is more visible as an identifier. Analytics and attestation layers are otherwise similar.

Q: Where does the Reassigned Numbers Database fit if I do not cold-call? A: Even for warm or opt-in calls, the RND provides the FCC's TCPA safe-harbor and prevents inheriting prior-owner bad reputation. It is useful on any DID acquisition, not just cold campaigns.

Q: What is the Free Caller Registry protecting me from? A: It does not block labels, but it provides a positive business-registration signal that tempers how Hiya, TNS, and First Orion weight behavioral signals. Without it, negative signals have nothing to counterbalance them.

Q: How do I verify my STIR/SHAKEN attestation level? A: Your trunk provider's call detail records should include the attestation level per call. If they do not expose it, that is itself a sign the provider is not actively managing attestation quality.

The bottom line

Caller ID is not one system — it is five or six cooperating systems, each with its own failure modes. The acronyms are not window dressing; each one corresponds to a layer where your number's reputation can break. Know the stack, and you can diagnose any display problem in minutes.

Related: CNAM uniformity and branding and spam-label remediation.

---

Stop guessing. Run the audit.

LineAudit checks your first 20 DIDs free. You'll see exactly which numbers are flagged, mis-registered, or at risk — in 30 seconds.

Run Free Audit →

---