on 01-24-2014 02:07 AM
Janine,
You can do this using a Java call end class that sends a custom VoiceXML document as the final resposne after hangup. In this case, the VoiceXML document is a modified subdialog return which simply returns the caller_input and FromExtVXML variables with your data as required.
Attached is a sample end class that builds the required VoiceXML to perform the custom subdialog return and invokes it using the setCustomVxmlResponse method. This returns data that will be successfully propagated back into the ICM database. You can see that the caller_input and two of the FromExtVXML values are set to constants for testing but clearly these can be set to whatever element or session data you wish.
There is one small thing to be aware of. Because this now returns from the subdialog normally with data, the error code is set to 0 rather than 1 and the RunSriptResult now returns successful status. You can of course return some data in caller_input for example to indicate in the ICM data that a hangup happened and distinguish this from exit via the normal subdialog return element.
Remember also that the script won¿t execute any more nodes after the hangup so that does rule out populating normal call variables with the returned data in the ECCs.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: