Gammu:Readme

From Gammu.org wiki

  • 1 Compiling under Borland C++ 3.1 for MS-DOS
  • 2 Compiling under DJGPP for MS-DOS
  • 3 Using source tarballs in Linux
    • 3.1 Compiling and installing from source tarballs
    • 3.2 Creating Debian packages
  • 4 Using ready packages in Linux
    • 4.1 RPM based distributions
    • 4.2 Debian
    • 4.3 Ubuntu
    • 4.4 Gentoo
    • 4.5 Arch Linux
  • 5 Installing binary version in Windows
  • 6 Compiling using MS Visual C++
    • 6.1 commercial version 6.0
    • 6.2 commercial version 7.0, 7.1 (.NET)
    • 6.3 free Visual C++ Express 2005
  • 7 Compiling using Borland C++
    • 7.1 free (for non commercial use) Borland C++ Builder 5/6 Personal
    • 7.2 free Borland C++ 5.5 command line tools
    • 7.3 Borland C++ X
  • 8 Compiling using CygWin for Windows
  • 9 Connecting to Symbian (Nokia and probably other)
  • 10 Connecting to Nokia without Symbian
    • 10.1 Cable
      • 10.1.1 DKU2 cable
      • 10.1.2 DKU5 cable
      • 10.1.3 ark3116 cable
    • 10.2 Infrared
    • 10.3 Bluetooth
    • 10.4 Flasher Cables
  • 11 Connecting to Ericsson / Siemens / Samsung / Alcatel
    • 11.1 Cable
    • 11.2 Infrared
    • 11.3 Bluetooth
  • 12 General connection notes
    • 12.1 Cables
    • 12.2 Infrared
    • 12.3 Bluetooth
  • 13 Configuration file options
    • 13.1 port
    • 13.2 model
    • 13.3 connection
    • 13.4 synchronizetime
    • 13.5 logfile
    • 13.6 logformat
    • 13.7 use_locking
    • 13.8 gammuloc
    • 13.9 startinfo
    • 13.10 gammucoding
    • 13.11 rsslevel
    • 13.12 UsePhoneDB
  • 14 Working with multiple phones

Return to Main page|Gammu main page

Compiling under Borland C++ 3.1 for MS-DOS

Non successfull

Compiling under DJGPP for MS-DOS

To get and install DJGPP you can try such steps:

OR

  • go directly into http://www.simtel.net
  • find section for getting DJGPP
  • download packages (or newer):
    • v2/readme.1st - Instructions for DJGPP setup
    • v2/faq230b.zip - The DJGPP Frequently Asked Questions
    • v2/djdev203.zip - The DJGPP Development kit
    • v2misc/csdpmi4b.zip - The DPMI Server
    • v2gnu/bnu210b.zip - The GNU Binary Utilities
    • v2gnu/gcc2952b.zip - The GNU C Compiler
    • v2gnu/mak279b.zip - The GNU Make Utility
  • unzip to one directory (let's say C:\DJGPP)
  • add to autoexec.bat these lines:
PATH C:\DJGPP\BIN;%PATH%
SET DJGPP=C:\DJGPP\DJGPP.ENV

If you have it, compiling is easy:

  • set CFLAGS and LDLIBS in cfg/Makefile.glo
  • simply use "make djgpp"

Please note, that DJGPP support gives serial cable connection and nothing more.

Return to Main page|Gammu main page

Using source tarballs in Linux

Compiling and installing from source tarballs

First you will need some tools available with developer libraries, if you want some functionality:

  1. MySQL - database functions
  2. BlueZ - BlueTooth

If you have everything, simply do such steps:

1. Download gammu from one of the mirrors

2. Uncompress the downloaded file :

$ tar xjvf gammu.tar.bz2

3. Enter the gammu directory:

$ cd gammu-*

4. Run the configure script:

$ ./configure

5. Compile the programm:

$ make

6. Install it as root:

$ su
# make install

Creating Debian packages

1. Download and unpack gammu tarball.

2. Get required build dependencies:

aptitude install debhelper libc6-dev libbluetooth1 libbluetooth1-dev autoconf fakeroot

3. Build it:

fakeroot debian/rules binary

Using ready packages in Linux

RPM based distributions

Some vendors already included Gammu, so you can use version they ship. At least SUSE and Mandriva have Gammu inside their distribution. If this does not apply, you can try luck with third party sources:

1. Download the RPM file (see mirrors)

2. Switch to root user:

$ su

3. Install the file

$ rpm -ivh gammu-*.rpm

Debian

Gammu and related are now officialy inside Debian: [1]

You can use packages built for Sid (Debian Unstable) too (you might have luck using them on other). Those are mostly in queue waiting for upload to official archives.

1. Add apt repository for Gammu:

$ echo deb http://debian.cihar.com/ unstable main | sudo tee -a /etc/apt/sources.list

2. Install it (you might also want to install Wammu from that repository):

$ sudo aptitude install gammu

If it all fails, try building from sources.

Ubuntu

You can try packages for Debian. However they will most likely not work so you will have to build from sources.

Gentoo

Gentoo contains ebuild for gammu, so you can just

$ emerge gammu

Arch Linux

Arch Linux contains pkgbuild in unsupported section, install as usual.


When you have program installed, you need to configure it, see documentation.

Return to Main page|Gammu main page

Installing binary version in Windows

Compiling using MS Visual C++

You will probably need additional SDKs:

After downloading and installing them into your system:

  • add include/library files to directories used by your compiler (add them AFTER compiler default directories).
  • enable options in Gammu/cfg/config.h (HAVE_MYSQL_MYSQL_H and BLUETOOTH_RF_SEARCHING)

commercial version 6.0

  • change parameters in /cfg/config.h
  • enter into /gammu/msvc6.mak directory
  • run gammu.dsw

commercial version 7.0, 7.1 (.NET)

  • change parameters in /cfg/config.h
  • enter into /gammu/msvc2003.mak directory
  • run gammu.vcproj

free Visual C++ Express 2005

  • set compiler to work with Platform SDK (see description)
  • change parameters in /cfg/config.h
  • enter into /gammu/msvc2005.mak directory
  • run gammu.vcproj

Compiling using Borland C++

free (for non commercial use) Borland C++ Builder 5/6 Personal

  • go into gammu/bcc.mak
  • check if there is subdirectory "output" (if not, create it)
  • run gammu.bpr

free Borland C++ 5.5 command line tools

  • go into gammu/bcc
  • check if there is subdirectory "output" (if not, create it)
  • execute "make -fgammu.mak" from command line

Borland C++ X

  • you need to create new makefile. It was added from box to some older Gammu versions too.

Compiling using CygWin for Windows

Not checked.

Return to Main page|Gammu main page

This page should generally explain, how you can connect your phone to PC.

If you know, what should be selected, you need to write it into the config file.

Connecting to Symbian (Nokia and probably other)

Before you will try connect to Gammu, you have to install gnapplet application in phone first.

Later steps depends on connection type. For example for Bluetooth use "bluerfgnapbus" connection and model "gnap" and device addresss as "port". You can read notes described below for infrared and Bluetooth too. Cables connections (DKE-2, DKU-2, etc.) are not supported by gnapplet now.

When you want to communicate with phone, enable medium (bluetooth, irda, etc.), run gnapplet in phone and use Gammu then.

Connecting to Nokia without Symbian

Cable

There are three main protocols used in cable connections:

  • MBUS (sometimes called M2BUS) - old, not recommended
  • FBUS - recommended
  • AT commands - limited, recommended for data calls

All phones have a connector under the battery (the exception is the Nokia 3210 - it's on right side of battery) - it's for FBUS and MBUS. This connector is only way for connecting to phone functions on Nokia 5510 (DKE-2 gives access to MP3 side only)

To use Gammu with it you will only need a simple converter and the pins description from Internet.

The alternative to cable working with one phone is kit - plug for phone from flasher (RJ45 or PS2) + compatible with it converter for serial port. There are many offers - it's enough to write for example "ps2 and cable and phone_model" in Google

Many phones have connector on bottom of phone. It's for FBUS (always), sometimes for AT commands and sometimes for MBUS:

  • Older phones had connector like in Nokia 6110. You can use FBUS and MBUS cable there. Original Nokia cables for these phones were called DAU9P. With Nokia 7110/6210/6310/6310i you can additionaly use DLR3/DLR3P cables too (they will not work with older models like Nokia 5110 or 6110) - you will have FBUS and AT commands. All of them don't need special drivers, because are designed to use with serial ports.
  • Nokia 9210 have connector working in FBUS and MBUS...but if you want to use FBUS with original and non-modified DLR-2L, you have to enable FBUS mode from netmonitor menu 31...but for enabling netmonitor you have to use MBUS cable (and MBUS is not supported by DLR-2L)
  • New phones have PopPort. It's for FBUS, MBUS the most often is not connected (see article from NokiaPort.de). You have AT commands in more expensive phones too.

For PopPort you have to connect cable with USB converter inside or not (it depends on phone model - new/more expensive models have USB converter on main board and cable is simple cable extension only).

  • cables for for phones without USB converter on phone main board
    • original DKU5 - Supported by Gammu in windows but unsupported in Linux (nobody wanted to make the kernel driver for it)
    • original CA42 - no info (probably very similiar to DKU5)
    • cloned DKU5 with PL2303 and other - The most often suported in Windows, sometimes in Linux (depends on quality of manufacturer driver)
  • for phones with USB converter on phone main board.
    • original DKU2 - Supported by Gammu in windows.
      There is easy driver in Gammu distribution for Linux too - it works quite enough with the most popular phones, adding support for more models need to add their ID only (because all USB processing is done by phone, you add phone product ID). It doesn't work with Nokia 6230 with firmware 5.xx.
      NOTE: this cable will not give access to phone functions in Nokia 3300
      For more info (both for Linux and Windows) see notes below.
    • original CA53 - no info (probably very similiar to DKU2)
    • ark3116 cable - see below

A little more about cables compatibility for Nokia phones: http://europe.nokia.com/nokia/0,,79898,00.html (probably all CA42 phones can be used with DKU5 cable and probably all CA53 phones can be used with DKU2)

Generally - Gammu doesn't have problems with serial port cables. Just enable read/write access to the serial port being used, set it as "port" in gammurc and set "connection" to right protocol.

There are notes in Net, that some 3rd party serial cables for 8210/8250 doesn't work with 5210, some from 8210 doesn't work with 2100. It can happen, if signals are in different places in both models. So, be carefull here. Please note, that during connection using serial cable you can have incorrect chars too:

  • (Linux) if you have wrong kernel options for serial port - for FBUS there should be support enabled for the best possible UART (16550 or something similiar, which is required to have 115200 and 16 bytes UART queue)
  • if port can't be set correctly to required speed (the most often 115200)
  • if you have something wrong with hardware (cable, phone)

A little more about USB support in Linux: http://www.linux-usb.org/

DKU2 cable

for Linux:

  • build and install the kernel module -- this is for 2.6 *only*, it will not work on a 2.4 kernel. The Makefile uses the standard convention of /usr/src/linux-2.6 as the kernel source home; if you already have that, simply type "make; make install" and you're done.

NOTE: if you're on Fedora Core 3 and have no clue how to prepare your kernel source for building external modules, follow step #1 in my HowTo for the rt2x00 project on Sourceforge: http://sourceforge.net/forum/message.php?msg_id=2959689

  • Compile gammu as normal (./configure; make)
  • Plug in your phone, and look in /var/log/messages for the device that was registered as "FBUS". It should look like this:
  kernel: Nokia FBUS Port:
kernel: Nokia DKU2 1-2:1.10: Nokia 7600/6230 DKU2 driver converter detected
kernel: usb 1-2: Nokia 7600/6230 DKU2 driver converter now attached to ttyUSB0

NOTE: there are two drivers that fight for the AT side of your Nokia -- the stock "cdc_acm" driver and the "nokia_dku2" module. So, if cdc_acm got there first and created ttyACM0, then most likely your phone will be ttyUSB0. If the nokia_dku2 got there first, then most likely your AT will be ttyUSB0, and the FBUS port ttyUSB1. I've had it happen both ways.

This can make sometimes problems (report from other user):

Problem: My Nokia 6230 phone does weird things - when I run smsd and receive new message, phone just hangs, restarts and message isn't saved in mysql, but ofcoure is saved next time I run smsd, but the same happens again if I receive message. Actually noticed the same when phone said - battery is full (or any other action is done with phone), connection with smsd droped.
Solution: Ok, problem seems to be solved, seems that linux acm module tries to make serial connection to phone and try to do something and when connection through fbus and serial is done at the same time, everything hangs. - just removed acm module and now serial and fbus connection is made through nokia_dku2 module.

  • make sure /dev/ttyUSB* is owned by the user running gammu! chown/chmod it as needed. On my FC3 machine I added the proper configurations to /etc/security/console.perms to chown it to the logged in user for me:
  Under this line: <raw1394>=/dev/raw1394
Add this line: <usbdev>=/dev/ttyACM* /dev/ttyUSB*
  Under this line: <console>  0600 <raw1394>    0600 root
Add this line: <console> 0600 <usbdev> 0600 root

Log out and log back in and it will work properly for you forever.

  • Configure your .gammurc:
[gammu]
port = /dev/ttyUSB0
connection = dku2
  • run gammu --identify! At this point is should be working.

for Windows:

  1. Download driver from nokia.com (http://europe.nokia.com/nokia/0,,81914,00.html or other)
  2. Install driver
  3. (for some phones like N6111) Unlock phone keypad - it must be unlocked all time
  4. Connect phone to cable, cable to pc
  5. (for some phones like N6111) Select default mode in phone
  6. Phone will be installed
  7. Gammurc:
[gammu]
Connection = dku2

DKU5 cable

for Windows:

  • install driver from Nokia (latest 1.24 version). It's for Atmel based cables. Other drivers and cables with other chipsets sold as original DKU5 were not tested.
  • enter Control Panel and properties to created "Port 1 on Nokia adapter" device
  • set "bits per second" to 115200
  • set connection "dku5" without device (for FBUS) or "at..." with Port 1 device name (for AT) in Gammu config file
  • connect cable to phone

Sometimes it happen, that first connection try isn't successfull. Without disconnecting cable and phone try again. It should work then.

When cable will switch from AT to FBUS and you will want to use AT again, you have to reconnect phone and cable (switching from FBUS to AT is not possible).

ark3116 cable

The ark3116 driver for 2nd-source cable (original does not exist) is included in the Linux-kernel since 2.6.17rc5.

Infrared

There are two methods: direct communication with the phone, or using operating system functions to communicate with it.

The first method ("infrared" in gammurc) is obsolete, but required with 6110/6130/6150 and compatible. Also Nokia 8210 uses it, when entering infrared using the 2 player mode.

In Linux disable infrared in kernel, connect your infrared device to serial port (other irda dongles than conenected to serial port won't be supported in this mode) and try Gammu with "infrared" connection. If doesn't work, there will be required some modifications of sources. Please contact authors.

In Windows ANY infrared device can be assigned to serial port with driver written by Jan Kiszka.

The second method ("irda" in gammurc) is much better. It's compatible with all modern operating systems (under Linux, infrared must be enabled in the kernel). This is called socket infrared and is used in all new phones.

Note: in many new models (like Nokia 6230 or 6230i) you have to have keypad unlocked during all connection time. Simply activate Bluetooth, infrared (or whatever you use) and enter phone menu before you will try to connect with Gammu.

Note: some infrared modules for PC require setting non standard parameters (for example, lowering max. speed to 115200) for communicating with phones. This is not Gammu issue then ! Example: for Stir 4200 based dongle you have to set in Control Panel

Infrared transceiver type - vishay 6101E
Min. Turn-around time - 0.5 ms (instead of default 1 ms)
Speed enable - 115200 (instead of default 4Mbps)

Example of using socket infrared under Linux (based on USB dongle):

  1. compile the kernel with USB and infrared protocols (this is already done in most modern distributions).
  2. if necessary, insert USB module (e.g. modprobe irda-usb) (in most modern distributions, this shouldn't be necessary).
  3. use irattach irda0 -s or similiar, to set up the infrared port.
  4. enable read/write access to the infrared port (/dev/ircomm0, or whatever) with the following command:
    chmod ugo+rw /dev/ircomm0
    (This step may or may not be necessary, depending on the way the distribution's configured.)
  5. set "connection" in gammurc to "irda", "port" to "/dev/ircomm0" (or the relevant infrared port)

A little more about infrared in Linux is here: http://www.hpl.hp.com/personal/Jean_Tourrilhes/IrDA/IrDA.html

Bluetooth

Works OK in all situations.

Note: in many new models (like Nokia 6230 or 6230i) you have to have keypad unlocked during all connection time. Simply activate Bluetooth, infrared (or whatever you use) and enter phone menu before you will try to connect with Gammu

Note: some old Nokias (6310i with old firmware and so on) need to use special connections (for example "bluerfphonet" instead of "bluephonet").

Example of using USB dongle for Linux (BlueZ stack): (Note: most of this needs to be done as the superuser - i.e., root)

  1. compile the kernel with USB and Bluetooth - don't use the bluetooth setting in the USB section! (this is already done in most modern distributions)
  2. if necessary, load the kernel driver (modprobe hci_usb) (in most modern distributions, you shouldn't need to do this)
  3. use hciconfig hci0 up to enable the dongle
  4. create a text file /etc/bluetooth/givepin with the following contents:
    #!/bin/sh
    echo "PIN:5432"
  5. change the file permissions to make it executable:
    chmod a+x /etc/bluetooth/givepin
  6. in /etc/bluetooth/hcid.conf set "pin_helper" to "/etc/bluetooth/givepin;"
  7. execute hcid to send options from hcid.conf to bluetooth device
  8. do hcitool scan to get the phone address and enter this as the "device" parameter in gammurc. Set protocol to "bluephonet" or whatever is relevant for your setup (see the Connection section of the config file for details on this)
  9. during first connection give PIN 5432 in phone
  10. use "bluephonet" or "bluerfphonet" or "blueat" connections (with or without device address in "device")

A little more about Bluez is here:

In Windows there are two ways:

  1. using emulated serial ports for connecting to concrete phone services. It was used by old Bluetooth stacks (like WidComm) or can be set with Microsoft stack (Windows XP SP2, Windows 2003 and later). Not recommended. To use it you need to pair phone with PC, assign some phone service to serial port, give it as "device" and use correct "*blue" (like "phonetblue") connection
  2. using Microsoft stack (Windows XP SP2, Windows 2003 and later) to direct connection. Recommended.
    1. pair phone with computer using "Bluetooth devices" in Windows Control Panel
    2. use "bluephonet" (for older phones there could "bluerfphonet" instead of "bluephonet" required) or "blueat" connections (with or without device address in "device")

Flasher Cables

Flasher cables are different from standard data cables. They connect to the parallel (LPT) port and allow you to read from and write to the phone's internal flash memory. Using the correct software (called a flasher) and a flasher cable, you can upgrade the phone's firmware to a more recent version. Gammu, as user software, doesn't support flashing.

There's plenty of information about flashing and flasher equipment on the web - using a search engine, with terms like flasher, mobile, firmware, etc should turn some up.

Connecting to Ericsson / Siemens / Samsung / Alcatel

Cable

Get serial cable for the appropriate model, plug it into the phone and in a free serial port of the PC. In gammu, set the correct port ("COM1:" .. "COM9:" in Windows, "/dev/ttyS*" in Linux). Set "connection=at115200" (or lower) and "model=at". You can also try "model=obex".

Infrared

You can map your infrared connection to a virtual COM port in Win9x and XP. Then give "port=COM4:" (or check the correct port in Control Panels/Infrared transfer) and the connection will look like normal serial connection. Continue as above.

If you wish to use true infrared connection, follow the steps in the Nokia answer above.

Bluetooth

See Nokia answer above.

General connection notes

Cables

  • New Nokia protocol for FBUS/DAU9P
    Connection "fbus"
    Port type serial
  • New Nokia protocol for DLR3/DLR3P
    Connection "fbusdlr3"/"dlr3"
    Port type serial
  • New Nokia protocol for DKU2 (and phone without USB chip like 6230
    Connection "dku2phonet"/"dku2"
    Port type dku2
  • New Nokia protocol for DKU5 (and phone with USB chip like 5100
    Connection "dku5fbus"/"dku5"
    Port type dku5
  • New Nokia protocol for PL2303 USB cable (and phone with USB chip like 5100)
    Connection "fbuspl2303"
    Port type usb
  • Old Nokia protocol for MBUS/DAU9P
    Connection "mbus"
    Port type serial
  • AT commands for DLR3, DKU2, DKU5 or other AT compatible cable (8 bits, None parity, no flow control, 1 stop bit). Used with Nokia, Alcatel, Siemens, etc.
    Connection "at", optionally followed by desired speed, such as "at19200" or "at115200"
    Port type serial

Infrared

  • Nokia protocol for infrared with Nokia 6110/6130/6150
    Connection "fbusirda"/"infrared"
    Port type serial
  • Nokia protocol for infrared with other Nokia models
    Connection "irdaphonet"/"irda"
    Port type irda
  • AT commands for infrared. Used with Nokia, Alcatel, Siemens, etc.
    Connection "irdaat" (under Windows) or "at" (under Linux)
    Port type irda
  • OBEX for infrared
    Connection "irdaobex"
    Port type irda
    Model "obex"

Bluetooth

  • Nokia protocol with serial port set in BT stack (WidComm, other) from adequate service and Nokia 6210
    Connection "fbusblue"
    Port type serial
  • Nokia protocol with serial port set in BT stack (WidComm, other) from adequate service and other Nokia models
    Connection "phonetblue"
    Port type serial
  • Nokia protocol for Bluetooth stack with Nokia 6210
    Connection "bluerffbus"
    Port type BT
  • Nokia protocol for Bluetooth stack with DCT4 Nokia models, which don't inform about services correctly (6310, 6310i with firmware lower than 5.50, 8910,..)
    Connection "bluerfphonet"
    Port type BT
  • Nokia protocol for Bluetooth stack with other DCT4 Nokia models
    Connection "bluephonet"
    Port type BT
  • AT commands for Bluetooth stack and 6210 / DCT4 Nokia models, which don't inform about BT services correctly (6310, 6310i with firmware lower than 5.50, 8910,..)
    Connection "bluerfat"
    Port type BT
  • AT commands for Bluetooth stack with other phones (Siemens, other Nokia,etc.)
    Connection "blueat"
    Port type BT
  • OBEX for Bluetooth stack with DCT4 Nokia models, which don't inform about BT services correctly (6310, 6310i with firmware lower than 5.50, 8910,...)
    Connection "bluerfobex"
    Port type BT
  • OBEX for Bluetooth stack with other phones (Siemens, other Nokia, etc.)
    Connection "blueobex"
    Port type BT
    Model "obex"

Return to Main Page - Gammu:Main Page

Configuration file options

If you know, how to generally connect your phone to PC, it's time to write it into configuration file. For start here is a sample configuration file:

[gammu]
port = com8:
model = 6110
connection = fbusblue
synchronizetime = yes
logfile = gammulog
logformat = textall
use_locking = yes
gammuloc = locfile
startinfo = yes
gammucoding = utf8
rsslevel = teststable
usephonedb = yes

Configuration file can be located either in your home directory (this location is prefered) or can be configured for whole system. The location of the global configuration file depends on which system you use.

Location of the Global Configuration File for Windows:

  • Located in the directory where the gammu.exe file located. This is normally in the gammu installation directory.
  • The filename of the configuration file is gammurc. Note: there is no extension on the filename (i.e *.ini, *.cfg, and so on).
  • Make a backup of the gammurc file (e.g. gammurc-bak) before making experimental changes.

Location of the Global Configuration File for Linux:

  • Located in /etc/gammurc or ~/.gammurc

port

The value of this parameter can be:

  • it can be empty - for irda, dku2, dku5 connection in Windows
  • 'COM*:' - for serial connection in Windows (eg. 'COM1:')
  • '/dev/ttyS*' (or '/dev/tts/**' with DevFS) - for serial connection in Linux (eg. '/dev/ttyS0')
  • '/dev/ircomm*' - for infrared connection in Linux (eg. '/dev/ircomm0')
  • '/dev/ttyUSB*' or '/dev/ttyACM*' - for dku2 connection in Linux
  • 'XX:XX:XX:XX:XX:XX' (bluetooth address) for bluetooth connection (eg. '00:0A:D9:15:AA:81')

model

Use only when Gammu doesn't recognize your phone model. Example values: "6110", "6150", "6210", "8210".

connection

For information on which connection parameter to use, see the Methods of connecting to phone page

Valid parameters are:
mbus, fbus, fbuspl2303, dlr3, fbusdlr3, dku5, dku5fbus, dku2,dku2phonet, fbusblue, phonetblue, mrouterblue, blueobex, bluephonet, blueat, bluerfobex, bluerffbus, bluerfphonet, bluerfat, infrared, fbusirda, irda, irdaphonet, irdaat, irdaobex, at*

You can find and exchange working configurations in our phone databases

synchronizetime

Use this if you want to set the phone's time from the computer's time when gammu first connects to the phone. Do not use this option when you want to reset the phone during the connection (some phones need the time set again after a restart)

logfile

Use this when you want gammu to keep a record of communication in a log file.

logformat

What debug info and format should be used:

  • "nothing" - no debug level (default)
  • "text" - transmission dump in text format
  • "textall" - all possible info in text format
  • "errors" - errors in text format
  • "binary" - transmission dump in binary format

use_locking

Under Unix/Linux set this to "yes" if you want to lock the device being used, to prevent other applications trying to use it. (This is probably not important on a single-user system, unless you use the same serial port for a modem and some other program could try and dial out while you're using gammu.) Under win32 this option is ignored.

gammuloc

Name of localisation file. Localisation is chosen automatically if you have set locales and properly installed Gammu.

See How to make national version of Gammu

startinfo

This option allows you to set whether you want to see a message on the phone screen or if the phone's backlight should come on for a moment when gammu connects to it. Set this to "yes" to see a message on the phone. With this option set, the phone won't beep when the connection is initiated.

gammucoding

Forces use of a specified codepage (in win32 - for example "1250" will force CP1250) or UTF8 (in Linux - "utf8")

rsslevel

Should Gammu connect to www.mwiacek.com and check for new versions ?

if yes, there will be taken Image:rss.png http://www.mwiacek.com/gsm/soft/gammu.rss file, read latest version numbers and (if any exist) displayed info to user on each application startup.

parameter value:

  1. "teststable" - check for latest stable and test versions
  2. "stable" - check for latest stable versions

No private data are sent to server, Internet connection to http://www.mwiacek.com on port 80 required. By default option not active

UsePhoneDB

Should Gammu connect to http://www.gammu.org and check for latest firmware versions for device ?

if yes (value "yes"), there will be taken http://www.gammu.org/support/phones/phonedbxml.php?model=x file, read all phone details from it and (if any higher firmware exist) displayed info to user on each application startup. No private data are sent to server, Internet connection to http://www.gammu.org on port 80 required. By default option not active

Working with multiple phones

You can create several section in configuration file:

[gammu]
port = /dev/ttyS0

[gammmu1]
port = /dev/ttyS1

[gammmu2]
port = /dev/ttyS2

...

And then just call

gammu N --any-command

Where N is section number you want to use.