Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!wuarchive!sdd.hp.com!ucsd!casbah.acns.nwu.edu!accuvax.nwu.edu!nucsrl!telecom-request
From: lairdb@crash.cts.com (Laird P. Broadfield)
Newsgroups: comp.dcom.telecom
Subject: Re: LD vs Voice Mail / Lower Hotel Phone Charges
Message-ID: <15318@accuvax.nwu.edu>
Date: 7 Dec 90 20:50:47 GMT
Sender: news@accuvax.nwu.edu
Organization: TELECOM Digest
Lines: 25
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 873, Message 3 of 9

In <15248@accuvax.nwu.edu> snowgoose!dave@uunet.uu.net writes:

[stuff about pressing # to enter voicemail....]

>[Moderator's Note: But don't you have to hold the # key for at least a
>couple seconds to get a carrier disconnect?  Most voice mail systems
>require far less. That is, you could probably just give a half-second
>of # and access voice mail without it being long enough to trigger the
>network disconnect.  Sprint and ATT both indicate in their literature
>to hold down the # key for a couple seconds to make it work right.   PAT]

Nope.  From _numerous_ locations throughout the ConUS I have made the
mistake of hitting the # key to sign on to our voicemail system too
soon and had AT&T dump the connection.  The "key" here is to _wait_
about three or four seconds into the answer message, at which point
AT&T is apparently no longer listening.  I haven't tried a LONG # at
all; only short ones.  Perhaps the call-progress is significant to the
tone-recognizer; before it has "realized" the connection, or after it
has recognized a hangup, maybe any # works, but during a connection
only a _long_ #?  Just guessing....


Laird P. Broadfield                       
UUCP: {akgua, sdcsvax, nosc}!crash!lairdb 
INET: lairdb@crash.cts.com