A roaming SIM, often sold as a multi-network, multi-operator, or IoT SIM, allows a router to connect to more than one mobile network. What it does not do is continuously hunt for the best possible network in the background. In Teltonika routers, the cellular modem is designed to prioritise connection stability first. Once it has attached to a network that meets minimum requirements, it will usually stay there unless something forces it to reconsider.
This behaviour regularly surprises users who have been told that roaming SIMs “automatically switch to the strongest or fastest network”. In reality, whether a roaming SIM changes networks depends far more on modem behaviour and router configuration than on the SIM itself.
This article explains why roaming SIMs often appear stuck on poor networks, why rebooting usually doesn’t help, and how Teltonika routers are designed to handle network reselection properly in real-world IoT deployments.
Roaming SIM, multi-network SIM, IoT SIM: different names, same expectation
In practice, roaming SIM, multi-network SIM, multi-operator SIM, and IoT SIM are often used interchangeably. They all describe SIM cards that are authorised to register on more than one mobile network rather than being locked to a single operator.
Throughout this article, the term roaming SIM is used as shorthand for this entire category. The principles discussed apply equally to multi-network and IoT SIMs used in industrial routers, especially where long-term reliability matters more than peak speed.
What most people are told about roaming SIMs
The usual sales message is simple:
“It automatically switches to the best available network.”
That statement creates a very specific mental model. Most people imagine the SIM or router constantly comparing signal strength, congestion, and performance, then dynamically hopping between networks to stay on the best one.
That is not how cellular modems are designed to behave.
What roaming SIMs actually do in practice
A roaming SIM gives the modem permission to attach to multiple networks. It does not tell the modem to keep optimising indefinitely.
At installation time, the modem scans for available networks, evaluates them against basic criteria, and registers on one that is acceptable. Once registered, the modem’s priority changes. Instead of optimisation, it focuses on stability.
If the network remains technically available, the modem will usually stay attached to it, even if performance degrades over time. From the modem’s point of view, “available” does not mean “good”. It simply means “not rejected”.
What PLMN selection really means in plain English
PLMN stands for Public Land Mobile Network. It is simply the mobile network the SIM is currently registered on.
In the UK, that might be EE, Vodafone, O2, or Three. A roaming or multi-network SIM is authorised to register on more than one of these.
Once the modem registers on a PLMN, it stores that decision internally. Unless something forces a reselection, the modem will repeatedly try to reconnect to the same PLMN because that is the most stable and standards-compliant behaviour.
Why roaming and IoT SIMs get stuck on poor networks
This behaviour is deliberate, not a fault.
Modern LTE and 5G modems are designed to avoid unnecessary reselection because:
- Frequent switching increases signalling load
- Mobile networks enforce back-off timers on repeated registration attempts
- Stability is prioritised over chasing marginal improvements
As a result, once a roaming SIM attaches to a network, the modem will typically:
- Reconnect to the same network after a reboot
- Reconnect after a power cycle
- Remain attached even if latency rises or throughput drops
This is why engineers so often report that a roaming SIM appears “stuck”. The modem is doing exactly what it was designed to do.
SIM-level steering: a hidden influence
Some roaming and IoT SIMs apply operator steering at the SIM or core-network level. Commercial agreements can cause the SIM to prefer certain networks regardless of signal quality.
This steering happens before the router gets involved. Even a perfectly configured router cannot always override SIM-level preferences. It also explains why two different roaming SIMs can behave very differently in the same router at the same site.
Rebooting the router vs resetting the modem
One of the most common misunderstandings in cellular deployments is assuming that rebooting the router resets everything.
It does not.
What a normal reboot actually does
Whether you short-press the reset button (1–4 seconds) or click Reboot in the WebUI, the outcome is broadly the same:
- RutOS restarts
- Network services restart
- The mobile interface goes down and back up
- The modem’s internal network state is preserved
That last point is critical. The modem remembers the last PLMN and will usually attempt to reattach to it immediately if it is still reachable.
This is why power cycling, scheduled reboots, and watchdog reboots so often fail to resolve roaming issues.
Why factory reset appears to work (and why it’s the wrong tool)
A full factory reset often does cause PLMN reselection, because modem state is cleared and cached preferences are lost. The device behaves like a first boot.
The downside is obvious. All configuration is wiped: VPNs, firewall rules, routing, Wi-Fi, credentials. In professional deployments, factory reset should be a last resort, not a routine fix.
Ping Reboot and Auto Reboot: what they really solve
Teltonika routers include Auto Reboot features such as Ping Reboot or Wget Reboot. These monitor connectivity and reboot the router if checks fail.
They are useful for recovering from dead connections, but they do not solve poor network selection. If the current network is slow but still responding, ping reboot will never trigger.
At best, it may coincidentally help if the current network becomes completely unavailable during the reboot window. That is accidental, not intelligent network switching.
How Teltonika handles network reselection properly
Rather than exposing unsafe low-level controls, Teltonika implements controlled mechanisms designed specifically for cellular behaviour.
The most important of these is Low Signal Reconnect.
Low Signal Reconnect: the practical way to force switching
Low Signal Reconnect continuously monitors radio conditions. When signal quality drops below a defined threshold for a defined period, the router:
- Forces the modem to drop its connection
- Tears down the active data session
- Triggers a fresh network registration
- Allows PLMN reselection to occur
In practice, this behaves like a safe, conditional PLMN reset without touching the router’s configuration.
This feature exists precisely because reboots are not sufficient.
For most roaming SIM deployments, Low Signal Reconnect should be enabled. Typical starting thresholds are around −100 to −110 dBm RSSI, adjusted based on the environment.
Manual network scan: a useful middle ground
While there is no dedicated “PLMN reset” button, Teltonika routers provide a manual network scan.
By scanning available networks and reselecting automatic mode, the modem is forced to detach and perform a fresh registration. This is effectively what many people mean when they ask for a PLMN reset.
Manual scans are invaluable during commissioning and troubleshooting, but they are not suitable for unattended deployments because they require human intervention.
Operator whitelists and blacklists
For sites where network behaviour is predictable, Teltonika routers allow operator whitelists and blacklists.
This lets you prevent the modem from attaching to known-poor networks or restrict it to networks that consistently perform well. Used carefully, this can reduce the need for reactive switching altogether.
Misuse can also leave a site offline, so these controls should only be applied once you understand which networks are actually available.
Managing roaming behaviour at scale with RMS
For multi-site deployments, Teltonika’s Remote Management System (RMS) becomes essential.
RMS allows you to:
- See which network each router is connected to
- Monitor signal strength and cellular metrics
- Adjust Low Signal Reconnect thresholds remotely
- Apply configuration changes across fleets
- Reboot routers or modems when required
While RMS cannot magically override modem behaviour, it gives you visibility and control that make roaming SIM deployments manageable at scale.
Using the CLI: what’s possible and what’s risky
Teltonika routers include a CLI accessible via SSH or the WebUI. Through this interface, advanced users can interact with the modem using tools like gsmctl.
Modem reboot via CLI
Rebooting the modem directly (as opposed to the router) is more aggressive than a normal reboot and can sometimes trigger PLMN reselection. It is still not guaranteed, but it is more effective than power cycling.
AT commands and PLMN reselection
It is also possible to issue AT commands to the modem. Toggling modem functionality using commands such as AT+CFUN=0 followed by AT+CFUN=1 forces a full radio reinitialisation and often triggers fresh network selection.
This is powerful but risky:
- Behaviour varies by modem vendor and firmware
- Commands may be ignored while data sessions are active
- Incorrect use can leave the modem offline
- This is intentionally not exposed in the WebUI
CLI-based methods are best reserved for diagnostics and controlled testing, not routine operation.
When roaming SIMs add value – and when they don’t
A roaming SIM is not a magic solution. It provides options, not optimisation.
Roaming SIMs add value when:
- Coverage varies between networks
- Resilience against outages matters
- Deployments span multiple regions
- Commissioning flexibility is important
They add little value when:
- All networks are equally poor
- Router configuration never triggers reselection
- SIM-level steering overrides modem choice
The benefit only materialises when the router is configured to take advantage of the flexibility the SIM provides.
Troubleshooting checklist: roaming SIM not switching networks
If a roaming SIM appears stuck:
- Check signal levels on all available networks
- Perform a manual network scan to confirm alternatives exist
- Verify Low Signal Reconnect is enabled and sensibly configured
- Check for operator whitelist or blacklist conflicts
- Consider SIM-level steering with your provider
- Use modem reboot or CLI tools cautiously if needed
In most cases, the issue is configuration, not the SIM.
Final takeaway
Roaming, multi-network, and IoT SIMs do not continuously optimise for the best network. They enable access to multiple networks, but the modem prioritises stability unless told otherwise.
Rebooting a Teltonika router rarely changes that behaviour. Proper network reselection requires modem-level triggers, which is why features like Low Signal Reconnect exist and why advanced CLI methods are kept out of normal workflows.
If a roaming SIM is clinging to a poor network, the solution is almost always correct router configuration, not a different SIM and not a site visit.
A router that is “connected” is not necessarily connected well. Understanding that distinction is what separates professional IoT deployments from consumer-grade thinking.