Common problems

Call is answered but it does not behave as expected

There are several possible errors that might cause this problem:

A configuration error within the VRBE subsystem in the default.cff file and would typically be caused by the following:
- A CCXML application has not been configured successfully within the default.cff file.
To solve the problem, do the following:
- Check your nodes log file to see if it contains the following text:
  INFO: Inbound call to 1005 rejected. Reason=Unknown called number.
- Check that the correct CCXML application is configured and that the file name and paths are correct for the CCXML application. Refer to Blueworx Voice Response for AIX: Deploying and Managing VoiceXML and Java Applications for further information.
- Check that the telephone line is mapped to the CCXML root application.
A syntax error that might have occurred when loading the CCXML document and would typically be caused by:
- An invalid CCXML element.
- Incorrectly terminated element
- An expected element is missing. For example, a <transition> element without a <eventprocessor> element.
- The required CCXML document can not be loaded and found.
To solve the problem:
- Check the CCXML Interpreter log file for any error that might have occurred during document parsing. If an error has occurred, a CCXML Parser error will be reported in the log output, giving an indication of the line number and reason for the error. For example,
```
 INFO:  CCXML. Document parse error  The element type "transition"
must be terminated by the matching end-tag "</transition>". at line 88:7
http://www.example.com/example.ccxml 
```
- Check that the filename and paths in the CCXML Document are correct for the CCXML applications.
A runtime error might have occurred and would typically be caused by:
- Referencing variables or attributes which might not have been defined.
To solve the problem:
- Check wildcard transitions. These transitions might have picked up an unexpected or a non-handled event, resulting in unexpected behavior. For information on wildcard transitions, see Error handling, Using a wildcard transition to catch and log any unexpected events.
- Check that the order of transitions in the document is as expected.
These runtime problems should generate error.semantic events which can be caught with an error.semantic transition. Event variables should contain information about the cause of the error and, wherever possible, the element name. The following example contains a sample error.semantic transition:
```
<transition event="error.semantic" name="evt">
	<log label="error.semantic caught" />
	<log expr="'a '+evt.name' error condition has occurred on
            ['+evt.tagname+'] tag '" />
	<log expr="'  giving an error=['+evt.reason+']'" />
</transition>			
```

An expected dialog is not played

Check whether there are errors in the dialog by running it outside the CCXML environment.

Check the log.x.log file for dialog errors. See Formatting the log file.

Document reports an error and exits unexpectedly

This can happen when an error is found within the error.semantic transition. If an error.semantic event is thrown within an error.semantic transition, it will result in an endless loop of error.semantic events. The CCXML Browser will detect this and exit.

A session shuts down unexpectedly

Check the log file for uncaught error events.