Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

The Setup

  • Ubuntu 12.04 64bit
  • Elsa Microlink 56k modem:

    root@energie1:~$ stty -a -F /dev/ttyACM0
    speed 9600 baud; rows 0; columns 0; line = 0; intr = ^C; quit = ^\; erase = ^?; kill = ^H; eof = ^D; eol = ; eol2 = ; swtch = ; start = ^Q; stop = ^S; susp = ^Z; rprnt = ^R; werase = ^W; lnext = ^V; flush = ^O; min = 127; time = 1; -parenb -parodd cs8 -hupcl -cstopb cread clocal crtscts -ignbrk -brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr -icrnl -ixon -ixoff -iuclc -ixany -imaxbel -iutf8 -opost -olcuc -ocrnl -onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0 bs0 vt0 ff0 -isig -icanon -iexten echo echoe echok echonl -noflsh -xcase -tostop echoprt echoctl echoke

  • Hylafax out of the repos.

The Problem

Hylafax

Hylafax is configured to use faxgetty for receiving faxes, but faxstat is only reporting that it's waiting for the modem to become ready. It was said to me that this setup worked a few month ago but then stopped working.

I was able to collect the following informations in /var/log/syslog by setting ServerTracing: 0xfff within my modem config.

Mar 27 10:50:42 energie1 FaxQueuer[1339]: HylaFAX (tm) Version 6.0.5
Mar 27 10:50:42 energie1 HylaFAX[1342]: Listening to 0.0.0.0:4559
Mar 27 10:50:42 energie1 HylaFAX[1342]: HylaFAX INET Protocol Server: restarted.
Mar 27 10:50:42 energie1 FaxGetty[1350]: Unknown speaker volume "on"; using "quiet"
Mar 27 10:50:42 energie1 FaxGetty[1354]: OPEN /dev/ttyACM0  HylaFAX (tm) Version 6.0.5
Mar 27 10:50:42 energie1 FaxGetty[1354]: Purge stale UUCP lock /var/lock/LCK..ttyACM0
Mar 27 10:50:43 energie1 FaxGetty[1354]: MODEM set DTR OFF
Mar 27 10:50:43 energie1 FaxGetty[1354]: DELAY 75 ms
Mar 27 10:50:43 energie1 FaxGetty[1354]: MODEM set DTR ON
Mar 27 10:50:43 energie1 FaxGetty[1354]: DELAY 2600 ms
Mar 27 10:50:46 energie1 FaxGetty[1354]: MODEM set baud rate: 9600 baud, input flow RTS/CTS, output flow RTS/CTS
Mar 27 10:50:46 energie1 FaxGetty[1354]: DELAY 10 ms
Mar 27 10:50:46 energie1 FaxGetty[1354]: MODEM flush i/o
Mar 27 10:50:46 energie1 FaxGetty[1354]: <-- [4:ATZ\r]
Mar 27 10:50:47 energie1 FaxGetty[1354]: --> [3:ATZ]
Mar 27 10:50:47 energie1 FaxGetty[1354]: --> [2:OK]
Mar 27 10:50:47 energie1 FaxGetty[1354]: DELAY 3000 ms
Mar 27 10:50:50 energie1 FaxGetty[1354]: MODEM flush i/o
Mar 27 10:50:50 energie1 FaxGetty[1354]: <-- [5:ATX3\r]
Mar 27 10:50:50 energie1 FaxGetty[1354]: --> [4:ATX3]
Mar 27 10:50:50 energie1 FaxGetty[1354]: --> [2:OK]
Mar 27 10:50:50 energie1 FaxGetty[1354]: <-- [7:ATS0=0\r]
Mar 27 10:50:50 energie1 FaxGetty[1354]: --> [6:ATS0=0]
Mar 27 10:50:50 energie1 FaxGetty[1354]: --> [2:OK]
Mar 27 10:50:50 energie1 FaxGetty[1354]: <-- [5:ATE0\r]
Mar 27 10:50:50 energie1 FaxGetty[1354]: --> [4:ATE0]
Mar 27 10:50:50 energie1 FaxGetty[1354]: --> [2:OK]
Mar 27 10:50:50 energie1 FaxGetty[1354]: <-- [5:ATV1\r]
Mar 27 10:50:50 energie1 FaxGetty[1354]: --> [2:OK]
Mar 27 10:50:50 energie1 FaxGetty[1354]: <-- [5:ATQ0\r]
Mar 27 10:50:50 energie1 FaxGetty[1354]: --> [2:OK]
Mar 27 10:50:50 energie1 FaxGetty[1354]: <-- [7:ATS8=2\r]
Mar 27 10:50:50 energie1 FaxGetty[1354]: --> [2:OK]
Mar 27 10:50:50 energie1 FaxGetty[1354]: <-- [8:ATS7=60\r]
Mar 27 10:50:51 energie1 FaxGetty[1354]: --> [2:OK]
Mar 27 10:50:51 energie1 FaxGetty[1354]: <-- [6:AT&K3\r]
Mar 27 10:50:51 energie1 FaxGetty[1354]: --> [2:OK]
Mar 27 10:50:51 energie1 FaxGetty[1354]: <-- [6:AT&D2\r]
Mar 27 10:50:51 energie1 FaxGetty[1354]: --> [2:OK]
Mar 27 10:50:51 energie1 FaxGetty[1354]: <-- [6:AT&C1\r]
Mar 27 10:50:51 energie1 FaxGetty[1354]: --> [2:OK]
Mar 27 10:50:51 energie1 FaxGetty[1354]: <-- [12:AT+FCLASS=?\r]
Mar 27 10:50:51 energie1 FaxGetty[1354]: --> [7:0,1,2,8]
Mar 27 10:50:51 energie1 FaxGetty[1354]: --> [2:OK]
Mar 27 10:50:51 energie1 FaxGetty[1354]: MODEM Supports "Data"
Mar 27 10:50:51 energie1 FaxGetty[1354]: MODEM Supports "Class 1"
Mar 27 10:50:51 energie1 FaxGetty[1354]: MODEM Supports "Class 2"
Mar 27 10:50:51 energie1 FaxGetty[1354]: MODEM Supports "Voice"
Mar 27 10:50:51 energie1 FaxGetty[1354]: MODEM set DTR OFF
Mar 27 10:50:51 energie1 FaxGetty[1354]: /dev/ttyACM0: Can not initialize modem.
Mar 27 10:50:51 energie1 FaxGetty[1354]: STATE CHANGE: BASE -> MODEMWAIT (timeout 30)
Mar 27 10:51:22 energie1 FaxGetty[1354]: MODEM set DTR OFF
Mar 27 10:51:22 energie1 FaxGetty[1354]: DELAY 75 ms
Mar 27 10:51:22 energie1 FaxGetty[1354]: MODEM set DTR ON

Connection with cu/screen/...

For testing the modem only it connected with cu -l /dev/ttyACM0. There I was able to establish connection with ATD<num> and so..

UPDATE: After I started hylafax once, the Modem don't echo the commands I typed. If I connect to the modem after I replugged it, everythink works fine within cu. So it seems that hylafax is responsible in some way for the wedged modem.

The Questions

  • Any Idea how Hylafax can be responsible for wedgeding the
  • How I am able to debug the modem or the cdc_acm kernel module?

And of corse :-)

  • What do needs to be done to bring Hylafax to work again?
share|improve this question
    
See link - someone else having problems with cdc_acm on Ubuntu and was able to workaround the problem vy using usbserial instead: ubuntuforums.org/showthread.php?t=2003466 –  symcbean Mar 4 '13 at 15:38
    
Thanks for the Idea, unfortunately the usbserial driver didn't help me out. I was unable to load it but I was able to collect some more data. I updated the question with logging information and behavior within cu –  tvn Mar 27 '13 at 10:20
1  
Your log shows hylafax sending an ATE0 - which disables echo. And ATS0=0 which disables answering. Your real problem though seems to be: /dev/M56kUSB-fax: Can not initialize modem –  symcbean Mar 27 '13 at 10:28
    
Ah ok, but I am unable to activate the echo with ATE1 again. The modem is beeping for a short time but nothing changes. (I changed the modem name now completly in the post by /dev/ttyACM0, i switched recently to an symlink /dev/M56kUSB-fax because I have more than one modem) –  tvn Mar 27 '13 at 10:35
    
The symlink shouldn't be a problem - but are both devices the same hardware (i.e. software modems)? I've only used serial connected real modems (and not recently) but never had problems like this. (yeah, I know, it's a bit of a cop-out to blame the hardware) –  symcbean Mar 27 '13 at 10:38
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.