vgetty beep error

Marc SCHAEFER (schaefer@alphanet.ch)
3 Jun 1999 1911:05:34 +0200


Brian B. <ixnay@wws.net> wrote:
> let go of my phone line I just get this constant beep forcing a reboot.

forcing a reboot ?!  What about a kill of vgetty pid ?

> 06/03 00:54:54 yS2    vgetty: AT#VTS=[933,0,15]
> 06/03 00:54:54 yS2    vgetty: unqueued event RESET_WATCHDOG at position 0011
> 06/03 00:54:54 yS2    vgetty: voice_handle_event got event RESET_WATCHDOG with
> data <
> 06/03 00:54:54 yS2   voice command: '' -> 'OK'
> 06/03 00:54:54 yS2    Rockwell:
> 06/03 00:55:05 yS2  vgetty: timeout while reading character from voice modem

Well, your modem doesn't say OK, it seems, after AT#VTS=[933,0,15]

It just dies with this command, apparently. Maybe a firmware bug, since
it doesn't really revive after:

> 06/03 00:55:05 yS2    vgetty: queued event RESET_WATCHDOG at position 0012
> 06/03 00:55:05 yS2   voice command: 'ATH0' -> 'VCON|OK'
> 06/03 00:55:05 yS2    vgetty: ATH0
> 06/03 00:55:05 yS2    vgetty: unqueued event RESET_WATCHDOG at position 0012
> 06/03 00:55:05 yS2    vgetty: voice_handle_event got event RESET_WATCHDOG with
> data <
> 06/03 00:55:05 yS2    Rockwell:
> 06/03 00:55:16 yS2  vgetty: timeout while reading character from voice modem

It's not an echo problem (the echo comes). It's the command result which
never comes.

Never saw that. Bizarre.

> Sorry I offend anyone for posting such a large mail but everything seemed
> important as far as showing the modem detected and the beep error.

Can you, in the source, comment where the beep is sent and recompile ?
If everything works, except the beep, well, maybe the firmware crashes
on beep :(

That would be to replace &IS_101_beep in voice/libvoice/Rockwell.c
by NULL. Or I hope so :)