I doubt faxing over a VoIP connection to your provider will work. Please see: http://www.soft-switch.org/foip.html
--Tim
That is not so strange. Faxing over Voip will work once... in a while. But it's the inconsistency of it that makes it unusable. You may want to look into some of the various Fax over IP technologies out there since straight fax data compressed into a lossy codec and sent out a best effort transport method like SIP/IAX will only give you headaches...
--Tim
The job file q40 shows that commid:000000051
So we look in the log file c000000051 and we see the following:
Nov 04 17:58:44.49: [ 4267]: SESSION BEGIN 000000051 5511XXXXX
Nov 04 17:58:44.49: [ 4267]: HylaFAX (tm) Version 4.4.4
Nov 04 17:58:44.49: [ 4267]: SEND FAX: JOB 40 DEST +5511XXXXX COMMID
000000051 DEVICE '/dev/ttyIAX0' FROM 'root <ro...@debian.localhost>' USER
root
Nov 04 17:58:44.49: [ 4267]: <-- [12:AT+FCLASS=1\r]
Nov 04 17:58:44.49: [ 4267]: --> [2:OK]
Nov 04 17:58:44.49: [ 4267]: DIAL 0115511XXXXX
Nov 04 17:58:44.49: [ 4267]: <-- [20:ATDT0115511XXXXX\r]
Nov 04 17:59:45.72: [ 4267]: --> [10:NO CARRIER]
Nov 04 17:59:45.72: [ 4267]: SEND FAILED: JOB 40 DEST +5511XXXX ERR [2] No
carrier detected
Nov 04 17:59:46.72: [ 4267]: <-- [5:ATH0\r]
Nov 04 17:59:46.72: [ 4267]: --> [2:OK]
Nov 04 17:59:46.72: [ 4267]: SESSION END
So this tells us that when the modem tried to dial in detected no carrier.
The best place to start troubleshooting this issue is to make sure that you
are able to actually dial out using this /dev/ttyIAX0
And the easiest way to do this is to use minicom and manually initiate the
outbound call with AT commands:
ATD<number>
Until you can actually dial out using minicom and manually providing the AT
commands you can stop expecting HylaFAX to send faxes.
Let us know what happens?
Dominique
On Wed, Nov 4, 2009 at 10:11 PM, Cams <cams...@gmail.com> wrote:
> could this help?
>
>
> ----- Original Message -----
> *From:* Dominique dHotman <domi...@dhotman.za.net>
> *To:* Cams <cams...@gmail.com>
> *Sent:* Wednesday, November 04, 2009 5:39 PM
> *Subject:* Re: [hylafax-users] No Carrier Detected
>
> these log files are found in /var/spool/hylafax/log/
>
> and the file name is c<communication_id> (i.e. c0002344)
>
> you can find the communication id by looking at the fax job file which is
> either in the sendq or doneq depending on if the fax job is in queued, in
> progress or finished. These queue directories are found in
> /var/spool/hylafax/sendq and /var/spool/hylafax/doneq
>
>
>
> On Wed, Nov 4, 2009 at 9:36 PM, Cams <cams...@gmail.com> wrote:
>
>> wich one is this file?
>> and where to find it?
>>
>>
>> ----- Original Message -----
>> *From:* Dominique dHotman <domi...@dhotman.za.net>
>> *To:* Cams <cams...@gmail.com>
>> *Sent:* Wednesday, November 04, 2009 5:35 PM
>> *Subject:* Re: [hylafax-users] No Carrier Detected
>>
>> interceptty will only log traffic that passes through a tty it works the
>> same as tcpdump. The best thing for you to look at are the communication
>> logs.
>>
>> Posting the communication log of a failed fax job would help understanding
>> your problem.