> On 9 Jun 96 at 10:31, Leo Savage wrote:
>
> > On Sun, 9 Jun 1996, MegaZone wrote:
> >
> > > The PM only sends the string on boot and when manually resetting a port,
> > > not after every call.
> >
> > Oof. It should reset the modem after every call. Lord only knows what
> > crap got sent to the modem in command mode between the time the caller
> > disconnected and the time you noticed CD drop. What if he was reading
> > Carl's message about modem setup strings?
>
> Why not attach to the modem, configure it, save settings to NVRAM (AT&W)
> and program the modem to reset on DTR drop (e.g. ATS13=1 with USR
> Courier). The PM drops DTR to end connections or to reset modems.
> Forget the modem table. Do it the DTR way - and the modems gets
> initialized to your programmed settings after each call. Works like a
> charm...
That works like a charm as long as the modem doesn't forget what it's
doing. Meanwhile, a little paranoia about modems goes a long way. The
old Kitten BBS did an outstanding job of keeping its modems online. At
startup and after every call it would:
Drop DTR, pause, raise DTR, pause
Send control-Q, CR
Send modem init string
The ^Q was because some modems can get locked in command mode when they
get a ^S, and totally freeze until they're told to continue. Note that
this is often true even when the modem is set for hardware flow control,
since command mode is a special case.
Actually, Kitten would reset all unused modems once an hour, just on
general principle. It made sure the modems didn't fall asleep. It worked
well enough that some time back I wrote a cron task for the server that
sends resets to the Portmaster for all unused lines once an hour. I'm
sure this is why we get such good results from El Cheapo modems.
--
("`-/")_.-'"``-._ Leo "doc" Savage
. . `; -._ )-;-,_`)
(v_,)' _ )`-.\ ``-' leo@esva.net
_.- _..-_/ / ((.'
((,.-' ((,/ http://www.esva.net/~leo/