I’ve just finished adding support for Asynchronous AGI to Asterisk-Java. The way AsyncAGI is supported by Asterisk-Java hides the differences in the underlying communication from the differences in the underlying communication from the users of our l…

ie, Fastagi call looked like:
123 =>{
AGI(agi://hostname:4567/scriptname?param1=val1&param2=val2);
};

How should this be implemented with AsyncAGI?

Even when anything you can do through FastAGI you can do it as well throug Async AGI, the client code has to change quite a bit since now, froma single connection you have to be aware of ALL channels, not of a single channel. This brings power but also complexity when dealing with many channels.

Currently you cannot pass parameters directly to AsyncAGI, but you can

Set(param1=val1)
Set(param2=val2)
AGI(agi:async)

Then from your manager connection
Action: AGI
Command: GetVariable param1

However I agree is easier to just pass parameters, so I will add that support.

What you don’t seem to understand is what I just said to you, AsyncAGI HANDLES ALL THE CHANNELS THROUGH THE MANAGER, there is no such thing as an execution script (sure thing probably there will be manager connections controled from scripts, but that’s outside the AsyncAGI scope to know). That’s what “Async” means, Asynchronous.

When you execute a script via FastAGI that script will control the channel during the life of the script, your script just takes care of that single channel and when you execute an AGI command your script “blocks” its execution until the command finishes.

AsyncAGI just puts the channel to wait for Asynchronous AGI commands, where those commands will come from? is up to you. In my case I had a program that connected to the Asterisk manager and handled all the channels, so I had a single script that worked pretty much like a PBX in a scripting language, took care of knowing which channels were active and what to do with ALL of them, bridging them, un-bridging them, put in them in conferences, play audio etc.

If you do anything at all with Async AGI you will have to understand event-oriented programming, because that’s how you do to control channels over AsyncAGI.