This section describes the errors that the Blueworx Platform can generate:
All errors, warnings and info messages that occur will be logged out to the relevant component error_X.out files (or bvr.out, brm.out or bam.out for start up problems - for example configuration). Listed below are a subset of errors that normally occur due to configuration, infrastructure or application errors. These errors detail steps to be taken to resolve the error. In all other cases Blueworx support should be contacted.
An example error would look like
2015/10/28 10:02:43.647 ########### CONFIG [main - 1] [T000052] WARNING Invalid configuration parameter(s) in configuration file: {invalid_var=Invalid}
This is error T000052 and a problem with the configuration. In this case an invalid parameter "invalid_var" has been specified.
The numbers listed below are trace_ids
T000002
MRCP services failed to start. This can be caused by:
T000052
Incorrect configuration supplied
Check the configuration file bvr.config for the problem specified in the error.
T000152
Invalid SDP received in SIP message
Check the SDP from the remote SIP server is valid.
T000155
Invalid SIP INFO DTMF message received
Check the SIP INFO from the remote SIP server is valid.
T000156
Unsupported Content-Type detected in incoming SIP INFO request
The SIP INFO will be ignored by BVR. Check the SIP INFO from the remote SIP server is expected and valid.
T000158
Invalid SDP received in SIP message
Check the SDP from the remote SIP server is valid.
T000164
Invalid SDP received in SIP message
Check the SDP from the remote SIP server is valid.
T000230
Incoming call has been rejected by the Voice Browser. This error will follow either T000250 or T000267
Check the warning message reason and the earlier error message
T000250
Incoming call has been rejected by the Voice Browser during preload. The requested document could not be fetched. The warning message will contain the URI of the document.
T000252
Unable to create broswer directory. The error message contains the directory that failed to create
Check the file system is not full
Check the parent directory has write permission
T000267
Incoming call has been rejected by the Voice Browser during preload
Check the error message reason
T000344
BVR is unable to write to the bin/bvr.pid file
Check the file system is not full
Check that /opt/blueworx/vr/bin directory has write permissions
Check that /opt/blueworx/vr/bin/bvr.pid has write permissions
T000409
Check bvr.config has all the TTS and Reco services for each locale.
Check local network configuration.
T000437
Unexpected request from MRCP server. No requests should be sent from MRCP servers to BVR
This is a warning and the request is ignored by BVR
T000448
Invalid SIP URI
Check the supplied SIP URI is valid
T000485
Invalid SDP in 200 response during MRCP SIP negotiation
Check the MRCP voice server is configured correctly
T000486
SIP connection to MRCP server failed. This can happen for many SIP reasons including timeouts
Check the MRCP voice server is configured correctly
T000489
Sent MRCP RECOGNIZE that has failed
Check the MRCP voice server is configured correctly
T000491
Socket connection to MRCP server failed
Check the network connection between BVR and the MRCP server
Check the MRCP voice server is configured correctly
T000497
Invalid SDP in 200 response during MRCP SIP negotiation
Check the MRCP voice server is configured correctly
T000498
SIP connection to MRCP server failed. This can happen for many SIP reasons including timeouts
Check the MRCP voice server is configured correctly
T000501
Sent MRCP SPEAK that has failed
Check the error message for more specific reason
Check the MRCP voice server is configured correctly
T000502
Socket connection to MRCP server failed
Check the network connection between BVR and the MRCP server
Check the MRCP voice server is configured correctly
T000555
RECOGNITION COMPLETE message from the MRCP server with content that was not NLSML. BVR only supports NLSML content
Check the MRCP message contains valid NLSML
Check the MRCP message Content-Type header is "application/nlsml+xml"
Check the MRCP voice server is configured correctly
T000559
RECOGNITION COMPLETE message from the MRCP server however the NLSML content could not be processed
Check the MRCP message contains valid NLSML
T000580
Invalid SIP URI
Check the supplied SIP URI is valid
T000635
Failed to define an MRCP grammar
T000636
Failed to define an MRCP grammar
T000664
No completion cause> specified in the RECOGNITION COMPLETE message from the MRCP server
This will be ignored by BVR. Check the MRCP voice server is configured correctly
T000666
Grammar Content-Type has not been set
Check the grammar contains a Content-Type
T000667
Grammar Content-Type is not recognized
T000763
Unable to store the audio recording for the application during the call.
This uses the private audio cache for that particular call, which is located in <audio_dir>/_private/<call_index>
Description for variables in above path:
T000782
Unable to create the private cache for the system.
The private cache is located in <audio_dir>/_private
Description for variables in above path:
Check the file system is not full
Check the /opt/blueworx/vr/audio_dir/ directory has write permissions
T000811
Recognition failed
Check the error message reason
T000813
Unable to start a recognition as the locale in the document (or default) has not been configured
Check the recognition section for the required locale has been setup in bvr.config
T000814
Unable to start a TTS as the locale in the document (or default) has not been configured
Check the TTS section for the required locale has been setup in bvr.config
T000847
Transfer failed, remote party does not support REFER
It is not possible to transfer to this destination
T000848
Transfer failed, malformed SIP URI
Check the transfer to SIP URI is correct
T000849
Transfer failed, malformed URI is not SIP
Check the transfer to SIP URI is correct
T000850
Transfer failed as secure destinations are not supported
It is not possible to transfer to this destination
T000888
Transfer property not set
Check the VXML2 transfer tag is correct
T000890
Transfer destination not set
Check the VXML2 transfer tag is correct
T000892
Transfer locale not set
Check the VXML2 transfer tag is correct
T000912
Unable to convert audio from AU format
Check the input audio is a valid AU file
T000915
Unable to convert audio from WAV format
Check the input audio is a valid WAV file
T000919
BVR is running with a trial license. Maximum call capacity can not be set.
Upgrade to the full product
T000922
The BVR trial has expired because the system date was changed
Upgrade to the full product
T000923
The BVR trial has expired
Upgrade to the full product
T000928
Product has been used before but install date is after the last time product was running
Check the system time is correct
T000932
Unable to retrieve the VM's current local IP address.
Validate that the VM's local IP address is present in /etc/hosts.
T001001
Unable to create grammar cache directory. The error message contains details of the directory that could not be created.
Check the file system is not full. Check the parent directory has write permission.
T001112
Unable to process this type of transfer. Only blind and consultation transfer is supported.
Ensure your application only uses blind and consult transfer.
T001131
Answer machine detection hints supplied in an unexpected format.
Check the answer machine detection hints are supplied as a valid javascript object inside the CCXML document.
T001132
Invalid answer machine detection threshold mode supplied.
Check the thresholdmode is one of "fixed", "offset", or "ratio" in the CCXML document.
T001133
Invalid answer machine detection threshold supplied.
Check the threshold is a valid number in the CCXML document.
T001134
Invalid answer machine detection voice on time supplied.
Check the voiceontime is a valid number in the CCXML document.
T001135
Invalid answer machine detection voice off time supplied.
Check the voiceofftime is a valid number in the CCXML document.
T001136
Invalid answer machine detection amd time supplied.
Check the amdtime is a valid number in the CCXML document.
T001137
Invalid answer machine detection max run time supplied.
Check the maxruntime is a valid number in the CCXML document.
T001138
Invalid answer machine detection beep on time supplied.
Check the beepontime is a valid number in the CCXML document.
T001139
Invalid answer machine detection beep off time supplied.
Check the beepofftime is a valid number in the CCXML document.
T001140
Invalid answer machine detection beep modulation supplied.
Check the beepmodulation is a valid number in the CCXML document.
T001141
Invalid answer machine detection events supplied.
T001142
Invalid answer machine detection value supplied.
Check the answer machine detection hints contain correct values.
T001222
A transfer has failed but the call that was being transferred has been removed from the session
This issue may be a timing problem of shutting down calls whilst transferring if the user hangs up. If this error is seen frequently there may be a more serious problem with transfers - contact Blueworx support.
T001232
A CCXML session started in multiple call mode has ended due to the <exit> tag. The <exit> tag should be used to clean up sessions created by <createccxml>, single call mode and the basic HTTP session creation extension to the web server, but not multiple call sessions. Using <exit> there will terminate all calls owned by the session as well as all VoiceXML sessions started in it.
Either set the configuration to be in single call mode or rework the application not to use <exit> in top level CCXML documents
T001251 or T001256
Both of these errors are caused by a failure in parsing a CCXML document.
Check the syntax of the CCXML document that was to be loaded. Other errors may provide more information.
T001296
A CCXML tag could not be executed due to an incorrectly formatted timecode. Such codes must be in CSS2 time format, for example "10.5s" or "356ms". Check your CCXML document for invalid values.
Check the attribute of the referenced tag in your CCXML document and amend the values so that a CSS2 valid time code will be supplied to CCXML.
T001302
An error has occurred when attempting to fetch the CCXML file.
Check the URI is correct and the resource is available.
T001306
CCXML has failed to start up
Check other errors and the printed error on this message for further details.
T001324
The CCXML document failed to parse due to elements inside an <else/> or <elseif/> tag, which is not permitted by the specification.
Rework the CCXML document to fix this.
T001325
The CCXML document failed to parse as an <else/> element was located outside of an <if>.
Rework the CCXML document to fix this.
T001326
The CCXML document failed to parse as an <elseif/> element was located outside of an <if>.
Rework the CCXML document to fix this.
T001327
The listed CCXML element has an invalid property.
Check the spelling of all properties of the listed element in your CCXML document
T001334
The CCXML document contains an eventprocessor element with a non-<transition> element as a direct child.
All child elements of the eventprocessor must be <transition>s, rework the CCXML document accordingly.
T001335
The listed element is part of the CCXML specification but not supported in our implementation at this time.
Use alternate elements where possible to achieve the goal of that element, or rethink the application.
T001336
The listed element is not a valid CCXML element.
Check the spelling of the element name in your CCXML document.
T001338, T001339
An element in your CCXML document has failed to parse.
Check the syntax of your CCXML document, and if no problem exists contact Blueworx support.
T001352, T001353, T001354
The CCXML parser could not handle your document.
Check the syntax of your document and the output of the exception for a reason.
T001361
Your CCXML document has attempted to evaluate a null or undefined value.
Check that all required ECMAscript variables have been defined, especially in the case where a sub-property of a variable is being used.
T001362, T001363, T001364
A runtime exception was encountered in the ECMAScript environment.
Check your application logging and the javascript expression on the error message to see why an invalid evaluation might have been made.
T001383
An evaluation in CCXML was given a variable name that is either invalid or does not exist
Check the CCXML document for invalid assignments.
T001409, T001412
An invalid scope was given as part of an evaluation in CCXML. For example, trying to access myObj.value.property where myObj or value is null.
Rework your CCXML document to use correct scoping and check values have been set before assigning subproperties
T001415
An <accept> tag was processed in CCXML execution but the connectionid attribute was not set.
The connectionid attribute may be omitted only when processing a BVR-generated connection.* event, otherwise you must explicitly declare the connectionid to use.
T001416
The value supplied as a connectionid for the <accept> tag could not be evaluated
Check spelling and scoping of the variable you are supplying to the connectionid.
T001419
A semantic error has been generated in processing the <accept>
Read the error message supplied and fix the issue accordingly
T001422
You cannot assign to a session variable, they are read only variables set up by the browser
If you need to use an altered version of a session variable, use <var> to create a variable not scoped under session, assigning the altered session.x value
T001424
A semantic error has been generated in processing the <assign>
Read the error message supplied and fix the issue accordingly
T001430
A semantic error has been generated in processing the <cancel>
Read the error message supplied and fix the issue accordingly
T001434
A semantic error has been generated in processing the <createcall>
Read the error message supplied and fix the issue accordingly
T001447
A semantic error has been generated in processing the <createccxml>
Read the error message supplied and fix the issue accordingly
T001456
A semantic error has been generated in processing the <createconference>
Read the error message supplied and fix the issue accordingly
T001462
A semantic error has been generated in processing the <destroyconference>
Read the error message supplied and fix the issue accordingly
T001482
A semantic error has been generated in processing the <dialogprepare>
Read the error message supplied and fix the issue accordingly
T001509
<dialogstart> failed to start up the dialog and is sending an error.dialog.notstarted event to CCXML
BVR will continue running but there may be an issue with your application, unless the dialog was being started whilst the call was shutting down or similar. If the reason on the event indicates any of the ids were invalid check your application for incorrect assignments or contradictions between dialogprepare and dialogstart values.
T001510
A semantic error has been generated in processing the <dialogstart>
Read the error message supplied and fix the issue accordingly
T001517
A semantic error has been generated in processing the <dialogterminate>
Read the error message supplied and fix the issue accordingly
T001521
A semantic error has been generated in processing the <disconnect>
Read the error message supplied and fix the issue accordingly
T001540
A semantic error has been generated in processing the <elseif>
Read the error message supplied and fix the issue accordingly
T001547
A state variable was declared by the <eventprocessor> tag in CCXML but that variable has not been defined
Amend CCXML document to declare a <var> for the statevariable inside <ccxml> but before <eventprocessor>
T001548
An event was not caught by any transition in the CCXML event processor
Check what the event was - if the event does not need a response behaviour (for example send.successful) then consider adding a catch-all event at the bottom of your <eventprocessor> to avoid seeing this message - otherwise you may need to add transitions to handle the encountered event
T001562
A semantic error has been generated in processing the <exit>
Read the error message supplied and fix the issue accordingly
T001575
A semantic error has been generated in processing the <fetch>
Read the error message supplied and fix the issue accordingly
T001579
A semantic error has been generated in processing the <goto>
Read the error message supplied and fix the issue accordingly
T001586
The cond value of the <if> tag doesn’t evaluate to a boolean.
Check the cond values of <if> tags in the CCXML document and amend errors
T001590
A semantic error has been generated in processing the <if>
Read the error message supplied and fix the issue accordingly
T001604
A semantic error has been generated in processing the <join>
Read the error message supplied and fix the issue accordingly
T001612
A semantic error has been generated in processing the <merge>
Read the error message supplied and fix the issue accordingly
T001616
The <meta> tag in the CCXML document does not have a valid content
Check for mistakes in the <meta> tag of the CCXML document
T001617
The <meta> tag in the CCXML document has neither name or http-equiv specified.
Specify what this meta tag is (e.g. if setting the cache-control meta tag, use <meta http-equiv=”cache-control” value=”no-cache”/>)
T001618
The <meta> CCXML tag may not have both name and http-equiv specified
Delete either name or http-equiv from the <meta> tag.
T001619
The value for <meta http-equiv=”...” .../> cannot be the empty string.
Put a value in for http-equiv in the CCXML document
T001621
Name is specified as anything other than seeAlso in <meta>
Other names outside of http-equiv tags are not supported, either delete the tag or use http-equiv if possible.
T001634
One of source and event must be specified in <move> in CCXML
Add attributes to the <move> in the CCXML documents to make it legitimate
T001642, T001643, T001644
<move> has failed due to fetch or other reason respectively.
Check error details for potential issues, check any external documents that might have been fetched are correctly addressed.
T001648
The value supplied as a connectionid for the <redirect> tag could not be evaluated
Check the spelling and scoping of the variable being supplied to the connectionid.
T001652
A semantic error has been generated in processing the <redirect>
Read the error message supplied and fix the issue accordingly
T001655
The value supplied as a connectionid for the <reject> tag could not be evaluated
Check the spelling and scoping of the variable being supplied to the connectionid
T001663
Both src and fetchid attribute of <script> were specified
These two attributes are mutually exclusive, select one to use and remove the other.
T001667
The <script> CCXML tag has a fetch destination specified but also has inline data to process.
Either remove the src and/or fetchid attributes from the script or remove the inline data and make it self-terminating (e.g. <script src=”...”/>)
T001671
A bad URI was supplied to the script.
Fix the URI in the <script> attributes in the CCXML document.
T001672
The CCXML <script> element has no src, fetchid or inline data to actually use as a script
Finish filling out the script element in the CCXML document
T001674
A semantic error has been generated in processing the <script>
Read the error message supplied and fix the issue accordingly
T001675
A fetch error has been generated in processing the <script>
Read the error message supplied to see what issues CCXML had getting the script document - does the document exist, and is it accessible? Has the protocol been correctly stated (e.g. http://www.example.com/script.js)
T001690
A semantic error has been generated in processing the <send>
Read the error message supplied and fix the issue accordingly
T001706
The state variable set on a transition was not defined.
Check the state variable is defined before being used on the transition.
T001708
State variable was not defined in the eventprocessor parent of a transition, but the state attribute of the transition has been set
Either correctly set the statevariable or remove the state attribute from the transition in the CCXML document.
T001717
A semantic error has been generated in processing the <unjoin>
Read the error message supplied and fix the issue accordingly
T001720
CCXML document attempted to define a session variable in a <var>
Instead remove the ‘session.’ from the start of the name, or rename the attribute
T001721
CCXML <var> had a name with a ‘.’ in it. Scope may not be defined in this way.
Either use the name without the preceding scope or use <assign> to set the subproperty of an object.
T001722
Empty name on a CCXML <var>
Specify the name attribute of the <var> element of the CCXML document
T001826
An invalid URI was passed to <dialogprepare> and so could not be prepared
Fix the CCXML document to have a valid URI passed to <dialogprepare>
T001842
The CCXML document attempted to start a Java API application
This functionality is not currently supported on BVR Linux edition, if possible use VXML instead.
T001880
An error.unsupported event has been generated
The CCXML document has attempted to execute functionality that can be parsed but is not supported in BVR. Check the generated CCXML event for more details.
T001881
The CCXML Dialog Manager generated an error.notallowed event
The specified action was not allowed in this state - this may be a timing issue or the application may be written to perform a dialog action multiple times by mistake. Check the CCXML document and logs.
T001953
The CCXML fetch agent has failed to parse part of the fetched CCXML document
Check the resource that was being fetched for errors. The error details on this trace point may have further pointers.
T001999
The CCXML basichttp server failed to start up even though it was configured to do so.
Check that ports can be opened and closed on the machine.
T002020
URI failed to be parsed on the HTTP-POST request from the HTTP server
Check destination on <send> tag in CCXML for a bad URI destination
T002104
The CCXML browser failed to start properly. Check the supplied exception message and the error log for parsing and/or fetching error messages.
Fix the root cause of the problem - this message should not occur unless other errors have occurred first
T003131
The license has expired. The system is limited to 1 call.
Check there is a valid unexpired license file "/opt/blueworx/vr/license/bvr.key".
T003132
The system failed to load the license key file. The system is limited to 1 call.
Check there is a valid license file "/opt/blueworx/rm/license/bvr.key". Check the license file has read permissions.
T003137
The system failed to load the license key file, the license key file does not exist. The system is limited to 1 call.
Check there is a valid license file "/opt/blueworx/rm/license/bvr.key". Check the license file has read permissions.
T003138
The system failed to load the license key file, the license key file is invalid. The system is limited to 1 call.
Check there is a valid license file "/opt/blueworx/rm/license/bvr.key". Check the license file has read permissions.
T003139
BVR licensing has changed. Your current license is now invalid and you have been given a 30 day grace period to contact Blueworx for a new license.
Contact Blueworx for a new license.
T003140
System Identifier does not match License Identifier, as they previously matched you will be given a 30 day grace period to resolve this issue with Blueworx.
Contact Blueworx for a new license with the new system identifier for the machine.
T003141
System Identifier does not match License Identifer.
Check the license has been installed onto the correct machine. If this is a new machine contact Blueworx for a new license with the new system identifier for the machine.
T003142
License key file is invalid. The system is limited to 1 call.
Check there is a valid license file "/opt/blueworx/rm/license/bvr.key". Check the license file has read permissions.
T003143
This BVR license is self-expiring due to system time being significantly changed.
Contact Blueworx for a new license.
T003144
Your BVR license has exceeded its grace period.
Contact Blueworx for a new license.