Skip to content

Caller ID Test: How to Check CLI on a VoIP Route

How to run a caller ID test on a VoIP route: test setup, reading the received CLI, the delivery rate to agree and the warning signs of grey routes.

Updated 20 October 2026

To run a caller ID test (a CLI delivery check), call real handsets in the destination with a known caller ID and record which number actually appears, in which format and on how many calls. A CLI route is only as good as the share of calls that arrive with the right number, so measure it as a percentage over several operators and times of day.

Why CLI delivery needs testing

A route sold as CLI can still lose or change the caller ID along the way. Every carrier in the chain can rewrite the From and P-Asserted-Identity headers, and some routes pass through networks that replace the number with a local one or remove it. The result matters: calls without a recognisable number are answered less often, and callbacks fail. The differences between route types are covered in CLI vs non-CLI routes and local CLI routes explained.

How to run the test

  1. Pick a test CLI you own, in full international format (E.164, for example 44 followed by the national number). Never test with a number you are not authorised to use. See E.164 number format.
  2. Get receiving handsets in the destination: colleagues, partners, or a test-call service that has SIMs on the local operators and reports the received caller ID.
  3. Cover each operator the route claims to reach. CLI delivery often differs by operator, especially between mobile and fixed.
  4. Make at least 10 calls per operator, spread over different hours. A single successful call proves very little.
  5. Record for each call: time, dialled number, CLI sent, CLI received, and whether the call connected.

How to read the results

Received on the handsetWhat it means
Your number, correct formatCLI delivered
Your number with a wrong prefix or missing country codeCLI delivered but badly formatted; callbacks may fail
A local number you did not sendCLI replaced; acceptable only if you bought local CLI
"Private", "Unknown" or no numberCLI removed: the route behaves as non-CLI
A different number on each callRandom CLI, often a sign of a grey or SIM based route

Calculate the CLI delivery rate as calls with the correct number divided by connected calls. Agree in advance what rate the route must reach. Some carriers state a guaranteed share; others make no promise, and the route should then be priced as non-CLI.

Warning signs

  • CLI arrives on the first few calls and disappears once volume grows.
  • The received number is a local mobile number that changes between calls. This is typical of SIM box bypass, which is illegal in many countries and can be cut off without notice.
  • The price for "CLI" is below what legitimate operators charge for international termination in that country.
  • The carrier asks you to send a specific number, or a number from the destination country, as your CLI. Presenting numbers you do not have the right to use breaks rules in many markets; see CLI spoofing and robocall rules.

Keep testing after go-live

Carriers change their own suppliers, so CLI delivery can change from one week to the next. Repeat a short test regularly, and every time ASR or callback volume moves without a reason. Add CLI checks to the routine described in how to test a VoIP route.

When you request a route through VoIPMatcher, say which CLI types you can accept and what delivery rate you need, and we source VoIP termination that matches. Request a CLI route.

Frequently asked questions

Why is my caller ID not showing on outbound calls?

Common causes are a route that is really non-CLI, a carrier in the chain that removes or rewrites the From or P-Asserted-Identity header, a number sent in the wrong format, or a destination that blocks international calls showing a local number. Check the number format first, then test the route on several operators.

What is a good CLI delivery rate?

There is no universal figure. Some carriers guarantee a share of calls with the correct number, others promise nothing. Agree the target before testing, measure it as calls with the correct number divided by connected calls, over at least 10 calls per operator, and price a route without a stated guarantee as non-CLI.

Can I test caller ID without people in the destination country?

Yes. Test-call services keep SIM cards on local operators and report the caller ID received on each call, along with connection and audio results. They are the practical option when you have no colleagues or partners in the destination, and they let you repeat the same test regularly after go-live.

What format should a caller ID be sent in?

Send the caller ID in full E.164 international format: the country code followed by the national number, without an international prefix or the national trunk zero. Many networks reject or strip numbers that are incomplete or badly formatted, and callbacks fail when the number arrives without its country code.

Is it legal to display any number as caller ID?

No. In most countries you may present only numbers you own or are authorised to use, and that can be called back. Presenting someone else's number or a random one is spoofing, which regulators such as the FCC and Ofcom restrict, and calls with invalid caller IDs are increasingly blocked.

Need a route?

Send the destination, route type and target rate. We reply with what we can deliver.

More guides

All guides
Quality and testing VoIP One-Way Audio and Dropped Calls: Causes and Fixes VoIP one-way audio and dropped calls: NAT, SDP, SIP ALG, firewalls, codecs, the 32 second drop and session timers, with a fix for each cause. Quality and testing VoIP Jitter, Latency and Packet Loss: Limits Acceptable jitter, latency and packet loss for VoIP calls, how a jitter buffer works, what causes jitter and how to test and reduce it. Quality and testing Post-Dial Delay (PDD): Causes, Standards and Fixes Post-dial delay (PDD) in VoIP: what is normal, what causes long PDD on wholesale routes, how to find it in SIP traces and CDRs, and how to cut it. Quality and testing SIP 487 Request Terminated: What It Means What SIP 487 Request Terminated means, the CANCEL call flow behind it, why dialers and slow routes produce many 487s and how to reduce them. Quality and testing Q.850 Cause Codes: List and Meaning for VoIP The common ITU-T Q.850 cause codes (1, 16, 17, 34, 41 and more) with their meaning, their SIP equivalents and how to use them to troubleshoot routes. Quality and testing False Answer Supervision (FAS) in VoIP: How to Detect It False answer supervision (FAS) in VoIP: how it shows up in ASR, ACD and NER, how to test a route for FAS and what to do when you find it. Quality and testing OTP SMS Not Received: Causes and Fixes for Apps Why users do not receive your OTP SMS or get it late: filtering, sender ID, registration, slow routes, content issues and how to fix them. Quality and testing SIP 408, 480 and 486: Timeouts and Busy Codes What SIP 480 Temporarily Unavailable, 408 Request Timeout and 486 Busy Here mean, their Q.850 causes, and when they point to a route problem.