Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!wuarchive!zaphod.mps.ohio-state.edu!sdd.hp.com!decwrl!hayes.fai.alaska.edu!accuvax.nwu.edu!nucsrl!telecom-request
From: synsys!jeffj@uunet.uu.net
Newsgroups: comp.dcom.telecom
Subject: Re: A New Feature One Might Build Into a Phone
Message-ID: <10715@accuvax.nwu.edu>
Date: 10 Aug 90 00:53:01 GMT
Sender: news@accuvax.nwu.edu
Organization: TELECOM Digest
Lines: 50
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 559, Message 11 of 12


In Volume 10, Issue 547, Message 9 of 15, Message-ID: <10550@accuvax.
nwu.edu>, John Nagle posted:

>     Now here's a thought.  We all know the announcments which begin
>with a special three-tone sequence followed by "The number you have
>reached...".  How about a voice recognition unit to recognize the new
>number and update your autodialer?  The spoken digits are well
>separated, the background noise is low, and the digits are clearly
>enunciated, so a relatively simple system should suffice.  This would
>be a neat addition to one of those "turn your computer into an
>answering machine" programs.

>     It would be really easy if the spoken digits were standardized
>nationally, but they are not.  Even the rate varies with location.

I'll go you one better: right after the tritone (that's called a SIT,
right?), transmit the data DIGITALLY with a modem, the same FSK as
used in Caller-ID.

This is kind to machines:
The tritone is the header followed immediately by the data.  

This is kind to humans: 
The tritone is loud and annoying already so a little more screaming
won't hurt.

FAX/modem/autodialer manufacturers should love this:
If the machine recognizes the tritone and can act accordingly, you'll
prevent repeated failed calls.  You could automatically update the
phone list when a new number is given.  The retry mechanism could
adapt if the line is temporarily out of service or give up if it's
permanently out of service.

I'd expect a CCITT definition of the command to be something like a 16
bit command followed by a variable length field.  The commands would
be specified like:

command: 0000h  Number out of service
following data: none

command: 0001h  all lines temporarily busy
following data: none

command: 0010h  number changed
following data: phone number (in the same format as ANI)
[I'm not sure what will be sent for an unlisted number]

Jeffrey Jonas
jeffj@synsys.uucp