The right SIM card makes a significant difference to reliability, coverage and total cost. Here is what to look for.
Consumer SIMs from high-street networks are designed for phones. They use network steering to direct devices to the same operator regardless of signal quality. Fair-use policies can throttle data. Roaming on consumer SIMs is expensive. Most are tied to a 12 or 24-month contract that assumes the device is a smartphone.
IoT deployments have different requirements. The gateway might run for 5-10 years. Coverage at the site might only be viable on one specific network. Remote management requires a stable public IP address. These requirements need a proper IoT SIM.
A multi-network roaming SIM connects to whichever operator has the strongest signal at any given time. Rather than being locked to a home network, the SIM roams domestically across multiple UK networks – EE, Vodafone, O2 and Three – as an IoT device rather than a roaming handset.
This is the most important feature for TRB gateways deployed in rural areas, remote sites or anywhere with variable coverage. A single-operator SIM that loses signal leaves the device completely offline. A multi-network SIM switches automatically to the next available operator.
Standard mobile data connections use dynamic public IPs that change on reconnection. This makes remote access via VPN or direct connection unreliable without a dynamic DNS service running continuously. A static IP SIM gives the gateway a fixed, routable public IP address that never changes.
Static IP is essential if you are connecting to the TRB gateway from a head-end system, SCADA server or cloud platform using an IP whitelist. It is also useful for remote WebUI access and for configuring RMS with a known endpoint.
The TRB246, TRB247 and TRB256 all support dual SIM. A common and effective configuration is:
RutOS monitors the primary SIM continuously and switches to the secondary on any of the following triggers: weak signal below threshold, data allowance reached, no network available, connection failure. When the primary recovers, it can switch back automatically or stay on the secondary until manually reset.
RutOS supports Auto APN detection for major UK operators. For IoT SIMs, particularly private APNs used on static IP services, you will need to enter the APN manually. The APN, username and password are found in the SIM provider documentation. On TRB devices, the APN is configured under Network – Mobile in the WebUI.
Some private APN services use an additional authentication type – PAP or CHAP. RutOS supports both. If you have connectivity issues with a static IP SIM, verify the authentication type matches what the provider requires.
The TRB501 includes built-in eSIM with bootstrap connectivity in production batch 2 onwards. Bootstrap connectivity means the device can download an eSIM profile even without an active SIM installed – it connects to a bootstrap network, downloads the profile from the SM-DP+ server and becomes operational. This is transformative for large-scale deployments where shipping a SIM separately to each device adds significant logistics overhead.
The TRB247 also offers an optional eSIM configuration for North American deployments.
Routerstore.com stocks IoT SIM cards to complement Teltonika TRB gateway purchases. These are proper IoT SIMs – multi-network where available, with data management and static IP options. Buying SIM and gateway from the same supplier simplifies pre-sales advice and support.