A small MVNO or IoT connectivity provider often already pays for SMS. Cloud OTA from a SIM bureau adds a second meter and a second place that holds OTA keys. On-site OTA next to your SMSC is the other shape: RFM and RAM over SMS, keys on site, no recurring platform fee on traffic you already own. The deployed baseline is headless SCP80 — SCP81, a GUI and extra bearers are project work. This is not SGP.32 profile provisioning. If you are mid-campaign, paste a packet into the decoder below (no keys) and read SPI, TAR and counter before you book the call.
Guide
On-site OTA when you cannot put keys in a cloud
Small MVNO and IoT connectivity operators that already own SMSC traffic: on-site RFM/RAM over SMS, no platform fee on that traffic, OPC/Ki stay on site. Not an eSIM RSP.
Parsers
Read the packet. Then talk.
Do not paste production keys. If the campaign is still stuck after the decode, that is the programme.
TS 102 225 / TS 31.115
Packet decoder
SPI, key versions, TAR, counter, CHL — command or PoR.
Paste a packet, or load one of the examples above.
Questions
- Is this a cheap Thales replacement?
- No. It is on-site OTA for mixed UICC cards you already operate. Big platforms win eSIM RSP and managed-service RFPs. This fits when keys must stay on site and the work is a scoped programme.
- Do I buy the server or the programme?
- The commercial lead is the programme — migration, rescue, validation. MoreOTA is what we install when you need a campaign engine on site.
Related
Mid-campaign?
A live campaign
Rescue, retry policy and mixed-vendor forensics — or a CSV in MoreOTA if you already run the server.