I am interested in installing a hunter on three telephone lines that are
attached to modems that are receiving calls. The phone company tells me
that the lines are "auxiliary" lines and that one cannot put a hunter
on these lines. They claim that a "trunk" line is needed if one wants
to use a hunter.
What is the difference between an auxiliary line and a trunk line?
Are the phone company claims accurate?
Could someone supply a short tutorial?
Thanks.
------------------------------
From: Gary Wells <gary%percival%reed%tektronix.tek.com@RELAY.CS.NET>
Subject: Re: Submission for mod.telecom
Date: 20 Mar 87 01:32:55 GMT
Reply-To: Gary Wells <reed!percival!gary%tektronix.tek.com@RELAY.CS.NET>
There are several methods used by the telco's for line testing. The simplest
is that all cables have a known (very precisely) resistance and capacitance per
foot. If a short is applied at the end of a cable (or a known resistance, etc),
then a calibrated ohmmeter can tell you how far away the short is. If you are
looking at a clean open, you can apply the same principle with a capacitance
meter (though, in practice, it is not as accurate). By knowing WHAT is hanging on the end of your cable, you can quickly tell the status of the pair AND the
station. This is why the telco's fought so hard about registration. They
really didn't care about the equipment, they just need to know what it "looks"
like, for trouble isolation purposes.
------------------------------
Date: Fri, 20 Mar 87 01:46:59 EST
From: kitty!larry@seismo.CSS.GOV
Subject: Submission for mod.telecom
Subject: Re: color code for wire?
In a recent reply to my original article, rdsnyder@MIT-CCC writes:
> > DESIGNATION TIP RING NOTES
> > green wire of green/red pair X
> > red wire of green/red pair X
> > black wire of black/yellow pair X #1
> > yellow wire of black/yellow pair X #1
> >
> > NOTE 1: When used as pair for second telephone line in 4-wire cable
>
> The yellow/black pair above is reversed.
> Yellow is TIP of the second pair in quad (4 cond. Gr/Rd/Yl/Bk cable) and
> black is RING of the second pair.
Sorry, but you are incorrect. Black is always TIP and yellow is
always RING. This true not only for inside station wiring, but for outside
direct burial two-pair "B" Service Wire. I refer to AT&T System Practices
Sections 461-610-100 and 460-300-143 as examples in case anyone doubts
my statement.
You may be confused by looking at the end of a modular plug and
thinking that TIP is one side of center, and RING is the other; the pin
locations on modular connectors are transposed every other pair (up to
the full 4-pairs for an RJ-45).
> The yellow/black pair is also used in key systems as the A/A1 pair. The
> station equipment shorts A & A1 together while off-hook.
In this application, the A-lead is the actual control line, and
the A1-lead is ground. The A-lead is always the "tip" conductor and the
A1-lead is always the "ring" conductor, when the two are in the same pair.
> White, red, black, yellow and violet are tip, and blue, orange, green,
> brown, and slate are ring.
Except, of course, when white/red, white/black, and yellow/red
is used for distributing frame jumper pairs... :-)
<> Larry Lippman @ Recognition Research Corp., Clarence, New York
Is there any way to set up an IBM System 36 so it can
call other systems?
In particular, I know someone with a 36, who wants to communicate
by modem to a VAX/VMS system. I heard that the 36
has only synchronous communication, no asynch.
What I would really like would be something that lets
him emulate a VT100 with his 36 terminals.
Failing that, is there an easy way to connect an IBM PC or compatible
to a 36? Thenit could be used to capture data from the VAX
and upload it to the 36.
Thanks,
Mike Ciaraldi
ARPA: ciaraldi@cs.rochester.edu
uucp: seismo!rochester!ciaraldi
------------------------------
From: SPGDCM%UCBCMSA.Berkeley.EDU@berkeley.edu
Date: Tue, 14 Apr 87 13:19:34 PDT
Subject: telephone credit cards
MSG:FROM: SPGDCM --UCBCMSA TO: NETWORK --NETWORK 04/14/87 13:19:33
To: NETWORK --NETWORK Network Address
From: Doug Mosher <SPGDCM at UCBCMSA>
Title: MVS/Tandem Systems Manager (415)642-5823
Office: Evans 257, Univ. of California, Berkeley, CA 94720
Subject: telephone credit cards
To: telecom@xx.lcs.mit.edu
Does anyone know about the law and policy regarding charge cards following the
divestment? I am puzzled by the following practice:
Pacific bell sent me a card with the number consisting of my telephone number
and a secret 4-digit code not on the card. ATT sent me a card with the same
whole number INCLUDING the same 4-digit verifier embossed on the card.
Both cards have magnetic strips. (I may have it reversed about which one
was secret, which clear-text.)
In any case, two facts appear: apparently there is still a "deal" between
them about long-distance; I suppose in effect that when you charge, you
needn't know whether the call is intra- or inter-lata, and the billing all
gets done by Pac bell anyway. But it seems odd to have two cards from
two different companies, that look different, that perform an identical
practical and business function.
Moreover it is interesting to see the choice of styles, whether you
choose the secret or clear-text code to carry around.
Thanks, Doug
; telephone credit cards
------------------------------
Date: 14-Apr-1987 1940
From: covert%covert.DEC@decwrl.DEC.COM (John R. Covert)
Subject: Radio Station Call Letters, International Allocations
FR: Greg Monti, National Public Radio, Washington, DC
RE: SUBMISSION FOR TELECOM DIGEST
In answer to Kevin. J Burnett's request...
RADIO STATION CALL LETTERS, INTERNATIONAL ALLOCATIONS
Source: 1983 Broadcasting Yearbook, used without permission
Afghanistan YA, T6
Albania ZA
Algeria 7R, 7T-7Y
Andorra C3
Antigua V2
Argentina AY, AZ, LO-LW, L2-L9
Australia AX, VH-VN, VZ
Austria OE
Bahamas C6
Bahrain A9
Bangladesh S2, S3
Barbados 8P
Belgium ON-OT
Benin TY
Bhutan A5
Bolivia CP
Boputhatswana H5
Botswana 8O, A2
Brazil PP-PY, ZV-ZZ
Bulgaria LZ
Burma XY, XZ
Burundi 9U
Cambodia XU
Cameroon TJ
Canada CF-CK, CY, CZ, VA-VG, VO, VX, VY, XJ-XO
Cape Verde D4
Central African Republic TL
Chad TT
Chile CA-CE, XQ, XR, 3G
China B, XS, 3H-3U
Colombia HJ, HK, 5J, 5K
Comoros D6
Congo TN (hmm, thought this was Zaire now)
Costa Rica TE, TI
Cuba CL, CM, CO, T4
Cyprus 5B, C4, H2, P3
Czechoslovakia OK-OM
Denmark OU-OZ, XP, 5P, 5Q
Djibouti J2
Dominica J7
Dominican Republic HI
Ecuador HC, HD
Egypt SSA-SSM, SU, 6A, 6B
El Salvador HU, YS
Equatorial Guinea 3C
Ethiopia ET, 9E, 9F
Fiji 3DN-3DZ
Finland OF-OJ
France & territories F, HW-HY, TH, TK, TM, TO-TQ, TV-TX
Gabon TR
Gambia C5
Germany West DA-DT
Germany East Y2-Y9
Ghana 9G
Greece SV-SZ, J4
Grenada J3
Guatemala TD, TG
Guinea 3X
Guinea Bissau J5
Guyana 8R
Haiti HH, 4V
Honduras HQ, HR
Hungary HA, HG
Iceland TF
India AT-AW, VT-VW, 8T-8Y
Indonesia JZ, PK-PO, YB-YH, 7A-7I, 8A-8I
West Irian JZ
International Civil Aviation Organization 4Y
Iran EP, EQ, 9B-9D
Iraq HN, YI
Ireland EI, EJ
Israel 4X, 4Z
Italy I
Ivory Coast TU
Jamaica 6Y
Japan JA-JS, 7J-7N, 8J-8N
Jordan JY
Kampuchea XU
Kenya 5Y, 5Z
Kiribati T3
Korea North P5-P9
Korea South HL, HM, 6K-6N, D7-D9
Kuwait 9K
Laos XW
Lebanon OD
Lesotho 7P
Liberia EL, 5L, 5M, 6Z, A8, D5
Libya 5A
Lithuania LY
Luxembourg LX
Madagascar 5R, 5S, 6X
Malawi 7Q
Malaysia 9M, 9W
Maldive Islands 8Q
Mali TZ
Maliwi 7Q
Malta 9H
Mauritania 5T
Mauritius 3B
Mexico XA-XI, 4A-4C, 6D-6J
Monaco 3A
Mongolia JT-JV
Morocco CN, 5C-5G
Mozambique C8, C9
Nauru C2
Nepal 9N
Netherlands PU-PI
Netherlands West Indies PJ, P4
New Hebrides YJ
New Zealand ZK-ZM
Nicaragua HT, YN, H6, H7
Niger 5U
Nigeria 5N, 5O
Norway JW, JX, LA-LN, 3Y
Oman A4
Pakistan AP-AS, 6P-6S
Panama HO, HP, 3E, H3, H8-H9
Papua New Guinea P2
Paraguay ZP
Peru OA-OC, 4T
Phillipines DU-DZ, 4D-4I
Poland HF, SN-SR, 3Z
Portugal CQ-CU
Portuguese Overseas Provinces XX
Qatar A7
Romania YO-YR
Rwanda 9X
Saint Lucia J6
Saint Vincent J8
San Marino 9A
Sao Tome e Prinicpe S9
Saudi Arabia HZ, 7Z, 8Z
Senegal 6V, 6W
Service abbreviations (not used for call signs) Q
Seychelles S7
Sierra Leone 9L
Singapore 9V, S6
Solomon Island H4
Somali Republic 6O, T5
South Africa ZR-ZU
Spain AM-AO, EA-EH
Sri Lanka 4P-4S
Sudan SSN-STZ, 6T, 6U
Surinam PZ
Swaziland 3DA-3DM
Sweden SA-SM, 7S, 8S
Switzerland HB, HE
Syria YK, 6C
Tanzania 5H, 5I
Thailand HS
Togo 5V
Tonga A3
Transkei S8
Trinidad & Tobago 9Y, 9Z
Tunisia TS, 3V
Turkey TA-TC, YM
Tuvalu T2
Uganda 5X
United Arab Emirates A6
United Kingdom G, M, VP-VS, ZB-ZJ, ZN, ZO, ZQ, 2
United Nations 4U
United States AA-AL, K, N, W
Upper Volta XT
Uruguay CV-CX
Union of Soviet Socialist Republics EK, EM-EO, ER, ES, EU-EW, EX-EZ, LY,
R, U, YL, 4J-4L
Belorussia EU-EW
Estonia ES
Latvia YL
Lithuania LY
Ukraine UR-UT
Vatican State HV
Venezuela YV-YY, 4M
Vietnam XV, 3W
Western Samoa 5W
World Meterological Organization C7
Yemen Arab Republic 4W, 7O
Yemen PDR 7O
Yugoslavia YT, YU, YZ, 4N, 4O
Zaire 9O-9T
Zambia 9I, 9J
Zimbabwe Z2
-end-
------------------------------
From: rochester!ur-laser!daemon@seismo.CSS.GOV
Date: 14 Apr 87 22:24:58 GMT
Subject: Submission for comp-dcom-telecom
Path: ur-laser!rochester!ciaraldi
From: ciaraldi@rochester.ARPA (Mike Ciaraldi)
Newsgroups: comp.sys.misc,comp.dcom.telecom
Subject: IBM System 36 Telecom Info Wanted
Message-ID: <26989@rochester.ARPA>
Date: 14 Apr 87 17:42:55 GMT
Reply-To: ciaraldi@rochester.UUCP (Mike Ciaraldi)
Distribution: world
Organization: U of Rochester, CS Dept, Rochester, NY
Lines: 19
Is there any way to set up an IBM System 36 so it can
call other systems?
In particular, I know someone with a 36, who wants to communicate
by modem to a VAX/VMS system. I heard that the 36
has only synchronous communication, no asynch.
What I would really like would be something that lets
him emulate a VT100 with his 36 terminals.
Failing that, is there an easy way to connect an IBM PC or compatible
to a 36? Thenit could be used to capture data from the VAX
and upload it to the 36.
Thanks,
Mike Ciaraldi
ARPA: ciaraldi@cs.rochester.edu
uucp: seismo!rochester!ciaraldi
------------------------------
From: SPGDCM%UCBCMSA.Berkeley.EDU@BERKELEY.EDU
Date: Tue, 14 Apr 87 17:54:54 PDT
Subject: handling telephone repair people
MSG:FROM: SPGDCM --UCBCMSA TO: NETWORK --NETWORK 04/14/87 17:54:53
To: NETWORK --NETWORK Network Address
From: Doug Mosher <SPGDCM at UCBCMSA>
Title: MVS/Tandem Systems Manager (415)642-5823
Office: Evans 257, Univ. of California, Berkeley, CA 94720
Subject: handling telephone repair people
To: telecom@xx.lcs.mit.edu
The problem was mentioned where one waits unnecessarily at home for
a tel repair person, when the problem is surely central office. I
tend to adopt the following strategy now:
I disconnect my house wiring and make sure the problem is at the telco
end. Then I call for the repair. When they say "will you be home on
day x?" I say "suuuurrrree". Then I don't be home. They fix the central
office problem and never come out.
I don't know whether all offices think the way ours does but they should.
It is expensive to do a customer call. Why not run the office checks first.
Since that catches the problem there is no reason for the expensive
customer visit.
Now we have an ESS. Some offices might I suppose have an opposite economic
rule; for them it may be more expensive to do the office check.
Note that, though there could be a charge if customer equipt is at fault, there
is not currently a charge for "customer not home when visited".
I generally think that simple lying is bad karma, but in the specific case
where I know that it's telco equipment, and the secretary I call can't
operate on such info and is instructed to arrange a time for the customer
to be home, lying seems the most effective path of action.
Thanks, Doug
handling telephone repair people
------------------------------
From: ketri!kslim@seismo.CSS.GOV (Sik Lim)
Subject: Transmission Product
Date: 15 Apr 87 00:38:10 GMT
I am working in the transmission part.
So please send me information (i.e. product companies, Tel NO., FAX NO. etc ...) about products which convert 1 Mbps serial input data into T-1 carrier (1.544)
speed as soon as possible.
Thank you.
------------------------
Donghee Han
Switching S/W Dept.
ETRI, KOREA.
{...!seismo}!kaist!ketri!tops!kslim
------------------------------
Date: Mon, 13 Apr 87 17:06:27 edt
From: ms6b#@andrew.cmu.edu (Marvin Sirbu)
Subject: Calling number delivery
For those who want more information about how CLASS systems deliver the
caller's number to a handset in a non-ISDN environment, consult the
following:
BellCore Technical Advisory TA-TSY-000031, November 1984
"Calling Number Delivery"
and
TA-TSY-000030, November 1984
"SPCS/Customer Premises Equipment Data Interface"
Available from:
Manager-Information Release
Bell Communications Research, Inc.
435 South Street Room 2J-272
Morristown, NJ 07960-1961
(201) 829-4149
Some quotes:
"The Calling Number Delivery service allows the called customer premises
equipment (CPE) to receive the Directory Number (DN) of the calling party
during the ringing cycle....Then, depending on the options offered by the
CPE, the DN is displayed, and or printed out.
"...Calling Number Delivery service allows customers with Call Waiting
Service to possibly receive the calling DN two times in the call
sequence--during the ringing cycle, as above, and also during the talking
state of the call. For the latter case, the DN transmitted is the DN of the
party calling the customer while the customer is busy on another call.
"Finally Calling Number Delivery service allows the called CPE to receive a
four digit or longer Personal Identification Number (PIN) instead of the
calling DN. The PIN would be dialed by the calling party as part of the
calling sequence. Receiving a PIN would indicate to the called party that
the call is from someone that the called party probably wants to talk to,
even though the call might be from a line having a DN that would not have
been recognized if displayed to the called party (e.g. a coin line)."
"For calling parties concerned about the privacy of their DN's the capability
is provided to allow callers to prevent transmission of their DN's to the
called party's CPE, either for all calls or on a per call basis."
The details of the data communication physical layer is not spelled out in
TA-TSY-000030--in this report BellCore seems to be soliciting ideas from
switch vendors.
The link layer protocol specified consists of checksummed packets of asynch
characters with a simple ACK/NAK stop and wait ARQ. Information can be coded
as ASCII or BCD (specified in packet header).
------------------------------
End of TELECOM Digest
*********************
-------
18-Apr-87 23:42:54-EDT,15769;000000000000
Mail-From: JSOL created at 18-Apr-87 23:29:56
Date: 18 Apr 87 23:29-EDT
From: The Moderator (JSol) <Telecom-REQUEST@XX.LCS.MIT.EDU>
Subject: TELECOM Digest V6 #33
To: Telecom@XX.LCS.MIT.EDU
Reply-To: Telecom@XX.LCS.MIT.EDU
TELECOM Digest Saturday, April 18, 1987 11:29PM
Volume 6, Issue 33
Today's Topics:
KYW
Submission for comp-dcom-telecom
Submission for mod-telecom
conference calls
Re: Universal telephone network plug??
Submission for comp-dcom-telecom
Re: Submission for mod.telecom (Modems and data jacks)
<> FAX: 716/741-9635 {G1,G2,G3 modes} "Have you hugged your cat today?"
------------------------------
Date: Sun 19 Apr 87 13:16:08-CDT
From: Werner Uhrig <CMP.WERNER@R20.UTEXAS.EDU>
Subject: [news from the SW: additional $3 service fee considered ]
[ from the Austin American Statesman, April 12, 87 ]
PHONE UTILITIES CONSIDERING $3 SERVICE FEE
DALLAS (AP) - More than a dozen Texas telephone utilitties are considering adding a $3 cahrge for basic service to monthly bills, a move that would transfer costs now paid by long-distance companies to local consumers.
The additional charge, which must be approved by the PUC would cost customers $820 million over five years, the Dallas Times Herald reported Saturday.
Jon Loehman, vice president for rates and revenues for Southwestern Bell Telephone Co., said the suggested charge has not been formally approved by the utilities. If the proposal was approved by the companies, it would go before the PUC.
The utilities' proposal is to gradually use revenue from the $3 fee to replace some of the multimillion-dollar charges long-distance companies must pay local telephone companies for access to their lines.
"It sounds to me like another plan to put money in the pockets of phone companies that is going to hurt some consumers and small businesses," said Sen. Chet Edwards, D-Duncanville.
------------------------------
Date: Sun 19 Apr 87 13:27:59-CDT
From: Werner Uhrig <CMP.WERNER@R20.UTEXAS.EDU>
Subject: [news from the SW: "marketing-test" ends ]
[ from the Daily Texan, April 14, 1987 ]
BELL ENDS AREA MARKETING PROGRAM (by Keefe Borden, Daily Texan Staff)
Southwestern Bell Telephone ended a two-year marketing program Sunday designed
to evaluate the marketability of several telephone features.
Jim Goodwin, public relations manager for SWB, said Monday "customer response
has been good" to the program, entitled "Custom Calling Services Plus."
Although Bell received a few complaints, "there was no strong customer
reaction" to the decision to end the program, Goodwin said.
The services included automatic re-call, distinctive ringing, selective call
rejection, selective call forwarding and customer-originated trace, Goodwin
said.
SWB officials chose the Austin area for the market-testing program the local
company has the type of equipment needed for the test, Goodwin said.
The test began in January 1985 and was planned for two years. The program was
extended into April to evaluate the effictiveness of an advertising campaign
started in fall 1986, Goodwin said.
Generally, telephone numbers beginning with four or eight, about 200,000 of the
370,000 lines in the Austin area, had access to the services. About 30,000
customers used at least one of the services each month, Goodwin said.
He said SWB will not reintroduce the services in the Austin area in the near
future.
Selective call rejection allowed customers to avoid unwanted phone calls and
cost 25 cents for each use.
Customer-originated trace recorded the number of the caller, the date and the
time of a call. Customers had to contact Bell officials to have the
information released to police. The cost of tracing a call was $5.
The distinctive ringing service, which cost 25 cents per use, allowed customers
to assign identifiable rings for up to three numbers.
Selective call-forwarding allowed customer to forward calls from a maximum of
three different numbers to a second number. Other calls would not be
forwarded. That service cost 10 cents for each use.
[ instead of passing on the advantages that new technology brings to the
consumers, they want to milk the customer all they can. As long as
local service is left as a monopoly, the Baby-Bells will continue
in the tradition of Mama, it seems. Would anyone care to discuss
the possibilities and problems of demonopolizing local service?
I certainly think it's needed and possible.
Please don't misunderstand - I will praise the achievements and benefits
of the US-phone system anyday. my metha is "take the best and
improve on it; ignore the mediocre and eliminate the bad".
Unfortunately, as most of us seem to agree, the breakup was done
in a manner which cannot be considered as an improvement by anyone
but the consumer. ---Werner ]
------------------------------
From: deej@ius2.cs.cmu.edu (David Lewis)
Subject: Re: standards activities
Date: 19 Apr 87 23:56:20 GMT
> In past times, MA bell was a focal point for a lot of telephone activity, but
>even then there were other companies. Now it's the known mess. How in the
>past, and how now, does anyone coordinate? Such matters as protocols,
>assignment of area codes, plans for new service offerings, etc. Are there
>agencies such as ANSI involved? Do they all meet with some sort of
>trust-busting exemption? Are we worse off after the bustup in terms of
>coordinated development? Do companies copy each other to some extent to
>coordinate service offerings?
>
> An example of an issue would be this: "call-waiting" has been out long
>enough
>now for "the public" to begin to have some understanding of what it is an
>what those funny beeps mean etc. This was an advantage of a new concep
>disseminating itself into the populace over time. (But, answering machines are
>also now widely understood even though they required no particular standards
>activity.)
>
>I wonder about the developments such as passing the caller's number, call
>screening, etc. It would seem advantageous to have some aspects of the form of
>this service comprehensible to "the populace", and more specifically for
>instrument makers to know what to look for on the line no matter where the
>call originated.
I'm sure there are Bellcore people out there rushing to answer this, but...
Much of this is done by Bell Communications Research (Bellcore), which is an
offshoot of Bell Labs (now completely independent of AT&T) owned by the
Regional Bell Operating Companies. Bellcore does a lot of standards setting
and new services planning.
I know a little about it; I'm starting in their Network Services Planning