SM-SR console: tasks with tested values

The hands-on companion to the SM-SR console guide. Results were produced on 4 October 2026 by a principal holding smsr: maintain and smdp: maintain, starting from no cards.

More than the guide’s “state only” view

The console now offers New lab M2M card, Deliver pending scripts, profile Enable, Disable and Delete, and administration session triggers. Each change still goes through SGP.02 — the console queues it and the card receives it as a script.

Before you start

Address	smsr.rsplab.click/console
Role needed	smsr: read to look at eUICCs, profiles, scripts and sessions; smsr: maintain for every action below. You only see your own eUICCs. smsr: admin adds other people’s eUICCs and the right to reassign one

1. Create a lab M2M card

Choose New lab M2M card.

Expected result. A new EID with one profile, already claimed by you. In this run:

Field	Value
EID	89049032202600000200000000058866
Profile	ICCID 89882920000000005886, ISD-P A0000005591010FFFFFFFF8900001100, ENABLED, Fall-Back
ISD-R AID	A0000005591010FFFFFFFF8900000100
Bearers	HTTPS yes, CAT_TP no
SCP81 key	version 64, identifier 1

2. Download a second profile

Order it in the SM-DP console for this EID. The SM-SR then holds two Pending OTA scripts for the card.

Choose Deliver pending scripts.

Expected result. Each script answers POR_OK — the card accepted the script. After delivery the profile list shows the new ICCID 89882930000000000158 as DISABLED, and all six scripts of the download as Delivered.

3. Switch profiles

1. On 89882930000000000158, choose Enable and confirm Enable this Profile?.

   Answer: accepted, call id …:enable, operation enable.

2. Deliver pending scripts — one script, POR_OK.

Expected result. 89882930000000000158 is ENABLED and the first profile is DISABLED. The profile’s lifecycle shows one change: enable, origin ES4, state DELIVERED.

4. Follow an administration session

1. Under Administration sessions, choose Ask the card to check in and confirm. Answer: a job id.
2. Deliver pending scripts — the trigger answers POR_OK.

Expected result. A new session in CLOSED state. Opening a session shows its events in order — for example:

#	Phase	Summary
0	BEARER	connection opened to smsr.rsplab.click:443
1–3	BIP_RECEIVE	141, 152 and 235 octets from the card (the TLS handshake)
4	HTTP_POST	POST, 0 byte body
5	SCRIPT	200, next script
7	HTTP_POST	POST, 8 byte body, status=ok
8	HTTP_204	204, final

5. Claiming

Claim an eUICC by EID takes an EID that is one of your simulated cards. Claiming the shared demo card 89049032202600000200000000043928, which is not yours, answers not found.

Not yet verified

Capability	Why
Delete a profile, Abandon change	Not run in this pass
A script that fails	No failing case was produced