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] R: R: T.30 Error



On 2004.07.28 00:55 hylafax-users-bounce@xxxxxxxxxxx wrote:
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 :

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)

Well, firstly, you really shouldn't use a USR modem in Class 2.0 because there's no good way to be positive that you're not encountering one of the many bugs in the firmware.


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

And what the comparison of the two logs tell is us that the sender is not detecting the receiver's post-page response signal (MCF) and it probably isn't even detecting the DCN signal sent just before ATH0 (I deduce this by comparing the clocks between the logs). So maybe the i536EP driver has a faulty V.21 modulator. (?)


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...

T.30 is always a good bedtime read ;-) Reading it to your children will put them (and you) right to sleep. :-)


In this case, however, I suspect a problem with the i536EP driver that T.30 study won't resolve... especially if you can reproduce this when the USR is run in Class 1.

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*




Project hosted by iFAX Solutions