This is an old revision of the document!



This is an advanced module

This module functions like the Goto App ( ) module, with the exception that the ‘Subdialog’ ( ) module allows users to jump to an external VoiceXML application. Fuse passes data to the VoiceXML application and receives data in return that can be used as subvariables, just like the ‘Goto App’ ( ).

Enter the URL of the web server location where the VoiceXML application lives in the first field.

Executing a subdialog tells Plum's VoiceXML browser to go request that page. The VXML browser, in turn, can make that request in a few different ways.

The ‘submit as’ drop-down menu gives users the options: POST, GET (w/ parameter), or GET.

All three settings allow users to enter an event name, which can include variables.

POST and GET (w/ parameter) both allow users to define a custom variable.

  • POST: Users must define variables as POST variables. These variables are “hidden” in the request, behind the scenes, so to speak, and are passed directly to the backend scripting server. Once the server receives these requests, it can act upon them. Users building PCI-compliant application(s) should use POST because it prevents data from being passed to the server in clear text in the URL.
  • GET: GET requests pass variables directly in the URL request to a server. A tell-tale sign of a GET request is a URL with a question mark (?) in it followed by additional data. GET data is passed directly to the application server but this method is less secure that a POST request. GET data is typically logged in web server logs, which is not a PCI-compliant.
  • GET w/ <param>: A GET w/ <param> request is used when users need data in their application server, but want to pass that data directly to their VoiceXML script. A GET w/ <param> request initiates a GET request to the web server but does not pass any data to the server. Instead, the data is stored inside Plum's VoiceXML browser. A common use case for a GET w/ <param> request is when users want to pass data that will be used to dynamically prompt the end-user, but there is no need to have that data on the web server. Another useful application of this method is when users are not using a dynamic scripting language on their web server and are serving static VoiceXML instead. Those static pages cannot receive data directly and instead need to receive all its data as <param> values.

The two most common errors that users see with this module occur when a server times out or an application returns invalid data.

Module Settings

  • Hold Music
  • Timeout Length (default 30 seconds)
  • Private
  • Show Events (enabled by default)
  • Show Custom Errors
modules/subdialog.1487258733.txt.gz · Last modified: 2017/02/16 15:25 by admin