1 .TH MDSMS 1 "30 Oct 1999" ~ VERSION ~ "MDSMS Manual"
6 mdsms \- Mobile Device SMS tool
9 .BR "mdsms --send" [ -mobildock ]
19 .BR "mdsms --logo-send"
25 .BR "mdsms --ring-send"
31 .RB [ "-c <cfgfile>" ]
35 .RB [ "-l <lockfile>" ]
44 Program sends one SmartMessaging SMS through one of the supported mobile
45 device connected through the serial port. Currently supported:
48 .B Nokia Communicator 9000/9000i
49 All modes except \fB--logo-send\fP supported.
51 .B Nokia Communicator 9110
52 All modes supported. This is the only device with \fB--logo-send\fP capability for now.
55 Firmware revision 2.0 required. All modes except \fB--logo-send\fP supported.
60 .BR -c | --config\ < cfgfile >
61 Process recursively this file and read all options from it. See the section
65 .BR -d | --device\ < device >
66 Specify serial device to communicate with your mobile. If only bare name is
67 specified, "\fB/dev/\fP" is prepended automatically. This device name is used
72 .BR -L | --log\ < file >
73 Log all important messages to this file preceded by timestamp, machine hostname
74 etc., similar to output of
76 If set to empty string (which is default - ~\fB DEF_LOGNAME \fP~), nothing
79 .BR -b | --baud\ < rate >
80 Sets custom baudrate for accessing Nokia modem. Supported speeds are currently:
86 \fB57600\fP. Default is \fB DEF_BAUD \fP.
88 .BR -l | --lockfile\ < lockfile >
89 Prior to accessing serial device specified above the lockfile should be
90 acquired for correct concurrent processes behaviour. Although this name
91 can be given as direct filename more common method is to use pattern
92 with embedded "\fB%s\fP" where this mark is replaced by actual basename
93 (last component of pathname with all preceding directory names stripped)
94 of serial device used.
95 Default name for lockfile is ~\fB DEF_LOCKFILE \fP~.
97 .BR -s | --smsc\ < smsc\ # >
98 Specify custom SMS center number. If not specified (or overriden as empty
99 string by \fB-s ""\fP)
101 asks by "\fBAT+CSCA?\fP"
102 for the current default SMS center. Situation with undeterminable SMS center
103 is unrecoverable and casues immediate fail. It is a common practice to use
104 plus sign ("\fB+\fP") to indicate international number type.
105 Known SMS centers as of May 1999:
108 .BR "CZ Paegas " ( "230 01" "): " +420603052000
110 .BR "CZ EuroTel " ( "230 02" "): " +420602909909
113 .BR -m | --maxretry\ < # >
114 Maximum retries of any \fBAT\fP-style command during the session. All the
115 retries are summed during one run of
117 and no more retries of the command are permitted. After exceeding this
118 value the program is terminated. Exception is \fB--receive\fP which is never
119 quit after the initial initialisation has been successfuly negotiated.
121 .BR -r | --readtime\ < sec >
122 Maximum response read timeout before command retry.
124 sends the requested \fBAT\fP-style command to the device and expects response.
125 After exceeding this time interval,
127 reissues the last command until the maximum retry count (\fBmaxretry\fP) is exhausted.
130 seconds and should be enough for standard
132 responses. This is the only point where
134 differs the behaviour from regular
136 option. Unfortunately when
138 has a voice call in progress, it will block any serial device
139 communication with \fBSiemens A1\fP and it is impossible to differentiate between call-in-progress
141 and stucked/disconnected one, so the parameter
143 has very large value, see further. After exceeding this time interval,
145 is terminated immediately,
147 parameter notwithstanding. Standard value of this parameter is
148 .BR DEF_READTIME_MOBILDOCK
149 seconds and should be enough for any voice call.
151 .BR -t | --chartime\ < msec >
152 \fB(This paragraph\fP
154 \fBapply to Nokia 9110 or similiar smart devices but the functionality has been
155 retained just to be on the safe side.)\fP
156 Although the fixed used baudrate of
158 is pretty low, MobilDock/Siemens A1 couple
160 able to accept steady
161 stream of data at this speed. Even the used XON/XOFF handshaking is just not
162 enough. The only possible workaround is to slowdown the communication by
163 waiting a bit after character sent to give relax time to these devices.
164 When full rate communication was used, occasional longer SMS data corruption
165 was observed. Argument is given in milliseconds and its default value is
168 .BR -T | --cmdtime\ < msec >
169 \fB(This paragraph\fP
171 \fBapply to Nokia 9110 or similiar smart devices but the functionality has been
172 retained just to be on the safe side.)\fP
173 This delay is given before sending any
175 command to the device.
176 Its primary purpose is to let any previous entered commands to finish and
177 to clear any input before actually sending our own command. Also all Siemens
178 devices are known that they strongly dislike fast edge-to-edge communication
179 and to satisfy these requirements this delay was considered as the best
185 When parameter <\fBmsg text\fP> has been specified, by using this option
186 \fBmdsms\fP will read the file with the <\fBmsg text\fP> filename instead
187 and send its \fBcontents\fP as the SMS message.
188 This parameter is applicable only together with \fB--send\fP or \fB--send-mobildock\fP mode.
191 Increase verbosity level by one. Currently the maximum defined level is
197 Give short parameters description to
199 (standard error output stream).
202 Print the version number and exit.
204 .RB < "dest. phone" >
205 This mandatory parameter specifies the telephone number of the recipient
206 of SmartMessaging message. International prefix character plus
208 is supported the national mode without plus
210 prefix is supported and the meaning is specific to the GSM operator currently
211 being roamed in (NOT the native
213 operator of the SIM card!).
214 This number can be made default in system configuration files, see below
219 Here you write the exact body of the message. This parameter should be
220 specified only as one component, although if more found they are concatenated
221 with separating space (" "). But this practice is discouraged as
222 your shell will probably remove any multiple spaces found and also other
223 metacharacters may be incorrectly interpreted. To prevent any escaping
224 mess, you may prefer to omit this parameter and the the message text is
227 (standard input stream).
228 This parameter is applicable only together with \fB--send\fP or \fB--send-mobildock\fP mode.
230 .RB < "logo filename" >
231 Here you specifify the filename of the logo file to be uploaded. Currently
232 recognized file formats are \fBNOL\fP (Nokia logo?) and \fBNGG\fP (Nokia
233 Group Graphics). These formats are proprietary by \fBKESSLER Wireless Design\fP
234 and \fBmdsms\fP currently "can't" edit them.
235 This parameter is applicable only together with \fB--logo send\fP mode.
236 More info can be found on:
238 .B http:/ /www.kessler-design.com/wireless/operatorlogo.php3
242 Specify GSM network code to be set on the logo being uploaded. Upon upload to
243 Nokia phone each operator logo has a GSM network code binded with it. When
244 you are registered (even roamed) into such network the logo is displayed on
245 the phone. Current Nokia mobile phones can handle only one logo loaded
246 simultaneously, it will be rewritten by any other upload. You can also
247 specify string ~\fB WORD_GROUP \fP~ to send the logo as group graphics
248 (even from \fBNOL\fP format) or string ~\fB WORD_NET \fP~ to force detection
249 of network code from \fBNOL\fP. The default if this parameter is not specified
250 is ~\fB WORD_NET \fP~ for \fBNOL\fP files and ~\fB WORD_GROUP \fP~ for
252 This parameter is applicable only together with \fB--logo send\fP mode.
256 reads ~\fB CONFIG_MAIN \fP~ followed by ~\fB$HOME CONFIG_HOME \fP~
257 configuration files. The content of these files (and also any file read by
262 syntax with dashes. Newlines are taken as whitespace, both double ("\fB~\fP")
263 and single ("\fB'\fP")
264 quoting is supported. Embedded quote characters can be escaped by backslash
266 Arguments are processes in order as specified in configuration files and
267 finally the command-line of the program itself, overriding any previous
268 values. Although the order of
270 options on one line is preserved the first file is read AFTER all of the
271 current options are processed. Recursive use of
273 is permitted and the files are read in LIFO (Last-In First-Out, AKA stack)
274 order. You should use "\fB-v -v\fP"
275 to see details of option processing with more complex configuration setups.
280 locks the port (see option
282 for details) and opens the serial device with specified baudrate (default
283 \fB DEF_BAUD \fP baud), software handshaking (XON/XOFF style), 8 bits,
284 no parity. Then issues the following commands:
286 .BR AT <ESCAPE><CTRL-Z>
290 (if present, otherwise it is harmlesss anyway) and pass the following
292 (ascii decimal code 27 followed by 26) characters to the device and break it from eventual
294 mode in which it may errorneously remain from previous sessions.
297 Test the responsiveness of the device.
299 \fBAT+CSCA="\fPsmc # from user\fB"\fP
300 This command is omitted if
302 is not specified by user (or specified/overriden as empty string \fB""\fP
305 Query the currently set SMC center number to include it later to the
306 header of SMS PDU format where it is required. If \fBAT+CSCA="\fP...\fB"\fP
307 was issued before, this number should match it but no sanity checks are
308 currently do so. Also it is used to detect possibly unset SMS center.
310 .RB "Mode-dependent."
311 Here are executed the commands listed for each of the specified operation
315 Check that the mobile survived our torture.
318 The following operations are dependant on the operation:
320 .BR --send / --send-mobildock :
323 \fBAT+CMGF=0\fP, if fails \fBAT+CMGF=1\fP
324 Set the default SMS message format to PDU type (preferred) or text mode (if
325 PDU not available). Next \fB+CMGS\fP command is dependant on the mode selected
328 \fBAT+CMGS=\fP# chars if \fB+CMGF=0\fP
329 This command physically sends the message and the resulting "\fB+CMGS:\fP" output
330 is catched and returned as
332 (message reference) number to the user. \fB# chars\FP corresonds to total data
333 bytes sent to the phone (so the half of the hex-string, SMSC is included).
334 SMSC number is preceding the rest of PDU to be conformant with GSM Phase 2
335 specification. Siemens M1 or Siemens M20 rev. 1.x are known that
337 like this SMSC number, I have to get in touch with such device to be able to autodetect
338 it properly (mail me if you want to be helpful).
340 \fBAT+CMGS="\fPphone # from user\fB"\fP if \fB+CMGF=1\fP
341 The same as the previous command except that the message is text as pure text
342 terminated with \fB<CTRL-Z>\fP character. SMSC number is not present anywhere
346 .BR --logo-send / --ring-send :
349 \fBAT+CSMP=81,,0,245\fP
350 Sets PDU type to 81 (\fBSMS-SUBMIT\fP + integer-type for \fBvalidity\fP
351 + \fBUDHI\fP - user data header indicator), PID (protocol identifier) to
352 0 (standard non-converted SMS) and DCS (data coding scheme) to 0xF5
353 (\fBdata coding\fP/\fBmessage class\fP, \fB8-bit data\fP + \fBmobile-equipment\fP
356 \fBAT+CMGS="\fPphone # from user\fB"\fP
357 This command physically sends the message and the resulting "\fB+CMGS:\fP" output
358 is catched and returned as
360 (message reference) number to the user.
362 \fBAT+CSMP=17,,0,0\fP
363 Resets back PDU type to 17 (\fBSMS-SUBMIT\fP + integer-type for \fBvalidity\fP),
364 PID (protocol identifier) to 0 (standard non-converted SMS) and DCS (data coding
365 scheme) to 0 (\fBalphabet indication\fP, \fBdefault 7-bit alphabet\fP).
369 Receiving of messages is performed using direct routing of incoming data to TE (Terminal Equipment).
370 No SMSes are stored to SIM card/device memory and then read back as one may expect.
371 There are slight advantages of better response times (SIM card access is very slow) and
372 saving EEPROM writes to SIMcard. Unfortunately there is one big advantage that when
374 suddenly stops/crashes without switching the device back to SIM-store mode, messages
375 being consequently received are lost on the dead end of serial port.
377 tries very hard to restore the device state before its termination but sometimes it just
379 possible. Due to this fact \fBnever kill mdsms with SIGKILL (-9) signal\fP, use standard
380 SIGTERM instead, please. Also one fact resulting of this behaviour is that messages
381 with Class-2 (SIM store) specific routing are really stored to SIM card and as such are
382 not processed in any way by
384 Safer SIM store/retrieve mechanism may be implemented in future versions. Command sequence used in
389 \fBAT+CMGF=0\fP, if fails \fBAT+CMGF=1\fP
390 Set the default SMS message format to PDU type (preferred) or text mode (if
391 PDU mode not available).
394 Set the message routing to go directly to TE (Terminal Equipment), see the discussion
395 in paragraph above for more. Also right before starting attempt to send this command,
396 \fBAT+CNMI=,0\fP is set to be tried before finishing
398 to restore the original device behaviour.
403 really much interested in additional non-standard values of
404 PID (Protocol IDentifier), DCS (Data Coding Scheme) etc.
407 In this point the device lock file is removed, retry count is set to infinite value
412 starts to passively listen for any incoming data. Possible dial-out mode is being
413 detected afterwards, otherwise message receive sequence follows as described below.
416 Any waiting \fB+CMT\fP incoming message indications are read and processed. Format
417 being processed (text/PDU) depends on the actual value of \fBAT+CMGF\fP set before. Any
418 possible \fB+CMTI:\fP input is discarded as we are not interested in SIM-store
422 After processing all the messages, the whole initialization sequence is restarted as
423 the device configuration may have changed or lost during the data wait phase.
429 ETSI documentation for SMS messages in GSM networks
431 .B GNokii, tools and drivers for Nokia mobile phones
432 Nokia logo data format was read from its sources:
433 .B http:/ www.gnokii.org/
435 .B "Developers'" Guide: SMS with the A1
436 Tech note on PDU SMS format etc:
437 .B http:/ /www.siemens.se/telefoner/ovrigtgsm/fragorsvar/a1_sms.pdf
439 .B Technical Description of the Siemens A1
440 Siemens A1 command description
441 .B http:/ /www.siemens.se/telefoner/ovrigtgsm/fragorsvar/a1_manual.pdf
446 Main configuration file
448 \fB$HOME CONFIG_HOME \fP
449 User personalized local configuration file
453 was written by Jan Kratochvil who should be responsible for all the bugs
454 included. Please see the file "\fBAUTHORS\fP"
455 shipped with the original distribution archive for more details.