Article ID:	51
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

An application that uses a custom voice element logs an error during execution that mentions a problematic exit state.

SYMPTOMS

The error message:

SERVER ERROR: An invalid element/exit state pair was returned: element was ________ and exit state was null

is present in the application's logs, where the blank is filled with the name of the custom voice element.

RESOLUTION

Normally, voice elements return null when they have produced some VoiceXML, and are not done interacting with the caller.  The VoiceXML is then sent back to the voice browser, and interactions with the caller take place.  However, if the voice element returns null but does not generate any VoiceXML, this error message will be produced.  This error message is often seen when extending an existing element, and relying on that element to produce VoiceXML, while manipulating the variables that it works with (i.e. to achieve the functionality of the new element). 

There are two additional situations where this error message will be produced, even though the developer has generated some VoiceXML before returning null:

1) The first form in the VoiceXML is not named "start".  This is the required name of the first form.

2) The developer has manually removed the auto-generated form that is always produced by the VFCs, which normally initializes some variables.  The developer then adds some VoiceXML.

Although VoiceXML is prepared by the developer using VFCs, Audium Call Services treats these error situations as though no VoiceXML was produced, and the error message is logged.

To resolve this error message, the situations described above should be avoided.