NetNews Usenet Archive 1992 #20/NN_1992_20.iso/spool/comp/dcom/fax/1643

Internet Message Format | 1992-09-08 | 7.9 KB

Path: sparky!uunet!wupost!waikato.ac.nz!comp.vuw.ac.nz!am.dsir.govt.nz!kauri.ida.dsir.govt.nz!olof
Newsgroups: comp.dcom.fax
Subject: Problems with Supra and Netfax 3.2 (again)
Message-ID: <[e-mail]>
From: [e-mail] (Olof Olsson)
Date: 8 Sep 92 19:54:35 GMT
Sender: [e-mail]
Organization: DSIR/IDA Auckland, New Zealand
Lines: 193

I have posted this question before, but I haven't been able to solve
it. I have also talked to people at Supra using e-mail, but they have
not been very helpful. Here is the story:

Configuration: Supra Faxmodem+ V32bis connected to Sun Sparcstation
IPX running a modified version of GNU Netfax 3.2.

Problem: I am having problem sending faxes to some remote fax
machines.

Symptoms: I get an "FHNG: 52" from the remote machine after sending
the first page. Well, the first page doesn't actually arrive, even
though my Supra seems to think so. A sample of the log:

Aug 17 13:14:40 totara fax[1001]: sending to 033589506
Aug 17 13:14:40 totara fax[1766]: syncing with 10 tries
Aug 17 13:14:46 totara fax[1766]: modem is now in sync
Aug 17 13:14:46 totara fax[1766]: enabling bit reversal
Aug 17 13:14:46 totara fax[1766]: numeric response code: 0
Aug 17 13:14:46 totara fax[1766]: dialing: 033589506
Aug 17 13:14:58 totara fax[1766]: parse_text_response: parsing: "+FCON"
Aug 17 13:15:00 totara fax[1766]: parse_text_response: parsing: "+FCSI: "        64 3 3589506""
Aug 17 13:15:01 totara fax[1766]: parse_text_response: parsing: "+FDIS: 1,3,0,2,1,0,0,2"
Aug 17 13:15:01 totara fax[1766]: numeric response code: 0
Aug 17 13:15:01 totara fax[1766]: sending g3 file
Aug 17 13:15:01 totara fax[1766]: setting xmit params: 0 1 0 0
Aug 17 13:15:14 totara fax[1766]: parse_text_response: parsing: "+FDCS: 0,0,0,3"
Aug 17 13:15:14 totara fax[1766]: numeric response code: 1
Aug 17 13:15:26 totara fax[1766]: numeric response code: 0
Aug 17 13:15:26 totara fax[1766]: send of file has completed
Aug 17 13:15:26 totara fax[1766]: end of current page, another page will be sentAug 17 13:15:44 totara fax[1766]: parse_text_response: parsing: "+FHNG: 52"
Aug 17 13:15:44 totara fax[1766]: numeric response code: 0
Aug 17 13:15:44 totara fax[1766]: hangup code received while sending pages
Aug 17 13:15:44 totara fax[1766]: send of page 0 failed
Aug 17 13:15:44 totara fax[1766]: hanging up the modem
Aug 17 13:15:45 totara fax[1766]: numeric response code: 0
Aug 17 13:15:49 totara fax[1766]: modem is now in unsynced
Aug 17 13:15:49 totara fax[1766]: unable to send fax to 033589506
Aug 17 13:15:49 totara fax[1001]: child exited with rc=0, status=4

Comments: The only thing that appears on the remote fax is my
"station-id". I don't know why it gets printed, but that's the only
thing that appears on the first page.

I know that the new Supra roms are supposed to fix a problem with the
modem being unable to connect to some fax machines (appearently some
panafaxes, canons, and harris machines were affected). I not sure
though that my problem will be fixed by the new roms.

Any help with my problem would be greatly appreciated (before I
trash the Supra and buy some fax modems that work!).

I am including a some material from [e-mail]
that seem to have the same problem as myself:

-------------------------------------------

From [e-mail] Mon Sep  7 16:30:32 1992
Subject: Re: Problems with Netfax and Supra
To: [e-mail] (Olof Olsson)

>
> You said you were going to send me some info about what you have discovered
> so far. Could you please send it to me as soon as is convenient for you?
> (I am trying to get some action out of our Supra agent, and I want to
> collect as much info as possible before talking to them.)

>From supra![e-mail] Tue Aug 18 20:38:48 1992
Received: by CS.ORST.EDU (15.11/1.15)
    id AA15428; Tue, 18 Aug 92 19:40:20 edt
Received: from supra with uucp; Tue, 18 Aug 92 16:29:30
Received: from uucp.supra.uucp by supra.supra.UUCP
    id aa22113; Tue, 18 Aug 92 16:29:29 PDT
To: orstcs!tinker.appliedmicro.ns.ca!dinn (Michael 'Moose' Dinn)
Subject: Re: Mail bounced -- here it is again
In-Reply-To: Your message of Fri, 14 Aug 92 13:47:10 PDT.
             <[e-mail]>
Date: Tue, 18 Aug 92 16:29:27 PDT
From: supra![e-mail]
Message-Id:  <[e-mail]>
Status: OR


> A technical question:
>
> Have you tested the modem with NetFax 3.2 under SunOS?
>

No we really haven't.  All of our machines are SYSV types and I haven't had
the time to convert the code.

I did ask a engineer to look at it, I don't know if he will come up with
anything.

Kenny                             Supra Tech Support
[e-mail]                     503-967-2440
-----------------------------------------------------------------------------
"I assumed you needed help.  I see I am in error."
        - Spock




>From dinn Wed Aug 19 10:29:37 1992
Subject: Sometime I've got to reconfigure our mailer...
To: [e-mail]
Date: Wed, 19 Aug 92 10:29:37 ADT
X-Mailer: ELM [version 2.3 PL11]

> From: dinn (Michael 'Moose' Dinn)
> Subject: Re: Mail bounced -- here it is again
> To: supra![e-mail]
> Date: Wed, 19 Aug 92 10:26:07 ADT
> In-Reply-To:  <[e-mail]>; from "[e-mail]" at Aug 18, 92 4:29 pm
> X-Mailer: ELM [version 2.3 PL11]
>
> > No we really haven't.  All of our machines are SYSV types and I haven't had
> > the time to convert the code.
> I think there's a SYSV port of NetFax out there. Want me to go find it for
> you?
>
> > I did ask a engineer to look at it, I don't know if he will come up with
> > anything.
> Better than nothing -- Thanks!
>

>From supra![e-mail] Wed Aug 19 16:39:04 1992
Received: by CS.ORST.EDU (15.11/1.15)
    id AA14631; Wed, 19 Aug 92 15:40:31 edt
Received: from supra with uucp; Wed, 19 Aug 92 12:30:48
Received: from uucp.supra.uucp by supra.supra.UUCP
    id aa05429; Wed, 19 Aug 92 12:30:47 PDT
To: orstcs!tinker.appliedmicro.ns.ca!dinn (Michael 'Moose' Dinn)
Subject: Re: FAX Info..
In-Reply-To: Your message of Wed, 19 Aug 92 13:01:33 PDT.
             <[e-mail]>
Date: Wed, 19 Aug 92 12:30:44 PDT
From: supra![e-mail]
Message-Id:  <[e-mail]>
Status: OR


> > : >My problem with NetFax is simple: at the end of a sent page, I often get
 an
> > : >FHNG: 52 from the modem. Interestingly, this happens only enough to be
> > : >annoying.
> > :
> > : I have the same problem except that I get a FHNG: 54 sometimes as
> > : well. I use NetFax 3.2 and Supra V32bis fax modem on a Sun4.
> > :
> > :
> > : Would be *very* greatful for any pointers,
> > :
> > :     Olof
> >
> > +FHNG: 52 is described as Phase-D (negotiation for next page)
> >
> >         error: "No response to MPS"
> >
> > Quite likely the distant end was requested to retrain and hung up instead o
f
> > complying.  This is a rampant condition we've addressed with DFax for the N
eXT.
>
> This looks interesting... ideas anyone? I suspect to make a good judgement
> on whether this is a problem one would have to be more familiar with the FAX
> protocol than I am..

This is at the software level of control, which is also what the engineer said
that I showed it to.  We have many other packages that work, so I have a hard
time believing that it is a modem problem.


Kenny                             Supra Tech Support
[e-mail]                     503-967-2440
-----------------------------------------------------------------------------
"When fishing for boys, the proper bait is girls."
        - Mary Anne




--
 Michael Dinn                       |  [e-mail]
 Network Technologist               |  [e-mail] (school)
 Applied Microelectronics Institute |  [phone] Tel ; 429-9983 FAX



--
Olof Olsson                                               Machine Vision Team
E-mail: [e-mail]                         Industrial Research Ltd
Phone: [phone], Fax: [phone]              Auckland, New Zealand