Re: [hylafax-users] T38modem and Hylafax issues

[Aidan Van Dyk <aidan@xxxxxxxx>]

* Jennifer Eyrich <jce@xxxxxxxxxxx> [071129 15:41]:
> 
> Status so far...
> 
> 
> I setup the T38modem again and left the terminal window open.  This 
> solves the wedged issue and the modem is now ready.

That makes sence, if t38modem isn't running correctly, then faxgetty
would find the modem "wedged".

> When I try to send a fax, this is what I get in the log
> 
> Nov 29 15:38:26.67: [17010]: SESSION BEGIN 000000023 12156284752
> Nov 29 15:38:26.67: [17010]: HylaFAX (tm) Version 4.4.0

Note that 4.4.3 is out already.

> Nov 29 15:38:26.67: [17010]: SEND FAX: JOB 3 DEST 12156284752 COMMID 
> 000000023 DEVICE '/dev/ttyx0' FROM 'Jennifer <jce@xxxxxxxxxxx>' USER  username
> Nov 29 15:38:26.67: [17010]: STATE CHANGE: RUNNING -> SENDING
> Nov 29 15:38:26.67: [17010]: <-- [12:AT+FCLASS=1\r]
> Nov 29 15:38:26.67: [17010]: --> [2:OK]
> Nov 29 15:38:26.67: [17010]: DIAL 12156284752
> Nov 29 15:38:26.67: [17010]: <-- [16:ATDT12156284752\r]
> Nov 29 15:38:26.67: [17010]: --> [4:BUSY]

So t38modem told faxsend that it was busy.  

> The fax machine is one that is in the office and it is not busy..
> 
> What could possible be the issue?

You'll have to see where the call wasn't made.  You'll have to look at
t38 logs/output, maybe your gateway logs/output, etc, to find how var
down the "sip/h323" chain the call made it, and where it was rejected.

> Also, what do I go about the T38modem terminal window, it appears that 
> I have to leave it open.

I'm not sure what options t38modem has.  A simple trick is to run it in
a screen session, so you can see all it's output, but not have it hang if
you're shell/terminal disconnects/quits, etc.  

a.

-- 
Aidan Van Dyk                                             aidan@xxxxxxxx
Senior Software Developer                          +1 215 825-8700 x8103
iFAX Solutions, Inc.                                http://www.ifax.com/

Attachment: signature.asc
Description: Digital signature