![]() |
Yoshi wrote:
Oct 12 10:56:55.17: [ 86]: SESSION BEGIN 000000013 *********** Oct 12 10:56:55.17: [ 86]: HylaFAX (tm) Version 4.4.0 Oct 12 10:56:55.17: [ 86]: <-- [4:ATA\r] Oct 12 10:57:02.43: [ 86]: --> [7:CONNECT] Oct 12 10:57:06.46: [ 86]: --> [5:ERROR] Oct 12 10:57:06.46: [ 86]: MODEM Command error Oct 12 10:57:06.46: [ 86]: ANSWER: Oct 12 10:57:06.46: [ 86]: SESSION END
The *only* case in which ATA should result in error would be if, according to T.31...
"if five seconds elapses from the time when the DCE reported the CONNECT result code without any additional data transmitted from the DTE"
This would require a HylaFAX problem. Your logging level is not sufficient to see if it is HylaFAX at fault here. Please set ServerTracing to 0xFFF immediately preceded by "TracingMask: 0" in your modem config file, restart faxgetty, and try again. Then show me the session log.
Thanks,
Lee.
I tried AT commands written on modem config file on 'minicom', there occured an error by: AT+FAA=1
It was declared as: ModemSetupAACmd: AT+FAA=1
____________________ 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*