Mailinglist Archive: opensuse (3337 mails)

< Previous Next >
Re: [SLE] Faxing from 10.0
  • From: "Carlos E. R." <robin.listas@xxxxxxxxxxxxxx>
  • Date: Sun, 16 Apr 2006 17:16:28 +0200 (CEST)
  • Message-id: <Pine.LNX.4.61.0604161703310.28787@xxxxxxxxxxxxxxxx>
-----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.

> 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.

> 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?


- --
Cheers,
Carlos Robinson

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
Comment: Made with pgp4pine 1.76

iD8DBQFEQl/OtTMYHG2NR9URAsceAJkBQlViQYHVHdDIqX80D1PUQk6/sQCfZcdq
a3Fos88RTdIiQt07g24B3QA=
=Kk55
-----END PGP SIGNATURE-----


< Previous Next >
Follow Ups