1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
1001
1002
1003
1004
1005
1006
1007
1008
1009
1010
1011
1012
1013
1014
1015
1016
1017
1018
1019
1020
1021
1022
1023
1024
1025
1026
1027
1028
1029
1030
1031
1032
1033
1034
1035
1036
1037
1038
1039
1040
1041
1042
1043
1044
1045
1046
1047
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060
1061
1062
1063
1064
1065
1066
1067
1068
1069
1070
1071
1072
1073
1074
1075
1076
1077
1078
1079
1080
1081
1082
1083
1084
1085
1086
1087
1088
1089
1090
1091
1092
1093
1094
1095
1096
1097
1098
1099
1100
1101
1102
1103
1104
1105
1106
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116
1117
1118
1119
1120
1121
1122
1123
1124
1125
1126
1127
1128
1129
1130
1131
1132
1133
1134
1135
1136
1137
1138
1139
1140
1141
1142
1143
1144
1145
1146
1147
1148
1149
1150
1151
1152
1153
1154
1155
1156
1157
1158
1159
1160
1161
1162
1163
1164
1165
1166
1167
1168
1169
1170
1171
1172
1173
1174
1175
1176
1177
1178
1179
1180
1181
1182
1183
1184
1185
1186
1187
1188
1189
1190
1191
1192
1193
1194
1195
1196
1197
1198
1199
1200
1201
1202
1203
1204
1205
1206
1207
1208
1209
1210
1211
1212
1213
1214
1215
1216
1217
1218
1219
1220
1221
1222
1223
1224
1225
1226
1227
1228
1229
1230
1231
1232
1233
1234
1235
1236
1237
1238
1239
1240
1241
1242
1243
1244
1245
1246
1247
1248
1249
1250
1251
1252
1253
1254
1255
1256
1257
1258
1259
1260
1261
1262
1263
1264
1265
1266
1267
1268
1269
1270
1271
1272
1273
1274
1275
1276
1277
1278
1279
1280
1281
1282
1283
1284
1285
1286
1287
1288
1289
1290
1291
1292
1293
1294
1295
1296
1297
1298
1299
1300
1301
1302
1303
1304
1305
1306
1307
1308
1309
1310
1311
1312
1313
1314
1315
1316
1317
1318
1319
1320
1321
1322
1323
1324
1325
1326
1327
1328
1329
1330
1331
1332
1333
1334
1335
1336
1337
1338
1339
1340
1341
1342
1343
1344
1345
1346
1347
1348
1349
1350
1351
1352
1353
1354
1355
1356
1357
1358
1359
1360
1361
1362
1363
1364
1365
1366
1367
1368
1369
1370
1371
1372
1373
1374
1375
1376
1377
1378
1379
1380
1381
1382
1383
1384
1385
1386
1387
1388
1389
1390
1391
1392
1393
1394
1395
1396
1397
1398
1399
1400
1401
1402
1403
1404
1405
1406
1407
1408
1409
1410
1411
1412
1413
1414
1415
1416
1417
1418
1419
1420
1421
1422
1423
1424
1425
1426
1427
1428
1429
1430
1431
1432
1433
1434
1435
1436
1437
1438
1439
1440
1441
1442
1443
1444
1445
1446
1447
1448
1449
1450
1451
1452
1453
1454
1455
1456
1457
1458
1459
1460
1461
1462
1463
1464
1465
1466
1467
1468
1469
1470
1471
1472
1473
1474
1475
1476
1477
1478
1479
1480
1481
1482
1483
1484
1485
1486
1487
1488
1489
1490
1491
1492
1493
1494
1495
1496
1497
1498
1499
1500
1501
1502
1503
1504
1505
1506
1507
1508
1509
1510
1511
1512
1513
1514
1515
1516
1517
1518
1519
1520
1521
1522
1523
1524
1525
1526
1527
1528
1529
1530
1531
1532
1533
1534
1535
1536
1537
1538
1539
1540
1541
1542
1543
1544
1545
1546
1547
1548
1549
1550
1551
1552
1553
1554
1555
1556
1557
1558
1559
1560
1561
1562
1563
1564
1565
1566
1567
1568
1569
1570
1571
1572
1573
1574
1575
1576
1577
1578
1579
1580
1581
1582
1583
1584
1585
1586
1587
1588
1589
1590
1591
1592
1593
1594
1595
1596
1597
1598
1599
1600
1601
1602
1603
1604
1605
1606
1607
1608
1609
1610
1611
1612
1613
1614
1615
1616
1617
1618
1619
1620
1621
1622
1623
1624
1625
1626
1627
1628
1629
1630
1631
1632
1633
1634
1635
1636
1637
1638
1639
1640
1641
1642
1643
1644
1645
1646
1647
1648
1649
1650
1651
1652
1653
1654
1655
1656
1657
1658
1659
1660
1661
1662
1663
1664
1665
1666
1667
1668
1669
1670
1671
1672
1673
1674
1675
1676
1677
1678
1679
1680
1681
1682
1683
1684
1685
1686
1687
1688
1689
1690
1691
1692
1693
1694
1695
1696
1697
1698
1699
1700
1701
1702
1703
1704
1705
1706
1707
1708
1709
1710
1711
1712
1713
1714
1715
1716
1717
1718
1719
1720
1721
1722
1723
1724
1725
1726
1727
1728
1729
1730
1731
1732
1733
1734
1735
1736
1737
1738
1739
1740
1741
1742
1743
1744
1745
1746
1747
1748
1749
1750
1751
1752
1753
1754
1755
1756
1757
1758
1759
1760
1761
1762
1763
1764
1765
1766
1767
1768
1769
1770
1771
1772
1773
1774
1775
1776
1777
1778
1779
1780
1781
1782
1783
1784
1785
1786
1787
1788
1789
1790
1791
1792
1793
1794
1795
1796
1797
1798
1799
1800
1801
1802
1803
1804
1805
1806
1807
1808
1809
1810
1811
1812
1813
1814
1815
1816
1817
1818
1819
1820
1821
1822
1823
1824
1825
1826
1827
1828
1829
1830
1831
1832
1833
1834
1835
1836
1837
1838
1839
1840
1841
1842
1843
1844
1845
1846
1847
1848
1849
1850
1851
1852
1853
1854
1855
1856
1857
1858
1859
1860
1861
1862
1863
1864
1865
1866
1867
1868
1869
1870
1871
1872
1873
1874
1875
1876
1877
1878
1879
1880
1881
1882
1883
1884
1885
1886
1887
1888
1889
1890
1891
1892
1893
1894
1895
1896
1897
1898
1899
1900
1901
1902
1903
1904
1905
1906
1907
1908
1909
1910
1911
1912
1913
1914
1915
1916
1917
1918
1919
1920
1921
1922
1923
1924
1925
1926
1927
1928
1929
1930
1931
1932
1933
1934
1935
1936
1937
1938
1939
1940
1941
1942
1943
1944
1945
1946
1947
1948
1949
1950
1951
1952
1953
1954
1955
1956
1957
1958
1959
1960
1961
1962
1963
1964
1965
1966
1967
1968
1969
1970
1971
1972
1973
1974
1975
1976
1977
1978
1979
1980
1981
1982
1983
1984
1985
1986
1987
1988
1989
1990
1991
1992
1993
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
2027
2028
2029
2030
2031
2032
2033
2034
2035
2036
2037
2038
2039
2040
2041
2042
2043
2044
2045
2046
2047
2048
2049
2050
2051
2052
2053
2054
2055
2056
2057
2058
2059
2060
2061
2062
2063
2064
2065
2066
2067
2068
2069
2070
2071
2072
2073
2074
2075
2076
2077
2078
2079
2080
2081
2082
2083
2084
2085
2086
2087
2088
2089
2090
2091
2092
2093
2094
2095
2096
2097
2098
2099
2100
2101
2102
2103
2104
2105
2106
2107
2108
2109
2110
2111
2112
2113
2114
2115
2116
2117
2118
2119
2120
2121
2122
2123
2124
2125
2126
2127
2128
2129
2130
2131
2132
2133
2134
2135
2136
2137
2138
2139
2140
2141
2142
2143
2144
2145
2146
2147
2148
2149
2150
2151
2152
2153
2154
2155
2156
2157
2158
2159
2160
2161
2162
2163
2164
2165
2166
2167
2168
2169
2170
2171
2172
2173
2174
2175
2176
2177
2178
2179
2180
2181
2182
2183
2184
2185
2186
2187
2188
2189
2190
2191
2192
2193
2194
2195
2196
2197
2198
2199
2200
2201
2202
2203
2204
2205
2206
2207
2208
2209
2210
2211
2212
2213
2214
2215
2216
2217
2218
2219
2220
2221
2222
2223
2224
2225
2226
2227
2228
2229
2230
2231
2232
2233
2234
2235
2236
2237
2238
2239
2240
2241
2242
2243
2244
2245
2246
2247
2248
2249
2250
2251
2252
2253
2254
2255
2256
2257
2258
2259
2260
2261
2262
2263
2264
2265
2266
2267
2268
2269
2270
2271
2272
2273
2274
2275
2276
2277
2278
2279
2280
2281
2282
2283
2284
2285
2286
2287
2288
2289
2290
2291
2292
2293
2294
2295
2296
2297
2298
2299
2300
2301
2302
2303
2304
2305
2306
2307
2308
2309
2310
2311
2312
2313
2314
2315
2316
2317
2318
2319
2320
2321
2322
2323
2324
2325
2326
2327
2328
2329
2330
2331
2332
2333
2334
2335
2336
2337
2338
2339
2340
2341
2342
2343
2344
2345
2346
2347
2348
2349
2350
2351
2352
2353
2354
2355
2356
2357
2358
2359
2360
2361
2362
2363
2364
2365
2366
2367
2368
2369
2370
2371
2372
2373
2374
2375
2376
2377
2378
2379
2380
2381
2382
2383
2384
2385
2386
2387
2388
2389
2390
2391
2392
2393
2394
2395
2396
2397
2398
2399
2400
2401
2402
2403
2404
2405
2406
2407
2408
2409
2410
2411
2412
2413
2414
2415
2416
2417
2418
2419
2420
2421
2422
2423
2424
2425
2426
2427
2428
2429
2430
2431
2432
2433
2434
2435
2436
2437
2438
2439
2440
2441
2442
2443
2444
2445
2446
2447
2448
2449
2450
2451
2452
2453
2454
2455
2456
2457
2458
2459
2460
2461
2462
2463
2464
2465
2466
2467
2468
2469
2470
2471
2472
2473
2474
2475
2476
2477
2478
2479
2480
2481
2482
2483
2484
2485
2486
2487
2488
2489
2490
2491
2492
2493
2494
2495
2496
2497
2498
2499
2500
2501
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="Title" content="SMS Server Tools 3">
<meta name="Robots" content="INDEX,FOLLOW">
<meta name="Language" content="English">
<meta http-equiv="PRAGMA" content="no-cache">
<meta http-equiv="CACHE-CONTROL" content="no-cache">
<title>SMS Server Tools 3</title>
<STYLE type="text/css">
BODY {
BACKGROUND: #ffffff; MARGIN: 5px 5px 10px; FONT: 10pt verdana, geneva, lucida, arial, helvetica, sans-serif; COLOR: #000000
}
td {
FONT: 10pt verdana, geneva, lucida, arial, helvetica, sans-serif;
}
h3 {
background-color: #DCDCFE;
}
blockquote {
background-color: #FFD;
font-size: 90%;
padding:5pt;
padding-top:1pt;
margin-bottom:5pt;
border-style: outset;
border-color: #aaaa99;
border-width: 0.05pt 2pt 2pt 0.05pt;
}
blockquote p:first-letter {
font-size: 110%;
font-weight: bold;
color: red;
}
</STYLE>
</head>
<body>
<h2><font color=blue><a href="http://smstools3.kekekasvi.com">SMS Server Tools 3</a></font></h2>
<a href="index.html">Home</a>
<h3>Future plans (some of them)</h3>
<!-- START -->
<p>
<ul>
<li><p>
Built-in Wap Push message support (already done but can be enhanced).
</p></li>
<li><p>
Error handler and reporting feature which can send message(s) to "administrative emergency" number.
</p></li>
<li><p>
Configuration changes via administrative SMS.
</p></li>
<li><p>
SMSC Large Account support. (Not coming very soon).
</p></li>
<li><p>
About support for incoming messages with Symbian S60 based smart phones like Nokia N95 etc.:<br>
There will be <b>no support</b> for those devices as they do not show incoming messages thru the AT command interface.<br>
See F.A.Q. for more details.
</p></li>
If you have any comments, ideas, needs or other SMS Server Tools 3 related things, please write them
to <a href="http://smstools3.kekekasvi.com?p=support">SMSTools3 Community</a> which is a support forum for this software.
</ul>
</p>
<h3>Coming to the next version, not yet released</h3>
<p>
Estimated release time for following additions <s>is fall 2009.</s> <i>was fall 2009, but the publishing is delayed.</i>
</p>
<p>
<ol>
<li><p>
Faster spooling algorithm. Required if system has <u>lot</u> of modems and <u>very</u> much messages to send.
Current algorithm works well on systems with less than 10 - 15 modems and with about 500 -600 messages per hour per each modem.
</p></li>
<li><p>
SQL database based spooling and message handling.
Can be used together with current filesystem based spooling, or instead of it.
At least MySQL will be supported, probably SQLite too.
</p></li>
</ol>
</p>
<!--
<h3>Coming to the next version, currently available as beta</h3>
-->
<h3>Version history</h3>
<b>21.06.2010 3.1.11</b>
<ol>
<li><p>
A modem setting <b>ussd_convert = number</b> can now have a new value: <b>4</b>.
With this value text part from the USSD answer is converted from hexadecimal dump to ASCII.
</p></li>
<li><p>
Some cleanup has been done to the code.
The fix for "overlapped buffers" bug now uses it's own function containing a simple loop, instead of using memmove().
</p></li>
</ol>
<p>
<a href="http://smstools3.kekekasvi.com/packages/">Download</a>
</p>
<hr>
<b>19.06.2010 3.1.10</b>
<p>
Bug fixes:
<ol start="1">
<li><p>
Global settings <i>international_prefixes</i>, <i>national_prefixes</i> and global and modem setting <i>priviledged_numbers</i>
did not always work because of an "overlapped buffers" bug.
This failure happened on 32bit environments too.
</p></li>
</ol>
</p>
<hr>
<b>17.06.2010 3.1.9</b>
<ol>
<li><p>New setting for a modem: <i><b>trust_spool = yes/no</b></i>.<br>
<font size="1">Default value: <i>yes</i>.</font><br>
When a modem process is searching for a file from the spooler, it assumes that the file is complete when it exists and it's not locked.
This will speed up sending, because one second delay is avoided.
If some other process or checkhandler is creating files directly to the spooler, it may be necessary to set this to <i>no</i>.
</p></li>
<li><p>
When searching for a file to send, the lock file is created before the one second delay is spent.
</p></li>
<li><p>New global setting: <i><b>log_read_from_modem = yes/no</b></i>.<br>
<font size="1">Default value: <i>no</i>.</font><br>
In some cases, when resolving troubles with a modem, it's useful to see exact data which is received from the modem.
This setting is similar than <i>log_unmodified</i>, but displays the data as a hexadecimal dump.</i>
</p></li>
<li><p>
Programs <i>regular_run</i> and <i>regular_run_post_run</i> now get the device name as a third argument.
</p></li>
<li><p>
The script <i>sendsms</i> has automatic detection of character set and creates Unicode messages if necessary.
</p></li>
<li><p>New setting for a modem: <i><b>send_handshake_select = yes/no</b></i>.<br>
<font size="1">Default value: <i>yes</i>.</font><br>
Instead of checking the flag TIOCM_CTS, select() function is used when the serial transmitted is busy.
If because of some reason the old style should be used, this setting allows it.
</p></li>
<li><p>
With a setting <i>trim_text = yes</i>, whitespaces are not removed if the message is going blank.
This is because some people, really, need to send a message which contains only single space character.
</p></li>
</ol>
<p>
Bug fixes:
<ol start="8">
<li><p>
When manipulating strings, the coding style assumed that strcpy() and some other functions start copying from the begin of a buffer.
That's how those have worked for years, but it's against what the manual of those functions says about overlapped buffers.
With <b>64bit Ubuntu 10.04</b> running on <b>Intel</b> processor this caused serious failures.
The code is reviewed and fixed.
</p></li>
<li><p>
When a <i>Sent</i> header was printed to the incoming message file, wrong variable was used causing that only current date was printed.
</p></li>
<li><p>
The setting <i>umask</i> did not work properly and that caused the message files became world writable.
</p></li>
</ol>
</p>
<hr>
<b>05.05.2010 3.1.8</b>
<ol>
<li><p>
Added "init info" for chkconfig to the init.d script sms3.
</p></li>
</ol>
<p>
Bug fixes:
<ol start="2">
<li><p>
When a signal quality was asked from the modem, and it was explained to the log, incorrect severity was used.
Changed severity from LOG_NOTICE to LOG_INFO.
</p></li>
</ol>
</p>
<hr>
<b>02.05.2010 3.1.7</b>
<ol>
<li><p>
When a signal quality is asked from the modem, it's also explained to the log.
</p></li>
<li><p>
The sample script <b>sendsms</b> can now use keys for protecting the usage, for example when running with <i>tcpserver</i> over the internet.
</p></li>
<li><p>
The name of a global setting <i>datetime</i> is changed to <i>datetime_format</i>.
The old name can still be used because of backward compatibility.
</p></li>
<li><p>
The init.d script sms3 now uses option -n for setting the process title:
ARGS="<b>-n </b>MAINPROCESS -p$PIDFILE -i$INFOFILE".
Smsd still works without that option, because of backward compatibility.
</p></li>
</ol>
<p>
Bug fixes:
<ol start="5">
<li><p>
If a setting <i>voicecall_hangup_ath</i> was not defined in the configuration, default value was handled as <i>yes</i>, but it's defined as <i>no</i>.
</p></li>
<li><p>
A modem setting <i>status_signal_quality</i> was not parsed and was giving a startup error.
</p></li>
</ol>
</p>
<hr>
<p>
<b>20.04.2010 3.1.7beta7</b>
</p>
<ol>
<li><p>New global setting: <i><b>suspend = filename</b></i>.<br>
<font size="1">Default value: <i>not in use</i>.</font><br>
With this file, any modem process can be suspended.
When a process is suspended, the modem port is closed and modem process does not do anything.
</p><p>
The file is checked before smsd starts sending or receiving.
If a name of the device is found from the file, suspend will start.
The format of a line in file is: <b><devicename>: <reason></b>.
Colon is needed, but the <reason> is optional.
It is printed to the log.
A special line <b>ALL: <reason></b> can also be used, and this affects for all modem processes.
</p><p>
When a process is suspended, the file is checked every ten seconds, or more frequently if the <i>delaytime</i> value is smaller.
</p><p>
When a process is suspended, it listens a signal SIGUSR2.
If this signal is received, modem process will send and receive messages <u>once</u>.
</p></li>
<li><p>New setting for a modem: <i><b>phonecalls_error_max = number</b></i>.<br>
<font size="1">Default value: <i>3</i>.</font><br>
Specifies the maximum number of errors before phonecalls are ignored.
</p></li>
</ol>
<p>
Bug fixes:
<ol start="3">
<li><p>
Modem setting <i>socket_connection_errorsleeptime</i> (from 3.1.7beta4) did not work because it's name is longer than the code was able to handle.
</p></li>
</ol>
</p>
<p>
<b>18.04.2010 3.1.7beta6</b>
</p>
<ol>
<li><p>
A modem setting <b>phonecalls = yes/no</b> can now have a new value: <b>clip</b>, or <b>2</b>.
This value could be used with modems which do not support reading of phonebook,
or phobebook cannot be used because entries cannot be deleted.
Phocecall is detected using the <i>+CLIP Calling line identification report</i> from a modem.
</p><p>
When <i>phonecalls = clip</i> is used, a setting <i>hangup_incoming_call</i> is automaticatty set to <i>yes</i>.
This is because smsd <u>must</u> hangup a call before it's handled.
Smsd also initializes a modem with +CLIP=1 automatically to enable this functionality.
</p></li>
<li><p>
File of a missed call has now more headers, like file of a received SMS has:
<ul>
<li><b>Subject:</b> <modemname></li>
<li><b>Modem:</b> <modemname></li>
<li><b>Number:</b> <phone number> (if defined in the configuration)</li>
<li><b>IMSI:</b> <string> (if available)</li>
</ul>
</p></li>
<li><p>
The setting <i>date_filename</i> now applies for files of missed calls too.
</p></li>
</ol>
<p>
Bug fixes:
<ol start="4">
<li><p>
When <i>filename_preview</i> was used, creation of modified filename for message file of a missed call caused modem process to freeze.
</p></li>
<li><p>
When dialling of a voicecall ended with timeout, the result was taken from the answer of hangup and was "OK". Now it's "Timeout".
</p></li>
</ol>
</p>
<p>
<b>16.04.2010 3.1.7beta5</b>
</p>
<ol>
<li><p>
When running smsd as an unpriviledged user and <b>group</b> is defined,
given group is added to the group access list which is initialized by reading the group database.
In the previous versions of smsd the given group was used as only group.
</p></li>
<li><p>New settings for a modem:</p>
<p>
<i><b>start = modem command</b></i>.<br>
<font size="1">Default value: <i>not in use</i>.</font><br>
<i><b>startsleeptime = number</b></i>.<br>
<font size="1">Default value: <i>3</i>.</font><br>
<i><b>stop = modem command</b></i>.<br>
<font size="1">Default value: <i>not in use</i>.</font><br>
<br>
If defined, <i>start</i> command is sent to the modem when a modem process starts.
After a command is sent, <i>startsleeptime</i> is spent.
When a modem process is stopping, <i>stop</i> command is sent to the modem.
</p></li>
<li><p>
When using queues without provider sorting, it's no more necessary to define providers.
The number list of each queue defaults to "catch-all", which is the same as "0,1,2,3,4,5,6,7,8,9,s".
See the <a href="configure2.html">manual</a> for more details and examples.
</p></li>
</ol>
<p>
Bug fixes:
<ol start="4">
<li><p>
In the 3.1.7beta4, when eventhandler_ussd was used and the answer was read back from the file, extra linefeed was included in the answer string.
This linefeed was printed to the log and statfile.
</p></li>
</ol>
</p>
<p>
<b>11.04.2010 3.1.7beta4</b>
</p>
<p>
In addition to other changes, this version contains couple of changes which were provided as a patch by <i>yjh</i>,
a member of SMSTools3 Community.
<a href="http://smstools3.kekekasvi.com/topic.php?id=73">This topic</a> contains more details.
These changes were originally going to the version 3.2, but because it's still delayed, I publish those changes now.
</p>
<p>
In 3.2, handling of character sets is based on <i>iconv</i> and the code is widely changed.
Because the "iconv" patch in 3.1.7 is not very well tested, it's disabled by default.
Edit the src/Makefile to enable the patch, if necessary.
The patch requires that UTF-8 is used as a locale.
</p>
<ol>
<li><p>New global setting: <i><b>logtime_format = format string</b></i>.<br>
<font size="1">Default value: <i>compatible with previous versions of smsd</i>.</font><br>
With this setting a format of the timestamp in the logging can be set.
The format string is strftime() compatible.
</p></li>
<li><p>New global setting: <i><b>use_linux_ps_trick = yes/no</b></i>.<br>
<font size="1">Default value: <i>no/yes</i></font><br>
This setting changes the way how smsd processes are shown in the process list.
Instead of command line, processes can be shown like "smsd: MAINPROCESS", "smsd: GSM1" etc.
In the Makefile there is a definition which sets the default value for this setting.
This is a "Linux trick", it's not quaranteed that this can be used in all possible environments.
</p></li>
<li><p>
In the outgoing message file, the setting <b>System_message</b> can now have a value <i>2</i> or
<b>ToSIM</b> for communicating with SIM applications.
SMS is sent as <i>SS</i> (no show) and stored (sent) to SIM.
Currently this only works with binary messages.
</p></li>
<li><p>
If <b>USE_ICONV</b> is defined in the src/Makefile, <i>iconv</i> is used for character set conversions.
The current implementation works with Unicode and UTF-8 and could be used with cyrillic languages.
</p></li>
<li><p>New global setting: <i><b>date_filename_format = format string</b></i>.<br>
<font size="1">Default value: <i>compatible with previous versions of smsd</i>.</font><br>
With this setting a format of the timestamp in filenames (<i>date_filename >= 0</i>) can be set.
The format string is strftime() compatible.
</p></li>
<li><p>New setting for a modem: <i><b>device_open_retries = number</b></i>.<br>
<font size="1">Default value: <i>1</i>.</font><br>
Defines how many times smsd will retry when cannot open a device.
When maximum number of retries is reached, modem process will call alarmhandler and stop.
With value -1 smsd will retry forever.
</p></li>
<li><p>New setting for a modem: <i><b>device_open_alarm_after = number</b></i>.<br>
<font size="1">Default value: <i>0</i>.</font><br>
After defined number of retries, an alarmhandler is called.
Smsd still continues trying, if <i>device_open_retries</i> value is bigger.
</p></li>
<li><p>New setting for a modem: <i><b>device_open_errorsleeptime = number</b></i>.<br>
<font size="1">Default value: <i>30</i>.</font><br>
Defines how many seconds the smsd will sleep after an error with device open.
</p></li>
<li><p>New setting for a modem: <i><b>socket_connection_errorsleeptime = number</b></i>.<br>
<font size="1">Default value: <i>5</i>.</font><br>
Defines how many seconds the smsd will sleep after an error with socket connection.
</p></li>
<li><p>New command line options: <i><b>-Ex</b></i> and <i><b>-Dx</b></i>.
<ul>
<li><b>-Ex</b> encodes a given string to the GSM 7bit packed format.
The string can be written using ISO or UTF-8 alphabet.</li>
<li><b>-Dx</b> decodes a given string from GSM 7bit packed format.
The result uses ISO alphabet, or UTF-8 if <i>incoming_utf8 = yes</i> is defined in the configuration file.</li>
</ul>
<p>
Both options can used as a helper for USSD message handlers.
When these optios are used, smsd does not start as a daemon.
Therefore options can be used even when smsd is running as a daemon.
</p>
</p></li>
<li><p>New setting for a modem: <i><b>ussd_convert = number</b></i>.<br>
<font size="1">Default value: <i>0</i>.</font><br>
Defines if a text part from incoming USSD message is decoded.
Possible values are:<br>
<table border=1 bgcolor=lightgrey>
<tr><td bgcolor=yellow valign=top> 1 </td><td>Unicode format is converted to UTF-8. This requires that USE_ICONV is defined.</td></tr>
<tr><td bgcolor=yellow valign=top> 2 </td><td>GSM 7bit packed format is converted to ISO or UTF-8.</td></tr>
</table>
<p>Decoded text is appended to the original answer with two slashes and one space character.
</p>
</p></li>
<li><p>New setting for a modem: <i><b>eventhandler_ussd = filename</b></i>.<br>
<font size="1">Default value: <i>not in use</i>.</font><br>
This setting defines an eventhandler to use with USSD messages.
It is possible to use the same script or program which is used as <i>eventhandler</i>,
but it's not a default because basically those scripts are not compatible without modifications.
<br><br>
After an USSD message is received, and probably <i>ussd_convert</i> is done, eventhandler_ussd is called.
Smsd checks what is the current character set of a modem and creates a temporary file which contains the USSD answer.
Arguments for the eventhandler_ussd are:<br>
<table border=1 bgcolor=lightgrey>
<tr><td bgcolor=yellow valign=top> $1 </td><td>"USSD" keyword.</td></tr>
<tr><td bgcolor=yellow valign=top> $2 </td><td>Filename (which contains the answer).</td></tr>
<tr><td bgcolor=yellow valign=top> $3 </td><td>Devicename.</td></tr>
<tr><td bgcolor=yellow valign=top> $4 </td><td>Character set.</td></tr>
<tr><td bgcolor=yellow valign=top> $5 </td><td>Command what was used to get the USSD answer.</td></tr>
</table>
<p>
Eventhandler_ussd can do whatever is needed with the USSD answer.
It can also modify the answer, or delete the file.
After eventhandler_ussd returns, smsd will check if the file still exists.
If it exists, it's first line is taken as a new answer.
Modified answer is then logged and probably printed to the regular_run_statfile.
</p>
</p></li>
</ol>
<p>
Bug fixes:
<ol start="13">
<li><p>
Removed reasons for compiler warning messages when compiling with -W -Wall under x64.
</p></li>
<li><p>
In 3.1.7beta2 socket_connection_retries was counted incorrectly.
</p></li>
</ol>
</p>
<p>
<b>30.03.2010 3.1.7beta3</b>
</p>
One important feature has been requested, but I forgot to include it in the previous version :(.
So here it is:
<ol>
<li><p>New setting for a modem: <i><b>regular_run_post_run = filename</b></i>.<br>
<font size="1">Default value: <i>not in use</i>.</font><br>
This setting can define the second script or program which is executed regularly.
The same script with <i>regular_run</i> can be used.
The script gets an argument <i>$1</i> which is <i>PRE_RUN</i> for <i>regular_run</i> and <i>POST_RUN</i> for <i>regular_run_post_run</i>.
There is also the second argument <i>$2</i>, which includes a definition of <i>regular_run_statfile</i>.
<br>
<br>
This is how the regular_run for a modem currently works:
<ul>
<li>If <i>regular_run</i> is defined, it's executed with arguments <i>PRE_RUN</i> and <i>regular_run_statfile</i>.
A modem is closed while the script is running.
<i>regular_run_statfile</i> is available from the previous run.
</li>
<li><i>regular_run_statfile</i> is deleted.
</li>
<li>If <i>regular_run_cmdfile</i> is defined and the file exists, commands from this file are sent to the modem.
If <i>regular_run_logfile</i> is defined, results are written to the file.
If <i>regular_run_statfile</i> is defined, results are written to this file too.
NOTE: <i>regular_run_cmdfile</i> is deleted after commands are handled.
Use PRE_RUN phase or an external process to create this file.
</li>
<li>If <i>regular_run_cmd</i>, one or more, is defined, commands are sent to the modem.
Results are logged and written to the statfile, if defined.
</li>
<li>If <i>regular_run_post_run</i> is defined, it's executed with arguments <i>POST_RUN</i> and <i>regular_run_statfile</i>.
</li>
</ul>
</p></li>
</ol>
<p>
<b>29.03.2010 3.1.7beta2</b>
</p>
<ol>
<li><p>
Smsd can connect directly to the network modem.
This enhancement is provided by Hubert Gilch, SEP Logistik AG.
</p><p>
A <i>device</i> definition which starts with <b>@</b> character is handled as a socket.
Format for the internet host is: <i>@<host_or_ip>:<port></i>.
Host definition can be name or IP address.
</p></li>
<li><p>New setting for a modem: <i><b>socket_connection_retries = number</b></i>.<br>
<font size="1">Default value: <i>11</i>.</font><br>
Defines how many times smsd will retry when a socket connection fails.
When maximum number of retries is reached, modem process will call alarmhandler and stop.
With value -1 smsd will retry forever.
</p></li>
<li><p>New setting for a modem: <i><b>socket_connection_alarm_after = number</b></i>.<br>
<font size="1">Default value: <i>0</i>.</font><br>
After defined number of retries, an alarmhandler is called.
Smsd still continues trying, if <i>socket_connection_retries</i> value is bigger.
</p></li>
<li><p>New setting for a modem: <i><b>report_device_details = yes/no</b></i>.<br>
<font size="1">Default value: <i>no/yes</i>.</font><br>
Defines if a details from device are printed to the log when modem process is starting.
With beta versions of smsd this setting defaults to <i>yes</i>, otherwise it defaults to <i>no</i>.
</p></li>
<li><p>New setting for a modem: <i><b>using_routed_status_report = yes/no</b></i>.<br>
<font size="1">Default value: <i>no</i>.</font><br>
Smsd can detect routed status reports, but usually it's not recommended to use them.
Modems should store status reports as an ordinary messages, which can be read when smsd will need them.
However, some modem cannot store status reports, and therefore routing is the only way to get them.
With this setting smsd will change some severity and text of a logging.
</p></li>
<li><p>New setting for a modem: <i><b>routed_status_report_cnma = yes/no</b></i>.<br>
<font size="1">Default value: <i>yes</i>.</font><br>
Defines if +CNMA acknowledgement is needed to send after routed status report was received.
</p></li>
<li><p>New setting for a modem: <i><b>phonecalls_purge = yes/no/string</b></i>.<br>
<font size="1">Default value: <i>no</i>.</font><br>
Usually missed calls are deleted from the device using AT+CPBW=index command.
Some modems do not support this command, and have an alternative way to clear Missed Calls storage.
With setting <i>yes</i>, this feature uses Siemens compatilbe way for purging: <i>AT^SPBD="MC"</i>.
Another command can be defined as a string.
</p></li>
<li><p>New setting for a modem: <i><b>voicecall_vts_quotation_marks = yes/no</b></i>.<br>
<font size="1">Default value: <i>no</i>.</font><br>
Defines if quotation marks are used when sending VTS command to the modem.
NOTE: previously quotation marks were used, now this setting default to <i>no</i>.
</p></li>
<li><p>New setting for a modem: <i><b>voicecall_cpas = yes/no</b></i>.<br>
<font size="1">Default value: <i>no</i>.</font><br>
Defines if AT+CPAS is used to detect when a call is answered.
This is required if modem returns OK immediately after the call.
</p></li>
<li><p>New setting for a modem: <i><b>needs_wakeup_at = yes/no</b></i>.<br>
<font size="1">Default value: <i>no</i>.</font><br>
After being idle, some modems do not answer to the first AT command.
For example with BenQ M32, there can be OK answer, but in many times there is not.
To avoid error messages, smsd first send AT and read the answer if it's available.
</p></li>
<li><p>New setting for a modem: <i><b>keep_messages = yes/no</b></i>.<br>
<font size="1">Default value: <i>no</i>.</font><br>
Defines if messages are not deleted from the device.
Unlike a global setting <i>keep_messages</i>, smsd continues running.
</p></li>
<li><p>New global setting: <i><b>umask = value</b></i>.<br>
<font size="1">Default value: <i>empty</i>.</font><br>
Effective umask for smsd can be set in the configuration file.
Value can be hexadecimal, decimal or octal format.
</p></li>
<li><p>New global setting: <i><b>log_unmodified = yes/no</b></i>.<br>
<font size="1">Default value: <i>no</i>.</font><br>
In some cases, when resolving troubles with a modem, it's useful to see what kind of line ends were received from the modem.
With this setting spaces and line ends are not removed from the string which is logged.
This setting overrides the setting <i>log_single_lines</i>.
</p></li>
<li><p>New global setting: <i><b>trim_text = yes/no</b></i>.<br>
<font size="1">Default value: <i>yes</i>.</font><br>
With this setting trailing whitespaces are removed from the outgoing message.
Does not effect with messages written using Unicode or GSM alphabet.
</p></li>
<li><p>
When a modem process is starting, it's checked if reading of messages is supported.
This version will not do the check, if a device is not going to read incoming messages.
</p></li>
<li><p>
When checking the PIN, some modems include quotation marks in the answer.
Some modems may leave a space away after <i>+CPIN:</i>.
Those kind of answers are now handled.
</p></li>
<li><p>
When initializing a modem, and it does not respond, after 5 retries the port is closed and reopened.
</p></li>
<li><p>
When handling the smsc setting from configuration file, extra + sign is removed from it.
</p></li>
<li><p>
Message counter file (for example GSM1.counter) is always created, even when messages are not yet sent.
</p></li>
<li><p>
Startup check will check that any modem does not use duplicate device name.
</p></li>
<li><p>
Locked files in the spooler: as in the past, <i>*.LOCK</i> files are handled as locked files, and now
<i>LOCKED*</i> files are handled as locked too.
</p></li>
<li><p>
When using a communication mode, it's no longer necessary that the name of a modem is in the <i>devices</i> list.
It's enough that a section for the modem exists.
Note, that still no more than one smsd can run at the same time.
</p></li>
<li><p>
When sending SMS and From field is not defined, content of a setting <i>number</i> is printed to the log:
"Sending SMS from <number> to <destination>".
If the setting <i>number</i> is not defined, log line is as before: "Sending SMS from to <destination>".
</p></li>
</ol>
<p>
Bug fixes:
<ol start="24">
<li><p>
When a GMGL list was handled and sorted, older message was not read first.
With this fix messages are sorted by the date and time when a message was sent.
</p></li>
<li><p>
When reading messages from the modem, some modems return only LF characters, even when both CR and LF should be returned.
Some modems may give the answer with double line-ending. Both cases are now handled.
</p></li>
</ol>
</p>
<p>
<b>01.02.2010 3.1.7beta</b>
</p>
This is not the major version change, it's publishing is still delayed.
This version continues 3.1.x and contains some minor features which may be useful for some users.
<ol>
<li><p>New global setting: <i><b>ignore_exec_output = yes/no</b></i>.<br>
<font size="1">Default value: <i>no</i>.</font><br>
Usually eventhandlers should not output anything.
If there is some output, it usually means that some error has occurred.
These errors are often problematic, because that output cannot be seen and error is therefore not notified.
Smsd will print any output from the evenhandlers to the log file.
This output can also be used for debugging purposes, but usually debugging should be done by running eventhandler manually.
With a setting <i>ignore_exec_output = yes</i> this feature can be disabled.
</p></li>
</ol>
<hr>
<p>
<b>30.11.2009 3.1.6</b>
</p>
This version was released because of a critical bug in the handling of a concatenation storage.
Users of version 3.1.5 should upgrade to this version.
As a workaround, disable purging of a concatenation storage with a global setting in the smsd.conf: <i>ic_purge_hours = 0</i>.
If <i>ic_purge_minutes</i> was set, remove the setting or change it to 0.
<ol>
<li><p>
Outgoing message files with the same timestamp are selected by name.
</p></li>
<li><p>
Carriage return characters are removed from the modem response when writing it to the log.
</p></li>
<li><p>
Trouble logging is slightly enhanced: if something was printed to the log and trouble is over, "Everything is ok now" is printed to the trouble log.
</p></li>
<li><p>
Regular_run_statfile is created using the same mask as the message files.
</p></li>
</ol>
<p>
Bug fixes:
<ol start="5">
<li><p>
Purging of a concatenation storage freezed modem process in some environments. This was caused by too small buffer.
</p></li>
<li><p>
With incoming Unicode messages the Euro character was decoded incorrectly.
</p></li>
<li><p>
When checkhandler spooled a message and returned a value 2, trouble logging was started.
</p></li>
<li><p>
Destination number was accepted even if it contained 's' only.
</p></li>
<li><p>
Check_memory_method using CMGL did not accept zero as a message number.
</p></li>
</ol>
</p>
<hr>
<p>
<b>01.06.2009 3.1.5</b>
</p>
<ol>
<li><p>New global setting: <i><b>smart_logging = yes/no</b></i>.<br>
<font size="1">Default value: <i>no</i>.</font><br>
This feature is available when file based logging is used.
If <i>loglevel</i> is less than 7 (for example "notice" is a good choise with smart_logging),
trouble log (with loglevel 7) about whole communication is written to different file if there has been any errors.
<p>
"Whole communication" means sending single SMS, receiving single SMS, and other things what smsd will do after idle time is spent.
When communication starts, all possible log lines are collected to internal buffer and only <i>loglevel</i> lines are written to the <i>logfile</i>.
If during communication there are any errors, all collected lines are printed to trouble log when communication reaches it's end.
</p>
<p>
This feature was made because with loglevel 7 logfile grows very much and fast, and debug level is not usually needed when there was no any errors.
In case of errors it's important to see whole communication, not just a single line which says that "something happened".
</p>
<p>
File name is created with the rule: if lenght of <i>logfile</i> setting is more than 4 characters and setting ends with ".log",
trouble log filename will end with "_trouble.log".
If length is less than 4 or setting does not end with ".log", trouble log filename is <i>logfile</i> appended with ".trouble".
In usual cases <i>logfile</i> is <b>/var/log/smsd.log</b> and trouble log filename will be <b>/var/log/smsd_trouble.log</b>,
or in some (Debian, Ubuntu, ...) distributions: <b>/var/log/smstools/smsd.log</b> and <b>/var/log/smstools/smsd_trouble.log</b>.
</p>
</p></li>
<li><p>
New setting for a modem: <i><b>unexpected_input_is_trouble = yes/no</b></i><br>
<font size="1">Default value: <i>yes</i>.</font><br>
With smart_logging, this setting defines if unexpected input activates trouble log.
</p></li>
<li><p>
New global and modem setting: <i><b>hangup_incoming_call = yes/no</b></i><br>
<font size="1">Default value: <i>no</i>.</font><br>
If set to <i>yes</i> and detected unexpected input contains "RING", incoming call is ended.
Use setting <i>voicecall_hangup_ath</i> to define if "ATH" is used to make hangup instead of "AT+CHUP".
</p></li>
<li><p>
New setting for a modem: <i><b>communication_delay = number</b></i><br>
<font size="1">Default value: <i>0</i>.</font><br>
Only some very problematic modems may need this setting.
Defines minimum time in milliseconds between latest answer from modem and next command which will be sent to modem.
</p></li>
<li><p>New global setting: <i><b>status_interval = number</b></i>.<br>
<font size="1">Default value: <i>1</i>.</font><br>
If statistics function is enabled and <i>stats</i> directory is defined, smsd writes file named <b><i>status</i></b> into this directory.
The file contains status of all modems in the first line using <i>Status:</i> header (this is similar than smsd -s outputs to console) and
explained status in the next lines using modem's name as a header.
Smsd writes status file every <i>status_interval</i> seconds if a status has changed. Value 0 disables this feature.
<p>
For example, the output is like:
<pre>
Status: 09-05-27 20:46:17, irir------------
SONERA: 09-05-27 20:46:09, Idle, 123, 0, 321, ssi: -63 dBm, ber: < 0.2 %
ELISA: 09-05-27 20:46:12, Receiving, 234, 0, 432, ssi: -73 dBm, ber: < 0.2 %
DNA: 09-05-27 20:46:06, Idle, 456, 0, 543, ssi: -77 dBm, ber: < 0.2 %
SAUNALAHTI: 09-05-27 20:46:14, Receiving, 678, 0, 654, ssi: -69 dBm, ber: < 0.2 %
</pre>
</p><p>
Timestamp value tells when status is created or modem initialization was last started.
</p><p>
Status can be: (s) Sending, (r) Receiving, (i) Idle, (b) Blocked, (t) Trouble, (-) Unknown.
Trouble -status means that something abnormal has happened and if smart_logging is in use, trouble log will be written.
</p><p>
Counters are: sent, failed, received.
Sent counter is the value from <i>stats/<modemname>.counter</i> file. Smsd does not clear this value.
Failed and received counters are from original statistics data and they are cleared each time when stats are stored (<i>stats_interval</i>), or smsd is restarted.
</p>
</p></li>
<li><p>
New global and modem settings:<br>
<i><b>status_include_counters = yes/no</b></i><br>
<font size="1">Default value: <i>yes</i>.</font><br>
<i><b>status_signal_quality = yes/no</b></i><br>
<font size="1">Default value: <i>yes</i>.</font><br>
Modem setting overrides global setting.
These settings define if message counters and explained signal quality is included in the line of <i>status</i> file.
</p></li>
<li><p>
New global and modem setting:<br>
<i><b>max_continuous_sending = number</b></i><br>
<font size="1">Default value: <i>300 (5 min)</i>.</font><br>
As usual, modem setting overrides global setting.
This setting is in seconds and defines how long modem can send messages without doing anything else.
After <i>max_continuous_sending</i> time is reached, received messages are checked and other tasks are run.
</p></li>
<li><p>
Number of modems can be defined in the <b>src/Makefile</b>. Default value is 64.
If you are running SMSTools3 in an embedded device, you can use <i>NUMBER_OF_MODEMS=1</i> to save memory.
This setting also affects the number of provider queues.
If you need more provider queues than you have modems, just increase the number of modems value.
</p></li>
<li><p>
Modem setting <i>init2</i> can be used to monitor signal quality.
When init2 contains AT+CSQ (uppercase), signal quality is explained in the log file using log level "notice".
</p></li>
<li><p>
If shared memory is not in use, global setting <i>stats_no_zeroes</i> defaults to <i>yes</i>.
</p></li>
<li><p>
Error message after PDU was sent is changed:
Previously: "The modem said ERROR or did not answer.".
Now: "The modem did not answer (expected OK)." or "The modem answer was not OK: <the answer what it was>" depending on the answer.
This change is because in some cases it's important to see if there was any answer or not.
</p></li>
<li><p>
IMSI (International Mobile Subscriber Identity) is now logged with log level "notice".
If AT+CIMI query was supported, Product Serial Number is also logged (CGSN).
</p></li>
<li><p>
Modem setting <i><b>voicecall_hangup_ath</b></i> is now global too.
</p></li>
<li><p>
Modem setting <i>queues</i> can be defined using special keyword <b>modemname</b> which is replaced with a name of modem.
</p></li>
<li><p>
New section in configuration file: <b>[default]</b>.
This section can be used to define default settings for all modems.
If setup has large count of similar modems, almost all settings can be defined once in [default] section and only device depended
settings like <i>device</i> are required to define in the modem sections.
In the future versions this will replace all modem settings which are now defined in the global part of configuration.
</p><p>
As "default" is now reserved name, it cannot be used as a modem name.
</p>
</p></li>
</ol>
<p>
Bug fixes:
<ol start="16">
<li><p>
Smsd did not compile on old GCC because two variables were defined elsewhere than begin of a block.
</p></li>
<li><p>
When logged to syslog, modem processes missed the correct program name.
Now the program name is always <i>smsd</i> and in addition, <i>MAINPROCESS:</i> title is included in the lines which are from the main process.
</p></li>
<li><p>
During the startup check, smsd used file mode 0600 when checking directories.
In Cygwin this was not enough when mode 0666 was inherited and directories were 0755.
For testing smsd uses now the same mode which is later used to create message files.
</p></li>
</ol>
</p>
<hr>
<p>
<b>11.05.2009 3.1.5beta9</b>
</p>
<ol>
<li><p>
Maximum number of provider queues is increased to 64 which is the same as maximum number of modems.
</p></li>
<li><p>
New setting for a modem: <i><b>voicecall_ignore_modem_response = yes/no</b></i>.<br>
<font size="1">Default value: <i>no</i>.</font><br>
When a voicecall is ringing, some devices give OK answer after couple of seconds even if a call is not yet answered.
With this kind of device DTMF tones cannot be sent.
If a ringing time is defined in the message file (using <b>TIME: n</b>), the waiting loop is breaked too soon.
To avoid this, use <i>voicecall_ignore_modem_response = yes</i> in the modem settings.
With this setting call rings n seconds (if not answered) and after this voicecall is over.
</p></li>
<li><p>
New setting for a modem: <i><b>voicecall_hangup_ath = yes/no</b></i>.<br>
<font size="1">Default value: <i>no</i>.</font><br>
Defines if <b>ATH</b> is used to hangup call instead of <b>AT+CHUP</b>.
</p></li>
</ol>
<p>
Bug fixes:
<ol start="4">
<li><p>
When PDU had no sender address included, decoding failed with an error message "Invalid sender address length: 00".
</p></li>
</ol>
</p>
<p>
<b>05.04.2009 3.1.5beta8</b>
</p>
<ol>
<li><p>
New setting for a modem: <i><b>detect_unexpected_input = yes/no</b></i><br>
<font size="1">Default value: <i>yes</i>.</font><br>
Before any command is sent to the modem, smsd checks if there is some unexpected input.
For example some modem may send new message identification (CMTI) if settings are incorrect.
Any unexpected input will be logged.
</p></li>
</ol>
<p>
<b>31.03.2009 3.1.5beta7</b>
</p>
<ol>
<li><p>
If signal quality is asked from a modem (when initializing it or when running a regular_run),
the result is explained in the log file.<br>
For example:
<pre>
2009-03-17 12:40:05,5, GSM1: CMD: AT+CSQ: +CSQ: 20,0 OK
2009-03-17 12:40:05,5, GSM1: Signal Strength Indicator: -73 dBm,
Bit Error Rate: less than 0.2 %
</pre>
</p></li>
<li><p>
New setting for a modem: <i><b>detect_message_routing = yes/no</b></i><br>
<font size="1">Default value: <i>yes</i>.</font><br>
By default smsd tries to detect if a modem is in message routing mode.
Before sending a command smsd listens if some data with routed message is available.
Also, after a command is sent, smsd checks the answer.
In both cases, if there is one or more routed message coming, a notification is written to the log and alarmhandler is called.
Routed messages are saved and handled later when smsd can do it.
<p>
NOTE: This checking is done to avoid errors and loss of messages.
Routing mode SHOULD NOT BE USED in normal operation.
With routing mode it is NOT quaranteed that all messages are delivered.
Some devices are in routing mode by default and this feature helps to detect it.
Use <i>init = AT+CNMI=...</i> with suitable values to disable routing mode.
Values depend on modem, see the manual of a modem for details.
All received messages must be stored to the message store which is usually "SM" (SIM card memory).
</p>
</p></li>
<li><p>New global setting: <i><b>shell = filename</b></i>.<br>
<font size="1">Default value: <i>/bin/sh</i>.</font><br>
Defines which shell is used to run eventhandler and other external scripts.
<p>
During the startup check it is now verified that the shell is accessible and it works.
Runtime errors are now logged with details.
</p>
</p></li>
<li><p>
If running of eventhandler or regular_run fails, an administrative alert is sent (if <i>admin_to</i> is specified).
Each process has it's own error status and while the error remains, no more messages are sent unless the problem is first solved.
</p></li>
<li><p>New global setting: <i><b>adminmessage_device = name</b></i>.<br>
<font size="1">Default value: <i>first available device</i>.</font><br>
This settings defines which modem is used to send administrative messages when mainspooler detects some trouble.
</p></li>
<li><p>
New settings for a modem:<br>
<i><b>adminmessage_limit = number</b></i><br>
<font size="1">Default value: 0.</font><br>
<i><b>adminmessage_count_clear = number</b></i><br>
<font size="1">Default value: 0.</font><br>
With these settings sending of administrative messsages can be limited.
<i>adminmessage_limit</i>, defines a maximum number of messages to be sent.
<i>adminmessage_count_clear</i> defines a period to automatically clear the message counter.
This value is number of minutes.
</p></li>
<li><p>
Timeout for message sending is increased.
If your modem still gets timeout, use a modem setting <i>read_timeout = 10</i> to increase value even more.
</p></li>
<li><p>
USSD messages using regular run for a modem feature: You can use a <i>regular_run_cmd</i> = <b>AT+CUSD=1,"*100#",0;</b> to get saldo details of a prepaid SIM.
When a command starts with AT+CUSD and the length is more than 9 characters, smsd will wait response which starts with <b>+CUSD:</b> instead of OK string.
For example in Finland the response in the log file will be like (here split into three lines):
<pre>
2009-03-30 11:56:00,5, GSM1: CMD: AT+CUSD=1,"*100#",0;:
OK +CUSD: 2,"Liittymsi saldo on 35.95 EUR ja
voimassaoloaika pttyy 27.07.2009.",15
</pre>
</p></li>
<li><p>
Sample script sendsms now checks if an user "smsd" is existing, and if it is, ownership of an outgoing file is given to the user "smsd".
If you are using some else unpriviledged user to run smsd, change the script variable "smsd_user".
</p></li>
</ol>
<p>
<b>15.03.2009 3.1.5beta6</b>
</p>
<ol>
<li><p>
New global settings:<br>
<i><b>ic_purge_hours = number</b></i><br>
<font size="1">Default value: 24.</font><br>
<i><b>ic_purge_minutes = number</b></i><br>
<font size="1">Default value: 0.</font><br>
<i><b>ic_purge_read = yes/no</b></i><br>
<font size="1">Default value: yes.</font><br>
<i><b>ic_purge_interval = number</b></i><br>
<font size="1">Default value: 30.</font><br>
These settings defines how concatenation storage is purged when <i>internal_combine</i> is used
and messages with missing parts are received.
Storage is checked every <i>ic_purge_interval</i> minutes.
If there are message parts older than defined with <i>ic_purge_hours</i> and/or <i>ic_purge_minutes</i> settings,
message parts are deleted. If <i>ic_purge_read</i> is <i>yes</i>, message is stored to the incoming folder.
In this case there will be only one part in the file and a header <i>Incomplete: yes</i> indicates that message is broken.
Value 0 for both <i>ic_purge_hours</i> and <i>ic_purge_minutes</i> disables this feature.
</p></li>
<li><p>
New settings for a modem:<br>
<i><b>ms_purge_hours = number</b></i><br>
<font size="1">Default value: 6.</font><br>
<i><b>ms_purge_minutes = number</b></i><br>
<font size="1">Default value: 0.</font><br>
<i><b>ms_purge_read = yes/no</b></i><br>
<font size="1">Default value: yes.</font><br>
These settings are used only with SIM600 (or compatible) modems (<i>check_memory_method</i> 5).
If multipart message is received with one or more parts missing, incomplete message is removed from the message storage after time defined.
Time is calculated from timestamp of first available part.
Value 0 for both settings disables this feature.
Setting <i>ms_purge_read</i> defines if parts are read before they are deleted.
If <i>internal_combine</i> setting is used, parts are stored to the concatenation storage.
If missing part(s) are later received, there will be similar timeout before parts are purged.
After this the messsage is complete and is stored to the incoming folder.
</p></li>
<li><p>
New setting for a modem: <i><b>read_timeout = number</b></i>.<br>
<font size="1">Default value: <i>5</i>.</font><br>
When smsd reads data from a modem, timeout will occur after <i>read_timeout</i> seconds if an acceptable answer is not received.
Some very slow devices might need greater value than 5 seconds.
</p></li>
<li><p>
A modem setting <i>check_network</i> is enhanced. Possible values are:<br>
<table border=1 bgcolor=lightgrey>
<tr><td bgcolor=yellow valign=top> 0<br> no </td><td>Network registration is not checked.</td></tr>
<tr><td bgcolor=yellow valign=top> 1<br> yes </td><td>Network registration is always checked</td></tr>
<tr><td bgcolor=yellow valign=top> 2 </td><td>Network registration is checked only when preparing to send messages.</td></tr>
</table>
<p>
Default value is 1. If a modem does not support network checking, checking is automatically ignored.<br>
With value 2 incoming messages are processed faster.
</p>
</p></li>
</ol>
<p>
<b>11.03.2009 3.1.5beta5</b>
</p>
<ol>
<li><p>
New value for <i>check_memory_method</i>: 5 = CMGL list is used and messages are handled with SIMCOM SIM600 compatible way:
Multipart message is handled after all of it's parts are available.
After multipart message is handled, only the first part is deleted by the smsd.
The modem will delete rest parts by itself.
</p></li>
<li><p>
New global and modem settings: <i><b>priviledged_numbers = list of numbers</b></i><br>
<font size="1">Default values: <i>not in use</i>.</font><br>
These lists can be used with <i>check_memory_method</i> values 31, 41, and 5.
If a modem setting is defined, it overrides global setting which is default for each modem.
List can be comma delimited list of numbers or their parts starting from the left.
Maximum 25 priviledged numbers can be defined.
When messages are received, messages from priviledged numbers are handled first.
First number in the list has highest priority.
</p></p>
</ol>
<p>
<b>09.03.2009 3.1.5beta4</b>
</p>
<ol>
<li><p>New global settings: <i><b>international_prefixes = value(s)</b></i><br>
and: <i>national_prefixes = value(s)</i>.<br>
<font size="1">Default values: <i>not in use</i>.</font><br>
Can be used for automated Type Of Address selection.<br>
See <a href="fileformat.html">SMS file</a> (Using Type Of Address selection) for details.
</p></li>
<li><p>New header: <i><b>To_TOA: value</b></i>.
Can be used for Type Of Address setting. Possible values are <i>unknown</i>, <i>international</i> and <i>national</i>.<br>
See <a href="fileformat.html">SMS file</a> for details.
</p></li>
<li><p>
If character set conversion <i>incoming_utf8</i> is used, a header <i>Alphabet: UTF-8</i> is written to the incoming message file.
</p></li>
<li><p>
The script <i>sendsms</i> is enhanced: it now accepts multiple destination numbers.
While used from the command line, last argument is taken as a text and all other arguments as numbers.
In Debian based distribution scripts can be found from the /usr/share/doc/smstools/<b>examples</b>/scripts/ directory.
</p></li>
<li><p>
A function tempnam is not used anymore.
It is removed because of a compiler warning which said that "using is dangerous".
However, it was used safely but compiler did not know it :).
Now there are no any warnings while compiling smstools3.
NOTE that after this change there must be /tmp directory available in the system.
</p></li>
<li><p>
Baud rate 460800 is now supported. All other possible rates are supported too.
Default baudrate is now 115200 which is good value for many old modems too.
</p></li>
<li><p>
The smsd main process checks periodically if it's own pid is still in the pidfile.
If it's not, it means that another smsd was started and it's illegal to run more than one daemon at once.
To avoid problems, all other than latest smsd will stop with logfile and alarmhandler notice.
Usually this kind of usage happens in testing, in productive environments <b>init.d/sms3 script should always be used to start and stop the smsd</b>.
<p>
Update: 3.1.5beta7: this checking is not done in Cygwin, when <i>os_cygwin = yes</i> is defined.
This is beacause Windows locks serial ports and another modem process will not start.
</p>
</p></li>
<li><p>New global setting: <i><b>keep_messages = yes/no</b></i>.<br>
<font size="1">Default value: <i>no</i>.</font><br>
This is for testing purposes. Smsd runs as usual but messages are not removeed from the modem.
After all messages are read, smsd will stop. Use this with one modem only.
</p></li>
<li><p>
New value for <i>check_memory_method</i>: 4 = CMGL list is used and messages are deleted after all messages are read.
There is also some more new values, see the <a href="configure.html">How to configure</a> for details.
</p></li>
<li><p>
Default <i>cmgl_value</i> is <i>4</i> which is good for most modems.
</p></li>
<li><p>
New global and modem setting: <i><b>internal_combine_binary = no</b></i>.
In this version all multipart messages including binary messages are combined internally.
Setting <i>internal_combine</i> now defaults to <i>yes</i>.
When a binary message is combined, UDH is removed from the message body and it's shown as a header line.
</p></li>
</ol>
<p>
Bug fixes:
<ol start="12">
<li><p>
While retrieving identification from device, if IMSI was not supported, CGSN was not tried because ERROR text was removed incorrectly.
</p></li>
<li><p>
Phonecall reading freezed process if there was incorrect syntax (broken answer) from a modem.
</p></li>
</ol>
</p>
<p>
<b>16.02.2009 3.1.5beta3</b>
</p>
<ol>
<li><p>
When a modem is first time initialized, support for reading of messages is checked.
If it looks like reading is not supported, a notice is written to the log and alarmhandler is called.
This is general issue with S60 based phones. See F.A.Q. for more details.
</o></li>
<li><p>
Log file size more than 2GB is now supported.
</p></li>
<li><p>
When sending or spooling is failed, "Failed: timestamp" header is printed to the message file.
</p></li>
</ol>
<p>
Bug fixes:
<ol start="4">
<li><p>
When a CMGL method (available from 3.1.5beta) was used to check incoming messages, there was a delay when modem did not have any messages.
<!--
<br><br>
Fix to resolve this issue:<br>
In the smsd.c, if you search a string \\+CMGL: you can locate a line:<br>
<i>put_command(modem, devices[device].name,devices[device].send_delay, tmp, answer, sizeof(answer), 50, <b>"(\\+CMGL:.*OK)|(ERROR)"</b>);</i><br>
Change the last argument to <b>"(OK)|(ERROR)"</b>.
-->
</p></li>
</ol>
</p>
<p>
<b>03.02.2009 3.1.5beta2</b>
</p>
<ol>
<li><p>
Modem setting <i>send_delay = number</i> has slightly enhanced:<br>
Value 0 now means that whole string is sent at once without any delays.
This resolves slow communication with LAN based multiport servers, like Digi Portserver II.
If, for some reason, "tcdrain" is still needed after sending, use value -1.
</p></li>
</ol>
<p>
<b>30.11.2008 3.1.5beta</b>
</p>
<ol>
<li><p>
New setting for a modem: <i><b>number = string</b></i>.<br>
<font size="1">Default value: empty.</font><br>
SIM card's telephone number. If not empty, it is stored to the message files using header "<i>Number:</i>".
</p></li>
<li><p>New global setting: <i><b>delaytime_mainprocess = number</b></i>.<br>
<font size="1">Default value: <i>not in use</i>.</font><br>
If this value is not set, <i>delaytime</i> setting is used in the main process.
With this setting outgoing messages can be checked more frequently than incoming messages.
</p></li>
<li><p>
<i>HDR_Modem</i> header is printed to incoming messages too.
There is still <i>HDR_Subject</i> header presented for backward compatibility.
</p></li>
<li><p>
New command line argument: <i>MAINPROCESS</i>.
Each modem process will change this with it's own name.
With long modem names underscores like <i>MAINPROCESS___</i> can be used.
</p></li>
<li><p>
Failure with network registration will stop the modem process only if SIM was never registered successfully.
</p></li>
<li><p>
Phonecalls are read even if incoming messages are not read.
</p></li>
<li><p>
Configuration file: Only whole line comments are now allowed. For example:<br>
<i># This comment line is valid.</i><br>
<i>devices = GSM1 # This kind of comment is invalid.</i><br>
</p></li>
<li><p>
Queue directory definitions are checked. If there is similar typed definition for more than one queue, it's reported and smsd does not start.
</p></li>
<li><p>
New setting for a modem: <i><b>check_memory_method = number</b></i><br>
<font size="1">Default value: <i>1</i>.</font><br>
Defines how incoming messages are checked:<br>
<table border=1 bgcolor=lightgrey>
<tr><td bgcolor=yellow valign=top> 0 </td><td>CPMS is not supported. Default values are used for <i>used_memory</i> and <i>max_memory</i>.</td></tr>
<tr><td bgcolor=yellow valign=top> 1 </td><td>CPMS is supported and must work. In case of failure incoming messages are not read.</td></tr>
<tr><td bgcolor=yellow valign=top> 2 </td><td>CMGD is used to check messages. Some devices does not support this.</td></tr>
<tr><td bgcolor=yellow valign=top> 3 </td><td>CMGL is used to check messages. Some devices are incompatible with this.</td></tr>
</table>
</p></li>
<li><p>
New setting for a modem: <i><b>cmgl_value = string</b></i><br>
<font size="1">Default value: <i>empty</i>.</font><br>
If <i>check_memory_method = 3</i> is used, correct value for AT+CMGL= command must be defined. This value depends on the modem.
</p></li>
</ol>
<p>
Bug fixes:
<ol start="11">
<li><p>
Filename preview for sent and failed files was generated using GMS alphabet version of a message text.
Because of this, skandinavian characters were not recognized and underscore was used. This is fixed.
</p></li>
<li><p>
When SMSC: was set in the message file, this caused an infinite loop.
</p></li>
</ol>
</p>
<hr>
<p>
<b>11.08.2008 3.1.3</b>
</p>
<ol>
<li><p>
New setting for a modem: <i><b>voicecall_vts_list = yes/no</b></i>.<br>
<font size="1">Default value: <i>no</i>.</font><br>
Defines how VTS command is used to create DTMF tones:
<i>yes</i> = AT+VTS=1,2,3,4,5 (list is used), <i>no</i> = each tone is created with single command like AT+VTS="1";+VTS="2" etc.
</p></li>
</ol>
<p>
Security fix:
<ol start="2">
<li><p>
Tone definition string used to make a voicecall was not checked and it was possible to send user entered AT commands to the modem.
</p></li>
</ol>
</p>
<hr>
<p>
<b>10.08.2008 3.1.2</b>
</p>
<p>
Bug fixes:
<ol start="1">
<li><p>
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.
</p></li>
</ol>
</p>
<hr>
<p>
<b>06.08.2008 3.1.1</b>
</p>
<ol>
<li><p>
New setting for a modem: <i><b>messageids = number</b></i>.<br>
<font size="1">Default value: <i>2</i>.</font><br>
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.
</p></li>
<li><p>
Destination number can have minus characters, like <i>358-40-111 2222</i>.
</p></li>
<li><p>
If a modem is used for sending only, it is initialized when a device spooler is started.
</p></li>
<li><p>
Filename preview is applied for sent and failed files too.
</p></li>
<li><p>
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.
</p></li>
<li><p>New global setting: <i><b>executable_check = yes/no</b></i>.<br>
<font size="1">Default value: <i>yes</i>.</font><br>
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 <i>eventhandler = /usr/local/bin/php -f /usr/local/bin/smsd_eventhandler.php</i>,
the check will fail and smsd will not start unless <i>executable_check = no</i> is defined.
</p></li>
<li><p>
If stats directory is defined, smsd will store and update message counter files in this directory.
</p></li>
<li><p>
If a file which is failed to send is empty, it's deleted even if there is failed folder defined.
</p></li>
<li><p>
While checking the network registration, result 3 (registration denied) will stop the modem process after two retries.
</p></li>
<li><p>
PIN handling is slightly improved.
If a modem needs PIN, but there is no PIN defined in the configuration file, the process will stop.
</p></li>
<li><p>
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.
</p></li>
</ol>
<p>
Bug fixes:
<ol start="12">
<li><p>
While reading PDU string from file and directory was defined for <i>pdu_from_file</i> 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".
</p></li>
</ol>
</p>
<hr>
<p>
<b>11.05.2008 3.1</b>
</p>
<p>
General:
<ol>
<li><p>
While running as an unpriviledged user, outgoing files which are not writable for smsd are re-created to fix the permissions.
</p></li>
<li><p>
In the log, a process id is now included in the "started" message.
</p></li>
<li><p>
Message sending time (how long it took) is logged. Some other changes and enhancements is also applied to the logging.
</p></li>
</ol>
</p>
<p>
Outgoing message file:
<ol start="4">
<li><p>Binary message can now have UDH-DATA defined.
</p></li>
<li><p>New header: <i><b>System_message: yes</b></i>.
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.
</p></li>
</ol>
</p>
<p>
Incoming message file:
<ol start="5">
<li><p>New header: <i><b>Flash: yes</b></i>.
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.
</p></li>
</ol>
</p>
<p>
Configuration file (smsd.conf):
<ol start="6">
<li><p>New global setting: <i><b>date_filename = number</b></i>.<br>
<font size="1">Default value: 0.</font><br>
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.
</p></li>
<li><p>Baudrate 4800 is now supported.
</p></li>
<li><p>New global setting: <i><b>log_single_lines = yes/no</b></i>.<br>
<font size="1">Default value: yes.</font><br>
Linefeeds are removed from the modem response.
</p></li>
<li><p>New setting for a modem: <i><b>check_network = yes/no</b></i>.<br>
<font size="1">Default value: yes.</font><br>
Network checking can be disabled if it's known that a device cannot support it.
</p></li>
<li><p>New settings for a modem: <i><b>logfile</b></i> and <i><b>loglevel</b></i>.<br>
<font size="1">Default value: empty.</font><br>
Each modem can now have it's own logfile and loglevel setting.
If <i>logfile</i> is not defined, global log is used.
</p></li>
</ol>
</p>
<hr>
<p>
<b>15.08.2007 3.1beta7</b>
</p>
<p>
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.
</p>
<p>
Configuration file (smsd.conf):
<ol>
<li><p>New global setting: <i><b>saved = directory</b></i>.<br>
<font size="1">Default value: empty.</font><br>
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.
</p></li>
<li><p>New global setting: <i><b>phonecalls = directory</b></i>.<br>
<font size="1">Default value: empty.</font><br>
If defined and reporting of phonecalls is used, message files are store to this directory
instead of incoming directory.
</p></li>
<li><p>New setting for a modem: <i><b>phonecalls = yes/no</b></i>.<br>
<font size="1">Default value: no.</font><br>
Report phonecalls. Currently only missed calls are reported.<br>
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.
</p></li>
<li><p>New global setting: <i><b>language_file = filename</b></i>.<br>
<font size="1">Default value: empty.</font><br>
Message files can be written using localized headers.
See the <a href="localizing.html">localizing</a> for details.
</p></li>
<li><p>New setting for a modem: <i><b>keep_open = yes/no</b></i>.<br>
<font size="1">Default value: yes</font><br>
If this is changed to <i>no</i>, a modem is closed while it's not used.
</p></li>
<li><p>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 <a href="configure.html">How to configure</a> for details.
</p></li>
<li><p>New global setting: <i><b>datetime = format string</b></i>.<br>
<font size="1">Default value: compatible with previous versions of smsd.</font><br>
</p></li>
<li><p>Defining loglevels and alarmlevel, can use string value like LOG_NOTICE or "notice".
</p></li>
<li><p>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.
</p></li>
<li><p>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.
</p></li>
<li><p>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.
</p></li>
<li><p>Device names are checked. Only alphanumeric characters, underline, minus-sign and dot are allowed.
</p></li>
<li><p>All errors are reported, not just the first one found.
</p></li>
<li><p>Numbers for the provider sorting can be given in the grouped format. (3.1beta4).
</p></li>
<li><p>New global setting <i><b>report = directory</b></i>.
This can be used to define where status report files are stored.
By default they are stored to the Incoming Folder. (3.1beta3).
</p></li>
<li><p>New global settings: <i><b>keep_filename</b></i> and <i></b>store_original_filename</b></i> to select file naming convention
when files are moved between directories. (3.1beta).
</p></li>
<li><p>New global settings: <i><b>regular_run = filename</b></i> and <i><b>regular_run_interval = number</b></i>.
It is possible to define an external script or program which is executed regularly within a given interval.
See an usage sample on <a href="run.html">How to run/use</a>. (3.1beta).
</p></li>
<li><p>Whitelist can specify a queue to be used with a list of numbers. See <a href="blacklist.html">more details</a>. (3.1beta).
</p></li>
<li><p>New global setting: <i><b>admin_to</b></i>, destination number for administrative messages.
Messages are sent without using the filesystem. (3.1beta).
</p></li>
<li><p>New modem settings: <i><b>message_limit</b></i>, defines a maximum number of messages to be sent. <i>message_count_clear</i> defines
a period to automatically clear the message counter. This value is number of minutes. (3.1beta).
</p></li>
<li><p>New global setting: <i><b>filename_preview = number</b></i>. Defines how many characters of message text is concatenated
to the name of messsage file. Currently works with incoming message files. (3.1beta).
</p></li>
</ol>
</p>
<p>
Outgoing message file:
<ol start="22">
<li><p>New header: <i><b>Include: filename</b></i>.
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.
</p></li>
<li><p>New header: <i><b>Macro: definition</b></i>.
Works like macros usually do.
See the <a href="fileformat.html">SMS file format</a> for details.
</p></li>
<li><p>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.
</p></li>
<li><p>Unicode messages can now have part numbering as text (Autosplit: 2).
</p></li>
<li><p>Priority: HIGH accepted case insensitive, all which means "yes" is accepted too (including localized strings).
</p></li>
<li><p>Voicecall can now have <i><b>TIME: number</b></i> 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.
</p></li>
<li><p><i>To: </i> number is accepted in the grouped format, like <i>358 12 345 6789</i>.
The number can also contain * and # character(s). (3.1beta3).
</p></li>
<li><p>While smsd reads the message, all string length's are checked to prevent possible buffer overflows. (3.1beta).
</p></li>
</ol>
</p>
<p>
Incoming message file:
<ol start="30">
<li><p>New header: <i><b>Length: number</b></i>.
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.
</p></li>
</ol>
</p>
<p>
General:
<ol start="31">
<li><p>While retrieving identification from device, CGSN is tried if IMSI is not supported.
</p></li>
<li><p>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".
</p></li>
<li><p>Incoming PDU checking: content of a broken PDU is shown as much as possible.
</p></li>
<li><p>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 <i>-C devicename</i>,
for example <i><b>smsd -C GSM1</b></i>.
This runs smsd in terminal mode which can be breaked with Ctrl-C. (3.1beta3).
</p></li>
<li><p>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).
</p></li>
<li><p>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).
</p></li>
<li><p>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).
</p></li>
<li><p>When the modem is initialized and modem answers ERROR to some command, an <i>errorsleeptime</i> 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).
</p></li>
<li><p>Concatenated id start's from the random value between 1 ... 255. (3.1beta).
</p></li>
<li><p>Modem is blocked only if sending has failed because of a modem related reason. (3.1beta).
</p></li>
<li><p>"SMS sent" log information includes a message id and part information (while sending multipart messsages). (3.1beta).
</p></li>
<li><p>Status report log information includes a message id and status value. (3.1beta).
</p></li>
</ol>
</p>
<p>
Bug fixes:
<ol start="43">
<li><p>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.
</p></li>
</ol>
</p>
<hr>
<p>
<b>18.07.2007 3.0.10</b>
</p>
<p>
Configuration file (smsd.conf):
<ol>
<li><p>New global setting: <i><b>os_cygwin = yes/no</b></i>.
Default value is <i>no</i>.
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.
</p></li>
</ol>
</p>
<p>
Bug fixes:
<ol start="2">
<li><p>Command line argument <i>-t</i> had no effect.
This <i>terminal</i> mode is useful when running smsd under Cygwin as a Windows service as it prevents one error message.
</p></li>
<li><p>In QNX, the OS libraries include already an unlock() function, causing a name conflict.
The unlock() function of smsd is therefore renamed.
</p></li>
</ol>
</p>
<hr>
<p>
<b>06.07.2007 3.0.9</b>
</p>
<p>
General:
<ol>
<li><p>Minor changes to the PDU checking.
<ul>
<li>An incorrect sender number produces only a warning.
</li>
<li>It now shows error position in the message file.
</li>
<li>All possible data is checked (unused too) to detect invalid characters and a broken and/or incompatible PDU.
</li>
</ul>
</p></li>
<li><p><i>Replace:</i> usage is ignored while sending multipart message.
</p></li>
<li><p>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).<br>
The smsd does not send 0x24 while messages are written using ISO/UTF-8 character set.
</p></li>
<li><p>Documentation is updated. Sample configuration files are not,
see the <a href="configure.html">How to configure</a> for details of new features.
</p></li>
</ol>
</p>
<p>
<b>NOTE</b> for users running smsd with very heavy load:
<ul>Current version of smsd moves files between spooler directories using the original file name.
If outgoing files are created using a fixed filename (which is not recommended) and lot of
files using the same name are created within a short period, it's possible that previous file
and it's .LOCK file are still existing in the spooler directory. In this case a new file cannot
be moved to the spool. Previously the smsd stopped with a fatal error in this case. Now an
alarmhandler is called and after it has returned a file moving is retried. If a file still
cannot be moved, the smsd will stop with a fatal error.<br>
<br>
The alarmhandler can be used to help with a file moving conflict. The script can wait until
a spooler can be used, or it can wait some fixed time like 5 seconds. It can also produce some
notices to the administration, if necessary.<br>
<br>
In some cases this kind of conflict is a result of a previously happened error in the system
which creates outgoing files to send. In this case it's better to let smsd stop, instead of
sending couple of thousand messages to somewhere...<br>
<br>
In the conflict case the alarmhandler will get following arguments (as an example):
<ul>
<li>$1=ALARM
</li>
<li>$2=2007-07-06
</li>
<li>$3=12:00:00
</li>
<li>$4=2
</li>
<li>$5=smsd
</li>
<li>$6=Conflict with .LOCK file in the spooler: /var/spool/sms/outgoing/test_file /var/spool/sms/checked
</li>
</ul>
</ul>
</p>
<p>
Thank's for all users who have provided feedback, idea's, code and fixes.
</p>
<hr>
<p>
<b>28.06.2007... 3.0.9beta2</b>
</p>
<p>
General:
<ol>
<li><p>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.
<ul>
<li>In case of errors a new header <i><b>Error: explanation</b></i> is printed to the message file.
With existense of this header it's easy to detect that there is no usual message content in the file.
Text part will tell more details of errors found.
</li>
<li>In the successfully processed message file there can be one or more <i>Warning: explanation</i> headers
telling that some minor issues has detected, but the message is still processed.
</li>
</ul>
</p></li>
<li><p>If an incoming PDU does not match to the <i>mode</i> 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.
</p></li>
<li><p>Number of devices is increased to 64.
</p></li>
<li><p>While reading a PDU from file, a first line starting with PDU: and space is taken if any exists.
</p></li>
<li><p>There is a simple script <i>smstest.php</i> 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.
</p></li>
<li><p>Installation / uninstallation: path of executables can now be defined in the Makefile.
</p></li>
<li><p>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.
</p></li>
<li><p>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:
<i><b>IMSI: 123456789</b></i>.
<br>
This header is also inserted to sent and failed files.
</p></li>
<li><p>Running as an unpriviledged user: if <i>user</i> is set but <i>group</i> 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.
</p></li>
<li><p>When finding files from the spooler directories, the oldest file is selected.
</p></li>
<li><p>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.
</p></li>
</ol>
</p>
<p>
Outgoing message file:
<ol start="12">
<li><p>New header: <i><b>Replace: code</b></i>. 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.<br>
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.
</p></li>
<li><p>SMSC setting is allowed only if there is a smsc set in the config file.
</p></li>
</ol>
</p>
<p>
Incoming message file:
<ol start="14">
<li><p>New header: <i><b>From_TOA: string</b></i>.
Includes a Type Of Address definition with short explanation,
like: "From_TOA: 91 international, ISDN/telephone".
</p></li>
<li><p>New header: <i><b>Report: yes/no</b></i>.
Tells if a status report is going to be returned to the SME.
</p></li>
<li><p>New header: <i><b>Replace: number</b></i>.
This header is included if a message has a Replace Short Message Type 1..7 (number) defined.
</p></li>
</ol>
</p>
<p>
Configuration file (smsd.conf):
<ol start="17">
<li><p>Setting: <i>pdu_from_file = filename / dirname/</i> 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.
</p></li>
<li><p>New setting: <i><b>log_charconv = yes/no</b></i>.
Default is <i>no</i>.
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.
</p></li>
<li><p>New setting for a modem: <i><b>modem_disabled = yes/no</b></i>.
Default is <i>no</i>.
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 <i>sending_disabled</i> setting.
Incoming messages are taken only from the file, if <i>pdu_from_file</i> 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 <i>device = /tmp/modemfile</i>.
If this file exists and is writable for the process owner, it's enough for smsd.
</p></li>
<li><p>Startup check will now report if there is a queue defined but no provider numbers for it.
</p></li>
<li><p>New global setting: <i><b>store_sent_pdu = value</b></i>.
Default is <i>1</i>.
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.
</p></li>
<li><p>Validity period setting now accepts keywords typed mixed/upcase.
Keyword can now be given without any numbers, like <i>month</i> means the same than <i>1 month</i>.
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.
</p></li>
<li><p>Each provider can now have up to 64 numbers defined.
</p></li>
<li><p>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.
</p></li>
<li><p><i>stats_interval</i> defaults to 3600 (1 hour).
</p></li>
<li><p>New setting: <i><b>blockafter = number</b></i>. Defines number of errors which will cause modem to be blocked. Default value is 3.
</p></li>
<li><p>New setting for a modem: <i><b>outgoing = yes/no</b></i>.
Default is <i>yes</i>.
If set to <i>no</i>, a modem does not handle any outgoing message(s).
</p></li>
</ol>
</p>
<p>
Bug fixes:
<ol start="28">
<li><p>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.
</p></li>
<li><p>When alphanumeric senders had length more than 9 characters, garbage was appended to the sender's name.
</p></li>
<li><p>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).
</p></li>
<li><p>SMSC setting in the message file did not work. However, usually this setting should not be used.
</p></li>
</ol>
</p>
<hr>
<p>
<b>20.06.2007 3.0.9beta</b>
</p>
<p>
Outgoing message file:
<ol>
<li><p>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.
</p></li>
</ol>
</p>
<p>
Configuration file (smsd.conf):
<ol start="2">
<li><p>New setting: <i><b>outgoing_utf8 = yes/no</b></i>.
Default is <i>yes</i>.
With this setting automatic UTF-8 to ISO conversion of outgoing files can be switched off, if necessary.
</p></li>
</ol>
</p>
<p>
Bug fixes:
<ol start="3">
<li><p>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).
</p></li>
</ol>
</p>
<hr>
<p>
<b>03.06.2007 3.0.8</b>
</p>
<p>
General:
<ol>
<li><p>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.
</p></li>
<li><p>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.
</p></li>
<li><p>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.
</p></li>
<li><p>When a message is sent successfully, possible previous errors with a modem are forgotten.
</p></li>
<li><p>Logging of character set conversation problems is changed from LOG_INFO to LOG_NOTICE.
Log lines have now name of a modem.
</p></li>
</ol>
</p>
<p>
Configuration file (smsd.conf):
<ol start="6">
<li><p>New setting: <i><b>incoming_utf8 = yes/no</b></i>.
Incoming message files with ISO or GSM alphabet can be saved using UTF-8 character set.
Default is <i>no</i>.
</p></li>
<li><p>If a modem needs some idle time after a PIN is entered, new setting <i><b>pinsleeptime</b></i> can be used to produce that.
This value is seconds.
</p></li>
<li><p>New setting for a modem: <i><b>pre_init = yes/no</b></i>.
This settting defaults to "yes" and causes "echo off" and "CMEE=1" commands to be sent to the modem
before anything else is done.
</p></li>
</ol>
</p>
<p>
Outgoing message file:
<ol start="9">
<li><p>When an alphabet is ISO or GSM, smsd can also read files stored using the UTF-8 character set.
</p></li>
<li><p>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.<br>
Please note that while creating a text part for message file, a coding UCS-2BE should be used (not UCS-2).
</p></li>
</ol>
</p>
<p>
Bug fixes:
<ol start="11">
<li><p>Storage for startup error strings was not initialized properly.
</p></li>
<li><p>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.
</p></li>
</ol>
</p>
<hr>
<p>
<b>18.05.2007 3.0.7</b>
</p>
<p>
General:
<ol>
<li><p>If smsd is compiled without a support for status monitor, command line option -s is not useable.
</p></li>
</ol>
</p>
<p>
Bug fixes:
<ol start="2">
<li><p>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.
</p></li>
</ol>
</p>
<hr>
<p>
<b>14.03.2007 3.0.6</b>
</p>
<p>
General:
<ol>
<li><p>New header <i><b>Modem: devicename</b></i> is automatically inserted to the SENT/FAILED message files.
</p></li>
<li><p><i>Message_id: n</i> and <i>Sent: timestamp</i> headers are inserted to the message file <b>before</b> eventhandler is executed.
</p></li>
</ol>
</p>
<hr>
<p>
<b>20.02.2007 3.0.5</b>
</p>
<p>
General:
<ol>
<li><p>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.
</p></li>
<li><p>If smsd is running on terminal (foreground), smsd shuts down when a terminal window is closed.
</p></li>
<li><p>Internal combine can now handle 16-bit message reference numbers too.
</p></li>
<li><p>Log line titles are now completely process based.
For example the "SMS received" message tells now which one process (=modem) received that SMS.
</p></li>
</ol>
</p>
<hr>
<p>
<b>22.01.2007 3.0.4</b>
</p>
<p>
Bug fixes:
<ol>
<li><p>Incoming PDU was not handled correctly when there was no SMSC information in the PDU string.<br>
Also note that in this case there will not be <b>From_SMSC:</b> field in the message file,
which should be notified by the event handler.
</p></li>
</ol>
</p>
<hr>
<p>
<b>11.01.2007 3.0.3</b>
</p>
<p>
<h4>The major change is done to daemonizing:</h4>
When smsd is started to background (which is default), it forks itself before running processes are created.
This solves some issues when the smsd is started from the sh shell.
</p>
<p>
It is no more necessary to use the & sign at the end of a starting command line.
</p>
<p>
There is a command line switch <b>-t</b> 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.
</p>
<p>
The start-stop script <b>sms3</b> is updated.
The smsd now removes possible <i>infofile</i> and <i>*.LOCK</i> files at startup,
it is no more necessary to take care of them in the script.<br>
New script can be used with most operating systems.
</p>
<p>
See more details on <a href="run.html">How to run/use</a>.</li>
</p>
<p>
General:
<ol>
<li><p>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 <b>checkhandler-utf-8</b> and <b>eventhandler-utf-8</b> in the scripts directory
to demonstrate how character set conversation can be made using checkhandler and eventhandler.
</p></li>
<li><p>While smsd reads the configuration, all string length's are checked to prevent possible buffer overflows.
</p></li>
<li><p>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.
</p></li>
<li><p>Lockfile is detected by finding ".LOCK" from the end of filename instead of the whole string.
</p></li>
<li><p>A logfile setting can be made using the command line argument <i>-l</i> (ell).
This overrides the config file setting.
</p></li>
<li><p>If received SMS is status report, log line starts with "SMS received (Report)".
</p></li>
<li><p>It's no more necessary to define <i>user=root</i> to get smsd running as a root.
</p></li>
</ol>
</p>
<p>
<b>NOTE for Windows users:</b> 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 <i>--neverexits</i> option should not be used anymore.
See more details on <a href="windows.html">instructions for Windows</a>.
</p>
<hr>
<p>
<b>30.11.2006 3.0.2</b>
</p>
<p>
General:
<ol>
<li><p>The smsd can be defined to run without root priviledges.
</p></li>
<li><p>System check is performed at startup to avoid some potential problems with permissions of directory structure
and some other settings.
</p></li>
<li><p>If a config file cannot be read, the smsd does not stay running.
</p></li>
<li><p>Only the process id of a main process is written to the pid file.
</p></li>
<li><p>Some code cleaning is done to avoid compiler warnings on Solaris 10 (6/06 x86) with gcc.
</p></li>
<li><p><i>mypath</i> setting is not used anymore.
</p></li>
</ol>
</p>
<p>
Configuration file (smsd.conf):
<ol start="7">
<li><p><i><b>user = username</b></i> and <i><b>group = groupname</b></i> settings to change priviledges for the smsd.
</p></li>
<li><p><i><b>infofile = filename</b></i> and <i><b>pidfile = filename</b></i> settings to change file locations,
needed when the smsd is not running as a root.
</p></li>
<br>
These settings can be overridden by the command line arguments.
<br>
See the <a href="configure.html">How to configure</a> for details and
<a href="run.html">How to run/use</a> for more details.
</ol>
</p>
<p>
Bug fixes:
<ol start="9">
<li>Sample script mysmsd did not read status report correctly while storing it to the MySQL database.
</li>
</ol>
</p>
<hr>
<p>
<b>14.11.2006 3.0.1</b>
</p>
<p>
General:
<ol>
<li><p>When syslog is used to logging, a modem name is presented in the log line.
</p></li>
<li><p>Outgoing PDU: Data Coding Scheme uses message class bits only when message is sent as an alert (flash).
</p></li>
<li><p>Some code has 'cleaned' to avoid compiler warning messages.
</p></li>
</ol>
</p>
<p>
Bug fixes:
<ol start="4">
<li><p>Syslog call is now made using a format string.
</p></li>
<li><p>There was two compiler warnings (with gcc >= 4) because blacklist.c and whitelist.c missed prototypes of exit() function.
</p></li>
<li><p>Buffer used to store received PDU's was not initialized correctly.
This caused a runtime error while concatenating multipart messages on latest Ubuntu releases.
</p></li>
</ol>
</p>
<hr>
<p>
<b>02.11.2006 3.0</b>
</p>
<p>
Bug fixes:
<ol>
<li><p>Blacklist and Whitelist handling: fixed incorrect log message when the file was not readable.
Also fixed the program termination in those cases.
</p></li>
<li><p>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.
</p></li>
<li><p>While reading a configuration file there was stack misuse which caused device_list become empty while running on ubuntu 6.10.
</p></li>
</ol>
</p>
<hr>
<p>
<b>25.09.2006 3.0beta</b>
</p>
<p>
This version is based to the SMS Server Tools version 2.2.8.
</p>
<p>
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.
</p>
<h4>New features:</h4>
<p>
Configuration file (smsd.conf):
<ol>
<li><p>Received PDU's can be stored to the incoming message file. It's possible to select which kind of PDU's will be stored.
</p></li>
<li><p>Message validity time can be selected for default.
</p></li>
<li><p>Incoming Unicode message can be decoded internally.
</p></li>
<li><p>Incoming multipart message can be combined internally.
</p></li>
<li><p>Dual memory handler: it's possible to read messages from both memories (SIM and Mobile Equipment).
</p></li>
<li><p>Incoming PDU string can be read from the file. This is for testing purposes.
</p></li>
<li><p>Sending can be disabled. This is for testing purposes.
</p></li>
<br>
See the <a href="configure.html">How to configure</a> for more details.
</ol>
</p>
<p>
Outgoing message file:
<ol start="8">
<li><p>Priority can be set to high. This also works while the Provider Queue is used.
</p></li>
<li><p>Message validity time can be selected for the message.
</p></li>
<li><p>It's possible to make a voice call with DTMF tones.
</p></li>
<li><p>Binary messages can be presented as a Hex in the message file. There is a Wap Push demo using this feature.
</p></li>
<li><p>After a message is sent, <b>Message_id</b> is stored to the file if a status report was requested.
</p></li>
<br>
See the <a href="fileformat.html">SMS file format</a> for more details.
</ol>
</p>
<p>
General:
<ol start="13">
<li><p>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.
</p></li>
<li><p>If a modem reading reaches timeout, it will be reported to the log file.
</p></li>
<li><p>If for some reason the file moving fails, destination lock is removed.
</p></li>
<li><p>While creating a log file, file access permissions are limited to 640 (-rw-r-----).
</p></li>
<li><p>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.</b>
</p></li>
</ol>
</p>
<p>
Bug fixes:
<ol start="18">
<li><p>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.
</p></li>
<li><p>Short number preceeding with 's' caused number become empty and sending failed.
</p></li>
</ol>
</p>
<hr>
</body>
</html>
|
