Possible bug in IS_101_voice_mode_on.c

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

Hi,

I'm new to vgetty and am trying to to get it to work with an external USR
Sportster 33.6 under RedHat 6.0 using mgetty-1.1.21

At one stage I had it all working then everything went downhill!  One
problem is that sometimes the modem will not answer the phone.  I think I
have narrowed this down to a possible problem in IS_101_voice_mode_on.c, but
since I am not at all familiar with the internals of vgetty I'll happily
stand to be corrected.

The relevant part of the log file shows:

08/08 20:39:02 yS0   vgetty: entering voice mode
08/08 20:39:02 yS0   vgetty: Installing signal handlers
08/08 20:39:02 yS0   voice command: 'AT#CLS?' -> ''
08/08 20:39:02 yS0    vgetty: AT#CLS?
08/08 20:39:02 yS0    US Robotics: RING
08/08 20:39:02 yS0   voice command: '' -> 'OK'
08/08 20:39:02 yS0    US Robotics: 0
08/08 20:39:02 yS0  vgetty: Invalid modem answer
08/08 20:39:02 yS0   voice command: 'AT#VLS=0A' -> 'VCON'
08/08 20:39:02 yS0    vgetty: AT#VLS=0A
08/08 20:39:02 yS0    US Robotics: OK
08/08 20:39:02 yS0    US Robotics: ERROR
08/08 20:39:02 yS0  vgetty: Modem returned ERROR
08/08 20:39:02 yS0    vgetty: queued event RESET_WATCHDOG at position 0001
08/08 20:39:02 yS0   voice command: 'AT#VLS=0' -> 'OK|VCON'
08/08 20:39:03 yS0    vgetty: AT#VLS=0
08/08 20:39:03 yS0    vgetty: unqueued event RESET_WATCHDOG at position 0001
08/08 20:39:03 yS0    vgetty: voice_handle_event got event RESET_WATCHDOG
with data <NUL>
08/08 20:39:03 yS0    US Robotics: ERROR
08/08 20:39:03 yS0  vgetty: Modem returned ERROR
08/08 20:39:03 yS0  vgetty: Could not answer the phone. Strange...

It seems that IS_101_voice_mode_on.c is asking for the current mode the
modem is in:
    voice_command(voice_modem->ask_mode_cmnd, "")
and because the expected answer is "" (strlen(expected_answer)==0)
voice_analyze(...) is never called in voice_command, and so the first thing
back is returned - in this case the RING.

>From then on in everything is out of sync. with the modem and the modem is
never switched into voice mode.

I've seen this happen several times, but it obviously isn't 100%
reproducible.

Is this correct or is something else the problem?

Rob