Skip to content


Subversion checkout URL

You can clone with
Download ZIP
PHP AGI ( Asterisk Gateway Interface ) facade, with CDR ( Call Detail Record ), Call spool and schedule auto dial, Send and Receive Fax, Channel Variables, and Caller ID management
Fetching latest commit...
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.


This software is still in development, stay tuned.

This framework is intended to simply making agi applications. You will 
extend PAGIApplication and your signal handler, error handler, init, and
shutdown methods are automatically setup and called.

Please see docs/examples/quickstart for a very basic example. You'll need
something like this in your dialplan:

Checkout the api (phpdoc) at:

exten => 1,1,AGI(/tmp/PAGI/docs/examples/quickstart/,a,b,c,d)
exten => 1,n,Hangup

Currently there is no manual or comprehensive documentation, so please refer
to the examples, it's really all there (I will write the documentation as
soon as possible). Please contact me if you have any comments, doubts, or
any kind of feedback. Send an email to:

You may want to take a look at Ding if you're
interested in using DI, AOP, and other stuff in your telephony applications.

CallFiles are supported. You can also schedule a call in the future.
Sending and receiving faxes is supported using spandsp (applications SendFax
and ReceiveFax).
Available Facades
PAGI\Client\CDR: Provided to access cdr variables.
PAGI\Client\ChannelVariables: Provided to access channel variables and asterisk
environment variables.
PAGI\Client\CallerID: Provided to access caller id variables.
PAGI\Client\Result: Provided to wrap up the result for agi commands.
PAGI\CallSpool\CallFile: Call file facade.
PAGI\CallSpool\CallSpool: Call spool facade.
PAGI\Logger\Asterisk: Provides access to asterisk logger (see logger.conf in your
asterisk installation).
For every operation, a Result is provided. Some operations decorate this
Result to add functionality, like PlayResult, ReadResult, etc. For example,
a stream file will return a PlayResult, which decorates a ReadResult which 
in turn, decorated a Result.
* PAGI\Client\DialResult
* PAGI\Client\ExecResult
* PAGI\Client\ReadResult
* PAGI\Client\PlayResult
* PAGI\Client\FaxResult
Debugging, logging

You need log4php ( if you want debugging
output from the container. Just make sure you copy it to the include_path and
PAGI will pick it up from there.

This means that this is NOT A REQUIREMENT FOR A DEPLOY. It's not even a
requirement at develop time (except when you really want debug output).
You can use the included example of a file in

Of course it is recommended that you do not set DEBUG output in your log4php
configuration (or remove it from the include path so PAGI will notice and not
use it). This *will* create a difference in performance.
* build.xml is a phing build file, not ant.
* It's very possible that you may need to edit
* Available main targets: all, build, test, report.
* Tools run: phpdoc, phploc, phpcs, phpmd, phpcpd, phpdepend, phpunit.
Something went wrong with that request. Please try again.