Book Image

Asterisk Gateway Interface 1.4 and 1.6 Programming

By : Nir Simionovich
Book Image

Asterisk Gateway Interface 1.4 and 1.6 Programming

By: Nir Simionovich

Overview of this book

<p>Asterisk is the world's leading open-source PBX, telephony engine, and telephony applications toolkit with immense flexibility.<br /><br />This book will give you a firm understanding of Asterisk Gateway Interface (AGI) development and proper AGI development practices. You will learn how to formulate Atomic AGI-enabled scripts, enabling rapid development within a well-defined Asterisk execution and runtime environment.<br /><br />This book builds from the simplest form of an Asterisk application, the dialplan-based application, gradually building a full understanding of AGI scripting. The book also introduces a new concept of AGI development named "Atomic AGI" or "Particle Programming". It will introduce you to various techniques of interacting with the user, where user interaction isn't limited to keypad-based input, but also includes recording messages from the user, sending output to the user, and controlling the call flow.<br /><br />The book takes a pragmatic approach with clear and complete examples, and a service development project &acirc;&euro;&rdquo; allowing you to understand the project cycle of developing an Asterisk-based service or application.</p>
Table of Contents (16 chapters)
Asterisk Gateway Interface 1.4 and 1.6 Programming
Credits
About the author
Acknowledgement
About the reviewers
Preface

Project implementation guide


Every project should be split into several distinct steps. While each software development and project management methodology may define different steps, the following are the minimum number of steps required to implement our project.

  • Step 1: Analysis of the requirements In my view, this is the most crucial part of the project flow, as every other step is a direct derivative of this one. The analysis stage should contain a complete investigation of the platform's requirements, the possible pitfalls, and more importantly, the possible implementation paths to be taken. If your project requires the utilization of multiple business entities or departments, this would be the time to identify the various critical paths in the implementation.

  • Step 2: Understanding operational constraints Understanding the operational constraints can be described as: "knowing your game field". Each computing and hardware environment will impose a different set of constraints on your...