error_id 1 and error_id 25032 caused by an unsupported application design

If a voice application terminates with CHP coredump, error messages error_id = 1 and error_id = 25032 are reported from the CHP process and a core file /var/adm/ras/dirTalk/core.CHP is generated.

The problem is caused by a VoiceXML application that invokes a state table, which in turn then invokes another VoiceXML document, giving an application flow like the following:

VoiceXML -> state table -> … -> state table -> VoiceXML

where the route back to VoiceXML is by using an InvokeStateTable action to call the JavaApplication state table. This design is causing the CHP coredump, and is not supported.

To return to VoiceXML again, avoiding the problem, the application should be coded to just exit the state tables. The call will then naturally end up back in the original VoiceXML application, and can then be handed off to the new VoiceXML application through a goto, submit or similar operation.

Blueworx Voice Response does support handing a call off to VoiceXML after a state table, but only if the call has not already been in a VoiceXML application. So an application flow like the following is supported:

state table -> VoiceXML

using an InvokeStateTable action to call the JavaApplication state table.