After Faxsend the idle-Script stops

[JM]

Hello,

if I send a Fax with (capisuitefax -d 0123456789 ~/FaxSend/test.ps) the
fax is queued but
not send.
The log-file (/var/log/capisuite.log) in log_level="3":

Sun Jan 8 07:55:22 2006 CapiSuite 0xbfea2bec: CapiSuite 0.4.5 started.
Sun Jan 8 07:55:22 2006 Capi 0x812fc70: Capi object created
Sun Jan 8 07:55:22 2006 Capi 0x812fc70: >LISTEN_REQ ApplID 0x1 msgNum
0x0 Controller 0x1 InfoMask 0x10 CIPMask 0x0 0x0 NULL NULL
Sun Jan 8 07:55:22 2006 Capi 0x812fc70: info: 0
Sun Jan 8 07:55:22 2006 Capi 0x812fc70: Registered successful at CAPI
with ApplId 1
Sun Jan 8 07:55:22 2006 CapiSuite 0xbfea2bec: 1 controllers found
Sun Jan 8 07:55:22 2006 CapiSuite 0xbfea2bec: Capi driver: AVM Berlin,
version 2.0/1.16
Sun Jan 8 07:55:22 2006 CapiSuite 0xbfea2bec: Controller 1: AVM GmbH (2
B channels, DTMF, SuppServ, transparent, FaxG3, FaxG3ext), driver
version 2.0/49.23
Sun Jan 8 07:55:22 2006 Capi 0x812fc70: >LISTEN_REQ ApplID 0x1 msgNum
0x1 Controller 0x1 InfoMask 0x10 CIPMask 0x10012 0x0 NULL NULL
Sun Jan 8 07:55:22 2006 Capi 0x812fc70: info: 0
Sun Jan 8 07:55:22 2006 Capi 0x812fc70: >LISTEN_REQ ApplID 0x1 msgNum
0x2 Controller 0x1 InfoMask 0x10 CIPMask 0x30012 0x0 NULL NULL
Sun Jan 8 07:55:22 2006 Capi 0x812fc70: info: 0
Sun Jan 8 07:55:22 2006 Capi 0x812fc70: *
Sun Jan 8 07:55:22 2006 Capi 0x812fc70: <LISTEN_CONF Controller 0x1
Info 0x0
Sun Jan 8 07:55:22 2006 Capi 0x812fc70: **
Sun Jan 8 07:55:22 2006 Capi 0x812fc70: *
Sun Jan 8 07:55:22 2006 Capi 0x812fc70: <LISTEN_CONF Controller 0x1
Info 0x0
Sun Jan 8 07:55:22 2006 Capi 0x812fc70: **
Sun Jan 8 07:55:22 2006 Capi 0x812fc70: *
Sun Jan 8 07:55:22 2006 Capi 0x812fc70: <LISTEN_CONF Controller 0x1
Info 0x0
Sun Jan 8 07:55:22 2006 Capi 0x812fc70: **
Sun Jan 8 07:55:22 2006 Pythonscript
/usr/lib/capisuite/idle.py,idle,0x815b190: PythonScript created.
Sun Jan 8 07:55:22 2006 Pythonscript
/usr/lib/capisuite/idle.py,idle,0x815b190: IdleScript created.
Sun Jan 8 07:55:25 2006 Pythonscript
/usr/lib/capisuite/idle.py,idle,0x815b190: executing idlescript...
.....etc.
Sun Jan 8 08:06:40 2006 Pythonscript
/usr/lib/capisuite/idle.py,idle,0x815b190: idlescript finished...
Sun Jan 8 08:07:10 2006 Pythonscript
/usr/lib/capisuite/idle.py,idle,0x815b190: executing idlescript...
Sun Jan 8 08:07:10 2006 CapiSuite 0xbfea2bec: job fax-0.sff from jens
to 0123456789 initiated
Sun Jan 8 08:07:10 2006 Connection 0x81b5fc0: Connection object created
for outgoing call from 8789074 to 0123456789 service 1
Sun Jan 8 08:07:10 2006 Connection 0x81b5fc0: using faxStationID +49
01234 567 89 faxHeadline Jens Moeller by CapiSuite (www.CapiSuite.de) CLIR 0
Sun Jan 8 08:07:10 2006 Capi 0x812fc70: >CONNECT_REQ: ApplId 0x1, MsgNr
0x4, Controller 0x1 CIPValue 0x11, B1proto 0x4, B2proto 0x4, B3proto 0x5
Sun Jan 8 08:07:10 2006 Capi 0x812fc70: info: 0
Sun Jan 8 08:07:10 2006 Capi 0x812fc70: *
Sun Jan 8 08:07:10 2006 Capi 0x812fc70: <CONNECT_CONF, PLCI: 0x101,
Info 0x0
Sun Jan 8 08:07:10 2006 Connection 0x81b5fc0: got PLCI 101
Sun Jan 8 08:07:10 2006 Capi 0x812fc70: **

After the last line in the log-file is no more line writing. The
idle-script is never finished?!

In the /var/log/capisuite.error is no error entry:
Sat Jan 7 17:07:10 2006 CapiSuite 0xbfe985fc: CapiSuite 0.4.5 started.
Sat Jan 7 23:45:13 2006 CapiSuite 0xbfe985fc: CapiSuite finished.
Sun Jan 8 07:55:22 2006 CapiSuite 0xbfea2bec: CapiSuite 0.4.5 started.

The spool directory looks so:
-rw-r--r-- 1 root root 0 2006-01-08 08:07 fax-0.lock
-rw------- 1 jens jens 23462 2006-01-08 08:07 fax-0.sff
-rw------- 1 jens jens 331 2006-01-08 08:07 fax-0.txt
-rw-r--r-- 1 jens jens 2 2006-01-08 08:07 fax-nextnr

The capiinfo connand talk this, so that I think it's ok?

Number of Controllers : 1
Controller 1:
Manufacturer: AVM GmbH
CAPI Version: 2.0
Manufacturer Version: 3.11-07 (49.23)
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

If I not clean the spool directory and starts the capisuite daemon new,
I have
the same effect. I must clean the spool dirictory than the idle-script
is running
after a restart of the capisuite daemon.

I use a ubuntu-Linux (5.10) with kernel 2.6.12-10-386.


I hope for help - Thanks in forward.

Jens Moeller

[Gernot Hillier]

Hi!

Post by JM
/usr/lib/capisuite/idle.py,idle,0x815b190: executing idlescript...
Sun Jan 8 08:07:10 2006 CapiSuite 0xbfea2bec: job fax-0.sff from jens
to 0123456789 initiated
Sun Jan 8 08:07:10 2006 Connection 0x81b5fc0: Connection object created
for outgoing call from 8789074 to 0123456789 service 1
Sun Jan 8 08:07:10 2006 Connection 0x81b5fc0: using faxStationID +49
01234 567 89 faxHeadline Jens Moeller by CapiSuite (www.CapiSuite.de) CLIR
0 Sun Jan 8 08:07:10 2006 Capi 0x812fc70: >CONNECT_REQ: ApplId 0x1, MsgNr
0x4, Controller 0x1 CIPValue 0x11, B1proto 0x4, B2proto 0x4, B3proto 0x5
Sun Jan 8 08:07:10 2006 Capi 0x812fc70: info: 0
Sun Jan 8 08:07:10 2006 Capi 0x812fc70: *
Sun Jan 8 08:07:10 2006 Capi 0x812fc70: <CONNECT_CONF, PLCI: 0x101,
Info 0x0
Sun Jan 8 08:07:10 2006 Connection 0x81b5fc0: got PLCI 101
Sun Jan 8 08:07:10 2006 Capi 0x812fc70: **
After the last line in the log-file is no more line writing. The
idle-script is never finished?!

Wow, this sounds like a really non-trivial internal error of CapiSuite.
CapiSuite should now send the next CAPI REQUEST but it seems to hang
somewhere instead :-(

You should either try to update your system (CAPI drivers, kernel, CapiSuite)
if possible or do real debugging to see why and where it hangs.

This would however mean you should have some spare time and experience in
gdb/printf debugging, I'm sorry...

Possibly your system is also somehow corrupt (bad CAPI library, bad C
library, ...)