B2 protocol no.12

[Krzysztof Brzezinski]

Hello,

I need to use B2 protocol no.12 (LAP-D with free SAPI/TEI selection). My AVM
Fritz! PCMCIA card (and its CAPI) says it does not support no.12.

Does anybody know of a commercially available card (not necessarily of the
PCMCIA variety) that DOES support this mode? And in general - is CAPI
specification serious about this mode, or is it in fact a deprecated
functionality?

TIA,

Chris Brzezinski
Warsaw, Poland

[mm]

Hi Krzysztof;

The Eicon Server cards support capi b2 protocol bit 12 and 3 (SAPI=16,
X.25).

Capi needs to be serious about LAPD. After all LAPD is carrying the
signalling information between TEs and exchange. ;)

Bye
Michael

Post by Krzysztof Brzezinski
Hello,
I need to use B2 protocol no.12 (LAP-D with free SAPI/TEI selection). My AVM
Fritz! PCMCIA card (and its CAPI) says it does not support no.12.
Does anybody know of a commercially available card (not necessarily of the
PCMCIA variety) that DOES support this mode? And in general - is CAPI
specification serious about this mode, or is it in fact a deprecated
functionality?
TIA,
Chris Brzezinski
Warsaw, Poland

[Krzysztof Brzezinski]

Thanks!
Actually, almost every mode uses LAPD. It is just that CAPI hides signalling
information and/or substitutes its own info, because the implicit assumption
is that the application is interested in data transfer. My application is
interested in signalling transfer, and needs to fully control this exchange.
BTW, chapter D.2.3.3 of CAPI Part 1 writes about Capi Guard, which disables
the use of b12. Capi Guard is optional, but I do not know if it can be
disabled itself, in order not to interfere. I would be grateful for any
further enlightment.

Krzysztof

Post by mm
The Eicon Server cards support capi b2 protocol bit 12 and 3 (SAPI=16,
X.25).
Capi needs to be serious about LAPD. After all LAPD is carrying the
signalling information between TEs and exchange. ;)

[mm]

Hi Krzysztof;

I use these cards on linux systems. The setup gives you quite a few
choices, but I cannot remember anything that has to do with disabling
this feature. The web interface does not seem to have any switches for
that either, so I guess you have to try and see.
The software includes a D-Channel analyzer. Software access to
D-Channel information can be gained (I believe) via Eicon's proprietary
API (nothing to do with CAPI, contrary to AVM cards).
I don't know wether you can send LAPD frames this way as well.

Hope that helped.

Michael

Post by Krzysztof Brzezinski
Thanks!
Actually, almost every mode uses LAPD. It is just that CAPI hides signalling
information and/or substitutes its own info, because the implicit assumption
is that the application is interested in data transfer. My application is
interested in signalling transfer, and needs to fully control this exchange.
BTW, chapter D.2.3.3 of CAPI Part 1 writes about Capi Guard, which disables
the use of b12. Capi Guard is optional, but I do not know if it can be
disabled itself, in order not to interfere. I would be grateful for any
further enlightment.
Krzysztof

Post by mm
The Eicon Server cards support capi b2 protocol bit 12 and 3 (SAPI=16,
X.25).
Capi needs to be serious about LAPD. After all LAPD is carrying the
signalling information between TEs and exchange. ;)

[Krzysztof Brzezinski]

Hi,
I am a student of dr Brzezinski's.
I am working on thi, to no avail up to now.
I have some questions about CAPI 2.0. I need to know if there is any way to
disable automatic sending the RELEASE_COMPLETE masssage by card whith CAPI
2.0 when not in listening state (when B2Protocol = 12), after reciving
'something'. I also have trouble whith sending messages while in B2Protocol
= 12. I don't get CONNECT_B3_ACTIVE_IND and while trying to send DATA_B3_REQ
i get DATA_B3_CONF whith info that "this massage is not supported in current
state".
I would be very gratefull for any help

P.Ratuszek.