README
1
2 UNIX SMS Client 3.0.2 by (c) 2014 portmaster - http://bsdforge.com
3 ==============================================================
4
5 Linux SMS Client 3.0.1 by (c) 1997,1998,1999,2000 Angelo Masci
6 ==============================================================
7
8
9A simple UNIX client Allowing you to send SMS messages to mobile phones
10and pagers. The software currently supports a number of providers
11and protocols:
12
13 +----------------------------------------------------------------------+
14 | Service Protocol Notes |
15 +----------------------------------------------------------------------+
16 | CELLNET TAP Supports multiple sends (see NOTE) |
17 | DETEMOBIL D1 TAP Supports multiple sends (see NOTE) |
18 | D2 UCP |
19 | EPLUS TAP Supports multiple sends (see NOTE) |
20 | AZCOM TAP Supports multiple sends (see NOTE) |
21 | CALLMAX TAP Supports multiple sends (see NOTE) |
22 | TELSTRA TAP Supports multiple sends (see NOTE) |
23 | VODAFONE proprietary UK/Australian Telenote services |
24 | VODAFONE_TAP TAP UK |
25 | ORANGE proprietary Supports multiple sends (see NOTE) |
26 | Includes Hutchinson Pagers |
27 | PAGEONE proprietary Supports multiple sends (see NOTE) |
28 | MINICALL PAGEONE Supports multiple sends (see NOTE) |
29 | ONE2ONE proprietary Supports multiple sends (see NOTE) |
30 | VODAPAGE proprietary Block Mode supported |
31 | VODACOM proprietary |
32 | PTT/KPN Telcom proprietary Supports multiple sends (see NOTE) |
33 | ANSWER proprietary |
34 | MTN proprietary |
35 | LIBERTEL proprietary Supports multiple sends (see NOTE) |
36 | TIM proprietary Supports multiple sends (see NOTE) |
37 | PROXIMUS proprietary |
38 | AMPI TAP |
39 | EUROPOLITAN CIMD Currently in ALPHA and testing |
40 | BTEASYREACH TAP Currently in ALPHA and testing |
41 | SWISSCOM UCP Currently in ALPHA and testing |
42 | TELENOR UCP Currently in ALPHA and testing |
43 | HELLO Currently in ALPHA and testing |
44 | VOICESTREAM TAP Currently in ALPHA and testing |
45 | TELECOM NZ TAP Currently in ALPHA and testing |
46 | SKYTEL TAP Currently in ALPHA and testing |
47 | TELECOM NZ TAP Currently in ALPHA and testing |
48 | TELIA UCP Currently in ALPHA and testing |
49 | NETCOM TAP Currently in ALPHA and testing |
50 | MOBISTAR UCP Currently in ALPHA and testing |
51 | EIRPAGE TAP Currently in ALPHA and testing |
52 +----------------------------------------------------------------------+
53 | CELLNET_WEB proprietary Currently in ALPHA and testing |
54 | ORANGE_WEB proprietary Currently in ALPHA and testing |
55 | PROXIMUS_WEB proprietary Currently in ALPHA and testing |
56 | ATT_WEB proprietary Currently in ALPHA and testing |
57 | NEXTEL_WEB proprietary Currently in ALPHA and testing |
58 | PAGENET_WEB proprietary Currently in ALPHA and testing |
59 | LYCOS_WEB proprietary Currently in ALPHA and testing |
60 +----------------------------------------------------------------------+
61 | SNPP* Currently in ALPHA and testing |
62 | GENERIC* Currently in ALPHA and testing |
63 +----------------------------------------------------------------------+
64
65Using an unlisted provider that allow TAP access should be quite straight
66forward.
67
68There are a large number of services that do not appear to use TAP
69but instead simple user interfaces for interactive use by a user dialing up
70with a modem. For several UK based services such as these I have written
71drivers, note that providers often offer more that one service and as such
72you may require a different driver for each one.
73
74NOTE - Services supporting 'multiple sends' allow the same message to
75 be sent to several recipients with only a single connection
76 having to be established, saving the cost of addition connection
77 charges.
78
79 It should be noted that ORANGE although allowing multiple
80 sends does seem to limit them to a maximum of 3 messages per
81 connection. Likewise, PTT/KPN Telcom has a limit of 2 messages
82 per connection.
83
84NOTE - Protocols marked '*' are using ALPHA version drivers.
85 SNPP support is limited as we don't currently have any SNPP
86 servers to connect to other than 'snppd'. The GENERIC driver
87 uses a script to connect to either modem based or tcp/ip based
88 servers, it's still early days for this driver but is
89 interesting to play with.
90
91
92SMS Client 2.0.7 can use the optional libmodem package written by
93Riccardo Facchetti. Prior to version 2.0.7 this package was a requirement
94to build and use the SMS Client. You can obtain it from sunsite.unc.edu in
95/pub/Linux/libs/ as libmodem-1.3.tar.gz
96
97NOTE - Prior to version 1.3 of libmodem a patch was required, this is no
98 longer the case. To use libmodem instead of the builtin modem
99 handling routines edit 'Makefile.config'
100
101
102To build the sms_client binary on Linux/Solaris:
103
104 sh configure
105 make ; make install
106
107
108NOTE - To build the sms_client binary under on a different Operating
109 System copy the appropriate 'Makefile.config.OS' file from the
110 config directory along with 'Makefile', rename the
111 'Makefile.config.OS' to 'Makefile.config' edit if necessary
112 and run 'make ; make install'
113
114
115
116Example using the SMS Client:
117
118 sms-client [SERVICE:]XXXXXXXX "Test Message 1" "Test Message 2" ...
119 | | |
120 | | +-- The message you
121 | | want to send
122 | | Maximum 150 Characters
123 | |
124 | +------------ Mobile or Pager ID
125 |
126 | For mobiles phones this is
127 | usually the telephone number,
128 | In some cases this must be
129 | written in international format.
130 | ie. For UK Numbers remove leading
131 | 0 and add 44 prefix
132 |
133 +---------------------- Optional SERVICE name
134
135
136You can use a simple address book file called sms_addressbook
137This is your global resource file, it should contain the name of
138your default service and possibly commonly used numbers. See the
139sms_addressbook file for examples. Any user can also create a local
140version of this file which should be placed in their home directory as
141.sms_addressbook The names are searched for in the user's local resource
142file and and finally the global resource file, this is so a user can
143override global names.
144
145The sms/sms_services file contains a list of services and the protocols
146that should be used when sending a message via that service.
147
148Each service must have a corresponding SERVICE file in sms/services,
149this file instructs the software which settings to use for the specified
150service, the service centre number to dial and additional comms parameters.
151A number of these service files exist and can be found in the sms/services
152directory.
153
154
155
156Configuring Drivers:
157You may want of modify the number of services that are supported
158by sms_client, you can do this simply by editing Makefile.config
159and adding or removing drivers from the DRIVERS line. You must then
160rebuild and install the sms_client binary. To obtain a list of drivers
161currently built into your binary simply type:
162
163 sms_client -d
164
165
166
167Writing Drivers:
168This is much more straight forward than you may think. Take a look
169at src/driver/skeleton.c for an example driver.
170
171
172
173Return Values:
174On error sms_client WILL return some useful error codes so that you can
175determine what went wrong. For each message sent you receive output
176in the form:
177
178 [ERROR] SERVICE:NUMBER "MESSAGE"
179
180The ERROR is set to 000 for successful delivery any positive value
181indicates there was a problem in delivery. See sms_error.h for description
182of values.
183
184If all messages were delivered successfully then sms_client returns 0
185any other value indcates one or more delivery problems occurred.
186
187
188
189Contributions:
190A New 'contrib' directory has been added which contains some useful
191scripts, at the moment we have:
192
193 mail2sms (Andy Hawkins) - perl script for forwarding E-Mail via sms.
194 www (David Usherwood) - WWW Frontend
195
196NOTE - These scripts were written for sms_client-2.0.5 and may not work
197 correctly with this version as I have not tested them.
198
199
200
201Credits:
202I would like to express my thanks to the following individuals for
203their help in testing, hardware, debugging, support and general
204feedback:
205
206 Mike Casella <mike@lines0.uwic.ac.uk>
207 Guy William Hayton <guy@hayton.demon.co.uk>
208 David Hill <dave@minnie.demon.co.uk>
209 Chris Voce <cvoce@rcsuk.com>
210 Frans Andersson <frans@concept.se>
211 Jonathan M. Hunter <jon@ninja.ml.org>
212 Geoff Peacock <geoff@ccmobile.com>
213 Harald Milz <hm@seneca.muc.de>
214 Job J. van Gorkum <JvGorkum@gbnetworks.com>
215 Nick Andrew <nick@gidora.zeta.org.au>
216 Jon Laughton <jon@eoin.demon.co.uk>
217 Michael Josephson <michael@josephson.org>
218 Dimitri Brukakis <dimitri.brukakis@omp.de>
219 Are Tysland <arety@dolphinics.no>
220 Petter Reinholdtsen <pere@td.org.uit.no>
221 Chris Berrington <chrisb@redac.co.uk>
222 Tim Ruehsen <TRuehsen@aol.com>
223 Gareth Abel <abelge@behp72.gpt.co.uk>
224 Jeff Duffy <jduffy@semcor.com>
225 Sergio Barresi <sbarresi@imispa.it>
226 matth <matth@labyrinth.net.au>
227 David Ockwell-Jenner <doj@nortelnetworks.com>
228 Chuck Hurd <hurd@hurd.is.ge.com>
229 Jonas Borgstrom <jonas_b@bitsmart.com>
230 Fredrik Bjork <Fredrik.Bjork.List@varbergenergi.se>
231 Alexander Grapenthin <a.grapenthin@sicomtec.de>
232
233
234 Contrib Credits:
235
236 Forward queries concerning 'mail2sms' perl script
237 to the author:
238
239 Andy Hawkins <andy@gently.demon.co.uk>
240
241 Forward queries concerning 'mail2sms' shell script
242 to the author:
243
244 Matt Foster <matt@molnir.demon.co.uk>
245
246 Forward queries concerning 'smsweb'
247 to the author:
248
249 David Usherwood <David_Usherwood@infocat.co.uk>
250
251
252 Driver Credits:
253
254 Forward queries concerning Australian Telenote service
255 using the VODAFONE driver to the patch contributor:
256
257 Jeremy Laidman <JLaidman@AUUG.org.au>
258
259 Forward queries concerning VODACOM and MTN
260 to the author:
261
262 Alf Stockton <stockton@fast.co.za>
263
264 Forward queries concerning VODAPAGE 'verbose'
265 to the author:
266
267 Neil A. Hillard <hillardn@gkn-whl.co.uk>
268
269 Forward queries concerning LIBERTEL
270 to the authors:
271
272 Henk Wevers <jhwevers@telekabel.nl>
273 Aart Koelewijn <aart@mtack.xs4all.nl>
274
275 Forward queries concerning TIM
276 to the authors:
277
278 Massimo Nuvoli <massimo@nuvoli.to.it>
279 <adrieder@sbox.tu-graz.ac.at>
280
281 Forward queries concerning PROXIMUS
282 to the author:
283
284 Mario Brackeva <mariob@jeeves.be>
285
286 Forward queries concerning AZCOM
287 to the contributor:
288
289 Brad Smith <brad@figint.com>
290
291 Forward queries concerning TELSTRA
292 to the contributor:
293
294 Paul Gampe <paulg@apnic.net>
295
296 Forward queries concerning PTT
297 to the contributor:
298
299 Harold Baur <bo@bikerider.com>
300
301 Forward queries concerning ANSWER
302 to the contributor:
303
304 Paul Andrew <PaulJ@Optimation.co.nz>
305
306 Forward queries concerning VSTREAM
307 to the contributor:
308
309 doughnut <doughnut@doughnut.net>
310
311 Forward queries concerning NZ
312 to the contributor:
313
314 Robbie Poharama <robbiep@sequent.com>
315
316 Forward queries concerning SKYTEL
317 to the contributor:
318
319 Kal Kolberg <Kal.Kolberg@BassHotels.com>
320
321 Forward queries concerning FREEBSD
322 to the contributor:
323
324 Nick Hibma <nick.hibma@jrc.it>
325
326 Forward queries concerning NETCOM
327 to the contributor:
328
329 Bjorn Rogeberg <bjornrg@a.sol.no>
330
331 Forward queries concerning RPM Packages
332 to the contributor:
333
334 Ross Golder <rossigee@bigfoot.com>
335
336 Forward queries concerning Debian Packages
337 to the contributor:
338
339 Michael Holzt <kju@flummi.de>
340
341 Forward queries concerning MOBISTAR
342 to the contributor:
343
344 <yves.seynaeve@eyc.be>
345
346Contact information:
347This Software is still considered BETA release. If you have any comments,
348problems, patches and improvements, please contact the author:
349
350 Angelo Masci <angelo@styx.demon.co.uk>
351
352
353WWW Sites:
354
355 http://www.styx.demon.co.uk/
356
357
358Mailing List:
359'Mark Lewis' has kindly set up a mailing list for SMS Client.
360If you would like to join, send and email to 'majordomo@medusa.myth.co.uk'
361with the following text in the body of the message:
362
363 subscribe sms_client
364
365Mark can be contacted via email at mark@mythic.net
366
README.1ST
1Version 3.0.2
2=============
3
4This version is under HEAVY revision. It should continue to work as has
5in the past. But is undergoing a great deal of updating. As a result;
6the documentation will become far more concise, and easier to understand.
7Old outdated material will be removed. yadda, yadda, yadda...
8
9Version 2.0.8
10=============
11
12Version 2.0.8 differs from 2.0.7 most noteable in that the
13configuration file syntax has changed. The service files
14are now all in lower case, the easiest way to install this
15version if you have 2.0.7 already installed is simply to
16move /etc/sms to /etc/sms.orig and install this version,
17the news files will be placed in /etc/sms leaving your
18originals alone. When calling a service use the lower case
19name, for example.
20
21 sms_client minicall:angelo "SMS Client-2.0.8f Test EMAIL_ADDRESS"
22
23This version does not offer the same level of protect that
242.0.7s-7 has over forcefully hanging up by killing children
25that have been sitting waiting for too long. I'll fit the
26code as soon as I get a chance.
27
286 Jan 2000 - The code to force hanging up has been backfitted
29 you can now consider the 2.0.8 releases as useable
30 as the 2.0.7 releases.
31