Hi,
I just installed Efax-gtk on Debian and it works great out of the box.
I'm using an external USR Faxmodem.
efax-0.9a: 16:14:23 opened /dev/ttyS0
efax-0.9a: 16:14:26 using U.S. Robotics 56K FAX EXT V5.11.6U.S. Robotics 56K FAXOKOK in class 2.0
efax-0.9a: 16:14:28 dialing Txxxxxxx
*** Stopping send/receive session ***
Everything works great when the remote fax picks up.
When the line is busy, Efax just keeps on waiting & polling until I manually end the connection.
This happens from the old command line Efax script as well, not just Efax-gtk.
What should I do next? I assume it's the modem's responsibilty to detect the busy signal.
Thanks for any help,
Bernn
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It is the modem's responsibility. Possibly the modem is set for the wrong country so the busy signal is not being detected; possibly there are some modem command strings you need to send to it on initialisation. In any event, there is nothing that can be done about it at the efax/efax-gtk level.
Chris
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
I just installed Efax-gtk on Debian and it works great out of the box.
I'm using an external USR Faxmodem.
efax-0.9a: 16:14:23 opened /dev/ttyS0
efax-0.9a: 16:14:26 using U.S. Robotics 56K FAX EXT V5.11.6U.S. Robotics 56K FAXOKOK in class 2.0
efax-0.9a: 16:14:28 dialing Txxxxxxx
*** Stopping send/receive session ***
Everything works great when the remote fax picks up.
When the line is busy, Efax just keeps on waiting & polling until I manually end the connection.
This happens from the old command line Efax script as well, not just Efax-gtk.
What should I do next? I assume it's the modem's responsibilty to detect the busy signal.
Thanks for any help,
Bernn
It is the modem's responsibility. Possibly the modem is set for the wrong country so the busy signal is not being detected; possibly there are some modem command strings you need to send to it on initialisation. In any event, there is nothing that can be done about it at the efax/efax-gtk level.
Chris
Just in case someone else has the problem.
I added "X4" to the end of the modem init string and it fixed the problem.
Thanks for the report. As you say, it may come in handy for someone else.
Chris