![]() |
Aug 26 00:50:12.42: [30154]: DIAL 4537442 Aug 26 00:50:12.42: [30154]: <-- [12:ATDT4537442\r] Aug 26 00:53:12.45: [30154]: SEND FAILED: JOB 30 DEST 4537442 ERR [6] Unknown +problem Aug 26 00:53:12.49: [30154]: SEND FAILED: JOB 30 DEST 4537442 ERR [333] Unknown +problem; too many attempts to dial Aug 26 00:53:13.49: [30154]: <-- [5:ATH0\r] Aug 26 00:53:13.70: [30154]: --> [2:OK] Aug 26 00:53:13.72: [30154]: SESSION END
As you can see, the fax server waits 3 minutes idling, and then exits.
It seems it has no notion that the called device "took up the hook".
(While the Elink 310 itself clearly seems to have that notion, its
dialing led stops blinking exactly at the point my "remote" faxdevice
takes up the hook).
Unfortunately, I don't know how fax is actually done, so I didn't
manage to come further with minicom, either.
Here is my config.tty in case this matters:
http://dpaste.com/hold/234092/
(It's mostly standard. I have changed +fdcc=? to +fdcc? because my
Elink wants it that way, and the flow control commands, but those seem
to have no influence (as opposed to +fdcc=? which broke device
initialization).
Any suggestions? Is there the possibility that it simply won't work with Elink 310?
What could I do to make a test fax sending from minicom?
____________________ 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*