henry007
asked on
USB modem with hylafax - redhat ES5 - waiting for modem to come ready....
Hi I added a 2nd and 3rd modem to my RH server with faxaddmodem command and basicaly here's what it configured ,but I can't make these modems send faxes due to "waiting for modem to come ready" status, any clues of what's wrong with this picture ?
Hmm, this looks like a Class 1 modem.
Product code (ATI0) is "5601".
Other information (ATI3) is "U.S. Robotics 56K FAX USB V1.1.0".
DTE-DCE flow control scheme [default]?
Modem manufacturer is "3Com U. S. Robotics".
Modem model is "3CP5610".
Using prototype configuration file usr-xon...
The modem configuration parameters are:
ModemAnswerCmd: AT+FCLASS=1A
ModemFlowControl: xonxoff
ModemHardFlowCmd: AT&H1&I0&R2
ModemMfrQueryCmd: !USR
ModemModelQueryCmd: ATI3
ModemNoFlowCmd: AT&H0&I0&R1
ModemRate: 19200
ModemResultCodesCmd: ATQ0X4
ModemRevQueryCmd: ATI7
ModemSetupAACmd: AT+FCLASS=0
ModemSetupDCDCmd: AT&C1
ModemSetupDTRCmd: ATS13=1&D2
ModemSoftFlowCmd: AT&H2&I2&R1
Class1NFLOCmd: AT&H0&I0&R1
Class1HFLOCmd: AT&H1&I0&R2
Class1SFLOCmd: ""
Class1ResponseWaitCmd: AT+FRS=1
Class1SwitchingCmd: "<delay\0727>"
[root@atkred etc]# faxstat
HylaFAX scheduler on atkred.com: Running
Modem ttyACM0 (+1.714.850.####): Waiting for modem to come ready
Modem ttyACM1 (+1.714.850.####): Waiting for modem to come ready
Modem ttyS0 (+1.714.850.####): Running and idle
This is my log file when I run
[root@atkred etc]# /usr/local/sbin/faxgetty /dev/ttyACM1
Aug 28 22:06:56 atkred FaxGetty[19401]: OPEN /dev/ttyACM1 HylaFAX (tm) Version 4.4.4
Aug 28 22:06:56 atkred FaxGetty[19401]: Purge stale UUCP lock /var/lock/LCK..ttyACM1
Aug 28 22:07:13 atkred FaxGetty[19401]: /dev/ttyACM1: Can not initialize modem.
Aug 28 22:08:47 atkred FaxGetty[19401]: Unable to setup modem on /dev/ttyACM1; giving up after 2 attempts
Aug 28 22:08:47 atkred FaxGetty[19401]: CLOSE /dev/ttyACM1
Aug 28 22:08:47 atkred FaxQueuer[17983]: MODEM /dev/ttyACM1 appears to be wedged
Aug 28 22:08:47 atkred FaxQueuer[17983]: MODEM WEDGED: bin/wedged "ttyACM1" "/dev/ttyACM1"
Aug 28 22:08:48 atkred FaxQueuer[17983]: NOTIFY exit status: 0 (19404)
Thanks
Hmm, this looks like a Class 1 modem.
Product code (ATI0) is "5601".
Other information (ATI3) is "U.S. Robotics 56K FAX USB V1.1.0".
DTE-DCE flow control scheme [default]?
Modem manufacturer is "3Com U. S. Robotics".
Modem model is "3CP5610".
Using prototype configuration file usr-xon...
The modem configuration parameters are:
ModemAnswerCmd: AT+FCLASS=1A
ModemFlowControl: xonxoff
ModemHardFlowCmd: AT&H1&I0&R2
ModemMfrQueryCmd: !USR
ModemModelQueryCmd: ATI3
ModemNoFlowCmd: AT&H0&I0&R1
ModemRate: 19200
ModemResultCodesCmd: ATQ0X4
ModemRevQueryCmd: ATI7
ModemSetupAACmd: AT+FCLASS=0
ModemSetupDCDCmd: AT&C1
ModemSetupDTRCmd: ATS13=1&D2
ModemSoftFlowCmd: AT&H2&I2&R1
Class1NFLOCmd: AT&H0&I0&R1
Class1HFLOCmd: AT&H1&I0&R2
Class1SFLOCmd: ""
Class1ResponseWaitCmd: AT+FRS=1
Class1SwitchingCmd: "<delay\0727>"
[root@atkred etc]# faxstat
HylaFAX scheduler on atkred.com: Running
Modem ttyACM0 (+1.714.850.####): Waiting for modem to come ready
Modem ttyACM1 (+1.714.850.####): Waiting for modem to come ready
Modem ttyS0 (+1.714.850.####): Running and idle
This is my log file when I run
[root@atkred etc]# /usr/local/sbin/faxgetty /dev/ttyACM1
Aug 28 22:06:56 atkred FaxGetty[19401]: OPEN /dev/ttyACM1 HylaFAX (tm) Version 4.4.4
Aug 28 22:06:56 atkred FaxGetty[19401]: Purge stale UUCP lock /var/lock/LCK..ttyACM1
Aug 28 22:07:13 atkred FaxGetty[19401]: /dev/ttyACM1: Can not initialize modem.
Aug 28 22:08:47 atkred FaxGetty[19401]: Unable to setup modem on /dev/ttyACM1; giving up after 2 attempts
Aug 28 22:08:47 atkred FaxGetty[19401]: CLOSE /dev/ttyACM1
Aug 28 22:08:47 atkred FaxQueuer[17983]: MODEM /dev/ttyACM1 appears to be wedged
Aug 28 22:08:47 atkred FaxQueuer[17983]: MODEM WEDGED: bin/wedged "ttyACM1" "/dev/ttyACM1"
Aug 28 22:08:48 atkred FaxQueuer[17983]: NOTIFY exit status: 0 (19404)
Thanks
LunarNRG
I assume you already know this is a cdc compliant usb modem (a hardware modem, or a linux supported winmodem)? My initial thought would be that it is not.
ASKER
yes it does based on this readme file that came from the install cd :
-----------------start here --------------------------
Installation instructions for Linux 2.4.x and 2.6.x kernels.
The U.S.Robotics 56K USB modem conforms to the CDC specification and to
the ACM sub-class.
Requirements:
A recent kernel; example: 2.4.20 kernel or higher.
USB Modem (CDC ACM) driver compiled into the kernel or as a loadable module.
The U.S.Robotics USB modem has been tested in the following distributions:
RedHat 9.0 (kernel 2.4.20-8)
Fedora Core 1 (kernel 2.4.22-1)
Red Hat Enterprise Linux 3 (kernel 2.4.21-51.EL)
Fedora 7 (kernel 2.6.22.1-41.fc7)
Ubuntu 7.04 (kernel 2.6.20-16)
Procedure:
1. Insert the modem into a free USB port.
2. Verify the PWR LED has illuminated.
3. Access the modem with a terminal emulation program.
Troubleshooting:
Open a terminal shell and log in as root.
1. Verify modem enumeration with the following command:
lsusb
Below is an example output.
Bus 001 Device 002: ID 0baf:0303 U.S. Robotics
2. Verify the CDC ACM module as loaded with the following command:
lsmod
If the version of Linux kernel has the CDC ACM driver compiled into it, you
should now be able to use a terminal emulator program (for example: minicom)
to attach to the modem.
If the kernel has the CDC ACM driver built as a module, then you may have to
enable the driver with the following command:
modprobe acm
(used in 2.4.x kernels)
modprobe cdc_acm
(used in 2.6.x kernels)
3. Verify device node creation.
Some distributions will automatically create a device node
for the modem in /dev. Below is the device node as created in Fedora 7.
crw-rw---- 1 root uucp 166, 0 2007-09-12 10:33 ttyACM0
The CDC ACM driver allows up to 32 modems. If the device node does not exist,
create one using the following command:
mknod /dev/ttyACM0 c 166 0
Additional device nodes can be created for additional modems as follows:
mknod /dev/ttyACM1 c 166 1
mknod /dev/ttyACM2 c 166 2
mknod /dev/ttyACM3 c 166 3
4. Access the modem.
Use a terminal emulator program (for example: minicom) to access the modem using
the device node created above. For example, setup the serial port for minicom to
use the device node /dev/ttyACM0.
5. Internet dialers.
Applications such as WvDial and KPPP may require access to the modem via the
/dev/modem device node.
You can set up a symbolic link from /dev/modem to the ACM modem device by using
the following command:
ln -s /dev/ttyACM0 /dev/modem
--------------------- cut here --------------------------
please let me know what you think
-----------------start here --------------------------
Installation instructions for Linux 2.4.x and 2.6.x kernels.
The U.S.Robotics 56K USB modem conforms to the CDC specification and to
the ACM sub-class.
Requirements:
A recent kernel; example: 2.4.20 kernel or higher.
USB Modem (CDC ACM) driver compiled into the kernel or as a loadable module.
The U.S.Robotics USB modem has been tested in the following distributions:
RedHat 9.0 (kernel 2.4.20-8)
Fedora Core 1 (kernel 2.4.22-1)
Red Hat Enterprise Linux 3 (kernel 2.4.21-51.EL)
Fedora 7 (kernel 2.6.22.1-41.fc7)
Ubuntu 7.04 (kernel 2.6.20-16)
Procedure:
1. Insert the modem into a free USB port.
2. Verify the PWR LED has illuminated.
3. Access the modem with a terminal emulation program.
Troubleshooting:
Open a terminal shell and log in as root.
1. Verify modem enumeration with the following command:
lsusb
Below is an example output.
Bus 001 Device 002: ID 0baf:0303 U.S. Robotics
2. Verify the CDC ACM module as loaded with the following command:
lsmod
If the version of Linux kernel has the CDC ACM driver compiled into it, you
should now be able to use a terminal emulator program (for example: minicom)
to attach to the modem.
If the kernel has the CDC ACM driver built as a module, then you may have to
enable the driver with the following command:
modprobe acm
(used in 2.4.x kernels)
modprobe cdc_acm
(used in 2.6.x kernels)
3. Verify device node creation.
Some distributions will automatically create a device node
for the modem in /dev. Below is the device node as created in Fedora 7.
crw-rw---- 1 root uucp 166, 0 2007-09-12 10:33 ttyACM0
The CDC ACM driver allows up to 32 modems. If the device node does not exist,
create one using the following command:
mknod /dev/ttyACM0 c 166 0
Additional device nodes can be created for additional modems as follows:
mknod /dev/ttyACM1 c 166 1
mknod /dev/ttyACM2 c 166 2
mknod /dev/ttyACM3 c 166 3
4. Access the modem.
Use a terminal emulator program (for example: minicom) to access the modem using
the device node created above. For example, setup the serial port for minicom to
use the device node /dev/ttyACM0.
5. Internet dialers.
Applications such as WvDial and KPPP may require access to the modem via the
/dev/modem device node.
You can set up a symbolic link from /dev/modem to the ACM modem device by using
the following command:
ln -s /dev/ttyACM0 /dev/modem
--------------------- cut here --------------------------
please let me know what you think
Ah, I see. Can you show the relevant dmesg, or /var/log/messages, output where the device is assigned? Or are you using mknod as in part 3 or the USR provided instructions?
Have you tried to use minicom with either modem?
IIRC, you would start by running 'minicom -s', goto serial port setup, and assign the serial device as the correct device node (/dev/ttyACM0), then choose exit, when connected to the modem type
'AT', and if you get an OK back then you've probably got a working modem. CTRL-A X to exit, I believe. This link might be helpful:
http://tldp.org/HOWTO/html_single/Modem-HOWTO/#minicom_test
Have you tried to use minicom with either modem?
IIRC, you would start by running 'minicom -s', goto serial port setup, and assign the serial device as the correct device node (/dev/ttyACM0), then choose exit, when connected to the modem type
'AT', and if you get an OK back then you've probably got a working modem. CTRL-A X to exit, I believe. This link might be helpful:
http://tldp.org/HOWTO/html_single/Modem-HOWTO/#minicom_test
ASKER
Ok I did what you suggested on /dev/ttyACM0 and it seems to work , look :
Welcome to minicom 2.1
OPTIONS: History Buffer, F-key Macros, Search History Buffer, I18n
Compiled on Jul 26 2006, 06:38:12.
Press CTRL-A Z for help on special keys
AT S7=45 S0=0 L1 V1 X4 &c1 E1 Q0
OK
at
OK
--------------- cut here -----------------
So is there something wrong with the initializing string from Hylafax to the modem ?
Welcome to minicom 2.1
OPTIONS: History Buffer, F-key Macros, Search History Buffer, I18n
Compiled on Jul 26 2006, 06:38:12.
Press CTRL-A Z for help on special keys
AT S7=45 S0=0 L1 V1 X4 &c1 E1 Q0
OK
at
OK
--------------- cut here -----------------
So is there something wrong with the initializing string from Hylafax to the modem ?
ASKER
I even tried calling my cell phone using atdt 91714###### and I got call ;)
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
ati7
Configuration Profile...
Product Type US/Canada USB
Product ID: USR5637
Options V32bis,V.80,V.34+,V.90,V.9
Error Correction MNP,V.42
Data Compression MNP5,V.42bis,V.44
Fax Options Class 1
Line Options Caller ID
Flash Date 01/30/2008
Flash Rev 1.1.0
OK
here are all the FAX commands that this modem supports,
http://www.usr.com/support/5637/5637-ug/ref_fax.html
Configuration Profile...
Product Type US/Canada USB
Product ID: USR5637
Options V32bis,V.80,V.34+,V.90,V.9
Error Correction MNP,V.42
Data Compression MNP5,V.42bis,V.44
Fax Options Class 1
Line Options Caller ID
Flash Date 01/30/2008
Flash Rev 1.1.0
OK
here are all the FAX commands that this modem supports,
http://www.usr.com/support/5637/5637-ug/ref_fax.html
ASKER
I noticed that minicom was using "FLOWCONTROL" HARDWARE, and Class 1 faxmodems are software by hylafax, so I changed flow control and shaaazaaammm. Thanks for your help