1. UE SIM/eSIM authentication failure during field deployment
Local carriers might reject attach requests from IoT devices in the field if their SIM/eSIM profiles are not configured as expected by the local carrier. This might happen when the Key or the IMEI is misconfigured or when the SIM and the network don’t support the same authentication algorithm. In these cases, the IoT devices would not be able to send or receive data even if they can detect the signal from nearby towers.
Roaming networks may issue different reject types (02 roaming not allowed) 03 Permanently forbidden PicoLTE allows testing of all these to ensure robust handling by the modem/application.
The PicoLTE supports Milenage, XOR, and TUAK authentication algorithms with physical testing SIM cards or pre-loaded eSIM with testing profiles.
If the authentication process on the IoT devices is correctly configured, the attach request will be accepted by PicoLTE, and end-to-end connections will be established. The attach request message from the UE and its reception by the PicoLTE will be displayed on the PicoLTE GUI, in the log, or through the API. Otherwise, the attach request message from the UE and its rejection message by the PicoLTE, as well as the reason for rejection, will be displayed on the PicoLTE GUI, in the log, or through the API, so you can trace the cause of the problem.