Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!bellcore!texbell!vector!telecom-gateway From: morris@jade.jpl.nasa.gov (Mike Morris) Newsgroups: comp.dcom.telecom Subject: Re: Establishing a hunt group between private lines Message-ID: Date: 13 Jun 89 03:57:19 GMT Sender: news@vector.Dallas.TX.US Reply-To: Mike Morris Lines: 33 Approved: telecom-request@vector.dallas.tx.us X-Submissions-To: telecom@eecs.nwu.edu X-Administrivia-To: telecom-request@vector.dallas.tx.us X-TELECOM-Digest: volume 9, issue 195, message 7 of 9 In article fred@dtix.ARPA (Fred Blonder) writes: >I'm hoping that someone can provide some useful advice regarding >the following situation: I'm planning on getting my own phone line >run in a house which I share with roommates. I've been told by the >local phone company (Chesapeake & Potomac) that they will not allow >the new line to hunt to the old "communal" line which I already >share with my roommates, because it's listed under a different name. >While they may have sound reasons for this policy, I don't see how >they apply in this case. >My question is: Does anyone have an idea of how high up the chain- >of-command I'll need to go in order to get an exception granted? >Has anyone done this, or something similar? Is this hopeless? Pacific Bell offers (or at least used to - a friend had it about '82) but it's expensive, and all lines must be in the same name. Why not get call forwarding, or call forwarding-no-answer? Another alternative is used by some friends of mine: there is one listed line, and each person has their own unlisted line. The answering machine on "pub" can be dumped remotely. The answering machine on the private line(s) are the individual's own responsibility. It is a large house (5 bedrooms) and a multi-line (1A2) key system services the house (complete with "head" phones). "Pub" rings everywhere, the private lines ring in the individual bedrooms and buzzes everywhere. US Snail: Mike Morris UUCP: Morris@Jade.JPL.NASA.gov P.O. Box 1130 Also: WA6ILQ Arcadia, Ca. 91006-1130 #Include disclaimer.standard | The opinions above probably do not even