externalivr.txt 5.8 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153
  1. Asterisk External IVR Interface
  2. -------------------------------
  3. If you load app_externalivr.so in your Asterisk instance, you will
  4. have an ExternalIVR() application available in your dialplan. This
  5. application implements a simple protocol for bidirectional
  6. communication with an external process, while simultaneous playing
  7. audio files to the connected channel (without interruption or
  8. blocking).
  9. The arguments to ExternalIVR() consist of the command to execute and
  10. any arguments to pass to it, the same as the System() application
  11. accepts. The external command can be executed in a child process,
  12. with its standard file handles connected to the Asterisk process as
  13. follows:
  14. stdin (0) - DTMF and hangup events will be received on this handle
  15. stdout (1) - Playback and hangup commands can be sent on this handle
  16. stderr (2) - Error messages can be sent on this handle
  17. The application will also create an audio generator to play audio to
  18. the channel, and will start playing silence. When your application
  19. wants to send audio to the channel, it can send a command (see below)
  20. to add a file to the generator's playlist. The generator will then
  21. work its way through the list, playing each file in turn until it
  22. either runs out of files to play, the channel is hung up, or a command
  23. is received to clear the list and start with a new file. At any time,
  24. more files can be added to the list and the generator will play them
  25. in sequence.
  26. While the generator is playing audio (or silence), any DTMF events
  27. received on the channel will be sent to the child process (see
  28. below). Note that this can happen at any time, since the generator,
  29. the child process and the channel thread are all executing
  30. independently. It is very important that your external application be
  31. ready to receive events from Asterisk at all times (without blocking),
  32. or you could cause the channel to become non-responsive.
  33. If the child process dies, ExternalIVR() will notice this and hang up
  34. the channel immediately (and also send a message to the log).
  35. ExternalIVR() Options
  36. ----------------------
  37. n: 'n'oanswer, don't answer an otherwise unanswered channel.
  38. i: 'i'gnore_hangup, instead of sending an 'H' event and exiting
  39. ExternalIVR() upon channel hangup, it instead sends an 'I' event
  40. and expects the external application to exit the process.
  41. d: 'd'ead, allows the operation of ExternalIVR() on channels that
  42. have already been hung up.
  43. DTMF (and other) events
  44. -----------------------
  45. All events will be newline-terminated strings.
  46. Events sent to the child's stdin will be in the following format:
  47. tag,timestamp[,data]
  48. The tag can be one of the following characters:
  49. 0-9: DTMF event for keys 0 through 9
  50. A-D: DTMF event for keys A through D
  51. *: DTMF event for key *
  52. #: DTMF event for key #
  53. H: the channel was hung up by the connected party
  54. E: the script requested an exit
  55. Z: the previous command was unable to be executed
  56. T: the play list was interrupted (see S command below)
  57. D: a file was dropped from the play list due to interruption (the
  58. data element will be the dropped file name) NOTE: this tag conflicts
  59. with the D DTMF event tag. The existence of the data element is used
  60. to differentiate between the two cases
  61. F: a file has finished playing (the data element will be the file
  62. name)
  63. P: a response to the 'P' command (see below)
  64. G: a response to the 'G' command (see below)
  65. I: a Inform message, meant to "inform" the client that something
  66. has occured. (see Inform Messages below)
  67. The timestamp will be 10 digits long, and will be a decimal
  68. representation of a standard Unix epoch-based timestamp.
  69. Commands
  70. --------
  71. All commands must be newline-terminated strings.
  72. The child process can send commands on stdout in the following formats:
  73. S,filename
  74. A,filename
  75. H,message
  76. E,message
  77. O,option
  78. V,name=value[,name=value[,name=value]]
  79. G,name[,name[,name]]
  80. L,log_message
  81. P,TIMESTAMP
  82. T,TIMESTAMP
  83. The 'S' command checks to see if there is a playable audio file with
  84. the specified name, and if so, clear's the generator's playlist and
  85. places the file onto the list. Note that the playability check does
  86. not take into account transcoding requirements, so it is possible for
  87. the file to not be played even though it was found. If the generator
  88. is not currently playing silence, then T and D events will be sent
  89. to the child to signal the playlist interruption and notify it of
  90. the files that will not be played.
  91. The 'A' command checks to see if there is a playable audio file with
  92. the specified name, and if so, adds it to the generator's
  93. playlist. The same playability and exception rules apply as for the
  94. 'S' command.
  95. The 'E' command stops the generator and continues execution in the dialplan,
  96. and logs the supplied message to the Asterisk log.
  97. The 'H' command stops the generator and hangs up the channel, and logs
  98. the supplied message to the Asterisk log.
  99. The 'O' command allows the child to set/clear options in the
  100. ExternalIVR() application. The supported options are:
  101. autoclear/noautoclear:
  102. Automatically interrupt and clear the playlist upon reception
  103. of DTMF input.
  104. The 'T' command will answer and unanswered channel. If it fails either
  105. answering the channel or starting the generator it sends a Z response
  106. of "Z,TIMESTAMP,ANSWER_FAILED" or "Z,TIMESTAMP,GENERATOR_FAILED"
  107. respectively.
  108. The 'V' command sets the specified channel variable(s) to the specified
  109. value(s).
  110. The 'G' command gets the specified channel variable(s). Multiple
  111. variables are separated by commas. Response is in name=value format.
  112. The 'P' command gets the parameters passed into ExternalIVR() minus
  113. the options to ExternalIVR() itself:
  114. If ExternalIVR() is executed as:
  115. ExternalIVR(/usr/bin/foo(arg1,arg2),n)
  116. The response to the 'P' command would be:
  117. P,TIMESTAMP,/usr/bin/foo|arg1|arg2
  118. The 'L' command puts a message into the Asterisk log.
  119. Errors
  120. ------
  121. Any newline-terminated output generated by the child process on its
  122. stderr handle will be copied into the Asterisk log.