Vgetty can't detect RING, but it's there
John R. Haggis (haggis@unilinear.com)
Sun, 19 Jul 1998 09:10:04 +0200
In article <m0yxe62-000BeFC@greenie.muc.de>, gert@greenie.muc.de (Gert Doering) wrote:
>Hi,
>
>John R. Haggis wrote:
>> 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".
>
>Interesting. Sounds like a baud rate mismatch problem.
>
>Are you sure that all "speed" settings in mgetty.config and voice.conf are
>identical?
>
>> What's happening?
>
>No idea, but I'd like to see a complete log file with "-x6" set (all the
>stuff between the last two "mgetty version 1.1.16" lines).
>
>gert
Gert,
I changed the speed at the beginning of mgetty.config to 38400 to match the
setting in voice.conf and everything works now. I wonder why it worked with
the wrong speed in 1.1.9? Who knows. But thanks for the tip.
Now, everything looks good; outgoing message plays, and incoming messages
record fine, except that looking at the log file something is trying to use
group "phone". I set the Makefile PHONE_GROUP=uucp. Here is an excerpt from
the log with level = 6. Let me know if you need more.
Oh, I also set the group to uucp in mgetty.config:
port-owner uucp
port-group modem
port-mode 0660
What is trying to use the group "phone"? Do I really have to set up this
group? What might be failing because of this?
Regards and Thanks,
John
Log File Excerpt at the end of recording a message.
==============================================
07/18 23:55:24 aa1 vgetty: <STOP RECORDING>
07/18 23:55:24 aa1 Rockwell: <VOICE DATA 52981 bytes>
07/18 23:55:24 aa1 Rockwell: <DLE> <ETX>
07/18 23:55:24 aa1 voice command: '' -> 'OK|VCON'
07/18 23:55:24 aa1 Rockwell: VCON
07/18 23:55:24 aa1 can't get group 'phone': Undefined error: 0
07/18 23:55:24 aa1 vgetty: queued event RESET_WATCHDOG at position 0011
07/18 23:55:24 aa1 voice command: 'AT#VTS=[933,0,1]' -> ''
07/18 23:55:24 aa1 vgetty: AT#VTS=[933,0,1]
07/18 23:55:24 aa1 vgetty: unqueued event RESET_WATCHDOG at position 0011
07/18 23:55:24 aa1 vgetty: voice_handle_event got event RESET_WATCHDOG with
data <
07/18 23:55:24 aa1 Rockwell: AT#VTS=[933,0,1]
07/18 23:55:24 aa1 voice command: '' -> 'OK'
07/18 23:55:24 aa1 Rockwell: OK
07/18 23:55:24 aa1 vgetty: queued event RESET_WATCHDOG at position 0012
07/18 23:55:24 aa1 voice command: 'ATH0' -> 'VCON|OK'
07/18 23:55:25 aa1 vgetty: ATH0
07/18 23:55:25 aa1 vgetty: unqueued event RESET_WATCHDOG at position 0012
07/18 23:55:25 aa1 vgetty: voice_handle_event got event RESET_WATCHDOG with
data <
07/18 23:55:25 aa1 Rockwell: ATH0
07/18 23:55:25 aa1 Rockwell: OK
07/18 23:55:25 aa1 voice command: 'AT#VLS=0' -> 'OK'
07/18 23:55:25 aa1 vgetty: AT#VLS=0
07/18 23:55:26 aa1 Rockwell: AT#VLS=0
07/18 23:55:26 aa1 Rockwell: ERROR
07/18 23:55:26 aa1 vgetty: Modem returned ERROR
07/18 23:55:26 aa1 vgetty: leaving voice mode
07/18 23:55:26 aa1 voice command: 'AT#CLS=2' -> 'OK'
07/18 23:55:26 aa1 vgetty: AT#CLS=2
07/18 23:55:26 aa1 Rockwell: AT#CLS=2
07/18 23:55:26 aa1 Rockwell: OK
07/18 23:55:26 aa1 vgetty: Restoring signal handlers
07/18 23:55:26 aa1 closing voice modem device
07/18 23:55:26 aa1 removing lock file
07/18 23:55:26 ##### message keep, length=00:00:16, name='', caller=none,
dev=cuaa1, pid=5263
07/18 23:55:26 aa1 vgetty: creating message flag file
/var/spool/voice/.flag
07/18 23:55:26 aa1 executing message program, dev=cuaa1, pid=5263
07/18 23:55:26 aa1 vgetty: Executing shell script /var/spool/voice/message.sh
with shell /bin/sh
07/18 23:55:26 aa1 vgetty: opening pipes
07/18 23:55:26 aa1 vgetty: forking shell
07/18 23:55:26 aa1 vgetty(0): HELLO SHELL
07/18 23:55:28 aa1 vgetty: shell exited normally with status 0x0001
--
--
John R. Haggis (haggis@unilinear.com)