Troubleshooting · Symptoms
Wrong Caller ID: Name, Number and 'Spam Likely'
Your outbound calls display a stranger's business name, an old employee's name, a raw number with no name at all — or, worst of all in 2026, get labeled 'Spam Likely' and ignored. Caller ID feels like one setting; it is actually three separate systems that must agree: the number your system presents, the name databases attach to that number, and the attestation your carrier signs about the call's legitimacy.
Each symptom maps to one system. Fixing the wrong one changes nothing, which is why caller-ID tickets go in circles.
The three systems
| What recipients see | Controlled by | Where to fix |
|---|---|---|
| Wrong NUMBER (or a number you don't recognize) | Your PBX/trunk outbound identity (From / P-Asserted-Identity), or the carrier's default | Your dial plan/trunk settings: per-user and per-trunk caller ID; confirm the carrier permits presenting that DID (you must own/control it) |
| Right number, wrong NAME | CNAM databases at the receiving side: your carrier submits your name (15-char limit, US practice) to registries that terminating carriers query | Ask your carrier to correct the CNAM submission for each DID; allow days for databases to converge; name changes do not propagate instantly |
| 'Spam Likely' / blocked / no name on mobiles | STIR/SHAKEN attestation level + analytics engines at the receiving carrier | Attestation: calls must leave through a carrier path that signs them with A-level attestation for numbers you own; analytics: register numbers with the major carriers' caller-ID reputation services and keep calling patterns legitimate |
STIR/SHAKEN in one paragraph
STIR/SHAKEN is the FCC-mandated framework in which the originating carrier cryptographically signs calls, attesting how well it verified the caller and their right to the number: A (fully verified customer and number), B (customer verified, number not fully), C (gateway — call merely passed through). Calls that traverse resellers, foreign gateways or mismatched trunk configurations lose or downgrade attestation, and receiving carriers combine the level with behavior analytics to label or block. If your calls are signed at B/C or unsigned while competitors' show clean, the fault is in your carrier chain — your provider must tell you the attestation your calls actually receive, in writing.
Fix sequence by symptom
- Wrong number: check the extension's and trunk's outbound caller-ID settings; place a test call to your mobile and capture the presented identity; confirm with the carrier that the DID is authorized for presentation on that trunk.
- Wrong name: submit a CNAM correction through your carrier for each affected DID (exact legal/trading name, ≤15 characters); verify after several days from multiple carriers — databases converge at different speeds.
- Spam labeling: ask your provider for your calls' STIR/SHAKEN attestation level; if it is not A for your own numbers, escalate until it is or change the carrier path.
- Register your numbers with the major US carriers' caller-ID/reputation portals (your provider can tell you the current programs) and submit false-positive reports with call examples.
- Audit your own calling behavior: high-volume short-duration outbound patterns from few numbers trip analytics regardless of paperwork — spread legitimately across your DID range where appropriate.
Frequently asked questions
- Why does the name show correctly on landlines but not mobiles (or vice versa)?
- Because name lookup and spam analytics are run by different databases and engines per terminating carrier. There is no single caller-ID switchboard; each receiving network presents what its sources tell it, which is why verification must sample several carriers.
- We changed our business name months ago; old name still shows.
- CNAM updates propagate slowly and some databases only refresh on carrier resubmission. Re-submit through your carrier and keep the ticket open with dated recipient examples until the major databases converge.
- Can we present our main number for all outbound calls?
- Yes, if your carrier authorizes it (you own the number) — a common and legitimate configuration. Attestation stays A-level when the presenting carrier is your number's carrier of record or has the right agreements in place.