README.gigaset 13 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330
  1. GigaSet 307x Device Driver
  2. ==========================
  3. 1. Requirements
  4. ------------
  5. 1.1. Hardware
  6. --------
  7. This release 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.4.)
  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. CAPI4Linux support is planned but not yet available.
  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.
  89. Your distribution should provide some configuration utility.
  90. 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 recent 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:
  100. 2.4. Unimodem mode
  101. -------------
  102. This is needed for some devices [e.g. SX100] as they have problems with
  103. the "normal" commands.
  104. If you have installed the command line tool gigacontr, you can enter
  105. unimodem mode using
  106. gigacontr --mode unimodem
  107. You can switch back using
  108. gigacontr --mode isdn
  109. You can also load the driver using e.g.
  110. modprobe usb_gigaset startmode=0
  111. to prevent the driver from starting in "isdn4linux mode".
  112. In this mode the device works like a modem connected to a serial port
  113. (the /dev/ttyGU0, ... mentioned above) which understands the commands
  114. ATZ init, reset
  115. => OK or ERROR
  116. ATD
  117. ATDT dial
  118. => OK, CONNECT,
  119. BUSY,
  120. NO DIAL TONE,
  121. NO CARRIER,
  122. NO ANSWER
  123. <pause>+++<pause> change to command mode when connected
  124. ATH hangup
  125. You can use some configuration tool of your distribution to configure this
  126. "modem" or configure pppd/wvdial manually. There are some example ppp
  127. configuration files and chat scripts in the gigaset-VERSION/ppp directory
  128. in the driver packages from http://sourceforge.net/projects/gigaset307x/.
  129. Please note that the USB drivers are not able to change the state of the
  130. control lines (the M105 driver can be configured to use some undocumented
  131. control requests, if you really need the control lines, though). This means
  132. you must use "Stupid Mode" if you are using wvdial or you should use the
  133. nocrtscts option of pppd.
  134. You must also assure that the ppp_async module is loaded with the parameter
  135. flag_time=0. You can do this e.g. by adding a line like
  136. options ppp_async flag_time=0
  137. to /etc/modprobe.conf. If your distribution has some local module
  138. configuration file like /etc/modprobe.conf.local,
  139. using that should be preferred.
  140. 2.5. Call-ID (CID) mode
  141. ------------------
  142. Call-IDs are numbers used to tag commands to, and responses from, the
  143. Gigaset base in order to support the simultaneous handling of multiple
  144. ISDN calls. Their use can be enabled ("CID mode") or disabled ("Unimodem
  145. mode"). Without Call-IDs (in Unimodem mode), only a very limited set of
  146. functions is available. It allows outgoing data connections only, but
  147. does not signal incoming calls or other base events.
  148. DECT cordless data devices (M10x) permanently occupy the cordless
  149. connection to the base while Call-IDs are activated. As the Gigaset
  150. bases only support one DECT data connection at a time, this prevents
  151. other DECT cordless data devices from accessing the base.
  152. During active operation, the driver switches to the necessary mode
  153. automatically. However, for the reasons above, the mode chosen when
  154. the device is not in use (idle) can be selected by the user.
  155. - If you want to receive incoming calls, you can use the default
  156. settings (CID mode).
  157. - If you have several DECT data devices (M10x) which you want to use
  158. in turn, select Unimodem mode by passing the parameter "cidmode=0" to
  159. the driver ("modprobe usb_gigaset cidmode=0" or modprobe.conf).
  160. If you want both of these at once, you are out of luck.
  161. You can also use /sys/class/tty/ttyGxy/cidmode for changing the CID mode
  162. setting (ttyGxy is ttyGU0 or ttyGB0).
  163. 2.6. M105 Undocumented USB Requests
  164. ------------------------------
  165. The Gigaset M105 USB data box understands a couple of useful, but
  166. undocumented USB commands. These requests are not used in normal
  167. operation (for wireless access to the base), but are needed for access
  168. to the M105's own configuration mode (registration to the base, baudrate
  169. and line format settings, device status queries) via the gigacontr
  170. utility. Their use is controlled by the kernel configuration option
  171. "Support for undocumented USB requests" (CONFIG_GIGASET_UNDOCREQ). If you
  172. encounter error code -ENOTTY when trying to use some features of the
  173. M105, try setting that option to "y" via 'make {x,menu}config' and
  174. recompiling the driver.
  175. 3. Troubleshooting
  176. ---------------
  177. 3.1. Solutions to frequently reported problems
  178. -----------------------------------------
  179. Problem:
  180. You have a slow provider and isdn4linux gives up dialing too early.
  181. Solution:
  182. Load the isdn module using the dialtimeout option. You can do this e.g.
  183. by adding a line like
  184. options isdn dialtimeout=15
  185. to /etc/modprobe.conf. If your distribution has some local module
  186. configuration file like /etc/modprobe.conf.local,
  187. using that should be preferred.
  188. Problem:
  189. Your isdn script aborts with a message about isdnlog.
  190. Solution:
  191. Try deactivating (or commenting out) isdnlog. This driver does not
  192. support it.
  193. Problem:
  194. You have two or more DECT data adapters (M101/M105) and only the
  195. first one you turn on works.
  196. Solution:
  197. Select Unimodem mode for all DECT data adapters. (see section 2.4.)
  198. Problem:
  199. You want to configure your USB DECT data adapter (M105) but gigacontr
  200. reports an error: "/dev/ttyGU0: Inappropriate ioctl for device".
  201. Solution:
  202. Recompile the usb_gigaset driver with the kernel configuration option
  203. CONFIG_GIGASET_UNDOCREQ set to 'y'. (see section 2.6.)
  204. 3.2. Telling the driver to provide more information
  205. ----------------------------------------------
  206. Building the driver with the "Gigaset debugging" kernel configuration
  207. option (CONFIG_GIGASET_DEBUG) gives it the ability to produce additional
  208. information useful for debugging.
  209. You can control the amount of debugging information the driver produces by
  210. writing an appropriate value to /sys/module/gigaset/parameters/debug, e.g.
  211. echo 0 > /sys/module/gigaset/parameters/debug
  212. switches off debugging output completely,
  213. echo 0x10a020 > /sys/module/gigaset/parameters/debug
  214. enables the standard set of debugging output messages. These values are
  215. bit patterns where every bit controls a certain type of debugging output.
  216. See the constants DEBUG_* in the source file gigaset.h for details.
  217. The initial value can be set using the debug parameter when loading the
  218. module "gigaset", e.g. by adding a line
  219. options gigaset debug=0
  220. to /etc/modprobe.conf, ...
  221. Generated debugging information can be found
  222. - as output of the command
  223. dmesg
  224. - in system log files written by your syslog daemon, usually
  225. in /var/log/, e.g. /var/log/messages.
  226. 3.3. Reporting problems and bugs
  227. ---------------------------
  228. If you can't solve problems with the driver on your own, feel free to
  229. use one of the forums, bug trackers, or mailing lists on
  230. http://sourceforge.net/projects/gigaset307x
  231. or write an electronic mail to the maintainers.
  232. Try to provide as much information as possible, such as
  233. - distribution
  234. - kernel version (uname -r)
  235. - gcc version (gcc --version)
  236. - hardware architecture (uname -m, ...)
  237. - type and firmware version of your device (base and wireless module,
  238. if any)
  239. - output of "lsusb -v" (if using an USB device)
  240. - error messages
  241. - relevant system log messages (it would help if you activate debug
  242. output as described in 3.2.)
  243. For help with general configuration problems not specific to our driver,
  244. such as isdn4linux and network configuration issues, please refer to the
  245. appropriate forums and newsgroups.
  246. 3.4. Reporting problem solutions
  247. ---------------------------
  248. If you solved a problem with our drivers, wrote startup scripts for your
  249. distribution, ... feel free to contact us (using one of the places
  250. mentioned in 3.3.). We'd like to add scripts, hints, documentation
  251. to the driver and/or the project web page.
  252. 4. Links, other software
  253. ---------------------
  254. - Sourceforge project developing this driver and associated tools
  255. http://sourceforge.net/projects/gigaset307x
  256. - Yahoo! Group on the Siemens Gigaset family of devices
  257. http://de.groups.yahoo.com/group/Siemens-Gigaset
  258. - Siemens Gigaset/T-Sinus compatibility table
  259. http://www.erbze.info/sinus_gigaset.htm
  260. 5. Credits
  261. -------
  262. Thanks to
  263. Karsten Keil
  264. for his help with isdn4linux
  265. Deti Fliegl
  266. for his base driver code
  267. Dennis Dietrich
  268. for his kernel 2.6 patches
  269. Andreas Rummel
  270. for his work and logs to get unimodem mode working
  271. Andreas Degert
  272. for his logs and patches to get cx 100 working
  273. Dietrich Feist
  274. for his generous donation of one M105 and two M101 cordless adapters
  275. Christoph Schweers
  276. for his generous donation of a M34 device
  277. and all the other people who sent logs and other information.