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] All faxes failing



Now everything is working.  I'm thinking this telco related.  I have
many messages in my /var/log/messages file that look like this:

Apr  4 23:23:36 hylafax01 kernel: zaptel Disabled echo canceller because
of tone (rx) on channel 10
Apr  4 23:23:37 hylafax01 kernel: zaptel Disabled echo canceller because
of tone (rx) on channel 4
Apr  4 23:23:40 hylafax01 kernel: zaptel Disabled echo canceller because
of tone (rx) on channel 5
Apr  4 23:23:44 hylafax01 kernel: zaptel Disabled echo canceller because
of tone (rx) on channel 8
Apr  4 23:24:25 hylafax01 kernel: zaptel Disabled echo canceller because
of tone (rx) on channel 1
Apr  4 23:24:45 hylafax01 kernel: zaptel Disabled echo canceller because
of tone (rx) on channel 2
Apr  4 23:25:38 hylafax01 kernel: zaptel Disabled echo canceller because
of tone (rx) on channel 2
Apr  4 23:25:44 hylafax01 kernel: zaptel Disabled echo canceller because
of tone (rx) on channel 6
Apr  4 23:25:45 hylafax01 kernel: zaptel Disabled echo canceller because
of tone (rx) on channel 9
Apr  4 23:25:46 hylafax01 kernel: zaptel Disabled echo canceller because
of tone (rx) on channel 4
Apr  4 23:25:49 hylafax01 kernel: zaptel Disabled echo canceller because
of tone (rx) on channel 3
Apr  4 23:25:56 hylafax01 kernel: zaptel Disabled echo canceller because
of tone (rx) on channel 7
Apr  4 23:28:58 hylafax01 kernel: zaptel Disabled echo canceller because
of tone (rx) on channel 1
Apr  4 23:29:02 hylafax01 kernel: zaptel Disabled echo canceller because
of tone (rx) on channel 2
Apr  4 23:29:39 hylafax01 kernel: zaptel Disabled echo canceller because
of tone (rx) on channel 2
Apr  4 23:29:40 hylafax01 kernel: zaptel Disabled echo canceller because
of tone (rx) on channel 1
Apr  4 23:30:34 hylafax01 kernel: zaptel Disabled echo canceller because
of tone (rx) on channel 1
Apr  4 23:30:37 hylafax01 kernel: zaptel Disabled echo canceller because
of tone (rx) on channel 2
Apr  4 23:31:06 hylafax01 kernel: zaptel Disabled echo canceller because
of tone (rx) on channel 1
Apr  4 23:31:42 hylafax01 kernel: zaptel Disabled echo canceller because
of tone (rx) on channel 1

But I havent seen one since everything started working.  Weird that both
PRI's from separate providers would have the same issue.

-Dan

-----Original Message-----
From: hylafax-users-bounce@xxxxxxxxxxx
[mailto:hylafax-users-bounce@xxxxxxxxxxx] On Behalf Of Dan Brummer
Sent: Wednesday, April 04, 2007 11:56 PM
To: Lee Howard
Cc: hylafax-users@xxxxxxxxxxx
Subject: Re: [hylafax-users] All faxes failing

My /var/spool/hylafax/docq dir contains files like this:

doc832061.ps.832059  doc832127.ps.832125  doc832193.ps.832191
doc832501.ps         doc832567.ps
doc832062.ps.832060  doc832128.ps.832126  doc832194.ps.832192
doc832502.ps.832500  doc832568.ps
doc832063.ps.832061  doc832129.ps.832127  doc832195.ps.832193
doc832503.ps.832501  seqf
doc832064.ps.832062  doc832130.ps.832128  doc832196.ps.832194
doc832504.ps.832502
doc832065.ps.832063  doc832131.ps.832129  doc832197.ps.832195
doc832505.ps.832503
doc832066.ps.832064  doc832132.ps.832130  doc832198.ps.832196
doc832506.ps.832504
doc832067.ps.832065  doc832133.ps.832131  doc832199.ps.832197
doc832507.ps.832505

I take it that the ones with a .xxxxx after the .ps are not right
correct?

-Dan

-----Original Message-----
From: Lee Howard [mailto:faxguy@xxxxxxxxxxxxxxxx]
Sent: Wednesday, April 04, 2007 11:53 PM
To: Dan Brummer
Cc: hylafax-users@xxxxxxxxxxx
Subject: Re: [hylafax-users] All faxes failing

Dan Brummer wrote:

>Apr 04 23:01:42.57: [25966]: USE 9600 bit/s Apr 04 23:01:42.57: 
>[25966]: USE error correction mode Apr 04 23:01:42.57: [25966]: <-- 
>[9:AT+FTH=3\r] Apr 04 23:01:42.57: [25966]: --> [7:CONNECT] Apr 04 
>23:01:42.57: [25966]: <-- HDLC<3:FF C8 DF> Apr 04 23:01:42.57: [25966]:

><-- data [3] Apr 04 23:01:42.57: [25966]: <-- data [2] Apr 04 
>23:01:43.65: [25966]: --> [2:OK] Apr 04 23:01:43.65: [25966]: MODEM 
>input buffering enabled Apr 04 23:01:43.65: [25966]: <-- [5:ATH0\r] Apr

>04 23:01:43.75: [25966]: --> [2:OK]
>

Double-check how you are submitting faxes.  The log you show basically
is telling you that faxq invoked faxsend to transmit a fax, but when
faxsend got around to looking at the documents to transmit (now, after
the call has been placed) it doesn't find anything to transmit.

So most likely the problem is that the documents are disappearing from
/var/spool/hylafax/docq (faxqclean malfunction?) or that the client is
submitting bad documents.

Thanks,

Lee.

____________________ 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*




Project hosted by iFAX Solutions