Caller ID Saga: Stopped by a bug.

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

Hi,

On Sun, May 16, 1999 at 10:08:32PM -0700, Daniel Swan wrote:
> The above log statement also tells another tale:  That caller ID isn't working right.  So I went into the log file,  and made a list of ALL AT commands send to the modem .  Using minicom, I manually entered each command, calling each time to see which one was breaking the caller ID.  Finally, after "at#CLS=0", Caller ID stopped working.
> 
> Searching dejanews, I see that others have encountered this as well, but solutions are only hinted at.

Use "post-init-chat" (mgetty.config) to send a "final AT command" after
everything else is done.

[..]
> Rambo could probably do a better job, but this is the best I can come up with.  Has anyone figured out a more elegant solution to this problem? 

Yes, use the methods intended for that:

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

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