HylaFAX The world's
most advanced open source fax server
|
|
[
Date Prev][
Date Next][
Thread Prev][
Thread Next]
[
Date Index]
[
Thread Index]
EOP / Phase B problems -- Zoom Modem
HylaFax v4.0pl2 - Linux i586 machine (Slackware 3.5)
Zoom VFX modem - running class 2
I'm having repeated problems with faxes erroring out with EOP and Phase B
problems.
It seems like it is always the same fax machines that I have the problems
with.
The strange thing is that I have used this modem to connect to those same
fax machine before without problems (using a different FAX server software
program).
Can anyone give me any guidance on what I can do to make this modem more
compatible?
Here are the log excerpts:
EOP problem:
Dec 03 20:47:13.49: [ 2178]: SEND end page
Dec 03 20:47:17.88: [ 2178]: --> [2:OK]
Dec 03 20:47:17.88: [ 2178]: SEND send EOP (no more pages or documents)
Dec 03 20:47:17.88: [ 2178]: <-- [9:AT+FET=2\r]
Dec 03 20:47:33.30: [ 2178]: --> [9:+FHNG: 54]
Dec 03 20:47:33.30: [ 2178]: REMOTE HANGUP: No response to EOP repeated 3
times (code 54)
Dec 03 20:47:33.30: [ 2178]: SEND: No response to EOP repeated 3 times;
Giving up after 3 attempts to send same page "docq/doc149.ps;70", dirnum 0
Dec 03 20:47:33.30: [ 2178]: <-- [5:ATH0\r]
Dec 03 20:47:33.51: [ 2178]: --> [2:OK]
Dec 03 20:47:33.51: [ 2178]: SESSION END
Phase B problem:
Dec 03 20:57:43.72: [ 2263]: <-- [24:AT+FDIS=0,5,0,2,1,0,0,0\r]
Dec 03 20:57:43.97: [ 2263]: --> [2:OK]
Dec 03 20:57:43.97: [ 2263]: <-- [7:AT+FDT\r]
Dec 03 20:57:51.42: [ 2263]: --> [9:+FHNG: 20]
Dec 03 20:57:51.42: [ 2263]: REMOTE HANGUP: Unspecified Transmit Phase B
error (code 20)
Dec 03 20:57:51.54: [ 2263]: --> [2:OK]
Dec 03 21:00:51.54: [ 2263]: MODEM <Timeout>
Dec 03 21:00:51.54: [ 2263]: SEND: Unspecified Transmit Phase B error;
Giving up after 3 attempts to send same page "docq/doc163.ps;70", dirnum 0
Dec 03 21:00:51.54: [ 2263]: <-- [5:ATH0\r]
Dec 03 21:00:51.91: [ 2263]: --> [2:OK]
Dec 03 21:00:51.91: [ 2263]: SESSION END
I have seen in the archives that I have been able to get to that other
people have asked this same problem, but I have not found any pointers or
suggestions for fixing / working around the problem.
Any suggestions that you have will be greatly appreciated.
Cheers,
Jeff
--
-- Jeff Scott -- Technical Designer -- jeff@realbeer.com
-- Real Beer, Inc. -- (415) 522-1516x310 (voice) -- (415) 522-1535 (fax)
-- Internet Publishers and Consultants -- http://www.realbeer.com
-- The single largest source for beer information, known to man!