Unetwork CLI and SMS Testing: How Verification Tasks Earn You Rewards

Unity CLI and SMS Testing: Turning Your Phone Into a Telecom Verification Tool

Your Unity license does more than sit in the background collecting passive rewards. Two of the most active earning tasks available right now are CLI testing and SMS testing. These verification tasks turn your smartphone into a frontline quality assurance tool for the global telecom industry, and they pay you for the work your device performs.

CLI stands for Caller Line Identification. In telecom, it refers to the caller ID information that travels with every phone call. When your phone runs a Unity CLI test, it receives a real test call from the network, records the caller ID data that arrives with it, and reports that information back. SMS testing works the same way but with text messages. Both tasks help carriers and enterprises verify that their networks are delivering calls and messages accurately.

This guide covers how both tasks work, what they earn, the new Sender ID and Content Testing task that recently launched alongside them, and how to make sure your device is set up to participate.

What Is Unity CLI Testing?

CLI testing is route verification through real phone calls. The Unity network needs to confirm that telephone numbers across different carriers and regions are reachable, that calls connect properly, and that the caller ID information arrives intact at the other end. Your device helps answer those questions.

When a CLI task is assigned to your phone, the network initiates a test call to your device. This is not a simulated or synthetic call. It is a live call that routes through real carrier infrastructure, the same paths that regular phone calls travel every day. Your device picks up the call (this happens automatically through the Unity app), records the caller ID metadata that arrived with it, and sends a verification report back to the network.

What CLI Testing Actually Measures

Each CLI test captures several pieces of information that are valuable to telecom companies:

• Caller ID accuracy: Did the correct number appear on the receiving end? Spoofed or altered caller IDs indicate fraud or routing errors.
• Call completion: Did the call actually connect, or did it drop, ring without answer, or fail to route?
• Audio quality: Was there latency, jitter, or distortion on the line? These metrics reveal infrastructure problems.
• Routing path: How did the call travel from origin to destination? Misrouted calls waste money and degrade service quality.
• Connection timing: How long did it take to establish the call? Excessive setup time signals network congestion or misconfigured routes.

All of this data gets cryptographically hashed and recorded on chain through WMChain. Every verification task your device completes creates an immutable record that can be independently audited. This is what makes Unity’s verification data trustworthy to the enterprise customers who pay for it.

Why CLI Testing Matters to Carriers

Telecom fraud costs the industry billions of dollars every year. One of the most common fraud types is caller ID spoofing, where bad actors alter the originating number on outbound calls to impersonate legitimate businesses or individuals. CLI testing catches this by comparing what the caller ID should be against what actually shows up on the receiving device.

Beyond fraud detection, CLI testing helps carriers identify revenue leakage. When calls route through unauthorized third party paths instead of the carrier’s own infrastructure, the carrier loses the revenue from those calls. CLI tests map exactly how calls travel from point A to point B, exposing unauthorized routing that would otherwise go undetected.

International carriers find this data especially valuable. A call from the United States to Southeast Asia might pass through five or six different carrier networks before reaching its destination. At each handoff point, there is a chance for quality degradation, routing errors, or revenue loss. Unity’s distributed testing network, powered by real devices in real locations, catches problems that centralized monitoring probes would miss.

What Is Unity SMS Testing?

SMS testing follows the same principle as CLI testing, but for text messages instead of voice calls. The Unity network sends a test SMS to your device, your phone receives it, and the app reports back metadata about the delivery.

What SMS Testing Measures

When your device receives a test SMS, the Unity app captures:

• Delivery confirmation: Did the message actually arrive? Some messages get silently dropped by intermediary networks.
• Sender ID accuracy: Does the sender identification match what was originally sent? Altered sender IDs are a common vector for phishing and spam.
• Delivery timing: How long did the message take to arrive? Delays can indicate network congestion or routing inefficiencies.
• Content integrity: Did the message content arrive intact, or was it modified in transit? Some networks strip or alter message content.

SMS testing is critically important because the global SMS ecosystem is even more fragmented than the voice network. A single text message might pass through multiple aggregators, gateways, and carrier networks before reaching the recipient. Each intermediary introduces the possibility of delays, content modification, or outright message loss.

The Business SMS Problem

Enterprise SMS is a massive industry. Banks send verification codes. Airlines send boarding passes. Healthcare providers send appointment reminders. Every one of these messages needs to arrive reliably, with the correct sender ID, and without content modification.

When an authentication code from your bank arrives 30 seconds late, you might just wait. When it arrives 5 minutes late, you request a new one. When it never arrives at all, you call customer support. Multiply that frustration across millions of customers and you begin to see why enterprises will pay for reliable SMS delivery verification.

Unity’s SMS testing helps these businesses and thei

r carrier partners identify which routes are reliable and which ones are dropping or delaying messages. The data feeds directly into routing optimization decisions that affect how billions of text messages travel across the global network every day.

Sender ID and Content Testing: The Newest Task

Unity recently launched a third verification task that sits alongside CLI and SMS testing: Sender ID and Content Testing. This task specifically focuses on verifying that the sender identification and message content delivered to your device match what was originally transmitted.

Think of it as a specialized quality check. While standard SMS testing covers broad delivery metrics, Sender ID and Content Testing zooms in on two specific problems that cost enterprises the most money:

1. Sender ID manipulation: Did an intermediary network change the sender name or number? This breaks brand recognition and can trigger spam filters.
2. Content alteration: Did the message text arrive exactly as sent? Some networks inject advertising, shorten URLs, or modify character encoding in ways that break the original message.

To enable this task, restart your Unity app and look for it in the task list. It earns rewards just like CLI and SMS testing, and it runs automatically once enabled.

How Much Do Verification Tasks Earn?

Verification tasks are among the highest earning activities available to Unity license operators. Here is how the earnings break down:

Task Type	Earnings Per Task	Status
CLI Testing (Calls)	0.2 to 2 UPS	Live
SMS Testing	0.2 to 2 UPS	Live
Sender ID and Content	0.2 to 2 UPS	Live (New)
Background Connection	0.20 to 0.40 UPS/day	Live

One UPS equals one US dollar. That means a single CLI or SMS verification task can earn you anywhere from $0.20 to $2.00. The exact amount depends on several factors including the type of verification performed, the route being tested, network demand at the time, and your device’s performance grade.

What Affects Your Task Earnings

Not every device earns the same amount. Several factors influence how many tasks your phone receives and how much each task pays:

• Uptime: Devices that stay online 24/7 receive more task assignments than those that disconnect frequently. Unity requires a minimum of 50% uptime to maintain good standing.
• Connection type: Devices on mobile data sometimes generate more rewards than devices on WiFi alone, because mobile connections enable certain verification checks that WiFi cannot.
• Location: Your geographic location affects which routes can be tested through your device. Some regions have higher demand for verification data.
• Network diversity: If you run multiple licenses, spreading them across different internet connections produces better results than clustering them all on one network.
• Device grade: Unity assigns performance grades to devices based on their reliability, connection quality, and task completion history. Higher graded devices get priority for higher value tasks.

Monthly Earnings Projection

With all currently available tasks running (Connection, CLI, SMS, and Sender ID), operators can expect to earn in the range of $4 to $10 per license per month under current network conditions. As more enterprise customers come online and task volume increases, Unity’s published projection is up to $48 per license per month at the ULO’s 50/50 share, based on nearly a year of network pilots.

That $48 figure represents the underlying gross estimate of approximately $96 per license per month in network service fees, with the operator receiving their share based on the lease agreement split. The exact percentage depends on your license terms, but most operators start at a 60% share that can increase to 70% through referral tiers.

How Verification Data Gets Secured

Every CLI test, SMS test, and Sender ID verification your device completes follows the same security pipeline:

1. Task assignment: The network assigns a verification task to your device based on what routes need testing and your device’s capabilities.
2. Execution: Your device performs the test (receives a call, receives an SMS, or checks sender ID data).
3. Metadata capture: The Unity app records all relevant metadata from the task without storing any personal content.
4. Cryptographic hashing: The metadata is secured with a cryptographic hash that makes it tamper proof.
5. On chain recording: The hash is sent to WMChain, creating a permanent, auditable record of the verification.
6. Validation: Validation Nodes confirm the integrity of the result before rewards are distributed.

This pipeline is what makes Unity’s data commercially viable. Enterprise customers trust the verification results because every test is independently verifiable on chain. No one can fabricate or alter results after the fact. Switch Nodes manage the initiation and routing of test calls across the global telecom grid, while Validation Nodes confirm the integrity and connectivity of the edge mobile devices performing the tests.

Requirements for CLI and SMS Testing

The requirements for running verification tasks are straightforward. If you already have a Unity license and a compatible device, you likely meet all of them.

Device Requirements

• Operating system: Android 6 or newer, iOS 15 or newer
• Memory: 3 GB RAM or more recommended for smooth background operation
• Storage: Minimal. The Unity app is lightweight and verification data is transmitted in real time.

Connectivity Requirements

• Internet: Stable WiFi or mobile data connection
• SIM card: A SIM or eSIM is required for CLI and SMS testing, since these tasks involve receiving real phone calls and text messages. WiFi only devices can still run the background Connection task and some other verifications.
• Phone number verification: You must verify your phone number through SMS before CLI and SMS tasks become available.
• Data usage: Approximately 7 GB per month for all network testing combined. WiFi preferred for the data heavy portions.

What to Avoid

• VPNs: Do not run the Unity app behind a VPN. It interferes with accurate network testing.
• Emulators: Virtual devices and emulators are not allowed. Unity verifies that tasks run on real hardware.
• Clustered IPs: Running too many devices on the same /24 IP range will trigger flags. Spread devices across different connections.
• Battery and data savers: Disable these for the Unity app. They can prevent the app from receiving task assignments in the background.

How to Enable Verification Tasks

Setting up CLI and SMS testing takes just a few minutes if you already have an active Unity license.

1. Update the app: Make sure you are running the latest version of the Unity Network app from the App Store or Google Play.
2. Verify your phone number: Open the app and complete the phone number verification process. This requires receiving an SMS code, which confirms your device can receive messages.
3. Enable tasks: Navigate to the task settings inside the app. Toggle on CLI Testing, SMS Testing, and Sender ID and Content Testing.
4. Keep the app running: The app needs to stay active in the background. Make sure battery optimization is disabled for Unity.
5. Monitor your dashboard: Check your earnings periodically to confirm tasks are being assigned and completed successfully.

Tasks are assigned automatically once enabled. You do not need to manually trigger them. The network determines which tasks to send based on what routes need testing and your device’s eligibility.

For a detailed walkthrough with screenshots, read our step by step activation guide.

The Six Categories of Network Verification

CLI and SMS testing fit within Unity’s broader verification framework. The network performs six categories of verification work, and your device may participate in any or all of them depending on your task settings and connectivity:

Category	What It Detects
Call Quality	Latency, jitter, audio distortion, and degraded voice connections
Fraud Prevention	Suspicious signaling patterns, unauthorized network access, caller ID spoofing
Routing Accuracy	Misrouted calls, dropped connections, incomplete call setups
Connection Reliability	Repeated failures, sudden disconnects, unstable infrastructure
Spam and Abuse Detection	High volume automated calling, robocall patterns, messaging abuse
Latency and Performance	Delay measurements, jitter analysis, performance bottlenecks

CLI testing contributes directly to the Call Quality, Fraud Prevention, and Routing Accuracy categories. SMS testing contributes to Fraud Prevention, Spam and Abuse Detection, and Connection Reliability. Together, they cover a significant portion of the verification work that makes Unity’s data valuable to enterprise customers.

To see all available Unity tasks and how they fit together, read our complete guide to Unity network tasks.

Privacy and Data Collection

A common concern with verification tasks is what data your device actually shares. Unity is explicit about this: the app collects only anonymized task metadata. Here is exactly what is and is not collected:

What Unity Collects

• Signal strength and connection quality metrics
• Call and message delivery timing data
• Caller ID and sender ID information from test traffic (not personal calls or messages)
• Anonymized device type and OS version for accuracy and deduplication
• Coarse region level location data (not precise GPS coordinates)
• Network identifiers and timestamps

What Unity Does Not Collect

• Your personal phone calls, messages, or contacts
• Your name, address, or any personally identifiable information
• Files, photos, apps, or any content stored on your device
• Precise GPS location or movement tracking
• Browsing history or app usage data

Unity is GDPR compliant and does not require KYC (Know Your Customer) verification. You can verify this yourself using network monitoring tools like Wireshark to inspect the data your device transmits while running the app. Multiple community members have done this and confirmed that the app transmits only what Unity claims.

Frequently Asked Questions

Sources

• Unity Network Official Site
• Unity License Operator Guide (Unity Nodes Club)
• Unity Network on X (@UnityNodesIO)
• HexyNodes Unity License Directory
• Complete Guide to Unity Network Tasks