LTE rejection

RE: LTE rejection

Nicholas Henson — Tue, 30 Sep 2025 14:38:56 GMT

@ Slope 2 It could be a network registration or configuration issue rather than the SIM itself. I think sometimes forcing a manual network search also helps in diagnosing LTE rejection errors.

RE: LTE rejection

Øyvind — Mon, 29 Sep 2025 11:12:53 GMT

Hello again, our product management team have been in contact with both Conexa and Onomondo, and at this stage there is unfortunately not much we can do. The best solution is for you to reach out to both directly as the issue seems to be on SIM side.

Kind regards,
Øyvind

RE: LTE rejection

spruce — Mon, 29 Sep 2025 09:17:36 GMT

Hi I do have an old T-Mobile NL sim card that appeared to connect to the 1nce network after T-Mobile became Odido here in The Netherlands. That sim is working fine to be able to continue our development work.

Let me know if I can provide more information or test more with the Conexa and Onomondo Sims

RE: LTE rejection

Øyvind — Mon, 29 Sep 2025 08:07:14 GMT

Hello, we're really sorry for the inconvenience. There have been several reports of similar issues with both provided SIMs and we are working hard to find the culprit.
Do you have any other IoT SIMs that you can test with while we find a solution?

Kind regards,
Øyvind

RE: LTE rejection

spruce — Tue, 23 Sep 2025 09:03:14 GMT

And on the Conexa sim

RE: LTE rejection

spruce — Mon, 22 Sep 2025 21:54:37 GMT

All PLMNs are forbitten?

RE: LTE rejection

spruce — Mon, 22 Sep 2025 09:29:53 GMT

Yes, I tried many things.
Resetting, clean builds, cleaning entire SIP

RE: LTE rejection

Øyvind — Mon, 22 Sep 2025 09:09:22 GMT

Hello again! Here is the response I got from Onomondo

I have reviewed SIM ID 002598284. Please see my findings below.

This SIM has no network logs.

This SIM is activated.

The signaling logs show an authentication loop.

Signaling authentication loops like this indicate that either:

The device is in a bad state and should be reset.

The local network is rejecting the device (e.g. for load balancing, or due to a lack of available cells) and the problem might resolve itself with time.

I assume that you have tried resetting the device?

Kind regards,
Øyvind

RE: LTE rejection

Øyvind — Wed, 17 Sep 2025 07:15:18 GMT

Thanks for providing this information. I'm currently out traveling but have forwarded this information today.

RE: LTE rejection

spruce — Sat, 13 Sep 2025 09:05:19 GMT

On the Onomondo SIM it is 002598284

RE: LTE rejection

Øyvind — Fri, 12 Sep 2025 11:21:55 GMT

Hello, we are in contact with both Onomondo and Conexa regarding this issue. Onomondo has requested the ICCID or SIM ID for their SIM card. Could you please provide this information for both SIMs?

Kind regards,
Øyvind

RE: LTE rejection

Øyvind — Thu, 11 Sep 2025 13:35:49 GMT

Hello, sorry, I've been out of office. Looking into this now. I hope to have an answer for you within 3-4 business days.

Kind regards,
Øyvind

RE: LTE rejection

spruce — Thu, 11 Sep 2025 11:00:22 GMT

Any updates on this one?

RE: LTE rejection

spruce — Tue, 09 Sep 2025 18:51:45 GMT

Hi Øyvind,

I'm relatively sure it has nothing to do with the application, but to have a good reference, I programmed the multi-service quickstart into the SIP with modem 2.0.2

I have 3 modem traces made with the same application. (see attachments)

Both Onomodo and Conexa failed to connect.
But I had an old T-Mobile IoT SIM that I would not expect to work at all after it became Odido, but surprisingly that one works and connects to iot.1nce.net.

Also the CoAP message arrive at nrfcloud with this T-Mobile SIM.

devzone.nordicsemi.com/.../onomondo.mtrace

devzone.nordicsemi.com/.../conexa.mtrace

devzone.nordicsemi.com/.../old-T_2D00_mobile-SIM.mtrace

RE: LTE rejection

Øyvind — Tue, 09 Sep 2025 07:36:50 GMT

Hello,

Are you able to provide a modem trace from your device using both the Conex SIM and Onomondo SIM? Make sure to reset board after starting modem trace in the Cellular Monitor app and leave it running for minimum 20 minutes.

[quote user=""]I was busy extending the asset tracker project and all of a sudden I got this lte rejection.[/quote]

Could you elaborate more on what you were adding/changing in the Asset Tracker template? Just to confirm, are you building with the NCS 3.1.0 branch? What modem FW is your device running?

From the provided logs the device is rejected on both LTE-M and NB-IoT.

Cause #42 – Severe network failure

This EMM cause is sent to the UE when the network has determined that the requested procedure cannot be completed successfully due to network failure. The failure is not expected to be temporary and repeated request is not likely to succeed in near future.

Cause #17 – Network failure

This EMM cause is sent to the UE if the MME cannot service an UE generated request because of PLMN failures.

Cause #13 – Roaming not allowed in this tracking area

This EMM cause is sent to an UE which requests service, or if the network initiates a detach request, in a tracking area of a PLMN which by subscription offers roaming to that UE but not in that tracking area.

Cause #15 – No suitable cells in tracking area

This EMM cause is sent to the UE if it requests service, or if the network initiates a detach request, in a tracking area where the UE, by subscription, is not allowed to operate, but when it should find another allowed tracking area or location area in the same PLMN or an equivalent PLMN.

NOTE 3: Cause #15 and cause #12 differ in the fact that cause #12 does not trigger the UE to search for another allowed tracking area on the same PLMN.

Let's start with modem traces using both SIMs to evaluate what is going on.

Kind regards,
Øyvind