11.08.2008 3.1.3
New setting for a modem: voicecall_vts_list = yes/no.
Default value: no.
Defines how VTS command is used to create DTMF tones:
yes = AT+VTS=1,2,3,4,5 (list is used), no = each tone is created with single command like AT+VTS="1";+VTS="2" etc.
Security fix:
Tone definition string used to make a voicecall was not checked and it was possible to send user entered AT commands to the modem.
10.08.2008 3.1.2
Bug fixes:
Signal handlers are now silent. Previously informative messages were written to the log but at least in some environments this caused process to hang when logging function was called twice. This fix has no effect to the run script like /etc/init.d/sms3.
06.08.2008 3.1.1
New setting for a modem: messageids = number.
Default value: 2.
Defines how message id's are stored: 1 = first, 2 = last, 3 = all.
When all id's are stored, numbers are delimited whith space and there is one space and dot in the end of string.
Destination number can have minus characters, like 358-40-111 2222.
If a modem is used for sending only, it is initialized when a device spooler is started.
Filename preview is applied for sent and failed files too.
While checking the network registration status, some modems include extra space character in the answer. All space characters are now removed before second field of answer is checked. The format like "+CREG: 000,001" (Motorola) is now accepted. All additional fields are remove before testing.
New global setting: executable_check = yes/no.
Default value: yes.
This setting defines if all executables are checked during the startup check.
Usually eventhanler, alarmhandler etc. are shell scripts or some other single files which can be executed and therefore checked simply.
If using a settings like eventhandler = /usr/local/bin/php -f /usr/local/bin/smsd_eventhandler.php,
the check will fail and smsd will not start unless executable_check = no is defined.
If stats directory is defined, smsd will store and update message counter files in this directory.
If a file which is failed to send is empty, it's deleted even if there is failed folder defined.
While checking the network registration, result 3 (registration denied) will stop the modem process after two retries.
PIN handling is slightly improved. If a modem needs PIN, but there is no PIN defined in the configuration file, the process will stop.
Some modems do not include "OK" in the answer for CPMS query. In this case timeout time will be spent, but after this the answer is accepted if it includes at least 8 commas.
Bug fixes:
While reading PDU string from file and directory was defined for pdu_from_file setting, file handle for directory was not closed after finding the PDU file. After a while this caused modem process to stop with error message "Too many open files".
11.05.2008 3.1
General:
While running as an unpriviledged user, outgoing files which are not writable for smsd are re-created to fix the permissions.
In the log, a process id is now included in the "started" message.
Message sending time (how long it took) is logged. Some other changes and enhancements is also applied to the logging.
Outgoing message file:
Binary message can now have UDH-DATA defined.
New header: System_message: yes. With this setting message is sent as a system message. This kind of message has fixed values 0x40 for Protocol Identifier and 0xF4 for Digital Coding Scheme. A message cannot have User Data Header. Maximum length of a message is 140 bytes.
Incoming message file:
New header: Flash: yes. This header exists if a message was received as a flash (immediate display). Note that usually phone devices do not save flash messages, they can be saved manually if necessary.
Configuration file (smsd.conf):
New global setting: date_filename = number.
Default value: 0.
Defines if date is included to the filename of incoming message.
With value 1 like 2007-09-02.GSM1.xxxxxx and with value 2 like GSM1.2007-09-02.xxxxxx.
Baudrate 4800 is now supported.
New global setting: log_single_lines = yes/no.
Default value: yes.
Linefeeds are removed from the modem response.
New setting for a modem: check_network = yes/no.
Default value: yes.
Network checking can be disabled if it's known that a device cannot support it.
New settings for a modem: logfile and loglevel.
Default value: empty.
Each modem can now have it's own logfile and loglevel setting.
If logfile is not defined, global log is used.
15.08.2007 3.1beta7
After 3.1beta was released at march 2007, lot of changes are tested and implemented to the "stable" version of smsd. This new 3.1beta7 contains all changes and features included in the 3.0.10. Because the feature list of beta's was quite long, it's shortened and this new list contains only the changes and additions not included in the 3.0.10. Older beta versions are removed from the download area because there is no reason to use them.
Configuration file (smsd.conf):
New global setting: saved = directory.
Default value: empty.
If defined, smsd will store concatenation storage's to this directory (otherwise incoming directory is used).
At startup check existing concatenation storages are moved from incoming directory to saved directory.
Zero sized files are ignored.
If both directories has a storage file with data, fatal error is produced and the smsd does not start.
New global setting: phonecalls = directory.
Default value: empty.
If defined and reporting of phonecalls is used, message files are store to this directory
instead of incoming directory.
New setting for a modem: phonecalls = yes/no.
Default value: no.
Report phonecalls. Currently only missed calls are reported.
When a phonecall entry is read from the phone, eventhandler is executed with argument $1 = CALL.
This event can be used to make some actions after an unanswered phonecall is received.
New global setting: language_file = filename.
Default value: empty.
Message files can be written using localized headers.
See the localizing for details.
New setting for a modem: keep_open = yes/no.
Default value: yes
If this is changed to no, a modem is closed while it's not used.
Regular_run for a modem: Like in the global part, it is possible to define an external script or program which is executed regularly within a given interval. A modem is available for script and command definitions as well as logging can be defined. See the How to configure for details.
New global setting: datetime = format string.
Default value: compatible with previous versions of smsd.
Defining loglevels and alarmlevel, can use string value like LOG_NOTICE or "notice".
New command line argument -a (ask). In the configuration file there can be multiple choices for values and selections can be done while the smsd is starting.
Primary_memory and Secondary_memory settings can now have multiple parameters defined, like SM,SM,SM. Double-quotation marks are not necessary to use in the string.
All yes/no values are checked, also the "no" value should be typed correctly. Previously all incorrect values were interpreted as "no". This might have an effect if you have errors in the current setup. Possible errors are reported at startup and the smsd does not start spooling.
Device names are checked. Only alphanumeric characters, underline, minus-sign and dot are allowed.
All errors are reported, not just the first one found.
Numbers for the provider sorting can be given in the grouped format. (3.1beta4).
New global setting report = directory. This can be used to define where status report files are stored. By default they are stored to the Incoming Folder. (3.1beta3).
New global settings: keep_filename and store_original_filename to select file naming convention when files are moved between directories. (3.1beta).
New global settings: regular_run = filename and regular_run_interval = number. It is possible to define an external script or program which is executed regularly within a given interval. See an usage sample on How to run/use. (3.1beta).
Whitelist can specify a queue to be used with a list of numbers. See more details. (3.1beta).
New global setting: admin_to, destination number for administrative messages. Messages are sent without using the filesystem. (3.1beta).
New modem settings: message_limit, defines a maximum number of messages to be sent. message_count_clear defines a period to automatically clear the message counter. This value is number of minutes. (3.1beta).
New global setting: filename_preview = number. Defines how many characters of message text is concatenated to the name of messsage file. Currently works with incoming message files. (3.1beta).
Outgoing message file:
New header: Include: filename. 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.
New header: Macro: definition. Works like macros usually do. See the SMS file format for details.
Binary message can be automatically splitted to the concatenated messages. With Autosplit value of 0 message is not sent if it does not fit in the single message. All other Autosplit values cause concatenated UDH part to be inserted to the message parts. If a message starts with UDH data (which is the default for binary messages), concatenation header is inserted to the existing user data header. If there is no UDH by the user, a new header is created.
Unicode messages can now have part numbering as text (Autosplit: 2).
Priority: HIGH accepted case insensitive, all which means "yes" is accepted too (including localized strings).
Voicecall can now have TIME: number defined, where number is number of seconds to keep modem calling. 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.
To: number is accepted in the grouped format, like 358 12 345 6789. The number can also contain * and # character(s). (3.1beta3).
While smsd reads the message, all string length's are checked to prevent possible buffer overflows. (3.1beta).
Incoming message file:
New header: Length: number. Length of text / data. With Unicode text number of Unicode characters. If non-Unicode text message is stored using UTF-8, number of bytes may differ.
General:
While retrieving identification from device, CGSM is tried if IMSI is not supported.
Dirty patch for Wavecom SR memory bug is included in the PDU handling. If PDU starts with "000000FF00", first 8 bytes are removed and zeros are catenated to the PDU until it's length is enough. Because of missing information, the Status Report cannot be really fixed. With this patch the SR still can be handled, but all result codes are assumed to be "ok, message delivered".
Incoming PDU checking: content of a broken PDU is shown as much as possible.
Very simple communication feature is included in this version. If you need to communicate with a device, but do not have any terminal program available, you can start the smsd with a communicate option -C devicename, for example smsd -C GSM1. This runs smsd in terminal mode which can be breaked with Ctrl-C. (3.1beta3).
Smsd processes are listening SIGCONT signal to break an idle loops. When the mainspooler has moved a file to the outgoing folder, SIGCONT is sent to all modem processes. This causes a new message to be immediately handled and sent. This is especially important when a delaytime is long (for a modem and directory polling). (3.1beta2).
Execution order of checkhandler has changed: When the mainspooler finds a message file, checkhandler is executed first before anything else is done. This allows checkhandler to make changes to the message file, for example queue selecting or "nickname to phonenumber" replacing. The smsd can also be notified with return code 2, if checkhandler has spooled a message by itself. (3.1beta).
Execution order of eventhandler has changed: eventhandler is executed after a file is moved to it's final location. File will then have it's final directory and name, and the smsd does not do any prosessing with a file after an eventhanler was called. (3.1beta).
When the modem is initialized and modem answers ERROR to some command, an errorsleeptime is spent and a command is tried once again. If a program is going to terminate while the modem is initialized, initializing is interrupted immediately. (3.1beta).
Concatenated id start's from the random value between 1 ... 255. (3.1beta).
Modem is blocked only if sending has failed because of a modem related reason. (3.1beta).
"SMS sent" log information includes a message id and part information (while sending multipart messsages). (3.1beta).
Status report log information includes a message id and status value. (3.1beta).
Bug fixes:
If both received and sent PDU's were stored to the messsage files, some sent PDU's were lost if a message was received while the smsd was sending a multipart message. This is because the same buffer was used to store PDU's and receiving side cleaned it. Receiving and sending side now uses their own buffer to store PDU's.
18.07.2007 3.0.10
Configuration file (smsd.conf):
New global setting: os_cygwin = yes/no. Default value is no. Defines if the smsd is running on Cygwin environment. This information is needed when some process creates outgoing files with incorrect permissions for smsd. If smsd has no write access to the file, it tries to get it using chmod 766.
Bug fixes:
Command line argument -t had no effect. This terminal mode is useful when running smsd under Cygwin as a Windows service as it prevents one error message.
In QNX, the OS libraries include already an unlock() function, causing a name conflict. The unlock() function of smsd is therefore renamed.
06.07.2007 3.0.9
General:
Minor changes to the PDU checking.
Replace: usage is ignored while sending multipart message.
Character set conversion now converts incoming "currency symbol" (0x24 GSM) to € character (0xA4 ISO).
This can easily be changed in top of charset.c if necessary (should not be any reason).
The smsd does not send 0x24 while messages are written using ISO/UTF-8 character set.
Documentation is updated. Sample configuration files are not, see the How to configure for details of new features.
NOTE for users running smsd with very heavy load:
Thank's for all users who have provided feedback, idea's, code and fixes.
28.06.2007... 3.0.9beta2
General:
All incoming PDU's are checked comprehensively. If there is some illegal values in the content or illegal characters in the string or some characters are missing, a problem is reported and handling of a broken PDU is aborted. However, all possible junk cannot be detected because the PDU does not have any checksums.
If an incoming PDU does not match to the mode setting defined in the smsd.conf file, alternative mode is tried before error is reported and handling is aborted. This means that the mode setting is now automatic for PDU's of incoming messages. Note that the outgoing side works like before and you have to use correct mode -setting in the configuration file.
Number of devices is increased to 64.
While reading a PDU from file, a first line starting with PDU: and space is taken if any exists.
There is a simple script smstest.php included in the scripts directory. This script can be used to create sms files using a web browser. The script demonstrates a character set conversion made with PHP and can be used for testing purposes.
Installation / uninstallation: path of executables can now be defined in the Makefile.
Startup check: permission check for executable scripts is changed. Previously this check required mode 750 for scripts. Now owner and group settings are examined and permission is checked like a shell does.
International Mobile Subscriber Identity (IMSI) is asked once from the modem when it's first time initialized.
If a device supports this query, information is printed to each incoming message file as a new header:
IMSI: 123456789.
This header is also inserted to sent and failed files.
Running as an unpriviledged user: if user is set but group is unset, that user's normal groups (e.g. from /etc/groups) are used. This means you can allow other users on the system access to write messages to the outgoing spool without giving them direct access to the serial port.
When finding files from the spooler directories, the oldest file is selected.
If a file in the spool directory cannot be handled because of file mode or ownership, error message is printed to the log and alarm handler is called. As soon as the problem is fixed, a file is processed normally. If a file is deleted (outside of smsd), the smsd forgets past problems with it and in the future a file with the same name is processed as usual.
Outgoing message file:
New header: Replace: code. Code can be a number from 1 to 7.
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.
Note that the smsd does not use this value while sending concatenated (multipart) message.
This is because some phones do not understand concatenated message as a single message and
therefore a previously received part might become overwritten if a replace code is used.
SMSC setting is allowed only if there is a smsc set in the config file.
Incoming message file:
New header: From_TOA: string. Includes a Type Of Address definition with short explanation, like: "From_TOA: 91 international, ISDN/telephone".
New header: Report: yes/no. Tells if a status report is going to be returned to the SME.
New header: Replace: number. This header is included if a message has a Replace Short Message Type 1..7 (number) defined.
Configuration file (smsd.conf):
Setting: pdu_from_file = filename / dirname/ is slightly enhanced. The original setting style will work when it points to the file which is read and then deleted. If this setting ends with a slash and a directory with that name exists, file(s) are read from this directory (and deleted after processing). All files found from the given directory are processed one by one, expect hidden files (name begins with a dot). When this setting points to the directory, no dot's are allowed in any position of a path. Be very careful with this setting while it will delete the content of a whole directory.
New setting: log_charconv = yes/no. Default is no. With this setting a details of character set conversions (outgoing UTF-8 to ISO conversion and incoming GSM/ISO to UTF-8 conversion) is printed to the log. If smsd is compiled using DEBUGMSG definition, details are also printed to the console. Logging feature can be useful if you have some troubles with characters and like to know what exactly happens inside the smsd.
New setting for a modem: modem_disabled = yes/no. Default is no. This is for testing purposes. Whole messaging system including eventhandlers etc. can be tested without any working modem existing. Sending of messages is simulated in the similar way than with sending_disabled setting. Incoming messages are taken only from the file, if pdu_from_file is defined. No any communication is made between smsd and modem, but a device setting should still exist because smsd wants to open and close a device. If in you testing environment you do not have a priviledges to the usual modem device, like /dev/ttyS0, you can use a definition like device = /tmp/modemfile. If this file exists and is writable for the process owner, it's enough for smsd.
Startup check will now report if there is a queue defined but no provider numbers for it.
New global setting: store_sent_pdu = value. Default is 1. Possible values are: 0 = no PDU's are stored, 1 = failed (to send) PDU's are stored, 2 = failed PDU's and PDU's of binary/Unicode messages are stored, 3 = all PDU's are stored.
Validity period setting now accepts keywords typed mixed/upcase. Keyword can now be given without any numbers, like month means the same than 1 month. This same applies to the outgoing message files. When the smsd is started, a validity period setting is reported to the log if the setting used is less than maximum.
Each provider can now have up to 64 numbers defined.
Queue, provider and device/queues settings are checked. If there is too much definitions, an error message is displayed and the daemon does not start.
stats_interval defaults to 3600 (1 hour).
New setting: blockafter = number. Defines number of errors which will cause modem to be blocked. Default value is 3.
New setting for a modem: outgoing = yes/no. Default is yes. If set to no, a modem does not handle any outgoing message(s).
Bug fixes:
The smsd accepted definition of providers only if it was written as [provider] in the configuration file. Now singular/plural does not matter anymore, you can use [provider] or [providers]. This same applies to the queues: both definitions [queue] and [queues] are accepted.
When alphanumeric senders had length more than 9 characters, garbage was appended to the sender's name.
Setting of validity period did not accept clean numeric value, like 204 (for 12 weeks). An error message was produced and a default value (maximum possible time) was used. Validity setting also calculated some values incorrectly, like "3 months" produced a maximum time (63 weeks).
SMSC setting in the message file did not work. However, usually this setting should not be used.
20.06.2007 3.0.9beta
Outgoing message file:
When sending ISO coded message, all characters which cannot be transferred using the GSM character set are replaced with their alternatives. For example Ê becomes E, õ becomes o and so on. In the previous versions of smsd there was a replacement made only for few characters.
Configuration file (smsd.conf):
New setting: outgoing_utf8 = yes/no. Default is yes. With this setting automatic UTF-8 to ISO conversion of outgoing files can be switched off, if necessary.
Bug fixes:
Internal decoding of Unicode message was not done if a message contained only single part and no user data header including concatenation information. (Some devices include contatenation header even if there is only one part).
03.06.2007 3.0.8
General:
Some modem(s), probably because of the firmware bug, gives an "OK" answer while trying to read a message from the empty memory space. This causes an additional five seconds delay to the process, because an "ERROR" answer is expected. New version of smsd accepts both messages without any additional delay.
While a PIN code status is asked from the modem, some modems do not include "OK" result code in the response. This has caused an additional delay with those modems. Handling of response is changed to avoid delays. Also some informative message logging is added to the modem initialization.
If a modem does not accept the PIN code, the modem process will terminate immediately. Previously it tried to use the same incorrect PIN again and again, and this caused SIM card to be locked and the PUK code was then required.
When a message is sent successfully, possible previous errors with a modem are forgotten.
Logging of character set conversation problems is changed from LOG_INFO to LOG_NOTICE. Log lines have now name of a modem.
Configuration file (smsd.conf):
New setting: incoming_utf8 = yes/no. Incoming message files with ISO or GSM alphabet can be saved using UTF-8 character set. Default is no.
If a modem needs some idle time after a PIN is entered, new setting pinsleeptime can be used to produce that. This value is seconds.
New setting for a modem: pre_init = yes/no. This settting defaults to "yes" and causes "echo off" and "CMEE=1" commands to be sent to the modem before anything else is done.
Outgoing message file:
When an alphabet is ISO or GSM, smsd can also read files stored using the UTF-8 character set.
Autosplit works now with Unicode messages.
If a message text is longer than 70 Unicode (16-bit) characters, multiple messages are created.
Autosplit value 2 (text numbers) is not in use, with this setting a message is splitted as with setting 3,
to multiple part with an UDH numbering.
Please note that while creating a text part for message file, a coding UCS-2BE should be used (not UCS-2).
Bug fixes:
Storage for startup error strings was not initialized properly.
If a message file in the spooler is readable, but some program is still keeping it open to write, smsd tried to spool the file and failed because the file cannot be deleted. As a fix, the smsd first checks if the message file is writable.
18.05.2007 3.0.7
General:
If smsd is compiled without a support for status monitor, command line option -s is not useable.
Bug fixes:
Incorrectly written message file without an empty line between the header part and text part caused modem process to scratch if there was previously sent a message with less header lines or message text containing an empty line.
14.03.2007 3.0.6
General:
New header Modem: devicename is automatically inserted to the SENT/FAILED message files.
Message_id: n and Sent: timestamp headers are inserted to the message file before eventhandler is executed.
20.02.2007 3.0.5
General:
Termination handling is changed. Previously the main process sent SIGTERM to the whole process group. With sh shell it was possible that incorrect processes were killed because they were running in the same process group. Also processes started from the eventhandler received SIGTERM and eventhandler was terminated before the job was completelly done. New version of smsd sends SIGTERM to the modem processes only. This allows smooth shutdown to the eventhandlers. If there is some eventhandlers running while the smsd gets a termination signal, an information is written to the logfile and main process will wait until all modem processes are terminated.
If smsd is running on terminal (foreground), smsd shuts down when a terminal window is closed.
Internal combine can now handle 16-bit message reference numbers too.
Log line titles are now completely process based. For example the "SMS received" message tells now which one process (=modem) received that SMS.
22.01.2007 3.0.4
Bug fixes:
Incoming PDU was not handled correctly when there was no SMSC information in the PDU string.
Also note that in this case there will not be From_SMSC: field in the message file,
which should be notified by the event handler.
11.01.2007 3.0.3
It is no more necessary to use the & sign at the end of a starting command line.
There is a command line switch -t available to force smsd to run in terminal (foreground). If logging or debugging messages are printed to the terminal, smsd runs in foreground by default. There is also TERMINAL keyword available in the Makefile to force smsd to run in foreground.
The start-stop script sms3 is updated.
The smsd now removes possible infofile and *.LOCK files at startup,
it is no more necessary to take care of them in the script.
New script can be used with most operating systems.
See more details on How to run/use.
General:
The smstools uses ISO character set in message files. If a locale is set to UTF-8, smsd does not handle outgoing message files correctly. There is sample scripts checkhandler-utf-8 and eventhandler-utf-8 in the scripts directory to demonstrate how character set conversation can be made using checkhandler and eventhandler.
While smsd reads the configuration, all string length's are checked to prevent possible buffer overflows.
More checks are done at startup. Fatal errors while reading the config are written to the log and starting the daemon is prevented. Executable permissions of eventhandler(s) are checked.
Lockfile is detected by finding ".LOCK" from the end of filename instead of the whole string.
A logfile setting can be made using the command line argument -l (ell). This overrides the config file setting.
If received SMS is status report, log line starts with "SMS received (Report)".
It's no more necessary to define user=root to get smsd running as a root.
NOTE for Windows users: If you are running smsd as a Windows service, you need to update settings of cygrunsrv. The smsd should be run in terminal mode and --neverexits option should not be used anymore. See more details on instructions for Windows.
30.11.2006 3.0.2
General:
The smsd can be defined to run without root priviledges.
System check is performed at startup to avoid some potential problems with permissions of directory structure and some other settings.
If a config file cannot be read, the smsd does not stay running.
Only the process id of a main process is written to the pid file.
Some code cleaning is done to avoid compiler warnings on Solaris 10 (6/06 x86) with gcc.
mypath setting is not used anymore.
Configuration file (smsd.conf):
user = username and group = groupname settings to change priviledges for the smsd.
infofile = filename and pidfile = filename settings to change file locations, needed when the smsd is not running as a root.
Bug fixes:
14.11.2006 3.0.1
General:
When syslog is used to logging, a modem name is presented in the log line.
Outgoing PDU: Data Coding Scheme uses message class bits only when message is sent as an alert (flash).
Some code has 'cleaned' to avoid compiler warning messages.
Bug fixes:
Syslog call is now made using a format string.
There was two compiler warnings (with gcc >= 4) because blacklist.c and whitelist.c missed prototypes of exit() function.
Buffer used to store received PDU's was not initialized correctly. This caused a runtime error while concatenating multipart messages on latest Ubuntu releases.
02.11.2006 3.0
Bug fixes:
Blacklist and Whitelist handling: fixed incorrect log message when the file was not readable. Also fixed the program termination in those cases.
If write_to_modem failed, for example because the modem was not clear to send, put_command did not free the memory used by regexp.
While reading a configuration file there was stack misuse which caused device_list become empty while running on ubuntu 6.10.
25.09.2006 3.0beta
This version is based to the SMS Server Tools version 2.2.8.
Some of new features were previously published as an enhancements to the 2.x version. Now these features are officially maintained in this new 3.x version of smstools.
Configuration file (smsd.conf):
Received PDU's can be stored to the incoming message file. It's possible to select which kind of PDU's will be stored.
Message validity time can be selected for default.
Incoming Unicode message can be decoded internally.
Incoming multipart message can be combined internally.
Dual memory handler: it's possible to read messages from both memories (SIM and Mobile Equipment).
Incoming PDU string can be read from the file. This is for testing purposes.
Sending can be disabled. This is for testing purposes.
Outgoing message file:
Priority can be set to high. This also works while the Provider Queue is used.
Message validity time can be selected for the message.
It's possible to make a voice call with DTMF tones.
Binary messages can be presented as a Hex in the message file. There is a Wap Push demo using this feature.
After a message is sent, Message_id is stored to the file if a status report was requested.
General:
A new sms3 script is available (in the scripts directory) as an alternative for the original sms script. This new script handles some special issues, including a smoother shutdown, multiple instance prevention and force-stop ability.
If a modem reading reaches timeout, it will be reported to the log file.
If for some reason the file moving fails, destination lock is removed.
While creating a log file, file access permissions are limited to 640 (-rw-r-----).
Provider definition can now have 's' for short numbers. For example: "FINLAND = 358, s". If this is not defined to any provider, outgoing message file must have a provider queue setting while sending to short number.
Bug fixes:
In the outgoing message file the "UDH: yes/no" setting did not work correctly. However using this setting is not necessary because this value defaults to true when it's needed.
Short number preceeding with 's' caused number become empty and sending failed.