I've been trying to set up faxing under 10.0. I've added a modem using hylafax's modemadd, specifying ttyS4 as the correct modem device. I did a test run using jhylafax and it connected to my cell phone properly. After a system reboot neither jhylafax not susefax (which errors in java) can find the modem. KDEPrintFax errors with: Sending to fax using: /usr/bin/capisuitefax -d '***1928' '/opt/fax/Mike/fax' can't write to queue dir (Note first three digits of phone are grunged be me for this message.) /opt/fax/Mike has attributes of 777 as does the intended fax file /opt/fax/Mike/fax. Also is there a way once I get this sorted out to just print to teh fax-modem using cups? Mike
On Thu, 06 Apr 2006 04:17:58 -0400, you wrote:
I've been trying to set up faxing under 10.0. I've added a modem using hylafax's modemadd, specifying ttyS4 as the correct modem device. I did a test run using jhylafax and it connected to my cell phone properly. After a system reboot neither jhylafax not susefax (which errors in java) can find the modem. KDEPrintFax errors with:
Sending to fax using: /usr/bin/capisuitefax -d '***1928' '/opt/fax/Mike/fax' can't write to queue dir
(Note first three digits of phone are grunged be me for this message.)
/opt/fax/Mike has attributes of 777 as does the intended fax file /opt/fax/Mike/fax.
Also is there a way once I get this sorted out to just print to teh fax-modem using cups?
Mike
I can't help with the modem problem, but to print to the faxmodem under linux, look at kdeprintfax (or google - there are several other alternatives). Under windows, WHFC is pretty good Mike- -- If you're not confused, you're not trying hard enough. -- Please note - Due to the intense volume of spam, we have installed site-wide spam filters at catherders.com. If email from you bounces, try non-HTML, non-encoded, non-attachments,
Mike McMullin wrote:
I've been trying to set up faxing under 10.0. I've added a modem using hylafax's modemadd, specifying ttyS4 as the correct modem device. I did a test run using jhylafax and it connected to my cell phone properly. After a system reboot neither jhylafax not susefax (which errors in java) can find the modem. KDEPrintFax errors with:
Sending to fax using: /usr/bin/capisuitefax -d '***1928' '/opt/fax/Mike/fax' can't write to queue dir
(Note first three digits of phone are grunged be me for this message.)
/opt/fax/Mike has attributes of 777 as does the intended fax file /opt/fax/Mike/fax.
Also is there a way once I get this sorted out to just print to teh fax-modem using cups?
Mike
Did you restart the hylafax daemon? I do not believe the hylafax daemon is setup to start automatically. -- Joseph Loo jloo@acm.org
On Thu, 2006-04-06 at 18:20 -0700, Joseph Loo wrote:
Mike McMullin wrote:
I've been trying to set up faxing under 10.0. I've added a modem using hylafax's modemadd, specifying ttyS4 as the correct modem device. I did a test run using jhylafax and it connected to my cell phone properly. After a system reboot neither jhylafax not susefax (which errors in java) can find the modem. KDEPrintFax errors with:
Sending to fax using: /usr/bin/capisuitefax -d '***1928' '/opt/fax/Mike/fax' can't write to queue dir
(Note first three digits of phone are grunged be me for this message.)
/opt/fax/Mike has attributes of 777 as does the intended fax file /opt/fax/Mike/fax.
Also is there a way once I get this sorted out to just print to teh fax-modem using cups?
Mike
Did you restart the hylafax daemon? I do not believe the hylafax daemon is setup to start automatically.
Daemon is running (levels 3 and 5) but not modem action. jhylafax is still not doing anything, susefax is not working, and kdeprintfax gives the same error as reported above.
On Friday 07 April 2006 12:06 am, Mike McMullin wrote:
On Thu, 2006-04-06 at 18:20 -0700, Joseph Loo wrote:
Mike McMullin wrote:
I've been trying to set up faxing under 10.0. I've added a modem using hylafax's modemadd, specifying ttyS4 as the correct modem device. I did a test run using jhylafax and it connected to my cell phone properly. After a system reboot neither jhylafax not susefax (which errors in java) can find the modem. KDEPrintFax errors with:
Sending to fax using: /usr/bin/capisuitefax -d '***1928' '/opt/fax/Mike/fax' can't write to queue dir
(Note first three digits of phone are grunged be me for this message.)
/opt/fax/Mike has attributes of 777 as does the intended fax file /opt/fax/Mike/fax.
Also is there a way once I get this sorted out to just print to teh fax-modem using cups?
Mike
Did you restart the hylafax daemon? I do not believe the hylafax daemon is setup to start automatically.
Daemon is running (levels 3 and 5) but not modem action.
jhylafax is still not doing anything, susefax is not working, and kdeprintfax gives the same error as reported above.
Do you have Hylafax's settings in /etc/inittab correct and running? Stan
On Fri, 2006-04-07 at 09:31 -0500, S Glasoe wrote:
On Friday 07 April 2006 12:06 am, Mike McMullin wrote:
On Thu, 2006-04-06 at 18:20 -0700, Joseph Loo wrote:
Mike McMullin wrote:
I've been trying to set up faxing under 10.0. I've added a modem using hylafax's modemadd, specifying ttyS4 as the correct modem device. I did a test run using jhylafax and it connected to my cell phone properly. After a system reboot neither jhylafax not susefax (which errors in java) can find the modem. KDEPrintFax errors with:
Sending to fax using: /usr/bin/capisuitefax -d '***1928' '/opt/fax/Mike/fax' can't write to queue dir
(Note first three digits of phone are grunged be me for this message.)
/opt/fax/Mike has attributes of 777 as does the intended fax file /opt/fax/Mike/fax.
Also is there a way once I get this sorted out to just print to teh fax-modem using cups?
Mike
Did you restart the hylafax daemon? I do not believe the hylafax daemon is setup to start automatically.
Daemon is running (levels 3 and 5) but not modem action.
jhylafax is still not doing anything, susefax is not working, and kdeprintfax gives the same error as reported above.
Do you have Hylafax's settings in /etc/inittab correct and running?
From my /etc/inittab # modem getty. mo:235:respawn:/usr/sbin/mgetty -s 38400 ttyS4 # fax getty (hylafax) mo:35:respawn:/usr/lib/fax/faxgetty /dev/ttyS4
On Friday 07 April 2006 11:41 pm, Mike McMullin wrote:
On Fri, 2006-04-07 at 09:31 -0500, S Glasoe wrote:
Do you have Hylafax's settings in /etc/inittab correct and running?
From my /etc/inittab
# modem getty. mo:235:respawn:/usr/sbin/mgetty -s 38400 ttyS4
# fax getty (hylafax) mo:35:respawn:/usr/lib/fax/faxgetty /dev/ttyS4
Try commenting out the modem's line there and running with just the fax. Haven't checked the documentation lately and its been awhile since I set this up so I don't remember if this is an either/or situation. Modem or fax but not both. I know that if just the fax getty is running it will work. Stan
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2006-04-10 at 09:37 -0500, S Glasoe wrote:
From my /etc/inittab
# modem getty. mo:235:respawn:/usr/sbin/mgetty -s 38400 ttyS4
# fax getty (hylafax) mo:35:respawn:/usr/lib/fax/faxgetty /dev/ttyS4
Try commenting out the modem's line there and running with just the fax. Haven't checked the documentation lately and its been awhile since I set this up so I don't remember if this is an either/or situation. Modem or fax but not both.
I know that if just the fax getty is running it will work.
I understand you may have both devices running, but only one handler. Ie, use a getty that diferentiates when the incoming call is a modem or a fax and that calls the appropiate program to handle it. Not sure how to do it, but I agree that he has to leave only the fax line in inittab. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFEPAAktTMYHG2NR9URAs9BAJ4/CCQzFzpKDwNyxlEKzhDPAo83XwCfTOuC 9uUirVAgev2r7C4OoLqOC+s= =sUPV -----END PGP SIGNATURE-----
On Tue, 2006-04-11 at 21:14 +0200, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Monday 2006-04-10 at 09:37 -0500, S Glasoe wrote:
From my /etc/inittab
# modem getty. mo:235:respawn:/usr/sbin/mgetty -s 38400 ttyS4
# fax getty (hylafax) mo:35:respawn:/usr/lib/fax/faxgetty /dev/ttyS4
Try commenting out the modem's line there and running with just the fax. Haven't checked the documentation lately and its been awhile since I set this up so I don't remember if this is an either/or situation. Modem or fax but not both.
I know that if just the fax getty is running it will work.
I understand you may have both devices running, but only one handler. Ie, use a getty that diferentiates when the incoming call is a modem or a fax and that calls the appropiate program to handle it.
Not sure how to do it, but I agree that he has to leave only the fax line in inittab.
I'll comment out the modem getty. However I'm not aware of how this will allow me to fax as a client when the clients still report failure, even though my cell phone records a connection. :(
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Saturday 2006-04-15 at 13:40 -0400, Mike McMullin wrote:
I'll comment out the modem getty. However I'm not aware of how this will allow me to fax as a client when the clients still report failure, even though my cell phone records a connection. :(
Pardon? Could you expand that info, I don't quite understand it. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFEQT94tTMYHG2NR9URAs6HAJ9UVNS4mwU9puS8eim4OeBvKjEF5ACeKf9H AUcu/VmmNud0B4yjhk4GpAo= =YhQd -----END PGP SIGNATURE-----
On Sat, 2006-04-15 at 20:46 +0200, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Saturday 2006-04-15 at 13:40 -0400, Mike McMullin wrote:
I'll comment out the modem getty. However I'm not aware of how this will allow me to fax as a client when the clients still report failure, even though my cell phone records a connection. :(
Pardon? Could you expand that info, I don't quite understand it.
My cell phone has fax receive capabilities, so I've been trying to fax to it. jhylafax now connects to the cell phone, kdeprintfax errors with the following: [beginning of error message] Converting input files to PostScript Sending fax to ***-**** (Mike (Fax)) Sending to fax using: /usr/bin/capisuitefax -d '8901928' '/opt/fax/Mike/fax' can't write to queue dir [end of error message] 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] Apr 16 09:28:37.05: [ 6813]: <-- [9:AT+FPP=0\r] Apr 16 09:28:37.16: [ 6813]: --> [2:OK] Apr 16 09:28:37.16: [ 6813]: <-- [9:AT+FBO=0\r] Apr 16 09:28:37.27: [ 6813]: --> [2:OK] Apr 16 09:28:37.27: [ 6813]: <-- [10:AT+FCT=30\r] Apr 16 09:28:37.38: [ 6813]: --> [2:OK] Apr 16 09:28:37.38: [ 6813]: <-- [15:AT+FNR=1,1,1,0\r] Apr 16 09:28:37.50: [ 6813]: --> [2:OK] Apr 16 09:28:37.50: [ 6813]: <-- [9:AT+FIE=0\r] Apr 16 09:28:37.61: [ 6813]: --> [2:OK] Apr 16 09:28:37.61: [ 6813]: <-- [9:AT+FBU=0\r] Apr 16 09:28:37.73: [ 6813]: --> [2:OK] Apr 16 09:28:37.73: [ 6813]: <-- [23:AT+FCC=1,5,2,2,0,0,0,0\r] 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] Apr 16 09:29:34.13: [ 6813]: --> [10:NO CARRIER] 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) 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.
On Sun, 2006-04-16 at 09:42 -0400, Mike McMullin wrote:
On Sat, 2006-04-15 at 20:46 +0200, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Saturday 2006-04-15 at 13:40 -0400, Mike McMullin wrote:
I'll comment out the modem getty. However I'm not aware of how this will allow me to fax as a client when the clients still report failure, even though my cell phone records a connection. :(
Pardon? Could you expand that info, I don't quite understand it.
My cell phone has fax receive capabilities, so I've been trying to fax to it. jhylafax now connects to the cell phone, kdeprintfax errors with the following: [beginning of error message] Converting input files to PostScript
Sending fax to ***-**** (Mike (Fax))
Sending to fax using: /usr/bin/capisuitefax -d '8901928' '/opt/fax/Mike/fax' can't write to queue dir [end of error message] 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] Apr 16 09:28:37.05: [ 6813]: <-- [9:AT+FPP=0\r] Apr 16 09:28:37.16: [ 6813]: --> [2:OK] Apr 16 09:28:37.16: [ 6813]: <-- [9:AT+FBO=0\r] Apr 16 09:28:37.27: [ 6813]: --> [2:OK] Apr 16 09:28:37.27: [ 6813]: <-- [10:AT+FCT=30\r] Apr 16 09:28:37.38: [ 6813]: --> [2:OK] Apr 16 09:28:37.38: [ 6813]: <-- [15:AT+FNR=1,1,1,0\r] Apr 16 09:28:37.50: [ 6813]: --> [2:OK] Apr 16 09:28:37.50: [ 6813]: <-- [9:AT+FIE=0\r] Apr 16 09:28:37.61: [ 6813]: --> [2:OK] Apr 16 09:28:37.61: [ 6813]: <-- [9:AT+FBU=0\r] Apr 16 09:28:37.73: [ 6813]: --> [2:OK] Apr 16 09:28:37.73: [ 6813]: <-- [23:AT+FCC=1,5,2,2,0,0,0,0\r] 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] Apr 16 09:29:34.13: [ 6813]: --> [10:NO CARRIER] 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) 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.
Mike@P-733:/opt/fax/Mike> cd /dev Mike@P-733:/dev> ls -l ttyS4 crw------- 1 uucp uucp 4, 68 2006-04-16 09:29 ttyS4 Mike@P-733:/dev> ls -l ttys4 crw-rw-rw- 1 root tty 3, 52 2006-04-16 05:02 ttys4 Most of the ttyS? and ttys? are root:tty owned, the ones that are root:uucp are all ttyS?. ttyS4 is the only one with owner and group uucp.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Sunday 2006-04-16 at 10:21 -0400, Mike McMullin wrote:
Mike@P-733:/opt/fax/Mike> cd /dev Mike@P-733:/dev> ls -l ttyS4 crw------- 1 uucp uucp 4, 68 2006-04-16 09:29 ttyS4 Mike@P-733:/dev> ls -l ttys4 crw-rw-rw- 1 root tty 3, 52 2006-04-16 05:02 ttys4
Most of the ttyS? and ttys? are root:tty owned, the ones that are root:uucp are all ttyS?. ttyS4 is the only one with owner and group uucp.
The "uppercase" devices (major 4) are serial ports: 4 char TTY devices 0 = /dev/tty0 Current virtual console 1 = /dev/tty1 First virtual console ... 63 = /dev/tty63 63rd virtual console 64 = /dev/ttyS0 First UART serial port ... 255 = /dev/ttyS191 192nd UART serial port But the lower case ttys I don't know. The major is 3... ah, they are PTY slaves, ie, pseudo-TTY slaves: 3 char Pseudo-TTY slaves 0 = /dev/ttyp0 First PTY slave 1 = /dev/ttyp1 Second PTY slave ... 255 = /dev/ttyef 256th PTY slave These are the old-style (BSD) PTY devices; Unix98 devices are on major 136 and above. As for the ownership diference you mention, faxgetty changes it. Try to modify the owner or permissions, you will see how it changes back within the minute. I don't know about mgetty, though. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFEQly+tTMYHG2NR9URAs42AKCMw6TUET9VfY7/l8VbWXsEO59VkQCcDHn5 21+FChMgfsxhzbxwxCuN+VQ= =9zFv -----END PGP SIGNATURE-----
-----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-----
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
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Sunday 2006-04-16 at 12:31 -0400, Mike McMullin wrote: ...
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.
I don't like those discrepancies... the end number should be the same, but the error would pop up after the first dial attempt, not before. ...
I think the log files are being generated from jhylafax and not from kdeprintfax.
Ah. :-(
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.
Not good. Then, you have a problem with "kdeprintfax", not hylafax. Try faxing directly with "sendfax"; for instance, from the configuration I have in OpenOffice: sendfax -m -n -T 3 -s a4 -D -d "(PHONE)" "(TMP)" from "man sendfax" (different from "info sendfax"): SYNOPSIS sendfax [ options ] [ files... ] DESCRIPTION sendfax submits one or more facsimile transmission requests to a HylaFAX facsimile server. Requests are normally processed immedi ately, although they may also be queued for transmission at a later time using a syntax identical to the at(1) command. ... sendfax passes POSTSCRIPT® and TIFF documents directly through to the fax server for transmission, and attempts to convert other file formats to either POSTSCRIPT or TIFF. In normal operation sendfax automatically converts ASCII-text, troff(1) output, Portable Document Format (PDF), and Silicon Graphics format images for transmission. Support for other file formats can be easily added through an extensible file typing and conversion facility; see typerules(5F). Note that since TIFF Class F documents are processed directly it is simple to forward a received facsimile. If this works, then check what kdeprintfax is using to send faxes. Mine (which I've never used, so it contains the defaults) says it uses: /usr/bin/sendfax -n %server_h %res %time_a %enterprise_x %comment_c %email_f -d %name_{@@@}%number %files which is the same command. I wonder if the syntax is entirely correct, I dont see many command switches above. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFEQ6RLtTMYHG2NR9URArkHAKCNss6zfPD9jSMjUr+KjjoObgLYhgCffx2s sduUzFL+OE7xqipKE6ft1QM= =Nxs4 -----END PGP SIGNATURE-----
On Mon, 2006-04-17 at 16:20 +0200, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Sunday 2006-04-16 at 12:31 -0400, Mike McMullin wrote:
...
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.
I don't like those discrepancies... the end number should be the same, but the error would pop up after the first dial attempt, not before.
Our phone company has decided to phase in the 10 digit dialing for all numbers including local.
I think the log files are being generated from jhylafax and not from kdeprintfax.
Ah. :-(
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.
Not good.
I thought as much
Then, you have a problem with "kdeprintfax", not hylafax. Try faxing directly with "sendfax"; for instance, from the configuration I have in OpenOffice:
sendfax -m -n -T 3 -s a4 -D -d "(PHONE)" "(TMP)"
log file created! It errored out, but then the I had my cell turned off Here's the log file: { Apr 17 18:16:08.12: [19843]: SESSION BEGIN 000000023 8901928 Apr 17 18:16:08.12: [19843]: HylaFAX (tm) Version 4.2.1 Apr 17 18:16:08.12: [19843]: SEND FAX: JOB 9 DEST 890-1928 COMMID 000000023 DEVICE '/dev/ttyS4' Apr 17 18:16:08.12: [19843]: STATE CHANGE: RUNNING -> SENDING Apr 17 18:16:08.12: [19843]: MODEM input buffering enabled Apr 17 18:16:08.12: [19843]: <-- [9:AT+FLO=2\r] Apr 17 18:16:08.23: [19843]: --> [2:OK] Apr 17 18:16:08.23: [19843]: <-- [9:AT+FPP=0\r] Apr 17 18:16:08.35: [19843]: --> [2:OK] Apr 17 18:16:08.35: [19843]: <-- [9:AT+FBO=0\r] Apr 17 18:16:08.46: [19843]: --> [2:OK] Apr 17 18:16:08.46: [19843]: <-- [10:AT+FCT=30\r] Apr 17 18:16:08.57: [19843]: --> [2:OK] Apr 17 18:16:08.57: [19843]: <-- [15:AT+FNR=1,1,1,0\r] Apr 17 18:16:08.69: [19843]: --> [2:OK] Apr 17 18:16:08.69: [19843]: <-- [9:AT+FIE=0\r] Apr 17 18:16:08.80: [19843]: --> [2:OK] Apr 17 18:16:08.80: [19843]: <-- [9:AT+FBU=0\r] Apr 17 18:16:08.91: [19843]: --> [2:OK] Apr 17 18:16:08.91: [19843]: <-- [23:AT+FCC=1,5,2,2,0,0,0,0\r] Apr 17 18:16:09.03: [19843]: --> [2:OK] Apr 17 18:16:09.04: [19843]: DIAL 890-1928 Apr 17 18:16:09.04: [19843]: <-- [13:ATDT***-***\r] Apr 17 18:17:04.84: [19843]: --> [10:NO CARRIER] Apr 17 18:17:04.85: [19843]: SEND FAILED: JOB 9 DEST 890-1928 ERR No carrier detected Apr 17 18:17:04.85: [19843]: <-- [5:ATH0\r] Apr 17 18:17:04.96: [19843]: --> [2:OK] Apr 17 18:17:04.96: [19843]: MODEM set DTR OFF Apr 17 18:17:04.96: [19843]: STATE CHANGE: SENDING -> MODEMWAIT (timeout 5) Apr 17 18:17:04.96: [19843]: SESSION END }
from "man sendfax" (different from "info sendfax"):
SYNOPSIS sendfax [ options ] [ files... ]
DESCRIPTION sendfax submits one or more facsimile transmission requests to a HylaFAX facsimile server. Requests are normally processed immedi ately, although they may also be queued for transmission at a later time using a syntax identical to the at(1) command. ... sendfax passes POSTSCRIPT® and TIFF documents directly through to the fax server for transmission, and attempts to convert other file formats to either POSTSCRIPT or TIFF. In normal operation sendfax automatically converts ASCII-text, troff(1) output, Portable Document Format (PDF), and Silicon Graphics format images for transmission. Support for other file formats can be easily added through an extensible file typing and conversion facility; see typerules(5F). Note that since TIFF Class F documents are processed directly it is simple to forward a received facsimile.
If this works, then check what kdeprintfax is using to send faxes. Mine (which I've never used, so it contains the defaults) says it uses:
/usr/bin/sendfax -n %server_h %res %time_a %enterprise_x %comment_c %email_f -d %name_{@@@}%number %files
which is the same command. I wonder if the syntax is entirely correct, I dont see many command switches above.
The fax system specified is hylafax, the default command line is: /usr/bin/capisuitefax -d %number %files IIRC capisuitefax was installed when I went into YaST to set up the fax. I want to note that I'm using kde 3.5.2. I do appreciate the help Carlos. I know I'm getting some where.
On Mon, 2006-04-17 at 18:28 -0400, Mike McMullin wrote:
On Mon, 2006-04-17 at 16:20 +0200, Carlos E. R. wrote:
[snip}
If this works, then check what kdeprintfax is using to send faxes. Mine (which I've never used, so it contains the defaults) says it uses:
/usr/bin/sendfax -n %server_h %res %time_a %enterprise_x %comment_c %email_f -d %name_{@@@}%number %files
which is the same command. I wonder if the syntax is entirely correct, I dont see many command switches above.
The fax system specified is hylafax, the default command line is: /usr/bin/capisuitefax -d %number %files
IIRC capisuitefax was installed when I went into YaST to set up the fax. I want to note that I'm using kde 3.5.2.
I do appreciate the help Carlos. I know I'm getting some where.
I switched your command line for mine and got the following in my log files using kdeprintfax: { Apr 17 18:41:48.49: [21367]: SESSION BEGIN 000000028 ******* Apr 17 18:41:48.49: [21367]: HylaFAX (tm) Version 4.2.1 Apr 17 18:41:48.49: [21367]: SEND FAX: JOB 11 DEST ******* COMMID 000000028 DEVICE '/dev/ttyS4' Apr 17 18:41:48.49: [21367]: STATE CHANGE: RUNNING -> SENDING Apr 17 18:41:48.49: [21367]: MODEM input buffering enabled Apr 17 18:41:48.49: [21367]: <-- [9:AT+FLO=2\r] Apr 17 18:41:48.60: [21367]: --> [2:OK] Apr 17 18:41:48.60: [21367]: <-- [9:AT+FPP=0\r] Apr 17 18:41:48.71: [21367]: --> [2:OK] Apr 17 18:41:48.72: [21367]: <-- [9:AT+FBO=0\r] Apr 17 18:41:48.83: [21367]: --> [2:OK] Apr 17 18:41:48.83: [21367]: <-- [10:AT+FCT=30\r] Apr 17 18:41:48.94: [21367]: --> [2:OK] Apr 17 18:41:48.94: [21367]: <-- [15:AT+FNR=1,1,1,0\r] Apr 17 18:41:49.06: [21367]: --> [2:OK] Apr 17 18:41:49.06: [21367]: <-- [9:AT+FIE=0\r] Apr 17 18:41:49.18: [21367]: --> [2:OK] Apr 17 18:41:49.23: [21367]: <-- [9:AT+FBU=0\r] Apr 17 18:41:49.34: [21367]: --> [2:OK] Apr 17 18:41:49.34: [21367]: <-- [23:AT+FCC=1,5,2,2,0,0,0,0\r] Apr 17 18:41:49.46: [21367]: --> [2:OK] Apr 17 18:41:49.47: [21367]: DIAL ******* Apr 17 18:41:49.47: [21367]: <-- [12:ATDT*******\r] Apr 17 18:41:51.58: [21367]: --> [12:NO DIAL TONE] Apr 17 18:41:51.58: [21367]: SEND FAILED: JOB 11 DEST 8901928 ERR No local dialtone Apr 17 18:41:51.58: [21367]: <-- [5:ATH0\r] Apr 17 18:41:51.69: [21367]: --> [2:OK] Apr 17 18:41:51.69: [21367]: MODEM set DTR OFF Apr 17 18:41:51.69: [21367]: STATE CHANGE: SENDING -> MODEMWAIT (timeout 5) Apr 17 18:41:51.69: [21367]: SESSION END } The not dial tone makes sense here. I unplugged the modem from the wall just prior to trying this. (Expected in-coming phone call.)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2006-04-17 at 18:48 -0400, Mike McMullin wrote:
I switched your command line for mine and got the following in my log files using kdeprintfax: ... Apr 17 18:41:49.47: [21367]: DIAL ******* Apr 17 18:41:49.47: [21367]: <-- [12:ATDT*******\r] Apr 17 18:41:51.58: [21367]: --> [12:NO DIAL TONE] ... The not dial tone makes sense here. I unplugged the modem from the wall just prior to trying this. (Expected in-coming phone call.)
Good! We are getting nearer, then :-) - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFERCh1tTMYHG2NR9URAih2AJ9qSg/AtH0yYlnMa+oBLxG4VFmrFgCgjD81 sab1vUcYdBTjFlI4WRuADGE= =urqr -----END PGP SIGNATURE-----
On Tue, 2006-04-18 at 01:44 +0200, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Monday 2006-04-17 at 18:48 -0400, Mike McMullin wrote:
I switched your command line for mine and got the following in my log files using kdeprintfax: ... Apr 17 18:41:49.47: [21367]: DIAL ******* Apr 17 18:41:49.47: [21367]: <-- [12:ATDT*******\r] Apr 17 18:41:51.58: [21367]: --> [12:NO DIAL TONE] ... The not dial tone makes sense here. I unplugged the modem from the wall just prior to trying this. (Expected in-coming phone call.)
Good! We are getting nearer, then :-)
I finally got back to this today. Here's the resulting log file (edited for space): May 21 09:59:38.14: [10019]: SESSION BEGIN 000000044 5199740726 May 21 09:59:38.14: [10019]: HylaFAX (tm) Version 4.2.1 May 21 09:59:38.15: [10019]: SEND FAX: JOB 13 DEST ***-***-**** COMMID 000000044 DEVICE '/dev/ttyS4' May 21 09:59:38.15: [10019]: STATE CHANGE: RUNNING -> SENDING May 21 09:59:38.15: [10019]: MODEM input buffering enabled May 21 09:59:38.16: [10019]: <-- [9:AT+FLO=2\r] May 21 09:59:38.27: [10019]: --> [2:OK] May 21 09:59:38.27: [10019]: <-- [9:AT+FPP=0\r] May 21 09:59:38.38: [10019]: --> [2:OK] May 21 09:59:38.38: [10019]: <-- [9:AT+FBO=0\r] May 21 09:59:38.50: [10019]: --> [2:OK] May 21 09:59:38.50: [10019]: <-- [10:AT+FCT=30\r] May 21 09:59:38.61: [10019]: --> [2:OK] May 21 09:59:38.61: [10019]: <-- [15:AT+FNR=1,1,1,0\r] May 21 09:59:38.72: [10019]: --> [2:OK] May 21 09:59:38.72: [10019]: <-- [9:AT+FIE=0\r] May 21 09:59:38.84: [10019]: --> [2:OK] May 21 09:59:38.84: [10019]: <-- [9:AT+FBU=0\r] May 21 09:59:38.95: [10019]: --> [2:OK] May 21 09:59:38.95: [10019]: <-- [23:AT+FCC=1,5,2,2,0,0,0,0\r] May 21 09:59:39.07: [10019]: --> [2:OK] May 21 09:59:39.07: [10019]: DIAL ***-***-*** May 21 09:59:39.07: [10019]: <-- [17:ATDT***-***-****\r] May 21 10:00:06.42: [10019]: --> [4:+FCO] May 21 10:00:08.94: [10019]: --> [27:+FCI:" *** *** ****"] May 21 10:00:08.94: [10019]: REMOTE CSI "*** *** ****" May 21 10:00:08.94: [10019]: --> [20:+FIS:1,5,0,2,1,0,0,3] May 21 10:00:08.94: [10019]: --> [2:OK] May 21 10:00:08.94: [10019]: REMOTE best rate 14400 bit/s May 21 10:00:08.94: [10019]: REMOTE max A4 page width (215 mm) May 21 10:00:08.94: [10019]: REMOTE max unlimited page length May 21 10:00:08.94: [10019]: REMOTE best vres 7.7 line/mm May 21 10:00:08.94: [10019]: REMOTE best format 2-D MR May 21 10:00:08.94: [10019]: REMOTE best 10 ms/scanline May 21 10:00:08.94: [10019]: USE 14400 bit/s May 21 10:00:08.95: [10019]: USE 10 ms/scanline May 21 10:00:08.95: [10019]: SEND file "docq/doc11.ps;01" May 21 10:00:08.95: [10019]: USE A4 page width (215 mm) May 21 10:00:08.95: [10019]: USE unlimited page length May 21 10:00:08.95: [10019]: USE 7.7 line/mm May 21 10:00:08.95: [10019]: USE 1-D MH May 21 10:00:08.95: [10019]: <-- [23:AT+FIS=1,5,0,2,0,0,0,3\r] May 21 10:00:09.07: [10019]: --> [2:OK] May 21 10:00:09.07: [10019]: <-- [7:AT+FDT\r] May 21 10:00:09.35: [10019]: --> [20:+FCS:1,5,0,2,0,0,0,3] May 21 10:00:15.97: [10019]: --> [7:CONNECT] May 21 10:00:15.97: [10019]: SEND begin page May 21 10:00:15.97: [10019]: <-- data [1027] _______________ May 21 10:00:36.98: [10019]: <-- data [569] May 21 10:00:36.98: [10019]: SENT 28217 bytes of data May 21 10:00:36.98: [10019]: SEND 1D RTC May 21 10:00:36.98: [10019]: <-- data [9] May 21 10:00:36.98: [10019]: SEND end page May 21 10:00:36.98: [10019]: SEND send MPS (more pages, same document) May 21 10:00:36.98: [10019]: <-- data [2] May 21 10:00:48.58: [10019]: --> [2:OK] May 21 10:00:48.58: [10019]: <-- [8:AT+FPS?\r] May 21 10:00:48.82: [10019]: --> [1:1] May 21 10:00:48.82: [10019]: --> [2:OK] May 21 10:00:48.82: [10019]: SEND recv MCF (message confirmation) May 21 10:00:48.83: [10019]: SEND FAX (000000044): FROM Mike@P-733.mwmcmlln TO ***-***-**** (page 1 of 4 sent in 0:40) May 21 10:00:48.83: [10019]: <-- [7:AT+FDT\r] May 21 10:00:49.19: [10019]: --> [7:CONNECT] May 21 10:00:49.19: [10019]: SEND begin page May 21 10:00:49.19: [10019]: <-- data [1028] _________________ May 21 10:01:15.77: [10019]: <-- data [428] May 21 10:01:17.92: [10019]: SENT 39340 bytes of data May 21 10:01:17.92: [10019]: SEND 1D RTC May 21 10:01:17.93: [10019]: <-- data [9] May 21 10:01:17.93: [10019]: SEND end page May 21 10:01:17.93: [10019]: SEND send MPS (more pages, same document) May 21 10:01:17.93: [10019]: <-- data [2] May 21 10:01:25.30: [10019]: --> [2:OK] May 21 10:01:25.31: [10019]: <-- [8:AT+FPS?\r] May 21 10:01:25.54: [10019]: --> [1:1] May 21 10:01:25.55: [10019]: --> [2:OK] May 21 10:01:25.55: [10019]: SEND recv MCF (message confirmation) May 21 10:01:25.55: [10019]: SEND FAX (000000044): FROM Mike@P-733.mwmcmlln TO ***-***-**** (page 2 of 4 sent in 0:37) ____________________ May 21 10:01:55.19: [10019]: SENT 41583 bytes of data May 21 10:01:55.19: [10019]: SEND 1D RTC May 21 10:01:55.19: [10019]: <-- data [9] May 21 10:01:55.30: [10019]: SEND end page May 21 10:01:55.30: [10019]: SEND send MPS (more pages, same document) May 21 10:01:55.30: [10019]: <-- data [2] May 21 10:02:04.17: [10019]: --> [2:OK] May 21 10:02:04.17: [10019]: <-- [8:AT+FPS?\r] May 21 10:02:04.41: [10019]: --> [1:1] May 21 10:02:04.41: [10019]: --> [2:OK] May 21 10:02:04.41: [10019]: SEND recv MCF (message confirmation) May 21 10:02:04.42: [10019]: SEND FAX (000000044): FROM Mike@P-733.mwmcmlln TO ***-***-**** (page 3 of 4 sent in 0:39) May 21 10:02:04.42: [10019]: <-- [7:AT+FDT\r] May 21 10:02:04.78: [10019]: --> [7:CONNECT] May 21 10:02:04.78: [10019]: SEND begin page ____________________ May 21 10:02:17.41: [10019]: SENT 14543 bytes of data May 21 10:02:17.41: [10019]: SEND 1D RTC May 21 10:02:17.41: [10019]: <-- data [9] May 21 10:02:17.41: [10019]: SEND end page May 21 10:02:17.41: [10019]: SEND send EOP (no more pages or documents) May 21 10:02:17.41: [10019]: <-- data [2] May 21 10:02:25.22: [10019]: --> [7:+FHS:00] May 21 10:02:25.22: [10019]: REMOTE HANGUP: Normal and proper end of connection (code 0) May 21 10:02:25.22: [10019]: SEND recv MCF (message confirmation) May 21 10:02:25.23: [10019]: SEND FAX (000000044): FROM Mike@P-733.mwmcmlln TO ***-***-**** (page 4 of 4 sent in 0:21) May 21 10:02:25.23: [10019]: SEND FAX (000000044): FROM Mike@P-733.mwmcmlln TO ***-***-**** (docq/doc11.ps;01 sent in 2:17) May 21 10:02:26.24: [10019]: <-- [5:ATH0\r] May 21 10:02:26.24: [10019]: --> [2:OK] May 21 10:02:26.24: [10019]: MODEM set DTR OFF May 21 10:02:26.24: [10019]: STATE CHANGE: SENDING -> MODEMWAIT (timeout 5) May 21 10:02:26.24: [10019]: SESSION END _____________ End of log file. I faxed four pages, and then went and picked them up. I think my modem config file needs a bit of tweakling in the ident section, and I noticed this line above: May 21 10:00:08.95: [10019]: USE A4 page width (215 mm) I'd prefer a normal letter size, and I'm wondering if this is teh result of t4eh negotiation with the fax reciever?: May 21 10:00:08.94: [10019]: REMOTE max A4 page width (215 mm) I ended up faxing right out of OpenOffice which I didn't really want to do, but couldn't seem to find a simple print to file as postscript. I'll probably want to be able to fax unmodified copies of this at various times so I'm figuring it would be easier to just fire up either kdeprintfax or jhylafax and send that way. Mike
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2006-04-17 at 18:28 -0400, Mike McMullin wrote:
Then, you have a problem with "kdeprintfax", not hylafax. Try faxing directly with "sendfax"; for instance, from the configuration I have in OpenOffice:
sendfax -m -n -T 3 -s a4 -D -d "(PHONE)" "(TMP)"
log file created! It errored out, but then the I had my cell turned off
Apr 17 18:16:09.04: [19843]: <-- [13:ATDT***-***\r] Apr 17 18:17:04.84: [19843]: --> [10:NO CARRIER]
Funny. It should have been "no answer", or something of the sort; those error depend on the modem, though. No... I'm thinking... the cellular company might have given a voice message to your modem, so the "no carrier". Correct, then.
The fax system specified is hylafax, the default command line is: /usr/bin/capisuitefax -d %number %files
I thought capisuite was used for ISDN :-? [...] Yes, it is: : Summary : ISDN telecommunication suite providing fax and voice services : Description : : CapiSuite is an ISDN telecommunication suite providing easy to use : telecommunication functions which can be controlled from Python : scripts. Therefore, it will not work for you unless you have ISDN services and an appropiate card.
IIRC capisuitefax was installed when I went into YaST to set up the fax. I want to note that I'm using kde 3.5.2.
I do appreciate the help Carlos. I know I'm getting some where.
Welcome; it is an interesting problem. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFERChttTMYHG2NR9URAiVHAJ9v3B54aa5W6OJB5AZethUNKHZaVACeJOCk JnMy/MS9tPoS2TQp0reGRdE= =rHB1 -----END PGP SIGNATURE-----
On Tue, 2006-04-18 at 01:44 +0200, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Monday 2006-04-17 at 18:28 -0400, Mike McMullin wrote:
Then, you have a problem with "kdeprintfax", not hylafax. Try faxing directly with "sendfax"; for instance, from the configuration I have in OpenOffice:
sendfax -m -n -T 3 -s a4 -D -d "(PHONE)" "(TMP)"
log file created! It errored out, but then the I had my cell turned off
Apr 17 18:16:09.04: [19843]: <-- [13:ATDT***-***\r] Apr 17 18:17:04.84: [19843]: --> [10:NO CARRIER]
Funny. It should have been "no answer", or something of the sort; those error depend on the modem, though. No... I'm thinking... the cellular company might have given a voice message to your modem, so the "no carrier". Correct, then.
Voice mail capable cell phone, so the company takes a message when the phone doesn't get answered.
The fax system specified is hylafax, the default command line is: /usr/bin/capisuitefax -d %number %files
I thought capisuite was used for ISDN :-?
[...]
Yes, it is:
: Summary : ISDN telecommunication suite providing fax and voice services : Description : : CapiSuite is an ISDN telecommunication suite providing easy to use : telecommunication functions which can be controlled from Python : scripts.
Therefore, it will not work for you unless you have ISDN services and an appropiate card.
I think YaST needs a bit of a going over then. ISDN cards are a separate module, and I just checked to make sure nothing was set up, and it comes up blank. The one other thing that the modem is capable of is voice, which I'll wait on. I think that's more of a server function, and this modem is on my main system.
IIRC capisuitefax was installed when I went into YaST to set up the fax. I want to note that I'm using kde 3.5.2.
Checking just now it seems that the phone answering module will install capisuite. :(
I do appreciate the help Carlos. I know I'm getting some where.
Welcome; it is an interesting problem.
:) I hope to get this written down and posted so others will have an easier time of it than I have had. Googleing this subject I ran across an old question from Carl Spitzer, which may end up getting answered in course. Mike
participants (6)
-
Carlos E. R. -
Carlos E. R. -
Joseph Loo -
Michael W Cocke -
Mike McMullin -
S Glasoe