Core console: tasks with tested values
The hands-on companion to the Core console guide. Results were
produced on 4 October 2026 by a principal holding eir, nef and pcf at
maintain, on a line it owned: IMSI 001010000000570, created when it
downloaded a profile in the SM-DP+ console.
Before you start
| Address | core.rsplab.click/console |
| Role needed | maintain on eir, nef or pcf for that tab’s changes |
| Your lines | each tab lists the lines you own; a new download gives you one |
1. Test a phone (Equipment)
Test a phone: IMEI 490154203237518, your line.
Expected result. WHITELISTED, Unknown phone, allowed by policy, mode
observe. The IMEI is shown masked: 49015420•••••1-8.
2. Block it, then enforce
| Do this | Answer |
|---|---|
Blocked, tracked and allowed phones: IMEI 490154203237518, list blocked, reason Docs guide: stolen phone test | added; TAC 49015420 |
| Test a phone again (observe) | WHITELISTED, … (observe mode: allowed, would have refused), would have been BLACKLISTED |
| Mode → enforce | mode enforce, unknown phones allow |
| Test a phone again | BLACKLISTED, refused, Blocked by its IMEI: Docs guide: stolen phone test |
| Mode → observe, then remove the entry | removed: true |
The Check log keeps every answer, each marked manual for a test from the
console.
| If you see | It means |
|---|---|
| list is allowed, tracked or blocked | The list name was not one of the three |
3. Name a line for an application (Exposure)
Your identifier domain is <you>.iot.rsplab.click. Map
meter-1@<you>.iot.rsplab.click to your line.
Expected result. mapped. Remove answers unmapped.
4. Send a trigger
Send a trigger to the mapped identifier, Custom port 9000, text hello,
validity 300 seconds.
Expected result. Created (201), payload aGVsbG8=. In this run the line had
no phone number, so the delivery result was FAILURE. A trigger needs a line
with an MSISDN to reach the phone by SMS.
The Lab sink is per browser and empty until something reports to it.
5. See why a line gets its speed (Policy)
What this line gets now for 001010000000570:
| Before | After Boost this line | |
|---|---|---|
| Speed | 20 Mbps down / 5 Mbps up, 5QI 9 | 50 Mbps down / 10 Mbps up, 5QI 7 |
| Source | plan | boost:166, for 10 minutes |
| Reasons | plan (lab default) | plus boost 166 until … |
Cancelling the boost answers cancelled: true.
QoS profiles lists the lab’s QOS_E, QOS_L, QOS_M and smaller ones.
Rules shows the lab’s lab-blocked (precedence 10, gate closed) and
lab-throttle (precedence 100, 128/64 kbps).
Add my throttle rule with id docs-throttle, precedence 50, 256 kbps:
saved in scope own; removing it answers removed: true.
Not yet verified
| Capability | Why |
|---|---|
| A trigger delivered to a phone | The test line had no number |
| Monitoring subscriptions | Not run in this pass |
| Wi-Fi calling refused for a blocked phone | Needs the device emulator run |
| Everyone | Admin only |