Gigaset ISDN Driver For Linux

external links

about the project

The aim of this project is the development of Linux device drivers and user space programs for the Siemens Gigaset 307x ISDN DECT base (and successors).

The drivers connect the base to the Linux system, either through a direct USB connection or through one of the DECT data devices M101 (serial) or M105 (USB). They provide integration with the Linux ISDN subsystem for making ISDN connections through the base, as well as character devices for direct access to its AT command interface.

User space programs provide access to the device configuration, journal log, and additional features like SMS.

current status (2008-01-26)

Since Linux kernel release 2.6.21, all Gigaset drivers are part of the standard kernel. They support the direct USB connection as well as DECT devices, outgoing and incoming calls, HDLC (data) and transparent (voice) connections. All drivers are still based on isdn4linux.

In release 2.6.17 through 2.6.20, only the drivers for the USB connected devices (bases and M105 / Sinus data 2) are part of the standard Linux kernel. There is an adapted gigaset-driver package (version 1.0.0) to support systems where the kernel already contains the base driver modules. It provides the driver for the serial devices (M101 / Sinus data 1) and configuration scripts for SuSE users.

Driver release 0.5.2 is still available for installation on older kernels. It works on Linux kernels 2.4 and 2.6.4 through 2.6.16. As the drivers compile on recent 2.2 kernels, you might also get them to work on older kernels.

supported devices

The following table lists the devices known to work with this release.

Siemens product	compatible products
Gigaset 3070 isdn	Sinus 45 isdn (Deutsche Telekom) Vox Chicago 390 ISDN (KPN Telecom)
Gigaset 3075 isdn	Sinus 45 AB isdn (Deutsche Telekom)
Gigaset 4170 isdn	Sinus 721 X (Deutsche Telekom)
Gigaset 4175 isdn	Sinus 721 XA (Deutsche Telekom)
Gigaset SX255isdn
Gigaset SX353isdn
Gigaset M105 data Gigaset USB Adapter DECT	Sinus 45 data 2 (Deutsche Telekom) Sinus 721 data Chicago 390 USB (KPN Telecom)
Gigaset M101 data	Sinus 45 data 1 (Deutsche Telekom)

The following devices will probably work, too, although we don't have any reports on them so far. If you own one of these, please do let us know about your success or any problems you may encounter:

Siemens product	compatible products
Gigaset SX205isdn	Sinus 721 X SE (Deutsche Telekom)
Gigaset SX303isdn

There is also limited support (unimodem mode only) for using the DECT data devices with the following ISDN DECT bases:

Siemens product	compatible products
Gigaset CX100isdn	Sinus 721 (Deutsche Telekom)
Gigaset SX100isdn	Sinus 721 Komfort (Deutsche Telekom)
Gigaset SX150isdn
Gigaset CX203isdn
Gigaset CX253isdn	Sinus 721 PA (Deutsche Telekom)
Gigaset SLX740isdn	Sinus 721 MMS (Deutsche Telekom)

The Gigaset M34 / Sinus 702 data USB adapter does not work with these drivers. Its USB interface is completely different from that of the M105. The prospects for supporting this device are currently rather dim, as Siemens so far hasn't shared any information on its interface with our team.

We lack information about other models (in particular, the newer CX 34x / SX 44x / Sinus 722 series bases) so we cannot say whether they will work with our drivers. If you own such a beast you are welcome to try them and report the results.

how to install the driver

We recommend running a current Linux kernel (release 2.6.21 or later) which already includes the drivers. This ensures you'll have all the latest enhancements and bugfixes.

If you must use the devices with an older kernel, you can find matching sources, source rpm packages, and some binary packages at the project file list.

kernel 2.6.21 and later

All major distributions ship a kernel with the Gigaset drivers compiled as modules, so you don't have to do anything.

If you compile a kernel yourself, you can select the Gigaset drivers you want built, and whether you want them built as modules or linked directly into the kernel, in the drivers' kernel configuration section:

Device Drivers
    ---> ISDN Support
        ---> Old ISDN4Linux (deprecated)
            ---> Siemens Gigaset support (isdn)

There you can also change the two build options, GIGASET_DEBUG (to enable debug messages) and GIGASET_UNDOCREQ (to enable extended M105 commands not documented by Siemens).

rpm packages

You can only use binary packages matching your kernel version and distribution. I.e. use gigaset-driver-0.5.2-1-suse90.i586.rpm and gigaset-modules-2.4.21-297-default-0.5.2-1-suse90.i586.rpm iff you use SuSE 9.0 and uname -r prints 2.4.21-297-default.

For installing an rpm package, you can type rpm -ihv NAME.i586.rpm, for upgrading to a newer version, use rpm -Uhv NAME.i586.rpm. Please have a look at your documentation directory (e.g. /usr/share/doc/packages/gigaset-driver) for information about configuration of the drivers.

Note that the former driver package is split into a driver package and a kernel module package, which allows installation of modules for different kernels (and avoids a dirty hack regarding the release number). There is also a separate package for the command line tools gigacontr and gigaconf, now.

source rpm

If you want to create rpm packages from the source rpm, you should ensure to have a file .rpmmacros containing a suitable %_topdir definition in your home directory:

cd
echo "%_topdir $HOME/rpm" >> .rpmmacros
mkdir rpm
cd rpm
mkdir BUILD RPMS SOURCES SPECS SRPMS

For building the rpm packages ensure to have installed the usual development tools (as gcc and GNU make) and the kernel sources (and kernel symbols for SuSE 9.1 or later) and execute

rpmbuild --rebuild NAME.src.rpm

or if you need to configure the M105 (THIS IS HIGHLY EXPERIMENTAL; needed only for gigaset-driver)

rpmbuild --rebuild NAME.src.rpm --with undoc

Note that you must install the driver before you can build the front-end tools gigacontr and gigaconf (package gigaset-frontend).

You can install the rpm packages (~/rpm/RPMS/) as described above.

compiling from the sources

If you have to compile the sources, get one of the tar archives, unpack it with tar xzvf NAME.tar.gz or tar xjvf NAME.tar.bz2 and follow the instructions from the README file (driver) in the gigaset-driver-0.5.2 directory, the README file (driver, kernel 2.6.17+) in the gigaset-driver-1.0.0 directory, or the README file (front-end) in the gigaset-frontend-0.5.3 directory.