Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

gammu-smsbackup(5) [debian man page]

GAMMU-SMSBACKUP(5)						       Gammu							GAMMU-SMSBACKUP(5)

NAME
gammu-smsbackup - gammu(1) SMS backup file format. The SMS backup format is text file encoded in current encoding of platform where Gammu is running. This file use ini file syntax, see ini. SECTIONS
The file consists of sections, whose name starts with SMSBackup. When creating the backup file, three digits are appended to this text defining order. While reading the backup, any part after SMSBackup text is ignored and everything which begins with this is processed. So you can as well give the section name SMSBackupFoo and it will be processed. The number of messages in backup file is currently limited by GSM_BACKUP_MAX_SMS (100000 at time of writing this document). SMSBackup section Each section interprets one physical SMS message (eg. one message part in case of multipart messages). Decoded text For SMS backups created by Gammu, there is a decoded text as a comment just after the section name: [SMSBackup001] ; This is message text The text can be split to more lines if it is too long or of original message included new lines. Note This is easiest way to get message text, however also the least reliable one, because it is stored in the comments in the file. Variables The following variables can be defined for each SMS: SMSC Text representation of SMSC number, not used by Gammu if SMSCUnicode exists. SMSCUnicode Hex encoded UCS-2 string with SMSC number. Class Message class. Sent Timestamp, when message has been sent. PDU Message type, one of: o Deliver - received message o Submit - message to send o Status_Report - message to send with delivery report DateTime Timestamp of message (sent or received). RejectDuplicates Whether receiver should reject duplicates. ReplaceMessage ID of message to replace. MessageReference Message reference number as generated by network. State State of the message: o Read o UnRead o Sent o UnSent Number Recipient number. Name Name of the message. Length Length of message text. Coding Coding of the message: o 8bit - binary message o Default - GSM encoding, up to 160 chars in message o Unicode - Unicode encoding, up to 70 chars in message Text00 ... TextNN Numbered parts of the message payload. Folder ID of folder where the message was saved. UDH User defined header of the message. EXAMPLE
The backup of message can look like following: [SMSBackup000] #ABCDEFGHIJKLMNOPQRSTUVWXYZ # SMSC = "+4540590000" SMSCUnicode = 002B0034003500340030003500390030003000300030 Sent = 20021201T025023 State = UnRead Number = "+4522706947" NumberUnicode = 002B0034003500320032003700300036003900340037 Name = "" NameUnicode = Text00 = 004100420043004400450046004700480049004A004B004C004D004E004F0050005100520053005400550056005700580059005A000A Coding = Default Folder = 1 Length = 27 Class = -1 ReplySMSC = False RejectDuplicates = True ReplaceMessage = 0 MessageReference = 0 AUTHOR
Michal iha <michal@cihar.com> COPYRIGHT
2009-2012, Michal iha <michal@cihar.com> 1.31.90 February 24, 2012 GAMMU-SMSBACKUP(5)

Check Out this Related Man Page

GAMMU-SMSD-FILES(7)						       Gammu						       GAMMU-SMSD-FILES(7)

NAME
gammu-smsd-files - gammu-smsd(1) backend using filesystem as a message storage DESCRIPTION
FILES backend stores all data on a filesystem in folders defined by configuration (see gammu-smsdrc for description of configuration options). RECEIVING OF MESSAGES
Received messages are stored in a folder defined by configuration. The filename will be IN<date>_<time>_<serial>_<sender>_<sequence>.<ext>, for example NN20021130_021531_00_+45409000931640979_00.txt. Explanation of fields: <date> date in format YYYYMMDD <time> time in format HHMMSS <sender> sender number <serial> order of a message (in case more messages were received at same time), in format NN <sequence> part of the message for multipart messages, in format NN <ext> txt for text message, 8-bit messages are stored with bin extension, smsbackup for gammu-smsbackup The content of the file is content of the message and the format is defined by configuration directive InboxFormat (see gammu-smsdrc). TRANSMITTING OF MESSAGES
Transmitted messages are read from a folder defined by configuration. The filename should be one of the following formats: o OUT<recipient>.<ext> o OUT<priority>_<recipient>_<serial>.<ext> o OUT<priority><date>_<time>_<serial>_<recipient>_<note>.<ext> Explanation of fields: <recipient> recipient number where to send message <priority> an alphabetic character (A-Z) A = highest priority <ext> txt for normal text SMS, smsbackup for gammu-smsbackup <note> any artibrary text which is ignored For text messages, you can additionally append flags to extension: d delivery report requested f flash SMS b WAP bookmark as name,URL Other fields are same as for received messages. For example OUTG20040620_193810_123_+4512345678_xpq.txtdf is a flash text SMS requesting delivery reports. SMSes will be transmitted sequentially based on the file name. The contents of the file is the SMS to be transmitted (in Unicode or stan- dard character set). The contents of the file is the SMS to be transmitted (in Unicode or standard character set), for WAP bookmarks it is split on as Name,URL, for text messages whole file content is used. Please note that if file is not in Unicode, encoding is detected based on locales, which do not have to be configured if SMSD is running from init script. If this is your case, please add locales definition to init script. AUTHOR
Michal iha <michal@cihar.com> COPYRIGHT
2009-2012, Michal iha <michal@cihar.com> 1.31.90 February 24, 2012 GAMMU-SMSD-FILES(7)
Man Page