Perl program for voice calls does not work... (fwd)

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

Hi,

On Fri, Jun 25, 1999 at 01:29:10PM +0200, Thorbjoern List wrote:
> > > MGetty/VGetty 1.1.20 with patch from 310599
> > > ZyXEL 2864I firmware 2.99
> >
> > Ok, I have only tested with a ZyXEL 2864I with a much lower firmware
> > version (2.11 I think). If you have the time, can you downgrade ?
> 
> I have now tested this with firmwares 2.99, 2.12, 2.11 and 2.10...
> I have tested these on two ZyXEL 2864Is...

There are at least two things that are really weird here:

> 06/18 02:00:19 yS0  playing voice file /var/spool/voice/welcome.rmd
> 06/18 02:00:19 yS0   vgetty: raw modem data header found
> 06/18 02:00:19 yS0   vgetty: modem type ZyXEL 2864 found
> 06/18 02:00:19 yS0   vgetty: compression method 0x0004, speed 9600, bits 4
> 06/18 02:00:19 yS0    vgetty: queued event RESET_WATCHDOG at position 0006
> 06/18 02:00:19 yS0   voice command: 'AT+VSM=4,9600' -> 'OK'
> 06/18 02:00:19 yS0    vgetty: AT+VSM=4,9600
> 06/18 02:00:19 yS0    vgetty: unqueued event RESET_WATCHDOG at position 0006
> 06/18 02:00:19 yS0    vgetty: voice_handle_event got event RESET_WATCHDOG with data <o>
> 06/18 02:00:19 yS0    ZyXEL 2864: 
> 06/18 02:00:30 yS0  vgetty: timeout while reading character from voice modem
> 06/18 02:00:30 yS0  vgetty: Illegal compression method

There is no "OK" coming from the modem here.  Which smells bad (especially
since it works later on).

Standard case:

> 06/18 02:04:31 yS0    vgetty: AT+VSM=4,9600
> 06/18 02:04:31 yS0    vgetty: unqueued event RESET_WATCHDOG at position 0003
> 06/18 02:04:31 yS0    vgetty: voice_handle_event got event RESET_WATCHDOG with data <d>
> 06/18 02:04:31 yS0    ZyXEL 2864: OK

The AT command in question is ACKed, everything looks good, but later...

> 06/18 02:04:32 yS0    vgetty: AT+VTX
> 06/18 02:04:32 yS0    ZyXEL 2864: CONNECT
> 06/18 02:04:32 yS0    ZyXEL 2864: <DLE> <u>
> 06/18 02:04:32 yS0  vgetty: Buffer underrun

... there's a buffer underrun, so something isn't right either.

What serial port speed do you use? Please make sure you use at least
57600 for 9600/ADPCM-4, better 115200. Have you tried a different serial
port?  Different serial cable?

I don't really have an idea what could be the problem, but I strongly
suspect something in the serial communication.

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