Hello everyone, I know it’s been a while since someone last posted here, and you may have gotten your question figured out. However, for those of you who are still finding this thread, and are wondering the same thing that started the thread. I will attempt to answer your questions from my experience with the R410/R412.
It turns out that your experience with SMS is a well documented issue, and it has to do with the MNO network that your modem might be riding on (NOT a hologram issue). More to the point, it has to do with what network gear the tower you are talking to, and what version of the standard it has implemented. I know this sounds ominous, and if you don’t do something about it, it will likely be a BIG problem as you move forward.
Fortunately, there is an answer, and that’s to set up a listening socket on UDP. It’s actually much lower cost overall, and provides a layer of security to your device, since it will be tucked nicely behind the hologram API, versus open for for everyone to exploit.
The procedure to test things out goes as follows, using a terminal interface…
- Once connected to the network , set up an IP connection ( you probably do this already)
AT+CGDCONT=1,“IP”,“hologram” - Activate the profile (likely do this too)
AT+CGACT=1,1 - Create a UDP socket (might be new to you), and it will return the socket number created. We will assume it returned “0”.
AT+USOCR=17 - Listen on the socket created. it will return “OK” of you are in business.
AT+USOLI=0,4010 - Go to your hologram dashboard and open the messaging console for the device you just set up, and select “cloud data” as the method versus “SMS”
- Don’t forget to set the port (4010), and UDP as the method.
- Type in your message and click send.
- Eventually you should receive a ++UUSORF message
- Send AT+USORF=0,1024 to the modem. This says get up to 1K bytes from socket 0.
- The reply should tell you what IP address the data came from, and how many bytes are in the message, and then the message itself.
I hope that helps.