Possible bug in IS_101_voice_mode_on.c

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

Hi,

On Tue, Aug 10, 1999 at 11:06:45PM -0400, Rob Walker wrote:
> 08/10 22:42:33 yS0    serial port: (1.0USR0007\\Modem\Sportster 33600
> FAX/VOICE EXT)FF
> 08/10 22:42:34 yS0    serial port: OK
> 08/10 22:42:34 yS0   voice command: 'ATI' -> ''
> 08/10 22:42:34 yS0    vgetty: ATI
> 08/10 22:42:34 yS0    serial port: 3361
> 08/10 22:42:34 yS0    US Robotics: OK
> 08/10 22:42:34 yS0  US Robotics detected
> 08/10 22:42:34 yS0   vgetty: entering voice mode
> 08/10 22:42:34 yS0   vgetty: Installing signal handlers
> 08/10 22:42:34 yS0    *rnw* IS_101_voice_mode_on: sleeping...
> 08/10 22:42:44 yS0    *rnw* voice_command: AT#CLS?
> 08/10 22:42:44 yS0   voice command: 'AT#CLS?' -> ''
> 08/10 22:42:45 yS0    vgetty: AT#CLS?
> 08/10 22:42:45 yS0    *rnw* voice_read
> 08/10 22:42:45 yS0    US Robotics: RING
> 08/10 22:42:45 yS0    *rnw* mode_save == RING
> 08/10 22:42:45 yS0    *rnw* voice_command("", "OK")
> 08/10 22:42:45 yS0   voice command: '' -> 'OK'
> 08/10 22:42:45 yS0    US Robotics: 0

Interesting indeed.  If you can reproduce it, your modem is weird - if
not, this was just a random coincidence, the phone RINGing just at the
very same time that vgetty was re-initializing the modem.

Up to the ATI -> 3361/OK response, everything is perfectly in sync, and
after AT#CLS? the modem "responds" with RING, which shouldn't happen
unless the phone *really* RINGs.

Unfortunately, it's very hard to guard against spurious RINGs in places
where they are not expected, so failure in those cases *is* to be expected
- but unless you have a very very busy voice line, occurence of this
should be fairly rare.

gert
-- 
USENET is *not* the non-clickable part of WWW!
                                                           //www.muc.de/~gert/
Gert Doering - Munich, Germany                             gert@greenie.muc.de
fax: +49-89-35655025                        gert.doering@physik.tu-muenchen.de