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] Problems with resolution



Hmm..

the hylafax log manpage says:


REJECT: High resolution document is not supported by client, image resolution %g line/mm. The document to be transmitted was imaged using 7 line/mm, but the client only supports 3.85 line/mm. This is not a fatal error; the server will disconnect and reimage the document using the newly discovered client capabilities.

I can not see my server (hylafax+5.1.3) doing this ?

Moritz


On 4/24/07, Lee Howard <faxguy@xxxxxxxxxxxxxxxx> wrote:
Moritz Winterberg wrote:

> I'm trying to send a fax to myself using an EICON DIVA PRI card.
> The output tells me I can send but not receive in high resolution mode:
>
> [High resolution document is not supported by client..]
>
> any idea how to tell the modem to use high res mode ? Do I have to set
> some AT command in the modem config ?
>
> Apr 24 20:05:02.31: [20556]: --> [22:+FDIS: 0,8,2,2,0,2,0,0]
> Apr 24 20:05:02.31: [20556]: --> [2:OK]
> Apr 24 20:05:02.31: [20556]: REMOTE best rate 21600 bit/s
> Apr 24 20:05:02.31: [20556]: REMOTE max A3 page width (303 mm)
> Apr 24 20:05:02.31: [20556]: REMOTE max unlimited page length
> Apr 24 20:05:02.31: [20556]: REMOTE best vres 3.85 line/mm
> Apr 24 20:05:02.31: [20556]: REMOTE format support: MH
> Apr 24 20:05:02.31: [20556]: REMOTE supports T.30 Annex C, half duplex
> ECM


If your receiver here really does support high resolution then the Diva Server is preventing you from seeing that. Realize that the Diva Server kind of acts as a fax proxy - so you can't completely trust that the picture that the Diva Server presents to you is the same picture that some other device may let you see.

Anyway, according to the Diva Server's responses here the remote does
not support anything other than normal resolution.

Also, notice the "T.30 Annex C" claim there - it's incorrect, no doubt.
So it would seem that Eicon has changed things in that regard to more
correctly meet the Class 2 spec (instead of the Class 2.0 one).  It
won't help you for this resolution issue, but you should change your
modem config file to use:

Class2ECMType: 2

(Or just remove the "Class2ECMType: 2.0" line entirely.)

Lee.



--
--
Moritz Winterberg - winterberg@xxxxxxxxxx
Telefon: +49 (0)211-63 55 55-36
Telefax: +49 (0)211-63 55 55-22

indigo networks GmbH - Gladbacher Str. 74 - 40219 Düsseldorf
HRB Düsseldorf 39841 - Geschäftsführer: Thilo Salmon, Tim Mois
Steuernummer: 133/5838/1589, Umsatzsteuer-ID: DE219349391

www.sipgate.de - www.sipgate.at - www.sipgate.co.uk

____________________ 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