![]() |
Hi All, We have two systems running HylaFax. Both are RedHat 8.0 with the lastest patches. Both are source compiled versions of HylaFax 4.1.5. One system is using two USR Courier external modems that function correctly for both send and receive. The second system is just a test plaform for sending faxes from various Windows clients for test purposes and uses a single modem for send only operation. That system uses some "NoName" Brand modem called a QuickTel which reports the Rockwell chipset as its technology. This system correctly sends queued faxes but the "Waiting for modem to come ready" is the continuous status found in /var/spool/hylafax/status/ttyS0 whenever the modem is not actually initializing or sending. So we seem, with one particular modem to have even in the 4.1.5 release, the same problem others are having. Could anyone suggest a debugging strategy or what faxd uses to determine modem status (if in fact it is faxd that is keeping track of the modem)? All suggestions appreciated. Cheers, Michael Balamuth mlb@chroma.com PS the log shows what I believe to be a correct termination at the end of a sent fax: Dec 04 16:51:32.63: [ 7478]: REMOTE HANGUP: Normal and proper end of connection (code 0) Dec 04 16:51:32.63: [ 7478]: SEND recv MCF (message confirmation) Dec 04 16:51:32.63: [ 7478]: SEND FAX (00000002): FROM mlb@bashful.chroma.com TO 2579400 (page 2 of 2 sent in 0:07) Dec 04 16:51:32.63: [ 7478]: SEND FAX (00000002): FROM mlb@bashful.chroma.com TO 2579400 (docq/doc3.ps;30 sent in 0:07) Dec 04 16:51:32.63: [ 7478]: <-- [5:ATH0\r] Dec 04 16:51:33.20: [ 7478]: --> [2:OK] Dec 04 16:51:33.21: [ 7478]: SESSION END ____________________ 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@hylafax.org < /dev/null *To learn about commercial HylaFAX(tm) support, mail sales@hylafax.org.*