telecom@ucbvax.ARPA (05/15/85)
From: Jon Solomon (the Moderator) <Telecom-Request@BBNCCA>
TELECOM Digest Tue, 14 May 85 16:46:40 EDT Volume 4 : Issue 192
Today's Topics:
Modem Madness
800-xxx-xxxx (except in sssss)
Re: TELECOM Digest V4 #191
more about 700-555-1212
Re: UUUUUUUUUUU~i{gak!
Re: TELECOM Digest V4 #191
Wiring
----------------------------------------------------------------------
Date: Mon, 13 May 85 23:05:17 edt
From: Michael A. Grant <mgrant@gymble>
To: telecom@bbncca
Subject: Modem Madness
Refering to that long string of UUUUUU's, somone said it's a test
pattern. The modems that we connect to are those bell vadic triple's.
Does anyone know how to get them out of the test mode once you've been
inadvertently dumped into it? Or even, how to get into it?
-Mike
p.s. once in it, is the connection lost?
------------------------------
Date: Mon, 13 May 85 16:07:53 est
From: hadron!jsdy@seismo.ARPA (Joseph S. D. Yao)
To: seismo!telecom@Berkeley
Subject: 800-xxx-xxxx (except in sssss)
> Why is it that many of the 800 numbers advertised have an exception for
> a whole state? I assume that it's a regulatory/billing problem.
That state is the state within which the company's offices (at least
those answering the inward WATS line) are located. Each state has its
own local WATS service, so you should always see this exception.
Inward WATS fees within the state are paid to the state telco. After
this, then, there is a set of n (n ~= 4) concentric WATS areas around
the state for AT&T LongLines WATS. The user pays a different fee,
depending on how far out he wants this inward WATS line to be valid.
Also depending on the state, this fee may or may not be more than the
in-state inWATS fee.
Warning: this explanation was good as of the last time I looked into
this, and should still be mostly valid; but that was before the
dismemberment of AT&T.
Joe Yao hadron!jsdy@seismo.{ARPA,UUCP}
------------------------------
Date: Mon 13 May 85 17:28:35-PDT
From: Doug <Faunt%hplabs.csnet@csnet-relay.arpa>
Subject: Re: TELECOM Digest V4 #191
To: telecom@bbncca.ARPA
The "UUUUUUUUUUUU" test pattern from 212 modems does sound like it's
going into remote test mode. I had this problem from one and only one
user here once. The Racal-Vadic modems I was using here apparently go
into self-test based on a short, timed interruption of carrier.
His telephone line caused exactly this to happen. They rewired his
neighborhood shortly thereafter, I re-enabled remote testing on
the lines he used, and never saw the problem again.
-------
------------------------------
From: ima!johnl@bbncca
Date: Tue May 14 10:15:00 1985
Subject: more about 700-555-1212
To: bbncca!telecom
I tried it here in Cambridge, where equal access was recently turned on.
Due to slowness at the telco, my default carrier is still AT&T and, sure
enough, when I dialed it I got a recording thanking me for choosing AT&T.
Then I tried using other carriers' prefixes, e.g. 10222-1-700-555-1212. That
worked also, and I got various recordings identifying the various carriers
I had connected to:
10222 - MCI
10288 - AT&T
10333 - U S Tel
10488 - ITT
10777 - Sprint
10888 - hmmn. see below.
With a 10888 prefix, I got a recording at SBS that said my call coudn't be
completed or wasn't on the network. Guess their equal access department hasn't
gotten around to that yet. (SBS does know who I am and will complete normal
calls, by the way, which they won't if you haven't explicitly signed up.)
John Levine, ima!johnl or Levine@YALE.ARPA
------------------------------
To: telecom@bbncca.ARPA
Subject: Re: UUUUUUUUUUU~i{gak!
Date: 13 May 85 18:52:22 EST (Mon)
From: Christopher A Kent <cak@Purdue.ARPA>
Thanks to everyone that informed me that the UUUUUUU sequence, followed
by echo, indicates that one or both of the modems in my connection is
dropping into (remote) digital loopback. I'll get the test mode stuff
disabled at both ends and hope it goes away.
Cheers,
chris
----------
------------------------------
Date: Tue 14 May 85 11:39:16-PDT
From: Andrew Sweer <SWEER@SUMEX-AIM.ARPA>
Subject: Re: TELECOM Digest V4 #191
To: TELECOM@BBNCCA.ARPA
Regarding the recent notes about receiving multiple UUUUUUs
as a test pattern, can one speculate that the character U was chosen
because its ASCII representation, namely 125 octal or 55 hex, contains
4 sets of alternating zeros and ones? i.e. 01010101.
-------
------------------------------
Date: 14 May 85 16:04:49 EDT
From: *Hobbit* <AWalker@RUTGERS.ARPA>
Subject: Wiring
To: Telecom@RUTGERS.ARPA
It's rather difficult to send out schematic diagrams to a network of people
using regular old ascii terminals, but since wiring inside most fones is
pretty standard, a description should do the trick. This applies to *all*
WE phones and ITT phones that use the standard dial/ringer/network block/
handset configuration. I've rebuilt lots of these suckers, and can
confidently say that they're all the same.
Everything basically talks to the network block. The network block contains
the ringer capacitor, the induction coil that handles the handset, and very
little else save some spare screw terminals. Left to itself, the network
block can function as a standard line load [it looks electrically like a
phone] when a line is connected across RR and C. These are the inputs to
the coil. The ringing capacitor is indeed across A and K as someone mentioned.
In addition, older blocks have a smaller capacitor across F and RR, to
decrease sparking across rotary dial contacts.
Handset:
Green and White: Earpiece leads. These connect to net R and GN respectively.
Black and Red: Mike leads. Connect to net B and R respectively.
Ringer [two-winding]:
Black and Red: To line. Connect to L1 and L2 [or whever your line comes in].
Grey and Grey/red [these may vary; they are the ''other two'' wires, anyway]:
Connect to net A and K. The circuit thus formed runs from one side
of the line to one ringer winding, thru the A-K cap, thru the other
ringer winding, to the other side of the line. This configuration
has infinite DC resistance, but picks up the AC ring voltage.
Ringer [one-winding, rare]: Connect the single winding [two wired] in
series with the A-K capacitor somehow, and this whole thing across
the line as above.
Rotary dial:
Blue and Green: Interruptor. Connect to net F and RR.
White [2]: Earpiece suppress. Connect to net B and GN if desired.
Touch-tone dial:
Green: + Line in. Connect to net F.
Black: + Line out. Connect to net RR.
Org/Blk: - Line in. Connect to net C.
Red/Grn: output common. Connect to net R.
Blue: output. Connect to net B.
*Note: the above 5 connections will give you a ''bare-bones'' dial
configuration without features. Features are mike disconnect, earpiece
suppress, etc which are done simply by routing leads to these through the
extra contacts on the dial instead of directly. If you want the features,
modify the wiring as follows. If your network block doesn't have the S and
T terminals, you have an old one designed for rotary dials, and you'll have to
do kludges.
Earpiece mute:
Move Handset lead at White to net S. Also connect Dial White-Blue to net S.
Connect Dial White to net GN. This routes the earpiece through
the dial switching mechanism which resistifies the circuit on button press.
Mike disable:
Move Handset Red to T. Also connect Dial Red to T. This completely disables
the mike on button press. Make sure Dial Red-Green is connected to R if you
do this mod!
Hookswitch:
You'll find many variants of this in different units; some configurations
switch both sides of the line, some only one, some switch out the ringer
when off-hook [which isn't necessary, really]. The following should work:
Yellow: Connect to net L2. This is where the line enters.
Brown: Connect to net C.
Green: Connect to net L1. This is the other side of the line.
White: Connect to F. This is switched line power to the dial and the rest.
Red: Connect to R. This, with Black, is shorting earpiece mute.
Black: Connect to GN.
Line in:
Green and Red connect to L1 and L2. Try one polarity; if the touchtone dial
doesn't work, then flip them. Rotary dials, of course, don't matter.
If someone sees errors in this, please notify the list with the correction...
_H*
-------
------------------------------
End of TELECOM Digest
******************************