 HylaFAX The world's
most advanced open source fax server
|
[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index] [Thread Index]
Re: [hylafax-users] Desperation with Hylafax and AVM Fritz ISDN C ard PCI on a debian system
- To: hylafax-users@xxxxxxxxxxx
- Subject: Re: [hylafax-users] Desperation with Hylafax and AVM Fritz ISDN C ard PCI on a debian system
- From: Guido Hecken <guido.hecken@xxxxxxxxxxxxx>
- Cc: Andreas Moser <A.Moser@xxxxxx>
- Date: Mon, 5 Sep 2005 19:18:09 +0200
Hi Andreas, hi list,
after following this thread, I began to examine the whole thing one more
time.
I changed my running config to the one Andreas submitted and got the same
problem:
here is the result when using c2faxsend without any modifications
(wrapper-script)
Sep 5 18:49:41 server2 FaxQueuer[3928]: FIFO RECV "Sclient/3931:64"
Sep 5 18:49:41 server2 FaxQueuer[3928]: SUBMIT JOB 64
Sep 5 18:49:41 server2 FaxQueuer[3928]: JOB 64 (suspended dest pri 127 tts
0:00 killtime 2:59:00): CREATE
Sep 5 18:49:41 server2 FaxQueuer[3928]: Apply CanonicalNumber rules to
"870664"
Sep 5 18:49:41 server2 FaxQueuer[3928]: --> match rule "^[^+]", result now
"+492244870664"
Sep 5 18:49:41 server2 FaxQueuer[3928]: --> return result "+492244870664"
Sep 5 18:49:41 server2 FaxQueuer[3928]: JOB 64 (ready dest +492244870664
pri 127 tts 0:00 killtime 2:59:00): READY
Sep 5 18:49:41 server2 FaxQueuer[3928]: FIFO SEND client/3931 msg "S*"
Sep 5 18:49:41 server2 FaxQueuer[3928]: JOB 64 (ready dest +492244870664
pri 127 tts 0:00 killtime 2:59:00): PROCESS
Sep 5 18:49:41 server2 FaxQueuer[3928]: JOB 64 (active dest +492244870664
pri 127 tts 0:00 killtime 2:59:00): ACTIVE
Sep 5 18:49:41 server2 FaxQueuer[3928]: JOB 64 (active dest +492244870664
pri 127 tts 0:00 killtime 2:59:00): PREPARE START
Sep 5 18:49:41 server2 FaxQueuer[3933]: JOB 64 (active dest +492244870664
pri 127 tts 0:00 killtime 2:59:00): CONVERT DOCUMENT: bin/ps2fax -o
docq/doc65.ps;31 -r 196 -w 1728 -l 280 -m 4294967295 -U -1 docq/doc65.ps.64
Sep 5 18:49:41 server2 FaxQueuer[3928]: JOB 64 (active dest +492244870664
pri 127 tts 0:00 killtime 2:59:00): PREPARE DONE
Sep 5 18:49:41 server2 FaxQueuer[3928]: JOB 64 (active dest +492244870664
pri 127 tts 0:00 killtime 2:59:00): CMD START /usr/local/bin/c2faxsend -m
faxCAPI sendq/q64 (PID 3937)
Sep 5 18:50:11 server2 kernel: kcapi: appl 3 ncci 0x10101 down
Sep 5 18:50:11 server2 FaxQueuer[3928]: JOB 64 (active dest +492244870664
pri 127 tts 0:00 killtime 2:58:30): CMD DONE: exit status 0x200
!!!!!
Sep 5 18:50:11 server2 FaxQueuer[3928]: JOB 64 (sleeping dest +492244870664
pri 126 tts 0:00 killtime 2:58:30): SEND INCOMPLETE: requeue for 7:13;
!!!!!
Sep 5 18:50:11 server2 FaxQueuer[3928]: JOB 64 (sleeping dest +492244870664
pri 126 tts 0:00 killtime 2:58:30): SLEEP FOR 7:13
Sep 5 18:50:11 server2 FaxQueuer[3928]: NOTIFY: bin/notify "sendq/q64"
"requeued" "" "18:57"
Sep 5 18:50:11 server2 FaxQueuer[3928]: NOTIFY exit status: 0 (3939)
The same with the wrapper-script in the main configfile "config" enabled
Sep 5 18:55:44 server2 FaxQueuer[4031]: FIFO RECV "Sclient/4043:65"
Sep 5 18:55:44 server2 FaxQueuer[4031]: SUBMIT JOB 65
Sep 5 18:55:44 server2 FaxQueuer[4031]: JOB 65 (suspended dest pri 127 tts
0:00 killtime 2:59:00): CREATE
Sep 5 18:55:44 server2 FaxQueuer[4031]: Apply CanonicalNumber rules to
"870664"
Sep 5 18:55:44 server2 FaxQueuer[4031]: --> match rule "^[^+]", result now
"+492244870664"
Sep 5 18:55:44 server2 FaxQueuer[4031]: --> return result "+492244870664"
Sep 5 18:55:44 server2 FaxQueuer[4031]: JOB 65 (ready dest +492244870664
pri 127 tts 0:00 killtime 2:59:00): READY
Sep 5 18:55:44 server2 FaxQueuer[4031]: FIFO SEND client/4043 msg "S*"
Sep 5 18:55:44 server2 FaxQueuer[4031]: JOB 65 (ready dest +492244870664
pri 127 tts 0:00 killtime 2:59:00): PROCESS
Sep 5 18:55:44 server2 FaxQueuer[4031]: JOB 65 (active dest +492244870664
pri 127 tts 0:00 killtime 2:59:00): ACTIVE
Sep 5 18:55:44 server2 FaxQueuer[4031]: JOB 65 (active dest +492244870664
pri 127 tts 0:00 killtime 2:59:00): PREPARE START
Sep 5 18:55:44 server2 FaxQueuer[4044]: JOB 65 (active dest +492244870664
pri 127 tts 0:00 killtime 2:59:00): CONVERT DOCUMENT: bin/ps2fax -o
docq/doc66.ps;31 -r 196 -w 1728 -l 280 -m 4294967295 -U -1 docq/doc66.ps.65
Sep 5 18:55:44 server2 FaxQueuer[4031]: JOB 65 (active dest +492244870664
pri 127 tts 0:00 killtime 2:59:00): PREPARE DONE
Sep 5 18:55:44 server2 FaxQueuer[4031]: JOB 65 (active dest +492244870664
pri 127 tts 0:00 killtime 2:59:00): CMD START /usr/local/bin/c2faxsend.wrap
-m faxCAPI sendq/q65 (PID 4048)
Sep 5 18:55:54 server2 kernel: r8169: eth2: PHY reset until link up
Sep 5 18:56:14 server2 last message repeated 2 times
Sep 5 18:56:14 server2 kernel: kcapi: appl 3 ncci 0x10101 down
Sep 5 18:56:16 server2 FaxQueuer[4031]: JOB 65 (active dest +492244870664
pri 127 tts 0:00 killtime 2:58:28): CMD DONE: exit status 0x200
Sep 5 18:56:16 server2 FaxQueuer[4031]: DOC UNREF: docq/doc66.ps;31 files
docq/doc66.ps;31
Sep 5 18:56:16 server2 FaxQueuer[4031]: DOC UNREF: expunge imaged files
Sep 5 18:56:16 server2 FaxQueuer[4031]: NOTIFY: bin/notify "doneq/q65"
"done" "0:32"
!!!!
Sep 5 18:56:16 server2 FaxQueuer[4031]: JOB 65 (done dest +492244870664 pri
127 tts 0:00 killtime 2:58:28): SEND DONE: 0:32
!!!!
Sep 5 18:56:16 server2 FaxQueuer[4031]: JOB 65 (done dest +492244870664 pri
127 tts 0:00 killtime 2:58:28): DEAD
Sep 5 18:56:16 server2 FaxQueuer[4031]: JOB 65 (done dest +492244870664 pri
127 tts 0:00 killtime 2:58:28): DELETE
Sep 5 18:56:17 server2 FaxQueuer[4031]: NOTIFY exit status: 0 (4052)
Here the script, invoked by SendFaxCmd:
"/usr/local/bin/c2faxsend.wrap" in mainconfig-file "config"
BTW the file config.c2fax isn't used by hylafax
#!/bin/sh
/usr/local/bin/c2faxsend "$@"
rc=$?
eval qfile=\$$#
vi -c '%s/^returned:0$/returned:'${rc}'/' -c 'wq' ${qfile}
exit $rc
C2faxsend is buggy!! Or did I miss something?
Sorry for the now really long mail too, hope it helps.
Regards
Guido Hecken
> -----Ursprüngliche Nachricht-----
> Von: Andreas Moser [mailto:A.Moser@xxxxxx]
> Gesendet: Montag, 5. September 2005 12:12
> An: hylafax-users@xxxxxxxxxxx
> Cc: guido.hecken@xxxxxxxxxxxxx
> Betreff: [hylafax-users] Desperation with Hylafax and AVM Fritz ISDN Card
PCI on a
> debian system
>
> Hello together.
>
> At the moment I'm very desperate with the installation of the
> hylafax-server on my debian system. The receiving of facsimiles is
> working but there is no way, that the delivery of a facsimile is working
> too. In this mail I will try to explain, how I installed the
> hylafax-server. I used a howto of the german debianhowto page.
>
> At first I installed the debian system with the net_install image
> (debian-31r0a-i386-netinst.iso). After this I configuerd my new system
> (Internet over pppoe).
> Now it was time to start with the hylafax howto.
>
> The first step was to include the AVM driver.
> The AVM Card needs the equivalent kernel sources and headers. So I had
> to install a new kernel (2.6.8-2-686). After the successful
> installation of the new kernel, I had to download and install the AVM
> driver.
>
> cd /usr/src
> wget
ftp://ftp.avm.de/cardware/fritzcrd.pci/linux/suse.93/fcpci-suse93-3.11-07.ta
r.gz
> unp fcpci-suse93-3.11-07.tar.gz
> cd fritz
> ./install
>
> The second step was to install capi support.
> I had to install the isdnactivecards package and configure the capi.conf
> file.
>
> apt-get -u install isdnactivecards
>
> capi.conf:
>
> #card file proto io irq mem cardnr options
> #b1isa b1.t4 DSS1 0x150 7 - - P2P
> #b1pci b1.t4 DSS1 - - - -
> #c4 c4.bin DSS1 - - - -
> #c4 - DSS1 - - - -
> #c4 - DSS1 - - - - P2P
> #c4 - DSS1 - - - - P2P
> #t1isa t1.t4 DSS1 0x340 9 - 0
> #t1pci t1.t4 DSS1 - - - -
> fcpci - - - - - -
> #fcclassic - - 0x300 5 - -
>
> With capiinfo you are able to see, whether your card is working. I got
> the following output:
>
> /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/
>
> Seems so that my controller is working.
> Now I had to check whether the group dialout can access on /dev/capi20
> and the user "uucp" is member in this group too.
>
> alpha:/dev# ls -l capi20
> crw------- 1 uucp dialout 68, 0 2005-09-01 14:14 capi20
>
> alpha:/dev# grep dialout /etc/group
> dialout:x:20:andreas,uucp
>
> ln -s /dev/capi20 /dev/faxCAPI
> chgrp dialout /dev/faxCAPI
>
> The third step is to install hylafax and capi4hylafax.
>
> apt-get -u install hylafax-server hylafax-client capi4hylafax
>
> To install both services I had to change the following config files:
>
> */etc/default/capi4hylafax:*
>
> run_capi4hylafax=1
>
>
> */etc/default/hylafax:*
>
> USE_FAXGETTY=no
> RUN_HYLAFAX=1
>
> Now it was time to configurate the following config files:
> *alpha:/etc/hylafax# cat config
>
> LogFacility: daemon
> ServerTracing: 0xFFFFFFFF
> SendFaxCmd: /usr/local/bin/c2faxsend
> Use2D: no
> MaxDials: 3
> NotifyCmd: "bin/notify"*
>
> *alpha:/etc/hylafax# cat config.faxCAPI
>
> **SpoolDir: /var/spool/hylafax
> FaxRcvdCmd:
> PollRcvdCmd: /var/spool/hylafax/bin/pollrcvd
> FaxReceiveUser: uucp
> FaxReceiveGroup: dialout
> LogFile: /var/spool/hylafax/log/capi4hylafax
> LogTraceLevel: 4
> LogFileMode: 0600
> {
> HylafaxDeviceName: faxCAPI
> RecvFileMode: 0644
> FAXNumber: "+49.xxxx.xxxxxx"
> LocalIdentifier: "Family Moser"
> MaxConcurrentRecvs: 1
> OutgoingController: 1
> OutgoingMSN: "xxxxxx"
> SuppressMSN: 0
> NumberPrefix:
> UseISDNFaxService: 0
> RingingDuration: 0
> {
> Controller: 1
> AcceptSpeech: 1
> UseDDI: 0
> DDIOffset: "12345"
> DDILength: 3
> IncomingDDIs:
> IncomingMSNs: "xxxxxx"
> AcceptGlobalCall: 1
> }
> }
> *
> At the end of the installation I had to publish Hylafax the faxCAPI
"modem".
>
> faxaddmodem faxCAPI
>
> To use Hylafax with a windows Client I've added a new user without
password.
>
> faxadduser andreas
>
> The last step was to install the WHFC Windows Client for Hylafax. If I
> try now to send a facsimile I get the following log messages from
> /var/log/syslog
>
> /Sep 5 14:11:07 alpha HylaFAX[6406]: Filesystem has SysV-style file
> creation semantics.
> Sep 5 14:11:07 alpha FaxQueuer[6377]: FIFO RECV "Sclient/6406:35"
> Sep 5 14:11:07 alpha FaxQueuer[6377]: SUBMIT JOB 35
> Sep 5 14:11:07 alpha FaxQueuer[6377]: JOB 35 (suspended dest pri 127
> tts 0:00 killtime 3:00:00): CREATE
> Sep 5 14:11:07 alpha FaxQueuer[6377]: JOB 35 (ready dest 49109 pri 127
> tts 0:00 killtime 3:00:00): READY
> Sep 5 14:11:07 alpha FaxQueuer[6377]: FIFO SEND client/6406 msg "S*"
> Sep 5 14:11:07 alpha FaxQueuer[6377]: JOB 35 (ready dest 49109 pri 127
> tts 0:00 killtime 3:00:00): PROCESS
> Sep 5 14:11:07 alpha FaxQueuer[6377]: JOB 35 (active dest 49109 pri 127
> tts 0:00 killtime 3:00:00): ACTIVE
> Sep 5 14:11:07 alpha FaxQueuer[6377]: JOB 35 (active dest 49109 pri 127
> tts 0:00 killtime 3:00:00): CMD START /usr/local/bin/c2faxsend -m
> faxCAPI sendq/q35 (PID 6407)
> Sep 5 14:11:17 alpha FaxQueuer[6377]: JOB 35 (active dest 49109 pri 127
> tts 0:00 killtime 2:59:50): CMD DONE: exit status 0
> Sep 5 14:11:17 alpha FaxQueuer[6377]: JOB 35 (sleeping dest 49109 pri
> 126 tts 0:00 killtime 2:59:50): SEND INCOMPLETE: requeue for 7:13;
> Sep 5 14:11:17 alpha FaxQueuer[6377]: JOB 35 (sleeping dest 49109 pri
> 126 tts 0:00 killtime 2:59:50): SLEEP FOR 7:13
> /
> The receiving of a facsimile is no problem. I got two facsmiles so far
> without any errors. I would very happy if someone could help me with
> this problem. Perhaps I forgot something to configure. At this time I
> haven't got any further idea to solve this problem. I hope that someone
> could help me. (Sorry for this long e-mail)
>
> With kind regards
> Andreas
>
> ____________________ HylaFAX(tm) Users Mailing List
_______________________
> To subscribe/unsubscribe, click
http://lists.hylafax.org/cgi-bin/lsg2.cgi
> On UNIX: mail -s unsubscribe hylafax-users-request@xxxxxxxxxxx <
/dev/null
> *To learn about commercial HylaFAX(tm) support, mail sales@xxxxxxxxx*
____________________ HylaFAX(tm) Users Mailing List _______________________
To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
On UNIX: mail -s unsubscribe hylafax-users-request@xxxxxxxxxxx < /dev/null
*To learn about commercial HylaFAX(tm) support, mail sales@xxxxxxxxx*
- Prev by Date: [hylafax-users] c2faxrecv segfault
- Next by Date: [hylafax-users] How to debug faxmail ?
- Previous by thread: Re: [hylafax-users] c2faxrecv segfault
- Next by thread: [hylafax-users] How to debug faxmail ?
- Index(es):
Project hosted by iFAX Solutions