Mailinglist Archive: opensuse (3337 mails)

< Previous Next >
Re: [SLE] Faxing from 10.0
  • From: Mike McMullin <mwmcmlln@xxxxxxxx>
  • Date: Sun, 16 Apr 2006 12:31:45 -0400
  • Message-id: <1145205106.11361.19.camel@xxxxxxxxxxxxxx>
On Sun, 2006-04-16 at 17:16 +0200, Carlos E. R. wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
> The Sunday 2006-04-16 at 09:42 -0400, Mike McMullin wrote:
>
>
> ...
>
> > The log file for that try is as follows:
> > [start of log file]
> > Apr 16 09:28:36.93: [ 6813]: SESSION BEGIN 000000018 5198901928
> > Apr 16 09:28:36.93: [ 6813]: HylaFAX (tm) Version 4.2.1
> > Apr 16 09:28:36.93: [ 6813]: SEND FAX: JOB 6 DEST 519-890-1928 COMMID
> > 000000018 DEVICE '/dev/ttyS4'
> > Apr 16 09:28:36.93: [ 6813]: STATE CHANGE: RUNNING -> SENDING
> > Apr 16 09:28:36.93: [ 6813]: MODEM input buffering enabled
> > Apr 16 09:28:36.93: [ 6813]: <-- [9:AT+FLO=2\r]
> > Apr 16 09:28:37.05: [ 6813]: --> [2:OK]
>
> Once we get this far we know there is connection from hylafax to the
> modem.
>
> > Apr 16 09:28:37.85: [ 6813]: --> [2:OK]
> > Apr 16 09:28:37.88: [ 6813]: DIAL ***-***-****
> > Apr 16 09:28:37.88: [ 6813]: <-- [17:ATDT***-***-****\r]
>
> At this point, we know that it dialled. I assume it was you who removed
> the phone number, so not to post it here; good, but check that the number
> is correct. Hylafax can add prefixes on tis own.

Yes I blanked the number. Makes sense when this will be going into a
web wide search-able archive. From the phone book, I have a seven digit
number in Kdeprintfax, the phone book from jhylafax is the ten digit
number.

> > Apr 16 09:29:34.13: [ 6813]: --> [10:NO CARRIER]
>
> This is the real problem. No carrier. The fax-modem could not establish a
> sucessfull connection to the other side. Notice there is about one minute
> delay between the dialing and this error, so I can assume the call got
> through to your celular, but the fax negotiation failed.
>
> If you tel hylafax to keep the speaker on till connected, you might
> confirm this. I can guess by the noise if things are going well or not.

I hear the speaker in jhylafax, but not in kdeprintfax. This is
from /var/spool/fax/etc/config.ttyS4

SpeakerVolume: on

.....

# Set modem speaker volume commands: OFF QUIET LOW MEDIUM HIGH.
# Note that we both turn the speaker on/off and set volume.
#
ModemSetVolumeCmd: "ATM0 ATM1 ATM1 ATM1 ATM1"

This is from the stock USR56k config file provided with hylafax. I
copied it over to the etc directory and edited in the changes from the
hylafax setup utility, the original is backed up.


> > Apr 16 09:29:34.13: [ 6813]: SEND FAILED: JOB 6 DEST ***-***-**** ERR No
> > carrier detected
> > Apr 16 09:29:34.13: [ 6813]: <-- [5:ATH0\r]
> > Apr 16 09:29:34.25: [ 6813]: --> [2:OK]
> > Apr 16 09:29:34.25: [ 6813]: MODEM set DTR OFF
> > Apr 16 09:29:34.25: [ 6813]: STATE CHANGE: SENDING -> MODEMWAIT (timeout 5)
>
> Ok; I have compared it with failed a session of mine, and it gives the
> same messages.
>
> > Apr 16 09:29:34.25: [ 6813]: SESSION END
> > [end of log file]
> >
> > It cannot access the modem for some reason, while jhylafax does, and
> > did with modem mgetty not commented out.
>
> No, it is accessing correctly. It is kdeprintfax who gives the wrong
> error message. The log shows it. Or the error is another one: after the
> first try fails, the fax should be queued so that hylafax retries later on
> its own. Do you have the hylafax daemon running?

I think the log files are being generated from jhylafax and not from
kdeprintfax. I open konq in the log file directory and tried running
kdeprintfax, there was not new log from the failed attempt. I waited
several minutes and then ran jhylafax and it produced a new log file.
given the difference in phone numbers, 10 for jhylafax and 7 for
kdeprintfax, I'm fairly sure that the logs are from jhylafax, and
kdeprintfax isn't getting far enough to create an eror log file in
the /var/spool/fax/log directory.


P-733:/home/Mike # /etc/init.d/hylafax
usage: /etc/init.d/hylafax {start|stop|status|restart|reload}
P-733:/home/Mike # /etc/init.d/hylafax status
Checking for service HylaFAX: HylaFAX queue manager process:
running
HylaFAX client-server protocol server:
running



< Previous Next >
Follow Ups