Hi! It does not matter which sim you use in your project. Even when you used the simcard in another project before.
Your old simcard is still active 
CEREG 5 means that you are connected (too be more precite, it means ‘roaming’).
What protocol did you select to register your IMEI in your project? Was it UDP or CoAP?
Hi Paul,
I just wrote you back via DM. This is a DB issue and not the usual issue that device has been locked because of sending a message before being registered.
We’re working on it! Hopefully we will have a fix today
As usual with these corporate press releases, this is just an annoucement indeed…
The availibility of NB-IoT roaming on Deutsche Telekom IoT simcards depends on a few things:
But the simcards that we provide at iot.t-mobile (soon to be iotcreators.com) already have the right profile to roam in 18 countries! We’re currently testing it and we can use some help here.
For now these countries are confirmed:
Netherlands, Germany, Austria, Poland, Denmark
Currently we are testing in these countries:
United Kingdom, Switzerland, Czech Republic, Spain, Sweden
Looking for testers in:
Norway, Finland, Italy, Slovakia, Croatia, Liechtenstein, Greece, Hungary
Maybe an issue in our back-end. Can you pls add and remove a dummy IMEI in your project?
https://dyrk.org/tools/imei/
This will maybe solve the problem (for now).
Not yet, in our internal organization we do not have experience with it yet. That will change soon!
I will ask if someone of Sodaq nows the commands for this module.
@trick2011
Thanks for this question, I will try to find this information for you today.
Good question! I just changed a setting which allows you to delete a post in the first 180 seconds after creating your post. Can you try it?
Yup! We have some people working on that as well! Should be available end of June
Thx Jurriaan. Working on a fix as we speak!
@Martijn-Kooijman I am not sure if it is the same, but this problem occured with the Ublox R410 as well.
With simcard it was not possible to send AT commands, without simcard it was possible.
This problem was solved in a later firmware release…
Ah wait… I now noticed that you already did.
Then I’m also lost. It should work like this. 
Did you try to open the socket first?
You can do that by executing this command
AT+USOCR=17
Hi Marijn,
You will find the instructions for your module in the Getting started section. I think you need the ‘network attach’ page.
W.r.t. the Azure integration, you are right. We will update this a.s.a.p.
Fiddling around? 
Can you send me your simcardnumber in a direct message pls?
Did not find anyone
Do you have another device that you could test?
Ok, thanks for clarifying!
Did you already try to set-up the AT+COPS values in a way that it will automatically select the PLMN ID (20416)?
I think that the Particle Boron only supports LTE-M and not NB-IoT…
I received this question a lot these days. I still need to understand why. Is our document library (getting) too complex maybe? Please let me know
However, if you ordered your NB-IoT simcard at iot.t-mobile.nl, I can assure you that your simcard is already active.
We want to save you from the simcard hassle as much as possible. All our NB-IoT simcards have the same configuration. To make sure that you can simply keep one single stock for all your different use cases/projects,
Just register the IMEI number of your module in one of your projects. Configure your module with the right settings, put your simcard in it and it should work right away.
The simcard is not able to send and receive SMS.
Besides that, the simcard only supports NB-IoT. I am not sure if your device is able to support NB-IoT. I don’t see it coming back in tje screenshots. Can you confirm that it supports NB-IoT?