Live caller ID validation
CLI testing checks whether the caller's number is transmitted and displayed correctly during real inbound calls.
Unetwork task guide
Caller Line Identification
Validate caller ID delivery with real inbound calls on live mobile networks. Report what your phone actually received.
Status Active task
Estimated reward 0.05 to 0.2 UPs/call
Call handling Answering not required
Line requirement SIM or eSIM can receive calls
Why it matters
Caller ID should arrive correctly
Caller Line Identification testing checks whether the caller's number is transmitted and displayed correctly to the receiving device.
Route visibility
Real devices help show how call delivery behaves across countries, carriers, device types, and routing paths.
Better network trust
Accurate caller ID supports call quality, fraud reduction, customer trust, and telecom compliance.
Operator mindset
Report the number exactly as shown
Your job is not to guess what the caller ID should have been. Your job is to report what actually appeared on your device so Unetwork can verify real delivery behavior.
Do not guess
If the number looks unusual, report it exactly as it appeared. Your job is not to decide what it should have been.
No need to answer
CLI calls are focused on delivery verification and reporting. Answering the call is not required.
Missed calls may still count
If you miss the call, check the app. CLI tasks include a reporting window for submitting the observed call event.
Requirements
Keep your line reachable
CLI tasks rely on real telecom infrastructure. The device needs an active mobile line, app access, and enough background availability to receive task prompts.
Active license
Use an active Unetwork license connected to the app.
Task opt-in
Enable Caller ID Testing in the app and follow the on-screen number validation steps.
Active SIM or eSIM
Your line must be able to receive incoming mobile calls. Wi-Fi alone is not enough for CLI tasks.
Background access
Keep notifications enabled and allow the app to operate in the background where possible.
Battery settings
Reduce restrictive battery optimization or power-saving settings when they block background activity.
Updated app
Keep the Unetwork app updated so call notifications and reporting remain reliable.
How it works
A simple call event and report loop
CLI calls look like regular incoming calls. The task is complete when the call event is reported and validated in the app.
-
Receive a notification
When a CLI test is available, the app can send a push notification and in-app prompt.
-
Observe the call event
The call appears like a normal inbound call. You do not need to answer it.
-
Report what appeared
Submit the displayed number exactly as your device showed it within the available reporting window.
-
Validation and rewards
After a valid report is completed, rewards are handled through the Unetwork app.
Estimated CLI range 0.05 to 0.2 UPs per call reported
Rewards
Rewards depend on valid reporting
The current estimate is a reference range, not a guarantee. Actual rewards can vary by test outcome, country, operator, customer demand, and validation.
- Test outcome
- Country and operator
- Customer demand
- Eligible call events
- Valid reporting
Task distribution
Task volume varies by route and demand
Operators should not expect identical CLI task volume across all devices or regions. Call tests are assigned when online numbers match the requested country, carrier, and campaign needs.
- Country and mobile carrier
- Regional testing demand
- Coverage objectives
- Active verification campaigns
- Device readiness and app availability
Common questions
Caller ID task FAQ
What is Caller Line Identification testing?
Caller Line Identification testing verifies whether the caller's number is transmitted and displayed correctly during real inbound calls on live networks.
Do I need to answer CLI calls?
No. The task is about call delivery verification and reporting. If a call arrives, report what appeared on your device.
What if I miss the call?
Missing the call does not automatically mean the task is lost. Check the app because CLI tasks include a reporting window after the call event.
What should I report?
Report the number exactly as it appeared on your device. Do not edit it, normalize it, or guess what it should have been.
Is Wi-Fi enough for CLI testing?
No. Wi-Fi can help keep the app connected, but CLI calls arrive through the mobile line. A SIM or eSIM that can receive calls is required.
Does CLI work on iPhone?
Yes. CLI tasks are supported on iOS even when PoW connectivity indicators appear offline because of background restrictions.
How much can CLI tasks earn?
The current estimate is 0.05 to 0.2 UPs per call reported. Rewards are not guaranteed and can vary by test outcome, country, operator, demand, and validation.