MSG_OOB flag on HANGUP packet removed.
authorPaul Belanger <paul.belanger@polybeacon.com>
Wed, 16 Jun 2010 18:43:22 +0000 (18:43 +0000)
committerPaul Belanger <paul.belanger@polybeacon.com>
Wed, 16 Jun 2010 18:43:22 +0000 (18:43 +0000)
Per Tilghman's request on IRC (#asterisk-bugs).

(closes issue #17506)
Reported by: brycebaril
Tested by: pabelanger, tilghman

git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@270936 65c4cc65-6c06-0410-ace0-fbb531ad65f3

CHANGES
res/res_agi.c

diff --git a/CHANGES b/CHANGES
index 5e69680..68fc290 100644 (file)
--- a/CHANGES
+++ b/CHANGES
@@ -1468,7 +1468,7 @@ Language Support Changes
 AGI Changes
 -----------
   * Added SPEECH commands for speech recognition. A complete listing can be found
-     using agi show.
+    using agi show.
   * If app_stack is loaded, GOSUB is a native AGI command that may be used to
     invoke subroutines in the dialplan.  Note that calling EXEC with Gosub
     does not behave as expected; the native command needs to be used, instead.
@@ -1477,6 +1477,7 @@ AGI Changes
     of the URI parameter to the AGI function call in your dial plan. Also note
     that specifying a port number in the AGI URI will disable SRV lookups,
     even if you use the hagi: protocol.
+  * No longer support MSG_OOB flag on HANGUP.
 
 Logger changes
 --------------
index 4665724..4f0d17b 100644 (file)
@@ -814,9 +814,9 @@ ASTERISK_FILE_VERSION(__FILE__, "$Revision$")
                        signals a desire to stop (either by exiting or, in the case of a net script, by
                        closing the connection). A locally executed AGI script will receive SIGHUP on
                        hangup from the channel except when using DeadAGI. A fast AGI server will
-                       correspondingly receive a HANGUP in OOB data. Both of these signals may be disabled
-                       by setting the <variable>AGISIGHUP</variable> channel variable to <literal>no</literal>
-                       before executing the AGI application.</para>
+                       correspondingly receive a HANGUP inline with the command dialog. Both of theses
+                       signals may be disabled by setting the <variable>AGISIGHUP</variable> channel
+                       variable to <literal>no</literal> before executing the AGI application.</para>
                        <para>Use the CLI command <literal>agi show commands</literal> to list available agi
                        commands.</para>
                        <para>This application sets the following channel variable upon completion:</para>
@@ -3345,7 +3345,7 @@ static enum agi_result run_agi(struct ast_channel *chan, char *request, AGI *agi
                                if (pid > -1) {
                                        kill(pid, SIGHUP);
                                } else if (agi->fast) {
-                                       send(agi->ctrl, "HANGUP\n", 7, MSG_OOB);
+                                       send(agi->ctrl, "HANGUP\n", 7, 0);
                                }
                        }
                }
@@ -3443,7 +3443,7 @@ static enum agi_result run_agi(struct ast_channel *chan, char *request, AGI *agi
                        }
                        waitpid(pid, status, WNOHANG);
                } else if (agi->fast) {
-                       send(agi->ctrl, "HANGUP\n", 7, MSG_OOB);
+                       send(agi->ctrl, "HANGUP\n", 7, 0);
                }
        }
        fclose(readf);