Package: capiutils
Version: 1:3.9.20060704-3
Severity: normal
Tags: patch

Hello,

at least with a FritzCard PCI on the Deutsche Telekom network my standard
response from 'capifax -v' for a sucessful delivery is:

    Disconnected.
      Reason            : 3400 No additional information
      Reason-B3         : 0000 No additional information

According to
    http://www.capisuite.de/manual/apb.html
also the CAPI 2.0 codes 3400 and 3480 signal a normal termination of the
connection while they are treated as errors in capifax. Only 3490 and 349F are
treated as success in capifax.c and the detailed descriptions of 3400 and 3480
are missing in c20msg.c .

Regarding the 3400 status code some more information is given on
    http://help.netop.com/support/communication/isdn/capi_error_codes.htm
where it says:
    "34xx   Abort by network, low order 8 Bit contain the cause value, the MSB
            is used to signal an error, but is not set by all ISDN-CAPI 2.0
            implementations"

Additionally, 3400 was the code for "Normal termination from the network" in
CAPI 1.1 (german ISDN 1TR6) which might be the reason that it is still used.

The attached patch fixes these problems.

It would be nice if the default Debian package could include this fix as well
as the patch from #354830 .

Ch. Scheurer

-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.20-local
Locale: LANG=C, [EMAIL PROTECTED] (charmap=ISO-8859-15)

Versions of packages capiutils depends on:
ii  libc6                  2.3.6.ds1-13etch5 GNU C Library: Shared libraries
ii  libcapi20-3            1:3.9.20060704-3  libraries for CAPI support
ii  lsb-base               3.1-23.2etch1     Linux Standard Base 3.1 init scrip

capiutils recommends no packages.

-- no debconf information

-- 
Christoph Scheurer                                  GnuPG key Id: 0x6128C6B6

Attachment: capifax.additional_error_codes.patch.gz
Description: Binary data

Reply via email to