[Asterisk-Users] Basic Asterisk questions

[Steven Critchfield]

Why is it that most users who don't understand threaded email is on
Windows systems. 

On Thu, 2003-06-26 at 19:47, Scott Stingel wrote:
> Hello-
> 
> I apologise for the basic nature of these questions:
> 
> I am considering using Asterisk/Digium for the implementation of a simple
> IVR application - inbound E1's only.  All I want to do is to answer each
> line, play some prompts, receive a DTMF, play some more prompts, then log
> everything, and hang up.  Seems simple enough.
> 
> I've been looking over the various web sites and have downloaded the
> asterisk tar files, and looked at the README's contained therein.   I have a
> few question though:
> 
> (a) For my logging, I want to insert records into an external SQL database.
> I don't understand the general way to call SQL routines that I have written,
> or to other access code outside of the Asterisk environment

If you are on a postgres database, just use PSQL to issue your queries
directly from the extensions.conf file. If you can write a simple cli
app that can take care of it with a system  call. Or you can go out to
an agi app and do you database interfaces with whatever programming
language app you can think of.


> (b) Where can I read about events and how they are handled?  For example,
> upon the reception of a DTMF during a prompt, does the prompt get
> interrupted as it should?  Same thing on disconnect events.

Depends on how you are playing a prompt. If it is by use of Playback
then no it will not be interrupted. If you use Background, then yes it
will be interrupted. If you are in AGI, you can specify the only
characters that would interrupt. 

> No doubt I have not read some very basic documentation or user notes, so if
> anyone can steer me to the proper documents to read, would be greatly
> appreciated!

Compile asterisk, and from the asterisk command line, use "help", "show
applications", and "show application <application>" to see descriptions
of what each command does.
-- 
Steven Critchfield <critch at basesys.com>