vgetty doesn't like Atlas modem (Rockwell chipset)

• Messages sorted by:[ date ][ thread ][ subject ][ author ]

I recently upgraded from a 28.8 modem to an Atlas 56K v.90 modem that I got at Best Buy.  I
remembered hearing about mgetty+sendfax+voice, so I thought I would give it a shot.

Vgetty seems to do OK when the message is terminated with a # key.  There is a major problem when
the caller simply hangs up:  The modem makes a continuous buzzing beep sound and stays off hook
until the computer is reset.

I am using version 1.1.17.  With log level set at 4, I get the following excerpts from
/var/log/vgetty.ttyS1:

09/05 17:57:30 yS1  mdm_send: 'ATI'
09/05 17:57:30 yS1  Generic Rockwell modem (56000)
09/05 17:57:30 yS1  mdm_send: 'ATI3'
09/05 17:57:30 yS1  mdm_send: 'ATI4'
09/05 17:57:30 yS1  additional info: '56kifxspA Int Modem NCI1032A V2.065 03.12.98'
09/05 17:57:30 yS1  modem quirks: 0004
09/05 17:57:30 yS1  mdm_send: 'AT+FCLASS=2' -> OK
09/05 17:57:30 yS1  mdm_send: 'AT+FCLASS=0' -> OK
09/05 17:57:30 yS1  mdm_send: 'AT+FAA=1;+FCR=1' -> OK
09/05 17:57:30 yS1  mdm_send: 'AT+FBOR=0' -> OK
09/05 17:57:30 yS1  mdm_send: 'AT+FLID="402 467 1707"' -> OK
09/05 17:57:30 yS1  mdm_send: 'AT+FDCC=1,5,0,2,0,0,0,0' -> OK
09/05 17:57:30 yS1  detecting voice modem type
09/05 17:57:31 yS1  Rockwell detected
09/05 17:57:32 yS1  initializing ROCKWELL voice modem

I'm running vgetty from the command line in a separate console while setting up.  tail -f
/var/log/vgetty.tty!1 shows me whats going on as it happens.  Here's what happens when the caller
just talks and exits:

09/05 17:59:28 yS1  wfr: waiting for ``RING''
09/05 17:59:28 yS1  wfr: waiting for ``RING''
09/05 17:59:32 yS1  cannot set controlling tty (ioctl): Operation not permitted
09/05 17:59:32 yS1  reading ring_type ring configuration from config file /usr/local/etc
/mgetty+sendfax/voice.conf
09/05 17:59:33 yS1  playing voice file /var/spool/voice/messages/hi.rmd
09/05 17:59:39 yS1  recording voice file /var/spool/voice/incoming/va00580.rmd

I hang up the other phone, and I hear the beeping buzz (it sounds alot like the beep from the
announcement), but this beep continues.  The modem stays off hook.  I kill -9 vgetty in the other
console, come back and see:

09/05 18:00:02 yS1  vgetty: timeout while reading character from voice modem
09/05 18:00:02 yS1  /dev/ttyS1: Beep command failed
09/05 18:00:13 yS1  vgetty: timeout while reading character from voice modem


The modem is still off hook.  The buzzing persists.  setserial /dev/ttyS1 pauses several seconds and
returns a null line.

Am I misconfigured, or does vgetty not like my modem?