![]() |
On Thu, 14 Jan 1999, David Woolley wrote: > There is no such message in the Hylafax sources as best I can tell. This > one probably comes from init, and is probably the result of an exit(1) call, > which is the way that most user programs signal a failure. Nope, the error is from getty, which is run to initiate the fax connection (i think)... i've been looking all over for getty errors, but i just can't seem to find any docs on them. My only guess is that, since this was an international call, the machines didn't have enough time to negotiate a connection... So I've added a line to my config.cua1 file that reads something along the lines of: ATS7=90, which sets time to wait for a connection to be negotiated to 90 seconds. > To get any further, we need detailed Hylafax session logs. > > What fax class are you using? Fax class is 2.0. here's one log: Jan 10 21:15:23.88: [ 91]: SESSION BEGIN 00000005 ********* (fax number edited out) Jan 10 21:15:23.89: [ 91]: <-- [4:ATA\r] Jan 10 21:16:17.30: [ 91]: --> [10:NO CARRIER] Jan 10 21:16:17.31: [ 91]: ANSWER: Ring detected without successful handshake Jan 10 21:16:17.31: [ 91]: SESSION END Then, on a second call from the very same fax machine, HylaFAX generates a different log: Jan 10 21:17:02.80: [ 91]: SESSION BEGIN 00000006 18476570217 Jan 10 21:17:02.80: [ 91]: <-- [4:ATA\r] Jan 10 21:17:22.15: [ 91]: --> [4:+FDM] Jan 10 21:17:22.15: [ 91]: ANSWER: DATA CONNECTION Jan 10 21:17:22.15: [ 91]: GETTY: START "/sbin/getty -h cua1 dx_38400", pid 4$ Jan 10 21:17:22.28: [ 91]: GETTY: exit status 0400 Jan 10 21:17:22.28: [ 91]: SESSION END Another call from the fax machine (which is located in Korea, I'm in USA) generated exactly the same log, only with different time stamps. S. Lee