gammurc - gammu(1) configuration file
~/.gammurc or /etc/gammurc
On Microsoft Windows:
C:\\Documents and Settings\\username\\Application Data\\gammurc or .\\gammurc
On Windows, user configuration is tried at profile/Application Data/gammurc and then gammu falls back to current directory (./gammurc).
This file use ini file syntax, with comment parts being marked with both ; and #. Sections of config file are identified in square brackets line [this]. All key values are case insensitive.
Configuration file for gammu can contain several sections - [gammu], [gammu1], [gammuN], ... Each section configures one connection setup and in default mode gammu tries all of them in numerical order. You can also specify which configuration section to use by giving it's number ([gammu] has number 0) as a parameter to gammu(1) and it will then use only this section.
Protocol which will be used to talk to your phone.
For Nokia cables you want to use one of following:
fbus - serial FBUS connection
fbususb - FBUS over USB cable (experimental, for Nokia
cables on Linux, including DKU-2)
dlr3 - DLR-3 and compatible cables
dku2 - DKU-2 and compatible cables
dku5 - DKU-5 and compatible cables
mbus - serial MBUS connection
If you use some non original cable, you might need to append -nodtr (eg. for ARK3116 based cables) or -nopower, but Gammu should be able to detect this automatically.
For non-Nokia phones connected using cable you generally want:
at - generic AT commands based connection
You can optionally specify speed of the connection, eg. at19200, but it is not needed for modern USB cables.
For IrDA connections use one of following:
irdaphonet - Phonet connection for Nokia phones.
irdaat - AT commands connection for most of phones (this is
not supported on Linux).
irdaobex - OBEX (IrMC or file transfer) connection for most
of phones.
irdagnapbus - GNapplet based connection for Symbian
phones
For Bluetooth connection use one of following:
bluephonet - Phonet connection for Nokia phones.
blueat - AT commands connection for most of phones.
blueobex - OBEX (IrMC or file transfer) connection for most
of phones.
bluerfgnapbus - GNapplet based connection for Symbian
phones
Device node or address of phone. It depends on used connection.
For cables or emulated serial ports, you enter device name (for example /dev/ttyS0, /dev/ttyACM0, /dev/ircomm0, /dev/rfcomm0 on Linux, /dev/cuad0 on FreeBSD or COM1: on Windows). The special exception are DKU-2 and DKU-5 cables on Windows, where the device is automatically detected from driver information and this parameters is ignored.
For USB connections (currently only fbususb and dku2 on Linux), you can specify to which USB device Gammu should connect. You can either provide vendor/product IDs or device address on USB:
Device=0x1234:0x5678#Matchdevicebyvendorandproductid
Device=0x1234:-1#Matchdevicebyvendorid
Device=1.10#Matchdevicebyusbbusanddeviceaddress
Device=10#Matchdevicebyusbdeviceaddress
For Bluetooth connection you have to enter Bluetooth address of your phone (you can list Bluetooth devices in range on Linux using "hcitool scan" command). Optionally you can also force Gammu to use specified channel by includig channel number after slash.
Before using Gammu, your device should be paired with computer or you should have set up automatic pairing.
For IrDA connections, this parameters is not used at all.
If IrDA does not work on Linux, you might need to bring up the interface and enable discovery (you need to run these commands as root):
iplsdevirda0up
sysctlnet.irda.discovery=1
Alias for Device, kept for backward compatibility.
Do not use this parameter unless really needed! The only use case for this is when Gammu does not know your phone and misdetects it's features.
The only special case for using model is to force special type of OBEX connection instead of letting Gammu try the best suited for selected operation:
obexfs - force using of file browsing service (file
system support)
obexirmc - force using of IrMC service (contacts, calendar
and notes support)
obexnone - none service chosen, this has only limited use
for sending file (sendfile command)
If you want to set time from computer to phone during starting connection.
This option allow to set, that you want (setting "yes") to see message on the phone screen or phone should enable light for a moment during starting connection. Phone will not beep during starting connection with this option. This works only with some Nokia phones.
Forces using specified codepage (for example "1250" will force CP-1250 or "utf8" for UTF-8). This should not be needed in most cases, Gammu should detect it according to your locales.
Path to directory with localisation files (the directory should contain LANG/LC_MESSAGES/gammu.mo). If gammu is properly installed it should find these files automatically.
Path to file where information about communication will be stored.
Determines what all will be logged to LogFile. Possible values are:
nothing - no debug level
text - transmission dump in text format
textall - all possible info in text format
textalldate - all possible info in text format, with time
stamp
errors - errors in text format
errorsdate - errors in text format, with time stamp
binary - transmission dump in binary format
For debugging use either textalldate or textall, it contains all needed information to diagnose problems.
Custom features for phone. This can be used as override when values coded in common/gsmphones.c are bad or missing. Consult include/gammu-info.h for possible values (all GSM_Feature values without leading F_ prefix). Please report correct values to Gammu authors.
On Posix systems, you might want to lock serial device when it is being used using UUCP-style lock files. Enabling this option (setting to yes) will make Gammu honor these locks and create it on startup. On most distributions you need additional privileges to use locking (eg. you need to be member of uucp group).
This option has no meaning on Windows.
There is more complete example available in Gammu documentation.
Gammu configuration for Nokia phone using DLR-3 cable:
[gammu] device = /dev/ttyACM0 connection = dlr3
Gammu configuration for Sony-Ericsson phone (or any other AT compatible phone) connected using USB cable:
[gammu] device = /dev/ttyACM0 connection = at
Gammu configuration for Sony-Ericsson (or any other AT compatible phone) connected using bluetooth:
[gammu] device = B0:0B:00:00:FA:CE connection = blueat
Gammu configuration for phone which needs to manually adjust Bluetooth channel to use channel 42:
[gammu] device = B0:0B:00:00:FA:CE/42 connection = blueat
Gammu can be configured for multiple phones (however only one connection is used at one time, you can choose which one to use with --section parameter). Configuration for phones on three serial ports would look like following:
[gammu] device = /dev/ttyS0 connection = at [gammmu1] device = /dev/ttyS1 connection = at [gammmu2] device = /dev/ttyS2 connection = at
[GW]ammu