If you've ever looked at a wholesale rate deck, you'll have seen the same destination listed twice at very different prices — once as "CLI" and once as "non-CLI" (sometimes "NCLI" or "grey"). The cheaper one is tempting. This article explains what actually changes between the two, and which of your traffic belongs on each.
What CLI means
CLI stands for Calling Line Identification — the caller ID number the person you're calling sees on their screen. In SIP it's carried in the From header, and often also in P-Asserted-Identity.
A route is described as CLI when the carrier guarantees your number arrives at the destination unchanged. It's non-CLI when there's no such guarantee: the number may be replaced by a random local number, shown as "unknown", or dropped completely.
The difference isn't a setting someone flips. It comes from how the call physically reaches the destination network.
Why non-CLI routes exist
International calls are expensive to terminate because the receiving operator charges an interconnect (termination) fee. In some countries that fee is high — particularly for mobiles.
Non-CLI routes usually avoid part of that fee. Common ways they do it include:
- SIM-box or GSM gateway termination — the call is pushed into a box full of local SIM cards, so it arrives as a cheap local mobile call. The callee sees the SIM's number, not yours.
- Grey or unofficial interconnects that don't pay the full international rate.
- Least-cost routing chains where the call passes through several carriers, any of which may strip or rewrite the caller ID.
Some of these methods break local law, and regulators actively hunt for them. When a regulator shuts a SIM-box farm down, every call relying on it fails overnight.
Not all non-CLI is illegal
Some cheaper routes simply don't guarantee caller ID end to end, without doing anything wrong. But you can't tell the difference from a rate deck — which is exactly why non-CLI routes are unpredictable.
What actually changes for your calls
Answer rates
People increasingly ignore calls from numbers they don't recognise — and "unknown" or a random local mobile number is exactly that. On the same destination, it's common to see CLI routes answer noticeably more often than non-CLI routes. For outbound sales or appointment reminders, that difference alone usually outweighs the per-minute saving.
Callbacks
If your caller ID doesn't arrive, the callee can't call you back. Missed calls become lost leads, and customers who try to ring back may reach a stranger whose SIM was used to terminate your call.
Trust and spam labelling
In markets with call authentication or spam-labelling apps, calls from rotating or mismatched numbers are more likely to be flagged as "Spam Likely" or blocked by the network. In the US, unsigned or poorly attested calls are especially exposed — see our STIR/SHAKEN guide.
Audio quality and post-dial delay
SIM-box routes add an extra hop through a mobile radio link and often transcode audio twice. Expect more post-dial delay, more one-way audio, and calls that drop when the box rotates SIMs.
Compliance exposure
Many regulators require a valid, dialable caller ID on every call. In the UK, Ofcom requires that the CLI presented is valid and is a number the caller has permission to use (UK CLI rules). Sending regulated business traffic over routes that rewrite caller ID can put you in breach — and "the carrier did it" isn't a strong defence.
Side-by-side comparison
| CLI route | Non-CLI route | |
|---|---|---|
| Caller ID delivered | Yes, as sent | Not guaranteed |
| Price | Higher | Lower |
| Answer rate | Higher | Lower and variable |
| Callbacks work | Yes | Often not |
| Typical ACD | Longer, stable | Shorter, swings day to day |
| Regulatory risk | Low | Medium to high |
| Stability | Stable | Can disappear without warning |
| Good for | Business, call centres, reminders, support | Some low-value retail calling where price matters most |
Which traffic belongs where
A simple rule: if the callee needs to know who's calling, or needs to call back, use CLI.
Use CLI routes for:
- Business phone systems and office PBXs
- Outbound sales and customer contact centres
- Appointment reminders, delivery calls and verification calls
- Anything regulated — finance, healthcare, debt collection
- US and Canadian traffic, where unsigned calls are increasingly blocked
Non-CLI can make sense for:
- Retail calling-card or app-to-phone traffic, where users understand the number won't show
- Price-sensitive personal calling to friends and family, where callers will answer anyway
Even here, the trade-off is cost against reliability. Many retail operators run a CLI route as the primary for their most valuable destinations and use non-CLI only as overflow.
How to tell what you're actually getting
Routes are often mislabelled — sometimes deliberately. Before you trust a "CLI" route, test it:
- Make test calls to real phones in the destination country, on more than one mobile network. Check the number displayed.
- Call from a number you can be called back on, and ring it back from the destination.
- Watch the ACD. A sudden fall in average call length on a CLI route is a classic sign that traffic has been moved onto a SIM box.
- Compare pricing. If a "CLI" rate is far below everyone else's, ask how.
- Ask for written terms that state CLI is delivered, and what happens if it isn't.
Our ASR and ACD guide explains how to read the numbers from your CDRs.
How SIPTrunkHub handles CLI
Our CLI routes are sold as exactly that: we deliver your caller ID as sent, on direct or carefully chosen interconnects, and we monitor every route for CLI loss. If we find a vendor rewriting numbers, the route is pulled.
We also check what you send. You must present a valid number you're allowed to use — usually a DID you've bought from us or a number you can prove you own. Spoofed, invalid or rotating numbers are rejected under our acceptable use policy. That protects your traffic as much as ours: networks are far more likely to pass calls from a carrier with clean CLI.
Summary
CLI and non-CLI routes reach the same countries, but they aren't the same product. CLI costs more because it delivers what business calling needs: a recognisable number, callbacks, stable quality and lower compliance risk. Non-CLI is cheaper because it cuts corners somewhere between you and the callee — and you don't get to choose which corner.
For most businesses the right answer is CLI by default. If you'd like to compare both on your own traffic, ask for test credit and we'll set it up.