CNAM Lookup Explained: What It Is, How It Works, and Why It Matters
You have probably looked at your phone, seen an incoming call from “WIRELESS CALLER” or “CITY STATE” or some business name you have never heard of, and wondered where that information comes from. Or worse — you run a legitimate business, you are placing outbound calls to customers who expect to hear from you, and your caller ID displays the name of the company that owned your phone number three years ago. Your customers do not answer because they do not recognize the name. Your answer rates drop. You blame your dialer, your carrier, your leads — but the actual problem is a 15-character text string sitting in a database you have never heard of.
That database is CNAM, and understanding how it works is essential for any operation that depends on outbound calling. This guide is written by SIPNEX, an FCC-licensed carrier that holds its own STIR/SHAKEN Service Provider certificate. We provision DIDs across every North American area code and we manage CNAM records as part of our carrier operations. What follows is the carrier-side view of how caller ID names actually work.
What CNAM is
CNAM stands for Calling Name. It is the name string — a maximum of 15 characters — that displays on the recipient’s phone alongside the calling phone number when an inbound call arrives. When your phone shows “JOHN SMITH” or “ABC PLUMBING” next to an incoming number, that name came from a CNAM lookup.
CNAM is not part of the phone call itself. The calling party’s phone system does not transmit the name. Instead, the name is looked up by the terminating carrier (the carrier serving the person being called) at the moment the call arrives. The terminating carrier queries a CNAM database using the calling phone number as the key, retrieves the associated 15-character name record, and passes it to the recipient’s handset for display.
This is a critical distinction that most people misunderstand. You do not send your caller ID name with your call. The recipient’s carrier looks it up independently. This means the name displayed depends on which database the terminating carrier queries, how recently that database was updated, and whether a record exists for your number at all.
CNAM records are stored in databases historically called LIDB — Line Information Database. The LIDB system was built for the landline telephone network in the 1980s and 1990s. It was designed for a world where phone numbers were permanently assigned to physical copper lines at fixed addresses, owned by one of a handful of local telephone companies. That world no longer exists, but the CNAM infrastructure still largely operates on its assumptions.
The 15-character limit is a legacy of the original Bellcore specification for LIDB. It was designed for names like “SMITH JOHN” or “US GOVERNMENT” — short enough to display on the single-line LCD screens of early caller ID units. In 2026, your smartphone can display a full paragraph, but the CNAM record is still capped at 15 characters. “SIPNEX TELECOM” fits. “SIPNEX TELECOMMUNICATIONS LLC” does not — it would be truncated to “SIPNEX TELECOMM” and the rest discarded.
How CNAM lookup works end to end
Here is the complete technical flow of a CNAM lookup, from origination to display.
Step 1: Call origination. Your PBX or dialer places an outbound call through your SIP trunk. The SIP INVITE contains your calling number in the From header. It does not contain a caller name — SIP can carry a display name in the From header, but most terminating carriers ignore it for CNAM purposes and perform their own lookup instead.
Step 2: Call reaches the terminating carrier. The carrier serving the called party receives the inbound call with the calling number. Before (or simultaneously with) ringing the subscriber’s phone, the terminating carrier initiates a CNAM dip — a real-time database query using the calling number as the lookup key.
Step 3: CNAM database query. The terminating carrier queries its CNAM data provider. There are several major CNAM database providers in North America: iconectiv (formerly Neustar/Telcordia), Transaction Network Services (TNS), Broadforward, and others. Each carrier has agreements with one or more of these providers. The query goes out, the provider looks up the 10-digit calling number in its database, and returns the associated 15-character name record.
Step 4: Display. The terminating carrier passes the name to the subscriber’s handset. The phone displays it alongside the calling number. The entire process — from call arrival to CNAM display — takes 100 to 300 milliseconds. In some cases, the phone rings before the CNAM lookup completes, and the name appears a moment after the number.
The multi-database problem. There is no single, authoritative CNAM database for all of North America. Different providers maintain different databases with different records. When you register a CNAM record for your phone number, that record propagates to some databases but not necessarily all of them. Carrier A querying iconectiv might display “ABC PLUMBING” for your number, while Carrier B querying a different provider might display “WIRELESS CALLER” or nothing at all. This fragmentation is the root cause of the inconsistent caller ID experience that frustrates operators.
Wireless vs landline CNAM. This is the biggest gap in the system. Landline numbers have historically been well-represented in CNAM databases because the incumbent local exchange carriers (ILECs) maintained LIDB records as part of their network operations. Wireless numbers are a different story. Wireless carriers are not required to populate CNAM databases, and many do not — or they maintain their own proprietary databases that are not shared with the broader LIDB ecosystem. This is why calls from cell phones often display “WIRELESS CALLER” or “CELL PHONE TX” instead of the subscriber’s name. It is also why VoIP numbers — which are even newer to the system than wireless — often have no CNAM record at all unless the VoIP carrier explicitly registers one.
Branded calling programs. Major wireless carriers have introduced branded calling initiatives that bypass traditional CNAM entirely. T-Mobile’s Branded Caller ID, AT&T’s Branded Call, and Verizon’s Verified Calls allow businesses to register their name, logo, and call reason for display on subscriber handsets. These programs use carrier-specific databases and APIs, not the traditional LIDB/CNAM infrastructure. They offer richer display (logos, call reason text, verification badges) but require separate registration with each carrier. For high-volume outbound operations, branded calling registration is increasingly important alongside traditional CNAM management.
Why your caller ID shows the wrong name
If you have ever seen the wrong business name on your outbound calls, one of these six causes is responsible.
Stale CNAM records. CNAM databases do not update in real time. When you register or change a CNAM record, the update propagates through the database ecosystem over 24 to 72 hours — and in some cases longer. During that propagation window, some carriers will display the old name and others will display the new one. If the previous owner of your phone number was “QUICK LOANS LLC,” that name may persist in some databases for days or weeks after you register your own business name.
VoIP numbers with no CNAM registration. Many VoIP providers provision phone numbers without registering a CNAM record. The number works for placing and receiving calls, but when the terminating carrier performs a CNAM lookup, there is no record — so the phone displays a generic label like “UNKNOWN” or the city and state associated with the area code prefix. If your carrier did not register CNAM when they provisioned your DID, you are calling with no name attached to your number.
Number porting lag. When you port a phone number from one carrier to another, CNAM records do not transfer automatically. The losing carrier’s CNAM record may persist in databases for the number, while the gaining carrier may not register a new record until after the port completes — or at all, if you do not request it. During and after a port, your caller ID name can display anything from the previous owner’s name to your old carrier’s name to nothing.
The 15-character truncation problem. Your business is called “Northeast Property Management Group.” You register that as your CNAM. The database stores “NORTHEAST PROPE” — the first 15 characters. The recipient sees a garbled, truncated name that looks unprofessional. This is not a bug; it is a hard limit of the CNAM specification. The fix is to choose a CNAM-friendly abbreviated version of your name: “NE PROP MGMT” or “NORTHEAST PM” or whatever fits in 15 characters while remaining recognizable to your customers.
Recycled numbers with bad history. Phone numbers are recycled. When a carrier releases a number (because a subscriber canceled, a business closed, or a VoIP provider released unused inventory), that number eventually gets reassigned to a new subscriber or provisioned to a new customer. But the CNAM record — and more critically, the spam reputation and analytics flags from services like Hiya and TNS — may still reflect the previous owner. If that previous owner was a robocaller, you inherited their reputation along with their number. CNAM re-registration helps with the name display, but the analytics reputation requires separate remediation through the relevant platforms.
T-Mobile and proprietary display overrides. T-Mobile’s Scam Shield and branded calling program can override CNAM entirely. Even if your CNAM record is correct and up to date, T-Mobile may display a different name (or no name) based on its own analytics data, your STIR/SHAKEN attestation level, and whether you have registered with their branded calling program. This is frustrating but increasingly common as carriers invest in their own caller identification systems that operate independently of traditional CNAM.
CNAM vs STIR/SHAKEN
Operators frequently confuse CNAM and STIR/SHAKEN because both relate to caller ID, but they solve completely different problems.
CNAM answers: what name should we display? It is a database lookup that returns a text string. It makes no judgment about whether the caller is legitimate, whether they have the right to use the number, or whether the call is wanted. CNAM is purely informational — a label, nothing more.
STIR/SHAKEN answers: should we trust this caller ID claim? It is a cryptographic verification that the originating carrier has attested to the caller’s authority over the phone number. It determines whether the call is displayed as “Verified Caller” or flagged as potential spam. STIR/SHAKEN is a trust signal — a judgment, not a label.
These two systems are complementary, not competing. A call can have:
Correct CNAM + A-level attestation: The ideal state. The recipient sees your business name and a verification indicator. This produces the highest answer rates.
Correct CNAM + B-level attestation: Your name displays correctly, but the attestation is partial. Some carriers may still flag the call or display a warning alongside your name. The recipient sees “ABC PLUMBING” but also sees a caution indicator. Confusing and trust-eroding.
Wrong CNAM + A-level attestation: The call is verified as legitimate, but the name displayed is wrong — maybe the previous owner or a generic label. The recipient sees “QUICK LOANS LLC” with a verification badge. They do not answer because the name is unfamiliar, despite the trust signal.
No CNAM + C-level attestation: No name, no trust verification. The recipient sees a bare phone number with a “Potential Spam” label. This call does not get answered.
The takeaway: you need to manage both systems. Register accurate CNAM with your carrier. And make sure your carrier provides A-level STIR/SHAKEN attestation — which requires being on a direct carrier that holds its own SP-KI certificate, not a reseller that inherits B-level from upstream.
Managing your CNAM as a SIPNEX customer
When you provision DIDs through SIPNEX, we provide CNAM registration as part of the service. Here is how the process works and what you should know.
Initial registration. When you order new DIDs, we can register your CNAM record at the time of provisioning. Provide us with your preferred 15-character (or shorter) business name and we submit it to our CNAM database provider. The record propagates within 24 to 72 hours to the major databases.
Choosing your CNAM string. Keep it under 15 characters. Use your recognizable business name, not your legal entity name. “SIPNEX” is better than “SIPNEX TELECOM” which is better than “SIPNEX TELECOM LLC.” All caps is the convention — CNAM databases traditionally store records in uppercase. Avoid abbreviations that your customers would not recognize. Test the name by asking yourself: if a customer saw this on their phone, would they pick up?
Ported numbers. When you port numbers to SIPNEX, the existing CNAM records may be stale or incorrect. We re-register CNAM as part of the porting completion process. If you need the CNAM updated before the port completes (because you are already calling on those numbers through a different trunk), let us know and we can coordinate timing.
Update timelines. CNAM changes are not instant. Expect 24 to 72 hours for propagation across the major databases. Some smaller carriers with less frequent database synchronization may take longer. During the propagation window, some recipients will see the old name and others will see the new one. This is normal and there is no way to accelerate it — it is an artifact of the distributed database architecture.
Monitoring. Periodically test your caller ID by calling landline numbers (which reliably perform CNAM lookups) and noting what name displays. Call your own landline from each of your outbound DIDs. If you see incorrect names, stale records, or “WIRELESS CALLER” / “UNKNOWN” labels, contact SIPNEX support and we will verify and update the records.
The wireless display caveat. You control your CNAM records in the LIDB ecosystem. You do not control how T-Mobile, Verizon, or AT&T choose to display caller information on their wireless subscribers’ phones. They may use your CNAM record, they may override it with their own branded calling data, or they may suppress it entirely based on their analytics scoring of your number. For maximum control over wireless display, consider registering with each carrier’s branded calling program in addition to maintaining your CNAM records. This is additional effort but increasingly necessary for high-volume outbound operations where wireless recipients are the majority of your call targets.
The business impact of CNAM management
CNAM management is not a technical checkbox — it directly impacts revenue for any operation that depends on answered outbound calls.
Consider the math. Your call center runs 50,000 outbound calls per month. Your current answer rate is 12 percent — 6,000 answered calls. You discover that 30 percent of your DIDs are displaying the wrong business name or “WIRELESS CALLER” because CNAM was never registered or is stale from a previous owner. You fix the CNAM records on those numbers. Answer rate on the corrected numbers increases by 3 to 5 percentage points because recipients now see a recognizable business name instead of a suspicious or unfamiliar label.
That 3 to 5 percent increase on 30 percent of your calls represents roughly 450 to 750 additional answered calls per month. At any reasonable conversion rate and average deal value, the revenue impact dwarfs the effort required to manage CNAM records. And unlike STIR/SHAKEN attestation (which requires the right carrier) or reputation management (which requires ongoing monitoring), CNAM registration is a one-time action per DID that pays dividends on every call placed from that number.
The operators who dominate answer rates in 2026 are managing all three layers simultaneously: CNAM (correct name display), STIR/SHAKEN (A-level attestation from a direct carrier), and reputation monitoring (proactive flagging remediation). Any one layer alone is insufficient. All three together create a caller ID profile that passes every filter, displays correctly on every handset, and gives the recipient confidence that the call is worth answering.
Frequently asked questions
What is CNAM in telecom?
CNAM stands for Calling Name. It is the name — up to 15 characters — that displays on the recipient’s phone when an incoming call arrives. The name is not transmitted with the call. Instead, the terminating carrier (the carrier serving the person being called) performs a real-time lookup against a CNAM database using the calling number, retrieves the associated name record, and passes it to the handset for display. The system dates back to the LIDB (Line Information Database) infrastructure built for the landline telephone network. In the modern VoIP environment, CNAM records must be explicitly registered by the originating carrier or the number owner — they do not populate automatically.
How do I update my CNAM or caller ID name?
Contact your carrier and request a CNAM update for the specific phone numbers you want to change. Provide the exact name string you want displayed — keep it under 15 characters and use the most recognizable version of your business name. On SIPNEX, we handle CNAM registration directly as part of DID provisioning and can update records on request. Changes propagate through the CNAM database ecosystem within 24 to 72 hours. During propagation, some recipients may see the old name while others see the new one. If your carrier cannot update your CNAM or tells you it is “not available for VoIP numbers,” that is a carrier limitation — not a technical one. Switch to a carrier that manages CNAM as a standard part of DID service.
Why does my caller ID show a different business name?
The most common cause is a stale CNAM record from a previous owner of your phone number. Phone numbers are recycled, and the CNAM database may still contain the previous owner’s registration. Other causes: your carrier never registered a CNAM record when they provisioned the number (common with VoIP providers that skip CNAM registration), the record was truncated because your business name exceeds 15 characters, or the terminating carrier is querying a CNAM database that has not yet received your update. To fix it: confirm with your carrier that CNAM is registered for each of your DIDs, verify the exact name string stored, and allow 72 hours for propagation after any changes.
Is CNAM the same as STIR/SHAKEN?
No. They solve different problems and operate independently. CNAM determines what name displays on the recipient’s phone — it is a database lookup that returns a text label. STIR/SHAKEN determines whether the caller ID claim is trustworthy — it is a cryptographic verification by the originating carrier that the caller is authorized to use the phone number. You need both: correct CNAM registration so your business name displays, and A-level STIR/SHAKEN attestation so the call is not flagged as spam. A call with correct CNAM but bad attestation may show your name alongside a spam warning. A call with good attestation but wrong CNAM may be verified but show an unfamiliar name that the recipient does not answer. Managing both systems together produces the best answer rates.
How long do CNAM updates take to propagate?
Expect 24 to 72 hours for a CNAM change to propagate across the major databases. The variation exists because there is no single authoritative CNAM database — multiple providers (iconectiv, TNS, and others) maintain separate databases that synchronize on different schedules. Some smaller carriers with infrequent database updates may take even longer. During the propagation window, your caller ID name will display differently depending on which carrier the recipient uses and which database that carrier queries. There is no way to accelerate propagation — it is an inherent limitation of the distributed database architecture. For new DID provisioning, request CNAM registration at the time you order the numbers so the 72-hour propagation window runs while you are setting up your campaigns rather than after you have started dialing.
SIPNEX is an FCC-licensed carrier that registers CNAM as part of standard DID provisioning. We pair accurate CNAM with direct A-level STIR/SHAKEN attestation so your calls display the right name and the right trust signal. Request DIDs with CNAM or see our rates.
SIPNEX
FCC-licensed carrier with its own STIR/SHAKEN SP certificate. Operator-owned. SIP trunks built for operators who dial at volume.