Manual:Tools/Sms: Difference between revisions
No edit summary |
|||
| Line 88: | Line 88: | ||
USSD (Unstructured Supplementary Service Data) messages can be used to communicate with mobile network provider to receive additional information, enabling additional services or adding funds to prepaid cards. | USSD (Unstructured Supplementary Service Data) messages can be used to communicate with mobile network provider to receive additional information, enabling additional services or adding funds to prepaid cards. | ||
USSD messages can be proceeded by using AT commands (commands can differ or even may be blocked on some modems) '''3G or GSM network mode must be activated to proceed those messages''', as they are not supported under LTE only mode ('''R11e-LTE''' modem auto switches to 3G mode to send out USSD message) | USSD messages can be proceeded by using AT commands (commands can differ or even may be blocked on some modems). | ||
'''3G or GSM network mode must be activated to proceed those messages''', as they are not supported under LTE only mode ('''R11e-LTE''' modem auto switches to 3G mode to send out USSD message). | |||
PDU (Protocol Data Unit) message and it's decrypted version in printed under LTE debug logging | PDU (Protocol Data Unit) message and it's decrypted version in printed under LTE debug logging | ||
| Line 127: | Line 128: | ||
11:51:23 gsm,info USSD: konta atlikums | 11:51:23 gsm,info USSD: konta atlikums | ||
</pre> | </pre> | ||
== Receiving == | == Receiving == | ||
Revision as of 13:15, 11 September 2018
Applies to RouterOS: v5 +
Summary
Sub-menu: /tool sms
Package: advanced-tools
Standards:
It is possible to connect GSM modem to RouterOS device and use it to send and receive SMS messages. RouterOS lists such modem as serial port that appears in '/port print' listing. GSM standard defines AT commands for sending SMS messages, and defines how messages should be encoded in these commands.
'advanced-tools' package provides command '/tool sms send' that uses standard GSM AT commands to send SMS.
Sending
Command: /tool sms send
Example
Sending command for ppp interface:
/tool sms send usb3 "20000000" \
message="ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz!@#\$%^&*(){}[]\"'~"
For lte interface use lte interface name in port field:
/tool sms send lte1 "20000000" \
message="ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz!@#\$%^&*(){}[]\"'~"
Send command takes following parameters:
| Parameter | Description |
|---|---|
| port (string) | Name of port from /port list that GSM modem is attached to. |
| phone-number (string) | Recepient phone number. Allowed characters are "0123456789*#abc". If first character is "+" then phone number type is set to international, otherwise it is set to unknown. |
| channel (integer) | Which modem channel to use for sending. |
| message (string) | Message contents. It is encoded using GSM 7 encoding (UCS2 currently is not supported), so message length is limited to 160 characters (characters ^{}\[]~ |
| smsc (string) | |
| type (string) | If set to class-0, then send class 0 SMS message. It is displayed immedeately and not stored in phone. |
Note: Since V3.23 there is one port per modem, and modem has channels used for commands and data. Channels have numbers 0,1,2, etc. Some modems may have just two channels, some have more. The SMS tool has channel support since v3.28
USSD messages
USSD (Unstructured Supplementary Service Data) messages can be used to communicate with mobile network provider to receive additional information, enabling additional services or adding funds to prepaid cards. USSD messages can be proceeded by using AT commands (commands can differ or even may be blocked on some modems). 3G or GSM network mode must be activated to proceed those messages, as they are not supported under LTE only mode (R11e-LTE modem auto switches to 3G mode to send out USSD message). PDU (Protocol Data Unit) message and it's decrypted version in printed under LTE debug logging
Example
Check if LTE debug logging is active:
/system logging print Flags: X - disabled, I - invalid, * - default # TOPICS ACTION PREFIX 0 * info memory 1 * error memory 2 * warning memory 3 * critical echo
If there is no logging entry add it by running:
/system logging add topics=lte,!raw
/system logging print
Flags: X - disabled, I - invalid, * - default
# TOPICS ACTION PREFIX
0 * info memory
1 * error memory
2 * warning memory
3 * critical echo
4 lte,!raw memory
To recieve account status from *245#
/interface lte at-chat lte1 input="AT+CUSD=1,\"*245#\",15" output: OK /log print 11:51:20 lte,async lte1: sent AT+CUSD=1,"*245#",15 11:51:20 lte,async lte1: rcvd OK 11:51:23 lte,async,event +CUSD: 0,"EBB79B1E0685E9ECF4BADE9E03", 0 11:51:23 gsm,info USSD: konta atlikums
Receiving
Since v3.24 RouterOS also supports receiving of SMS messages, and can execute scripts, and even respond to the sender.
Before router can receive SMS, relevant configuration is required in general /tool sms menu. Following parameters are configurable:
| Parameter | Description |
|---|---|
| allowed-number (string; Default: "") | Sender number that will be allowed to run commands, must specify country code ie. +371XXXXXXX |
| channel (integer; Default: 0) | Which modem channel to use for receiving. |
| keep-max-sms (integer; Default: 0) | Maximum number of messages that will be saved. If you set this bigger than SIM supports, new messages will not be received!' |
| port (string; Default: (unknown)) | Modem port (modem can be used only by one process "/port> print" ) |
| receive-enabled (yes | no; Default: no) | Must be turned on to receive messages |
| secret (string; Default: "") | the secret password, mandatory |
Inbox
Sub-menu: /tool sms inbox
If you have enabled the reader, you will see incoming messages in this submenu.
Read-only properties:
| Property | Description |
|---|---|
| phone (string) | Senders phone number. |
| message (string) | Message body |
| timestamp (time) | Time when message was received. It is the time sent by operator, not the router's local time. |
| type (string) | Message type |
Syntax
:cmd SECRET script NAME [[ VAR[=VAL] ] ... ]
- SECRET - the password
- NAME - name of the script that's available in "/system script"
- VAR - variables that will be passed to the script (can be passed as VAR or as VAR=value), separated by spaces.
Other things to remember:
- *Parameters can be put into quotes "VAR"="VAL" if necessary.
- *Escaping of values is not supported (VAR="\"").
- *Combined SMS are not supported, every SMS will be treated separately
- * 16Bit unicode messages are not supported
- * SMS are decoded with the standard GSM7 alphabet, so you can't send in other encodings, otherwise it will be decoded incorrectly
Examples
Wrong:
:cmd script mans_skripts :cmd slepens script mans skripts :cmd slepens script mans_skripts var= :cmd slepens script mans_skripts var= a :cmd slepens script mans_skripts var=a a
Right:
:cmd slepens script mans_skripts :cmd slepens script "mans skripts" :cmd slepens script mans_skripts var :cmd slepens script mans_skripts var=a :cmd slepens script mans_skripts var="a a"
Debugging
/tool sms send command is logging data that is written and read. It is logged with tags gsm,debug,write and gsm,debug,read For more information see system logging.
Implementation details
AT+CMGS and AT+CMGF commands are used. Port is acquired for the duration of the command and cannot be used concurently by another RouterOS component. Message sending process can take a long time, it times out after a minute and after two seconds during initial AT command exchange.
See also
- http://www.3gpp.org/ftp/Specs/html-info/27-series.htm
- http://www.3gpp.org/ftp/Specs/html-info/23-series.htm
[ Top | Back to Content ]