Just to add a bit more information, this doesn't need AT commands. The SMS could be accessed either via browser or with basic BASH script to get the data in XML format through the modem's IP.
www.developershome.com
Interesting to head that some cell modems have a web interface. The one I'm using (Telit via SixFab) does not, only an AT interface. At least as far as I've found in the documentation so far.
Yes. Cell phones are in constant low-level contact with the nearest cell tower, mostly to tell the tower "I am here and I will be able to hear a broadcast". Towers then regularly send out a broadcast, which says "Hi, I have some traffic for 123-456-7890, if you hear this please come online". That traffic could then become a SMS, or a phone call, or just a request for "didn't hear from you in a while, tell me that you're still around".
As far as I can tell from looking at the interface, the cell "phone" does have a persistent memory buffer for multiple SMS messages, and there seem to be commands to read and delete from these buffers. I didn't go into great detail on that: Since I need to set up IP connectivity over the cell modem anyway, I decided to not bother with SMS, but instead use traditional e-mail (SMTP and all that) once the IP connection is up.
That might be easier to do if the cell phone provider has a service that allows e-mail based SMSes. In reality, SMS come from the cell provider (In the US, typically AT&T, Verizon and T-Mobile), and are held in their cloud during transit. These providers know how to interface to other services, right from their cloud. I know that in the US, the Twilio e-mail service had some SMS capability in its sendgrid product, but I never looked into the details. You might not need to use a cell phone or modem at all to integrate SMS.
Absolutely. I am using it in my server to send me sms whenever zabbix trigger an issue.
#!/bin/sh
MODEM_IP="192.168.8.1"
/usr/local/bin/curl -s -X GET "http://$MODEM_IP/api/webserver/SesTokInfo" > /tmp/ses_tok.xml
/bin/chmod 777 /tmp/ses_tok.xml
COOKIE=`grep "SesInfo" /tmp/ses_tok.xml | cut -b 58-185`
TOKEN=`grep "TokInfo" /tmp/ses_tok.xml | cut -b 205-236`
if [ "$1" = "sms" ]; then
/usr/local/bin/curl -v http://$MODEM_IP/api/sms/send-sms -H "Cookie: $COOKIE" -H "__RequestVerificationToken: $TOKEN" -H "Content-Type: application/x-www-form-urlencoded; charset=UTF-8" --data "<?xml version='1.0' encoding='UTF-8'?><request><Index>-1</Index><Phones><Phone>$2</Phone></Phones><Sca></Sca><Content>$3</Content><Length>160</Length><Reserved>1</Reserved><Date>-1</Date></request>"
elif [ "$1" = "read" ]; then
curl -s -X POST "http://$MODEM_IP/api/sms/sms-list" -H "Cookie: $COOKIE" -H "__RequestVerificationToken: $TOKEN" -H "Content-Type: text/xml" -d "<request><PageIndex>1</PageIndex><ReadCount>10</ReadCount><BoxType>1</BoxType><SortType>0</SortType><Ascending>0</Ascending><UnreadPreferred>1</UnreadPreferred></request>" > /tmp/modem_status.xml
message=$(grep -r -E 'Phone|Content' /tmp/modem_status.xml | sed -e 's/<[^>]*>//g' | sed -e 's/^[ \t]*/------\n/g')
echo "$message\n------"
elif [ "$1" = "rssi" ]; then
curl -s -X GET "http://$MODEM_IP/api/device/information" -H "Cookie: $COOKIE" -H "__RequestVerificationToken: $TOKEN" -H "Content-Type: text/xml" > modem_status.xml
curl -s -X GET "http://$MODEM_IP/api/device/signal" -H "Cookie: $COOKIE" -H "__RequestVerificationToken: $TOKEN" -H "Content-Type: text/xml" >> modem_status.xml
wmode=$(cat modem_status.xml | grep workmode | sed -e 's/<[^>]*>//g')
rssi=$(cat modem_status.xml | grep rssi | sed -e 's/<[^>]*>//g')
echo "mode: $wmode"
echo "signal: $rssi"
fi