Active SIM or eSIM
Required. Your phone must have a working number that can receive normal incoming calls.
Live Unetwork task
Earn rewards by verifying call delivery across live carrier networks using your device.
CLI operator guide
Current section: Overview
What ULOs do
CLI means Caller Line Identification. In this task, Unetwork sends or assigns a real inbound test call to a ULO phone.
The task checks whether the call reached your device and whether the caller ID details can be reported in the app. That helps Unetwork understand how live carriers perform across real countries, networks, and devices.
Caller ID quality can change by:
Reports from ULO devices show what actually happens on live networks, not just in lab tests.
Operator requirements
The test call is delivered through your mobile carrier. If your SIM cannot receive normal incoming calls, the task cannot be verified.
Required. Your phone must have a working number that can receive normal incoming calls.
Your line must be reachable on the mobile network. Wi-Fi alone cannot receive a test call.
Allow notifications and background activity so you see task alerts and can report quickly.
If the phone is off, the SIM is disabled, or the network is unavailable, the call may not be received.
Wi-Fi helps keep the app connected, but the call itself comes through your mobile number. SIM or eSIM service is required.
Caller ID CLI Testing supports both iOS and Android. On iPhone, PoW may show offline because of iOS background limits, but CLI tasks can still be available.
Reporting workflow
CLI tasks include a reporting window so ULOs can submit the requested details after a call is received or missed. Use the task window shown in the Unetwork app.
It looks like a normal incoming call. The task checks whether the call reaches your device.
Letting the phone ring or missing the call can still be valid. Follow the report flow in the app.
If you miss the call, open the Unetwork app and submit the report within the reporting window.
Enter the call details exactly as shown. If something looks wrong, report that instead of guessing.
Task availability
This is normal. Calls are assigned based on customer requests, countries, mobile carriers, and active testing campaigns.
These settings or line issues can stop your phone or app from seeing the event:
Good setup
Frequently asked questions
No. The task checks whether a real call reaches your device. Answering is not required.
Yes. Caller ID CLI Testing supports iOS and Android. On iPhone, PoW may look offline because of background limits, but CLI tasks can still work.
No. Wi-Fi can keep the app synced, but the call arrives over your mobile network. You need an active SIM or eSIM.
Yes. You can use your everyday phone if it has an active SIM or eSIM and can receive incoming calls.
Task volume varies by country, carrier, customer demand, and active campaigns. It is normal for ULOs to see different volumes.
No. Missed calls may still be reportable. Open the app and submit within the 24-hour window shown for the task.
More details
The CLI Deep Dive slides explain the same operator basics: use a real device, keep an active SIM, you do not need to answer, report within the window, and expect task volume to vary by location and carrier.
Slide 1 of 3
A quick overview of Caller Line Identification and why real devices matter.
Slide 2 of 3
The active SIM, device readiness, and task distribution basics for ULOs.
Slide 3 of 3
Simple setup tips and answers about missed calls, iOS support, and rewards.
Ready to participate
Caller ID CLI Testing helps verify call delivery on real carrier networks while giving ULOs another way to earn rewards.