1scmxx(1) General Commands Manual scmxx(1)
2
6 scmxx - exchange data with your Siemens mobile phone
7
9 scmxx [--device device] [--baud baudrate] [--quiet] [--verbose]
10 [--reset] {--info | --set-time | --mem-info | --lock-info | --lock lock
11 {--enable | --disable} | --set-smsc --number {number | name} }
12 scmxx [--device device] [--baud baudrate] [--quiet] [--verbose]
14 [--reset] [--out file] [--pipe pipe] {--remove | --send | --get}
15 [--binary] [--mem memory] [--slot slot] [file...]
16 scmxx [--device device] [--baud baudrate] [--quiet] [--verbose]
18 [--reset] [--out file] [--pipe pipe] [--pin PIN] {--remove | --send |
19 --get} [--pbook] [--mem memory] [--slot slot] [--text text] [ --number
20 {number | name} ] [file...]
21 scmxx [--device device] [--baud baudrate] [--quiet] [--verbose]
23 [--reset] [--out file] [--pipe pipe] {--remove | --send | --get}
24 [--sms] [--mem memory] [--slot slot] [--text text] [ --number {number |
25 name} ] [--direct] [--flash] [--srr] [--unicode] [file...]
26 scmxx [--help] [--version]
28
30 SCMxx can copy files to and from a Siemens mobile phone and also delete
31 stored files. Files can read from a given file or through stdin and
32 stored to a given file or stdout. SMS can also be directly sent or
33 received without storing in the mobile phone. SCMxx was tested with
34 several mobile phones manufactured by Siemens (only S25 and later).
35
37 --device (-d)
38 specify another than the compiled in device. This overwrites the
39 SCMXX_TTY environment variable and the compiled-in value. For
40 linux systems, this may be e.g. /dev/ttyS0 for serial connec‐
41 tions, /dev/ircomm0 for infrared connections and /dev/rfcomm0
42 for bluetooth connections.
43 --baud (-b)
45 specify the device's speed. Valid values are dependent on the
46 system but may be 9600, 19200, 38400, 57600 or 115200. The
47 default value is 19200. The S25 and *35i only work at the 19200,
48 all later phones also work at full serial speed. Infrared con‐
49 nections may be an exception to these rules (dependent on the
50 infrared donle). This overwrites the SCMXX_BAUD environment
51 variable and the compiled-in value.
52 --out (-o)
54 specify a file to use. When getting binary files with "all", the
55 slot number, a dot and the filetype are appended. When sending
56 or deleting, this parameter has no use but the last parameters
57 that should be valid files. Stdout must be explicitly selected
58 with the dash ("-"), by default nothing is written to stdout.
59 There is nothing appended to "-" when getting multiple files.
60 --pipe (-p)
62 specify a pipe to another program. When getting with "all",
63 every file is piped to this programs on its own (only for
64 --binary and --sms).
65 --quiet (-q)
67 decreases verbosity by 1
68 --pin use this option if a PIN code is required for access
70 --verbose (-v)
72 increases verbosity by 1
73 --reset
75 try to reset the phone, so it gets accessible again. It may hap‐
76 pen that the phone does not answer on the serial interface any‐
77 more, especially with a previous user-interrupted file transfer.
78 This simply blindly sends some special characters.
79 --help (-h)
81 print the help message
82 --version
84 print the version number
85 --remove (-r)
87 removes an entry from the phone. When specified with --sms and
88 --get, this will get'n'delete. When specified with --sms and
89 --send, this will send'n'delete.
90 --get (-g)
92 get an entry and save it to a file. When specified with --sms
93 and --remove, this will get'n'delete. When specified with --sms
94 and --send, this will get'n'send.
95 --send (-s)
97 sends a file to the phone. When sending sms, you might want to
98 take a look at the option --direct, too. When specified with
99 --sms and --remove, this will send'n'delete. When specified
100 with --sms and --get, this will get'n'send.
101 --info (-i)
103 collect information from the phone, --mem-info can be used as a
104 trigger to display a more complex listing of the available memo‐
105 ries
106 --mem-info
108 display information about available memories and their slots and
109 other information. It uses the same format as --mem=? (see
110 below) and can also be use as a trigger for --info to replace
111 the short memory listing.
112 --lock-info
114 display status of locks. It can also be use as a trigger for
115 --info to replace the lock name listing.
116 --lock specify a lock that you can enable or disable. For some locks,
118 a password is needed (see --pin)
119 --enable
121 enable e.g. a lock
122 --disable
124 disable e.g. a lock
125 --dial dial a number (requires --number). The program returns either
127 after 10 seconds or when the call reached the other side.
128 --hangup
130 hangup all currently active calls
131 --set-time
133 synchronize time to phone. The use of tools like ntpdate is rec‐
134 ommended before using this.
135 --set-smsc
137 set the SMSC number (requires --number)
138 --binary (-N)
140 select binary file transfer mode
141 --pbook (-P)
143 select phonebook transfer mode
144 --sms (-S)
146 select short message service mode
147 --mem select a memory to access. Slot numbers may vary depending on
149 the selected memory. See the output of --info for the supported
150 memory types. Not using this option triggers the default behav‐
151 iour (if a default behaviour was defined). There is a special
152 string "?" that outputs in the same format as --mem-info but
153 only for the selected mode.
154 --slot select a slot to access. See the output of --mem-info or
156 --mem=?. Not using this option triggers the default behaviour
157 (if a default behaviour was defined). The special string "all"
158 defines the whole range of available slots for the selected mem‐
159 ory and mode and, except with --sms, cannot be used with --send.
160 For SMS, there are four additional special strings: "read",
161 "unread", "sent" and "unsent". The latter two can be used with
162 --send. For phonebook access, there is the additional special
163 string "last". When this option is omitted with --send, scmxx
164 tries to find an empty slot (that may or may not take long).
165 Finding an empty slot is not supported for phonebooks, yet.
166 When a slot was specified and also multiple files to upload, the
167 specified slot is the starting point to search for empty slots.
168 Overwriting multiple, non-empty slots is not supported, yet,
169 except for the special case "all".
170 --text (-t)
172 specify content text of short message or text of the phonebook
173 entry. For phonebook entries, the length limit may depend on
174 the selected phonebook (see output of --mem-info or --mem=?).
175 --number (-n)
177 specify number to send the short message to or the number for
178 the phonebook entry. Note that the number may have a leading
179 '+' for international numbers. It is normally limited to 20 dig‐
180 its (without the '+') which is certainly enough.
181 --direct
183 send/get short messages without storing in the phone. This is
184 not default because you will certainly be charged for it when
185 sending. With direct getting, SMS that are not of type DELIVER
186 are still stored on the phone (scmxx cannot decode those mes‐
187 sages, yet).
188 --unicode
190 send the short message and use UCS-2 (16bit unicode) as charac‐
191 ter set. You do not need to specify this parameter to enable
192 unicode sms decoding.
193 --flash
195 set the class0 in the data coding scheme field that is normally
196 interpreted as "immediate display". Not all receiving entities
197 support this. Note that a second sms of this type normally over‐
198 writes a previous one without asking! Its use is not recom‐
199 mended.
200 --srr this sets the StatusReportRequest bit in the pdutype field of
202 the sms pdu. It depends on the SMSC if this is honored. With
203 some providers, this produces additional costs!
204 --sort sort the messages on printing to chosen output. Possible sorting
206 methods are "type", "slot" and "type,slot". "type" sorts for the
207 type of the short message with an internal order of unsupported
208 types first, then SMS-SUBMIT, SMS-STATUS-REPORT and SMS-DELIVER.
209 "slot" sorts for the slot of the short message. "type,slot" does
210 sorting like "type" first and sorts each type like "slot".
211 Default is to not sort at all (order depends on phone).
212 --pin enable pin usage. Use this only if there was an error message
214 that asks for a PIN or PUK. For a PIN, this is the corresponding
215 "<PIN>", for a PUK, it is "<PUK>,<new PIN>". The value is only
216 used once. Consider using the pin file (see below) instead of
217 this option.
218 --system-charset
220 define the system character set instead of using the return
221 value from nl_langinfo(CODESET). This is to work around systems
222 that do not support unicode locales like UTF-8 or when data from
223 a different system with a different locale is used as input.
224 Usually, you do not need this option.
225
227 Send an bitmap file to the phone as bitmap (logo):
228 scmxx --send --binary --mem="bmp" --slot=0 myfile.bmp
229 Get a Bitmap from the phone and save it into a new file:
231 scmxx --get --binary --mem="bmp" --slot=0 --out=myfile.bmp
232 Get all unread (default on get) short messages and output to stdout:
234 scmxx --get --sms --slot=unread --out=-
235 scmxx -gS -o-
237 Send a short message directly (not stored in the phone):
239 scmxx --send --sms --direct --number=123 --text="test"
240 Get a phonebook and store it to a file:
242 scmxx --get --pbook --mem=SM --out=SM.pb
243 Modify a specific slot (33) in phonebook memory SM:
245 scmxx -sP --mem=SM --slot=33 --number=123 --text="test"
246
248 The output of text (phonebook and sms) depends on the character set of
249 your current locale. Input is the same. This has the advantage of
250 localization but may have the drawback that all other characters must
251 be entered by a sequence \XXXX where X is a hex character (e.g. \20ac
252 for EuroSign). This is a 16bit representative of the unicode value. The
253 \XXXX is only used for output with the intention to read it again at a
254 later time. For normal output, characters that cannot be displayed in
255 the current local are replaced by a '?'. Using an UTF-8 based locale
256 will make sure that all character can be converted. The newline char‐
257 acter can be entered using the common \n and '\' must be masked with
258 itself. In bash, this might even result in a needed input like "\\\\".
259
261 There are additional parameters --ignore-serial-bits (default) and
262 --keep-serial-bits. Use it only when you get no response from the
263 phone at all. Which setting is needed depends on the cable and serial
264 port and cannot be determined automatically.
265 If you experience timeouts on the first command, try the
267 --start-delay=<seconds> parameter.
268 Another parameter --device-timeout=<seconds> is provided for the case
270 that your phone ever needs more than default value of 10 seconds to
271 answer. Actually, this should be more than enough but one never knows.
272 The minimum value is 1, values higher than 25 mean "forever".
273
275 The --pin option should be used with care. The option and its argument
276 are visible in the process list.
277
279 SCMXX_TTY
280 see --device for decription
281 SCMXX_BAUD
283 see --baud for description
284
286 ~/.scmxx/cache.pb
287 this file serves as lookup file during short message output (for
288 recipient/sender address) and for number aliasing for --number
289 on sending a short message. The format is the same as a phone‐
290 book file (slot numbers don't matter but must be present).
291 ~/.scmxx/config
293 this file can contain long options (without the --), the argu‐
294 ments is seperated from the option name by an '='. Any amount
295 of spaces at beginning of line, before and after the seperator
296 are allowed. A '#' at beginning of line marks this line as com‐
297 ment. Examples:
298 #choose a device to access
301 device = /dev/ttyS0
302 #always send SMS using UCS-2
303 unicode
304 ~/.scmxx/pin
308 This file is used as an alternativ to the --pin command line
309 option. The file MUST NOT be group readable/writeable or world
310 readable/writeable! It also MUST be a regular file, not a sym‐
311 link. SCMxx refuses to use the file if this is not the case. If
312 a PUK value is requested by the phone, the corresponding PIN
313 must also be defined. The only necessary format elements are
314 '{', '=', ';' and '}'. Spaces and newlines are ignored. The
315 file has the following format:
316 sim 262031234567890 {
319 pin = 1234
320 puk = 12345678;
321 pin2 = 4321;
322 puk2 = 87654321;
323 }
324 device 350123456789012 {
325 type SIM {
326 pin = 0000;
327 puk = 0000;
328 }
329 }
330 "sim" sections use the IMSI as identifier, "device" sections use
333 the IMEI as identifier (see output of --info). Since the IMSI is
334 needed, you canNOT switch the phone on with this! The "type"
335 sub section in the device section has the following idenfifiers:
336 SIM device code (theft protection)
338 FSIM very first inserted SIM
340 NET network personalization
342 NETSUB network subset personalization
344 SP service provider personalization
346 CORP corporate personalization
348
351 Hendrik Sattler post@hendrik-sattler.de
352SCMxx 2005-06-24 scmxx(1)