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] V.21 signal reception timeout +FCERROR
dev.malst wrote:
Nov 29 09:37:30.68: [ 3155]: <-- [9:AT+FRH=3\r]
Nov 29 09:37:30.70: [ 3155]: --> [7:CONNECT]
Nov 29 09:37:31.03: [ 3155]: --> [2:OK]
Nov 29 09:37:31.03: [ 3155]: RECV recv DCS (command signal)
Nov 29 09:37:31.03: [ 3155]: REMOTE wants 9600 bit/s
Nov 29 09:37:31.03: [ 3155]: REMOTE wants A4 page width (215 mm)
Nov 29 09:37:31.03: [ 3155]: REMOTE wants unlimited page length
Nov 29 09:37:31.03: [ 3155]: REMOTE wants 3.85 line/mm
Nov 29 09:37:31.03: [ 3155]: REMOTE wants 1-D MH
Assuming you haven't disabled a bunch of features in your Class 1 modem
config file, then either the sender is a feature-deprived (no V.17 and
no ECM) excuse for a fax device (are you sending with some other fax
software?) or the call is passing through a heavy-handed T.38
connection. Either way, this is an indication that things could go wrong.
Nov 29 09:37:31.03: [ 3155]: RECV training at v.29 9600 bit/s
Nov 29 09:37:31.03: [ 3155]: <-- [10:AT+FRM=96\r]
Nov 29 09:37:31.43: [ 3155]: --> [7:CONNECT]
Nov 29 09:37:33.00: [ 3155]: RECV: TCF 1888 bytes, 2% non-zero, 1001
zero-run
Nov 29 09:37:33.00: [ 3155]: RECV: reject TCF (zero run too short, min
1200)
Nov 29 09:37:33.01: [ 3155]: --> [10:NO CARRIER]
The modem determined that the audio quality was too poor for fax using
the V.29 9600 bps modulation. Either the modem is wrong or the audio
really is bad.
Nov 29 09:37:39.17: [ 3155]: <-- [9:AT+FRH=3\r]
Nov 29 09:37:39.18: [ 3155]: --> [7:CONNECT]
Nov 29 09:37:39.52: [ 3155]: --> [2:OK]
Nov 29 09:37:39.52: [ 3155]: RECV recv DCS (command signal)
Nov 29 09:37:39.52: [ 3155]: REMOTE wants 9600 bit/s
Nov 29 09:37:39.52: [ 3155]: REMOTE wants A4 page width (215 mm)
Nov 29 09:37:39.52: [ 3155]: REMOTE wants unlimited page length
Nov 29 09:37:39.52: [ 3155]: REMOTE wants 3.85 line/mm
Nov 29 09:37:39.52: [ 3155]: REMOTE wants 1-D MH
Looks like the sender's going to retry training at the same settings.
Apparently the sender believes that the audio problems are transient.
Nov 29 09:37:39.52: [ 3155]: RECV training at v.29 9600 bit/s
Nov 29 09:37:39.52: [ 3155]: <-- [10:AT+FRM=96\r]
Nov 29 09:37:39.91: [ 3155]: --> [7:CONNECT]
Nov 29 09:37:41.48: [ 3155]: RECV: TCF 1888 bytes, 1% non-zero, 1825
zero-run
Nov 29 09:37:41.49: [ 3155]: --> [10:NO CARRIER]
Nov 29 09:37:41.49: [ 3155]: <-- [9:AT+FRS=7\r]
Nov 29 09:37:41.57: [ 3155]: --> [2:OK]
Nov 29 09:37:41.57: [ 3155]: TRAINING succeeded
And this time it passes training.
Nov 29 09:37:41.57: [ 3155]: <-- [9:AT+FTH=3\r]
Nov 29 09:37:42.44: [ 3155]: --> [7:CONNECT]
Nov 29 09:37:42.44: [ 3155]: <-- data [3]
Nov 29 09:37:42.44: [ 3155]: <-- data [2]
Nov 29 09:37:42.76: [ 3155]: --> [2:OK]
Nov 29 09:37:42.76: [ 3155]: <-- [10:AT+FRM=96\r]
Nov 29 09:37:43.80: [ 3155]: --> [8:+FCERROR]
Nov 29 09:37:43.80: [ 3155]: <-- [10:AT+FRM=96\r]
Nov 29 09:37:44.62: [ 3155]: --> [7:CONNECT]
Nov 29 09:37:44.62: [ 3155]: RECV: begin page
Nov 29 09:37:44.73: [ 3155]: RECV: 0 total lines, 0 bad lines, 0
consecutive bad lines
Nov 29 09:37:44.73: [ 3155]: RECV: REJECT page quality, too few
scanlines: 0
Nov 29 09:37:44.73: [ 3155]: RECV: end page
Nov 29 09:37:44.73: [ 3155]: --> [10:NO CARRIER]
But no sooner had the Phase C V.29 9600 bps carrier been detected than
the modem detected a loss of carrier. (Either the modem is wrong, or
the audio is bad.)
Nov 29 09:37:44.73: [ 3155]: <-- [9:AT+FRH=3\r]
Nov 29 09:37:54.85: [ 3155]: --> [10:NO CARRIER]
And apparently there was another 10 seconds of some kind of signal which
was not V.21 HDLC... and then that signal was lost.
These look like VoIP symptoms. Is this modem working through a VoIP line?
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*