CallXML Logging De-Mystified

The logger, as previously mentioned, takes some insight in order to correctly interpret the output. We are always trying to make the logger a better tool for our developers, and we will continue to add helpful suggestions to the error statements that will assist you in your debugging. What follows is a breakdown of the more common messages, what they mean, and what to look for in the event that you see them when running your application.

event: error "telephony" (server error 404)
This error occurs when we have a reference to a URL value, but the resource returns a server error 404 (file not found), such as the following snippet of code:


<playaudio value="Bogus.wav"/>

Check to make sure that all url references are valid, (playaudio etc)

event: error "event" (invalid target session identifier for external event)
attempting to conference with a session that is no longer up

event: error "document" (invalid number value) error in the Voxeo Logger
This error will appear when using the <playnumber> element, and the the 'value' attribute has an improper setting, 9such as one that is over 50 characters long, for instance)

event: error "document" (No handler was found for event type hangup)
Seeing this in the logger indicates that a hangup was detected by the CallXML system, but no event handler matching this hangup condition is present in the code.

warning: error (2, 7) "The XML or Text declaration must start at line/column 1/1", please check your script
This error thrown to the Logger is indicative of having whitespace present before the initial XML declaration. Open the URL for the code in IE, and choose 'view source' to confirm and correct.

event: error "telephony" (telephony error during money playback)
This error will be thrown when using the <playmoney> element and having the value set to an unsupported setting, such as:


<playmoney value="0.003"/>

LOG "'simline' is deprecated. Use the 'log' tag instead." (non fatal)
This is a non-fatal system message which simply reminds you that the <simline> element is deprecated in favor of the <log> element.

warning: error (21, 10) "Expected end of tag '_____'", please check your script
event: error "document" (Error on line xx: Expected end of tag '______')
Regardless of the specific tag mentioned in this line of output, the message is the same, and indicates that the code is missing a closing tag somewhere. Open the URL of the code in IE to check for parsing errors.

event: error "telephony" (cannot determine the value URL type)
This error message thrown to the Logger indicates that an element is missing a required attribute or attribute + value set, such as having an <inputaudio> element without the required 'playvalue' attribute.

event: error "document" (Error on line 10: Invalid boolean value.)
This error is a simple one, and indicates that we have an improperly formatted value for a boolean attribute, such as 'caching', or <recordaudio beep="okeedokee"/>. Check the element guide to ensure that you have the correct values set for your attributes.

event: callfailure "unreachable"
event: externalevent "unreachable"
This error occurs when the we have an illegal call value specified, such as the following examples demonstrate:


<call value="tell::11122233333"/>  
<call value="11122233334"/>

event: error "execution" (document for child session to run could not be fetched (server error 404))
This error occurs when the child session specified in the <run> tag points to an invalid file, such as:


<run value="calltarget_Bogus.xml"/>

event: error "event" (invalid target session identifier for external event)
The 'little sister' of the above error, this will occur when we use the <run> tag, and point to an invalid parent or child session, such as :


    <assign var="ParentSessionID" value="$sessionn.ID;"/>

event: hangup
This is a non-fatal error, and simply informs the developer that a hangup has been detected in the application.

event: error "document" (Error on line __: empty value)
This error informs us that there is a missing/empty attribute value on the line mentioned which needs to be corrected. Check your code at the line mentioned in the logger, and ensure that all attributes have proper values assigned.

event: error "document" (invalid target for goto or next attribute)
Shame on you. This error will only be present in the Logger's output stream when there is a <goto> or a <next> which points to an undefined target:


<goto value="#Doesnt_Exist"/>

event: error "document" (Error on line 12: invalid time value)
This error is thrown to the Logger when there is an invalid time denomination specified. Remember, that time formatting for attributes allows only (h|m|s|ms) values, so the following example would throw this error:


<wait value="23minutes" termdigits="*"/>

event: error "document" (Error on line 41: invalid termdigits value.)
This event is thrown in only one circumstance; for some reason, you have decided to enter a really crazy value for a termdigit attribute:


<termdigits="z>"/>

Your punishment for doing something so dopey: Fifty lashes with an overcooked strand of spaghetti. And get off the drugs.

warning: error (9, 6) "A '<' character cannot be used in attribute 'value', except through <", please check your script
This is a pretty common error, which is often due to the bane of all developers: a typo. This error indicates that we have mistakenly added a value using a single quote rather than a double quote:


<assign var="MyVar" value="Penn'/>

Got a funky logger error that isn't covered here? Let us know that we need to list it, along with the code that generated the error, and we can add it for you.

ANNOTATIONS: EXISTING POSTS

0 posts - click the button below to add a note to this page

Getting Support Help

| TOC

| F: XPath