|
Hylafax Developers Mailing List Archives
|
[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
[hylafax-devel] Another Class1 question
"Dr. Harald Pollack" <Harald.Pollack@Datanews.at> writes:
Hello, Harald!
> Well, there is a small problem at receivers side, if it could not switch fast enough from data
> carrier to signal carrier (V.17 or V.29 to V.21), but if first post page message is lost, sender
> will repeat twice this message (in a window of 15 - 18 seconds), so there is a lot of spare time.
I have a strange Class1 problem, which I cannot understand without your
comment. Help!!! :-)
Here is the log:
Jun 08 17:17:27.45: [31768]: SESSION BEGIN 00006538
Jun 08 17:17:27.46: [31768]: MODEM set XON/XOFF/FLUSH: input ignored, output disabled
yes, I am using XONXOFF as the worst possible case :-) Modem (Zyxel 1496) was
initialized the following way (as usual, some init stuff was not necessary :-)):
Jun 8 21:44:07 gw FaxGetty[24533]: <-- [4:ATZ\r]
Jun 8 21:44:08 gw FaxGetty[24533]: --> [2:OK]
Jun 8 21:44:08 gw FaxGetty[24533]: <-- [25:AT*P7S38.3=1E0V1Q0S0=0H0\r]
Jun 8 21:44:08 gw FaxGetty[24533]: --> [24:AT*P7S38.3=1E0V1Q0S0=0H0]
Jun 8 21:44:08 gw FaxGetty[24533]: --> [2:OK]
Jun 8 21:44:08 gw FaxGetty[24533]: <-- [21:ATS8=2S7=60&H4&D2&C1\r]
Jun 8 21:44:08 gw FaxGetty[24533]: --> [2:OK]
Jun 8 21:44:08 gw FaxGetty[24533]: <-- [12:AT+FCLASS=1\r]
Jun 8 21:44:08 gw FaxGetty[24533]: --> [2:OK]
return to the receive log:
Jun 08 17:17:27.46: [31768]: <-- [4:ATA\r]
Jun 08 17:17:34.99: [31768]: --> [7:CONNECT]
Jun 08 17:17:34.99: [31768]: ANSWER: FAX CONNECTION
Jun 08 17:17:34.99: [31768]: STATE CHANGE: ANSWERING -> RECEIVING
Jun 08 17:17:34.99: [31768]: MODEM input buffering enabled
Jun 08 17:17:34.99: [31768]: RECV FAX: begin
Jun 08 17:17:35.09: [31768]: MODEM input buffering disabled
Jun 08 17:17:35.09: [31768]: <-- HDLC<23:FF C0 02 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04>
Jun 08 17:17:35.09: [31768]: <-- data [23]
Jun 08 17:17:35.10: [31768]: <-- data [2]
send our CSI
Jun 08 17:17:36.61: [31768]: --> [7:CONNECT]
Jun 08 17:17:36.61: [31768]: <-- HDLC<10:FF C8 01 00 77 5F 01 79 03 C0>
Jun 08 17:17:36.61: [31768]: <-- data [10]
Jun 08 17:17:36.61: [31768]: <-- data [2]
Jun 08 17:17:37.07: [31768]: --> [2:OK]
... DIS
Jun 08 17:17:37.07: [31768]: <-- [9:AT+FRH=3\r]
and wait for the response.
Jun 08 17:17:41.57: [31768]: --> [0:]
Jun 08 17:17:41.57: [31768]: MODEM <Empty line>
Jun 08 17:17:41.57: [31768]: MODEM TIMEOUT: waiting for v.21 carrier
still have no CONNECT after 4.5 seconds (T.30 T4 counter). Why?
Well, reset the modem, sending CAN character
Jun 08 17:17:41.57: [31768]: <-- data [1]
Jun 08 17:17:41.58: [31768]: --> [2:OK]
Jun 08 17:17:41.58: [31768]: DELAY 1500 ms
... and try again
Jun 08 17:17:43.09: [31768]: <-- [9:AT+FTH=3\r]
Jun 08 17:17:43.12: [31768]: --> [7:CONNECT]
Jun 08 17:17:43.12: [31768]: <-- HDLC<23:FF C0 02 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04>
Jun 08 17:17:43.12: [31768]: <-- data [23]
Jun 08 17:17:43.12: [31768]: <-- data [2]
send CSI
Jun 08 17:17:44.84: [31768]: --> [7:CONNECT]
Jun 08 17:17:44.84: [31768]: <-- HDLC<10:FF C8 01 00 77 5F 01 79 03 C0>
Jun 08 17:17:44.84: [31768]: <-- data [10]
Jun 08 17:17:44.84: [31768]: <-- data [2]
Jun 08 17:17:45.30: [31768]: --> [2:OK]
DIS
Jun 08 17:17:45.30: [31768]: <-- [9:AT+FRH=3\r]
Jun 08 17:17:45.54: [31768]: --> [7:CONNECT]
Jun 08 17:17:47.10: [31768]: --> HDLC<23:FF C0 C2 9C CC CC 8C 8C 6C 9C 04 AC 9C 0C 04 EC 04 04 04 04 04 04 04>
Jun 08 17:17:47.10: [31768]: --> [2:OK]
Jun 08 17:17:47.10: [31768]: REMOTE TSI "7 095 9611339"
Jun 08 17:17:47.10: [31768]: <-- [9:AT+FRH=3\r]
Jun 08 17:17:47.12: [31768]: --> [7:CONNECT]
Jun 08 17:17:47.37: [31768]: --> HDLC<7:FF C8 C1 00 45 19 00>
Jun 08 17:17:47.37: [31768]: --> [2:OK]
Jun 08 17:17:47.37: [31768]: REMOTE wants 14400 bit/s
Jun 08 17:17:47.37: [31768]: REMOTE wants page width 1728 pixels in 215 mm
Jun 08 17:17:47.37: [31768]: REMOTE wants unlimited page length
Jun 08 17:17:47.37: [31768]: REMOTE wants 3.85 line/mm
Jun 08 17:17:47.37: [31768]: REMOTE wants 2-D MR
Now we have succeeded! But why failed before?
Jun 08 17:17:47.37: [31768]: RECV training at v.17 14400 bit/s
Jun 08 17:17:47.37: [31768]: MODEM set XON/XOFF/DRAIN: input ignored, output generated
Jun 08 17:17:47.37: [31768]: <-- [11:AT+FRM=145\r]
Jun 08 17:17:49.01: [31768]: --> [7:CONNECT]
Jun 08 17:17:50.65: [31768]: MODEM set XON/XOFF/DRAIN: input ignored, output disabled
Jun 08 17:17:50.65: [31768]: RECV: TCF 2802 bytes, 3% non-zero, 2636 zero-run
Jun 08 17:17:50.66: [31768]: --> [10:NO CARRIER]
Jun 08 17:17:50.66: [31768]: DELAY 75 ms
Jun 08 17:17:50.76: [31768]: <-- [9:AT+FTH=3\r]
Jun 08 17:17:50.79: [31768]: --> [7:CONNECT]
Jun 08 17:17:50.79: [31768]: <-- HDLC<3:FF C8 21>
Jun 08 17:17:50.79: [31768]: <-- data [3]
Jun 08 17:17:50.79: [31768]: <-- data [2]
Jun 08 17:17:52.03: [31768]: --> [2:OK]
Jun 08 17:17:52.03: [31768]: TRAINING succeeded
14400 is OK
Jun 08 17:17:52.03: [31768]: MODEM input buffering enabled
Jun 08 17:17:52.03: [31768]: MODEM set XON/XOFF/FLUSH: input ignored, output generated
Jun 08 17:17:52.03: [31768]: <-- [11:AT+FRM=146\r]
Jun 08 17:17:52.92: [31768]: --> [7:CONNECT]
Jun 08 17:17:52.92: [31768]: RECV: begin page
Jun 08 17:18:20.17: [31768]: RECV/CQ: Bad 1D pixel count, row 1142, got 0, expected 1728
Jun 08 17:18:20.19: [31768]: RECV/CQ: Bad 1D pixel count, row 1143, got 0, expected 1728
Jun 08 17:18:20.19: [31768]: RECV/CQ: Bad 1D pixel count, row 1144, got 0, expected 1728
Jun 08 17:18:20.19: [31768]: RECV/CQ: Bad 1D pixel count, row 1145, got 0, expected 1728
Jun 08 17:18:20.19: [31768]: RECV/CQ: Bad 1D pixel count, row 1146, got 0, expected 1728
... found RTC
Jun 08 17:18:20.26: [31768]: RECV/CQ: Bad 1D pixel count, row 1147, got 425, expected 1728
Jun 08 17:18:20.26: [31768]: RECV/CQ: Bad 1D pixel count, row 1148, got 1867, expected 1728
Jun 08 17:18:20.49: [31768]: RECV/CQ: Bad 1D pixel count, row 1149, got 1853, expected 1728
Jun 08 17:18:20.79: [31768]: RECV/CQ: Invalid EOL code word, row 1150, x 255
Jun 08 17:18:20.79: [31768]: RECV/CQ: Bad 2D pixel count, row 1150, got 255, expected 1728
Jun 08 17:18:20.79: [31768]: RECV/CQ: Invalid WhiteTable code word, row 1151, x 29
Jun 08 17:18:20.79: [31768]: RECV/CQ: Bad 1D pixel count, row 1151, got 29, expected 1728
Jun 08 17:18:21.00: [31768]: RECV/CQ: Bad 2D pixel count, row 1152, got 1729, expected 1728
Jun 08 17:18:21.08: [31768]: RECV/CQ: Bad 1D pixel count, row 1153, got 2993, expected 1728
Jun 08 17:18:21.63: [31768]: RECV/CQ: Adjusting for trailing noise (12 run)
Jun 08 17:18:21.63: [31768]: RECV: 1142 total lines, 0 bad lines, 0 consecutive bad lines
Jun 08 17:18:21.63: [31768]: RECV: end page
Jun 08 17:18:21.63: [31768]: --> [10:NO CARRIER]
What is why I presume to disturb you. :-)) Remote has not immediately
dropped the carrier after RTC!!! Or our DCE has not detected its loss and eaten
PPM as Phase C data? Or what???
Jun 08 17:18:21.63: [31768]: MODEM set XON/XOFF/DRAIN: input ignored, output disabled
Jun 08 17:18:21.63: [31768]: MODEM input buffering disabled
Jun 08 17:18:21.63: [31768]: <-- [9:AT+FRH=3\r]
We are still trying to detect PPM...
Jun 08 17:19:01.62: [31768]: --> [0:]
Jun 08 17:19:01.62: [31768]: MODEM <Empty line>
Jun 08 17:19:01.62: [31768]: MODEM TIMEOUT: waiting for v.21 carrier
... but with no luck even after 40 secs (T.30 T1 timer)
Jun 08 17:19:01.62: [31768]: <-- data [1]
Jun 08 17:19:01.64: [31768]: --> [2:OK]
Jun 08 17:19:01.68: [31768]: RECV FAX (00006538): recvq/fax01268.tif from 7 095 9611339, route to <unspecified>, 0 pages in 1:26
Jun 08 17:19:01.74: [31768]: RECV FAX: T.30 T2 timeout, expected page not received
message is obviously wrong, but it does not matter. The received page
(without any single error!) has gone to nothere :-(
Jun 08 17:19:01.74: [31768]: <-- [9:AT+FTH=3\r]
Jun 08 17:19:01.77: [31768]: --> [7:CONNECT]
Jun 08 17:19:01.77: [31768]: <-- HDLC<3:FF C8 5F>
Jun 08 17:19:01.77: [31768]: <-- data [3]
Jun 08 17:19:01.77: [31768]: <-- data [2]
Jun 08 17:19:03.01: [31768]: --> [2:OK]
Jun 08 17:19:03.01: [31768]: MODEM input buffering enabled
Jun 08 17:19:03.01: [31768]: RECV FAX (00006538): session with 7 095 9611339 terminated abnormally: T.30 T2 timeout, expected page not received
Jun 08 17:19:03.02: [31768]: RECV FAX: bin/faxrcvd "recvq/fax01268.tif" "zyxel" "00006538" "T.30 T2 timeout, expected page not received"
Jun 08 17:19:07.51: [31768]: RECV FAX: end
Jun 08 17:19:07.51: [31768]: SESSION END
Do you have any idea why all this can happen?
Hope to hear from you soon,
Dmitry
____________________ HylaFAX(tm) Developers Mailing List ____________________
To unsub: mail -s unsubscribe hylafax-devel-request@hylafax.org < /dev/null
