Article ID:	54
Last updated:	January 08, 2007

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

A VoiceXML Insert element has been created that should set some element or session data, but this data is not available when the VoiceXML Insert element is done.

SYMPTOMS

Although the data is being submitted through a namelist (i.e. part of a <SUBMIT>element), it is not being stored in element or session data as expected.

RESOLUTION

Since the data is already being submitted to Audium, it is easy to fix this problem.  Audium Call Services expects VoiceXML variables holding element and session data to be declared following a specific naming convention:

For element data:
element_log_[VARNAME] (e.g. <ASSIGN name="element_log_myvar1" expr="'some string'" />)

Note that the "log" portion of this name can be changed to "nolog", if you would not like the new value of the variable to be recorded (e.g. <ASSIGN name="element_nolog_myvar1" expr="'some string that is not logged'" />).

For session data:
session_[VARNAME] (e.g. <ASSIGN name="session_mysessionvar1" expr="'some other string'" />

If variables are declared with these names and submitted back to Audium Call Services, the matching element and session data will be created and become accessible to other parts of the application.

For more information about naming conventions used in VoiceXML Insert elements, please refer to the User Guide.