SIM steps
Every action available in SIM tests, organized like the action palette, with the metrics each one produces.
SIM tests run on real SIM cards in your cellular agents. Each action drives the modem (USSD, SMS, calls) or the data connection (ping, downloads, speedtest) and produces network metrics that feed Analytics. The groups below match the action palette in the product.
USSD
| Action | What it measures |
|---|---|
| USSD Command | Send a code, verify the response, session state, response time |
| Wait USSD Push | Network-initiated USSD: content and reception delay |
SMS
| Action | What it measures |
|---|---|
| Wait SMS | Incoming SMS: sender, content, parts, reception delay |
| Send SMS | Send time, parts, retries, optional delivery report |
DATA
| Action | What it measures |
|---|---|
| PDP Activation | Data session activation time, assigned IP configuration |
| Ping | ICMP round-trip time, jitter, packet loss |
| TCP Ping | Connection latency at the TCP layer |
| HTTP Ping | Response latency of a web endpoint |
| DNS Lookup | Resolution time and resolved addresses |
| Download File | Download throughput with the full timing waterfall |
| HTTP Upload | Uplink throughput over HTTP |
| FTP Download | Download throughput over FTP |
| FTP Upload | Uplink throughput over FTP |
| Send Mail | SMTP delivery from the mobile network |
| API Call | Full HTTP request: status, body, timing waterfall |
| Ookla Speedtest | Download, upload, latency, jitter, packet loss |
| Traceroute | Per-hop response times and loss |
| Check SSL/TLS Certificate | Certificate validity and time before expiry |
| Youtube | Video streaming quality: buffering, dropped frames |
| Web Script | A scripted web journey over the cellular connection |
CALL
| Action | What it measures |
|---|---|
| Wait Call | Incoming call: answer delay, duration, audio MOS |
| Place Call | Connect time, post-dial delay, call hold |
Other
| Action | What it measures |
|---|---|
| Reboot sim | Modem restart and network re-registration time |
Common options
Every SIM action shares the same envelope:
- Owner (
owner): which SIM runs the action. Owners are assigned per test and can be overridden per campaign. - Assertions (
assertions): compare any field of the action's report against an expected value (status, response time, packet loss, status code...). A failing assertion fails the action. Some actions ship with a default, likepacket_loss == 0on Ping. - Stored variables (
store): copy a report field (duration, extracted text, RTT...) into a test variable for later actions, with an optional default when the source is absent. - Should fail (
expect_failure): invert the verdict, to verify that something is blocked (a barred number, a filtered domain). - Skip (
skip): keep the action in the scenario without running it. - Artifacts (
command.options.artifacts): capture network traces, TCP dumps, AT command logs, or call audio with the result.
Connection settings
DATA actions also share the connection setup:
- Access technology (
command.access_technology): force 2G/3G/4G or specific profiles; empty means automatic. - APN (
command.default_apn,command.apn,command.login,command.password): use the SIM's default APN or custom credentials. - Keep pdp context (
command.keep_alive): leave the data session open for the next actions instead of tearing it down. - Check internet connection (
command.check_network.active): verify connectivity before measuring.
From results to analytics
Every action records a typed report: its status, duration, and the measurements specific to the action (RTT, throughput, MOS, expiry time...). The KPI processor turns each report into a measurement tagged with the test, the SIM, the antenna (MCC, MNC, LAC, cell ID), and the access technology, which is what you chart and alert on in Analytics. Each action page lists its exact fields.
What's next?
Last updated on