Counter low
Add 1, try again.
MoreOTA server
An OTA server that runs on your servers.
RFM and RAM over SCP80. Cards from different vendors and different key sets in the same campaign. Retry from a CSV, keyed to the error code each card returned. Your keys never leave the building.
Tools · Tell me what you need to change
- RFM · RAM
- SCP80 · SMS
- On-premise
- Retry from a CSV
Where it sits
As deployed today
Capabilities
Baseline first. Extra features are added per project. See Custom add-ons and What it does not do yet.
| Workflows | RFM (remote file management), RAM (remote applet management) |
|---|---|
| Bearer | SMS. Additional bearers on a project basis. |
| Security | SCP80 secured packets, with operator key handling |
| Card mix | Different SIM makers, generations, profiles and key sets in one campaign |
| Campaign control | Targeting and segmentation, batching, throttling, response handling, per-card status |
| Retry engine | CSV per network or SIM code. Examples: counter low → add 1; PoR 01 → fix inventory; absent subscriber → try in a day. You can add your own rows. |
| Applet interface | Drives custom on-card applets, including migration applets, through application-specific command hooks |
| Deployment | On-premise, next to the operator's SMSC. Ki, OPC and OTA keys never leave the site. |
| Custom add-ons | Per project: SCP81/BIP, an operator GUI, local DB or SMTP integration, custom OTA packet generation, AI-assisted retry. |
Honesty
What it does not do yet
SCP81 / BIP over HTTP and a custom web GUI are available as project work, not as shipped features. The deployed baseline is headless SCP80 over SMS.
Retry
We ship a retry. You can add your own.
The mechanism is a CSV: what to do for each network or SIM code. Use the rows we ship, or add your own retry plan in the same file. Reading the codes takes experience. These are examples, not the whole catalogue.
A card that went quiet after a security error is not a row to hammer. That silence can be correct.
PoR 01 — cipher error
Wrong key. Often the MSISDN and IMSI in inventory no longer match. Update the inventory, try again.
PoR 06 — unidentified security
Sent in the clear. Check key versions, PoR rules, then CHL.
PoR 08 — more time
Not a failure. Do not retry. Wait for the follow-up PoR.
Error **:** — network
Usually absent subscriber. Try in a day. Best: align the send to VLR registration so fewer are absent.
Got an error?
Decode it here.
Paste the PoR or the command. Status, SPI, TAR, counter. Guides if you already know the code.
Paste a packet, or load one of the examples above.
Hex, with or without 0x
Related work
Other situations
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.
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.
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.
FAQ
OTA server questions
- What is an OTA campaign?
- An OTA (over-the-air) campaign sends a set of commands to many SIMs at once to change what is on the card. File changes use RFM (remote file management). Applet install or update uses RAM (remote applet management).
- Is SIM OTA secure over SMS and HTTP?
- Yes, when a Secure Channel Protocol wraps the commands. Over SMS the common protocol is SCP80. Over HTTP it is SCP81. MoreOTA’s deployed baseline today is SCP80 over SMS; SCP81 can be added per project.
- What does the MoreOTA platform include?
- Baseline today: RFM and RAM over SMS with SCP80 secured packets, mixed card vendors, campaign control, retry from a CSV per network or SIM code, and an applet interface. Per project you can add SCP81, an operator GUI, local DB or SMTP integration, custom OTA packet generation, or an AI-assisted retry layer.
- How does MoreOTA retry a failed OTA campaign?
- Orchestration scripts plus a CSV: what to do for each network or SIM code. Use a shipped template, or write your own rows from the error codes. Examples: counter low → add 1 and try again; PoR 01 → often stale MSISDN/IMSI inventory; absent subscriber → try in a day, aligned to network registration when possible.
- Where are OTA keys stored with MoreOTA?
- On the operator site. MoreOTA runs on-premise next to the SMSC (SMS centre). OPC/Ki and OTA keys do not leave the operator.
Contact
Tell me what you need to change.
Remote worldwide. On-site Israel only.
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.