Good question. It depends on where the check sits and how the roaming traffic is routed. Most roaming IoT SIMs use home routing: the data session goes back to the issuer's packet gateway (PGW or GGSN). The device's IMEISV is normally carried in the session setup (the MEI field of the GTP Create Session Request), so a lock enforced at that gateway behaves the same at home and abroad. The visited network only passes the request through. It changes in two cases: Local breakout. The session ends on a gateway in the visited network, so the home check never sees the data session. The lock may then only apply at registration, if at all. Missing IMEI. The MEI field is conditional, so a visited core can omit it. A lock that blocks when the IMEI is absent will cut off good devices in that country. One that allows it will not catch a swap there. What we would do in practice is test it rather than treat roaming as a general exception. In each target country, put a bound SIM into a different device and confirm the session is refused, then check that the platform logs the IMEI it saw. Where the IMEI comes through, keep the lock. Where it does not, turn the missing IMEI into an alert rather than a block, and rely on usage and location monitoring there. One unrelated thing that looks the same in the field: national IMEI registries (Turkey, Indonesia) can block an unregistered device with no SIM lock involved.
