Open-source SIM tooling
Published at github.com/morestk.
SIM · OTA · eSIM
Change SIMs that are already in people's hands.
Network migrations, custom applets, key systems, and an OTA server that runs on your own hardware. Twenty years of SIM engineering, across operators, IoT providers and security teams.
Start here
What's the situation?
We're moving subscribers to a different network.
An acquisition, a new host operator, a new PLMN. IMSI, MSISDN, PLMN lists and applet parameters change on cards that are already issued. No recall, no reshipping, no visit to a store. Planned in waves, with retries keyed to the actual error code.
Open →Our OTA campaign is failing and nobody knows why.
Cards go silent. Proof of Receipt comes back with the same codes again and again. Counters drift out of sync and half the update is applied. Get the packets read, the cause named, and a retry plan that does not make it worse.
Open →We want to run OTA ourselves.
MoreOTA is an OTA server that runs on your own servers. RFM and RAM over SCP80, mixed card vendors and key sets in one campaign, retry from a CSV. Your Ki, OPC and OTA keys never leave your site. Licensed as software, not billed per SMS on traffic you already own.
Open →We need something on the card that doesn't exist yet.
Multi-IMSI switching, IMEI lock, polling, network fingerprinting, SIMbox detection. Java Card and STK applets written, loaded over the air, and tested against real cards from real vendors.
Open →We need SIM expertise, not a product.
Key generation and key ceremony: how to produce Ki, OPC and OTA keysets, hand them to a SIM vendor, store them, and keep an inventory without losing control of them. SIM file structure and electrical profile design. Choosing between SGP.02, SGP.22 and SGP.32 for an eSIM programme. SIM security research.
Open →Tools
Free tools. Nothing leaves your browser.
Paste a packet, get the SPI, TAR, counter and command back. Paste a status code, get the cause and whether retrying will help. Everything runs locally. Never paste production keys into any website, including this one. All tools · Guides
TS 102 225
Packet decoder
SPI, TAR, counter, CHL.
Paste a packet, or load one of the examples above.
Table 5
PoR status
Cause, action, retry or not.
Hex, with or without 0x
Audience
Who gets in touch
- MVNOs that changed, lost or bought a host network
- Small and mid-size MNOs with no in-house OTA team, or paying their SIM vendor for every campaign
- IoT and M2M connectivity providers with devices already deployed
- Integrators and solution providers whose customer asked for something SIM-shaped and who have no SIM engineer
- Security teams and research labs that need a real SIM and OTA environment to work against
- SIM vendors, bureaus and test labs
Why this way
What you get that a platform vendor won't give you
- You talk to the engineer who writes the code. No account manager in between.
- The server runs on your hardware. Ki, OPC and OTA keys stay with you.
- Vendor-neutral. Cards from different SIM makers, different generations and different key sets in the same campaign.
- Scoped as a project or licensed as software. Not a per-SIM or per-SMS tariff on traffic you already own.
- Small enough to start in weeks instead of quarters.
Background
Where this comes from
OTA servers and applets in production
Multiple OTA servers built and deployed. Java Card and STK applets shipped across operators and card vendors.
SIM security research
Technical lead on SIM and OTA security work: replay, counters, SCP behaviour in the field.
National SIM migration
OTA side of a national migration of about 2 million live SIMs, including the on-card applet, at over 98% success. A separate migration of about 300,000 subscribers for another operator.
Experience
Our clients
- Golan Telecom
- Cellcom
- Unibeam
- Monogoto
- Webbing
- Verint Systems
- Elbit Systems
- Jacada
Also
eSIM model selection
SGP.02, SGP.22 or SGP.32. Advice and architecture, not profile provisioning.
Open →PoR guides
One page per OTA failure code. Cause, action, when not to retry.
Open →Notes
How SIMs behave in the field. Some pages are interactive.
Open →Free parsers
Packet decoder, PoR lookup, Terminal Profile.
Open →FAQ
Questions
- What is MoreOTA?
- An on-premise OTA server for SIMs already in the field: RFM and RAM over SMS with SCP80. Mixed card vendors in one campaign. Ki, OPC and OTA keys stay on the operator site. Around it: subscriber migration, campaign troubleshooting, custom applets, key work and eSIM advice. Licensed as software, not billed per SMS on traffic you already own.
- Who is MoreOTA for?
- MNOs, MVNOs, IoT and M2M connectivity providers, integrators and solution providers without a SIM engineer, security teams, and SIM vendors, bureaus and test labs. Especially where cards from different makers, generations and key sets share one campaign.
- What success rate can a campaign reach?
- With retry keyed to error codes, campaigns routinely reach over 98% of available subscribers: cards registered on the network in the window, not absent. Absent or unreachable cards need their own window. The national migration case study used the same denominator.
- Do the website tools upload my packets or keys?
- No. The packet decoder, PoR lookup and Terminal Profile analyser run in your browser. Nothing is uploaded. Do not paste production keys. MoreOTA itself is on-premise, so operator keys never come to this website. See the privacy notice.
- Where do I start if a campaign is failing?
- Look up the PoR codes in the free tool. Treat clusters (01, 02, 06, silence) as inventory, SPI or segmentation work, not a blind resend. MoreOTA can ship CSV retry keyed to those codes. See the OTA server page.
Contact
Tell me what you need to change.
Thirty minutes, engineer to engineer. Useful things to include: roughly how many SIMs, which SIM vendors, what has to change on the card, and by when.
Email direct: contact@moreota.com
Include the network and SIMs, the SIM vendors, and what the campaign needs to do. A technical call is 30 minutes, engineering to engineering.
Enquiries are handled as in the privacy notice. Do not paste production keys.