readme.src

控制语音Modem的程序

.\" Process this file with man -l ./README.src > README
.\"
.de LINE
-----------------------------------------------------------------
.br
..
.\"
.\"
.LINE
DESCRIPTION
.br
.LINE
.ta 1.5i 2.5i
.in +1.5i
.ti -1.5i
voice	Suite of programs to drive voice modems, it
includes a full-featured answering machine.
Ready to go for Rockwell voice commands.
Developed and tested under Linux, free software distributed
under GNU General Public License.
.sp
.ti -1.5i
Version:	0.6.1		Jul 14 1999
.sp
.ti -1.5i
Author:	Niccolo Rigacci <[e-mail]>
.in 0i
.sp
.sp
.LINE
QUICK INTRODUCTION
.br
.LINE
I think that the simplest way to drive a modem is through a shell
script and a simple program like "chat" that allow interaction
of the type: "send string" - "wait string".
.br
For voice operation we must add some functionalities because
it is not possible to give a stream of digitized voice on
the command line and we must capture the incoming voice to
a file too.
.br
Beside that we have to handle the "escaped chars" that the
modem embed in the voice stream when we receive voice (to
signal silence, DTMF tones, etc.), and those we send to the
modem when we send voice.
.br
Voice Modem Control Porgram (vmcp) addresses all the problems:
.sp
 - send to the modem a string specified on the command line
 - send to the modem a binary file
 - capture data from the modem to a file, stripping escaped chars
 - capture escaped chars from the modem to a second file
 - exit on receiving a string from the modem
 - exit on receiving a given escaped char from the modem
 - exit on timeout or keypress
.sp
All these functions can be enabled or disabled, see vmcp.8 man
page for command line options (you can read a man page without
installing it with the command "man -l ./vmcp.8").
.br
If you want fully understand how a voice modem works, read the
Rockwell voice commands guide, or the US-Robotics one.
Relative URLs are in the Credits section below.
.br
As a working example of how vmcp can be used, you can find ans,
a bash script that emulates a full-featured answering machine.
It includes discrimination of incoming voice, fax or data calls,
remote password protected retrieving of messages, changing of
password and greeting message.
.br
Any feedback on this work will be greatly appreciated; send notes,
suggestions and bug reports directly to the author.
.sp
.sp
.LINE
WHAT YOU HAVE (ARCHIVE CONTENTS)
.br
.LINE
.ta 1.5i
COPYING		GNU General Public License
.br
Makefile	Script for compiling and installing everything
.br
README	This file
.br
README.src	Source file for README
.br
VOICE_FAQ	Answers to some frequently asked questions
.br
ans	Bash script to emulate an answering machine
.br
ans.8	Man page for ans
.br
passwd	Contains the secret code for ans remote access
.br
vmcp.8	Man page for vmcp
.br
vmcp.c	Source code of the communication utility
.br
voice.lsm	Linux Software Map entry for this package
.br
vplay	Bash script to play voice files
.br
vrec	Bash script to record a voice file
.br
.sp
.sp
.LINE
WHAT YOU NEED
.br
.LINE
.in +0.3i
.ti -0.3i
.ta 0.3i
-	A voice modem. The scripts "ans", "vplay" and "vrec" are customized
to work with Rockwell voice commands, they should work with US-Robotics
modems and many others. I think however you can edit them and
adapt to any voice modem.
.ti -0.3i
-	You must know which serial line your modem is connected to
and you must have read-write rights on this device. The
scripts are ready for a modem on the first serial line
(/dev/ttyS0), but you can easily edit them.
.ti -0.3i
-	The modem must have a full-wired serial cable because programs
use RTS, CTS, DTR and CD signals to work properly. No problems
with internal modems.
.ti -0.3i
-	If you want to handle incoming faxes, you must get a fax program,
I suggest efax (see Credits section); the ans script is already
configured for it.
.ti -0.3i
-	You must to know a little about how modems work: some AT
commands, etc.
.ti -0.3i
-	You must be able to edit bash scripts :-).
.in 0i
.sp
.sp
.LINE
GETTING NEW VERSIONS
.br
.LINE
My home page is at
.br
http://www.apsoftware.it/~niccolo/
.br
Sorry but this is in Italian. If you want you can go directly
to the directory
.br
http://www.apsoftware.it/~niccolo/comp/software/voice/
.br
Here you can also find voicecmd.zip, a complete guide
to voice commands for Rockwell modems (MS-Word 6 format).
.br
I also submitted version 0.6.1 to sunsite.unc.edu on 14 July 1999,
look in the directory
.br
/pub/Linux/apps/serialcomm/modem or
.br
/pub/Linux/Incoming.
.br
.sp
.sp
.LINE
COMPILING AND INSTALLING FILES
.br
.LINE
.ta 0.5i
To compile vmcp.c simply switch to the directory
where you unpacked the archive and issue the command:
.sp
	make
.sp
Hopefully no editing to the source is needed. To create the required
directories and to copy the files in their subdirectories with
appropriate rights, you must be root and execute:
.sp
	make install
.sp
If you want to know what directories are needed and to preview
where files are scattered across your system, have a look at the
Makefile. It is quite simple. You can also use the -n switch of
make to have a preview of install operations.
Directories structure, name and location of files are File System
Standard compliant (see Linux Filesystem Structure, Release 1.2).
.br
The installing procedure checks for the presence of many binary files
on which the ans script relies: if one of them is not found the
installation fails.
.sp
.sp
.LINE
QUICK TEST
.br
.LINE
Edit vrec and vplay scripts adjusting the "TTYS=ttySn" to reflect
your modem's serial line. Also adjust the $VMCP path if needed.
If you are unable to understand these scripts go away,
read the man bash and come back within a week :-)
.sp
.ta 2i
.in +2i
.ti -2i
vrec\ testfile\	Start recording to a file. Speak through
the microphone connected to the modem after
the beep and stop the recording pressing
the ESC key.
.sp
.ti -2i
vplay\ testfile\	Playback the message through the modem
speaker.
.in 0i
.sp
If this does not work, don't go any further! You must take your
modem manual and check every command sent to the modem via the
vrec script. In the Output Samples section below you find the
output you should get from the above test.
Exit status should help to understand what is not working (see
vmcp man page for an exit status table).
.sp
.sp
.LINE
SCRIPTS CUSTOMIZATION
.br
.LINE
Three files (ans, vplay and vrec) are bash scripts and may need
some editing to reflect your system peculiarities.
Hopefully no changes are needed if you follow FSSTND
directives and you are using a Rockwell compatible voice modem on /dev/ttyS0.
Check the begin of the three files for user configurable items.
All the scripts are configured to use the modem on the first
serial line (ttyS0), change the "TTYS=ttyS0" statement if your
modem is on a different device.
.br
The ans script need a bit more attention. It relies on many
binaries which should to be standard on every Unix-like system,
check yours for the presence and location of such binaries
(listed at the begin of the script too).
.br
Ans script also relies on efax program, not included in this
archive. Efax is called when an incoming fax is detected.
If you want incoming faxes handling, you must get efax running
and then you *MUST* check the line beginning with $EFAX in
the ans script and edit it (at least to remove my phone number
as the fax ID!).
.br
You see also many modem commands in the scripts, they all works
well on my internal modem (UMC chipset). Hopefully again no
editing needed for Rockwell chipset based modems. If you have
another modem you must find equivalent commands, see Credits
section for a pointer to Rockwell voice modems commands list.
.sp
.sp
.LINE
ABOUT THE SERIAL PORT
.br
.LINE
On Linux systems, serial ports are addressed via /dev/ttyS*
devices. Old /dev/cua* are obsolete and should not be used
anymore. Most systems make a symlink /dev/modem pointing to
the ttyS, purists don't like it.
See Linux Serial HOWTO for some hints.
.br
Device rights are not a problem, because I run all the scripts
as root. By the way this is my configuration:
.sp
.nf
crw-rw----   1 root    dialout  4,  64 Aug 22 10:35 /dev/ttyS0
crw-rw----   1 root    dialout  4,  65 Aug 22 10:35 /dev/ttyS1
 ...
.fi
.sp
.sp
.LINE
RECORDING DEFAULT MESSAGES
.br
.LINE
.ta 0.5i
Before using the ans script you *MUST* record some messages. You
can use the script vrec with a command like:
.sp
	vrec greeting.msg
.sp
The messages must go in the appropriate directory.
I think the best choice is
/usr/local/lib/ans, see the LIBDIR setting in the ans script.
Those are the messages needed and their contents. Append to the name
the extension ".msg" (as declared in the ans script).
.sp
.ta 2i
.in +2i
.ti -2i
ask_passwd.msg\	Please enter your password and terminate
it with #.
.ti -2i
ch_greeting.msg\	Record the new greeting after the beep, press
# to confirm, 9 to cancel.