Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!julius.cs.uiuc.edu!apple!bionet!hayes.ims.alaska.edu!accuvax.nwu.edu!nucsrl!telecom-request
From: SABAHE@macalstr.edu (Arun Baheti <SABahe@Macalstr.EDU>)
Newsgroups: comp.dcom.telecom
Subject: Call-Waiting Disable
Message-ID: <14557@accuvax.nwu.edu>
Date: 9 Nov 90 18:33:00 GMT
Sender: news@accuvax.nwu.edu
Organization: TELECOM Digest
Lines: 17
Approved: Telecom@eecs.nwu.edu
X-Submissions-To: telecom@eecs.nwu.edu
X-Administrivia-To: telecom-request@eecs.nwu.edu
X-Telecom-Digest: Volume 10, Issue 807, Message 8 of 12


I'm having trouble disabling the call waiting feature in the Twin
Cities area.  While the standard methods (*70 and 1170) are listed in
the phone book, and the phone company claims vehmently that these
methods will work, I continue to receive "call not completed" messages
whenever I try.  The normal methods work in SoCal (Pac*Tel), so I am
beginning to wonder ... Does anyone else have experience with the Twin
Cities system? 


[Moderator's Note: Two assumptions are in order: (1) You *do* have
Call Waiting on the line in question (not just 'think you do'), and
(2) the serving CO is equipped with the proper generics. For example,
here in the Illinois Bell LATA almost everyone has *70 available. But
the folks in Mor(t)on Grove -- Moron Grove is the sister city of the
People's Republic of Ann Arbor, yuk, yuk! -- do not have it. The
generics on their switch are different.  PAT]