Re: [hylafax-users] hylafax does not answer rings

[Steve-Kai Vyska <vyska@xxxxxx>]

Hallo

ok dmeg of course tells a lot but nothing about the dev :-( This is what I 
found for ISDN or CAPI

CAPI Subsystem Rev 1.1.2.8
fcpci: module license 'Proprietary' taints kernel.
fcpci: AVM FRITZ!Card PCI driver, revision 0.7.2
fcpci: (fcpci built on Jun 30 2006 at 12:53:52)
fcpci: -- 32 bit CAPI driver --
ACPI: PCI Interrupt 0000:00:0a.0[A] -> GSI 18 (level, low) -> IRQ 201
fcpci: AVM FRITZ!Card PCI found: port 0xd000, irq 201
fcpci: Loading...
fcpci: Driver 'fcpci' attached to fcpci-stack. (152)
fcpci: Stack version 3.11-07
kcapi: Controller 1: fcpci-d000-201 attached
kcapi: card 1 "fcpci-d000-201" ready.
fcpci: Loaded.
capifs: Rev 1.1.2.3
capi20: Rev 1.1.2.7: started up with major 68 (middleware+capifs)
ISDN subsystem Rev: 1.1.2.3/1.1.2.3/1.1.2.2/1.1.2.3/1.1.2.2/1.1.2.2 loaded
capidrv-1: now up (2 B channels)
capidrv-1: D2 trace enabled
capidrv: Rev 1.1.2.2: loaded

So I linked faxCAPI to isdnctr0 and isdnctrl1 but bouth the same. nothing 
happends :-(

Steve

Am Montag, 10. Juli 2006 16:51 schrieb Lívio Cipriano:
> Like I told you, in my instalation (SuSE 9.2) it's "/dev/isdnctrl1". I
> think that in yours must be the same, because you must be using the
> proprietary driver of AVM, are you?
>
> Check the startup log with dmesg to see what is happen whem the driver is
> loaded.
>
> Lívio Cipriano
>
> ----- Original Message -----
> Ah ok,
>
> I tried a little bit an you are right. /dev/capi20 has no device connected.
>  So the question ist, where das the fcpci-driver connect to? How can I find
>  this out?
>
> Steve
>
> Am Montag, 10. Juli 2006 16:22 schrieb Lívio Cipriano:
> > Hi Steve,
> >
> > I'm using a SuSE 9.2 instalation and my physical device is
> > /dev/isdnctrl1. I think that capi20 is just a virtual device. The setup
> > instructions of capi4hylafax says that we should use faxCAPI as the
> > hylafax device. Is it different for Debian?
> >
> > Livio Cipriano
> >
> > ----- Original Message -----
> > Hallo,
> >
> > I checked your config, an exept that I use capi20 as device and of course
> > other Area-Codes I have the same configuration. But I also changed
> > everything to your configs (dev and user root) but the result was the
> > same. I get an notification, but It does not go off-hook and The
> > ISDN-Service says not available :-(
> >
> > Hi Steve,
> >
> >
> > Seams that you have the same hylafax instalation. I also have a AVM Card
> > and it took a lot of time setting up the hylafax server, but now it's
> > running and I setup up 1 outgoing number and 2 incoming.
> >
> > Let me sending you my config files, that you can study and adapt.
> >
> > Let me know if it helped.
> >
> > Regards
> >
> > Livio Cipriano
> >
> > >>CONFIG
> > >>-------------------------------------------------------------------
> > >>LogFacility: daemon
> > >>CountryCode: 351
> > >>AreaCode: 1
> > >>LongDistancePrefix: 1
> > >>InternationalPrefix: 00
> > >>DialStringRules: "etc/dialrules"
> > >>ServerTracing: 1
> > >>SessionTracing: 0xffffffff
> > >>MaxConcurrentCalls: 2
> > >>MaxSendPages: 1024
> > >>ModemGroup: any:.*
> > >>SendFaxCmd: /var/spool/fax/bin/faxsend
> > >>
> > >>
> > >>CONFIG.faxCAPI
> > >>------------------------------------------------------------------
> > >>
> > >>PollRcvdCmd: /var/spool/fax/bin/pollrcvd
> > >>FaxReceiveUser: root #fax
> > >>FaxReceiveGroup: dialout
> > >>LogFile: /var/spool/fax/log/capifax.log
> > >>LogTraceLevel: 4
> > >>LogFileMode: 0600
> > >>{
> > >> #
> > >> HylafaxDeviceName: faxCAPI
> > >> RecvFileMode: 0600
> > >> #
> > >> FAXNumber: "123456789"
> > >> #
> > >> LocalIdentifier: "XXX"
> > >> MaxConcurrentRecvs: 2
> > >>
> > >> # ----------- outgoing params -----------
> > >>
> > >> OutgoingController: 1
> > >> OutgoingMSN: 123456789
> > >> SuppressMSN: 0
> > >> NumberPrefix:
> > >> UseISDNFaxService: 0
> > >> RingingDuration: 0
> > >>
> > >> # ----------- incoming params -----------
> > >> {
> > >>
> > >> Controller: 1
> > >> AcceptSpeech: 0
> > >> UseDDI: 0
> > >> DDIOffset:
> > >> DDILength:
> > >> IncomingDDIs:
> > >> IncomingMSNs: 123456789,987654321
> > >> AcceptGlobalCall: 0
> > >> }
> > >>}
> >
> > ----- Original Message -----
> > Hallo,
> >
> > I'm trying to set up an hylafax server on an dial-in ISDN server using an
> > passiv AVM PCI Fritz Card
> >
> > According to HOWTOs found in the www I first set up the cap-driver wich
> > no seems to work properly
> >
> > capiinfo says:
> > --------------------------------------------------------
> > 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
> > 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
> > ------------------------------------------
> >
> > so this seems to work.
> >
> > Next I setup the dialin usin ipppd which also wors, since the dial in is
> > possible :-)
> >
> > Next was to setup hylafax.
> >
> > hylafax and capi4hylafax are installed and setup to the faxnumer. I
> > changed the capi Driver from capiFAX to capi20 since this is the /dev an
> > debian.
> >
> > than I start capi4hylafax and haylafax it self an they come ok correctly.
> >
> > But as an ring comes in nothing happens :-(
> >
> > /usr/bin/c2faxrecv runs
> >
> > in the log files is written:
> >
> > ------------------------
> > ul 10 09:53:34.83: [32076]: c2faxrecv - INFO:
> > C4H-Version 01.03.01svn (32Bit).
> >
> > Jul 10 09:53:34.83: [32076]: c2faxrecv - INFO: The SpoolDirectory
> > is /var/spool/hylafax.
> > Jul 10 09:53:34.83: [32076]: c2faxrecv - INFO: Changed to effective
> > user "uucp" and group "dialout" succesfully.
> > Jul 10 09:53:34.83: [32076]: c2faxrecv - INFO:
> > Device "capi20" uses 2 receive thread(s) with the following config:
> > Jul 10 09:53:34.83: [32076]: c2faxrecv - INFO: Controller=1 : accept all
> > Jul 10 09:53:34.83: [32076]: c2faxrecv - INFO:
> > Started in Hylafax mode and waiting on incoming calls.
> > ------------------------
> >
> > so this is really online
> >
> > As an Ring comes in, syslog says:
> >
> > ------------------------
> > FaxQueuer[32189]: HylaFAX (tm) Version 4.3.0
> > FaxQueuer[32189]: Copyright (c) 1990-1996 Sam Leffler
> > FaxQueuer[32189]: Copyright (c) 1991-1996 Silicon Graphics, Inc.
> > HylaFAX[32191]: HylaFAX INET Protocol Server: restarted.
> > Kernel: capidrv-1: incoming call incommingnumber,1,1,faxnumber
> > kernel: capidrv-1: patching si2=1 to 0 for VBOX
> > kernel: isdn_net: call from incommingnumber -> 0 faxnumber ignored
> > kernel: isdn_tty: call from incommingnumber -> faxnumber ignored
> > kernel: capidrv-1: incoming call incommingnumber,1,0,faxnumber ignored
> > ------------------------
> >
> > So why is it ignored?
> >
> > TNX for all hints, and sorry for my englisch, it has been a while I had
> > to write :-)
> >
> > Steve
> >
> > ____________________ 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*
> >
> > ____________________ 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*
>
> ____________________ 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*