ZyXEL 1496R + vgetty ring cadence

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

Nichard Rixon <rixon@swbt.net> wrote:
> taking too much time to read the settings, and dosen't send the +VLS
> command until about the time when the next ring occurs.  (This is just an
> observation by watching a tail of the log file.)  The modem never picks

Can you fix that:

06/05 16:44:48 yS1    vgetty: number of rings (3) was set directly

so, waiting for RINGs.

06/05 16:44:48 yS1   got: [0a][0d][0a]RING[0d]
06/05 16:44:48 yS1    CND: RING

one

06/05 16:44:48 yS1   got: [0a][0d][0a]RING[0d]
06/05 16:44:52 yS1    CND: RING

two

06/05 16:44:52 yS1   got: [0a][0d][0a]RING[0d]
06/05 16:44:56 yS1    CND: RING

three.

06/05 16:44:56 yS1  cannot set controlling tty (ioctl): Operation not permitted
06/05 16:44:56 yS1  >>> this might be caused because you have run mgetty/vgetty
06/05 16:44:56 yS1  >>> from the command line.  Don't do that, use /etc/inittab!

Can you check that you run vgetty from inittab ?

06/05 16:44:56 yS1   conf lib: read: 'program vgetty'
06/05 16:44:56 yS1   conf lib: read: 'rings 3'

Well, maybe you could set that to 1. That shouldn't make any difference.


06/05 16:44:56 yS1   voice command: 'AT+FCLASS?' -> ''
06/05 16:44:56 yS1    vgetty: AT+FCLASS?
06/05 16:44:56 yS1    ZyXEL 1496: AT+FCLASS?
06/05 16:45:07 yS1  vgetty: timeout while reading character from voice modem

Well, you problem is not that a ring comes inappropriately, it's either
the inittab problem above, or that simply your modem doesn't answer
commands anymore for some reason.

I do not adhere by your understanding that vgetty is too slow to
go from RING to answer, since last RING (the third) is heard at
16:44:56, and the first command is done at 16:44:56 too.

The modem just doesn't answer the first command. Then we timeout.

Having used a 1496 in voice mode (however 6.19, not 6.13),
I never saw that happening.

Can you upgrade one of the modems just to try (after fixing the
inittab problem above) ?