Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!lll-winken!telecom-request From: rhyre@cinoss1.att.com (Ralph W. Hyre) Newsgroups: comp.dcom.telecom Subject: Re: Touch-Tone vs. Rotary - A Frustrating Experience Message-ID: Date: 10 May 91 13:18:25 GMT Sender: Telecom@eecs.nwu.edu Reply-To: "Ralph W. Hyre" Organization: AT&T OSS Development, Cincinnati Lines: 33 Approved: Telecom@eecs.nwu.edu X-Submissions-To: telecom@eecs.nwu.edu X-Administrivia-To: telecom-request@eecs.nwu.edu X-Telecom-Digest: Volume 11, Issue 353, Message 2 of 12 In article det@nightowl.mn.org (Derek E. Terveer) writes: X-Telecom-Digest: Volume 11, Issue 344, Message 1 of 10 > jiro@shaman.com (Jiro Nakamura) writes: >> For my new line, I deliberately didn't order touch-tone service ... > I agree. For my data line, I specifically ordered it with just pulse > The only potential disadvantage that I see is if I want my Unix box to > call long distance and use some sort of calling card code number or > something like that that requires touch-tone. You can STILL send touch-tones over your phone line, whether you pay for it or not. When you pay your local phone company for 'touch-tone' that just means you can dial your initial number using touch-tone. They don't card what you dial once you are talking to your long distance carrier/information provider whatever. Calling card example: (manual dial) pulse 10288 + 0 + 700 555 4141 [switch to tone] + Card Number (My phone has a push button to switch to touch tone mode, so it's really handy for this application.) Modem example: (don't try this at home, my recollection of the Hayes command set is fuzzy.) ATDP1073207005554141T {card number digits}