Error: +CME ERROR: 513
-
Hello all,
Im using a Sodaq NB-IoT shield with an arduino board and the latest library from sodaq_nbiot.
It worked fine a week ago.
The error i get from the debug message now is: +CME ERROR: 513, what tells me that it isn’t be able to save it?Is there something changed in the network?
Can i do something to prevent this?I hope to hear soon,
Thanks in advance,
Paul -
Hi Paul,
Can you check if you have attachment?
AT+CGATT? should return “1” if you are attached to the network.
I can reproduce the CME: 513 error if I try to send a message before I have attachment.
-
@andre-rodenburg said in Error: +CME ERROR: 513:
I can reproduce the CME: 513 error if I try to
Hello,Yes i am connected to the network, when i send an message i’ll get an OK back.
The next problem i’ve got since this morning is that all messages are recieved by Nokia Impact, only when they send them to our endpoint, we’ll get an acces denied (403). When i put the same request in Postman i’ll recieve an TRUE.
Is there something changed in the Nokia Impact post?
-
@paul-koenen said in Error: +CME ERROR: 513:
So the CME: 513 error is fixed?
The next problem i’ve got since this morning is that all messages are recieved by Nokia Impact, only when they send them to our endpoint, we’ll get an acces denied (403). When i put the same request in Postman i’ll recieve an TRUE.
At what api call all do you receive this 403?
-
Yes, the 513 is fixed,
We doesn’t use a api call, we have created an endpoint and for all the data T-mobile (Nokia Impact) push to us.
Before 4 mei it worked just fine, after that we’ve recieved the 403 (acces denied). Only we haven’t changed a thing is our code.
So i gues there is something changed on T-mobile side?
What is the message we’re recieving from T-Mobile? -
Hi Paul,
Can you give us some more details?
What API call are you trying todo?Also what IMEI are u using?
-
Als het goed is, ben je er al uit toch @Paul-Koenen ?
