Differences

This shows you the differences between two versions of the page.

--- vxi_installation_guide:management:start [2015/02/03 21:28] – [Management Commands] borja
+++ vxi_installation_guide:management:start [2015/02/25 21:23] – borja
@@ Line 1: / Line 1: @@
-====== System Management ======
+====== Management ======
 ===== Getting Started =====
@@ Line 112: / Line 112: @@
 After execution, the VoiceXML result of <exit> tag and the property ‘expr’ are accessible by the variable VXML_RESULT.
-Example:
+** VXML_ERROR **
+After execution, the VoiceXML application notify the error cause, if the VoiceXML session cannot be launched.
+  * VXML_ERROR=(empty) ; No error occurs.
+  * VXML_ERROR=INITALISATION ; Session refused, Asterisk module not connected to the VoiceXML browser.
+  * VXML_ERROR=LICENSE ; Session refused, license locking
+  * VXML_ERROR=ACCOUNT_LIMIT ; Session refused, max session for the account reached.
+  * VXML_ERROR=SPEECH ; Session refused, cannot allocate the Speech (ASR) ressource.
+  * VXML_ERROR=TTY/TDD ; Session refused, no TTD availabe.
+  * VXML_ERROR=BILLING ; Session refused, billing interface refuse the session.
+  * VXML_ERROR=INTERPRETER ; Session refused, critical error with the VoiceXML browser connection.
+Example use with an URL parameter:
 <code>
 [incoming]
@@ Line 121: / Line 136: @@
 </code>
+Example to catch the Vxml() errors :
+<code>
+exten => _X.,1,Vxml()
+exten => _X.,n,NoOp(${VXML_ERROR})
+exten => _X.,n,GotoIf($["${VXML_ERROR}" == ""]?hangup)
+exten => _X.,n,Busy()
+exten => _X.,n(hangup),Hangup()
+</code>
 ===== Asterisk Online Help ======
@@ Line 216: / Line 239: @@
 The following entries are the Asterisk CLI commands for the VoiceXML browser.
-Example:
+===== VoiceXML example ======
 Add extensions to the Asterisk dial plan /etc/asterisk/extensions.conf:
 <code>
@@ Line 226: / Line 250: @@
 You can create and edit the file /root/example.vxml with the GNU text editor, VI, for example.
+<code>
+# vi /root/example.vxml
+</code>
 NOTE:
@@ Line 231: / Line 259: @@
 This example will work if you have text-to-speech configured.  If not, use a pre-recorded wav or gsm file to replace the “Hello world!” text by an <audio> tag.  For more information, see the format extensions supported by Asterisk.
 <code>
-<block><audio src=”hello.wav”/></block>
+<?xml version="1.0"?>
+<vxml version = "2.0" xmlns="http://www.w3.org/2001/vxml">
+ <form>
+  <block><audio src=”hello.wav”/></block>
+ </form>
+</vxml>
 </code>
 Save the file in the same directory as the VoiceXML script (relative reference in this example).
 Reload the extensions configuration with:
-*CLI> extensions reload
+<code>
+CLI> extensions reload
+</code>
 Call the service by calling:
@@ Line 255: / Line 291: @@
 /tmp/log.txt (default configuration)
 </code>
-**Core files**
-Collected files should be sent by email to Technical Support (support@i6net.com).
 **Log Files**
@@ Line 310: / Line 342: @@
    - An Apache/PHP script exists generate the traces from a standard Internet browser (Internet Explorer, Mozilla/firefox...). Get it from our web site
    - At the end of the trace record, don’t forget to stop it to recover optimal real time function. With the V4.x release, you can dynamically enable/disable the interpreter traces with an Asterisk *CLI> command.
-Simple traces for the VoiceXML development:
-<code>
-*CLI> vxml debug interpreter dev
-</code>
 Full traces:
 <code>
-*CLI> vxml debug interpreter all
+*CLI> vxml debug interpreter
 </code>
@@ Line 324: / Line 351: @@
 <code>
 *CLI> vxml no debug interpreter
-</code>
-Restore the log traces:
-<code>
-*CLI> vxml debug interpreter log
 </code>