README.gigaset 14 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336
  1. GigaSet 307x Device Driver
  2. ==========================
  3. 1. Requirements
  4. ------------
  5. 1.1. Hardware
  6. --------
  7. This driver supports the connection of the Gigaset 307x/417x family of
  8. ISDN DECT bases via Gigaset M101 Data, Gigaset M105 Data or direct USB
  9. connection. The following devices are reported to be compatible:
  10. Bases:
  11. Siemens Gigaset 3070/3075 isdn
  12. Siemens Gigaset 4170/4175 isdn
  13. Siemens Gigaset SX205/255
  14. Siemens Gigaset SX353
  15. T-Com Sinus 45 [AB] isdn
  16. T-Com Sinus 721X[A] [SE]
  17. Vox Chicago 390 ISDN (KPN Telecom)
  18. RS232 data boxes:
  19. Siemens Gigaset M101 Data
  20. T-Com Sinus 45 Data 1
  21. USB data boxes:
  22. Siemens Gigaset M105 Data
  23. Siemens Gigaset USB Adapter DECT
  24. T-Com Sinus 45 Data 2
  25. T-Com Sinus 721 data
  26. Chicago 390 USB (KPN)
  27. See also http://www.erbze.info/sinus_gigaset.htm and
  28. http://gigaset307x.sourceforge.net/
  29. We had also reports from users of Gigaset M105 who could use the drivers
  30. with SX 100 and CX 100 ISDN bases (only in unimodem mode, see section 2.5.)
  31. If you have another device that works with our driver, please let us know.
  32. Chances of getting an USB device to work are good if the output of
  33. lsusb
  34. at the command line contains one of the following:
  35. ID 0681:0001
  36. ID 0681:0002
  37. ID 0681:0009
  38. ID 0681:0021
  39. ID 0681:0022
  40. 1.2. Software
  41. --------
  42. The driver works with ISDN4linux and so can be used with any software
  43. which is able to use ISDN4linux for ISDN connections (voice or data).
  44. Experimental Kernel CAPI support is available as a compilation option.
  45. There are some user space tools available at
  46. http://sourceforge.net/projects/gigaset307x/
  47. which provide access to additional device specific functions like SMS,
  48. phonebook or call journal.
  49. 2. How to use the driver
  50. ---------------------
  51. 2.1. Modules
  52. -------
  53. For the devices to work, the proper kernel modules have to be loaded.
  54. This normally happens automatically when the system detects the USB
  55. device (base, M105) or when the line discipline is attached (M101). It
  56. can also be triggered manually using the modprobe(8) command, for example
  57. for troubleshooting or to pass module parameters.
  58. The module ser_gigaset provides a serial line discipline N_GIGASET_M101
  59. which drives the device through the regular serial line driver. It must
  60. be attached to the serial line to which the M101 is connected with the
  61. ldattach(8) command (requires util-linux-ng release 2.14 or later), for
  62. example:
  63. ldattach GIGASET_M101 /dev/ttyS1
  64. This will open the device file, attach the line discipline to it, and
  65. then sleep in the background, keeping the device open so that the line
  66. discipline remains active. To deactivate it, kill the daemon, for example
  67. with
  68. killall ldattach
  69. before disconnecting the device. To have this happen automatically at
  70. system startup/shutdown on an LSB compatible system, create and activate
  71. an appropriate LSB startup script /etc/init.d/gigaset. (The init name
  72. 'gigaset' is officially assigned to this project by LANANA.)
  73. Alternatively, just add the 'ldattach' command line to /etc/rc.local.
  74. 2.2. Device nodes for user space programs
  75. ------------------------------------
  76. The device can be accessed from user space (eg. by the user space tools
  77. mentioned in 1.2.) through the device nodes:
  78. - /dev/ttyGS0 for M101 (RS232 data boxes)
  79. - /dev/ttyGU0 for M105 (USB data boxes)
  80. - /dev/ttyGB0 for the base driver (direct USB connection)
  81. You can also select a "default device" which is used by the frontends when
  82. no device node is given as parameter, by creating a symlink /dev/ttyG to
  83. one of them, eg.:
  84. ln -s /dev/ttyGB0 /dev/ttyG
  85. 2.3. ISDN4linux
  86. ----------
  87. This is the "normal" mode of operation. After loading the module you can
  88. set up the ISDN system just as you'd do with any ISDN card supported by
  89. the ISDN4Linux subsystem. Most distributions provide some configuration
  90. utility. If not, you can use some HOWTOs like
  91. http://www.linuxhaven.de/dlhp/HOWTO/DE-ISDN-HOWTO-5.html
  92. If this doesn't work, because you have some device like SX100 where
  93. debug output (see section 3.2.) shows something like this when dialing
  94. CMD Received: ERROR
  95. Available Params: 0
  96. Connection State: 0, Response: -1
  97. gigaset_process_response: resp_code -1 in ConState 0 !
  98. Timeout occurred
  99. you might need to use unimodem mode. (see section 2.5.)
  100. 2.4. CAPI
  101. ----
  102. If the driver is compiled with CAPI support (kernel configuration option
  103. GIGASET_CAPI, experimental) it can also be used with CAPI 2.0 kernel and
  104. user space applications. ISDN4Linux is supported in this configuration
  105. via the capidrv compatibility driver. The kernel module capidrv.ko must
  106. be loaded explicitly ("modprobe capidrv") if needed.
  107. 2.5. Unimodem mode
  108. -------------
  109. This is needed for some devices [e.g. SX100] as they have problems with
  110. the "normal" commands.
  111. If you have installed the command line tool gigacontr, you can enter
  112. unimodem mode using
  113. gigacontr --mode unimodem
  114. You can switch back using
  115. gigacontr --mode isdn
  116. You can also load the driver using e.g.
  117. modprobe usb_gigaset startmode=0
  118. to prevent the driver from starting in "isdn4linux mode".
  119. In this mode the device works like a modem connected to a serial port
  120. (the /dev/ttyGU0, ... mentioned above) which understands the commands
  121. ATZ init, reset
  122. => OK or ERROR
  123. ATD
  124. ATDT dial
  125. => OK, CONNECT,
  126. BUSY,
  127. NO DIAL TONE,
  128. NO CARRIER,
  129. NO ANSWER
  130. <pause>+++<pause> change to command mode when connected
  131. ATH hangup
  132. You can use some configuration tool of your distribution to configure this
  133. "modem" or configure pppd/wvdial manually. There are some example ppp
  134. configuration files and chat scripts in the gigaset-VERSION/ppp directory
  135. in the driver packages from http://sourceforge.net/projects/gigaset307x/.
  136. Please note that the USB drivers are not able to change the state of the
  137. control lines. This means you must use "Stupid Mode" if you are using
  138. wvdial or you should use the nocrtscts option of pppd.
  139. You must also assure that the ppp_async module is loaded with the parameter
  140. flag_time=0. You can do this e.g. by adding a line like
  141. options ppp_async flag_time=0
  142. to /etc/modprobe.conf. If your distribution has some local module
  143. configuration file like /etc/modprobe.conf.local,
  144. using that should be preferred.
  145. 2.6. Call-ID (CID) mode
  146. ------------------
  147. Call-IDs are numbers used to tag commands to, and responses from, the
  148. Gigaset base in order to support the simultaneous handling of multiple
  149. ISDN calls. Their use can be enabled ("CID mode") or disabled ("Unimodem
  150. mode"). Without Call-IDs (in Unimodem mode), only a very limited set of
  151. functions is available. It allows outgoing data connections only, but
  152. does not signal incoming calls or other base events.
  153. DECT cordless data devices (M10x) permanently occupy the cordless
  154. connection to the base while Call-IDs are activated. As the Gigaset
  155. bases only support one DECT data connection at a time, this prevents
  156. other DECT cordless data devices from accessing the base.
  157. During active operation, the driver switches to the necessary mode
  158. automatically. However, for the reasons above, the mode chosen when
  159. the device is not in use (idle) can be selected by the user.
  160. - If you want to receive incoming calls, you can use the default
  161. settings (CID mode).
  162. - If you have several DECT data devices (M10x) which you want to use
  163. in turn, select Unimodem mode by passing the parameter "cidmode=0" to
  164. the driver ("modprobe usb_gigaset cidmode=0" or modprobe.conf).
  165. If you want both of these at once, you are out of luck.
  166. You can also use /sys/class/tty/ttyGxy/cidmode for changing the CID mode
  167. setting (ttyGxy is ttyGU0 or ttyGB0).
  168. 2.7. Unregistered Wireless Devices (M101/M105)
  169. -----------------------------------------
  170. The main purpose of the ser_gigaset and usb_gigaset drivers is to allow
  171. the M101 and M105 wireless devices to be used as ISDN devices for ISDN
  172. connections through a Gigaset base. Therefore they assume that the device
  173. is registered to a DECT base.
  174. If the M101/M105 device is not registered to a base, initialization of
  175. the device fails, and a corresponding error message is logged by the
  176. driver. In that situation, a restricted set of functions is available
  177. which includes, in particular, those necessary for registering the device
  178. to a base or for switching it between Fixed Part and Portable Part
  179. modes.
  180. 3. Troubleshooting
  181. ---------------
  182. 3.1. Solutions to frequently reported problems
  183. -----------------------------------------
  184. Problem:
  185. You have a slow provider and isdn4linux gives up dialing too early.
  186. Solution:
  187. Load the isdn module using the dialtimeout option. You can do this e.g.
  188. by adding a line like
  189. options isdn dialtimeout=15
  190. to /etc/modprobe.conf. If your distribution has some local module
  191. configuration file like /etc/modprobe.conf.local,
  192. using that should be preferred.
  193. Problem:
  194. Your isdn script aborts with a message about isdnlog.
  195. Solution:
  196. Try deactivating (or commenting out) isdnlog. This driver does not
  197. support it.
  198. Problem:
  199. You have two or more DECT data adapters (M101/M105) and only the
  200. first one you turn on works.
  201. Solution:
  202. Select Unimodem mode for all DECT data adapters. (see section 2.5.)
  203. Problem:
  204. Messages like this:
  205. usb_gigaset 3-2:1.0: Could not initialize the device.
  206. appear in your syslog.
  207. Solution:
  208. Check whether your M10x wireless device is correctly registered to the
  209. Gigaset base. (see section 2.7.)
  210. 3.2. Telling the driver to provide more information
  211. ----------------------------------------------
  212. Building the driver with the "Gigaset debugging" kernel configuration
  213. option (CONFIG_GIGASET_DEBUG) gives it the ability to produce additional
  214. information useful for debugging.
  215. You can control the amount of debugging information the driver produces by
  216. writing an appropriate value to /sys/module/gigaset/parameters/debug, e.g.
  217. echo 0 > /sys/module/gigaset/parameters/debug
  218. switches off debugging output completely,
  219. echo 0x10a020 > /sys/module/gigaset/parameters/debug
  220. enables the standard set of debugging output messages. These values are
  221. bit patterns where every bit controls a certain type of debugging output.
  222. See the constants DEBUG_* in the source file gigaset.h for details.
  223. The initial value can be set using the debug parameter when loading the
  224. module "gigaset", e.g. by adding a line
  225. options gigaset debug=0
  226. to /etc/modprobe.conf, ...
  227. Generated debugging information can be found
  228. - as output of the command
  229. dmesg
  230. - in system log files written by your syslog daemon, usually
  231. in /var/log/, e.g. /var/log/messages.
  232. 3.3. Reporting problems and bugs
  233. ---------------------------
  234. If you can't solve problems with the driver on your own, feel free to
  235. use one of the forums, bug trackers, or mailing lists on
  236. http://sourceforge.net/projects/gigaset307x
  237. or write an electronic mail to the maintainers.
  238. Try to provide as much information as possible, such as
  239. - distribution
  240. - kernel version (uname -r)
  241. - gcc version (gcc --version)
  242. - hardware architecture (uname -m, ...)
  243. - type and firmware version of your device (base and wireless module,
  244. if any)
  245. - output of "lsusb -v" (if using an USB device)
  246. - error messages
  247. - relevant system log messages (it would help if you activate debug
  248. output as described in 3.2.)
  249. For help with general configuration problems not specific to our driver,
  250. such as isdn4linux and network configuration issues, please refer to the
  251. appropriate forums and newsgroups.
  252. 3.4. Reporting problem solutions
  253. ---------------------------
  254. If you solved a problem with our drivers, wrote startup scripts for your
  255. distribution, ... feel free to contact us (using one of the places
  256. mentioned in 3.3.). We'd like to add scripts, hints, documentation
  257. to the driver and/or the project web page.
  258. 4. Links, other software
  259. ---------------------
  260. - Sourceforge project developing this driver and associated tools
  261. http://sourceforge.net/projects/gigaset307x
  262. - Yahoo! Group on the Siemens Gigaset family of devices
  263. http://de.groups.yahoo.com/group/Siemens-Gigaset
  264. - Siemens Gigaset/T-Sinus compatibility table
  265. http://www.erbze.info/sinus_gigaset.htm
  266. 5. Credits
  267. -------
  268. Thanks to
  269. Karsten Keil
  270. for his help with isdn4linux
  271. Deti Fliegl
  272. for his base driver code
  273. Dennis Dietrich
  274. for his kernel 2.6 patches
  275. Andreas Rummel
  276. for his work and logs to get unimodem mode working
  277. Andreas Degert
  278. for his logs and patches to get cx 100 working
  279. Dietrich Feist
  280. for his generous donation of one M105 and two M101 cordless adapters
  281. Christoph Schweers
  282. for his generous donation of a M34 device
  283. and all the other people who sent logs and other information.