hey, I have a new device (kind of an IOT device) with eSim, it is supposed to be prepaid, but I don’t know how to check the details, and whether it has global data plan already.
I don’t have the number, can have the imsi number

the embedded sim is MFF2-QNF8

how can I proceed?

#eSim #germany

hey, I have a new device (kind of an IOT device) with eSim, it is supposed to be prepaid and activated, but It is not connecting and I don’t know how to check the details, and whether it has global data plan already.
I don’t have a phone number or anything, can have the imsi number.

the embedded sim is from the family MFF2-QNF8

how can I proceed?

Thanks

The problem is, I bought this from a private person used on ebay. I hope they answer next week on my mail.

@inka-O,

As stated above, we will implement eDRX for LTE-M beginning of next year, but we cannot tell you exactly when right now (our current target is Q1 2021). As far as we know, most of the other European LTE-M operators haven’t yet enabled eDRX neither, but also plan to deploy it next year. eDRX does not exist in 2G, only in LTE, and deployed primarily (if not exclusively) in its Low-Power Wide-Area categories (i.e. LTE-M and NB-IoT). PSM is supported in all of DT’s LTE-M networks as well as in all of our roaming partner networks. Like eDRX, PSM has only been standardized in LTE networks and is not available for 2G.

Best regards,

Ronan

Dear all,

from December 6th, 2020 on, our IoT Forum will only be reachable via direct URL forum.iotcreators.com.

The former URL iotbytelekom.com, which was used to redirect you to the forum, will be phased out.
If you have any questions, let us know. Simply start a discussion in the forum or contact hello@iotcreators.com.

Thanks!

Sorry, I missed this post.

Showing the payload in our GUI is not a problem for new devices.

What you need to do is the following:

APN cdp.iot.t-mobile.nl
Send your payload to: 172.27.131.100

Hi Frank,

WUS and other 3GPP Release 15 features aren’t yet supported in the DT networks and to our knoweldge in most other Operator networks.
Our focus is right now on completing the roll-out of key features like eDRX, while in parallel planning the introduction of new Rel. 14 features like New Category NB2.
WUS and other important Rel. 15 features are of course already on our Roadmap, unfortunately we cannot give you a concrete date when those will be deployed in the our networks yet.
Can’t eDRX to a certain extent address your power saving requirements for the time being?

Best regards,

Ronan

@Lauwie007
I have not tested it myself, but I guess your live test has just proven it, hasn’t it? 😊
Keep in mind that this time is provided by the local network in which you are actually roaming, so if you’re roaming in say, the Vodafone UK network, this time and associated timezone will be provided by Vodafone UK (if supported as just discussed).
Kind regards, Ronan

@Holger-Wech you can use LTE-M instead of the 2G/3G fallback that is described in our quick start guide. Please use the APN internet.m2mportal.de for LTE-M.

@lorenz
Dear Lorenz,
Thanks a lot for the feedback and I’m glad to see eDRX is delivering its promise on energy saving!
Another tip maybe: please consider setting your preferred Periodic TAU Timer to save further energy.
This can be done without setting any PSM activity timer with the CPSMS command, with a TAU-timer of up to 310 hours.
To enable Long-Periodic TAU without PSM, use value “11100000” for parameter <Requested_Active-Time>.
Best regards,
Ronan

Hi Eben,

Quick feedback: I can use GNSS and TCP at the same time using the SIM7000E using the latest firmware, which I had to update beforehand.

Best Regards,
Daniel

AT+CGMR Revision:1529B03SIM7000E OK AT+CGNSPWR=1 OK AT+CGNSTST=1,1 OK $GNGGA,,,,,,0,,,,,,,,*78 $GNRMC,,V,,,,,,,,,,N*4D $GPGSV,1,1,03,18,,,32,20,,,33,30,,,38*78 $GNVTG,,T,,M,,N,,K,N*32 $GPGSA,A,1,,,,,,,,,,,,,,,,*32 $GLGSA,A,1,,,,,,,,,,,,,,,*02 $GAGSA,A,1,,,,,,,,,,,,,,,,*23 AT+CGNSTST=1,1 OK $GNGGA,,,,,,0,,,,,,,,*78 $GNRMC,,V,,,,,,,,,,N*4D $GLGSV,1,1,04,69,04,320,31,85,11,011,23,,,,26,86,00,056,*5C $GPGSV,2,1,06,07,23,066,34,15,34,293,22,18,12,305,32,20,01,329,35*76 $GPGSV,2,2,06,28,49,135,28,30,54,067,38*7D $GNVTG,,T,,M,,N,,K,N*32 $GPGSA,A,1,,,,,,,,,,,,,,,,*32 $GLGSA,A,1,,,,,,,,,,,,,,,*02 $GAGSA,A,1,,,,,,,,,,,,,,,,*23 AT+CGNSTST=1,1 OK ... got a fix after that! Establish test TCP server (Simple Perl script) AT+CPIN? +CPIN: READY OK AT+CSQ +CSQ: 9,99 OK AT+CGATT? +CGATT: 1 OK AT+CSTT? +CSTT: "CMNET","","" OK AT+CSTT="iot.1nce.net" OK AT+CIICR OK AT+CIFSR 100.84.13.2 AT+CIPSTART="TCP","10.65.61.189","5000" OK CONNECT OK WILMA-SERVER #1 AT+CGNSTST=1,1 OK ... Got GPS FIX AT+CIPSEND > PING SEND OK 100.84.13.2:PONG TCP connection successful.

May I suggest you also take a look at our central FAQ page for NB-IoT Roaming? 😉

@inge-eriksen
Hi Inge,

all of our SIMs for M2M and IoT are G-SIMs, which means that technically they are always roaming. So a query for the registration state, for instance with AT+CEREG, should always yield: 5.
On our testcards, we have currently no HPLMN deployed. For this reason the modem searches for a suitable network and will consider any NB-IoT network on the supported bands.
To make sure that the modem will only connect to the DT network, you can either fall back to manual network selection (PLMN-Id=26201), or restrict the supported bands to band 8. This will exclude any operators in Germany for which we have not yet roaming agreements.

Best regards,
Thorsten

Hi Aleksandra,
thanks for your offer. But I think at the moment it is not necessary to conduct tests in your lab in Bonn. We have the oppotunity to do some tests with a network simulator in an other Honeywell department (in India). If I will have the need for testing in Bonn before June, I would gladly come back to your offer.

Best regards, Thomas

@apuhl , with a classic M2M GSIM (IMSI starting with 90140), you may use the standard APN “internet.m2mportal.de”, with a Consumer SIM card (starting with 26201), it should be “internet.telekom.de”.

Best,
Ronan

Release announcement: Activation of NB-IoT network features

Dear IoT Community,

please note that we will soon be activating new features, as well as will update the configuration of already available features in the NB-IoT network. With the transition, you’ll be able to manage your NB-IoT devices even more flexibly and efficiently. The activation is currently planned for beginning of November and will affect our networks in Austria, Czech Republic, Germany and the Netherlands.

The changes at a glance:
• Switch to dynamic Power Saving Mode (PSM) - the network will now accept the values suggested by devices
• Switch to dynamic (long-periodic) Tracking Area Update (TAU/LP-TAU) - the network will now accept the values suggested by devices
• Introduction of Data Packet Buffering - the network will buffer up to 10 data packets for the sleeping devices in the PSM

More information can be found in the attached document: Feature Release Communication

If you already use PSM and / or TAU / LP-TAU, then please note that your devices may behave differently than usual after activating the network functions. We recommend checking the settings on your devices.

If you have questions, don’t hesitate to ask in our IoT Forum!

In general, other networks such as LoRa and Sigfox are also still in their build-up. NB-IoT has the advantage of being able to use existing LTE base stations, which will allow for sufficiently dense network with good indoor penetration, especially in urban regions.