Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!uakari.primate.wisc.edu!sdd.hp.com!decwrl!hayes.fai.alaska.edu!accuvax.nwu.edu!nucsrl!telecom-request From: merlyn@iwarp.intel.com (Randal Schwartz) Newsgroups: comp.dcom.telecom Subject: Re: Can One Disable Call-Waiting If *70 Doesn't Work? Message-ID: <9245@accuvax.nwu.edu> Date: 25 Jun 90 16:16:30 GMT Sender: news@accuvax.nwu.edu Reply-To: Randal Schwartz Organization: Stonehenge; netaccess via Intel, Beaverton, Oregon, USA 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 453, Message 9 of 15 In article <9217@accuvax.nwu.edu>, john@bovine (John Higdon) writes: | I am curious, though. Why would anyone have call waiting on a data | line? Cuz sometimes we use voice lines for "data" lines. I live in GTE-land (boo hiss!) and they only recently added call-waiting disable to my home phone exchange (switch?). Before that, I simply forwarded my phone to my answering service. That's the other way around it -- get call forwarding. =Randal L. Schwartz, Stonehenge Consulting Services (503) 777-0095 =========== | on contract to Intel's iWarp project, Beaverton, Oregon, USA, Sol III | | merlyn@iwarp.intel.com ...!any-MX-mailer-like-uunet!iwarp.intel.com!merlyn |