Merged revisions 314069 via svnmerge from
authorRichard Mudgett <rmudgett@digium.com>
Mon, 18 Apr 2011 16:27:14 +0000 (16:27 +0000)
committerRichard Mudgett <rmudgett@digium.com>
Mon, 18 Apr 2011 16:27:14 +0000 (16:27 +0000)
commit0a5c2d8391bf591c497f9f112827305fd692b469
treebbe5597ce8c110ca3195ea5f5092b7500a6e2973
parent7c4fc0f0e807f9bbb67acd485eb78a739e729403
Merged revisions 314069 via svnmerge from
https://origsvn.digium.com/svn/asterisk/branches/1.8

........
  r314069 | rmudgett | 2011-04-18 11:10:10 -0500 (Mon, 18 Apr 2011) | 22 lines

  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/trunk@314080 65c4cc65-6c06-0410-ace0-fbb531ad65f3
res/res_agi.c