Network Diagnostics
A device in the field goes quiet. Usually that means a support ticket, a wait, and a technician's visit to discover it was a network setting. Here the answer is visible: every network in every country connects into one core, so every attach attempt is in your portal's network log, and every signalling exchange and packet can be captured live.
Every attach, every rejection, every silent session
Each attempt a device makes is logged with the network, the radio technology and the outcome, so a rejection or an empty session is visible the moment it happens.
| Time (UTC) | Network log message | ||
|---|---|---|---|
| 2026-10-02 07:14:02 | 4G | Attached 4G connection on network: MCC 234 MNC 15 (Vodafone UK) | |
| 2026-10-02 07:14:03 | 4G | Allowed to use data on network: MCC 234 MNC 15 | |
| 2026-10-02 07:42:51 | 4G | Detached data connection from network: MCC 234 MNC 150B | |
| 2026-10-02 07:43:10 | 4G | Attach rejected: MCC 234 MNC 20 (Three UK) is not on this SIM's network list | |
| 2026-10-02 07:43:18 | LTE-M | Attached LTE-M connection on network: MCC 234 MNC 30 (EE) | |
Four views into the network, nothing installed on the device
Network logs are in your portal for every SIM. Traffic capture, signalling logs and cell location are run for you by our team when you raise a problem.
Network logs
Every attach attempt: which network and technology the device used, and the exact reason for any rejection, such as a network that is not on its list.
Traffic monitor
Every packet to and from a device, captured live in the core network anywhere in the world, and sent to you as a PCAP file for offline analysis.
Signalling logs
The protocol exchanges between the local radio network and the core (GSM MAP, Diameter, GTP), to see exactly why a connection behaves as it does.
Cell-tower location
Which cell a device is attached to, to confirm where it is and to troubleshoot coverage at a particular site.
Debugging with and without core-network visibility
| Situation | Without it | With VoicePro IoT |
|---|---|---|
| A device stops reporting | Raise a ticket and wait for the operator | Read the network log: attach, rejection or empty session |
| You need to see the traffic | Add logging to the firmware and redeploy | Packets captured in the network and sent to you as PCAP |
| Is it the device or the network? | Guesswork until someone visits | Signalling logs show the exchange with the local network |
| Battery draining too fast | Lab tests on a sample device | Real reconnect and traffic patterns from the field |
From silent device to root cause
Spot it
An alert or a zero-byte session shows a device has stopped sending data.
Trace it
The network log shows it tried a network that is not on its list and was rejected. The signalling log confirms why.
Fix it
We add the network to the list. The device reconnects on its next attempt, with no site visit.
More of VoicePro IoT
IoT SIMs
Card, embedded chip or software SIM, commercial or industrial grade, with the full technical specification.
IoT eSIM & SGP.32
Choose the operator after the device ships, and change it over the air for the life of the device.
Fleet management
Your SIMs, their status and network logs in the VoicePro portal, with data limits, alerts, an API and webhooks.
Security & private networking
IMEI lock, device isolation, IPsec and OpenVPN. Keep devices off the public internet.
Coverage explorer
Every network in 203 countries, with 2G, 3G, LTE, LTE-M and NB-IoT status by operator.
Industries
Asset tracking, logistics, telematics, metering, EV charging, payments and more, each in depth.
Bring us your hardest device
Tell us which devices are hardest to keep online, and we will show you what the network logs and traffic monitor reveal about them.