Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!casbah.acns.nwu.edu!accuvax.nwu.edu!nucsrl!telecom-request
From: moocow!drmath@iuvax.cs.indiana.edu (Doctor Math)
Newsgroups: comp.dcom.telecom
Subject: Re: Network Interfaces: What's The Difference?
Message-ID: <16624@accuvax.nwu.edu>
Date: 1 Feb 91 05:13:16 GMT
Sender: news@accuvax.nwu.edu
Organization: Brown Cow Software (a licensed Waffle developer)
Lines: 21
Approved: Telecom@eecs.nwu.edu
X-Submissions-To: telecom@eecs.nwu.edu
X-Administrivia-To: telecom-request@eecs.nwu.edu
X-Telecom-Digest: Volume 11, Issue 86, Message 8 of 11


sethcohn%alchemy.uucp@theory.tn.cornell.edu (seth cohn) writes:

> I recently had a second phone installed for a BBS system.  The
> operator gave me a choice of:

> 1) a testable network interface
> 2) a NONtestable network interface

> What's the difference? (Besides about $5 :) )

The "testable" network interface probably has a modular jack wired
inside of it such that all the wiring in your house (past demarc) can
be unplugged, allowing the customer to plug in an ordinary phone and
see if the inside wiring is at fault before calling repair. A less
likely possibility is that it contains a chip that the telco can "see"
from the CO, also to determine where any problem lies. I say "less
likely" because (at least here) they've stopped using these chips;
apparently they register about a ringer and a half and this was
causing problems (installer told me this as I watched him yank out all
six of the little buggers).