Know exactly what Caller ID your customers see.

CLI testing is available on both prepaid and postpaid plans, charged per test. You can start with your existing TelQ account — no separate subscription needed.

SMS testing verifies message delivery, content, and Sender ID. CLI testing verifies voice call routing — specifically what Caller ID appears on the receiving end and whether the call was genuinely connected. Both use real local test numbers; the verification methodology differs by channel.

TelQ supports CLI testing via REST API or SIP trunk. With REST API, you retrieve test numbers and results programmatically. With SIP trunk testing, calls route through your own SIP infrastructure — TelQ records the SIP result codes from your supplier and compares them against what our handset actually received. Check with our team for SIP CLI availability.

TTL (time-to-live) defines how long TelQ's test number waits to receive your call. If the call doesn't arrive within this window, the test is marked as expired. You set the TTL when initiating the test — longer TTLs are useful for routes with higher expected delay.

Test whenever you change your call setup or switch providers. For high-volume campaigns, routine testing is recommended — especially when expanding to new markets.

Yes. TelQ's REST API supports CLI testing — you can retrieve test numbers, initiate tests, and fetch results programmatically. See the API documentation for full details and examples.

TelQ flags potential FAS when your provider reports a call as answered but TelQ's test handset never received it. This discrepancy suggests you may be billed for a call that didn't connect. It doesn't confirm fraud on its own — but it gives you the data to investigate with your provider.

A positive result shows the Caller ID received on our test handset — compare it against what you sent. If they match, the route is clean. If the CLI was modified, the intermediary altered it in transit. An expired result means the call didn't arrive within the TTL window. A potential FAS result means the provider reported the call as answered but our handset didn't receive it. The delay value shows the time from test creation to call receipt — useful for benchmarking route performance.

TelQ can confirm whether your Caller ID is being modified in transit — a common cause of spam flags. If the CLI you send is changed to an unknown number by the time it reaches the recipient, that's a routing problem TelQ will surface.

CLIR is a network feature that allows callers to hide their Caller ID from the recipient. When CLIR is active, the receiving handset shows 'Private Number' or 'Unknown' instead of the actual number. TelQ's CLI testing can detect whether CLIR is being applied to your calls unexpectedly — which could indicate a routing issue.

CLI testing uses your own phone numbers and systems to place calls to TelQ's test numbers — numbers we own and operate. No third-party subscribers are involved. The testing process is fully compliant with telecommunications regulations, as you are simply verifying how your own Caller ID is transmitted through your chosen route.