From 91b9c8fca12c39d89ed0e3d22fed8c8f8b57df3d Mon Sep 17 00:00:00 2001 From: David Ruggles Date: Wed, 11 Nov 2009 20:47:06 +0000 Subject: [PATCH] Remove non-functional feature from ExternalIVR documentation Remove non-functional socket implementation of ExternalIVR from documentation (closes issue #16225) Reported by: thedavidfactor Patches: externalivr.txt.20091111.1542.patch uploaded by thedavidfactor (license 903) git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@229568 65c4cc65-6c06-0410-ace0-fbb531ad65f3 --- doc/externalivr.txt | 9 --------- 1 file changed, 9 deletions(-) diff --git a/doc/externalivr.txt b/doc/externalivr.txt index cc61c69972..75a5610311 100644 --- a/doc/externalivr.txt +++ b/doc/externalivr.txt @@ -18,15 +18,6 @@ stdin (0) - DTMF and hangup events will be received on this handle stdout (1) - Playback and hangup commands can be sent on this handle stderr (2) - Error messages can be sent on this handle -The external command can also be executed on another host entirely -(specified by the ivr:// prefix), with its standard file handles -connected to the Asterisk process as follows: - -stdin (0) - DTMF and hangup events will be received on this handle -stdout (1) - Playback and hangup commands can be sent on this handle -There are no error messages available when using ExternalIVR over TCP, -use the 'L' command as a replacement for this. - The application will also create an audio generator to play audio to the channel, and will start playing silence. When your application wants to send audio to the channel, it can send a command (see below)