configure.html

GSM猫管理程序

</p>

<p>
<i><b>mode = old/new</b></i><br>
<font size="1">Default value: <i>new</i>.</font><br>
Specifies version of modem command set. 
Almost everybody needs to use this as a "new".
<p>
From version >= 3.0.9 this effects mainly to the sending side. In the receiving side the incoming PDU is checked,
and if it does not match to the selected mode, another mode is tried automatically.
<p>
<table border=1 bgcolor=lightgrey>
<tr><TD bgcolor=yellow>old</TD>
<td>For Falcom A1 and maybe some other old modems of GSM phase 1 (1990-1995).<br>
In the receiving side this mode <b>does not have SCA</b> information in the begin of PDU.
</td></tr>
<tr><TD bgcolor=yellow>new</TD>
<td>For nearly all mobile phones and modems.<br>
In the receiving side this mode <b>has SCA</b> information in the begin of PDU.
</td></tr>
</table>
(SCA stands for Service Centre Address).
</p>

<p>
<i><b>smsc = number</b></i><br>
<font size="1">Default value: not in use.</font><br>
Specifies the SMSC number that this modem should use to send SM. 
You need this setting only if the default of the SIM card is bad. 
Write the phone number of the SMSC in <u><b>international format</b></u> without the starting "+".
</p>

<p>
<i><b>baudrate = number</b></i><br>
<font size="1">Default value: <i>19200</i>.</font><br>
Specifies the speed of the serial communication in bits per second. 
Most modems work well with 19200 baud, some need 9600 baud.

<p>
<i><b>rtscts = yes/no</b></i><br>
<font size="1">Default value: <i>yes</i>.</font><br>
You can disable usage of hardware handshake wires by setting this option to "no". 
Please don't use this feature in commercial applications because 
the hardware handshake wires ensure proper communications timing between the 
computer and the modem. 
</p>

<p>
<i><b>send_delay = number</b></i><br>
<font size="1">Default value: <i>1</i>.</font><br>
If your modem does not support hardware handshake you should use the lowest possible baudrate to ensure that the
program does not run faster than the modem can do. However, if the lowest possible baudrate is still to fast, then you
can use this parameter to make it even slower. 
A value of 300 means that the program waits 300 milliseconds between sending each single character to the modem 
which makes the program very slow.
</p>

<p>
<i><b>cs_convert = yes/no</b></i><br>
<font size="1">Default value: <i>yes</i>.</font><br>
The program converts normal text messages into GSM character set. You need this to display
german umlauts and control characters correctly.
</p>

<p>
<i><b>report = yes/no</b></i><br>
<font size="1">Default value: <i>no</i>.</font><br>
If you enable this, the program requests a status report SM from the SMSC for each sent message.
This does not work on many mobile phones and on some modems.
</p>

<p>
<i><b>eventhandler = filename</b></i><br>
<font size="1">Default value: empty.</font><br>
Specifies an eventhandler script like in the global part. 
If you use this variable, then this modem will use its own individual eventhandler instead of the global one.
</p>

<p>
<i><b>primary_memory = memory name</b></i><br>
<font size="1">Default value: not in use.</font><br>
<i><b>secondary_memory = memory name</b></i><br>
<font size="1">Default value: not in use.</font><br>
<i><b>secondary_memory_max = number</b></i><br>
<font size="1">Default value: accept what device returns.</font><br>
These three settings are used to control dual-memory handler, available from version >= 3.0.<br>
If your modem/phone receives messages to the Mobile Equipment (ME) memory after the SIM memory (SM) has been filled up,
with dual-memory handler messages can be read from the Mobile Equipment memory too.<br>
Defining secondary_memory_max is needed, if your device does not tell how much there is space in the Mobile Equipment memory.
For example the Nokia 6210 does not tell (it returns 0 as max value) and with this device 150 is reasonable value.<br>
From version >= 3.1, multiple parameters can be defined for memories, like SM,SM,SM.
Double-quotation marks are not necessary to use in the string.
</p>

<p>
<i><b>pdu_from_file = filename / directoryname/</b></i><br>
<font size="1">Default value: not in use.</font><br>
Available from version >= 3.0. This is for testing purposes.<br>
You can test you eventhandler and some other things without actually receiving a message from the modem/phone.
This is especially important when it's not possible to receive the same message again because the sender cannot be reached.<br>
You may have the original PDU string stored to the incoming messsage file, or you may see it in log file (depending of the loglevel).
This PDU string can be stored to the <i>pdu_from_file</i> named file, and when this file exists the smsd will read the PDU from there.
Rest processing will be done similarry than with normally received messsages and you can then debug possible problems
and see when they are fixed.<br>
This file can contain empty lines and comment lines starting with # character.<br>
Actual data can be stored as one line containing the PDU string, or two lines containing (first) the modem answer
and (second) the PDU string.<br>
For example:<br>
<font size="1">#2006-09-13 13:12:10,7, GSM1: &lt;- <br>
+CMGR: 0,,40<br>
0791531811111111240C9153183254769800F1609031314174211854747A0E4ACF416110BD3CA783DAE5F93C7C2EBB14</font><br>
or simply one line only:<br>
<font size="1">079153181111111106BC0C91531832547698609031314174216090313141842100</font><br>
<br>
<b>NOTE:</b> After this file is processed, it is <b>removed</b>.
<br>
After >= 3.0.9 the setting can be a directory.<br>
If this setting ends with a slash and a directory with that name exists,
file(s) are read from this directory (and deleted after processing).
All files found from the given directory are processed one by one, expect hidden files (name begins with a dot).
When this setting points to the directory, no dot's are allowed in any position of a path.
Be very careful with this setting while it will delete the content of a whole directory.
<br>
After >= 3.0.9: while reading a PDU from file, a first line starting with PDU: and space is taken if any exists.
</p>

<p>
<i><b>sending_disabled = yes/no</b></i><br>
<font size="1">Default value: <i>no</i>.</font><br>
Available from version >= 3.0. This is for testing purposes.<br>
You can test your eventhandler and whole system around the smsd without sending any messages to the GSM network.
All other functionality is working as usual, so this is some kind of "mute" to the modem.
However the modem should be connected and working.
This does not have an effect to the incoming messsages.
</p>

<p>
<i><b>modem_disabled = yes/no</b></i><br>
<font size="1">Default value: <i>no</i>.</font><br>
Available from version >= 3.0.9. This is for testing purposes too.<br>
Whole messaging system including eventhandlers etc. can be tested without any working
modem existing. Sending of messages is simulated in the similar way than with <i>sending_disabled</i> setting.
Incoming messages are taken only from the file, if <i>pdu_from_file</i> is defined.
No any communication is made between smsd and modem, but a device setting should still exist because smsd wants to
open and close a device.
If in you testing environment you do not have a priviledges to the usual modem device,
like /dev/ttyS0, you can use a definition like <i>device = /tmp/modemfile</i>.
If this file exists and is writable for the process owner, it's enough for smsd.
</p>

<p>
<i><b>decode_unicode_text = yes/no</b></i><br>
<font size="1">Default value: use the global part setting.</font><br>
Available from version >= 3.0. Specifies an internal Unicode decoding like in the global part.
</p>

<p>
<i><b>internal_combine = yes/no</b></i><br>
<font size="1">Default value: use the global part setting.</font><br>
Available from version >= 3.0. Specifies an internal multipart message combining like in the global part.
</p>

<p>
<i><b>pinsleeptime = number</b></i><br>
<font size="1">Default value: <i>0</i>.</font><br>
Available from version >= 3.0.9. Specifies how many seconds the program will sleep after a PIN is entered.
Some modems do not work without some delay.
</p>

<p>
<i><b>admin_to = phone number</b></i><br>
<font size="1">Default value: not in use.</font><br>
Available from version >= 3.1. Specifies a destination number for administrative messages created by smsd.
This setting overrides the setting in the global part.
</p>

<p>
<i><b>message_limit = number</b></i><br>
<font size="1">Default value: not in use.</font><br>
<i><b>message_count_clear = number</b></i><br>
<font size="1">Default value: not in use.</font><br>
Available from version >= 3.1. Message_limit specifies the maximum number of messages to send.
After this limit is reached, no more messages will be sent until the smsd is restarted or message counter
is cleared by the message_count_clear setting. The value of this setting is minutes.<br>
If <i>admin_to</i> is specified, an administrative message is sent when the limit is reached.
</p>

<p>
<i><b>outgoing = yes/no</b></i><br>
<font size="1">Default value: <i>yes</i>.</font><br>
Available from version >= 3.0.9.
Specifies if a modem is used to handle and send outgoing messages.
</p>

<p>
<i><b>phonecalls = yes/no</b></i><br>
<font size="1">Default value: <i>no</i>.</font><br>
Available from version >= 3.1.
Specifies is missed phonecalls are reported.
</p>

<p>
<i><b>keep_open = yes/no</b></i><br>
<font size="1">Default value: <i>yes</i>.</font><br>
Available from version >= 3.1.
If this is changed to <i>no</i>, a modem is closed while it's not used.
</p>

<p>
<b>Regular_run for a modem is available from version >= 3.1:</b><br>
<i><b>regular_run_interval = number</b></i><br>
<font size="1">Default value: <i>300</i>.</font><br>
Describes number of seconds between each run.
Value <i>0</i> disables this feature including next 6 settings.
</p>

<p>
<i><b>regular_run = filename</b></i><br>
<font size="1">Default value: not in use.</font><br>
An external script or program to execute.
A modem can be used as it's closed by the smsd.
</p>

<p>
<i><b>regular_run_cmdfile = filename</b></i><br>
<font size="1">Default value: not in use.</font><br>
This file can contain command lines which smsd will write to the modem.
Modem result of each line is logged and written to the regular_run_statfile (if defined).
After a file is processed, it is removed.
If you need to use permanent commands on each run, use regular_run script to create this file or
define commands using regular_run_cmd settings.
</p>

<p>
<i><b>regular_run_cmd = string</b></i><br>
<font size="1">Default value: empty.</font><br>
Like regular_run_cmdfile, this string can be used to define modem commands.
This setting can be used more than once to define multiple commands.
</p>

<p>
<i><b>regular_run_logfile = filename</b></i><br>
<font size="1">Default value: not in use.</font><br>
Defines a log file for regular_run. Syslog cannot be used for this.
If a log file is not defined, smsd's main log is used.
</p>

<p>
<i><b>regular_run_loglevel = number</b></i><br>
<font size="1">Default value: LOG_NOTICE.</font><br>
Defines a level of logging.
</p>

<p>
<i><b>regular_run_statfile = filename</b></i><br>
<font size="1">Default value: not in use.</font><br>
If defined, results of commands are written to this file.
Old file is cleared before each run.
</p>

<p>
</p>

</body>
</html>