Vgetty can't detect RING, but it's there

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

I just upgraded from mgetty-1.1.9 to 1.1.16 on FreeBSD 2.2.2 (I have the 
freebsd.org official patched build).

Now, when it rings, I get: [0a] [00] [00] [00] [00] [00]...  in the log file 
and then it aborts due to "Junk on the Line".

When I switch back to my 1.1.9 build, it's just fine;  it sees "RING_" "RING_" 
"RING_".

When I switch the modem over to a terminal port and call in to it, I see the 
"RING" "RING" "RING" on the terminal quite nicely.

What's happening?

I have a Cardinal 28.8 Faxmodem with VoiceMail (MVP288XV2) (Rockwell).  I had 
to add an entry to the modem_database list in libvoice/detect.c.

I'm using my old config files that I made with version 1.1.9;  is that a 
problem?

Regards,

John


Log File Excerpt:
=================================================
07/17 19:06:07 aa1  waiting...
07/17 19:06:39 aa1    select returned 1
07/17 19:06:39 aa1   checking lockfiles, locking the line
07/17 19:06:39 aa1   makelock(cuaa1) called
07/17 19:06:39 aa1   do_makelock: lock='/var/spool/lock/LCK..cuaa1'
07/17 19:06:39 aa1   lock made
07/17 19:06:39 aa1    vgetty: number of rings (4) was set directly
07/17 19:06:39 aa1    vgetty: decremented number of rings (4) by 0
07/17 19:06:39 aa1  wfr: waiting for ``RING''
07/17 19:06:39 aa1   got: [0a][00][00][00][00][00][00][00][00]
07/17 19:06:49 aa1  mdm_read_byte: read returned -1: Interrupted system call
07/17 19:06:49 aa1  wfr: timeout waiting for RING
07/17 19:06:49 aa1   wfr: rc=-1, drn=0
07/17 19:06:49 aa1  huh? Junk on the line?
07/17 19:06:49 aa1   removing lock file
--
07/17 19:06:49 aa1  vgetty: experimental test release 0.8.1 / 25Mar98
07/17 19:06:49 aa1  mgetty: experimental test release 1.1.16-Jul05
07/17 19:06:49 aa1  reading generic configuration from config file 
/usr/local/etc/mgetty+sendfax/voice.conf
=================================================


--
John R. Haggis     (haggis@unilinear.com)