patch-2.0.31 linux/Documentation/isdn/README
Next file: linux/Documentation/isdn/README.HiSax
Previous file: linux/Documentation/isdn/INTERFACE
Back to the patch index
Back to the overall index
- Lines: 267
- Date:
Mon Aug 4 17:33:59 1997
- Orig file:
v2.0.30/linux/Documentation/isdn/README
- Orig date:
Fri Jun 7 06:02:39 1996
diff -u --recursive --new-file v2.0.30/linux/Documentation/isdn/README linux/Documentation/isdn/README
@@ -27,7 +27,14 @@
subscribe isdn4linux <your_email_address>
To write to the mailing-list, write to isdn4linux@hub-wue.franken.de
+
+ This mailinglist is bidirectionally gated to the newsgroup
+
+ de.alt.comm.isdn4linux
+ There is also a well maintained FAQ (both english and german) available
+ at ftp.franken.de in /pub/isdn4linux/FAQ/
+ This FAQ is also available at http://www.lrz-muenchen.de/~ui161ab/www/isdn/
1.1 Technical details
@@ -53,7 +60,7 @@
A raw-control-device with the following functions:
write: raw D-channel-messages (format: depends on driver).
read: raw D-channel-messages (format: depends on driver).
- ioctl: depends on driver, for the ICN-driver, the base-address of
+ ioctl: depends on driver, i.e. for the ICN-driver, the base-address of
the ports and the shared memory on the card can be set and read
also the boot-code an the protocol software can be loaded into
the card.
@@ -89,6 +96,7 @@
ATI Return "ISDN for Linux...".
ATI0 "
ATI1 "
+ ATI2 Report of last connection.
ATO On line (data mode).
ATQ0 Enable result codes (default).
ATQ1 Disable result codes (default).
@@ -99,7 +107,7 @@
ATZ Load registers and EAZ/MSN from Profile.
AT&Bx Set Send-Packet-size to x (max. 4000)
The real packet-size may be limited by the
- low-level-driver used. i.e.: the Teles-Module-
+ low-level-driver used. i.e.: the HiSax-Module-
limit is 2000. You will get NO Error-Message,
if you set it to higher Values, because at the
time of giving this command the corresponding
@@ -112,8 +120,7 @@
AT&D3 Same as AT&D2 but also resets all registers.
AT&Ex Set the EAZ/MSN for this channel to x.
AT&F Reset all registers and profile to "factory-defaults"
- AT&Sx Set window-size for Teles-driver (x = 1..8) (not yet
- implemented)
+ AT&Sx Set window-size (x = 1..8) (not yet implemented)
AT&V Show all settings.
AT&W0 Write registers and EAZ/MSN to profile. See also
iprofd (5.c in this README).
@@ -173,6 +180,10 @@
1 = T.70 protocol (Only for BTX!) on
Bit 2: 0 = Don't hangup on DTR low.
1 = Hangup on DTR low.
+ Bit 3: 0 = Standard response messages
+ 1 = Extended response messages
+ Bit 4: 0 = CALLER NUMBER before every RING.
+ 1 = CALLER NUMBER after first RING.
14 0 Layer-2 protocol:
0 = X75/LAPB with I-frames
1 = X75/LAPB with UI-frames
@@ -182,7 +193,7 @@
15 0 Layer-3 protocol: (at the moment always 0)
0 = transparent
16 250 Send-Packet-size/16
- 17 8 Window-size for Teles-driver (not yet implemented)
+ 17 8 Window-size (not yet implemented)
18 4 Bit coded register, Service-Octet-1 to accept,
or to be used on dialout:
Bit 0: Service 1 (audio) when set.
@@ -201,6 +212,14 @@
20 0 Bit coded register (readonly)
Service-Octet-1 of last call.
Bit mapping is the same like register 18
+ 21 0 Bit coded register (readonly)
+ Set on incoming call (during RING) to
+ octet 3 of calling party number IE (Numbering plan)
+ See section 4.5.10 of ITU Q.931
+ 22 0 Bit coded register (readonly)
+ Set on incoming call (during RING) to
+ octet 3a of calling party number IE (Screening info)
+ See section 4.5.10 of ITU Q.931
Last but not least a (at the moment fairly primitive) device to request
the line-status (/dev/isdninfo) is made available.
@@ -243,124 +262,16 @@
2 System prerequisites:
- ATTENTION! The program "insmod" from the Package "modules-1.2.8" (It's
- on nearly all newer distributions) has a bug, which makes
- it impossible to set both driver-Id's when loading the
- icn-module for the Double-ICN-Card. A patch is supplied
- in the utility-package called "insmod-1.2.8.patch". Change into
- the source-directory of insmod, and type
- "patch < insmod-1.2.8.patch". Then recompile it. This will fix
- the bug.
- This bug does NOT occur when using insmod with the Teles-driver
- or a single ICN-card.
+ ATTENTION!
+
+ Always use the latest module utilities. The current version is
+ named in Documentation/Changes. Some old versions of insmod
+ are not capable of setting the driver-Ids correctly.
3. Lowlevel-driver configuration.
- Configuration depends on how the drivers are built.
-
- 3.1 Drivers built into the kernel.
-
- 3.1.1 Teles driver.
-
- The Teles driver can be configured using the commandline-feature
- while loading the kernel with LILO or LOADLIN. It accepts the
- following syntax:
-
- teles=p0,i0,m0,d0[,p1,i1,m1,d1 ... ,pn,in,mn,dn][,idstring]
-
- where
-
- p0 = portbase of 1st card. (default: 0xd80)
- i0 = irq of 1st card. (default: 15)
- m0 = shared memory of 1st card. (default: 0xd0000)
- d0 = D-channel protocol of 1st card. 1=1TR6, 2=EDSS1 (default: 2)
-
- p1,i1,m1,d1 = Parameters of second card (defaults: none)
- pn,in,mn,d1 = Parameters of n'th card (up to 16 cards are supported)
-
- idstring = Driver-Id for accessing with utilities and identification
- when using a Line-monitor. (default: none)
- idstring must start with a character!
-
- The type of the card is determined by the port, irq and shared memory:
-
- port == 0, shared memory != 0 -> Teles S0-8
- port != 0, shared memory != 0 -> Teles S0-16.0
- port != 0, shared memory == 0 -> Teles S0-16.3
-
- ATTENTION:
-
- Due to limited hardware-capabilities, there is no way to check the
- existence of a card. Therefore you need to be sure your card's setup
- is correct. Also there are bugs in the printed manual of some newer
- 16.3 cards. Have a look to the kernel-syslog. With most of the cards,
- you should see a line "HSCX version A:5 B:5" there.
-
- 3.1.2 ICN driver.
-
- The ICN driver can be configured using the commandline-feature while
- loading the kernel with LILO or LOADLIN. It accepts the following
- syntax
-
- icn=p,m[,idstring1[,idstring2]]
-
- where
-
- p = portbase (default: 0x320)
- m = shared memory (default: 0xd0000)
-
- When using the ICN double card, you MUST define TWO idstrings.
- idstring must start with a character!
-
- If you like to use more than one card, you can use the program
- "icnctrl" from the utility-package to configure additional cards.
- You need to configure shared memory only once, since the icn-driver
- maps all cards into the same address-space.
-
- Using the "icnctrl"-utility, portbase and shared memory can also be
- changed during runtime.
-
- The D-channel protocol is configured by loading different firmware
- into the card's memory using the "icnctrl"-utility.
-
-
- 3.2 Drivers built as modules.
-
- 3.2.1 Teles driver.
-
- The module teles.o can be configured during "insmod'ing" it by
- appending its parameters to the insmod-commandline. The following
- syntax is accepted:
-
- io=m0,i0,p0,d0[,m1,i1,p1,d1 ... ,mn,in,pn,dn] teles_id=idstring
-
- where
-
- m0,i0,p0,d0 ... mn,in,pn,dn have the same meanings like the
- parameters described for the kernel-
- version above. Watch out: different
- sequence!
-
- 3.2.2 ICN driver.
-
- The module icn.o can be configured during "insmod'ing" it by
- appending its parameters to the insmod-commandline. The following
- syntax is accepted:
-
- portbase=p membase=m icn_id=idstring icn_id2=idstring2
-
- where p, m, idstring1 and idstring2 have the same meanings like
- parameters described for the kernel-
- version above.
-
- When using the ICN double card, you MUST define TWO idstrings.
- idstring must start with a character!
-
- Using the "icnctrl"-utility, the same features apply to the modularized
- version like to the kernel-builtin one.
-
- The D-channel protocol is configured by loading different firmware
- into the card's memory using the "icnctrl"-utility.
+ Configuration depends on how the drivers are built. See the
+ README.<yourDriver> for information on driver-specific setup.
4. Device-inodes
@@ -371,26 +282,11 @@
44 for the ISDN-callout-tty's.
45 for control/info/debug devices.
-
5. Application
- a) (Only for ICN-cards) Load the firmware into the card:
-
- cd icn
- For 1TR6:
- icnctrl [-d IDstring] load download/loadpg.bin download/pc_1t_ca.bin
- For Euro-ISDN:
- icnctrl [-d IDstring] load download/loadpg.bin download/pc_eu_ca.bin
-
- When using the ICN-4B, the protocol-software for the second half of
- the card must be appended to the command line.
-
- -> The two LEDs at the back cover of the card (ICN-4B: 4 LEDs) must be
- blinking intermittently now. If a connection is up, the corresponding
- led is lit continuously.
-
- For loading pcbit-firmware, refer to Documentation/isdn/README.pcbit
- and the pcbit manpage, included in the utility-package.
+ a) For some card-types, firmware has to be loaded into the cards, before
+ proceeding with device-independant setup. See README.<yourDriver>
+ for how to do that.
b) If you only intend to use ttys, you are nearly ready now.
@@ -422,8 +318,7 @@
h) additionally you may activate charge-hang-up (= Hang up before
next charge-info, this only works, if your isdn-provider transmits
- the charge-info during and after the connection, it does NOT work
- with the Teles on an EDSS1-Line.):
+ the charge-info during and after the connection):
isdnctrl chargehup isdn0 on
i) Setup the interface with ifconfig as usual, and set a route to it.
@@ -527,7 +422,7 @@
"isdnctrl l2_prot <InterfaceName> <L2-ProtocolName>"
Selects a layer-2-protocol.
- (With the ICN-driver and the Teles-driver, "x75i" and "hdlc" is available.
+ (With the ICN-driver and the HiSax-driver, "x75i" and "hdlc" is available.
With other drivers, "x75ui", "x75bui" may be possible too.)
isdnctrl l3_prot <InterfaceName> <L3-ProtocolName>
FUNET's LINUX-ADM group, linux-adm@nic.funet.fi
TCL-scripts by Sam Shen, slshen@lbl.gov