|
Hylafax Mailing List Archives
|
[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
Re: [hylafax-users] DIS/DTC 3 times with Panasonic KX-F90
On 2003.09.25 06:20 Giulio Orsero wrote:
Linux, HylaFAX 4.1.7, class1, rockwell, remote is recognized as
Panasonic
KX-F90 by HylaFAx (not sure if this is correct).
I always get DIS/DTC when trying sending to this machine.
I'm attaching a session log.
Thanks
Sep 25 15:11:57.92: [16400]: SESSION BEGIN 00019467 390000000000
Sep 25 15:11:57.92: [16400]: HylaFAX (tm) Version 4.1.7
Sep 25 15:11:57.92: [16400]: SEND FAX: JOB 14784 DEST 0000-000000
COMMID 00019467 DEVICE '/dev/ttyS2'
Sep 25 15:11:57.92: [16400]: STATE CHANGE: RUNNING -> SENDING
Sep 25 15:11:57.92: [16400]: sched policy=1, priority=1
Sep 25 15:11:57.92: [16400]: MODEM input buffering enabled
Sep 25 15:11:57.92: [16400]: <-- [12:AT+FCLASS=1\r]
Sep 25 15:11:58.04: [16400]: --> [2:OK]
Sep 25 15:11:58.04: [16400]: DIAL 1077,0000000000
Sep 25 15:11:58.04: [16400]: <-- [20:ATDT1111,0000000000\r]
Sep 25 15:12:17.86: [16400]: --> [7:CONNECT]
Sep 25 15:12:17.86: [16400]: MODEM input buffering disabled
Sep 25 15:12:19.63: [16400]: --> HDLC<42:FF C0 04 00 00 70 00 00 00 69
F0 80 40 00 08 A0 40 A9 13 10 80 92 40 5A AA 4A 92 E2 F2 04 04 04 04
04 04 04 04 04 04 C0 1D 24>
Sep 25 15:12:19.64: [16400]: --> [2:OK]
Sep 25 15:12:19.64: [16400]: REMOTE NSF "00 00 0E 00 00 00 96 0F 01 02
00 10 05 02 95 C8 08 01 49 02 5A 55 52 49 47 4F 20 20 20 20 20 20 20
20 20 20 03"
Sep 25 15:12:19.64: [16400]: NSF remote fax equipment: Panasonic
KX-F90
Sep 25 15:12:19.64: [16400]: NSF remote station ID: "ABCDEF "
Sep 25 15:12:19.64: [16400]: <-- [9:AT+FRH=3\r]
Sep 25 15:12:19.66: [16400]: --> [7:CONNECT]
Sep 25 15:12:20.33: [16400]: --> HDLC<25:FF C0 02 9C 0C 6C 8C 2C AC 04
4C 1C 8C 0C 04 04 04 04 04 04 04 04 04 A5 24>
Sep 25 15:12:20.33: [16400]: --> [2:OK]
Sep 25 15:12:20.33: [16400]: REMOTE CSI "0000 000000"
Sep 25 15:12:20.33: [16400]: <-- [9:AT+FRH=3\r]
Sep 25 15:12:20.35: [16400]: --> [7:CONNECT]
Sep 25 15:12:20.59: [16400]: --> HDLC<9:FF C8 01 00 72 1D 00 71 24>
This is the DIS signal.
Sep 25 15:12:20.60: [16400]: --> [2:OK]
Sep 25 15:12:20.60: [16400]: REMOTE best rate 9600 bit/s
Sep 25 15:12:20.60: [16400]: REMOTE max A4 page width (215 mm)
Sep 25 15:12:20.60: [16400]: REMOTE max unlimited page length
Sep 25 15:12:20.60: [16400]: REMOTE best vres 7.7 line/mm
Sep 25 15:12:20.60: [16400]: REMOTE best format 1-D MR
Sep 25 15:12:20.60: [16400]: REMOTE best 20 ms, 10 ms/scanline
This is an accurate representation of the DIS signal (after checking it
against T.30 Table 2).
Sep 25 15:12:20.60: [16400]: USE 9600 bit/s
Sep 25 15:12:20.60: [16400]: USE 20 ms, 10 ms/scanline
Sep 25 15:12:20.60: [16400]: SEND file "docq/doc15176.ps;01"
Sep 25 15:12:20.60: [16400]: USE A4 page width (215 mm)
Sep 25 15:12:20.60: [16400]: USE unlimited page length
Sep 25 15:12:20.60: [16400]: USE 7.7 line/mm
Sep 25 15:12:20.60: [16400]: USE 1-D MR
Sep 25 15:12:20.60: [16400]: SEND training at v.29 9600 bit/s
Sep 25 15:12:20.60: [16400]: <-- [9:AT+FTH=3\r]
Sep 25 15:12:20.66: [16400]: --> [7:CONNECT]
Sep 25 15:12:20.66: [16400]: <-- HDLC<23:FF C0 C2 0C EC 6C EC 4C 6C 04
9C 8C 0C 04 9C CC D4 04 04 04 04 04 04>
HylaFAX sends TSI.
Sep 25 15:12:20.66: [16400]: <-- data [23]
Sep 25 15:12:20.66: [16400]: <-- data [2]
Sep 25 15:12:22.44: [16400]: --> [7:CONNECT]
Sep 25 15:12:22.44: [16400]: <-- HDLC<10:FF C8 C1 00 62 11 01 01 01
00>
HylaFAX sends DCS. The description above is an accurate representation
of the DCS signal.
Sep 25 15:12:22.44: [16400]: <-- data [10]
Sep 25 15:12:22.44: [16400]: <-- data [2]
Sep 25 15:12:22.98: [16400]: --> [2:OK]
Sep 25 15:12:22.98: [16400]: <-- [9:AT+FTS=7\r]
Sep 25 15:12:23.07: [16400]: --> [2:OK]
Sep 25 15:12:23.07: [16400]: <-- [10:AT+FTM=96\r]
Sep 25 15:12:23.14: [16400]: --> [7:CONNECT]
Sep 25 15:12:23.14: [16400]: <-- data [1024]
Sep 25 15:12:23.14: [16400]: <-- data [776]
Sep 25 15:12:23.14: [16400]: <-- data [2]
Sep 25 15:12:25.09: [16400]: --> [2:OK]
HylaFAX sends TCF and will now look for CFR signal.
Sep 25 15:12:25.09: [16400]: <-- [9:AT+FRH=3\r]
Sep 25 15:12:26.02: [16400]: --> [7:CONNECT]
Sep 25 15:12:27.89: [16400]: --> HDLC<42:FF C0 04 00 00 70 00 00 00 69
F0 80 40 00 08 A0 40 A9 13 10 80 92 40 5A AA 4A 92 E2 F2 04 04 04 04
04 04 04 04 04 04 C0 1D 24>
But the remote immediately sends NSF, then later CSI and DIS.
Sep 25 15:12:27.90: [16400]: --> [2:OK]
Sep 25 15:12:27.90: [16400]: <-- [9:AT+FRH=3\r]
Sep 25 15:12:27.92: [16400]: --> [7:CONNECT]
Sep 25 15:12:28.59: [16400]: --> HDLC<25:FF C0 02 9C 0C 6C 8C 2C AC 04
4C 1C 8C 0C 04 04 04 04 04 04 04 04 04 A5 24>
Sep 25 15:12:28.59: [16400]: --> [2:OK]
Sep 25 15:12:28.59: [16400]: REMOTE CSI "0000 000000"
Sep 25 15:12:28.59: [16400]: <-- [9:AT+FRH=3\r]
Sep 25 15:12:28.61: [16400]: --> [7:CONNECT]
Sep 25 15:12:28.85: [16400]: --> HDLC<9:FF C8 01 00 72 1D 00 71 24>
Sep 25 15:12:28.86: [16400]: --> [2:OK]
So we resend TSI, DCS, and TCF...
Sep 25 15:12:28.86: [16400]: SEND training at v.29 9600 bit/s
Sep 25 15:12:28.86: [16400]: <-- [9:AT+FTH=3\r]
Sep 25 15:12:28.92: [16400]: --> [7:CONNECT]
Sep 25 15:12:28.92: [16400]: <-- HDLC<23:FF C0 C2 0C EC 6C EC 4C 6C 04
9C 8C 0C 04 9C CC D4 04 04 04 04 04 04>
Sep 25 15:12:28.92: [16400]: <-- data [23]
Sep 25 15:12:28.92: [16400]: <-- data [2]
Sep 25 15:12:30.70: [16400]: --> [7:CONNECT]
Sep 25 15:12:30.70: [16400]: <-- HDLC<10:FF C8 C1 00 62 11 01 01 01
00>
Sep 25 15:12:30.70: [16400]: <-- data [10]
Sep 25 15:12:30.70: [16400]: <-- data [2]
Sep 25 15:12:31.24: [16400]: --> [2:OK]
Sep 25 15:12:31.24: [16400]: <-- [9:AT+FTS=7\r]
Sep 25 15:12:31.33: [16400]: --> [2:OK]
Sep 25 15:12:31.33: [16400]: <-- [10:AT+FTM=96\r]
Sep 25 15:12:31.40: [16400]: --> [7:CONNECT]
Sep 25 15:12:31.40: [16400]: <-- data [1024]
Sep 25 15:12:31.40: [16400]: <-- data [776]
Sep 25 15:12:31.40: [16400]: <-- data [2]
Sep 25 15:12:33.35: [16400]: --> [2:OK]
Sep 25 15:12:33.35: [16400]: <-- [9:AT+FRH=3\r]
Sep 25 15:12:34.31: [16400]: --> [7:CONNECT]
Sep 25 15:12:36.16: [16400]: --> HDLC<42:FF C0 04 00 00 70 00 00 00 69
F0 80 40 00 08 A0 40 A9 13 10 80 92 40 5A AA 4A 92 E2 F2 04 04 04 04
04 04 04 04 04 04 C0 1D 24>
Same thing happens again and again until we give up.
My first suspicion was that perhaps the DCS signal we were sending was
incorrect somehow, but this does not appear to be the case.
In T.30 Figure 5.2B the only loop whereby the receiver should loop back
to sending DIS is if it does not hear any signal response to DIS. It
should do this until T1 elapses. Because the receiver promptly
retransmits NSF/CSI/DIS after we send TCF and await CFR, it certainly
seems that the receiver is hearing our signals. T.30 Figure 5.2B and
5.2D indicate that if a receiver hears a signal response to DIS but it
is invalid, then the receiver should send DCN... however, I suspect
that many receivers will not do this and will follow the procecure
outlined above for no response heard. So anyway, I don't know what's
happening here, sorry.
Can you send to this destination with another Class 1 modem? Class 2?
efax, mgetty-sendfax, or MS-FAX? If so, can you provide a successful
log? Then I could compare the differences and determine, possibly, the
reason this one fails.
Thanks.
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@xxxxxxxxxxxx*
