HylaFAX The world's
most advanced open source fax server
|
|
[
Date Prev][
Date Next][
Thread Prev][
Thread Next]
[
Date Index]
[
Thread Index]
[hylafax-users] R: T.30 Error
Thank you very much.
The modem I use is an internal modem based on 536ep chip.
The long delay was only a trial.
I found that rising this time to 90ms with
Class1SwitchingCmd: "<delay:9>"
reduces drastically the number of wrong faxes.
I tried to arrive to 150ms but with no luck.
I forgot to correct this value.
I can try the absolutely opposite way, to lower this time a lot...
Bye and thanks
Tiziano
-----Messaggio originale-----
Da: Lee Howard [mailto:faxguy@xxxxxxxxxxxxxxxx]
Inviato: martedì 27 luglio 2004 18.04
A: Tiziano Arbizzani
Cc: hylafax-users@xxxxxxxxxxx
Oggetto: Re: [hylafax-users] T.30 Error
On 2004.07.27 01:27 hylafax-users-bounce@xxxxxxxxxxx wrote:
> Hi all,
> I will appreciate if someone can give me an advice for a little
> problem I had.
> Sometimes, receiving multi-page faxes, I get no answer to the AT+FRM
> command after MCF.
What kind of modem are you using?
> Jul 27 04:00:37.89: [ 8299]: RECV: begin page
> Jul 27 04:01:00.45: [ 8299]: RECV: 2371 total lines, 0 bad lines, 0
> consecutive bad lines
> Jul 27 04:01:00.45: [ 8299]: RECV: end page
> Jul 27 04:01:00.45: [ 8299]: --> [10:NO CARRIER]
> Jul 27 04:01:00.45: [ 8299]: <-- [9:AT+FRH=3\r]
> Jul 27 04:01:00.61: [ 8299]: --> [7:CONNECT]
> Jul 27 04:01:01.74: [ 8299]: --> [2:OK]
> Jul 27 04:01:01.74: [ 8299]: RECV recv MPS (more pages, same
> document)
> Jul 27 04:01:01.74: [ 8299]: DELAY 150 ms
This 150 ms delay is 55 ms longer than T.30 allows. Why have you made
it so long?
> Jul 27 04:01:01.89: [ 8299]: <-- [9:AT+FTH=3\r]
> Jul 27 04:01:02.02: [ 8299]: --> [7:CONNECT]
> Jul 27 04:01:02.02: [ 8299]: RECV send MCF (message confirmation)
> Jul 27 04:01:02.02: [ 8299]: RECV FAX (00000440): from xxxxxx, page
> 1 in 0:26, INF, 7.7 line/mm, 2-D MR, 14400 bit/s
> Jul 27 04:01:02.02: [ 8299]: <-- data [3]
> Jul 27 04:01:02.02: [ 8299]: <-- data [2]
> Jul 27 04:01:03.21: [ 8299]: --> [2:OK]
> Jul 27 04:01:03.21: [ 8299]: <-- [11:AT+FRM=146\r]
> * Jul 27 04:01:10.21: [ 8299]: <-- data [1]
> * Jul 27 04:01:10.24: [ 8299]: --> [2:OK]
> Jul 27 04:01:10.24: [ 8299]: RECV keeping unconfirmed page
The modem is *supposed* to respond with CONNECT, ERROR, or +FCERROR
before 7 seconds elapse. However, it (like many, many other modems)
doesn't always do this it seems, and this is usually because either 1)
there is no carrier at all, e.g., the sender hung up, or 2) the sender
already has raised the high-speed data carrier, and the requisite
carrier flags are missed.
In this case I'd first suspect that the remote has hung up due to the
150 ms delay being longer than allowed.
Lee.
____________________ 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*