Problem solved. It denpends on the sim card

The command for the US is:
AT+CGDCONT=1,“IP”, “iot.nb”

It is true that there is no time synchronization in Germany. The CCLK feature does not work on the network in Germany. The manual of the n211 says it comes back with a +CCLK measage but in practice it only gives OK when this feature does not work on the network.

Best Regards

Hello Max,

our network supports just one active PDP context per connection.

Best regards

Hi,

This might help a little:

Reception levels:

Excellent: >= -105 dBm

Very good: >= -115 dBm

Good: >= -125 dBm

Average: >= -137dBm

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

The PLMN of Telekom Deutschland is 26201

Hello,

Unfortunately, there is no app for the iPhone because the iPhone would have installed an NB-IoT-capable modem upfront. The iPhones do not have it. The easiest way to check the data reception level is to use an NB-IoT modem.

Best Regards!

In Germany we have rolled out Band 8.

You should firstly check your firewall rules. It’s possible that your server accepts incoming UDP packets but drops outgoing packets on that specific port. You should firstly check your firewall rules. If there is a problem on your servers side, I can try to explain to you how you can configure everything in python to get it to work. From this you can adapt it to your tools and infrastructure. First of all we open a socket and tell it to listen to a specific port:

import socket

sock = socket.socket(socket.AF_INET, socket.SOCK_DGRAM) # UDP
sock.bind((‘’, 16666)) # bind the socket to address (port)
message, address = sock.recvfrom(1024)
Now our server is ready to receive messages on port 16666. From our modem we send some data to the server with IP:Port in our case ww.xx.yy.zz:16666:

at+nsost=0,ww.xx.yy.zz,16666,3,414243
In python you will then get something like this

message = ‘ABC’
address = (‘85.147.106.108’, 3618)
With the following command we can send a message back to the client (our NB-IoT module):

sock.sendto(“Hello World”, address)
With these commands everything should work properly.

Make sure that you send the answer from the same socket (i.e. same source port) otherwise it won’t work (network will drop the packets). So for example the following won’t work:

import socket

sock = socket.socket(socket.AF_INET, socket.SOCK_DGRAM) # UDP
sock.bind((‘’, 16666)) # bind the socket to address (port)
message, address = sock.recvfrom(1024)
…
Receive some data here
…
sock.sendto(‘Hello World!’, address) # this will work fine

Now we close the socket and open a new one with a different source port (on the same server so same IP)

sock.close()
sock = socket.socket(socket.AF_INET, socket.SOCK_DGRAM)
sock.bind((‘’, 1883)) # different source port than before
sock.sendto(‘Hello World!’, address)
Even so we send the packet to the correct address (IP:Port) the module will never receive the packet because the source port ist different this time.

Please let me know if this was of any help.

Best regards