Re: [hylafax-users] zyxel u-1496e config

[Lee Howard <faxguy@deanox.com>]

At 11:46 AM 8/29/01 -0500, Dan wrote:
>
>>here is the part of the message log that is related to hylafax i hope I got
>>it all anyway.
>
>>Okay, thanks... now we need this same section of log entry from when you
>>get the "wedged" errors.
....
>Aug 29 11:20:00 yesdan FaxSend[1897]: <-- [12:AT+FCLASS=?\r]
>Aug 29 11:20:01 yesdan FaxSend[1897]: --> [13:0,1,2,2.0,6,8]
>Aug 29 11:20:01 yesdan FaxSend[1897]: --> [2:OK]

Interesting... what is Class 6?

>Aug 29 11:22:46 yesdan FaxQueuer[939]: HylaClient::send: client/1908: Cannot
>open FIFO: No such file or directory

This isn't a good sign... any idea where the FIFO file went?  It should be
in /var/spool/hylafax

>Aug 29 11:20:19.14: [ 1897]: REMOTE best rate 14400 bit/s
>Aug 29 11:20:19.14: [ 1897]: REMOTE max page width 1728 pixels in 215 mm
>Aug 29 11:20:19.14: [ 1897]: REMOTE max unlimited page length
>Aug 29 11:20:19.14: [ 1897]: REMOTE best vres 7.7 line/mm
>Aug 29 11:20:19.14: [ 1897]: REMOTE best format 2-D MMR
>Aug 29 11:20:19.14: [ 1897]: REMOTE supports T.30 Annex A, ECM
>Aug 29 11:20:19.14: [ 1897]: REMOTE best 0 ms/scanline
>Aug 29 11:20:19.14: [ 1897]: USE 14400 bit/s
>Aug 29 11:20:19.14: [ 1897]: USE 0 ms/scanline
>Aug 29 11:20:19.14: [ 1897]: SEND file "docq/doc17.ps;40"
>Aug 29 11:20:19.14: [ 1897]: USE page width 1728 pixels in 215 mm
>Aug 29 11:20:19.14: [ 1897]: USE unlimited page length
>Aug 29 11:20:19.14: [ 1897]: USE 3.85 line/mm

Hrmm... your modem supports 7.7 line/mm, why isn't it using it?

>Aug 29 11:20:01 yesdan FaxSend[1897]: MODEM Supports 7.7 line/mm

>Aug 29 11:20:19.14: [ 1897]: USE 2-D MR
>Aug 29 11:20:19.14: [ 1897]: SEND training at v.17 14400 bit/s
>Aug 29 11:20:19.14: [ 1897]: <-- [9:AT+FTH=3\r]
>Aug 29 11:20:19.16: [ 1897]: --> [7:CONNECT]
>Aug 29 11:20:19.16: [ 1897]: <-- HDLC<23:FF C0 C2 0E AE 2E A6 CA E6 76 96 16
>2E F6 72 04 04 04 04 04 04 04 04>
>Aug 29 11:20:20.88: [ 1897]: --> [7:CONNECT]
>Aug 29 11:20:20.88: [ 1897]: <-- HDLC<6:FF C8 C1 00 45 1E>
>Aug 29 11:20:21.21: [ 1897]: --> [2:OK]
>Aug 29 11:20:21.21: [ 1897]: DELAY 75 ms
>Aug 29 11:20:21.29: [ 1897]: <-- [11:AT+FTM=145\r]
>Aug 29 11:20:21.75: [ 1897]: --> [10:NO CARRIER]

Well, I wasn't aware that NO CARRIER was a possible modem response at this
point.  I didn't know that +FTM looked for the carrier.  Apparently it does
in your modem.  My understanding was that +FTM simply responded CONNECT
when the modem itself was ready to transmit.

>Aug 29 11:20:21.75: [ 1897]: MODEM No carrier
>Aug 29 11:20:21.75: [ 1897]: Problem sending TCF data
>Aug 29 11:20:21.75: [ 1897]: <-- [9:AT+FRH=3\r]
>Aug 29 11:20:21.76: [ 1897]: --> [5:ERROR]
>Aug 29 11:20:21.76: [ 1897]: MODEM Command error

By this time it's a lost cause.

So... I'm not sure if HylaFAX needs to loop there with +FTM=145 until it
gets a CONNECT, or if we need to do something else, but I can tell you that
I can fax to this destination just fine with my Conexant K56 modem.

Maybe we're looking at a HylaFAX bug, maybe we're looking at a firmware bug
in your modem.  Most likely a HylaFAX bug.

At this point all I can do is say to hope that your modem works with all
other destinations and wait for a HylaFAX or firmware bugfix, or to try a
different modem.

Lee.



____________________ HylaFAX(tm) Users Mailing List _______________________
 To unsub: mail -s unsubscribe hylafax-users-request@hylafax.org < /dev/null