FreeCalypso > hg > fc-pcsc-tools
comparison doc/User-oriented-commands @ 72:54800d2f5752
doc/User-oriented-commands: SMS manipulation documented
author | Mychaela Falconia <falcon@freecalypso.org> |
---|---|
date | Mon, 15 Feb 2021 05:40:10 +0000 |
parents | a008f7a4bddf |
children | a56bbd6b0277 |
comparison
equal
deleted
inserted
replaced
71:a008f7a4bddf | 72:54800d2f5752 |
---|---|
309 one does not write into SIM LND. | 309 one does not write into SIM LND. |
310 | 310 |
311 Manipulating stored SMS | 311 Manipulating stored SMS |
312 ======================= | 312 ======================= |
313 | 313 |
314 The fundamental operating model of all message stores for SMS (whether SIM or | |
315 phone-based) is that received messages accumulate (and possibly sent ones too, | |
316 if they are stored in this manner), the limited available memory fills up, and | |
317 then the user needs to clean out the accumulated messages, preferably also | |
318 archiving them by transferring to a larger computer for longer-term storage. | |
319 Given this fundamental operating model, we only need to provide commands for | |
320 dumping the content of the message store and for cleaning it out - there is no | |
321 real need to implement commands for writing messages into the store. | |
322 | |
323 The extent of special support for the SIM SMS store in fc-simtool is rather | |
324 minimal because it just so happened that we already have external tools that do | |
325 a major part of the work. Some phone firmwares, particularly that of the | |
326 Pirelli DP-L10 phone currently used by the Mother, implement their on-the-phone | |
327 SMS storage by a way of a file in their local flash file system whose binary | |
328 format just happens to be exactly the same as the binary format of SIM-based | |
329 EF_SMS if all 176-byte records are simply abutted together in the host-based | |
330 binary representation. A few release cycles ago we added a new utility named | |
331 pcm-sms-decode to our FreeCalypso host tools suite; this utility reads a binary | |
332 file in this "EF_SMS records concat" format and performs the quite involved job | |
333 of fully decoding all messages into human-readable form. Given that we have | |
334 this external pcm-sms-decode utility, all we need to do in fc-simtool is save | |
335 all records of EF_SMS into a single concatenated binary file, and let | |
336 pcm-sms-decode do the rest. | |
337 | |
338 Our dedicated commands for working with the SIM SMS store are as follows: | |
339 | |
340 save-sms-bin host-filename | |
341 | |
342 This command saves the full content of EF_SMS in the named file in the host file | |
343 system in binary format, suitable for further decoding with pcm-sms-decode. | |
344 | |
345 sms-erase-all | |
346 | |
347 This command erases every record entry in EF_SMS. | |
348 | |
349 sms-erase-one rec | |
350 | |
351 This command erases the specified individual record in EF_SMS. | |
352 | |
353 sms-erase-range start-rec end-rec | |
354 | |
355 This command erases the specified range of records in EF_SMS. The starting | |
356 record must be identified by number (SIM record numbers are 1-based); the | |
357 ending record argument may be either as a number or the "end" keyword. | |
358 | |
314 Manipulating SMS profiles | 359 Manipulating SMS profiles |
315 ========================= | 360 ========================= |
316 | 361 |
317 Identifying MVNO SIMs | 362 Identifying MVNO SIMs |
318 ===================== | 363 ===================== |