A CLI route delivers your calling number to the terminating network. An NCLI route does not. That single difference drives most of the price gap between wholesale routes — and most of the disappointment when a cheap route underperforms.
By Vedant Vhanyalkar
CLI is the calling party's number, carried with the call so the terminating network can present
it to the called party. On a SIP route it travels in the signalling headers — commonly the
From header, and where the interconnect supports it, P-Asserted-Identity
or Remote-Party-ID. Which header the terminating carrier trusts varies by
interconnect, which is why the same CLI can display on one route and vanish on another.
NCLI describes a route where the calling number does not reach the called party. That can happen three ways, and the distinction matters when you are diagnosing a route:
All three look identical on the handset. They are very different problems, and only the first is something the buyer chose.
Some routes present a number that is neither the caller's nor absent — a rotating or randomised value. This is sold as CLI, prices like CLI, and is not the same thing. If the presented number cannot receive a return call, treat it as its own category and test it separately.
The gap between CLI and NCLI answer rates is behavioural before it is technical. A handset receiving a CLI call displays a number, and often a name if the destination network supports CNAM lookup. An NCLI call displays "unknown", "private", "no caller ID" or nothing at all. A large share of people do not answer those, and the share is growing as handset-level call screening becomes default rather than opt-in.
This is why a route that looks cheaper per minute can be more expensive per connected call. The arithmetic that matters is cost per answered minute, not cost per minute — and that number cannot be read off a rate sheet.
Answer rate is not the only loss. Carrier-side analytics, handset features and network filters all treat missing or untrusted CLI as a signal. Traffic can be blocked, diverted to voicemail, or flagged before it ever reaches a handset. When that happens the call may still bill as answered upstream while never reaching a human, which distorts any ASR you calculate from supplier reports rather than your own CDRs.
A CLI call can be returned. For any campaign where the called party might call back — support callbacks, appointment confirmation, collections, verification — NCLI removes that entire channel. The cost of the route is then only part of the cost of the decision.
CLI is not a property of your traffic. It is a property of every interconnect the call crosses. A direct interconnect into the terminating network has one opportunity to strip or rewrite the calling number. A route that transits three intermediate carriers has three, and you have visibility into none of them.
This is the usual explanation when the same traffic, from the same platform, with the same headers, presents CLI on one supplier and arrives anonymous on another. Nothing changed at your end. The path changed.
Most wholesale routing is dynamic. A supplier's least-cost logic can send today's traffic down a different carrier chain than yesterday's, at the same contracted rate. If that new chain does not carry CLI, your answer rate drops without any change you made or were told about.
Two consequences follow. Monitor CLI delivery continuously rather than at onboarding — a route accepted on a good test can drift within weeks. And when answer rate falls, check CLI delivery before you rewrite the campaign; the cause is more often routing than messaging.
In markets with caller-name lookup, the terminating network queries a database using the CLI to display a name. That is a separate system with its own coverage. A call can deliver CLI perfectly and still show no name, because the number is absent from the CNAM database — not because the route is faulty.
Worth separating when you are diagnosing, because "our name isn't showing" and "our number isn't showing" have different causes and different fixes.
These get conflated and should not be. Placing a call without presenting a number is not, in itself, unlawful in most jurisdictions. Presenting a number you have no right to use, in order to mislead the called party, generally is. NCLI is an absence; spoofing is a misrepresentation. Regulators treat them differently, and so should your compliance policy.
STIR/SHAKEN authenticates the calling number by signing it, then verifying that signature downstream. A call carrying no calling number gives the framework nothing to sign. In practice NCLI traffic into the US either fails attestation or lands at the lowest attestation level, and terminating networks increasingly use that signal in how they present, filter or label a call.
The direction of travel is consistent across markets even where the framework differs: networks are becoming less tolerant of traffic that cannot identify itself. A route economical today on answer rate alone may not remain viable on delivery.
CLI obligations are set nationally, not globally. Some regulators require CLI on specific call types, some require it be reachable, and some mandate that international-origin traffic presenting a domestic number be blocked outright. Before you buy a route for a destination, confirm the rule for that destination — a route that is fine in one country can be undeliverable in the next.
Route labels describe intent. Only a termination test tells you what the terminating carrier does with your CLI. Place calls to real handsets on the destination network, on more than one mobile operator, and record what is displayed. Repeat at different times — behaviour can change with routing, and a route tested once at 3am is not a route you have tested.
Read them together. ASR alone can be raised by mechanisms that do not produce conversations, which is precisely why it is the number most often quoted in isolation.
Compare routes on cost per answered call, using your own CDRs rather than supplier summaries. A CLI route at a higher rate frequently costs less per outcome than an NCLI route at half the price. It is the same arithmetic used for any acquisition channel, and it is routinely skipped in route buying.
There are legitimate cases. Capacity and failover testing, internal transit between your own platforms, and destinations where the terminating network will not accept foreign-origin CLI under any arrangement. The decision only goes wrong when NCLI is bought as a cheaper substitute for CLI on customer-facing traffic. It is not a substitute; it is a different product.
Route decisions are commonly made on rate per minute. That is the one number guaranteed not to answer the question you are asking. Here is the comparison in the shape it should take — figures below are illustrative, to show the method, not MCC rates or a claim about any route.
| Metric | CLI route (example) | NCLI route (example) |
|---|---|---|
| Rate per minute | higher | lower |
| Answer rate | higher | materially lower |
| Average call duration | longer | shorter |
| Return calls possible | yes | no |
| Attestation into US | possible | lowest or none |
| Cost per answered call | the only column that decides anything | |
Populate that final row from your own CDRs, per destination, over a period long enough to survive routing changes. Suppliers report on their side of the call; you are buying outcomes on yours. Where the two disagree, yours is the one that pays.
Do it per destination, not in aggregate. CLI behaviour varies enormously between countries and between mobile operators inside one country. A blended figure across a mixed destination mix hides exactly the detail you are trying to find.
When CLI disappears, the cause is usually one of a small set. Working through them in order saves time, because the cheapest checks eliminate the most common causes.
Capture the signalling leaving your platform and check which headers carry the number. A
mismatch between From and P-Asserted-Identity is a frequent cause of
suppression, because the terminating side cannot decide which to trust.
Check format and allocation. An E.164 number in an unallocated range, or a national-format number sent to an international interconnect, will often be dropped rather than displayed.
If CLI displays on one mobile network in the destination and not another, the route is partially delivering. That is a routing conversation with your supplier, not a configuration problem at your end.
Not ASR. The proportion of completed calls where CLI was presented, broken out by destination. A supplier who cannot produce it usually cannot see it either, which tells you something about how many hops the traffic is taking.
A reduced rate frequently means a different carrier chain. If the price moved and nobody explained why, assume the path moved and test again.
Related reading: CC Routes, Wholesale Voice, What Is SIP Trunking?.
MCC provisions CC routes and wholesale voice termination by traffic profile. Availability of CLI and NCLI presentation varies by destination — confirm coverage for yours.