VXML Server: VXML browser cannot stop the execution of the VXML node, when audio file from the previous audio node is missing
VXML browser cannot stop the execution of the VXML node, when audio file from the previous audio node is missing.
|Problem Summary|| When the audio node is executed, the VXML browser tries to fetch the audio file and simultaneously posts a HTTP request to the new VXML document. The VXML Server returns the next VXMLDocument(which has TTS string to play) when the VXML browser gets a badfetch from the Media Server and sends a HTTP POST request with the errorType as bad.fetch to the VXML server.
Also, the Hotevent defined in the application for badfetch throws VXMLDocument(which includes Error.wav and disconnects the call) but the call does not get disconnected.
|Error Message/Symptom||Hotevent document is not executed, and as a result call never drops and goes on.|
|Possible Cause||The nature of the VXML browser is such that once the VXML document starts processing, it cannot be interrupted. This results in the VXML document being executed before the next node which will eventually drop the hotevent VXML document.|
|Recommended Action||Use a dummyObject which will halt the execution of the browser until object tag finishes. This ensures that the interpreter sends 404 badfetch in the POST request and will process the Hotevent instead of the next node.|
|Release||CVP 8.0 ESxx. onwards|
|Associated CDETS #||CSCug77989. For more information on dummyObject,VXML syntax, see the attachments in CDETS.|