Re: [hylafax-users] Problem Faxing To Brother NSC/IntelliFax

Hi,

We're seeing what appears to be similar behaviour when sending to Brother faxmachines

USR 56k modem, hylafax 4.2.0 - linux Sles9 kernel2.6

Users are complaining about recieved faxes:

a)cut off half of first page but printed the second OK of 2 pages
b)very last page cut off of 5pages in total

Whats the status in your environment ie did you change .conf files., upgrade hylafax to 4.2.5 or try or different faxcard ?

Before upgrading - I'll be keen to forward a failed fax to confirm if it works on a different hylafax version (or faxcard)

Many thanks

Pete

Log cxxxxx snippets from b) above - all appears to be good: - anything else to look for

Jan 23 09:34:47.58: [13909]: NSF remote fax equipment: Brother
Jan 23 09:34:47.58: [13909]: <-- [9:AT+FRH=3\r]
Jan 23 09:34:47.59: [13909]: --> [7:CONNECT]
Jan 23 09:34:48.27: [13909]: --> HDLC<25:FF C0 02 CC 2C 9C 9C AC 2C 6C 9C 2C 9C 04 04 04 04 04 04 04 04 04 04 A8 3B>
Jan 23 09:34:48.27: [13909]: --> [2:OK]
Jan 23 09:34:48.27: [13909]: REMOTE CSI "9496459943"
Jan 23 09:34:48.27: [13909]: <-- [9:AT+FRH=3\r]
Jan 23 09:34:48.29: [13909]: --> [7:CONNECT]
Jan 23 09:34:48.59: [13909]: --> HDLC<11:FF C8 01 00 77 15 23 01 88 E7 CD>
Jan 23 09:34:48.59: [13909]: --> [2:OK]
Jan 23 09:34:48.59: [13909]: REMOTE best rate 14400 bit/s
Jan 23 09:34:48.59: [13909]: REMOTE max A4 page width (215 mm)
Jan 23 09:34:48.59: [13909]: REMOTE max unlimited page length
Jan 23 09:34:48.59: [13909]: REMOTE best vres 15.4 line/mm
Jan 23 09:34:48.59: [13909]: REMOTE best format 2-D MMR
Jan 23 09:34:48.59: [13909]: REMOTE supports T.30 Annex A, 256-byte ECM
Jan 23 09:34:48.59: [13909]: REMOTE best 10 ms/scanline
Jan 23 09:34:48.59: [13909]: USE 14400 bit/s
Jan 23 09:34:48.59: [13909]: USE error correction mode
Jan 23 09:34:48.59: [13909]: USE 0 ms/scanline
Jan 23 09:34:48.59: [13909]: SEND file "docq/doc262.cover;f1"
Jan 23 09:34:48.59: [13909]: USE A4 page width (215 mm)
Jan 23 09:34:48.59: [13909]: USE unlimited page length
Jan 23 09:34:48.59: [13909]: USE 7.7 line/mm
Jan 23 09:34:48.59: [13909]: USE 2-D MMR
Jan 23 09:34:48.59: [13909]: SEND training at v.17 14400 bit/s

an 23 09:37:28.05: [13909]: --> [2:OK]
Jan 23 09:37:28.05: [13909]: SEND send PPS (partial page signal)
Jan 23 09:37:28.05: [13909]: SEND send EOP (no more pages or documents)
Jan 23 09:37:28.05: [13909]: <-- [9:AT+FRH=3\r]
Jan 23 09:37:28.35: [13909]: --> [7:CONNECT]
Jan 23 09:37:29.49: [13909]: --> HDLC<5:FF C8 31 45 8F>
Jan 23 09:37:29.49: [13909]: --> [2:OK]
Jan 23 09:37:29.49: [13909]: SEND recv MCF (message confirmation)
Jan 23 09:37:29.49: [13909]: <-- [9:AT+FRS=7\r]
Jan 23 09:37:30.91: [13909]: --> [2:OK]
Jan 23 09:37:30.91: [13909]: SEND end page
Jan 23 09:37:30.91: [13909]: SEND FAX (000000313): FROM Birch xxx(page 5 of 5 sent in 0:24)
Jan 23 09:37:30.91: [13909]: SEND FAX (000000313): FROM Birch xxx(docq/doc523.ps;f1 sent in 2:11)
Jan 23 09:37:30.91: [13909]: <-- [9:AT+FTH=3\r]
Jan 23 09:37:31.11: [13909]: --> [7:CONNECT]
Jan 23 09:37:31.11: [13909]: <-- HDLC<3:FF C8 DF>
Jan 23 09:37:31.11: [13909]: <-- data [3]
Jan 23 09:37:31.11: [13909]: <-- data [2]
Jan 23 09:37:32.28: [13909]: --> [2:OK]
Jan 23 09:37:32.28: [13909]: MODEM input buffering enabled
Jan 23 09:37:32.28: [13909]: <-- [5:ATH0\r]
Jan 23 09:37:32.52: [13909]: --> [2:OK]
Jan 23 09:37:32.52: [13909]: MODEM set DTR OFF
Jan 23 09:37:32.52: [13909]: STATE CHANGE: SENDING -> MODEMWAIT (timeout 5)
Jan 23 09:37:32.52: [13909]: SESSION END

----- Original Message -----

From: Robert McIntosh

To: hylafax-users@xxxxxxxxxxx

Sent: Thursday, January 12, 2006 10:31 AM

Subject: Re: [hylafax-users] Problem Faxing To Brother NSC/IntelliFax

OK, I've upgraded to 4.2.3 which is the most recent update for rh9.

The problem is still there, with an odd twist after further investigation. Our set-up is unique and awkward (as is probably fairly common) and I fully expect "oh well, no wonder!" responses.

We use WHFC to submit fax jobs to the hylafax queue. We have a custom application written on top of MS Access that takes a form and inserts data and prints it to the print device that translates to postscript and thereby submits it to the fax queue from WHFC. This process works great for probably 99% of our clients that receive the fax. For clients with the  Brother MFC-3100C/MFC-8600 based fax machines (we have two that I know of), they only receive the top fifth of the one-page fax. This continues to be a problem after upgrading hylafax to 4.2.3

The twist is that, from other applications, like MS Word, if I submit a full-page document to WHFC to hylafax, the whole document comes through just fine for the same machines. So, I've written it off to somewhere between MS Access and that specific line of fax machines.

If there are suggestions out there from the hylafax community regarding this issue, I'm all ears. I fully expect that there are none, as it doesn't seem to be a hylafax problem. I can only hope that someone can echo problems faxing to the Brother MFC's.

Many thanks,

Robert

On 1/11/06, Lee Howard <faxguy@xxxxxxxxxxxxxxxx> wrote:
Robert McIntosh wrote:

> I'm running hylafax 4.2.0 and have a steady problem with sending faxes
> to two models of fax machines, the Brother IntelliFax 2800 and Brother
> NSC 8500.  When our installation of hylafax sends a fax to either of
> these machines, only about 1/5 of the first page comes through.  The
> rest of the fax is lost.
>
> Any suggestions on what to look for/adjust?
>
> I've got two modems hooked up to the server: a USR 56k faxmodem 5686
> and a Creative Modem Blaster DE5621.
>
> The following is a log from a "succesful" transmission to the Brother
> Intellifax 2800 (still just the 1/5 of the page received, though - all
> else is lost):

There have been so many fixes since 4.2.0 that it would be best if we
first could determine if the problem is something that has already been
fixed in the last 18 months of work.  Can you upgrade to 4.2.4.2 or
4.2.5rc2 and then try again?  If you cannot upgrade, can I send some
test faxes to those fax machines, and then could you say if the full
page came through or not?

Thanks,

Lee.

--
mcintoshrt@xxxxxxxxx
rupreckt1553 (AIM)