gordon@uunet.uu.net> (04/06/90)
>One thought though, if this is for a school project, there's really no >need to attach it to the phone lines. You could attach it to the >phone system in your school -- It may be easier to get permission to >do this. ... This brings up another question: what happens to (a) the FCC type registration requirement and (b) the requirement to notify the phone company about attached equipment when the phone line in question is an extension of a key system/PBX? Presumably you told them about the stuff directly attached (the key system) already. What about new extensions? I'm thinking of something like the KX-T61610 but if the type matters, what about any type? The phone company doesn't seem to care much about what's attached to the line. If you try to follow the directions in the instruction book of your new phone/modem/fax machine/answering machine to tell the phone company the FCC registration number of what you're connecting to the line, the phone company (Southwestern Bell in this case) usually says something like "we don't lease those", "talk to the company you bought it from", and "it's not covered since you don't have Inside Wire Maintenance", indicating they don't have the faintest idea what I'm talking about. This from the same customer service people who told me I'd have to SCRAP every phone I had when I ordered another line, because if more than one line goes to the same residence, only multi-line phones will function. Another one tried to convince me that someone else talking on my line (over dial tone, very intelligible, and not someone in my house) was a problem in my inside wiring, even while she was having trouble hearing me over the other person. (The repairman said there was foreign battery on the line, and called back later saying a problem had been found in the cable a few blocks away. No problem since. I take that to mean one side of my line was connected to one side of someone else's through rainwater and bad insulation.) Gordon L. Burditt sneaky.lonestar.org!gordon
macy@cwjcc.ins.cwru.edu (04/13/90)
In article <6112@accuvax.nwu.edu> you write: X-Telecom-Digest: Volume 10, Issue 235, Message 8 of 11 >This brings up another question: what happens to (a) the FCC type >registration requirement and (b) the requirement to notify the phone >company about attached equipment when the phone line in question is an >extension of a key system/PBX? Presumably you told them about the >stuff directly attached (the key system) already. What about new >extensions? I'm thinking of something like the KX-T61610 but if the >type matters, what about any type? Geez, its been a while since I have read Part 68, but as I remember it ... your extension is behind a "registered protective device" or some such interpretation. The idea was that equipment connected behind a registered product did not itself have to be registered. Now, you still have to comply with all the requirements for the maximum level you can put on the line and such, but that's the general idea. I also know that there were conflicting opinions about this back when Part 68 was new, and all the telco were still kicking and screaming about "damage to the network". (Has anybody noticed any damage to the network since Part 68? You mean all that stuff about couplers back in the late 60's and early 70's might not have been true? And with all the research Bell put into it?) It now seems the only people at the telco who care about FCC registration numbers is COG (Centralized Operations Group), who are the people interconnect co.'s are supposed to order lines through (not the business office). Since there is a blank on the COG form for FCC Registration No., we HAVE to fill it out, or they will not order. Twice the hassle, and we get the orders worked twice as slow, too... Macy M. Hallock, Jr. macy@NCoast.ORG uunet!aablue!fmsystm!macy F M Systems, Inc. {uunet!backbone}!usenet.cwru.edu!ncoast!fmsystm!macy 150 Highland Drive Voice: +1 216 723-3000 Ext 251 Fax: +1 216 723-3223 Medina, Ohio 44256 USA Cleveland:273-3000 Akron:239-4994 (Dial 251 at tone) (Please note that our system name is "fmsystm" with no "e", .NOT. "fmsystem")