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] Unspecified Transmit Phase C error



SCIN - Danilo Bottino wrote:

SCIN - Danilo Bottino wrote:

hasV17Trouble:yes



Change it from "yes" to "no". And then send a fax to the number and check the log to see if V.17 (14400 or 12000) actually works. If it does, then lock the setting by putting an "&" in front of the line, like this:


&hasV17Trouble:no

However, it would appear that there is some problem with the V.29 combination of sender and receiver here. So, something's not right, at least.


Done it. Looks like v.17 works fine now.


Yeah, it looks fine. There apparently is some kind of V.29 incompatibility. Lock the hasV17Trouble setting with the "&" as I described. It would be nice to know, if you can see the log, why V.17 is being detected as troublesome.


Locked. I did a search through the log archive and found that actually it wasn't the first time I had this error, I had it two weeks ago with another receiver:



Nov 30 17:08:02.64: [18503]: SESSION BEGIN 000005920 390110755919098
Nov 30 17:08:02.64: [18503]: HylaFAX (tm) Version 4.3.0
Nov 30 17:08:02.64: [18503]: SEND FAX: JOB 1125 DEST 0755919098 COMMID 000005920 DEVICE '/dev/modem2' FROM 'cora <************>' USER fax
Nov 30 17:08:02.64: [18503]: <-- [12:AT+FCLASS=1\r]
Nov 30 17:08:02.66: [18503]: --> [2:OK]
Nov 30 17:08:02.66: [18503]: DIAL 0755919098
Nov 30 17:08:02.66: [18503]: <-- [15:ATDT0755919098\r]
Nov 30 17:08:11.85: [18503]: --> [7:CONNECT]
Nov 30 17:08:13.53: [18503]: --> [2:OK]
Nov 30 17:08:13.53: [18503]: REMOTE NSF "00 00 25 00 00 00 12 10 6C 00 00 50 00 28 B8 A4 80 80 10"
Nov 30 17:08:13.53: [18503]: NSF remote fax equipment: Ricoh
Nov 30 17:08:13.53: [18503]: <-- [9:AT+FRH=3\r]
Nov 30 17:08:13.54: [18503]: --> [7:CONNECT]
Nov 30 17:08:13.99: [18503]: --> [2:OK]
Nov 30 17:08:13.99: [18503]: REMOTE NSF "00 00 25 01 4C 52 53 20 47 26 42"
Nov 30 17:08:13.99: [18503]: NSF remote fax equipment: Ricoh
Nov 30 17:08:13.99: [18503]: NSF remote station ID: "B&G SRL"
Nov 30 17:08:13.99: [18503]: <-- [9:AT+FRH=3\r]
Nov 30 17:08:14.00: [18503]: --> [7:CONNECT]
Nov 30 17:08:14.69: [18503]: --> [2:OK]
Nov 30 17:08:14.69: [18503]: REMOTE CSI "0039755919098"
Nov 30 17:08:14.69: [18503]: <-- [9:AT+FRH=3\r]
Nov 30 17:08:14.71: [18503]: --> [7:CONNECT]
Nov 30 17:08:14.95: [18503]: --> [2:OK]
Nov 30 17:08:14.95: [18503]: REMOTE best rate 14400 bit/s
Nov 30 17:08:14.95: [18503]: REMOTE max A4 page width (215 mm)
Nov 30 17:08:14.95: [18503]: REMOTE max unlimited page length
Nov 30 17:08:14.95: [18503]: REMOTE best vres 7.7 line/mm
Nov 30 17:08:14.95: [18503]: REMOTE format support: MH
Nov 30 17:08:14.95: [18503]: REMOTE supports T.30 Annex A, 256-byte ECM
Nov 30 17:08:14.95: [18503]: REMOTE best 10 ms/scanline
Nov 30 17:08:14.95: [18503]: USE 9600 bit/s
Nov 30 17:08:14.95: [18503]: USE error correction mode
Nov 30 17:08:14.95: [18503]: SEND file "docq/doc1126.ps;c0"
Nov 30 17:08:14.95: [18503]: USE A4 page width (215 mm)
Nov 30 17:08:14.95: [18503]: USE unlimited page length
Nov 30 17:08:14.95: [18503]: USE 3.85 line/mm
Nov 30 17:08:14.95: [18503]: USE 1-D MH
Nov 30 17:08:14.95: [18503]: USE 0 ms/scanline
Nov 30 17:08:14.95: [18503]: SEND training at v.29 9600 bit/s
Nov 30 17:08:14.95: [18503]: <-- [9:AT+FRS=7\r]
Nov 30 17:08:15.12: [18503]: --> [2:OK]
Nov 30 17:08:15.12: [18503]: <-- [9:AT+FTH=3\r]
Nov 30 17:08:16.09: [18503]: --> [7:CONNECT]
Nov 30 17:08:16.11: [18503]: --> [7:CONNECT]
Nov 30 17:08:17.30: [18503]: --> [2:OK]
Nov 30 17:08:17.30: [18503]: <-- [9:AT+FTS=7\r]
Nov 30 17:08:17.37: [18503]: --> [2:OK]
Nov 30 17:08:17.37: [18503]: <-- [10:AT+FTM-\r]
Nov 30 17:08:17.39: [18503]: --> [7:CONNECT]
Nov 30 17:08:17.39: [18503]: DELAY 400 ms
Nov 30 17:08:19.37: [18503]: --> [2:OK]
Nov 30 17:08:19.37: [18503]: <-- [9:AT+FRH=3\r]
Nov 30 17:08:19.98: [18503]: --> [7:CONNECT]
Nov 30 17:08:21.15: [18503]: --> [2:OK]
Nov 30 17:08:21.15: [18503]: TRAINING succeeded
Nov 30 17:08:21.15: [18503]: SEND begin page
Nov 30 17:08:21.16: [18503]: Reading MMR-compressed image file
Nov 30 17:08:21.16: [18503]: SEND 1D RTC
Nov 30 17:08:21.16: [18503]: SEND send frame number 0
Nov 30 17:08:21.16: [18503]: SEND send frame number 1
Nov 30 17:08:21.16: [18503]: SEND send frame number 2
Nov 30 17:08:21.16: [18503]: SEND send frame number 3
Nov 30 17:08:21.16: [18503]: SEND send frame number 4
Nov 30 17:08:21.16: [18503]: SEND send frame number 5
Nov 30 17:08:21.16: [18503]: SEND send frame number 6
Nov 30 17:08:21.16: [18503]: SEND send frame number 7
Nov 30 17:08:21.16: [18503]: SEND send frame number 8
Nov 30 17:08:21.16: [18503]: SEND send frame number 9
Nov 30 17:08:21.16: [18503]: SEND send frame number 10
Nov 30 17:08:21.16: [18503]: SEND send frame number 11
Nov 30 17:08:21.16: [18503]: SEND send frame number 12
Nov 30 17:08:21.16: [18503]: SEND send frame number 13
Nov 30 17:08:21.16: [18503]: SEND send frame number 14
Nov 30 17:08:21.16: [18503]: SEND send frame number 15
Nov 30 17:08:21.16: [18503]: SEND send frame number 16
Nov 30 17:08:21.16: [18503]: SEND send frame number 17
Nov 30 17:08:21.16: [18503]: SEND send frame number 18
Nov 30 17:08:21.16: [18503]: SEND send frame number 19
Nov 30 17:08:21.17: [18503]: SEND send frame number 20
Nov 30 17:08:21.17: [18503]: SEND send frame number 21
Nov 30 17:08:21.17: [18503]: SEND send frame number 22
Nov 30 17:08:21.17: [18503]: SEND send frame number 23
Nov 30 17:08:21.17: [18503]: SEND send frame number 24
Nov 30 17:08:21.17: [18503]: SEND send frame number 25
Nov 30 17:08:21.17: [18503]: SEND send frame number 26
Nov 30 17:08:21.17: [18503]: SEND send frame number 27
Nov 30 17:08:21.17: [18503]: SEND send frame number 28
Nov 30 17:08:21.17: [18503]: SEND send frame number 29
Nov 30 17:08:21.17: [18503]: SEND send frame number 30
Nov 30 17:08:21.17: [18503]: SEND send frame number 31
Nov 30 17:08:21.17: [18503]: SEND send frame number 32
Nov 30 17:08:21.17: [18503]: SEND send frame number 33
Nov 30 17:08:21.17: [18503]: SEND send frame number 34
Nov 30 17:08:21.17: [18503]: SEND send frame number 35
Nov 30 17:08:21.17: [18503]: SEND send frame number 36
Nov 30 17:08:21.17: [18503]: SEND send frame number 37
Nov 30 17:08:21.17: [18503]: SEND send frame number 38
Nov 30 17:08:21.17: [18503]: SEND send frame number 39
Nov 30 17:08:21.17: [18503]: SEND send frame number 40
Nov 30 17:08:21.17: [18503]: SEND send frame number 41
Nov 30 17:08:21.17: [18503]: SEND send frame number 42
Nov 30 17:08:21.17: [18503]: SEND send frame number 43
Nov 30 17:08:21.17: [18503]: SEND send frame number 44
Nov 30 17:08:21.17: [18503]: SEND send frame number 45
Nov 30 17:08:21.17: [18503]: SEND send frame number 46
Nov 30 17:08:21.17: [18503]: SEND send frame number 47
Nov 30 17:08:21.17: [18503]: SEND send frame number 48
Nov 30 17:08:21.17: [18503]: SEND send frame number 49
Nov 30 17:08:21.17: [18503]: SEND send frame number 50
Nov 30 17:08:21.17: [18503]: SEND send frame number 51
Nov 30 17:08:21.17: [18503]: SEND send frame number 52
Nov 30 17:08:21.17: [18503]: SEND send frame number 53
Nov 30 17:08:21.17: [18503]: SEND send frame number 54
Nov 30 17:08:21.17: [18503]: SEND send frame number 55
Nov 30 17:08:21.17: [18503]: SEND send frame number 56
Nov 30 17:08:21.17: [18503]: SEND send frame number 57
Nov 30 17:08:21.17: [18503]: SEND send frame number 58
Nov 30 17:08:21.17: [18503]: SEND send frame number 59
Nov 30 17:08:21.17: [18503]: SEND send frame number 60
Nov 30 17:08:21.17: [18503]: SEND send frame number 61
Nov 30 17:08:21.17: [18503]: SEND send frame number 62
Nov 30 17:08:21.17: [18503]: SEND send frame number 63
Nov 30 17:08:21.17: [18503]: SEND send frame number 64
Nov 30 17:08:21.17: [18503]: SEND send frame number 65
Nov 30 17:08:21.17: [18503]: SEND send frame number 66
Nov 30 17:08:21.17: [18503]: SEND send frame number 67
Nov 30 17:08:21.17: [18503]: SEND send frame number 68
Nov 30 17:08:21.17: [18503]: SEND send frame number 69
Nov 30 17:08:21.17: [18503]: SEND send frame number 70
Nov 30 17:08:21.17: [18503]: SEND send frame number 71
Nov 30 17:08:21.17: [18503]: SEND send frame number 72
Nov 30 17:08:21.17: [18503]: SEND send frame number 73
Nov 30 17:08:21.17: [18503]: SEND send frame number 74
Nov 30 17:08:21.17: [18503]: DELAY 200 ms
Nov 30 17:08:21.37: [18503]: <-- [10:AT+FTM-\r]
Nov 30 17:08:21.39: [18503]: --> [7:CONNECT]
Nov 30 17:08:21.39: [18503]: DELAY 400 ms
Nov 30 17:09:45.95: [18503]: MODEM WRITE SHORT: sent 1025, wrote 882
Nov 30 17:09:45.95: [18503]: SEND end page
Nov 30 17:09:45.95: [18503]: Unspecified Transmit Phase C error
Nov 30 17:09:45.95: [18503]: <-- [9:AT+FTH=3\r]
Nov 30 17:09:45.95: [18503]: --> [5:ERROR]
Nov 30 17:09:45.95: [18503]: SEND FAILED: JOB 1125 DEST 0755919098 ERR Unspecified Transmit Phase C error; too many attempts to send
Nov 30 17:09:45.95: [18503]: <-- [5:ATH0\r]
Nov 30 17:09:50.96: [18503]: MODEM <Timeout>
Nov 30 17:10:20.96: [18503]: SESSION END



In its info file there was hasV17Trouble:yes as well, I changed it to "no" and after a succesfull attempt to send a fax I've locked it with &.


How exactly are created those info files? I mean, is hylafax able to change a troublesome value on the fly whenever it detects a problem, as long as they're not manually locked with "&"?


____________________ 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