This document explains what kind of session and element data can cause problems for VoiceXML Insert elements and how to resolve this issue.
The information in this document is based on Cisco Unified Call Services, Universal Edition, and Cisco Unified Call Studio, Universal Edition.
Refer to Cisco Technical Tips Conventions for more information on document conventions.
Symptoms: The voice browser throws 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 its name. For example, these variable names would cause this issue:
The means by which Cisco Unified Call Services makes element and session variables available to the VoiceXML used by VoiceXML Insert elements is to declare all these variables in the root document with the <var> elements. As Section 5.1.3 of the VoiceXML 2.0 Recommendation 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.
In order to resolve this issue, rename your element and session data without the use of periods.
The Cisco Support Community is a forum for you to ask and answer questions, share suggestions, and collaborate with your peers.
Refer to Cisco Technical Tips Conventions for information on conventions used in this document.