]> git.ipfire.org Git - thirdparty/asterisk.git/commit
The AsyncAGI command loop is lax in the value it returns for the return status.
authorRichard Mudgett <rmudgett@digium.com>
Mon, 18 Apr 2011 16:10:10 +0000 (16:10 +0000)
committerRichard Mudgett <rmudgett@digium.com>
Mon, 18 Apr 2011 16:10:10 +0000 (16:10 +0000)
commitc4d972a941a7fb00b68c51d8f1ac66fc079dd58f
treed9dca6076c630654e7dc2195f7ed65eb05c568b3
parentbc620cd2817435689f45034b2cf992c84ecb2a95
The AsyncAGI command loop is lax in the value it returns for the return status.

* Return correct status: SUCCESS/FAILED/HANGUP.  Previously, abnormal
exits from the command loop such as hangup would return SUCCESS.

* The "asyncagi break" command now returns SUCCESS and is now the only way
to break the command loop with that status.  Previously, it returned
FAILED.

* The AMI event AsyncAGI End is no longer sent if the AsyncAGI Start event
is not sent.  Previously, this happened because of an error setting up the
AGI pipes.

* All executed AGI commands now get an AsyncAGI Exec result event.
Previously, if the command returned failure (because of hangup), the
command loop just exited with FAILURE and did not send the AsyncAGI Exec
result event.

* Makes sure that the channel frame queue is empty on hangup.

Review: https://reviewboard.asterisk.org/r/1183/

git-svn-id: https://origsvn.digium.com/svn/asterisk/branches/1.8@314069 65c4cc65-6c06-0410-ace0-fbb531ad65f3
res/res_agi.c