Forum wide moderators
Hi,
today we took a nice comort sensor (CO2/Temp/Humidity/BodySense) in Barcelona into operation.
We configured
It worked immediately without any problems.
Regards, Roland
@Wessam Hi, have a look to https://forum.iotcreators.com/topic/626/how-long-does-it-take-that-the-network-detects-a-dead-ip-connection. Maybe it contains some info you are interested in.
Regards, Roland
Hi guys,
I made some test to the automatic release of IP addresses by the network.
With the “Tuino096 - Quectel BG96” I attached to the network with the following AT commands:
AT+CGDCONT=1,“IP”,“cdp.iot.t-mobile.nl”
AT+COPS=1,2,“26201”,9
AT+CGPADDR
+CGPADDR: 1,10.0.4.102
As a Telekom employee I am in the lucky situation that I can check the IP status of the device via some monitoring systems. Of cause I could see that the my device with its IMEI and IMSI got assigned the IP address 10.0.4.102.
After this I just unplucked my device from power and checked the IP connection status of the IMEI.
It took about ca. 2 hours the DCD of the network recognized that the device is dead and release the IP address to be used again by other devices.
I repeated this test a few times and I could reproduce the 2 hours.
BUT if I power up the device after I swiched it off and attach it bag to the network the network detects the same IMEI and IMSI requires a new IP. By this the provious IP is released immediately and a new IP is assigned to the device.
Hope this info helps you a bit to get a better understanding what is going on in the network.
Cheers, Roland
@paulvha This URL and headers work for me:
To get the list of all devices:
URL:
GET https://iot.netwerk.t-mobile.nl:443/rest/device?iDisplayLength=-1
Headers:
Content-Type:application/json
Authorization:Basic base64(<USERNAME>:<PASSWORD>)
Accept:application/json
This should work with your credentials:
curl -X GET https://iot.netwerk.t-mobile.nl:443/rest/device?iDisplayLength=-1 -H 'Authorization:Basic base(<USERNAME>:<PASSWORD>)
As you can see the request works also without Content-Type and Accept.
To get the details of a single device:
URL:
GET https://iot.netwerk.t-mobile.nl:443/rest/device/<ID>
Headers:
Content-Type:application/json
Authorization:Basic base64(USERNAME:PASSWORD)
Accept:application/json
To get the details of the device don’t use the deviceId!
Regards, Roland
@Malte-Neumann Hi Malte, please send the 10 ICCIDs to support@iotcreators.com . I will check them .
Please use as PLMN IDs from page https://docs.iotcreators.com/docs/telekom-iot-networks-in-europe
Regards, Roland
@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
@Eben-van-Ellewee @Stefan-de-Lange Many many thanks for this hints! I will take this to our doc and dev team.
Regards, Roland
@Eben-van-Ellewee I opened the page with Chrome, Internet Explorer, Firefox. Additionally I did a “Save as” with Chrome and I also did a “GET” of the URL with Postman. In any of those cases I didn’t get any security complains of my HTTP client or the proxy.
Two days ago we had an outage for some hours of our documentation library. Maybe your problem has been caused by this.
Regards, Roland
@Marijn many thanks for this . I am highly interested in this.
Regards, Roland
