VoxComms Blog

CLI vs NCLI routes explained for wholesale VoIP buyers

What CLI and NCLI really mean, where CC and A-Z routes fit, and how to make sure a CLI route actually delivers the caller ID you pay for.

By VoxComms · · 4 min read

If you buy wholesale voice termination, you will quickly meet two labels on rate decks and route offers: CLI and NCLI. They often have different prices and different quality expectations, and choosing the wrong one for your traffic can lead to unhappy customers or unnecessary cost. This guide explains what the terms mean, where each type fits, and how to check that you are getting what you pay for.

What does CLI mean?

CLI stands for Calling Line Identification — the caller’s number (also called the A-number or ANI) that is shown to the person receiving the call. In a VoIP call it is carried in the SIP signalling, typically in the From header and, depending on the network, in headers such as P-Asserted-Identity.

Whether that number actually reaches the destination handset depends on every carrier along the path. Each hop can pass the number on unchanged, modify it, replace it, or drop it.

CLI routes

A CLI route is a route on which the vendor commits to delivering the original caller ID to the destination, unchanged. When the call arrives, the called party sees the number that was sent.

CLI routes usually travel over more direct, regulated paths to the destination network, which is one reason they are often priced higher.

When CLI matters

NCLI routes

An NCLI route (non-CLI) makes no promise about caller ID. The number may arrive correctly on some calls, but it can also be replaced with a different number, shown as unknown or private, or not delivered at all.

NCLI routes are generally offered at lower prices and can make sense for traffic where the caller’s number is not important to the recipient. The trade-off is less predictability: answer rates can be lower when people do not recognise the number, and callbacks are not possible if the number is not shown.

CLI vs NCLI at a glance

AspectCLI routeNCLI route
Caller ID deliveryOriginal number deliveredNot guaranteed; may be changed or hidden
Typical price levelHigherLower
CallbacksPossibleNot reliable
Good fit forRetail, business and conversational callsTraffic where caller ID is not essential
What to monitorThat CLI really arrives unchangedOverall quality, ASR and ACD

Where do CC and A-Z routes fit?

You will also see CC (call-centre) routes, which are intended for high-volume, short-duration traffic profiles, and A-Z termination, which offers broad destination coverage under a single interconnect. These labels describe the traffic profile or coverage rather than caller ID handling, so always confirm with the vendor whether a given CC or A-Z route is CLI or NCLI for each destination.

Risks to watch on “CLI” routes

The most common issue buyers report is a route sold as CLI that does not consistently deliver the original number. This can happen when traffic is quietly re-routed through a cheaper path. Signs include:

It is also important to keep compliance in mind. Many countries and operators have rules about how caller ID may be presented and which numbers may be used. Make sure the numbers you send are ones you are entitled to use and that your traffic follows the rules of the destination.

How to test CLI delivery

  1. Call a handset you control in the destination country through the route, and compare the number displayed with the number you sent.
  2. Repeat over time. A single successful test does not prove consistency; test at different times of day and after vendor changes.
  3. Check signalling. Compare the caller ID headers you sent with what your vendor and the far end return, using SIP traces where available.
  4. Monitor automatically. CLI/ANI change detection on live traffic catches problems between manual tests.
  5. Keep records. Note the date, route and result of each test so you can raise specific, evidence-based tickets.

Choosing between CLI and NCLI

Start from your traffic, not from the price. Ask:

Many carriers buy both: CLI routes for traffic where identity matters, and NCLI routes where it does not. The key is to label routes clearly in your switch, test them before sending volume, and keep monitoring after go-live.

How VoxComms can help

VoxComms provides wholesale voice termination including CLI, CC and A-Z routes over SIP interconnects. For carriers running VOS3000, VoxInspector adds CLI/ANI change detection, SIP ladder traces and live quality monitoring, so you can confirm that each route delivers what it promises.

Questions about routes for a specific destination? Contact our sales team.

Monitor your routes with VoxInspector

Live ASR, ACD, PDD and MOS, automatic FAS detection and route testing for VOS3000 carriers.

Discover VoxInspector