[...]Asterisk Asynchronous AGI « Moy Blog[...]…

I’m glad you found it useful.

I am not sure I am following what you propose. When you say:

“the following would send the AGI request to sessions authenticated by the AMI user account ‘mark’”

What AGI “request” are you talking about? The initial AsyncAGI event that is launched when a channel executes the AGI(agi:async:ami_accnt=’mark’) application?

If that is the case, then, it looks like you’re talking about associating a given AsyncAGI execution (both manager commands and events??) to a single manager account?

One thing I would love to see is the ability to target a specific AMI session with the command to better support environments with multiple concurrent AMI sessions. For example, the following would send the AGI request to sessions authenticated by the AMI user account ‘mark’

AGI(agi:async:ami_acct=’mark’)

What are your thoughts. Would this be difficult to implement?

I recommend you to ask in the asterisk-users mailing list, you have more chances of getting help there.

How can i do it?

Thanks.

tcore*CLI> agi exec SIP/testing-09a5b960 “Answer”

You just need to call the AGI application with the arguments agi:async, like this:

AGI(agi:async);

I have the next response:
Failed to add AGI command to channel SIP/8029-000001ea queue

In the CLI interface I see this control message:
Channel SIP/8029-000001ea is not at Async AGI.

Why? How can I add a channel to Async AGI?

Thanks