On Fri, 2007-01-12 at 15:22 +0100, Alain NAKACHE wrote: > Damjan Jovanovic a écrit : > > On Fri, 2007-01-12 at 11:42 +0100, Alain NAKACHE wrote: > > > > > Dear all, > > > > > > I'm very disapointed since my several attempts to send a fax with TxFAX > > > have failed. > > > > > > Here is my config : > > > - OpenPBX.org 1.2-RC3 > > > - spandsp-20070105 (same result with spandsp 0.0.3pre27) > > > - libtiff 3.8.2 > > > - zaptel 1.4.0 > > > - libpri 1.4.0 > > > - Hardware : Digium card TE210P (2 T1/E1 - used with 1 E1) > > > - OS : CentOS 4.4 > > > - Platform : Intel(R) Pentium(R) III -1133MHz with 1Gb RAM > > > > > > > > > I try to send with a call file a follow : > > > <snip> > > > Channel: Zap/g1/0426682409 > > > CallerID: ALINTO <426680953> > > > MaxRetries: 3 > > > WaitTime: 20 > > > retryTime: 5 > > > SetVar: LOCALHEADERINFO=Il faut beau et chaud > > > SetVar: LOCALSTATIONID=BEAUCHAUD-426680953 > > > Application:TxFAX > > > Data:/var/tmp/lisa.tifg4|caller|ecm|debug > > > </snip> > > > > > > The called fax is an Audiocodes Mediant 2000 but same results are > > > obtained with an HP multifonction printer through a PSTN line. > > > > > > Log result (full.txt.bz2) is joined to this mail . > > > > > > Can you help me to find where is the problem. > > > > > > > Look at /proc/interrupts and make sure the card isn't sharing an IRQ, if > > it is, move it to a different slot. > > > > > /proc/interrupts > CPU0 > 0: 101364487 local-APIC-edge timer > 8: 1 IO-APIC-edge rtc > 9: 7 IO-APIC-level acpi > 185: 565 IO-APIC-level ohci_hcd > 193: 100317217 IO-APIC-level wct2xxp > 201: 264822 IO-APIC-level eth0 > 217: 101519 IO-APIC-level ide2 > NMI: 0 > LOC: 101369685 > ERR: 0 > MIS: 0 > > How to check if interrupt is shared by another hardware ?
It's not. If it was shared, you would have comma-separated values on the
same line, which you don't.
Try what Bartek suggested with PCI latencies.
The only reason RxFAX/TxFAX ever failed me over the ZAP channel are
timing issues from interrupt sharing and the like, it was unbreakable in
every other case. Is DMA enabled on your hard drives (hdparm -
d /dev/hd*)?
> > Try with the latest SVN.
> >
> Impossible since automake and libtool from CentOS 4(RHEL4) are too
> old.
I got that working on CentOS 4.3 :-). Install them from source.
> If yes, how to force one hardware ?
> > Try without |ecm.
> >
> Already done, same result
> > Try without LOCALSTATIONID and LOCALHEADERINFO.
> >
> Same result
> > Try increasing WaitTime.
> >
> Same result
> > Try TxFAX -> RxFAX.
> >
> >
> New contexts :
> <snip>
> [zaptel-in]
>
> exten => _X.,1,Answer
> exten => _X.,n,Goto(faxin,s,1)
>
> [faxin]
> exten => s,1,Set(LOCALSTATIONID=426680950)
> exten => s,n,Set(LOCALHEADERINFO=ALINTO RXFAX)
> exten => s,n,Set(FAXFILE=/tmp/${UNIQUEID}.tif)
> exten => s,n,Set(FAXFILENOEXT=/tmp/${UNIQUEID})
> exten => s,n,RxFAX(${FAXFILE}|ecm|debug)
> exten => s,n,NoOp(RX: REMOTESTATIONID is ${REMOTESTATIONID})
> exten => s,n,NoOp(RX: PHASEESTATUS is ${PHASEESTATUS})
> exten => s,n,Hangup
> </snip>
>
> *CLI> show channels
> Channel Location State Application(Data)
> Zap/8-1 [EMAIL PROTECTED]:5 Up RxFAX
> (/tmp/1168610644.1.tif|ec
> Zap/1-1 [EMAIL PROTECTED]:1 Up TxFAX
> (/var/tmp/kbis.tifg4|call
> 2 active channels
> 1 active call
>
> TxFax -> RxFax done but unsuccessful. Same result as above.
But, what are the errors on the sender/receiver?
> Do you want more logs ?
Try with the attached image, it's known to work (CtRiX faxed it many
times around the world).
Try downgrading/upgrading libtiff and then recompiling both spandsp and
openpbx. Versions of libtiff known to work are somewhere on the soft-
switch website.
Make sure there isn't 2 versions of spandsp installed (like one in /usr,
another in /usr/local).
Try spandsp 0.0.3pre24 and 0.0.3pre26, those are the ones I tested on
most.
Try faxing over T.38 to rule out the possibility of any ZAP channel
issues.
Speak to coppice on IRC.
> Thanks
> Alain
Good luck
Damjan
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
> _______________________________________________
> Openpbx-users mailing list
> [email protected]
> http://lists.openpbx.org/mailman/listinfo/openpbx-users
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
test3_opbx_rulez.tif
Description: TIFF image
_______________________________________________ Openpbx-users mailing list [email protected] http://lists.openpbx.org/mailman/listinfo/openpbx-users
