mgetty fails with modem after the first successfully received fax

[Spiro, Cyril]

Hi,

We've used mgetty successfully for years, but it stopped working about 3 weeks ago. We use a Red Hat Linux Server 4 operating system and a Multi-Tech Modem MT5634ZBA. I suspected the modem went bad and so we replaced it. However, we got the same error messages in the mgetty and sendfax logs after replacing the modem, so I suspected that the serial port was bad and purchased an MT5634ZBA-USB modem.

With the new USB modem installed, I rebooted the server and several faxes were sent successfully and then I successfully received a fax. After that it stopped working! When I rebooted again, I got a successful incoming fax and then it stopped working again after the first fax!

I've attached the mgetty log file below which shows the successful fax after the reboot and then the failing connection to the modem. Any ideas?

--
-- System Reboot --

--

07/30 20:41:17 CM0 mgetty: experimental test release 1.1.31-Jul24

07/30 20:41:17 CM0 check for lockfiles

07/30 20:41:17 CM0 locking the line

07/30 20:41:17 CM0 lowering DTR to reset Modem

07/30 20:41:18 CM0 send: AT&FE0V1M0&C1&D2S0=0S37=9[0d]

07/30 20:41:18 CM0 mdm_send: 'ATI'

07/30 20:41:18 CM0 got no modem ID. Hagenuk Speed Dragon?

07/30 20:41:18 CM0 mdm_send: 'ATI0'

07/30 20:41:18 CM0 additional info: 'Agere OCM V.92 MT9234ZBA-USB Data/Fax Modem Version 2.02m'

07/30 20:41:18 CM0 mdm_send: 'AT+FCLASS=2.0' -> OK

07/30 20:41:18 CM0 mdm_send: 'AT+FAA=0;+FCR=1' -> OK

07/30 20:41:18 CM0 mdm_send: 'AT+FBO=1' -> OK

07/30 20:41:18 CM0 mdm_send: 'AT+FNR=1,1,1,0' -> OK

07/30 20:41:19 CM0 mdm_send: 'AT+FLI="8134430608"' -> OK

07/30 20:41:19 CM0 mdm_send: 'AT+FCC=1,5,0,2,0,0,0,0' -> OK

07/30 20:41:19 CM0 waiting...

07/30 20:52:57 CM0 wfr: waiting for ``RING''

07/30 20:52:57 CM0 send: ATA[0d]

07/30 20:52:57 CM0 waiting for ``CONNECT''

07/30 20:53:10 CM0 found action string: ``+FCO_''

07/30 20:53:10 CM0 start fax receiver...

07/30 20:53:10 CM0 fax_wait_for(OK)

07/30 20:53:10 CM0 fax_id: '+FTI:" "'

07/30 20:53:11 CM0 transmission par.: '+FCS:1,5,0,2,0,0,0,0'** found **

07/30 20:53:11 CM0 mdm_send: 'AT+FLO=2' -> OK

07/30 20:53:11 CM0 fax_send: 'AT+FDR'

07/30 20:53:11 CM0 fax_wait_for(CONNECT)** found **

07/30 20:53:16 CM0 fax_get_page_data: receiving /home/dormoisdoc/public_html/pdfs/fax/ff3d99369M0.01...

07/30 20:53:24 CM0 fax_get_page_data: page end, bytes received: 14005

07/30 20:53:24 CM0 fax_wait_for(OK)

07/30 20:53:24 CM0 page status: +FPS:1,2149,0,0,0** found **

07/30 20:53:25 CM0 fax_send: 'AT+FDR'

07/30 20:53:25 CM0 fax_wait_for(CONNECT)

07/30 20:53:29 CM0 connection hangup: '+FHS:0'** found **

07/30 20:53:29 ##### fax dev=ttyACM0, pid=5644, caller='none', name='', id='', +FHNG=000, pages=1/0, time=00:00:32





07/30 20:53:29 CM0 system() failed: No such file or directory ---> This line means nothing, it was successful!

07/30 20:53:30 CM0 mdm_send: 'ATH0' -> OK

--

07/30 20:53:30 CM0 mgetty: experimental test release 1.1.31-Jul24

07/30 20:53:30 CM0 check for lockfiles

07/30 20:53:30 CM0 locking the line

07/30 20:53:31 CM0 lowering DTR to reset Modem

07/30 20:53:32 CM0 send: AT&FE0V1M0&C1&D2S0=0S37=9[0d]

07/30 20:53:32 CM0 mdm_send: 'ATI'

07/30 20:53:42 CM0 Warning: got alarm signal!

07/30 20:53:42 CM0 mdm_read_byte: read returned -1: Interrupted system call

07/30 20:53:42 CM0 mdm_get_line: cannot read byte, return: Interrupted system call

07/30 20:53:42 CM0 mdm_identify: can't get modem ID

07/30 20:53:42 CM0 mdm_send: 'AT+FCLASS=?'

07/30 20:53:52 CM0 Warning: got alarm signal!

07/30 20:53:52 CM0 mdm_read_byte: read returned -1: Interrupted system call

07/30 20:53:52 CM0 mdm_get_line: cannot read byte, return: Interrupted system call

07/30 20:53:52 CM0 available modem classes: <ERROR>

07/30 20:53:52 CM0 mdm_send: 'AT+FCLASS=2'

07/30 20:54:02 CM0 Warning: got alarm signal!

07/30 20:54:02 CM0 mdm_read_byte: read returned -1: Interrupted system call

07/30 20:54:02 CM0 mdm_get_line: cannot read byte, return: Interrupted system call -> ERROR

07/30 20:54:02 CM0 waiting...

07/30 21:54:02 CM0 checking if modem is still alive

07/30 21:54:02 CM0 mdm_send: 'AT'

07/30 21:54:12 CM0 Warning: got alarm signal!

07/30 21:54:12 CM0 mdm_read_byte: read returned -1: Interrupted system call

07/30 21:54:12 CM0 mdm_get_line: cannot read byte, return: Interrupted system call -> ERROR

07/30 21:54:12 CM0 mdm_send: 'AT'

07/30 21:54:22 CM0 Warning: got alarm signal!

07/30 21:54:22 CM0 mdm_read_byte: read returned -1: Interrupted system call

07/30 21:54:22 CM0 mdm_get_line: cannot read byte, return: Interrupted system call -> ERROR

07/30 21:54:22 CM0 modem on dev=ttyACM0 doesn't react!: Interrupted system call

--

Cyril

[Gert Doering]

Hi,

Post by Spiro, Cyril
I've attached the mgetty log file below which shows the successful fax after the reboot and then the failing connection to the modem. Any ideas?

This very much looks like the modem gets stuck after a fax reception.

Does it come back if you reset just the modem (unplug/replug USB)? In
that case, I'd blaim the modem, and complain to the vendor... Multitech
used to listen, no idea how things are today.

For "serious" faxing, I'm using Eicon/Diehl DIVA BRI active ISDN cards
now (PCI/PCIe). Expensive as hell, but the best fax implementation I've
seen so far - V.34 fax, ECM, transparent recoding to twodimensional
compression, etc.

For "just every now and then", I'm still using my old ZyXEL 1496s, hooked
to a PCI 4x serial card...

gert

[Gert Doering]

Hi,

We have resolved the issue thanks to the support of MultiTech. Thank you for pointing me in their direction.
The problem was that the modem's default baud rate was 57600 and we had to change that for both mgetty and sendfax.

Mmmh. Well, the point of the "AT" command sequence is to synchronize
the modem to the speed the host uses, and modems really *should* adapt
to whatever (reasonable) is used talking to them...

But whatever, if it works now, fine.

gert