@Roalnd-Baldin The 2 hours is probably related to the 3GPP TAU timer, if it expires the device is implicitly released from the network I believe. Which is bad if you have a device that wants to sleep for more than 2 hours. So usually you set this value to whatever is the greatest the network accepts. You can run AT+CEREG=5, AT+CEREG? and check the returned values. It will tell you the timers that are used.

@Ronan-Lacroix I have a question: The min value for T3412 is only valid for the “extended” version of TAU ? Does the 1 hour apply also to the min. value of standard TAU or is it shorter? Having a min TAU of 1 hour seems to me for many use cases difficult because the devices in those use cases need to wakeup from sleeping much more often (e.g. every 10 minutes). Many many thanks for your support! Regards, Roland I

@afzal_m Proprietary sucks I hope more open protocols are added, UDP is pretty limiting

Cool, still happy to receive your logs (as Eric requested)

@Roalnd-Baldin Cool! Nice to see it works now.

@IoT-Arista Interesting combination. You are right, nRF9160 requires a very different development strategy. It uses Zephyr RTOS and c-api’s to control the cellular modem. In my opinion it is much better to work with than the ancient, slow, outdated AT interface. But if you want to use AT commands on nRF9160 you still can: https://github.com/nrfconnect/sdk-nrf/tree/master/applications/serial_lte_modem If you don’t want to redesign you should contact SIMCOM and t-mobile ( @Eric-Barten ) to fix your issue

@Noah-Marx said in Max message length: https://forum.iot.t-mobile.nl/topic/504/maximum-number-of-messages-per-day/6 Thnx Noah, but no. My experience is that messages can not exceed 512 bytes from CDP to device and 1024 bytes from device to CDP. I would like this constrained by relieved, at least to one UDP frame of 1460 bytes, but even larger if possible. In the message you refer to I read that larger messages should be split up, but since with a CDP communication is message based and not frame based, you have to sort and glue those messages to one yourself on both sides. That is a waste since TCP/IP was designed to do this for us! So next best to an ordinary TCP/IP connection directly to the backend server (or any other IP address) would be a larger message IMHO.

Hi Tibor, Did you succeed to connect? I want to use the Boron to.

Ah that’s a shame Good luck with finding solution.

@Dylan-Frings said in Connection to Azure IoT Hub: Hi, I’m trying to connect an Arduino MKRNB1500 to MS Azure IoT Hub but I constantly get the error -2 (Connection refused) on both port 443 and 8883. If I try to run the exact same script with a different SIM and carrier everything works perfectly. My company uses T-Mobile SIMs and with those SIMs I can’t establish a connection to the IoT Hub. Is T-Mobile blocking any ports on the mobile network in the NL or is there another fix for this problem? Thanks a lot! You can’t access any server on the internet directly, this is why it’s not working. The CDP is always in between and acts as a proxy. You can register a URL as an endpoint and the CDP will forward any trafic it receives from your device to your registered endpoint

@stefan-de-lange thank you for pointing me in this direction. I will read up and try to make it work using this manual.

Problem solved. It denpends on the sim card

Hi Thomas, sorry for late response. Please check our latest version of the Solution Guidelines, we have extended it with the information you inquired about. BR, Aleksandra

Hi, what kind of SIM are you using? I’m asking because our m2m/IoT SIMs usually come with PIN disabled. For this reason, PIN handling is not included in our HW-library. Unfortunately, the module you are using does not support any management of facility locks, other than entering the PIN when the radio is turned. To proceed you should deactivate the PIN on the SIM on a different device. You can either try a smartphone or a different module which supports the management of facility locks. The required AT-commands for this are: AT+CLCK=“SC”,2 # Query status of SIM lock +CLCK: 0 # SIM is unlocked (1 would be locked) AT+CLCK=“SC”,0,“1234” # Remove SIM lock (for PIN 1234) Best regards