[hylafax-users] R: R: T.30 Error

To: <hylafax-users@xxxxxxxxxxx>
Subject: [hylafax-users] R: R: T.30 Error
From: hylafax-users-bounce@xxxxxxxxxxx
Date: Wed, 28 Jul 2004 09:55:45 +0200
Hi all, 
I have some news about the problem.
I can now create the problem by myself: I found that trying to send fax to the server with the problem using a server absolutely identical (same hardware, hard disk clone) but with a modem USR 56K (I ran out of 536EP) I can see the problem.
These are the two logs :

---Sender---

lug 28 08:51:01.96: [27266]: SEND begin page
lug 28 08:51:01.96: [27266]: <-- data [1028]
lug 28 08:51:01.96: [27266]: <-- data [1025]
lug 28 08:51:01.96: [27266]: <-- data [1024]
lug 28 08:51:01.96: [27266]: <-- data [1040]
lug 28 08:51:03.96: [27266]: <-- data [1034]
lug 28 08:51:03.96: [27266]: <-- data [1069]
lug 28 08:51:03.96: [27266]: <-- data [1036]
lug 28 08:51:03.96: [27266]: <-- data [1051]
lug 28 08:51:05.96: [27266]: <-- data [1037]
lug 28 08:51:05.96: [27266]: <-- data [1042]
lug 28 08:51:05.96: [27266]: <-- data [1045]
lug 28 08:51:05.96: [27266]: <-- data [1067]
lug 28 08:51:07.95: [27266]: <-- data [1040]
lug 28 08:51:07.95: [27266]: <-- data [1053]
lug 28 08:51:07.95: [27266]: <-- data [1045]
lug 28 08:51:09.95: [27266]: <-- data [1044]
lug 28 08:51:09.95: [27266]: <-- data [1042]
lug 28 08:51:09.95: [27266]: <-- data [1049]
lug 28 08:51:09.95: [27266]: <-- data [1040]
lug 28 08:51:11.95: [27266]: <-- data [1028]
lug 28 08:51:11.95: [27266]: <-- data [1024]
lug 28 08:51:11.95: [27266]: <-- data [1024]
lug 28 08:51:11.95: [27266]: <-- data [134]
lug 28 08:51:11.95: [27266]: SENT 22662 bytes of data
lug 28 08:51:11.95: [27266]: SEND 1D RTC
lug 28 08:51:11.95: [27266]: <-- data [9]
lug 28 08:51:11.95: [27266]: SEND end page
lug 28 08:51:11.95: [27266]: SEND send MPS (more pages, same document)
lug 28 08:51:11.95: [27266]: <-- data [2]
lug 28 08:51:25.80: [27266]: --> [7:+FHS:51]
lug 28 08:51:25.80: [27266]: REMOTE HANGUP: RSPREC error/got DCN (code 51)
lug 28 08:51:25.80: [27266]: <-- [5:ATH0\r]
lug 28 08:51:25.93: [27266]: --> [2:OK]
lug 28 08:51:25.93: [27266]: MODEM set DTR OFF
lug 28 08:51:25.93: [27266]: STATE CHANGE: SENDING -> MODEMWAIT (timeout 5)
lug 28 08:51:25.93: [27266]: SESSION END 

-- Receiver --

Jul 28 08:50:59.64: [ 3466]: TRAINING succeeded
Jul 28 08:50:59.64: [ 3466]: <-- [9:AT+FTH=3\r]
Jul 28 08:50:59.77: [ 3466]: --> [7:CONNECT]
Jul 28 08:50:59.77: [ 3466]: <-- data [3]
Jul 28 08:50:59.77: [ 3466]: <-- data [2]
Jul 28 08:51:00.97: [ 3466]: --> [2:OK]
Jul 28 08:51:00.97: [ 3466]: <-- [11:AT+FRM=146\r]
Jul 28 08:51:01.36: [ 3466]: --> [7:CONNECT]
Jul 28 08:51:01.36: [ 3466]: RECV: begin page
Jul 28 08:51:14.12: [ 3466]: RECV: 2292 total lines, 0 bad lines, 0 consecutive bad lines
Jul 28 08:51:14.12: [ 3466]: RECV: end page
Jul 28 08:51:14.12: [ 3466]: --> [10:NO CARRIER]
Jul 28 08:51:14.12: [ 3466]: <-- [9:AT+FRH=3\r]
Jul 28 08:51:14.22: [ 3466]: --> [7:CONNECT]
Jul 28 08:51:15.29: [ 3466]: --> [2:OK]
Jul 28 08:51:15.29: [ 3466]: RECV recv MPS (more pages, same document)
Jul 28 08:51:15.29: [ 3466]: DELAY 90 ms
Jul 28 08:51:15.38: [ 3466]: <-- [9:AT+FTH=3\r]
Jul 28 08:51:15.51: [ 3466]: --> [7:CONNECT]
Jul 28 08:51:15.51: [ 3466]: RECV send MCF (message confirmation)
Jul 28 08:51:15.51: [ 3466]: RECV FAX (00000576): from xxx, page 1 in 0:16, INF, 7.7 line/mm, 1-D MR, 14400 bit/s
Jul 28 08:51:15.51: [ 3466]: <-- data [3]
Jul 28 08:51:15.51: [ 3466]: <-- data [2]
Jul 28 08:51:16.70: [ 3466]: --> [2:OK]
Jul 28 08:51:16.70: [ 3466]: <-- [11:AT+FRM=146\r]
Jul 28 08:51:23.70: [ 3466]: <-- data [1]
Jul 28 08:51:23.73: [ 3466]: --> [2:OK]
Jul 28 08:51:23.73: [ 3466]: RECV keeping unconfirmed page
Jul 28 08:51:23.73: [ 3466]: RECV FAX (00000576): from xxx, page 2 in 0:08, INF, 7.7 line/mm, 1-D MR, 14400 bit/s
Jul 28 08:51:23.73: [ 3466]: RECV FAX (00000576): recvq/fax00535.tif from xxx, route to <unspecified>, 2 pages in 0:32
Jul 28 08:51:23.73: [ 3466]: RECV FAX: T.30 T2 timeout, expected page not received
Jul 28 08:51:23.73: [ 3466]: <-- [9:AT+FTH=3\r]
Jul 28 08:51:23.88: [ 3466]: --> [7:CONNECT]
Jul 28 08:51:23.88: [ 3466]: <-- data [3]
Jul 28 08:51:23.88: [ 3466]: <-- data [2]
Jul 28 08:51:25.08: [ 3466]: --> [2:OK]
Jul 28 08:51:25.08: [ 3466]: RECV FAX (00000576): session with DIGIBYTESRL terminated abnormally: T.30 T2 timeout, expected page not received
Jul 28 08:51:25.08: [ 3466]: RECV FAX: bin/faxrcvd "recvq/fax00535.tif" "536ep" "00000576" "T.30 T2 timeout, expected page not received" "" ""
Jul 28 08:51:25.88: [ 3466]: RECV FAX: end
Jul 28 08:51:25.88: [ 3466]: SESSION END 


so: I send the page, I send MPS, remote receives MPS, remote activates HDLC, sends MCF, and activates reception.
I give no answer to MCF and after some time I state connection is out (or sometimes I state "no answer to EOP/MPS").

Perhaps I must study intensively T.30 standard...
Thanks a lot.
Tiziano

-----Messaggio originale-----
Da: hylafax-users-bounce@xxxxxxxxxxx [mailto:hylafax-users-bounce@xxxxxxxxxxx] Per conto di Tiziano Arbizzani
Inviato: martedì 27 luglio 2004 18.28
A: Lee Howard
Cc: hylafax-users@xxxxxxxxxxx
Oggetto: [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*


____________________ 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*
Follow-Ups:
- Re: [hylafax-users] R: R: T.30 Error
  - From: Lee Howard
Prev by Date: Re: [hylafax-users] Mails with virus in the list
Next by Date: [hylafax-users] VoIP
Previous by thread: Re: [hylafax-users] "Successful" Faxes never receied after delay in 4.1.8
Next by thread: Re: [hylafax-users] R: R: T.30 Error
Index(es):
- Main
- Thread
Report any problems to webmaster@hylafax.org

HylaFAX is a trademark of Silicon Graphics Corporation.
Internet connectivity for hylafax.org is provided by:
VirtuALL Private Host Services