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] t38modem, failure to receive silence
Daniele Martini wrote:
Jun 16 16:47:46.05: [ 2224]: TRAINING succeeded
Jun 16 16:47:46.05: [ 2224]: <-- [9:AT+FTH=3\r]
Jun 16 16:47:46.05: [ 2224]: --> [7:CONNECT]
Jun 16 16:47:46.05: [ 2224]: <-- data [3]
Jun 16 16:47:46.05: [ 2224]: <-- data [2]
Jun 16 16:47:47.10: [ 2224]: --> [2:OK]
Jun 16 16:47:47.10: [ 2224]: <-- [10:AT+FRM=98\r]
Jun 16 16:47:48.98: [ 2224]: --> [8:+FCERROR]
Jun 16 16:47:48.98: [ 2224]: <-- [10:AT+FRM=98\r]
Jun 16 16:47:48.98: [ 2224]: --> [8:+FCERROR]
Jun 16 16:47:48.98: [ 2224]: <-- [9:AT+FRH=3\r]
Jun 16 16:47:48.98: [ 2224]: --> [7:CONNECT]
Jun 16 16:47:50.39: [ 2224]: --> [2:OK]
Jun 16 16:47:50.39: [ 2224]: RECV recv TSI (sender id)
Jun 16 16:47:50.39: [ 2224]: REMOTE TSI "YYYYYY"
This is the repeated problem in session 000009521. It seems to indicate
that the sender cannot "hear" your CFR signal. That said, I really
think that this session requires the inspection of the t38modem author,
since it seems to represent a bug either in t38modem or in the T.38
gateway (and the latter wouldn't be surprising, actually).
Jun 16 10:43:54.44: [ 2224]: <-- [11:AT+FRM=146\r]
Jun 16 10:43:56.69: [ 2224]: --> [7:CONNECT]
Jun 16 10:43:56.69: [ 2224]: RECV: begin page
Jun 16 10:44:09.63: [ 2224]: RECV: 0 total lines, 0 bad lines, 0
consecutive bad lines
Jun 16 10:44:09.63: [ 2224]: RECV: end page
Jun 16 10:44:09.63: [ 2224]: --> [10:NO CARRIER]
Jun 16 10:44:09.63: [ 2224]: <-- [9:AT+FRH=3\r]
Jun 16 10:44:09.83: [ 2224]: --> [7:CONNECT]
Jun 16 10:44:10.99: [ 2224]: --> [2:OK]
Jun 16 10:44:10.99: [ 2224]: RECV recv EOP (no more pages or documents)
This is in session 000009430, and basically it says that the sender
started Phase C as expected, but that 13 seconds later the sender
apparently aborts the fax without sending any page image data. Did the
sender have a paper jam or something? If not, then it's probably a bug
in the T.38 gateway.
Jun 13 08:10:20.58: [ 2224]: RECV training at v.17 14400 bit/s
Jun 13 08:10:20.58: [ 2224]: <-- [11:AT+FRM=145\r]
Jun 13 08:10:25.08: [ 2224]: --> [0:]
Jun 13 08:10:25.08: [ 2224]: MODEM <Empty line>
Jun 13 08:10:25.08: [ 2224]: <-- data [1]
Jun 13 08:10:25.08: [ 2224]: --> [2:OK]
Jun 13 08:10:25.08: [ 2224]: <-- [9:AT+FRS=7\r]
Jun 13 08:10:25.15: [ 2224]: --> [2:OK]
Jun 13 08:10:25.15: [ 2224]: <-- [9:AT+FTH=3\r]
Jun 13 08:10:25.15: [ 2224]: --> [7:CONNECT]
Jun 13 08:10:25.15: [ 2224]: <-- data [3]
Jun 13 08:10:25.15: [ 2224]: <-- data [2]
Jun 13 08:10:27.22: [ 2224]: --> [2:OK]
Jun 13 08:10:27.22: [ 2224]: TRAINING failed
The modem (well, the T.38 gateway) cannot "hear" the high-speed image
data coming from the sender. This probably represents a bug in the T.38
gateway... but you may want to have the t38modem author look at this, too.
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@xxxxxxxxx*