Article ID:	273
Last updated:	November 02, 2006

Would you like to...

Print this page

Post a comment

User Opinions

No users have voted.

---

How would you rate this answer?

Helpful

Not helpful

Thank you for rating this answer.

SUMMARY

This article explains what kind of session and element data might cause problems for VoiceXML Insert elements, and how to resolve this issue.

SYMTPOMS

The voice browser is throwing an error.semantic event, and your voice application uses a VoiceXML Insert element with the "Include: All Element/Session Data" option checked in its element configuration (on the "General" tab).

RESOLUTION

This error occurs when one or more session or element data variables includes a period (.) in their name.  For example, the following variable names would cause this issue:

• session.my.var
• this.is.my.var
• com.mycompany.myvar

The means by which Audium Call Services makes element and session variables available to the VoiceXML used by VoiceXML Insert elements is to declare all of these variables in the root document using <var> elements.  However, as section 5.1.3 of the VoiceXML 2.0 specification details, a period is used to delimit the scope prefix from the variable name.  So when a variable name such as "this.is.my.var" is encountered, the voice browser attempts to evaluate "this" as a scope, and fails with an error.semantic event.

To resolve this issue, rename your element and session data to not use periods.