NOTE the difference of ISO and UTF-8 since version 3.1.16:

Handling of alphabets is enhanced and all conversions are now done using internal routines which work well with cyrillic languages too. For backward compatibility, the alphabet of message file still defaults to ISO-8859-15, and this can be changed to UTF-8 in the configuration, or a header Alphabet: UTF can should be used.

Alphabet: ISO

• depending on the global setting outgoing_utf8 (which defaults to yes), UTF-8 is still accepted and converted.
• optical replacement is done, depending on the modem setting cs_convert_optical (which defaults to yes).
• characters are converted to the GSM alphabet, and missing characters are dropped.

Alphabet: UTF

• like with ISO, but if any characters cannot be converted to the GSM alphabet, whole message is converted to the UCS2 alphabet.
• if conversion to UCS2 is done, each message part will have less characters and therefore more parts will be required, but the text delivers as it was written.

Sets the Message Class, 0...3.

Sets Data Coding Scheme in the PDU. Note that value must be represented as two hexadecimal digits.

Together with Alphabet: binary setting the binary data can be presented in hexadecimal format.
Since version 3.1.16 this can be used with text messages other than UCS2 too.

One byte should be presented with two hexadecimal characters, for example 0F. Text can have empty lines and comment lines starting with /, ', # or : character. Also after hexadecimal bytes there can be a comment character marking the rest of line as a comment.

Special keywords available:

See example below for more details.

Some parts of a message can be read from different file. If an included file contains only text part, it should begin with one empty line.

These settings define National Language Shift Tables to be used. Text body must be written using UTF-8 character set. Value can be number, or variable length string which first macthes (case insensitive).
Choices are:

• 0 = basic
• 1 = Turkish
• 2 = Spanish
• 3 = Portuguese
• 4 = Bengali and Assemese, or Bengali, or Assemese
• 5 = Gujarati
• 6 = Hindi
• 7 = Kannada
• 8 = Malayalam
• 9 = Oriya
• 10 = Punjabi
• 11 = Tamil
• 12 = Telugu
• 13 = Urdu

Usually it is not necessary to set Language_ext value. When Language is set, Language_ext defaults to the same, and if only Language_ext is defined, Language defaults to basic character set. If nothing is set, default values are taken from the configuration.

Syntax is: Macro: name=value. Multiple macros can be defined. All name's found in the message body are replaced with a value.

Sets TP-MR field in the PDU. Number can be 0...255.

Selects the Short Message Type 0, which is also known as a silent SMS. As this kind of SMS is not stored by the receiving device, report is always requested, even if report was disabled in the configuration.

Sets TP-RD bit in the PDU.

If a receiving device and SIM supports "Replace Short Message Type n" -feature, a previously received message with the same code is replaced with a new message. Only the messages sent from the same originating address can be replaced. If there is nothing to replace, a message is stored in the normal way.

Sets TP-RP bit in the PDU.

Defines how many times smsd will retry if sending fails. This overrides send_retries setting.

With this setting message is sent as a system message. This kind of message has fixed values 0x40 for Protocol Identifier and 0xF4 for Data Coding Scheme. A message cannot have User Data Header. Maximum length of a message is 140 bytes.

Since version 3.1.7, value for this setting can be 2 or ToSIM for communicating with SIM applications. SMS is sent as SS (no show) and stored (sent) to SIM. Currently this only works with binary messages.

If this feature is enabled by defining text_is_pdu_key in the configuration, and To: number matches that key, message body is handled as ready made PDU.

See Using Type Of Address selection for more details.

Incorrect values are ignored.

With this feature the smsd will make a voice call to the receivers phone number given in To: header. If the receiver answers to the call, some DTMF tones are played.
The message text must start with TONE: keyword. After this there can be number and space, which is number of times to repeat the tone sending. Supported tones are #,*,0...9 and the tone list must be comma separated.
For example:
TONE:   1,2,3,4,5,6,7,8,9,0
- this plays all digits, and it's repeated 3 times which is the default.

TONE:   5   #,#,#
- this plays three #'s, and it's repeated 5 times.

TONE:
- some default tones are played 3 times.

Since version 3.1 additional TIME: number definition can be used. After a time has reached, hang up is done. If a call is answered before a time is reached, normal sound playing is done. NOTE that this time counting starts after a command is given to the modem and there will be some delay before receiving device starts ringing. You should test this with your own handset to find a reasonable time which works fine in the network you are using. Example:
TONE:   TIME:   15   2   #

Before using this feature to serious alarm purposes, you should test if this works with you modem/phone. Also notice that automatic redialing should be turned off in the phone's settings.

After version 3.1.3 VTS command usage can be selected with voicecall_vts_list setting, see the How to configure for more details.

After version 3.1.5 there is a new voicecall_ignore_modem_response setting for problematic devices, see the How to configure for more details. Also notice voicecall_hangup_ath setting if AT+CHUP does not hangup call on your device.

After version 3.1.7 there is a voicecall_cpas setting available. If your device returns OK immediately after a dial command, with this setting AT+CPAS can be used to detect when a call is answered. With this setting TIME: has no effect.