Path: utzoo!attcan!uunet!wuarchive!decwrl!hayes.fai.alaska.edu!accuvax.nwu.edu!nucsrl!telecom-request From: john@bovine.ati.com (John Higdon) Newsgroups: comp.dcom.telecom Subject: Re: Help with Rotored Lines/ Rack Mounted Modems Message-ID: <9928@accuvax.nwu.edu> Date: 19 Jul 90 08:41:22 GMT Sender: news@accuvax.nwu.edu Reply-To: John Higdon Organization: Green Hills and Cows Lines: 29 Approved: Telecom@eecs.nwu.edu X-Submissions-To: telecom@eecs.nwu.edu X-Administrivia-To: telecom-request@eecs.nwu.edu X-Telecom-Digest: Volume 10, Issue 499, Message 10 of 14 Julian Macassey writes: > Anyhow a good administarator of telco gear should check all trunks and > associated equipment on a regular basis. This is a task an operator > can do first thing in the morning. It is also handy to check 800 > numbers on thge local loops as well, they do die sometimes. I'll second that. Even here at home, where I have five modems working various trunks, in and out through the PBX, a weekly check is performed. From a phone, I dial the extension number of each modem and check for answer, and then using one of the electronic phones, punch up each CO line that is involved with modem use and check for dial tone. This may seem silly, but this routine check solved a problem that had gone unnoticed. One of my uucp neighbors calls on my 1200 bps modem at night because they run out of Telebits due to heavy traffic. As a courtesy, they don't tie up Telebits with a "slow" call. Somehow, I had kicked the modular cord out of the modem, and it went out of service. All week, I noticed that my mailing list subscriptions were coming in late but passed it off as just "net aberations". When I did my weekly check, the 1200 bps modem failed to respond and the problem was readily corrected. Suddenly, my Telecom Digests started arriving on time once again. John Higdon | P. O. Box 7648 | +1 408 723 1395 john@bovine.ati.com | San Jose, CA 95150 | M o o !