We covered gateway troubleshooting in an earlier field note, and SIM or APN misconfiguration showed up as one of the most common root causes. It deserves its own post, because most of these problems are entirely avoidable by making the right choice before a gateway ever ships to the field, not by debugging it afterward.
Consumer SIM vs. IoT/M2M SIM
A standard consumer prepaid SIM will often work for a field gateway, at least initially, but it's usually the wrong long-term choice. Consumer SIMs are managed through consumer account systems: bundle expiry policies, occasional forced re-registration, and account-level restrictions aren't designed with an unattended device in mind. A gateway sitting in a cage-side enclosure can't respond to an SMS prompting it to confirm it's still active, the way a phone-holding human would.
A dedicated IoT or M2M (machine-to-machine) SIM plan, where available from your carrier, is built for exactly this use case: predictable data bundles designed for continuous low-to-moderate usage rather than burst consumption, account management that doesn't assume a human is checking a phone app, and often better support for static or predictable IP addressing if your architecture needs it.
For a single pilot device, a consumer SIM is a reasonable way to get started quickly. For anything you intend to leave running unattended for months, budget for a proper IoT SIM plan from the outset.
Physical form factor and vibration
A field gateway experiences more vibration and thermal cycling than most consumer devices, particularly if it's mounted on something that moves at all (a boat, a cage structure exposed to wave action) or exposed to daily heating and cooling. A standard SIM card in a friction-fit tray can work itself loose over time in a way it never would sitting in a phone in someone's pocket.
Where the modem and budget allow it, a soldered MFF2 (embedded SIM form factor) or a SIM held with additional physical retention removes this failure mode entirely. Where a standard SIM is what you have, at minimum confirm the tray has a positive latch and consider a small dab of appropriate adhesive or foam packing to prevent it working loose, checked at each maintenance visit.
Getting the APN right, and confirming it in the field
The Access Point Name (APN) tells the modem how to establish a data connection through your specific carrier. An incorrect or default APN is one of the single most common reasons a device with apparently good signal still shows zero data connectivity: it can register on the network but never actually get an IP address for data traffic.
Three things matter here: use the correct APN string for your specific carrier and plan type (a consumer APN and an IoT-plan APN from the same carrier are often different), never assume a default or auto-detected APN will work correctly for an IoT SIM, and test the actual data connection, not just network registration, before considering a deployment ready. A modem showing full signal bars and network registration can still fail to pass any data if the APN is wrong.
Signal strength is a siting problem, not just a SIM problem
Even with a correctly provisioned SIM, no gateway that lands in a location with genuinely marginal cellular signal will perform reliably. Before finalising a gateway's physical location, we recommend a simple signal survey: check RSSI (received signal strength) at the actual intended mounting height and orientation, not just at ground level nearby, and if signal is marginal, evaluate whether a slightly different mounting point, or an external antenna with better gain, resolves it before committing to that as the permanent site.
A short pre-deployment checklist
Before any gateway leaves the workshop for a field site, we confirm: the SIM type matches the intended deployment duration and unattended-operation requirements, the correct APN is configured and a real data connection (not just registration) is verified, the SIM is physically secured against vibration for the mounting environment, and signal strength has been checked at the actual intended mounting location.
Getting these right before deployment turns what would otherwise be a return trip to a remote site into a five-minute bench check.
If you're specifying connectivity for a new field deployment in Western Kenya and want a second opinion on SIM, carrier, or APN choices before committing hardware to a site, reach out. You can also see how we take hardware from prototype to the field.
