Discussion:
Cannot receive faxes with Capisuite / FRITZ!Card PCMCIA on kernel 2.6.8 — Error 0x3315
Dr. Holger Magnussen
2004-12-02 21:53:19 UTC
Permalink
Dear all,

after many night hours trying to solve my problem, I must admit that I
am a bit lost. I am hoping that somebody has been facing the same issue
and might have found a solution that is of any help for me.

While the answering machine part works without any problems, I cannot
receive FAXes. My machine picks up the call, but hangs up after a few
milliseconds. The capisuite error log shows that CAPI sends a
DISCONNECT_B3_ACTIVE_IND with error cause 0x3315 (remote procedure error).

Here are the details:

I have used Capisuite for about a year on a debian system with a 2.2
kernel and an AVM FRITZ!Card PCMCIA. My hardware is a VIA EPIA MII
board. Everything worked very well until my hard disk crashed completely.

With a new hard disk, I am now running

* a debian 2.6.8 kernel
* capisuite-0.4.5 (I tried both the binaries and compiled it myself
- same situation), and
* the AVM drivers from the "fcpcmcia-suse91-3.11-02.tar.gz" package
(I compiled them without any errors).
* "isdnactivecards" V3.3.0.20 is also installed.


I also checked the hardware: no conflicts with interrupts, dma channels
or IO areas.

Does anybody have a clue?

-holger

------------------------------------------------------------------------
capiinfo output looks OK:

Number of Controllers : 1
Controller 1:
Manufacturer: AVM GmbH
CAPI Version: 2.0
Manufacturer Version: 3.101-02 (49.18)
Serial Number: 1000001
BChannels: 2
Global Options: 0x00000039
internal controller supported
DTMF supported
Supplementary Services supported
channel allocation supported (leased lines)
B1 protocols support: 0x4000011f
64 kbit/s with HDLC framing
64 kbit/s bit-transparent operation
V.110 asynconous operation with start/stop byte framing
V.110 synconous operation with HDLC framing
T.30 modem for fax group 3
Modem asyncronous operation with start/stop byte framing
B2 protocols support: 0x00000b1b
ISO 7776 (X.75 SLP)
Transparent
LAPD with Q.921 for D channel X.25 (SAPI 16)
T.30 for fax group 3
ISO 7776 (X.75 SLP) with V.42bis compression
V.120 asyncronous mode
V.120 bit-transparent mode
B3 protocols support: 0x800000bf
Transparent
T.90NL, T.70NL, T.90
ISO 8208 (X.25 DTE-DTE)
X.25 DCE
T.30 for fax group 3
T.30 for fax group 3 with extensions
Modem

0100
0200
39000000
1f010040
1b0b0000
bf000080
00000000 00000000 00000000 00000000 00000000 00000000
01000001 00020000 00000000 00000000 00000000

Supplementary services support: 0x000003ff
Hold / Retrieve
Terminal Portability
ECT
3PTY
Call Forwarding
Call Deflection
MCID
CCBS

------------------------------------------------------------------------
Here is the corresponding section from capisuite.log (capisuite.error
has nothing of interest in it):

Thu Dec 2 00:01:32 2004 CapiSuite 0xbffff880: CapiSuite 0.4.5 started.
Thu Dec 2 00:01:32 2004 Capi 0x80a4680: Capi object created
Thu Dec 2 00:01:32 2004 Capi 0x80a4680: >LISTEN_REQ ApplID 0x1 msgNum
0x0 Controller 0x1 InfoMask 0x10 CIPMask 0x0 0x0 NULL NULL
Thu Dec 2 00:01:32 2004 Capi 0x80a4680: info: 0
Thu Dec 2 00:01:32 2004 Capi 0x80a4680: *
Thu Dec 2 00:01:32 2004 Capi 0x80a4680: <LISTEN_CONF Controller 0x1
Info 0x0
Thu Dec 2 00:01:32 2004 Capi 0x80a4680: **
Thu Dec 2 00:01:32 2004 Capi 0x80a4680: Registered successful at CAPI
with ApplId 1
Thu Dec 2 00:01:32 2004 CapiSuite 0xbffff880: 1 controllers found
Thu Dec 2 00:01:32 2004 CapiSuite 0xbffff880: Capi driver: AVM Berlin,
version 2.0/1.16
Thu Dec 2 00:01:32 2004 CapiSuite 0xbffff880: Controller 1: AVM GmbH (2
B channels, DTMF, SuppServ, transparent, FaxG3, FaxG3ext), driver
version 2.0/49.18
Thu Dec 2 00:01:32 2004 Capi 0x80a4680: >LISTEN_REQ ApplID 0x1 msgNum
0x1 Controller 0x1 InfoMask 0x10 CIPMask 0x10012 0x0 NULL NULL
Thu Dec 2 00:01:32 2004 Capi 0x80a4680: info: 0
Thu Dec 2 00:01:32 2004 Capi 0x80a4680: >LISTEN_REQ ApplID 0x1 msgNum
0x2 Controller 0x1 InfoMask 0x10 CIPMask 0x30012 0x0 NULL NULL
Thu Dec 2 00:01:32 2004 Capi 0x80a4680: info: 0
Thu Dec 2 00:01:32 2004 Capi 0x80a4680: *
Thu Dec 2 00:01:32 2004 Capi 0x80a4680: <LISTEN_CONF Controller 0x1
Info 0x0
Thu Dec 2 00:01:32 2004 Capi 0x80a4680: **
Thu Dec 2 00:01:32 2004 Capi 0x80a4680: *
Thu Dec 2 00:01:32 2004 Capi 0x80a4680: <LISTEN_CONF Controller 0x1
Info 0x0
Thu Dec 2 00:01:32 2004 Capi 0x80a4680: **
Thu Dec 2 00:06:51 2004 Capi 0x80a4680: *
Thu Dec 2 00:06:51 2004 Capi 0x80a4680: <CONNECT_IND PLCI 0x101 CIP 0x10
Thu Dec 2 00:06:51 2004 Connection 0x80c2810: Connection object created
for incoming call PLCI 101 from 02283690815 to 3692882 CIP 0x10
Thu Dec 2 00:06:51 2004 Capi 0x80a4680: **
Thu Dec 2 00:06:51 2004 Pythonscript
/usr/local/lib/capisuite/incoming.py,callIncoming,0x80ea580:
PythonScript created.
Thu Dec 2 00:06:51 2004 Pythonscript
/usr/local/lib/capisuite/incoming.py,callIncoming,0x80ea580: Connection
0x80c2810 created IncomingScript
Thu Dec 2 00:06:51 2004 Connection 0x80c2810: call from 02283690815 to
3692882 for faxks connecting with fax
Thu Dec 2 00:06:51 2004 Connection 0x80c2810: accepting with service 1
Thu Dec 2 00:06:51 2004 Connection 0x80c2810: using faxStationID +49
228 369 2882 faxHeadline Holger Magnussen - sent by CapiSuite
Thu Dec 2 00:06:51 2004 Capi 0x80a4680: >CONNECT_RESP ApplId 0x1,
msgNum 0x14, PLCI 0x101, Reject 0x0, B1proto 0x4, B2proto 0x4, B3proto 0x5
Thu Dec 2 00:06:51 2004 Capi 0x80a4680: info: 0
Thu Dec 2 00:06:51 2004 Capi 0x80a4680: *
Thu Dec 2 00:06:51 2004 Capi 0x80a4680: <CONNECT_ACTIVE_IND PLCI 0x101
Thu Dec 2 00:06:51 2004 Capi 0x80a4680: >CONNECT_ACTIVE_RESP ApplId 0x1
MsgNum 0x15 PLCI 0x101
Thu Dec 2 00:06:51 2004 Capi 0x80a4680: info: 0
Thu Dec 2 00:06:51 2004 Capi 0x80a4680: **
Thu Dec 2 00:06:51 2004 Capi 0x80a4680: *
Thu Dec 2 00:06:51 2004 Capi 0x80a4680: <CONNECT_B3_IND NCCI 0x10101
Thu Dec 2 00:06:51 2004 Capi 0x80a4680: >CONNECT_B3_RESP ApplId 0x1
MsgNum 0x16 NCCI 0x10101 Reject 0x0
Thu Dec 2 00:06:51 2004 Capi 0x80a4680: info: 0
Thu Dec 2 00:06:51 2004 Capi 0x80a4680: **
Thu Dec 2 00:06:51 2004 Capi 0x80a4680: *
Thu Dec 2 00:06:51 2004 Capi 0x80a4680: <CONNECT_B3_ACTIVE_IND NCCI 0x10101
Thu Dec 2 00:06:51 2004 Capi 0x80a4680: >CONNECT_B3_ACTIVE_RESP ApplId
0x1 MsgNum 0x17 NCCI 0x10101
Thu Dec 2 00:06:51 2004 Capi 0x80a4680: info: 0
Thu Dec 2 00:06:51 2004 Connection 0x80c2810: fax connected with rate
0, lowRes, ID:
Thu Dec 2 00:06:51 2004 Capi 0x80a4680: **
Thu Dec 2 00:06:51 2004 Capi 0x80a4680: *
Thu Dec 2 00:06:51 2004 Capi 0x80a4680: <DISCONNECT_B3_IND NCCI 0x10101
Reason 0x3315
Thu Dec 2 00:06:51 2004 Connection 0x80c2810: fax finished with rate 0,
lowRes, ID: , 0 pages
Thu Dec 2 00:06:51 2004 Connection 0x80c2810: stop_file_transmission
initiated
Thu Dec 2 00:06:51 2004 Connection 0x80c2810: stop_file_transmission
finished
Thu Dec 2 00:06:51 2004 Connection 0x80c2810: stop_file_reception finished
Thu Dec 2 00:06:51 2004 Capi 0x80a4680: >DISCONNECT_B3_RESP ApplId 0x1
MsgNum 0x18 NCCI 0x10101
Thu Dec 2 00:06:51 2004 Capi 0x80a4680: info: 0
Thu Dec 2 00:06:51 2004 Capi 0x80a4680: **
Thu Dec 2 00:06:51 2004 Connection 0x80c2810: disconnect initiated
Thu Dec 2 00:06:51 2004 Capi 0x80a4680: >DISCONNECT_REQ ApplId 0x1
MsgNum 0x3 PLCI 0x101
Thu Dec 2 00:06:51 2004 Capi 0x80a4680: info: 0
Thu Dec 2 00:06:51 2004 Capi 0x80a4680: *
Thu Dec 2 00:06:51 2004 Capi 0x80a4680: <DISCONNECT_CONF PLCI 0x101
Info 0x0
Thu Dec 2 00:06:51 2004 Capi 0x80a4680: **
Thu Dec 2 00:06:51 2004 Capi 0x80a4680: *
Thu Dec 2 00:06:51 2004 Capi 0x80a4680: <DISCONNECT_IND PLCI 0x101
Reason 0x3400
Thu Dec 2 00:06:51 2004 Capi 0x80a4680: >DISCONNECT_RESP ApplId 0x1
MsgNum 0x19 PLCI 0x101
Thu Dec 2 00:06:51 2004 Capi 0x80a4680: info: 0
Thu Dec 2 00:06:51 2004 Capi 0x80a4680: **
Thu Dec 2 00:06:51 2004 Connection 0x80c2810: connection lost with
cause 0x3400,0x3315
Thu Dec 2 00:06:51 2004 Connection 0x80c2810: Python: deleting
connection object
Thu Dec 2 00:06:51 2004 Connection 0x80c2810: stop_file_transmission
initiated
Thu Dec 2 00:06:51 2004 Connection 0x80c2810: stop_file_transmission
finished
Thu Dec 2 00:06:51 2004 Connection 0x80c2810: stop_file_reception finished
Thu Dec 2 00:06:51 2004 Connection 0x80c2810: Connection object deleted
Thu Dec 2 00:06:51 2004 Pythonscript
/usr/local/lib/capisuite/incoming.py,callIncoming,0x80ea580:
IncomingScript deleted
Thu Dec 2 00:06:51 2004 Pythonscript
/usr/local/lib/capisuite/incoming.py,callIncoming,0x80ea580:
PythonScript deleted.

------------------------------------------------------------------------
Here is the corresponding section from kern.log (after activating an
avmcapictrl trace): The only interesting thing that I can see is that
CAPI seems to send both CONNECT_B3_ACTIVE_IND and DISCONNECT_B3_IND
before capisuite can even respond with CONNECT_B3_ACTIVE_RESP.
capisuite.log shows a different order.

Dec 2 00:06:36 localhost kernel: kcapi: contr 1 set trace=4
Dec 2 00:06:51 localhost kernel: kcapi: got [0x1]
CONNECT_IND ID=001 #0x0014 LEN=0048
Dec 2 00:06:51 localhost kernel: Controller/PLCI/NCCI = 0x101
Dec 2 00:06:51 localhost kernel: CIPValue = 0x10
Dec 2 00:06:51 localhost kernel: CalledPartyNumber =
Á3692882
Dec 2 00:06:51 localhost kernel: CallingPartyNumber =
<21 81>2283690815
Dec 2 00:06:51 localhost kernel: CalledPartySubaddress =
default
Dec 2 00:06:51 localhost kernel: CallingPartySubaddress =
default
Dec 2 00:06:51 localhost kernel: BC =
<80 90 a3>
Dec 2 00:06:51 localhost kernel: LLC =
default
Dec 2 00:06:51 localhost kernel: HLC =
<91 81>
Dec 2 00:06:51 localhost kernel: AdditionalInfo =
default
Dec 2 00:06:51 localhost kernel:
Dec 2 00:06:51 localhost kernel: kcapi: put [0x1]
CONNECT_RESP ID=001 #0x0014 LEN=0090
Dec 2 00:06:51 localhost kernel: Controller/PLCI/NCCI = 0x101
Dec 2 00:06:51 localhost kernel: Reject = 0x0
Dec 2 00:06:51 localhost kernel: BProtocol
Dec 2 00:06:51 localhost kernel: B1protocol = 0x4
Dec 2 00:06:51 localhost kernel: B2protocol = 0x4
Dec 2 00:06:51 localhost kernel: B3protocol = 0x5
Dec 2 00:06:51 localhost kernel: B1configuration =
default
Dec 2 00:06:51 localhost kernel: B2configuration =
default
Dec 2 00:06:51 localhost kernel: B3configuration =
<00 00 00 00 10 2b>49 228 369 2882<24>Holger Magnussen <2d> sent by
CapiSuite
Dec 2 00:06:51 localhost kernel: ConnectedNumber =
default
Dec 2 00:06:51 localhost kernel: ConnectedSubaddress =
default
Dec 2 00:06:51 localhost kernel: LLC =
default
Dec 2 00:06:51 localhost kernel: AdditionalInfo
Dec 2 00:06:51 localhost kernel: BChannelinformation =
default
Dec 2 00:06:51 localhost kernel: Keypadfacility =
default
Dec 2 00:06:51 localhost kernel: Useruserdata =
default
Dec 2 00:06:51 localhost kernel: Facilitydataarray =
default
Dec 2 00:06:51 localhost kernel:
Dec 2 00:06:51 localhost kernel: kcapi: got [0x1]
CONNECT_ACTIVE_IND ID=001 #0x0015 LEN=0015
Dec 2 00:06:51 localhost kernel: Controller/PLCI/NCCI = 0x101
Dec 2 00:06:51 localhost kernel: ConnectedNumber =
default
Dec 2 00:06:51 localhost kernel: ConnectedSubaddress =
default
Dec 2 00:06:51 localhost kernel: LLC =
default
Dec 2 00:06:51 localhost kernel:
Dec 2 00:06:51 localhost kernel: capilib_new_ncci: kcapi: appl 1 ncci
0x10101 up
Dec 2 00:06:51 localhost kernel: kcapi: got [0x1]
CONNECT_B3_IND ID=001 #0x0016 LEN=0022
Dec 2 00:06:51 localhost kernel: Controller/PLCI/NCCI =
0x10101
Dec 2 00:06:51 localhost kernel: NCPI =
<00 00 00 00 00 00 00 00 00>
Dec 2 00:06:51 localhost kernel:
Dec 2 00:06:51 localhost kernel: kcapi: put [0x1]
CONNECT_ACTIVE_RESP ID=001 #0x0015 LEN=0012
Dec 2 00:06:51 localhost kernel: Controller/PLCI/NCCI = 0x101
Dec 2 00:06:51 localhost kernel:
Dec 2 00:06:51 localhost kernel: kcapi: put [0x1]
CONNECT_B3_RESP ID=001 #0x0016 LEN=0015
Dec 2 00:06:51 localhost kernel: Controller/PLCI/NCCI =
0x10101
Dec 2 00:06:51 localhost kernel: Reject = 0x0
Dec 2 00:06:51 localhost kernel: NCPI =
default
Dec 2 00:06:51 localhost kernel:
Dec 2 00:06:51 localhost kernel: kcapi: got [0x1]
CONNECT_B3_ACTIVE_IND ID=001 #0x0017 LEN=0022
Dec 2 00:06:51 localhost kernel: Controller/PLCI/NCCI =
0x10101
Dec 2 00:06:51 localhost kernel: NCPI =
<00 00 00 00 00 00 00 00 00>
Dec 2 00:06:51 localhost kernel:
Dec 2 00:06:51 localhost kernel: kcapi: got [0x1]
DISCONNECT_B3_IND ID=001 #0x0018 LEN=0024
Dec 2 00:06:51 localhost kernel: Controller/PLCI/NCCI =
0x10101
Dec 2 00:06:51 localhost kernel: Reason_B3 = 0x3315
Dec 2 00:06:51 localhost kernel: NCPI =
<00 00 00 00 00 00 00 00 00>
Dec 2 00:06:51 localhost kernel:
Dec 2 00:06:51 localhost kernel: kcapi: put [0x1]
CONNECT_B3_ACTIVE_RESP ID=001 #0x0017 LEN=0012
Dec 2 00:06:51 localhost kernel: Controller/PLCI/NCCI =
0x10101
Dec 2 00:06:51 localhost kernel:
Dec 2 00:06:51 localhost kernel: kcapi: put [0x1]
DISCONNECT_B3_RESP ID=001 #0x0018 LEN=0012
Dec 2 00:06:51 localhost kernel: Controller/PLCI/NCCI =
0x10101
Dec 2 00:06:51 localhost kernel:
Dec 2 00:06:51 localhost kernel: kcapi: appl 1 ncci 0x10101 down
Dec 2 00:06:51 localhost kernel: kcapi: put [0x1]
DISCONNECT_REQ ID=001 #0x0003 LEN=0017
Dec 2 00:06:51 localhost kernel: Controller/PLCI/NCCI = 0x101
Dec 2 00:06:51 localhost kernel: AdditionalInfo
Dec 2 00:06:51 localhost kernel: BChannelinformation =
default
Dec 2 00:06:51 localhost kernel: Keypadfacility =
default
Dec 2 00:06:51 localhost kernel: Useruserdata =
default
Dec 2 00:06:51 localhost kernel: Facilitydataarray =
default
Dec 2 00:06:51 localhost kernel:
Dec 2 00:06:51 localhost kernel: kcapi: got [0x1]
DISCONNECT_CONF ID=001 #0x0003 LEN=0014
Dec 2 00:06:51 localhost kernel: Controller/PLCI/NCCI = 0x101
Dec 2 00:06:51 localhost kernel: Info = 0x0
Dec 2 00:06:51 localhost kernel:
Dec 2 00:06:51 localhost kernel: kcapi: got [0x1]
DISCONNECT_IND ID=001 #0x0019 LEN=0014
Dec 2 00:06:51 localhost kernel: Controller/PLCI/NCCI = 0x101
Dec 2 00:06:51 localhost kernel: Reason = 0x3400
Dec 2 00:06:51 localhost kernel:
Dec 2 00:06:51 localhost kernel: kcapi: put [0x1]
DISCONNECT_RESP ID=001 #0x0019 LEN=0012
Dec 2 00:06:51 localhost kernel: Controller/PLCI/NCCI = 0x101
Dec 2 00:06:51 localhost kernel:
Dec 2 00:07:02 localhost kernel: kcapi: contr 1 set trace=0

------------------------------------------------------------------------
Gernot Hillier
2004-12-04 07:46:10 UTC
Permalink
Hi!
Post by Dr. Holger Magnussen
after many night hours trying to solve my problem, I must admit that I
am a bit lost. I am hoping that somebody has been facing the same issue
and might have found a solution that is of any help for me.
Sorry, no real clue, but one question:

[...]
Post by Dr. Holger Magnussen
I also checked the hardware: no conflicts with interrupts, dma channels
or IO areas.
Did you only check in theory or did you try to swap around cards and IRQ
assignments chaotically?

Sometimes, bad things happen - I even heard of PCI slots getting
damaged... :-}
--
Ciao,

Gernot
Loading...