@Lauwie007

There are legal limitations imposed on us what we can commercially offer - but that might change in the future. However, then we also probably need to change the commercial offering of the public APN, because it’s basically raw connectivity what you would source from us.

As said the public APN is for TESTING ONLY. We are not planning on closing it down any time soon, but maybe we might at one point. So we cannot guarantee a continuity of this APN forever. Most likely it would change if we can commercially offer it at one point! Maybe it make sense if we have a quick call about it so I understand your requirements a bit better.

If the demands for ipv6 grows, we will consider implement it

Hey all,
I am trying to connect a Quectel BG96. Every time after configuring

AT+COPS=1,2,"20416",9

It says

CME Error: 13

Also a simple command to retrieve the IMSI AT+CIMI gives an error then.

When I reset the modem and use AT+CIMI again, it works and returns the IMSI. However, after trying to configure the COPS again, the error comes back…

Any ideas?

@Ravindra-Singh428 can you try to send data again please?

Deutsche Telekom will upgrade their NB-IoT platform in order to proactively increase the capacity and make it more scalable and robust for the future. Doing this, we benefit from better feature set (like using NB-IoT and LTE-M traffic through the same VPN tunnel) as well as security hardening.
The migration of our APN “cdp.iot.t-mobile.nl” to the new platform will be performed by the Deutsche Telekom Core Network team automatically. It does not require any activity from your side, so there is no need for new configuration of your IoT solution or anything alike.

Maintenance window:
May 10th, 2022 at 4:00 am CEST
May 17th, 2022 at 4:00 am CEST

Service Interruption:
There will be a service interruption for approx. 45 minutes during the night. The devices will lose the PDP connection and need to create a new IP session at the end of the maintenance window. After the new platform starts operation, the devices will re-login to the network automatically and will get a new IP address.

Experience from other customers:
This maintenance work was already performed for the customers located in Germany. We didn’t receive incident reports related to this change. That’s why we’re optimistic that it will run smoothly for the IoT Creators APN as well.

Please contact me/us in case you’ve got any questions or doubts and concerns.

We apologize for the inconvenience and are optimistic that you’ll benefit in the future from that change.

We have a partnership for NB-IoT with A1 Slovenija in Sovenia, so this was not intentional and will be fixed.
My previous suggestion unfortunately does not work properly, so contacting us directly is the best way to order in this case.
Sorry for the confusion.

@MarcoPeli Thank you, this was the problem. ;)

Hello @Mikael-Guenais,
NB-IoT roaming is available in France via SFR. You can also always find up-to-date information on our roaming partners in our documentation library here.

I will contact you about the SIM card directly from our support email.

Best regards
Oliver

@Mikael-Guenais If you order a free starterkit (incl. 1 SIM) you should be able to do the order process directly in the standard order flow. If you want to buy SIM cards, please reach out to support@iotcreators.com and we will help you out with your order. Sorry for the inconvience.

BR
Florian

Hi Mikael,

you can order a Starterkit with “public internet access” (it’s a bit misleading, but you need to select LTE-M starterkit in the order process). However, this is only available for testing purposes and not for productive systems. So in our paid plans we cannot offer this at the moment.

In our standard setup you would usually trigger the downlink message via API call (or directly in the portal) and thus the device’s IP does not need to be fixed.

BR
Florian

@Jan-Kolorenc-0 hello Jan, i wrote you in private

@Herr-Bruns

Feature deployment is in preparation, please bear with us a little longer… 🙏

Kind regards, Ronan

I second what Uta said for roaming use-cases.

For non-roaming use-cases, I would recommend to always set the band and the PLMN ID to ensure faster attach. So please be more patient with the attach time if you don’t set these values.

Should be fixed now!

Hi Matthew,

for NB-IoT there is a technical limitation of 1024 bytes (but this also includes the protocol information). According to our no harm to network guidelines you shouldn’t use more than 1 MB/device/month for NB-IoT.

Working with different technologies like NB-IoT and LoRa? You can now manage all your LPWA devices from one place with our IoT Creators Portal!
From now on we’re providing you with the access to the LoRaWAN Network Server as part of our tariffs.
Check out our IoT Access packages and follow our guide to integrate your LoRaWAN devices.

Hi,
thanks for your answers, very interesting information.
I’ll try it after that date.

Actually the device with the 1nce sim card goes into PSM sleep and also receives GPS-positions but wakes up all 15-20minutes. Also with longer sleep times.

Kind regards,
Christian

I can confirm the issue. I can reproduce it. The problem occurs not due to LTE-M but due to this specific APN (m2m.public.nl). @Uta will take care of this

@aliza-izaton As mentioned earlier, I strongly recommend using a python-based solution.

@Philipp-Berg-0 All good, I have not been aware that clicking Save already triggers a validation of the URL and an sending an “empty” package to the endpoint.

Hi Rik,

can we have a conf-call about this topic. We are currently making customer interviews to understand your requirements better.

Yes, we can raise priority for this topic :)

I will send you and email to schedule a conf-call.

Regards, Roland