2008 May

Redundant Asterisk setup
Obtaining a reliable, fault tolerant, highly available system with ASTERISK� has been difficult and nearly impossible especially from the PRI/TDM standpoint. IP based toolsets have been around for a number of years to allow integrators the ability to provide fault-tolerance on the VoIP side of their implementation. Until today however, providing quick, reliable and robust T1/E1 fail-over has been nearly non-existent. The foneBRIDGE fills this void allowing IT Managers and Systems Integrators to implement Asterisk in the most demanding of environments where downtime is a luxury a business simply can not afford. Read the rest of this entry »

Related posts

• No related posts.

What is AGI?

The Asterisk Gateway Interface (AGI) is a way to interface with Asterisk much like CGI is for Apache. It is language agnostic, and there are example scripts in PHP, Perl, and Python to name a few. The reason for this versatility is that AGI uses standard streams that are connected with modern UNIX operating systems. The streams used are STDIN, STDOUT, and STDERR.
Because of its flexibility, AGI can be used to create a range of different applications. Some examples that I have seen are applications that tell you the current temperature, pushing caller ID information to a MythTV system, writing CDR data to different backend databases, and the list goes on.
A small disclaimer, I wrote this guide as a learning tool for myself. I’ve attempted to present the information here in a clear, concise manner, and to be as accurate as possible. If you find any errors or have suggestions please post your suggestions.

Getting started
Asterisk has a standard location for AGI scripts when installed from source. If you’ve installed from a vendor’s package they might have changed the location to fit their standards. The location by default is /var/lib/asterisk/agi-bin/. Read the rest of this entry »

Related posts

• No related posts.