Possible bug: callerid with vgetty

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

Hi,

Shane Wegner wrote:
> I assume this isn't too common because not many people have it but a
> gentlemen posted sometime last week about callerid not working in vgetty
> but works in mgetty.  I am experiencing the same thing over here and I'm
> not sure what could be causing it.  The configs look ok and the only
> change I make to switch from mgetty to vgetty is:
> S3:234:respawn:/usr/local/sbin/mgetty ttyS3
> to
> S3:234:respawn:/usr/local/sbin/vgetty ttyS3
> 
> The above logs are generated with mgetty and vgetty (everything turned
> on).  I looked and all seems well with vgetty except for the absence of
> callerid data.

Please append the log files in a *readable* format (just include it in the
mail, don't use MIME attachments that I have to start guessing what format
it is).

Could be the problem mentioned on this list about two months ago, that
some modems forget their AT#CID=1 setting after a switch to voice mode and
back.  Try using 

  post-init-chat "" AT#CID=1 OK

in mgetty.config.

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